A newly created custom page isn't visible to a user even though that user has full access granted through the relevant permission set — what else typically needs to be checked?

All FAQ questions / Platform, Aurena, and customization

Answer

Permission-set access alone doesn't guarantee visibility — walk through a short checklist: confirm the new page has actually been enabled/made visible in the user's Profile (a page can be fully permitted but still hidden at the profile level); refresh both the Security cache and the Dictionary cache, since a stale cache can artificially block a newly added page from appearing for a period of time; and clear the local cache on the user's own machine as well, since client-side caching can also mask a recent server-side change. If none of that resolves it, swapping the user's profile (or permissions) with another user who can already see the page, one setting at a time, is a practical last resort for isolating exactly what's blocking visibility.

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

← Browse Platform, Aurena, and customization questions