This procedure is similar to the previous one, except that the access rights you define here apply to a specific scenario rather than to a scenario folder.

Important: Bear in mind a user’s access rights for content repositories as well as his or her access rights for scenarios. For example, you might give a user write access to a specific scenario, but does he or she also need access to one or more content repositories? To create slot elements, for example, a user may need read access to a repository that stores image files. Make sure that users have access to all required content, and in particular, check that their access rights for different repositories do not conflict.

You can set access control for individual scenario templates in the same way that you can control access to individual scenarios and scenario folders.