# Client Access Setup Checklist

Plan exactly what system access a new support team needs, and at what permission level — before the first account is created.

Provided free by VoiceSupportCrew.

---

## Part 1 — Systems inventory

List every system agents might need to touch. Not every system on this list needs agent access — that is decided in Part 2.

| System | Needed for this campaign? | Owner on your side |
|---|---|---|
| CRM | | |
| Helpdesk | | |
| Phone system | | |
| Chat platform | | |
| Ecommerce platform | | |
| Internal wiki / knowledge base | | |
| Scheduling / calendar tool | | |
| Payment system | | |
| Other: ____________ | | |

---

## Part 2 — Least-privilege scoping

For each system marked "yes" above, define the minimum permission level that actually does the job.

- [ ] Does the agent need to **view** records, **edit** them, or both?
- [ ] Does the agent need **create** permissions, or only work with existing records?
- [ ] Does the agent need **delete** permissions? (Default: no, unless specifically required)
- [ ] Does the agent need **export** permissions? (Default: no)
- [ ] Does the agent need **admin/user-management** permissions? (Default: no)
- [ ] Is there a pre-built "support" or "agent" role in this system you can assign instead of custom permissions?

---

## Part 3 — Account setup

- [ ] Individual named account per agent (not a shared login)
- [ ] Strong, unique password set at creation
- [ ] Multi-factor authentication enabled, if the platform supports it
- [ ] Access tested by logging in as the agent account, not as an admin
- [ ] VPN or IP allowlisting configured, if required

## Part 4 — Credential handling

- [ ] Credentials shared through a secure channel, never plain email or chat
- [ ] Password manager used where practical
- [ ] No credential sharing between agents

## Part 5 — Access logging

- [ ] Confirm whether the platform logs user activity
- [ ] If yes, confirm who reviews those logs and how often
- [ ] If no, note this as a limitation to be aware of

## Part 6 — Offboarding plan

Decide this now, before you need it urgently.

- [ ] Who is responsible for disabling an account when an agent leaves the campaign?
- [ ] How quickly does this need to happen? (Recommended: same day)
- [ ] Is the password also changed, in addition to disabling the account?
- [ ] Is there a process for confirming revocation actually happened?

---

## The principle behind this checklist

Access should be scoped to what the specific task requires — not granted broadly because it's easier to set up once. A support agent almost never needs admin rights, export permissions or the ability to delete records. If a system only offers all-or-nothing access, that is worth knowing before go-live, not discovering afterwards.

---

*More free templates and guides: voicesupportcrew.com/downloads*