Go to Manage → Users → Accesses to set up which Daktela modules agents can open and what they can do in them. Set up shortcuts agents will see below the main menu.
How Do Accesses and Rights Define What Users Can Do in Daktela?
which modules users with those Accesses can go to in the Daktela GUI (and via the API).
users' Create/Read/Update/Delete permissions for items contained in those modules.
The CRUD permissions for a module are not necessarily linked to access to that particular module. A user may e.g. not have access to the CRM but have read permission. As result, they can see CRM data in activities and in other modules where they do have access if the data is displayed there, e.g. Listings.
what specific items users with those Rights can see in the modules they have access to. E.g. users that have access to the CRM module need to also have rights to the CRM Database the CRM data is contained in to see it.
if they have create and edit permissions in Accesses, what data they can select in the details of items. E.g. users that have edit access to Tickets need to have Rights to the ticket's Category to see and open it. If they want to pass the ticket on to another user, they need to have Rights to that user.
for queues, Rights also define which ones users can log in and out of.
The diagram shows the relationship between Accesses and Rights. You can zoom in and out using ctrl/cmd + mouse wheel.
Create a New Access
Click Add new in the top right corner.
In the Create access screen, enter a Title and Description (optional).
To edit the Access settings, open its details.
By cloning an existing Access:
Click Clone in the Actions column. The Access settings will open – follow the steps in Edit an Access.
Edit an Access
Click the Title of an access to open its details – the Access settings screen will open.
You can edit the Title and Description (optional). The Name field can't be changed.
Backoffice access: Turn on if you want to use this Access with Back-office Users. Access to the Tickets module will automatically be turned on.
A CC user cannot simultaneously have read, update, or delete access to tickets and a right that lacks login (not 'none') to the queue. Alternatively, they must have a call without queue enabled with those settings to pass validation.
Set up your Shortcuts and Accesses:
When you have set up your Access, click Save.
Set up the shortcuts that agents can use below the main menu on the left hand sidebar.
We don't recommend using more than 6 shortcuts – if you add more shortcuts, they will be very small.
Add or remove shortcuts using the buttons at the end of each line.
Use the up and down arrows to change the shortcut order.
Select the type of shortcut from the drop down menu:
Empty – the shortcut will do nothing.
Link – open an internal or external page (follow Steps 4-7 below to set the link up).
Global search – search for a query in Daktela. Can search in the Menu, Contacts, Accounts, Tickets and Knowledge base.
Documentation – open doc.daktela.com.
New ticket – create a new ticket in Tickets.
Select the shortcut colour from the drop down menu.
If you have selected Link in Step 2:
Select the icon type from the drop down menu.
Enter a short description of the shortcut that will be displayed on mouse hover.
Enter an absolute (e.g. https://www.google.com/) or relative (/crm/contacts/create) address.
Check the checkbox to open the link in a new tab.
Click Save or go to Accesses below.
Use the toggle switches to enable or disable access to individual modules of Daktela.
Each Daktela module's access settings are in a separate tab. Check the checkboxes to allow access.
In general, you can grant the following types of access:
Access – the module will be displayed in the users' main menu.
Create – the users will be allowed to create new items.
Read – the users will be allowed to open items.
Update – the users will be allowed to edit items.
Delete – the users will be allowed to delete items.
Some modules have different types of access – these are described in tooltips directly in Daktela.
To prevent application errors, some settings automatically turn others on or off after you save the Access.
From version 6.20, if you need to set up very specific accesses, you can disable Set dependencies automatically above the list of Accesses. Keep in mind that if set up incorrectly, application errors can occur.
You can set up the dashboard layout of each Access.
In the list of Accesses, click the Dashboard settings button in the Actions column.
Drag fields from the Widgets, Statistics, Analytics or One metric widgets list on the right hand side and drop them into your dashboard layout on the left. There is a description of each widget displayed once you drag it into the layout.
Click the Split button to set up multiple columns and adjust their width using the plus and minus signs.
Repeat the process to set up all desired dashboard items.
Some items may have a Settings button. Click it to open more options. If you are using Statistics, you can set up filters using the Settings button.
Save your Dashboard settings.
Page in iFrame
Enter the URL (including any variables) and widget height.
In the Allow attribute, you can control the Feature Policy, allowing the iFrame to access fullscreen, microphone, camera and geolocation. Enter e.g.
Drag record categories from the Available field and drop them in the Selected field to include them in the widget.
Delete an Access
How you can delete an Access depends on your version:
From Version 6.20
When you delete an Access, all users that use it will be automatically logged out and deactivated.
After you click the Delete button, a dialog window will inform you of the number of users that use the Access and ask you to confirm.
Up to Version 6.19.x
If an Access has at least one user, it is not possible to delete it – the Delete button will be inactive. You can see how many users each access has assigned to it in the list of accesses.
To activate the Delete button, go to Manage → Users → List of users and remove the access from all users. If you have a large number of users, you can change their accesses in bulk.