Decide who sees what, one role at a time.
Create roles, give each one an access level, and point approval rules at the level instead of a job title. When someone needs a second hub, grant it to them directly. Edit a role once and everyone who holds it updates immediately.
Access is the role, not a list of people. Widen the role and every person on it widens with it, the same day, with nothing to reissue.
The access screen
Permissions per role, per hub.
Roles run down the left, each with its access level. Every HQ appears across the top with its four permission levels. Each cell shows how many of that hub's permissions the role holds, out of the total available.
Editing a role changes access immediately for everyone assigned to it.
Approvals reach the right manager on their own.
Create roles, and set what each one can do.
Change a role once, and everyone who holds it gets the change immediately.
- Start from a preset, or build a role from scratch
- Give the role an access level for approval rules to use
- Grant or remove permissions per HQ, at four levels
- Draft a role with NearSync AI and review it before saving
Set approval rules for eight kinds of decision.
Each tier names an access level rather than a specific person, so it keeps working when people or titles change.
- Write tiers for expenses, leave, discounts and advances
- Add tiers for hiring, procurement, refunds and commission
- Route by access level, by named person, by role, or up the reporting line
- Require a receipt, and escalate after a time you set
Give someone access to a second hub.
The grant belongs to the person, so nothing changes for anyone else with the same role.
- Set a home hub for every member of staff
- Grant an individual access to another hub
- Take the access back whenever you need to
- Apply an approval rule to one hub, or to all of them
Access
Who can do what.
Viewing the roster, changing somebody's manager and creating a role are three separate permissions, using the same four levels as every other part of NearSync.
View the roster, the org chart and who holds which role.
Change a reporting manager, or invite a new user.
Create roles, set permissions and write approval tiers.
Full access to everything, not limited by the permission grid.
Admin is the highest role and is not constrained by the permission grid, so it is worth keeping to the smallest group that genuinely needs it.
One request, routed
The amount decides who needs to approve it.
Every amount range has its own approval tier. The tier decides how senior the approver must be, and how long to wait before escalating. The audit trail keeps the whole story: which tier matched, who approved, and when.
The policy checks the amount and matches it to an approval tier.