How to use Alchex

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

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

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

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

How to reach us from inside Alchex, what we see when you write, and when to expect an answer.

The ways to start a document in Alchex — from scratch, from a conversation with the assistant, or by uploading a file you already have.

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

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

A control asks a document something on a schedule — add one from the library or write your own on the Controls page, and every run is a session you can open and reply to.

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

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.

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

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

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

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.

Organize the Library like a file drive — folders inside folders, one home for every record, a path to walk back up, and Move to… or a drag to file things.

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

Ask the assistant for a document and it designs it with you, then writes it in your team in one standard structure, its defaults marked in its rules.

Download an authored document as a Word copy or Markdown, or a file-backed document as its original file — all from the one Download every record carries.

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

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.

How Zapier, Make or n8n add and change register rows through an API key — creating the key, the four addresses, repeat-safe sending, the rate limit, the teams a key may work in, the switch that decides whether rows go in live, and where to see when a key last sent something.

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.

Link a project to a standard and read its plan on the project page — the phases in order, the documents each phase delivers, and which you already have.

How Ask Alchex answers from your own records and how every AI change leaves a receipt — and why publishing is yours, on the document's page.

How the assistant answers "do we actually have to?" — where the answer comes from, why it names a clause every time, and what it does when you tell it that it is wrong.

A control is a document of type Control. It is written, reviewed, published, cited and checked exactly like any other document.

One status per requirement of every standard you work to, from the newest check of it. Each requirement has its own page with the report its check wrote and every earlier check.

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

What the assistant knows about your frameworks — the requirements, the implementation guidance behind them, the regulations that apply in your jurisdiction, and the ways a business actually runs each process — and how it keeps them apart.

Let Claude, ChatGPT, Cursor or another AI assistant work in your Alchex workspace with your own sign-in, through the same tools Alchex's assistant uses.

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

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

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

How the assistant knows what it knows — your documents, the notes it keeps from earlier chats, and the conversation itself. There is nothing to fill in or keep up to date.

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

Your workspace has one subscription for a number of people you choose, and one credit balance that AI draws from; you change the number and add credit on the Billing page, confirmed on Autumn's page.

The connector catalog — what each connection reads, which ones need an admin account in the app, the one way every app connects, and how Alchex shows a connection is actually working.

Read the list of devices signed in to your account, sign one or all of them out, change your password, turn two-factor authentication on or off, and require it for a whole workspace.