> For the complete documentation index, see [llms.txt](https://docs.nalpeiron.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nalpeiron.com/zentitle2-docs/premium-features/end-user-portal-eup/end-user-use-of-the-portal.md).
# End user - Use of the portal
Explore what your end users see and can do in the End User Portal (EUP), from logging in and reviewing entitlements to performing offline activations.
The End User Portal (EUP) facilitates the review of entitlements and any "offline" activation that may be required. The entitlement screens can be restricted so users can't see the usage graphs—see setup.
The URL for the EUP is unique to your company, and that is what you will issue to your end-users for access e.g.,
Access to the EUP can be via either of our [Account Based Licensing (ABL)](/zentitle2-docs/ui-administration/configuration/account-based-licensing-identity-based-licensing.md) methods - internal username/password or via an iDP, e.g., Auth0, etc
The portal can be customized using your logo and styled via CSS per the previous page. In our examples, we will use the fictitious company "Elevate Software."
### Login page
Here is the login page the end user will see once you issue them the custom URL to the EUP mentioned above. The custom logo has been added.
You can see the two methods for logging in—the first is using the "internal" username and password from Zentitle2, and the second is using your iDP via single sign-on (SSO).
{% hint style="info" %}
Your end-user attached to a "Customer" will need to be sent access to the EUP, and only end users with an attached entitlement will get access to the EUP.
{% endhint %}
### Using an iDP
Here is an example of an ISV like you setting up Auth0, which is the second option—you must set up this option in settings before it will function, obviously.
### EUP Dashboard
When your end-users log in, the main page shows a list of their entitlements and the opportunity to perform an offline activation process. The end-user can filter their entitlements and download reports quickly and easily.
#### Permissions
{% hint style="warning" %}
The views below are for the "**admin**" role for your end-users.
Admin users can see **all** the entitlements in their account.
Standard users can only view the entitlements to which they are attached.
**Note**: you can add your custom logo like this example, it displays on the left hand navigation
{% endhint %}
### Offline Activation
This is only used in cases where the end user is not connected to the Internet - [more details here](#offline-activation).
### Reviewing Entitlements
Clicking on an entitlement will provide details on the features and capabilities they purchased.
{% hint style="warning" %}
End users cannot edit this information; they can only review it.
{% endhint %}
{% hint style="info" %}
There is no requirement to use an activation code.
{% endhint %}
Using the internal tabs on the entitlements: "activations" and "Activity log," will allow your user to review their usage and any attached activation codes.
#### Activations
The **Activations** tab lists the seats in use on the entitlement. Admin end users see every seat; standard end users see only the seats activated with their own login.
The table shows the following columns:
| Column | Description |
| ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Seat ID** | The identifier your application sent when it activated the seat. |
| **Seat Name** | The name your application sent with the activation, if any. |
| **Mode** | **Online**, **Offline**, or **Roaming**. A roaming seat keeps working offline until a fixed end date. For details, see [License Roaming](/zentitle2-docs/ui-entitlements/using-entitlements/license-roaming.md). |
| **Activated** | When the seat was activated. |
| **Lease Expiry** | When the seat's lease ends. For a roaming seat, it is the roaming end date, and pointing to it shows **Roaming deadline**. |
| **Lease Status** | **Active** while the lease is valid, and **Lease Expired** after the lease has ended. |
You can filter and sort the table, including by **Lease Status**.
Admin end users can delete a seat to free it; standard end users cannot. To delete a seat, select the trash icon in the seat's row, then select **Deactivate**. The trash icon is disabled for the following seats, and its tooltip gives the reason:
* Offline seats. The end user releases them with a deactivation token from the offline application.
* Seats of a node-locked entitlement.
* Roaming seats before their end date. After the end date, a roaming seat on a concurrent entitlement can be deleted.
If a seat starts roaming after the page has loaded, Zentitle rejects the deletion and shows **Deactivation failed**.
#### Activity log
The **Activity Log** tab shows a **Usage Over Time** graph (when *Show activations graph* is enabled) and, for **Admin** end users when *Show activations log* is enabled, an **Activation History** table listing detailed activation and feature-usage events with filtering, column selection, and CSV export via **Download report**.
The activity log shows the end user the activity on the entitlement over time.
Activation history
### Logging out
In the top right-hand corner, the user can easily log out or reset their password.
---
# 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.nalpeiron.com/zentitle2-docs/premium-features/end-user-portal-eup/end-user-use-of-the-portal.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.
