# Workspaces, roles and team invitations

How FlowConsent workspaces organize your banners, what the owner, admin, manager and editor roles allow, and how invitations work.

> Canonical: https://www.flowconsent.com/en/doc/team-and-workspaces
> Last updated: 2026-07-30
A **workspace** represents one organization: every banner lives inside one, and one workspace can host several sites. The **Team** page is where you invite colleagues into the workspace, assign their role, and manage pending invitations — within the user limit of your plan.

## The four roles

Every member has exactly one role in the workspace:

- **Owner** — full control, including changing admins' roles. The owner cannot demote or remove themselves, so a workspace can never end up ownerless by accident.
- **Admin** — manages the team and the workspace.
- **Manager** — can also manage members.
- **Editor** — works on banners without team-management rights. This is the default role for new invitations.

Team management — inviting, changing roles, removing members — is available to owners, admins and managers. Two safeguards apply: only the **owner** can change an **admin's** role, and your own owner row cannot be edited or deleted.

## Inviting a member

Click **Invite a member**, enter the email address and pick a role — **editor**, **manager** or **admin** (ownership is not granted by invitation). The invitation lands in one of two lists depending on the recipient:

- **New-user invitations** — the address has no FlowConsent account yet. The row shows who invited them and waits for account creation.
- **Pending invitations** — the person has an account but hasn't accepted yet.

Either kind can be cancelled by anyone allowed to manage the team, from the row itself.

> [!NOTE]
> The Team page header always shows your current member count against the plan's user limit: **2 users on Free, 10 on Pro, unlimited on Enterprise**. When the limit is reached, sending an invitation prompts an upgrade instead — see [Free vs Pro](/en/doc/free-vs-pro).

## Changing roles and removing members

For active members, the role is edited inline from the member list — pick the new role and it applies immediately. Removing a member revokes their access to the workspace, not their FlowConsent account; they can be re-invited later.

> [!TIP]
> Keep the number of admins small and give day-to-day contributors the **editor** role: they can work on banners while the set of people able to alter the team stays short — which is also what an audit will ask you to justify.

## Next steps

- [Get started with your first banner](/en/doc/getting-started)
- [Compare Free and Pro plans](/en/doc/free-vs-pro)