Adobe recommends using the SPA Editor for projects that require single page application framework-based client-side rendering (e.g. React). Learn more.
This chapter describes the user roles and how to configure your users and groups to support the authoring and mangement of your mobile apps.
Members of the app-author group are responsible for authoring AEM mobile application content including, pages, text, images and videos.
Create a new user group called, 'app-authors':
Navigate to the User Admin Console: http://localhost:4502/libs/granite/security/content/groupadmin.html
From within the user group console, select the '+' button to create a the group.
Set the ID of this group to 'app-authors' to denote that it is a specific type of author user group specific to authoring mobile applications within AEM.
Now that you have created the app-authors User Group, you can add individual team members to this new group through the User Admin console.
Members of the app-admins group can author application content with the same permissions included with app-authors AND in addition are also responsible for:
- Staging, publishing and clearing application ContentSync OTA updates
Permissions determine availability of some user actions in the AEM App Command Center.
You'll notice some options are not available for app-authors that are available for app-admins.
On the same Permissions console, add permissions to stage, publish and clear app content updates;
- (Read, Modify, Create, Delete, Replicate) on /etc/packages/mobileapp
- (Read) on /var/contentsync
Package replication is used to publish app updates from author instance to publish instance
/var/contentsync access is denied OOTB.
Omitting the READ permission can result in empty update packages being built and replicated.
To understand more on the other two roles and responsibilities for creating an AEM Mobile On-Demand Services App, see the following resources: