Manage your SaaS workspace
This section is for administrators of a customer enterprise. Commands depend on your assigned role. It describes customer-facing administration only.
Enterprise and project settings
Section titled “Enterprise and project settings”Use Admin for the available enterprise-wide management pages. Ordinary project work remains under App. Confirm the current enterprise/project context before applying a change.
Enterprise defaults apply to resources that inherit them. Project settings can override those defaults, and Jobs/Tasks can apply more specific overrides. Review effective values and origins before saving.
Suspension, archive and deletion are different operations. Read the actual command and confirmation. Do not infer that a suspended project has no accepted work, that archive deletes results, or that removing membership stops a Robot.
Project Danger zone
Section titled “Project Danger zone”Authorized project settings expose Reset project and Delete project separately. Both erase project Jobs, Tasks, execution/Toolbox content, collected data/history, files, Containers and Browser profiles. Reset keeps the project identity and its retained settings/access/capacity; Delete also removes the project and its settings/secrets. Retained reset settings may still reference removed files/profiles and need repair.
Read the confirmation and cleanup status before proceeding. Outstanding work or transfers can block the operation. Cancel writes nothing. An uncertain response calls for consulting/retrying the same command through the offered controls, not starting an unrelated cleanup. These commands are separate from suspending dispatch or deleting selected Data rows.
Capacity
Section titled “Capacity”Your enterprise’s available Robot capacity is granted by the service. Customer configuration can allocate within the granted envelope; it cannot increase the service allowance.
Use project capacity controls where available to manage the distribution. Capacity configuration is separate from whether a particular Session has started and from whether a selected Robot can execute its actions.
If work remains queued, inspect project dispatch, Session diagnostics and current capacity before changing retry settings. Increasing retries does not create capacity.
Change management
Section titled “Change management”Review a settings change with the people responsible for affected Jobs and schedules. New accepted executions can use updated inherited settings; existing accepted Sessions keep their captured values.
When a command reports a revision conflict, consult the latest saved state. When its outcome is uncertain, use its consultation/reconciliation controls before creating a different operation.
Plans and limits
Section titled “Plans and limits”Review current plans for allowances and commercial terms. Some account flows are enabled separately; a published offer is not proof that checkout, extra-spend authorization or a support inbox is available in your current workspace. Single-user restrictions can prevent invitations. A Toolbox is not an ordinary Session, but interactive usage can still count under the applicable offer.
For day-to-day administration, continue with members and project access and managed secrets and keys.