Google Data Studio
for LuumenAI
Find Data Studio reports and manage who can view or edit them
Connect Google Data Studio and Luumen can find the report or data source you mean, read its current permission roles, and adjust who has access. Searches and permission reads answer right away. Changes to sharing — adding viewers, replacing role memberships, revoking a departing user — are previewed and held for approval by default. Authentication is OAuth2.
The Google Data Studio toolbox
5 tools: 2 read, 3 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet Asset PermissionsGet every populated permission role and the current concurrency etag for one Google Data Studio asset.
- ReadSearch AssetsSearch accessible Google Data Studio reports or data sources and return one page of asset metadata.
- WriteAdd Members to Asset RoleEnsure one or more members belong to a mutable asset role and verify each requested membership after the write. Approval by default
- WriteReplace Asset PermissionsReplace all four mutable permission-role memberships for a Google Data Studio asset, preserving owners and rejecting stale etags. Approval by default
- WriteRevoke Asset Member PermissionsRemove one or more members from every removable role on a Google Data Studio asset and verify whether each was removed or already absent. Approval by default
One prompt, start to finish
What a governed Google Data Studio run looks like inside Luumen.
Questions
Authorize once with OAuth 2.0. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — add members to asset role, replace asset permissions, revoke asset member permissions — is shown as a plan and requires approval by default, including the 2 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Google Data Studio — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
PostgreSQLQuery PostgreSQL state safely; maintenance held for approval.
MySQLQuery MySQL state safely; maintenance held for approval.
Microsoft SQL ServerQuery Microsoft SQL Server state safely; maintenance held for approval.Oracle DatabaseQuery Oracle Database state safely; maintenance held for approval.Put Google Data Studio to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.