Publishing Apty Content

After creating your content, the important step is to publish it, so that your users can access it  on your application.

Any content created using Apty Studio or the Admin Portal can be in one of the following states:

Publishing State Description



Content that has been finalized and made accessible to users within the hosting application through the Apty Client.
Not published


Content that has been created but not yet made accessible to users. This content remains in draft mode until it is published.
published 2


The blue dot indicates one of the following alerts:

 1.  Content that is not synchronized with the latest changes in the main environment. This typically happens when updates have been made but not yet published, causing a discrepancy between the version available to users and the most recent modifications.

2. The Revert option in the Apty publish menu allows users to restore content to its previous version. When changes are made and saved, users have the flexibility to revert back to an earlier iteration if needed. This can be particularly useful in situations where updates may not meet expectations or if errors are introduced unintentionally. By selecting the Revert option, users can ensure that only the desired content is published and made available to users of the hosting application through the Apty Client.

You can publish Apty content in three ways:

With Content Review and Approval feature enabled

Content development can sometimes be challenging and contain opportunities for enhancement. As a solution, you can enable the Content Review and Approval feature which helps you to request the content for review and approval before publishing them in your environments.

This way you can ensure a risk-free content creation process and publish the content to your environment only if it has been approved. This will establish a secure environment for content development, reduce errors, allow Approvers to evaluate the content's quality, and accelerate process completion.


Content Review and Approval is a feature flag. Reach out to your Apty representative to enable this feature for your application.

The process of Content Review and Approval typically consists of two stages:

Stage 1: Create Content and Request for Approval

Stage 2: Review Content and Approve for Publish


With Content Review and Approval feature disabled

You can publish your content through the Apty Studio or the Admin Portal without enabling the Content Review and Approval feature for your application. In this case, Admins and any user with the Publisher role can publish the content.

Publish Apty Content using Apty Studio

  1. When you log in to the Studio, choose the application you want to work on.
    select application-1
  2. Next, navigate to the Workflows section.
    select workflows
  3. Find the workflow you wish to publish, then click on the vertical ellipses located on the right side of the workflow name.
    select publish
  4. Select the "Publish" option from the dropdown menu.
  5. You will then be directed to the Publish screen.
  6. Proceed to publish the workflow in the desired environments.
    publish latest


It is important to publish a workflow in lower environments before moving it to the production environment.

Publish Apty Content using Admin Portal

  1. When accessing the Admin Portal, select the specific application you wish to work with.

    select application and publish
  2. Navigate to the Publish tab, where you can search for the workflow you intend to publish using the Search bar, or use the filter option.
    publish tab
  3. Once you locate the workflow in question, click on the vertical ellipses along the row of its details.
    publish wf admin
  4. Finally, select the option to publish the latest version on the desired environments.


Bulk publish Apty Content using bundles

You can efficiently store and bulk publish Apty Content together, saving you time and effort every Release period. To learn more, see Create Content Release Bundles.

Video Tutorial - Publishing content: