> For the complete documentation index, see [llms.txt](https://docs.digitalapi.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalapi.ai/api-gateway/setup/managing-your-organisation.md).

# Managing your organisation

The **organisation** is AILIX's top-level tenant container. Every service, plugin, route, environment, developer, app, user, group, and role belongs to one. The **Organizations** page exposes the current organisation's general settings: name and ownership.

### Reading the organisation settings

#### View and edit organisation settings

**Before you start**

* The organisation owner role or `organization.update`. The first user provisioned holds the owner role; others need it explicitly granted.
* The new value confirmed. Renaming changes the label that appears in the portal's top right; it does not change UUIDs, slugs, or consumer-facing surfaces.

To view and edit settings:

1. From the left sidebar, choose **Setup** → **Organizations**.
2. Edit **Enter organization name** to rename the organisation.
3. Use **Select owner** to transfer ownership to another portal user.
4. Click **Save Changes**.

![Figure 14-1. The Organizations page.](/files/2gSfZjwmxQKu2zbS0khr)

The form on this page exposes:

1. **Enter organization name.** Display name shown across the portal. Required.
2. **Select owner.** The user designated as organisation owner. Owners hold full administrative access regardless of role.
3. **Save Changes.** Persists the edits.

**Verify**

1. The new name appears in the portal's top-right chip within seconds.
2. Refreshing the page shows the new name in the field.

{% hint style="success" %}
**Result:** Organisation settings reflect the change.
{% endhint %}

{% hint style="danger" %}
**Caution:** Owner transfer is irreversible from the side losing it; only the new owner can transfer it back. Confirm the new owner exists as a user, has accepted the invitation, and is reachable *before* clicking save.
{% endhint %}

{% hint style="info" %}
**Note:** This page shows the settings for the organisation you are signed in to. Operators see the organisation they belong to here.
{% endhint %}

Related tasks:

* [Inviting and managing users](/api-gateway/setup/inviting-and-managing-users.md#inviting-and-managing-users): invite the candidate owner before transferring.
* [Defining roles and permissions](/api-gateway/setup/defining-roles-and-permissions.md#defining-roles-and-permissions): grant `organization.update` to other admins so editing settings does not require the owner role.


---

# 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://docs.digitalapi.ai/api-gateway/setup/managing-your-organisation.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.