What one sign-in saves: a joiners and leavers checklist
Kazee team · · 6 min read
Someone joins your business on Monday. By Friday they are still waiting for two logins, and they are borrowing a colleague's password for a third. Six months later someone else leaves. You remember to close their email, but a year on their login still works in a tool nobody thought to check.
In many small businesses in Kenya, access grows one app at a time, and nobody keeps the full list. One sign-in across your apps can shrink the problem, though it will not remove it. This guide explains what shared sign-in really saves, what it leaves for you to do, and gives you a checklist you can use whichever tools you have.
What one sign-in means
Single sign-on means that one account and its credentials give access to several applications. Your staff have one work account, not a separate username and password for each app.
What it saves
- Fewer passwords. People have fewer to remember and fewer reasons to write them down or reuse them.
- Less setup for each joiner. You create one account, then give access to what the job needs, rather than opening accounts app by app.
- A shorter list to check when someone leaves. The UK's National Cyber Security Centre says single sign-on can help you revoke access along with someone's work account when they leave.
- One place to look. You can answer "who has access?" without opening every app in turn.
What it does not save
- Tools outside the shared sign-in. Your bank portal, domain registrar, SMS provider and social media pages probably have their own logins.
- Shared logins. If four people use one password for the supplier portal, closing one person's work account does nothing. Change the password.
- Open sessions and phones. Blocking an account does not always end access straight away. Microsoft's own guide says that blocking an account can take up to 24 hours to take effect, and advises a password reset to stop sign-in immediately. Google's guide for departing staff lists separate steps, such as wiping mobile devices and resetting sign-in cookies. Every system differs, so ask your own supplier how theirs behaves.
- Personal accounts. A work group on someone's own phone, or files in their personal cloud storage, sit outside any company sign-in.
First, write the access list
The checklist below depends on one page that many businesses do not have. Make a simple table with a row for every tool the business uses, and these columns:
- The tool, including any on someone's personal card.
- Who is the admin. There should be at least two, so that one departure cannot lock you out.
- How people sign in. Shared sign-in, own login, or a shared password.
- Who has access, or where to look to find out.
- How to remove someone, in one line.
Give the list an owner, usually HR or operations, and check it every few months. The NCSC advises every organisation to have a joiners, movers and leavers policy, so access can be revoked when it is no longer needed.
Joiners checklist
Start this before the first day.
- Get the request from the manager. Ask what the role needs, not what the last person had.
- Create one work account. Each person gets their own, and nobody starts on a borrowed login.
- Give only what the job needs. Add more when a real need appears.
- Set up two-step sign-in wherever a tool offers it, starting with email and banking.
- Record any equipment. Note the laptop, phone, keys or card, with serial numbers where you can.
- Add them to the work groups they need, and note which ones.
- Walk through it on day one. Check they can actually open each tool.
Movers checklist
Movers are easy to forget. Someone moves from sales to accounts and keeps both sets of access.
- Add the new access the new role needs.
- Remove the old access on the same day, unless a handover needs it for a set time. If so, write down the end date.
- Check admin rights. Someone who was an admin in the old role may no longer need to be.
Leavers checklist
The US cyber security agency CISA advises a defined process for departures that covers contractors and vendors as well as staff and revokes all access to systems and facilities.
Before the last day
- Tell whoever owns the access list, as soon as the departure is agreed. For a sudden or difficult exit, close access first and hold the conversation straight after.
- Hand over the work. Give open tickets, deals, tasks and customer conversations a new owner.
- Move shared files out of personal folders and into a team location.
- Check who else depends on their email or phone number, such as password resets, supplier accounts and customer contact details.
- Find anything they are the only admin of, and add a second admin.
On the last day
- Close the work account, and confirm it no longer opens each app that relies on it.
- Go down the access list and remove them from every tool outside the shared sign-in.
- Change shared passwords and door codes they knew.
- Collect equipment, keys and cards, and tick them off against your record.
- Remove them from work groups, including any chat groups on personal phones.
In the week after
- Deal with their mailbox. Decide who reads it, for how long, and what senders are told.
- Sign out or wipe work phones and laptops before you hand them to anyone else.
- Review what you keep. Under Kenya's Data Protection Act, personal data should be kept no longer than necessary, and that includes the leaver's own records. Ask your adviser if you are unsure.
- Update the access list.
Test it once
Create a test person, give them the access a normal employee has, then remove them using your own process. Try each tool from a phone and a laptop where they were signed in. Note how long access lasts and what still works.
Where Kazee fits
Kazee's core apps share Kazee sign-in and organisation access through Kazee Central. That covers Kazee People, Chat, Spaces, CRM and Desk, all of them Live. You add your people in Central and manage their roles there, so you can see who has access without checking a separate account in each app. In People, an onboarding checklist helps with joiners, staff can see the equipment assigned to them under Assets, and the audit logs record who did what and when.
It will not do all of this for you. Shared sign-in covers Kazee's own core apps, so your bank, domain, SMS provider and other outside tools stay on your list. Meeting guests in Chat do not need a Kazee account, so hosts manage them separately. Desk departments and Spaces memberships also decide what a person can see, so check those when someone moves. There is no import of a full staff list from a file, because people are added through Central. And the list above stays your own job, because no app can collect a laptop or change a door code.
Whichever tools you use, the habit is the same: keep one list, and work through it every time someone joins, moves or leaves. If you would like to run a test person through Kazee Central and see what happens in each app, book a demo and we will do it with you.
Sources
- NIST Computer Security Resource Center glossary, Single sign-on (from NIST SP 800-63-4)
- National Cyber Security Centre (UK), 10 Steps to Cyber Security: Identity and access management (11 May 2021)
- CISA, Cybersecurity Performance Goals 2.0: revoking credentials for departing staff
- Microsoft Learn, Remove a former employee, step 1: prevent sign-in
- Google Workspace Help, Maintain data security after an employee leaves
- DLA Piper, Data Protection Laws of the World: Kenya, security and data principles (last modified 23 March 2026)