Administration Guide

Branding, Styles and Language

On this page

You can change how the Alloy Navigator applications look and which language and formats they use:

  • The logo at the top of the Web App and of each Self Service Portal instance, the color theme of each Web App and portal instance, and the title and header image of a portal instance. The Admin Center's header and main menu take the color theme of a Web App instance.
  • The CSS styles of announcements, knowledge base articles, service catalog items, outgoing HTML notifications, and the Web App's preview pane.
  • The installation's display language and its currency and duration formats, and the languages of each portal instance.
  • The logo and the locale of reports.

The Admin Center holds the logo and color theme pages, the CSS Styles page, and Language & Region. The Settings App has its own CSS Styles editors, a Regional Settings node with the currency and duration formats, and Report Settings, with the report logo and the default report locale. The Admin Center also has a Report Settings page under General; see Report Settings. For how the two administration applications relate, see Admin Center and Settings App.

In the Admin Center, CSS Styles and Language & Region are each gated by their own permission, and in the Apps and Portals menu group the Web App and Self Service Portal families are each gated by their own configuration permission. In the Settings App, the CSS Styles folder and the Regional Settings and Report Settings nodes under General are each gated by their own right. See Permissions Reference.

In the Admin Center

Set the logo of the Web App or a portal

The logo at the top of the Web App and of each Self Service Portal is set per instance, on the instance's Logo page.

  1. In the main menu, open Apps and Portals, choose Web App or Self Service Portal, and choose the instance. When only one instance exists, the menu shows that instance's pages directly. When no instance of the family is configured, a screen that links to the family's installation guide appears instead of the instance's pages.
  2. Open Logo.
  3. Load a custom image into the image field. Supported formats are PNG, JPG, BMP, and SVG, and a file of another type is refused. The logo area is 50 pixels high; larger images are scaled down, keeping the aspect ratio.
  4. Click Save, which appears with Cancel once you change the image.

On a portal instance's Logo page, Restore puts back the logo of the portal's default settings. Restore is unavailable while the logo already is the default one. The Web App's Logo page has no Restore.

Once you change the image, each page states when the change takes effect: within an hour for the Web App, and within a few minutes for a portal. Users can do a hard refresh in the browser (for example, Ctrl+F5) to see the change at once.

The logo at the left end of the Admin Center's own top bar is the logo of the Web App instance the Admin Center belongs to. The Admin Center is installed within a Web App instance's site, and the Web Configuration tool links it to that instance when it configures the instance. The top bar shows the image saved on that instance's Logo page, up to 50 pixels high and 200 pixels wide, or the Alloy logo when that instance has no logo. Logos of Self Service Portal instances do not appear there. The browser keeps the last logo it received and shows it until the current one arrives.

Set a portal's title and header image

A Self Service Portal instance has Title and Header pages beside Logo:

  • Title holds Title and Subtitle. The title appears at the top of each page next to the logo, and the subtitle just below it in a smaller font. The page recommends a title under 50 characters and a subtitle under 80 characters; it does not enforce these lengths.
  • Header holds the image at the top of the portal's homepage. To load an image, drop a file on the image box ("Drop an image here, or click to select a file"), click the box, or click Upload. Supported formats are PNG, JPG, BMP, and SVG, and a file of another type is refused. The header image area is 1600 pixels wide and 330 pixels high; larger or smaller images are resized to fill the area and centered, keeping the aspect ratio. Restore puts back the image of the portal's default settings; it is unavailable while the image already is the default one.

To keep a change, click Save; Save and Cancel appear once you change a value. Changes on these pages take effect within a few minutes after saving, and a hard refresh in the browser shows them at once.

Choose a color theme

Each Web App instance and each Self Service Portal instance has a Color Theme page, under Apps and Portals, the family, and the instance. The two families offer different colors.

  • A Web App instance's Color Theme page chooses the color theme of the Web App. It offers ten named colors: Ocean Blue, Sky Blue, Cyber Grape, Violet Iris, Bordeaux Red, Jungle Green, Dark Slate Green, Slate Gray, Dark Gray, and Sand Cream. When you choose one, the page shows a preview picture of that theme. The change takes effect within an hour after saving, and users can do a hard refresh in the browser (for example, Ctrl+F5) to see it at once.
  • A Self Service Portal instance's Color Theme page offers eight named colors: Ocean Depth - Default, which is the default, and Alien Eyes, Bordeaux, Dark Side, Fresh Iris, Jungle, Lotus, and Soho Lights. When you choose one, the page's preview is recolored. The preview shows a header strip in the theme's color with the instance's logo, the instance's header image beneath it, and a sketch of the portal's page over both. The change takes effect within a few minutes after saving, and the page adds that users can do a hard refresh in the browser (for example, Ctrl+F5) to see it at once.

