Study guide
11.2 Branding the SailPoint User Interface
SailPoint Certified IdentityIQ Engineer Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: The IdentityIQ Engineer Exam
1.1 Exam Format, Official Blueprint, and Study Strategy
2 Chapter 2: Infrastructure, Installation, and Extended Attributes
2.1 IdentityIQ Infrastructure Components 2.2 Installation Steps and Procedures 2.3 Creating Extended Attributes and the Objects That Support Them
3 Chapter 3: Build, Deployment, Patching, Access, and Email
3.1 Ongoing Build and Deployment 3.2 Installing Patches and Performing Upgrades 3.3 Configuring End-User Access 3.4 Email Server Settings and Email Redirection
4 Chapter 4: Lifecycle Manager Configuration, Provisioning Policies, and Workflows
4.1 Configuring Lifecycle Manager 4.2 Identity Provisioning Policies 4.3 Configuring LCM Workflows
5 Chapter 5: Lifecycle Events, QuickLinks, Batch Requests, and Rapid Setup
5.1 Lifecycle Events and Their Workflows 5.2 QuickLinks and QuickLink Populations 5.3 Configuring and Using Batch Requests 5.4 Rapid Setup in Lifecycle Events and Identity Operations
6 Chapter 6: Certification Campaigns and Certification Rules
6.1 Configuring and Scheduling Certification Campaigns 6.2 The Purpose of Common Certification Rules
7 Chapter 7: Policies and Policy Violations
7.1 Configuring and Leveraging Policies 7.2 Responding to Policy Violations
8 Chapter 8: Reporting, Advanced Analytics, and Auditing
8.1 Executing and Leveraging Reports 8.2 Leveraging Advanced Analytics 8.3 Configuring and Using Auditing
9 Chapter 9: Rules, Rule Libraries, and the SailPoint API
9.1 The Purpose and Use of Rule Libraries 9.2 Rule Input and Output Arguments 9.3 Common SailPoint API Objects and Methods
10 Chapter 10: Workflow Development
10.1 Workflow Variables, Transitions, and Step Conditions 10.2 Workflow Steps That Generate Work Items 10.3 The Different Workflow Step Usages 10.4 Leveraging Sub-Workflows
11 Chapter 11: Email Templates, Branding, and Localization
11.1 Customizing and Using Email Templates 11.2 Branding the SailPoint User Interface 11.3 Localizing the SailPoint UI
12 Chapter 12: Application Definitions, Connector Settings, and Rapid Setup Aggregation
12.1 Configuring Application Definitions 12.2 Configuring Common Connector Settings 12.3 Configuring Rapid Setup Aggregation Settings
13 Chapter 13: Data-Loading Tasks and Application and Connector Rules
13.1 Scheduling Tasks for Data Loading and Processing 13.2 Common Application Rule Types 13.3 Common Connector Rule Types
14 Chapter 14: Debugging with log4j, Syslog, and the IdentityIQ Console
14.1 Configuring and Leveraging log4j 14.2 Configuring and Leveraging Syslog 14.3 Leveraging the IdentityIQ Console for Debugging
15 Chapter 15: Debug Pages and the Administrator Console
15.1 Leveraging the Debug Pages for Debugging 15.2 Leveraging the Administrator Console for Debugging
16 Chapter 16: Role Model and Identity Attribute Mappings
16.1 Default Role Models and Role Types 16.2 Configuring Roles and Role Options 16.3 Configuring Identity Attribute Mappings
17 Chapter 17: Data Objects, Relationships, and Group Types
17.1 Common IdentityIQ Data Objects 17.2 Relationships Between Common Data Object Models 17.3 The Difference Between Group Types
11.2 Branding the SailPoint User Interface
Key Takeaways Explain This Topic AI
Colors, fonts, spacing, and other styling are overridden with custom CSS; ui-custom.css holds the modern UI overrides and iiq-custom.css the classic JSF-page styles.
Logos are image files; SailPoint recommends replacing files in ui/images with custom images of the same file names instead of editing core .xhtml pages.
Product text and labels come from the message catalog and are changed with iiqCustom.properties overrides (section 11.3).
Email branding is done in email templates; Rapid Setup also has style sheet, header, and footer templates.
Branding files live in the web application directory, so keep them in the build (for example, the SSB web folder) or they will be lost on upgrade.
Last updated: September 2026
Branding the SailPoint User Interface
Objective 4.9 asks you to know which elements of the SailPoint UI can be branded and how to change them . SailPoint's Compass white paper Branding IdentityIQ is the detailed reference. For the exam, know the categories of brandable elements and the mechanism for each.
What Can Be Branded, and How
Element Mechanism Where
Colors, fonts, spacing, backgrounds, menu styles Custom CSS overrides ui/css/ui-custom.css for the responsive (Angular) UI; css/iiq-custom.css for classic JSF pages
Logos and product images Replace image files with same-name custom images ui/images directory. Only edit .xhtml includes such as the login page if a new file name is unavoidable.
Product name, labels, headings, button text Message catalog overrides WEB-INF/classes/sailpoint/web/messages/iiqCustom.properties (section 11.3)
Email look and feel Email templates with HTML in CDATA Custom EmailTemplate objects (section 11.1). Rapid Setup has Notification Style Sheet, Header, and Footer templates.
Icons for special account types or role types CSS classes plus images; UIConfig entries Account icons use AccountIconConfig in UIConfig (section 2.3). Role type icons reference images from iiq-custom.css .
Home page content QuickLink cards and widgets QuickLink populations (section 5.2) and user-selectable Home page widgets
- Help contact Configuration Help Contact Email Address on the Miscellaneous tab adds an Email Help button
- CSS Branding
The custom style sheets exist so that rules placed in them override the product defaults without anyone editing product CSS. Community examples use rules like these: /* Page background */
.sp-body-container { background-color: #ffffff; }
- /* Top navigation hover and selected colors */
- .bg-primary .nav li > a:hover,
- .bg-primary .nav li > a:focus { background-color: #0b3d91 !important; }
- .bg-primary .nav li.active > a { background-color: #0b3d91 !important; }
Practical tips:
Use the browser's developer tools to find the class that styles an element, then override it in the custom file.
Browsers cache CSS aggressively. Clear the cache or use a private window when testing.
Some product rules use !important . An override may need the same weight or a more specific selector.
Image Branding
The white paper's guidance, as quoted in SailPoint's developer community:
The logos are specified in core product .xhtml files. The recommended approach is to replace the image files in the ui/images directory with custom images, using the same file names . This avoids changing the .xhtml files and simplifies upgrades.
If you must point to a new file name, you edit the include that renders it, such as the login page include. That file then has to be re-checked on every upgrade .
Text Branding
To show "ACME Access Portal" instead of product wording, override the relevant message keys in iiqCustom.properties instead of editing pages. The same mechanism translates text (section 11.3).
Keeping Branding Safe
Everything lives under the web application. Upgrades replace the installation directory (section 3.2), so custom CSS, images, and properties must be reapplied .
Put branding in the build. With the SSB (section 3.1), branding files go in the project's web folder, so every build and environment gets them. The community also describes using build file-layout rules to ship different logos per environment , such as a red "TEST" banner in non-production.
Prefer overrides over edits. Custom CSS files, same-name images, and iiqCustom.properties all avoid changing product files, which keeps upgrade work small.
Remember object text. Application, role, policy, and entitlement descriptions shown in the UI are data , not branding files. They can be localized with multi-language descriptions (section 11.3).
A Branding Project Plan
A typical branding request covers the login page, the header, colors, email, and a few wording changes. A practical order:
Inventory the requirements against the table above: which are CSS, which are images, which are text, and which are email templates.
Build styles first in ui-custom.css . Test the Home page, request pages, certifications, and the login page in each supported browser.
Swap images by replacing same-named files in ui/images with correctly sized logos, including any images used on the login page.
Adjust text in iiqCustom.properties (and the language variants if the installation is multilingual).
Match email styling by giving custom templates the same colors and logo, hosted at a URL recipients can reach. For Rapid Setup, update the style sheet, header, and footer templates on its Miscellaneous tab.
Package and promote the files through the build, so development, test, and production match. Consider a visible environment marker in non-production.
Test after every patch as well. Patches can change page markup, and a CSS selector that worked before may no longer match.
What You Cannot Brand Through the UI
IdentityIQ has no admin screen for logos and colors . Some SaaS products offer a "Product Branding" page, but IdentityIQ branding is done with files (CSS, images, and properties) deployed with the application. If an exam option says "upload a logo in Global Settings," reject it for IdentityIQ.