We have a large number of users involved in the creation of Self-Paced Labs and SCORM-based modules. Right now if a user is assigned to 1 Lab Series they gain access to all the labs in both Dev and Prod through the LOD development environment. It would be advantageous to be able to lock them down to just the object(s) that they are responsible for.
I see a system, similar to the TMS Subscriptions, that can be used to lock down the Development environment and focus the users on the work they need to do. This could prevent them from even seeing any non-related Lab Series.
| Who would most benefit from this idea? | Lab Developers or Lab Authors |
This would require a deep revision to permissions.
An immediate solution to this problem is using "Sub-Orgs". These would be children of your main development org, and you can assign specific developers to different ones rather than the master dev org. This would permit for example Developer 1 to have access to "Org A and B" and Developer 2 to have access to "Org B and C". This allows both developers access to series within Org B, but only one of them each would have access to series within Orgs A and C. Support can help with setting this kind of thing up.