> For the complete documentation index, see [llms.txt](https://docs.feathery.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.feathery.io/develop/api-authentication/admin-controls.md).

# Admin Controls

How Admins manage OAuth apps, members' personal access tokens, and API keys for the organization.

Admins manage API access for the whole organization from the **Developer** tab in Feathery settings.

| Control                       | What it does                                                                                      |
| ----------------------------- | ------------------------------------------------------------------------------------------------- |
| **OAuth apps**                | Only Admins can create, edit, and delete OAuth apps and their secrets                             |
| **Personal access tokens**    | See every member's tokens in the list and revoke any of them                                      |
| **Let members create tokens** | Turn personal access tokens on or off for the organization; the switch is at the top of that list |
| **Accept API keys**           | Turn API keys on or off for the organization                                                      |

### Review Members' Tokens

Admins see every member's tokens in the **Personal access tokens** list, with who owns each one, its access, when it was last used, and when it expires. Search by owner, name, or the last characters of a token. To revoke one, choose **Revoke**; the token stops working right away.

When you remove a member from the organization, their personal access tokens are deleted. OAuth apps belong to the organization, so they keep working when the Admin who created them leaves.

### Turn Off Personal Access Tokens

Turn off **Let members create tokens**, at the top of the **Personal access tokens** list, to stop personal access tokens for the whole organization. Every member's tokens stop working, and no one can create new ones until you turn it back on. Tokens that haven't expired work again when you do.

### Turn Off API Keys

Once your integrations use OAuth apps or personal access tokens, turn off **Accept API keys**. Requests that use an API key are refused, while OAuth apps and personal access tokens keep working.

Before you turn it off, move everything that still uses an API key, such as Zapier, Power Automate, an MCP connection set up with an API key, or an integration that works inside child workspaces.

### Expiry Emails

* Admins get an email 30 days and 7 days before an OAuth app secret expires. The emails stop once a newer secret for that app has been used.
* Each member gets an email 30 days and 7 days before one of their personal access tokens expires. A 30-day token only gets the 7-day email.

### Audit Log

Actions taken with a personal access token appear in the audit log under the token's owner, with the token named. Actions taken with an OAuth app appear under the app's name.


---

# 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.feathery.io/develop/api-authentication/admin-controls.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.
