Content Approvals | Yext Hitchhikers Platform

What You’ll Learn

In this section, you will learn:

• What content approvals are
• Overview of the workflow
• Common approvals use cases

What are Content Approvals?

Content Approvals enable users to suggest content changes to certain fields on entities and then have other users review and approve or reject that suggestion. This workflow ensures that more people can add data to Yext at lower risk — nothing will get published publicly until someone approves the content.

When should I use Content Approvals?

Content Approvals are great if you want to empower more users in your account to add data, but at low-risk.

Here are some of the most common use cases for using Content Approvals:

• Professionals - If you have professionals, like doctors, insurance agents, or wealth advisors, it’s great to give them access to the platform so that they can make the content personal to them and their clients.

• Compliance heavy industries - If you’re in a highly regulated industry like healthcare or financial services, you’ll want to make sure that you have content approvals turned on to make sure that your brand is not at risk. Our approvals are fully auditable and you can choose to sync all logs to a WORM (Write Once Read Many) database if needed.

• Local photos - If you want to crowdsource local photos like storefront photos or event photos, you might want to have these go through approval workflows to make sure that the image quality and content is on-brand.

How it all works

When a suggested edit is created, it enters the Suggestions system while it waits for review. Until it is actually approved, the edit is not applied to the entity and it is not published anywhere publicly.

By default, the Suggestions page is filtered to show Suggestions assigned to the user who is viewing the page, or any groups which that user is a member of. Additionally, depending on the user’s permission, the page will also display any unassigned Suggestions.

When a user reviews an edit, they have a few options:

• Approve
• Reject
• Comment
• Modify
• Assign
• Re-assign

For more details on these actions, visit the Suggestions Unit .

How do you determine whether a user can only Edit with Approval vs. Administer Approvals?

For all fields in Yext, you can control whether a user can:

• View only
• Edit with assets only
• Edit with approval
• Edit
• Hide the field entirely from the user

You can use built-in roles like “Content Requester” which will give the user only the ability to Edit with Approval for all fields, or you can make a custom role if you want to vary the behavior by field or hide any fields. When you apply the role to a user, you can also determine the scope of that role – whether it’s for a specific entity, a folder of entities, a type of entity or the entire account. To learn more about users, permissions and custom roles, visit the Users Module .

If a user has the permission to edit a field on an entity, then the user can be assigned the suggestion, and take action on suggestions for that field.