Permission
A permission is an authorization specifying whether an actor 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.
Also covered in
- GitHub Actions in Action: Continuous integration and delivery for DevOps
- Architecting Autonomous Agentic SystemsIn early access (MEAP)
- Azure Security
- Django in Action
- Building Reliable AI Systems
- Snowflake Data Engineering
- Practical Automation with PowerShell: Effective scripting from the console to the cloud
- Web Design Playground, Second Edition
- The Well-Grounded Python Developer: How the pros use Python and Flask
- Spring Microservices in Action
- Modern Angular
What to know first
- AI agentAn AI agent is a computational system that uses artificial intelligence to interpret information and select or perform actions toward goals while interacting with an environment.
- web applicationA web application is software that provides functionality through web technologies and is accessed over a network, typically through a browser or other web client.
- credentialA credential is information or an artifact presented to verify an entity’s identity or establish its authorization to access a system or resource.
- authenticationAuthentication is the process of verifying the claimed identity of a user, service, device, or other entity.
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 permissions necessary for its authorized tasks.
- control server permissionincludes · The CONTROL SERVER permission is a SQL Server permission that grants control over the SQL Server instance.
- impersonate permissionincludes · An impersonate permission allows a principal to execute under the security context of another database or server security principal.
- authorizationused by · Authorization is the determination of which actions or resources an identity or other entity is permitted to access under defined permissions or policies.
Questions about permission
What is permission?
A permission is an authorization specifying whether an actor may perform an action on or access a resource.
Which Manning books explain permission?
Building Web APIs with ASP.NET Core, .NET MAUI in Action, Grokking Web Application Security and ScyllaDB in Action.
What should I know before learning permission?
Manning books that teach permission usually introduce AI agent, web application, credential and authentication first.
What kinds of permission are there?
Kinds of permission include control server permission, impersonate permission and reproduction permission.
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.



