Role
A role is a defined function, responsibility, perspective, or set of permissions associated with a participant in an organization or system.
Authorization in Action
A role is an authorization abstraction that groups permissions or access responsibilities for assignment to principals.
- How it is used
- Organizes permissions around job functions and responsibilities for scalable authorization, onboarding, job changes, and audits.
- How deep it goes
- Defines roles and works through RBAC assignment, inheritance, separation of duty, and limitations, while deferring dynamic conditions to other approaches.
- Examples
- Uses enterprise engineer and support roles, inherited deployment permissions, collaborator and viewer UI roles, and tenant-issued project-role credentials.
- What you can do after
- Apply roles to centralize permission assignments, evaluate inherited access, and recognize when contextual requirements exceed static RBAC.
Amazon Web Services in Action, Third Edition: An in-depth guide to AWS
An IAM role is an AWS identity with permissions that can be assumed by trusted entities such as services or processes.
- How it is used
- Authenticates EC2 instances and Lambda functions making AWS API calls, while identity policies authorize their actions.
- How deep it goes
- Works through console setup and CloudFormation and SAM policies, including trust, instance profiles, temporary credentials, and least-privilege conditions.
- Examples
- Uses an EC2 Session Manager connection, a self-stopping instance, and a Lambda function that tags EC2 instances.
- What you can do after
- Apply it via IAM, CloudFormation, or SAM to give EC2 and Lambda workloads the permissions their tasks require.
Read how Amazon Web Services in Action, Third Edition: An in-depth guide to AWS explains role →
Effective Platform Engineering
A cloud role is a permission-bearing identity configuration that can be assumed by an authorized user, service, or pipeline.
- How it is used
- Grants infrastructure pipelines the permissions required to change their assigned cloud resources.
- How deep it goes
- Defines role assumption and describes a dedicated role-management pipeline, without detailing individual permission policies.
- Examples
- Illustrates consistent pipeline roles across state, sandbox, non-production, and production accounts.
- What you can do after
- Operate/configure AWS pipeline roles so service accounts can assume permissions scoped to each pipeline’s resources.
Spring Security in Action, Second Edition
A role is a named grouping of permissions or authorities used to represent an actor's access level.
- How it is used
- Groups recurring permissions so Spring Security can restrict endpoint access according to an authenticated user's role.
- How deep it goes
- Explains role grouping, GrantedAuthority representation, ROLE_ naming, Java configuration, and a successful-versus-forbidden request test.
- Examples
- Uses READER, MANAGER, and ADMIN roles, plus john and jane requests demonstrating successful access and HTTP 403 Forbidden.
- What you can do after
- Apply it via Spring Security by assigning roles and configuring hasRole rules for protected endpoints.
Read how Spring Security in Action, Second Edition explains role →
Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform
An access-control role is a named collection of permissions that can be assigned to an identity or service account.
- How it is used
- Uses roles to manage IAM access, enforce least privilege, and separate high-level permissions from monolithic infrastructure configuration.
- How deep it goes
- Explains permission grouping and demonstrates extraction, state import, verification, and removal, but does not detail role internals.
- Examples
- Uses GCP project IAM extraction and a frontend pipeline limited to network, application, and Cloud SQL roles.
- What you can do after
- Operate/configure role-based access by composing minimum permission sets and safely importing existing IAM resources into separated Terraform state.
MongoDB 8.0 in Action, Third Edition
A database role is a named set of permissions assigned to a user or other identity.
- How it is used
- Controls what authenticated users can do in Atlas organizations and projects or within MongoDB databases.
- How deep it goes
- Explains built-in and custom database roles, effective access from multiple roles, and Atlas CLI creation commands; defers exhaustive privilege listings.
- Examples
- Uses organization and project responsibilities, built-in database roles, and Atlas CLI commands granting collection-specific or inherited privileges.
- What you can do after
- Operate/configure it by selecting appropriately scoped roles and creating custom database roles with the Atlas CLI when built-in permissions are too broad.
Read how MongoDB 8.0 in Action, Third Edition explains role →
Kubernetes for Developers
A Kubernetes Role is a namespace-scoped object that defines permissions for API groups, resources, and verbs.
- How it is used
- Controls developer access within a namespace while preserving Pod Security guardrails and restricting namespace changes.
- How deep it goes
- Explains namespace scope, permission rules, bindings, and cluster-level counterparts through deployable YAML and command results.
- Examples
- Uses a team1 developer Role, user binding, deployment attempts, and forbidden namespace and cluster-resource operations.
- What you can do after
- Operate/configure namespace permissions with Role YAML, RoleBinding, and kubectl.
ScyllaDB in Action
A role is a database identity to which permissions can be assigned and through which users can receive those permissions.
- How it is used
- Structures ScyllaDB access for authenticated clients and separates application capabilities from superuser administration.
- How deep it goes
- Explains creation, permission grants, inheritance, login configuration, and driver authentication, but does not detail internal authorization implementation.
- Examples
- Uses application and reviews_api roles, reviews-keyspace SELECT and MODIFY grants, LIST ROLES output, and Python driver credentials.
- What you can do after
- Operate/configure ScyllaDB access by creating roles, granting scoped permissions, assigning inherited roles, and authenticating applications.
Building Web APIs with ASP.NET Core
A role is a named identity-group designation assigned to a user for evaluating the permissions and access the user has.
- How it is used
- Controls API permissions by grouping users and applying role-specific authorization rules to endpoints.
- How deep it goes
- Explains role creation, assignment, JWT claims, authorization attributes, seeding, and verification, stopping short of broader policy design.
- Examples
- Uses Moderator, Administrator, TestUser, TestModerator, TestAdministrator, SwaggerUI, and role-restricted test endpoints.
- What you can do after
- Configure and verify role-restricted ASP.NET Core API endpoints with seeded users, JWT role claims, and authorization attributes.
Read how Building Web APIs with ASP.NET Core explains role →
Software Security for Developers
A role is a named collection of permissions or access responsibilities assigned to a subject in an access-control system.
- How it is used
- Groups permissions by responsibility so authorization can decide access from assigned roles.
- How deep it goes
- Explains definitions, role inheritance, endpoint checks, role explosion, and distributed enforcement, but not implementation internals.
- Examples
- Uses employee, manager, and admin responsibilities, a JWT roles claim, and a Spring Security endpoint check.
- What you can do after
- Evaluate access designs by assigning responsibility-based roles and recognizing when attributes or relationships require another model.
The Well-Grounded Python Developer: How the pros use Python and Flask
An authorization role is a named grouping of permissions that determines which actions a user may perform.
- How it is used
- Controls what authenticated users can do and which application routes they may access.
- How deep it goes
- Defines three roles, their action boundaries, database relationships, enum values, startup initialization, and template exposure.
- Examples
- Uses administrator, editor, and registered-user roles with distinct content and user-management capabilities.
- What you can do after
- Configure roles in a Flask application and use them to protect pages and system-wide actions.
Read how The Well-Grounded Python Developer: How the pros use Python and Flask explains role →
Related concepts
- role-based access controlused by · Role-based access control is an authorization model that assigns permissions to roles and grants users or other principals access through their assigned roles.
- promptconfigures · An input, typically containing instructions or context, supplied to an artificial-intelligence model to guide or elicit its output.
- authorizationhas part · Authorization is the determination and enforcement of rules governing which subjects may access resources or perform operations.
- administratorincludes · An administrator is a user, account, role, or process granted elevated permissions to manage a system, application, or its resources and settings.
- ASP.NET Core Identityused by · ASP.NET Core Identity is an extensible ASP.NET Core membership system for managing user accounts, credentials, claims, roles, authentication, and related identity data.
- custom roleincludes · A custom role is a user-defined authorization role with an explicitly selected set of permissions or privileges.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.