Configure Organization Branding, Contact Details, and Custom URLs - Article

Give customers and partners a recognizable academy experience. Configure organization branding, contact information, and custom entry URLs while keeping presentation separate from membership and access permissions.

Updated: 27 Sep 2026

8 min read

Summary

Give customers, partners, and internal audiences an experience they recognize. Organization branding and custom entry URLs help people understand where they are, while appropriate contact details direct questions to the team responsible for supporting them.

Use this article to:

Configure the available appearance and banner options.
Provide an organization-specific entry route.
Distinguish visual presentation from membership and access.
Validate the experience for the people who will actually use it.

A recognizable experience with clear responsibility

A customer academy may use centrally maintained training while presenting the customer's identity. A partner program may need local contact recipients even though the provider operates the platform. An internal business unit may need a different welcome banner without needing a separate learning system.

Organization settings support these experiences where enabled. The purpose is not only to change colors: it is to help people recognize the service, understand who is supporting them, and reach the correct entry route.

Open the organization's More → Settings menu. Depending on configuration, the available tabs include Appearance, Top banner, Contact details, and Custom URL.

Choose the right presentation control

Control	What it does	When to use it
Appearance	Applies the available organization-specific visual settings, such as logo, background, and colors.	A customer, partner, or business unit needs a recognizable presentation.
Top banner	Provides the banner shown on My overview.	The audience needs a welcome, identity, or program message at its main overview page.
Contact details	Provides available organization-specific support and contact recipient settings.	Queries should reach the organization or service team responsible for that audience.
Custom URL	Creates an organization-specific entry address on the platform.	People should enter through a recognizable route that can display organization appearance before login.

A custom URL is an organization-specific platform address, not automatically a separate internet domain. Branding also does not create security separation by itself. Access must be designed through roles, organization scope, and the relevant feature settings.

Keep these controls separate from Storefront styling, which controls the presentation of Storefront sections, and from authoring brand-color presets, which are configured at platform level for content creators. The organization’s Top banner belongs to My overview; it is not a Storefront banner. Choose the control for the page or authoring experience you intend to change.

Configure Appearance

Open the organization's Settings → Appearance.
Configure the logo, backgrounds, and color options available on your platform.
Use approved images and colors with readable contrast.
Save and inspect representative pages as a user with the intended membership.
Check the anonymous entry experience separately if you will distribute a custom URL.

Use clear logos and avoid placing important instructions only inside an image. Buttons, links, and text must remain readable against the chosen background. Advanced appearance options should be reviewed as part of the complete page, not only in the setting preview.

Where video watermark or other additional appearance options are available, use them according to the relevant feature configuration. Do not assume every appearance setting affects every type of content.

Authentication pages

When an anonymous user enters through an organization-specific custom URL, the organization appearance can apply to the pages available before login. A configured organization site background overrides the platform site and login backgrounds for that organization-specific authentication experience, including login, signup, and password recovery.

This is useful for a customer who should recognize the academy before signing in. Test the actual link you intend to distribute; opening the generic platform address is not the same test.

Configure the Top banner

Open Settings → Top banner, configure the available banner content, and save. The Top banner is shown on My overview, not on every page.

The documented minimum banner image width is 1260 pixels. Also review the result on a smaller screen: an image with important text near an edge may not communicate well when the available display area changes.

Keep the banner focused on the audience's current purpose. For example, a partner academy banner can explain the certification journey and direct learners to the relevant learning offer. It should not become the only place where an essential policy or deadline is communicated.

Understand membership-related presentation

Situation	What to expect or verify
No organization membership	The platform-level presentation is used.
One organization	The organization's configured appearance and banner can provide the audience-specific experience. A missing banner in this single-organization case falls back to the platform banner.
A suborganization within the same organizational structure	A configured suborganization appearance can take precedence over its parent's appearance. Check the intended branch account rather than assuming all branches look identical.
Several organizations or suborganizations	The resulting appearance and banner depend on the combination of memberships and configured presentation. Verify the actual accounts used by shared staff and administrators.
An anonymous visitor following a custom organization URL	Organization appearance can be shown before login. The result after login must also be tested against the user's memberships.

Do not use the visible brand as evidence of the person's full access scope. A user who supports several customers can have a different presentation from a participant who belongs to only one.

An explicitly saved default-looking suborganization appearance is still a configured appearance. It is not necessarily equivalent to leaving that suborganization without its own appearance settings.

