Permission Overrides

Roles set a sensible baseline, but you sometimes need to give one specific person access to something their role normally doesn’t include - without changing everyone else’s access. Permission overrides let you do exactly that.

What can be overridden

There are two gateable features:

Any member can have their access to either feature toggled independently of their role.

Setting an override

1. Go to Settings → Team.
2. Find the member in the table.
3. Look at the Access column - it shows their current effective permissions (Revenue and Reports).
4. Click the toggle for the feature you want to change.

The change takes effect immediately. The member’s next page load will reflect the new access.

How overrides interact with roles

The logic is: an explicit override always wins. If no explicit override is set, the role default applies.

For example:

• An Admin has revenue = off by default. If you set a revenue override to “on” for them, they see revenue data. If you set it to “off” explicitly, they’re locked out (same as default, but now explicit). If you clear the override, they revert to the role default.
• An Agent has reports = off by default. You can grant reports access for one specific agent (your team lead, for instance) without changing all agents.

Use cases

• Give your operations manager revenue access without promoting them to owner.
• Give your senior agent access to reports so they can review their own metrics.
• Lock down revenue data from a specific admin during an audit period.

Checking effective permissions

The Access column in the Team table shows the resolved effective permissions for each member, taking both their role and any overrides into account. What’s shown is what they actually see - no guessing needed.