Skip to content

What RShift Support can see

The exact context support receives, and what it never receives.

Updated View as Markdown

Support is reached through email written to the product’s support address. Nothing is sent to a third-party chat vendor.

Context that can be sent

  • RShift user id.
  • Current workspace id or slug.
  • Current module, such as integrations, billing, or monitoring.
  • Plan, entitlements, and AI credit state.
  • Provider, status, error code, run id, or job id.

Content that is not sent

  • Platform tokens, refresh tokens, API keys, client secrets.
  • AI prompts, completions, tool inputs, or tool outputs.
  • Publishing body text, asset files, or unpublished drafts.
  • Raw monitoring data and audit log contents.
  • Application package files.
  • Payment card numbers or raw payment provider payloads.

If support asks for more, share visible error codes, screenshots, time ranges, and states — never secrets, tokens, or private customer content.

Navigation

Search for a question, a feature, or a task.

↑↓ to navigate↵ to openEsc to close