> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/end-user-and-partner-section/end-user-section/getting-access-and-signing-in.md).

# Getting Access and Signing In

This page explains how to get a DocBits account and how to sign in:

* [Sign in with an existing account](#sign-in-with-an-existing-account) — the fields on the login screen and the region selector.
* [Registration](#registration) — create your own DocBits account.
* [Forgot password](#forgot-password) — reset your password with a reset link.
* [First password for admin-created accounts](#first-password-for-admin-created-accounts) — set the first password for an account your administrator created for you.

Two-Factor Authentication, passkeys and the second sign-in step are covered in [Two-Factor Authentication (2FA)](https://docs.docbits.com/security/two-factor-authentication.md). Use the language menu at the top right of these forms if you need another display language.

## Sign in with an existing account

Open the DocBits web address your organisation was given — for example `https://app.docbits.com` — and sign in on the login screen.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-ccd036e841e5bb648fba4e6a44e50fc79383bd0e%2Fgetting-access-login-en-20261107.png?alt=media" alt="English DocBits login screen with empty E-Mail and Password fields, Remember me, the Auth region selector set to Europe, Log In, Sign in with a passkey, Sign in with Google and Sign in with Microsoft"><figcaption><p>The login screen: email and password, Remember me, the Auth region selector, Log In, passkey and the Google and Microsoft sign-in buttons.</p></figcaption></figure>

1. **E-Mail** — the address your DocBits account was created with.
2. **Password** — your DocBits password. The eye icon in the field shows or hides what you typed.
3. **Remember me** — fills in your email address the next time you open the login screen.
4. **Auth region** — DocBits runs in two regions, **Europe** and **United States**, and each has its own sign-in service. The selector is shown on deployments that use both (production, dev and sandbox). DocBits preselects your last choice, otherwise the region that matches your computer's time zone, otherwise Europe. If your account was created in the other region, select it here before you click **Log In**.
5. Click **Log In**.

Below the password fields:

* **Sign in with a passkey** — appears when your browser supports passkeys. It signs you in without your password. See [Passwordless sign-in](https://docs.docbits.com/security/two-factor-authentication.md).
* **Sign in with Google** and **Sign in with Microsoft** — for organisations that use single sign-on with these providers. The identity provider handles the sign-in, so the DocBits password and the DocBits two-factor requirement do not apply.
* **Forgot password?** — see [Forgot password](#forgot-password) below.
* **Register** — see [Registration](#registration) below.

{% hint style="info" %}
Pick the **Auth region** your organisation uses before you click **Log In**: the choice decides which region's sign-in service receives your credentials. If you are unsure, ask your administrator.
{% endhint %}

## Registration

You can create a DocBits account yourself on the registration page. Open it from the **Register** link on the login screen, or navigate to `https://app.docbits.com/register` (use the web address your organisation was given).

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-512a0315c51971e4161f50873feb8a56ecbc779c%2Fdbdc-8-register-native-en-20261101.png?alt=media" alt="English DocBits registration form with five empty fields, unchecked reCAPTCHA and Terms and Conditions, Get Started, Google and Microsoft, and the Login link"><figcaption><p>Create your account with your name, work email and password. Complete reCAPTCHA when shown, accept the terms and choose Get Started; Login returns to sign-in.</p></figcaption></figure>

Fill in the form:

1. **First name** and **Last name** — your name as it should appear in DocBits.
2. **E-Mail** — your work email address. This is your login identifier.
3. **Password** and **Confirm password** — see the password rules below. A checklist under the password field shows which rules your password already meets.
4. If the page shows a **reCAPTCHA** widget, complete it. The widget only appears when your DocBits deployment has bot protection enabled.
5. Tick the checkbox to confirm that you agree to the **Terms and Conditions**.
6. Click **Get Started**. If you already have an account, click **Login** at the bottom to return to the sign-in page. **Visit website** opens the DocBits website for product information.

Use the eye icon next to a password field to show or hide the characters you entered.

### Password rules

Your password must:

* be between **8 and 20 characters** long,
* contain at least one **uppercase** and one **lowercase** letter,
* contain at least one **digit**,
* contain at least one **special character** (`!@#$%^&*()_+=\[{]\};:,.<>?/\|~-`).

Only letters, digits, and these special characters are allowed.

### Sign up with Google or Microsoft

Instead of a password, you can click the **Google** or **Microsoft** button under **Or sign up with**. DocBits creates your account through your identity provider, and you sign in the same way later.

### Confirm your email address

After you submit the form, DocBits shows a confirmation page and sends a **verification email** to the address you entered. Open the email and click the link inside — it takes you to a confirmation page that verifies your address. If the email does not arrive, the confirmation page offers a **resend** option. Once the address is verified, click **Sign in** and log in with your email and password.

## Forgot password

DocBits stores login passwords as salted, one-way hashes. An existing password cannot be retrieved from its hash, so this procedure sets a new password. See [Secure Storage of Credentials](https://docs.docbits.com/security/secure-storage-of-credentials.md) for password storage and recovery details.

If you forgot your password:

1. On the login screen, click **Forgot password?**.
2. On the **Forgot Password** page, enter your **E-Mail** address and click **Reset Password**. If a reCAPTCHA widget is shown, complete it first.

   <figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-426e65143471c06338d4debfe9d100293ae91bd4%2Fdbdc-8-forget-password-native-en-20261101.png?alt=media" alt="English Forgot Password form with an empty E-Mail field, unchecked reCAPTCHA, Reset Password and Back to Login"><figcaption><p>Request a password reset link with your email address and Reset Password, or return with Back to Login. Complete reCAPTCHA when it appears.</p></figcaption></figure>

   If you do not want to reset your password, click **Back to Login** to return to sign-in.
3. DocBits emails you a **password reset link**. Open the email and click the link — it opens the reset page.
4. Enter your **new password twice**. The same password rules as during [registration](#password-rules) apply, and a checklist shows which rules are met.
5. Click **Reset Password**. DocBits confirms the change and takes you back to the login screen, where you can sign in with the new password.

{% hint style="info" %}
Reset links expire after a short time. If the link no longer works, repeat the steps above to request a new one.
{% endhint %}

## First password for admin-created accounts

When your administrator adds you as a user (see [Users](https://docs.docbits.com/administration-and-setup/settings/global-settings/groups-users-and-permissions/users.md)), you receive an email with your login details and a link to set your **first password**. The link opens the **Set Password** page:

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-30a8479156c13825c0eeeb1aacc929b3967509c4%2Fdbdc-8-set-password-native-en-20261101.png?alt=media" alt="English Set Password form with the Welcome to DocBits message, two empty password fields, eye icons, Set Password and Go to Login"><figcaption><p>The Set Password form for the first password of an administrator-created account. Enter the password twice and choose Set Password; Go to Login returns to sign-in.</p></figcaption></figure>

1. Click the link in the invitation email. The page greets you with "Welcome to DocBits! Your account has been created. Please set your password to get started."
2. Enter your password twice — the same [password rules](#password-rules) apply.
3. Click **Set Password**. You can then sign in with your email and this password.

The eye icons show or hide what you entered. If you leave before setting a password, **Go to Login** returns to sign-in.

The link is tied to your account and works only once. If it expires before you use it, ask your administrator to resend the invitation or use **Forgot password?** with your email address.


---

# 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://docs.docbits.com/end-user-and-partner-section/end-user-section/getting-access-and-signing-in.md?ask=<question>&goal=<user_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.
