Join the waitlist

Security · Sep 17, 2026 · 5 min read

Private by default: who sees what in CIRO

Each person sees their own data or what is shared with them. Here is how sharing works, and why admins are not an exception.

The rule

Each person sees their own data, or what someone shared with them. That covers sources, dashboards, chats and Studio documents. Admins are not an exception: being an admin lets you manage people, apps and plans, not read everyone’s work.

How sharing works

Share with one person, a team or the whole company. When you share a dashboard or a Studio document, its data travels with it under your access, and CIRO lists the sources you are about to share so nothing goes out by surprise.

Being an admin lets you manage the workspace, not read everyone’s work.

Underneath

Each company’s data is kept separate, with row-level security on every table. Connections are read-only. Before any AI call, schema-level tokenization keeps raw identifiers away from the model, and your data never trains anyone’s model.

Only youYour chats, drafts and private dashboards.
Your teamWhat you share with a group.
The whole companyDashboards shared with everyone.
AdminsManage people, apps and plans. They see your work only if you share it.

Sign-in you control

SSO, two-factor authentication and sessions you can revoke. In Admin, access bundles decide which apps each person or group can open.

Key takeaways

  • You see your data and what is shared with you.
  • Admins manage the workspace; they don’t read your work.
  • Shared dashboards list the sources they share.
  • Your data never trains a model.
Try it on your own data.Free to start. Join the waitlist for 30% off your first 3 months.
Join the waitlist

Newsletter

Field Notes by CIRO

One email a month: product updates, playbooks for operators, and what we learn going live with customers. First issue on November 4.

Keep reading

All posts