What goes where?
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
explains objects, records, and attributes in more detail.
Walk through a first piece of work
1
Choose a workspace
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.
2
Find the relevant record
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.
3
Create one actionable task
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.
4
Make the task easy to pick up
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.”
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 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
Do I need to create all my objects and attributes first?
Do I need to create all my objects and attributes first?
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.
Why does my workspace look different from the examples?
Why does my workspace look different from the examples?
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.
Should each client have a separate workspace?
Should each client have a separate workspace?
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
Find your way around
Learn where work lives and how to find it again.
Set up your workspace
Choose your workspace details and invite your team.