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

# Admins

The Admin role

## Who are Admins?

Admins are members of the Organization that can manage people and invites, teams and security settings.

![The Admin area is Admins only!](https://2875185778-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwEhLPSRTDuhd61395hZu%2Fuploads%2FqMo5yEqAvhK26WCqbRwa%2Fadmins.png?alt=media\&token=695ae08c-36ba-4d60-8ffb-ae6c27156045)

Designate an Admin by changing a person's role in [People Management](/management/people.md).

Admins can:

1. Manage team members.
2. Manage teams.
3. Promote other people to Admin, and demote other Admins. Nobody can change their own role.
4. Manage the Access and SSO settings.
5. Manage team invite approvals
6. Open every team in the Organization without being a member of it.

Only individuals designated as Admins can access the Admin management screens.

## Owners

Owners have the same permissions as Admins. In addition, only Owners can:

* Manage the [plan, subscription, and billing](/management/billing-and-subscription.md)
* Change the AI Settings
* Appoint other Owners
* Delete the Organization (once any subscription has ended)


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.spreo.io/management/admins.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 `build a script that syncs our docs to a CMS` 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.