The Organisation Settings page at /settings/org/settings is where you flip features on and off for everyone in your org. There is no global save; every toggle commits immediately when clicked.
Layout
Five cards, stacked:
- Chat & AI Capabilities: what users can do inside a conversation
- Memory: whether members can save facts from conversations
- Sharing & Collaboration: member sharing and visibility
- Shell & MCP Access: isolated shell containers, MCP servers, and custom connectors
- User Management: shortcuts into the Members and Teams pages (documented separately in Users and teams)
Each toggle shows its current state (On or Off), a description, and an Enable/Disable button. Some toggles carry a small badge or a lock icon. See Platform overrides below.
Chat & AI Capabilities
| Toggle | What it controls |
|---|---|
| Web Search | Whether users can ask the model to search the web for real-time information during a conversation |
| File Attachments | Whether users can attach PDFs, images, and other documents to messages for the model to analyse |
| Code Execution | Whether the model is allowed to write and run code inside shell containers to complete a task |
| Skills | Whether the model can use reusable skills (document creation and more) automatically. Requires Code Execution. Sub-toggles govern whether members can create, share, and promote their own skills |
| Automations | Whether users can dispatch long-running autonomous agents and build automated workflows |
| Image Generation | Whether the model can create images from a prompt |
These default to on for a new org. Turning one off hides the corresponding UI affordance in chat (for example, disabling Web Search removes the globe button from the composer) and refuses the equivalent API path.
Shell & MCP Access
| Toggle | What it controls |
|---|---|
| Shell Access | Whether members get isolated shell containers. Required for Code Execution and any tool that uses the shell |
| MCP Servers | The master switch for Model Context Protocol tools and connectors in your org |
| Custom MCP Servers | Whether org admins can register their own external connectors: MCP servers and REST APIs. Opens the Custom Connectors page (see below) |
To add your own connectors, turn on both MCP Servers and Custom MCP Servers, then register each one on the dedicated Custom Connectors page. Registration is self-service for org admins; there is no separate approval queue.
Platform overrides
Some toggles can be disabled platform-wide by the PrivateMind platform team. When that happens the toggle:
- shows in a dimmed, locked state
- displays the message "Disabled platform-wide by administrator"
- refuses the Enable click
You cannot re-enable a platform-overridden feature from this page. If a feature you need is locked off, contact support.
The override is one-way: platform admins can disable but not force-enable. Your local Off state still wins over a platform-wide On state.
Registering custom connectors
Your own connectors (external MCP servers and REST APIs) are registered on a dedicated page at /settings/org/mcp-servers (Settings, Custom Connectors in the sidebar), not here. Once MCP Servers and Custom MCP Servers are on above, an org admin opens that page, adds each connector by name and URL, and PrivateMind opens the egress path for it. Registered connectors then appear in the Connectors Library for everyone in your org, who can connect them (which adds them to My Connectors) and attach them in a chat.
The full walkthrough is in the Custom Connectors guide.
What is not on this page
- Org name, display name, description, logo. These come from your subscription record and are edited by your PrivateMind account contact, not in the app.
- SSO configuration. Allowed email domains, IdP endpoints, and SAML metadata are configured outside the app, at the identity provider and platform layer.
- Data residency. Where your data is stored depends on where your org was provisioned. Changing residency requires re-provisioning and is handled by support.
- Subscription details. Tier, billing cycle, user limit, storage limit, and feature access are visible on the Overview page but are managed by the PrivateMind platform team.
If you expected to find any of these on this page and don't, that is by design. They are platform-level rather than org-admin-level controls.
Where next
- Users and teams: manage members and team groupings
- Audit logs: every toggle flip is logged with who and when
- Budgets and limits: metering and spend controls for the org
