| Role | Group | Reponsibliities | HTML, CSS | JavaScript | Enterprise Components | Custom Components | HTL | JSP | Workflow | Backend Server-Side Java |
|---|
| AEM Administrator | Technology Operations | Monitoring of operations. Arms-Length deployment. Automation |  | | | | | | | |
|
|
|
|
|
|
|
|
|
|
|
| AEM Developer | Enterprise | Development Standards and Stewardship |  | 
Devs should only change content, but we know this will be abused. So this is viably only if using publishing workflow. The approvals also should meet SOX (ie be under different stream management) | | | |
Devs should only change content, but we know this will be abused. So this is viably only if using publishing workflow. The approvals also should meet SOX (ie be under different stream management)
| | |
|
|
|
|
|
|
|
|
|
|
|
| Author Head | Digital Marketing | The largest region. Represent interests and sets standards for authors. | | | | | | | | |
|
|
|
|
|
|
|
|
|
|
|
| Regional Administrator | Region | User Management, Compliance | | | |
| | | | |
| Regional AEM Developer | Region |
| | | | | | | |
|
| Author | Region | Day to day update of the website using | | | | | | | | |
| Contributor | Region | Access to very limited frequently updated content. |
|
| | | | | |
|
| Subscriber | Business Line to Region | Mainly used for being part of the approval workflow and very very limited area of content to update for the Region. |
|
| | | | | |
|
|
|
|
|
|
|
|
|
|
|
|