FAQ
Short answers to the questions users ask most often.
Why is a feature missing from my sidebar?
The portal lists only features you can open, so a short sidebar means that feature’s permission hasn’t been granted — ask an administrator. Features that vanished overnight, or several colleagues losing theirs at once, is an outage instead.
Why is my Data Catalog empty even though I can open it?
The catalog isn’t gated by a feature permission, but its contents are scoped to your data grants, so an empty catalog means you have none yet — ask an administrator or the warehouse owner. See data permissions.
Why does a dashboard or chart error instead of showing rows?
Dashboards is a door, not a filter: each query runs as you, so a chart on data you have no grant for errors. Note which tables it reads and ask for a grant. See how access works.
I was granted access — why don’t I see it yet?
It depends on the layer: a feature permission is live, so wait ~15 seconds and reload; a data grant applies to your next query, so press Check again in the catalog; Notebooks reads its permission at sign-in, so sign out and back in. See how access works.
My notebook query fails with a token error.
Your sign-in aged out — re-call load_user_catalog() and reload your tables, and if it still won’t
authenticate, sign out of Notebooks and back in.
Is my notebook work backed up?
No — your home persists across restarts but is not backed up, so treat the git remote as source of truth and push often. See working with Git and notebook storage.
Which engine should I use for my query?
Small and exploratory goes in a notebook; large and repeated goes over Trino in SQL Lab; the catalog preview is for a first look only. See query engines.
Why can I see every pipeline (or none)?
Pipeline access is fleet-wide: open Pipelines and you see every pipeline in the deployment, or none. There is no per-pipeline or per-team scope, so an empty list is not a permissions problem.
Do I log in again for each feature?
No — single sign-on means you sign in once and every feature trusts the same identity for the session. See quickstart.