An organization groups Orbit apps and provides a boundary for organization-scoped API access.

## Apps are projects within an organization

The [Orbit API specification](https://api.orbitapps.io/openapi.json) describes apps as projects within an organization.

For example, suppose your team has an app named `Repair requests`. Think of the app as the project and the organization as the group that contains it.

Read [Apps](/concepts/apps) for the project model.

## Token scope limits the apps you can see

A profile-scoped token can list apps across organizations where you have an active membership. An organization-scoped token lists apps only within the organization bound to that token.

In the `Repair requests` example, an organization-scoped token for another organization does not provide access to this app.

The organization boundary does not replace the app's own access rules. Your customers sign in to the app through its [authentication](/features/authentication). An Orbit API token is a separate credential.

## An empty app list needs context

The app-list request accepts an optional `org_id` filter. An organization you cannot access returns an empty `data` array, not an HTTP `403` response.

An empty list therefore does not prove that an organization has no apps. Check the organization identifier and the token's scope before you draw that conclusion.

Use the [List apps reference](/reference/apps) for the request and response fields.