After hiding some columns on the Documents/Attachments tab via changes made to the Base Profile for a screen like Shop Floor Workbench, users with a disabled Personal Profile now see an error every time they log in and open that screen — turning Personal Profiles back on for those users avoids the error, but that isn't the desired configuration.

All FAQ questions / Security and access

Answer

Rather than fully disabling Personal Profiles for these users, which is uncommon and can produce exactly this kind of conflict since some screens expect to reconcile a personal profile against the base profile's controlled changes, leave Personal Profiles enabled but instead revoke the specific permissions that let users make profile changes themselves — for example allowing harmless personalization like creating their own Favorites/Shortcuts, while explicitly disallowing things like Navigator changes or Layout changes. This achieves the same practical goal, users can't override base-profile-controlled layout/column changes, without disabling Personal Profiles outright, and avoids the specific error this disabled-personal-profile configuration was producing on that screen.

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