Clients

Clients are the people and organizations you do work for. Most other things in Ceum — projects, invoices, transactions, documents — can be linked to a client. A client record also tracks pipeline information (estimated value, probability, source) and a follow-up schedule driven by its status.

What you can do

Browse all your clients on the Clients page, where columns are sortable and filterable and rows are highlighted by follow-up urgency — yellow as a follow-up approaches (within 3 days) or when none is scheduled, red once it's overdue. Create a new client using a two-column form — contact info on the left, internal info on the right — and add projects inline as you go. Open a client to see its full contact info, status with follow-up urgency, the inline list of its projects, and its related documents. From there you can edit any field or open its full edit history.

Each client gets an ID like C-7, which sorts numerically so C-10 comes after C-9 rather than next to C-1.

Fields you fill in

Contact section:

• Name — required, unique per workspace (max 255 characters).
• Company — optional (max 255 characters).
• Email — optional; validated as an email when provided.
• Website — optional; you can type a bare domain and https:// is added if missing (max 2048 characters).
• Phone — optional (max 50 characters).
• Address — optional, multi-line (max 1000 characters).

Internal section:

• Status — required; one of your Custom statuses. A status can be set up to require follow-up after a number of days.
• Next follow-up date — filled in automatically when you pick a status that requires action, but you can edit it.
• Estimated value — optional currency amount (0 or more).
• Probability — optional: HIGH, MEDIUM, or LOW.
• Source — optional free text (e.g. "Referral", "Conference").
• Tags — optional, see Tags.
• Notes — optional, multi-line (max 10,000 characters).
• Last contact date — editable; not set automatically.

Workflows

Create a client

1. Open the new client form.
2. Fill in the contact section. Only the name is required.
3. Pick a status. If the status requires action, the follow-up date is set for you; override it if you have a specific date in mind.
4. Optionally add projects inline at the bottom of the form (name, dates, status).
5. Save. The new client appears at the bottom of the list with the next ID.

Update a client

1. From the list or detail page, use Edit.
2. Any change is captured in the Entity changelog.
3. If you try to leave the page with unsaved changes, the form prompts you before navigating away.

Delete a client

Use the Delete button on the client's detail page or its edit page. You'll be asked to confirm; deletion is permanent (see Tips and edge cases for what happens to linked records).

Track follow-ups

When you pick a status that requires action, the client is highlighted by how urgent its follow-up is: yellow as the date approaches (within 3 days) or while no date is scheduled yet, and red once it's overdue. The same coloring shows in the list, on the Alerts page, in the alert bell, and on the detail page, so they always agree. A status can also be set to suppress this entirely — useful for terminal states like "Lost" where overdue dates shouldn't generate noise. You can also hide the client alert from the bell, dropdown, and sidebar by turning off the Clients category (or all alerts) in Alerts settings; the list-row highlight and the follow-up date itself stay put regardless.

Status workflow

Client statuses are configured under Client statuses and are fully customizable. Beyond name, color, and order, each status carries three settings relevant to clients:

• Requires action — sets the follow-up date automatically when this status is picked.
• Action days — how many days from today to use for that follow-up date.
• Action suppression — silences the highlight and alert even when the follow-up date passes.

Changing a status records when the change happened. Clients with an approaching, overdue, or unscheduled follow-up also surface in Alerts.

Import and export

• Import — bring clients in from a CSV file on the Clients import page. Supported columns include name, company, email, website, phone, address, status (by name), next follow-up date, estimated value, probability, source, tags (comma-separated), and notes. Names must be unique per workspace; see Import CSV.
• Export — pick columns and a format (CSV or JSON) on the Clients exports page. Exports are prepared in the background and download from the exports list once ready. See Export data.
• Bulk edit is not available for clients — edit them individually, or use import to apply bulk changes by name.

Related entities

• Projects — added or linked directly from a client's detail page, and reorderable within the client. A project can belong to several clients at once, so the same project may appear on more than one client's page, each with its own position in that client's list.
• Invoices and Transactions — both can reference a client. Deleting a client leaves those records in place but removes their link to that client.
• Documents — a client's related documents appear on its detail page; full management lives in Documents.

Privacy

When Privacy mode is on, personal fields (email, website, phone, address) appear masked in both the detail view and the edit form.

Tips and edge cases

• Deletion is permanent. Deleting a client removes it for good. Related projects, invoices, transactions, and documents keep their history but lose their link to that client — there's no trash bin. A project shared with other clients stays linked to those; a project left with no clients simply becomes floating.
• Unique names per workspace. Trying to create a second client with the same name fails validation.
• IDs sort numerically, so C-10 correctly sorts after C-9 instead of next to C-1.
• Inline project edits are saved together with the client form. Drag the handles to reorder a client's projects.

On mobile

• Create and edit clients in a native bottom-sheet form with native pickers; list rows respect compact density, and edits made offline are queued and sent on reconnect — see Offline support.