---
title: What users see after they login
slug: device-management-apple/what-users-see-after-they-login
createdAt: 2026-10-06T07:47:38.655Z
---

Depending on the user portal role enabled, device users may have a different view of the user portal.

## Welcome menu

The Welcome menu is in the top-right of the user portal. From this menu, you can perform the following actions:

- View Activity - View a list of all device activity. See [If Register Device role is enabled](docId:6OsRa8TBO_D9YEJA-SXYk).
- Helpdesk - Configure the help desk contact information to display in the user portal. See [Configuring help desk contact information](docId:4JxNfl3tsoSGF-UZbeIZ7).
- Settings - View user portal settings.
- Sign Out - Sign out of the self-service user portal.

## If Register Device role is enabled

If the <font color="#323232">Register Device</font> role is enabled, device users will be able to send an invitation from the user portal to register their device.

Figure: Send invitation to register

::Image[]{src="https://api.archbee.com/api/optimize/V3jJx_afLEcmDauLTrzss/243r8S8QGu6-rnybzVvip_userportalsendreginv105.PNG" position="flex-start" size="100" width="2404" height="1574" initialPath="../Resources/Images/UserPortalSendRegInv105.PNG" githubPath="Device Management Guide for Apple/Resources/Images/UserPortalSendRegInv105.PNG" darkWidth="2404" darkHeight="1574" showCaption="false" indent="1"}

After the invitation is sent, the device status is seen as <font color="#323232">Pending</font>.

Figure: Registration pending for device

::Image[]{src="https://api.archbee.com/api/optimize/V3jJx_afLEcmDauLTrzss/IX6XwHVD15ACVTh75oawS_userportalregpending.PNG" position="flex-start" size="100" width="747" height="441" initialPath="../Resources/Images/UserPortalRegPending.PNG" githubPath="Device Management Guide for Apple/Resources/Images/UserPortalRegPending.PNG" darkWidth="747" darkHeight="441" showCaption="false" indent="1"}

Device users can complete the registration on their mobile device at https\://\<EPMM\_Server\_FQDN>/go.

Figure: Complete device registration

::Image[]{src="https://api.archbee.com/api/optimize/V3jJx_afLEcmDauLTrzss/6IdDvwHfsL8ggm7_Cc1Xy_mwireg-registerdevice.png" position="flex-start" size="100" width="1577" height="793" initialPath="../Resources/Images/M@W_iReg-Register_Device.png" githubPath="Device Management Guide for Apple/Resources/Images/M@W_iReg-Register_Device.png" darkWidth="1577" darkHeight="793" showCaption="false" indent="1"}

After registration is completed on the mobile device, the status for the device is changed to <font color="#323232">Active</font>.

Figure: Active device status

::Image[]{src="https://api.archbee.com/api/optimize/V3jJx_afLEcmDauLTrzss/JzWtC_BX-1NxuNRnpM16U_userportalregactive.PNG" position="flex-start" size="100" width="739" height="419" initialPath="../Resources/Images/UserPortalRegActive.PNG" githubPath="Device Management Guide for Apple/Resources/Images/UserPortalRegActive.PNG" darkWidth="739" darkHeight="419" showCaption="false" indent="1"}

## Registration instructions

On iOS devices, Ivanti Mobile\@Work is installed only if it was set up for distribution through  Ivanti EPMM. If not, users can download Ivanti Mobile\@Work from the Apple App Store. Instructions for downloading Ivanti Mobile\@Work from the Apple App Store are provided in the email sent to the device user.

## If PIN-based registration is enabled

If PIN-based registration is enabled, device users will see <font color="#323232">Request Registration PIN</font>.

::Image[]{src="https://api.archbee.com/api/optimize/V3jJx_afLEcmDauLTrzss/jWtj1tTuAqXI2_7QyRkCj_userportal001reqregpin.png" position="flex-start" size="100" width="2430" height="1356" initialPath="../Resources/Images/UserPortal_001_ReqRegPIN.png" githubPath="Device Management Guide for Apple/Resources/Images/UserPortal_001_ReqRegPIN.png" darkWidth="2430" darkHeight="1356" showCaption="false" indent="1"}