On both pages, Save and Cancel appear once you choose another color; click Save to keep the choice.

In the portal, the color theme colors the bar at the top of every page except the sign-in pages. The sign-in pages have no such bar; there the theme colors only the strip with the logo at the top of the sign-in box, and the page background is the same for every theme. Light or dark mode is not part of the theme: it is kept in each visitor's browser as light, dark, or the system setting.

The Admin Center's own header and main menu take their colors from the color theme of the Web App instance the Admin Center belongs to, the same instance whose logo its top bar shows (see Set the logo of the Web App or a portal). When that instance has no color theme saved, or the Admin Center is not linked to a Web App instance, they use the colors of Ocean Blue. Saving a Web App instance's settings makes the Admin Center you save from load the theme again, so a new theme for that instance shows in its header and menu. The browser keeps the last theme it received and starts with it on the next visit. Otherwise, an open Admin Center treats the theme it received as current for an hour.

Edit CSS styles

CSS Styles, under General, edits the style sheets of these targets:

  • Announcement, Knowledge Base Article, and Service Catalog Item, each with a Web App, a Self Service Portal, and a Mobile Apps variant.
  • Outgoing HTML Notifications.
  • The Web App's preview pane, in a horizontal and a vertical variant.

To edit a style sheet:

  1. Open General > CSS Styles. The page opens on the Web App style of Announcement.
  2. Choose the target and its variant.
  3. Edit the CSS in the editor. The editor's toolbar also offers:
    • Export, which saves the current CSS to a .css file named after the target.
    • Import, which loads a file's text into the editor.
    • Restore Default, which replaces the text with the target's built-in default CSS. It is unavailable when the target has no default or the text already equals it.
  4. Save the change from the action bar, which appears once you edit the text.

The action bar notes that changes take effect in a few minutes after saving. For the Web App variants and the preview pane targets, it adds that users can do a hard refresh in the browser (for example, Ctrl+F5) to see the changes at once.

Set the display language and regional formats

Language & Region, under General, is one form of three sections: Language, Currency format, and Duration format. The currency and duration formats apply to the whole installation; there is no per-user currency format.

  1. Open General > Language & Region.
  2. Under Language, choose the Display language: English - United States or Spanish. The section is marked Preview.
  3. Under Currency format, set the four values:
    • Currency symbol.
    • Positive currency format (four choices) and Negative currency format (16 choices). Each choice is shown as the sample 1.1 with the current symbol.
    • No. of digits after decimal, a whole number from 0 to 4.
    • Reset fills the four fields with currency settings taken from the regional settings that the Admin Center's server process runs with at that moment, not from a stored value.
  4. Under Duration format, enter Time duration format and When duration is less than 1 hour. The page does not check what you enter. See Duration formats.
  5. Click Save and Restart. Save and Restart and Cancel appear once you change a value.

If you changed the display language, a dialog shows Applying New Language and then Import Completed, and a restart follows. The dialog's only button, Close, is unavailable while the language is being applied. If you did not change the display language, the first Web App instance restarts.

IMPORTANT: Save and Restart starts the language import or the restart in the same click as the save, without waiting for the save to finish, so the import or the restart runs even if the save fails. Before you rely on the language import or the restart, check that the save completed.

When no value has been saved yet, the display language is English (United States), and the page shows the symbol $, 2 digits after the decimal, the first positive and the first negative format, and empty duration formats.

The display language changes:

  • The Web App's interface texts, for every technician. The Web App has no language selection of its own.
  • The labels of object fields. Statuses, actions, forms, views, and other configured names keep the names they were configured with.
  • The Admin Center's own language. The Admin Center falls back to the browser's language and then to English (United States), and a text without a translation appears in English.

Saving Language & Region also sets the default language of every Self Service Portal instance to the display language and adds that language to the instance's languages. Once the display language is stored, the portal uses it as its default language ahead of the instance's Default language.

Duration formats

Both duration fields hold a template. When duration is less than 1 hour applies to durations under 60 minutes, and Time duration format to 60 minutes and more. In a template, these tokens stand for parts of the duration:

