You have a team sprinting through code reviews, releases, and analytics dashboards. Then someone asks for a data snapshot, and the thread devolves into “Who has permission for that?” chaos. JetBrains Space Looker is built to end that kind of chaos by unifying collaboration and analytics inside one governed workflow.
JetBrains Space handles communication, CI/CD, and package hosting. Looker turns raw data into live, explorable dashboards. Combined, they let engineers move from planning to measuring without switching contexts or leaking data across tools. The Space identity model and Looker’s permission layers tie together so you can trace a chart back to the team and commit that produced its numbers.
The setup logic is simple: Space provides a trusted identity source through its organization graph. Looker consumes that identity for access controls and audit logging. Space projects map to Looker folders, while Space roles (Developer, Maintainer, Admin) map to Looker groups. You manage everything through SSO, most often with OIDC or SAML backends like Okta or AWS IAM Identity Center. Once connected, any dashboard request runs with verified user context, not shared service accounts.
If Looker queries fail authorization, it usually means mismatched group attributes. Align role claims in your identity provider to Space roles and reissue tokens. For long-lived sessions, rely on refresh tokens that expire early and rotate automatically. Encryption keys should live in a managed KMS, never in pipeline variables.
Key benefits of integrating Space and Looker:
- Uses existing Space identities to enforce least privilege on data access.
- Links deployment metrics directly to commits and pull requests.
- Prevents credential sprawl by replacing API keys with scoped tokens.
- Improves compliance reporting for SOC 2 or ISO 27001 audits.
- Cuts time-to-insight because dashboards stay one login away from the repo.
Developers notice the difference fast. Fewer Slack messages about “who can see this dashboard.” No chasing Jira tickets for temporary access. Approvals move faster, builds stay cleaner, and graphs reflect production reality instead of exports from last week.
Platforms like hoop.dev turn those access rules into guardrails that enforce policy automatically. Instead of writing IAM glue, you define intent once and let it propagate across Space, Looker, and any other endpoint you protect. It is policy-as-enforcement, not just policy-as-documentation.
How do you connect Space and Looker?
Use Space as your OIDC identity provider in Looker’s admin panel. Map groups in your IdP to Space roles, verify token claims, and test one dashboard load per role. The whole process takes under an hour if your IdP is already federated.
AI copilots make this pairing even more useful. When LLMs query analytics APIs or suggest dashboards, consistent identity from Space keeps data exposure predictable. You can audit prompts, responses, and data lineage with the same visibility you give human developers.
In short, JetBrains Space Looker integration unites code, users, and data under one security model. Teams gain both velocity and clarity, which is the rare kind of automation everyone actually likes.
See an Environment Agnostic Identity-Aware Proxy in action with hoop.dev. Deploy it, connect your identity provider, and watch it protect your endpoints everywhere—live in minutes.