Reminder - Digital Publishing Suite (DPS) will End of Life on August 31st, 2019. 
Prerequisite knowledge
  • Basic familiarity with the Adobe Digital Publishing Suite product.
User level: Intermediate
Required Adobe products (retail)


This article will help corporate marketing, creative and IT managers as they plan their team’s roles and responsibilities for an enterprise DPS publishing workflow.

Accounts and Account Administration

Before you begin creating apps with DPS you will need to provision “delegate” accounts under your enterprise license, which involves assigning email-based Account IDs to roles in the administration tool. You will need assistance from IT to supply generic email address that can be used for the Master and Application accounts. The types of account roles available in the administration tool are summarized below:
Master Used to consolidate all accounts under one DPS license. This account is generally used only to facilitate the creation of the sub-accounts (listed below). This account should be created with a generic email address.
Administrator Used to setup and manage Application and App Builder accounts.
Application An Application account is created for each app. This account is used to manage folios, publish folios and will have access to the analytics reports for the app. This account should be created with a generic email address.
App Builder An App Builder account is used to access the App Builder tool to create the custom native app.
Some of your designers or third-parties creating content might not require a delegate account under your enterprise license.
Any Adobe ID can be used to create and preview folios in the Folio Producer. Often, individual designers or agency partners will work with you using their personal Adobe IDs. Personal accounts do not require provisioning under the master account.
The image below shows an example of the online Account Administration tool where accounts are managed. Note that multiple account roles can be associated to the same user (Account ID).
The DPS Account Administration page. The columns to the right show the DPS account roles assigned for the user.
Figure 1: The DPS Account Administration page. The columns to the right show the DPS account roles assigned for the user.
Please see the Account Administration tool page on the Digital Publishing Suite Help site for more information on account management.

Typical Roles & Tools

Every organization and workflow is different, but you will likely need to designate people to fill the following roles.
Employee Role DPS Role Account Tools Required
Administrator from Marketing Management or IT Administrator and/or Master
  • Access to the online DPS Dashboard (
Graphic Designers Personal
  • InDesign (CS6 or later is preferred)
  • iPad and/or other devices for testing with Adobe Content Viewer (free download from the app store)
  • Adobe ID (free) and access to
HTML Developer N/A
  • HTML5 web development tools
Reviewer Personal
  • iPad and/or other devices for testing with Adobe Content Viewer
  • Adobe ID (free)
Publisher from Marketing Management or Business Application
  • Access to the online DPS Dashboard (

App Builder

  • Access to the online DPS Dashboard (
  • Install App Builder tool
  • Digital Signing Certificate

Workflow Overview

A typical DPS workflow can be separated into the following processes:
  • Content creation: the on-going process of creating, updating and reviewing folios.
  • Publishing new folios or updates.
  • Building new apps or updating apps and then distributing them to an app store or internally via a Mobile Device Management system or intranet.
  • Reviewing analytics and fulfillments.
The following are summaries of the roles and responsibilities for each of these processes:
DPS creator and reviewer roles
Figure 2: DPS creator and reviewer roles
  1. Designers from the creative team create folio articles in InDesign and preview locally on their device.
  2. (Optional) The creative team may require some developer help with creating or re-purposing HTML widgets or complex HTML animations. The developers package HTML content and share it with the creative team.
  3. Designers upload the folio to a shared account or to a personal account using a free Adobe ID.
  4. Designers share the folios with specific Reviewer’s Adobe ID email addresses.
  5. Reviewers log in to the Adobe Content Viewer on their device to review the folios.


DPS publishing roles
Figure 3: DPS publishing roles
  1. Designer shares the folio to the Application account or uploads the source files directly to the Application account.
  2. Publisher reviews the content (if necessary), makes any meta-data adjustments and publishes the folio to the distribution service.


DPS app building roles
Figure 4: DPS app building roles
  1. Designer supplies custom branded icons and splash screens for the app.
  2. (Optional) Developers can create a custom UI for the app using HTML5. Developers may work with UX designers and/or information architects for this task.
  3. An App Builder from IT collects all of the assets and any other configuration options for the app from the marketing, creative and business teams.
  4. The App Builder uses the App Builder tool to configure the app properties and sign the app with the company certificate. Once the app is created, the app an be submitted to an app store or distributed via MDM or an intranet.  A developer app can be created as well, for testing before the final app is released.
Reviewing Analytics
A manager or business owner uses the Application account to access the app reports from the DPS Dashboard and/or the fulfillment reports.
Apps can also feed analytics data to an Adobe Analytics (formerly SiteCatalyst) instance for advanced analytics. You will need an Adobe Analytics account to access advanced analytics reports. More information about analytics is detailed on the DPS analytics page on the Digital Publishing Suite Help site.

Where to go from here

The roles and workflows outlined above are typical for DPS apps without entitlement. Adding entitlement (i.e., a login) to your app will require additional help from IT or a third-party partner to setup the back-end integration to a user management system.
Comments are currently closed as we migrate to a new commenting system. In the interim, please provide any feedback using our feedback form. Thank you for your patience.