When a permission-set structure is too restrictive and something can't be accessed, the client's own log window shows no useful detail — is there an easier way to diagnose exactly which permission is missing, short of digging through the browser's developer tools?

All FAQ questions / Security and access

Answer

As things currently stand, the browser's own developer tools (Network tab, inspecting the failed request/response) are the only reliable way to trace down which specific permission is missing — IFS's own R&D feedback on this is that a built-in 'here's exactly what's missing and how to grant it' diagnostic is deliberately not exposed at a normal permission level, since that level of detail could be misused; it's treated as something closer to a debug/diagnostic-level capability rather than a standard admin one. Keep this in mind when scoping how much time to budget for troubleshooting complex permission-set structures — there's no shortcut beyond the developer-tools approach today, though this is an area IFS has said it may revisit in a future release.

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