Access Controls in Hoop

Define group-based access to your infrastructure that syncs with your identity provider

Track
Platform Fundamentals, lesson 1
Length
6 min video
Level
Beginner
For
Platform Engineer

Tags: beginneraccess-controlsadminrbacoktaazure-ad

All lessons

Watch this lesson

Enter your work email to open every lesson in hoop University. One email, full access. No spam.

What you will learn

  • Create a user group in the Hoop admin interface and assign infrastructure resources to it
  • Add users to groups so they inherit access to assigned resources
  • Understand how Hoop hides all resources from users by default until access is explicitly granted
  • Run a query as a developer through the Hoop Web UI against a connected database
  • Review session activity as an admin, including who ran what query and when

Chapters

  1. Introduction to the Hoop control plane

    Framing Hoop as a control plane for infrastructure access and introducing the access controls focus of this lesson.

  2. Why group-based access matters

    The problem with all-or-nothing access in most engineering organizations and how Hoop solves it through identity-provider-integrated groups.

  3. Admin perspective: creating a user group

    Walkthrough of creating a Platform group in the admin interface and assigning a database resource to it.

  4. Identity provider sync

    How groups sync from Okta, Azure AD, or Auth0 in production environments via tokens at login.

  5. Developer perspective: default-deny in action

    Logging in as Teo to confirm zero resources are visible until access is granted.

  6. Granting access through group membership

    Adding Teo to the platform engineering group and watching the resource appear in his account.

  7. Running a query as a developer

    Executing a select all users query through the Hoop Web UI and viewing the results.

  8. Admin audit review

    Reviewing the session in the sessions tab: resource, user, timestamps, query, and results.

  9. Recap and what's next

    Three takeaways on group-level access, default-deny, and automatic session recording. Preview of the data masking lesson.

Key concepts

Control plane
Hoop acts as a central control plane for everything interacting with your critical infrastructure, with all activity tracked and monitored.
User group
A collection of users that shares access to the same set of resources. Access is defined at the group level rather than per individual.
Resource
A connected piece of infrastructure such as a database, server, or cloud service that users can interact with through Hoop.
Default-deny model
All connections and resources are hidden from users by default unless an admin explicitly grants access through group membership.
Identity provider sync
In production environments, Hoop groups sync automatically with identity providers like Okta, Azure AD, or Auth0. Group membership arrives with the user's token and Hoop enforces access accordingly.
Session recording
Every action taken through Hoop is automatically recorded and made available in the sessions tab, including the resource accessed, the user, timestamps, the exact query run, and its results.

Check what you learned.

3 questions. No clock, no account. Each answer shows the right option and why, and you can change it any time.

Answer 3 short questions about this lesson.

  1. 1By default, what does a new user in Hoop see when they log in?
  2. 2Where should access be defined in Hoop for it to scale with your organization?
  3. 3What does Hoop capture in the sessions tab for an admin to review?