About the Tables Permissions List

The Tables permissions list displays details on the specific object permissions directly granted to users or roles for a single view.

There are several table object permissions, which can be granted with or with out administrative rights. Some permissions can be granted at table level only, while others can be granted at either the table or column level.
You can grant object permissions in several ways:

Users or roles with object ownership or the MANAGE ANY OBJECT PRIVILEGE system privilege are automatically granted all possible object permissions with administrative rights.

You can grant object permissions with or without administrative rights. The grantee can perform authorized tasks requiring the permission, but cannot in turn grant the permission to another user or role when granted without administrative rights. The grantee can do both when granted with administrative rights (With grant option).

The permissions list only lists those permissions granted directly to user or roles. The list indicates which columns the permissions are granted to, to whom (grantee), by who (grantor), and the permissions and their corresponding administrative rights. The permissions list does not list object permissions obtained through ownership, the MANAGE ANY SYSTEM OBJECT system privilege, or role membership.

The permissions list only lists those permissions granted directly to user or roles. The list indicates which columns the permissions are granted to, to whom (grantee), by who (grantor), and the permissions and their corresponding administrative rights. The permissions list does not list object permissions obtained through ownership, the MANAGE ANY SYSTEM OBJECT system privilege, or role membership.

Permissions granted to all columns on the table are listed first. The remainder of the list is sorted alphabetically, by column name.

All members of the role inherit permissions granted to a role, including administrative rights. The role, not the users indirectly granted the permissions through inheritance, appears on the permissions list.

The REVOKE command applies to the database object permission itself, not to any administrative right granted on the permission. Therefore, to remove the administrative right only and leave the database object permission intact, do not use the Revoke button. Rather, regrant the specific permission without administrative rights. Only the original grantor can remove the administrative rights only from a granted permission. If another grantor regrants the same permission without administrative rights, a new permission without administrative rights is granted, but the original permission with administrative rights remains and takes precedence over any other non-administrative grants of the same permission to the same user or role.

If multiple permissions are granted, you can revoke some or all of the permissions. However, if you revoke a permission granted administrative rights, and the grantee has granted the permission to other users, who in turn have granted it to other users, and so on, every grantee in the chain who has received the permission indirectly, with or without administrative rights, also has their permission revoked. For example, UserA is granted the SELECT permission with the With grant option. UserA grants SELECT to UserB with the With grant option. UserB grants SELECT to UserC and UserD without administrative rights and to UserE with administrative rights. When you revoke the SELECT permission from UserA, it is also revoked for UserB, UserC, UserD and UserE.

Permissions can be granted on the same column, to the same grantee, by multiple grantors, resulting in the same grantee appearing multiple times on the list. If the same permission is granted to the same grantee, with and without administrative rights, the grant with the administrative right takes precedence.

For example, Jane is granted permissions by both Bob and Alex. Bob grants Jane permissions on all columns, while Alex only grants permissions on column C. Jane has INSERT, UPDATE, and REFERENCE permissions without administrative rights on all columns in the table (granted by Bob). However, she also has REFERENCE permission on column C only (granted by Alex). When the same permission is granted with different administrative rights the higher administrative right takes precedence, at the specific level. Therefore, the REFERENCE permission with administrative rights only applies to column C on the table.

When you revoke a permission granted multiple times, the permission is revoked from all instances, regardless of administrative rights. For example, Manager1 grants User2 INSERT with administrative rights. User1 also grants INSERT to User2, without administrative rights. Both instances of INSERT are revoked for User2, regardless of which instance of INSERT is revoked.

Related concepts
Following the Table Permissions Grant Trail
Manage Permissions on a Proxy Table
Related tasks
Granting Permissions on a Table
Revoking Permissions on a Table
Removing Administrative Rights Only from a Table Permission
Adding Administrative Rights to a Granted Table Permission
Related reference
Table Permissions Privilege Summary