The following section explains how to segregate projects using ACLs so that each individual or team handles their own project.
As an AEM administrator, you want ensure that team members of a project do not interfere with other projects and each of the users are assigned sepecific roles as per project requirements.
|/apps/<project>||READ||Provides access to project files (if applicable)|
|/content/dam/<project>||ALL||Provides access to store the projects assets such as images or video in DAM|
|/content/screens/<project>||ALL||Removes access to all other projects under /content/screens|
|/content/screens/svc||READ||Provides access to the registration service|
|/libs/screens||READ||Provides access to DCC|
|/var/contentsync/content/screens/||ALL||Allows to update offline content for the project|
In some cases, you can separate author functions (such as managing assets and creating channels) from admin functions (such as registering players). In such a scenario, create two groups and add the authors group to contributors and the admin group to both contributors and user-administrators.
Creating a new project should also create default user groups with a basic set of permissions assigned. You should extend the permissions to the typical roles we have for AEM Screens.
For example, you can create the following project specific groups:
- Screens Project Administrators
- Screens Project Operators (register players, and manage locations and devices)
- Screens Project Users (work with channels, schedules and channel assignments)
The following table summarizes the groups with description and permissions for an AEM Screens project:
|Admin level access for AEM Screens capabilities||
|Create and update channels and schedules and assign to location in AEM Screens||
|Create and update location structure and register players in AEM Screens||
|Groups all players and all players/devices are member of the contributors automatically.||
Member of Contributors