Organization Visibility and Audience Targeting - Article

What organization visibility helps you achieve

Organizations in Eurekos can represent customers, business units, subsidiaries, departments, associations, franchises, or other audience groups. Adding the Organization feature to a Training Activity uses that structure to decide who receives the activity as a Storefront offer.

Typical uses include:

• Showing customer-specific onboarding only to that customer's people.
• Making a corporate program available to every subsidiary beneath a parent organization.
• Offering local training to one country or branch and its departments.
• Keeping a negotiated course, date, or price out of the general catalog.
• Providing an activity to the members of one association chapter.

Organization visibility is especially useful on a shared platform where several audiences use the same Storefront but should not receive identical offerings.

Understand the boundary of the feature

The Organization feature is an activity-level Storefront and self-enrollment control. It is not a universal prohibition on participation.

When an organization is selected, the activity is normally not visible in the Storefront to:

• Users without an organization in their profile
• Users connected only to other organizations
• Anonymous visitors

However, users can still be enrolled outside the organization through supported administrative or integration routes. Manual administrator enrollment, API enrollment, and QR-code enrollment are not blocked by this feature.

Use a different or additional control when the real requirement is:

Do not treat a hidden Storefront card as a security boundary. Decide whether manual, API, QR, and direct-link paths are intended, then configure and test the complete enrollment design.

Confirm that the feature is available

Configuration path: Course Administration → Activities → edit the activity → Features → Organization or suborganization.

The Organization feature is not available when Storefront is disabled in the platform's General settings. This reflects its purpose: it determines who receives the activity as a Storefront offering.

Before configuring, confirm that:

• Storefront is enabled.
• The organization hierarchy is current.
• Intended users have the correct organization relationships in their profiles.
• The activity's other Storefront settings allow it to appear.
• Your direct-link and enrollment-block policy is understood.

Select the organization

1. Open the Training Activity for editing.
2. At activity level, add or enable Organization or suborganization.
3. Select the highest organization or the specific suborganization that represents the audience.
4. If you select a parent organization, decide whether its descendants should inherit visibility.
5. If descendants are allowed, use the suborganization selection and Access restriction level where the audience begins or ends deeper in the hierarchy.
6. Save the activity.
7. Test the Storefront and direct link with representative users at every relevant level.

Choose the lowest stable point in the hierarchy that expresses the business requirement. Selecting a very broad parent and then adding several restrictions can be harder to operate than selecting the intended branch directly.

Parent organization visibility

When the activity is assigned to a parent organization, it is visible in the Storefront to users belonging to that organization and, by default, users belonging to its suborganizations.

For example:

• Watershed Corp
  • Watershed Corp Denmark
    • Sales
    • Operations
  • Watershed Corp Sweden

If Watershed Corp is selected and descendant access is not restricted, members of Watershed Corp, Denmark, Sweden, Sales, and Operations can receive the activity.

Use this inheritance for a group-wide program. It avoids maintaining the same activity against every child organization separately.

Restrict visibility to the selected parent only

Enable Restrict Storefront access to activity for suborganization members when the activity should be visible to members of the selected organization but not to any organization below it.

In the example above, selecting Watershed Corp with this restriction means:

• Watershed Corp members can see the activity.
• Denmark, Sweden, Sales, and Operations members cannot see it through inherited organization visibility.

Use this for parent-company leadership, central administrators, holding-company staff, or another audience stored at the parent level.

When this checkbox is selected, descendant selection is no longer needed because all suborganization levels are excluded.

Suborganization visibility

When a specific suborganization is selected, the activity is visible to:

• Users in that suborganization
• Users in any nested suborganizations below it, unless a deeper restriction is configured

It is not inherited upward. Users who belong only to the parent organization do not see an activity assigned to a child.

For example, selecting Watershed Corp Denmark makes the activity available to Denmark, Sales, and Operations. A user connected only to Watershed Corp or Watershed Corp Sweden does not receive it.

This downward—but not upward—inheritance is important when testing. A parent administrator's own participant profile does not automatically behave like a member of every child organization.

Select a deeper suborganization branch

If descendant access remains enabled, the Suborganization selector lets you choose a particular branch or nested level. A number shown beside a suborganization indicates how many nested suborganizations are included beneath it.

Selecting a suborganization includes that selected node and the nodes nested under it. It does not include:

• Sibling suborganizations on the same level
• The selected suborganization's parent
• Other branches elsewhere in the hierarchy

This lets one activity target, for example, the Operations branch without also targeting Sales.

