Users and Groups
Add people to your organization, set their organization role, build groups, and create and revoke group API keys
Organization admins manage members, organization roles, groups and group API keys on the Users & Groups page in the app. Only organization admins can open it. It has two tabs, Users and Groups. What each role can do on environments, packages and workspaces is in Permissions.
Organization Roles
Every member holds one organization role. It sets what they can do across the organization; access to individual environments, packages and workspaces is granted separately.
| Role | Can |
|---|---|
| Admin | Everything in the organization: manage users, groups, API keys, Access Control values and organization settings; create environments; act as Admin on every environment and package; manage every shared workspace |
| Modeler | Everything a Member can. The app also offers modeling actions, but building or publishing in an environment still needs the Admin or Modeler role on that environment |
| Member | Sign in, create workspaces, and use the environments, packages and workspaces shared with them |
The Modeler organization role does not grant access to any environment by itself, and a Member can be made Modeler on a single environment. See Environment Roles.
A group can hold an organization role too, which every member of the group then has. This is also what lets a group API key reach organization-level actions.
Manage Members
The Users tab lists every member with their organization role and the number of access control attributes assigned to them.
- Add people. Enter an email and an organization role. The person gets access immediately, and Credible emails them that they've been added. They sign in with any supported sign-in method that uses that email. For Entra ID, enter the person's User Principal Name (UPN), which Credible matches on.
- Change a role. Pick a new organization role in the member's row.
- Remove a member. Removes them from the organization.
- Access requests. Someone who signs in without access can request it. Organization admins get the request by email, with a link that opens the add dialog for that person.
Adding someone to the organization grants no access to environments or packages. Grant that next, directly or through a group, as described in Permissions.
Manage Groups
A group grants access to many people together. Grant roles on environments, packages and workspaces to the group, then add and remove people as they join or leave a team.
On the Groups tab you can create a group with a name and description, and delete one. Deleting a group removes its organization role and every grant it holds, so its API keys reach nothing; its members keep any access of their own. Open a group to:
- Add or remove members. A member can be a user or another group.
- Set each member's group role.
- Give the group an organization role, or change or remove it.
- Assign access control attribute values to the group.
- Create and revoke the group's API keys.
| Group role | Can |
|---|---|
| Admin | Manage the group's members and details, revoke its API keys, and delete it |
| Member | Hold every grant the group holds |
A group admin can give anyone the group's access. A group admin can add any member of the organization to the group, and that person then holds every role and grant the group holds, including an organization role and its place in $GROUPS access rules. Make someone a group admin only if you'd trust them to grant everything the group can reach.
The group's name is also what $GROUPS contains when a model's access rules check group membership.
From the CLI: cred add group, cred add member <group> user|group <name> admin|member, cred rm member and cred rm group. See the CLI reference.
Group API Keys
Applications, scripts and CI/CD jobs authenticate with a group's API key (also called a group access token). A key acts as its group: what the key can reach is whatever the group holds at the moment of each request.
- Create. Organization admins create keys in the group's API Keys section, choosing a name and an expiry, or with
cred add group-access-token <group> <name>. The key is shown only when it is created; store it as a secret. A key can't create other keys. - Use. Send it as
Authorization: ApiKey <key>, or log the CLI in withcred set-access-token. See REST APIs. - Revoke. Group admins and organization admins can revoke a key in the app, or with
cred rm group-access-token.
A key has every role its group holds, including organization Admin. Keys have no scopes of their own, and there are no personal API keys. Give each integration its own group, grant that group only what the integration needs, and keep people out of groups that hold keys.
What a Key Can Reach
| Grant the group | The key can |
|---|---|
| Viewer on a package | Query that package |
| A role on an environment | What that environment role allows: query every package in it as Viewer, publish as Modeler, manage connections as Admin |
| A workspace role | Use that workspace, only while the group also holds an organization role |
| The organization Admin role | Everything Admin allows, including creating environments |
Creating an environment requires the organization Admin role. If your automation provisions environments, as Terraform and CI pipelines often do, the group needs it:
cred add permission group:<group-name> adminAdd --environment <name> (and --package <name>) to grant on an environment or package instead. Because the grant lives on the group and not on the key, changing or removing it takes effect immediately for every key the group holds. Removing the group's grant is the fastest way to cut off a key.