Community Connection - Article

What Community Connection helps you achieve

Community Connection gives the people involved in a Training Activity a shared collaboration space alongside the formal learning journey.

It is useful when participants should be able to:

• Ask questions before, during, or after training.
• Share files, examples, experiences, and follow-up resources.
• Continue a cohort discussion between scheduled sessions.
• Work with instructors or responsible administrators outside the course content itself.
• Participate through a collaboration tool already used by the organization.
• Join a Community of practice that spans several deliveries of related training.

The Training Activity remains the controlled learning record. It holds enrollment, schedules, modules, progress, completion, certificates, and reporting. The connected Community, Team, or channel provides the collaborative environment around that record.

A connection is an operating model—not merely a shortcut

Connecting an activity can add people to another space and, for Microsoft Teams, can also create activity signups from Team membership. Disabling the connection can remove members and can delete the connected platform Community. Decide which system governs membership before enabling the feature.

Decide whether an activity connection is the correct design

Use Community Connection when membership in the collaboration space should follow participation in a particular Training Activity.

Use another mechanism when the collaboration group has an independent audience or lifecycle.

Avoid connecting a Community simply because the feature is available. A collaboration space without an owner, facilitation plan, purpose, or retirement decision often becomes confusing or inactive.

Understand the available connection types

Community Connection is an activity-level feature. It becomes available when at least one supported Community capability is enabled for the platform.

The connection types share a purpose but not an identical lifecycle. Read the section for the selected type before connecting an activity that already has participants or an established external membership.

Confirm platform prerequisites

Community Connection is shown when one or more of the following is enabled:

• Native Eurekos Communities
• Microsoft Teams integration
• Slack integration

Native Communities are activated at platform level. Microsoft Teams and Slack also require their corresponding third-party integration to be configured.

For an external service, platform activation alone may not be sufficient. The connected account, application permissions, tenant or workspace policies, and the administrator's rights in the external system determine which Teams or channels can be selected and what Eurekos can do with their membership.

Before configuring a connection, confirm:

• The intended Community capability is enabled.
• The third-party integration is healthy where applicable.
• The administrator can see and select the intended external resource.
• Participant identities can be matched across Eurekos and the external service.
• External guests are permitted where the training serves customers or partners.
• Membership changes initiated by synchronization comply with the organization's privacy and access policies.

For platform activation, see General Settings. For the Microsoft integration, see Microsoft.

Permissions and ownership

The administrator configuring Community Connection must be able to edit the Training Activity. Managing the resulting collaboration space can require additional permissions:

• A native Community needs a defined owner and suitable moderation permissions.
• A Microsoft Team remains subject to Microsoft Entra, Microsoft Graph, tenant, Team, and account permissions.
• A Slack channel remains subject to the workspace's channel and application permissions.
• Activity responsibility does not automatically grant every administrative permission in the external service.

Define ownership before launch:

• Learning owner—decides why collaboration is part of the training design.
• Activity administrator—configures the connection and manages activity participation.
• Community owner or facilitator—moderates the collaborative space and responds to participants.
• Integration owner—maintains Microsoft or Slack credentials, permissions, and service health.
• Data and security owner—approves membership, retention, external access, and offboarding rules.

Do not rely on one person being implicitly responsible for all five areas.

Plan the membership lifecycle before connecting

Answer these questions before selecting a Community, Team, or channel:

1. Should collaboration membership be governed by activity enrollment or by another audience rule?
2. Does the activity already contain participants?
3. Does the intended Team or channel already contain members?
4. Should one collaboration space serve one cohort or several cohorts?
5. Who owns moderation and participant support?
6. What should happen when a participant is cancelled or an activity ends?
7. Will the space remain useful after training completion?
8. Who may approve disconnection or replacement?
9. What information and files will remain in the collaboration space?
10. How will account changes, external guests, and departed users be handled?

These questions are especially important for Microsoft Teams and Slack because connecting an existing external population does not produce a symmetrical initial synchronization.

Configure Community Connection

1. Open Course Administration → Activities.
2. Open the intended Training Activity and edit it.
3. Go to the activity-level Features.
4. Add or enable Community connection.
5. Select the available connection type.
6. Create or select the intended native Community, select the intended Microsoft Team, or create or select the intended Slack channel.
7. Complete the displayed ownership or connection information.
8. Save the Training Activity.
9. Verify membership on both sides with representative test users.

The exact fields depend on the enabled Community type and integration configuration.

The selected connection becomes locked

After a Community, Team, or channel has been assigned through Community Connection, its selection fields are disabled. You cannot simply replace it with another space. Changing the connection requires disabling the feature first, which can remove participants and delete a connected native platform Community.

