Set up a Klaq workspace around the way your team works

A useful workspace connects the people, customer relationships, delivery work, and records your team actually needs. Start with a small complete workflow rather than filling every app with sample data you will not use.

The short version

Confirm the active workspace and your role. Add or find a customer, organize the sales conversation in CRM, create the delivery work in Tracker, and prepare billing in Invoice. Set up Time Off policies and assignments when your team needs leave management.

Know which workspace you are changing

Klaq scopes records and permissions to the selected workspace. When you belong to more than one, check the current workspace before creating a customer, project, document, or leave request.

A running timer is a special case worth noticing: it stays associated with the workspace where it started, even when you navigate elsewhere. Stop or inspect that timer rather than assuming navigation moved it.

Start with one real customer workflow

Search the shared customer directory before creating another record. Use CRM for the lead, contact, company, and deal context that describes the relationship.

Create a Tracker project for the agreed work and add a few concrete tasks. Use the customer relationship and project currency thoughtfully if the tracked work may later be imported into an invoice.

Then prepare the appropriate estimate or invoice in Invoice. The apps share context, but you still review each handoff. A won deal does not automatically issue a document.

Make team responsibilities explicit

Owners, administrators, and members have different actions available. Financial changes, time approval, and leave administration require the appropriate role.

Lead visibility and project visibility also have their own rules. Do not assume being a workspace member makes every record visible or editable.

For Time Off, configure the schedule, holidays, policies, and annual assignments before relying on the balances. An administrator requesting leave also needs an independent approver.

Check feature availability where you work

Some workflows, including approved-time invoice import, recurring invoices, shared time reports, and configurable rounding, require Pro. The interface and API enforce the applicable entitlement.

Use the current pricing information and workspace controls rather than relying on a fixed allowance copied from an old guide. Existing history and new creation permissions are different questions when the plan changes.

Common questions

Do I need to duplicate customers in every app?

No. CRM, Tracker, and Invoice use the shared customer directory within the workspace.

Does setup automatically send invoices or approve leave?

No. Sending, finalization, and approval are deliberate actions with their own permissions.

Begin with shared customers, then follow the client onboarding checklist.