How do AEM Launches work for multiple projects with different users? Can ACLs restrict per project?

[James16]

We are looking to start using the launches feature of AEM within an established space where multiple projects exist.  We have users who can only view one or some of all the projects, all fully controlled via different groups with ACLs that restrict on the pages within /content and the folders within /content/dam.  In both cases, the projects are mostly at the first level within that.

So we have /content/foo and /content/bar as two distinct spaces with different groups.  But if I create a launch from project foo, it goes into /content/launches/2024/07/17/<name from wizard> without "foo" at any point.

Is it possible to prevent users of project "bar" who wouldn't be able to read or edit the page the launch was created from, from being able to see and edit the launch copy?

I have read all the available documentation for launches in AEM and have not found any references to restrictions based on multiple sites.  Any guidance will be greatly appreciated.

[RahulBGPandey]

Hi James,

I have also gone through most of the documentation related to the AEM launch, but I didn't find anything related to Access control on Launches. But We can write the custom script to assign the same permission as the pages for which the launch is created. we can trigger it using workflow or event listener (on the node creation event) under /content/launches.

[kautuk_sahni]

@James16 Did you find the suggestion helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!

[James16]

I connected Adobe support.  They have acknowledged this isn't currently supported, therefore there is no answer to the question.

[James16 · Accepted solution]

This is from Adobe Support:

There doesn't seem to be any easy way to do this. You could create a new group for each Launch. I'll make a feature enhancement request to find a better way to handle this.

---