}
{caption && !thumbnail && {caption}{src && Select the image to view it full size.}}
;
};
Kato brings your team's tasks, meetings, and business records into a shared
workspace. The useful part is the connection between them: you can understand
who a piece of work is for, why it exists, and what needs to happen next.
This guide follows a website project for **Relio**. The screenshots use example
workspaces and project data; use your own workspace, people, and dates as you follow along.
By the end, you should know where to put your information and how to start a
first workflow without configuring the whole product.
## What goes where?
| In Kato | Use it for | Relio example |
| ------------- | ----------------------------------------------------------- | ------------------------------------- |
| **Workspace** | The shared home for your team's data, members, and settings | Your agency's workspace |
| **Object** | A collection of one kind of business information | Clients or Projects |
| **Record** | One item within an object | Relio or Relio website |
| **Attribute** | A detail stored on each record | Project status or target date |
| **Task** | A specific action to finish | Send the revised homepage brief |
| **Meeting** | The agenda and context for a conversation | Relio kickoff |
| **View** | A way to focus on a set of records | Active projects sorted by target date |
A project record describes the project. A task describes an action within that
work. Keeping those separate means the project can stay useful after any one
task is complete. [The data guide](/documentation/data/how-data-connects)
explains objects, records, and attributes in more detail.
## Walk through a first piece of work
Select the workspace name at the top of the sidebar to open the workspace
menu. The checkmark identifies the selected workspace. If your team already uses Kato,
join that workspace so you can work with its existing information. If you
are setting up a new team, [create a workspace](/documentation/create-your-workspace).
Open the appropriate object under **Objects**. Look for the client or
project before creating another record. For this example, open **Projects**
and select **Relio**. Review its attributes on the left and its activity in
**Overview**. The **Tasks** tab contains the work linked to this project.
Open **Tasks** and create **Send the revised homepage brief**. Choose the
assignees, a current status, and a due date if there is a real deadline.
Add the acceptance criteria to the description: what should be sent, to
whom, and what makes the brief ready. Link the relevant record for context.
Open it again and check that someone who missed the kickoff could tell
what to do. A clear title, the related record, and a short description are
more useful than a task named “Follow up.”
**You are ready to continue when:** you can find the task, identify who is
working on it, and open the record that explains the surrounding work.
## Bring meetings into the workflow
For the next client call, put the questions to resolve in the meeting agenda.
After the call, distinguish **decisions** from **actions**. “Use the revised
homepage direction” is a decision. “Send the revised brief” is an action and
belongs in a task.
Connecting a calendar helps bring scheduled events into Kato. It does not
replace the need to review the meeting and give follow-up work a clear owner.
Use [Meetings and follow-ups](/documentation/meetings-and-follow-ups) for a
complete before-and-after example.
## Where Ask Kato and automations help
**Ask Kato** helps you work with available context: ask a focused question,
summarize an item, or draft an update. Start with a named record or task and
check the result against the underlying information.
**Automations** apply a configured workflow when a trigger occurs. They are
useful once you understand the repetitive step you want to handle. Start with
one trigger and one action, then inspect the results before adding more steps.
Neither feature fixes missing project details on its own. Accurate records and
clear tasks give both your teammates and Kato better context to work with.
## Common first-day questions
No. Start with the objects already available and one real piece of work.
Add an attribute when you can explain what it stores and who will keep it
current. Use a view when you just need to see a subset of existing records.
Object names and attributes are configurable. Sidebar preferences, your
role, enabled apps, and feature availability can also change what appears.
Follow the purpose of each step and use your workspace's actual labels.
Use a client record when the same team needs to manage clients together.
Consider a separate workspace when membership and administration need to
be separate. A new workspace creates another place to manage, so do not
create one simply to categorize a client.
## Up next
Learn where work lives and how to find it again.Choose your workspace details and invite your team.
: