A wide variety of approval strategies can be created for the post creation in the Publisher. These regulate who must obtain approval requests, who may approve or reject them and for which networks or profiles approvals are to be obtained. A distinction is made between single-stage processes based on the two-man rule and multi-stage, i.e. advanced, approval strategies.

Approvals are obtained in the last step of the post creation process. Current approval processes can be viewed in the approval overview.

Two-man rule

Advanced Approval Process

Permissions


Two-man rule

An approval strategy according to the two-man rule enables the coordination of content between two people. You can create such a strategy in the admin settings in the Publisher area under the item Approval Strategies. Click on + Approval Strategy and select Two-man rule.

πŸ‘‰ Title, networks and profiles

The first step is to make general settings. First, give the new approval strategy a meaningful title. It may be seen by the persons making the request.

Then select whether the approval strategy should only apply to specific networks. This applies to all profiles of the selected networks. If you do not make a selection here, the approval strategy applies to all networks.

The same applies to the profiles. If you do not make a selection here, the approval strategy applies to all profiles. However, if you select certain profiles, the strategy is only applied to them.

You can also combine the network and profile selection. For example, if you want the approval strategy to apply to all Facebook profiles and two specific Instagram profiles, select Facebook in the Networks section. In addition, you select the two Instagram profiles in the Profiles section.

Click on Save & Continue to be taken to an overview. Here you can check or edit your network and profile settings under the item Networks & Profiles.

πŸ‘‰ Set users

Who needs approval?

In the next step, you determine who should be able to request approval. Again, this applies to everyone by default unless you specify the settings. By clicking on the +, you can select entire teams and/or individual users for whom the approval strategy should apply.

Who can approve?

You also need to define who should be able to approve requests. Make sure that these users have the appropriate permissions. Choose between the following options:

  • Team members: Any team member of the requesting user can give or reject an approval. Remember that this applies to all teams in which the user making the request is a member.

  • Team members on all levels above: All members in teams that are superior to the team of the requesting users in the team structure can accept or reject approvals.

  • Dedicated approvers: Click on the + to select specific teams or individual users who are to be permitted to accept or reject approvals. Here you work with and and or operators. Teams or users that you select together in one step are seen with an or link. Select teams or users individually to add them with an and link.

    An or link means that only one team member or one specific user within the link must accept the approval. If linked with and, several users or teams must accept the approval.

πŸ‘‰ Advanced Options

Set Deadline

You can optionally set a deadline by which an approval request must be processed. This deadline is specified in days, hours and minutes and refers to the period before the planned publication. If the approval deadline has passed, the approval is automatically rejected by default. If you want the post to be approved automatically when the deadline expires, tick the box Auto approve steps on deadline expiration.

Use Dedicated Approvers

If you tick this option, the requesting user can choose which user should process their request. Then, in the post creation, they can select from a drop-down menu the users you have specified in the item Who can approve?.

Make Approval Optional

Specify whether approval must be obtained in this approval strategy or whether it should serve as an optional feedback loop.

Click on Save to directly activate the approval strategy. In the overview in the Publisher settings under the item Approval Strategies, you can deactivate it again with one click or delete or duplicate it via the three-point menu.

Advanced Approval Process

An Advanced Approval Process has several approval steps that follow one another. It can be designed very flexibly to reflect almost any approval scenario. Each strategy can be adapted so that no one, not even a Company Admin, can skip it. These mandatory approval strategies serve the security of critical posts or social media profiles.

You can create such a strategy in the Admin Settings in the Publisher section under Approval Strategies. Click on + Approval Strategy and select Advanced Approval Process.

πŸ‘‰ Title, networks and profiles

The first step is to make general settings. First, give the new approval strategy a meaningful title. It may be seen by the persons making the request.

Then select whether the approval strategy should only apply to certain networks. This applies to all profiles of the selected networks. If you do not make a selection here, the approval strategy applies to all networks.

The same applies to the profiles. If you do not make a selection here, the approval strategy applies to all profiles. However, if you select certain profiles, the strategy is only applied to them.

You can also combine the network and profile selection. For example, if you want the approval strategy to apply to all Facebook profiles and two specific Instagram profiles, select Facebook in the Networks section. In addition, you select the two Instagram profiles in the Profiles section.

Click on Save & Continue to be taken to an overview. Here you can check or edit your network and profile settings under the item Networks & Profiles.

πŸ‘‰ General settings

The settings made in the next step and the selection of networks and profiles apply to all release steps in the multi-stage process.

Who needs approval?

In the next step, you specify who should be able to request approval. Again, this applies to everyone by default unless you specify the settings. Click on the + to select entire teams and/or individual users for whom the approval strategy should apply.

Advanced Options

  • Disable Force Approval: Set a checkmark here if there should be no possibility to force approval. You thus deactivate this special authorisation for this approval strategy.

  • Make Approval Optional: Specify whether approval must be obtained in this approval strategy or whether it should serve as an optional feedback loop.

  • Auto approve steps on deadline expiration: If you have specified a deadline for individual or several approval steps, you can decide what should happen after the deadline has expired. By default, the post is automatically rejected. If you tick this box, the approval will be automatically approved instead.

πŸ‘‰ Add Approval Steps

Start with the first approval step and indicate whose turn it is to accept approval for the post in this step. Make sure that the users have the appropriate permissions. Choose between the following options:

  • Team members: Any team member of the requesting user can give or reject an approval. Remember that this applies to all teams in which the user making the request is a member.

  • Team members on all levels above: All members in teams that are superior to the team of the requesting users in the team structure can accept or reject approvals.

  • Dedicated approvers: Click on the + to select specific teams or individual users who are to be permitted to accept or reject approvals. Here you work with and and or operators. Teams or users that you select together in one step are seen with an or link. Select teams or users individually to add them with an and link.

    An or link means that only one team member or one specific user within the link must accept the approval. If linked with and, several users or teams must accept the approval.

You can also optionally set a deadline by which an approval request must be processed. This deadline is specified in days, hours and minutes and refers to the period before the planned publication. You can decide how to proceed after the deadline in the general settings under Advanced options.

Now add as many approval steps as you like via Add Approval Step. The steps are carried out in the order in which they were created. First, a person specified in step 1 must accept approval, then a person from step 2, and so on.

Click on Save to directly activate the approval strategy. In the overview in the Publisher settings under the item Approval Strategies, you can deactivate it again with one click or delete or duplicate it via the three-point menu.

Permissions

For the approval processes to work, you may have to assign certain permissions to the users involved. You can choose between five permissions, which you can adjust in the Permission sets section and then assign to the corresponding users.

πŸ’‘Users with the permission set Default User with Full Access already have all the permissions presented here by default.

  • Accept Approval Requests: Allows approval requests to be accepted. If a user is to approve a post as part of an approval process, they need this permission.

  • Read Approval Requests: Allows you to see the approval overview with all approval requests and comments as well as to revoke your approval requests.

  • Force Accept Approval Requests: Allows to accept approval requests even if the user has not been directly requested. This permission can be used to force approval for a post even if the post has not yet been approved by the users who initially requested it. In the case of advanced approval processes, it is possible to deactivate this right for individual strategies.

    πŸ’‘ Users with this permission can publish posts immediately, even though the post is still in a release process.

  • Reject Approval Requests: Allows approval requests to be rejected. If a user is to reject a post as part of an approval process, they need this permission.

  • Force Reject Approval Requests: Allows approval requests to be rejected, even if the person was not directly requested. With this permission, it is possible to intervene in the approval process at any time and force a rejection for a post, even if the post has not yet been rejected by the users originally requested.

Did this answer your question?