Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Marketing Analytics › Looker Studio

Sharing and Embedding Reports

How to share Looker Studio reports safely: access levels, data source credentials, link sharing, scheduled delivery, embedding and per-audience views.
Guidebeginner11 min readUpdated

Access levels and what each allows

Looker Studio reports are shared much as files are in Google Drive: by inviting named people or groups, or by setting what a link allows. Each person holds one of a small number of roles, and the role governs the report, not the data behind it. The data source is shared separately with its own roles, which is the source of most surprises; a person can be an editor of a report and have no rights on its data source at all, in which case they can rearrange charts but not change fields or credentials.

RoleOn a reportOn a data source
ViewerOpen the report, use controls, change the date range, download or copy where the owner allowsSee the source's fields when building a report on it; cannot edit fields
EditorChange pages, charts, controls and styling; add or remove data sources; share, unless the owner has restricted sharing to themselvesEdit fields, calculated fields, freshness and credentials; share the source
OwnerEverything an editor can do, plus transfer ownership and deleteThe same for the source; the owner's credentials are what owner's-credentials mode uses

Two owner-only settings change what the roles above can do. One prevents editors from changing access or adding people, so a report with many editors still has one gatekeeper. The other disables downloading, printing and copying for viewers, which limits casual leakage of a PDF but is not a security boundary, since a screenshot is always possible. Google documents both in the sharing settings. The dashboard governance guide covers who should hold which role across a team's reports; here the point is that the role on the report is only half the answer.

Data source credentials: owner vs viewer

Each data source carries a credential mode, and that mode decides whose data a viewer sees. Under owner's credentials, every query runs as the person who owns the source's credentials, and every viewer sees the same data regardless of their own access to the product. Under viewer's credentials, each query runs as the person viewing, who must therefore have their own access to the analytics property, ad account or warehouse table; anyone without it sees an error in place of the chart. The data sources guide explains the setting; this section is about what it means for sharing. When a viewer reports that a chart shows an error the owner never sees, the troubleshooting page for a Looker Studio chart showing an error or no data checks access alongside the other causes.

Owner's credentials are what makes most marketing dashboards possible. A sales director has no reason to hold access to the advertising account, yet needs the cost-per-lead page; owner's credentials let the report show it. The price is that report access becomes the only barrier between the data and the world: whoever can open the report sees the owner's data in full, filtered only by whatever the charts apply. Viewer's credentials invert the trade: the data is as safe as the product's own permissions, and the report is useless to anyone without those permissions.

The combination to be deliberate about is owner's credentials on a GA4 or advertising source together with permissive link sharing. It is the configuration behind most accidental disclosures, and it happens by default when a report built for a small team is later opened up for convenience. Before widening any report's access, list its sources, note each one's credential mode and ask whether every new viewer should see what the owner can see.

Beyond named invitations, a report's link settings decide what the link itself grants. A restricted link opens only for people who have been invited. An unlisted link opens for anyone who has it, as viewer or editor depending on the setting, without the report being findable. A public setting goes further and allows the report to be discovered, which is appropriate for a report meant as a publication and for nothing else.

Unlisted links are convenient and widely misused. They travel: forwarded in email, pasted in chat, left in a shared document, indexed by a wiki. Once the link is out, revoking it means changing the setting, which breaks every legitimate reader at once. For reports with any data the business would not publish, the working rule is to invite people or groups by name and keep the link restricted; a Google group for the audience keeps the invitation list manageable as people join and leave. Use unlisted links for reports whose data is safe to show to anyone who might obtain the link, and for the short-lived demo that will be deleted afterwards.

A report built from a template or copied from another also inherits its data sources' credential modes, so a copy made to share more widely needs the same check as the original. Where an audience must see a report without being signed in — a screen in an office, a link in a newsletter — owner's credentials and an unlisted link are the only way, and the report should contain nothing that would embarrass anyone if the link escaped.

Scheduled delivery

Scheduled delivery sends the report by email on a timetable, as a PDF attached to a message with a link to the live report. The schedule's owner chooses the recipients, the pages included, the start time and the repeat frequency, and can set the date range that the delivery applies. It is the right tool for the audience that reads a weekly summary and never opens a dashboard, and for the executive who wants the month's KPI page in their inbox on the first working day.

The PDF is rendered with the schedule creator's access, which matters in two ways. Recipients see the data the creator can see, regardless of their own report or data source rights, so a schedule is itself a form of sharing and should be set up with the same care as a link. And if the creator leaves and their account is suspended, the schedule stops; schedules should belong to a role account or be recreated when the owner changes. In practice the attachment also fixes the moment the data was fetched, so a delivery sent before the platforms have finalised the previous day will carry provisional figures, and the start time should sit after the sources' usual update.

Delivery works best for pages designed to be read without interaction: a single question per page, the headline with its target, the annotated trend and a short table, as the dashboard design guide describes. Pages that depend on filter controls or cross-filtering lose that interaction in a PDF and should be left out of the schedule. Keep the recipient list to a group rather than individuals, so leavers are removed in one place.

Embedding

Embedding places a live report inside another web page using the embed option from the report's file menu, which provides either an inline frame snippet or a URL for a page builder. Embedding must be enabled on the report, and the embed carries the report's sharing settings: visitors to the host page see exactly what they would see opening the link directly. On an intranet where visitors are signed in with invited accounts, a restricted report embeds cleanly. On a public site, the report needs link sharing that allows anyone to view, and its sources need owner's credentials, with all the consequences described above.

Embedding is useful in three situations. A client portal or internal wiki where the report sits beside its commentary and other links. A single-page summary on a site that already handles its own access, such as a project space. And the office screen, where a kiosk page cycles through dashboards. In each case, the host page can pass parameters in the URL to preset controls, so one embedded report can show a different market or client per host page, provided the viewer cannot simply edit the URL to see another — which, for owner's-credentials reports, they can.

