# Access should match the action.

Control what your team can view and change across the agency’s records, documents and settings with Vestta permissions.

[Try Vestta for free ](https://crm.vestta.io/register)[How it works ](https://www.vestta.io/en/product/permissions#guide-section-1)

7 days free · no card required

## Team and access

 Agency context

Roles

Permissions define the actions each person can perform.

### Sales agent

An example of access by action

View clients

 Allowed

Edit properties

 Allowed

View documents

 Allowed

Manage commissions

 Restricted

Illustrative product scenes with fictional records. Interactions only change this example.

On this page

## Read and change are different responsibilities

Review permissions by the action the user needs to perform. Viewing operational context does not imply permission to change a property, edit settings or manage commissions.

## Apply the scope through roles

Roles make it practical to assign a coherent set of permissions to the team. Custom roles depend on the account’s enabled plan. Review the actual permission set before granting it.

[Explore this feature ](https://www.vestta.io/en/product/roles.md)

## Documents retain their access rules

A document linked to a client or property still needs the appropriate access. AI assistants and other product surfaces work within the user’s permitted context.

[Explore this feature ](https://www.vestta.io/en/security.md)

## Put your next opportunity in context.

Explore Vestta with the way your agency actually works.

[Start your free trial ](https://crm.vestta.io/register)

7 days free · no card required

## Explore the next connection.

From the first enquiry to the work behind each property.

Source: https://www.vestta.io/en/product/permissions
