SCORM 1.2 support: Outdoo courses now work with even more learning platforms
Outdoo courses now export as SCORM 1.2 as well as SCORM 2004 (4th Edition). Pick the version in the Export SCORM dialog to match your LMS.
Outdoo Permission Profiles control page access, whose calls people can open, the actions they can take and the settings they can manage, per workspace.
A contact center runs three client programs in Outdoo, each in its own workspace. A team lead on one program needs to review her agents' calls, but she should never open a call from another client's program, and she should not be able to change scoring settings. Until now the answer was a broad role and a hope that nobody clicked the wrong thing. Permission Profiles let you set exactly what each person can see and do, workspace by workspace.
Roles were too coarse for the way regulated and multi-team organizations actually work. A call recording can hold account numbers, health details or a customer's complaint, and the person who coaches a team is rarely the person who should see every team's calls. When the only options are "Manager" or "Admin," teams either over-share access or hold back the people who need it, and both cost something. Over-sharing creates an audit finding. Holding back slows coaching down.
Training only works when the right people can see the right practice and the right real calls. Permission Profiles make that a setting rather than a workaround.
Go to Settings > People Settings > Permission Profiles. You can start from one of the default profiles or create your own.
A profile controls four things: which pages a person can open, whose calls they can open, the actions they can take, and the settings they can manage.
Profiles apply per workspace, so the same person can have broad access in one workspace and read-only access in another. To build a new profile quickly, duplicate a custom one and change only what is different.
Permissions are only as good as the profile design behind them. Before rolling profiles out to a large workspace, test a custom profile on one person and check what they can and cannot open.
A compliance officer at an insurer limits call visibility so team leads see only their own agents' calls, and documents that setting for the next audit instead of describing a process.
A BPO operations director gives each client program its own workspace and its own profiles, so a team lead on one account never sees another client's customers.
An enablement lead gives regional trainers the right to build and assign roleplays and AI Trainers without giving them access to scoring settings or billing.
Who can see a call is a training decision as much as a security one, and it belongs with the people who run the program.
Outdoo courses now export as SCORM 1.2 as well as SCORM 2004 (4th Edition). Pick the version in the Export SCORM dialog to match your LMS.
In Outdoo roleplays, team members can share their screen. Outdoo tracks the demo, slides or video and tells managers if the right message went with it.
Link an LMS, Confluence or website and Outdoo builds AI Trainers, roleplays and scoring criteria from it, then re-syncs daily so they stay current.
A 30-minute walkthrough built around your team's calls. When you're ready, prove it with a proof of concept.