Roles and permissions
Not everyone in a company should be able to do everything — approve leave, change settings or manage the team. That's why everyone in the workspace has a role, a simple label that decides what they see and what they can do.
Why roles exist at all
Picture a workspace with no roles: everyone can do everything. One person accidentally changes settings for the whole company, someone approves their own holiday, and a new hire on a trial week can manage the team. That's a fast track to mistakes you can't undo.
Roles solve this without fiddly configuration. Instead of ticking dozens of individual permissions for every person, you assign one role — and it already knows what's allowed and what isn't.
How to think about roles
The easiest way is to picture roles on a ladder, from the smallest scope to the largest. A higher role includes everything the lower ones can do, and adds something on top.
| Role | What it can do (beyond the lower roles) |
|---|---|
| Viewer | Sees the workspace and results, but generates nothing |
| Member | Uses the modules — generates, uploads files, saves results |
| Manager | Approves what needs approval, and manages the team and settings |
| Admin | Full company management inside the workspace |
| Owner | Everything above plus reserved actions — such as granting the owner role |
A few permissions worth knowing:
- Using modules — available to member and up. This is what lets you click Generate.
- Approving — for example leave requests in the HR module, or appointments booked by the voice agent. Needs a role with approval rights.
- Managing the team and settings — adding people, changing roles, configuration — that's manager and admin level.
- Owner-reserved actions — only an owner can grant someone the owner role.
Info
The last owner of a company is protected — they can't be removed or demoted, so the company is never left without someone in full control.
What this means for you
If a button or a whole module simply isn't there for you, think about your role first — it's usually not a bug, it's a deliberate limit. The workspace only shows what you're allowed to use, so a lower role sees fewer options.
Two rules people trip over most often:
- Only an owner can grant the owner role. A manager or admin can't make someone an owner.
- The last owner can't be removed. If you want to hand the company over to someone else, grant that person the owner role first.
Wskazówka
Not sure what role you have? Ask the company owner or your WebImpact manager — both can see it.
What you can do about it
If you need broader access — say you want to approve leave or add people to the team — you can't change that yourself. Ask the company owner or your WebImpact manager to update your role. It's a quick change and takes effect right away.
See also
- Organisations and workspace — what the workspace is and how each company's data is kept separate.
- Services and limits — which modules are enabled for your company and how the monthly limit works.