Organization User Management

Use Organization -> Members to add people, change roles, reset passwords, and remove access.

For most teams, this is the only access screen that matters. The install-wide Super Admin surface is separate and is only relevant for the person operating the whole Vivd instance.

How access works

Each person has one account.
That account can belong to one or more organizations.
Day-to-day permissions come from the person’s organization role.
The global system role mostly matters only for install operators.

In other words: for normal end users, think in terms of Owner, Admin, and User inside the organization they are currently working in.

Roles at a glance

Role	What it is for	Typical capabilities
Owner	Highest-trust organization role. Keep this to one or two responsible people.	Everything an admin can do, plus protected organization-level ownership tasks such as renaming the organization.
Admin	Day-to-day organization management.	Add and remove members, change member roles, reset another member’s password, create and manage projects, and run organization-level maintenance tasks.
User	Regular project contributor.	Work inside existing projects, use Studio, review content, and handle normal project work without managing the organization itself.
Super Admin	Install-wide operator role, not a normal project-team role.	Cross-organization and instance-wide administration such as instance settings and global user management.

What admins do in practice

From the Members tab, organization admins and owners can:

add an existing account by email
create a new account directly from the organization workspace
change a member between User and Admin
remove a member from the organization
reset another member’s password when local password auth is used

Users cannot manage people or organization settings, but they can still do normal project work inside the projects they already have access to.

Guardrails you should expect

You cannot change your own role from inside the organization workspace.
You cannot remove yourself from the current organization.
Owners are treated as protected members in the normal organization UI.
Organization name changes are owner-only.

These guardrails are intentional. They keep the org-management surface safe from accidental lockouts and make it clear that Owner is a higher-trust role than day-to-day Admin.

Recommended setup

Keep Owner very limited.
Use Admin for people who manage team access or organization operations.
Use User for regular collaborators working inside existing projects.
Re-check membership before launch, project handoff, or staffing changes.