Feature 1
Assign the right credential to the right people
Select a recognised credential and apply it to the smallest appropriate set of roles or staff.
- Choose a credential
- Select roles and staff
- Set due and renewal timing
Capability
Credential Requirements
Define the credentials required by organisation roles or individual staff and maintain their renewal rules.
The outcome
Make staff credential obligations explicit and create the right work before a record expires.
How it helps
How Credential Requirements works
This capability connects with the wider Apollo platform, so information can support action, evidence and reporting without being entered again.
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
- Credential library selection
- Role and individual assignment
- Initial due periods
- Renewal timing
- Active and retired requirements
- Requirement replacement
Connected platform
Keep exploring Apollo
See where this capability is available and the related capabilities and solutions that use the same connected information.
Credential Library
Start with recognised checks, qualifications, registrations and training records that staff may need for their roles.
Explore capabilityCredential Records
Collect staff credential details and evidence, verify each submission and preserve current and previous credential periods.
Explore capabilityTask Management
Assign, prioritise and track responsibilities across all aspects of your GRC program.
Explore capabilityAvailable in:Organisational GRC
Questions and answers
Questions about Credential Requirements
Practical answers to common questions about managing this responsibility well.
Why does credential requirements matter?
Make staff credential obligations explicit and create the right work before a record expires.
What should credential requirements include?
It should cover credential library selection, role and individual assignment, initial due periods, renewal timing and active and retired requirements, with enough context to support action and explain decisions.
Who should be responsible for credential requirements?
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 credential requirements 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 credential requirements?
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 Credential Requirements in Apollo
Book a focused demonstration and we will show how the capability fits your current responsibilities, existing information and next practical priorities.