Restricted meetings: only the people in the call can see it

Most calls at an insurance agency are fine to share. A renewal review, a carrier update or a team stand-up is useful to anyone who might pick up the work later. Some calls are not like that. A sensitive client situation or an internal personnel matter belongs to the people who were in the room.

The new Restricted flag is built for those calls. When a meeting is marked Restricted, it is visible only to:

the host
the attendees
the invitees
platform admins

Everyone else on the team does not see it. The rest of this post covers what that means in practice, how to set the flag in Quill Meet, and how to confirm it took effect.

What the Restricted flag does

Restricted is a visibility setting on a single meeting. It narrows who can see that call to the people connected to it, plus the admins who run the platform.

That list is deliberately short:

Host: the person who set up and ran the call.
Attendees: the people who actually joined.
Invitees: the people who were invited, whether or not they joined.
Platform admins: the people responsible for administering the platform.

If you weren't part of the call and you aren't an admin, a Restricted meeting is not visible to you.

Restricted is a per-meeting choice. You don't have to change how your whole team shares calls. You flag the conversations that need it and leave everything else as it is.

When to use it

The flag is a practical privacy tool, not a blanket policy. A few examples of the kind of conversation it suits:

A delicate client conversation. A client is going through something difficult and wants to talk it through with their producer and an account manager. The call is useful to those people. It doesn't need to be visible to the rest of the agency.
An internal people matter. A manager and a team member are discussing something personal or performance-related. That conversation should stay between them.
An early-stage internal discussion. Leadership is working through a sensitive decision and isn't ready to share it more widely.

In each case, the people who need the call can still see it. The people who don't need it never come across it.

A simple test: if you would close the office door for this conversation, mark the call Restricted.

How to set it in Quill Meet

You can mark a meeting Restricted in Quill Meet before the call is recorded or after it has been recorded.

Before recording

If you know ahead of time that a conversation is sensitive, set the flag when you set up the meeting. That way the call is Restricted from the start and there is no window where it is more widely visible.

This is the better habit for anything you can see coming: a scheduled conversation with a client about a hard situation, or a planned one-to-one on a personal matter.

After recording

Not every sensitive conversation is planned. A routine check-in can turn personal partway through, or a client can raise something unexpected. Restricted can also be applied after the call has been recorded, so you can narrow its visibility once you realize it needs it.

If a call took a turn you didn't expect, mark it Restricted as soon as the call ends rather than waiting.

For the exact steps in Quill Meet, see the full guide: Guide: Restricted meetings.

How to confirm it worked

After you set the flag, check that it took effect. The guide walks through how to confirm a meeting is Restricted.

It also helps to think about what you expect to see. Once a meeting is Restricted:

The host, attendees and invitees should still have access.
Platform admins should still have access.
A teammate who wasn't part of the call, and isn't an admin, should not see it.

If something doesn't match what you expect, go back to the guide and recheck the setting before you rely on it.

A note on admins

Platform admins can see Restricted meetings. That is by design: the people responsible for running the platform keep visibility. When you tell a client or colleague that a call is Restricted, it's accurate to say it is limited to the people on the call and the platform's admins, not that no one else can ever see it.

Being clear about that up front helps people trust the setting. It does what it says, and no more.

Building it into how your agency works

A privacy setting only helps if people use it. A few ways to make Restricted routine:

Agree on the kinds of calls that should be Restricted. Client hardship, personnel matters and sensitive internal decisions are a good starting list.
Set it before the call when you can. Treat the after-recording option as a backstop, not the default.
Check it once it's set. Confirming takes a moment and removes the guesswork.
Explain who can see it. Host, attendees, invitees and platform admins. Saying this plainly sets the right expectations.

In short

The Restricted flag gives you a straightforward way to keep a sensitive call between the people who were part of it. Mark a meeting Restricted in Quill Meet before or after recording, and it becomes visible only to the host, attendees, invitees and platform admins.

Full steps, including how to confirm the setting, are in the Restricted meetings guide.