B2B Access - Permission Set

Hi ​@HEMA G A,

Yes, it is possible to restrict a user effectively to B2B only access in IFS Cloud, but this cannot be achieved through a single configuration that outright blocks access to the Aurena client; instead, it must be enforced through careful design of permission sets and role assignments. In IFS Cloud, access is governed using a role-based access control model where users are granted permission sets that determine which frameworks and functionalities they can use. Specifically, Aurena client access is enabled through core platform roles such as:

1. FND_WEBRUNTIME (required for login)
2. FND_WEBUSER_MAIN (which provides standard Aurena functionality)
3. FND_WEBUSER_B2B (which is intended for limited, external-facing access scenarios)

Therefore, to enforce B2B only access, the recommended approach is to assign only B2B related permission sets (including FND_WEBUSER_B2B and relevant functional roles tied to B2B processes) and avoid assigning general Aurena roles like FND_WEBUSER_MAIN or broader business roles.

In such a setup, even though the user technically authenticates through the same web framework, their access to Aurena navigation and pages is effectively restricted because no corresponding privileges or navigator entries are granted. This aligns with the intended use of B2B users as limited task users, where access is deliberately constrained to a predefined functional scope rather than full system interaction.

However, it is important to note that IFS Cloud does not provide a native “disable Aurena UI” flag per user, so the restriction is implemented indirectly by limiting what the user is authorized to see and execute, rather than preventing login entirely.