Don't have CRXDE access

Could you elaborate your use case?

The 'title' of question made me think that you want to know how to get access on /crx/de console. Is this correct?

You could navigate to '/useradmin' and assign appropriate "read", "write" permissions to users/groups.

Yes, I would like to know which permission I must add to my user to allow read and modify the rest of the folders

He already has read/write permission under /content/myproject/

Hence, I would say for the new AEM version we need to add another special permission.

On /crx/de console, the nodes are listed based on user's permissions.

You'd need to navigate to localhost:4502/useradmin > Login with admin account > Search the user/group whose permissions you'd like to modify > Double click on that user once it is listed in the search list on left panel > Click on Permissions tab > Check/uncheck whatever permissions you want that user/group should have.

Is this what you're looking for?

Hi,

Not needed to add any special/extra permission. User might not have proper permission.

Try to give him read permission to all the folders like /apps/, /libs/, /etc/, /var/, /tmp/ etc.

I'm seeing similar issues with my 6.4 implementation.  I created a local AEM test user and put that user into the content author's group.  Then validated that the test user was granted read access via the content author group.

However when logged in as that user the CRX console does not show the folders in which the user has read access to:

There is ONE exception.  If I add permissions to "home" withing user admin, that then shows up under CRX/DE but no other folders with the same permissions do.

The only solution I have found is that in order to access crx/de a user must be in the Administrators group, which is not a good solution for content admin access.

Hi,

Please follow below:

1. create a group say testGroup in aem. 
2. set below permission for 'testGroup' , don't add other group in this group, set permission manually

1. add test user user in this group.

CRXDE view, with above changes

This does work.  Though I'm not sure why since the permissions to the paths are the same as the content author group.

I've also confirmed that with the custom group and the content author group added for the test user, that crx/de access is maintained. 

With further testing of the above I found the solution will be to create a custom group called "crxde-access" or something of the sort and manually grant permissions to it as above.  Then assign that "crxde-access" group to the content authors group.  This allows all content authors access to crx/de folders, as well as editing rights in crx/de in the content directory.

Exactly -- only admin should have access to CRXDE lite. Authors have access to Touch UI views - like Site admin.

While I agree only Admins should have access to CRX DE, in practice, our "power users" find that they can do more when they have access to it (ie. change content / page templates / properties directly).  I created a group that has access to crx/de by setting the permissions to be "Read" on "/" and "conf" (I did not need that group to have read on the etc or home directories but YMMV). 

Additionally, I noticed that if I added a person to the "operators" group, they would have access to crxde, but I can't seem to locate any documentation on what the "operators" group in AEM does (The node permissions seem very restrictive, but I don't know if they had additional permissions on osgi bundles).