Skip to main content
Domo Knowledge Base

Domo Publish

Version 15



Domo Publish allows you to quickly and easily replicate Pages and Cards from the Publisher instance and share them with customers in a dedicated Subscriber instance. Control all the content by filtering to the appropriate data for each Subscriber before it is published. Manage all of your Publish Jobs, content, filters and Subscribers all in one convenient, central location within the Admin Settings.

Here are some terms you should know before using Domo Publish:

  • Publisher - The instance that pushes the data out to the Subscribers. Domo Publish always lives in the Publisher instance.
  • Subscriber - The instance that receives data from the Publisher.
  • Job - Configure the Cards, DataSets, and filters that will be published as well as select which Subscribers should receive the content. You can create multiple Jobs.
  • Data Permissions - Custom filters you can set for each Subscriber to control what rows of data they are allowed to see.
Important: Publish is NOT currently available for instances hosted on Azure.

Getting this feature

If you are interested in using this feature, please contact your Customer Success Manager (CSM).

Note:  This feature is available on demand and paid.


To request this feature be enabled,

  • Reach out to your Domo Customer Success Manager, Technical Consultant, or AE.

  • If you do not have contact information for your CSM, TC, or AE, contact Technical Support by using /Support in Buzz or by email at

Depending on the feature, you may be required to complete training before you can use the feature.

Requesting a Subscriber Instance

This is different than Publish V1. The request should be sent to Sales Ops. They will validate that the customer has a contract for additional instances. The standard naming convention is

Creating a Publication

  1. Navigate to Publish in Admin Settings.

    Admin Settings Publish.png
  2. Choose Publications.
  3. Choose New Publication.

    New Publication.png
  4. Name the Publication.
    This should be a name that will identify the job.
    The description can be used to document the content that is being published and the recipients of the content/data that is being published.
    Click Next.

    Publication Name.png
  5. Add New Subscriber.
    To add a Subscriber, it is necessary to know the URL of the Subscriber domain. The format for this domain is
    Subscribers that have been added to other Jobs will appear in the list as options to select.
    Click Next.

  6. Choose the Page or Pages that you want to Publish.
    Note: The Pages that are chosen must be shared with the user configuring the Job.

    Important: When you add a Parent Page to a Publish Job it automatically adds all of the Subpages of that Page.


    Click Next.

    Select Pages.png
  7. Review DataSets that power the Dashboard.
    The toolkit will automatically select DataSets that are required to power the Cards.
    Additional DataSets can be added if desired.
    Click Next.

    Publish DataSet.png
  8. Set Data Permissions.
    If all rows for a DataSet are to be shared with the Subscriber, then select the Include in publication box. If a filtered version of the data should be shared, select the Add Permission button. This will bring up filtering options to filter the data.
    Important: One policy must be chosen for each DataSet whether that is All Rows or a subset of rows by utilizing filters.

    Click Next.

    Data Permissions.png
  9. Final Review and Save.
    Review the final information before saving to confirm that the number of Pages, Cards, and DataSets are as expected.
    Click Save.
    Note: This will make the Publication available for subscription in Subscriber instances. Subscribers will still need to accept the invitation before any content appears.

    Final Review.png

Subscribing to a Publication

  1. Navigate to Publish in Admin Settings of the Subscriber instance.
  2. Choose My Subscriptions.

    Subscriber Admin.png
  3. Choose Invitations.

    My Subscriptions.png
  4. Review Invitations and click the Subscribe button.

  5. Accept invitation.
    Once accepted, the Publish Toolkit will immediately start to populated the Pages, Cards, and DataSets that are included in the Publication.

    Accept Invitation.png

Refreshing a Publication

  1. Navigate to Publish in Admin Settings of the Publisher instance.
  2. Choose Publications.

    Admin Settings Publish.png
  3. Find the Publication that should be refreshed, hover over the Publication, click the wrench icon on the right-hand side, and select Refresh.
    Note: If you make changes to a Dashboard or a Card in a Dahsboard, you will need to refresh the Publication in order for it to show in the Subscriber instance.


    Important: Do not modify the source Pages while the job is being refreshed. This causes the layout of the Page to change and it corrupts the layout of Cards in the Subscriber instance.

    Delete Pubication.png

