Restricting Classic SSP Access in Responsive Self Service Procurement

We've recently enabled Responsive Self Service Procurement in our test environment and are currently reviewing user access. As per Oracle's recommendations, we assigned both the "Requisition Self Service User Duty Role" and "Requisition Self Service Responsive Application User Duty Role."

While the first role grants access for actions within the responsive application, the second provides visibility to the RSSP Workarea. However, this also grants visibility to the Classic Self Service Procurement (SSP) workarea, which shares a common privilege with the "Requisition Self Service User Duty Role."

We intend to provide access to RSSP for specific users only. However, assigning the "Requisition Self Service User Duty Role" (required for actions) also exposes them to the Classic SSP workarea through the same tab. Since users won't be utilizing the classic version, this creates confusion and potential for unintended actions.