Back to home
Team

Team & permissions

Roles and per-tab permissions, with a log of who owns what and who changed what.

Team management
With Moshaar
Members24
Roles5
PermissionsPer tab
Roles and permissions

Who sees what, and who can do what —
one matrix you read at a glance.

Switch the role to see its rights, and press any box to toggle it. Turn View off on a tab and the tab disappears from that role's interface entirely — and the line under the table tells you where things now stand.

Team / roles and permissionsPress any box to toggle it
TabViewAddEditDelete
Tasks
Projects & cases
Finance
Files
Calendar
Clients
Conversation
Leave requests

Accountant Sees 7 of 8 tabs. Hidden from them entirely: Chat. Delete is allowed on: Finance.

◻Turn View off and the tab does not appear for that role at all — they do not see it empty⇄Switch the role to see the difference between an accountant, a designer and an intern
Three foundations

A permission is not a lock on a door,
it is the shape of the interface for each role.

A permission per tab, per action

Not admin or user. Every tab has four independent actions: view, add, edit and delete — so the accountant can edit Finance without touching Tasks, and the designer can add files without deleting them.

And private content has its own view right: what is not yours you do not see, even when you can see the tab.
What cannot be seen does not appear at all

Turning View off hides the tab from the whole interface — the role never sees it empty and cannot reach it by URL. The interface itself is built from your permissions, not cosmetically hidden.

So a new joiner sees only what concerns them from the first minute.
The role follows the job, not the person

Define the role once, then put whoever you like in it. An employee leaves and their access ends by itself; another joins and inherits the same permissions with no per-person setup.

And no links or files are left stranded in a personal account after they go.
Tips

Four habits that make permissions serve you instead of blocking you.

Start with the least that lets the work happen

Give a role what it needs today and add more when asked. The reverse — grant everything then claw back — leaves open doors nobody remembers.

Name roles after jobs, not after people

Accountant and Designer outlive the people in them. A role named after an employee becomes a riddle after they resign.

Watch the view-private right

Seeing a tab is one thing; seeing the private content in it is another. Keep them apart: your team sees all the tasks, but only the notes that concern them.

Review roles on every joiner and leaver

Two minutes on a colleague's first day saves a week of I cannot access this. And on their last day, removing the member is enough — no chasing links in somebody's inbox.

Put Team to work

Try it with your team and judge after the first hour.