Your team and their permissions
Invite teammates, give them the right level of access, and make exceptions without inventing new roles.
Everything in ClearTalk belongs to your organisation, not to the person who created it — so agents, campaigns, and numbers survive people joining and leaving. What changes per person is what they can see and do.
Inviting someone
Team Members (under your name at the bottom of the sidebar) has two tabs: people who've joined, and invitations still outstanding. Invite by email address and pick their role; they'll get a link to set up their own sign-in.
You can change someone's role later, remove them, or cancel an invitation that hasn't been accepted. The number of people you can have is set by your plan.
The built-in roles
| Role | Suited to |
|---|---|
| Owner | The person accountable for the account — full access including billing. |
| Admin | Runs the operation day to day: agents, campaigns, numbers, integrations, and team. |
| Member | Does the work: sees conversations and contacts, but not billing or account settings. |
Most teams need nothing more than these three. Start here and only reach for a custom role when a real need appears.
Custom roles
Roles & Permissions lets you build your own role by choosing exactly which areas someone can see and change — agents, campaigns, contacts, conversations, scheduling, suppression lists, telephony, integrations, tools, knowledge bases, reports, and account settings.
Useful shapes:
- Sales rep — conversations and contacts, nothing else. They work the leads; they can't reconfigure the agent that produced them.
- Analyst — reports and conversations, read-only.
- Contractor — one area only, for the duration of a project.
The payoff is immediate and visible: sign in as that person and the sidebar itself is shorter. People don't have to navigate around things that aren't their job, and can't change something important by accident.
Exceptions without new roles
Sometimes one person needs one extra thing — a rep who should also manage the Do Not Call list, say. Rather than cloning a role for one person, open that member and adjust their individual permissions directly. The override sits on top of their role.
Use this sparingly. A handful of overrides is convenient; twenty is a role you should have created.
Sensible practice
- Give the least access that lets someone do their job. Not out of suspicion — it's simply a smaller surface for mistakes, and a shorter sidebar to learn.
- Billing access is genuinely different. It moves money and changes plans. Keep it with the people accountable for it.
- Recordings and transcripts are sensitive. They can contain payment, health, and personal details. Think about who has access, and encourage two-factor authentication for anyone who does — it's self-service under Settings → Security.
- Remove people the day they leave. Not the week after.
- Review it a couple of times a year. Roles drift as teams change.