Custom Logos & White Labeling

Replace Nira branding with your own — from a simple logo swap to a fully white-labeled experience on your own domain. This is an implementation guide for admins.

Written By Nira.app

Last updated 15 days ago

Prerequisites

  • Custom Branding (logos): Professional, Business, or Enterprise plan.

  • White Labeling (watermark removal, custom domain): Enterprise plan only.

  • Admin access. Branding is configured from the Admin side of your dashboard.

Two Levels: Custom Branding vs. White Labeling

Custom BrandingWhite Labeling

Plan

Professional, Business, Enterprise

Enterprise only

Replace Nira logo with yours

✅

✅

"Powered by Nira" watermark removed

❌

✅

"Powered by Nira" PDF footer removed

❌

✅

Custom domain (your URL for login/sharing)

❌

✅

Custom Branding: Add Your Logo

Available on Professional, Business, and Enterprise.

  1. Log in with an Admin account.

  2. From your dashboard, click the hamburger button (top left) → Branding.

  3. Upload your company logo.

Your logo then replaces the Nira logo across: the Login page, Asset List Dashboard, Public Homepage, Asset Preview Page, Asset Loading Splash Screen, and PDF Reports.

💡 Tip: Upload an SVG for crispest results at any size. If you use PNG, use a 32-bit image with an alpha channel (transparency) so it sits cleanly on any background.

[SCREENSHOT: Dashboard hamburger menu → Branding panel with logo upload]

White Labeling: Remove Nira Branding (Enterprise)

White Labeling builds on Custom Branding and adds:

  • Removal of the "Powered by Nira" watermark from the viewer.

  • Removal of the "Powered by Nira" footer from PDF reports.

  • Custom domain for login and asset URLs (see next section).

Setting Up a Custom Domain

A custom domain lets your login and asset links use your own URL instead of nira.app. For example, your login page could be view.mycompany.com, and an asset link could look like view.mycompany.com/<assetid>.

Custom domains are part of the White Labeling package. Two behaviors to plan for:

  1. Email notifications route to Admins only. With a custom domain, Nira sends all user emails to Admin profiles rather than directly to your users — this keeps the experience white-labeled. When you add a new user, forward the login instructions yourself, or set a password for them manually and share it privately. You can create users and assign temporary passwords in the admin panel (e.g. view.mycompany.com/admin/users).

  2. The Help icon is hidden for guests. Guest accounts logged into a custom domain won't see the Help icon. It remains visible to users with upload privileges (Admins, Team Members, Contributors).

💡 Tip: Ask users to change their password after first login if you set one for them. For a smoother experience at scale, enable SSO instead of managing passwords — see SSO & Login Troubleshooting.

Who Actually Sees the White-Labeled Experience

This is the most common point of confusion, so test against this list. The white-labeled experience is built only for view-only visitors — the people you'd want it for (clients, reviewers).

Will see white-labeled experience:

  • A logged-in External Guest with View Only access to an asset.

  • Anyone without an account viewing a Password Protected or Publicly Accessible asset.

  • Anyone without an account using an Inspection Link.

Will NOT see white-labeled experience:

  • Any logged-in Team Member, Contributor, or Administrator (anyone who can upload).

  • Any logged-in account granted Edit access to an asset.

⚠️ Warning: When testing, use a scenario from the first list only. The easiest way is a private/incognito window so you aren't accidentally logged in with an upload-capable account.

Troubleshooting

Problem: My logo looks blurry or has a white box around it.

Cause: Low-resolution or non-transparent image.

Fix: Upload an SVG, or a 32-bit PNG with alpha. Avoid JPEGs and flattened PNGs.

Problem: I enabled White Labeling but still see "Powered by Nira."

Cause: You're testing while logged in as an upload-capable user, who never gets the white-labeled view.

Fix: Test in incognito as an External Guest (View Only), or via a Password Protected / Publicly Accessible / Inspection Link asset.

Problem: My new client never got their invitation email.

Cause: On a custom domain, invitation and notification emails go to Admins, not the guest — by design.

Fix: Retrieve the invitation from the Admin inbox and forward it, or set the guest's password manually in the admin panel and share it privately.

Problem: A guest says they can't find the Help button.

Cause: The Help icon is intentionally hidden for guests on custom domains.

Fix: This is expected. Provide your own support contact, or point them to a Guide for Shared Link Recipients.

Problem: Will my clients be able to tell I'm using Nira?

Cause: White Labeling removes visible branding, but data is still served from Nira servers. Fix: A technically savvy user could identify Nira by inspecting network traffic. Fully removing "Nira" from served files requires an on-premises / self-hosted configuration.

Technical Notes

  • Custom Branding = logo replacement (Professional+). White Labeling = watermark removal + custom domain (Enterprise only).

  • White-labeled experience applies to view-only visitors only, never to upload-capable users.

  • On custom domains, all user emails route to Admins, and the Help icon is hidden for guests.

  • Data remains on Nira servers even with a custom domain. True "no Nira anywhere" requires on-premises deployment. See Data Storage & Security.

  • Logos: SVG recommended; PNG must be 32-bit with alpha.

Related Articles