Skip to main content

Manage permissions

BETA Preview

This feature is still being finalized by Development.

In briefA role is a set of grants, each pairing a permission 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. Roles are created and edited on Administration › Permissions, on the Roles tab, and their members are chosen in the same dialog. The same page's Event Identities tab holds the credentials that scripts and machines raise events with, its Workspaces tab the workspaces that keep teams' content apart, and its z/OS User IDs tab the z/OS user ID each person saves JCL as.

Notes
  • A request is allowed only when one of the person's roles grants that 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 one.
  • Connections, Agents and Agent Pools permissions — Agents Execute for the SAP lookups, Check SAP Job Numbers and reading z/OS JCL included — count only when granted under All workspaces.
  • Saving z/OS JCL needs z/OS JCL Edit and a z/OS user ID assigned on the z/OS User IDs tab.
  • An action on a running workflow or job is checked in the workspace of the workflow it was built from.
  • A role name is 3 to 23 letters, digits, underscores or hyphens; an older role with any other name can't be saved until it is renamed.
  • Permission simulation and the permission catalog are reached only by address.
  • A script or a machine's event files use an event identity, created on the Event Identities tab. Its events are applied to the raising machine's Default event environment and checked against the identity's roles there.
  • Workflows, scripts, properties, thresholds, resources and service requests belong to a workspace; frequencies, calendars and tags are shared. Every tenant starts with General.
Watch out
  • On Marketplace, a role decides only whether the screen is offered, not what can be done there.
  • Agents, Processes, the Event Log, Vision's live view and Environments now check roles. Someone who used them only because nothing was checked needs the grant now.
  • Removing a user from a role signs them out of every Continuous solution. Renaming a role signs nobody out.
  • SSO group names are not checked against your identity provider; a misspelled group grants nobody anything.
  • An event identity's secret is shown only once. Store it before you select Done.
  • A workspace can't be deleted while a role grants permissions in it or it still holds objects.