Setting up ACLs setting-up-acls
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 to ensure that team members of a project do not interfere with other projects and each of the users are assigned specific roles as per project requirements.
Setting up Permissions setting-up-permissions
The following steps summarize the procedure for setting up ACLs for a project:
-
Login to AEM and navigate to Tools > Security.
-
Click Groups and enter an ID (for example, Acme).
Alternatively, use this link,
http://localhost:4502/libs/granite/security/content/groupadmin.html.Next, click Save.
-
Click Contributors from the list and double-click it.
-
Add the Acme (project that you created) to Add Members to Group. Click Save.
note note NOTE If you want project team members to register players (which involves creating a user for every player) find the group user-administrators and add the ACME group to user-administrators -
Add all the users who are working on the Acme Project to the Acme group.
-
Set up the permissions for the group Acme using this
(http://localhost:4502/useradmin).Click the group Acme and click the permissions.
Permissions permissions
The following table summarizes the path with the permissions at the project level:
/apps/<project>/content/dam/<project>/content/screens/<project>/content/screens/svc/libs/screens/var/contentsync/content/screens/Creating Groups creating-groups
Creating a project should also create default user groups with a basic set of permissions assigned. Extend the permissions to the typical roles defined in 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: