Onboarding: joining a team

For someone a teammate already invited. There’s no org to create and no billing to set up, just a link or a code to redeem.

Setting up your own org instead? Go to Onboarding: starting fresh. This page assumes you already have an invite.

Terminal track

Never opens a browser, except to approve sign-in. The link or code your teammate sent you goes straight into the command:

npx @retasc/cli join <invite-code-or-link>

How do you sign in to Retasc?
  1) GitHub
  2) Google
Choose a number: 1

  Open: https://github.com/login/device
  Enter code: B7X4-QP2K

  Waiting for GitHub authorization…

You authenticate as your own identity. There’s no separate Retasc account and no email invite to accept.

Redeem the invite

Nothing else to type, the code was already in the command:

✓ Joined org "Acme".

Codes are single-use and expire (7 days by default). If yours is stale, ask the owner to mint another.

Claim your imported identity

If a migration carried people across when the org was set up:

When Acme migrated, some people were carried across.
One of them may be you:
  1) Ben Alvarez          from Jira
  2) None of these are me
Choose a number: 1
✓ Linked. Everything "Ben Alvarez" wrote is now yours.

Pick the project

Only asked if the org has more than one:

Which project:
  1) Engineering (ENG)
  2) Design (DES)
Choose a number: 1

Install retasc globally, or run it on demand

Same question as the other onboarding path:

Install the retasc command on this machine?
  1) Yes, globally          A `retasc` command you can use anywhere.
  2) No, run it on demand   Nothing installed, fetched fresh each run.
Choose a number [1]:

Connect the folder, and confirm

Nothing to type. It mints your key and wires the folder:

✓ Minted key for this workspace (rtsc_k_2mQ9fd…).

✓ This folder is bound to org "Acme" / project ENG.
  Agents launched here can only ever read or write ENG.

Start your agent in this folder, or restart it if it's already open,
and it'll pull from the queue.

Run join before bind. If you don’t belong to an org yet, retasc bind offers to create one, so binding first puts you in an org of your own instead of your team’s, and your work lands somewhere nobody else can see. retasc join <code> (or the combined command above) always runs the join first. If it already happened: run retasc join <code>, then retasc bind --org-id <their-org-id> --yes to repoint the folder.

Web track

Never opens a terminal, a raw command shown to you would be a bug.

Open the link

A real join page, not a sign-up for your own org.

retasc.com/j/8kd2m1

You’re invited

Ana Petrescu invited you to Acme. Sign in to join, no org to create.

GContinue with GoogleFor the many people who have no GitHub account→

GHContinue with GitHubOAuth, one identity→

Choose GitHub or Google, whichever you have.

Join the org

One click. You never see a create-an-org screen.

Claim your imported identity

If a migration carried your work across, say which name is you.

dash.retasc.com

Imported history

The import carried this human across. A name isn’t proof, so only you can say.

Ben Alvarezfrom JiraThat’s me

Connect your agent

The same handover an owner gets: copy a block, paste it to your agent, and it sets the folder up itself.

dash.retasc.com/onboarding

Last step

Same handover as an org owner gets: paste this to the agent running in your project folder.

Set Retasc up in the folder you’re…Copy

Waiting for your agent’s first call…

Set Retasc up in the folder you're working in, so you can pull work from my queue.

First tell me its full path, and wait for me to say go.

Then run exactly this:
npx @retasc/cli bind --setup rtscsetup_7ka92m

If Node 18 or newer isn't installed, install it. Prefer a way that doesn't need
admin rights. Only ask me if there's no other option.

When it's done, restart yourself so the Retasc tools load, then check my queue
and tell me what you find.

What you can do

Every membership is owner, admin, or member. Invites always join as member, an owner upgrades someone from there.

	Owner	Admin	Member
Read and write issues, claim work	✓	✓	✓
Mint, rotate, and revoke their own agent keys	✓	✓	✓
Invite teammates, offboard ordinary members	✓	✓	-
Run billing, connectors, imports, projects, settings	✓	✓	-
Export org data	✓	-	-
Change a member’s role, delete the org, transfer ownership	✓	-	-

Admin runs the org day to day, everything above except deleting the org, exporting its data, or acting on the owner or another admin. It’s the role for someone who shouldn’t wait on the owner for routine ops.

Upgrading to admin is Dash-only, and owner-only. From the Dashboard’s Team tab, the owner clicks Make admin next to a member’s name (a confirm step, since it’s a real permission grant), or Make member to reverse it, no confirm needed. There is no CLI command for this, and it isn’t exposed over MCP either, on purpose: an admin who could grant admin would be self-propagating.

Members are free and unlimited, Retasc meters actions, not seats, so adding people costs nothing. See Pricing.

Get started

How it works

Connectors

Pricing & billing

Reference

Onboarding: joining a team

Terminal track

Web track

What you can do

Next steps

Onboarding: starting fresh

Pricing & billing

​Terminal track

​Web track

​What you can do

​Next steps

Onboarding: starting fresh

Pricing & billing

Terminal track

Web track

What you can do

Next steps