> For the complete documentation index, see [llms.txt](https://docs.contextual.io/documentation-and-resources/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.contextual.io/documentation-and-resources/tenants/what-is-the-tenant-api/api-keys/api-key-permissions.md).

# API Key Permissions

Once an API Key is created, you can view and manage its permissions on the Permissions tab of the API Key Detail view.

* **Access the API Key**
  * Click on the API Key in the data grid on Tenant API > API Keys to view its details.
* **API Identifier**
  * This is the unique identifier for the API. It is included as the `audience` when retrieving an access token as described on [API Key Settings](/documentation-and-resources/tenants/what-is-the-tenant-api/api-keys/api-key-settings.md)
* **Manage Permissions**
  * A data grid displays the available permissions (read, create, update, delete, execute).
  * You can apply permissions as a wildcard for all current and future Object Types in your Contextual tenant, or select them individually for specific Object Types.


---

# 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.contextual.io/documentation-and-resources/tenants/what-is-the-tenant-api/api-keys/api-key-permissions.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.