If you manage several Riot workspaces within the same organization, you can define a shared awareness programme and roll it out to your workspaces, instead of rebuilding it in each one.
💡 Prerequisite: this feature is reserved for customers with organization management. If you don't see the options described here, contact us via the chat.
1️⃣ Defining the organization's programme
The organization's programme is built from the master workspace, using the same editor as a standard programme. It can contain:
Riot courses from the catalogue;
Studio courses created in your workspaces, provided they have been made visible to the organization (see section 3️⃣).
2️⃣ Importing the programme into a workspace
👉 Step 1: Go to the workspace concerned, on the Programme page.
👉 Step 2: Click Import programme. The organization's programme replaces the workspace's own, and the employees of that workspace now follow it.
⚠️ Important: the import creates a copy. A change made afterwards at organization level does not automatically flow down to workspaces that have already imported the programme: you need to run the import again.
⚠️ Important: only the programme is imported. The Awareness module settings are not — reminders, prelude, and the settings specific to certain courses such as the company leader's name or the recommended authentication app. Those still have to be set workspace by workspace.
3️⃣ Sharing a Studio course with the organization
A Studio course created in a workspace is only visible in that workspace. To be able to include it in the organization's programme, you have to explicitly make it visible to the organization from the course itself.
This is a manual, deliberate action: without it, the organization's programme cannot contain that course, since the other workspaces would have no access to it.
👍 Good to know: making a course visible to the organization doesn't add it anywhere automatically and doesn't deliver it to anyone. It only makes it available for selection when building the organization's programme.
Organization administrators can also create and edit Studio courses directly at organization level, without going through a workspace.
4️⃣ Points to watch
👉 The workspace must genuinely belong to the organization
If the import button doesn't appear on a workspace, the most common reason is that this workspace isn't attached to the organization — even if it has a similar or identical name. Contact us via the chat to attach it.
👉 The models must be aligned
Copying the programme is blocked when the organization and the workspace don't run on the same model. An organization programme built for Cyber Missions cannot be imported into a workspace still on the previous model, and vice versa.
👍 Good to know: an organization and its workspaces can move at different speeds: you can migrate your organization to the new model while keeping some workspaces on the old one. Only copying the programme between different models is prevented.
Key takeaways
The programme is defined in the master workspace, then imported workspace by workspace.
The import is a copy: later changes do not propagate.
Only the programme is imported, never the module settings.
A Studio course must be made visible to the organization to appear in it.
The organization and the workspace must run on the same model.