What can a Handbooks Administrator do?
In Handbooks, the Handbooks Administrator role has full editing access to the module. A Handbooks Administrator can:
- Create, update, and delete articles and content packs
- Add and hide sections in Simployer-verified articles
- Manage topics
- Manage files in central file management
- Control access to content packs
What can a Handbooks Reader do?
In Handbooks, the Handbooks Reader role has read-only access. A Handbooks Reader can view published articles but cannot create or edit content.
How are user roles assigned in Handbooks?
Handbooks roles are assigned automatically based on the user's role in Simployer One. There is no separate role configuration for Handbooks — access is controlled entirely by the user's standard Simployer One role.
| Simployer One role | Handbooks role |
|---|---|
| Owner | Handbooks Administrator |
| Administrator | Handbooks Administrator |
| Manager | Handbooks Reader |
| Colleague | Handbooks Reader |
Who can manage access to Handbooks content packs?
By default, content packs in Handbooks are not visible to anyone. A Handbooks Administrator controls who can see each content pack by managing its scope of access.
How do I add access to a Handbooks content pack?
You need the Handbooks Administrator role to manage content pack access.
- Go to Content Management.
- On the content pack card, click Manage Access.
- Select an access type: Employee (individual), Department, Team, Office, Employee type, or Organization.
- Select the target from the dropdown.
- Click Add to assign access.
The new access rule appears under Available to on the content pack card.
How do I remove access from a Handbooks content pack?
You need the Handbooks Administrator role to manage content pack access.
- Go to Content Management.
- On the content pack card, find the scope entry you want to remove under Available to.
- Click the × next to that scope entry.
The access rule is removed from the content pack.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article