Teams Support: grouping users and resources

Overview

Teams are logical groupings of users and resources within a SiteDetour organization. They enable multi-tenant-style isolation inside a single billing entity: one organization, one subscription, but multiple independent resource pools.

The problem Teams solve

Consider a marketing department and an engineering department sharing one SiteDetour account. Marketing owns campaign-driven Smart Links; engineering owns service-level redirects and SSL-protected domains. Without Teams:

• Everyone sees everything. Accidental edits are likely.
• There's no clean way to give a marketer read-only access to engineering's redirects without giving them read access to every redirect.

Teams solve this. Each department gets its own team; each team sees only its own resources.

How Teams work

1. Create teams on the Teams page.
2. Add users to teams. A user can belong to multiple teams.
3. Assign each resource to a team at creation. Redirects, Smart Links, Landing Pages, and Audiences all have a Team dropdown at the top of the editor.
4. Access is scoped by team membership. A View/Edit or Read Only user sees resources only in the teams they belong to. Owners and Administrators see everything across all teams.

Default Team

Every organization starts with a Default Team containing every existing user. Resources created before Teams are migrated into the Default Team. If you never create additional teams, nothing changes for your workflow — everything continues to belong to the Default Team.

Worked example

Setup:

• Organization with 8 users.
• Two departments: Marketing (4 users) and Engineering (4 users).

Configuration:

1. Create team Marketing; add the 4 marketers.
2. Create team Engineering; add the 4 engineers.
3. Assign Smart Links and Landing Pages to the Marketing team.
4. Assign infrastructure redirects to the Engineering team.

Now: marketers see only marketing resources; engineers see only engineering resources; the Owner sees both.

Moving resources between teams

Open any resource editor. Change the Team dropdown at the top right. Save. Access changes immediately.

Common patterns

• Department — one team per department.
• Environment — Staging and Production teams so accidental staging edits can't touch production.
• Agency → client — agencies running multiple clients under one org can create a team per client.

Administrators and Owners

Administrators and Owners see every team's resources. Their team membership is tracked for activity-log purposes but doesn't restrict their access.

Plan requirement

Teams are available on Business and Enterprise plans. On lower tiers only the Default Team exists.

Next steps

• Managing users
• Organizing resources with tags