Token Stands for
%H% Hours
%HH% Hours, two digits
%N% Minutes
%NN% Minutes, two digits

All other text is printed as written. Without the percent signs, HH and NN are plain text.

The templates format the duration placeholders of notifications and other templates, and the durations in the Web App's grids and forms. These read a template differently in some cases:

  • Notifications and templates accept the tokens in any case, so %nn% works like %NN%. The Web App recognizes them only in uppercase.
  • In notifications and templates, hours are split out only when the duration is 60 minutes or more and the template has an hour token; otherwise all the minutes go into the minutes token, and an hour token prints nothing. So when Time duration format has no hour token, 90 minutes under %N% min reads "90 min". The Web App's grids and forms drop the hours instead: 90 minutes under %NN% min reads "30 min".
  • The Web App's grids and forms remove an hour token from When duration is less than 1 hour.
  • The Web App's grids and forms replace only the first occurrence of each token.
  • The Web App's preview form built on the server, the grid columns rendered on the server, and computed time fields read a template in a third way: they replace every occurrence of a token, write the sign in front of a negative duration, and, for an empty template, show 0:<minutes> under an hour and <hours>:<minutes> from an hour up. They pass only the minutes to When duration is less than 1 hour, so a template there that holds an hour token makes their formatting fail.
  • In notifications and templates, a negative duration starts with "- ".
  • An empty template prints nothing in notifications and templates. In the Web App's grids and forms, an empty template shows the bare minutes under an hour and <hours> : <minutes> from an hour up.
  • The Web App picks up a change to either template only after its application process restarts.

When the duration formats have never been saved, durations read as %H%:%NN%, and as 0:%NN% under an hour.

A new 2026.1 database created with the Default Workflow has both templates saved: Time duration format is set to %H%h %NN%m and When duration is less than 1 hour to %NN%m in the supplied configuration, so 135 minutes reads "2h 15m" and 5 minutes reads "05m". An upgraded database need not have these values, and an administrator may have changed them.

Manage portal languages

Each Self Service Portal instance has a Languages page, under Apps and Portals > Self Service Portal > the instance.

  • Default language is the instance's default display language. It offers only the languages checked under Additional languages. When the installation's display language is stored, the portal uses that language as its default instead.
  • Additional languages lists every stored language in alphabetical order of the name the page shows; the default language keeps its alphabetical place and is shown in bold. The checked ones are the display languages available to the portal's users. The default language's box is always checked and cannot be cleared. The portal's own language list shows the checked languages by their stored names, in the order of their language codes; for a language it knows, the Languages page shows its own name for the language instead.
  • Only the default language and the checked languages wait for you to save the page; they take effect within a few minutes after saving. Import, Export, and Delete act at once.
  • Import language takes one .json file. The language's code is read from the file's Formats.Id and its name from Formats.Description; a file without either is refused, and a file that does not parse shows "The file content is invalid." A file with a new code adds a language, which no portal user is offered until you check it under Additional languages and save. A language whose code is not one of the 31 codes the portal knows still works: its texts come from the file, and its date picker and calendar use those of the default language, then of English (United States). A file with a code already stored replaces that language's content after Replace language?, and the stored name stays.
  • A language's menu offers Export, which downloads the language as <code>.json, and Delete, which deletes it after "Are you sure you want to delete the selected item?". Delete is not offered for English (United States) or for the default language.

A running portal picks up a saved change or an import within a few minutes, without a restart.

Change a portal text

A portal language file is one JSON document. The portal reads only three things from it: Formats.Id, the language code; Formats.Description, the language's name at its first import; and Terms, a list of entries that each hold a key and a text. The file's name is not read. An entry with an empty key is ignored, and when a key appears more than once, only its first entry is used.

  1. In the language's menu, choose Export.
  2. In the file, change the text of an entry, or add an entry with its key and text to Terms.
  3. Click Import language, choose the file, and confirm Replace language?. The import replaces the whole language, so the file must keep every entry it had.

The keys follow the portal's areas: TICKETS (Incidents), SERVICES (Service Requests), RESERVATIONS, APPROVAL, LIBRARY, and ASSETS.

