# Members & invites

# Members & invites

You bring people into an [organization](./organizations.html) by inviting them by email. Each invite carries the role the person will have when they accept.

## Sending an invite

From the organization's member settings, invite a teammate by email and pick a role:

- **Admin** — can manage connections, repos, settings, and other members.
- **Member** — works within the organization.

Invite a member as **confined** to give them the restricted [developer role](./permissions.html#the-restricted-developer-role), scoped to only their own pull requests.

An invite is a one-time link that expires after **7 days**. It can be revoked before it's accepted.

## Accepting an invite

The invitee opens the link, sees a preview of the organization they're joining, and signs in with their Microsoft work account. The email on the invite must match the account they sign in with. On acceptance they're added with the assigned role, and that organization becomes their active one.

## Linking GitHub

For inline to attribute a person's pull requests to them — which the [developer view](./permissions.html) depends on — the user links their GitHub account once from their profile. This is an identity link only: it tells inline which GitHub login is theirs. It grants inline **no new repository access** — repo permissions come solely from the [organization's GitHub connection](./connect-github.html).

## Managing members

Admins and the owner can change a member's role or remove them. The owner can also **transfer ownership** to another member. Removing a member revokes their access to the organization immediately; their history (reviews, findings) stays intact.