Key concepts
The handful of ideas that the rest of Task Arrow is built on — workspaces, records, templates, custom fields and services.
Workspaces
A workspace is an organisation's space in Task Arrow. Tasks, projects, lists, forms, workflows, settings and members all belong to one workspace, and nothing is shared between workspaces unless you use the Service Hub.
Your account is you. One account can belong to many workspaces: your own company's, a client's you were invited to, and so on. Each workspace has its own plan.
The four record types
| Record | Think of it as | Example |
|---|---|---|
| Task | One piece of work with an owner and a due date. Tasks can nest as subtasks. | Send the Q3 invoice |
| Project | A container for related tasks, with its own status and team. | Website relaunch |
| List | A table of structured entries, with columns you define. | Vendors, Equipment, Clients |
| Custom form | A set of questions whose answers are saved as entries. | Support request, New hire intake |
Each record type keeps a History of every change: who changed what, and when.
Standard records and templates
Every record type can also be a template: a blueprint you create real records from. Task and project templates can recur, so Task Arrow creates the next one for you on a schedule, such as every 1 month. Switch between your records and your templates with the view selector next to each page title. See Templates and recurring tasks.
Statuses, priorities and custom fields
Your workspace decides its own vocabulary in Settings:
- Statuses: the stages work moves through, like To do, In progress and Done. A status can be marked Closed, which is how Task Arrow knows work is finished. Tasks and projects have separate sets.
- Priorities: how urgent a task is, like Low, Medium and High.
- Custom fields: extra information on a record. There are 19 field types, from text and dates to people, files and links to other records.
Services
The Service Hub connects workspaces. A provider workspace bundles templates into a service, and a subscriber workspace subscribes to it. Subscribing creates the service's records in the subscriber's workspace, and the subscriber decides how much the provider can see and do there.