Skip to content

How Users & Rights Work

Every person who logs in to Daktela is a user. What a user can do is defined by three things that combine into one configuration:

  • User type β€” the user's fundamental behaviour and which licenses they consume (Contact center, Back office, Cloudphone, Passive).
  • Access β€” which modules the user can open and the general actions they can perform there (create, read, update, delete, export…).
  • Rights β€” which content the user can work with inside those modules: which queues, ticket categories, CRM databases, macros, wallboards and so on.

Access and rights are reusable sets β€” you build a handful that match your team roles and assign the same set to many users, rather than configuring each person from scratch.

When you are ready to add someone, follow Onboard a New Agent β€” it takes you through the steps in the order the system requires.

What Defines a User

flowchart TD
    user["User"] --> type["User type<br>(licenses & behaviour)"]
    user --> access["Access<br>(which modules)"]
    user --> rights["Rights<br>(which content)"]
    user --> calling["Extension + device(s)<br>(for calls)"]
    rights --> q["Queues"]
    rights --> cat["Ticket categories"]
    rights --> crm["CRM databases & records"]
    access --> mod["Module actions<br>(create / read / update / delete)"]

A user needs an extension and at least one device only if they make or receive calls β€” see How calls reach a user below.

The Building Blocks

Building block What it does Where to set it up
User types Fundamental behaviour and license consumption. Set per user in the user detail
Accesses Which modules a user can open and the actions allowed there; also dashboard layout and custom shortcuts. Settings β†’ Users β†’ Accesses
Rights Which queues, categories, CRM and other content a user can work with. Settings β†’ Users β†’ Rights
Agents The individual user records β€” identity, password, 2FA, devices, recording, API tokens. Settings β†’ Users β†’ List of Users
AI Coworkers AI-powered users (chatbots, voicebots, mailbots) managed alongside agents. Settings β†’ Users β†’ List of Users, AI Coworkers tab
Devices & extensions The phones a user calls from and their internal number. Settings β†’ Devices
Call permissions Rules limiting which destinations a user may dial. Settings β†’ Users β†’ Call permissions
External users Limited read-only ticket access for partners, vendors or customers via a separate portal. Settings β†’ Users β†’ External users

Two Places to Connect Agents and Queues

A queue offers activities to agents based on their user rights β€” never to individual users directly. There are two screens for the same relationship, and they edit the same underlying setting from opposite ends:

  • From the rights side β€” the Queues tab in a set of user rights lists every queue those rights can use, with the login type (Manual / Automatic / Fixed), call pickup and priority.
  • From the queue side β€” the Agents dialog in Queue Basics lists every set of rights that can use that queue, with the same login-type and priority options.

Info

Both screens assign user rights, not people. To give one person access to a queue, you assign the queue to the rights they hold β€” everyone sharing those rights gets the same queue access. If you need one person to differ, they need their own set of rights.

How Calls Reach a User

A user is reachable by their extension β€” a unique internal number. The extension can ring one or more devices (a WebRTC softphone, a hardware SIP phone, a mobile, an MS Teams client). The full explanation, with an example, is in SIP Devices. Users who don't take calls need neither.

Assigning Type, Access and Rights to a User

You set all three in the user detail at Settings β†’ Users β†’ List of Users β€” edit any user and change their type, access and rights.

  • You cannot change a user's type, access or rights while they are logged in and ready.
  • Cloudphone users have neither access nor rights β€” see User types.
  • When saved, the user immediately behaves according to the new settings.

Tip

Use the clone feature when adding someone to an existing role: it copies the same type, access and rights and adds the new user to all the relations the cloned user belongs to.

Before You Start

  • Administrator access to the Users module and its sub-modules.
  • A picture of your team's roles β€” each distinct role becomes one Access set and one Rights set that you reuse.
  • The licenses you need are available β€” check the Licensing module.
  • The queues and ticket categories the agents will work already exist (or plan to create them first).

Ready? Continue to Onboard a New Agent.