Skip to main content

Platform Admin Manual

This manual is for MedSuite platform staff — the team that provisions and operates the multi-tenant RCM platform. If you are a customer (provider organization) using the platform day-to-day, you want the Tenant Manual instead.

Two different things are called "admin" — this manual is not the console
NameWhat it isHost
docs-adminThis manual. A Docusaurus site; prose only, nothing to sign into.admin.docs.<env>.medsuiteone.ai
admin-appThe platform console — the SPA you actually click, with admin-service as its API behind the same host.admin.<env>.medsuiteone.ai

<env> is dev or stg; production drops the label, so the console is admin.medsuiteone.ai and this manual is admin.docs.medsuiteone.ai. The docs. separator is deliberate — it keeps admin, tenant, edi and billing usable as tenant slugs.

Both hosts are new. Platform administration used to be a route prefix (/platform/*) inside the tenant app, served from admin.rcm.medsuite.com. It is now its own application pair, and .medsuite.com has been retired as a customer domain.

⚠ /platform/ means two different things, and only one of them moved.

  • API paths kept it. POST /platform/auth/login, GET /platform/tenants, GET /platform/env-config — unchanged, now answered by admin-service. A browser or curl reaches them through the /api prefix the edge routes to the service: https://admin.<env>.medsuiteone.ai/api/platform/….
  • Console URLs dropped it. The SPA routes at the host root, so the pages are /tenants, /tenants/new, /env-config, /audit, /federation, /master-data/… — not /platform/tenants. An old /platform/… page link redirects to /tenants.

Engineering background: docs/architecture/adr/006-platform-admin-application.md and docs/operations/runbook-platform.md PLAT-2 in the repo.

Manual map​

What you'll find here​

  • New Customer Onboarding Guide — start here for a fresh platform install, plus the per-customer onboarding workflow.
  • Operations Runbook — daily ops, incident response, and on-call playbooks across nine task-shaped categories (tenant lifecycle, EDI, receivables, configuration, ingestion, clinical, reporting, security, platform infrastructure).
  • Federation — register partner IdPs, manage signing keys, configure per-tenant linking + scopes, revoke federated sessions.
  • Reference — glossary and master / tenant data-model diagrams.

Audience​

You are likely:

  • A platform admin with PLATFORM_ADMIN role — full provisioning + impersonation rights.
  • A support engineer with PLATFORM_SUPPORT role — read + limited writes, can impersonate.
  • A read-only operator with PLATFORM_READONLY role — view-only across master data.

All platform-admin sign-ins require step-up MFA (TOTP or WebAuthn) — see Operations → Security & Compliance.

Your day-to-day tasks live in this manual. Anything that requires editing source code or schema lives in the engineering docs (docs/operations/OPERATIONS_RUNBOOK.md, docs/development/RUN.md in the repo).

Need a quick reference?​