Phone System User Permissions: Who Can Change What

Tom Reed · Updated 22 October 2026

On a small business phone system, keep admin rights to one or two named people, give supervisors only the controls their job needs, such as listening to or coaching calls, and leave everyone else as standard users. Put changes to call flows, numbers and outbound routes through a quick approval step, and review who has access every quarter.

That's the whole model. This guide turns it into something you can set up and run: a table of who can change what, a change approval checklist, a quarterly permission review and what to do when someone leaves. The roles here are generic job descriptions, not product settings. SessionPBX is used as the worked example, and its Teams Phone and Teams Business plans are SessionPBX plans, not Microsoft Teams.

Why do phone system permissions matter for a small business?

A phone system looks harmless until someone changes the wrong setting. Then it's the front door of your business that breaks. If you're new to how a hosted system is put together, our guides to the PBX phone system and the cloud-based phone system explain the parts this guide refers to.

Phone system permissions matter for three practical reasons.

Cost and fraud risk. Whoever can change outbound routes or SIP trunk settings can, in effect, decide where your calls go and who pays for them. A stolen admin login, or a well-meaning change to an outbound route, can run up charges on your carrier account. Fewer people with that power means fewer ways for it to go wrong. Our guide to VoIP toll fraud prevention covers the wider controls.

Broken call flows. The auto attendant, business-hours rules, ring groups and queues decide whether a customer reaches a person or a dead end. One edit to an opening-hours rule or a menu option can send every caller to voicemail. When several people can edit the call flow without telling anyone, nobody knows which change caused the problem.

Privacy of calls and recordings. Listening to live calls, coaching agents and playing back recordings all touch conversations your customers and staff expect to be handled carefully. Those controls belong with people who have a clear reason to use them and a written policy behind them.

There's also a quieter benefit. When user permissions are clear, changes get made by the right person, at a sensible time, and someone else knows they happened.

Permissions aren't about distrust. Most problems come from good intentions: a manager fixing a ring group before a busy morning, or a colleague updating a greeting without checking the menu still matches. A simple model protects those people as much as it protects the business.

Which tasks should only an admin do?

Start by listing the tasks on your phone system and deciding who should do each one. The table below is a starting point for most small businesses. "Admin", "supervisor" and "standard user" are generic descriptions of what people do, not role names in any particular product.

Who can change what

A few rules of thumb sit behind that table.

Keep admin rights to one or two named people. Name each phone system admin, not a job title. Two is usually right for a small business, so one can cover when the other is on holiday or off sick. More than that and it gets hard to know who changed what.

Separate "can do" from "should do alone". An admin may have the rights to edit the auto attendant, but the approval column says a second person should look first. The permission model and the approval step work together.

Treat SIP trunks and outbound routes as the most sensitive settings. They connect your phone system to your carrier, and your carrier bills you. Only admins should touch them, and every change should be agreed in advance.

Write it down. Keep the table, with real names in it, wherever you keep other IT records. A permission model that lives only in someone's head disappears when they leave.

Numbers and caller ID go together. Which number a person shows when they call out is part of your brand and part of your fraud protection. Our guide to outbound caller ID on a business phone system explains how to choose what each person or team displays. Keep the choice with admins so nobody can present a number your business doesn't use.

What should supervisors be allowed to do?

A supervisor sits between admin and standard user. They run a team's calls day to day, so they need some controls that standard users don't, but not the keys to the whole phone system.

Good supervisor permissions usually include:

• Live call supervision, where your plan offers it: listening to a call, whispering advice that only the colleague hears, and barging in to join the conversation when a customer needs help.
• Managing their own team's availability, such as who is taking queue calls and who is on a break, where your phone system supports it.
• Reviewing recordings for their own team, for coaching and quality checks, under a written policy.
• Requesting changes to call flows, ring groups and greetings, rather than making them directly.

Supervisors usually shouldn't add or remove users, buy or assign numbers, change caller ID, touch SIP trunks or change billing. Those tasks stay with admins, even when a supervisor is senior.

Live call supervision needs particular care. Before anyone can listen to or join calls, decide who is authorised, when they may use it, and how staff and callers are told. Our guide to call monitoring with whisper and barge covers how to use those controls well. If you record calls, our guide to softphone call recording compliance covers the notice and consent side. This guide doesn't give legal advice, so check the rules that apply to your business and take advice if you're unsure.

A useful test for any supervisor permission: could this person explain to a customer why they had it and how they used it? If not, it probably belongs with an admin or nobody.

How should you approve changes to call flows and routes?

Most phone system outages in a small business aren't technical failures. They're changes: a new menu option, a holiday rule, a ring group edit, a new outbound route. A light approval step catches most mistakes before callers see them.

This is process advice. You don't need special software for it; an email, a shared document or a ticket is enough. What matters is that a second person sees the change before it goes live and that you can undo it.

Change approval checklist

1. Draft the change. Write down what you want to change and why, such as "add a holiday message to the main number". If your phone system lets you save a call flow as a draft, build it there.
2. Get a second pair of eyes. Ask another admin, or the person who owns that line of business, to read the draft and check it against your call flow plan.
3. Schedule the change. Pick a quiet time, not the start of your busiest morning, and tell the people who answer calls that a change is coming.
4. Check before and after. Before publishing, check the flow for dead ends and missing destinations. After publishing, call the number from outside your office and follow each menu option to confirm it reaches the right place.
5. Keep a way to roll back. Note the previous setup, or keep the old flow, so you can put it back quickly if something goes wrong.
6. Record what changed. Add a line to your change notes: what changed, who approved it, when it went live and how it was checked.

