Permissions
Invite and configure permissions for all your team members on orq.ai
Admins
Admins have all the rights within a workspace. Admins are the only ones who can invite colleagues, choose the models that should be available within the workspace, and access the billing settings.
Inviting a new member to a workspace
To invite a new member, head to your orq.ai panel.
Choose Settings > Members and select Invite Colleagues.
Here, you can enter one or multiple e-mail addresses to send the invite to, as well as the team the member will be part of.
Once ready press Invite, an invitation will be sent to all new users who will then have access to your workspace.
Inviting users will increase your seat plan.
Choosing which models are available
Only the admin can see the Model garden, which means that they can choose which models their workspace members are able to use in production (Deployments).
Billing
Only the admin is able to see and change the billing details.
Members
Members are separate accounts for each member of your team within one workspace. Members have a unique name and e-mail address. Members can also belong to a team, which further defines their roles and accesses.
Teams
Teams are used to organize your members into separate groups. Each team has specific permissions across the different Projects existing in the workspace.
Creating a new team
To create a new team, head to your orq.ai.
Choose Settings > Teams and select Add Team.
Enter a Name, and you will be taken to your team configuration screen.
On this configuration screen, you can add existing members and select permissions.
Team permissions
For each Projects, you can define the level of permissions needed for members of the teams over the entities belonging to that Project.
![The team configuration screen lets you create granular permissions scheme so that you only let members have access to the needed resources.](https://files.readme.io/3765ed5-Screenshot_2024-08-13_at_17.22.07.png)
The team configuration screen lets you create granular permissions scheme so that you only let members have access to the needed resources.
You can choose three different roles for permissions:
Role | Description |
---|---|
Project expert | Has all rights on this project entities. |
Developer | Can edit the entities of the project, some actions will be unavailable. |
Read Only | Can view and use the entities of the project, cannot make changes on them. |
None | Cannot view nor interact with entities within that project. |
Updated 25 days ago