# FAQ (/reference/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. If features vanish for several colleagues at once, report it to your
Databaas team 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](/catalog/data-permissions).

## Why does a dashboard or chart error instead of showing rows?

Dashboards are 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](/access/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](/access/how-access-works#when-a-change-takes-effect).

## My notebook query fails with a token error.

Your sign-in aged out. The catalog itself does not need re-creating — sign out of Notebooks and back
in, then reload your tables.

## Is my notebook work backed up?

No — your home and the shared folder persist across restarts but are not backed up, so treat the git
remote as source of truth and push often. See [working with Git](/notebooks/git) and [notebook storage](/notebooks/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](/dashboards/query-engines).

## Why can I see every pipeline (or none)?

Pipeline access is fleet-wide: open Pipelines and you see every pipeline in your instance, 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.
Where your instance is connected to your organisation's identity provider, you sign in with your
organisation account. See [quickstart](/getting-started/quickstart).

## How do I stop a pipeline that is running away?

Pause it so no new runs start, then mark the running run as failed. You need **Run pipelines**. See
[monitoring pipelines](/pipelines/monitoring).

## Can I hide columns or rows from some people?

Not within one table. Access is granted per warehouse, namespace or table, with no column masking or
row filtering. Build a separate table with only the columns or rows a group may see — typically in a
pipeline — and grant that table instead. See [limits](/reference/limits).

## Can I work from VS Code or PyCharm?

Yes — connect your editor to your notebook server with a token. See
[connect from an IDE](/notebooks/ide).

## Where do I get help?

Ask your platform administrator about access, or contact your Databaas team.