"New" Data Certification - Data Certification experience in CMDB Workspace

[SHIZZYWIZZY]

Team,

Could we review the current process for reassigning CMDB data certification tasks? At present, users must request reassignment manually, which is quite time-consuming and inefficient.

Today, when a task is assigned to the wrong owner, it has to be sent back to the ServiceNow administrator for reassignment, or to a support group that then needs to identify the correct owner before the task can be updated. This creates unnecessary delays and additional administrative effort.

Is there an opportunity to streamline this process, either by allowing users to reassign the task directly to the correct owner or by introducing a role/permission that enables authorized users to update task ownership themselves?

Simplifying this workflow would improve efficiency and reduce the administrative overhead involved in managing CMDB data certification tasks.

Thanks.

[Shahjay]

Hi @SHIZZYWIZZY ,

You’re not stuck with only the “Request reassignment” path. The new Data Certification experience in CMDB Workspace already supports direct reassignment — it mainly comes down to roles and how the policy assigns the task in the first place.

Users with the data_manager_user role can work tasks that are assigned to them, to a group they belong to, or to a group/user they manage. data_manager_admin can see and reassign all certification tasks. From the Data Certification Dashboard (or the Certification tasks list in CMDB Workspace / Service Graph Workspace) those users can open a task and reassign it without sending it back through a central admin queue.

A couple of practical ways to streamline this:

- Give a small set of data stewards or CI owners the data_manager_user role and make sure they are managers of the relevant assignment groups. They can then pick up and reassign tasks themselves from the dashboard, including past-due ones.

- Review the Data Manager certification policy. If it’s pointed at a fixed group or a single admin, wrong-owner volume stays high. Pointing it at a user field on the CI (Owned by, Managed by, etc.) or at a real operational group usually cuts down how often reassignment is needed in the first place.

The “Request reassignment” button is the OOTB action for people who don’t have broader rights. You can leave that for end users and let a data-steward group with the right role complete the actual owner change. That still removes platform admin from the middle of every hand-off.

If you later want any end user to reassign freely with no request step, that would be a small Workspace/UI Builder change rather than a missing platform feature. For most teams, adjusting roles + policy assignment is enough to remove the bottleneck you’re describing.

Hope that helps.