Use Access restriction level

The Access restriction level selection refines how deeply visibility should continue below the selected suborganization. Use it when the chosen branch is correct but members beyond a particular nested level should be excluded.

Think of the two selections as a boundary:

• Organization/Suborganization establishes where the eligible branch begins.
• Access restriction level determines which deeper nested levels are no longer included.

Because organization structures differ, always validate the result with actual test users at the selected node, its parent, its siblings, and every affected child level. A hierarchy diagram and a short audience statement are useful acceptance criteria.

Example business statement:

Make the program visible to Watershed Corp Denmark and its direct departments, but not to teams nested below those departments.

Understand the Organization layer

The platform-level Organization layer applies organization-based filtering more broadly. It changes which privileged roles can bypass normal organization visibility.

When the Organization layer is off:

• Users with the permission Allow to see all courses and filter users by organizations can see activities limited by organization.
• This commonly includes Administrator, Global Administrator, Platform Administrator, Affiliate Administrator, Course Administrator, Support, and Assistant roles, depending on the platform's permission setup.

When the Organization layer is on:

• Administrator and Global Administrator can see all activities in the Storefront regardless of organization assignment.
• Other roles follow the normal organization-based visibility rules.
• A user outside the assigned organization cannot see the activity and cannot normally open it as an available offer by direct link.

Roles and permissions may be customized. Test the roles used on your platform instead of relying only on their names.

The activity setting and the Organization layer solve different problems

The activity feature declares the intended organization audience. The Organization layer controls broader content segregation and which administrative roles are subject to that audience filtering.

Storefront search and direct links

Storefront search results follow what the user is allowed to see. An organization-targeted activity that is outside the user's audience should not appear as a normal search result.

Direct-link behavior depends on the broader Storefront and Organization-layer configuration. Where direct-link access is enforced, a user outside the organization receives an Unavailable to your organization message instead of an Enroll button.

An anonymous visitor normally cannot see an organization-targeted activity because Eurekos has no authenticated organization relationship to evaluate. A Custom URL used as an organization alias can provide organization context and may make the targeted offer visible through that route.

Test all intended entry points:

• Normal Storefront browsing
• Storefront search
• The Activity Description URL
• Organization-specific Custom URL
• Links in email or another portal
• Manager and administrator enrollment routes
• API and QR enrollment, when used

Users with several organization relationships

Where a participant is connected to several organizations, a matching eligible relationship can make the activity visible. Verify actual profile relationships and the hierarchy beneath each one.

Do not infer organization from email domain, job title, manager, or an external CRM label unless an integration explicitly maintains the Eurekos profile relation. Organization visibility evaluates the stored organization structure.

Interaction with other activity settings

Organization targeting is one condition in a larger availability decision. A correctly matched user may still not see or enter the activity because of:

• Activity status or publication state
• Storefront section, category, or other audience targeting
• Available from and Schedule dates
• Latest registration
• Language or portal context
• No available seats when waiting list is disabled
• External Storefront hiding
• Self-enrollment requirements
• Participation Approval
• Price and checkout conditions
• Linked/repeated activity option filtering

Conversely, an administrator may be able to see the activity because of elevated permissions even though a normal participant in the same organization cannot.

Existing Training modules

An Existing Training module can present one or several previously created activities as enrollment choices. The choices are filtered by the participant's organization visibility.

If a candidate activity uses the Organization feature, users outside the selected organization or suborganization should not receive it as a selectable option. The filter also needs to be considered alongside available seats, dates, linked-activity rules, and other Storefront conditions.

This matters when a parent program is visible broadly but its delivery options are targeted locally. Test both layers:

1. Can the user see and enroll in the parent activity?
2. Does the Existing Training selector show only the delivery options that user may choose?

For more detail, see Existing Training (nesting).

Organization visibility and repeat or clone workflows

Treat organization assignment as business-sensitive data when cloning or repeating an activity. Before publishing the new activity, verify:

• The selected organization and suborganization
• Descendant restrictions
• Access restriction level
• Storefront section and Custom URL context
• Prices, seat allocations, and approvers that may be customer-specific
• Administrators, instructors, and email recipients

Do not assume that every related setting is copied or synchronized. Review the new activity as if it were a new offer, especially when it is created for a different customer or business unit.

Realistic use cases

Verify the configuration

Use representative accounts and the routes enabled for your delivery. Check the relevant outcomes before launch and after a material change; an administrator preview alone does not verify the participant experience.

Troubleshooting