Set a password for this file. Anyone opening the downloaded file must enter this password to view the upload credentials.
Minimum 8 characters. Share the password separately — do not send it in the same email or chat as the file.
.html file or .zip bundle — or click to browse
Upload one .zip file that contains both:
index.html file, plus any images or files it uses.reproducibility/lineage.json that says where the numbers came from, who (or which tool) built the report, and when.The proof must point to the actual data behind the report: either the data-warehouse queries it was built from, or a copy of the source data file included in the same .zip. If an AI tool built the report for you, keep the data file you gave it and include that file in the .zip. The system checks everything automatically — a Regulated report without this proof cannot be sent for review or published.
The lineage.json file must record: the generator repo and git commit (generatorRepo, gitSha), dbtModels, the semantic-layer version, run parameters, runTimestamp and runnerIdentity, the data reference (bigQueryJobIds + dataAsOf, or a sourceFileSha256 of the uploaded source file), a files list with a SHA-256 for every bundle file, and the outputSha256 of the output. The server verifies every hash.
A Collection references existing artifacts — no file upload is required. Hold Ctrl/Cmd to select several. Membership can be edited later from the Collection's detail page.
Certification & Stewardship are system-derived — trust is earned from governance & certified-metric usage, and stewardship from ownership & activity. Neither is author-set here.
Creating your artifact…
Your artifact is saved as a Draft. Assign a reviewer to send it into the review queue — you can’t approve your own artifact, so a different person signs off before it publishes. Not ready? Save as draft and submit it for review anytime from its page.
Your artifact was created. Submit it for review to publish it to the catalog.
.html file, a .zip bundle, or a single .pdf / .docx / .xlsx / .pptx document to replace it. The link and everything else stay the same.
The stored file must be a .zip that contains the report (index.html) together with a proof-of-origin record (reproducibility/lineage.json) showing where the data came from, who or which tool built the report, and when. Without that proof, this Artifact cannot be sent for review or published — use Edit → Replace to upload a package that includes it.
Certification & Stewardship are set automatically by the system and can't be edited here.
This will publish the artifact directly to the catalog — no review step required.
Preview of version. Restoring uploads this content as a new current version — your current live version is first saved to history, so nothing is lost.
This artifact will be placed in the review queue. The reviewer you specify below will be asked to approve or return it with feedback.
Approving will publish this artifact to the catalog and make it visible to all users.
The artifact will return to Draft status. Your comments will be shown to the author on the detail page.
This will cancel the review request and move the artifact back to Draft status. The reviewer will no longer see it in their review queue.
Creates a copy of this artifact as a new Draft. Content, domain, and tags are copied. Password, thumbnail, and invite-only are not.
Are you sure you want to download this artifact?
Add the people or groups you want to share this artifact with.
Save a named group of recipient emails. You can then pick it from the Share dialog to auto-fill everyone at once.
Share this group with other users. They'll see it in their own Share dialog and can use it to auto-fill recipients. Sharing is read-only — only you can rename it, delete it, or change its members.