Capability controls
Narrow which built-in capabilities appear in your own tool list, and understand the organization-level ceiling above it.
Capability controls apply to the built-ins — Memory, Media, Web, and Social — not to connectors. Connecting or disconnecting an account is already a connector's switch.
The control surface is Dashboard → Tools. Built-ins are on by default; a setting only narrows what you see.
Open a card to browse its tools and descriptions. Use Enable for me on the detail page to change your personal setting. Disabled groups remain browsable.
Two levels, one effective result
effective capability = enabled for the organization AND enabled by the member- The member level is yours. Each member can turn a built-in off for themselves in Dashboard → Tools. The setting is scoped to that member in that organization — never to a global profile, so the same person can have different settings in two organizations.
- The organization level is the ceiling, and CoreSpeed operates it. A capability can be disabled for a whole organization on the platform side; when it is, no member can turn it back on from the dashboard. Contact support if a built-in is missing for everyone in your organization.
- No stored setting means enabled. Only deviations from the default are recorded.
What disabling changes
Disabling a built-in unregisters its tools from your /mcp surface. They
disappear from tools/list rather than staying visible and failing at
execution time, so an agent never sees a tool it cannot call.
Disabling Memory affects tool visibility only: existing memories stay stored until you delete them in Dashboard → Memory. Disabling Media likewise leaves stored artifacts and job receipts in place.
Settings apply per member, not per credential: an API key follows the settings of the member who created it. An agent has no settings of its own, so an agent key sees every built-in the organization allows.