> For the complete documentation index, see [llms.txt](https://knowledge.rollcredits.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.rollcredits.io/getting-started/sign-in.md).
# Sign in to RollCredits
Accept your invite, sign in with a one-time email code, a password or Google, and log out.
Whenever you're signed out, RollCredits shows the log-in screen at any address you open, and opens that page once you've signed in. Everyone signs in the same way, whatever their role, on a phone or a computer.
{% hint style="info" %}
If your company uses multi-factor authentication and you've enrolled in it in **Settings**, you also enter a code texted to your phone each time you sign in. See [Enter your verification code](#enter-your-verification-code).
{% endhint %}
The log-in screen, **Log in to your account**, offers three ways in: a one-time code sent to your email, your email and password, or your Google account. For help signing in, use the support email address at the bottom of the screen.
## Accept your invite
When someone adds you to a production and you don't have a RollCredits login yet, you get an email headed "You've been invited to RollCredits!".
1. In the invite email, select **Log in**. If the button doesn't work, copy the link printed under the code into your browser.
2. RollCredits opens **Enter your one-time code** for the email address the invite went to.
3. Type or paste the 6-digit code from the invite email into the boxes. On a phone, the boxes use the number keypad.
4. RollCredits checks the code as soon as all 6 digits are in. You can also select **Verify Code**.
If RollCredits still needs your details, the setup page opens the first time you sign in. See [Set up your account and company](/getting-started/set-up-your-account.md).
On **Enter your one-time code**:
* **Resend Code** emails you a new code and clears the boxes. Use the code from the newest email.
* **Back to Log In** returns to the log-in screen.
* If the code is wrong, **Unable to verify with OTP** appears. Check the digits, or select **Resend Code**.
{% hint style="info" %}
You don't need the invite email to sign in. If its code doesn't work, select **Back to Log In** and [log in with a one-time email code](#log-in-with-a-one-time-email-code) instead.
{% endhint %}
## Log in with a one-time email code
You can always sign in with a code, whether or not you've set a password.
1. On the log-in screen, under **Login with a one-time email code**, enter your **Email**.
2. Select **Send a login code**. **Successfully sent code! Please check your inbox.** appears, and **Enter your one-time code** opens.
3. Open the "Your OTP Has Arrived!" email and copy the 6-digit code.
4. Type or paste the code into the boxes. It's checked on its own once all 6 digits are in, or you can select **Verify Code**.
Keep the RollCredits page open while you get the code from your email. If the page reloads before you enter it, you're back on the log-in screen and need to send a new code.
## Log in with your password
1. On the log-in screen, under **or login with password**, enter your **Email** and **Password**.
2. Select **Sign in**.
**Sign in** stays greyed out until you've entered a valid email address and a password. If either is wrong, **Unable to login with the provided credentials** appears.
You have a password only if you've set one, and invited people start without one. To set one or replace a forgotten one, select **Forgot password?** below the **Password** field. See [Reset your password](/getting-started/reset-password.md).
## Sign in with Google
1. On the log-in screen, select **Sign in with Google**.
2. Choose your Google account and follow Google's steps.
Choose the Google account for the email address your invite went to. RollCredits then opens the page you were trying to reach.
## Sign up
Sign up emails you a code and then lets you set a password for your email address. It doesn't add you to a production. Only an invite does that.
1. At the bottom of the log-in screen, next to **Don't have an account?**, select **Sign up**.
2. Enter your **Email** and select **Send One-Time Code**. **Successfully sent sign up code! Please check your inbox.** appears.
3. On **Enter your one-time code**, type or paste the 6-digit code from the email.
4. The **Set your password** page opens. Choose your password there. See [Reset your password](/getting-started/reset-password.md) for the password rules.
**Send One-Time Code** stays greyed out until you enter an email. To leave, select **Back to Log In**.
If nobody has invited your email address to a production yet, the not-set-up screen opens instead of **Set your password**.
## If RollCredits says you're not set up yet
When you sign in with an email address that isn't on any production, RollCredits shows **You are not set up to use RollCredits yet under this email**, followed by the address you signed in with. You also see it if you've been removed from every production you were on.
1. Select **Log out** at the top right.
2. Sign in again with the email address your invite went to.
If you haven't been invited, ask your production's admin to invite you. They do it on **Project > Team**. See [Manage your team](/project/team.md).
## Enter your verification code
If your company uses multi-factor authentication and you've enrolled in it, this step comes after any of the ways in above.
1. Sign in. **Enter your verification code** opens.
2. After a few seconds, RollCredits texts a code to the phone number you enrolled with and shows that number on the screen.
3. Type or paste the code into the boxes. It's checked on its own once all 6 digits are in, or you can select **Verify Code**.
On **Enter your verification code**:
* **Resend Code** texts you a new code.
* **Back to Log In** signs you out and returns to the log-in screen.
* If the code is wrong, **Failed to verify MFA code.** appears, followed by the reason. Check the digits, or select **Resend Code**.
* If the text can't be sent, **Failed to send MFA code. Please try refreshing the page, or contact support if the issue persists.** appears. Refresh the page to try again.
To stop using multi-factor authentication, or to get your codes on a new phone number, sign in and go to **Settings**. See [Manage your account settings](/getting-started/settings.md).
## Emails you get when you're invited
* **New to RollCredits:** the invite email, headed "You've been invited to RollCredits!", and a second email saying you've been added to the production.
* **Already have a login:** only the email saying you've been added to the production. There's no new invite. Sign in the usual way and switch to the new production. See [Switch projects and companies](/getting-started/switch-projects.md).
* **After your first sign-in:** a welcome email for your role, usually within half an hour. You get it only once.
## Log out
1. Open the sidebar. On a phone, select the menu button (three lines) at the top right. On a computer, point at the left edge of the screen.
2. Select the red power button at the bottom of the sidebar, next to **Logged in as** and your email.
You're logged out right away, with no confirmation step, and the log-in screen appears. On a computer, the power button shows at the bottom left even while the sidebar is closed.
Pages without a sidebar, such as **Set your password**, the setup page and the not-set-up screen, have a **Log out** button at the top right instead.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://knowledge.rollcredits.io/getting-started/sign-in.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
