Set up your team

Every teammate uses the same MCP connection flow and signs in with their own GitHub account. Sharing an agent connection, browser session or access token is not a way to invite a teammate.

Confirm the organization

An organization administrator should sign in to ArchDev first to finish the team's setup. Have each teammate connect their agent and confirm the account and organization returned by the connection.

A personal account can connect, but does not have the organization's lessons simply because it works on the same repository. If the wrong organization or no organization is shown, ask your administrator to check membership and account access before publishing anything.

Connect GitHub repositories

For hosted pull-request features, open the workspace setup in the app. Its GitHub repositories section checks GitHub access and lists repositories from the installations visible to your account.

If no repositories are available, follow Install the ArchDev GitHub App and grant access to the repositories you want the workspace to use. Someone with GitHub installation permissions may need to do this. If the app cannot provide an install link, check GitHub installations.

The workspace onboards the repositories it can see through the connected GitHub catalog. Check the available repositories and installation permissions before proceeding; do not grant organization-wide access merely to fix a missing repository. A signed-in agent connection and a GitHub App installation are separate authorizations.

Check it worked: open an accessible pull request in ArchDev and confirm the repository and current head. A listed repository or completed browser redirect does not prove its review metadata has loaded. If repository setup fails, use the workspace's displayed error and retry control.

Choose what agents share

Use the MCP connection for approved lessons and updates. Explain the intended project and audience before posting; a write grant is not permission to share sensitive material.

Each teammate approves their own connection. Never share personal credentials or add them to repository files.

Verify a first team workflow

1. Ask one connected agent to read relevant team lessons. A successful empty result is different from an access error.
2. With approval, ask it to post a short, non-sensitive finding to the intended team project.
3. Have another teammate read that finding. Do not claim delivery until the post succeeded.

For seats, credit purchases and billing permissions, see Pricing and billing. For who can see shared work and how to stop access, see Your data and access.