Revoking Select Permissions on Tables

👤 This documentation is intended for Site Administrators and/or Database Administrators.

In many cases, tables may contain private information that should not be shared with an instance's Sisense users. Database administrators can quickly revoke Sisense's access to these tables via a REVOKE command run by a database's superuser. The commands will vary slightly depending on the type of SQL database, and the examples on this page assume that the Periscope user has been named 'periscope'.

A quick way to test if the revoke was successful is to try selecting from a particular table in the Sisense editor. An error regarding the table not existing or the Sisense user not having permissions will indicate the revoke was successful.

Revoking MySQL Table Access

In MySQL, select privileges for a particular table can be revoked by a database superuser running a command similar to the following:

REVOKE SELECT ON my_table FROM 'sisense'@*

For additional reference, please see the MySQL Documentation Page on the Revoke Syntax.

Revoking Postgres Table Access

The Postgres syntax for revoking access is similar to MySQL, but lacks the single quotes and identifiers. The command is similar to what is shown below:

REVOKE SELECT ON my_table FROM sisense

The Postgres Documentation Page on the Revoke Syntax covers the possible alternatives and restrictions for schemas as well.

Revoking Redshift Table Access

The basic Redshift syntax for revoking access is identical to the syntax for Postgres:

REVOKE SELECT ON my_table FROM sisense

The Redshift Documentation Page for the Revoke Syntax also shows the different options when revoking access from a user or group.

Revoking SQL Server Table Access

SQL Server's syntax is also quite similar to Redshift and Postgres. The database name or table name can be specified in the revoke statement.

REVOKE SELECT ON my_table FROM sisense

Documentation depicting other Revoke options can be found on SQL Server's Revoke Page.