@PranjalSrvst 

Hi Pranjal,

The RIDAC view is part of Strategic Planning Workspace. I would first verify that the Strategic Planning application (sn_apw_advanced) is installed and entitled on the client instance.

Then check the user's roles:

• sn_align_ws.ridac_read_only — read access
• sn_align_ws.ridac_user — create/edit/manage RIDAC

The roles sn_align_core.apw_user, sn_apw_advanced.spw_goal_user, and sn_apw_advanced.eap_user include the appropriate RIDAC access.

If the application and roles are correct but RIDAC is still not visible, compare the Strategic Planning application version between the two instances and then check the Strategic Planning Workspace navigation/configuration.

You can check application/entitlement >> roles >> application version >> workspace configuration in that order rather than looking for a system property.

Note: sn_pw.disable_ridac_monitor is a current property, but it applies to the Project Workspace's legacy “All RIDAC” grid, not to the RIDAC visibility issue in Strategic Planning Workspace.

FYR:

• https://www.servicenow.com/docs/r/it-business-management/scenario-planning-in-spw/install-alignment-...
• https://www.servicenow.com/docs/r/it-business-management/strategic-planning/using-ridac-spw.html

Helpful? Please mark the response as Accepted Solution ✅ and close the thread 🔒 — this helps future readers find the solution faster.

Regards,
Sachinvic
✨ArchX Certified | ✨ 16x ServiceNow AI MVP