How to use the Alloy Self-Service mobile app

On this page

The Alloy Self-Service app is the mobile app for Self Service Portal customers. From one home screen, portal users submit tickets, request services, search the knowledge base, follow their approval requests, reserve equipment, look at their assets, and read announcements, as far as the modules you offer allow. An administrator checks that the server is ready for the app and chooses which modules it offers in the Admin Center, then hands out the API URL. Portal users install the app, sign in with the URL, and start from the home screen.

Before you begin

  • The app reaches the server through the API module, which must be installed and configured for Access Token authentication. When the URL entered in the app answers with a Windows authentication challenge, the app shows "Make sure the URL points to Alloy Navigator API configured for Access Token authentication". See System Requirements and Install the API.
  • Each user of the app needs a Self Service Portal customer account. See Create and Maintain Customer Accounts.
  • The app does not need a Self Service Portal web site. You can offer it as the only self-service channel or together with the portal.
  • The app refuses to sign in to a server older than version 2022.1.0. Some parts of the app need a later server version; for example, push notifications need version 2025.1.0 or later. See the note in Connect to your server.
  • What the app offers depends on your license: the server keeps only the modules the license allows. If the license covers neither ITSM nor ITAM, the app shows only the Last Updates portlet, and search and the plus button are turned off.
  • To open the Admin Center, your account needs the Basic administrative access permission. Managing mobile application records requires the Mobile Applications administrative permission ("Allows managing Mobile Applications"); in the Admin Center, the server also checks the access policy for administering services. See Who may open each application and Permissions Reference.

Check the app's configuration record

The app reads its configuration from the mobile application record with the application id SelfServiceMobile. A record with an empty URL mask always qualifies; a record with a URL mask qualifies when the mask appears, compared without regard to case, inside the API URL the app connects with. The first qualifying record wins; when no record qualifies, the app's configuration request fails.

In the Admin Center:

  1. Go to Services and Integrations > Mobile Applications. The page lists the records.
  2. Open the SelfServiceMobile record. The drawer is titled with the application id, and its section reads "Mobile Application ID:" followed by the id.
  3. If the record has a URL Mask, check that the mask appears in the API URL you are going to hand out.

A database upgraded from a version before 2022.1 has no SelfServiceMobile record until you import one. The Admin Center's Mobile Applications page has no New button; you bring records into a database with Import Settings… in the Settings App. See Export and import records.

Choose the modules the app offers

The SelfServiceMobile configuration has two blocks, <Views> and <Modules>. <Modules> holds one <Module Name="…"/> line per module, and the installed modules alone decide which buttons, portlets, drawer entries, and search scopes the app shows. The list is a request: the server keeps only the modules the license allows, and a module you list but the license does not allow is silently absent. For the module names, the modules each license allows, and what each module turns on in the app, see Licensed modules.

In the Admin Center:

  1. Go to Services and Integrations > Mobile Applications and open the SelfServiceMobile record.
  2. In Configuration, add or remove <Module Name="…"/> lines in the <Modules> block.
  3. Save your changes.

Configuration is required: left empty, it fails with "The "Configuration" field is mandatory, it can't be left blank." The page makes no other check on the configuration text.

The server reads the module list at every configuration request, so a module line you remove takes the entries that module turns on out of the app. A license change reaches the app after the API process restarts. The <Views> block names the views the app offers in its view selectors, such as those on the tabs of My Items; the server keeps the views it has read until the API process restarts, so a changed view reaches the app after that restart. See Self-service app configuration.

Hand out the API URL

Users need the API URL, the address of the API module (for example https://navigator.example.com/api), for their first sign-in. Give it to them as text or as a QR code that they scan in the app; a QR code can also carry the user name to prefill. How to find the URL, encode it, and hand the code out is described in How to generate QR code for Alloy mobile apps.

Install the app and sign in

Users install the app from their device's app store; it is released for Android and iOS.

In the Alloy Self-Service app:

  1. Open the app and enter the URL, or tap Scan QR code next to the URL field to scan one instead.
  2. The app asks the server how it authenticates and then offers password sign-in, single sign-on, or both, depending on what the server allows. If it cannot get that answer, it offers password sign-in only.
  3. Enter your credentials, or sign in with single sign-on.

The app signs you in as a Self Service Portal customer, not as a technician. On a server running version 2025.1.0 or later, signing in also asks for permission to send you notifications. The app remembers up to five server URLs, and every user who has signed in through each one; the sign-in screen offers one row per remembered URL. For what a QR code fills in, see Connect the Alloy Self-Service app; for redirects, certificates, and keep me signed in, see Connect to your server.

Get started on the home screen

After sign-in, the home screen opens. Its app bar greets you by name and carries a search box and, on a server running version 2025.1.0 or later, a notification bell. Below it, the home screen shows up to three buttons, Submit a Ticket, Request a Service, and Browse Solutions, and then the portlets Announcements, Last Updates, Popular Service Catalog Items, My Tickets, Approvals, and Popular Articles. Each button and each portlet except Last Updates is shown only when its module is on. The bottom bar offers Home, a plus button, and Search, and the navigation drawer holds Tickets and Requests, My Assets, Knowledge Base, Service Catalog, Reserve Equipment, About, and Sign Out; each of the first five appears only when its module is on. See Home screen.

From there, portal users:

  • Submit a ticket: Submit a Ticket on the home screen or under the plus button opens the ticket creation action. See Action forms.
  • Request a service: Request a Service opens the Service Catalog. When a Service Catalog item has a submit action, the Submit button on its card opens the action form directly.
  • Find answers: Browse Solutions opens the Knowledge Base. Search covers one scope at a time: All, which is always offered, or a scope that one of your modules adds. See Search.
  • Reserve equipment: Reserve Equipment under the plus button and in the drawer, when the Library module is on.
  • Follow their tickets, service requests, equipment reservations, and approval requests: My Items has a tab for each, shown when its module is on. A record opens on Overview, Activities, and Attachments tabs, with an Actions menu for its update actions; a record whose form is read-only in the portal offers none. See My Items and Records.
  • Look at their assets: My Assets in the drawer lists the assets recorded against them; an asset offers ticket creation actions.
  • Read announcements: the Announcements portlet, and See more for the Announcements page.

What you have now

Your portal users are signed in to the Alloy Self-Service app, which offers the modules that the SelfServiceMobile configuration lists and the license allows. Each device that signed in is registered for the person. On a server running version 2025.1.0 or later, a push notification that targets the app goes to each of the recipient's devices registered for it. The Person record in the Web App lists the devices registered for the person, and you can delete a registration there. See Registered devices and Push Notifications.