Week 6 · Friday
Adding and removing employee access
Give each person the access their job requires, review it when responsibilities change, and remove access without losing the business records you need.
A new employee needs to answer customers, check appointments, and send estimates. The quickest solution seems to be giving them the owner's login.
A few months later, their responsibilities change. Eventually, they leave. By then, nobody is quite sure which applications they could reach or which account owns the files they created.
A small amount of planning at the start makes every later step easier.
This week's lessons covered device maintenance and safer ways to work from different locations. Today, we will connect those protections to the people using them: what access they receive, how it changes, and how it ends.
Give the person what the job requires
An account identifies someone to a service. Permissions determine what that account can do, such as viewing appointments, changing prices, exporting customer details, or adding other users.
Least privilege means providing the access required for the job, for as long as it is needed. Microsoft's small-business security guidance uses this principle to limit unnecessary access. Microsoft: Zero Trust guidance for small businesses.
You can apply the idea without adopting a new platform or learning the rest of that terminology. Start with the work.
Here is an illustrative starting point for a service business:
| Role | Access to consider | Access requiring a separate reason |
|---|---|---|
| Front-desk employee | Appointments and the customer details needed to arrange service. | Payroll, account administration, or exporting the entire customer list. |
| Field technician | Assigned jobs, relevant contact details, and the tools needed to complete them. | Unrelated employee records or every customer's files. |
| Bookkeeper | Approved accounting records and invoicing functions. | Managing all business technology accounts. |
Your actual permissions will depend on your applications and responsibilities. A small company may combine several roles, but the owner should still be able to explain why each permission is needed.
Use individual accounts where the service supports them
Give each person their own work account. This helps you change one person's access without changing everyone else's and makes available activity records more useful.
A shared email address such as inquiries@yourbusiness.com can still be handled by several authorized people through delegated access or a shared mailbox. They do not necessarily need to share the mailbox's password. Ask the provider which arrangement it supports.
If an application only offers a shared login, record that limitation. Decide who may use it, store the credential in the business's controlled password manager, and document how you will change it when access changes. Consider better account controls when evaluating a replacement.
An administrator can make powerful changes, often including adding users or changing security settings. Avoid making every employee an administrator for convenience. Where practical, use a separate account for administrative work and a standard account for everyday tasks.
The business also needs an authorized recovery path if its main administrator is unavailable. Do not make that path depend entirely on a departing employee's personal phone or email address.
Make the first day repeatable
Create a short setup record for each employee or contractor. Include the start date, the person approving access, the applications needed, and the person responsible for setting them up.
Before the person begins work:
- Create the individual accounts and assign the approved permissions.
- Set up MFA, the additional sign-in verification covered earlier in the series, where available.
- Provide the approved device or confirm the agreed rules for a personal device.
- Show the person where business records belong and how to report a suspicious request or missing device.
- Confirm they can perform the required task without borrowing somebody else's login.
NIST's small-business guide recommends limiting sensitive information to the people who need it, enabling MFA, and removing access that is no longer needed. NIST: Small Business Quick-Start Guide.
Keep passwords and recovery codes out of the setup checklist. Record where authorized people manage those secrets instead.
A role change deserves an access change
Someone moving from bookkeeping to scheduling may need new permissions. Their old permissions deserve a review at the same time.
Simply adding each new role's access can leave a person with years of unrelated permissions. Review what they still need, remove what they no longer need, and record who approved the change.
Apply the same habit to temporary projects and outside providers. If a web developer needs access for a particular job, agree on the purpose, responsible owner, and end or review date before granting it.
Put a short access review on your calendar. The right frequency depends on how often your team and systems change. At minimum, use hiring, role changes, project completion, and departures as clear triggers.
Plan a departure as two coordinated jobs
When someone leaves, the business needs to stop their access and keep the records needed to continue serving customers.
Choose who coordinates the departure and exactly when access should end. Prepare the handover in advance where appropriate. If someone must lose access immediately, do not leave them signed in while you work out how to organize their files.
Ask the administrator to handle the service's complete access-removal process. Sessions are existing signed-in connections. Connected apps may have been granted their own permission to use an account. Changing a password alone does not necessarily remove all of these routes.
Google Workspace's departure guidance includes reviewing connected applications, sign-in cookies, recovery methods, security keys, and app-specific passwords. The exact controls vary by service. Google Workspace: Maintain data security after an employee leaves.
At the same time, identify the business files, customer conversations, shared calendars, and other records another authorized person will need. Transfer ownership or arrange retention through the service's supported process before deleting accounts or canceling licenses.
Microsoft's offboarding guidance treats blocking access, preserving information, handing over work, and removing accounts or licenses as distinct tasks. That is a useful reminder to confirm the sequence with your provider. Microsoft: Remove a former employee and secure data.
Include the accounts outside your main email service: booking, payroll, social pages, the website, file sharing, password-manager access, and remote-support tools. Recover company equipment and review any shared secrets the person knew. Follow your agreed process for business information on personal devices, with clear boundaries around personal data.
Finally, confirm completion in the administrator tools. A returned laptop is useful, but it does not prove that cloud access has ended.
A twenty-minute access exercise
Choose one role in your business and make a simple record with these fields:
| Field | What to record |
|---|---|
| Business task | What the person needs to accomplish. |
| Accounts and permissions | The services and level of access required. |
| Approver and administrator | Who authorizes access and who changes it. |
| Business records | Where work is saved and who should retain it after a handover. |
| Change or end trigger | A new role, a project finish date, or the departure time. |
| Completion check | How the administrator confirms the change took effect. |
Walk through a fictional departure without changing a real employee's access. Identify what you would need to do and which systems you could easily overlook.
For a solo owner, use an outside bookkeeper, web provider, or other contractor as the example.
Your takeaway: Give access deliberately, review it when work changes, and remove it through a documented process that preserves the business's records.
Test your knowledge
You have now covered supported devices, safer working connections, and employee access.
Visit the EdwardsCG Week 6 Knowledge Check to try eight questions about this week's lessons. You can also choose an 18-question cumulative review covering one question from each article in Weeks 1 through 6.
Each answer includes an explanation and related reading. The check opens after Friday's article and the other two lessons are verified live.
Next week, we will look at saving, syncing, backups, and recovery. Follow the Small Business Learning Series.