Roles

Every member of a workspace has one role. Roles control access to configuration and to other people's data. They don't decide who approves leave: that comes from reporting lines and approval chains.

How it worksCopy Anchor Link

• Owner. Full control, including deleting the workspace. Whoever creates the workspace becomes its Owner, and there is one per workspace.
• Admin. Everything the Owner can do except deleting the workspace or changing the Owner. Admins manage settings such as locations, departments, roles, billing and leave rules, and can read the activity log.
• HR. Runs the workforce and leave: invites and edits employees, configures leave types, policies, approval chains, public holidays and blackouts, sees everyone's requests and balances, records leave on someone's behalf and views org-wide reports. HR can't change locations, departments, roles or billing, can't import or delete employees, and can't see the activity log.
• Employee. Self-service: their own profile, requests and balances, plus the people directory, org chart and team calendar that every member sees.
• Approvals. A request goes to the employee's manager, or through the approval chain on the leave policy. Anyone with direct reports, or named in a chain, approves in that capacity whatever their role. If no chain applies and the person has no manager, the request is approved automatically, unless it falls in a blackout that requires approval; then any Owner, Admin or HR member can decide it.

The Roles page shows what each role can do, permission by permission, and how many people hold it. Roles are fixed; you can't create custom ones.

Good to knowCopy Anchor Link

• Owners and Admins change someone's role on their employee record. Nobody can change their own role or the Owner's.
• A person needs an account before they have a role, so records added without an invite have none until they accept an invitation.

RelatedCopy Anchor Link

• Invite your team
• Approvals
• Approval chains