Settings

Settings holds everything you configure; the main rail holds what you use. Open it from the workspace menu, with ⌘, or with g s. The rail switches to the settings tree, topped by ← Back to app, with six groups:

Your display name and picture are global. Your mention handle is specific to each workspace and is set on your Profile. Authorized apps are grants to act as you; Connected accounts are OAuth/tool identities you own; workspace Connections are governed and may be private or shared.

Roles and access

Every member has a workspace-level role:

  • Member — works in the workspace; can view General, Execution & network, Billing usage, and connections, secrets and devices shared with them.
  • Admin — everything above, plus Members, Teams, Billing, Trash, Objects, Shared fields, Labels, Policies and the Audit log.
  • Owner — the workspace creator's protected role. Only the owner sees the Danger zone in General and the Cycle diagnostics under Teams.

Admin-only rows are absent for members. Pages members can open but not change render read-only controls.

The Operator console is not a workspace destination. It is a separate, cross-workspace support console at /operator, shown in the workspace menu only to explicitly allowlisted Rollout operators.

General

The workspace's identity and defaults. Members can view; admins can edit.

  • Name — rename the workspace in place.
  • Fiscal year starts — pick the start month. Fiscal-year filter tokens shift for everyone in the workspace.

Members

Admins invite teammates, adjust roles, and manage access at /settings/members.

  • Invite member — enter an email and choose Member or Admin. Invitees join with a workspace-level role; team membership is managed on team pages.
  • Change role — switch a member between Member and Admin. The select saves on change. You cannot demote yourself if you are the last admin, and the owner's role can't be changed here.
  • Invites — resend or revoke a pending invite.
  • Suspend / Activate — suspended members immediately lose access but keep their history.
  • Remove — removes the member from the workspace immediately. The owner can't be suspended or removed from settings.

Billing & usage

Plan and consumption form one family under /settings/billing:

  • Plan shows the current commercial plan, included usage, concurrent-run limit, and storage allowance. Cloud subscriptions expose billing management; self-hosted installations expose license state here instead of in General.
  • Usage at /settings/billing/usage shows recent runner time, storage, managed AI consumption, spend by workflow, workflow activity, and cluster resources.
  • Capacity links to Dedicated capacity.

Everyone can view usage. Plan and billing controls are admin-only. Credit-pack checkout appears only for entitled Cloud Pro subscriptions and never replaces the platform subscription.

Objects, shared fields and labels

Admin-only, under the Data group:

  • Objects at /settings/objects lists the built-in objects (Tasks, Projects, Objectives, Documents) and your custom objects. Each object's settings cover its fields, placement, access and search; Tasks adds Statuses and Types.
  • Shared fields at /settings/fields add reusable fields to tasks, projects, objectives, and documents.
  • Labels at /settings/labels are shared taxonomy for work, automation, documents, and records.

See Objects & Records for the object guide.

Teams

Admin-only. Settings › Teams lists the workspace's teams, with Cycle defaults beside it and owner-only invariant diagnostics. Each team has General (/settings/teams/:team), Members (/settings/teams/:team/members) and Cycles (/settings/teams/:team/cycles) tabs; the gear on a team's page opens them. A team's Current, Upcoming and History cycle views live on the team itself at /teams/:team/cycles, /teams/:team/cycles/upcoming and /teams/:team/cycles/history.

Agents

Agents live in the main rail under Automation. They are AI agent identities you bind to message and call trigger nodes in your Workflows. Any active member can create a private agent; sharing follows the private/team/workspace model, and team access inherits through the hierarchy.

  • Each agent has a name, handle, description, and avatar.
  • The model profile (model, BYOK model, token budget, BYOK connection) overrides the AI node's own settings wherever the agent acts.
  • Deactivated agents keep their bindings but stop answering. Admins can designate a workspace-shared agent as the default.
  • The Agents list takes the same filters and saved views as other lists. Each agent has Overview, Workflows, Chats, Access and Settings tabs.
  • The agent's Workflows tab lists its message and call bindings read-only — edit bindings from the trigger node in the workflow editor.

Pending deployment in this release: Task workflows adds a separate editable route from an agent and Project to an enabled, published workflow you own. Choose the workflow's Start entry and, when needed, its execution device. The assignment trigger can be Enabled or Paused. Workflow behavior stays in the workflow editor, and reusable instructions stay in Documents. See Task workflows for setup and Task-thread continuity.

Connections

Credentials and connectivity that back workflow Nodes — OAuth, credential, and connectivity providers. Add and share workspace Connections at /settings/connections. Personal authorization grants live under Authorized apps, while user-owned OAuth identities live under Connected accounts. See Integrations for providers, scopes, and sharing.

Secrets

Named values workflow steps resolve at runtime. Values are write-only: set exactly once at creation and never viewable again, anywhere.

  • Names are UPPER_SNAKE_CASE (a letter, then letters, digits, or underscores; max 63 characters).
  • A secret is either a locally encrypted value or a 1Password reference (op://vault/item/field) — the reference option appears only when the workspace has a 1Password Connection.
  • Sharing follows the private/team/workspace model. Workspace admins do not bypass private secrets.
  • Every access to the secret store is recorded in the audit log. See Security for the encryption model.

Execution & network

/settings/runtime contains network and runtime rules applied to the workspace's workflow Runs. Members can read the policy; only admins can change it.

  • Outbound network access — off by default. When on, Runs can only reach the listed destinations over HTTPS: plan defaults plus custom additions on Cloud Pro or Business. Changes apply to new Runs within a few minutes.
  • Container image registries — off by default. When on, workflow images must come from the allowed registries; custom entries replace the defaults (docker.io, ghcr.io). Enforced when Workflows are saved and when Runs start.

Devices

Devices registered by the Rollout client apps, with per-device sharing and the capabilities exposed to Workflows. Manage them at /settings/devices. A device stays private to its owner until deliberately shared. A device's details list what uses it: workflows whose steps run on it, agents whose task routes run on it, and tools pinned to it. It lists only what you can open. See Desktop App Companion.

Trash

Admin-only. Deleting a Workflow, Project, Task, Document, Objective or Template sends it to Trash for 30 days; after that it is permanently deleted (a Workflow with its runs, snapshots, and branches). Restore brings it back exactly as it was, and a restored Workflow re-arms Triggers only if it is enabled; Delete now removes it early. Deleting a Project keeps its Tasks: they leave with the Project into Trash and, when it is purged, stay as archived Tasks without a project that you can restore from the Tasks Archived view. The Project's context Pages move to the workspace. A Task or Project that Cycle history or team history still refers to disappears everywhere when purged, but reports keep showing its name. Apps and Pages can only be archived. Archived items are not in Trash: each list's Archived view shows them with a Restore action.

Audit log

Admin-only, append-only — entries cannot be edited or deleted. The Secrets, Access, and Billing tabs separate secret-store activity, operational sharing and ownership changes, and commercial events. See Security.

API keys

API keys are personal and live under your account at Security & access › API keys, not in workspace settings. Each key is bound to one workspace and acts on your behalf inside it. Generate a key, copy it once, and use it as a bearer token — for example in your local MCP config (see MCP Integration). Revoke keys individually or all at once.

Danger zone

Owner-only. Delete workspace permanently deletes the workspace and all of its data — projects, tasks, workflows, messages, and activity history. There is no grace period and no recovery. You confirm by typing the workspace name, and a recent re-authentication is required; everyone in the workspace loses access immediately.