Skip to content

Instantly share code, notes, and snippets.

@willtonkin

willtonkin/jcr-paths-permissioning.md

Created November 9, 2017 16:32
Show Gist options
  • Save willtonkin/9e449430acf42d0d151b2762d87f3e9e to your computer and use it in GitHub Desktop.
Save willtonkin/9e449430acf42d0d151b2762d87f3e9e to your computer and use it in GitHub Desktop.
Download ZIP
AEM JCR path notes and permissioning
Raw
jcr-paths-permissioning.md

JCR Root Paths

  • /libs holds predefined system functionality
  • /apps application specific
  • /etc a dumpsterfire
  • /tmp

User Permissioning

Author instance

I'm going off memory here, but I think the below is a good start

All authors have read access to:

  • /libs
  • /master
  • /tmp
  • /apps/[whatever their projects are]
  • /content/[whatever their projects are]
  • /etc [read access, unless there's good reason]

All authors have write access to:

  • /apps/[whatever their projects are]
  • /content/[whatever their projects are]
  • /etc/designs/[whatever their projects are]
  • /etc/tags/[whatever their projects are]

Approver (super) authors are able to write to:

  • /etc/designs/[whatever their projects are]

Developers should have super author access, plus read/write access to:

  • /conf
  • /etc/workflow/instances

Other Useful Paths

Compiled JSPs /var/classes/org/apache/jsp/apps Site Admin panels /libs/wcm/core/content/siteadmin Workflow instances /etc/workflow/instances

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment