Team and access
Everyone in your organization signs in with their own account, and what they can do comes from the roles they hold: on the organization, or on one project. A role can be given to a person directly or to a group they belong to. These guides cover bringing people in and deciding what they can reach.
Where access fits
Roles decide what you see everywhere else: a project role covers that project's tasks, worktrees and sessions, and only Org Owners and Admins see Billing. A person's roles add up: Direct, Via a group, or Inherited from the organization. An account starts Invited, becomes active once the person signs in (or Declined if they turn it down), and can be Disabled and enabled again.
Pages in this section
- Invite a person and grant access — create the account, send the invitation, and give it a role.
- Follow up on an invitation — resend an invitation, use Reinvite for someone who declined, or withdraw it.
- Create a group — gather people who need the same access and grant it once.
- Add someone to groups — change one person's groups from their account, or add or remove many people at once.
- Change a person's role or remove them — change someone's organization role, or disable or delete their account.
- Remove several people at once — tick the people who are leaving and disable or delete their accounts in one go.
- Hand over a leaving member's work — move their secrets and model accounts, reassign their tasks, then disable or delete the account.
- Hand your organization to a new owner — make someone else Org Owner, move the billing to them, then have them remove your Owner role.
- Let disabled people sign in again — list the disabled accounts and enable one or many of them again.
- Give someone access for a limited time — grant a project or model account role that ends on a date you pick, and give more time.
- Check what someone can access — see every role a person holds and ask whether they may do one thing.
- What one project can see of another — what people and agents on one project see of other projects' task titles, results and code, and how to keep projects apart.
- Review who holds an organization role — see every Org Owner and Org Admin, how they got the role, and remove the ones no one needs.
- Give people an organization role — grant one role across the whole organization to several people or groups at once, from the Access tab.
- See when someone last used Jaah — read when an account was created, first signed in and last seen, to find unused ones.
- Correct someone's name or email — fix a misspelled or missing name, or change the address someone signs in with.
- Reset someone's two-factor or SSO link — let someone set up two-factor again, or relink their identity provider account.
- Set a teammate's GitHub or GitLab push account — set a teammate's Git Access, so the tasks they start can push.
- Connect Slack — connect your organization's Slack workspace, and get task alerts and answer questions there.
- Rename or delete a group — rename a group or change its description, or check what it grants and delete it.
- Take a role away from a group — remove one role a group holds, so its members stop getting that access, and keep the group.
- Give everyone in your organization access to a project: grant one project role to the Everyone group, so every member holds it, including people who join later.
- Make members sign in with Google or Microsoft — limit sign-in to your Google Workspace or Microsoft Entra ID tenant.
- Limit sign-in to your network's addresses — admit members only from the address ranges you list.
- Switch to another organization — accept an invitation and move between the organizations you belong to.
- Create a staging organization — create your one organization for testing, switch to it and back, and sync its admins.
- Connect your GitHub, GitLab or other code host — connect your own GitHub, GitLab, Bitbucket or Azure DevOps account so your tasks can push.
- Change your password — set a new sign-in password from your profile, and what it signs out and forgets.
- Reset a forgotten password — get an email link from Forgot password?, set a new password, and ask again when the link has expired.
- Add your name — set your first and last name so teammates see it instead of your email.
- Remove a trusted device — see which browsers skip your two-factor code, and revoke one or all of them.
- Rotate or revoke an API key — give a key a new secret while the old one keeps working for a while, or end it for good.
- Change what an API key can do: edit a key's name, description, permissions or IP allowlist; its expiry stays fixed.
- Switch between light and dark mode — pick Light, Dark or Default for the console's colours on your profile.
- Reach a GitHub organization's repositories — clear the Git section's warning when a GitHub organization blocks Jaah.
- Connect your organization's Gmail — connect a Workspace mailbox with a service-account key so Jaah sends from your address.
- Create an API key — make a key for a script or CI job, with an expiry and only the permissions it needs.
- Choose the role new members get — set the Default role for people who join by your email domain, sign up or arrive by SSO.
- Apply for an organization of your own — start a new organization from your account menu and switch to it once approved.
- Find and change a setting — find a setting under Personal, Organization or Customize, or by searching, and save a new value.
- Set up two-factor sign-in — link an authenticator app when your organization requires it, save your recovery codes, and sign in with one.
Every screen used here is described in the People and Groups references. To grant a role on one project only, see Give someone access to a project. For the roles and where they come from, see How team and access work.