---
title: "Permissions"
canonical: "https://help.agiloft.com/space/HELP/926646298/Permissions"
format: markdown
---
After users log in to the KB, data access permissions determine what they can see and do. Permissions are managed through roles, groups, and teams. 

- Groups control access to records, fields, and administrative functions.
- Teams organize users for purposes such as record assignment, notifications, and user interface configuration.
- Roles make it easier to combine users' group and team assignments. Each role pairs one group with one team, ensuring that a user’s permissions, interface settings, and notifications remain aligned. When you select a role for a user, Agiloft CLM limits the available group and team choices to the combination defined for that role. Roles are also used to track which employees use assigned licenses.

> ℹ️ **Follow the principle of least privilege**
> ℹ️ 
> ℹ️ When assigning permissions, don’t give users privileges they don't need or don’t have the skills to use safely. For example, a user with the ability to delete all records in a table in one operation can do considerable unintentional damage if they’re not familiar enough with Agiloft CLM's architecture. Only trusted and trained users should be placed in the Admin group because members of this group can make drastic changes to the structure and data of your system.

The articles in this section describe administrator access permissions and provide guidance on configuring groups and teams.

> Macro (children)