On - Allows users to elevate privileges for a selected file. Enables Require approval and Require reason. Disables Block Run As Admin.

Off - Denies users the ability to elevate privileges for a selected file. Enables Block Run As Admin, which is how users with admin credentials can still elevate privileges.

On - Sends a request to the IT team, which must be approved before elevation is granted. Makes Require reason mandatory (i.e. must be On).

Off - Allows the user to elevate file privileges (and thus perform the action) as soon as the action is selected. For example, selecting "Run as administrator" to execute a program occurs immediately, without requiring approval. Makes Require reason optional (i.e. can be either On or Off).

On - Extends the authentication window and asks the user to enter email address, phone number and reason. Reason must comprise at least two words. This information is stored in the Auditlog.

Off - No reason is required by the user, but details of the actions performed are stored in the Auditlog.

On - Allows users to effectively become a local administrator for the number of minutes specified in Access time (minutes). Enables Require approval, Require reason and Access time (minutes).

Off - Denies users the ability to become a local administrator. Hides all other options under Admin Session.

On - Sends a request to the IT team, which must be approved before the request is granted. Makes Require reason mandatory (i.e. must be On).

Off - Allows the user to become a local administrator as soon as the request is made. Makes Require reason optional (i.e. can be either On or Off).

On - Extends the authentication window and asks the user to enter email address, phone number and reason. This information is stored in the Auditlog.

Off - No further information is required by the user, but user and computer details are stored in the Auditlog.

The maximum duration in minutes an Admin Session may last. This time must be sufficient for the user to install software or perform any other tasks that require elevation.

On - Additional email notifications are sent to the email addresses listed in Email addresses.

Off - Email notifications are not sent.

Standard email address format. Use a new line for each address.

A list of groups into which users are placed, with multiple groups on separate lines.

A list of groups into which computers are placed, with multiple groups on separate lines.

A list of organizational units into which users are placed, with multiple OUs on separate lines.

A list of organizational units into which computers are placed, with multiple OUs on separate lines.

On - Use the logo file selected under Logo file.

Add the file before turning this setting on.

Off - Do not use a logo file.

The name of the organization as it will appear in the portal and in Admin By Request dialog boxes on endpoints.

Use the Browse button to open an operating system File open dialog box. Locate and select a logo file.

Add a file here before turning on the Use logo file setting.

Auto-detect - The skin (light or dark) depends on what is currently being used by the operating system.

Light - Uses a light skin for Admin By Request dialog boxes.

Dark - Uses a dark skin for Admin By Request dialog boxes.

Follow Operating System - The skin (light or dark) depends on what is currently being used by the operating system.

Mandatory - Field appears in dialog boxes and must be filled-in.

Optional - Field appears in dialog boxes, but does not have to be filled-in.

Hide - Field does not appear in dialog boxes.

Mandatory - Field appears in dialog boxes and must be filled-in.

Optional - Field appears in dialog boxes, but does not have to be filled-in.

Hide - Field does not appear in dialog boxes.

On - Instructions are shown to the user per the period selected below via the drop-down. User clicks OK to close the instructions window.

Off - Instructions are not shown.

A title for the instructions window.

The instructions displayed to the user.

A frequency indicating when instructions are to be displayed:

• Show every time

• Show once a day

• Show once a week

• Show once a month

On - Instructions are shown to the user per the period selected below via the drop-down selection field. User clicks OK to close the instructions window.

Off - Instructions are not shown.

A title for the instructions window.

The instructions displayed to the user.

A frequency indicating when instructions are to be displayed:

• Show every time

• Show once a day

• Show once a week

• Show once a month

On - Includes an image with the illustrating how to select a program to "Run as administrator".

Off - No image is shown with instructions.

On - An Admin By Request icon is placed in the dock during installation.

Off - No icon is placed in the dock.

Confirm - User must confirm with Yes or No (or via the reason screen) to perform the operation..

