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

# Sign in

> Sign in with Google, Apple or GitHub, add another way to sign in to your account, connect GitHub for repository access, and delete your account.

On r5d.dev you sign in with **Google**, **Apple** or **GitHub**, through r5d's sign-in service, auth.r5d.dev. The three are equal: each only tells r5d who you are. Choose **Continue with Google**, **Continue with Apple** or **Continue with GitHub** on the first page, or **Sign in** in the top bar, which asks which one.

The first time you sign in, r5d creates your account: you choose your **handle**, and on r5d.dev the account joins the waitlist: expect an invite by email soon ([Signing up](https://docs.octomerge.dev/index.md#signing-up)). An installation with other ways to sign in, such as a company's own sign-in, lists them beside these.

auth.r5d.dev keeps you signed in for seven days, so other apps that sign in with it don't ask again in that browser.

## Signing in with Apple

Apple asks whether to share your email address or to **Hide My Email**. With Hide My Email, r5d gets an address at `privaterelay.appleid.com` instead, and it is your account's email like any other: Apple forwards r5d's emails to you. Because that address says nothing about you, r5d suggests a handle from your name instead. Apple shares your name only the first time you sign in with it; without one, you type a handle, and it also names your account.

## One account, several ways to sign in

You can add Google, Apple or GitHub to your account, and then sign in with any of them into the same account:

1. Open **Settings → Sign-in methods** (or **Sign-in methods** beside your name in **Settings**). It shows which of Google, Apple and GitHub your account signs in with.
2. Choose **Connect** beside the method to add. If you last signed in more than ten minutes ago, auth.r5d.dev, r5d's sign-in, first asks you to confirm it's you with a method you already have.
3. Sign in with the method you're adding. You come back to **Sign-in methods**, which shows it connected.

A method can be added only if it hasn't signed in to r5d before: a Google, Apple or GitHub account that is already its own account can't be added to another one, and **Sign-in methods** says so. If you made that other account by mistake and don't need it, [delete it](#deleting-your-account) first, then connect its method to the account you use. Methods you add stay; you can't remove them yourself yet.

A method you add somewhere else, such as on auth.r5d.dev itself or in another app that signs in with it, shows in **Sign-in methods** after you next sign in to r5d. auth.r5d.dev also lists your methods, with the email of each.

Your name and picture in r5d follow the method you signed up with: each time you sign in with it, r5d takes them from there. Signing in with a method you added leaves them as they are, and so does a sign-in that shares no name or picture (Apple shares no picture). Your email stays the one you signed up with.

The first time you sign in with a method auth.r5d.dev doesn't know, you go straight to choosing your handle. If you already have an account and signed in another way by mistake, choose **Already have an r5d account? Sign in to it instead** on that page. That frees the method, and after you sign in to your account, **Sign-in methods** opens, where you can add it. A sign-up you leave without choosing a handle frees its method too, within about half an hour. If you created a second account by mistake, [delete it](#deleting-your-account): that frees the method as well, and you can then add it to your account.

### "Another r5d account already uses this email address"

r5d never joins accounts by their email address. If you sign up with a method whose email another r5d account already has, r5d refuses the new account and frees that method again. If the other account is yours, choose **Sign in with another method** and sign in the way you usually do. **Sign-in methods** then opens, where you can add the method you tried.

### "Too many sign-ins were started from your network"

r5d limits how many sign-ins one network can start: 30 in 10 minutes, counted for everyone who shares its internet address, such as an office or a classroom behind one router. Past that, the page says how long to wait; then choose **Sign in again**. On r5d.dev, more than 10 sign-ins started in 10 seconds from one address are also blocked for 10 seconds. While you choose your handle, checking handles and submitting are limited too, far above what typing needs.

## GitHub repositories

Signing in with GitHub only identifies you: it gives r5d no access to your repositories. Repository access is a separate grant, the same whichever way you sign in: **Connect GitHub repositories** in **Settings → Git**, or when you start a project from GitHub. It uses the GitHub account you're signed in to on github.com, which can be any GitHub account, and your workers use it for GitHub's container registry too ([GHCR](https://docs.octomerge.dev/platform/ghcr.md)). Once connected, **Settings → Git** shows the grant as **Connected**, with the GitHub account it belongs to; **Connect another GitHub account** replaces the grant with another account's.

## Signing out

**Log out** (in the sidebar's **More** tab and in **Settings → Sign-in sessions**) also ends your sign-in at auth.r5d.dev in that browser, so the next sign-in goes to Google, Apple or GitHub again. **Sign out all devices** does the same and also ends your r5d sessions in every other browser. Neither touches your `r5dctl` credentials or API keys, nor your sign-in at Google, Apple or GitHub itself.

## Deleting your account

**Settings → Delete account** deletes your account and everything in it, at once. It can't be undone. The page lists what goes with it:

* your projects, with their branches, conversations, files and history at r5d (your repositories at GitHub and other Git hosts aren't touched);
* your conversations in your workspace; running ones are stopped first;
* your workspace's files, instructions and skills, secrets, model connections, MCP servers, the enrollments of your workers and browsers, and your `r5dctl` devices and API keys;
* your teams: a team only you are in is deleted, a team whose only admin you are gets its longest-standing other member as admin, and you leave the others;
* on r5d.dev, your [Open LLM Router](https://docs.octomerge.dev/platform/open-llm-router.md) account, when you sign in to it with r5d: it's deleted with everything in it (its apps, provider accounts, keys, logs and usage history). If it also signs in with Google, it stays and only loses its r5d sign-in. The page names the account.

Choose **Delete account…** and type your handle to confirm. Deleting many projects can take a minute; the page shows what it is doing. If it stops before it's done (you close the page, or something fails), what was deleted stays deleted and your account stays: delete it again to finish. If Open LLM Router can't be reached, your account isn't deleted until it can: delete it again a few minutes later.

Afterwards you're signed out, and auth.r5d.dev forgets your sign-in, with every method you linked: each Google, Apple or GitHub account you used can sign up again or be added to another r5d account. Files on your own workers stay on them.

Two things stop a deletion until you change them:

* **A plan that still renews.** Cancel it in **Settings → Billing** first: deleting your account doesn't cancel it. A cancelled plan runs until the end of its period; deleting your account before then gives up the rest, without a refund.
* **Being the installation's only administrator.** Another account has to become an administrator first.

Deleting needs a browser signed in to the account: `r5dctl`, API keys and agents can't delete it.


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