How do you actually grant a non-FNDADMIN user genuine, working access to the Aurena Page Designer / Navigator Designer — the specific projection names for these designers don't show up anywhere obvious via the debug console or log window when trying to figure out what to grant.

All FAQ questions / Security and access

Answer

The two headline projections that gate whether the client designers are enabled at all, CustomPagesHandling and CustomNavigatorHandling, are by default only granted to the locked FNDADMIN core permission set — but granting just those two alone isn't enough to make the designers genuinely usable for a non-FNDADMIN user. A working custom-permission-set grant for Page Designer / Navigator Designer access also needs a broader set of supporting projection grants alongside those two, including things like ConfigurationHandling, ConfigurationContextAdmin, ProjectionConfigHandling, AurenaPageDesigner itself, NavigatorConfigurationAdmin, EntityConfigHandling, and EnumConfigHandling, plus the Custom-Event- and Event-Action-related projections if custom events will also be configured from the same designer context, along with the DEFINE SQL system privilege. Granting only the two headline 'enable the designer' projections without this fuller supporting set typically leaves the designer appearing enabled but not actually functional for that user.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Security and access questions