Permission
A permission is an authorization specifying whether an identity or process may perform an action on or access a resource.
Building Web APIs with ASP.NET Core
A permission is an authorization grant allowing a user or role to perform a specified operation on a resource.
- How it is used
- Controls which authenticated users or roles may perform actions on web API resources.
- How deep it goes
- Defines permissions through ACLs and outlines steps for assigning role-based rules; stops short of showing complete code in the supplied evidence.
- Examples
- Uses read, update, delete, and database-seeding endpoints to distinguish ordinary users, moderators, and administrators.
- What you can do after
- Apply it via ASP.NET Core roles, JWT role claims, and [Authorize] requirements to restrict API actions.
Read how Building Web APIs with ASP.NET Core explains permission →
.NET MAUI in Action
A permission is an authorization that an operating system requires an application to obtain before accessing a protected capability or resource.
- How it is used
- Gates access to privacy-sensitive device features such as location in .NET MAUI applications.
- How deep it goes
- Explains declaration, runtime checking, and consent requests, but does not detail each platform’s complete permission model.
- Examples
- Uses location access, the FindMe! app scenario, and a Windows Package.appxmanifest capability declaration.
- What you can do after
- Operate/configure a .NET MAUI app to declare location access and request or verify user consent at runtime.
Grokking Web Application Security
A permission is an authorization that allows a software component, process, or user to perform a specified action or access a specified resource.
- How it is used
- Applies least privilege to web servers, databases, browser code, organizational roles, and uploaded files.
- How deep it goes
- Explains permission design through practical restrictions and upload file-mode examples, without defining operating-system permission internals.
- Examples
- Uses airport access roles, limited database accounts, nonroot servers, timed privileges, and executable uploaded-file scenarios.
- What you can do after
- Apply least-privilege restrictions to processes, accounts, roles, and uploaded files to limit breach damage.
Read how Grokking Web Application Security explains permission →
ScyllaDB in Action
A database permission is an authorization grant allowing a role to perform specified operations on database resources.
- How it is used
- Limits database access by granting roles specific actions on resources.
- How deep it goes
- Explains permission types, resource scope, role inheritance, grant commands, and authorization enforcement modes.
- Examples
- Uses reviews roles with SELECT and MODIFY grants, inherited permissions, and LIST ALL verification.
- What you can do after
- Operate/configure ScyllaDB access by creating roles, granting scoped permissions, assigning inherited roles, and verifying effective permissions.
Related concepts
- principle of least privilegeconfigured by · The principle of least privilege is a security principle that grants each user, process, or other subject only the access rights necessary for its authorized tasks.
- 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.
- metadatapart of · Metadata is information that describes, identifies, or provides context about other data, resources, or artifacts.
- authorizationused by · Authorization is the determination and enforcement of rules governing which subjects may access resources or perform operations.
- applicationconfigures · An application is a software program or system that performs tasks or provides functionality for users or other software systems.
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.