> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getkato.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Onboard a new client

> Connect a client's details, first project, and kickoff actions in one workspace.

export const DocImage = ({src, alt, caption, kind = "workspace", thumbnail = false, natural = false}) => {
  const paths = {
    objects: "m12 3 9 4.5v9L12 21l-9-4.5v-9L12 3Z M3 7.5l9 4.5 9-4.5 M12 12v9",
    attributes: "M4 5h16 M4 12h16 M4 19h16 M8 3v4 M16 10v4 M10 17v4",
    records: "M5 3h14v18H5z M8 7h8 M8 11h8 M8 15h5",
    relationships: "M8 8H4v8h4 M16 8h4v8h-4 M8 12h8 M10 10l-2 2 2 2 M14 10l2 2-2 2",
    views: "M3 4h18v16H3z M3 9h18 M9 9v11 M15 9v11",
    importing: "M12 3v12 M8 11l4 4 4-4 M4 16v5h16v-5",
    workspace: "M4 4h16v16H4z M4 9h16 M9 9v11",
    navigation: "m5 5 14 5-6 3-3 6-5-14Z",
    team: "M16 21v-2a4 4 0 0 0-4-4H6a4 4 0 0 0-4 4v2 M16 4a4 4 0 0 1 0 8 M22 21v-2a4 4 0 0 0-3-3.87 M13 7a4 4 0 1 1-8 0 4 4 0 0 1 8 0Z",
    tasks: "M9 6h11 M9 12h11 M9 18h11 M3 6l1 1 2-2 M3 12l1 1 2-2 M3 18l1 1 2-2",
    meetings: "M4 5h16v15H4z M4 10h16 M8 3v4 M16 3v4 M8 14h3 M8 17h6",
    ai: "m12 3 2.5 6.5L21 12l-6.5 2.5L12 21l-2.5-6.5L3 12l6.5-2.5L12 3Z",
    automation: "M9 3h6v6H9z M3 16h6v5H3z M15 16h6v5h-6z M12 9v4 M6 16v-3h12v3"
  };
  return <figure className={["kato-visual", thumbnail ? "kato-visual--thumbnail" : ""].filter(Boolean).join(" ")}>
    {src ? <div className={["kato-visual-frame", natural ? "kato-visual-frame--natural" : ""].filter(Boolean).join(" ")}>
        {thumbnail ? <img src={src} alt={alt || ""} loading="lazy" decoding="async" /> : <a className="kato-visual-fullsize" href={src} target="_blank" rel="noreferrer" aria-label={`Open full-size image: ${alt || caption || "Kato guide"}`}>
            <img src={src} alt={alt || ""} loading="lazy" decoding="async" />
          </a>}
      </div> : <div className="kato-visual-frame kato-placeholder" role={thumbnail ? undefined : "img"} aria-label={thumbnail ? undefined : `Image placeholder: ${alt || caption || "Kato workspace"}`} aria-hidden={thumbnail ? "true" : undefined}>
        <span className="kato-orbit kato-orbit--outer" />
        <span className="kato-orbit kato-orbit--inner" />
        <span className="kato-visual-icon"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" strokeWidth="1.4" strokeLinecap="round" strokeLinejoin="round" aria-hidden="true"><path d={paths[kind] || paths.workspace} /></svg></span>
        {!thumbnail && <span className="kato-placeholder-label">Image placeholder</span>}
      </div>}
    {caption && !thumbnail && <figcaption>{caption}{src && <span className="kato-visual-hint">Select the image to view it full size.</span>}</figcaption>}
  </figure>;
};

Use this recipe when a new engagement needs a shared home. You will create or
reuse a client record, connect its first project, and give the initial actions
clear owners.

**Before you start:** your workspace needs Clients and Projects objects, a
suitable record or relationship attribute between them, and access to create
records and tasks. Object names and required fields can differ by workspace.

<Steps>
  <Step title="Find or create the client">
    Search for the client first and inspect similar results. If no record
    represents the client, open **Clients**, select **New Client**, and fill
    in the name and required fields. Add confirmed website and contact details
    where your schema provides them.

    Keep unknown details empty until they are confirmed. Create one record for
    the client rather than a new client record for each engagement.
  </Step>

  <Step title="Give the engagement its own project">
    Open **Projects** and select **New Project**. Use a recognizable name such
    as **Relio website**. Add a short description of the engagement, the current
    status, and an agreed target date if one exists.

    A useful opening description is:

    > Prepare the Relio homepage brief. Confirm the audience, product benefits,
    > page sections, and call to action. Record open questions before drafting.
  </Step>

  <Step title="Connect the project to the client">
    On the project, use its **Client** attribute to select the existing client
    record. Open the linked record to check you selected the right one.

    If you need to configure this field, follow
    [Connect related records](/documentation/data/relationships). A paired
    Relationship can expose Projects on the client; a Record attribute should
    not be assumed to create that reciprocal field.

    <DocImage natural src="/images/introduction/relio-record.png" alt="Relio project details showing a Client attribute and a linked client record" caption="Use the project's client link to keep the connection explicit. The supplied Relio example links to Bobby Alv; select the correct client for your engagement." />
  </Step>

  <Step title="Create the first three actions">
    Open **Tasks → New Task** and create only the actions needed to start.
    Link each one to the project, choose assignees, and add completion criteria.

    | Action                               | Completion criteria                                                      |
    | ------------------------------------ | ------------------------------------------------------------------------ |
    | Confirm the kickoff agenda           | The questions and required decisions are written down.                   |
    | Collect the homepage source material | The current copy, brand assets, and available product images are linked. |
    | Agree on the brief reviewer          | The reviewer and review process are recorded in the project context.     |

    Set deadlines based on the engagement rather than copying dates from an example.
  </Step>

  <Step title="Review the engagement together">
    Open the project and its linked tasks. Confirm the client connection,
    immediate next action, and who is responsible. Add missing context before
    the kickoff so the meeting can focus on decisions.
  </Step>
</Steps>

## Check the result

There should be one recognizable client, one project for this engagement, and
linked kickoff tasks with clear owners. If the client already existed, confirm
you reused that record.

Next, [Prepare for a client meeting](/recipes/prepare-client-meeting).


## Related topics

- [Sync client records](/recipes/sync-client-records.md)
- [Get OAuth client metadata](/api-reference/oauth/client.md)
- [Introduction](/documentation/introduction.md)
- [Use Ask Kato](/documentation/use-ask-kato.md)
- [Choose what to track](/documentation/data/objects.md)