Deleting a Publication

  1. Navigate to Publish in Admin Settings of the Publisher instance.
  2. Choose Publications.

    Admin Settings Publish.png
  3. Find the Publication that should be deleted, hover over the Publication, click the wrench icon on the right-hand side, and select Delete.
    Note: This will immediately start the process of removing the Pages, Cards, and DataSets that have been subscribed to from all Subscribers.

    Delete Pubication.png

Unsubscribe from a Publication

  1. Navigate to Publish in Admin Section of Subscriber instance.
  2. Choose My Subscriptions.

    Subscriber Admin.png
  3. Choose Subscriptions.

  4. Find the Subscription to unsubscribe from, hover over the Subscription, click the wrench icon on the right-hand side, and select Delete.
    Note: This will immediately start the process of removing the Pages, Cards, and DataSets that have been subscribed to as part of the Publication.

    Delete Subscription.png

Details on DataSet PDP Policies

If the same DataSet is shared in two Publications to the same Subscriber instance, the PDP policies of the more recently saved Publication will be used for data permissions.

In the event that a Publish user wants to share the same DataSet to the same Subscribers twice with different permissions, they will need to duplicate the DataSet in the Publisher instance.


Are legacy collection Page types supported?

Legacy Card collection Page types are not supported in Publish V2. Please convert any "Standard Page" Dashboards to the newer and more flexible Dashboard layout Page type by clicking the Page options in the top-right of the page and selecting Design Dashboard.

Do Page Filters and Alerts get applied in Subscriber instances as part of Publish?

No, Page Filters and Alerts are not copied by Publish.

Are there any unsupported chart types like in Publish V1?

Yes, this is currently being worked on. These include:

  • Domo Apps, Image Cards, Poll Cards, and Sumo tables.
  • DataScience Cards: XY Line, Scatter, Predictive, Forecasting, Outliers, Vertical & Horizontal Box Plot.
How does the Publish Toolkit handle Beast Modes?

Beast Modes are only copied to the Subscriber instance if it is being used in the Cards.

Are links and Dynamic Summary Numbers in Notebook Cards supported?

No, Links and Dynamic Summary Numbers are not supported in Publish.

Are interactions applied to specific Cards applied in the Subscriber instance?

No, only interactions that are applied to all Cards are copied by Publish.

What information is transferred using Publish?

Only metadata is transferred (Card titles, Dashboard layout.)

Are there any row or refresh limits or data delays to be aware of in Publish?

There are no row or refresh limits and no delay in data updates when using Publish.

Are users in the Subscriber instance able to make changes to Cards/Dashboards Published to them?

Yes, however, any changes they made will be overwritten when the Job is refreshed. If users would like to make changes, they should Save As the Card/Dashboard to another location and make changes there as these will be independent of the Publish Job.


Publish job doesn’t show up on the subscriber side.
  • Cause 1: The instance URL was typed incorrectly or is missing the “”.

  • Cause 2: The publish toolkit hasn’t been enabled in the subscriber instance.

Card shows broken in the subscriber instance.
  • Cause 1: PDP wasn’t enabled properly. Verify the DataSet has PDP enabled.

  • Cause 2: The job was modified and had a new DataSet added and the permission hasn’t been set.

    • The user should click through all steps when editing the Publish job.

  • Cause 3: A new instance was added to the job. Fix is to click through all steps and close.

Instances that are not compatible.

We currently can’t publish between pre-production instances and production instances.

Referencing invalid columns.

Breaks Publications when referenced in Card definitions, Beast Modes, and Drill Paths.

Broken Card definitions.

Cards showing “fix it” usually just need to be resaved. Most of the time, there is no visible indication the Cards have problems.

Subscription creation can take up to 10 minutes.

The layout is applied at the very end.

Requesting assistance

Include the following information:

  • Instance(s) where behavior is occurring
  • Publication Name
  • Description of behavior
  • Screenshot of behavior (if applicable)
  • Steps to recreate behavior (if known/applicable)