Jump to a topic
What you will learn
This chapter starts with the simplest meaning of each term, then connects it to a real support situation. Read the topics in order the first time. On later reviews, use the jump links and practice tasks.
Safety rule: protect people, data, and equipment before speed. Get permission before making changes and do not practise destructive procedures on an important device.
24.1 Standard Accounts
Standard Accounts controls who can sign in and what that person can do afterward. Good support work distinguishes authentication (proving identity) from authorization (what the identity is allowed to access).
Beginner picture: A building badge may prove who you are, but different doors still require different permissions. Computers use the same idea.
Support example
A user reports a problem connected to **Standard Accounts**. Instead of immediately replacing hardware or resetting settings, you first reproduce the problem, collect one useful piece of evidence, and choose the lowest-risk test. If the test changes the symptom, you have learned something even before the final fix. This is the same evidence-first method used throughout User Accounts and Permissions.
Technician steps
- Write down the exact symptom related to Standard Accounts; avoid replacing it with a guess.
- Check the simplest dependency first: power, connection, access, free space, or configuration.
- Change or test only one important variable at a time so you know what affected the result.
- Retest the original user task, not just the tool you used during diagnosis.
- Record what you observed, what you changed, and whether the issue returned.
Common mistakes
- Assuming the first symptom proves the cause of the Standard Accounts problem.
- Making several changes at once and losing track of which change mattered.
- Skipping backup, permission, safety, or user-consent checks.
- Stopping when the error disappears without confirming the user's original task.
Safe practice
On a spare device, virtual machine, demo account, or paper diagram, create a simple scenario involving Standard Accounts. Write the symptom, three possible causes, the safest first test, the evidence you expect to collect, and how you would confirm success. Do not practise destructive steps on a device containing important data.
24.2 Elevated Access
Elevated Access controls who can sign in and what that person can do afterward. Good support work distinguishes authentication (proving identity) from authorization (what the identity is allowed to access).
Beginner picture: A building badge may prove who you are, but different doors still require different permissions. Computers use the same idea.
Support example
A user reports a problem connected to **Elevated Access**. Instead of immediately replacing hardware or resetting settings, you first reproduce the problem, collect one useful piece of evidence, and choose the lowest-risk test. If the test changes the symptom, you have learned something even before the final fix. This is the same evidence-first method used throughout User Accounts and Permissions.
Technician steps
- Write down the exact symptom related to Elevated Access; avoid replacing it with a guess.
- Check the simplest dependency first: power, connection, access, free space, or configuration.
- Change or test only one important variable at a time so you know what affected the result.
- Retest the original user task, not just the tool you used during diagnosis.
- Record what you observed, what you changed, and whether the issue returned.
Common mistakes
- Assuming the first symptom proves the cause of the Elevated Access problem.
- Making several changes at once and losing track of which change mattered.
- Skipping backup, permission, safety, or user-consent checks.
- Stopping when the error disappears without confirming the user's original task.
Safe practice
On a spare device, virtual machine, demo account, or paper diagram, create a simple scenario involving Elevated Access. Write the symptom, three possible causes, the safest first test, the evidence you expect to collect, and how you would confirm success. Do not practise destructive steps on a device containing important data.
24.3 Groups and Roles
Groups and Roles controls who can sign in and what that person can do afterward. Good support work distinguishes authentication (proving identity) from authorization (what the identity is allowed to access).
Beginner picture: A building badge may prove who you are, but different doors still require different permissions. Computers use the same idea.
Support example
A user reports a problem connected to **Groups and Roles**. Instead of immediately replacing hardware or resetting settings, you first reproduce the problem, collect one useful piece of evidence, and choose the lowest-risk test. If the test changes the symptom, you have learned something even before the final fix. This is the same evidence-first method used throughout User Accounts and Permissions.
Technician steps
- Write down the exact symptom related to Groups and Roles; avoid replacing it with a guess.
- Check the simplest dependency first: power, connection, access, free space, or configuration.
- Change or test only one important variable at a time so you know what affected the result.
- Retest the original user task, not just the tool you used during diagnosis.
- Record what you observed, what you changed, and whether the issue returned.
Common mistakes
- Assuming the first symptom proves the cause of the Groups and Roles problem.
- Making several changes at once and losing track of which change mattered.
- Skipping backup, permission, safety, or user-consent checks.
- Stopping when the error disappears without confirming the user's original task.
Safe practice
On a spare device, virtual machine, demo account, or paper diagram, create a simple scenario involving Groups and Roles. Write the symptom, three possible causes, the safest first test, the evidence you expect to collect, and how you would confirm success. Do not practise destructive steps on a device containing important data.
24.4 Passwords
Passwords is a security responsibility as well as a technical task. The goal is to reduce risk without blocking legitimate work. A support technician verifies identity, limits access, protects evidence, and avoids making the incident worse.
Beginner picture: Treat digital access like access to a building: verify who is asking, give only the level of access needed, keep doors closed when they are not in use, and record unusual events.
Support example
A user reports a problem connected to **Passwords**. Instead of immediately replacing hardware or resetting settings, you first reproduce the problem, collect one useful piece of evidence, and choose the lowest-risk test. If the test changes the symptom, you have learned something even before the final fix. This is the same evidence-first method used throughout User Accounts and Permissions.
Technician steps
- Write down the exact symptom related to Passwords; avoid replacing it with a guess.
- Check the simplest dependency first: power, connection, access, free space, or configuration.
- Change or test only one important variable at a time so you know what affected the result.
- Retest the original user task, not just the tool you used during diagnosis.
- Record what you observed, what you changed, and whether the issue returned.
Common mistakes
- Assuming the first symptom proves the cause of the Passwords problem.
- Making several changes at once and losing track of which change mattered.
- Skipping backup, permission, safety, or user-consent checks.
- Stopping when the error disappears without confirming the user's original task.
Safe practice
On a spare device, virtual machine, demo account, or paper diagram, create a simple scenario involving Passwords. Write the symptom, three possible causes, the safest first test, the evidence you expect to collect, and how you would confirm success. Do not practise destructive steps on a device containing important data.
24.5 Account Lockouts
Account Lockouts controls who can sign in and what that person can do afterward. Good support work distinguishes authentication (proving identity) from authorization (what the identity is allowed to access).
Beginner picture: A building badge may prove who you are, but different doors still require different permissions. Computers use the same idea.
Support example
A user reports a problem connected to **Account Lockouts**. Instead of immediately replacing hardware or resetting settings, you first reproduce the problem, collect one useful piece of evidence, and choose the lowest-risk test. If the test changes the symptom, you have learned something even before the final fix. This is the same evidence-first method used throughout User Accounts and Permissions.
Technician steps
- Write down the exact symptom related to Account Lockouts; avoid replacing it with a guess.
- Check the simplest dependency first: power, connection, access, free space, or configuration.
- Change or test only one important variable at a time so you know what affected the result.
- Retest the original user task, not just the tool you used during diagnosis.
- Record what you observed, what you changed, and whether the issue returned.
Common mistakes
- Assuming the first symptom proves the cause of the Account Lockouts problem.
- Making several changes at once and losing track of which change mattered.
- Skipping backup, permission, safety, or user-consent checks.
- Stopping when the error disappears without confirming the user's original task.
Safe practice
On a spare device, virtual machine, demo account, or paper diagram, create a simple scenario involving Account Lockouts. Write the symptom, three possible causes, the safest first test, the evidence you expect to collect, and how you would confirm success. Do not practise destructive steps on a device containing important data.
24.6 File Permissions
File Permissions concerns where information is kept and how the operating system finds it. Storage problems can affect booting, application performance, saving files, updates, and backups, so the first rule is to protect important data before risky repair work.
Beginner picture: Imagine storage as a filing room. Capacity tells you how much can fit, while file systems and folders describe how the material is organized so it can be found again.
Support example
A user reports a problem connected to **File Permissions**. Instead of immediately replacing hardware or resetting settings, you first reproduce the problem, collect one useful piece of evidence, and choose the lowest-risk test. If the test changes the symptom, you have learned something even before the final fix. This is the same evidence-first method used throughout User Accounts and Permissions.
Technician steps
- Write down the exact symptom related to File Permissions; avoid replacing it with a guess.
- Check the simplest dependency first: power, connection, access, free space, or configuration.
- Change or test only one important variable at a time so you know what affected the result.
- Retest the original user task, not just the tool you used during diagnosis.
- Record what you observed, what you changed, and whether the issue returned.
Common mistakes
- Assuming the first symptom proves the cause of the File Permissions problem.
- Making several changes at once and losing track of which change mattered.
- Skipping backup, permission, safety, or user-consent checks.
- Stopping when the error disappears without confirming the user's original task.
Safe practice
On a spare device, virtual machine, demo account, or paper diagram, create a simple scenario involving File Permissions. Write the symptom, three possible causes, the safest first test, the evidence you expect to collect, and how you would confirm success. Do not practise destructive steps on a device containing important data.
24.7 Shared Resource Permissions
Shared Resource Permissions controls who can sign in and what that person can do afterward. Good support work distinguishes authentication (proving identity) from authorization (what the identity is allowed to access).
Beginner picture: A building badge may prove who you are, but different doors still require different permissions. Computers use the same idea.
Support example
A user reports a problem connected to **Shared Resource Permissions**. Instead of immediately replacing hardware or resetting settings, you first reproduce the problem, collect one useful piece of evidence, and choose the lowest-risk test. If the test changes the symptom, you have learned something even before the final fix. This is the same evidence-first method used throughout User Accounts and Permissions.
Technician steps
- Write down the exact symptom related to Shared Resource Permissions; avoid replacing it with a guess.
- Check the simplest dependency first: power, connection, access, free space, or configuration.
- Change or test only one important variable at a time so you know what affected the result.
- Retest the original user task, not just the tool you used during diagnosis.
- Record what you observed, what you changed, and whether the issue returned.
Common mistakes
- Assuming the first symptom proves the cause of the Shared Resource Permissions problem.
- Making several changes at once and losing track of which change mattered.
- Skipping backup, permission, safety, or user-consent checks.
- Stopping when the error disappears without confirming the user's original task.
Safe practice
On a spare device, virtual machine, demo account, or paper diagram, create a simple scenario involving Shared Resource Permissions. Write the symptom, three possible causes, the safest first test, the evidence you expect to collect, and how you would confirm success. Do not practise destructive steps on a device containing important data.
24.8 Least Privilege
Least Privilege controls who can sign in and what that person can do afterward. Good support work distinguishes authentication (proving identity) from authorization (what the identity is allowed to access).
Beginner picture: A building badge may prove who you are, but different doors still require different permissions. Computers use the same idea.
Support example
A user reports a problem connected to **Least Privilege**. Instead of immediately replacing hardware or resetting settings, you first reproduce the problem, collect one useful piece of evidence, and choose the lowest-risk test. If the test changes the symptom, you have learned something even before the final fix. This is the same evidence-first method used throughout User Accounts and Permissions.
Technician steps
- Write down the exact symptom related to Least Privilege; avoid replacing it with a guess.
- Check the simplest dependency first: power, connection, access, free space, or configuration.
- Change or test only one important variable at a time so you know what affected the result.
- Retest the original user task, not just the tool you used during diagnosis.
- Record what you observed, what you changed, and whether the issue returned.
Common mistakes
- Assuming the first symptom proves the cause of the Least Privilege problem.
- Making several changes at once and losing track of which change mattered.
- Skipping backup, permission, safety, or user-consent checks.
- Stopping when the error disappears without confirming the user's original task.
Safe practice
On a spare device, virtual machine, demo account, or paper diagram, create a simple scenario involving Least Privilege. Write the symptom, three possible causes, the safest first test, the evidence you expect to collect, and how you would confirm success. Do not practise destructive steps on a device containing important data.
Chapter practice lab
Create a one-page troubleshooting worksheet for User Accounts and Permissions. Include the user complaint, environment, five possible causes, your safest first test, expected evidence, final verification, and ticket note.
15 Review Questions & Answers
1. What is the main purpose of Standard Accounts?
Its purpose is to help the technician understand, configure, protect, or troubleshoot that part of the system in a controlled way.
2. Why should a beginner learn Elevated Access?
Because many user symptoms depend on it, and understanding the basic role makes troubleshooting faster and safer.
3. What should you check before changing Groups and Roles?
Record the symptom, protect important data, confirm authorization, and check the simplest dependency first.
4. What is a common mistake when troubleshooting Passwords?
A common mistake is changing several things at once or assuming the symptom proves the cause.
5. How do you confirm a fix involving Account Lockouts?
Repeat the user's original task, check that the symptom is gone, and make sure the change did not create another problem.
6. What is the main purpose of File Permissions?
Its purpose is to help the technician understand, configure, protect, or troubleshoot that part of the system in a controlled way.
7. Why should a beginner learn Shared Resource Permissions?
Because many user symptoms depend on it, and understanding the basic role makes troubleshooting faster and safer.
8. What should you check before changing Least Privilege?
Record the symptom, protect important data, confirm authorization, and check the simplest dependency first.
9. What is a common mistake when troubleshooting Standard Accounts?
A common mistake is changing several things at once or assuming the symptom proves the cause.
10. How do you confirm a fix involving Elevated Access?
Repeat the user's original task, check that the symptom is gone, and make sure the change did not create another problem.
11. What is the main purpose of Groups and Roles?
Its purpose is to help the technician understand, configure, protect, or troubleshoot that part of the system in a controlled way.
12. Why should a beginner learn Passwords?
Because many user symptoms depend on it, and understanding the basic role makes troubleshooting faster and safer.
13. What should you check before changing Account Lockouts?
Record the symptom, protect important data, confirm authorization, and check the simplest dependency first.
14. What is a common mistake when troubleshooting File Permissions?
A common mistake is changing several things at once or assuming the symptom proves the cause.
15. How do you confirm a fix involving Shared Resource Permissions?
Repeat the user's original task, check that the symptom is gone, and make sure the change did not create another problem.