Building your workspace

Before your team logs a single entry, someone decides where entries are filed, what each form asks, and what happens once an entry exists. These guides are for that person: the administrator who shapes the directory, the forms, the lifecycles, the reports and the automations the rest of your team works inside.

What you can build

If you are setting up from scratch, start with the tree and its forms, because lifecycles, reports and automations all work on the entries those two produce. If you are changing one part of an existing setup, go straight to the guide you need.

Shape the directory that holds your data:

• Designing your tree — choose levels that match how your organisation divides up its work.
• Logs and registers — decide whether you are keeping a running account of events or a list of the things you look after.
• Categories — name and colour each level of the tree.

Design what your team fills in:

• Building input forms — add fields, put them in order and save the form for your team.
• Conditional questions — show follow-up questions only when an earlier answer calls for them.
• Field types — pick the right type for each answer you want back.
• Contract schemas — typed sets of fields that describe the data passing between the steps of an automation.
• Building forms with the assistant — describe the form you need and review the draft before you save it.

Model how work moves through your process:

• Designing a lifecycle — the states, actions and transitions that match how your team works.
• Attaching lifecycles automatically — give each matching entry its lifecycle as it is logged, without anyone choosing it.

Turn your entries into documents:

• Report templates — make a report template, preview it on paper and set its page.
• Drafting templates with the assistant — describe the report you need and refine the draft in conversation.
• Report inputs — the details a report asks for each time it is made.
• Previewing and generating — check a report on its pages, then have an automation make it.
• Browsing generated reports — find, open and download past reports.
• Report schedules — send the right report to the right inbox, on time.

Let routine work run on its own:

• Building an automation — the flow graph editor, where you place steps, connect them and switch the automation on.
• The building blocks — the sources, transforms, commands and control steps you connect together.
• Triggers and schedules — run on an event, on a timer, or at the press of a button.
• Run history — see every run, what it produced, and where one went wrong.

Show your team where things stand:

• Building shared dashboards — compose the organisation dashboard your team opens to see the latest figures.