dip db — rows never pass through Dippr’s control
plane. Trino reads it live as a catalog under ordinary governance, so a row you write is in the
next query’s result, and its owner can write to it with Trino SQL too.
Open it from Databases in the console. Anyone who can run a query at all can also create, read,
update or delete their own workspace databases — there is no separate privilege to ask for.
Personal vs shared
You never create your own personal database — it exists the moment you first reach for it. There is
no naming step and nothing to ask an administrator for: it’s named after you, from the local part of
your email (so
bob@corp.com gets a database and catalog called bob), set once when it’s created.
Changing your email later doesn’t rename it. A shared database is different: you name it, you own it,
and you choose who else may write to it.
A data plane has room for one personal database per member. With more than one data plane in your
tenant, you have one personal database on each. A SQL name is unique across your whole tenant, so
the personal database you get on a second plane takes a short suffix (for example bob_1a2b3c4d);
use the name shown next to In SQL on its card.
Administrators
A Data admin or Account admin sees every workspace database, not only their own:- In the console, Databases lists every workspace database in the tenant, on every data plane.
- Through an agent’s MCP connection,
workspace_db_listlists every workspace database on that connection’s data plane. A database on another plane isn’t listed there, and that’s the plane scope, not a missing permission.
dip db delete or dip db invite with its name. Only a shared database takes
invitations: a personal database stays its owner’s alone. An admin can’t mint a connection token for a
database, or write it with DuckDB or dip db, without being its owner or an invited member. Seeing
a database in this list isn’t reading it: in Trino an admin reads or writes someone else’s database
only with a share or a grant that names that database’s catalog, and doesn’t see it in SHOW CATALOGS
without one (see Query and share a database).
The role is the one assigned to you under Settings → Users, and a change applies on your next request.
Remove someone’s Data admin role and they go back to seeing the databases they own or were invited to.
An API key gets the admin view only if the service user it was minted for holds one of those roles.
Every workspace database on a given plane shares that plane’s single underlying pod and disk. Delete
your tenant’s very last workspace database on a plane with --discard-data (see
Deleting a database) and that pod and disk are torn down
too, not just the record. The console’s own Delete button never does this.
How your data becomes queryable
A workspace database is queryable in Trino with nothing to run after a write. Engines read it live:- When the database first starts serving, Dippr creates its catalog and gives you, the owner, access to read it and to write it with Trino SQL. This happens once in the database’s life.
- The engines on its data plane mount the catalog with one catalog apply. Applying restarts an engine, so Dippr does it for you only when that affects nobody else; otherwise the engine shows catalogs pending until someone who manages it clicks Apply.
- From then on, every row you write is in the next query’s result. Writing and adding tables never need another apply.
dip db, an agent, or, as the owner, Trino SQL. See
Connect and write for the write side and
Query and share a database for the catalog and sharing.
Availability
Workspace databases are a plan-gated feature, and the gate only ever blocks acquiring or growing one — never seeing or releasing what you already have. If your tenant doesn’t have the feature and holds no databases yet, the Databases page shows an explainer in place of the page: what a workspace database is, and that your account admin can turn it on. If your tenant already holds databases when the feature is off — commonly, it was turned off after they were created — the page still shows them, with a banner:Workspace databases are not enabled for this workspace You can still see these databases and delete them, so nothing you are paying for is stranded. Creating and connecting need the feature enabled — ask your account admin.Creating a database, connecting to write, inviting a member, and minting a connection token are all disabled in this state, each with a tooltip naming the same reason. Deleting a database — including your own personal one — keeps working, since it’s the one way to stop paying for something you can no longer grow. Ask your platform operator to enable workspace databases. See Entitlements for the full list of plan-gated features. Even with the feature turned on, a workspace database needs somewhere to run: it is a pod and a disk inside a data plane. If your tenant has no data plane registered yet, the page asks you to register one first — see Data planes.
Which roles can use workspace databases?
Every member with the built-inviewer role, or any role above it, has their own personal
workspace database. With viewer you can create it, load a spreadsheet into it, connect to it
and read it, in the console, with dip db and through your agent’s workspace database
tools. That is all viewer covers: you can’t create a shared database, be invited into one, reach
another member’s database, or add sample data.
Shared databases, invitations, renaming and deleting a database, and sample data start at analyst:
analyst, data_engineer, data_admin or account_admin (see the
Roles and permissions matrix).
A workspace admin can turn the personal database off for viewer. See
Turn off personal databases for viewers.
Why does it say my role doesn’t allow this workspace database action?
You asked for something your role doesn’t cover: for example a shared database or sample data withviewer, or anything at all after an admin turned personal databases off for your role. dip db
and your agent both answer with the same line:
Your role in this workspace doesn’t allow this workspace database action. Next: ask a workspace admin to give you the analyst role (Settings → Users).A workspace admin adds the role from Settings → Users with + role on your row (see Manage members). Nothing you already stored is deleted in the meantime. A database you made earlier is still there, and you can reach it again once your role covers it. With
--json, dip also reports the same step in next_action.
A connection token stops working within about two minutes of your role no longer covering its
database, and an open DuckDB connection is closed. Once your role covers the database again, create
a new token (dip db connect, or Connect in the console).
Addresses
Every database’s connection address and every piece of SQL you’re meant to paste into DuckDB is composed by Dippr and shown to you verbatim. Never type or guess this address yourself: your data plane’s own domain decides it, and that domain can differ between planes.Who can read your database in Trino?
The owner of a database gets a read grant on its catalog automatically, when the catalog is created. Nobody else does, including people you’ve invited to write to the database. Every other member needs a read grant before their queries against it succeed: you can share it, or an admin can grant it like any other catalog. Writing to a database and reading its catalog are two separate decisions, and inviting someone to write grants only the first. See Connect and write a database to start putting data in one.Related
Connect and write to a database
Get the connect snippet and load data with your own DuckDB.
Query and share a database
Query it live from Trino and share read access.