Permissions and security
Roles and permissions that survive contact with a real company
Most tools give you three roles: admin, member, viewer. Real companies have someone who approves time off but must not see hourly costs, and someone who issues invoices but has no business reading anyone's performance data.
Resource and action, not job titles
A permission is a pair: a resource (clients, projects, tickets, invoicing, capacity…) and an action (read, create, edit, delete, approve, advance, assign, issue). A role is a set of those pairs, and a person can carry more than one role — what they can do is the sum.
Some actions are deliberately separate from the obvious one. Issuing an invoice is not the same permission as drafting it, because issuing cannot be undone. Assigning work is not the same as creating it, because handing out other people's time is a different decision.
One rule that removes a whole class of bugs
Any action on a resource implies being able to read it. Editing something you cannot see is meaningless, and the screen you edit it on has to open. That single rule kills the most common permission bug there is: the role that can save but cannot load.
Seeing what someone else sees, without their password
When somebody says «that button is not there for me», guessing is slow and asking for their password is worse. An administrator can act on behalf of another person: same menu, same permissions, same blank screens.
Everything done that way is recorded under both identities — who really did it, and on whose behalf. A feature like this without that audit trail is a back door, not a support tool.
Frequently asked questions
Can I stop a role from seeing what people cost?
Yes. Hourly cost and margin hang off their own resources, so a project manager can run delivery end to end without ever seeing a cost figure.
What happens to a person who has no roles at all?
They still see their own work — their tasks, their hours, their time off, their own tickets. That is their job, not a privilege. Roles decide what they see of everyone else.
Is there a log of who changed a permission?
Yes. Permission changes are in the audit trail like everything else, with who, when and from where.
Getting started
Fourteen full days, no card and nothing to install. If it has not saved you work by then, there is nothing to cancel. And if you would rather see it first, book a demo and we will set it up with two or three of your real projects, which is where you find out whether it fits.
What we have written about this
Security
The access list nobody maintains and everybody needs
The uncomfortable question is not what they had access to. It is how they could still get back in, and almost nobody can answer that with confidence.
8 min read
Security
Access that never expires is access still live three years later
Nobody decides to grant access forever. They just do not set a date, which is the same thing under another name.
7 min read
Security
Five fields, written at the moment you grant it
Recording access takes thirty seconds when you grant it and an afternoon when you try to remember it.
6 min read
Security
Technical access is almost always all or nothing
You want them to fix this and only this. What you end up handing over is the key to everything, and both sides know it.
7 min read