> ## Documentation Index
> Fetch the complete documentation index at: https://tinyanalytics.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Team-Based Site Access

> Grant teams access to selected sites, then restrict organization members so they can see only the sites assigned through their teams.

**Teams** let you give members access to only some of your organization's sites instead of all of them. A team groups members together and grants that group a specific set of sites. By default every member can see all of your organization's sites; when you **restrict** a member, they see only the sites granted through the teams they belong to. Manage teams under **Settings → Teams**.

## When do I need teams?

Reach for teams when different people should see different sites — an agency giving each client's contact access to only that client's site, or a company where one team owns the marketing site and another owns the app. If everyone should see everything, you don't need teams at all: the default is full access to every site in the organization.

## How team-based access works

There are two pieces — a team grants sites, and a member's **restricted** flag decides whether that grant limits them:

<Steps>
  <Step title="Create a team and grant it sites">
    Under **Settings → Teams**, create a team, add members to it, and select which sites it grants. A member can belong to more than one team; their access is the combined set of all their teams' sites.
  </Step>

  <Step title="Restrict the members who should be limited">
    On the organization's members list, turn on **Restrict site access** for a member. A restricted member sees only the sites granted through their teams — every other site is hidden from their dashboard and returns no data.
  </Step>
</Steps>

An unrestricted member still sees all sites, whether or not they're on a team. The restriction is what turns a team into a boundary.

## Verify access

<Check>
  Team access is configured when a restricted member can open only the combined set of sites granted by their teams. Unrestricted members should still see every site in the organization.
</Check>

## Who can be restricted?

Only **members** can be restricted. Owners and admins always have full access to every site and can't be limited by teams — they manage the organization, so restricting them wouldn't make sense. The **Restrict site access** toggle only appears for people with the member role.

<Note>
  Restriction takes effect immediately across the whole product: a restricted member's sites list, per-site reports, and site settings all reflect only their teams' sites. Add them to a team with more sites — or turn off the restriction — and their access widens right away.
</Note>

## Who can create and edit teams?

Owners and admins create, edit, and delete teams, choose each team's members and sites, and set the restricted flag. Members can view the Teams page but can't change it. Editing a team replaces its member and site lists with whatever you select, so it always reflects exactly what's checked.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Can I restrict an owner or admin to specific sites?">
    No. In tinyanalytics, owners and admins always have full access to every site and can't be limited by teams. The **Restrict site access** toggle only appears for people with the **member** role.
  </Accordion>

  <Accordion title="Do I need teams if everyone should see every site?">
    No. By default every member can see all of your organization's sites, so if that's what you want, you don't need teams at all. Reach for teams only when different people should see different sites.
  </Accordion>

  <Accordion title="What happens if a member belongs to two teams?">
    Their access is the **combined set** of all their teams' sites. A member can belong to more than one team, and a restricted member sees every site granted by any team they're in.
  </Accordion>

  <Accordion title="How quickly does restricting a member take effect?">
    Immediately, across the whole product. A restricted member's sites list, per-site reports, and site settings all reflect only their teams' sites, and every other site is hidden and returns no data. Widen their access — or turn off the restriction — and it applies right away.
  </Accordion>
</AccordionGroup>

## Related

<Columns cols={2}>
  <Card title="Roles & permissions" icon="shield-halved" href="/docs/analytics-roles-permissions">
    How roles and team access fit together.
  </Card>

  <Card title="Organizations & members" icon="building" href="/docs/analytics-organizations-members">
    Where you add members and set the restricted flag.
  </Card>

  <Card title="Invitations" icon="envelope" href="/docs/invite-organization-members">
    Invite the people you'll add to teams.
  </Card>

  <Card title="Account settings" icon="user-gear" href="/docs/tinyanalytics-account-settings">
    Your personal profile and password.
  </Card>
</Columns>


## Related topics

- [Analytics Site Settings](/docs/analytics-site-settings.md)
- [Web Analytics Dashboard](/docs/web-analytics-dashboard.md)
- [Organizations and Members](/docs/analytics-organizations-members.md)