> For the complete documentation index, see [llms.txt](https://gradeapp.gitbook.io/gradeapp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gradeapp.gitbook.io/gradeapp/getting-started/first-time-setup/permissions-table.md).

# Permissions table

When creating or editing a custom role, you'll be presented with a permissions table. This table is organized by modules (or sections) of the CRM/ERP application, and each module has several permissions associated with it. The permissions table allows you to granularly control what users can do within each module.

The permissions table has the following columns:

1. **Module**: This column lists the various modules or sections of the application, such as Leads, Clients, Finance, and so on.
2. **Add**: This column determines whether users with the current role can create new records or entities within the corresponding module.
3. **View**: This column determines whether users with the current role can view the records or entities within the corresponding module.
4. **Update**: This column determines whether users with the current role can edit or update the records or entities within the corresponding module.
5. **Delete**: This column determines whether users with the current role can delete the records or entities within the corresponding module.

To set the permissions for a custom role:

1. Locate the module you want to configure in the "Module" column.
2. For each permission (Add, View, Update, Delete), select the appropriate checkbox to grant or revoke that permission.
   * Checked = Granted
   * Unchecked = Revoked
3. Repeat steps 1-2 for each module to configure the permissions as needed.
4. Once you've finished setting the permissions, save the custom role.

It's important to carefully consider the permissions you grant to each role, as this will directly impact what users can do within the application. Granting excessive permissions can compromise security, while overly restrictive permissions can hinder productivity.

We recommend following the principle of least privilege, where you assign the minimum permissions required for users to perform their job functions. Additionally, regularly review and audit the permissions assigned to each role to ensure they remain appropriate.


---

# 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://gradeapp.gitbook.io/gradeapp/getting-started/first-time-setup/permissions-table.md?ask=<question>&goal=<endgoal>
```

`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.