> 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/administration-and-setup/settings/global-settings/company-information.md).

# Company Information

## Video tutorial: Company, subscription and audit

{% embed url="<https://docbits-videos.fra1.cdn.digitaloceanspaces.com/settings-assistant/company-subscription-audit-admin/v2/en.mp4>" %}
Company information, subscription plan and audit logs in DocBits
{% endembed %}

The video shows the company information and preferences, the subscription plan, the login activity and the audit logs.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-52a456806e3c96bc2633c43487ac93fb4b711fbb%2Fprior-i002-en.png?alt=media" alt="Company email-domain configuration."><figcaption><p>Company email-domain configuration.</p></figcaption></figure>

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-f8c83468ba25d0dc9766c0a6d24cab9a3f0bf2c9%2Fprior-i001-en.png?alt=media" alt="Company information with organization values hidden."><figcaption><p>Company information with organization values hidden.</p></figcaption></figure>

The Company Information page lets you manage your company profile, preferences, and subscription details. It is organized into the following sections:

## Company Information

This section contains your core company data, grouped into four areas:

### Company Identity

* **Name** *(required)*: The legal name of your company.

### Address

* **Street + Number**: Your company's street address.
* **Postal Code**: ZIP or postal code.
* **City**: City name.
* **Country**: Select your country from the dropdown.

### Legal Information

* **Company ID**: A unique identifier for your company, used for integrations and internal reference.
* **Tax ID**: Your tax identification number for financial reporting.
* **Commercial Register ID**: Your commercial register number for legal documentation.

### Contact

* **Official Company Phone Number**: The primary phone number for your company.
* **E-Mail**: The main email address used for official communications.

After entering or updating any fields, click **Save** to apply your changes. The **?** icons beside the legal identifiers show extra field guidance. Select the section heading to expand or collapse the form.

## E-mail domains

Organization admins can open **Settings → Company Information → E-mail domains** to manage the domains used for automatic organization assignment. When someone signs in with Microsoft or Google and is not yet a member of an organization, DocBits can assign them to this organization if their e-mail address uses one of its listed domains. A domain can belong to only one organization.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-93f224736515c1cc9fe15582d5f5c81de97a4ade%2Fcompany_email_domains_en.png?alt=media" alt="Expanded E-mail domains section with an empty domain list, input field and Add domain button"><figcaption><p>The English E-mail domains section before a domain is added. Enter a company domain, then select Add domain.</p></figcaption></figure>

Enter the domain only, such as `example.com`, in the input and select **Add domain** or press Enter. The first domain becomes the primary domain. If more domains are listed, use **Make primary** on another row to change it, or the trash icon to remove a domain. Errors such as an invalid domain, a personal e-mail provider or a domain already assigned elsewhere appear under the input. **No domains assigned yet** means this organization has no domain rule.

Before adding a domain, check which organization should receive new sign-ins. To manage existing memberships, continue with [Users](https://docs.docbits.com/administration-and-setup/settings/global-settings/groups-users-and-permissions/users.md).

## Release Channel

The **Release Channel** section controls how this organization receives DocBits updates. Select the section heading to expand it.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-eba74b761b066f862491bc19d5d3e1b834b3aa48%2Fcompany_release_channel_en-20261010.png?alt=media" alt="Expanded Release Channel section with the Vesta and Nova options"><figcaption><p>The English Release Channel section. Vesta delivers hotfixes only, Nova delivers new features after every release (default).</p></figcaption></figure>

* **Vesta**: Receives hotfixes only, for maximum stability.
* **Nova**: Receives new features after every release. This is the default.

Only one channel is active at a time. Choose **Vesta** when the organization should stay on a proven version and only receive fixes; choose **Nova** to get new functionality with each release.

## Two-factor authentication

The **Two-factor authentication** section controls whether members of this organization must use multi-factor authentication (MFA) when signing in with a password. Select the section heading to expand or collapse it.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-2a6edb0b6d08c05fe0dca7f0e34aa31e375d9437%2Fcompany_mfa_requirement_en-20261010.png?alt=media" alt="Expanded Two-factor authentication section with the MFA requirement toggle, blocked-enablement hint, effect hint and the MFA adoption panel"><figcaption><p>The English Two-factor authentication section. Enabling is currently blocked until MFA enrollment at login is available; the MFA adoption panel shows how many members already use a second factor.</p></figcaption></figure>

Turn on **Require two-factor authentication for all members** to require every member of the organization to confirm their password sign-in with a second factor. Password logins are then blocked until the member sets up a second factor. Single sign-on (SSO) logins are exempt — their identity provider already enforces MFA.

Enabling is currently blocked: members without an enrolled second factor — including administrators — would be locked out. The option becomes available once MFA enrollment at login is ready. Turning a requirement off stays possible, so an organization can be unlocked.

The **MFA adoption** panel shows how widely a second factor is already used in the organization: the percentage and count of members with MFA enabled, broken down by authenticator app, e-mail and passkey. Select **Save** to apply a changed requirement.

## Settings assistant

The **Settings assistant** section lets your team ask questions about the organization's settings. Select the section heading to expand it.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-98aaa5e7f456478ee8b7ed786588ab9032cb1d2b%2Fcompany_settings_assistant_en-20261010.png?alt=media" alt="Expanded Settings assistant section with the Enable the settings assistant switch"><figcaption><p>The English Settings assistant section. Enable the assistant so that members can ask questions about the organization's settings.</p></figcaption></figure>

The settings assistant is a chat in the settings area. It reads the configuration of your organization and answers questions about its settings. Turn on **Enable the settings assistant** to make it available to your team.

A change is only made after an administrator has confirmed a preview of it.

## Company Preferences

Configure company-wide default settings:

* **Date Pattern**: Choose how dates are displayed throughout DocBits (e.g., `%m/%d/%Y`, `%d.%m.%Y`).
* **Amount Formatting**: Select the number format for amounts (e.g., Deutsch for `1.000,00`, English for `1,000.00`).
* **New Version Info Dialog**: Toggle whether users see a notification when a new DocBits version is released.

Click **Save** after making changes.

## App-Color

Customize the primary color of the DocBits interface. This is useful for visually distinguishing different environments (e.g., dev vs. production).

* **Color**: Enter a hex color code (e.g., `#2388AE`) or use the color picker.
* Click **Save** to apply, or **Reset** to restore the default color.

## Subscription Plan

View your active subscription plans and their details:

* **Plan Name**: The name of each active plan (e.g., DocBits, DocFlow Users, DocSearch).
* **Days Left**: How many days remain until the plan expires.
* **Start Date / End Date**: The subscription period.
* **Users Count**: Total number of users in your organization.
* **Sub Organizations Count**: Number of sub-organizations configured.
* **Suppliers Count**: Number of suppliers registered.

## Subscription Usage

Monitor your monthly token and workflow consumption:

| Column               | Description                                      |
| -------------------- | ------------------------------------------------ |
| **Type**             | The usage type (Document or Workflow).           |
| **From / To**        | The billing period dates.                        |
| **Tokens Used**      | Number of tokens consumed in the current period. |
| **Remaining Tokens** | Tokens still available in the current period.    |

Use the **Select** button to filter by specific date ranges.


---

# 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/administration-and-setup/settings/global-settings/company-information.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.
