> 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/june5-3.7/en/webanwendung/benutzerverwaltung/zuweisen-und-verwalten-von-nal.md).

# Assigning and Managing NAL

Named Access Licenses are access licenses. Depending on the product license, a certain number of named access licenses are available.

With the help of this licensing model, apps such as FlexIn, DataTrans, or JUNE5 Connectors, as well as users, can be granted access to JUNE5. Users assigned to an NA registration can access the system at any time. These users are not affected by the concurrent session model! Named access licensing (NAL) differs from the named user licensing model, in which the number of users is defined on a time-based basis. Furthermore, in NA registration, a distinction is made as to whether a named access license can be used by an app or by a user.

Named access licenses (NAL) can be distributed among tenants in multi-tenant mode. To assign named access licenses, proceed as follows:

1. Click the "Named Access Licenses (NAL)" button in the *User Management* view.
2. Enter the desired number of licenses in the input field of the corresponding tenant. Please note that the total number of assigned licenses must not exceed the number of allowed access licenses. This will be marked in red in the title of the displayed window! Detailed information about the product license can also be found in the *Product Information* view.

After the number of licenses has been assigned to the tenants, this can be completed via the *Save* button.

## NAL Registration

NAL registrations are displayed in a table in the *User Management* view under "Named Access Registration".

The following actions are possible - NA registrations:

* Add
* Edit
* Delete

NAL registrations can only be configured by the client administrator or system administrator.

### Parameters for Registration

* NA Type

oAutomatic (User)

oAutomatic (App)

oManual (User)

oManual (App)

* NA-ID (used by the application for login / Default NA-UID).
* NA Description (provided by the user during registration).
* Registered by (User who performed the registration).
* Registered on (Timestamp when the registration was performed).
* Last login (Timestamp of the last login).
* User (Shows the selected user and offers user selection).
* Permission Groups (Shows the selected permission group and offers permission group selection).
* API Key (This can only be created for manual registrations or renewed only after request and copied to clipboard).
* Delete (Deletes the associated NAL registration).

{% hint style="info" %}
When generating a new API key, the current registration is deleted! A new API key is generated and copied to clipboard.
{% endhint %}

### Configuration in NAL Registration

* In NAL registration, a user can be configured for an NAL record.

oThe login of the user and the current timestamp are entered in the NA-ID of the NAL record.

* In NAL registration, one or more permission group(s) can be configured for an NAL record.

### Automatic Registration of an App

Automatic registration is suitable for applications that require/have a user interface for registration, such as FlexIn, JUNE5 TO JUNE5 Connector, or JUNE5 Batch Connector.

The registration can happen automatically, but the JUNE5 server must be reachable. For registration, the user must also enter their login credentials (username/password).

### Manual Registration of an App

Manual registration is suitable for applications that do not require/have a user interface for registration, such as JUNE5 DataTrans.

Registration of a new app is possible directly in JUNE5 in NA registration. For this, a new record is added in NA registration.


---

# 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/june5-3.7/en/webanwendung/benutzerverwaltung/zuweisen-und-verwalten-von-nal.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.