The default database schema for every Panoply database is named
public. 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. Panoply is looking for ways to increase the functionality available to users related to the use of custom schemas.
What creates tables in the
When Panoply ingests data through Panoply data source connector, the tables that are created are all in the
What creates tables in schemas other than the
Third-party ingestion tools sometimes create a new schema for every integration. Consult the documentation for your specific tool to determine its defaults and available configurations.
Functionality related to the
Teams configurations affect permissions related to the
public schema. By default, Teams does not apply to schemas other than the
Functionality available in all schemas
Regardless of the constraints present in the Panoply UI, authorized users have full control over their databases. Just as authorized users can create additional schemas in a database, they can also grant specific permissions for users or for teams through direct queries.