Help center Customer portals Customize customer portal header links and brand colors Updated Wednesday, October 28, 2026 · Marc Staine A customer portal header should help a customer find the next useful action: read knowledge, review requests, contact support or open a relevant service destination. Core provides five configurable header-link slots and named brand colors. Use them to make a B2B support portal recognizable and easy to navigate, then test the actual customer experience. A link changes navigation; it does not grant permission to its destination. At a glanceFor: support operations administrators, portal owners and authorized portal designers. Applies to: Supportbench Core.Start here: Settings → Self-Service → Customer portal → select the portal → Branding Plan navigation around customer tasks · Prepare access and preserve the current settings · Add or change a header link · Remove or replace a link without stranding customers · Choose colors using the current theme’s meanings · Verify the saved customer experience · Worked example: help a technical customer find active requests · Troubleshoot header links and colors Plan navigation around customer tasks Customer needUseful label or destinationCheck before adding itFind an answer before opening a caseA descriptive knowledge destination, such as Knowledge base.Knowledge is enabled and the intended articles are accessible to the audience.Follow up on existing workThe portal request/case destination, with a label your customers recognize.Signed-in access and customer visibility are correct. A navigation link does not expose every Company case.Ask for helpThe configured request-submission destination.The form works for the intended audience and explains what information support needs.Check service informationAn approved external status or service-information page.The URL is current, belongs to the intended service and does not contain private or temporary credentials.Prepare for a technical changeA stable reviewed guide or training destination.The content applies to the supported product/version and the link will remain maintained.Choose a small set of tasks people actually use. Five available slots are a capacity, not a recommendation to fill every slot. “Resources” may be less useful than “Installation guides” when the latter is the customer’s real task. Use your established customer terminology, especially when different portals serve different products or customer groups. Prepare access and preserve the current settings Confirm that you have permission to edit the Customer portal configuration. A portal designer or administrator may need to make the change if your role cannot save it.Identify the exact portal name and customer URL. An account with several portals can have different branding and customer audiences; check the selected portal before editing.Record the existing link labels, URLs and color values so you can restore them if a change produces an unwanted result. Record the current theme as well.Open the intended destinations independently and verify their content and audience. Use a normal customer account for restricted destinations and an anonymous window for public ones.Agree the navigation wording and brand values with the portal owner. Start with one change so the resulting behavior is easy to assess.This procedure changes Branding settings. It does not require replacing the theme or changing customer access, identity-provider settings or portal security. If a custom design does not consume a setting, investigate the design with its owner before making a broader change. Add or change a header link Open Settings → Self-Service → Customer portal and select the intended portal.Open Branding and find Header links.Choose one of the five fixed slots. Enter both Link 1 label and Link 1 URL, or the corresponding numbered fields for another slot. The label allows up to 50 characters and the URL up to 250 in the editor.Write a short, descriptive label and the exact intended destination. A relative path such as /cases/ stays within this portal; a full URL such as https://example.com/status identifies an external destination. Replace the example with your actual approved URL.Review the other slots for duplicate labels, outdated destinations or empty half-completed entries. Keep the label and URL together; a slot needs both to provide a useful link.Choose Save Changes. Read any validation result and verify that the saved values remain after reopening Branding.Open the customer portal and locate the link in the header or mobile navigation. Follow it and confirm the intended destination and access behavior.Save Changes and Publish have different jobsSave Changes applies these portal settings immediately. The Publish controls used for design/page drafts are a separate workflow. Do not leave an intended Branding change unsaved because an old instruction says to publish the whole portal. Remove or replace a link without stranding customers Identify the slot and confirm whether another customer instruction, bookmark or help article refers to its current label.To remove the navigation item, clear both its label and URL. To replace it, update both fields consistently.Choose Save Changes, then reopen the customer portal and verify the result.Update any affected onboarding or help instructions that tell users to choose the old label. If the destination itself is being retired, manage its replacement separately; removing a header link does not delete a page or configure a redirect.A useful replacement should solve the same customer task whenever possible. Replacing a request-history link with a promotional homepage can leave an existing customer unable to find their work even if the new URL technically loads. Choose colors using the current theme’s meanings In Branding → Brand colors, the current labels are Primary, Secondary, Background, Text and Surface. In the Premiere theme, these correspond to the five color slots. The old statement that “Color 5 is always the header text color” is incorrect: its current Premiere role is Surface. Custom and other themes can use the underlying slots differently.Premiere colorTypical roleVerified theme fallback when blankPrimaryPrimary brand/accent color.#e43f73SecondarySecondary brand color.#141b2dBackgroundPage background role.#f7f8fbTextText color role.#141b2dSurfaceContent surface role.#ffffffThese are Premiere fallback values, not a claim that your existing portal uses them or that every theme applies them to the same element. Premiere accepts hexadecimal values in #RGB or #RRGGBB form; leaving a value blank uses the theme default. The theme can adjust text/link colors for readable contrast, so a rendered element is not guaranteed to use the exact entered value unchanged.Record the existing value and choose the named color role relevant to the design change.Enter the approved valid value, then choose Save Changes.Inspect headings, body text, links, buttons, cards and the header on actual portal pages. Check normal and selected/hovered states where relevant, including the mobile menu.If the result is wrong or difficult to read, restore the recorded value and save. If a custom header ignores the named setting, ask the design owner to inspect its template and CSS. Verify the saved customer experience TestWhat success looks likeWhat a failure usually points toAnonymous visitorPublic links open the intended page; restricted destinations follow the expected sign-in/access behavior.Wrong URL, a disabled feature or a destination with different access requirements.Representative signed-in ContactThe customer reaches the intended authorized content and request scope.Customer role, Company relationship or portal visibility configuration; navigation alone cannot fix it.Small screenNavigation remains reachable, labels are understandable and the destination is usable.Theme layout or an overly long label rather than the link value itself.Readable colorsText and controls remain distinguishable from their backgrounds.A poor color combination or custom CSS overriding the intended theme role.Different portalOnly the intended portal has the planned result.The wrong portal was edited or a shared/custom design has broader dependencies.Knowledge disabledThe visible navigation agrees with the enabled portal features.Knowledge links can be suppressed when knowledge is disabled; do not treat every absent link as a failed save.After saving, compare the portal with the values you just reopened in the editor. If the settings are stored correctly but the page looks unchanged, check the active theme, custom header/CSS and any relevant cache before repeatedly overwriting the same values. Keep audience tests separate from appearance tests. Worked example: help a technical customer find active requests Suppose customer administrators use the portal to review support work but cannot tell which header link opens their requests. The operational goal is to make that task obvious while preserving the account’s existing customer visibility.Confirm the correct request destination and verify it using a representative signed-in customer account. Note what that customer is authorized to see.Choose an unused or appropriate existing header slot and use a clear label, such as “My requests,” with the verified portal path. Avoid promising organization-wide visibility if that customer only has personal access.Save Changes and open the portal anonymously. Confirm the expected sign-in behavior for the request destination.Sign in as the representative customer and follow the same link. Confirm it opens the correct request list rather than an agent URL.Check the mobile menu and update the customer onboarding article to use the new label. Tell the support team where the link is so their instructions are consistent.The improvement is an easier path to an existing authorized task. It does not require expanding customer permissions or exposing additional cases merely to make the navigation useful. Troubleshoot header links and colors ProblemChecks and corrective actionThe link does not appearConfirm both label and URL, Save Changes, the selected portal and active theme. Check whether the theme renders that slot and whether the destination feature is enabled.The editor rejects the valueCheck the 50-character label and 250-character URL limits and the expected color format. Use a short stable destination rather than a long credential-bearing URL.The link opens the agent applicationReplace the agent URL with the intended customer-facing destination and retest using a customer identity.The customer is asked to sign inCheck whether the destination is intentionally restricted. Do not weaken access just to make the link open anonymously.Color 5 changes a surface instead of header textUse the current named Brand colors and the selected theme’s behavior. Premiere uses the fifth slot for Surface.The color differs slightly from the entered valueThe theme can adjust text/link colors for contrast. Check the rendered result and custom CSS instead of assuming storage failed.Desktop works but the mobile menu does notCheck the actual mobile navigation, label length and theme layout. Capture the affected controls for the design owner.A removed link still appears elsewhereThe same destination may be hard-coded in a page template or custom header. Review that design separately; the five Branding slots do not replace all custom navigation. Continue learning Configure the customer portal and its separate save workflowsOperate a useful customer self-service portalCustomize customer-portal pages with Supportbench LiquidUnderstand customer case visibilityBuild a practical KCS and self-service process Was this article helpful? Yes No Thank you for your feedback.