Workspace settings

Workspace Settings lives at /confluye/{slug}/settings/{section}. Default section is General. Deep links accept a resource id after the section (for example an API key id).

Navigation

Authentication contains enterprise organization and SSO settings. Environments preserves previous environment and release records, with links to each workflow's Versions & previews; it does not publish new releases (Enterprise). Mailer is documented under Mailer. API keys: API Keys. Security is where you verify MFA before AIMS governance actions. Approvals, in the main navigation, is the queue-first AIMS surface for governed drafts, review, renewal, and blocked production — see AI governance.

The previous AI Governance (governance) URL remains valid and opens the same Approvals page outside the Settings layout. Its Pending, Workflows, Approvals & history, and Configuration tabs preserve their links. The entry appears for an effective interactive AIMS assignment, an eligible setup step, or an Organization Owner who can manage approval policy; workspace ownership alone does not grant AIMS access.

General: workspace identity

An explicit workspace Owner or Admin can change the display name in Settings → General. The workspace slug, ID, URL, memberships, visibility, API keys, and integrations do not change. Existing bookmarks and automation therefore keep the same address after a rename.

The session tRPC and REST surfaces share the same trimmed 1–120 character name contract and audited rename service. Automated clients can use the confirmed, idempotent workspaces.rename capability; the organization MCP endpoint additionally requires a selected workspaceId. Submitting the current name is a successful no-op and does not write misleading change evidence.

A workspace Owner or Admin controls ordinary workspace access. That is not an AIMS role. The AIMS accountable System Owner is a separate governance assignment made in Approvals; the same person may hold both or neither. See AI governance.

General: members

General is Access. An organization Owner or Admin first invites external people to the organization. A workspace Owner or Admin can then assign an existing organization member to the workspace with role member, admin, or viewer (not owner). Workspace ownership transfers use the dedicated Owner-only action and are serialized so a workspace cannot lose its final Owner.

POST /api/v1/workspace-members requires a workspace API key with Admin or Owner authority. Invalid assignment roles return 400 "Member role must be admin, member, or viewer.". The email must already be an active member of the workspace organization; otherwise the API returns 409 with organization_membership_required and creates no invitation or assignment.

GET /api/v1/workspace-members lists explicit assignments as { members[] } (role, status, presence, lastActiveAt). A workspace Admin or Owner key is required.

GET /api/v1/workspaces returns { workspace } for the key's workspace.

Preferences

Canvas/theme/chat provider preferences: session GET|PATCH /api/settings/preferences and v1 GET|PATCH /api/v1/settings/preferences. Patchable fields include theme, autoConnectOnDrop, canvasErrorNotifications, canvasViewport, snapToGrid, showCanvasControls, allowTelemetry, chatAiProvider, chatAiModel, liveTransports, workflow/chat folders and assignments.

For Codex and Claude Code chat, the selected model and reasoning/Fast settings are forwarded to the connected CLI, including models newer than the bundled default list. An invalid selection reports an error rather than silently choosing a different model. Refresh the connected provider's models and select an available entry when a model is unavailable. This chat preference is separate from governed workflow-node model evidence.

v1 preferences accept any valid API key (not workspace-scope-only). Session PATCH uses workspaceId from the body or the session.

agentRuntimeRollout is not on the preferences PATCH allow-list. Use session GET|PATCH /api/settings/agent-rollout as Admin/Owner. Surfaces: agentNode, copilot, home. Modes: legacy, shadow, v2, or null to revert to env default. Audited as agent_runtime.rollout.update.

Git review repository

Require merged PRs for previews is editable by workspace Admins and Owners. Off allows a preview to test an exact commit from an open PR; on requires a verified merge for previews as well. Production always requires merge when a repository is linked. AIMS approval is required separately for every live destination. Policy changes apply to the next publication and do not stop existing deployments.

The API field is policy.requirePreviewMerge (boolean). Omitting policy while updating repository fields preserves the stored policy.

Session GET|PATCH|DELETE /api/settings/repository (tRPC settings.getRepository / upsertRepository / deleteRepository). GET: any member. PATCH/DELETE: Admin or Owner. PATCH requires owner and repo; defaults defaultBranch: main, pathPrefix: workflows. Response includes repositoryAccess (verified / warning / failed) from a GitHub list-files probe. There is no v1 repository route.

Authorization summary

Most Settings reads need only membership. Stricter roles: repository write (Admin/Owner), agent rollout (Admin/Owner), v1 member invite (Admin/Owner), observability retention POST (Owner — see recovery).

Provider connection verification

Use Test in Integrations to verify that the saved workspace credential can authenticate. Before a release, also execute the provider's workflow block against a dedicated test resource: credential testing alone does not prove node mapping, live controls, runtime scopes, or result handling. Read probes should run first. External writes require an explicit confirmation and a cleanup plan.

OpenAI voice transcription uses the workspace AI provider and gpt-4o-mini-transcribe. Audio remains bounded by the upload and duration limits; Confluye records duration/model usage, not audio bytes or transcript content. Google Slides connections use the limited drive.file scope and can access presentations created by or explicitly selected for the app.

Next steps