> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sreagent.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Sign in and join your team

> Sign in with GitHub or Google, ask to join your team's organization, and control who can ask.

export const Plan = ({tier}) => <Badge color="blue">{tier} plan</Badge>;

Anyone can sign in with GitHub, Google or email and password. Org admins decide who may join. Business organizations can also use [single sign-on](/guides/administer/single-sign-on).

<Plan tier="Free" />

## Sign in with GitHub or Google

<Steps>
  <Step title="Open the sign-in page">
    On **Sign in to SRE Agent**, click **Continue with GitHub** or **Continue with Google**. The
    same buttons are on the registration page.
  </Step>

  <Step title="Approve at the provider">
    After you approve, SRE Agent recognises you. A returning identity signs straight in.
  </Step>

  <Step title="Finish on the One more step page">
    A first-time visitor lands here. If your address is on a company domain that already has a team,
    the page shows **This looks like your team** with a **Request to join** button. Otherwise name
    your own organization and become its administrator.
  </Step>
</Steps>

If your address already has an account, you are asked to confirm the mailbox from the sign-up email, or with **Forgot password**. Public mailbox domains such as gmail.com never suggest a team, because everybody shares them.

An invitation link skips this step, because it already names the organization and role.

### Join your team

A request to join grants nothing until an admin answers it. Until then you stay on **Waiting for approval**, where you can also create your own organization instead. You are emailed when the admin decides. Requests nobody answers are dropped after 14 days, and you can ask again.

Admins answer under **Users**, in the **Requests to join** card at the top of the directory. Each request shows the address and whether it is verified. **Approve** appears once the address is verified, and **Deny** is always there. Approve only addresses you recognise.

### Control who can ask

Org admins find two switches under **Settings**, **Preferences**, **Social sign-in**:

| Setting | What it does |
| - | - |
| **Allow join requests from social sign-in** | With it off, people signing in with GitHub or Google are never offered your organization and cannot ask to join it. Invitations, members and waiting requests are unaffected. Save with **Save social sign-in**. |
| **Keep our email domains invitation-only** | On by default. Nobody with an address on a domain where you have a confirmed member can self-register a separate organization. They are routed to a join request instead. Save with **Save domain policy**. |

The page lists the domains the second setting covers. Public mailbox domains can never be made invitation-only.

Each person can see and remove their linked providers under **Account**, **Sign-in methods** with **Unlink**. An account with no password and one linked provider cannot unlink it, so set a password with **Forgot password** first.

## Related

* [Manage people and roles](/guides/administer/organizations-and-roles): approve requests and set roles.
* [Quickstart](/guides/get-started/quickstart): create an account and your first investigation.
* [Plan matrix](/guides/reference/plan-matrix): which plans include single sign-on.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.