Put your own name, logos and sender address on this server. The values are server-wide, only a global admin can change them, and a preview shows each one in place before you save.
What the Brand page controls
Brand is where a server says whose it is. The name the dashboard uses for itself, the logo above the sign-in form, the icon in the browser tab, and the address the server's email is sent from all come from this one page.
These settings are server-wide rather than per project, so one set of values covers every project on the server, and only a global admin can open the page or change what is on it.
Nothing is written while you type or crop. Text edits live in a draft and image crops are staged, so the Preview panel on the right shows what Save would produce rather than what the server currently holds. A bar appears along the bottom counting the unsaved changes, with Save and Discard beside the count.
There are four things to set, in four framed sections. Names holds the display name and the browser title. Logos and favicon holds the three images. Outgoing email holds the From name and the From address. Newsletter decides whether new users are offered the newsletter when they first sign in. Under each one, a row of Appears in chips names the preview scenes that setting reaches and how many surfaces it changes on each; choosing a chip opens that scene and flashes those surfaces.
How one name reaches every surface
There are two name fields and they do different jobs. The display name is what the software calls itself inside a sentence, such as Acme. The browser title is what the tab says, which is usually the longer form a company writes out, such as Acme Analytics.
Where the product has to name itself, it takes the display name first, the browser title when there is no display name, and Countly when neither is set. The browser tab takes the browser title first and falls back to Countly. So with only the browser title filled, the browser title becomes the name the product uses for itself, and with only the display name filled, the tab still reads Countly.
One field can land in several places at several sizes. The sign-in logo is the header above the sign-in form, and it is also the logo at the top of every email the server sends, at 130 pixels wide. The favicon is the browser tab icon, and it also stands in on the sign-in page when no sign-in logo has been uploaded.
Four of the surfaces are not in the dashboard at all. A report email and an invite email arrive in someone's inbox, a report attachment carries a filename, a paired authenticator app shows an account label, and a comment posted into a linked Jira project names the product. All of them read the names set here.
The largest effect has no field of its own. Once a display name or a browser title is set, links to count.ly and the Countly name are removed from email, from attachments and from the dashboard. The References to Countly panel at the foot of the page lists what is dropped and what stays on purpose.
Use Cases
Name your deployment
You want the dashboard, and the email it sends, to carry your own name rather than the vendor's.
- Open Manage > Brand. If the page shows a Global admins only notice instead of the form, ask a global administrator to make the change; these settings cover the whole server.
- In Names, fill Display name with the short form you want read inside a sentence, such as Acme.
- Fill Browser title with what the browser tab should say, such as Acme Analytics. This is also the fallback for the display name, so filling it alone still renames the running copy.
- Watch the Preview panel on the right as you type. Its four scenes are Sign-in, Dashboard, Email and Other, and the parts your fields changed are picked out on each one.
- Open References to Countly and choose Show details to read what setting a name removes and what it leaves in place.
- Choose Save in the bar at the bottom. The dashboard's own title, tab icon and top bar follow the new values without a reload.
Upload your logos and favicon
You want your own mark above the sign-in form, in the browser tab, and on the email this server sends.
- In Logos and favicon, click the tile for the slot you want. The tile is the control, so there is no separate button; hovering it reveals an upload glyph.
- Choose a PNG, GIF or JPEG. Another file type is refused with a message, and so is a source file above 20 MB, or smaller than that when this server's own upload limit is lower.
- Crop the picture in the dialog that opens. Each slot is saved at a fixed size, which the hint under its tile states: 330 by 100 pixels for the sign-in logo, and 64 by 64 pixels for both the top bar icon and the favicon.
- Read the tile again once you confirm the crop. It shows exactly the framing you chose, and the Preview panel picks it up at the same moment, because neither has been sent anywhere yet.
- Use Remove beside a tile's hint to clear a slot. That stages the removal rather than performing it, so Discard still puts the old image back.
- Choose Save. Images are written one at a time, and if any slot fails the message names it rather than reporting success.
A square image suits the top bar icon best, because the top bar renders it at 28 pixels. A wordmark shrunk into that box is unreadable.
Send email from your own address
You want report and invite email to arrive from your own address rather than the server default.
- In Outgoing email, fill From name with the name a recipient should see, such as Acme.
- Fill From address with the address it should come from, such as analytics@acme.com.
- Fill in both or neither. With only one of the two set, the server sends from its default instead, and the page says so under the fields rather than letting a half-filled override look active.
- Choose Save. These two values are used by the server alone and are never sent to the browser, so they do not appear anywhere in the dashboard.
- Send yourself a report from Email Reports to check a real message. The Email scene previews the envelope, but only a sent message proves the server picked the override up.
FAQs
I set the display name but the browser tab still says Countly. Why?
The tab reads the browser title, not the display name. The display name falls back to the browser title, but the fallback does not run the other way. Fill in the browser title as well.
Can I brand one project differently from another?
No. Brand is server-wide. Every project on this server shares one name, one set of logos and one sender address.
I filled in the From address but email still comes from the old sender.
The override needs both fields. With only the address or only the name set, the server keeps using its default, and the page shows a line under the fields saying so. Fill in the other field and save again.
Why is my logo cropped?
Every slot is saved at a fixed size, so the crop dialog is where you choose which part of the picture survives. The sign-in logo is saved at 330 by 100 pixels; the top bar icon and the favicon are both saved at 64 by 64.
My file was refused before the crop dialog opened.
Two checks run first. The file has to be a PNG, GIF or JPEG, and it has to be under the source limit, which is 20 MB or this server's own upload limit when that is lower. The message under the tile says which check it failed.
I uploaded a new logo but the old one is still in the top bar.
An upload is staged, not written. Choose Save in the bar at the bottom, which is also what publishes the change to the dashboard's own chrome.
What happens to the report attachment's filename?
It is named after this dashboard rather than Countly_Report.pdf once a name is set. The Email scene previews the name it will carry, built from the product name with anything that is not a letter or a digit replaced by an underscore.
Does turning the newsletter switch off hide the newsletter everywhere?
No. It decides whether new users are asked about the newsletter when they first sign in. The newsletter itself is published by Countly and stays listed among the references a name does not remove.
Do the email sender values show up anywhere in the dashboard?
No. They are used by the server only and are never sent to the browser.