What you'll achieve
You will maintain workforce and organisation credentials, team membership and capability records without turning governance signals into performance judgements.
Who this is for
This guide is for an Organisation Collaborator with the permission or assigned action described below. If the navigation or action is missing, check the selected organisation, effective account level, feature state and role before assuming the product is unavailable.
Before you start
Check that you have:
- Verified credential evidence and its owner.
- Approved team membership and roles.
- A shared definition of each organisational capability.
1. Record credentials
Open Credentials. Add certification, accreditation or membership evidence at the correct organisation or workforce scope. Distinguish self-declared, independently verified and expired records.
2. Maintain teams
Open Teams and select or create the team. Confirm manager, members and role information, then use linked workspaces for projects, risks, tasks and compliance.
3. Define capabilities
Open Capabilities. Record what the organisation needs to be able to do, its owner, criticality and evidence. Reuse a capability when multiple teams contribute to it.
4. Connect skills and roles
Use role and skill information to understand required capability and gaps. A gap is a governance signal and development opportunity, not an automatic performance finding.
5. Review evidence and expiry
Check source, issue and expiry dates. Update the record when evidence changes; do not overwrite history to make the current picture look cleaner.
Check it worked
- Credentials show source, scope and current status.
- Team membership matches the approved organisation record.
- Capabilities have accountable owners and evidence.
If something goes wrong
| What you see | What to do |
|---|---|
| A credential definition is missing | Create only the allowed custom candidate and request catalogue review where needed. |
| A person appears in the wrong team | Correct membership through the approved owner; do not change their organisation access as a shortcut. |
| A capability is weak | Record the evidence and action without framing it as blame. |
Human judgement, security and privacy
Workforce data can affect people. Keep the purpose transparent, minimise personal information and separate capability assurance from employee appraisal.
What's next
Set review dates for expiring credentials, team changes and critical capabilities.
Need help?
Use your organisation's approved Backstory support route. Include the organisation, page and action that failed, but do not include passwords, invitation links, secret keys or unnecessary personal or confidential content.