Feature 1
Use role-based access wherever the work happens
Control who can view, contribute to and manage sensitive information across Apollo.
- Role permissions
- Group access
- Record visibility
Capability
Role-Based Access
Control who can view, contribute to and manage sensitive information across Apollo.
The outcome
Support organisation-wide participation without giving every person the same level of access.
How it helps
How Role-Based Access works
This capability connects with the wider Apollo platform, so information can support action, evidence and reporting without being entered again.
Feature 2
Keep the context connected
Use the same people, records and supporting context across Apollo instead of recreating it for each area of work.
- Work from current information
- Connect related activity
- Reduce manual reconciliation
Feature 3
Available across the platform
This shared capability supports every Apollo bundle and works alongside the specialised capabilities your team uses.
- Consistent experience
- Shared platform controls
- Ready for connected reporting
What is included
One capability, connected to the wider platform
Use the capability you need now while keeping its records, work and evidence ready for related capabilities across Apollo.
Included features
- Role permissions
- Group access
- Record visibility
- Administrative roles
- Contributor access
- Access reviews
Connected platform
Keep exploring Apollo
See where this capability is available and the related capabilities and solutions that use the same connected information.
Questions and answers
Questions about Role-Based Access
Practical answers to common questions about managing this responsibility well.
Why does role-based access matter?
Support organisation-wide participation without giving every person the same level of access.
What should role-based access include?
It should cover role permissions, group access, record visibility, administrative roles and contributor access, with enough context to support action and explain decisions.
Who should be responsible for role-based access?
Ownership should sit with the person who can make decisions and keep the information current. A specialist or governance team may provide the method, but accountability should not be left with an unnamed group.
How do you keep role-based access current?
Set review dates according to risk and reassess after relevant incidents, material change, new evidence or overdue follow-up work. Preserve the history so changes remain explainable.
What evidence should be retained for role-based access?
Keep the source information, owner, review and approval history, supporting documents and resulting actions needed to show what was considered and what happened next.
See Role-Based Access in Apollo
Book a focused demonstration and we will show how the capability fits your current responsibilities, existing information and next practical priorities.