Onboard to AEM Forms as a Cloud Service

Decide personas

Before onboarding to an AEM Forms as a Cloud Service environment, decide personas and structure a team for your project. A typical AEM Forms project team has the following personas:
  • User Experience (UX) designer: A User Experience (UX) designer defines style, layout, and branding for AEM Forms assets.

  • Forms practitioner: A Forms practitioner creates Adaptive Forms, themes, and templates as per the style, layout, and branding provided by the UX designer. The practitioner also creates and integrates Adaptive Form with a Form Data Model and AEM Workflows. A Forms Practitioner typically undertakes front-end related tasks.

  • Forms developer: A Forms developer develops a custom forms solution. A Forms developer typically undertakes backend development like developing custom components, AEM Workflows, pre-fill service and more.

  • AEM administrator: An AEM administrator helps with overall configuration like setting up users, hardening the environment, configuring data sources, configuring email, and third party software. AEM administrator also helps with integrations like integrating with Adobe Analytics, Adobe Target, and Adobe Sign.

  • End user: An end user interacts with and submits the published form, signs submitted forms, tracks submitted applications through web portal, and receives personalized communications.

Onboard to the service

  • Onboard to the Adobe Experience Manager as a Cloud Service.

  • (For Sandboxes only) After onboarding the service, create and run both production and non-production pipelines. It enables and brings latest features of AEM Forms as a Cloud Service to your environment.

Configure users

After you complete onboarding to the service, login to your AEM Forms as a Cloud Service environment, open Author and Publish instances, and add users to Forms-specific AEM groups, based on their persona. The following table lists Forms-specific AEM groups, available out of the box, and corresponding user types. The table also provides AEM instance type for each user type:

User types (Personas) User groups AEM instance
Form practitioner /Forms developer
  • forms-users
  • template-author
  • workflow-users
  • workflow-editors
  • fdm-authors
Author instance
User Experience(UX) designer
  • forms-users
  • template-author
Author instance
AEM administrator
  • aem-administrators,
  • fd-administrators
Author and Publish instance
End user
  • When a user must log in to view and submit an Adaptive Form, add such users to forms-users group.
  • When no user authentication is required to access Adaptive Forms, do not assign any group to such users.
Author and Publish instance

For more information about Forms-specific AEM groups and corresponding permissions, see Groups and permissions.

Next step

Set up a local development environment. You can use local development environment to create an Adaptive Form and related assets (Themes, Templates, custom Submit Actions, pre-fill service and more) and convert PDF forms to Adaptive Forms without logging in to cloud development environment.

On this page