how to restrict Navigator visibility for specific screens while allowing contextual usage (e.g. Project Activity binding without Project folder access)?

Hi all,

We want to restrict the IFS Navigator view for certain end-users (e.g., requisitioners) so they don't see unnecessary top-level folders or modules in the left menu tree, such as "Project Management".

However, these users still need to perform specific actions that rely on those modules—for example, attaching a Purchase Requisition line to a Project Activity using the Project Activity LOV/Lookup dialog.

I am aware that removing nodes under "Presentation Objects by Navigator" is one way to hide menu items, but doing so can inadvertently break embedded dialogs or LOVs if parent objects are revoked.

I want to grant granular access under "Database Objects" (APIs/Views/Methods) to allow specific lookups while keeping the Navigator clean. However, finding the exact underlying database package/method for a specific lookup dialog in Permission Sets can be quite challenging.

1. What is the best practice to grant LOV/Lookup permissions (e.g., ACTIVITY_LOV, PROJECT_LOV) under Database Objects without granting full form/Navigator node permissions?

2. What is the easiest way or tool inside IFS (e.g., Debug Console, Page Info) to identify the exact Database Objects/APIs needed for a linked lookup dialog?

Thank you in advance for your help!