Team & account

Roles and permissions

The four roles in a Flamio organization — Owner, Admin, Editor and Viewer — and what each one can do.

Every member of an organization has one role. Roles apply to the whole organization, and they decide what a member can change. What a member can see is never limited: every role, Viewer included, can open every project, recording and report in the organization.

The four roles

RoleDescription
OwnerFull access, including billing and organization settings.
AdminManages members and all content. No billing access.
EditorCreates and edits projects, tests and reports.
ViewerRead-only access to everything.

Each organization has exactly one Owner — the person who signed up and created it. You invite everyone else as Admin, Editor or Viewer.

What each role can do

ActionOwnerAdminEditorViewer
Open every project, recording, report and Scout runYesYesYesYes
See the token balance and usage historyYesYesYesYes
Create projects and change project settingsYesYesYes—
Create, edit and delete test tasks, and launch Scout runsYesYesYes—
Generate AI reports and confirm or reject their issuesYesYesYes—
Create and edit funnels and dashboardsYesYesYes—
Message Flami, the assistantYesYesYes—
Connect integrations and create API and MCP keysYesYesYes—
Invite members, change roles, remove members and revoke invitationsYesYes——
Change the plan, buy tokens and manage billingYes———
Rename the organization and delete the accountYes———

A few buttons stay visible to roles that cannot use them. For example, Create project in the sidebar menu opens for a Viewer, and the page answers "You don't have permission to create projects."

See your own role

Click Settings in the sidebar, then Team under Organization. Your role is the pill next to Your role on the Organization card at the top.

When an Admin or the Owner changes your role, the new permissions apply right away — you don't need to sign out.

Limitations

  • Flamio does not have custom roles or per-permission settings — the four roles are fixed. Instead, pick the closest role in Settings > Team; the line under the Role picker says what it grants.
  • Flamio does not give access to a single project — roles cover the whole organization, and every member sees every project. Instead, use Viewer to remove editing rights. Data that must stay separate needs its own organization, which means a second Flamio account.
  • Flamio does not hide recordings from some members — every role can open every recording, report and Scout run. Instead, control who is a member: remove the person in Settings > Team.
  • Flamio does not transfer ownership to another member yet — Owner cannot be invited or assigned. Instead, make the person an Admin: they can do everything except billing, renaming the organization and deleting the account.