Welcome to AxisSynapse

AxisSynapse is one platform for your workforce, your operations, your compliance, and your numbers. These docs are the same content the in-product help drawer reads from, so a tip you find here is the same tip your employee, admin, developer, or auditor finds when they press ? inside the live product.

TL;DR — Use the search bar (or ⌘K / Ctrl+K) to jump straight to a task. Use the left rail to browse a module from start to end. Use the right rail to skip to a section on a long page. Every doc here is print-friendly, dark-mode-aware, and translation-ready.

Who these docs are for

Four audiences, all welcome on every page. The top-bar audience pill reorders the recommended reading without hiding anything.

How these docs are organized

The information architecture is three orthogonal axes that all point at the same content. Whichever axis matches how you think about the problem will get you there in a click or two.

The page-anatomy contract

Every walkthrough you'll read here follows the same anatomy so you can scan it in 20 seconds.

1. 1

   Title and badges

   The first thing you see is the page title plus two badges: the plan tier the feature is available on, and the workspace role required to use it. If your plan or role doesn't match, you'll know before you read further.

2. 2

   One-paragraph orientation

   What this surface is, who uses it, why it matters. Reading it twice is allowed.

3. 3

   A bold TL;DR

   One or two sentences plus the time estimate to complete the task. Long pages start here when you're in a hurry.

4. 4

   "Before you start"

   Prerequisites — prior configuration, material you should gather, other docs you may want open in another tab.

5. 5

   Numbered Steps

   Each Step names the exact button label or field you'll see on screen. Steps never reference internal implementation; they describe the visible product.

6. 6

   "Every field, explained"

   A table documenting every form field on the screen: label, what it does, accepted values, default. No field on any walkthrough is left undocumented.

7. 7

   "What appears in the audit log"

   The audit codes the action emits, each linked to the canonical catalogue at Reference → Audit codes. Audit-relevant changes always show this section.

8. 8

   "Common gotchas" + "Troubleshooting"

   Real patterns that catch real customers, plus the public error codes that may surface, linked to their remedy.

9. 9

   Related docs

   Two to four cross-links to adjacent topics so you can finish what you started without backtracking to the rail.

What the badges mean

You'll see these everywhere — on doc pages, the home grid, search results.

Where the in-product help reads from

The drawer that appears when you press ? inside the live application loads from the same MDX corpus you're reading right now. Translation flows, dark mode, the role pill, search relevance — all of it is shared.

That means three things in practice:

• A page that lands here is immediately available in-product, with no separate sync cycle.
• A search query that finds a result here finds the same result inside the product (and vice versa).
• Internal-only material does not appear in either surface. Every page is reviewed against a published disclosure policy before it's added; if you find anything that looks like a leak, please report it via the security contact on the marketing site.

Keyboard shortcuts you'll want today

Accessibility posture

Every interactive surface is designed against WCAG 2.1 AA. That means a keyboard-only path through every page, screen-reader semantics on every component, sufficient color contrast in both light and dark mode, and a reduced-motion fallback that respects the system preference. Read more in Keyboard and accessibility.

What's safe to share

Every page here is public by design and SEO-indexed. We deliberately omit internal model names, monorepo paths, runtime implementation details, scoring weights, prompt internals, and anything else that would help a hostile competitor or attacker without helping a legitimate user. If you spot something that looks like a leak, please contact your account team or the security inbox linked from the marketing site.