Users¶
Requires the "Users" permission.
From the Users page (CONFIGURATION menu) you manage everyone who signs in to Thelgo with your account: administrators, operators and agents. For each person you decide the roles, the permissions and, for operators, the phone system extension they use to call.
The three tabs of the page¶
Under the title there are three tabs:
| Tab | What it contains |
|---|---|
| Users | The list of users and the + New user button (see below) |
| Operator profiles | The permission profiles for operators (see Permission profiles) |
| Agent profiles | The permission profiles for agents |
The user list¶
In the Users tab you see how many users there are ("… users in the account") and the New user button, which appears only in this tab.
| Column | Content |
|---|---|
| Name | The profile photo or avatar, first and last name |
| The email address, which is also the username for signing in | |
| Roles | The user's roles, separated by commas |
| Extension | The assigned fixed phone system extension, or "—" |
| Last access | Date and time of the last access to Thelgo, or Never if the user has never signed in |
| (last column) | The trash icon (Delete user) |
To find a user:
- type in the Search by name or email… box: the search looks at first name, last name and email;
- choose a role in the filter (All roles, Administrator, Operator, Agent): a user with several roles appears under each of them;
- click a column header (Name, Email, Roles, Last access) to sort.
Click a row to open the user's page and edit it; the trash icon at the end of the row deletes the user (see Delete a user).
Clients are not users
Clients (see General settings) do not appear in this list and cannot be created from here. Access to Thelgo for the reports of their campaigns is given from the same section (see Client access).
Deleted users do not appear here
A deleted user disappears from this list but stays in the history (see Delete a user).
Create a user¶
- Press New user.
- Fill in the personal details and the password (see the table below).
- Turn on one or more Roles and, for each one, tick the Permissions to grant. For operators and agents, if profiles exist, you can instead choose a Profile (see Permission profiles).
- If you turned on the Operator role, choose the Extension mode.
- Save with one of the two buttons:
- Create user: creates the user without notifying them. You give them the credentials yourself.
- Create and send credentials: creates the user and sends them an email with username, password and sign-in link.
The save button stays disabled while first name, last name, email, password or at least one role is missing, or if you chose "Fixed extension" without choosing the extension.
If sending the credentials fails
The user is created anyway, but you stay on the page and the message "User saved, but the credentials could not be sent: check the email format in Settings." appears at the bottom as a red notice. The text of the credentials email is not configured in your account: it is a single format managed by the service provider. If the problem persists, give the user the credentials yourself and report the issue to support.
User fields¶
| Field | Notes |
|---|---|
| First name, Last name | Required |
| Required. "Also used as the username for sign-in.": two users cannot have the same email | |
| Password | Required when creating, at least 8 characters. The eye icon at the right of the field (Show password / Hide password) shows or hides the typed characters; it is also there when editing, in the New password field |
| Language | Interface language for that user: Italiano, English, Español, Français, Deutsch, Čeština, Română |
| Timezone | Time zone in which the user sees dates and times |
| Chat bot | Checkbox that turns the support chatbot on or off for that user. It is on by default (see below) |
| Work groups | A switch for each group: the user can belong to several groups, or to none. It appears only if there is at least one work group you can assign. Under the field you read "It can belong to several groups. A group administrator only sees what belongs to their groups or has no group." |
For a new user, Language and Timezone are pre-filled with yours: change them if the user works in another country.
The support chatbot
The support chatbot is available to all users, of any role and without needing any particular permission, if the service is active for your platform. From here you can turn it off for a single user by clearing the Chat bot checkbox; each user can still change it themselves from their own profile (see My profile).
Automatic avatar
Every new user, of any role, gets an avatar with their initials when created (the first letter of the first name and of the last name in white, on a background of a random color from a small palette): you do not need to upload anything. The user can then replace it with a photo or another avatar from their own profile (see My profile).
Automatic assignment to campaigns¶
Campaigns are not assigned from this page but from each campaign's configuration (see Campaign configuration). There is, however, an automatic mechanism: when you create a user with the Operator or Agent role, Thelgo immediately associates them with all the campaigns where Select all is on for operators or for agents.
Only at creation
The automatic association happens only when the user is created. If you add the Operator or Agent role to a user who already exists, assign them by hand to the campaigns you want.
If there are work groups, a new user joins with Select all only the campaigns without a group and those of their groups. The same applies when you add them to a group (from here or from the Group members window): they also join the campaigns of that group with Select all. If you remove them from a group, they leave that group's campaigns (they stay in the reports and the history).
Roles¶
Every user must have at least one role ("Select at least one role."). You can turn on more than one: after signing in, the user chooses which role to enter with and can change it at any time.
| Role | What it is for |
|---|---|
| Administrator | Administrator area: campaigns, data, reports, configuration. The visible pages depend on the permissions |
| Operator | Handling calls (see the operator manual) |
| Agent | Calendar of the appointments booked by operators |
Permissions¶
When you turn on a role, its Permissions appear below. With Select all / Deselect all you tick or clear them all at once. For operators and agents you can alternatively assign a profile: in that case the profile's permissions apply.
When changes take effect
Roles and permissions are read at sign-in: if you edit a user who is already connected, the changes apply from their next sign-in.
Prerequisite permissions¶
Some permissions depend on another permission of the same role. As long as the "base" permission is not ticked, the dependent one stays grey and cannot be selected; if you clear the base permission, Thelgo automatically clears the ones that depend on it too.
Administrator permissions¶
Each permission gives access to a page of the administrator area menu. Pages without the permission do not appear in the menu and cannot be reached.
| Permission | Page it gives access to |
|---|---|
| Dashboard | The initial dashboard (see Dashboard) |
| Campaigns | Campaign list and configuration (see Campaigns) |
| Calendar | Appointment calendar (see Calendar) |
| Databases | Contact databases and imports (see Database) |
| Download databases | The permission to export a database to a file (Export database icon on the Databases page) and to download from the Operations page the file of a Database export. It does not give access to any page: it can be assigned only to someone who also has Databases (while Databases is not ticked it stays grey, see Prerequisite permissions). See Database |
| Dynamic database fields | Schemas of custom fields (see Dynamic fields) |
| Operations | Log of bulk operations (see Operations) |
| Users | This page |
| Calls report | Call report (see Call report) |
| Access report | Access report (see Access report) |
| Operators report | Operator report (see Operator report) |
| Campaigns report | Campaign report (see Campaign report). The Campaigns permission (campaign list and configuration) is a different one |
| Predictive/Voice AI report | Predictive/Voice AI report (see Predictive report); the menu item appears only if the account has Predictive or Voice AI campaigns enabled |
| Connected users | List of connected users (see Connected users) |
| Audit log | Log of actions (see Audit log) |
| Anonymization | Anonymization of contacts (right to be forgotten). It enables the Anonymize button in the contact detail and on the Databases page (see Anonymization). It has no menu item of its own |
| General settings | General settings, External API, Email and SMS (see General settings, Email, SMS). Together with All work groups it manages the work groups |
| Outcome profiles | The Outcome profiles page (see Outcome profiles). Administrators who already had the General settings permission received it automatically; for everyone else, and for new users, it is assigned from here |
| Appointment outcome profiles | The Appointment outcome profiles page (see Appointment outcome profiles). As with Outcome profiles, administrators with General settings received it automatically |
| Surveys | The Surveys page (see Surveys): create, edit, test and delete surveys. To choose the survey in a campaign's form the Campaigns permission is enough; correcting a contact's answers requires the Campaigns permission |
| Help | Help page (see Help) |
| All work groups | It does not open any page: it says that the administrator sees and manages everything, not only what belongs to their groups or has no group, and is the only one who can create and manage the work groups. It appears in the permission list only when at least one group exists |
The Anonymization permission
The permission is not given automatically to existing administrators; it is present in the permission list on this page and is assigned from here.
Be careful with your own permissions
You can also edit your own user. If you remove the Users permission from yourself, you will no longer be able to get back into this page: another administrator will have to give it back to you.
Operator permissions¶
| Permission | What it allows the operator to do | Requires |
|---|---|---|
| Edit contacts | Correct personal data and phone numbers while handling a call | — |
| Insert contacts | Add a new contact by hand to a campaign | Edit contacts |
| View public callbacks | See and work public callbacks too, not only their own private ones | — |
| Search contact | Search for a contact in one or all of their campaigns and call them directly | — |
| View reports | Consult the history of their own calls | — |
| Download recordings/transcripts | Listen to the recordings of their own calls from the report | View reports |
| Quality Check | Work the Quality Check queue on the Positives they recorded | — |
| Quality Check on all operators | Work the Quality Check queue on the Positives of all operators | Quality Check |
An operator with no permissions can still work the campaigns they are assigned to and their own private callbacks.
Agent permissions¶
| Permission | What it allows |
|---|---|
| Allow multiple appointments in the same time slot | Without this permission Thelgo prevents booking (or postponing) an agent's appointment in a time slot already taken by another of their appointments or by a commitment on their linked external calendar. With the permission, overlaps are allowed |
| Hide operator and campaign reference | The agent does not see which operator booked the appointment or which campaign it belongs to, either in the appointment detail or in the calendar (Day view). This also applies to appointments the agent books with a contact |
| Search contacts for appointments | In the agent's New appointment popup the Find contact choice appears: the agent can link the appointment to a contact already in a campaign they are assigned to (blocked contacts or those registered in the Opposition Register are excluded). See Agent calendar |
| Add contacts for appointments | The New contact choice appears: the agent can enter a new contact in a campaign they are assigned to and link it straight away to the appointment. The two permissions are independent: you can assign just one |
What happens when an agent books an appointment with a contact
The contact automatically gets a Positive outcome recorded (origin "Agent", operator "Appuntamento Agente", which appears in the reports as "Appuntamento Agente (sistema)" (Agent appointment (system))), so operators do not offer it again. In the Calendar the appointment appears like those booked by operators. In the Audit log the action is recorded under the agent's name. The agent cannot delete these appointments: you do it from the Calendar.
Permission profiles¶
Requires the "Users" permission.
A profile is a named set of permissions, valid for the Operator role or for the Agent role. Instead of ticking the same permissions user by user, you create a profile and assign it to several users with a single choice in the user's page. When you change the profile, the permissions of all the users who have it change. Profiles do not exist for the Administrator role, which always has individual permissions.
Profiles are managed in the Operator profiles and Agent profiles tabs of the Users page. Each tab shows the description "A profile is a set of permissions you can assign to several users with the same role: when you change it, the permissions of every user who has it change." and the list of profiles, sorted by name, with the summary "Permissions: n · Users: n" (permissions of the profile and users who have it). If there are none you read "No profiles yet."
Create and edit a profile¶
- In the Operator profiles or Agent profiles tab press + New profile (to edit one, click its row).
- Write the First name (the field of the New profile window is labelled this way; at most 100 characters; in the same role two profiles cannot have the same name, uppercase and lowercase do not count).
- Tick the profile's Permissions, with Select all / Deselect all if you need it. The same rules as the prerequisite permissions apply: a permission that requires another stays grey until the other is ticked, and clearing the base one also clears the dependent ones.
- Press Save. The notice "Profile saved." appears.
When you edit an existing profile, the window reminds you that "Changes apply right away to every user who has this profile (users already logged in see them at their next login)."
The Save button stays off while the name is empty. If the name already exists, the server answers "A profile named '…' already exists for this role."
Assign a profile to a user¶
In the page of a user with the Operator or Agent role, under the role there is the Profile menu (only if at least one profile exists for that role). Choose a profile or No profile (individual permissions).
- With a profile chosen, the user has only the permissions of the profile: in the list of permissions the switches are locked and show those of the profile, with the note "The profile's permissions apply: to change them, edit the profile in the Profiles tab. This role's individual permissions are not used." The role's individual permissions are not kept.
- A user has at most one profile per role: if they are both operator and agent they can have an operator profile and an agent profile.
- The permissions of the Administrator role always stay individual.
- If you remove a role from a user, the profile of that role is removed too.
- If the chosen profile no longer exists, saving is refused with "The profile selected for the … role no longer exists: choose another one."
As with individual permissions, changes apply from the next sign-in of a user who is already connected.
Delete a profile¶
The trash can at the end of the row opens the Delete profile window: "You are about to delete the profile name." To confirm, type the word delete and press Delete.
- If the profile is assigned to users, the window warns: "n users have it: the profile's permissions will be applied to each of them as individual permissions, so nobody loses them." The users keep the same permissions, but now individual (without a profile).
- If nobody has it, you read "It is not assigned to any user."
At the end you see "Profile deleted." or "Profile deleted: its permissions were applied to n users."
Creating, editing and deleting profiles, and assigning a profile to a user, are recorded in the Audit log.
Phone system extension (Operator only)¶
When the Operator role is on, its box shows the Extension section:
| Option | Meaning |
|---|---|
| No extension | The operator has no extension associated in Thelgo |
| Dynamic extension | Cannot be selected: "Feature not yet available." |
| Fixed extension | The operator always uses the same phone system extension, to be chosen in the Choose an extension… menu |
The fixed extension is essential for Thelgo to be able to start calls toward the operator:
- to call a contact from the handling screen: without an extension the operator receives "Your user has no fixed extension assigned: contact the administrator.";
- for Predictive campaigns: without an extension the operator sees the campaign as unavailable, with the message "You need a fixed extension on the phone system to use this campaign. Contact the administrator.".
In the extension menu:
- each extension can be assigned to only one user: those already in use are grey and show in brackets the name of who has them;
- if the list is empty, "No PBX extension associated with this account." appears: the available extensions are configured by the service provider;
- until you choose an extension you see "Select an extension, or turn off "Fixed extension"." and you cannot save.
If you remove the Operator role from a user, their extension is freed immediately and can be assigned to another operator. The same applies at creation: the extension is saved only if Operator is among the roles.
When you save an operator with a fixed extension, Thelgo also tries to align on the phone system the extension's email with the user's and its office number with the Outgoing number chosen (see below).
Outgoing number¶
After you choose a Fixed extension, the Outgoing number menu appears: it decides which number the extension uses to call outside.
| Item | Effect |
|---|---|
| A number from the list | The numbers of your account's trunk: the chosen one is written as the extension's office number on the phone system |
| Do not allow outgoing calls | The extension's office number on the phone system is cleared: the extension cannot call outside. This is the item proposed for a new operator |
| Not set (the PBX is not changed) | Appears only for an existing operator who has never had a number: until you choose something else, Thelgo does not touch the extension's office number |
Under the menu you read: "The chosen number is also written as the office number of the extension on the PBX, together with the email.".
- The number is updated on the phone system at every save of the user, only if it differs from the one already there. If the phone system does not respond, the user is saved anyway and the office number does not change: reopen the user and save again.
- If the chosen number is not among those of your account, saving is rejected with "The outgoing number '…' is not one of the numbers of this account's phone system trunk.".
- Without a fixed extension (or when removing the Operator role) the outgoing number is not saved.
A new operator starts without outgoing calls
If you do not choose a number, an operator created with a fixed extension has Do not allow outgoing calls: the extension's office number is cleared. Choose the number before saving.
The operator's page with Fixed extension shows the Outgoing number menu under the extension choice, with the items Not set (the PBX is not changed), Do not allow outgoing calls and the phone system numbers.
Account without a phone system
If the account has no phone system configured, "This account has no phone system configured." appears and the only possible option is No extension.
Accounts with the App iFrame (x-bees or Collaboration)¶
If your account uses Thelgo inside the phone system app (x-bees or Collaboration), the app recognizes the operator by their extension. Under the options you read: "With the App iFrame integration active: an operator with a fixed extension connects only from the PBX app; without an extension they connect from the login page (and do not use Thelgo's telephony). Dynamic extension is not available."
| Operator | How they enter Thelgo |
|---|---|
| With Fixed extension | Only from the phone system app. They cannot use the classic login page as an operator |
| No extension | From the classic login page, like a normal user. They do not use Thelgo's telephony, which requires a fixed extension |
| Dynamic extension | Not allowed with the App iFrame active |
Someone who also has other roles can sign in from the login page, but without being able to choose the Operator role (unless they are an operator without an extension).
Dynamic extension with the App iFrame
With the App iFrame active, No extension can be chosen; only the dynamic extension is forbidden (if you try to save it, "With the iFrame App integration on, operators cannot have a dynamic extension: assign a fixed extension or no extension." appears).
Disconnecting trusted devices¶
With the App iFrame active, the first time an operator opens Thelgo from a new device they must confirm their identity with a code received by email; from then on the device is "trusted". On an existing operator's page you find the Disconnect all x-bees devices link (or Disconnect all collaboration devices, depending on the app used).
Use it if an operator loses or changes their computer, or if you suspect unauthorized access. After the confirmation, the green notice "x-bees devices disconnected." appears at the bottom (a red notice if it fails) and, the next time the app is opened, the operator will have to verify their identity again by email on every device. The operation is recorded in the Audit log.
Sending the operator the link to download the phone system app¶
On an existing operator's page, under the extension choice, you find the link Send the link to download the Collaboration app or Send the link to download the x-bees app: the app name depends on the type of Wildix phone system of your account. The operator receives by email the links to download the app for Windows and for macOS.
The link appears only if:
- you are editing a user who is already saved (not creating);
- the Operator role is on in the page;
- the account has a Wildix phone system.
The email goes to the user's already saved address. If you change the email and do not save, the link stays disabled and underneath you see "Save the user to send the link to the new email address.".
While sending is in progress, the link becomes "Sending…". At the end the following appears at the bottom:
| Notice | Meaning |
|---|---|
| "Link sent to address." | The email has been sent |
| "Unable to send the app link." | Generic error, with no more specific reason |
| "This account has no Wildix phone system: there is no app to download." | The account does not use Wildix |
| "The user has no email address." | The email is missing in the user's page |
| "The email format has not been set up yet." | The "Link app centralino (Collaboration / x-bees)" email format has not yet been prepared by the provider: contact Thelgo support |
| "No mail server has been assigned to this email format: contact Thelgo support." or "The SMTP assigned to this format no longer exists." | The email format has no sending server: the provider fixes it, contact Thelgo support |
| "Sending failed: …" | The mail server rejected the sending; after the colon is the reason |
The email has the subject "Scarica l'app Collaboration per lavorare con Thelgo" (Download the Collaboration app to work with Thelgo) (or x-bees). In the text, in the default format, it greets the operator by first and last name, explains that they need the app on their computer and offers two links, "app per Windows" (app for Windows) and "app per macOS" (app for macOS); it closes by inviting them to sign in, after installing, with the credentials they received from the administrator. Subject and text are prepared by the provider (super admin) in the "Link app centralino (Collaboration / x-bees)" email format: they can therefore be customized. The links point to the installers published by Wildix, always the latest version.
When to use it
You need it for a new operator who has to install the app before entering Thelgo. To also send them username and password use Save and send credentials (see below).
The user's page (Edit user) has the personal details, the new password, language and timezone on the left. On the right are the boxes of the roles Administrator, Operator and Agent with their permissions and, for the operator, the Extension section set to Fixed extension. For an operator, the Send the link to download the Collaboration app link sits under the Extension choice, above Disconnect all collaboration devices.
Edit a user and reset the password¶
Open the user from the list: the page becomes Edit user. You can change all the fields, roles and permissions; if you change the email, the username they sign in with changes too.
To reset the password:
- Type the new password in the New password field (at least 8 characters). If left empty, the password does not change.
- Save:
- with Save changes the password is changed and you give it to the user yourself;
- with Save and send credentials (it appears only if you typed a new password) the user receives the new credentials by email.
Every change to roles and permissions is recorded in the Audit log, with the before and after.
Delete a user¶
Deletion is done from the user list, not from the edit page (which only has the save buttons, aligned to the left).
- In the list, click the trash icon at the end of the user's row.
- In the Delete user window you read "You are about to delete first name last name. They will no longer be able to log in, but will remain visible in history (reports, appointments, audit log). This action cannot be undone.".
- To confirm, type the word delete in the field under "Type delete to confirm:" (the word is in the interface language).
- Press Delete permanently, which becomes active only when the word matches (upper and lower case do not matter).
If deletion is not possible, the reason appears in the window, or "Unable to delete the user."
Deletion is not definitive for the data:
- the user can no longer sign in and disappears from the user list and from the campaigns they were assigned to;
- their calls, appointments and audit log entries remain; in the reports and filters their name appears with the (deleted) marker. System users (automatic actors, not people: Public API, Appuntamento Agente, VoiceAI) have the (system) marker instead;
- if they were connected, their session is closed and they no longer show as connected;
- their extension and their email are freed: you can assign them to a new user.
You cannot delete:
- your own user ("You cannot delete your own user.");
- the only administrator of the account ("You cannot delete the only administrator of the account.").
Deactivate instead of delete
At the moment there is no "active/inactive" switch: to remove someone's access you use Delete user. If the person comes back, create a new user (you can reuse the same email).
Limits per role¶
Your contract may include six distinct limits, three per role (Administrators, Operators, Agents). They are all optional and are set by the service provider on your account: they cannot be changed from Thelgo, and if there is no limit for a role, that role is unlimited.
| Limit | What it counts | What happens when it is reached |
|---|---|---|
| How many can be created | Non-deleted users who have that role (a user with several roles counts in each) | When creating a user, or adding that role to an existing one, saving is rejected with "Maximum number of administrators reached for this account." (with "operators" or "agents" instead of "administrators" for the other roles) |
| How many connected at the same time | Whoever is using Thelgo with that role right now | Whoever tries to sign in with that role receives "Maximum number of administrators connected at the same time reached for this account." (with "operators" or "agents" instead of "administrators" for the other roles) |
Notes:
- The creation limit is checked only on new roles: editing other data of a user who already has that role is not blocked even if the limit has been reached. Deleting a user frees the place immediately.
- The connected limit applies at sign-in if the user has only one role; someone with several roles can always sign in, and the check kicks in when they choose which role to work with.
- Sessions left open by someone who closed the browser without logging out also count (see Connected users).
- If you need a higher limit, contact the provider.