# Teams and RBAC

> Group members into teams and use role-based access control to decide who can build, edit, and administer content and data.

*[View this page in the Flax docs](https://flax-analytics.com/docs/administration/teams-and-rbac)*

Teams group members so you can assign access once and manage it as your organization grows. Combined with organization roles, they give you role-based access control (RBAC) across content and data. Admins manage teams under `/app/settings/people`.

## Organization roles and seats

Every member has an organization-wide role and seat, set on the [Members page](/docs/administration/members-and-invitations):

- **Role** — `admin` or `member`. Admins manage the org, including teams, entitlements, SSO, and billing.
- **Seat** — `editor` or `viewer`. Editors create and change content; viewers consume it.

## Team roles

Within a team, each member holds one team role:

| Team role | Can do |
| --- | --- |
| `lead` | Manage the team's content and share the team's dashboards, charts, and sheets. |
| `member` | Work with the team's content according to their org seat. |
| `viewer` | View the team's content only. |

Team roles scope permission to a team's resources; org role governs org-wide administration. For example, a team lead can share resources their team owns, while only an org admin can grant a team access to a new data source.

## Managing teams

Admins can:

1. Create, rename, and delete teams.
2. Add and remove team members, setting each member's team role.
3. Grant the team access to data sources — see [Data entitlements](/docs/administration/data-entitlements).

Content is owned by a team, and its [visibility](/docs/administration/sharing-and-permissions) and grants are evaluated against team membership.

## Related

- [Members and invitations](/docs/administration/members-and-invitations)
- [Sharing and permissions](/docs/administration/sharing-and-permissions)
- [Data entitlements](/docs/administration/data-entitlements)