What embedding does not do is add any security. A frame on a page behind a login is still a report with its own link, and anyone who extracts the URL from the page source holds the same access the frame does. Treat the embedded report's own sharing settings as the only control that exists, and keep sensitive reports out of embeds unless viewer's credentials and named access are in place.

Illustrative example — not a real result

An agency's three clients, one report, no leaks

A performance agency reports to three retail clients from a single Looker Studio report built on one BigQuery reporting table that holds all accounts. The first attempt used owner's credentials and one unlisted link per client with a client filter in the URL; within a week one client's analyst changed the parameter and saw a competitor's spend. The rebuild keeps owner's credentials for convenience but adds a viewer-email field to the reporting table — each row carries the email addresses allowed to see it — and switches the data source to filter by viewer email. Each client's two or three named users are invited directly, link sharing is restricted, and a scheduled PDF of the headline page goes to each client's group at eight on Monday mornings. Over the next quarter the agency serves 14 named viewers from one report, and an audit of the access list takes ten minutes because the three Google groups are the whole story.

Per-audience views

Most organisations have more audiences than reports: executives who want one page, channel managers who want their channel, clients who must see only their own accounts, finance who want the cost figures without the Funnel detail. There are four ways to serve them, and they trade simplicity for maintenance in a predictable order.

Pages within one report are the simplest: one page per audience, with navigation, and everyone sees everything. This suits a single internal team where there is nothing to hide, and the dashboard design guide covers keeping each page to one question. Copies of the report, one per audience, each pointed at a source filtered to that audience's data, are the next step; robust and obvious, but every design change must be made in every copy, which governance has to track.

Filtering the data source by viewer email, which Looker Studio supports for sources that carry a field of permitted email addresses, keeps one report and one source while showing each signed-in viewer only their rows. It needs a reliable mapping from accounts to viewers, maintained in the data, and careful testing with a non-admin account, but it scales to many audiences without copies. Viewer's credentials are the fourth option: each person sees whatever the product itself allows them, which is the right answer when the product's permissions already model the audiences, as they often do for an analytics property per market or an ad account per client.

Parameters in the URL and report-level controls are not an access method. They change what is shown by default, not what can be shown, and anyone who can edit a control or a URL can see the rest. Use them for convenience within an audience that may see everything, never as the boundary between audiences.

Auditing access

Access drifts. People are added for a project and never removed, links are shared "just this once", a copy is made for a workshop and forgotten. Auditing is the practice of listing who can see what and comparing it with who should, on a schedule and whenever someone leaves. The report's sharing dialog lists every named person and group, and the link setting; each data source's sharing dialog lists its own. Both need checking, because a person removed from the report who remains an editor of the source can still build a new report on the data. For a new dashboard, the dashboard launch QA checklist sets permissions by role and checks for exposed personal data before the link is first shared.

For an organisation on Google Workspace, administrators can review Looker Studio activity in the admin audit tools, which show events such as sharing changes; the paid Looker Studio tier adds further audit logging and reporting on report usage, which answers the other half of the question — not only who can open a report, but who does. Google documents what each tier records; standard accounts should assume that the sharing dialog is the only record and keep their own register of reports, owners, sources, credential modes and audiences.

That register is the practical audit tool. One sheet with a row per report — owner, link setting, sources and their credential modes, audience, schedule recipients, last reviewed — turns an afternoon of clicking into a scan. The dashboard governance guide describes maintaining it alongside definitions and retirement; the SEO KPIs and reporting guide shows the same discipline applied to one channel's reporting, where the audience is usually mixed between specialists and stakeholders.

Common mistakes

  • Owner's credentials plus an unlisted link. The commonest accidental disclosure; check the pairing before widening access.
  • Treating URL parameters as access control. They preset a view; they do not prevent another.
  • Schedules owned by a person who leaves. The delivery stops, and until it does, it keeps sending their view of the data.
  • Embedding a restricted report on a public page. Visitors see an error, and the fix people reach for is the dangerous one.
  • Auditing the report but not the source. A former colleague who still edits the source can rebuild the report.
  • One unlisted link for everyone, forever. Revoking it breaks every reader; invite groups by name instead.
  • Disabling download and calling it secure. It discourages a PDF; it does not stop a screenshot.
  • Forgetting the copies. Every workshop copy carries the original's credentials and its own sharing settings.

The Looker Studio hub links the rest of the series; sound sharing starts with sound sources, so the data sources guide is the companion read.

Frequently asked questions

Can someone without a Google account view a Looker Studio report?

Only through a link setting that allows anyone with the link to view, combined with data sources that use owner's credentials, because a viewer's credentials require a signed-in account with access to the data. That combination means anyone who obtains the link can see the data, so it belongs to reports whose content is genuinely safe to publish. For client reporting, inviting a named Google account is the safer default.

Why does an embedded report show an error for some visitors?

The embed carries the report's sharing settings with it. If the report is restricted to named people, visitors who are not signed in as one of them see an access error inside the frame; if a data source uses viewer's credentials, the visitor also needs access to the underlying data. Embedding on an internal page usually works because visitors are signed in; embedding on a public site needs link sharing and owner's credentials.

How do I show each client only their own data from one report?

Either make one copy of the report per client, each pointed at a source filtered to that client, or keep one report and filter the data source by the viewer's email address, which Looker Studio supports for sources where a field holds the email. The copy approach is simple and robust; the email filter avoids maintaining copies but needs a reliable mapping of viewers to accounts and careful testing.

Terms used on this page

Where this page is used

Also related

Sources

  1. Looker Studio Help — Looker Studio Help

Related