Skip to main content

Roles and permissions

BETA Preview

This feature is still being finalized by Development.

In briefA role is a set of grants, each pairing a permission (an action on an object type, such as Workflows Edit) with the scope it applies in: tenant-wide, a workspace, or an environment and workspace pair. Roles decide which screens a person can open, and in the areas that check them, every action and what each list shows. The built-in Administrator role holds every permission everywhere and cannot be modified.

WhereAdministration › Permissions, on the Roles tab (Roles View). The Event Identities tab needs Roles View too, the Workspaces tab needs Workspaces View, and the z/OS User IDs tab needs Roles Edit. Permission simulation and the permission catalog are reached only by address: /permissions/simulation and /permissions/catalog.

When

  • Giving people access to the screens and actions they need, workspace by workspace.
  • Explaining why someone is refused: use permission simulation.
  • Looking up what a permission is called and how it is scoped: use the permission catalog.

To give a script or a machine's event files their own credential, create an event identity on the Event Identities tab. Give it roles there, or switch it onto a role from that role's Members tab. See Event Identities.

How

  1. Open Permissions and select New Role, or double-click a role to edit it.
  2. Enter a Role Name (3 to 23 letters, digits, underscores or hyphens) and a Description.
  3. Choose permissions on the Global, Workspaces and Environments tabs, and members on Members.
  4. Select Save. For the full steps, see Manage permissions.
Notes
  • A request is allowed only when one of the person's roles grants that exact permission in a scope that covers the object.
  • You can create, duplicate, edit or delete a role, or change its members, only when your own roles grant every permission it grants, in the same scope or a wider one.
  • Granting Create, Edit, Delete or Execute also grants View in the same scope, where the object type has a view permission.
  • Connections, Agents and Agent Pools permissions count only when granted under All workspaces. That includes Agents Execute (the SAP lookups, Check SAP Job Numbers and reading z/OS JCL). Relays is a global row.
  • Saving z/OS JCL needs z/OS JCL Edit and a z/OS user ID assigned on the z/OS User IDs tab.
  • Running workflows and jobs are checked in the workspace of the workflow they were built from. Lists and counts show only the instances in workspaces where the role grants the view permission, and an instance you cannot view answers as not found.
  • Every action on the Agents page needs its Agents, Agent Pools or Relays permission, and each of its tabs needs that row's View. Marketplace is offered by role but not otherwise restricted by it.
  • An item you cannot view answers as not found, exactly as one that does not exist.
  • Renaming a role keeps its members and their permissions, and signs nobody out. The old name keeps granting the renamed role for an hour, and no other role can take it in that time.
Watch out
  • Removing a user from a role on a native tenant signs them out of Continuous and every Continuous solution.
  • On an SSO tenant, group names are not checked: a misspelled group is saved and grants nobody anything.
  • A role named before the naming rule existed must be renamed before it can be saved again, and until then it cannot hold members.
  • An event identity's secret is shown only once, when it is issued. Store it before you tick I have stored this secret.