Skip to main content
Orq.ai lets you manage roles and permissions within your workspace using Members and Teams. This enables you to build a granular access model that fits your organization.
  • Each employee can be invited as a Member
  • A Member has one of three roles, described under Roles: Admin, Developer, or Researcher
  • Members can be grouped into Teams
  • Teams are assigned access to Projects
Developer and Researcher roles and team management are available with the Team add-on and are included by default on the Enterprise plan.

​
Members

Members list showing name, email, team count, and role for each workspace member, with an Add member button.

The Members overview shows all workspace members, their roles, and team assignments.

​
Adding a Member

Each member occupies a seat. Ten seats are included with and Pay as you go; extra seats on Pay as you go are invoiced monthly. Manage seats from Settings → Organization → Billing. See Seats for details.
To create a member, go to Settings → Organization → Members and select Invite. The Add workspace member sheet opens with the Email, Team, and Workspace Role fields; select Add member to send the invitation.
Add workspace member dialog with fields for email, team selection, and workspace role, with Admin, Developer, and Researcher options shown.

Enter the member's email, role, and team. These can all be updated later.

The Workspace Role field sets the member’s role. See Roles for what each role can do.

​
Roles

A role decides what a member can do in the workspace. Each member holds one role, selected when the member is invited and changed later from the member’s row in Settings → Organization → Members. The role applies in every project the member can reach.

​
Built-in roles

Edit member dialog showing the Admin role selected, with Developer and Researcher as alternatives.

Roles are assigned as members are created or edited.

​
Permissions by role

Full access creates, edits, and deletes a resource. View only reads it. Use only calls the resource without configuring it. No access keeps it out of reach. Annotations and log corrections are writable by every role; the Trace or Log itself stays read-only.

​
Teams

Teams let you group members and assign them to Projects. Members use their own role within each team’s projects. The Teams list shows each team’s Name, Members, Permissions, and Last Activity. Select a team to edit it; its row menu deletes it. This lets you model access flexibly, for example:
  • Developers can belong to separate teams, sharing projects or working on independent ones.
  • A Researcher can be assigned to multiple teams, contributing across several deployments.
Project access section showing Default project assigned to a team, with an Add project dropdown listing client-1 and research-and-development.

You can easily add projects to existing teams, letting teammates access new projects immediately.

​
Creating a Team

Go to Settings → Organization → Teams and select Team. The Add Team panel takes a Team name and Description, then assigns Members and Project access. Select Create team to finish.
Teams list on the left alongside an Add Team panel on the right, with fields for team name, description, member assignment, and project access.

Your team configuration screen, where you can add members or configure project access.

​
Assigning Members to a Team

Choose Add member and select a previously created member. Members use their own role within the team’s projects.

​
Assigning Projects to a Team

Choose Add project and select a previously created project.
To learn more about Projects, see Projects.