Today, the Central login page looks the same for everyone. For organizations running multiple servers or onboarding new team members, this can sometimes cause confusion about which Central you’re logging into.
We’re starting a new body of work in Central focused on customizing the login experience so users can feel confident they’re accessing the right server and feel a stronger sense of ownership when they do.
Admins will be able to upload their own logo and a hero image directly in Central. These assets will be applied consistently across the login experience, without affecting data collection or project configuration.
The login page will then reflect your organization’s branding, making it easier for users to recognize the correct server at a glance and feel confident they’re signing into the right place.
We’d love to hear your thoughts: would branded login pages help reduce confusion or improve trust for your teams? Are there other elements you’d expect to customize as part of this experience?
That's a really great idea - I'd definitely prefer this!
Maybe we could also consider adding an option to change the default theme color (I think it's magenta right now?) in ODK Central. This would allow organizations to align the interface with their own logo or brand color, and could really help create a more familiar and organization-friendly user experience.
I think the three core things that would be nice to change are:
Theme colors, just as suggested above.
Site title/name, so that it says “PNLP Data Collection Server” or “Maternal Health Project” instead of ODK Central in the top left corner. Still happy to have “Powered by ODK Central” appear prominently elsewhere (e.g. footer) for brand purposes or as makes sense.
Logo/Favicon. This would help with bookmarking, as all the favicons currently point to ODK, and would help distinguish in the browser omnibox so users click on the correct site if they have access to multiple sites.
I would prefer these things over the hero image, but would welcome any change to allow additional distinguishing between sites.
I think two versions of violets are used.
Another low haggle fruit would be selector for custom font from say Google Fonts vast library.
We may also think about Add footer customisation and an static page where markdown based information can be displayed in greater detail such as who is owner, terms of use etc.
While we are at it, within system management, can we save SMTP settings that may be used for email sending rather than depending on .env
Similarly we may also save s3 credentials and connection info there !
I have had users who have access to multiple ODK Central instances, trying to log in and failing only to realise they have the server URLs mixed up, because “the login pages all look the same.”
It would work well for institutions with instances that are up for a long time.
Thanks for the detailed feedback @Stephen_K_ojwang. This is really helpful as we scope out this area for Collect (and Web Forms). I’m curious if others have similar needs for branding on the collection side of things?
Starting in Central v2026.1.0, you can configure your login page. See the documentation for details.
If you've done this, we'd love to know what you think! Feel free to share a screenshot for inspiration.
Is anyone using the API to automatically make updates? I don't know how useful this really is but you could do something like share public announcements like "50% vaccination coverage reached!" or rotate through inspirational quotes from your organization leadership.