Glossary
Authorisation
Definition
Authorisation determines which information and actions an account is allowed to access.
Authentication verifies an identity. Authorisation decides which records, features and actions that identity may access.
A customer may include “Authorisation” in a supplier security questionnaire or spreadsheet. They want to understand whether this topic affects the service you provide and what safeguards or evidence support your answer.
Authorisation sets the boundaries of an account's access. It decides whether an employee can open a customer record, approve a payment, export a database or change a security setting. These decisions may depend on a role, a specific permission or conditions attached to the request.
It follows a different purpose from authentication. Authentication checks the identity behind a request; authorisation determines what that identity may do. Giving everyone a secure sign-in does not fix permissions that expose the whole company payroll.
In a hypothetical recruitment agency, a consultant can update their candidates' records while only the finance team can change billing details. The application must enforce those permissions whenever information is requested. Hiding a button on a screen is insufficient if the underlying action remains available.
Permissions can become excessive as people change jobs or receive temporary responsibilities. Review group membership, inherited roles and individual exceptions against each person's current work. Assign an application owner to approve new access and remove it when it is no longer needed; an employee account is not automatically appropriately restricted.