# Custom Access

Custom Access grants a specific user permission to a record or action on a collection without changing their role. Use it for one-off exceptions (e.g. access to one customer's transactions).

On this page

Overview & List View Quick Start Fields Actions FAQ Related

Overview & List View

Go to Settings → Custom Access from the left menu. List columns | **Column** | **Description** | |------------|-----------------| | Id | Record ID. | | Collection | ERP entity (module/document type). | | Action | Permission action granted (e.g. View, Edit). | | Owner | User who receives the access. | Filters: Collection (contains/equals), Created Date. List actions: New, View, Edit, Delete (multi).

Quick Start

1. Navigate

Go to Settings → Custom Access and click New.

2. Define access

Select Collection, Action, and Owner (user).

3. Save

The user gains the extra permission in addition to their role.

Fields

| **Field** | **Description** | |-----------|-----------------| | Collection * | Target entity or document type. | | Action * | Specific permission to grant. | | Owner * | User who receives custom access. |

Actions

New, View, Edit, Delete — standard list CRUD.

FAQ

Custom Access vs User Role?

Roles define broad module permissions for many users. Custom Access adds a targeted grant for one user on one collection/action.

Can Custom Access remove a role permission?

No. Custom Access only adds grants. Restrict access by editing the user's role or using data filters on User Settings.

When should I use Custom Access?

Use for one-off exceptions — e.g. allow a user Approve on purchase orders without cloning an entire role for one person.

Does Custom Access override branch filters?

No. Data filters on User Settings still apply. Custom Access adds module actions only.

Can I grant Custom Access on reports?

Yes when the collection appears in the Custom Access form — select user, collection, and allowed actions.