Approvals for Frames and Content

This guide explains how you can use approvals for Frames and Content.
​

Approvals for Frames and Content work very similar to approvals for social post sets. You can request approval directly in the object by using the approval button. Approval requests for non-social content are also shown on the approval dashboard, so reviewers can manage them in the same central place.

The main difference is how approval is connected to your workflow.

For social post sets, the approval process can follow a more standardized lifecycle.

For Frames and Content, this is more flexible. You can configure your own content types and status workflows. This means:

Because of this flexibility, the system cannot use one fixed approval process for every Frame or Content type.

Instead, you connect approval to your own workflow by selecting one status as the Approval Entry Status.

The Approval Entry Status is the status where approval becomes required.

You can think of it as a gate in your workflow.

Before this status, you can continue working freely.

At this status, approval is required.

After approval is completed, the system automatically moves the object to this status.

From there, you can continue through the remaining workflow. A later or final status can also be used to trigger further automated processes through the API platform, for example publishing a blog post or an intranet post in an external system.

Your statuses are:

You select this Approval Entry Status:

This means:

Before approval, you can use:

These statuses are blocked until approval is completed:

After approval is completed, the system automatically sets the status to:

From there, you can continue to:

The final status, for example Published, can then be used for further automated processing through the API platform, such as publishing the approved content as a blog post or intranet post.

When you create an Approval Strategy, you choose:

You can create an Approval Strategy for:

If you create one Approval Strategy for multiple content types, all of them must share the selected Approval Entry Status.

The system can only use a status as the approval gate if that status exists everywhere the strategy applies.

Frame Type A has these statuses:

Frame Type B has these statuses:

The common status is:

In this case, you can only select Published as the Approval Entry Status.

You cannot select Publishing, because Frame Type B does not have that status.

If there is no shared status, you cannot create one shared Approval Strategy.

You can:

Once you request approval:

After approval is completed:

A later or final status can also be used by the API platform to trigger automated follow-up processes in external systems.

Examples:

If approval is rejected:

You can use multi-step approvals.

The Approval Entry Status is still defined only once.

The object moves to the Approval Entry Status only after all approval steps are completed.

An Approval Strategy can become invalid if the Approval Entry Status is no longer available.

This can happen when:

In this case, the system informs you and you need to adjust the strategy.