Roles and permissions
This feature is still being finalized by Development.
- Synopsis
- Full Details
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
- Open Permissions and select New Role, or double-click a role to edit it.
- Enter a Role Name (3 to 23 letters, digits, underscores or hyphens) and a Description.
- Choose permissions on the Global, Workspaces and Environments tabs, and members on Members.
- Select Save. For the full steps, see Manage permissions.
- 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.
- 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.
Roles decide which screens a person can open. A screen that needs a View permission none of their roles grants is unavailable in the navigation, and opening it by link shows an access-denied panel instead. The home dashboard, Vision and Vision Config need no permission to open. Environments, which is reached by direct link, needs Environments View.
In these areas, roles also decide every action, and lists show only what the role's scopes reach: workflows and their deployments, scripts and the script catalog, the Toolkit (properties, thresholds, resources, calendars, frequencies and tags), service requests, their categories and their deployments, the Self Service portal, Vision cards and Vision's live view, notifications, roles, workspaces, custom fields, and running workflows and jobs on Processes. An action the role does not grant is refused, even when it is requested without going through the screen. Someone who holds no role can do nothing in these areas.
On Processes, workflow instances need Workflow Instances View and job instances Job Instances View, and each list shows only the instances whose workflow is in a workspace where the role grants it. Job Instances View on its own does not open Processes. See Running workflows and jobs are checked per workspace (on the Permission Catalog tab).
In these areas, roles decide every action too, but lists are not narrowed by a role's scopes:
- The Event Log. Reading the event history needs Audit History View, which is tenant-wide.
- Environments. Creating, changing and deleting an environment needs Environments Create, Environments Edit or Environments Delete. The environment selector still lists every active environment for everyone.
- Saved searches and saved reports. Creating, changing and deleting one needs Saved Searches Create, Saved Searches Edit or Saved Searches Delete, or Reports Create, Reports Edit or Reports Delete. The saved lists themselves are shared, and reading them is not checked by role.
Events are checked against the person who sends or saves them. See What an event is refused for (on the Where Grants Apply tab).
On Agents (agents, agent pools and relays), roles decide every action, and the grant has to be tenant-wide. Each action needs the matching Agents, Agent Pools or Relays permission under All workspaces, and the lists are not narrowed by a role's scopes. See Agents, agent pools and relays are checked (on the Permission Catalog tab).
On Marketplace, a role decides whether the screen is offered, but not what can be done there. Anyone signed in to your tenant can use its actions.
Connections, Agents, Processes, the Event Log, Environments, saved searches and saved reports used to be offered by role only, like Marketplace, and are now checked. See also Connections are checked, and the grant must be tenant-wide and The SAP lookups and JCL access are checked (on the Permission Catalog tab).
Permission checks used to let every signed-in request through. Review your roles: an account that worked only because nothing was being checked now needs the grant in the areas that are checked.
Task walkthrough: Manage permissions. This page is the full configuration and troubleshooting reference.
- About Roles
- Identity Sync
- Renaming Roles
- About Event Identities
- Managing Identities
- Members
- Permission Catalog
- Where Grants Apply
About Roles
Roles
| Field or tab | Notes |
|---|---|
| Role Name | Unique per tenant, and constrained — see What a role can be named. |
| Description | Optional through the API. The role editor requires one. |
| Type | System or Custom, as the Roles tab shows it. System roles (e.g. Administrator) are immutable. |
| Global tab | The tenant-wide permissions the role grants. |
| Workspaces tab | One entry per workspace, or for All workspaces, each with the permissions the role grants there. |
| Environments tab | One entry per environment and workspace pair, either of which may be "all", each with the permissions the role grants there. |
A role carries grants, and each grant pairs a permission with the scope it applies in. A role can therefore hold Workflows Edit in one workspace and only Workflows View in another. See Where a grant applies (on the Where Grants Apply tab). The grants on the three tabs are always saved and replaced together, and a role must grant at least one permission.
Two people editing the same role. The role editor remembers the role as it was when you opened it. Save sends only the name, description and permissions you changed, so saving a permission change never writes back a name or description you did not touch, and a save that changes only members writes nothing to the role itself. If someone else saved the role after you opened it, the save is refused with This role changed since you opened it. and a Reload button. Reload shows the current role and its members and discards your unsaved changes; make your change again and save. Member changes are applied only after the role itself saves, so a refused save applies none of them either.
The Administrator role is seeded per tenant with all permissions, each granted everywhere; it can't be modified.
The Permissions page
Roles are managed on the Permissions page, under Administration in the navigation. It has four tabs:
| Tab | What it holds | Needs |
|---|---|---|
| Roles | Every role, and the role editor | Roles View |
| Event Identities | The machine identities that raise events — see Event Identities (on the About Event Identities tab) | Roles View |
| Workspaces | Every workspace, and the workspace editor — see Workspaces | Workspaces View |
| z/OS User IDs | The z/OS user ID each person's JCL saves run under — see z/OS User IDs | Roles Edit |
The page is offered to anyone whose roles grant Roles View or Workspaces View. A tab you cannot
view is shown disabled, with You do not have permission for <tab>. on hover, and opening it by
link lands you on the first tab you can view. To Platform, at the right of the tabs, opens the
Continuous platform's users and roles screen in a new browser tab.
Old links still work. An address under /roles or /workspaces — a bookmark, a link in an
email — is redirected to the same place on the Permissions page, at /permissions/roles and
/permissions/workspaces.
z/OS User IDs
The z/OS User IDs tab, at /permissions/zos-user-ids, decides which z/OS (RACF) user ID each
person's JCL saves run under: a save from the
JCL dialog is made as the saver's own ID, and someone with no
ID cannot save. The tab needs Roles Edit, the same permission that searches the directory for
role members; without it the tab is disabled.
The table lists each person with an ID — Name, Email, z/OS user ID and Last changed — and shows No z/OS user IDs assigned yet. Use Assign z/OS user ID to add one. until there is one.
- Assign z/OS user ID opens a dialog: Find a person by name or email, pick the Person, and enter the z/OS user ID — 1 to 8 characters: letters, digits, @, # or $, not starting with a digit. Letters are upper-cased as you type. Any other ID is refused with Not a valid z/OS user ID. Use 1 to 8 characters: letters, digits, @, # or $, not starting with a digit.
- Change, on a row or by selecting it, gives the person a different ID. A person has one ID at a time, so assigning an ID to someone who already has one replaces it. Two people may share an ID.
- Remove, on a row, asks first: Remove z/OS user ID … from …? Their next JCL save is refused until someone assigns them an ID.
People who sign in with single sign-on can be found only after their first sign-in, as the tab says. JCL access and these IDs are for people: a service account can neither read nor save JCL, nor manage IDs. Saving also needs z/OS JCL Edit (on the Permission Catalog tab).
Where a role is edited
The Roles tab is a table of every role, with Name, Description, Type (System or Custom), Objects (how many object types the role grants anything on) and Updated. Creating or editing a role happens in a dialog over the list.
| On the Roles tab | What it does |
|---|---|
| New Role | Opens the editor dialog empty. Needs Roles Create. |
| The row menu (⋮, revealed on hover) | Edit and Delete. Delete is unavailable on a system role, because the platform refuses to delete one. |
| Double-clicking a row | Opens the editor for that role, if you hold Roles Edit. |
| The status line | The tenant's role-sync status, when the identity integration is configured. See Keeping roles in step with the identity system (on the Identity Sync tab). |
Duplicate is no longer on the Roles tab. The roles API still offers it.
The dialog is addressed by URL, not held in the page's memory: /permissions/roles/new and
/permissions/roles/<id> render the list with the dialog already open. A link to a role from
global search therefore still works, and Back closes the dialog rather than
leaving the page.
A save you leave with Back still reports a failure. If you press Back while a role, a
workspace or an event identity is saving, and the save then fails or is only partly applied, the
list you return to shows a warning naming what was not done — for example Workspace “<name>” was
not created — that you can dismiss. A later notice replaces an earlier one. A save that succeeds
shows nothing, and a notice is not shown once you have left the page.
Inside the dialog, Role Name, Description and Choose Persona Presets sit across the top, and the rest is on four tabs:
| Tab | Holds |
|---|---|
| Global | The role's tenant-wide permissions — see Where a grant applies (on the Where Grants Apply tab). |
| 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: the Users / Groups section, and the Event Identities (on the About Event Identities tab) section, where you switch identities onto and off the role. |
Choose Persona Presets offers only Custom in this build, so it changes nothing.
Each permission row is one object type, with six choices: No Access, View, Create, Edit, Delete and Execute. A permission is named by its row and its action: the Edit choice on the Workflows row is Workflows Edit, and that is how this documentation names permissions. An action the catalog does not offer for that object type is disabled. No Access clears the row, and choosing any other action also selects View, where the object type has one.
Things about the dialog worth knowing before you use it:
- Description is required in the editor, and so is at least one permission: saving a role that grants nothing shows Select at least one permission.
- Save is enabled only once something has changed, on a new role as well as an existing one, and closing with unsaved changes asks first.
- An edit that leaves the permissions alone sends none, so renaming or re-describing a role never rewrites its grants.
- New Workspace on the Workspaces and Environments tabs creates a workspace without leaving the editor, if you hold Workspaces Create.
- A role holding a permission the platform no longer offers opens with its permissions read-only, naming the permission. Saving its name, description or members, or deleting it, still needs your own roles to grant everything it grants, that permission included — see You can change only a role whose permissions you hold.
You can change only a role whose permissions you hold
Roles Create, Roles Edit and Roles Delete decide which role actions you can take. On top of them, every change to a role is checked against your own roles: you can create, duplicate, edit or delete a role, or change who holds it, only when your own roles grant every permission that role grants, each in the same scope or a wider one.
- Same permission, same or wider scope. A role granting Workflows Edit in one workspace needs Workflows Edit among your own roles in that workspace, or under All workspaces. A grant of a different permission does not count, however wide its scope. A permission on the Global tab only needs to be held.
- An edit is checked twice. The role must be covered as it is now and, when you change its permissions, as it will be after the save. This applies to a rename or a new description too.
- Duplicating a role and changing its members are checked against the role's current permissions. So is deleting it.
- The Administrator role grants every permission everywhere, so changing who holds it needs your own roles to grant every permission everywhere as well.
A change you are not covered for is refused with You can only create or change a role whose rights you hold yourself. In the role editor the message shows when you save; in the delete confirmation it shows when you confirm; and a members-only save that is refused shows it under Member changes were not applied. Ask someone whose roles grant at least the role's permissions to make the change, or leave out the permissions you do not hold.
Giving a role to an event identity follows the same rule — see Creating an event identity (on the About Event Identities tab).
Administrator keeps up with the catalog
"All permissions" now means all of them including the ones added after your tenant was created. The role is topped up automatically: any catalog permission it does not already hold is granted the first time the platform touches your tenant after an upgrade, so a new object type's permissions reach Administrator without anyone doing anything.
This is worth knowing because it did not always work that way. The role used to be seeded once, with the catalog as it stood on the day the tenant was created, and never revisited — and since the public API refuses to edit a system role, there was no way to add the missing permissions by hand either. On an older tenant that left Administrator genuinely short of the newest permissions, which showed up in simulation (on the Where Grants Apply tab) as Role does not grant this permission against a permission the catalog plainly lists. If you have seen that, it is fixed, and no longer a reason to contact support.
Two details worth being precise about:
- Grants are only ever added. Nothing Administrator already holds is taken away by the top-up.
- The top-up runs per tenant, once per platform start. If an upgrade has just been applied, simulation for Administrator is accurate from the first time anyone in your tenant uses the platform after it — not necessarily the instant the upgrade lands.
Permissions are the only thing reconciled this way. A role's scopes and description are still written once, when it is seeded; Administrator's wildcard scope already covers everything, so there is nothing for a later top-up to correct.
What a role can be named
A role name must be 3 to 23 characters of letters, digits, underscores and hyphens — no spaces and no other punctuation. Create, rename and duplicate all refuse anything else, with the same sentence in the form and from the API: Role name must be 3-23 characters using only letters, digits, underscores or hyphens.
The rule is narrow because the role's name is its name in the Continuous identity system, which is what lets a role hold members there. It is deliberately narrower than the rule for workspaces and environments, and it has no exemption for names already stored:
Such a role loads and grants exactly as before — nothing about who it applies to changes, and
nothing stops working. But the first time you edit it for any reason, the name field is in error and
the save is refused until the name conforms. Rename it deliberately rather than discovering it
mid-edit: a role called Workflow Designer becomes something like Workflow_Designer.
A non-conforming role is also left out of the sync (see the Identity Sync tab), so it cannot hold members in the identity system until it is renamed.
Identity Sync
Keeping roles in step with the identity system
Roles are mirrored into the Continuous identity system, so that a role defined here is the role members are assigned to there. The mirror is maintained for you: creating, renaming, deleting or duplicating a role sends the tenant's complete set of conforming roles. Editing only a role's permissions, scopes or description does not — there is nothing about those the identity system holds.
There is nothing to press. When the tenant's identity integration is configured, the Roles list shows a status line — Last synced 4m ago, or the reason the last attempt failed — and that line is reporting only. Before the tenant's first sync it reads Roles have not synced to Continuous Auth yet. The first sync is a one-time setup step run by an operator. — see Before the first sync.
A failed sync never fails the change that triggered it: the role is created, renamed or deleted regardless, and the failure is recorded. The platform then recovers by itself, when the thing that needs the sync is read:
| Reading | Retries the sync for |
|---|---|
| The Roles list's status | The whole tenant |
| Opening a role in the editor | That role |
| Reading a role's members | That role |
The retry runs before the read returns, so what you are shown is already the result of it — you do not have to reload, and there is no button to find. If the retry takes longer than about five seconds, the read returns what is recorded so far and the retry finishes in the background. These limits apply:
- It runs only for someone who may edit roles (Roles Edit). Someone who can only view roles sees the status as recorded, and triggers nothing.
- It runs only for a tenant that has synced successfully at least once. Before that, nothing retries — see Before the first sync.
- It only runs while the tenant or the role is actually unhealthy.
- After a failed attempt, it does not try again within a minute of the failure, however long the attempt itself took.
- While a rename started by an earlier build is still moving a role's members, it does not start another sync for that tenant.
- If a sync for the tenant is already running, the read waits for it — within the same five seconds — instead of starting another. So a link straight to a role, which reads the list and the role together, shows the role as the other read just left it rather than not synced.
- If another sync for the tenant is already under way somewhere the read cannot join, the retry is skipped and records nothing, and so is a retry when another sync has run for the tenant since the read decided to retry. A retry never replaces another sync's outcome with a failure. Earlier builds could show Role sync could not be completed; see the service log just after a sync had succeeded.
- It never breaks the read it runs ahead of. A sync that fails again just records why.
Before the first sync
A tenant's first sync to the identity system is a one-time setup step, run by an operator. Until it has completed, nothing else syncs the tenant's roles:
- Creating, renaming, deleting or duplicating a role does not sync. The change itself is saved as normal, and the role stays waiting to sync. The first sync sends it, along with every other role changed in the meantime.
- Reading does not retry, for the same reason.
- The Members section cannot be edited yet, because the role has no counterpart in the identity system to hold members. Its banner says Members cannot be managed until roles in this environment are first synced. Contact your administrator. — for a rename in progress, that the move finishes when an operator runs the first sync. A new role saved with members shows Role created — members are waiting on the sync, saying Members can be assigned after roles in this environment are first synced. Contact your administrator.; save the members again once it has synced.
- If an attempt at the first sync failed, the status line gives the reason, then Roles sync once an operator completes the first sync, a one-time setup step.
- If the one-time setup ran but a step of it failed, the Roles list says The one-time role setup did not finish and needs to run again. until a run with no failures clears it. If it finished but some members could not be restored to their roles, it says how many — The one-time role setup finished, but 2 of 40 members could not be restored. Add them back to their roles in the Continuous console. Running the setup again does not restore them, so add them back by hand; then someone with Roles Edit can select Mark as resolved under that line to clear it. The line is cleared only if it still reads as it did when you saw it, so a newer result is never cleared by mistake.
While the first sync is running, most role changes are refused. Creating, renaming, deleting or duplicating a role, and changing a role's members, are refused with a conflict — The first role sync is running for this tenant. Try again when it finishes. — and nothing is saved. Try again once the first sync has finished. Changing a role's permissions or description is not refused: it saves as normal while the first sync runs. Earlier builds refused those edits too, and let the first role change made before setup run the tenant's first sync itself.
The first sync waits for member saves already under way. If someone is saving a role's members when an operator starts the first sync, the first sync is refused — Role changes are in progress for this tenant. Try again in a moment. — until that save has finished.
A rename before the first sync is sent with the first sync. If the identity system already holds a role, made there by hand, under the role's old name, its members stay on that role: the first sync does not move them to the new name. Compare your role names with the roles in the Continuous console before the first sync, and move any such members there by hand.
The identity system accepts at most 100 roles in one sync, so a tenant with more than 100 conforming roles is not synced at all — no role is sent — and the status line reports Last sync failed: more than 100 roles. Delete roles you no longer need to bring the tenant back to 100 or fewer.
You can no longer create your way past the cap. Creating or duplicating a role is refused with a conflict once the tenant already holds 100 roles, so the tenant cannot be pushed into the not-syncing state by adding one more. Earlier builds accepted the create and the whole tenant then stopped syncing.
A non-conforming role name is excluded from every sync payload, so no retry can help it — rename it (on the About Roles tab) instead. And a notice left by a rename from an earlier build is not cleared by any retry: check the members in the Continuous console, then mark it resolved.
A tenant with no identity credential costs nothing here — no retry is attempted at all.
Every role change already ran a sync. The old Sync roles and Retry sync buttons only made an operator responsible for a retry the platform can do itself, so both are gone.
If you need to trigger one from a script, the API still offers it — for a tenant that has completed its first sync. For a tenant that never has, it is refused with a conflict, because the first sync is the one-time setup step.
Deleting a role removes it here immediately, but the withdrawal upstream — telling the identity system the role is gone, and with it every member's access through it — happens on the next sync. If that sync fails, the role still exists upstream with its members.
So a deleted role's name stays reserved until a successful sync has actually withdrawn it. While it is reserved:
- Creating, duplicating or renaming a role to that name is refused with a conflict, naming the reservation.
- If the role was renamed before it was deleted, its old name is reserved too — that is the name it may still be under upstream.
- The reservation clears by itself on the first successful sync that no longer carries the role. Nothing has to be done by hand.
Without this, recreating the name with different permissions would silently rebind every former member of the old role to the new one. If a name you expect to be free is refused, look at the tenant's sync status: a reservation that will not clear means the sync is still failing.
Deleting a role says what its members lose, and when. The delete confirmation carries the sentence "Access granted by this role is withdrawn at each member's next sign-in", placed after cannot be undone and before the question, so you are told the consequence before you are asked to accept it. A delete also re-reads the sync status afterwards, so a withdrawal that failed at the identity system — the one state where the two disagree about who has access — appears on the list rather than waiting for your next visit.
Deleting is owned by the Roles list, wherever you start it: the editor dialog's Delete hands the role back to the list, so there is exactly one confirmation to read rather than two that could drift apart.
Mirroring a role is what makes it able to hold members. Who holds it is then edited on the Members section of the role editor — see Members.
Renaming Roles
Renaming a role keeps its members
A rename is an ordinary role change. The role is renamed here, and the next sync sends the new name to Continuous Auth, which renames the role in place: its members keep it, nobody is re-assigned and nobody is signed out. Earlier builds moved every member to the new name one at a time, which could take minutes on a large role and, on a native tenant, signed each member out.
| About the rename | What happens |
|---|---|
| What a member notices | Nothing they need to act on. They keep the role and its permissions throughout. Their sign-in carries the role's old name until it refreshes, which takes at most 30 minutes; signing out and back in shows the new name at once. |
| Changing only the capitalization | The display name changes, and nothing else: role names are compared without regard to case. |
| How long it takes | Save returns as for any other change. There is nothing left running in the background. |
The role editor says so before you save. When the name changes by more than capitalization, the editor shows 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.
The old name keeps finding the renamed role for an hour. A member whose sign-in still carries the old name is granted the renamed role's permissions, so nobody loses access between the rename and their next refresh. For the same reason, no other role can take the old name for that hour: creating, duplicating or renaming a role to it is refused with The name '…' was used by a role that was renamed less than an hour ago. Signed-in users may still carry it. Try again in about … minutes., giving the minutes left. The hour starts once the rename has reached Continuous Auth; until then the message reads …the rename has not reached Continuous yet… and asks you to try again once the role sync has succeeded and an hour has passed. Renaming the role back to its own old name is allowed at any time. A rename of a role away from Administrator also holds back the built-in Administrator role from taking that name for the hour.
A rename started by an earlier build
A rename that an earlier build was still moving members for is finished, and until it is, the Roles list reads "A role rename is moving its members; a large role can take several minutes.", the old name stays reserved, and that role's members and name cannot be changed. A role that an earlier build left with a notice — headed Check this role's members in Continuous Auth in its Members section, and counted on the Roles list, such as 1 role needs its members checked: Operations. — keeps it until you have checked its members in the Continuous console and selected Mark as resolved. New renames leave no notice.
About Event Identities
Event Identities
An event identity is a machine credential: the identity a script or an agent's event file presents to Continuum in place of a person's sign-in. Use one wherever something other than a person raises events, such as the event files on a legacy LSAM machine. Each identity has a name and one or more secrets, and it holds no permissions of its own: what it may do comes entirely from the roles you give it, in the same way as for a person.
Event identities appear in two places, and the difference matters:
| Where | What you can do |
|---|---|
| The Event Identities tab of the Permissions page (on the About Roles tab) | Create, edit and delete identities, give them roles, and issue and revoke their secrets. The tab needs Roles View, because event identities have no permission of their own. |
| The Event Identities section of a role's Members tab | Give this role to identities, or take it away. It lists every identity, each with a switch that is on for the ones that hold the role and a link to the identity. |
Assigning identities from a role. The section reads Event identities will be assigned to this role & the selected permissions when it's saved. Switch an identity on or off, then Save: the identities are changed after the role and its users or groups are saved.
- The switches are unavailable without Roles Edit, while a save is running, and on a role that has not synced or whose name has to be renamed first (see What a role can be named (on the About Roles tab)). On New Role the section reads The role must be created before an Event Identity is assigned to it.: create the role, then assign them.
- An identity's only role cannot be switched off. Its switch stays on and reads This is its only role. Give it another role first.
- Adding an identity to a role that grants every permission is confirmed. Unless every identity you added is already High Privilege, Assign Full-Permission Role asks you to type the role's name, as the identity's own editor does, and records that you continued against your account in the audit log.
- An identity change that fails stays pending. The dialog stays open and lists each one that did not apply — The role was saved and the other changes applied. These did not: — with the reason. Save again to retry them. When the identity system cannot be reached, the changes not yet sent stay pending as well.
The list answers who holds this role whatever the role's sync status: it matches the tenant's identities on the role's name, so a role that has never synced simply has no holders rather than refusing to answer. It does need the tenant to have an identity credential, and it says so in its own words when there is none. When not every identity could be read, it says Not every identity could be read, so this list may be incomplete.
Opening an identity from that list asks first if the role has unsaved changes. Selecting one leaves the role editor, so with edits not yet saved you get the same Unsaved Changes confirmation as closing the dialog: Discard Changes leaves for the identity, and Keep Editing keeps you in the editor with your edits. With nothing unsaved it opens the identity straight away. Opening the identity in a new browser tab discards nothing, so it does not ask.
The Event Identities tab
The tab is a table of every event identity in your tenant:
| Column | Shows |
|---|---|
| Name | The identity's name. The filter in the column header searches names, descriptions and role names. |
| Description | What the identity is for. |
| Role | The roles it holds. |
| State | Every state that applies, most urgent first. See the next table. |
| Objects | How many object types its roles grant anything on, counted across all of its roles. |
| Expires | The last day the identity is valid, or Never. |
| State | Means |
|---|---|
| Platform-disabled | Continuous has disabled the identity. Only Continuous can clear this: turning the identity on in Continuum does not. |
| Expired | The expiration date has passed. The identity is refused whatever else is set. |
| Disabled | It is turned off in Continuum: Enabled in OpCon is off. It can be turned on again. |
| High Privilege | It holds a role that grants every permission: a role named Administrator, or a role that holds the whole current permission catalog. When the catalog gains a permission, custom roles that already held every permission are given it, so they keep this mark: Job Instances Create and Workflow Instances Create reached every such role when they arrived. |
| Orphaned | It has never been used, or not for 90 days. This is advisory: the editor's hint calls last use Approximate. |
| Expiring | It expires within 30 days. |
| Active | None of the above. |
| On the tab | What it does |
|---|---|
| New Event Identity | Opens the editor empty. Needs Roles Create. |
| The row menu (⋮) | Edit (needs Roles Edit) and Delete (needs Roles Delete). |
| Double-clicking a row | Opens the editor for that identity, if you hold Roles Edit. |
Like the role editor, the identity editor is addressed by URL: /permissions/event-identities/new
and /permissions/event-identities/<id>. The tab lists at most 1,000 identities; when it cannot show
them all it says The list is incomplete.
Creating an event identity
New Event Identity opens a dialog with two fields across the top:
| Field | Rules |
|---|---|
| Event Identity Name | Required. 1 to 100 characters, with no comma and no space at the start or end. A comma is refused because an event line is comma-separated, so it would break the credential pair. Name cannot be updated after saving. For a legacy machine's event files, use the login ID those files already carry. |
| Description | Required. Up to 500 characters. |
Below them are the editor's tabs. A new identity has three; an existing one has four:
| Tab | Holds |
|---|---|
| Expiration Details | The Does Expire switch and the Expiration Date, which is Valid through this date and must be in the future. With Does Expire off the identity never expires, and a new identity cannot be saved until you tick I accept that this identity never expires. |
| Roles | Choose Roles: a switch for each role the identity can be given, with a Filter. At least one role is required. |
| Secrets | Existing identities only. See Secrets. |
| Details | Allow API access, on new and existing identities. On an existing identity also Enabled in OpCon, and the read-only Identifier, Last used, Created and Created by. |
The Roles tab offers only roles that have synced to the identity system and whose names meet the naming rule (on the About Roles tab). A role that has not synced yet is not offered. Its sync retries when an editor opens it on the Roles tab, at most once a minute. A role the identity already holds but that is not offered still has a switch, so you can turn it off, and it says why it is not offered: Attached in Continuous Auth only, Name not accepted by Continuous Auth or Not synced to Continuous Auth.
Selecting Save creates the identity and its first secret together. A dialog titled
Event Identity Created, followed by the identity's name, shows the Secret once, with the
Identity (the identity's identifier) and a Download button that saves both as
event-identity-<name>.json. Copy the secret into your secret store or download the file, then
tick I have stored this secret: Done stays unavailable until you do. The secret cannot be shown again; if it is lost,
issue another.
Rules that apply whenever you create or change an identity:
- You can give an identity only roles whose permissions you hold yourself, in the same scopes. Otherwise Save is refused with You can't give this event identity the role(s) …: they grant permissions you don't hold. The same check runs when you turn a disabled identity back on, extend its expiry, issue it a secret or turn on Allow API access. Each is refused with You can't … this event identity: its role(s) … grant permissions you don't hold, naming what you tried.
- Adding a role that grants every permission needs a typed confirmation. While one is selected the editor warns This role grants every permission: the identity can act as a full administrator, and you must confirm it when you save. Save opens Attach Full-Permission Role: type the identity's name and select OK. The dialog states that continuing is recorded against your account. The check flags a role named Administrator and any role that holds the whole current permission catalog. A copy of Administrator that has fallen behind a newer permission is not flagged, so review the role itself.
- Only a signed-in person can change event identities. A script or another event identity is refused with Event identities can only be changed by a signed-in user, not by a service or event identity.
Secrets
An identity's secret is what the emitter presents. The Secrets tab lists every secret the identity has ever held, revoked ones included, with its Prefix, Expires and Last used. Only the prefix is ever shown: the full value is shown once, when the secret is issued.
| Action | What happens |
|---|---|
| Issue Secret | Opens Issue Additional Secret. Select Issue Secret and the new secret is shown once, in New Secret for and the identity's name, the same way as at creation. An identity can hold at most two active secrets. |
| Revoke | Asks for the identity's name in Revoke Secret, then revokes that secret. It cannot be undone, and the secret stops being accepted within 60 seconds, not instantly. Revoking the only active secret is allowed: the identity then cannot raise events until another secret is issued. |
To change a secret without interrupting the emitter, issue a second secret, put it in the emitter's configuration, and revoke the old one once the new one is in use. Both secrets work until you revoke the old one.
Managing Identities
Turning an identity off, and deleting it
- Enabled in OpCon on the Details tab takes effect at once, not on Save. Turning it off asks first, in Disable Event Identity. The identity stops raising events within 60 seconds, and you can turn it on again at any time.
- Delete, from the row menu or the editor, asks for the identity's name in Delete Event Identity. It removes the identity and every secret it holds, and it cannot be undone. Anything still presenting one of its secrets stops being accepted within 60 seconds.
Allow API access
Allow API access, on the Details tab, lets a script exchange the identity's secret for short-lived API tokens, and then call the Continuum APIs with them instead of a person signing in. Without it, the identity can only raise events. It applies when you save, and you can turn it on only if your own roles grant at least what the identity's roles grant.
Getting a token. The script sends the secret, and nothing else, in one request to your tenant's own address:
| Step | Details |
|---|---|
| Request | POST to /agent-api/v1/service-account-token on the address you open Continuum at, under the same path. The body is JSON with one string field: {"secret": "<the secret>"}. |
| Answer | 200 with access_token, token_type (Bearer) and expires_in, the number of seconds the token stays valid. If a token would have less than 60 seconds left, a fresh one is fetched before the answer is sent. |
| Using it | Send Authorization: Bearer <access_token> on each API call. What each call may do is decided by the identity's roles, in the same way as for a person. |
| Renewing it | Reuse the token until it is close to expiry, then send the secret again for a new one. There is no refresh token. |
The token lasts as long as the tenant's session lifespan, 20 minutes by default. Some APIs do not
accept API tokens whatever the identity's roles, and answer 403 with Service-account API tokens
cannot call this API. Use a signed-in person for those.
| Answer from the token request | Means | What to do |
|---|---|---|
400 invalid_request | The body was not JSON with a string secret. | Send Content-Type: application/json and {"secret": "…"}. |
401 invalid_credential | The secret was not accepted. Every cause gets this same answer: a wrong or revoked secret, Allow API access off, an identity that is disabled or expired, or an address Continuum does not recognise as a tenant. | Check each of those in turn. |
429 rate_limited | Too many token requests: about 10 a minute for one secret, and a limit for the whole tenant. | Wait for the seconds in the Retry-After header. Cache the token rather than requesting one per call. |
503 temporarily_unavailable | The token service is unavailable. | Wait for the seconds in the Retry-After header, then try again. |
401 whose error is not invalid_credential | The token request did not reach the token service. | Check the address and path, then contact support. |
With Allow API access on, every copy of the identity's secret works as an API credential. If its secret is already installed on machines to raise events, create a separate identity for the script instead, with only the roles the script needs.
Turning Allow API access off, revoking a secret, disabling the identity or deleting it stops new tokens within 60 seconds. Tokens already issued stay valid until they expire, which is up to the tenant's session lifespan (20 minutes by default) plus 60 seconds.
How an event identity raises events, and in which environment
On a legacy LSAM machine, every event line ends with a login ID and a token: the identity's name and one of its secrets. Continuum checks that the secret belongs to an identity with that name, then checks the identity's roles. The identity needs the permission the event requires, in the workspace of the object the event names and in the environment the event is applied to. The line format and the checks are in Events raised by a legacy agent.
An event identity has no environment of its own. The environment comes from the machine: every event a machine raises is applied to that machine's Default event environment, and an event line cannot name a different one. So:
- One identity can serve machines in several environments. Nothing ties an identity to a machine, so the same name and secret can be used on machines registered to different environments. Each event is checked in the environment of the machine that raised it.
- An event is applied in one environment only. To act in another environment, raise the event from a machine whose Default event environment is that environment.
- Environment-scoped permissions keep environments apart. For a permission granted on the role's
Environments tab, such as Job Instances Execute for a
$JOB:KILLline, the grant must cover the environment the event is applied in. A role that grants it only in a test environment does not let the identity's events do the same in production. A permission granted on the Global or Workspaces tab applies whatever the environment; see Where a grant applies (on the Where Grants Apply tab).
If you would rather keep environments fully separate, create one identity per environment and give each one roles scoped to its own environment.
When an identity cannot be managed or used
| What you see | Why | What to do |
|---|---|---|
| Event identity management is not switched on in this environment, so these identities cannot be managed yet. | Event identity management is not available on the deployment you are signed in to. | Contact support. |
| Continuous Auth is not configured for this tenant | Your tenant has no connection to the Continuous identity system, which holds event identities. | Contact Continuous to have it configured, as the message says. |
| No roles are synced to Continuous Auth yet on the Roles tab | No role has synced to the identity system yet. | Open the role on the Roles tab so its sync retries, then attach it once it has synced. |
| You can't give this event identity the role(s) … | The role grants permissions you do not hold. | Ask someone whose roles grant at least those permissions, or choose a narrower role. |
| That name is already in use in this tenant. Choose another. | Another identity has that name. | Choose another name. |
| This tenant has reached its limit of … event identities | The tenant holds as many identities as it may. | Delete one you no longer use. |
| An identity's events stop, and nothing appears in the event log | It is Disabled, Expired or Platform-disabled, its secret was revoked, or its roles no longer grant what the events need in that environment. | Check the identity's State and Secrets, then its roles. See Events raised by a legacy agent. |
Members
Members
A role's members are edited in the role editor. The Members tab is one of the editor's four tabs (on the About Roles tab): it lists the users who hold the role and lets you add and remove them without leaving Continuum.
You can pick members while creating a role. Choose them on New Role, and one action creates the role and assigns them. 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 is not ready at that moment, the dialog stays open and continues in Edit mode for the role it just created, with your selection still pending and an explanation of why it did not close. Nothing is lost and nothing is created twice — the next Save applies the selection. The same applies if only some of the additions went through: the ones that failed stay pending and Save retries just those.
What the section holds depends on how your tenant signs people in. A native tenant names users; an SSO tenant maps identity-provider groups. The two are different fields, not two skins of one, and the section says which it is in its heading and subtitle — Choose Users, Users will be assigned to this role & the selected permissions when it's saved, against Choose Groups, Identity-provider groups mapped to this role. Members receive it at their next sign-in.
| Role membership | Native tenant | SSO tenant |
|---|---|---|
| What it shows | A list of the tenant's users, each with a switch that is on for someone who holds this role | The identity-provider group names mapped to this role, as removable chips |
| Adding one | Switch the user on. The list shows the first 50 users of the directory; type into Filter to search it for anyone else. Current members always stay in the list | Type the group name and either press Enter or use the Add group "…" action. There is nothing to search — see below |
| Removing one | Switch the user off | Remove its chip |
| When it takes effect | On Save, with the rest of the role | On Save. Members of a mapped group receive the role at their next sign-in |
| Where the data lives | In the Continuous identity system. Every read is live, and Continuum stores no member list, email address or identity mapping of its own | The same — Continuum stores no group mapping of its own |
Membership on the Administrator role is editable. It is the role's definition that is frozen — its permissions and scopes — not who holds it. Changing any role's members needs your own roles to grant everything that role grants, so only someone holding every permission everywhere can change who holds Administrator — see You can change only a role whose permissions you hold (on the About Roles tab).
Removing a user signs them out of Continuous and of every Continuous solution, not only of Continuum. They can sign straight back in; what they lose is the session, and on signing back in they have whatever the remaining roles give them. The page warns you before you save, with a count of the users affected.
Removing a group mapping signs nobody out. Its members keep the session they are in and lose the role at their next sign-in, so the warning does not appear on an SSO tenant.
Removing yourself is confirmed before anything is written
Taking your own membership out of a role signs you out and may cost you the page you are on, so Save stops and asks first, naming the role: "You are removing yourself from … You will be signed out and may lose access to this page."
- OK resumes the save you interrupted, exactly as it was, once: selecting OK twice in quick succession saves the role a single time.
- Cancel abandons the whole save. Nothing is written, including the role's own permissions, and every edit stays as you left it — a save you deliberately backed out of should not be half applied.
The platform does not refuse this: handing your own role to someone else is a legitimate thing to do. The check is a confirmation, not a block. It compares against the signed-in user by identity and by email, and it applies on a native tenant only — a group mapping names nobody in particular.
On an SSO tenant, group names are not verified
Continuum cannot see your identity provider, so the group field has nothing to offer as suggestions — you type the name, and the popup holds only the add action and its hint. The field says so: Type names exactly as in your identity provider.
That is worth taking literally. A misspelled group name is accepted, saved, and grants nobody anything, with no error to tell you. Copy the name from the identity provider rather than typing it from memory.
Two rules the field applies as you type:
- Names are compared case-insensitively, because the identity system compares them that way. Typing a case variant of a group already mapped is refused with Already mapped rather than creating a second mapping that collides on save.
- A group name is at most 200 characters when you add one. Names may legitimately contain spaces and slashes. A removal is sent back exactly as it was read, so a mapping already in place can always be removed regardless of its length.
A single save carries at most 100 membership changes, additions and removals counted together, as on a native tenant. You cannot re-case an existing mapping in one save — remove it and add the new spelling in two.
On an SSO tenant, a role the identity system has withdrawn shows as Could not read members when you open it, because its group mappings cannot be read. As on a native tenant, the next role create, rename or delete re-declares it.
When the section is read-only, and why
The section always renders — it never quietly disappears — and states its own reason when it cannot be used. The reasons are evaluated cause first, because each one is the reason the next cannot be judged:
| What you see | What to do |
|---|---|
| Member management requires the Continuous Auth integration, which is not configured for this environment. | The tenant has no identity integration. Nothing about membership is editable until it is configured — and this state shows the sentence with no field at all |
| Rename this role to manage its members — This role name is not allowed, so the role cannot be saved. Rename it to 3–23 characters, using only letters, digits, underscores or hyphens. | The role's name doesn't conform (on the About Roles tab), so it has no counterpart in the identity system to hold members. The banner states the rule outright so you can act on it here. There is deliberately no retry: a non-conforming name is left out of every sync, so retrying could not fix it |
| This role has not reached Continuous Auth yet — The sync tries again when someone opens this role. Members can be managed once it has synced. | Nothing to press. Before the tenant's first sync (on the Identity Sync tab), the banner reads Members cannot be managed until roles in this environment are first synced. Contact your administrator. instead: nothing syncs until an operator runs that one-time setup step, and the role syncs as part of it. After it, an attempt runs each time a role editor opens the role, at most once a minute after a failure, so re-opening the role is the retry. When the last sync failed, the banner also quotes the recorded reason — and if that reason asks for an action in the Continuous console, do it there first, because that case is not retried automatically. See Keeping roles in step with the identity system (on the Identity Sync tab) |
| Could not read members — … could not be read from Continuous Auth: … Close and reopen the role to try again. | The identity system is configured but unreachable. The section reports the error and stays disabled rather than showing an empty role as the truth |
A background refresh that fails after your member list has loaded leaves your edits alone. That matters after a partial save, below: the changes you need to retry are still there.
A save can apply some member changes and not others
A role is saved in two writes: its name, description and permissions together, then its members. So a save can succeed for the role and then fail for some of its member changes. When that happens the dialog stays open rather than closing, and tells you which is which:
- Some member changes failed. Each one is named — Add Jordan Reyes (jordan@…) — with the reason. The changes that landed are kept, and the failed ones stay pending, so Save again retries exactly those.
- The whole member apply failed. The role itself is saved; your member changes are still pending. Save again to retry them.
One reason worth recognising: role not active — the next role sync re-declares it (any role create, rename or delete). The identity system has withdrawn the role, so additions cannot be applied to it. Removals still run. As the reason says, any role create, rename or delete runs the sync that re-declares it; then save again.
If the tenant's sign-in mode changed while the editor was open, the save is refused and tells you to reload. The editor pins the mode it loaded the chips against, so what you typed is never applied as the wrong kind of member — group names sent as user identities, or the reverse.
A "replace this person with that one" edit therefore never leaves the role empty in between. It also means a save that fails part-way is more likely to have added than removed.
One save carries at most 100 membership changes — additions and removals counted together. A larger change is refused with Too many membership changes in one request rather than partly applied; split it across saves.
Permission Catalog
Permission catalog
A permission is one action on one object type. The role editor shows each object type as a row and each action as a choice on that row, and this documentation names a permission the same way, row then action: Workflows Edit, Job Instances Delete, Audit History View.
- Actions: View, Create, Edit, Delete, Execute.
- Scope models — each decides which tab of the role editor the object type's row is on (see
Where a grant applies (on the Where Grants Apply tab)):
- Workspace (W), on the Workspaces tab — checked against the object's workspace (e.g. Workflows, Scripts, Properties, Thresholds, Resources, Service Request, Agents, Agent Pools, Connections, Vision Cards).
- Global (G), on the Global tab — tenant-wide (e.g. Workspaces, Frequencies, Calendars, Reports, Dashboards, Custom Fields, Tags, Service Request Categories, Script Catalog, Settings, Roles, Audit History, Environments, Saved Searches, z/OS JCL, Relays).
- Workspace × Environment (WE), on the Environments tab — both axes checked (e.g. Workflow Instances, Job Instances, Workflow Deployments, Service Request Deployments, Self Service Portal).
- Implied view: granting Create, Edit, Delete or Execute automatically includes that row's View in the same scope ("you can't manage what you can't see"). It does nothing for the three rows that have no View of their own: Script Catalog (see below), Dashboards, whose only permission is Dashboards Execute, and z/OS JCL, whose only permission is z/OS JCL Edit.
A few rows are named differently elsewhere in the product. The Connectors row governs what the
navigation calls Marketplace, and the Audit History row governs the Event Log. The
read-only permission catalog (on the Where Grants Apply tab) lists each permission's id as well,
such as workflows.edit.
The Service Request Categories row covers the categories a self service button is filed in, and the arrangement of the portal page — category order, band colour and button order. It is global, so a role's workspace scope does not apply to it. Only Administrator starts with Service Request Categories Create, Service Request Categories Edit and Service Request Categories Delete, because a category created from one workspace appears in every workspace's picker. Roles that already held Service Request View or Service Request Edit when the object type arrived were given Service Request Categories View as well. That was a one-time grant: add it yourself to a role created since.
Connections are checked, and the grant must be tenant-wide
A connection holds the credentials a job runs as — a batch user on an LSAM machine, a database login, an MFT compression password. Those routes are now gated on the Connections permission for the action being taken, before anything is read or written:
| What you are doing | Permission needed |
|---|---|
| Listing connections, opening one, or Test Connection | Connections View |
| Creating one | Connections Create |
| Editing one | Connections Edit |
| Deleting one | Connections Delete |
Earlier builds authorized these on tenant membership alone, so anyone signed in to your tenant could list, create, rewrite or delete a connection — including changing the account a job runs as.
The Connections row is on the Workspaces tab, as a workspace-scoped object type, but a connection carries no workspace — connections belong to the tenant. So the grant has to be tenant-wide: a role whose grant names particular workspaces holds the permission and still cannot use it, and the refusal says the role's scope does not match rather than that the permission is missing.
Grant Connections permissions under All workspaces on the role editor's Workspaces tab. Only a grant of that same Connections permission in all workspaces counts.
A Builder who picks a batch user needs Connections View too. The job editor's connection pickers read the same list, so a role without it shows an empty picker — which reads as "there are no connections" rather than as a permission problem. Grant Connections View to any role that builds jobs on legacy or database job types.
If the role service cannot be reached, the request is refused rather than allowed through. That is deliberate: a credential store is the wrong place to fail open.
The Script Catalog row covers writes to the tenant's own script runners and script types — Script Catalog Create, Script Catalog Edit and Script Catalog Delete, and no View. Reading the catalog stays on Scripts View, so anyone who can pick a runner on a job can already see it, and a write asks for Scripts View and the Script Catalog action. Because there is no Script Catalog View to imply, granting Create, Edit or Delete on that row adds no view permission of any kind: a role needs Scripts View granted as well. It is global, so a role's workspace scope does not narrow it — a runner belongs to the tenant rather than to a workspace. Administrator holds all three. No other role was granted them when the object type arrived, so add them to any role that should maintain the catalog.
The SAP lookups and JCL access are checked, and the grant must be tenant-wide
Agents Execute ("Run design-time queries against agents") is the permission for asking an SAP agent about its SAP system, and for reading a z/OS job's JCL. It is checked on:
| What you are doing | Where |
|---|---|
| Search… beside SAP Job Name, Exec. Target or Process Chain Name | The job editor — see Looking up the job and the server in SAP |
| Start Check | Check SAP Job Numbers — see Checking every stored SAP job number |
| View / edit JCL and Load | The JCL dialog of a z/OS job — see Viewing and editing JCL |
Without it, Search… and Start Check are unavailable and say why. Like Connections, the grant counts only when it is tenant-wide: an agent carries no workspace, so a role that grants Agents Execute in particular workspaces holds it and still cannot use it. Grant it under All workspaces on the role editor's Workspaces tab. Administrator holds it. Custom roles that already held Agents View when it arrived were given Agents Execute in the same scope — which is usable only where that Agents View grant was under All workspaces.
The rest of the Agents row decides what can be done on the Agents page — see Agents, agent pools and relays are checked.
z/OS JCL Edit
z/OS JCL Edit ("Save z/OS JCL members") is the permission for saving a z/OS job's JCL member back to the mainframe from the JCL dialog. The role editor shows it as the z/OS JCL row, on the Global tab, with Edit its only action: reading a member is Agents Execute, so the row has no View. Without it the dialog offers no Save. A save also needs a z/OS user ID assigned to the person — see z/OS User IDs (on the About Roles tab) — and Agents Execute alone never allows one.
Administrator holds it. When it arrived it was given to every custom role that held Agents Edit under All workspaces, and to every custom role that held every permission then in the catalog. A role whose Agents Edit was confined to particular workspaces was not given it, since a mainframe write cannot be confined to a workspace. That was a one-time grant: add it yourself to a role created since.
Agents, agent pools and relays are checked, and the grant must be tenant-wide
Every action on the Agents page is checked against the permission for the object it reads or changes, before anything is read or written. A legacy agent group counts as an agent pool, and an agent listed under a relay or a pool is still an agent:
| What you are doing | Permission needed |
|---|---|
| Seeing the Agents tab, or opening an agent | Agents View |
| New Agent, Universal or legacy | Agents Create. A legacy agent also needs Relays View, for its relay picker |
| Saving an agent, Update, the operator marks, Accept Host Name, assigning a default event environment to agents that have none | Agents Edit |
| Deleting an agent | Agents Delete. The check that the agent is not in use also reads its workflows with Agents View, and the unfinished jobs of every environment with Job Instances View, which must cover every workspace there — see An agent in use cannot be deleted |
| Seeing the Agent Pools tab, or opening a pool or group | Agent Pools View |
| New Agent Pool | Agent Pools Create, plus Agents Edit when you add Universal Agents to it as you create it, because that moves them out of their current pool |
| Saving a pool's or group's description, adding or removing a legacy group's members | Agent Pools Edit |
| Adding a Universal Agent to a pool, or removing one | Agent Pools Edit and Agents Edit |
| Deleting a pool or group | Agent Pools Delete |
| Seeing the Relays tab, or opening a relay | Relays View |
| New Relay | Relays Create |
| Renaming a relay, Rotate Credentials, Hand Over to a standby | Relays Edit — see Hand over to a standby |
| Deleting a relay | Relays Delete. Deleting one that still has jobs, which ends them, also needs Agents Delete — see Edit, rename and delete a relay |
The grant counts only when it is tenant-wide. An agent, a pool and a relay carry no workspace. The Agents and Agent Pools rows are on the role editor's Workspaces tab, but only a grant under All workspaces counts: a role that grants them in particular workspaces holds the permission and still cannot use it, and the refusal says the role's scope does not match. The Relays row, with View, Create, Edit and Delete, is on the Global tab.
The page follows the same permissions. Agents is in the navigation for a role with View on any of the three rows. Each tab is shown only to a role with its View under All workspaces, and a link to a hidden tab opens the first one you can see. With none of them, the page reads You do not have permission to view agents, agent pools or relays. Ask an administrator to grant access in all workspaces. An action you may not take is unavailable, and its tooltip says why — for example You do not have permission to delete relays. If your permissions could not be read, every tab is shown and each action is unavailable with Permissions could not be loaded. Refresh the page.
Other screens read agents and pools with your permissions too, such as the agent picker when you deploy, the agent and relay pickers of a notification group and the dashboard's agent widgets. A role without the matching View under All workspaces finds them empty or showing an error.
When these checks arrived, existing roles were given what they already used. Administrator holds every one of these permissions. Every other role that held Workflows View, in any scope, was given Agents View and Agent Pools View under All workspaces, so the pickers above keep working. Every role that held an Agents permission under All workspaces was given the same Relays permission, and a role that held every permission then in the catalog was given all four. Nothing else was added. That was a one-time grant: give a role created since the permissions it needs.
An event identity's API token (on the Managing Identities tab) can manage agents, pools and relays within its roles, as a person can. Earlier builds let anyone signed in to your tenant change or remove agents, pools and relays, and refused API tokens there.
Environments and saved searches
Two global object types arrived together, each with View, Create, Edit and Delete. Being global, their rows are on the role editor's Global tab, and a role's workspace and environment scopes do not narrow them.
| Row | What it decides |
|---|---|
| Environments | Environments View opens the Environments screen. Environments Create, Environments Edit and Environments Delete decide who creates, changes and deletes an environment, and the service addresses registered for it. Registering a service address through the API needs both Environments Create and Environments Edit, because it can also re-point an address that already exists. Reading environments is not checked, so the environment selector lists them for everyone. |
| Saved Searches | Saved Searches Create, Saved Searches Edit and Saved Searches Delete decide who saves a search, changes one, and deletes one. Reading saved searches is not checked, so Saved Searches View decides nothing yet. |
Existing roles were given these grants once, when the object types arrived, so nobody lost access they already had:
- Every custom role received all four Saved Searches permissions, because anyone signed in could save, change and delete a search before.
- Custom roles that held Settings Edit received all four Environments permissions. Other roles did not: an environment's service addresses decide where the platform sends its own credentials, so environment administration stays with roles that already administer the tenant.
- Administrator holds all eight, as it holds every permission.
That was a one-time grant. Add these permissions yourself to a role created since.
Saved reports are checked on the Reports permissions. Saving a report needs Reports Create, changing a saved one Reports Edit, and deleting one Reports Delete. Opening the shared list is not checked by role.
Running workflows and jobs are checked per workspace
Every request to read or act on workflow and job instances is checked against the person's roles, on the Processes page and through the API alike.
Reading is narrowed to the workspaces the role reaches. Each instance belongs to the workspace of the workflow it was built from:
- Lists show only the workflow and job instances in workspaces where the role grants the view permission, in the selected environment. The tags offered for filtering follow the same rule, and so does the list of workflows offered for scheduling, which shows only those where the role grants Workflow Instances Create.
- The run's counts are never refused. Workflow counts include only the workflows the role may view with Workflow Instances View, and job counts only the jobs it may view with Job Instances View. A role with neither sees zeros.
- Opening one instance, or its jobs, history, runs, notes or output, needs the view permission in that instance's workspace. Without it, the instance answers as not found, exactly as if it did not exist, so its existence is not revealed.
Acting on one instance needs the action's permission in the workspace of the workflow the instance was built from, in that environment. If the role does not grant the instance's view permission there either, the action answers as not found; if it grants view but not the action, the action is refused. The workflow is found by its identity rather than its name, so renaming a workflow does not change which workspace counts. Moving a workflow to another workspace moves its instances with it, within about a minute.
| What you are doing | Permission needed |
|---|---|
| Reading workflow instances, their dependencies and the run's counts | Workflow Instances View |
| Reading jobs, their history, their runs, notes and output | Job Instances View |
| Scheduling a workflow into the run (a build) | Workflow Instances Create |
| Add Job to a workflow instance | Job Instances Create |
| Start, Hold, Release, Close or Cancel on a workflow instance | Workflow Instances Execute |
| Changing a workflow instance's properties | Workflow Instances Edit |
| Delete on a workflow instance | Workflow Instances Delete |
| Hold, Release, Skip, Mark Fixed, Under Review, Mark Finished OK, Mark Failed, Cancel, Kill, Restart or Force Start on a job | Job Instances Execute |
| Editing a job or its properties, and adding, changing or deleting a note | Job Instances Edit |
| Delete on a job | Job Instances Delete |
These are the same permissions the matching events need, so an action gets the same answer whether it is taken on the page or sent as an event.
Every change of status needs an Execute permission. Building a workflow and adding a job each have a Create permission of their own, and Edit is left for changing settings and properties. Earlier builds split these differently: adding a job needed Workflow Instances Edit, a build Workflow Instances Execute, holding or marking a job Job Instances Edit, and cancelling or killing one Job Instances Delete. Custom roles were brought across so that none lost an action it had, in the same workspaces and environments it had them:
| A custom role that held | Was also given |
|---|---|
| Workflow Instances Edit | Job Instances Create, Job Instances View and Workflow Instances Execute |
| Workflow Instances Execute | Workflow Instances Create |
| Workflow Instances Delete | Workflow Instances Execute |
| Job Instances Edit or Job Instances Delete | Job Instances Execute |
Because each permission covers several actions, some roles can now do more than before. A role that held only Job Instances Edit can now also restart and force start jobs, and one that held only Job Instances Execute can now cancel and kill them. Review your custom roles with that in mind.
Worth knowing:
- A workflow that has since been deleted keeps its workspace. Its remaining workflow and job instances are read and acted on under the workspace the workflow was in, like any other. Earlier builds allowed it only to a role that granted the action in all workspaces of the environment.
- A role that grants a permission in all workspaces of the environment, such as Administrator, sees and acts on every instance there.
- A refused request changes nothing. The service answers with a
permission.deniederror naming the permission that is missing. - A dependency view can name a predecessor job in a workspace you cannot view. The job's name is shown so the dependency reads correctly; the job itself still cannot be opened.
- If the role lookup or the workflow lookup is briefly unavailable, the request is refused as unavailable rather than allowed through. Nothing was changed, and it can be tried again.
The event history needs Audit History
Reading the event log — the list of events, one event's detail, the events that share a correlation ID, and the event statistics — needs Audit History View, the same permission that offers the Event Log screen. It is global, so a grant applies tenant-wide.
Your own events are the one exception. A request for only the events you raised yourself is answered without the permission, which is what keeps the home dashboard's list of your events and its Self Service widgets working for everyone.
Vision's live view needs Vision Cards View. The board shows only the cards in workspaces that the role's Vision Cards View grants reach. See Vision.
Where Grants Apply
What an event is refused for
An OpCon event is a command that changes something — holds a job, sets a threshold, writes a property.
Events are also checked against a role, when they are saved. The events a workflow or a Vision card carries run later under the platform's own identity, so the permission each event type needs is checked once against the person saving it, scoped to the workspace of the object the event names. A workflow or service-request event has no environment until it is deployed, so it is accepted if the role grants the permission in any environment of that workspace; a Vision action that names its target environment is checked in that one. Only the events a save introduces are checked, so withdrawing a permission later does not block an unrelated edit of a config that already exists.
The same check applies in these places:
| Where | Who is checked, and for what |
|---|---|
| An OpCon Event action on a notification trigger, or on an escalation policy level | The person saving it: the permission the event's type needs, in the workspace of the object it names and the action's environment. A test send is checked on the line as it will be sent. |
| The events edited onto a running job instance | The person editing them, for the events the edit adds or changes. |
| An event submitted to Continuum directly | The person submitting it. |
| An automation import | The person importing: every event in each imported workflow, not only new ones — the permission its type needs, in the workspace the object it names will be in once imported (the General workspace for an object the import creates). One refused event refuses the import, and nothing is written. |
| A Self Service submission | The requester: Self Service Portal Execute for the button, then every event the request sends — the permission its type needs, in the workspace of the object it names once the requester's values are filled in — and Properties View for every property it names. One refused event refuses the whole submission, and nothing is sent. |
Separately from any role, Continuum refuses an event in these cases, whoever submits it.
| Refused | Why |
|---|---|
| An event type that is not a real event type | An unknown type is never treated as allowed. |
| A self service button whose template's first field is not literally a real event type — including one that only becomes a real type once a placeholder is filled | The type has to be known when the button is saved. |
| A name that matches objects in more than one workspace | Continuum cannot tell which object the event means. |
A [[…]] token whose property name is itself assembled when the event runs | There is no way to know which property it would read. |
| At submit, a token that cannot be resolved, or an input placeholder left unfilled, in the name of the object the event acts on | The event would not name a real object. |
At submit, a $PROPERTY event on an SSI. or SJI. property with a schedule part | The parent workflow or container job it writes to is only known when the event runs. Leave the schedule part blank, or address the parent directly. See instance-scoped property events. |
A self service request whose value reads an encrypted property, or whose resolved text still contains a [[ or {{ opener | An encrypted value cannot be copied into an event, and text left unresolved would be expanded again. |
| A self service request whose built event line carries more tokens than its template wrote | If a requester's input assembles a token the author never wrote, nobody authorized that read. |
| A suffixed date token in a field read as a date | See Date and time tokens. |
Where a grant applies
Every permission a role holds is granted in a scope, and the object type's scope model (on the Permission Catalog tab) decides which kind of scope it takes. Each kind has its own tab in the role editor:
| Tab | Object types it holds | A grant there applies |
|---|---|---|
| Global | Global (G) — for example roles, workspaces, calendars, tags | Tenant-wide. Workspace and environment never apply. |
| Workspaces | Workspace (W) — for example workflows, scripts, properties, connections | In the one workspace the grant names, or in every workspace for All workspaces. The environment is ignored. |
| Environments | Workspace × Environment (WE) — for example job instances, deployments, the Self Service portal | In the environment and workspace pair the grant names. Either half may be All environments or All workspaces. |
On the Workspaces tab, pick a workspace (or All workspaces) to add it to the role's list, then choose its permissions. On the Environments tab, pick an Environment and a Workspace, then Apply Environment + Workspace Selection to add the pair. Each workspace or pair in the list has its own permission rows, so a role can hold different permissions in each.
| A pair on the Environments tab | Applies |
|---|---|
| All environments + All workspaces | Everywhere. |
| All environments + a workspace | That workspace, in every environment. |
| An environment + All workspaces | That environment, in every workspace. |
| An environment + a workspace | Only that combination. |
A request is allowed when one of the person's roles holds a grant of that exact permission whose scope covers the object. A role's grant of a different permission in a wider scope does not count. A list returns only the objects the grants of its View permission reach.
Before per-scope grants, a role held one list of permissions and one list of scopes, and applied every permission in every scope. Each existing role was converted to grants that give exactly the access it had. The exception is a role that was saved with no scope at all: it keeps its global permissions, and its workspace and environment permissions now apply nowhere. Open such a role and add the workspaces and environments it should apply in.
An item you cannot view answers as not found
When you open or act on one item that is checked per workspace — a workflow, a script, a
deployment, a running instance — and none of your roles lets you view it where it is, Continuum
answers exactly as it would for an item that does not exist: <Item> not found, or you do not have
permission to view it. The answer names no workspace, so it does not reveal that the item is there.
If you can view the item but your roles do not grant the action, the action is refused with You do
not have permission to <action> this <item>. An event that names an object you cannot view is
refused in the same not-found words.
A permission that is checked tenant-wide, such as those on the Agents page, is checked before any item is looked up, so it is refused as a missing permission rather than answered as not found.
Where a grant has to be wider than one workspace
Most checks ask about the one workspace an object lives in. These ask for more, because the action itself reaches further than that:
| Action | What it needs |
|---|---|
| Creating an object | Create on the workspace it is written into — not the one you started from. When the request names no workspace, that is the tenant's General workspace, so a role scoped only to workspace A cannot create an object that lands in General. |
| Moving an object to another workspace | Edit on the destination, as well as the permission the edit itself needs. |
| Importing automation | Create and Edit on every workspace in the tenant (and, for an object type scoped by environment too, every environment), for each object type the bundle carries. An import matches existing objects by name across the whole tenant and writes them in place, so a role scoped to one workspace cannot import at all. |
| Exporting automation | View on every workspace in the tenant (and, for an object type scoped by environment too, every environment), for each object type the export asks for. |
| An environment-scoped transformation rule | Workflow Deployments Edit and Service Request Deployments Edit covering every workspace in that environment. The rule rewrites what is served to every deployment in the environment, so a grant for one workspace is not enough to write it. |
| An SAP lookup, or Start Check on Check SAP Job Numbers | Agents Execute under All workspaces — see SAP lookup permission. |
| Anything on the Agents page | The Agents, Agent Pools or Relays permission under All workspaces — see Agents, agent pools and relays are checked. |
A report is a smaller case of the same thing. Without Workspaces View, a report still runs, but it shows workspace ids where it would show names. Filtering or sorting that report on the workspace name is refused outright, naming that permission — a filter that silently matched nothing, or an order by id that looked like an order by name, would be worse than a refusal.
Simulation and catalog views
Neither view has a link on the Permissions page. Open them by address: /permissions/simulation and
/permissions/catalog. Both need Roles View. The older addresses, /roles/simulation and
/roles/catalog, redirect there.
- Permission simulation — pick a Role (and optionally a Workspace and Environment) and see each permission as Granted or Denied, with the reason for a denial: Role does not grant this permission, No scope tuple matches this context, Select a workspace to evaluate or Select an environment to evaluate. Use it to explain why a role does or does not grant something.
- Permission catalog — a read-only, searchable list of every permission grouped by object type,
showing each permission's action, description and id (such as
workflows.edit). The catalog currently holds 124 permissions across 33 object types. The newest object type is Relays (global), with View, Create, Edit and Delete — see Agents, agent pools and relays are checked (on the Permission Catalog tab). Before it came Workflow Instances Create and Job Instances Create — see Running workflows and jobs are checked per workspace (on the Permission Catalog tab) — and the z/OS JCL object type (global) — see z/OS JCL Edit (on the Permission Catalog tab). Before those came Environments and Saved Searches (both global) — see Environments and saved searches (on the Permission Catalog tab). Script Catalog (global) is for maintaining the tenant's own script runners and script types, Service Request Categories (global) covers the categories a self service button is filed in, and Vision Cards (workspace-scoped) arrived with the Vision feature.
- A role of your own named "Administrator" stops the built-in Administrator role from being created — a possible cause of unexpected Administrator behavior. Renaming or deleting your role is not enough on its own: the built-in role is created only after the platform next restarts, so contact support once you have renamed it.
- Use simulation to answer "does this role grant X?" questions.
Contact support when
- Simulation results contradict the permission catalog or the role's scopes. For Administrator specifically, check Administrator keeps up with the catalog (on the About Roles tab) first — a permission it was once short of is granted automatically now.