If you share a Power My Analytics hub with teammates, or you're an agency working inside a client's hub, you'll want to know exactly what everyone else can see. Here's the short version: everyone in a hub sees the same connected sources and data, your Data Studio reports list is yours alone, and who can open a specific dashboard is controlled by sharing in Data Studio.

• Applies to: All plans
• Who it's for: Hub members, agencies, and clients
• Destination: Data Studio (formerly Looker Studio)

The Short Answer

Layer 1: Everything Connected to a Hub Is Shared

Every member of a hub can see every connected data source, every account under those sources, and every export. Any member can also report on that data, for example by creating their own Data Studio data source from it.

This is by design, and there's no setting that hides one member's sources from another. Creating extra user accounts in the same hub doesn't create separation either.

Working inside a client's hub? Assume your client can see every source and account you connect there, and can build their own reports from that data.

Hub Security toggles aren't privacy controls. Under Hub name > Settings > Hub Security, a Hub Owner can limit members' ability to cancel the subscription or see billing information. These toggles don't change which sources, accounts, or data members can see.

Layer 2: Your Reports List Is Yours Alone

In your hub, go to Reports > Data Studio and look for the Your reports section. It lists Data Studio reports from the Google account (or accounts) you connected there, with the report name, owner, created and last-updated dates, and a link to open each one.

That Google account connection is saved to your own user profile, not to the hub. Other members don't see your reports in their list, and you don't see theirs. Each person connects their own Google account and gets their own list.

• The Google account you connect doesn't have to match the email you use to sign in to Power My Analytics. Whichever Google account you connect decides which reports appear.
• The list is for finding and opening your reports. It doesn't change who can open them or what data they show.

Layer 3: Opening a Report Is Controlled in Data Studio

Data Studio reports follow Google's own sharing settings. Power My Analytics doesn't grant, remove, or override them.

• A report you haven't shared can only be opened by you.
• A report you've shared can be opened by the people you shared it with, whether or not they're members of your hub.
• The report's data credentials decide whose Power My Analytics access powers the charts:
  • Owner's Credentials: Anyone you share the report with sees the data, even if they don't have a Power My Analytics account.
  • Viewer's Credentials: Each viewer needs their own access to the hub. Viewers without it see the error "You are not part of this organization."

To check or change this setting, open the report in Edit mode, go to Resource > Manage added data sources, click Edit next to the Power My Analytics data source, then set Data credentials.

A Power My Analytics data source in Data Studio is tied to the Google account that created it. If that person leaves your organization, reports using it lose their connection (the data isn't lost). See Transferring Access When a Team Member Leaves to hand things over smoothly.

Worked Examples

Example 1: An Agency Analyst Working Inside a Client's Hub

Jordan works at Brightline Agency. Brightline's client, Acme Outdoor, invites Jordan to Acme's hub. Jordan connects Acme's Google Ads and Facebook Ads accounts, then builds a Data Studio dashboard while signed in with a Brightline Google account. Jordan hasn't shared the dashboard yet.

Here's what Acme's Hub Owner can and can't do:

Takeaway: Jordan's dashboard (its layout, charts, and analysis) stays private until Jordan shares it. The data underneath it doesn't; Acme can see and use it.

Example 2: Sharing a Finished Dashboard with a Client Stakeholder

Jordan's dashboard is ready. Jordan clicks Share in Data Studio and adds two people from Acme as viewers: Sam, Acme's marketing manager (a member of Acme's hub), and Lee, Acme's CEO (not a hub member).

• With Owner's Credentials, both Sam and Lee see the data.
• With Viewer's Credentials, Sam sees the data because Sam is a hub member. Lee sees "You are not part of this organization" instead.

Takeaway: For stakeholders who aren't in the hub, use Owner's Credentials on the report's data source.

Example 3: Two Teammates in the Same Hub

Priya and Marco are on the same in-house marketing team and share one hub. Priya connects her work Google account under Reports > Data Studio and sees her 12 reports. Marco connects his and sees his 5.

• Neither sees the other's reports in their Your reports list.
• Both see every source and account connected to the hub.
• If Priya wants Marco to help edit one of her reports, she shares it with him in Data Studio with edit access.

Example 4: Keeping Agency Work Separate with Your Own Hub

Brightline decides it wants working dashboards that Acme can't see until they're finished. Instead of working inside Acme's hub, Brightline uses its own hub on the Pro plan:

1. In Brightline's hub, Jordan goes to Sources and clicks + Add new source.
2. Jordan turns on Request access from source owner, selects Google Ads, and copies the Auth Link.
3. Jordan sends the link to Sam at Acme. Sam signs in to Google Ads and approves the request. Sam doesn't need a Power My Analytics account.
4. The Google Ads source appears in Brightline's hub, visible only to Brightline's team members.
5. When the dashboard is ready, Jordan shares it with Acme from Data Studio (see Example 2).

Takeaway: Acme can't see anything in Brightline's hub because nobody from Acme is a member of it. Keep in mind that sources connected this way count toward Brightline's plan and billing, and Acme can revoke access from its Google Ads account at any time. For full steps, see Request Access from a Source Owner Using Auth Links.

Example 5: Limiting a Member with Hub Security

Acme's Hub Owner goes to Hub name > Settings > Hub Security and turns off members' ability to see billing information. Jordan can no longer see Acme's billing details, but still sees every source, account, and export in the hub. Hub Security manages what members can do with the subscription, not what data they can see.

Choosing a Setup for Agency Work

Good to Know

• Visibility works the same on every plan and for every role: Owners, admins, and members all see the same sources, accounts, and exports.
• The people you share a Data Studio report with don't need to be hub members, as long as the report uses Owner's Credentials.
• If you're not sure what a specific person can see, submit a ticket and include the hub name and the report link (as text), and our support team will help you check.

Related Articles

• Manage Team Roles and Permissions
• Request Access from a Source Owner Using Auth Links
• Transferring Access When a Team Member Leaves
• Understanding How Data Studio Connectors Are Assigned to Power My Analytics Accounts
• Error: You Are Not Part of This Organization, Please Check Your Access Token or Organization ID