> For the complete documentation index, see [llms.txt](https://docs.securepass.me/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.securepass.me/documentation/admin-user-guide/manage-license.md).

# Manage license

The licence defines the size and shape of your deployment. It is a signed file issued by eMudhra, and it carries the dates the deployment is valid between and the ceilings on what you can onboard — users, applications, systems, and databases.

SECUREpass enforces those ceilings. When a limit is reached, onboarding stops until an upgraded licence is applied. This page is where you check what you are entitled to and apply a new licence when the entitlement changes.

## The Manage License page

Select **Manage License** below the main navigation in the left panel.

![The Manage License page, showing the licence XML and the entitlement summary.](https://content.gitbook.com/content/W2srIAMN6RKFwvuEorV5/blobs/zrENSyv2ZhwUUEUcGid3/assets/01.png)

The page has two panes.

**Licence XML** holds the signed licence file itself. It is displayed read-only, with a copy control, and **Download XML** saves a copy. You would normally only need it when eMudhra support asks to see what is installed.

**Summary** is the readable version, and the pane worth knowing:

| Field                 | What it tells you                               |
| --------------------- | ----------------------------------------------- |
| Client Name           | The organisation the licence was issued to      |
| License Validity      | The dates the deployment is licensed between    |
| Product               | The licensed product                            |
| Version               | The licensed version                            |
| Licensed Users        | The maximum users that can be onboarded         |
| Licensed Applications | The maximum applications that can be registered |
| Licensed Systems      | The maximum systems that can be onboarded       |
| Licensed Databases    | The maximum databases that can be onboarded     |
| License ID            | The identifier of this licence                  |

An entitlement shown as **Unlimited** has no cap on that resource type.

{% hint style="warning" %}
**Note**

Check the validity end date against your renewal cycle rather than waiting to be told. A licence that lapses is not a billing inconvenience — it is a platform that stops accepting new onboarding while every authentication path in the organisation depends on it.
{% endhint %}

## Applying a new licence

{% stepper %}
{% step %}

### Open the update dialog

Select **Update License**.

![The Update License dialog.](https://content.gitbook.com/content/W2srIAMN6RKFwvuEorV5/blobs/fXBu63e6bksFZQfvLTwM/assets/02.png)
{% endstep %}

{% step %}

### Upload the licence file

Select **Click to upload**, or drag the file onto the panel. It must be **XML and under 5 MB**.
{% endstep %}

{% step %}

### Apply the licence

The dialog offers three actions:

| Action             | What it does                                                                                    |
| ------------------ | ----------------------------------------------------------------------------------------------- |
| Generate Unique ID | Produces the identifier for this deployment, which eMudhra needs before a licence can be issued |
| Cancel             | Closes the dialog without changing anything                                                     |
| Update License     | Applies the uploaded file. Stays disabled until a valid file is selected                        |

Select **Update License** and the new entitlements take effect. The Summary pane reflects them immediately.
{% endstep %}
{% endstepper %}

## Getting a licence issued

A SECUREpass licence is bound to the installation it runs on, so eMudhra needs to know which installation before they can issue one.

{% stepper %}
{% step %}

### Generate the unique ID

Select **Generate Unique ID** in the same dialog.

![The unique ID, ready to copy or download.](https://content.gitbook.com/content/W2srIAMN6RKFwvuEorV5/blobs/ZgW8xNrtzn2ln58y2Ye3/assets/03.png)
{% endstep %}

{% step %}

### Send the identifier to eMudhra

The identifier appears with **Copy** and **Download** beside it. Take a copy and send it to eMudhra with your renewal or upgrade request; the licence you receive back will be bound to this deployment and will not work on another.
{% endstep %}

{% step %}

### Keep the identifier

Keep the identifier with your deployment records. You will want it again at the next renewal, and it is quicker to have it than to go looking for it.
{% endstep %}
{% endstepper %}

## When a limit is reached

Reaching a cap does not degrade what is already running — existing users keep signing in and existing applications keep working. What stops is adding more of that resource type.

If onboarding fails and the reason is not obvious, check the Summary pane before looking anywhere else. A capacity ceiling reached quietly during a bulk import looks, from the console, much like a configuration fault.