Configure Contact details

Open Settings → Contact details. Where available, the interface provides options such as Enable custom support email for this organization and Enable custom email receivers for this organization.

Enable the option required for your support model and complete the fields shown. Contact categories can direct different types of requests to the relevant operational recipients—for example, account help, course questions, booking changes, or general support.

Use monitored service addresses with a clear owner. A local customer contact can handle business questions, while the provider may remain responsible for platform issues. Make that division understandable to both teams.

Do not assume that parent contact recipients automatically apply to every suborganization; the custom-recipient feature is organization-level. Verify the route used by a branch member before promising local routing.

These settings concern support and contact routing. They do not replace System Email templates, workflow sender configuration, or the platform's email delivery service.

Create a custom organization URL

Open Settings → Custom URL for the organization or supported suborganization.
Add or edit the custom URL using the controls provided.
Choose a stable, recognizable address and save it.
Open the resulting address in a fresh signed-out session.
Check the appearance and available learning presentation, then test the intended signup or login journey.

A conceptual address might look like academy.example.com/customer-academy. Use the address generated by your platform rather than constructing an assumed link.

Keep published URLs stable where possible. They may be used in welcome emails, customer intranets, printed material, or support instructions. Coordinate changes to the route with the owners of those channels.

Decide whether the route should also assign membership

Separate platform controls govern assignment for new users signing up and existing users logging in through organization-specific routes. A branded URL can therefore be used for presentation without assuming that every visitor becomes a member.

Review the intended route with the platform owner or Eurekos support if those controls are not available to you. Then test new users, existing signed-out users, and existing signed-in users. See Invite Users and Assign Organization Membership for the membership guidance.

Practical experience patterns

Requirement	Recommended design	Outcome
A customer wants its own academy entry	Configure organization appearance and a stable custom URL; agree the membership behavior separately.	Customers recognize their learning service without mistaking branding for a complete access policy.
Local teams handle business questions	Configure the supported organization contact recipients and retain clear provider escalation.	Questions reach the team that can act on them.
A branch needs its own identity	Use a suborganization appearance where supported and verify parent/branch behavior.	Local recognition fits within the broader academy.
Shared staff support several customers	Test representative multi-organization accounts in addition to single-customer participants.	Support staff understand why their presentation may differ from a customer's screenshot.

Verify the setup

Scenario or check	Expected result or evidence
Anonymous entry Open the distributed URL in a fresh signed-out session.	The intended organization presentation is shown before login.
Participant presentation Sign in with a representative member and inspect My overview and relevant pages.	Appearance and banner support the correct audience.
Shared and branch memberships Use the actual membership combinations required by the business.	Presentation is understood and acceptable for those users.
Contact routing Send an approved test contact request through the intended user route.	The responsible monitored recipient receives it.
Membership outcome Inspect membership after the intended signup or login flow.	Assignment follows the approved policy, independently of the visual branding.

Troubleshooting

What you observe	What to check
The generic platform appearance is shown	Check the entry URL, login state, organization memberships, and saved appearance configuration.
Two users see different branding	Compare their complete memberships and whether they entered through an organization-specific route.
A banner does not appear on another page	Top banner is intended for My overview. Check that page and the applicable membership configuration.
Parent appearance is not used by a branch	Check whether the suborganization has its own saved appearance, including default-looking settings.
A branch contact request reaches the default recipient	Check the organization-level scope of custom recipient settings; do not assume suborganization inheritance.
A branded URL does not add the user to the organization	Check the separate membership-assignment controls and the user's state. Appearance does not confirm membership.

FAQ

Does organization branding create a separate access boundary?

No. Branding changes presentation. Roles, organization scope, content relationships, and feature-specific rules determine access. A logo or customer-specific background is not proof that the user has joined the organization or that its content is isolated.
Does a custom organization URL automatically add every visitor as a member?

No. Membership assignment is configured separately from appearance. New-user signup and existing-user login can have different assignment behavior. Test the distributed route for new, signed-out existing, and already signed-in users, then check their actual memberships.
Is a custom organization URL a separate internet domain?

Not automatically. It is an organization-specific entry address on the platform. Use the address generated by the platform; a separately branded domain requires its own approved configuration rather than an assumption based on the URL field.
Where is the organization Top banner displayed?

The Top banner is displayed on My overview, not on every platform page. Check the intended member account and its organization relationships when reviewing the result.