> ## Documentation Index
> Fetch the complete documentation index at: https://hmm.heyhyper.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Onboard Your Team to Hyper Shared Memory

> Create a Hyper workspace, invite your team, and set up shared knowledge files so your AI tools remember everything your team learns.

Hyper's shared memory layer is most powerful when your whole team is connected to the same workspace. When everyone's AI tools draw from the same pool of memories — architecture decisions, coding conventions, resolved bugs, project goals — you stop re-explaining context and start compounding knowledge. This guide walks you through creating a workspace, inviting members, and getting everyone set up for day one.

***

## Step 1: Create Your Workspace

Your workspace is the shared memory container for your team. One person (the admin) creates it during the Hyper desktop app's onboarding flow.

<Steps>
  <Step title="Download and open the Hyper desktop app">
    If you haven't installed Hyper yet, download the desktop app from [gethyper.space](https://gethyper.space) and launch it.
  </Step>

  <Step title="Sign in with Google">
    Authenticate with your Google account. This becomes your Hyper identity across all AI tools.
  </Step>

  <Step title="Create a workspace">
    During onboarding, choose **Create a new workspace** when prompted. Give it a name that reflects your team or project — for example, `acme-eng` or `product-team`.
  </Step>

  <Step title="Complete setup">
    Hyper will initialize your workspace with a default structure. You're now the **admin** of this workspace.
  </Step>
</Steps>

<Note>
  The person who creates the workspace becomes the admin and has full control over members, integrations, and settings. Choose someone who will actively manage the workspace long-term.
</Note>

***

## Step 2: Invite Team Members

Once your workspace exists, generate an invite link to share with your team.

<Steps>
  <Step title="Open Workspace Settings">
    In the Hyper desktop app, go to **Settings → Workspace**.
  </Step>

  <Step title="Generate an invite link">
    Click **Invite**. Hyper generates a unique `join_token` and wraps it into a shareable link.
  </Step>

  <Step title="Share the link">
    Send the link to teammates via Slack, email, or any channel your team uses. Each link is tied to your workspace and can be reused for multiple people.
  </Step>
</Steps>

<Warning>
  Invite links contain a `join_token` that grants access to your workspace. Treat them like a password — share only with people you intend to add and rotate the link if it's accidentally exposed.
</Warning>

***

## Step 3: Join a Workspace

Team members can join in two ways — through the desktop app UI, or directly via their AI agent if they already have Hyper connected.

<Tabs>
  <Tab title="Via Desktop App">
    <Steps>
      <Step title="Open the Hyper desktop app">
        Download and install the desktop app if needed, then launch it.
      </Step>

      <Step title="Sign in with Google">
        Authenticate with your Google account.
      </Step>

      <Step title="Join the workspace">
        When prompted during onboarding, choose **Join a workspace**. Paste the invite link (or the raw `join_token`) that the admin sent you and confirm.
      </Step>

      <Step title="Connect your AI tools">
        Once you've joined, follow the [Claude setup guide](/guides/claude-setup) or [Cursor setup guide](/guides/cursor-setup) to connect Hyper to your AI tools.
      </Step>
    </Steps>
  </Tab>

  <Tab title="Via AI Agent">
    If you already have Hyper connected to Claude, Cursor, or another tool, you can join directly without touching the desktop app.

    Ask your AI agent to run the following:

    ```text theme={null}
    connect(join_token="paste-token-here")
    ```

    Replace `paste-token-here` with the `join_token` from the invite link. Hyper will add you to the workspace and load its context immediately.

    <Tip>
      This approach is ideal for developers who prefer staying in their editor. The token is a one-time join credential — once you're in the workspace, subsequent `connect()` calls (without a token) will pick up the workspace automatically.
    </Tip>
  </Tab>
</Tabs>

***

## Step 4: Set Up Team Integrations

After everyone has joined, connect the tools your team already uses so Hyper can pull context from them automatically.

<Steps>
  <Step title="Open Connections settings">
    In the Hyper desktop app, go to **Settings → Connections**.
  </Step>

  <Step title="Connect your integrations">
    Add the services your team relies on — for example, GitHub, Linear, Notion, or Slack. Each integration allows Hyper to observe and remember context from that source.
  </Step>

  <Step title="Encourage each member to connect">
    Integrations are per-user. Ask every team member to visit **Settings → Connections** after joining and connect their own accounts.
  </Step>
</Steps>

<Note>
  Workspace admins can see which integrations members have connected, but they cannot access the underlying credentials. Each member authorizes their own services independently.
</Note>

***

## Step 5: Recommended First Steps After Everyone Is Set Up

The shared workspace becomes genuinely powerful once you seed it with the foundational context your team returns to again and again. We recommend creating three files in your workspace's `org/` folder during your first team session.

<CardGroup cols={2}>
  <Card title="org/identity.md" icon="id-card" href="/guides/team-onboarding#sample-orgidentitymd">
    Describe who your team is: your mission, tech stack, team structure, and the conventions your AI tools should always respect. This file loads every time someone calls `connect`.
  </Card>

  <Card title="org/decisions.md" icon="gavel" href="/guides/team-onboarding#sample-orgidentitymd">
    A running log of significant architectural and product decisions — what you chose, what you rejected, and why. Prevents relitigating the same debates.
  </Card>

  <Card title="org/goals.md" icon="bullseye" href="/guides/team-onboarding#sample-orgidentitymd">
    Your current sprint goals, quarterly OKRs, or product roadmap. Gives AI tools the "why" behind requests, leading to more relevant suggestions.
  </Card>

  <Card title="Regular review" icon="calendar" href="/guides/team-onboarding#roles-at-a-glance">
    Schedule a short monthly review to keep these files current. Stale context is worse than no context — AI tools will confidently surface outdated information.
  </Card>
</CardGroup>

### Sample `org/identity.md`

Here's a starting template you can paste into your workspace and customize:

```markdown org/identity.md theme={null}
# Team Identity

## Who We Are
[Your team name] builds [product description] for [target users].

## Tech Stack
- Backend: [e.g., Python / FastAPI]
- Frontend: [e.g., React / TypeScript]
- Infrastructure: [e.g., AWS / Terraform]
- Primary language: [e.g., English]

## Conventions
- All PRs require two approvals before merge
- We prefer explicit error handling over silent failures
- API endpoints follow REST conventions unless documented otherwise

## Team Members
- [Name] — [Role]
- [Name] — [Role]
```

<Tip>
  Have each team member add a personal section to `org/identity.md` describing their role and areas of ownership. When someone asks the AI a question, it can route context to the right person or surface memories from the right part of the codebase.
</Tip>

***

## Roles at a Glance

| Role       | Capabilities                                                                                                                          |
| ---------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| **Admin**  | Full access: invite members, manage integrations, edit workspace settings, read and write all workspace files                         |
| **Member** | Write to their own `people/{name}/*` files, their assigned areas, and `feed.md`; read shared workspace memories and use all MCP tools |