eltPulse exposes an authenticated catalog for everyone in a workspace — not a public internet Signed-in users browse pipelines, connections, transform outputs, and optional git SQL projects; team roles control who can edit metadata and who sees the full catalog vs public-tagged entries only.
Each asset can carry a description and tags stored as catalog entries. Use tags like catalog:public or public to mark datasets that catalog-browser teammates may see when their role restricts visibility to public entries only.
Users with catalog editor or member roles can update descriptions and tags from asset detail pages or the assets list (import from pipelines when permitted). Viewers and catalog browsers cannot edit metadata.
Organization owners invite teammates from Team with one of these roles:
| Role | Catalog browse | Edit metadata | Pipelines / canvas / dbt admin |
|---|---|---|---|
| Member | Full | Yes | Full write |
| Viewer | Full | No | Read-only |
| Catalog editor | Full | Yes | Read-only (no pipeline saves, no dbt project create/run) |
| Catalog browser | Public-tagged only | No | Read-only |
API keys may include catalog:read and catalog:write scopes in addition to pipeline scopes. Catalog write allows metadata edits without full pipeline write.
GET /api/elt/catalog/overview — summary counts (filtered by visibility).GET /api/elt/catalog/search — search entries (visibility filter applied server-side).PUT /api/elt/catalog/entries — upsert description/tags (requires catalog edit permission).GET /api/elt/assets — workspace asset map (public-only filter for catalog browsers).GET /api/elt/workspace/permissions — current user role flags for UI gating.