Roles and permissions
What Viewers, Editors, Managers and Admins can do.
Everyone in your organisation has one of four roles. The role decides what they can do everywhere in Wikidoc. You can see and change roles on Settings›Access; only Admins can change them.
The four roles
Section titled “The four roles”- Viewer: reads and comments, completes their own training and reviews, and takes part in recognition and announcements. Viewers also report issues in Compliance and acknowledge the policies they’re asked to read.
- Editor: everything a Viewer can do, plus creating and editing content: files, process maps, training modules and checklists. In Registers, Editors view and export records, like Viewers; adding, changing and deleting records is for Managers and Admins (see Create a register). In Compliance, Editors draft policies with the policy builder.
- Manager: everything an Editor can do, plus managing the org chart, teams and registers, setting KPIs and seeing analytics for the people they manage. See What Analytics shows. In Compliance, Managers see and add every obligation, approve issue plans and policies, and ask staff to acknowledge policies.
- Admin: everything, including adding and removing members, running performance reviews, managing billing, changing the Compliance settings, and customising the sidebar.
Who can do what
Section titled “Who can do what”| What they can do | Viewer | Editor | Manager | Admin |
|---|---|---|---|---|
| Everyone | ||||
| Read and commentOpen any file, process map, checklist or training module, and comment on it. A file kept in a team workspace opens only for that team. | Every team's files | |||
| Do their own training and reviewComplete assigned modules and checklists, and write and acknowledge their own performance review. | ||||
| Employee recognitionPost a recognition about anyone in the organisation, applaud one, comment on it, and nominate and vote in an award round. Everyone takes part, Viewers included. A recognition is not an approval. | ||||
| Comment and RSVP on announcementsComment on a published announcement, react to one, and reply to an event invitation. Everyone takes part, Viewers included, and an author may comment on their own. | ||||
| Content | ||||
| Create and edit contentWrite files, draw process maps, build training modules and checklists, and organise folders. | — | |||
| Work | ||||
| Work on task boardsCreate a board, and write, move and comment on its cards. A board opens for its members only — being an Admin does not open someone else's personal board. | — | Personal, shared and team boards | Also org and department boards | Also org and department boards |
| Keep registersAdd, change and delete records in Registers, upload their files, and create, change, hide and archive registers. Everyone can view the registers and export them, except Private ones, which only Managers and Admins see. | — | — | ||
| Track obligationsSee every obligation in Compliance, add them, link the work that meets them and export the auditor pack. Anyone who owns an obligation sees it, adds its evidence and marks it reviewed. | Their own | Their own | ||
| Report and fix issuesReport an issue in Compliance or from a checklist task. Managers and Admins see every issue, choose owners, approve plans and cancel issues. An issue's owner, in any role, plans and runs the fix. | Report, and own | Report, and own | ||
| Write policiesDraft a policy with the policy builder. Managers and Admins approve policies and ask staff to acknowledge them. Everyone acknowledges the policies they're asked to read. | Acknowledge | Draft | ||
| Change Compliance settingsSet the industry, country and timezone Compliance uses, and which issues need an approved plan. Only an Admin deletes an obligation or an issue. | — | — | View | |
| Learning | ||||
| Publish training programsAssign a program to people so it appears in their training. | — | |||
| Publish a client portalMake a portal public, or edit one that is already live. Anyone can build an unpublished one. | — | — | ||
| People | ||||
| Post an announcementWrite and publish an official notice or event to the whole organisation, then edit or archive it afterwards. | — | — | Their own, to edit or archive | Anyone's |
| Manage the org chart and teamsChange the reporting structure, create teams, and move people who are already in the organisation between them. A team decides who can see that team's files; it does not add anyone to the organisation. | — | — | ||
| Open others' HR documentsRead and upload the resume, contract and certification slots on a member profile. | — | — | Everyone's | Everyone's |
| Set KPIsCreate and change the goals people are measured against. | — | — | Their department and reports | Anyone |
| Run an award roundOpen a nomination round, set its dates, confirm the winner and announce them. Anyone can nominate and vote in one. | — | — | ||
| Run performance reviewsStart and close the review rounds everyone takes part in, and reassign a reviewer. | — | — | — | |
| Insight | ||||
| See analyticsTraining completion, portal activity, performance reporting, and who recognition is missing. | — | — | Their reports and departments | Everyone |
| Organisation | ||||
| Add and remove membersAdd someone to the organisation by email, including someone who has not created a Wikidoc account yet, and choose the role they arrive with. Approve or decline requests to join, and remove a member to free their seat. | — | — | — | |
| Manage the accountBilling, seats and role changes. | — | — | — | |
| Change the sidebar logo and orderUpload the company logo and icon, and choose the order of the sidebar groups for everyone. Team plan. | — | — | — | |
This is the same table the app shows when you click the ! icon next to Role on Settings›Access, so the two always match.
Things people often mix up
Section titled “Things people often mix up”- A team is not the organisation. Adding someone to a team decides which team files they can see. It doesn’t add them to your organisation or use a seat. Only an Admin can add or remove members of the organisation. See Teams and team workspaces.
- Admins can’t open every task board. A task board opens for its members only. Being an Admin doesn’t open someone else’s personal board.
- Owning an obligation or an issue isn’t a role. Anyone can own one, Viewers included, and works on what they own. Seeing every obligation and issue is for Managers and Admins.
- Everyone can recognise colleagues. Recognition and comments on announcements are open to every role, Viewers included.
Which role should I give someone?
Section titled “Which role should I give someone?”A starting point:
| If they… | Give them |
|---|---|
| Follow procedures and complete training, but don’t write content | Viewer |
| Write or update procedures, process maps and training | Editor |
| Lead a team: organise people, set goals and track progress | Manager |
| Run the account: members, billing and review cycles | Admin |
Who starts with which role:
- Someone who signs up with your domain starts as an Editor.
- Someone you invite starts with the role you choose. The invite form starts on Viewer.
- Someone who asks to join is approved with the role shown on their row. For people outside your domain it starts on Viewer. Change it before you approve if you want a different one.
Only Admins can change roles. See Change a member’s role.
