> For the complete documentation index, see [llms.txt](https://helpdesk.augmentt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdesk.augmentt.com/management/look-and-feel.md). # Look and Feel **Look and Feel** is where you customize how the Augmentt Portal appears to you and your team — your browser's dark mode support, and white-labeling the portal itself with your own logo and favicon. ## Dark mode Several browsers let you view the Augmentt platform in dark mode. This is a browser-level setting, not an Augmentt setting — Augmentt doesn't currently ship its own in-app dark mode toggle, so it relies on your browser's ability to force-darken web content. ### Google Chrome Go to `chrome://flags/#enable-force-dark` and select **Enable** under "Auto Dark Mode for Web Contents." ### Microsoft Edge Go to `edge://flags/#enable-force-dark` and select **Enable** under "Auto Dark Mode for Web Contents." ### Mozilla Firefox Firefox doesn't have an equivalent built-in flag — install the [Dark Reader](https://addons.mozilla.org/en-US/firefox/addon/darkreader/) extension instead. {% hint style="warning" %} Because dark mode is applied by the browser forcing color inversion on the page (rather than Augmentt rendering a native dark theme), you may occasionally see rendering glitches in specific browsers — for example, an element that doesn't invert correctly. If you spot a visual bug that only appears with force-dark enabled, report it as a UI issue (see Reporting a UI Issue) and mention that dark mode was active — it helps support reproduce it. {% endhint %} ## Customizing the Augmentt Portal (branding) The Augmentt Portal can be customized and branded in two ways: * Displaying your own **custom logo**. * Changing the **favicon** (the icon shown in the browser tab). ### Where to configure it Find these settings within the Augmentt Portal by clicking **Look and Feel** at the bottom of the left-hand navigation. ### Uploading your branding 1. From the Look and Feel page, you'll be taken to a screen where you can upload or drag-and-drop your desired logo and/or favicon. 2. Image size restrictions: * Max width: **208px** * Max height: **64px** 3. After uploading, use the toggle switches to enable or disable your custom branding independently for the logo and favicon. Once enabled, the Augmentt dashboard displays with your company's images instead of Augmentt's default branding. {% hint style="info" %} Confirm current upload size limits and supported file formats in your own instance's Look and Feel page — these constraints can change, and this page reflects the values documented at the time of writing. {% endhint %} ## Common branding issues * **Logo doesn't appear on exported reports.** Look and Feel branding controls the in-app portal experience; whether that same logo automatically carries over to exported PDF reports (Summary Reports, Security Posture exports, etc.) has been a recurring point of confusion — some customers have found their logo doesn't show up on report exports even though it's correctly configured in Look and Feel. If your logo isn't appearing where you expect it (on a report, or positioned incorrectly relative to the report text), report it to support with the specific report type and an example export attached. * **Branding doesn't take effect after uploading.** Occasionally, after uploading a logo and enabling the toggle, the page doesn't fully reflect the change right away. Try a hard refresh; if it persists, it's worth flagging to support with your browser and a screenshot. * **Login Portal Branding (a different, separate feature).** Don't confuse portal branding (covered on this page — the Augmentt app's own look) with **Login Portal Branding**, which is a Microsoft 365 tenant configuration tracked as part of your security posture/compliance checks. That's a property of the customer's M365 sign-in page, configured in Azure/Entra, and it's evaluated separately as a compliance item — it isn't controlled from this Look and Feel screen. If a tenant shows as "partially compliant" or "non-compliant" for Login Portal Branding, that's a posture/compliance topic, not a Look and Feel setting. {% hint style="warning" %} The distinction above (portal Look and Feel branding vs. the Login Portal Branding compliance check) is based on support-ticket patterns; confirm the exact scope of the Login Portal Branding posture check against current Compliance/Configuration documentation. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://helpdesk.augmentt.com/management/look-and-feel.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.