Text Key
A column caption in a view <AREA>.GRID.<field name>, the field name as the view configuration names it; for example, TICKETS.GRID.<field name> for a column of an Incident view
A view's name <AREA>.VIEWS.<view name>, with spaces written as _
An action in a create or action list <AREA>.ACTION.<number>
An action form's caption <AREA>.FORMS.<form name>.FORM.CAPTION, the form name in uppercase with spaces written as _
An action form's instruction <AREA>.FORMS.<form name>.FORM.INSTRUCTION, then FIELDS.COMMON.FORM.INSTRUCTION
A field caption on an action form <AREA>.FORMS.<form name>.<field>, then FIELDS.COMMON.<field>, each also in uppercase, then <AREA>.FORMS.<form name>.<NAME> and FIELDS.COMMON.<NAME> with the field's name in uppercase; the field is its virtual name with spaces written as _, or else its id. A hint adds _HINT to the first four keys
A section of an action form The section's name with spaces written as _ in place of the field
A text element on a form The element's id alone, with no prefix
A $$<name>$$ placeholder in a view form's text FIELDS.COMMON.<NAME>, then FIELDS.COMMON.<NAME>_ID
A view form's texts The prefix <AREA>.FORMS.VIEW_FORM in place of <AREA>.FORMS.<form name>

A column or view key is also tried in uppercase. An action or form text with no entry keeps its configured wording, and a column caption with no entry falls back to the field's caption. A service catalog request form opened to create a request uses the area SERVICES_CATALOG. A form that has no name takes its caption, as written, in place of the form name.

In the supplied language file of the language the portal is built in, some entries carry the mark isWorkflowKey: view column keys other than shared ones, form keys other than captions, and business-logic terms. The portal skips marked entries in its default language. An entry you add carries no mark, so it applies in the default language as well.

In the Settings App

Edit CSS styles

  1. In the navigation, open General > CSS Styles, and then the editor: Announcement, Knowledge Base Article, Service Catalog Item, Preview Pane, or Outgoing HTML Notification.
  2. Select the style sheet row. Announcement, Knowledge Base Article, and Service Catalog Item have the rows Web App, Self Service Portal, and Mobile Apps. Preview Pane and Outgoing HTML Notification have one row, CSS.
  3. Edit the style sheet in the text box. To replace the row's text with a file's, click Load From File... and pick the file in Load Stylesheet from.... The text is loaded into the row but not yet saved.
  4. Click Apply. It is available while the row has unsaved changes.

Save To File... saves the row's text through Save Stylesheet to..., proposing a name such as Announcement.css, and asks before it overwrites a file. If you select another row while the text has unsaved changes, the Settings App asks "You should save your changes before leaving this page. Do you want to save the changes?": Yes saves, No discards. A row that has no style sheet gets an empty one when you first select it.

The Web App's preview pane does not use the style sheet saved in the Preview Pane editor; its preview pane styles are edited in the Admin Center (see What the style sheets style).

Set the currency and duration formats

Regional Settings, under General, edits the same installation-wide currency and duration formats as the Admin Center's Language & Region page. It has no display language; see Set the display language and regional formats.

  1. In the navigation, open General > Regional Settings.
  2. Under Currency format, set the values:
    • Currency symbol:.
    • Positive currency format: and Negative currency format:, two lists whose choices are shown as a sample amount with the current symbol.
    • No. of digits after decimal:, at most 4.
    • Reset returns the currency format to its default values.
  3. Under Duration format, enter Time duration format: and When duration is less than 1 hour:. See Duration formats.
  4. Click Save on the Settings App toolbar. It becomes available once you change a value.
  5. Restart Internet Information Services (IIS) on the web server. The page notes: "To apply new regional settings to all Alloy web and mobile apps, restart Internet Information Services (IIS) on your web server." Unlike Save and Restart in the Admin Center, Save here restarts nothing.

Set the report logo and the default report locale

Report Settings, under General, holds the report logo and the default report locale:

  • Report logo: Load... opens Load logo from file... for a BMP, JPEG, or PNG image. Save as... saves the current logo to a file, named AlloyLogo by default. Clear removes the logo after "Are you sure you want to remove the logo?". Save as... and Clear are available only while a logo is shown.
  • URL: is the address the logo links to in every shipped report that shows the logo. A new database has https://www.alloysoftware.com. With an empty URL, reports still show the logo, without a link target.
  • Default report locale: Locale: lists the locales known to Windows, plus a stored locale that is not among them. Reports show dates, numbers, and currency in this locale unless a report sets its own language. The Database Management tool fills an empty report locale with the system locale of the computer it runs on.

In the shipped reports, the logo is drawn in a box half an inch high and scaled to fit, keeping its aspect ratio. Report Settings is not included in a configuration export.

