Skip to content

Review data and security controls

Understand workspace isolation, audit logging, credential boundaries, and public-static-path restrictions.

Updated View as Markdown
For humans

Steps

  1. Open Security and review the controls available to the workspace.
  2. Confirm member access, integrations, MCP connections, public Pages, data actions, and monitoring destinations.
  3. Keep third-party tokens, APKs, user content, and monitoring data out of public static assets and logs.
  4. Use approved rotation, export, and offboarding workflows for sensitive state.

If you still need help

Search this Help Center using the exact feature or visible error. If the issue continues, use Call Rshift support from the Help Center navigation. Include any public reference and the approximate timestamp, but never include passwords, access tokens, provider credentials, or raw webhook payloads.

Rshift
Help and documentation for Rshift.
Navigation

Type to search…

↑↓ navigate↵ selectEsc close