Do not use disable and re-enable as an exploratory way to compare available spaces.

Connect a native Eurekos Community

For a native Community, the activity can:

• Create a new Community for the Training Activity.
• Connect an existing Community.

Create a new Community when the collaboration space belongs specifically to this cohort or learning journey. Select an existing Community when several activities should contribute members to a longer-lived Community of practice.

When creating a native Community, complete the available Community information and assign an appropriate Community owner. The owner should understand both the learning purpose and the expected moderation work.

What happens when the native connection is saved

When a native Community is connected:

• Existing activity signups are added to the Community.
• New participants are added as they enroll in or are registered for the activity.
• Users added to the activity as Responsible are added to the Community.
• Users removed from the activity as Responsible are removed from the Community.

The Community provides collaboration, but it does not change the participant's Course, Event, Assignment, certificate, or activity completion rules.

Use an existing Community across several cohorts

Connecting several Training Activities to one existing native Community can support:

• An alumni or professional Community that continues between deliveries.
• Product training cohorts that share implementation experience.
• A certification Community serving current and previously certified participants.
• A partner Community supported by several regional activities.

This model also creates shared membership ownership. Before using it, decide:

• Whether cancelling a participant from one activity should affect continued Community membership.
• Whether a participant enrolled through another connected activity should remain.
• Which activity administrators may disconnect from the shared Community.
• Whether the Community should survive the retirement of any one activity.

Because disabling Community Connection can delete the platform Community used by the activity, review every connected cohort and Community dependency before disconnecting a shared space.

Understand Microsoft Teams synchronization

A Microsoft Team connection can serve two related purposes:

• Add future activity participants to the connected Team.
• Create activity signups for members of the connected Team.

These directions do not initialize in the same way.

Initial connection behavior

When an activity is connected to a Microsoft Team for the first time:

This distinction is critical. If an activity already has 100 participants and is then connected to a new or empty Team, those 100 participants are not backfilled into the Team by the initial connection.

Do not promise existing participants immediate Team access until the actual Team membership has been verified.

Ongoing behavior after connection

While the connection is active:

• New activity signups are queued to be added as Microsoft Team members.
• New and existing Microsoft Team members can be processed into activity signups.
• Team-to-activity processing uses Microsoft notifications and background processing.
• Synchronization can take time; it should not be treated as an immediate transaction.

Use Eurekos participant management for an intentional cancellation and verify both systems after any exceptional cleanup.

A Microsoft Team collaboration connection is not a Teams meeting

Connecting a Team gives participants a shared collaboration space. Configuring Microsoft Teams as an Event's video-conference tool creates or supplies a meeting used at a scheduled time. An activity can need either capability or both, but they are configured and governed separately.

Microsoft identity and invitation considerations

External and newly matched users may require Microsoft invitation or account-connection steps before they can participate fully in the Team. Microsoft tenant policy, guest access, consent, and Graph permissions can affect the outcome even when the Eurekos activity signup exists.

Verify the participant's:

• Eurekos account and activity signup
• Email or other matched identity
• Microsoft invitation status
• Microsoft account or guest access
• Team membership
• Ability to open the Team

Do not treat a successful activity enrollment as proof that the external identity can already access Microsoft Teams.

Understand Slack-channel synchronization

When the Slack integration is configured, Community Connection can connect a Training Activity to a new or existing Slack channel. Use this when Slack is the organization's established collaboration environment and the channel has a defined training purpose, owner, moderation plan, and post-training lifecycle.

The Slack connection supports a specific initial import followed by one-way, activity-driven membership synchronization. Plan the order of connection and enrollment carefully because people who already belong to the activity are not treated in the same way as people enrolled after the connection is active.

Confirm the Slack integration and workspace prerequisites

A platform or integration administrator must first create and install the Slack app and save its Bot User OAuth Token under Settings → Third-party integrations → Slack.

Before connecting an activity, confirm that:

• The Slack app is installed in the intended workspace.
• The Bot User OAuth Token is current.
• The app has been added to an existing channel before that channel is selected in Eurekos.
• Participants have real email addresses that can be matched with their Slack identities.
• The users already belong to the configured Slack workspace or app. The integration does not automatically add an unknown user to Slack before adding them to a channel.
• Workspace permissions allow the Slack app to remove members when activity participation is cancelled or the connection is disabled.

Create or select the Slack channel