What the style sheets style

  • The Web App's preview pane wraps the previewed content in an element with the id preview, so a rule that begins with #preview styles only the preview content. A previewed knowledge base article, announcement, or service catalog item uses the Web App style of its own target. Any other record uses the preview pane style, horizontal or vertical according to the pane's layout. The preview pane styles are edited in the Admin Center, not in the Settings App's Preview Pane editor.
  • In the Web App and the mobile apps, a knowledge base article or an announcement is built from the body template of its style sheet. In a new 2026.1 database created with the Default Workflow, that template puts only the article or announcement text inside an element with the id kbarticle or announcement; the title and the #created, #appliesTo, and #attachments blocks sit beside it. A rule that begins with #kbarticle or #announcement therefore styles only the text: #announcement p reaches the announcement text but not its header or its attachment list.
  • When a technician edits the HTML field of a knowledge base article, an announcement, or a service catalog item on its full form in the Web App, the editor is styled with the Web App style of that target, with #kbarticle, #announcement, or #servicecatalog removed from its rules. A rule scoped to that id therefore also styles the text being edited.
  • The style sheet saved in the Settings App's Outgoing HTML Notification editor is applied to every e-mail created in HTML format, whatever the e-mail service: workflow e-mail notifications created in HTML format (a notification that uses an e-mail template always is), mention e-mails, and the self-registration and account e-mails. Administrative alerts, test messages, and e-mailed reports are created as plain text and never carry it.

When the Database Management wizard upgrades a database from a version earlier than 8.4.0, it first exports the existing style sheets to a local Styles backup folder. It then overwrites each existing style sheet for which the product supplies one, together with its body template, with the supplied version. The wizard's last page names the backup folder.

Language and format scopes

Language settings apply at these levels:

Scope What it decides Where it is set
Product The languages of the Web App and the Admin Center: English (United States) and Spanish The product build
Portal languages The languages that portal instances can offer Import language on a portal instance's Languages page
Installation The display language: the Web App's texts for every technician, field labels, and the Admin Center Display language on Language & Region
Portal instance The instance's default language and the languages its users may choose The instance's Languages page; saving Language & Region resets the default, and a stored display language is used ahead of it
Portal user The user's own language, and whether dates, times, and numbers follow the browser's language The user's portal profile

Technicians do not choose a language in the Web App. Their own date and time display options are personal settings; see Personal Settings.

The currency format (symbol, digits after the decimal, positive and negative formats) is set once for the installation, on the Admin Center's Language & Region page or the Settings App's Regional Settings node, and each application applies it in its own way:

Where Dates, times, and numbers Currency
Web App The browser's first preferred language, adjusted by the technician's own date and time options All four values. Decimal and grouping separators follow the browser's language. A grid row that carries its own currency code shows that code instead of the symbol, and a read-only form field shows the symbol only when its currency code is the default code.
Self Service Portal The language the user picked, else the first of the browser's languages that the instance offers, else the portal's default language. With Display dates, times, and numbers according to my browser locale selected in the user's profile, the browser's first language formats values while the texts stay in the picked language The symbol and the digits after the decimal (at most 4) only; the symbol's placement and the minus sign follow the formatting language. A value in a currency other than the default one is shown with its three-letter code
Alloy Navigator app and Alloy Self-Service app The device's locale All four values, unless a money field on a record's page sets its own. The decimal separator is a period, with no grouping separator. An amount is cut at the number of digits after the decimal, not rounded.
API Date-time values as yyyy-mm-ddThh:nn:ss with the offset of the API instance's time zone; dates as yyyy-mm-dd; money and decimal values with a period and no grouping Not applied to values; the API returns the four values for the mobile apps to use
Settings App, Automation Server, Import Wizard, connector and job programs The Windows regional settings of the account that runs the program All four values. The decimal separator comes from Windows.
Notifications and other workflow templates - The installation's symbol, digits, and formats. Decimal and grouping separators come from the Windows regional settings of the account that runs the process; for the Automation Server, that is its startup account, shown in the Automation Server Manager. With a multicurrency license, the amount is written without the symbol in a fixed format. A value that SQL Server has already turned into text, for example with CONVERT in a SQL macro, is inserted unchanged.
Reports The report locale: Default report locale, or the report's own language Not applied; reports show currency in the report locale. Some shipped reports always show two digits after the decimal, or, when a row carries a currency code, the amount followed by that code.

In a report, "this week" and the other week-based date ranges start on the first day of the week of the report locale.