Organizations and roles
Personal versus organization context, and who can do what.
Everything you create (connections, configs, dashboards) belongs either to you personally or to an organization.
Two contexts
| Context | Visible to |
|---|---|
| Personal | Only you |
| Organization | Members, subject to their role |
Switching context switches what you see. A connection created personally does not appear to teammates until it is migrated.
Migrating to an org
POST /api/configs/{key}/migrate-to-orgThis is one-way in practice: once a config is shared and teammates build dashboards on it, pulling it back to personal breaks their cards.
Roles
Access is enforced by role and permission on every endpoint, not just hidden in the UI. A member without permission to manage connections cannot create one by calling the API directly.
Decide context before you build
The commonest cleanup task is migrating a pile of personal configs that should have been organization-owned from the start. If more than one person will ever ask these questions, create it in the org.