> For the complete documentation index, see [llms.txt](https://docs.cipp.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cipp.app/user-documentation/identity/administration/jit-admin/add.md).

# Add JIT Admin

This page grants time-limited administrative access. You choose who gets it, what they get, and when it ends, and CIPP acts on the account automatically at expiry. The result appears on the [JIT Admin](/user-documentation/identity/administration/jit-admin.md)README.md page for as long as CIPP is tracking it.

## Tenant and template

| Field                                      | Description                                                                                                                                                                             |
| ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Select a tenant to create the JIT Admin in | The tenant the access is granted in. Required, and it has to be chosen before the template list and the tenant's Temporary Access Pass policy can be read.                              |
| JIT Admin Template (optional)              | Applies a saved template, filling in the rest of the form. Templates are managed on the [JIT Admin Templates](/user-documentation/identity/administration/jit-admin-templates.md) page. |

{% hint style="info" %}
A default template is applied on its own once a tenant is selected. A template marked as the default for that specific tenant wins; failing that, a template marked as the default across All Tenants is used. Anything a template fills in can still be changed before submitting.
{% endhint %}

## User

**Would you like to create a new user or assign permissions to an existing user?** decides which fields follow. Creating a new account keeps the elevated access separate from someone's day-to-day account, which is usually the point of doing this.

| Field                 | Description                                                                                               |
| --------------------- | --------------------------------------------------------------------------------------------------------- |
| First Name, Last Name | The new account's name. Shown for a new user.                                                             |
| Username              | The part before the @ symbol. Shown for a new user.                                                       |
| Domain Name           | The domain the account is created under, chosen from the tenant's verified domains. Shown for a new user. |
| Usage Location        | The country the account is licensed in. Shown for a new user.                                             |
| User                  | The existing account the access is granted to. Shown when assigning to an existing user.                  |

## Access window

| Field      | Description                                                                                           |
| ---------- | ----------------------------------------------------------------------------------------------------- |
| Start Date | When the access begins. Required.                                                                     |
| End Date   | When the access ends and the expiration action runs. Required, and it has to be after the start date. |

## Roles and groups

**Admin Roles** and **Group Membership** are switches, and each reveals its own selector. At least one entry is required in whichever selector is turned on.

| Field  | Description                                                                                                                      |
| ------ | -------------------------------------------------------------------------------------------------------------------------------- |
| Roles  | The Entra ID directory roles to assign for the duration of the access.                                                           |
| Groups | The groups to add the account to for the duration of the access.                                                                 |
| Reason | Why the access was granted. Required, and it is shown on the JIT Admin list, which is what makes the list reviewable afterwards. |

{% hint style="warning" %}
Apply least privilege here. Grant the narrowest role that covers the work rather than reaching for Global Administrator, and keep the window as short as the task allows.
{% endhint %}

## Temporary Access Pass

**Generate TAP** issues a Temporary Access Pass so the account can sign in and satisfy a strong authentication requirement without a registered method.

The pass lifetime is worked out from the access window rather than entered, then clamped to what the tenant's policy allows. The form states how long the pass will be valid once both dates are set, and warns before you submit if Temporary Access Pass is not enabled in the tenant, in which case generation fails.

{% hint style="info" %}
Temporary Access Pass has to be enabled in the tenant's authentication methods policy first. The templates include an "Enable Temporary Access Passwords" standard that turns it on.
{% endhint %}

## Expiry and notification

| Field               | Description                                                                                 |
| ------------------- | ------------------------------------------------------------------------------------------- |
| Expiration Action   | What happens to the account when the window closes. Required.                               |
| Notification Action | How you are told the JIT admin was created: Webhook, Email or PSA. Several can be selected. |

The expiration action offers **Delete User** and **Disable User** for any grant. Depending on which switches are on, it also offers **Remove Roles**, **Remove Groups**, or **Remove Roles and Groups**, so the account itself survives and only the elevation is taken away. Changing the switches after choosing clears the selection, since the option may no longer apply.

{% hint style="info" %}
Notification channels only deliver if they are configured in CIPP's [Notifications](/user-documentation/cipp/settings/notifications.md) settings first. Selecting one that is not set up produces no notification rather than an error.
{% endhint %}

***

## Feature Requests / Ideas

We value your feedback and ideas. Please raise any [feature requests](https://github.com/CyberDrain/CIPP/issues/new?template=feature.yml) on GitHub.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.cipp.app/user-documentation/identity/administration/jit-admin/add.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
