For licensed Collaborators with permission for this task. Check the selected organisation; feature availability and record access still apply.
What you will achieve
Connect a business capability to the team responsible for it, with a named steward where appropriate.
Team membership, capability ownership, RACI accountability and organisation permissions answer different questions. One should not be used as a shortcut for another.
Before you start
Agree what the team does, which capability it owns and who accepts stewardship. Check the organisation's existing teams and capability catalogue before creating duplicates.
Prepare the team
- Open the intended team from the team catalogue.
- Review its name, description, type, status and time zone. Use Edit Team to correct the record if authorised.
- Review virtual/invite-only settings according to the team's actual operating model, then save.
- Open Members and select Add Member.
- Choose the correct Person, select the offered team role and Add to team.
- Use Edit member role and Save role for a justified change. Verify the saved list before proceeding.
A team role is not evidence that the person has every platform permission needed for their work.
Assign the capability
- Open the capability catalogue and inspect existing capabilities for an appropriate match.
- For a new capability, choose Create Capability.
- Enter a specific name and description: describe what the organisation is able to do, not merely the team name.
- Choose Owner Team and, if agreed, Steward (Optional).
- Review domain, tier, criticality and status against the organisation's definitions.
- Select Create Capability, then reopen it and inspect ownership.
- Connect the relevant processes, controls and delivery context through the capability's available tabs.
Where an entity uses RACI, maintain accountability in its RACI controls. Do not assume a descriptive owner field replaces the accountable assignment.
Check it worked
Follow the capability to its owner team. Confirm the team has the intended members and that the steward understands the responsibility. Ask the responsible person to open and perform the necessary task in their own session.
If something goes wrong
| Problem | Next action |
|---|---|
| A person is absent from the picker | Check organisation membership before changing team setup |
| Ownership is named but work is inaccessible | Ask the administrator to diagnose permissions separately |
| Responsibility moves to another team | Agree handover, update ownership and review linked work |
| A member leaves | Reassign stewardship/accountability before removing them from the team |
Human judgement matters
A name in a field is not acceptance of responsibility. Confirm the handover and retain clear descriptions of the team's scope.
What next?
For the wider context, see Manage credentials, teams and capabilities.
Review control ownership, linked processes and outstanding tasks with the team. Keep ownership current when the operating model changes.
Get help
Ask your Organisation Administrator about access or the task owner about the content. For a platform error, include this guide reference, the affected page and a sanitised message, not confidential evidence or session details.