Team access records who has access to which of your business systems, and at what level: admin, user, or read only.
Why it deserves a screen
Most small businesses cannot answer "who has access to what" without opening six products and checking each one. That is fine until somebody leaves.
Offboarding is where the cost lands. A person who has left keeps whatever access nobody remembered to remove, and nobody remembers because the list only existed in the head of the person who set it up. A single page you can read down is the whole point.
Granting and removing
Add a person against a system and choose the level. Access shows as a badge you can select to revoke.
Removing access here is a record of the decision — the change still has to be made in the system itself. Treat this as the list you work from, not the switch.
The habit that makes it worth keeping
Two moments, and both are easy to miss:
When somebody joins, record what they were given as you give it. Reconstructing it later takes ten times as long.
When somebody leaves, work down this page the same day. Not the same week.
Reviewing it quarterly catches the third case, which is the most common of the three: access granted for one job, three years ago, still live.
Not the same as roles in Omnyra
This tracks access to your other systems — the field service software, the accounting package, the email platform. What somebody can see and do inside Omnyra is separate, and covered in roles and permissions.