Skip to navigation

Members and roles

Roles answer one question: who may do what in the organization’s account? The answer follows how teams actually work. The person who pays decides about money and the account’s existence. The people who run the team manage access, settings and integrations. The people who do the work build flows and run calls. And the people who only answer the phone get exactly that — calls transferred to them, and nothing else.

Every member has one role, and it applies in every account the organization owns. The server checks it on every request, from the dashboard and the API alike; the dashboard hides what your role can’t do.

The four roles

Owner
exactly one

Created the organization or was handed it. The only role that touches money and the account’s existence: payments, cards and auto-recharge, buying and releasing numbers, connecting carriers, deleting the account or organization, exporting the account’s data, transferring ownership, and changing members’ roles. Can do everything an Admin can.

Admin
any number

Runs the account and the team, without the money. Invites, suspends and removes members; manages API keys and the webhook signing secret; changes account settings; configures phone numbers, webhooks and integrations; manages transfer destinations and members’ teams. Can do everything a Member can.

Member
any number

Does the daily work: flows, prompts, calls, campaigns, schedules, contacts, the Do Not Call list, leads and analytics; reads transcripts, listens to recordings, listens in on and takes over live calls; sees the balance, invoices and costs. Can do everything an Agent can.

Agent
any number

Only takes calls. Sets their own availability and answers the calls transferred to them in the dashboard. Agents don’t see call history, flows, contacts or billing — the role is for the people on the phone, not for the people building the agent.

What each role can do

ActionOwnerAdminMemberAgent
Set your own availability; answer calls transferred to you; edit your own profile✓✓✓✓
Build, test and publish flows; manage prompts and flow functions✓✓✓—
Place calls; run campaigns and schedules; read transcripts and insights; listen to recordings✓✓✓—
Listen in on or take over a live call✓✓✓—
Manage contacts, imports, the Do Not Call list and leads; view analytics✓✓✓—
View the balance, invoices, costs and per-call cost breakdowns✓✓✓—
View transfer destinations, members’ teams and hours; set your own hours✓✓✓—
Change account settings (recording, analysis, compliance, notifications)✓✓——
Configure phone numbers (connect a flow, name, recording override); manage webhooks and integrations; web-call access on flows✓✓——
Delete call recordings✓✓——
Add, change or delete transfer destinations and destination groups✓✓——
Set members’ teams; set another member’s hours or availability✓✓——
Create and revoke API keys; create and rotate the webhook signing secret✓✓——
Invite members; suspend, reactivate or remove a member✓✓——
Top up; manage cards and auto-recharge; redeem coupons✓———
Buy or release numbers; add, edit or remove carriers (SIP, Twilio, WhatsApp)✓———
Change a member’s role✓———
Transfer ownership✓———
Export the account’s data; delete the account or the organization✓———

The same table is in the dashboard, under Team → Roles & permissions, with your own role marked. Apps can read it with GET /roles and the caller’s own role and permissions with GET /permissions.

Who changes roles

Only the Owner changes a member’s role, between Admin, Member and Agent. Nobody is made Owner by a role change — ownership is transferred. Admins invite people with any of the three roles but can’t change a role afterwards.

API keys and roles

API keys belong to the account, not to a person: Owners and Admins create and revoke them, and a key acts with the scopes it was given, whoever uses it. Give each integration only the scopes it needs.

Taking calls

Every role can take calls. Whether a transfer rings someone is decided by the flow’s destination, the member’s teams and hours, and their availability — not by role. Suspended members are never rung. See Take calls in the dashboard.

The Team page

Team in the sidebar (organization accounts only — a personal account has no team) has three tabs:

TabWhat it showsWho sees it
MembersEveryone in the organization with their role, status (Active, Suspended), availability for transferred calls, and teams and hours. The row menu holds Tags and available hours, availability, role, Suspend and RemoveOwner, Admin, Member
InvitationsInvitations not yet accepted or declined, with role and date sent; cancel one from its rowOwner, Admin, Member
Roles & permissionsThe role table above, with your own role markedEveryone, including Agents

Your own availability — whether you take transferred calls right now — is the You control at the top right of the page.

Inviting someone

1

Team → Invite to the team

Enter their email and choose Admin, Member or Agent (no one is invited as Owner — ownership is transferred, not granted). Optionally add a title and department for the member list. The person must already have a Talkif login with that email.

2

They accept

An email carries the invitation, and it also appears when they next sign in. Until then it’s listed under Team → Invitations, where you can cancel it.

3

They switch to the account

Accepting adds the organization’s account to their account switcher. Their personal account, if any, is untouched.

Suspending, removing, leaving

  • Suspend keeps the member on the list but blocks access until they’re reactivated — the right move for a leaver whose work you still need to audit. Reactivate reverses it.
  • Remove takes them out of the organization and all of its accounts. Their user and personal account continue to exist; anything they created in the organization’s account stays there.
  • A member can leave on their own. The Owner can’t leave without first transferring ownership.
  • The Owner can’t be suspended or removed by anyone; transfer ownership first.

Transferring ownership

The Owner picks an existing active member; that member becomes Owner and the previous Owner becomes an Admin. Do this before an Owner leaves the company — an organization without a reachable Owner can’t change its billing or delete itself without support’s help.

Next