Use this guide to get a new workspace into a usable state: members can enter, tasks have a source of truth, integrations are connected, and operators know where settings live.
Prerequisites
- A Cogno account.
- Permission to create or manage a workspace.
- The source material you want Cogno to work with: tasks, issues, meetings, documents, or connected apps.
First setup path
- Sign in to the Cogno app.
- Create a workspace, or open the workspace selector and choose an existing workspace.
- Open Settings > Members and invite the people who should work in the workspace.
- Add tasks manually in Tasks, or import an existing task CSV from Settings > General > Task import.
- Open Integrations and connect the services Cogno should use as workspace context.
- Open Settings > Memory and add the stable workspace facts Cogno should remember.
- For local workers, open Settings > API Keys, create a key, then run the CLI worker.
Workspace basics
Cogno work happens inside a workspace. The main app navigation contains:
| Area | Use it for |
|---|---|
| Tasks | Current work, imported tasks, saved views, status changes, assignees, due dates, and project links. |
| Inbox | Unread task comments and mentions. |
| Meetings | Meeting records and Google Calendar notetaker activity. |
| Projects | Project-level task organization. |
| Integrations | GitHub, Slack, Notion, Google Calendar, Discord, Microsoft Teams, and upcoming source apps. |
| Settings | Workspace identity, members, memory, API keys, workers, activity, import, and deletion controls. |
Add tasks
Choose one source of truth before inviting the whole team.
| Situation | Recommended action |
|---|---|
| You are starting fresh | Create a small set of tasks manually in Tasks. |
| You are moving from another task system | Export a task CSV and import it from Settings > General > Task import. |
| You need original context preserved | Keep source URLs, issue keys, labels, milestones, and custom fields as import metadata. |
| You want teammate ownership to survive import | Invite members first, then map source assignees during import. |
Task CSV import supports Linear, Notion databases, GitHub Issues through GitHub CLI, Asana projects, and Jira Cloud exports. See Import task CSVs into Cogno.
Invite members
Open Settings > Members.
| Action | Result |
|---|---|
| Invite | Opens member invite options. |
| Copy invite link | Creates a link that can be shared with teammates. |
| Add existing members | Adds people already known from your other workspaces. |
| Edit | Lets owners remove eligible non-owner members. |
Add members before importing task CSVs when the CSV contains assignees or collaborators.
Connect integrations
Open Integrations, then connect the apps that match the workspace.
| Integration | Use it for |
|---|---|
| GitHub | Pull request, commit, and issue workflows. |
| Slack | Workspace conversations and task creation from messages. |
| Notion | Pages and database context. |
| Google Calendar | Per-user calendar connection for Google Meet notetaker activity. |
| Discord | Server, channel, and message context. |
| Microsoft Teams | Team communication workflows when enabled. |
Each member connects their own Google Calendar account. A workspace can show multiple connected members.
Add memory
Open Settings > Memory and write the stable context Cogno should read when it wakes:
- What the workspace is building.
- Product areas and owners.
- Current operating priorities.
- Links or naming conventions that should be treated as canonical.
- Rules that should stay true across tasks and meetings.
Keep Memory short enough to maintain. Use Markdown headings and lists.
Set up workers
Cogno workers let local or external worker daemons authenticate without a browser session.
- Open Settings > API Keys.
- Create a key.
- Copy the raw key immediately.
- Run:
cogno login --token <key>
cogno
Open Settings > Workers to confirm liveness and recent agent work. A worker that stops reporting within two minutes becomes stale, then offline.
Setup checklist
Use this checklist before depending on the workspace for daily work.
| Check | Done when |
|---|---|
| Workspace identity | Name and icon are recognizable. |
| Members | Everyone who needs access can enter the workspace. |
| Tasks | Current work exists in Cogno, either manual or imported. |
| Source traceability | Imported tasks keep source URLs or external IDs. |
| Integrations | Required apps show the expected connection state. |
| Memory | Workspace facts are short, current, and readable. |
| Workers | Local worker setup appears in Settings > Workers when needed. |
LLM handoff
When asking an assistant to help finish setup, provide:
- Workspace name.
- Member roles or teammate list.
- Source apps that should be connected.
- Task source: manual entry or CSV import.
- Any worker or API key requirement.
Use Copy for LLM to pass this setup path with the related Cogno terms intact.