> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wejam.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Rolling Out JAM to Your Organization

> A short checklist for Admins: prepare, build content, launch, and keep training.

## Overview

A rollout has four steps. Mark each item as done when you finish it.

## 1. Prepare

**1.1 Assign responsibilities.** Choose three people: one for content, one for coaching, and one for setup. See [Assigning Roles to Users](https://docs.wejam.ai/external/admin/assigning-roles.md) for what each role can do.
*Done when:* each person knows their job.

**1.2 Get your leaders' support.** Explain to your leaders why you use JAM and ask them to back the rollout. Ask for approvals early: IT security, the data processing agreement (a privacy contract), and your employee council, if you have one. IT security often starts with [How Jam Uses AI](https://docs.wejam.ai/external/admin/ai-security-faq.md).
*Done when:* leaders support the rollout and approvals are in progress.

**1.3 Set your goals.** Agree on the numbers JAM should improve, such as deals closed. Write down where they stand today.
*Done when:* each goal has a starting value and a target.

## 2. Build content

**2.1 Pick what to train.** Choose the customer conversations that matter most for your goals, and the skills behind them.
*Done when:* each target group has a short list of situations to train.

**2.2 Create training content.** Start with one track (a set of practice missions). JAM's learning experience design team can build it for you, or you build it yourself in [Jam Studio](https://docs.wejam.ai/external/studio/creating-publishing-tracks.md). Let a few real learners test it.
*Done when:* your first track is approved and published.

## 3. Launch

**3.1 Set up your organization.** Do this in order. You can start while you build content.

1. **Single sign-on (SSO), if you want it.** Email [support@wejam.ai](mailto:support@wejam.ai). You get a setup link for your IT team. See [Setting Up Enterprise SSO](https://docs.wejam.ai/external/admin/saml-oidc-setup.md).
2. **Privacy and consent.** Choose your settings in [Organization settings](https://docs.wejam.ai/external/admin/account-settings.md).
3. **Teams.** Create your teams on the [Teams](https://app.wejam.ai/teams) page. A Coach sees only the learners in their own teams.
4. **Users.** Check that you have enough [seats](https://docs.wejam.ai/external/admin/billing-and-plan-limits.md). Pending invites use seats too. Then [invite your users](https://docs.wejam.ai/external/admin/managing-user-accounts.md).

*Done when:* login works, teams exist, and users are invited. If an invite doesn't arrive or a first login fails, see [Fixing Invitation and First-Login Problems](https://docs.wejam.ai/external/admin/invite-and-login-troubleshooting.md).

**3.2 Train your team and start.** Train your content owners and coaches first. Then hold a short start meeting where everyone plays a first mission. Assign the first track with a due date.
*Done when:* everyone has played once and the first track is assigned.

## 4. Keep training

**4.1 Run training cycles.** Every few weeks, assign a new [sprint](https://docs.wejam.ai/external/coaching/assigning-sprints.md): one track for a whole team, with one due date. [Review progress](https://docs.wejam.ai/external/coaching/monitoring-team-progress.md) and talk about results in team meetings. Turn new needs into new content.
*Done when:* each team trains regularly, every few weeks.

> [!TIP]
>
> Questions at any step? Email [support@wejam.ai](mailto:support@wejam.ai).

## Related articles

* [Understanding Who Sees Learner Data](https://docs.wejam.ai/external/admin/how-visibility-works.md) - who sees which learner data
* [Creating and Managing User Accounts](https://docs.wejam.ai/external/admin/managing-user-accounts.md) - inviting your users
* [Assigning a Sprint to Your Team](https://docs.wejam.ai/external/coaching/assigning-sprints.md) - the first sprint after the start meeting

***

*Last updated: November 2026*


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.