Selecting <font color="#323232">Request PIN</font> allows device users to send an invitation for registration as well as generate a PIN.

Figure: Registration with pin

::Image[]{src="https://api.archbee.com/api/optimize/V3jJx_afLEcmDauLTrzss/3Ns4Elgz7_JzIejX4a7tU_userportalreqpinconfirm9400.jpg" position="flex-start" size="100" width="775" height="516" initialPath="../Resources/Images/UserPortalReqPINConfirm9400.jpg" githubPath="Device Management Guide for Apple/Resources/Images/UserPortalReqPINConfirm9400.jpg" darkWidth="775" darkHeight="516" showCaption="false" indent="1"}

Device users can complete the registration on their mobile device at https\://\<EPMM\_Server\_FQDN>/go. They will have to enter the PIN if prompted.

## If QR-code registration is enabled

If Quick Response (QR) code-based registration is enabled, device users will see <font color="#323232">Generate QR Code</font>. Selecting <font color="#323232">Generate QR Code</font> allows device users to complete the device registration process.

When users log into the Self-service portal (SSP) home page, they can select one of two registration buttons:

- Send Invitation – Receive registration information by SMS message and email.
- Generate QR Code – Scan to be redirected to the appropriate registration page.

Users scan the QR code and are redirected to a browser to enter their pin or password:

- iOS users: Once authenticated, iReg profile installation starts, completing device registration.
- Android users: Once authenticated, the user is redirected to Google Play to download the registration app. Users open the app to complete device registration.
  Figure: Registration with QR code

::Image[]{src="https://api.archbee.com/api/optimize/V3jJx_afLEcmDauLTrzss/QXDZBNCcZO6jIUfZZLpS2_userportalregqrcode.png" position="flex-start" size="100" width="2389" height="1368" initialPath="../Resources/Images/UserPortalRegQRcode.png" githubPath="Device Management Guide for Apple/Resources/Images/UserPortalRegQRcode.png" darkWidth="2389" darkHeight="1368" showCaption="false" indent="1"}

## If getting an Entrust derived credential is enabled

:::hint{type="info"}
This feature is not supported on macOS devices.
:::

If you enabled getting an Entrust derived credential in the System Manager, device users will see <font color="#323232">Request Derived Credential</font> when they receive their registration PIN for a device. Before using the registration PIN to register Ivanti Mobile\@Work to Ivanti EPMM, the device user should request a derived credential.

Figure: Request derived credentials

::Image[]{src="https://api.archbee.com/api/optimize/V3jJx_afLEcmDauLTrzss/DWL5TdFBpR9-Rd0OxTtNI_requestderivedcredential.jpg" position="flex-start" size="77" width="540" height="322" initialPath="../Resources/Images/RequestDerivedCredential.jpg" githubPath="Device Management Guide for Apple/Resources/Images/RequestDerivedCredential.jpg" darkWidth="540" darkHeight="322" showCaption="false"}

## Getting a derived credential

**Procedure**

1. Select <font color="#323232">Request Derived Credential.</font>
   The user is directed to the Entrust IdentityGuard self-service module URL that you specified in the System Manager.
2. The user interacts with the Entrust self-service portal to get a derived credential, including naming the derived credential.
   The Entrust self-service portal provides a Derived Mobile Smart Credential Activation Password.
   **Important:&#x20;**&#x54;he user must record this password for later use in activating the derived credential.
3. After recording the password, the user follows directions to indicate he is done.
   The user is directed back to the user portal. A brief message indicates whether getting the derived credential was successful. If it was successful, <font color="#323232">Request Derived Credential</font> is disabled.

The user then does the following:

1. Use Ivanti Mobile\@Work to register the device to Ivanti EPMM.
2. Use the PIV-D Entrust app on the device to activate the derived credential.

## If Change Device Ownership role is enabled

If the <font color="#323232">Change Device Ownership </font>role is enabled, device users will see the option to change the device ownership.

Figure: Change device ownership option

