Reading room / Boundaries
Permission to read, change or run
Recognizing an account and allowing an action are separate decisions. Authentication establishes identity. Authorization determines what that identity may do with a particular resource.
General educational information
Actions have different consequences
Read permission can allow someone to inspect a file. Write permission can allow changes. Execute permission can allow a program to run. Exact meanings depend on the system and resource type. Being able to see a filename does not necessarily mean being able to open or modify its contents.
A hypothetical example
Imagine a shared reference document. A reviewer needs to read it, while an editor needs to change it. Giving both accounts the same broad access would make an unnecessary change possible. The example below separates three actions; it does not inspect your device or change any real permissions.
Permissions can accumulate
Access may come from an individual account, a group or inherited settings on a containing folder. Ownership and explicit rules can also affect the result. To understand an access decision, consider the effective combination rather than looking at a single visible setting.
Match access to purpose
The principle of least privilege means granting the access needed for a task. Needs can change, so a useful permission is not necessarily a permanent permission. If someone cannot complete an authorized task, identify the required action and resource before widening access. A narrowly understood rule is easier to assess than an unexplained grant of unrestricted control.
Further reading: Microsoft: access control overview.