Skip to main content

​
OVERVIEW

User management in Oumi is handled from a centralized location within the UI, making it easy to manage access and roles across your organization. To access user settings:
  1. Click your profile icon in the top navigation bar.
  2. Select Organization Settings from the dropdown menu.
  3. View the list of organization members and update roles as needed.
You can also invite new members and track the status of pending invitations.

​
OUMI ROLES

Roles define what actions a user can take at both the organization and project levels. By combining organization-level and project-level roles, you can control access broadly across your workspace while still managing more granular permissions within individual projects.

​
ORGANIZATION ROLES

  • Owner - the top-level role with complete authority, including managing settings, users, and billing. Each organization has a single designated owner role.
  • Admins - have broad management capabilities, such as inviting users and configuring organization settings, but cannot delete the organization or manage payment methods.
  • Members - limited to viewing and working within projects they’ve created or been added to.

​
PROJECT ROLES

Project roles define what a user can do within a specific project.
  • Project Admin - has full control, including managing members, updating settings, and deleting the project.
  • Editor - can actively contribute by creating and modifying resources such as datasets, models, and evaluations.
  • Viewer - has read-only access and can explore project resources without making changes.

​
HOW ROLES INTERACT

Organization and project roles work together to determine a user’s effective access level. Organization owners and admins automatically have full access to every project in the organization, and do not need to be assigned separate project roles. In contrast, organization members do not have access to any projects by default, and must be explicitly added to each project with an assigned role. Roles follow a clear hierarchy within a project: Admin > Editor > Viewer. Higher-level roles inherit the permissions of the roles below them, meaning an Admin can perform all actions available to editors and viewers, and an Editor can perform all actions available to viewers.

​
ROLE ASSIGNMENT & ACCESS CONTROL

A user must belong to an organization before they can be assigned any role within its projects. If a user is removed from the organization, they immediately lose access to all associated projects. Each organization is limited to a single owner. This role cannot be removed directly; ownership must be transferred to another user if a change is needed. Organization owners and admins have visibility into all projects by default, while members can only see and access the projects they have been explicitly added to.

​
ORGANIZATION ACCESS & PERMISSIONS

The following matrix shows what actions owners, admins, and members can perform within an organization.

​
PROJECT PERMISSIONS

The following matrix defines what each role can do within a project, from managing settings and members to creating and using resources.