10xDotIn Product Docs

Operator and Admin Escalation Appendix

Operator and Admin Escalation Appendix

Last updated: 2026-03-06

This appendix explains role-gated operations that are intentionally excluded from creator-safe public playbook steps.

1. Role badges

  • [Creator]: creator-safe route/action
  • [Operator]: operator role required
  • [Platform Admin]: platform-admin role required
  • [Escalation]: requires support-assisted execution or platform intervention

2. What changed in public docs

Advanced control-plane route paths are not published in external documentation. Public playbooks describe outcomes, guardrails, and evidence needed for escalation instead of exposing internal endpoint contracts.

3. Role-gated operation families (public-safe view)

  1. Platform-admin governance actions
  2. Operator publish/rollback actions
  3. Support-assisted recovery actions

4. Escalation handoff requirements

When a playbook reaches a role-gated boundary, submit POST /v2/support/report and include:

  • incident summary and expected outcome
  • handle, actor role, and environment
  • request IDs, run IDs, and affected resources
  • pre/post state evidence and rollback intent (if relevant)

Updated Jun 19, 2026