Answers, and a way to reach a person.

The questions that come up first, grouped by where they come up. If the answer is not here, every plan has a way through to somebody.

Talk to us Read the docs

Getting set up

An organisation, the units under it, the people in them, and then the first task. Most teams are running the same afternoon. The only decision that needs real thought is how you want work grouped into units, because that is the boundary everything else — the board, storage, analytics and permissions — is measured against.

Tasks are created with a brief, a unit, an owner and a credit amount, so moving live work in is a matter of re-briefing what is still open rather than importing an archive. Enterprise plans include onboarding and migration support; on the other plans it is a manual pass, which for most teams is one sitting.

The board, files and credits

The status of the tasks that are theirs, the comments addressed to them, and the files marked as deliverables. Credit costs, who the work is assigned to, internal review notes and every other client on the board stay with your team. It is the same task record, with the internal half withheld.

Roles, plans and support

Admins and project managers see the whole organisation. A supervisor sees their own unit and nothing from the ones next door. Writers see the work assigned to them, and HR sees attendance, leave and payroll without a line of sight into client work. An admin can adjust what each role is granted.

Base covers task boards and file attachments with 5 GB of storage. Standard adds the full ERP layer — attendance, leave and payroll — plus Gantt charts and the AI chatbot at 50 GB. Pro adds full MCP and automation access at 100 GB. Enterprise has no list price and is sized during onboarding.

Still stuck

Raise it from inside Clarix.

If you are already signed in, an issue raised in the product carries its own context — who raised it, in which unit, against which work — and reaches your admin before it reaches us.

It arrives with the context A priority, a status and the thread underneath it. Nobody has to reconstruct what you were doing when it went wrong.
Your admin sees it first Most of what gets raised is a permission or a setup question, and the person who can fix that is in your own organisation.
It has a state, not an inbox Open, in review, resolved or closed — so an issue is either being worked on or finished, never quietly lost in a mailbox.

Support by plan

Base Email support

Standard Priority email support

Pro Priority chat support

Enterprise Dedicated account manager

clarix.app/issues/214

ISS-214

Supervisor cannot see the Design board

Medium In review

Supervisor, Design 2h

I can open my own tasks but the unit board is empty. Everyone else in Design sees it.

Admin just now

You were on Content, not Design. Moved you across — reload and it should be there.

Reply… Resolve Send

Nothing here answering it?

Book twenty minutes and we will walk your setup rather than sending you a link to this page.

Get started Book a demo

Answers, and a way to reach a person.

Getting set up

How long does setting Clarix up take?

Do I have to design the board before I can use it?

Can I bring existing work across?

The board, files and credits

When is a credit actually charged?

Where do files live?

What can a client see?

What happens to a cancelled task?

Roles, plans and support

Who can see across units?

Which plan do I need?

Is there a limit on teams or units?

How do I reach a person?

Raise it from inside Clarix.

Supervisor cannot see the Design board

Nothing here answering it?