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

# Settings

Organisation settings, access, credentials and billing.

**Settings** in the MANAGE group of the left rail.

**Its sub-navigation is role-scoped (you will not see every page below.** An Owner or Admin sees People, General, API keys, Secrets, Environments, Configs, Database, SaaS Connectors, Billing, Roles, Audit log and Trash; a Developer sees API keys, Secrets, Environments, Configs, Database and Trash. The pages a Developer does not get are the administrative ones), People, General, Billing, Roles and the Audit log; Trash shows for everyone.

The table follows the Owner sidebar order, with Trash last.

| Page                                               | Covers                                                   |
| -------------------------------------------------- | -------------------------------------------------------- |
| [People](/manage/people.md)                        | Who is in the workspace, invitations, statuses.          |
| [General](/manage/general.md)                      | Organisation name, timezone, joining by email domain.    |
| [API keys](/manage/api-keys.md)                    | Programmatic access, test and live modes.                |
| [Secrets](/manage/secrets.md)                      | Encrypted values read at runtime.                        |
| [Environments and GitHub](/manage/environments.md) | Deployment stages and review gates.                      |
| [Configs](/manage/configs.md)                      | Per-environment values read at runtime.                  |
| [Database](/manage/database.md)                    | Which Postgres your workflows read and write through.    |
| [SaaS Connectors](/manage/saas-connectors.md)      | Your own SaaS API, and the scopes tenants connect under. |
| [Billing and limits](/manage/billing.md)           | Plan, credits and limits.                                |
| [Roles](/manage/roles.md)                          | What each role can do, and how to narrow one.            |
| [Audit log](/manage/audit-log.md)                  | Every action taken in the organisation.                  |
| [Trash](/manage/trash.md)                          | Deleted connectors, actions and workflows.               |

**Customers** is not here. It is a top-level item in the OPERATE group, and is documented with [Operate](/operate/customers.md).

Your own account is separate from the organisation:

{% content-ref url="/pages/ABxxcQtMkrSaTuhRvHMp" %}
[Your profile](/manage/profile.md)
{% endcontent-ref %}

### Who can reach what

The sidebar itself changes by role, so the first answer to "why can't I see that page" is usually the role you are signed in as.

| Page                                      | Who reaches it                                                                  |
| ----------------------------------------- | ------------------------------------------------------------------------------- |
| Audit log                                 | Owner or Admin: gated by role, enforced at the API layer on `/api/v1/audit-log` |
| People, General, Billing, Roles           | In the Owner and Admin sidebar; absent from a Developer's.                      |
| Secrets                                   | The `Secrets` permissions: `read`, `write`, `delete`.                           |
| API keys, Environments, Configs, Database | In both the Owner/Admin and Developer sidebars.                                 |
| Trash                                     | In the Owner, Admin and Developer sidebars, at `/settings/trash`.               |
| Everything else                           | Per the permission matrix in [Roles](/manage/roles.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.fastn.ai/manage/manage.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.