Members

Estimated reading: 5 minutes

The Members page in Control Plane allows users to view and manage membership in the current project. Depending on their assigned permissions, authorized users can add members, assign or modify roles, and remove members from the project.

Access to project resources is determined by the user’s organization role and, where applicable, their project role.

Prerequisites

To add, modify, or remove project members, you must have the Owner or Admin role with the required member management permissions.

Member List

The Members page displays the users associated with the current project and their assigned roles.

The member list includes the following fields:

Field Description
Name Displays the member's name.
Email Displays the member's registered email address.
SSO Provider Displays the authentication provider used by the member.
Organization Role Displays the member's role at the organization level.
Project Role Displays the member's role in the current project, if assigned.
Actions Displays the actions available for the member based on the current user's permissions.

Add a Member

To add a member to the current project:

1. Navigate to Members.
2. Click Add New Member.
3. Enter the member’s Email Address.
4. Select the required Organization Role.
5. Optionally, select a Project Role to assign project-specific permissions.
6. Click Add Member.

The member is added to the project with the selected role assignments.

Roles and Access

Control Plane uses organization roles and project roles to determine the actions a user can perform. Organization roles define access at the organization level, while project roles determine access to resources within a specific project.

Organization Roles

Organization roles determine the user’s access to organization-level resources and administrative functions.

Role Description
Owner Has full administrative access to the organization and its projects, including ownership-related operations.
Admin Can manage organization members, project resources, integrations, and settings within the permissions granted to administrators.
Member Has standard access to permitted organization and project resources.
Viewer Has read-only access to the organization resources available to this role.
None Does not have access to organization resources through an organization role. Project access may be granted separately through project membership and project-level permissions.

Project Role Override

A project role can be assigned to a user to define their permissions within a specific project. When a project role is assigned, it overrides the user’s default project permissions for that project only.

This allows users to have different levels of access across projects without changing their organization-wide role.

Project Access Matrix

The following table lists the permissions available for each project resource by project role.

Resource Owner Admin Member Viewer
ProjectView, Edit, DeleteView, EditViewView
Project MembersView, Add, Edit, RemoveView, Add, Edit, RemoveViewView
API KeysView, Create, Edit, DeleteView, Create, Edit, DeleteViewNo Access
IntegrationsView, Create, Edit, DeleteView, Create, Edit, DeleteViewNo Access
ObjectsView, Publish, Bookmark, TagView, Publish, Bookmark, TagView, Publish, Bookmark, TagNo Access
TracesDeleteDeleteDeleteNo Access
ScoresView, Create, Edit, DeleteView, Create, Edit, DeleteView, Create, Edit, DeleteNo Access
Score ConfigurationsView, Create, Edit, DeleteView, Create, Edit, DeleteView, Create, Edit, DeleteView
DatasetsView, Create, Edit, DeleteView, Create, Edit, DeleteView, Create, Edit, DeleteView
PromptsView, Create, Edit, DeleteView, Create, Edit, DeleteView, Create, Edit, DeleteView
Prompt Protected LabelsView, Create, Edit, DeleteView, Create, Edit, DeleteViewView
ModelsView, Create, Edit, DeleteView, Create, Edit, DeleteViewNo Access
EvaluationsView, Create, Edit, DeleteView, Create, Edit, DeleteView, Create, Edit, DeleteView
Evaluation JobsView, Create, Edit, DeleteView, Create, Edit, DeleteView, Create, Edit, DeleteView
Default Evaluation ModelView, Create, Edit, DeleteView, Create, Edit, DeleteView, Create, Edit, DeleteView
LLM API KeysView, Create, Edit, DeleteView, Create, Edit, DeleteViewView
LLM SchemasView, Create, Edit, DeleteView, Create, Edit, DeleteViewView
LLM ToolsView, Create, Edit, DeleteView, Create, Edit, DeleteViewView
Batch & ExportsView, Create, EditView, Create, EditView, Create, EditView
CommentsView, Create, Edit, DeleteView, Create, Edit, DeleteView, Create, Edit, DeleteView
Annotation QueuesView, Create, Edit, DeleteView, Create, Edit, DeleteView, Create, Edit, DeleteView
Annotation Queue AssignmentsView, Create, Edit, DeleteView, Create, Edit, DeleteViewView
Prompt ExperimentsView, Create, Edit, DeleteView, Create, Edit, DeleteViewView
Audit LogsViewViewViewNo Access
DashboardsView, Create, Edit, DeleteView, Create, Edit, DeleteView, Create, Edit, DeleteView
Table View PresetsView, Create, Edit, DeleteView, Create, Edit, DeleteView, Create, Edit, DeleteView
AutomationsView, Create, Edit, DeleteView, Create, Edit, DeleteViewView

Organization Access Matrix

The following table lists the permissions available for organization-level resources by organization role.

Organization Resource Owner Admin Member Viewer None
Organization Members View, Create, Edit, Delete View, Create, Edit, Delete View No Access No Access
Organization API Keys View, Create, Edit, Delete View, Create, Edit No Access No Access No Access
Organization Settings View, Update, Delete, Transfer Ownership View, Update No Access No Access No Access
Billing Management View, Create, Edit, Delete No Access No Access No Access No Access
Organization Audit Logs View View View No Access No Access

Manage Project Members

Users with the required permissions can manage project membership from the Actions column in the member list.

Action Owner Admin Member Viewer
View Members Yes Yes Yes Yes
Add Members Yes Yes No No
Modify Member Roles Yes Yes No No
Remove Members Yes Yes No No
Note: Available actions depend on the user's effective permissions. The table summarizes the standard member management permissions for each project role.

Permission Definitions

The following terms describe the actions listed in the access matrices.

Permission Description
View (Read) Allows users to view resources and their configurations.
Create Allows users to create new resources.
Edit (Update) Allows users to modify existing resources.
Delete Allows users to remove resources.
Publish Allows users to publish supported resources.
Bookmark Allows users to bookmark supported resources for quick access.
Tag Allows users to add or manage tags on supported resources.
Manage Allows users to administer resources, permissions, and access settings where supported.
No Access Does not grant permission to access the specified resource through the listed role.

Important Notes

a. Organization roles determine organization-level access, while project roles determine access within a specific project.
b. Assigning a project role changes the user’s permissions only for that project.
c. Changes to organization or project roles take effect immediately.
d. Changes to a member’s permissions may affect their ability to access project resources, including datasets, prompts, evaluations, models, integrations, automations, dashboards, and API keys.
e. The effective permissions available to a user depend on their assigned roles and the permissions configured for the relevant resources.

Share this Doc

Members

Or copy link

CONTENTS
Robility Chatbot
Robility Assistant
Online