Everyone in an organization has one role. The role decides which pages and buttons they get, and whose data they see there. When someone is missing a page or a button, start with their role.
The four built-in roles
- Admin: every permission, across the whole organization. Settings, billing, roles, pay rates and everyone's time. Give it to the one or two people who run the organization.
- Project Manager: runs the project side. Every project and task, the board's columns and the project reports. It can't invite or remove members, edit roles, or change settings and billing.
- Member: the everyday role. Tracks time on their projects, works the task board, and sees their own time and screenshots.
- Client: read-only, for clients and auditors. Sees only the projects they're attached to and doesn't take a member seat. See Give a client read-only access.
All four are marked System Role. Nobody in your organization can edit or delete them, so a role everyone depends on can't change by accident. If none of them fits, build a custom role.
Check a role, then give it to someone
- Go to Settings → Roles & Permissions. Existing Roles lists every role in your organization.
- Click the eye icon, View Role, on a role. Each area lists its permissions with a tick or a cross, and the scope where one applies.
- To give someone a role, use Quick Role Assignment at the top of the tab. Pick them under Select User, pick the role under Select Role, and click Assign.
You can also change a role on the person's profile. On Members, click Profile on their card, choose a new Role under Organizational Information and click Save Changes. The change applies straight away. If they have StaffVertex open, they may need to reload the page.
The same rules apply in both places:
- Nobody can change their own role.
- Only the organization owner can change someone's role to Admin. The owner's own role can't be changed.
- Client isn't offered. People get it when you invite them as a client, or accept their join request as one.
Permissions are per action
A role is a list of separate permissions, grouped by area: View projects, Create tasks, Edit existing time logs, Mark invoices as paid and so on. That is why access can be so precise. Someone can view time without editing it, or see invoices without marking them paid.
Scopes: whose data
Many permissions also have a scope, which answers "whose?":
- None: not at all.
- Own: their own records. For viewing, that includes what they're part of, such as the projects they're a member of and the tasks they're assigned to. For changing things, it means only what they created themselves.
- All: everyone's, across the organization.
So View time logs at Own or at All is the difference between seeing your own timesheet and seeing everyone's. A few permissions never go below Own, so everyone can always see their own projects, time and profile.
A permission can't reach further than the one it depends on. If View time logs is Own, Edit existing time logs can't be All.
Why someone can't see something
Check in this order:
- Role. Does their role include the permission at all? View the role and look.
- Scope. They may have the permission, but only at Own.
- Project. People track time only on projects they're on, and with View projects at Own those are the only projects they see. See Add members and clients to a project.
- Plan. A feature your plan doesn't include stays visible with a padlock. Opening it shows an Upgrade Plan button instead of the page.
Two things to know
- The organization owner has every permission, whatever their role says. That stops an organization locking itself out. Plan limits still apply.
- Client works differently from the other roles. A client's access comes from the projects you attach them to, not from a list of permissions.