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.

Voice recordings are limited to 10 MB and 60 seconds. Duration is verified from the uploaded audio, including fragmented MP4 recordings, and provider-reported duration can increase the metered amount. A provider request that completes can still incur usage when it returns an empty transcript or the recording fails the final duration check.

Personal browser connections

Manage my browser connections opens the personal connection screen. The deployment administrator must configure the browser worker first. If you open the screen directly, choose your workspace before adding a connection. Each connection can use a different website, including Centris. Enter a connection name, HTTPS login page, HTTPS account page, and exact text that uniquely identifies your signed-in account on that page, such as your displayed email. Do not use text also shown before login. Add any extra domains needed when the agent reuses the session, such as single sign-on or page resources. During human login the private browser can follow any public HTTPS website, including SSO and MFA redirects. Private networks and non-HTTPS destinations remain blocked. Saving keeps only cookies and storage belonging to the configured site domains; the agent then uses that domain allowlist. Extra domains are used only for login and page resources: agents read pages only on the account page's domain, and a read blocks any request that could change the account, such as a form submission.

Add the connection, choose Open browser, and complete login and MFA in the private browser viewer. The browser fills the available screen and adapts to mobile width. Tap or click a website field and type directly; use your keyboard, mouse wheel or touch swipes normally. Enter credentials for that website manually; the viewer does not provide Confluye password autofill. The browser bar shows the current domain and provides navigation and Refresh browser after an external MFA step. Save and verify closes that browser and checks the same account in a new session. Both persistent cookies and session cookies are restored; their expiration is not extended. Only a successful check marks the connection ready. Sessions can expire and require another interactive login. If Save and verify reports an error after the browser closed, the connection stays in saving; choose Save and verify again to finish.

Connections belong to their creator in the selected workspace. Create login link issues a private, single-use link that expires in 15 minutes for a new, disconnected connection. While the recipient's temporary access is active, you cannot view or control that browser. Send it only to the intended account holder: possession of this link grants access to that connection's login screen, without registering or signing in to Confluye. It never grants access to the rest of the app. The guest uses the same direct browser controls, without a separate text-entry form or keyboard buttons. For a temporary loading or viewport-sizing error, choose Retry; use the address bar or Back after a failed navigation. A slow preview capture keeps an open login available for Retry without sending the login again. If the page says the browser stopped and needs recovery, ask the sender for a new connection link; this is a browser failure even when the invitation has not expired. Typing is grouped into short batches instead of sending a request for each letter. Clicking, pressing Enter or navigating sends any earlier text first. Saving waits until typing, other input and the current preview update finish in both owner and guest viewers. The guest preview updates every two seconds for up to 20 seconds after opening, interacting or choosing Refresh browser, so a delayed navigation can finish without another click. Updates pause during input and stop after a snapshot error, when idle or when the viewer closes. If external MFA takes longer, choose Refresh browser to resume.

Opening or previewing the link does not consume it. The recipient selects Connect my account, then Open secure browser, and signs in to the website. Save and allow access verifies the saved session, enables agent reading, closes the viewer and ends the temporary access. The recipient can close the page and return to the conversation. Temporary access lasts at most 15 minutes after redemption. If saving reports a temporary error, retry Save and allow access. Reloading the page recovers a completed confirmation without reopening the browser. If cancellation fails, retry Cancel connection; browser control is already blocked while cleanup is pending. After the link session expires, ask the sender to finish cleanup. A viewer that reaches its ten-minute limit can be opened again to continue login. Issuing a replacement link before the browser opens invalidates the previous link. Links cannot expose an existing account, even if its session has expired. Create a new connection to request another person's login. Old invitations issued before this feature require a replacement link.

Disconnect and delete profile immediately blocks reuse and requests provider cleanup. If a browser operation is still running, the status remains revoking until cleanup succeeds; retry the button or contact the administrator. Recovery required also needs administrator attention. Your saved login stays on the dedicated Playwright worker in your deployment; Confluye stores encrypted references and site configuration. The saved cookies, local storage and site data are encrypted with a worker-only key. Encrypting the worker volume at rest is still recommended. Cookies are never returned to the agent.

Agents and workflow blocks can use the same connection at the same time; each action runs in its own temporary browser. Some websites sign you out when one session is used from several places at once. If that happens, sign in again and avoid running simultaneous actions for that site.

The preview Web browser workflow blocks offer Verify saved access, Get connection status and Read authenticated page. Select your connection, enter a page URL when reading a page, save the block, then use Authorize this block and save again. Authorization is limited to the same owner, workspace, workflow and block. Revoke block access disables subsequent use. Copying or exporting a workflow clears these account bindings. Existing Centris verification blocks remain compatible.

For Codex CLI and Claude Code workflow nodes, select a connection under Playwright MCP · saved browser, save, choose Authorize browser control, then save again. This separate control grant lets the agent navigate, click and fill forms, including submitting changes, through the existing MCP attachment mechanism. Once browser control is authorized, these browser tools can run unattended. This grant does not authorize tools on other MCP servers, and revoking it stops subsequent browser calls. It keeps other MCP tools and instruction skills. Each node run gets its own temporary browser from your saved login, which is saved and closed automatically; other runs and agent reads can use the same connection at the same time, so avoid running simultaneous changes to the same account. Revoke block access disables subsequent calls. Copy/export clears the binding. See MCP browser control.

For conversational agent access after connecting through the owner screen, choose Allow my agent to read. The recipient's Save and allow access already grants this permission in the private-link flow. Your agent can list your connections and read visible page text and links on each connection's account site using browser.list and browser.read. Remove agent read access stops subsequent agent reads without deleting the connection or changing a separately authorized workflow block. Other users cannot reuse your session. Page content is untrusted website data. These conversational tools support navigation and reading; form interaction requires the separate CLI node control grant above. Document-signing integrations and automatic Telegram account linking are not included.

End users and memory

When the deployment runs with FLUXUS_END_USERS=true, Integrations also shows End users and memory. Its Manage end users and memory button opens the console inside this workspace's app layout, preserving its navigation and theme: the external customers your product serves, the memory resources your workflows share per customer, and the websites and site notes those customers use. Workspace Admins and Owners with explicit membership can read and change customer content and delete a memory resource; every read is audited. The card is hidden while the flag is off. See End users and memory.

Next steps