Release security changes

Prior to release, the security relationships are expanded, and the appropriate access is applied. The release process then verifies that at least one member is included in the profile for each secured dimension. The expanded list includes only those members with read only or read/write access.

If you use the No Access option to exclude members, you must ensure that you do not inadvertently create a situation where you do not have at least one member defined in each secured dimension. The No Access option excludes members, essentially removing them from the profile.

The release security process verifies only the profiles that are assigned to a user.