1. Edit the Training Activity and enable Community connection.
2. Select Connect new Slack channel or Connect existing Slack channel.
3. For a new channel, enter the required channel name. It can contain lowercase letters, numbers, hyphens, and underscores, with a maximum of 80 characters.
4. For an existing channel, select it from the available channels and confirm that the Slack app has already been added to it.
5. Save the Training Activity.
6. Verify the resulting activity signups and Slack membership with representative users.

After the channel is connected, the selection fields are disabled. To use another channel, Community Connection must first be disabled, which removes the relationship and starts the participant-removal process described later in this article.

Understand the initial connection behavior

When a Slack channel is connected for the first time:

This means connecting a new or empty Slack channel after enrolling a complete cohort does not backfill that cohort into the channel. Connect Slack before creating the activity signups when all new participants should enter the channel through the normal synchronization flow.

Channel members becoming activity signups can also affect capacity, pricing, participation approval, organization targeting, Mandatory deadlines, and other activity processes. Review whether everyone already in the channel should become a participant before connecting it.

Understand ongoing synchronization

After the connection is active:

• A new activity signup is queued for addition to the Slack channel.
• Reactivating an activity signup queues the user for addition to the channel.
• Cancelling an activity signup queues the user for removal from the channel.
• The synchronization is asynchronous, so the activity and Slack can differ temporarily while the job is processed.
• A user who has not already been added to the configured Slack workspace or app is not automatically added to a new or existing channel.

Ongoing changes made directly in Slack do not update the Training Activity. Adding someone directly to the channel is not the normal enrollment process, and removing someone directly from Slack does not cancel their activity signup. Manage intended participation changes in the Training Activity and verify the resulting channel membership after processing.

The initial import of existing channel members is the exception: it occurs when the channel connection is established or re-established.

Understand what participants see

Participants connected to Microsoft Teams and Slack channels can see those external spaces in the Communities widget on My Overview and in their Profile.

The external service still determines whether the user can enter after opening the link. A visible Team or channel link does not override Microsoft or Slack identity, guest, workspace, or membership requirements.

External-widget visibility is a special case

Activity-connected Microsoft Teams and Slack channels can remain displayed in the Communities widget even when:

• The platform Community configuration is disabled.
• Hide widget on My Overview and Profile is selected.

Do not use the general widget-visibility setting as the only control for hiding an external activity-connected link. Test the actual participant view and remove or disconnect the underlying relationship only through an approved lifecycle process.

Disable Community Connection safely

Disabling Community Connection is a consequential action. Eurekos displays a warning explaining that participants will be removed from connected communities and that the platform Community used in the activity will be deleted.

Before confirming:

• Identify the exact native Community, Microsoft Team, or Slack channel.
• Review its members and all activities or processes that depend on it.
• Confirm whether the collaboration content must be retained or exported.
• Notify the Community owner, facilitators, and integration owner.
• Decide whether participants need another communication space.
• Record the business reason and approver.
• Test the impact in a non-production activity where practical.

Disabling a native Community connection

When the feature is disabled for a native Community:

• Participants are removed from the connected Community.
• The platform Community used for the activity is deleted.
• The activity no longer has a Community connection.
• New activity signups are no longer added.

Treat this as deletion, not merely unlinking. If the Community contains discussions, files, tasks, events, or historical collaboration that must be retained, resolve retention before confirming the action.

Disabling a Microsoft Team connection

When the feature is disabled for Microsoft Teams:

• The Team is no longer connected to the Training Activity.
• Synchronization stops.
• Users are queued for removal from the Team.
• Removal is asynchronous and is handled by a background process that runs approximately every five minutes.

Membership can therefore remain visible briefly after the connection is disabled. Wait for background processing and verify the Team before treating removal as failed.

The source documentation describes removing users from the Team. It does not state that disabling the connection cancels their Eurekos activity signups. Treat Team membership and activity participation as separate records when verifying the result.

Disabling a Slack channel connection

When Community Connection is disabled for Slack:

• The Slack channel is no longer connected to the Training Activity.
• Synchronization stops.
• Users are queued for removal from the channel.
• Member removal is asynchronous and is handled by a background process that runs approximately every five minutes.
• The external Slack channel is not described as being deleted; the deletion warning applies to a native platform Community created for the activity.

Allow the removal process to run, then verify both the Slack channel and the activity. Disabling the connection removes channel membership and stops synchronization; it does not cancel the activity signups.

Re-enable or replace a connection

After Community Connection has been disabled:

• The connection field is empty.
• The same or another available Community, Team, or channel can be selected.
• The new connection establishes a new synchronization relationship.

Re-enabling the feature does not restore every connection type in the same way.

Reconnect a native Community

When a native Community is connected after re-enabling:

