Connect your data to Workspace
For data storage solutions and technologies that are not yet natively supported through the SQL cell, you can use Environment Variables in combination with Python or R to securely read and write data. Visit the dedicated documentation articles for instructions. If you'd like us to add native support or documentation for additional database technologies, reach out!
To set up a connection between Workspace and a database, you will provide Workspace with the credentials for a user account in your database that Workspace will use to execute queries against the database. The permissions of this user account will control which tables and records you can access when querying this database.
We recommend you create (or ask your database admin to create) a new database user specifically for using with Workspace. Grant this new user read-only permission for the schemas and tables you want users to be able to query.
In addition to getting the credentials, ensure your database:
- Is allowed to accept incoming connections from Workspace's IP addresses (all connections from Workspace will come from one of these three IP addresses):
Once database credentials are filled in and the database connection is set up, for security reasons the credentials can not be consulted again.
Don't have a database but still want to experiment with native database connections and SQL cells? Workspace features sample databases for every natively supported database technology. You can select the sample database in the dropdown when you create a SQL cell.
If you set up a database connection in your personal account, only you can use and edit this database connection. It can not be shared with other users. This means that you cannot invite other users as an editor to a personal workspace that has a database connected.
If you set up the database connection in a group that you're a part of, you can use and edit the database connection, but other members of the group can also use the database connection.
We will soon add role-based access control on database connections, so that you are able to control access to database connections more granularly.
A database is "publicly accessible" if the server the database is hosted on can be reached via any internet connection, not requiring users to be logged into a VPN or connected to a private network.
To check if your database is publicly accessible, run the following command on a computer that's not logged into your VPN or private network. Replace
your_db_portwith the host and port of your database:
- Linux or OSX:
nc -v your_db_host your_db_port
telnet your_db_host your_db_port
Workspace allows you to use TLS/SSL (Transport Layer Security/Secure Socket Layer) to encrypt communication with your database. This encrypts data while it's in transit between your database and Workspace. For auditing purposes, Workspace tracks who executed which query in what workspace and when.