Permissions and credentials

Each Studio MCP credential belongs to a current Studio account. Its permissions can narrow that account’s access, but cannot make it more powerful than the account. VoxelSite checks the account and credential on each request, including retries.

The owner creates credentials in Settings → Connections. Open Connection name, account, and expiry to select the account and a 7-, 30- or 90-day expiry. The default is 30 days.

Choose the main access level

Draft editing permits trusted PHP code. Private storage and scoped tools do not make that code a sandbox. Trust the client, the account and the person directing it with your server.

Also allow restoring the live website is a separate option for owner accounts. It can replace the published version while preserving the draft.

Grant additional access deliberately

Additional access separates business reading and editing, real form and Action submissions, taking the live site offline, configuration, email, prompt overrides, diagnostics, team management, connections, updates and resets.

Business writes may affect live records immediately. Action definition changes also affect the live runtime; Action bar settings remain draft changes. Email requires its own grant. See Business workspaces.

Owner-only administrative grants do not replace separate human approval where an operation requires it. A confirmation in an AI conversation is not an owner approval in Studio.

Save and replace credentials

The create flow reveals the usable credential once. Save it in your client’s secret configuration or local environment, then choose I’ve saved it. Keep it out of chat, repositories, screenshots and shared configuration.

If creation loses its response, use Check result and the retained retry controls. An unclaimed delivery may appear under Credentials ready to save. If the secret has already been claimed or is unavailable, revoke that credential and create a replacement; the saved creation receipt cannot reveal it again.

Revocation, expiry, an inactive account or disabled connections prevent further access. Disable connections is the global switch; removing a server from one client does not revoke its credential.

Use one clearly named credential per client or purpose so you can identify its recorded use and revoke it independently.