> For the complete documentation index, see [llms.txt](https://docs.videc.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.videc.de/acron-9.3/en/anlagenverwaltung/register-lizenz.md).

# License tab

ACRON is operated with a network license by default. The scope of a license is defined by the number of [License Consumer](https://github.com/Dataforum-Software/gitbook/blob/master/acron/9.3/en/designer/glossar/license_consumer.md) and the number of process variables. The single License Consumers can be used as arbitrary, competing License Consumers from any workstation, can be permanently assigned to a workstation, or can be reserved for REST API data access. License utilization is managed by the active ACRON Database Server.

## Licensing beginning with ACRON 9.3. <a href="#lizenzierung_ab_93" id="lizenzierung_ab_93"></a>

Beginning with version 9.3, the network license is the new default type. The license settings are automatically changed to "Acquire license from Database Server" during the update to 9.3. Instead of workstations and users, [License Consumers](https://github.com/Dataforum-Software/gitbook/blob/master/acron/9.3/en/designer/glossar/license_consumer.md) are now licensed. The scope of a license is therefore defined by the number of license consumers and the number of process variables.

The single-user and multi-user licenses will be completely discontinued starting with version 9.4, but can still be used transitionally in 9.3. To do this, the license settings must be changed to "Acquire license locally" in ACRON Designer after updating.

## License information <a href="#lizenzinformationen" id="lizenzinformationen"></a>

The "Read" button displays general information about the license, such as status, license type, license number, version, as well as an overview of all available and currently used [License Consumers](https://github.com/Dataforum-Software/gitbook/blob/master/acron/9.3/en/designer/glossar/license_consumer.md), etc.

## License settings <a href="#lizenzeinstellungen" id="lizenzeinstellungen"></a>

Note

In future versions of ACRON, the license will be acquired from the Database Server only. When creating a new plant or when updating existing plants, this option is already set automatically by now. The license setting can be changed to 'Acquire license locally' or 'First search license locally, then acquire from Database Server as necessary'.

You can access a license as follows:

|                                                                                  |   |                                                                                              |
| -------------------------------------------------------------------------------- | - | -------------------------------------------------------------------------------------------- |
| Acquire license locally                                                          | : | A license is searched for on the local computer.                                             |
| Acquire license from Database Server                                             | : | A license is searched for on the Database Server computer.                                   |
| First search for license locally, then acquire from Database Server as necessary | : | A license is searched for on the local computer first, then on the Database Server computer. |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.videc.de/acron-9.3/en/anlagenverwaltung/register-lizenz.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.