Alloy Self-Service Mobile App

On this page

The Alloy Self-Service app is the mobile app for Self Service Portal customers of Alloy Navigator. It is released for Android and iOS; install it from your device's app store. For the app's administration on the server, see Mobile App Configuration.

In the Alloy Self-Service app

Connect to your server

Before you begin, you need:

  • The address of your organization's API module, for example https://navigator.example.com/api.
  • Your user name and password, or a single sign-on account.

To sign in:

  1. Open the app and enter the URL, or tap Scan QR code next to the URL field to scan one instead.
    • A QR code that contains only the URL fills in the URL field; you then enter your user name and password or use single sign-on.
    • A QR code that also contains a user name fills that in too.
    • A QR code that yields no URL is rejected with Invalid QR Code.
  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.

Each single sign-on provider appears as a button reading Sign in with and the provider's name. The user name and password fields appear only when the server allows password sign-in; when both are offered, a row reading or separates them. While the app asks the server how it authenticates, and while it completes your sign-in, the sign-in screen is dimmed behind a spinner with a CANCEL button that cancels that step.

If the URL you enter redirects, the app follows one redirect and keeps the redirected address. The app signs you in as a Self Service Portal customer, not as a technician, and never asks you about concurrent sessions. If your server's version is older than 2022.1.0, the app refuses to sign in and names the required version in its message. 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; a sixth URL replaces the one used least recently. The sign-in screen offers one row per remembered URL, prefilled with a user name stored for it, and the user name field suggests the names you have used. Your password or single sign-on credential is kept in the device's secure storage, and is stored empty when keep me signed in is off. If you accept an untrusted certificate, that exception lasts seven days, after which you are asked again. On Android, the app also trusts CA certificates that you have installed on the device.

NOTE:

Some parts of the app depend on the server version. On an older server the app shows less rather than an error:

  • Version 2022.1.1 or later: your regional settings are applied.
  • Version 2022.2.0 or later: attachments are listed on records and offered on action forms. On an older server, search results are sorted by class on the device.
  • Version 2023.1.0 or later: the server supplies the maximum attachment size and the lookup-record limit, and category trees arrive already sorted.
  • Version 2025.1.0 or later: push notifications, the notification center, and the unread badge are available.

Home screen

The app bar greets you by name with your picture, or your initials when you have no picture, and carries a search box and, on a server running version 2025.1.0 or later, a notification bell; see Notifications Overview. Tapping a push notification, a search result, or an entry in Last Updates opens the matching record, except for Change Request, Approval Stage, and Asset records, which open nothing and show no error. If a notification is about a kind of record the app does not support, the app does not open it and tells you that objects of that class are either not supported or have been disabled in this app.

Below the app bar, the home screen shows, in this order:

  • Up to three buttons, each shown only when its module is on: Submit a Ticket opens the ticket creation action, Request a Service opens the Service Catalog, and Browse Solutions opens the Knowledge Base.
  • Announcements, when the Announcements module is on. See more opens the Announcements page.
  • Last Updates, always shown. See more opens My Updates, the full activity feed.
  • Popular Service Catalog Items, when the Service Catalog module is on. See more opens the Service Catalog page.
  • My Tickets, when the tickets module is on. See more opens My Items filtered to tickets.
  • Approvals, when the Approvals module is on. See more opens My Items on the approvals tab.
  • Popular Articles, when the Knowledge Base module is on. See more opens the Knowledge Base page.

Each portlet requests five records. A portlet with no records shows There are no items to display. instead of hiding. A portlet with one record shows it on a near-full-width card; two or more records appear on narrower cards in a row that scrolls horizontally. Pulling down on the home screen refreshes it; if any one portlet's data fails to load, the whole home screen is replaced with an Error page that shows the error instead of the other portlets. The back arrow on that page signs you out; it is the only way off the page.

The notification bell shows the number of unread notifications when there are any, shortened to thousands with K from 1,000 and to millions with M from 1,000,000, without rounding up (1,999 shows as 1K). Tapping the bell opens the notification center, which lists all your notifications, newest first; while it loads for the first time, the app shows Please wait.... A notification that arrives while the app is open updates the list and does not open anything.

  • An unread notification is shown in bold with a NEW badge.
  • Swiping a notification from start to end marks it read or unread; swiping it from end to start deletes it. Long-pressing it opens a menu with the same two actions.
  • The overflow menu offers Mark All as Read and Delete All. Delete All asks "Are you sure you want to delete all notifications?" first.

The bottom bar offers Home, a plus button, and Search. The plus button opens the creation actions Submit a Ticket, Request a Service, and Reserve Equipment, each offered only when its module (tickets, Service Catalog, and Library, respectively) is on. 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. My Assets lists the assets recorded against you.

The list of modules comes from the app's configuration on the server, which filters it by your organization's license before sending it, so a module the license does not cover is simply absent from the app. If the license covers neither ITSM nor ITAM, the list is empty: the home screen shows only the Last Updates portlet, and search and the plus button are turned off.

Search covers one scope at a time, chosen from a selector. It opens with no scope selected, asks the server for the list of scopes, and then selects the first one. A search runs only when a scope is selected and you have typed a pattern; clearing the pattern clears the results instead of searching again. Results appear as a single list in the order the server returns them (on a server older than version 2022.2.0, sorted by class on the device), with a divider between two results of different record classes rather than headings grouping them.

All is always offered as a scope and searches everything you may see. Modules add further scopes:

  • Tickets module: Tickets.
  • Service Catalog module: Service Catalog and Service Request.
  • Library module: Equipment and Equipment Reservation.
  • Approvals module: Approval Request.
  • Knowledge Base module: Knowledge Base.
  • Assets module: Assets.

