Many publishers use Adobe Digital Publishing Suite (DPS) with a personal email address as their Adobe ID. This ID is the Adobe ID used to publish folios for an application. It's also used as the Title ID in Viewer Builder and to log in to the DPS dashboard to view the application's analytics. After the fact, publishers sometimes want to change the email address used for this function, without interrupting any functionality of their applications or publishing processes.
First, define a non-user-specific email address that can be set to forward to one or more people in your company. Also make sure that your IT department can change the address as necessary. Adobe recommends a convention of <magazine_title>@<publisher_domain>.
Next, ensure that the email address you want to use is not already associated with an Adobe ID. If it is, you can use the instructions below to change it to another valid email address. This step frees up the email address so that you can use it on your application Adobe ID. Note: You cannot change the Adobe ID to an email address that is already associated with another Adobe ID.
- Go to the Adobe website.
- Click Sign-in.
- Sign in with the existing email address and password.
- In the upper-right corner, click the user name and choose My Information.
- Change the email address (and password if you like) and click
Save my changes.
Now anyone logging in to the Folio Builder panel, Adobe Content Viewer, or DPS dashboard must use the new email address (and password, if changed). Also, if the application is later updated in the Viewer Builder, it's necessary to use the new email as the Title ID.
DPS applications and published folios do not have an email address associated with them. Instead, there is an underlying Account ID defined as a GUID (global unique identifier). This value doesn't change when you edit an Adobe ID. Therefore, existing folios continue to be delivered to the applications they are currently associated with after changing the email address. Using the new email address in subsequent work ensures that the folios and applications continue to use the same underlying GUID.