Course contentsShow
← Cloud and Infrastructure
Lesson 2933 of 2,98964. Platform EngineeringFree lesson

RBAC and Portal Access Control

Implementing role-based access to control who can view or provision services through the portal.

RBAC and Portal Access Control

What you'll learn: How to use role-based access control to govern who can view and provision resources through your developer portal.

Why Portal Access Control Matters

Your developer portal (like Backstage) is a powerful self-service tool—but not everyone should access everything. Just as you wouldn't give every employee the keys to every office, you shouldn't grant all developers permission to provision production databases or view sensitive service configurations.

Understanding Portal RBAC

Role-Based Access Control (RBAC) in a portal context means assigning permissions based on roles rather than individuals. Think of it like a library card system: students can browse and check out books, librarians can also catalog new items, and only administrators can modify the entire system.

In your portal, this translates to:

  • Viewers can browse the catalog but cannot create resources
  • Developers can use templates to scaffold new services in development environments
  • Platform Engineers can modify templates and infrastructure configurations
  • Admins control production provisioning and sensitive integrations

Implementation Patterns

Portal RBAC typically integrates with your existing identity provider (SSO/federation) and leverages conditional access policies you've already learned. The portal checks user roles before:

  • Displaying catalog items or documentation
  • Enabling "Create Component" buttons on templates
  • Executing infrastructure provisioning workflows
  • Revealing cloud resource visualizations for sensitive environments

Most portals support group-based permissions, where roles are inherited from identity provider groups (Active Directory, Okta, etc.), maintaining consistency with your broader Zero Trust security model.

Key Takeaway: RBAC in developer portals enforces the principle of least privilege at the self-service layer, ensuring developers have golden path access to what they need while protecting critical infrastructure from unauthorized changes.