Multi-factor Authentication - User must validate identity using MFA through Single Sign-on. Choosing this option unhides Multi-factor Configuration (see table below).

Authenticate - User must validate with credentials, face recognition, fingerprint, smartcard or similar..

Microsoft 365 / Entra ID - Use this as the SSO method.

-- ADD NEW METHOD -- - Create a new method. Choosing this option takes you to the portal's Single Sign-on (SSO) Setup page.

On - SSO authentication must match the email address from Active Directory or Azure AD.

Off - Email address does not need to match.

On - Admin privileges are removed for all users except those appearing in the Excluded accounts list..

Off - Admin privileges are not removed for users configured locally as administrators.

The account name(s) to retain local admin privileges. Multiple accounts must be specified on separate lines. Domain accounts must be prefixed with domain and backslash.

On - Users & Groups panel is not blocked for this user and will display.

Off - Panel is blocked for this user and will not display. No changes can be made.

On - Login Items panel is not blocked for this user and will display.

Off - Panel is blocked for this user and will not display. No changes can be made.

On - Network panel is not blocked for this user and will display.

Off - Panel is blocked for this user and will not display. No changes can be made.

On - Sharing panel is not blocked for this user and will display.

Off - Panel is blocked for this user and will not display. No changes can be made.

On - Startup Disk panel is not blocked for this user and will display.

Off - Panel is blocked for this user and will not display. No changes can be made.

On - Transfer or Reset panel is not blocked for this user and will display.

Off - Panel is blocked for this user and will not display. No changes can be made.

On - Wi-Fi panel is not blocked for this user and will display.

Off - Panel is blocked for this user and will not display. No changes can be made.

On - Remove the option to use a PIN Code to unlock an admin session or unlock a blocked application. If this option is Off and admin sessions are disabled, the system tray menu item to start an admin session will be removed.

Off - Allow access to the PIN Code unlock option (unless Allow Admin Sessions is Off under Authorization > AUTHORIZATION).

On - Forcibly close any sudo command or interactive sudo session at the end of the admin session.

Off - Do not force closure of sudo sessions.

On - Allow user to issue sudo commands from a terminal prompt.

Off - Do not allow user to issue sudo commands.

On - Support Assist is enabled.

Off - Support Assist is disabled.

The maximum duration in minutes a Support Assist session may last. This time must be sufficient for the assisting user to install software or perform any other tasks that require elevation.

If still running, Support Assist will be forcibly closed after this time, to make sure a session is not unintentionally left on-going.

On - Set the owner of the endpoint to the first person logging-in after the 24-hour stand-down period. Once set, only the Device Owner will be able to use Run As Admin or start an Admin Session.

Off - Device Owner will not be set regardless of who logs in.

On - The endpoint must be Intune-compliant to use Run as Admin or start an Admin Session.

Off - The endpoint is not required to be Intune-compliant.

On - When a user requests Run As Admin, the checksum of the file is evaluated. If the checksum is flagged, endpoint execution is blocked.

Off - The file's checksum is not evaluated prior to execution.

On - Unknown files will be uploaded to the OPSWAT cloud service for multi-engine malware scanning.

Off - Unknown files will not be uploaded.

IT Administrators have two options:

1. Quarantine: Send files to quarantine, allowing IT staff to look at the reported data, and assess whether this file should be allowed or not,

2. Permanently block: Block the file by choosing “Permanently block”. In this case, the file cannot be approved to run at all.

On - When malware is detected, additional email notifications are sent to the email addresses listed in Email addresses.

Off - Email notifications are not sent.

Standard email address format. Use a new line for each address.

On - .Relevant details about the application are logged.

Off - No logging is performed for this application.

On - The user must confirm elevation on the endpoint before the application can be run. This is the typical authentication window.

Off - The user does not need to confirm elevation on the endpoint before execution. Hides the Log to auditlog field.

Run As Admin application pre-approval - Pre-approve this application for Run As Admin.

Run As Admin vendor pre-approval - Pre-approve this vendor for Run As Admin.

Selecting this option enables the Vendor field and hides all other fields.

Enter vendor name. Adding the app via the Auditlog will auto-populate this field.

Prevent users from bypassing pre-approval by file renaming.

File must match vendor - The application name and the file name must align with the same details provided by the vendor.

File must match checksum - A checksum of a specific file version. If the file is updated, the checksum no longer matches and a new one must be collected.

No protection (not recommended) - Not recommended for anything except testing. The file can be located anywhere and is a file renaming vulnerability, in case a user is aware of (or can guess) the file name.

The name of the application. Mandatory, although used for convenience only to help identify applications in the list.

Enter file name.

Note that adding the app via the Auditlog will auto-populate this field.

Saves customization and changes to any fields.

Note that reloading any defaults does not take effect until Save is clicked.

On - Machine learning auto-approval is enabled.

A Run As Admin request will be automatically approved for apps that have been previously approved, provided the required number of Approvals has been met.

Off - Machine learning auto-approval is not enabled.

A "click and drag" scale that can take any value from 0 to 10.

The required number of times an application must be manually approved in order to be auto-approved in the future.

Approved email - Loads a template that advises the user (i.e. requester) that the request for access has been approved.

Denied email - Loads a template that advises the request for access has been denied without giving a reason.

Denied with reason - Loads a template that advises the request for access has been denied and provides the reason.

Administrator notify - Loads a template that advises the administrator (i.e. person who approves or denies) that a request for access is waiting for attention.

The email address to be used as the sender for the email. Can be used with custom domains. Use the Email address button to set up custom domains.

Refer to Email Domain for more information on configuring an email address to be used as the sender for all user notifications.

Text that will appear in the subject line of emails.

Loads the default Email template for the option selected.

NOTE:

• Default email templates are created by Admin By Request. Contact us if you wish to customize a default email template.

• Using this button will overwrite any customization you might have done in the Template body.

Switches to Email Domain in Tenant Settings in the portal, allowing you to use a custom domain as the sender.

This allows sending email from domains other than @adminbyrequest.com.

NOTE:

This is optional, but you cannot add an email sender field of e.g. "tom@mydomain.com" unless  you have first set up the custom email domain "mydomain.com" via the Email Domain setting in the portal (Settings > Tenant Settings > Email Domain).

The body of the email to be sent.

Includes three views:

• Design: WYSIWYG view of content. Enter and format body text here.

• HTML: The same content in HTML format. Can also be edited if necessary and changes will be reflected in Design and Preview.

• Preview: What the recipient sees. Read only - switch to Design view to make changes.

Dynamic content tags

Tags can be used in the body, which are place holders in curly braces. These are replaced with actual request values when emails are sent.

The following tags are available:

• {UserFullName} Name of requesting user

• {UserEmail} Email address of requesting user

• {UserPhone} Phone number of requesting user

• {UserReason} Reason the requesting user gave

• {DenyReason} Admin's reason for denial (only used for denial with reason)

• {ComputerName} Name of requesting computer

• {AdminUserName} Name of administrator receiving notification (only for admin notify)

The email address to which emails intended for your ticket system will be sent.

For example: itsupport@mycompany.com

The email address to be used as the sender for the email. Can be used with custom domains. Use the Email address button to set up custom domains.

Text that will appear in the subject line of emails.

Loads the default Email template for the option selected.

NOTE:

• Default email templates are created by Admin By Request. Contact us if you wish to customize a default email template.

• Using this button will overwrite any customization you might have done in the Template body.

Switches to Email Domain in Tenant Settings in the portal, allowing you to use a custom domain as the sender.

This allows sending email from domains other than @adminbyrequest.com.

NOTE:

This is optional, but you cannot add an email sender field of e.g. "tom@mydomain.com" unless  you have first set up the custom email domain "mydomain.com" via the Email Domain setting in the portal (Settings > Tenant Settings > Email Domain).