Knowledge base Rise Up

Forge and Rise Up Integration: Connect AI Coaching to Your Courses

  • Updated

 

Prerequisites

 This integration involves two separate admin surfaces. Access requirements differ depending on the task:

  • Forge Admin access is required to link a Rise Up company to a Forge workspace, and to create or configure coaches.
  • Rise Up Administrator access is required to view the linked Coaches page and assign coaches to courses.

Neither surface can perform the other's actions: Forge Admin cannot assign coaches to Rise Up courses, and Rise Up cannot create or configure a coach. Contact your Forge or Rise Up administrator if your role does not have the permissions needed to complete a step in this article.

Overview

Forge is an AI coaching companion that learners use to keep practicing after a course ends. Linking Forge to your Rise Up platform lets learners reach a coach directly from their course, their dashboard, and their learning history — without leaving Rise Up.

The integration follows five stages, each covered as a step below:

  • 1Before activation — Forge appears in the menu as a non-functional preview
  • 2Activation — an administrator links the Rise Up company to a Forge workspace
  • 3Configuration — the linked workspace unlocks Administration and Coaches entries in Rise Up
  • 4Assignment — coaches are made available on specific courses
  • 5Learner experience — assigned coaches surface across the learner journey

Forge Admin and Rise Up each own a different part of this workflow. Forge Admin owns coach creation and configuration; Rise Up owns coach distribution — which courses, and therefore which learners, can reach each coach.

Key elements
  • Workspace: the Forge environment linked to a single Rise Up company. All coach creation and configuration happens inside a workspace.
  • Hosting environment: the infrastructure (AWS, Azure, Scaleway, or OVH) a Rise Up platform runs on. A platform is only visible to Forge Admin within its own environment.
  • Company link: the connection between a Forge workspace and a Rise Up company, created from Forge Admin. It determines which Rise Up SSO users can reach the workspace.
  • Coach: an AI coaching agent created and configured in Forge — for example a coaching plan or an "ask me anything" format.
  • Assignment: the act of making a coach available on one or more Rise Up courses. This is a distribution setting, not a display setting, and it does not change what the coach knows.
  • Seat: a learner's access slot within the Forge workspace plan. A learner without a seat cannot open a coach until one is granted.

II — Link the company from Forge Admin

Audience: Forge Administrator.

Go to: Forge Admin > Workspaces > select the target workspace > Overview tab.

The Overview tab shows a Rise Up block with a badge indicating the current state (Not linked until a company is connected).

  1. Open Workspaces and select the target workspace.
  2. On the Overview tab, find the Rise Up block and click Link a company.
  3. Pick the hosting environment of the Rise Up platform: AWS, Azure, Scaleway, or OVH. A platform is only visible within its own environment.
  4. Search the company by name. Each result shows the label and the platform URL, so you can distinguish between two similarly named companies.
  5. Select the company and confirm with Link.

Result: The badge switches to the linked state, and the Forge entries in the Rise Up menu change from a preview to functional Administration and Coaches links (Section III).

Forge_link_thecompany.png

III — What the link unlocks in Rise Up

Audience: Administrator.

Once linked, the commercial Meet Forge entry disappears from the Rise Up menu and is replaced by two operational entries under Forge.

Entry Destination Purpose
Administration Forge Admin, opens in a new tab Create and configure coaches, manage the workspace, monitor quotas.
Coaches Native Rise Up page Review the workspace's coaches and make them available in courses.
Split of responsibilities
Forge Admin owns coach creation and configuration. Rise Up owns coach distribution — which courses, and therefore which learners, each coach is exposed to. The two surfaces do not overlap.

The Rise Up Coaches page lists every coach in the linked workspace, along with its type and its current level of distribution. A side panel offers search, a filter by type, and a direct link to Forge Admin through Manage coaches.

Forge_forgemenuaccessRU.png

IV — Make a coach available in courses

Audience: Administrator.

Go to: Rise Up > Forge > Coaches > Actions column on a coach row.

This is the pivotal operation of the integration: on its own, it determines everything a learner will see. A coach with no course assigned exists in the workspace but stays invisible inside Rise Up.

  1. Open the Coaches page and select the coach you want to distribute.
  2. In the Make this coach available in courses modal, use the search field or scroll the course list. Each course shows its type (e-learning, face-to-face, and so on).
  3. Check the courses you want the coach linked to.
  4. Click Save.

 

Result: Learners registered to the selected courses will be able to keep practicing with this coach after the course, from the entry points described in Section V.

 

Assignment does not configure the coach
Making a coach available in a course does not add that course's content to the coach. Assignment governs distribution only — who can reach the coach, and from where. What the coach actually knows, including the material it draws on to run its plan and exercises, is configured in Forge Admin, on the coach itself. Skipping that configuration step leaves learners with a reachable coach that knows nothing about the course they just finished.
Known limitation
Behavior when several coaches are assigned to the same course is not yet finalized. If you assign more than one coach to a course, verify in practice which coach the course card's Coach button opens before relying on it for learners.

V — How learners find their coaches

Audience: Learner-facing behavior (for admin awareness and support purposes).

Once a coach is assigned, Forge surfaces at several points in the learner journey. Two of them help a learner return to a coach already met; the others help a learner discover one from the course itself.

One-time email verification
The first time a learner opens a coach, Forge checks whether their Rise Up account has an email address on file. If it doesn't, an Add your email address screen (step 1 of 2) asks the learner to provide one before continuing — Forge needs it to secure the account and send a verification code. This is a one-time step per learner: once an email is confirmed, later coach openings go straight through without interruption.

1. The "My coaches" dashboard widget

A My coaches widget can appear on the learner's home dashboard, listing their most recent coaches with a See all link. This is the resumption entry point: a learner with no specific intent sees ongoing coaching conversations first.

