Schema selection

By default, Buster will pull in all tables and columns that are accessible to the read-only user that you provisioned. Buster does not store your data. We only use your database metadata.

​

Toggle columns on and off

Any columns that are toggled on will be query-able by your end users. Do not include columns that:

• Are deprecated
• Aren’t relevant to the questions that your users will ask
• Contain data integrity issues

You do not need to include tables or columns necessary for joins. Buster will still map across relationships in your database to answer questions.

​

Access control validation

The columns that you enable and disable during this step will be used as access controls. Every query that Buster generates will be validated against what you’ve enabled and disabled.

For example, in the image above we’ve turned off the email and phone columns in the contacts table. The following is an example of a user dialog with these access controls in place:

1. User asks: “Show me all of the emails for our contacts”
2. Buster begins query generation process…
3. Query generated is SELECT email FROM contacts;
4. Buster validates if the user has access to the contacts table, then checks to see if the user has access to the email column.
5. In this case, Buster prevents the query from running because the email column is toggled off.
6. Buster responds: “I’m sorry but I don’t have access to the data you are requesting.”

Please note, you are able to come back and change which columns are toggled on/off at any time after onboarding.