> For the complete documentation index, see [llms.txt](https://docs.apica.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apica.io/admin/access-management/policy-management/permissions.md).
# Permissions
## Overview
Permissions are essential for regulating access to a resource, ensuring that only authorized users can perform specific actions. Different levels of permissions can be assigned, ranging from read-only access, where users can view the data without making alterations, to full control, allowing users to modify and manage the resource completely.
**Components of a Permission:**
* Permission Name: A unique label for each permission within the policy.
* Resources: The specific assets or data (e.g., databases, files, services) that the permission controls access to.
* Actions: The operations permitted on the resources, such as read, write, delete, or execute.
***
### Add permissions to a policy
To add permissions:
1. Go to IAM > Policy Management.
2. Create a new customer-managed policy or edit an existing one.
3. Click Add Permission.
4. Enter a unique name for the permission.
5. Click Add Resources and select the applicable resources from the modal.
6. Click Actions and select the appropriate actions for those resources.
7. Click Save Policy to apply the changes.
Example: If you choose only the Read action on a Postgres data source, users with this permission will have read-only access.
***
### Remove permissions from a policy
To remove a permission:
1. Navigate to the desired policy under Settings > IAM > Policy Management.
2. Click on Edit button.
3. Click the Delete icon next to the permission you wish to remove.
4. Click Save Policy to confirm the changes.
***
### Permissions types and scopes
All policies created by users are categorized as customer-managed policies. These policies provide full flexibility in defining:
* Permission names
* Resources (e.g., data sources, services)
* Actions (e.g., read, write, delete)
This allows organizations to tailor access control based on specific roles, data sensitivity, and operational requirements.
---
# 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.apica.io/admin/access-management/policy-management/permissions.md?ask=&goal=
```
`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.