Schemas in Redshift

Panoply on Redshift

The public schema is the default schema for Panoply on Redshift. Every user who can connect to a database has access to this schema and everything in it. Authorized users can create additional schemas, which can be used to order, group, or categorize tables. For example, you might have a marketing schema with tables from Google Ads and a finance schema with tables from Stripe.

This article explains when and how Panoply uses the public schema, and which pieces of functionality are specifically available only in this default schema.

What creates tables in the public schema?

When Panoply ingests data through a data source connector, the tables that are created are all in the public schema. Users can also create custom schemas and use those to ingest data into Panoply.

What creates tables in schemas other than the public schema?

Third-party ingestion tools sometimes create a new schema for every integration. Some third-party ETL tools will not allow users to assign permissions to tables they create to have user permissions. Consult the documentation for your specific tool to determine its defaults and available configurations.

Functionality related to the public schema

By default, every user in every user group (admins/editors/viewers) has the usage privilege in this schema. Users who have the admin and editor permissions also have the create privilege. Users tab groups apply to the tables and views in this schema. Users can select/insert/delete based on their group.