Teams Overview

Teams let you organize users into space-scoped groups for ownership, review, access sharing, and workflow routing. Use teams when responsibility belongs to a group rather than a single person, such as a data platform squad, privacy office, steward group, or product support team.

Teams are available when the collaboration.teams feature is enabled.

Where Teams Appear

Surface	Route or control	Use it for
Teams list	/teams	Browse teams in the current space, search by name or description, create a new space team, or review organization-wide teams.
Team detail	/teams/{teamId}	Review team description, members, roles, and team actions.
Product governance	Product Governance tab	Assign a team as a product governance role holder, such as owner or steward.
Documents and Analyses	Access controls	Grant direct access to users or teams.
Repositories	Repository settings	Grant repository access to users or teams.
Workflow builder	Approval target search	Route approvals to users, teams, platform roles, or contextual roles.
Pipelines	Pipeline overview and filters	Assign or filter pipelines by team.
Global search	Search results	Discover team records by name.

Space And Organization Views

Teams are owned by spaces. The space view is the operational view for creating and managing teams.

Organization view aggregates teams across spaces and shows the source space for each team. Use it for discovery and portfolio review, then switch to the owning space before editing team membership or metadata.

Team Roles And Permissions

Role or permission	What it can do
Any space member	Create a team in the space. The creator is automatically added as a manager.
Team member	View the team and participate wherever team membership grants ownership, routing, or access.
Team manager	Edit the team, add and remove members, and change member roles.
Space Admin	Manage all teams in the space, including deletion.

Qarion prevents teams from losing their last manager. If you try to remove or demote the only manager, the action fails until another manager is added or promoted.

Create A Team

1. Open /teams in the space that should own the team.
2. Choose New Team.
3. Enter a team name. Qarion generates a lowercase hyphenated slug from the name, and the slug must be unique within the space.
4. Add an optional description that explains the team's domain, responsibility, or support channel.
5. Choose an avatar color for the team initials.
6. Create the team. You become the first manager.

Good team names are stable and responsibility-oriented, such as Data Platform, Finance Stewards, Privacy Office, or Customer Analytics.

Manage Members

Open a team detail page to manage membership.

Action	How it works
Add member	Search users by name or email, select a user who is not already on the team, and choose member or manager.
Change role	Use the role selector on a member row to switch between member and manager.
Remove member	Remove a user from the team membership list.
Edit team	Update the team name, description, or avatar color.
Delete team	Remove the team from the space. Use this carefully after checking active ownership and access references.

Membership changes affect future access, ownership, and routing decisions wherever the team is used. If a team has direct grants on documents, analyses, or repositories, adding a member can give that person access through the team grant; removing a member can remove that path of access.

Ownership And Governance

Teams can be assigned as product governance role holders from the product Governance tab. Team assignments reduce single-person ownership risk and make accountability visible to consumers.

Use team governance assignments when:

• Ownership belongs to a platform, steward, privacy, security, or domain group.
• Multiple people share a review queue.
• You want product pages to link to the responsible group rather than one individual.
• You need continuity when individual contributors rotate.

Keep the team membership current. A stale team assignment is worse than an individual owner if nobody on the team is still responsible for the product.

Collaboration Access

Teams are reusable principals in collaboration surfaces. When a surface lets you search for "people or teams", choose the team when access should follow group membership.

Common examples:

• Grant a team view, vote, or edit access on documents and standards.
• Grant a team access to analyses and analysis repositories.
• Grant repository view, edit, or manage permissions to a delivery team.
• Route workflow approvals to a team instead of a single named user.

For sensitive assets, review team membership before granting the team access. Team grants are convenient, but they make membership hygiene part of the access-control model.

Deleting Or Replacing Teams

Before deleting a team:

1. Review product governance assignments that reference the team.
2. Review document, analysis, and repository access grants that target the team.
3. Review workflow approval targets that route to the team.
4. Add or move ownership to the replacement team or individual owners.
5. Delete only when the team is no longer referenced or those references have been intentionally retired.

Deleting a team removes its memberships and team-linked governance assignments. Treat deletion as a cleanup action, not a quick way to remove access from a single user.

Troubleshooting

Symptom	Check
You cannot create a team	Confirm you are a member of the selected space and that Teams are enabled for the tenant.
A team name creates an error	The generated slug may already exist in the space. Rename the team or choose a more specific name.
A user does not appear in member search	Search by email, confirm the user exists, and confirm they are not already a member.
You cannot edit or manage members	You need to be a team manager or Space Admin.
You cannot remove or demote a manager	Add or promote another manager first; Qarion requires at least one manager per team.
Organization view shows a team you cannot edit	Switch to the owning space shown on the team card, then open the team there.

Technical Reference

• User routes: /teams and /teams/{teamId}
• Space API family: /api/v1.0/spaces/{slug}/teams
• Organization aggregate: /api/v1.0/organizations/{org_slug}/teams
• Developer reference: Teams API

Related

• Product Details - product governance assignments and team links.
• Documents - document sharing with users and teams.
• Analyses - analysis access grants and repositories.
• Workflows - workflow approvals that can target teams.