2.2 Business areas, groups, tasks, and automations
Business areas organize work and resources. Groups support collaboration. Tasks track individual deliverables. Automations schedule recurring execution.
| Object | When to use it | Example |
|---|---|---|
| Business area | You need to share related reference material, colleagues, and connections | Content operations, market research, security operations |
| Group | You need discussion and handoffs among participants | A group preparing a product introduction |
| Conversation | You need to discuss a particular question | Asking a research colleague for the sources behind a finding |
| Task | You need an assignee, status, and result | Complete a research summary today |
| Automation | You need work to run on a schedule | Organize authorized reference material every weekday |
| Task template | You want to reuse input and delivery requirements | A research brief template |
How they work together
First, organize colleagues and reference material in a business area, then create a group for discussion. Create tasks for deliverables, and configure automations for work that should repeat. A task template is a reusable definition; it does not run on a schedule by itself.
A group provides collaboration context. It does not automatically expand any colleague's permissions. General work is for activities without a dedicated business area. What a colleague can use still depends on its own declarations, scope, and permissions.
The current limits of projects
A separate persistent project layer has not been fully delivered. For now, use business areas and dedicated groups to organize related work, and keep task titles and reference material names consistent. This naming convention does not create a project entity, project permissions, or a project archiving mechanism.