How to use Alchex

Start here

The shortest path from signing in to a published document — what to set up, in what order, and what you can safely skip.

Document system overview

How documents move from draft to published version in Alchex, and the terms you meet along the way.

Workspaces and teams

The two containers everything else sits inside — what belongs to a workspace, what belongs to a team, and how that decides who sees what.

Your inbox

What Alchex tells you about, where those notices arrive, and what it deliberately stays quiet about.

Creating documents

The three ways to start a document in Alchex — from scratch, from a marketplace template, or by uploading a file you already have.

The editor

How to write and format a draft in Alchex, what the slash palette offers, and what "saved" means for your work.

References

Inline chips that point at another document, a register, a control, a risk or a connected source, and stay current as those records change.

Workflows in documents

Turn a procedure document into running processes — the builder reads your prose and separates it into the processes it describes, each with its own on/off switch.

Drafts

How Alchex's single live draft per document works — who can edit it, where unsaved work lives, and how a draft is superseded.

Collaboration

Work on the same document draft as your colleagues — how simultaneous edits merge, how quickly you see each other's work, and what happens when the connection drops.

Comments

Every record in Alchex — a document, a register, a risk — carries the same Comments panel; write a note, name a teammate, and it reaches them.

Submit and approve

How a draft moves from editing to published — requesting approval, who decides, the separation-of-duties rule, and what approve or reject does.

Publishing

How a draft becomes the version your readers see, who is allowed to publish, and what stays fixed afterwards.

Version history

Read a document's whole story in one list — published versions, saved versions and everything that happened to it — narrow it to the published versions alone, compare any two, and pull an old version back into the draft.

External documents

Bring a PDF you did not author into the governance record, and put it under the same versioning, review and access control as an authored document.

Templates and the marketplace

Browse ready-made document templates, each carrying its own processes and checks, and build or adopt a copy into one of your teams.

Exporting documents

Download an authored document as a Word copy with a generated document control section, or export a document's full activity log as CSV — both from the one Download every record carries.

Activity and archive

Read the audit log of everything that happened to a document, export it as CSV, and remove documents — Archive retires a record reversibly and keeps everything; Delete removes any record permanently and takes its history with it.

Registers

Keep the running logs your documents point at — exception logs, corrective actions, training records — as tables of records whose status says honestly whether they prove anything.

Connectors as references

A document points at a connected app the same way it cites a policy — by name, from the Connectors row, with a dot that says whether the app is answering.

Risk records

The register of risks and non-conformities — how a record is created, what its properties mean, how severity is worked out, and how the list reads.

Actions and activity

Break a record's treatment into steps that each have an owner, a date and their own thread — and read one running account of everything that happened to it.

AI review and assistance

How Ask Alchex answers from your own records and how every AI change leaves a receipt — with billed work and publishing kept on each record's own page.

Controls and evidence

How controls carry their own evidence, what the freshness states mean, and how a control is audited from its own procedure's workflow.

The compliance record

One page that says how ready you are — every clause of your standard, one verdict per clause, and a readiness number that reconciles against the rows below it.

Rating answers and data controls

Rate the assistant's answers, optionally share a conversation with Alchex, and govern all of it with one workspace switch that starts off.

Standards knowledge

What the assistant knows about your frameworks — the requirements, the implementation guidance behind them, and the regulations that apply in your jurisdiction — and how it keeps the three apart.

Workspaces

Creating a workspace, what its name controls, switching between workspaces, and what closing one actually does.

Roles and permissions

How Reader, Writer and Owner roles map to document actions, and why the person who submits a document can never approve it.

Members and invitations

Inviting people, what the invitation link is, why an invite can be refused, and the rules around removing someone.

Memory

What the assistant remembers about your organisation, each team and you — three pages of plain language it writes and you own.

Teams

Creating teams, managing who is on them, and the asymmetry in what deleting a team destroys and what it keeps.

Seats and licences

How a licence is consumed, why an invitation gets refused, and why removing someone only reduces your bill if you ask it to.

Connections

The connector catalog — what each connection reads, which ones need an admin account, how Okta's own-app setup works, and how Alchex shows a connection is actually working.

Your sign-ins and two-factor

Read the list of devices signed in to your account, sign one or all of them out, and turn on two-factor authentication.