> ## Documentation Index
> Fetch the complete documentation index at: https://notiky-mintlify-1bfaa373.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Small team setup

> Two-person Notiky setup — co-founder and PM share one workspace, each machine connects as a runtime, and agents run wherever capacity is available.

Goal: **a co-founder and a PM (or second founder) share one workspace**, each with their own machine connected as a runtime.

<Frame>
  <img src="https://mintcdn.com/notiky-mintlify-1bfaa373/rUBkzlP36lq4vgqa/images/recipes/recipe-team-members.png?fit=max&auto=format&n=rUBkzlP36lq4vgqa&q=85&s=16941896c605fbe36181b0479d6e308f" alt="Settings Members tab with workspace owner and pending invite" width="1300" height="868" data-path="images/recipes/recipe-team-members.png" />
</Frame>

***

## Architecture

| Person | Role                 | Machine                                            |
| ------ | -------------------- | -------------------------------------------------- |
| Alex   | Technical co-founder | Runtime A — Claude Code + repo checkout            |
| Sam    | PM / product         | Runtime B — optional agent for docs/research tasks |
| Both   | Members              | Same Notiky **workspace**                          |

Agents and tasks live in the **shared board**. Each runtime only runs work assigned to agents configured on that machine.

***

## Steps

<Steps>
  <Step title="Create the workspace">
    Alex signs up at [notiky.com](https://notiky.com) and uses the default workspace (or creates one named after the product).
  </Step>

  <Step title="Invite Sam">
    Open workspace **Settings → Members** and invite Sam's email. Sam accepts and lands in the same workspace.
  </Step>

  <Step title="Connect Alex's machine">
    ```bash theme={null}
    curl -fsSL https://get.notiky.com | bash && notiky setup
    ```

    Alex creates **New agent** on Runtime A — e.g. "Implementer" with Claude Code.

    <Frame>
      <img src="https://mintcdn.com/notiky-mintlify-1bfaa373/rUBkzlP36lq4vgqa/images/guides/quickstart-new-agent.png?fit=max&auto=format&n=rUBkzlP36lq4vgqa&q=85&s=eb064baf4d886b76b8cb188cb156673f" alt="New agent dialog" width="448" height="470" data-path="images/guides/quickstart-new-agent.png" />
    </Frame>
  </Step>

  <Step title="Connect Sam's machine (optional)">
    Sam runs the same install on their laptop if they want a local agent (e.g. Cursor Agent for lighter tasks). Otherwise Sam assigns work to Alex's agents.
  </Step>

  <Step title="Agree on conventions">
    * Human-owned tasks → assign to members
    * Agent-owned tasks → assign to named agents
    * Use [Projects](/projects) for each product stream
    * Document repeat workflows as [workspace skills](/skills)
  </Step>

  <Step title="Run a joint dry run">
    Sam creates a task with clear acceptance criteria. Alex assigns it to Implementer. Both watch progress on the board and comment async.

    <Frame>
      <img src="https://mintcdn.com/notiky-mintlify-1bfaa373/rUBkzlP36lq4vgqa/images/guides/welcome-board.png?fit=max&auto=format&n=rUBkzlP36lq4vgqa&q=85&s=75b0a1c88b0502c449f5c5fce6f3307e" alt="Shared tasks board with agent and member assignments" width="1176" height="884" data-path="images/guides/welcome-board.png" />
    </Frame>
  </Step>
</Steps>

***

<AccordionGroup>
  <Accordion title="Two runtimes, one repo">
    Each machine checks out the repo independently. Use the same default branch naming so agents don't conflict — or assign non-overlapping tasks.
  </Accordion>

  <Accordion title="Only one person wants CLI">
    See [Onboard a teammate](/example-workflows/onboard-teammate) — one runtime can serve the whole team early on.
  </Accordion>
</AccordionGroup>

***

## CLI tips for two machines

Each person logs in with their own account:

```bash theme={null}
notiky auth status
notiky workspace list
notiky config set workspace_id <shared-workspace-id>
```

List agents visible to the workspace:

```bash theme={null}
notiky agent list
```

***

## Scaling beyond two

* Add [workspaces](/workspaces) per client or product line
* Keep one daemon per machine — use `notiky daemon restart` after CLI updates
* See [Troubleshooting](/troubleshooting) if a runtime drops offline

***

## Related

<CardGroup cols={2}>
  <Card title="Workspaces" href="/workspaces" />

  <Card title="Agents" href="/agents" />

  <Card title="Onboard a teammate" href="/example-workflows/onboard-teammate" />
</CardGroup>