The same steps apply to outbound routes and SIP trunk settings, with one addition: both people should confirm which carrier account the change affects. A wrong trunk setting can stop all external calls, or send them somewhere you didn't intend.

If you design call flows visually, our guide to visual call flow design for small businesses shows how to map the flow before you build it, which makes the review step much easier. A reviewer can check a drawing far faster than a list of settings.

Keep the approval step proportionate. A typo in a greeting doesn't need the same care as a change to outbound routes. Agree which changes need approval, list them, and let admins make everything else directly.

How do you run a quarterly permission review?

Permissions drift. People change jobs, cover for colleagues and get extra access "just for this week". A quarterly review puts things back in line. Set a recurring reminder, name an owner and work through the checklist.

Quarterly permission review

1. List everyone with admin rights. Compare the list with your permission table. Anyone who isn't a named admin should lose admin access.
2. Remove leavers and unused accounts. Check every user and seat against your staff list. Remove people who have left and accounts nobody uses.
3. Confirm who can access recordings and supervision. Check that only authorised supervisors have live call controls, and that recording access still matches your written policy.
4. Check outbound caller ID for each user. Make sure each person shows the number they should, and that no one presents a number your business doesn't use.
5. Confirm trunk credentials are changed only by admins. Ask whether anyone outside the admin list has seen or changed SIP trunk settings since the last review.
6. Check recent changes to call flows. Read your change notes and compare them with the live setup. Anything changed without a note is worth a conversation.
7. Record the review date and owner. Write down when the review happened, who did it and what you changed, so the next review has a starting point.

This review is specific to the phone system. It fits inside a wider access review of all your business software, which our guide to the user access review for small businesses covers. Run the phone system section at the same time so it doesn't get forgotten.

Run an extra review whenever something significant changes: a new admin, a restructure, a security incident or a change of carrier. The quarterly rhythm is a floor, not a ceiling.

For the wider security controls around your phone system, such as protecting remote users and softphones, use our cloud PBX security checklist alongside this review.

What happens to permissions when someone leaves?

When someone leaves, their phone system access should go on their last day, not at the next quarterly review. That means removing their user and seat, taking them out of ring groups and queues, and handing over anything they owned.

Leavers with admin or supervisor rights need extra care. Before they go, check whether they made recent changes to call flows or routes, update your permission table, and name who takes over their responsibilities. If they knew the SIP trunk credentials, ask your carrier how to change them and update the phone system afterwards.

Our phone system leaver checklist walks through the full process for one person, including voicemail, call history and numbers. This guide doesn't repeat it.

Managing users and permissions on SessionPBX

Here's how SessionPBX describes user administration on its own page. You "invite people by email and configure mobile apps with a QR code or desktop apps with a setup link", and you "manage extensions, seats and member permissions centrally". In practice, that gives your named admins one place to add, change and remove people and to keep user permissions in line with your table.

For outbound calls, you can "set each member's outbound caller ID from your connected numbers", which supports the caller ID check in the quarterly review.

On Teams Business, you can "give authorised supervisors listen, whisper and barge controls in the desktop app". For recording, the page says "an administrator chooses each member's recording mode: disabled, on demand or automatic", and recorded calls can be played back and downloaded from the call log in the portal.

The Teams Business visual call flow designer lets you "save changes as a draft, validate the flow and publish when it's ready." That fits the first and fourth steps of the checklist above. The second pair of eyes, the schedule and the change notes are your own process.

On security, the page says "your SIP trunk usernames and passwords are stored encrypted at rest with AES-256-GCM", and that "IP access controls and automated blocking help protect your phone system against repeated login attempts, suspicious traffic, and toll fraud." Those protections sit alongside your permission model; they don't replace it.

Not every question in this guide is answered on the hosted PBX page. For anything it doesn't cover, ask SessionTalk support and keep the reply with your records. The table and checklists above are process advice you run yourself.

SessionPBX is fully hosted and managed, with native apps for Windows, macOS, iOS and Android. Teams Phone covers "everyday calling, messaging, voicemail, team contacts and app provisioning, with SIP trunks for external calls." Teams Business adds ring groups, call queues, visual call flows, recording and supervision. Teams Phone and Teams Business are SessionPBX plans, not Microsoft Teams.

SessionPBX is bring-your-own SIP trunk: "external calls use your own SIP carrier, which bills you directly for numbers and calls." SessionPBX doesn't supply numbers or lines, so numbers in your permission table come from your carrier. Both plans include a 14-day free trial, with no setup fee or long-term contract. See the plans on the SessionPBX hosted PBX page.

FAQ

How many admins should a small business phone system have?

Usually two named people. That way one can cover holidays and sick days, and there's always someone to review the other's changes. More admins make it harder to keep track of who changed what.

Should managers be able to listen to calls?

Only authorised supervisors, with a clear written policy on when they may listen, whisper or barge and how staff and callers are told. Our guides to call monitoring with whisper and barge and to call recording compliance cover the details.

Who should be allowed to change the auto attendant?

Admins, through the approval step. Supervisors and team leads can suggest changes, but a named admin should make them after a second person has reviewed the draft.

How do permissions help prevent toll fraud?

When fewer people can change outbound routes and SIP trunk settings, there are fewer accounts an attacker can misuse and fewer chances for an accidental change. Pair tight phone system permissions with the controls in our toll fraud guide.

How often should I review phone system access?

Review user permissions quarterly, plus whenever someone leaves or changes role. Use the quarterly permission review checklist above and record the date and owner each time.