The user would like the general functionality to mark content (even one's own) as Authoritative to be given to users in a custom role, without requiring the broader "Authoritative Update Content" privilege.
Where did this request originate?
We have a custom role called "GRX Manager" within our organization. This role is responsible for a majority of the content curation and management. This role can also curate groups to share content, but currently, this role has too much privilege as they have the administrative privilege to update content in the portal, which allows them to perform undesirable actions, like edit other user's site pages. If the "Update Content" privilege is removed, this role no longer can mark content as "Authoritative" or "Deprecated". Note: for our case in particular, the site page being affected would be our home page which could potentially affect over 9200 users if the site was compromised.
Why do we want this enhancement?
This special role will all the group of users to focus on content availability and curation to perform their duties without having unnecessary additional privileges to accidently modify another user's site page.
*See attachment for submitted enhancement request.
