Support Surface

Public help content lives at the Support root; operator-only diagnostics stay behind platform roles.
Workspace users can reach help and contact paths without seeing Hangfire or worker-status tooling.

Workspace access

Switch workspaces safely before you troubleshoot

Many apparent support issues are really workspace-context issues. Confirm the current workspace first.

Article

Why the current workspace matters

The hosted application resolves the current workspace early in the request pipeline. If you are troubleshooting the wrong workspace, plan limits, runtime visibility, and support channels can all look inconsistent.

  • Open the workspace overview before opening a support request.
  • Verify the workspace name shown in the support access callout.
  • If the wrong workspace is active, switch first and then retry the action.

Article

What not to expect

Switching workspaces should never reveal operator-only tooling such as Hangfire dashboards or support-operations status pages. Those remain tied to platform roles, not workspace membership.

  • Workspace support and platform support are separate boundaries.
  • Help-center pages remain public regardless of workspace membership.
  • Only platform support roles should see the operations console.

Related Articles

Keep reading

Open full help center
Invite users without losing track of reserved seats Workspace owners and admins

Pending invitations now reserve seats, so member management and support messaging should start from the workspace overview instead of guesswork.

Read article