Clarix

Documentation

Everything Clarix does, written down.

Six areas, in the order you meet them. Open any topic to read it here; the link at the foot of each card goes to the fuller overview of that area.

Get started Book a demo

Contents

Getting started
- Create your organisation
- Add units
- Add people and set roles
- Brief your first task
The board
- Statuses and what each means
- Board view and table view
- Filter and sort
- The task detail
- The activity log
Files
- Attach a file to a task
- Deliverables and working files
- Download everything on a task
- Storage per unit
Credits
- Set a task's credit amount
- When credits count
- Reading the credit report
- Exporting a period
People and roles
- The five roles
- Permissions per role
- Attendance
- Leave types and approvals
- Payroll records
Automation
- AXOKAI and the task record
- Chatbot
- Scheduled tasks
- MCP and plugins
- Calendar

Getting started

Standing an organisation up: the account, the units under it, the people in them, and the first task through the board.

Create your organisation

There is no self-serve sign-up, which is why every button on this site says log in rather than register. An organisation is created for you during onboarding together with its first admin account, and that account is the one that sets up everything below. Everyone else is added from inside the product.

Add units

A unit is a team, and it is the boundary the board, storage and analytics are all measured against — so it is worth deciding before you add people.

1 Open the Units screen from the admin area.
2 Create one unit per team you want kept apart — usually a craft such as Content or Design, or a client-facing group.
3 How many units a plan allows rises with the tier, so check the ceiling on the pricing page before you design a structure around a count.

Add people and set roles

An admin creates each account directly. There is no invitation email to chase and nothing for the new person to accept.

1 Open the Users screen and create the account with a name, a username or email address, and a password.
2 Choose the role: admin, PM, supervisor, HR or writer.
3 Assign the unit. A supervisor and a writer both see the board through it, so this is the field that decides what they can reach.

Brief your first task

A task carries everything the work needs: what it is, who owns it, when it is due and what it costs.

1 From the Tasks screen, choose New task.
2 Give it a title, a task code and a task type.
3 Set the unit and the project manager, then the priority and the deadline.
4 Set the credit amount. Once the task exists, only an admin can change this.
5 Save. The task lands in Pending, and the activity log starts recording from that moment.

Help Center

The board

The six statuses work moves through, the two ways of looking at them, and what the task record holds once it is open.

Statuses and what each means

A task sits in exactly one of six statuses: Pending, On hold, In progress, Sent for review, Completed and Cancelled. Five of them move work forward. Cancelled takes it off the board without deleting the record, and contributes nothing to any credit figure. A task counts toward credits when — and only when — it reaches Completed.

Board view and table view

The same tasks, two ways round. The table is the default and sorts by any column; the board is the drag-and-drop kanban, where moving a card between columns is what changes its status. Your choice is remembered for the session, so you come back to the view you left.

Filter and sort

Narrow the list by search, status, priority, unit or task type, and sort the table by any column in either direction. Changing a filter takes you back to the first page, so a narrowed view never strands you on page four of the result you were looking at before.

The task detail

Opening a task puts everything attached to it on one screen: the brief and its important notes, the unit and project manager, the priority, deadline and credit amount, the writers assigned to it, the notes thread, the files, and the activity log underneath all of it.

The activity log

Changes are recorded by observers on the model rather than by the screen that made them, so every route into an action is covered — the interface, a background job and the API all leave the same trail. Entries are appended and never edited. Writers are referred to by role rather than by name, so the log cannot be read as a report on one person.

Task Boards

Files

Attaching work to the task that asked for it, telling deliverables from drafts, and where the plan's storage ceiling is measured.

Attach a file to a task

Files are uploaded onto the task they belong to rather than into a folder tree. Each one records who added it, when, its size and its type, and the unit's storage total is updated by the same observer that writes the file — so the number cannot drift away from what is actually stored.

Deliverables and working files

Every file on a task is either a working attachment or a completed file. That flag is the line between the deliverable a client should receive and the briefs, references and drafts that got you there, and the two can be listed and downloaded separately.

Download everything on a task

Rather than pulling files down one at a time, a task can be taken whole: every file on it, streamed out as a single archive. There is a second download that takes only the completed files, which is the one to reach for when you are sending work to a client.

Storage per unit

Usage is tracked per unit and totalled for the organisation, and it is kept current as files arrive and leave rather than recalculated on a schedule. Admins get the breakdown by unit, which is what turns the plan's ceiling into a trend you can see coming instead of an upload that suddenly fails.

File Management

Credits

What a credit is, when it counts, and how a period of completed work becomes an export with one row per task.

Set a task's credit amount

