Permissions
The roles Credible grants on environments, packages and workspaces, how to grant them, and a table of who can do what
Roles on environments, packages and workspaces decide who can administer, model in, query or share each one. Organization roles and groups are in Users and Groups; access rules that limit which sources and rows a caller sees are in Row and Column Access.
How Access Is Granted
Adding someone to the organization gives them no access to environments or packages. Grant it in one of three ways:
- Directly, to a person, on an environment, package or workspace.
- Through a group: grant the role to a group, then add people to it.
- Through a workspace: every member of a workspace gets Viewer access to the packages added to it.
Groups are the easiest to maintain. Set up a few groups with the access each team needs, and add new people to the right group after adding them to the organization.
When you grant a role to a person on an environment or package in the app, Credible emails them about it. From the CLI, cred add permission sends that email only with --notifyPeople. Grants to a group send no email.
People who can't open a resource can request access from the app. The people who can grant it get the request by email.
Organization admins are Admin on every environment and package, and Manager on every shared workspace, without a grant.
Sharing Environments & Packages
An environment holds connections and packages. A role on an environment applies to every package in it, which is the usual way to share packages with the people who build and use them. See Environments and Packages for how to draw environment boundaries.
To grant a role, open the environment's members list in the app and add a user or group, or use cred add permission <user:email|group:name> <role> --environment <name>.
Environment Roles
| Role | Can |
|---|---|
| Admin | Everything a Modeler can, plus: create, view, edit and delete connections; change the environment's settings and members; delete the environment |
| Modeler | Everything a Viewer can, plus: create packages, publish and manage versions, change package settings, share and delete packages, and use the environment's connections to model without seeing their credentials |
| Viewer | Query every package in the environment, from any surface |
The organization Modeler role does not make someone a Modeler on an environment; grant the environment role. A Member of the organization can be Modeler on one environment.
An environment can also be shared with a workspace, as Viewer or Modeler. Every member of that workspace, and the workspace's agent, then holds that role on the environment.
Package Access
Admin and Modeler on a package come from the environment. On the package itself you can grant:
- Viewer, to a user or group: query the package.
- Anyone at your organization, as the package's general access: every member of the organization can query it.
Environment Admins and Modelers (including organization admins) share a package from its Share dialog, or with cred add permission ... viewer --environment <env> --package <name>. Anyone else who opens the dialog sees only their own access.
Workspace Roles
A shared workspace gives a team packages, chats and reports in one place. Anyone in the organization can create one. See Workspaces.
| Role | Can |
|---|---|
| Manager | Everything a Member can, plus: change the workspace's settings and members, add and remove packages, and delete the workspace |
| Member | Chat with the workspace's packages, and create, edit and delete any chat or report in the workspace |
Adding a package to a workspace widens who can query it, so it takes both workspace Manager and the right to share the package (environment Admin or Modeler).
Chats and reports have no permissions of their own: everyone in a shared workspace can see and change every chat and report in it. To keep work to yourself, use your personal workspace, which only you can change and which shows every package you have access to. Organization admins can read, but not change, personal workspaces.
Who Can Do What
| Action | Who |
|---|---|
| Manage users, groups, API keys, Access Control values and organization settings | Organization Admin |
| Create an environment | Organization Admin |
| Change an environment's settings or members, delete it | Environment Admin |
| Create, view or change a connection's configuration | Environment Admin |
| Model with an environment's connections | Environment Admin or Modeler |
| Create a package, publish or archive versions, change package settings, delete a package | Environment Admin or Modeler |
| Share a package | Environment Admin or Modeler |
| Query a package | Environment Admin, Modeler or Viewer; package Viewer; members of a workspace the package is added to; everyone in the organization when general access is Anyone at your organization |
| Create a workspace | Anyone in the organization |
| Change a workspace's settings, members or packages, delete it | Workspace Manager |
| Chat, and create or change chats and reports, in a shared workspace | Workspace Manager or Member |
Organization admins can do everything in this table. A group API key can do whatever its group's roles allow.
Access Control
The Access Control page holds the values behind custom secure givens: the data values, such as tenant names, that a model's access rules compare against. Only organization admins can open it.
Each row grants a user (by email), a group or everyone a list of values for one attribute. A caller's values are the union of every row that applies to them. An attribute appears on the page after a published model declares a #(secure) given of type string[] with that name. Changes take effect on the next query, without republishing. You can also see and assign values from a member's row in Users & Groups and from a group's page.