AxisSynapse Documentation

Every workspace surface, written for the person using it.

One platform, one corpus, one source of truth — for the employees who file requests, the admins who configure, the developers who integrate, and the auditors who confirm. The same MDX powers the in-product help drawer.

  • 84 guides
  • 11 modules
  • 4 audiences
  • Mobile-first · print-perfect · WCAG 2.1 AA

Pick your reading lens

The same pages, ranked for what you care about most.

Where to start

The four first-class entry points. Every workspace touches these.

Every module, every audience

Eleven modules. Each carries a welcome page and ServiceNow-depth walkthroughs of its core surfaces.

Curated journeys

Four common paths a visitor might be on. Each one strings the guides that complete the task.

Why these docs

Six commitments that travel with every page in the corpus.

  • Source of truth

    The in-product help drawer reads the same MDX you're on now. One corpus, no drift between docs and product.

  • Print-perfect

    Cmd+P scrubs the chrome and produces an evidence-pack-ready PDF. Auditors don't need a separate export.

  • Mobile-first

    Every page reflows at 375 px. Enforced by lint so the next page we add today still passes tomorrow.

  • Accessible

    WCAG 2.1 AA against every page — keyboard paths, screen-reader semantics, reduced-motion respect.

  • Translation-ready

    Structurally localized; a locale switcher in Account drives the entire surface, in-product and docs.

  • Dark + light

    Every page renders against the platform design tokens in both modes. No second authoring pass.

Reference catalogues

The four catalogues every contract — API, events, audit, errors — read from the canonical registries.

The pages buyers, admins, and security teams open most often.

What's new

Documentation reaches full coverage · 84 pages across every module

See the full changelog for everything that shipped this release.

These docs are intentionally focused on how to usethe product — they never publish internal implementation details, server-side schemas, or anything that wouldn't help a real reader. If you find anything that looks like a leak, contact your account team or the security inbox on the marketing site.