Core features

How a Kokar workspace is put together, what each part is for, and where to go next.

Kokar is one workspace for an agency's whole operation β€” every client, every project, the conversations about them, and the documents around them, in one place instead of four tools.

This page is the map. Each section is a part of the product, with what it is for and where to read more.

The hierarchy

Almost everything in Kokar sits somewhere in one structure, and understanding it is most of understanding Kokar.

Workspace β†’ Space β†’ Folder β†’ Project β†’ Task

  • Workspace β€” the organization at the top. It is what you pay for, and what people are invited into.
  • Space β€” a big division of the work. Most agencies use one space per client, or per department.
  • Folder β€” an optional grouping inside a space, for when one space has enough going on to need shelves. On Enterprise, a folder can hold subfolders one level deep.
  • Project β€” where tasks actually live. A project carries its own board of statuses, so "Design" and "Client Onboarding" can move through different stages.
  • Task β€” the unit of work: an assignee, dates, a priority, a status, subtasks, comments, files, checklists and tracked time.

You do not have to use every level. A small workspace can be spaces and projects, with no folders at all β€” and subfolders only exist on Enterprise, so most workspaces never meet them.

Each level has its own article: what it is for, how to create one, how to change it, and what happens when you archive or delete it.

Tasks

The centre of gravity. Beyond a title and an assignee, a task carries dates, priority, status, subtasks, checklists, tags, dependencies, comments, files, links to other tasks and docs, tracked time, and any custom fields you define for the project.

Each project has its own statuses, so the board matches how that work actually moves rather than a fixed to-do/doing/done.

Docs

Long-form writing lives in Docs: a tree of pages and sub-pages, written in a rich editor, with the same privacy model as the rest of the hierarchy. Docs can be linked to tasks, so the brief and the work that came out of it stay connected.

Chat

Conversations happen in Kokar rather than in a separate app β€” rooms for teams, direct messages for one-to-one, plus posts and calls.

Dashboards

Reporting built from cards β€” what is overdue, who logged what, estimated versus tracked time. A dashboard can cover the whole workspace or a single location, and each card respects the viewer's own permissions, so nobody sees numbers drawn from work they cannot open.

Teams

Groups of people you can address at once β€” assign a task to a team, or mention one in chat, instead of naming five individuals.

Time & attendance

Clock in and out with geofenced locations, request time off and have it approved, and track time against tasks. Available on paid plans.

AI

Kokar has AI throughout, and everyone gets a limited number of free uses each month. An AI seat removes that limit and adds the heavier capabilities.

Connect other tools

Kokar speaks MCP, so an AI app such as Claude can read and manage your workspace in plain language.

Plans and billing

What each plan includes is on the pricing page; how paying for it works is here.

Frequently asked questions

Where do my different clients or companies go?

Each one gets its own space inside a single organization. A space can be private, so the people working on one never see the others.

What is the difference between a folder and a project?

A project is where tasks live and has a board of statuses. A folder only groups projects together. If you want to put tasks in it, you want a project.

Do I have to use folders?

No. Folders are optional. A space can hold projects directly, and plenty of workspaces never create a single folder.

Can I hide a space or a project from some people?

Yes. A space, folder or project can be private, and a private one is invisible to anyone who is not a member of it.

Keep reading