Teams

Teams let you group organisation members and reuse that group when sharing work. Instead of adding people one-by-one to each container or project, you can link a team and apply access in bulk.

What Teams include

A team has:

• A name
• An owner (the creator)
• Members (organisation users added to that team)
• Linked resources (containers and projects)

Teams are organisation-scoped. They are not available in personal workspaces.

Enable Teams for a workspace

An organisation admin must turn on Teams first:

1. Go to Settings > Workspace > [organisation] > Teams
2. Enable Teams

When enabled, the Teams area appears in the workspace sidebar for that organisation.

Team membership

On a team page, you can:

• Add organisation members to the team
• Remove members from the team
• See current members and team owner

Linking Teams to containers and projects

On a team page, use Connected containers and Connected projects to link resources.

• Linking a container to a team applies that team to the container.
• Linking a project to a team applies that team to the project.
• If you link a team to a project inside a container, MONOid also ensures the team is linked to that container.

You can also add/remove teams directly from container/project Shared With panels.

Permission behavior (explicit)

Access matrix

Container links

When a team is linked to a container:

• Team members are granted container access in bulk.
• Existing and newly added team members can access that container.
• Access is removed when a user leaves the team, unless another linked team still grants access to that same container.

Project links

When a team is linked to a project:

• Team members can access that project via team membership.
• If the project is in a container, container-level access still applies.

Unlinking and deleting

• Unlinking a team from a container removes the team link and linked project links in that container.
• Removing a user from a team may remove container membership if no other linked team still covers that user/container pair.
• Deleting a team removes its memberships and resource links.

Scenarios

A user belongs to two teams linked to the same container

If Team A and Team B both grant access to the same container, removing the user from Team A does not remove access while the user still belongs to Team B. Access is removed only when no remaining team or direct share grants the same container.

A team is linked to a project inside a container

When you link a team to a project inside a container, MONOid also ensures the team is linked to that container. This prevents a project from being accessible without the parent container context.

A team is unlinked from a container

Unlinking a team from a container removes the team link and linked project links in that container. Use this when a team should no longer see that area of work.

Offboarding checklist

When someone leaves an organisation workspace:

1. Remove the user from the organisation membership list.
2. Remove the user from any teams they belonged to.
3. Check linked containers/projects where overlapping team grants may still apply.
4. Revoke or rotate any API keys the user created if those keys should no longer be active.
5. Review organisation integrations if the departing user owned the external account connection.
6. Confirm the user no longer appears in team member lists or resource sharing panels.

Constraints

• Teams work only in organisation workspaces.
• Team and linked resources must belong to the same organisation.
• Only users with management rights can link/unlink teams on containers/projects.

Related pages

• Settings — Workspace configuration and org settings
• Containers — Container model and ownership
• Projects — Project model and ownership
• Tasks — Task-level planning and assignment