Teams and multi-project access

Maintain one roster across Projects, apply access in bulk, and handle joining, detaching, and exclusions safely.

10 min readUpdated 8 September 2026

In short

A Team centralises membership while each attached Project keeps its own Owner, role assignments, module scopes, and optional No access exclusions.

On this page

When a Team is the right model

Use a Team when substantially the same authenticated users work across multiple Projects and someone can responsibly maintain the shared roster.

  • Good fit: the same leadership group runs camps, yearly programmes, or equipment Projects.
  • Poor fit: each Project has unrelated users or a one-off external collaborator list.
  • A Team is for Scoutzy users, not attendee records.

Attach a Project

Only a Project you own can be attached, and its direct access must be clean enough to avoid two competing membership models.

Step by step

  1. 1Open the Team workspace.
  2. 2Choose Add project.
  3. 3Select an eligible standalone Project you own.
  4. 4If it is not eligible, remove non-owner direct members and pending invitations.
  5. 5Attach it and review every Team member's Project access.

Set access in bulk

Bulk access is fastest when people share the same responsibility, but it should not flatten meaningful differences.

Step by step

  1. 1Select a Project in the Team access tab.
  2. 2Choose a role or No access.
  3. 3Choose from that Project's currently enabled modules.
  4. 4Select the members who should receive the same assignment.
  5. 5Apply and review exceptions individually.

Membership and lifecycle changes

Team membership and Project access answer different questions. Leaving the Team removes Team-provided Project access; detaching a Project removes Team access to that Project.

  • Use No access for a member who should stay in the Team but not enter one Project.
  • Remove a member when they should lose all Team-provided access.
  • Detach a Project when it should return to direct access.
  • Transfer Team ownership separately from Project ownership.

Put this into practice

Use this browser-only checklist during your next review.

0/5

Common questions

Can a Team member be excluded from one Project?

Yes. Assign No access for that Project. Their access to other Team Projects is unchanged.

Why can’t I attach my Project?

You must own it, it must be standalone, and non-owner direct members and pending invitations must be removed first.

Continue learning

Roles, module scope, and least-privilege accessAssign responsibility without creating dozens of roles, and keep each person inside the modules they need.Projects: structure, settings, and lifecycleUse Projects as focused workspaces, keep ownership clear, and handle seasonal transitions safely.Troubleshooting Scoutzy access and workflowsDiagnose missing modules, blocked invitations, Team attachment problems, and confusing operational records.