Setting up Access Control Lists (ACLs)
The following section explains how to segregate projects using Access Control Lists (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. Each user is assigned specific roles as per project requirements.
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 the Group. Click Save.
NOTEIf 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
The following table summarizes the path with the permissions at the project level:
| Path | Permission | Description |
|---|---|---|
/apps/<project> | READ | Provide access to project files, if applicable. |
/content/dam/<project> | ALL | Provide access to store the project 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 | Provide access to the registration service. |
/libs/screens | READ | Provide access to DCC. |
/var/contentsync/content/screens/ | ALL | Help you update offline content for the project. |
NOTECreating 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:
The Perfect Blend: A New Era of Collaboration with AEM and Workfront
Adobe Customer Success Webinars
Wednesday, Apr 2, 5:00 PM UTC
Explore how Adobe Experience Manager and Workfront integrate to help teams move from ideation to delivery without the usual bottlenecks, ensuring content is organized, on-brand, and ready to go live faster.
Register
Elevate and Empower Teams with Agentic AI for Exceptional Experiences
Elevate and empower your CX teams with AI that transforms creativity, personalization, and productivity. Discover how Adobe is...
Tue, Mar 18, 1:00 PM PDT (8:00 PM UTC)
3 Pillars of Purpose-driven Experiences: Trust, Data, and GenAI
Learn how leading B2B and B2C brands like AT&T and IBM are intersecting data, GenAI and trust to build “purpose-driven” experiences that...
Wed, Mar 19, 1:00 PM PDT (8:00 PM UTC)
Connect with Experience League at Summit!
Get front-row access to top sessions, hands-on activities, and networking—wherever you are!
Learn more