<h2>Control specific app usage</h2><br/><div style="overflow-x:auto"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><head><meta content="text/html; charset=UTF-8" /><meta name="copyright" content="(C) Copyright 2026" /><meta name="DC.rights.owner" content="(C) Copyright 2026" /><meta name="generator" content="DITA-OT" /><meta name="DC.type" content="concept" /><meta name="DC.title" content="Control specific app usage" /><meta name="abstract" content="To support your organization's authentication policies, admins can control which mobile apps can log in to ServiceNow instances." /><meta name="description" content="To support your organization's authentication policies, admins can control which mobile apps can log in to ServiceNow instances." /><meta name="DC.date.created" content="2023-08-03" /><meta name="DC.date.modified" content="2024-08-01" /><meta name="DC.format" content="XHTML" /><meta name="DC.identifier" content="control-mobile-app-usage" /><link rel="stylesheet" type="text/css" href="../../../CSS/commonltr.css" /><title>Control specific app usage</title></head><body id="control-mobile-app-usage"> <h1 class="title topictitle1" id="ariaid-title1">Control specific app usage</h1> <div class="body conbody"><p class="shortdesc">To support your organization's authentication policies, admins can control which mobile apps can log in to <span class="ph">ServiceNow</span> instances.</p> <div class="p">To control which mobile apps can log in to <span class="ph">ServiceNow</span> instances, admins can choose either basic app allowance lists or advanced app allowance. The advanced allowance mode enables admins to add links to authorized apps. These two modes are described in the following sections.<div class="note important"><span class="importanttitle">Important:</span> <ul class="ul" id="control-mobile-app-usage__ul_ftk_nyl_ntb"><li class="li">The basic and the advanced app allowance modes should not both be configured on the same instance. If you configure both modes on the same instance, the system always prioritizes the advanced mode configuration over the basic mode configuration.</li><li class="li">This feature is available on both on-premises and cloud instances.</li></ul> </div> </div> <div class="section" id="control-mobile-app-usage__section_mmy_rmf_xrb"><h2 class="title sectiontitle">Basic app allowance lists</h2> <div class="p">By configuring a system property, admins can create a list of mobile apps that can connect to <span class="ph">ServiceNow</span> instances. If a user tries to connect to an instance with an app that isn't on the list, the user receives an <samp class="ph systemoutput">Unable to log in …</samp> message as shown in the following image. <div class="fig fignone" id="control-mobile-app-usage__fig_ugp_cnf_xrb"><span class="figcap"><span class="fig--title-label">Figure 1. </span>Failed login by an unauthorized app</span> <br /><img class="image" id="control-mobile-app-usage__image_vgp_cnf_xrb" src="../image/mobile-app-cant-connect2instance.png" alt="Mobile app login screen that shows the "Unable to log in" message." /><br /> </div> </div> </div> <div class="section" id="control-mobile-app-usage__section_jdz_knf_xrb"><h2 class="title sectiontitle">Advanced app allowance with links to permitted apps</h2> <p class="p">Using Scripted Extension Points, admins can create a list of apps that can log in to <span class="ph">ServiceNow</span> instances. Admins can change the <span class="ph uicontrol">Dismiss</span> link text to route the user to the appropriate mobile app. Using the link, end users can connect to an instance with an authorized mobile app.</p> </div> </div> </body></html></div>