Amazon Redshift will no longer support the creation of new Python UDFs starting Patch 198. Existing Python UDFs will continue to function until June 30, 2026. For more information, see the [ blog post ](https://aws.amazon.com/blogs/big-data/amazon-redshift-python-user-defined-functions-will-reach-end-of-support-after-june-30-2026/).
# Examples
The following example revokes INSERT privileges on the SALES table from the GUESTS user group. This command prevents members of GUESTS from being able to load data into the SALES table by using the INSERT command.
```
revoke insert on table sales from group guests;
```
The following example revokes the SELECT privilege on all tables in the QA\$1TICKIT schema from the user `fred`.
```
revoke select on all tables in schema qa_tickit from fred;
```
The following example revokes the privilege to select from a view for user `bobr`.
```
revoke select on table eventview from bobr;
```
The following example revokes the privilege to create temporary tables in the TICKIT database from all users.
```
revoke temporary on database tickit from public;
```
The following example revokes SELECT privilege on the `cust_name` and `cust_phone` columns of the `cust_profile` table from the user `user1`.
```
revoke select(cust_name, cust_phone) on cust_profile from user1;
```
The following example revokes SELECT privilege on the `cust_name` and `cust_phone` columns and UPDATE privilege on the `cust_contact_preference` column of the `cust_profile` table from the `sales_group` group.
```
revoke select(cust_name, cust_phone), update(cust_contact_preference) on cust_profile from group sales_group;
```
The following example shows the usage of the ALL keyword to revoke both SELECT and UPDATE privileges on three columns of the table `cust_profile` from the `sales_admin` group.
```
revoke ALL(cust_name, cust_phone,cust_contact_preference) on cust_profile from group sales_admin;
```
The following example revokes the SELECT privilege on the `cust_name` column of the `cust_profile_vw` view from the `user2` user.
```
revoke select(cust_name) on cust_profile_vw from user2;
```
## Examples of revoking the USAGE permission from databases created from datashares
The following example revokes access to the `salesshare` datashare from the from the `13b8833d-17c6-4f16-8fe4-1a018f5ed00d` namespace.
```
REVOKE USAGE ON DATASHARE salesshare FROM NAMESPACE '13b8833d-17c6-4f16-8fe4-1a018f5ed00d';
```
The following example revokes the USAGE permission on the `sales_db` from `Bob`.
```
REVOKE USAGE ON DATABASE sales_db FROM Bob;
```
The following example REVOKE USAGE permission on the `sales_schema` from the `Analyst_role`.
```
REVOKE USAGE ON SCHEMA sales_schema FROM ROLE Analyst_role;
```
## Examples of revoking scoped permissions
The following example revokes usage for all current and future schemas in the `Sales_db` database from the `Sales` role.
```
REVOKE USAGE FOR SCHEMAS IN DATABASE Sales_db FROM ROLE Sales;
```
The following example revokes the ability to grant the SELECT permission for all current and future tables in the `Sales_db` database from the user `alice`. `alice` retains access to all tables in `Sales_db`.
```
REVOKE GRANT OPTION SELECT FOR TABLES IN DATABASE Sales_db FROM alice;
```
The following example revokes the EXECUTE permission for functions in the `Sales_schema` schema from the user `bob`.
```
REVOKE EXECUTE FOR FUNCTIONS IN SCHEMA Sales_schema FROM bob;
```
The following example revokes all permissions for all tables in the `ShareDb` database’s `ShareSchema` schema from the `Sales` role. When specifying the schema, you can also specify the schema’s database using the two-part format `database.schema`.
```
REVOKE ALL FOR TABLES IN SCHEMA ShareDb.ShareSchema FROM ROLE Sales;
```
The following example is the same as the preceding one. You can specify the schema’s database using the `DATABASE` keyword instead of using a two-part format.
```
REVOKE ALL FOR TABLES IN SCHEMA ShareSchema DATABASE ShareDb FROM ROLE Sales;
```
## Examples of revoking the ASSUMEROLE privilege
The following are examples of revoking the ASSUMEROLE privilege.
A superuser must enable the use of the ASSUMEROLE privilege for users and groups by running the following statement once on the cluster:
```
revoke assumerole on all from public for all;
```
The following statement revokes the ASSUMEROLE privilege from user reg\$1user1 on all roles for all operations.
```
revoke assumerole on all from reg_user1 for all;
```
## Examples of revoking the ROLE privilege
The following example revokes the sample\$1role1 from to sample\$1role2.
```
CREATE ROLE sample_role2;
GRANT ROLE sample_role1 TO ROLE sample_role2;
REVOKE ROLE sample_role1 FROM ROLE sample_role2;
```
The following example revokes system privileges from user1.
```
GRANT ROLE sys:DBA TO user1;
REVOKE ROLE sys:DBA FROM user1;
```
The following example revokes sample\$1role1 and sample\$1role2 from user1.
```
CREATE ROLE sample_role1;
CREATE ROLE sample_role2;
GRANT ROLE sample_role1, ROLE sample_role2 TO user1;
REVOKE ROLE sample_role1, ROLE sample_role2 FROM user1;
```
The following example revokes sample\$1role2 with the ADMIN OPTION from user1.
```
GRANT ROLE sample_role2 TO user1 WITH ADMIN OPTION;
REVOKE ADMIN OPTION FOR ROLE sample_role2 FROM user1;
REVOKE ROLE sample_role2 FROM user1;
```
The following example revokes sample\$1role1 and sample\$1role2 from sample\$1role5.
```
CREATE ROLE sample_role5;
GRANT ROLE sample_role1, ROLE sample_role2 TO ROLE sample_role5;
REVOKE ROLE sample_role1, ROLE sample_role2 FROM ROLE sample_role5;
```
The following example revokes the CREATE SCHEMA and DROP SCHEMA system privileges to sample\$1role1.
```
GRANT CREATE SCHEMA, DROP SCHEMA TO ROLE sample_role1;
REVOKE CREATE SCHEMA, DROP SCHEMA FROM ROLE sample_role1;
```