Some permissions take precedence over others. In cases where two or more permissions disagree, Sybase Data Federation interprets the settings according to specific rules.
Permissions are interpreted as follows:
The owner of an object or a member of the Administrators group can do anything with the object. Deny permissions for the owner of an object or an administrator have no effect.
Permissions for the “everyone” group take precedence over all other permissions. For example, if “everyone” is allowed to read an object, denying read permission for an individual user has no effect. Conversely, if “everyone” is denied permission to read an object, allowing a user or group has no effect.
Deny takes precedence over Allow and Unset. (This allows you to use groups effectively by granting a permission to a group, but denying the same permission to a few members of the group.)
User permissions take precedence over group permissions.
Permissions for groups other than everyone are effective only when not trumped by any of the preceding rules.
Send your feedback on this help topic to Sybase Technical Publications: pubs@sybase.com
Your comments will be sent to the technical publications staff at Sybase, Inc. For product-related issues or technical support, contact Sybase Technical Support at 1-800-8SYBASE.