The credit amount is set when the task is briefed and travels with it from there. Only an admin can change it afterwards, which is what stops the agreed cost of a piece of work drifting quietly while it is in flight.

When credits count

Credits are counted from completed work. A task contributes its amount once it reaches Completed and is stamped with a completion date; anything still moving, and anything cancelled, contributes nothing at all. That is why a month's figure only changes when something actually ships.

Reading the credit report

The credit list is a report over completed tasks for a period. Filter it by date range, unit, project manager or task type, and read it two ways: grouped, which subtotals by unit, or unified, which is one flat list across the whole organisation.

Exporting a period

Whatever you have filtered to can be exported. The grouped export carries a header and a subtotal for each unit and then a grand total; the unified export is a single table ending in the same grand total. Both give one row per task, so a client question about a line is answerable in seconds.

Credits & Billing

People and roles

Who can see what, how the unit boundary is enforced, and the attendance, leave and payroll records held against the same people.

The five roles

Admin, project manager, supervisor, writer and HR. An admin sees the whole organisation. A PM runs delivery across units. A supervisor is scoped to their own unit and sees nothing from the ones beside it. A writer sees the work assigned to them. HR sees attendance, leave and payroll without a line of sight into client work. There is a sixth role, superadmin, but it is ours rather than yours: it is how organisations are created and suspended.

Permissions per role

Roles are not a fixed set of hard-coded grants. Each one holds a set of permissions that an admin can widen or narrow from the authorization panel, so what ships is a sensible starting point rather than a ceiling you have to live with.

Attendance

Attendance is recorded per person per day, with a status and an optional note, and can be entered or corrected for any chosen date. Rolled up by unit, it turns "who is actually around this week" into a number rather than a guess.

Leave types and approvals

An admin defines the leave types the organisation uses, each with a default annual allowance, and people request leave against one of them. Balances are derived from the requests rather than kept in a column of their own — there is no stored figure that can quietly go wrong, because it is recomputed from what actually happened.

Payroll records

Payroll is held per person per month: a base amount, deductions and a note. A record is drafted and then finalised as a separate, deliberate step, and everyone can see their own payroll without being able to see anybody else's.

For Agencies

Automation

The AI surfaces inside the product — what the agent reads, what it acts on, and which plan each one arrives with.

AXOKAI and the task record

AXOKAI is the agent Clarix runs against your client work, and it has its own product site. Inside Clarix it works from the task record rather than from a prompt you have to assemble — the brief, the notes thread, the files and the completion history are what it reads.

Draft. This one is written from the shape of the feature rather than checked against the screen, so treat it as an outline until it loses this note.

Chatbot

Ask about your work in plain language and get an answer drawn from your own tasks rather than from a general model guessing at your business. The assistant carries an effort setting, with a balanced default that suits most questions and room to trade speed for depth when one deserves it.

Scheduled tasks

Recurring work that creates itself — the monthly report, the weekly batch — set up once against a trigger and then briefed and costed the way a manual task is.

Draft. This one is written from the shape of the feature rather than checked against the screen, so treat it as an outline until it loses this note.

MCP and plugins

A catalogue of connections into the tools the work already lives in, grouped by category. Full automation access is a Pro feature; the plans below that carry the chatbot without it.

Draft. This one is written from the shape of the feature rather than checked against the screen, so treat it as an outline until it loses this note.

Calendar

Deadlines, scheduled runs and delivery dates on one timeline, so a week that is already full looks full before you promise anything else into it.

Draft. This one is written from the shape of the feature rather than checked against the screen, so treat it as an outline until it loses this note.

AI Automation

How it is written

Short answers, and the screen beside them.

Each topic is written against the screen it describes, in the same language the interface uses. If the app calls a column Sent for review, so does the page about it.

Named the way the product is Units, credits, statuses and roles are the terms the app uses. There is no second vocabulary to learn before the documentation becomes useful.
One question per topic A topic answers a single thing — when a credit counts, how a supervisor's view is scoped — so the answer is the first sentence rather than the ninth paragraph.
Drafts say so A topic that has not been checked line by line against the product carries a note saying exactly that. We would rather flag an outline than let it pass as documentation.

clarix.app/docs/the-board/statuses

Getting started The board Files Credits People Automation

The board

Statuses

A task sits in exactly one status. Five of them move work forward; the sixth takes it off the board without deleting the record.

Pending

In progress

Sent for review

Completed

Note

A task counts toward credits once it reaches Completed.

Read it, or just open the board.

Most of Clarix explains itself once a real task is moving through it. The documentation is there for the parts that don't.

Get started Book a demo