Your new accounts assistant signs in using her own account. You want her to read incoming invoices and prepare drafts. But the service also lets her invite an administrator, an account able to manage other people or important settings. She has not pretended to be somebody else. Her login can be genuine while the permission she received is wrong.
This matters because business software must answer two separate questions. First: what identity is making the request, and has that identity been properly established? Checking this is called authentication. Second: may that identity perform this particular action? Deciding this is called authorization. You do not need to memorize the similar names. Keep the different questions in view: “Who is asking?” and “May they do this?” 2 5
What happens after the login screen?
A browser is the program you use to open websites. When the assistant opens the invoice service, her browser obtains pages and sends information to the provider’s receiving software. That software runs on computers commonly called servers. The browser shows the screen; the receiving service decides whether to supply data or carry out the requested work. 13
At login, the assistant presents the required evidence for her account, such as a password and a second confirmation. If the service accepts it, it establishes a signed-in session: a continuing interaction in which subsequent requests can be associated with the account.
For example, the service can give the browser a value to retain and include with later requests. The service uses it to connect those requests with the signed-in session. A value stored and returned this way can be a cookie. It is not the assistant’s invoice permission: the service still checks what the recognized account may do. This explains why the password need not be typed again for every invoice. The service still needs to protect the ways people sign in and recover accounts. 2 13
Now the assistant clicks an invoice. Her browser asks the receiving service for information about that invoice. The service needs to decide whether her account may read it before returning the permitted information. Later, a request to invite an administrator needs a different permission decision. Successfully recognizing the account is the starting point, not a decision to accept every later request. 1 5
An identity card gives a helpful comparison. It can establish that an employee is the person on the card, but it does not assign the employee authority to sign every contract. In software, the assignment comes from permissions chosen for the work and enforced when the service acts on requests. The card comparison alone cannot tell us whether those checks were implemented correctly.
Begin with the job, then describe the rights
For the assistant, the instruction might be: “Read our incoming invoices and prepare drafts; do not invite users or change account ownership.” Another person might approve documents. An account administrator might manage access. These are examples of dividing work, not a requirement that a small business employ three separate people. One owner can intentionally perform several roles.
A role is often a named collection of permissions, such as a reader or administrator. Its name is not the full explanation. Two services may give a role called “accountant” different powers. Ask what that role actually permits, rather than assuming the familiar name matches your intention. Function-level authorization concerns whether the requester may use the operation itself. 5
That is why hiding a button is insufficient. The screen may omit “Invite administrator” for the assistant, which helps avoid accidental use. But the request is ultimately handled by the receiving software. If that software would accept the operation from the assistant anyway, the screen has hidden an opportunity without enforcing the rule. The permission must be enforced where the action is carried out. This is an explanation, not an invitation to send altered requests to a live service. 5
There are also more specific questions. Permission to download invoices does not mean permission to download every company’s invoices. The service must check which record is requested and the relationship between that record and the requester. Our assistant may read the bakery’s invoice; an external accountant may be deliberately authorized for several businesses. Both arrangements can be correct. 1
Even a permitted invoice can contain restricted details. Suppose the assistant needs the total and processing status, while an internal dispute note is reserved for management. Or she may edit a draft’s description but not a protected payment field. A field means one item of information within a record. The service must distinguish access to the record from rights to read or change its individual fields. 3
Stronger recognition cannot repair excessive rights
A second login factor adds another kind of evidence beyond the password, for example confirmation in an authentication app. It helps protect the identity check. But when the genuine assistant signs in successfully, that extra check does not remove her unwanted administrator permission. Better login protection and correct rights are complementary measures, not replacements for one another. 2 5
Programs also make requests. Your accounting package may submit invoices automatically without a person currently using the provider’s website. The agreed way for programs to exchange requests and responses is an API. The provider can recognize the software connection separately from a human account; an API key is one possible configured value for recognizing a software client. It should not be used as evidence of an individual employee’s identity. 2
The same work-based principle applies: a sending connection can be allowed to submit this company’s invoices without being allowed to manage staff accounts. A history entry naming that connection records machine activity. Whether a human approved the invoice needs the relevant approval record, not an assumption drawn from automatic sending.
Permissions should change when responsibilities change
Suppose the assistant becomes a reviewer, or the external accountant finishes working for the bakery. Their intended rights change. Updating a job title in your own paperwork does not necessarily update the service. Ask how the changed permission is applied to existing signed-in sessions and automatic connections, not only to the next newly created account.
A practical discussion can begin without testing anything. Choose one sensitive activity, such as inviting administrators. Decide who needs it, then compare that decision with documented settings together with your access administrator. If the settings do not match the job, resolve the mismatch through the service’s normal management process.
If a demonstration is needed, request a separate, expressly authorized test environment with invented documents and temporary accounts. The assistant’s test account should be able to perform the permitted task and be refused the prohibited one. The authorized team should then check whether any unwanted account, document change or waiting task was created despite the refusal. No live-account bypass attempts or real invoices are needed.
A good explanation leaves you with more than “everyone has their own login”. You understand what each account is recognized as, what work it may do, and which information that work includes. Those are ordinary business decisions that software must reliably carry out.
Sources
2 — OWASP API2:2023 Broken Authentication
5 — OWASP API5:2023 Broken Function Level Authorization
13 — MDN: Overview of HTTP — client/server requests, responses and sessions
1 — OWASP API1:2023 Broken Object Level Authorization
3 — OWASP API3:2023 Broken Object Property Level Authorization