The search box in the home screen's app bar shows the placeholder text Text to search for.... When the module list is empty, that search box is disabled.

My Items

My Items has a tab each for Tickets, Service Requests, Equipment Reservations, and Approval Requests, shown when the tickets, Service Catalog, Library, and Approvals modules are on, respectively. Each tab has its own view selector, which offers the views the server returns for that tab's class. A tab opens with the first view in its list, or with no view selected when no views are returned for its class. Changing the view on one tab does not change what the other tabs have selected.

The app does not remember a chosen view, tab, or search scope: it lasts only as long as you stay on the page.

Cards

Each type of record has its own card:

  • An announcement card shows the title, a two-line excerpt of the body, and Start Date: with the date; a high-priority announcement is shown in the error color. Opening it shows the title, the start date, and the full body; on a server running version 2022.2.0 or later, if the announcement has attachments, an Attachments tab is added.
  • A knowledge base article card shows the title, a view count beside the creation date, and a star rating out of five stars, rounded to the nearest whole star. Opening it shows, under a title bar that shows the article's ID rather than its title, the view count, the creation date, and the star rating again, the full article, and the prompt Was this article helpful? with YES and NO buttons. Once a vote has been cast, the prompt is replaced with Thank you for your vote:, a green thumbs-up or red thumbs-down icon for the vote, and the date of the vote. Voting also refreshes the whole home screen, not just the article's own rating. The app remembers which articles you have opened, so opening one again is not counted as a new view. The same attachments rule as for announcements applies to articles.
  • A Service Catalog item card shows a picture, the item's name, and a three-line description. If the item has a submit action, a Submit button on the card opens the action form directly, without opening the item's detail page. The detail page has an Actions button when the item has actions, which opens the same action form from a menu. Completing an action from the detail page, or from the card's Submit button, does not refresh what is on screen.
  • Approval, service request, ticket, and equipment reservation cards show a status chip when the record has a status. Tapping any of them opens the record.
    • An Approval card shows Due Date and Decision Date, each only when it has a value.
    • A Service Request card shows Submit Date, Due Date, and Completed Date, each only when it has a value.
    • A Ticket card shows Created Date, Modified Date, and Completed Date, each only when it has a value, and a requester row only when a requester is set.
    • Where an Approval or Ticket card shows the requester, the requester is shown with the person's picture, or with the person's initials when the picture does not load.
    • An Equipment Reservation card always shows its From: and To: rows, whether or not the dates are set.
  • An asset card shows the asset tag, a status chip, the name, class, and model; tapping it opens the linked configuration item, not the asset record itself.
  • A library item card shows the name, description, and type; tapping it opens the library item record.

Records

A record opens on Overview, Activities, and Attachments tabs, with an Actions menu; an asset opens on Overview and Tickets tabs instead. The menu offers the record's update actions, except that a record whose form is read-only in the portal offers none. An asset offers ticket creation actions, and a library item offers reservation creation actions, even when its form is read-only. Attachments on a record are read-only: you attach a file only through an action form that has an attachments control.

On the Overview tab, fields are grouped under section headers, starting with a General section. Tapping the preview of a long text or HTML field opens it full-screen for reading, titled with the record's caption; images in the text load from your server. Long-pressing a field value opens a Copy menu, and choosing it copies the value and shows Copied. An encrypted field, shown as asterisks, opens no menu and copies nothing, and the record's title cannot be copied this way.

Action forms

An action form opens from Submit a Ticket, from a Service Catalog item's Submit button or Actions menu, and from a record's Actions menu.

  • A long text or HTML field shows a three-line preview. Tapping it opens a full-screen editor titled with the field's caption; the check mark in the title bar puts your text into the form. A read-only field opens the same page without the check mark, and its text cannot be edited.
  • A form in steps has a Back button and a Next or Apply button.
  • When the server's validation of the action returns a message, the app shows it in a dialog. Closing an information message runs the action; a confirmation asks yes or no, and only yes runs it; closing an error leaves the action unrun. When several messages are pending, they appear one after another, and the last one decides.

When the form has an attachments control, which appears only on a server running version 2022.2.0 or later, the paperclip opens the device's file picker and the camera icon opens a camera page in the app; there is no option to pick from the photo gallery. When the device lets the app set the flash, the camera page offers Auto, Off, On, and Torch and remembers your choice. A photo goes through the same attachment size check as a picked file. A photo taken with the camera is deleted from the device after it is attached; a picked file is not.

A form can also carry an AI field. The app shows it from version 1.1.43 on; release 1.1.37 shows such a field as an ordinary field, with no prompt and no chat.

  • The answer appears under the field's caption as it is generated. When the field arrives empty, the app asks for an answer when the form opens.
  • Each finished answer, including a regenerated one, replaces the field's value at once; there is no step to accept it.
  • Once the answer is ready, Copy copies it as plain text and shows Copied, and Regenerate asks for a new answer; Regenerate is disabled when the field is read-only. Open chat appears only when chat is enabled for the field.
  • A link in the answer opens in the device's browser, not inside the field.
  • If an answer fails, an Error dialog shows the error. After CLOSE, the field holds whatever part of the answer had arrived, replacing its earlier value. Nothing retries on its own.

Open chat opens AI Chat Assistant, which starts with the field's current answer. Type in the box that reads Ask AI assistant anything... and send; you can send again only after the previous answer has finished. Each later answer offers Copy and Use this response. Use this response writes that answer into the field and closes the chat; nothing else said in the chat reaches the field. If a chat answer fails, the same Error dialog appears, and after CLOSE that answer keeps whatever part of it had arrived.