::Image[]{src="https://api.archbee.com/api/optimize/V3jJx_afLEcmDauLTrzss/U8RtV99JEbrYJ4tBba6rb_userportalresetappconnectpasscode.png" position="flex-start" size="100" width="1640" height="688" initialPath="../Resources/Images/UserPortalResetAppConnectPasscode.png" githubPath="Device Management Guide for Apple/Resources/Images/UserPortalResetAppConnectPasscode.png" darkWidth="1640" darkHeight="688" showCaption="false" indent="1"}

Selecting <font color="#323232">Change Ownership</font> allows the user to change the device ownership.

Figure: change device ownership settings

::Image[]{src="https://api.archbee.com/api/optimize/V3jJx_afLEcmDauLTrzss/nOzuaw_negIke7PsDCy42_userportalchangeownershipselect.PNG" alt="User Portal, change device ownership settings" caption="User Portal, change device ownership settings" position="flex-start" size="100" width="949" height="522" initialPath="../Resources/Images/UserPortalChangeOwnershipSelect.PNG" githubPath="Device Management Guide for Apple/Resources/Images/UserPortalChangeOwnershipSelect.PNG" darkWidth="949" darkHeight="522" showCaption="true" indent="1"}

## If Default ownership for devices is enabled for Device users

If your device administrator has enabled **Default ownership for devices registered at the user self-service portal** for Employees, you can modify the default ownership for the device, from **Employee&#x20;**&#x74;o **Company** and back. By default, that information is not editable by the device user. For information about the administrator settings on the Registration page, see "Understanding the Registration page" in the Devices chapter of Getting Started with Ivanti EPMM.

## If generating a one-time PIN for resetting the secure apps passcode is enabled

If you have configured Ivanti EPMM as described in [What is the self-service user portal?](docId\:xD00eTMsfNfOavY4Gu_kH), the device user sees the option <font color="#323232">Reset Secure Apps Passcode</font>. This option is among the device management actions presented to the user for iOS and Android devices.

Figure: Reset secure apps passcode

::Image[]{src="https://api.archbee.com/api/optimize/V3jJx_afLEcmDauLTrzss/U8RtV99JEbrYJ4tBba6rb_userportalresetappconnectpasscode.png" alt="Reset secure apps passcode" caption="Reset secure apps passcode" position="flex-start" size="100" width="1640" height="688" initialPath="../Resources/Images/UserPortalResetAppConnectPasscode.png" githubPath="Device Management Guide for Apple/Resources/Images/UserPortalResetAppConnectPasscode.png" darkWidth="1640" darkHeight="688" showCaption="true" indent="1"}

**Procedure&#xA0;**

1. Select <font color="#323232">Reset Secure Apps Passcode</font>.
2. On the next screen, select the button <font color="#323232">Reset Secure Apps Passcode.</font>
3. A dialog box displays containing the one-time PIN.
4. In Ivanti Mobile\@Work on an iOS device, or in the Secure Apps Manager on an Android device, follow the instructions for resetting a forgotten secure apps passcode.
5. When prompted for user credentials, enter the user name and the one-time PIN.
6. Follow the instructions to create a new secure apps passcode.

## What client users see after registering their device

The user portal displays:

- Icons for each device management action the user is allowed to perform.
- User and device information, including:
  - Device type (iPod touch, 4th gen in the example)
  - Status (Active, for example)
  - Last check-in (example, 2 hours ago)
  - Phone number
  - OS and version (to 3 digits, iOS 7.1.1, for example)
  - Carrier (for example, AT\&T)
  - IMEI value, if applicable
  - Manufacturer
  - Date the device was registered with Ivanti EPMM
- Accounts settings and certificates uploaded by the device user.
- Helpdesk contact information configured by the Ivanti EPMM administrator.

Figure: User portal showing user's device information

![User portal showing user's device information](https://api.archbee.com/api/optimize/V3jJx_afLEcmDauLTrzss/xQwJyMSWvqPt3lu0QjHqe_tpubs-2479trustuntrust.png "User portal showing user's device information")

