> For the complete documentation index, see [llms.txt](https://docs.kinesis.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kinesis.network/organizations.md).

# Organizations

Bring your people, projects, compute and billing into one organization.

An organization owns your team's projects, apps, grids and servers, and pays for their usage. Your account is your identity; your role in each organization determines what you can do there.

```mermaid
flowchart TD
  O[Organization] --> M[Members and roles]
  O --> P[Projects]
  P --> A[Apps]
  O --> G[Grids and servers]
  O --> B[Balance and billing]
  A --> C[Serverless capacity or accessible grids]
```

## Start or join

A regular signup creates an organization for you. Signing up through an invitation joins the inviting organization without creating another one. You can belong to several organizations and own up to five.

To create one later, open the account menu at the bottom of the sidebar and choose **Create organization**. Give it a name and URL slug. You become its owner and an admin. The name can change; the slug is permanent.

Invitations appear in email, the notification bell and the [Organizations page](https://portal.kinesis.network/dashboard/orgs). Sign in with the invited email address to join or decline. Invitation links expire after seven days.

Organizations with [SSO](/organizations/single-sign-on.md) can also admit people through their identity provider. First sign-in uses a valid invitation’s role or the organization’s default; existing members keep their roles.

## Switch organizations

The current organization appears under your name at the bottom of the sidebar. Open that account menu and select another organization. Its projects, compute and billing become the current workspace.

Organization pages include the slug in the URL, for example `/dashboard/acme/projects`. A saved link continues to identify the same organization after a rename.

| In the organization          | What lives there                                                                     |
| ---------------------------- | ------------------------------------------------------------------------------------ |
| **Projects**                 | Projects and their apps, with creator and visibility filters                         |
| **Servers**                  | The organization's machines, their grids and who is using them                       |
| **Grids**                    | Capacity available to applications; admins manage it                                 |
| **Monitoring**               | Usage for resources you can see, with a person filter when several members have apps |
| **Cost**                     | Organization spend and resource breakdowns; admins only                              |
| **Organization → Billing**   | Credits, payment methods and invoices; admins only                                   |
| **Organization → Members**   | People, roles and invitations                                                        |
| **Organization → Settings**  | Name, compute and invitation controls, single sign-on and SSH keys                   |
| **Organization → Audit log** | One year of recorded activity; admins only                                           |

Your profile, sign-in methods, API keys and connected apps remain in [Account settings](https://portal.kinesis.network/dashboard/account), reached from the account menu. They are the same identity across organizations.

## Work as a team

| Guide                                                | Learn how to                                                            |
| ---------------------------------------------------- | ----------------------------------------------------------------------- |
| [Members and roles](/organizations/members.md)       | Invite colleagues, change roles, transfer ownership and leave           |
| [Sharing and visibility](/organizations/sharing.md)  | Choose private or organization-wide access and add members              |
| [Organization billing](/organizations/billing.md)    | Understand the shared balance, costs and admin responsibilities         |
| [Single sign-on](/organizations/single-sign-on.md)   | Connect an identity provider and require SSO for browser access         |
| [Move resources](/organizations/move-resources.md)   | Transfer a project, grid or server between organizations you administer |
| [Settings and audit log](/organizations/settings.md) | Control serverless use and invitations, and trace changes               |

Resources stay with the organization when their creator leaves, and their apps keep running. Admins of both organizations can [move projects, grids or servers in the portal](/organizations/move-resources.md). Merging whole organizations remains support-assisted; [contact Kinesis support](/support.md).

## Automate in the right organization

An API key or connected app acts as you, with your role in each organization it can reach. Use `GET /orgs` or MCP `list_orgs` to choose the organization. Organization-level calls take its slug as REST `?org=` or an MCP `org` argument; calls on a project, app or grid resolve it from that resource.

Start with [Authentication and scopes](/api/authentication.md), the [Organizations API](/api/organizations.md), or the [MCP organization actions](/mcp/tools/organizations.md).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.kinesis.network/organizations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.