analytics-hub-publisherlisted

# Analytics Hub publisher ## Decide the sharing mechanism first Analytics Hub is not always the answer. Work down this table before designing an exchange. | Situation | Use | Why not Analytics Hub | | --- | --- | --- | | One team, same org, one dataset | dataset IAM grant | an exchange is overhead for one grant | | Row or column restrictions per consumer | authorized view, or row-level security | listings share the whole dataset | | Many consumers, stable product, cross-project | Analytics Hub | this is what it is for | | External partner, different org | Analytics Hub | no data copy, no egress, revocable | | Consumer needs to write | not sharing, a pipeline | linked datasets are read-only | | One-off extract | authorized view or an export | a listing implies a commitment | Say plainly that a listing is a product commitment. Publishing one means you have promised a schema, a freshness, and a deprecation path to people you may never meet. If the user is not ready for that, recommend an authorized view instead. ## Structure - **Exchange**: a container, scoped by audience. `internal-analytics`, `partner-suppliers`, `public-reference`. Do not put internal and partner listings in the same exchange. - **Listing**: one per data product, backed by one dataset. - **Linked dataset**: what the subscriber creates in their own project. It is read-only, queried on the subscriber's own slots, and reflects the source live. Billing follows the query, so subscribers pay for their