Teams & permissions

Give every seat the access it needs. And nothing more.

Every permission starts switched off. Pick a role, grant what the job requires, and choose whether the person sees their own records, their team's or the whole account. Save the mix as a template and reuse it for the next hire.

Book a demoGet started
permissions in 16 groups
59
roles: admin, manager and agent
3
data scopes: own, team and account
3
how it works

Decide who sees and does what, one permission at a time, with teams, roles and data scopes for one office, several branches or several clients.

  1. Permissions

    Permissions are grouped by area, from the agent console and campaigns to supervision, billing and API keys. A permission can only be granted together with the one above it, so access builds up from view, to use, to manage. Sensitive actions stand alone: listening to calls is not the same permission as barging in.

    • 59 permissions in 16 groups
    • Listen, whisper and barge granted separately
    • Recording playback and recording download granted separately
    • Custom templates to reuse a role setup

  2. Structure

    Group people into teams, attach teams to departments, and give campaigns a project that holds the business context for scripts and coaching. Invite people by email or with a link, with their role and permission template set before they join. Pause reasons and contact statuses come in groups, so each campaign gets the lists that fit its work.

    • Teams with invitations by email or shareable link
    • Departments and projects to separate branches, clients or offers
    • Pause groups and status groups chosen per campaign
    • Role and permission template set at invitation

  3. Data scopes

    Agents see the records assigned to or created by them. Team managers see the teams they manage. Admins see the whole account, like the owner. Reports and supervision follow the same scopes, and each OVOKY account is isolated from every other.

    • Own: records assigned to or created by the person
    • Team: everything in the teams they manage
    • Account: the whole workspace
    • Accounts isolated from each other

What's included

Everything around teams & permissions

Branches and clients

Run several branches, clients or offers from one account with projects, teams and scoped managers.

Deny by default

A new user gets only what their role and template grant.

Permission templates

Save a role, its permissions and its data scope as a reusable template.

Pause groups

Pause reasons with an allotted time, grouped and assigned per campaign.

Status groups

Contact outcomes grouped and assigned to the campaigns that use them.

API key access

Only people with the API key permission can create or manage keys.

Teams & permissions: questions

Short answers to what teams ask us most. Something else on your mind? Talk to us

  • The role (admin, manager or agent) sets the starting point and the default data scope. A permission template is a saved set of permissions and a scope for a role, which you apply when you invite or edit someone.

  • Yes. Give the manager the team data scope. In reports and supervision they then see the agents, campaigns and lists of the teams they manage, not the rest of the account.

  • Yes. Create a project for each client or offer, group people into teams by branch or client, and give each team manager the team scope. Campaigns, scripts, statuses and pause reasons can then differ from one client to the next.

  • Yes. Listening to recordings and downloading them are two separate permissions, and live listening, whispering and barging are three more.

  • Not today. Users sign in with email and password, or with their Google account. SAML or OIDC single sign-on and two-factor authentication are not available.

Works with

Pair it with

Bring every customer conversation into one place

Calls, SMS, WhatsApp, email and chat in one inbox, on one invoice. Start with one team, then grow.

Book a demoSee pricingGet started