> For the complete documentation index, see [llms.txt](https://villagely.gitbook.io/site/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://villagely.gitbook.io/site/start-here/platform-overview.md).

# Platform overview

Villagely is a no-code platform for running both competitive opportunity programs and service-request workflows in one tenant. It connects public intake, staff operations, workflow management, communication, and reporting so teams can support more than one operating model without rebuilding the product around each use case.

## Two tenant apps

Villagely now supports two first-class apps inside the same tenant:

* The **Opportunities app** covers opportunities, applications, application forms, and competitive review workflows.
* The **Service app** covers service queues, cases, requester intake, assignment, and resolution workflows.
* Tenants can use one app or both, depending on whether they run funding programs, service delivery, or a mix of both.

## What you can do

* Publish opportunities with their own public visibility, open, and closing dates.
* Pair each opportunity with a configurable application form and workflow.
* Run service queues with queue-scoped intake, case workflows, and assigned ownership.
* Manage applications, cases, organizations, and user records in the same environment.
* Create public content pages that support discovery, eligibility guidance, and application launch.
* Export data once the work moves from intake to review, service handling, decision-making, and reporting.

## Good to know

* Villagely is organized around a shared record model, so opportunities, applications, service queues, cases, organizations, users, and content can stay linked.
* Each tenant works in its own separate space, with its own forms, settings, languages, and workflow rules.
* Opportunity workflows stay scoped to opportunity and application records, while service workflows stay scoped to service queues and cases.
* Runtime experiences differ by role, so applicants, staff, reviewers, and platform users do not all see the same actions or editing access.

{% hint style="info" %}
**Where to find this**

Applicants or requesters usually start from `/`, public content pages at `/Pages/{pageName}`, and the intake experience itself. Staff usually start from the dashboard at `/Home`, then work in record lists, record editors, the Settings console at `/staff/settings`, and reporting routes.
{% endhint %}

## Next step

{% content-ref url="/pages/Bj99azDIfsInyArgEc7I" %}
[Who Villagely is for](/site/start-here/who-villagely-is-for.md)
{% endcontent-ref %}

{% content-ref url="/pages/WgwaWDO3oiDYxbw7YabK" %}
[Service queues and cases](/site/staff/service-queues-and-cases.md)
{% endcontent-ref %}

{% content-ref url="/pages/6K1Jfr45eYd6zTyhgFqz" %}
[Launch and run a program](/site/staff/launch-and-run-a-program.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://villagely.gitbook.io/site/start-here/platform-overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.