Jörg Hoh wrote... Hi, To 1) and 2): Try to avoid to put access control down to a page level; it is possible and there are usecases for it, but doing so gives makes you a lot of work to define, implement and maintain it. It is constant work! And while technically you can even implement access control...

smacdonald2008 wrote... Follow the Adobe docs - if you think its wrong - please file a ticket. I wish we had more content for this use case - but the docs are the only source of content that is applicable. Is there a document that covers how to do this in a multi-tenant environment, (with pros and c...

Does anyone have any ideas/alternate solutions with various pros and cons, for resolving this issue?

In an AEM 6.1 environment with multiple sites deployed to the same instances, how could we go about extending/customizing the DAM asset editor in a way where all projects could add a few custom meta-data fields to the fields that come with the out of the box asset editor? Is it as simple as naming e...

Thanks Jorg!

1. What is the best means of providing granular access at the page level?2. What is the best means of providing access down to the field level?3. What is the difference between ACL's and ACP's, (i.e. Access Control Policies)? I'm assuming that in most general cases, using ACL's is the best option to...

alin7ilie wrote... So was this solved? I'm seeing the exact same issue. As bsloki suggested, please log a daycare ticket and then report back with the resolution. If enough of us log tickets, they may go ahead and determine the root cause of the issue instead of just saying you should restore from y...

bsloki wrote... It looks like an issue. Even I am facing the same problem. Please log a daycare ticket I logged daycare tickets, but they were not able to help. They had me go through all of the basic steps, but ultimately told me to restore from my backup, (which isn't much helped in resolving the ...

Didn't Adobe switch/change the implementation for user and group permissions from 5.6.1 to 6.1 from rep:policy nodes to rep:permission nodes? If that's the case, why are rep:policy nodes showing up in my AEM 6.1 installation? It could also explain some of the issues I mentioned in the other thread r...

smacdonald2008 wrote... I have passed this question to AEM support - you need input from support. There is some sort of bug here. One other question. Are rep:policy nodes supposed to be a part of AEM 6.1??? I thought you switched to a new ACL mechanism/implementation with the move from 5.6.1, to 6.1...