BrainDocs

Instance policies

Control signup mode, agent safety posture, workspace creation, auto personal workspace, and forgot-password.

On /settings/instance, instance admins set host-wide policies. Licensed hosts may lock some options based on entitlements. Signed-in members can read the current values; only the instance admin can change them.

PolicyUI labelMeaning
Signup modeInvite only / Open signup / SSO onlyWho can create accounts
Agent safety postureStrict / Auto / DangerousHow tool calls pause for approval, and whether Auto screens tool results
Allow create workspaceAllow creating workspacesUsers may create additional workspaces
Auto personal workspaceAuto personal workspaceProvision a personal workspace for new users
Allow forgot passwordAllow forgot passwordSelf-serve reset (needs SMTP for email)

Agent safety posture

Default is Auto. This control applies to interactive Agent turns.

PostureHITLResult screening
StrictAlmost every tool waits for in-chat approval, including reviewed reads and sandbox bash/writeAfter a tool runs, output is checked before the model sees it
AutoAllowlisted reads run; writes and unknown tools waitSame result screening as Strict
DangerousSkips those approval pausesSkips result screening in live chat

A command policy still blocks high-risk shell (recursive rm, mkfs, dd to /dev/, fork bombs) and destructive SQL (DROP TABLE, TRUNCATE, Mongo drop tools) in every posture, including Dangerous. Denied calls never become an approve prompt.

Auto and Strict also screen tool results for prompt-injection phrases and secret-like tokens (private keys, GitHub PATs, Slack tokens). A match is replaced with a short blocked stub. That is not an approve prompt, and it cannot undo a tool that already ran. Dangerous live chats skip that screening. Scheduled morning briefs and playbooks still screen (and keep Auto HITL) so they are not left unprotected.

Ask mode still blocks tools. Plan-style mutating-tool limits still apply if that mode is used.

See Approvals.

Signup mode notes

  • Invite only (default) — registration via invite links
  • Open signup/sign-up available when license allows
  • SSO only — password signup closed; company SSO on /sign-in (requires SSO entitlement)

Self-serve forgot-password also requires SMTP (BRAIN_EMAIL_FROM + BRAIN_SMTP_*). Instance admins can still reset passwords without SMTP.