Teammate join path

Join an existing HQ Cloud company by accepting the invite, opening HQ locally, syncing the company, and running /startwork.

01Accept the invite and sync the company before doing any work.

02Avoid duplicate companies and wrong-context sessions.

$ accept invite -> /hq-sync -> /startwork

Fig 03.0 · Joining the path

The concept

Join path

You receive access, pull the company, then start work inside the shared context.

Fig 03.1 · Accept the invite

Step 01 — Token

The invite grants membership to one intended company, not to every folder, setting, or piece of private context in HQ.

Open the invite link from your admin, confirm the company name, and complete the acceptance step before local setup work.

HQ confirms company membership instead of asking you to create a new company.

/invite teammate@example.com

Step 02 — Local shell

You need a local HQ workspace because HQ is a hard drive for intelligence, not just a cloud account.

Run the installer or open HQ from the signed team installer path your admin shared, then keep the workspace path stable.

HQ starts without asking for unrelated company credentials.

npx create-hq/setup

Fig 03.2 · Open HQ locally

Fig 03.3 · Into the shared context

Step 03 — Shared session

You are ready when the synced company context can drive /startwork without pasted background.

Run sync, select the accepted company, then run /startwork and choose the suggested project, worker, or safe starter task.

The /startwork summary names the synced company and offers scoped next actions.

/hq-sync/startwork

Commands

Accept path

$ accept invite -> /hq-sync -> /startwork

Your route from membership to the first scoped session.

Company sync

$ /hq-sync

Pulls the accepted company context into the local HQ workspace.

References

Accept invite, install or open HQ, sync company, run /startwork.

If HQ asks the teammate to create a company, stop and get a fresh invite.

Next move