Not displayed by default
This widget is not shown automatically. An administrator must add it to a custom homepage layout — go to Settings > homepage configuration, open the relevant homepage template (for example, Follow-up for my courses), and add the My coaches block from the widget list alongside other blocks like My courses or Community activity. Once saved, the widget appears for the learners assigned to that homepage.
Forge_learner_widget.png

2. The Coaches tab in My learning

A Coaches tab sits next to Courses, Learning paths, and has its own tab next to Resources in My learning called "Coaches". Each coach appears as a card showing its type, an excerpt of the latest conversation, how long ago it happened, and the progress rate. A search field and a course filter keep it usable as the number of coaches grows.

Separately, the Courses tab in My learning has its own With a coach checkbox filter, letting learners narrow their course list down to only the courses that have a coach assigned.

3. The Coach button on the course card

On courses with an assigned coach, a Coach button sits next to the card's primary action and opens Forge in a new tab, on the coach tied to that course. This is the button learners use to train with the coach directly from their course list.

4. The course completion modal

Rise Up's native course-completion modal includes a coaching block between the course recap and the suggested courses, inviting the learner to keep practicing with the assigned coach via an Open your coach action.

5. Inside the course player

The coach is visible in the left sidebar of the course player, above the module list, throughout the course. It is not clickable while the course is in progress — it becomes reachable only once the learner completes the course, at which point the block is highlighted and opens the coach.

Forge_widgetincourse.png

 

Visibility rules to know
A coach only becomes reachable for the first time once the learner completes its assigned course — from the course card, the completion modal, or the sidebar block described above. The dashboard widget and the Coaches tab, by contrast, are return points: they surface coaches the learner has already started a conversation with.

Both the dashboard widget and the Coaches tab list every coach a learner can reach — including coaches the learner was enrolled in directly within Forge, even if those coaches are not tied to any course the learner is registered to.

If no coach is available to a learner, Forge is entirely invisible to them: no dashboard widget, and no Coaches tab in My learning. Both surfaces only appear once at least one coach is reachable.

 

VI — When the plan has no seat for the learner

Audience: Administrator (for capacity planning) and Learner (fallback experience).

The learner experience described in Section V assumes the learner has a seat in the Forge workspace. If the workspace plan cannot accommodate them, none of the entry points opens a coach: the dashboard widget, the Coaches tab, the course card button, the player sidebar block, and the completion modal all lead to the same screen instead — a Request a seat for Forge modal.

This modal restates what the coach offers, names the coach the learner was trying to reach, and offers two actions: Not now and Request a seat.

Requests must be granted from Forge
Requesting a seat sends an email to the Forge administrators — the learner is told their administrator will be notified. Granting the seat is a Forge-side action driven by the plan and its quotas. Nothing in Rise Up can unblock it, so it's worth checking your coach quota before a rollout rather than after the first requests arrive.

 

FAQ & Troubleshooting

  • Issue Likely cause Resolution
    The company cannot be found when linking in Forge Admin. The wrong hosting environment is selected — a platform is only visible within its own environment. Confirm the Rise Up platform's hosting environment (AWS, Azure, Scaleway, or OVH) and re-run the search under the correct tab.
    The Forge menu in Rise Up still shows only "Meet Forge" after linking. The company link has not been confirmed, or the wrong company was linked. Check the Rise Up block on the workspace's Overview tab in Forge Admin — it should show the linked state, not "Not linked."
    A coach doesn't appear for a learner even though it's assigned to their course. The learner does not have a seat in the Forge workspace, so all entry points redirect to the "Request a seat" screen instead. Check the workspace's seat usage in Forge Admin and grant a seat if the plan allows it.
    A coach is configured in Forge but learners never see it in Rise Up. The coach has not been assigned to any course from the Rise Up Coaches page. Open the Coaches page in Rise Up and use the assignment action to link the coach to the relevant course(s).
    A coach answers questions unrelated to the course it's assigned to. Assignment only controls distribution — it does not configure what the coach knows. Open the coach in Forge Admin and update its configuration with the correct course material.
    The "Coach" button on a course card doesn't open the expected coach. More than one coach is assigned to the same course — which one opens is not currently guaranteed. Assign a single coach per course until this behavior is finalized.
    An administrator cannot find the "Link a company" option. This action requires Forge Admin access on the workspace record, not Rise Up Administrator access. Confirm which platform the action needs to be performed on before troubleshooting further.
    Requesting a seat doesn't grant learner access immediately. Seat requests only send a notification email to the Forge administrators. Granting the seat is a manual, Forge-side action governed by the plan's quota — check with your Forge administrator.
    Learners report they cannot see the "My coaches" widget on their dashboard. The widget only appears once at least one coach is reachable by that learner. Verify the learner has a seat in the Forge workspace and is registered to a course with an assigned coach.
  • Can one coach be assigned to more than one course?
    — Yes. The assignment modal in Rise Up allows a coach to be linked to any number of courses.

    Does assigning a coach to a course give it access to that course's content?
    — No. Assignment only controls distribution. What the coach knows is configured separately, in Forge Admin, on the coach itself.

    What happens if a learner's platform is unlinked from Forge after coaches were already assigned?
    — This scenario is not covered in current documentation. Contact support if you need to unlink a company and want to confirm what happens to existing assignments.

    Who can see a learner's coaching conversations?
    — This article does not cover coaching-conversation visibility. Refer to Forge Admin's own documentation for data access details.

    Can a learner reach a coach they were never registered to a course for?
    — Yes, if that learner was enrolled directly in the coach from within Forge. Direct Forge enrollments are not dependent on Rise Up course registration.
  • Contact Support
     

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request