Managing a Profile Approval Request

Your end users can type and submit updates for their social profile fields directly from Yext. When completed in Yext, these review items will be labeled as Profile Approval Requests in the Supervision Queue. This enables compliance admins the ability to approve, deny, or suggest changes to profile update requests before they’re pushed live to the social network for public view.

To learn more about each option, click on the desired section and/or review the video.

Reviewing and Approving a Profile Approval Request

Denying a Profile Approval Request

Suggest Changes to a Profile Approval Request

 

Reviewing and Approving a Profile Approval Request

If no compliance threats are detected in a request, compliance admins can approve the request which will update the user’s social profile or page with their requested update. The end user's profile will then update with their new information. Depending on the social network, the end user may need to manually copy the fields to their profile, once approved.

1. In the Administration view, click Supervision, then open a filter view to select which profile approval request you want to review.

2. While viewing the profile approval request, in the Details tab, review the classification, who triggered the profile alert, and the created/updated dates. 

3. Under the Profile Changes section, fields that the end-user has requested changes for are displayed. You can do the following while viewing and compare the request against the current information on the end user's profile:

  • For changes marked Field was modified, the green text represents text the end user added in that section, and grey-ed out text, marked by the strikethrough, represents text the end user removed.
  • The Redline toggle allows you to turn on and off the tracked changes from the last approved profile.
  • If a change is marked as Field was added, that means the field is a new field the user has not submitted before. 
  • Select Show All Fields to view all of the current profile fields on the end user's social account.

Screenshot 2025-11-10 at 1.48.58 PM.png

Screenshot 2025-11-10 at 1.50.32 PM.png

4. If the requested changes for the profile align with compliance policy, click Acceptable at the  bottom of the page.

 

Denying a Profile Approval Request

If the profile request does not align with compliance policy and therefore must be denied, admins can either deny the entire profile or deny specific fields. Denying the request will prevent the end-user's profile from updating.

Follow these steps to deny the entire profile/all of the updated fields.

1. As a best practice, leave a note for the user or an internal note to the team, if needed.

2. Click Needs Attention > Deny & Notify listed at the bottom of the Profile Approval Request. you are encouraged to leave a comment for the user. 

Suggest Changes to a Profile Approval Request

If the compliance admin reviews the request, sees that additional information is needed, and knows the specific text or imagery that the end-user needs to include, such as a cover photo, disclosure, or correct contact information, compliance admins can suggest changes back to the end-user. The end-user will receive the suggestions, and if they accept them, their profile will update with the suggested text. Follow the steps below to suggest changes. 

1. In the Profile Changes section, click Add Suggestion next to the field you want to suggest changes for.

2. Write your suggestion and, optionally, include a note to the user. 

Screenshot 2025-11-10 at 1.37.10 PM.png

3. When you are done making suggestions, click Needs Attention > Suggest Changes at the bottom of the page. 

Screenshot 2025-11-10 at 1.40.24 PM.png

4. Review your suggestions, add another optional note to the user, and click Send Suggestion

Screenshot 2025-11-10 at 1.40.29 PM.png

The user receives your suggested changes in an email, where they can accept the suggestions to continue publishing their post.

 

Was this article helpful?
0 out of 1 found this helpful

We're sorry to hear that.

Articles in this section