Build Agent Access Control

The Access Control administration page lets administrators decide who can use the Build Agent. Access is set for the environment, for each workspace, and for each Creator role. Access is not set for individual Creators. Changes on the page save together when an administrator selects Save Changes.

Only Designer Administrators can open this page. For other Creators, the Access Control item in the Settings sidebar is unavailable. The page is available only when UnqorkAI is on for the environment.

To open Access Control, navigate to Administration > Environment Settings > Build Agent > Access Control.

Environment Switch

The Build Agent Access for this Environment card at the top of the page has one switch. It controls the Build Agent for every Creator and workspace in the environment. The Roles and Workspaces tabs are below the card.

Roles

The Roles tab is the default tab. It lists every Creator role in the environment, including the Administrator role, with one level for each role.

The table displays 10 roles per page. When the environment has more roles, use Rows per page and the page controls below the table to move through the list.

The Build Agent Level drop-down has the following options.

A Creator who holds more than one role receives the highest level of those roles. The Administrator role is a role like any other, so an administrator can set it to No Access.

Role levels apply to Creators who hold an environment Creator role. Use the workspace switch to restrict Creators who hold only workspace roles.

The level for a role is also available in the Build Agent field of the Creator role form. See Creator Role Administration.

The Build Agent level is separate from the No Access workspace role. The workspace role controls access to a workspace. The level controls access to the Build Agent.

Workspaces

The Workspaces tab lists every workspace in the environment, each with its own switch. The switch controls whether the Build Agent is available in that workspace.

The table displays 10 workspaces per page. When the environment has more workspaces, use Rows per page and the page controls below the table to move through the list. When the page opens, workspaces with the switch off display first, followed by workspaces with the switch on. Each group is in alphabetical order. A row stays in place when its switch changes, so the list does not move under the pointer.

Saving Changes

The environment switch, every role level, and every workspace switch save together when a Creator selects Save Changes at the bottom of the page. The button is unavailable until a Creator changes a setting on either tab. While the page saves, the controls are locked and the button label changes to Saving....

After a successful save, the page displays Build Agent access settings have been saved. If the save fails, the page displays a message that explains the issue. The changes stay on the page so the Creator can try again.

A Creator who leaves the page with unsaved changes sees the Unsaved Changes dialog. The dialog has the following options:

• Save & Continue: Saves the changes, then leaves the page.
• Discard Changes: Leaves the page without saving.
• Cancel: Closes the dialog and keeps the Creator on the page.

Changes are recorded in the audit log after they save successfully.

How the Settings Combine

The Build Agent checks the environment switch first, then the workspace switch, and then the role level. If any of the three denies access, the Creator cannot use the Build Agent.

With no saved settings, the environment switch and every workspace switch are on and every role is set to Builder. Upgrading an environment does not change who can use the Build Agent.

What Creators See

When access is denied or limited, the Build Agent panel reacts as follows.

Removing access does not end a run that is already in progress. The run continues until it finishes or the Creator selects Stop run. After the run ends, the Creator cannot send another message.