We implement and support eramba for a range of clients, including some large UK enterprises, and portal customisation has now come up more than once. Raising it here at Samuel’s suggestion, as support confirmed it is not currently on the roadmap.
The portals are the only part of eramba that most of an organisation’s staff will ever see. Logo upload is supported, which is welcome, but everything else is fixed, including the banner treatment on the document listing page. In larger organisations that becomes a problem for two reasons.
The first is governance. Anywhere staff are asked to read a policy or complete an assessment is treated as a branded surface, and brand teams have a legitimate say over it. The current banner is quite vibrant and sits awkwardly against more restrained corporate palettes. It reads as someone else’s product rather than an internal system.
The second reason matters more, and it is a security one. We spend a lot of effort teaching people to be suspicious of unfamiliar portals that ask them to log in and confirm something. A page that does not look like it belongs to the organisation works against that training. It gets queried, forwarded to the service desk, or ignored, and completion rates suffer. Policy attestation and assessment response are exactly the metrics that GRC teams are judged on, so this is not purely cosmetic.
Three options, roughly in order of what I imagine the effort looks like:
- A small set of configurable colour values in settings (header or banner colour, primary accent, button colour). No full theming, no custom CSS, just a handful of hex fields.
- An option to suppress the decorative banner entirely and fall back to plain white with the logo.
- If neither is viable, change the shipped default to something more neutral.
Option 2 alone would resolve most of what we have run into and is presumably the least invasive.
Interested to know whether others are hitting the same objection, particularly anyone rolling the portals out across a few thousand staff.