Manage permissions
This feature is still being finalized by Development.
- Synopsis
- Full Details
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.
- 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.
- 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.
The Permissions page, under Administration in the navigation, has four tabs: Roles, Event Identities, Workspaces and z/OS User IDs. This page follows them: the Roles tab and the four tabs after it cover roles, the Event Identities tab covers the credentials scripts and machines use, the Workspaces tab covers workspaces, and the z/OS User IDs tab the z/OS user ID each person's JCL saves run under.
Roles define what people can do, and where. Each permission a role holds is granted in a scope: tenant-wide, in particular workspaces, or in particular environment and workspace pairs. So one role can edit workflows in one workspace and only view them in another.
Roles decide which screens a person can open. In design and administration areas — workflows, scripts, the Toolkit, service requests and Self Service, Vision cards, notifications, roles, workspaces and custom fields — they also decide every action, and lists show only what the role's scopes reach.
Running workflows and jobs are checked too. On Processes, Workflow View needs Workflow Instances View and Job View needs Job Instances View in the environment, and each shows only the instances whose workflow is in a workspace where the role grants that permission. An instance the role cannot view answers as not found. Job Instances View on its own does not open the page. Each action needs its own permission in the workspace of the workflow the instance was built from. Every change of status needs Execute: Hold, Release, Skip, the marks, Cancel, Kill, Restart and Force Start on a job need Job Instances Execute, and Start, Hold, Release, Close and Cancel on a workflow instance Workflow Instances Execute. Building a workflow needs Workflow Instances Create and adding a job Job Instances Create; deleting needs the matching Delete, and editing settings or properties the matching Edit. See Running workflows and jobs are checked per workspace.
The Event Log needs Audit History View, Vision's live view Vision Cards View, and the Environments screen Environments View, with Environments Create, Environments Edit and Environments Delete to change environments. Saving, changing and deleting a saved search or a saved report needs the matching Saved Searches or Reports permission. See Environments and saved searches.
Agents are checked too. Every action on Agents needs the matching Agents, Agent Pools or Relays permission, and each of its tabs needs that row's View. Because an agent, a pool and a relay carry no workspace, the Agents and Agent Pools grants count only under All workspaces; Relays is on the Global tab. When the checks arrived, every role that held Workflows View was given Agents View and Agent Pools View, and every role's tenant-wide Agents permissions were copied to Relays. See Agents, agent pools and relays are checked. Agents Execute, which the SAP lookups in the job editor (Search… on the SAP fields), Start Check on Check SAP Job Numbers and reading a z/OS job's JCL need, counts only under All workspaces as well. See SAP lookup permission.
On Marketplace, a role still decides only whether the screen is offered. Anyone signed in to your tenant can use the actions there, so do not rely on roles to restrict them.
Connections are checked as well. Every action on a connection — listing, opening, Test Connection, create, edit and delete — now needs the matching Connections permission. Because a connection carries no workspace, that grant has to be under All workspaces on the role's Workspaces tab: a grant confined to particular workspaces holds the permission and still cannot use it. Grant Connections View to any role that builds jobs on legacy or database job types as well, or its connection pickers come up empty. See Connections are tenant-wide.
Permission checks used to let every signed-in request through, so review your roles: an account that worked only because nothing was being checked now needs the grant in the areas that are checked. See What roles control today.
Everyone either has too much access or waits on an administrator for everything. Without scoped roles there's no way to prove who can do what, and where, when an audit asks.
- Roles
- Permissions and Scopes
- Configure a Role
- Members
- Check a Role
- Event Identities
- Workspaces
- z/OS User IDs
Roles
Roles
A role has a name, a description, and its grants — each a permission paired with the scope it applies in. The built-in Administrator role has every permission everywhere and can't be changed. You can create roles, and edit or remove the roles you create.
"Every permission" includes permissions added after your tenant was created — the role is topped up automatically after an upgrade, and nothing it already holds is taken away. On an older tenant this did not always hold, and the newest permissions really could be missing from Administrator with no way to add them by hand. If you have a note somewhere to check that after an upgrade, you can drop it. See Administrator keeps up with the catalog.
Where you create and edit one
Roles live on the Permissions page, under Administration in the navigation. Its Roles
tab sits beside Event Identities, Workspaces and z/OS User IDs, and you need Roles View to open it. Old
links to /roles still work — they redirect to the same place on the Permissions page.
On the Roles tab, New Role opens an editor dialog over the list; hovering a row reveals a ⋮ menu with Edit and Delete; double-clicking a row opens it if you hold Roles Edit. Delete is unavailable on the built-in Administrator role because the platform refuses to delete one. Duplicate is no longer offered here.
The dialog keeps Role Name, Description and Choose Persona Presets at the top, and puts the rest on four tabs:
- Global — the role's tenant-wide permissions.
- Workspaces — the workspaces the role applies in, each with its own permissions.
- Environments — the environment and workspace pairs the role applies in, each with its own permissions.
- Members — who holds the role, and the event identities that carry it.
Choose Persona Presets offers only Custom in this build, so it changes nothing.
Save stays disabled until something has actually changed, and closing with unsaved changes asks first. A description and at least one permission are required. Because the dialog is addressed by the URL, a link to a role still opens it and Back closes it rather than leaving the page.
You can change only a role whose permissions you hold yourself. Creating, duplicating, editing or deleting a role, and changing its members, needs your own roles to grant every permission that role grants, each in the same scope or a wider one: a role with Workflows Edit in one workspace needs Workflows Edit among your roles in that workspace or under All workspaces. An edit is checked against the role as it is and, if you change its permissions, as it will be. Otherwise the change is refused with You can only create or change a role whose rights you hold yourself. Ask someone whose roles cover the role, or leave out the permissions you don't hold. See You can change only a role whose permissions you hold.
Naming a role
A role name must be 3 to 23 characters using only letters, digits, underscores and hyphens — no spaces. The name is what the role is called in the Continuous identity system too, which is what lets it hold members there, so the rule is stricter than for workspaces or environments.
An older role with a name like Workflow Designer keeps working exactly as it did — it grants
the same access to the same people. But its name field is in error the moment you open it, and the
role can't be saved again until you rename it. It is also left out of the sync below until then.
Rename those roles deliberately rather than hitting it mid-edit: Workflow Designer becomes
something like Workflow_Designer.
Keep roles in step with the identity system
Creating, renaming or deleting a role sends the tenant's whole set of roles to the Continuous identity system, so a role defined here is the role members are assigned to there. Editing only a role's permissions or description doesn't need to — the identity system holds neither.
Where the integration is configured, the Roles list shows when the last sync happened, or why it failed. There is nothing to press — the line reports, and the platform retries by itself.
A failed sync never blocks the change that triggered it: the role is created or renamed regardless, and the failure is recorded. The retry then runs when the thing that needs it is read — the list's status retries the tenant, and opening a role or reading its members retries that role — before the read returns, so what you are shown already reflects it. It only runs while something is unhealthy, not again within a minute of a failure, only when the person reading may edit roles, and only once your tenant has synced successfully at least once.
So if a role you created isn't showing up on the identity side, open it while signed in with Roles Edit. That is the retry.
Before your tenant's first sync, nothing syncs. The first sync is a one-time setup step run by an operator, and the status line says so: Roles have not synced to Continuous Auth yet. The first sync is a one-time setup step run by an operator. Until it has run, creating, renaming, deleting or duplicating a role saves as normal but does not sync, and the role's members can't be edited yet. The first sync sends every role changed in the meantime. While it runs, creating, renaming, deleting or duplicating a role, and changing its members, are refused — The first role sync is running for this tenant. Try again when it finishes. — and nothing is saved; try again once it has finished. Changing only a role's permissions or description still saves. Earlier builds refused those too. A rename made before the first sync moves no members, so if the Continuous console already holds a hand-made role under the old name, move its members there by hand. See Before the first sync.
A tenant with more than 100 roles is not synced at all, and the list reports more than 100 roles — delete roles you no longer need.
A role whose name doesn't conform is left out of every sync, so no retry helps — rename it. And when the recorded reason asks you to do something in the Continuous console, do that first: that case isn't retried automatically, and the next role create, rename or delete clears the reason, which would hide the thing you still have to fix.
A rename changes the role's name and nothing else: its members keep the role and its permissions, and nobody is signed out. Before Save, the editor says Members keep this role and its permissions. They see the new role name within 30 minutes, or right away if they sign out and sign back in. Earlier builds moved every member to the new name, which on a native tenant signed each of them out.
For an hour after the rename, a member whose sign-in still carries the old name keeps the renamed role's permissions, and no other role can be created or renamed to the old name — the refusal says when you can try again. A role an earlier build left with Check this role's members in Continuous Auth keeps that notice until you have checked and selected Mark as resolved. See Renaming a role keeps its members.
The delete confirmation tells you that access granted by the role is withdrawn at each member's next sign-in, before asking you to confirm. Deleting is owned by the Roles list wherever you start it — the editor's Delete hands the role back to it — so there is one confirmation to read, not two. After a delete the sync status is re-read, so a withdrawal the identity system refused shows up on the list straight away instead of at your next visit.
The Permissions page's Event Identities tab is for the machine identities that raise events into the platform, rather than for people. See Give a script or machine its own event identity (on the Event Identities tab).
A role's Members tab lists every event identity with a switch, on for the ones that hold that role, and each links to the identity. Switch identities on or off and Save to give them the role or take it away; an identity whose only role this is cannot be switched off, and adding one to a role that grants every permission asks you to type the role's name. The switches need Roles Edit and a role that has synced, so assign identities to a new role after it is created. See Event Identities. If the role has unsaved changes, opening an identity from that list asks first, as closing the editor does.
Permissions and Scopes
Permissions
A permission is an action on an object type: View, Create, Edit, Delete, or Execute. The role editor shows each object type as a row and each action as a choice on it, and a permission is named the same way, row then action: Workflows Edit, Job Instances Delete. Object types fall into scope models:
- Workspace: things that live in a workspace (Workflows, Scripts, Properties, Thresholds, Resources, Service Request, Agents, Agent Pools, Connections, Vision Cards).
- Global: tenant-wide settings (Workspaces, Frequencies, Calendars, Reports, Custom Fields, Tags, Script Catalog for the script runner and script type catalog, Roles, Audit History, Environments, Saved Searches, z/OS JCL, Relays, and more).
- Workspace + environment: runtime things (Workflow Instances, Job Instances, Workflow Deployments, Service Request Deployments, Self Service Portal).
Each scope model has its own tab in the role editor — Global, Workspaces and Environments — so a permission is always granted on the tab that matches its object type.
Granting Create, Edit, Delete, or Execute automatically includes View for that object, in the same scope, where the object type has a View — you can't manage what you can't see. In the editor, each object type is a row of No Access, View, Create, Edit, Delete and Execute; an action the object type doesn't have is disabled, and choosing any action also selects View where there is one.
Two object types have no View of their own, so nothing is implied for them. Dashboards has only Dashboards Execute. Script Catalog covers maintaining the tenant's own script runners and script types; those are read under Scripts View, so a role that maintains them needs Scripts View granted as well — its Create, Edit and Delete imply nothing.
Environments and Saved Searches are global too. When they arrived, every custom role was given all four Saved Searches permissions, and every custom role holding Settings Edit all four Environments permissions, so no one lost what they could already do. Add them yourself to a role created since. Saved Searches View decides nothing yet, because reading saved searches is not checked.
Scopes
A permission on the Global tab applies tenant-wide. On the other two tabs you add the scopes the role applies in, and each scope you add gets its own permission rows:
| Tab | What you add | It applies |
|---|---|---|
| Workspaces | A workspace, or All workspaces | In that workspace, in every environment |
| Environments | An environment and a workspace, either of which can be All | In just that combination; All environments + All workspaces is everywhere |
A request is allowed when one of the person's roles grants that permission in a scope that covers the object. See Where a grant applies.
Existing roles were converted to per-scope grants without changing anyone's access — except a role that was saved with permissions and no scope. It keeps its tenant-wide permissions; its workspace and environment permissions now apply nowhere. Open it and add the scopes it should have.
Configure a Role
Configure a role
To set up a role, complete the following steps:
- Go to Administration › Permissions, open the Roles tab, and select New Role.
- Enter a Role Name — 3 to 23 characters of letters, digits, underscores or hyphens — and a Description.
- On Global, choose the role's tenant-wide permissions.
- On Workspaces, add each workspace the role applies in (or All workspaces), select it, and choose its permissions. New Workspace creates one without leaving the dialog.
- On Environments, choose an Environment and a Workspace, select Apply Environment + Workspace Selection, then choose the pair's permissions.
- Optionally, switch to Members and choose who holds the role — see Add and remove a role's members (on the Members tab).
- Save.
Members
Add and remove a role's members
You do this in the role editor's Members section, while creating the role or later. When you create a role, one save creates it and assigns its members. Assigning members needs Roles Edit as well as Roles Create: without it the role is still created, and the Roles list says its members were not assigned. If the role's sync isn't ready at that moment, the dialog stays open and continues in Edit on the role it just created, with your selection still pending and the reason on screen — save again to apply it. Nothing is created twice.
What you name here depends on how your tenant signs people in. On a native tenant you name users. On an SSO tenant you map your identity provider's group names — which you can now do here, rather than only in the identity system.
To change who holds a role on a native tenant, complete the following steps:
- Open the role from the Roles tab — Edit on its ⋮ menu, or double-click the row (which needs Roles Edit).
- Switch to Members. Under Choose Users, each user has a switch, on for the people who hold the role. The list shows the first 50 users; type into Filter to find anyone else.
- To add someone, switch them on.
- To remove someone, switch them off.
- Select Save. Nothing is applied until you do.
On an SSO tenant, the same section holds Groups instead:
- Open the role from the Roles tab.
- Switch to Members and review the mapped group names under Choose Groups.
- To map a group, type its name and press Enter, or use the Add group "…" action in the popup. There is nothing to search — Continuum cannot see your identity provider.
- To unmap a group, remove its chip.
- Select Save. The people in a mapped group receive the role at their next sign-in.
Group names are not checked against your identity provider, so a misspelling is accepted, saved, and grants nobody anything — with nothing to tell you. Names are matched without regard to case, so a case variant of a group already mapped is refused as Already mapped rather than mapped twice.
You can change the Administrator role's members. It's that role's permissions and scopes that are fixed, not who holds it. Because changing a role's members needs every permission the role grants, only someone whose roles grant every permission everywhere can change who holds Administrator.
Removing a user from a role signs them out of Continuous and of every Continuous solution, not just OpCon Continuum. They can sign back in immediately, with whatever their remaining roles give them. The editor tells you how many users a save will sign out before you commit it.
Unmapping a group signs nobody out — its members lose the role at their next sign-in instead.
If your own membership is among the removals, Save asks before writing anything: you will be signed out and may lose the page you are on. OK carries on with the save as it stood, once, even if you select it twice. Cancel abandons the entire save — permissions included — and leaves every edit where it was.
The platform doesn't stop you: handing your role to someone else is legitimate. It just won't let you do it by accident.
The section always shows, with one of these reasons: the tenant has no identity integration configured, in which case a line of text says so and there is no field at all; the role's name doesn't conform (on the Roles tab), and a warning states the rule so you can rename it without looking it up; the role hasn't synced yet, under a warning titled This role has not reached Continuous Auth yet — there is nothing to press: before your tenant's first sync it says the role syncs as part of that one-time setup step, and after it an attempt runs each time a role editor opens the role, and the warning quotes the recorded reason when the last sync failed; or the members couldn't be read from the identity system, shown as an error — close and reopen the role to retry.
The editor sends only what you changed. If another person saved the same role after you opened it, Save is refused with This role changed since you opened it. Select Reload to see the current role and members, which discards your unsaved changes, then make your change again.
A role is saved in two writes: its name, description and permissions together, then its members. If some member changes fail, the dialog stays open, names each failure with its reason, and leaves those changes pending so Save retries exactly them. One reason to recognise: role not active — the next role sync re-declares it means the identity system has withdrawn the role. Any role create, rename or delete runs that sync; then save again.
Additions are applied before removals, so a "swap this person for that one" edit never empties the role in between. One save carries at most 100 member changes, additions and removals counted together; a bigger change is refused with Too many membership changes in one request, so split it.
If the tenant's sign-in mode changed while you had the editor open, the save is refused and asks you to reload, rather than applying what you typed as the wrong kind of member.
Check a Role
Check what a role grants
Use permission simulation: choose a Role (and optionally a Workspace and Environment) to see each permission as Granted or Denied, with the reason for a denial — for example Role does not grant this permission, or Select a workspace to evaluate. It's the quickest way to confirm a role does what you intend. The permission catalog lists every available permission, grouped by object type.
Neither has a link on the Permissions page — open them by address, at /permissions/simulation
and /permissions/catalog.
An event whose type is not real, or that names an object Continuum cannot pin to one workspace, is refused for everyone. See What an event is refused for.
Event Identities
Give a script or machine its own event identity
An event identity is the credential something other than a person uses to raise events: for example, the event files a job writes on a legacy LSAM machine. Every event line ends with a login ID and a token, which are the identity's name and one of its secrets. The identity can do only what its roles grant, in the same way as a person, so give each one a role made for the events it raises rather than Administrator.
You need Roles Create to create an identity, Roles Edit to change one or manage its secrets, and Roles Delete to delete one. You can give an identity only roles whose permissions you hold yourself. Only a role that has synced to the identity system can be attached, so create the role first and let it sync.
To create an event identity, complete the following steps:
- Go to Administration › Permissions, open the Event Identities tab, and select New Event Identity.
- Enter the Event Identity Name: up to 100 characters, with no comma. For existing event files, use the login ID they already carry. The name cannot be changed after saving.
- Enter a Description that says what the identity is for and where its secret is installed.
- On Expiration Details, turn on Does Expire and pick the last day the identity is valid. To have it never expire, leave the switch off and tick I accept that this identity never expires.
- On Roles, turn on the roles it needs. At least one is required.
- Select Save.
- Copy the Secret into your secret store, or select Download to save it as
event-identity-<name>.json. - Tick I have stored this secret and select Done. The secret is not shown again.
The identity appears in the list on the Event Identities tab. Put its name and secret at the end of each event line, in place of the login ID and token. See Events raised by a legacy agent.
Which environment the events reach. An event identity has no environment of its own. Each event is applied to the Default event environment of the machine that raised it, and checked against the identity's roles there. So one identity can be used on machines in several environments, provided its roles grant what the events need in each of them, for example Job Instances on the role's Environments tab. If you would rather keep environments fully separate, create one identity per environment. See How an event identity raises events, and in which environment.
To replace a secret without stopping the emitter, open the identity, go to Secrets, and select Issue Secret. Install the new secret, then select Revoke on the old one. An identity can hold two active secrets at a time, and a revoked secret stops working within 60 seconds.
To let a script call the Continuum APIs, turn on Allow API access on the identity's Details tab. The script then exchanges the secret for a short-lived API token, 20 minutes by default, and the identity's roles decide what each call may do. Use a separate identity for this rather than one whose secret is installed on machines to raise events. See Allow API access.
To stop an identity, turn off Enabled in OpCon on its Details tab, which you can undo, or delete it, which you cannot. Either takes effect within 60 seconds.
Event identity management is not switched on in this environment, so these identities cannot be managed yet means the feature is not available on the deployment you are signed in to. Contact support. For the other messages the tab can show, see When an identity cannot be managed or used.
Workspaces
Create a workspace
To create a workspace, complete the following steps:
- Go to Administration › Permissions and open the Workspaces tab.
- Select New Workspace.
- Enter a Workspace Name (it must be unique, and can't be "General") and a Description.
- Save.
The list shows, for each workspace, how many roles grant permissions in it (Roles Using) and how many objects it holds (Objects). Open a workspace — Edit on its ⋮ menu, or double-click the row — to rename it, change its description, or see the objects in it.
What lives in a workspace
Workflows, scripts, properties, thresholds, resources, and service requests are scoped to a workspace. (Frequencies, calendars, and tags are shared across all workspaces.)
- The General workspace is built in and can't be deleted.
- A workspace can't be deleted while a role still grants permissions in it, or while it still contains objects. The refusal says which, and how many. Check Roles Using and Objects on the list first.
- Who can work in a workspace is governed by the roles that grant permissions in it, not by adding members to the workspace. See the Roles tab.
z/OS User IDs
Let people save z/OS JCL
A save from a z/OS job's JCL dialog runs as the saver's own z/OS (RACF) user ID, which you assign here. Someone with no ID cannot save.
- Go to Administration › Permissions and open the z/OS User IDs tab. It needs Roles Edit.
- Select Assign z/OS user ID, find the person by name or email under Find a person, and pick them.
- Enter their z/OS user ID — 1 to 8 letters, digits,
@,#or$, not starting with a digit — and select Assign. - Make sure the person's role holds z/OS JCL Edit, on the role editor's Global tab.
Verify: the person appears in the table with the ID, and their JCL dialog says Saving as that ID.
Use Change on a row to give someone a different ID, and Remove to take it away; their next save is then refused. A person who signs in with single sign-on can be found only after their first sign-in. See z/OS User IDs and z/OS JCL Edit.
Related topics
- Roles and permissions — full configuration reference and troubleshooting
- Workspaces — full configuration reference and troubleshooting
- Manage environments (Administrator)