• All current activity signups are added to the selected Community.
• Future activity participants are added automatically.
• The deleted Community from the earlier connection is not implicitly restored; select or create the intended current Community.

Reconnect Microsoft Teams

When a Microsoft Team is connected after re-enabling:

This is the same important asymmetry as the initial connection. Reconnecting a Team is not a method for backfilling all existing activity participants into it.

Reconnect Slack

When Slack is connected after re-enabling Community Connection:

The connection field is empty after the feature is disabled, so the same or another available Slack channel can be selected. Reconnection is not a method for backfilling all existing activity participants into Slack.

Account merging with a Microsoft Team connection

When two Eurekos user accounts are merged, one account is the source being absorbed and the other is the target that remains.

For an activity connected to Microsoft Teams, the documented behavior is:

In Eurekos

• The source user is removed from the Training Activity.
• The target user appears in the activity.

In Microsoft Teams

• The source user remains in the Team.
• An invitation is sent to the target user.
• The target user appears in the Team after accepting the invitation.

The merge can therefore leave the source identity in Microsoft Teams even though Eurekos now uses the target account. Include external-Team cleanup in the account-merging procedure; do not assume the Eurekos merge removes the old Microsoft identity.

Coordinate Community Connection with enrollment

For a native Community, activity participation normally drives Community membership. For Microsoft Teams and Slack, existing external members can also become activity signups when the connection is established.

Review every relevant route that can add people to the activity:

• Administrator enrollment
• Self-enrollment
• Import
• Onboarding Rules
• Invitations and approval
• Waiting-list promotion
• Existing Training enrollment
• Subscription or commerce workflows
• API or integration processes
• Microsoft Team membership
• Slack channel membership when a channel connection is established

After testing a route, confirm both the activity signup and the expected collaboration membership. A signup can exist before an external membership is processed, and an external identity problem can prevent practical access to the collaboration space.

Direct Community assignment can overlap

An Onboarding Rule can add a user directly to a native Community. A Training Activity connection can add the same user because of activity participation.

Avoid using both routes for the same population unless the overlap is intentional. Otherwise, administrators may not know whether cancelling the activity, changing the onboarding audience, or disabling the connection should own the membership lifecycle.

Define one governing rule wherever possible:

• Activity participation governs a cohort Community.
• Profile criteria govern a role-, region-, or customer-based Community.
• Manual Community membership governs individually approved exceptions.

Coordinate Community Connection with responsible users

For a native Eurekos Community, users added to the Training Activity as Responsible are added to the Community, and users removed as Responsible are removed.

This supports instructors and administrators who need to facilitate the cohort. It does not by itself define:

• Community ownership
• Moderation responsibilities
• Response-time expectations
• External Microsoft or Slack permissions
• Event-host or video-conference roles

When changing the Responsible field, verify the resulting Community membership and ensure that at least one approved facilitator or owner remains available.

Clone and repeat activities

Community Connection is an exception to the usual copying of enabled activity features.

Clone

When a Training Activity is cloned:

• The Community, Team, or Slack channel connection is not copied.
• Community Connection is disabled in the cloned activity.
• Other supported feature information can still be copied.

This prevents a copied activity from silently enrolling its new participants into the source cohort's collaboration space.

Repeat

The recurring-delivery workflow likewise does not carry the Community, Team, or Slack channel connection into the repeated activity. After repeating the activity, decide deliberately whether the new delivery should:

• Receive its own new Community.
• Connect to a new external Team or channel.
• Join an existing cross-cohort Community.
• Have no connected collaboration space.

Configure and test the selected connection before enrolling the new cohort. Do not assume synchronization is active because the source delivery had it.

Change or retire a live collaboration design

Changing a connection affects people, access, and potentially retained collaboration content. Treat it as a controlled change.

Before changing a live activity:

1. Identify current participants, responsible users, Community members, and external members.
2. Determine which system currently governs each person's membership.
3. Preserve required discussions, files, decisions, and records.
4. Review data-retention and external guest-removal obligations.
5. Choose the replacement collaboration space, if any.
6. Explain expected interruption and access changes to participants.
7. Disable only after the deletion and removal effects are approved.
8. Wait for external background synchronization where applicable.
9. Configure the replacement connection.
10. Verify both old and new memberships with named owners.

Do not make this change immediately before a scheduled session or deadline unless the risk and communication have been deliberately managed.

Verify the connection

Save the connection, then use representative accounts rather than relying only on the administrator view. Use the rows relevant to your native Community, Microsoft Teams, or Slack connection; you do not need to test integrations that the activity does not use.

Practical configuration patterns

Troubleshooting