After signing in, all users can access the same profile settings section. The top bar contains the sidebar toggle, the new ticket button for client and agent accounts, and the profile button. Agents also have a button for creating a new asset.
Your profile picture or initials appear in the top right corner. Click the circle to edit your profile or log out.
It will display a menu with the following options:
Open “Profile” to change your personal and contact details, appearance, ticket view, signatures and other settings. The examples below use an agent profile.
The profile contains these sections:
Basic information
This section contains:
Picture: your profile picture.
Login: your individual login, editable only by an administrator.
Email: your contact email address.
Personal details
You can change Language, Theme, First Name, Second Name and Surname here.
Password change
To change your password, complete Current password, New password and Repeat new password.
Further settings appear below.
User settings
This section consists of the following settings:
Language - you can choose from several available languages
Line manager - you can set your supervisor here (agent or customer) - setting used in Approvals (see Approvals tab in Admin profile)
Theme - you can choose from: Default (light theme), Gray, Dark
Ticket view - Controls the default panel settings when viewing ticket details. You can choose Chat view or Table view
Default ticket creation type (available only for Agent) - here, you can choose the default tab that will be set when entering the screen for creating a new ticket. Available options are: Ticket, Email Ticket and Customer Portal Case displayed as a tab (functionality described in the Customer Portal section in the Admin profile). This setting can be enabled or disabled in Admin profile in Settings > General > Tickets
Change status after assignee (available only for Agent) - Assigning an agent to a ticket with the “Open” status results in an automatic status change. This setting applies to the profile from which the assignment action is performed
Recipient autofill (available only for Agent) - If enabled, when replying to a ticket via email, the system automatically fills in the sender’s email address
Automatic ticket assignment to yourself (available only for Agent) - When enabled, any ticket created by an agent is automatically assigned to that agent. However, if the queue assigned to the ticket has a default agent with the “Assign when creating the ticket” option enabled, the default agent takes precedence
Line manager
Open your user profile and select a supervisor in the Line Manager field.
The line manager can be set up by Admin, Agent (with User management role) or via data from the user integration process (for example LDAP).
Assign a line manager for another user
To assign Secondary Agent as the line manager of Customer:
Open Customer’s profile from User Management. The Admin portal > Users > User management section describes how to edit user data.
Click Edit to open the window for selecting an Agent or Customer as line manager.
Select the user from the User list, or start typing their name.
Click Save to assign the selected Line Manager.
To change or remove the assigned Line Manager, click Edit. Use the ‘x’ to the right of the current user’s name to clear the assignment:
Then click Save.
User interface
Use Scroll size to set the width of scrollbars in Mint: Normal for the standard size or Small for the reduced size.
Default ticket creation properties (available for Agent and Customer)
An administrator can enable or disable this setting in Settings > General > Tickets. It sets default values in the ticket creation form.
Ticket type: select the default type for new tickets.
Queue: select the default queue.
Template: select the text shown at the start of Description when creating a ticket.
Default ticket answer properties (available for Agent and Customer)
An administrator can enable or disable this setting in Settings > General > Tickets. In Ticket Details, Template sets the text inserted at the start of Description when you click the field.
Custom fields
Custom fields appear above Signature settings. Administrators create and manage them in Admin > Agents > User fields, described later in this guide. The section is empty by default. Once fields are created, all users can see them here, as in the ‘Contact’, ‘Location’ and ‘Additional info’ examples below:
Next you have:
Signature settings (available for Agent and Customer)
Use Pick custom signature to choose a template prepared by an administrator in Tickets > Signatures. You can change any signature, including one from a template, with Edit signature. The scissors icon below the signature opens snippets that insert system values, such as the ticket number, creation date or user custom fields.
Out of office (available for Agent and Customer)
In ‘Out of office’, choose the start and end dates of your absence and select the checkbox to activate that period.
Use “Redirect notifications to” to send notifications from your assigned tickets to other agents during your absence. Click the field to see available agents.
NOTE: Redirect works only with ‘tickets.assignee’ option set in ‘Receivers’ section in notification configuration (see Admin portal -> Notifications).
After selecting specific individuals and checking the “Is active” option, notifications from the tickets you are assigned to will be sent to the chosen agents. Remember
that notifications will be redirected even if the selected target agent does not have permission for the ticket. In such a case, the agent will receive a message that
they do not have permission for the ticket when they click on the notification.
Contact group list
In ‘Contact group list’, create groups for use in ticket emails. A group can be private or shared with other agents.
Note: The contact group option is only available to agents.
The following example shows the Contact group list:
The Contact group categories field is in the top left corner.
Selecting specific categories will cause related contact groups created by other agents to appear (go to ‘Admin’ => ‘Tickets’ => ‘Contact Group Categories’ to see how to create categories.)
On the right are Search by, Add new group and Set column properties. Use column properties to choose visible columns and the fields included in searches.
The main part of this section is a table with a list of contact groups.
The table includes Group name, Description and Email addresses. Type identifies personal groups, visible only to you, and shared groups, visible to all agents. Action contains History, Edit and Delete. You can delete only groups you created, not those created by another agent.
To start configuring groups, press the button. When it is pressed, the configuration modal will be displayed.
Group name: enter the group name.
Description: describe the group.
Email addresses: enter the addresses included in the group.
Share the group with other system users: select to share with all agents, or leave clear to keep the group private.
Contact group categories: after enabling sharing, choose one or more categories. An administrator must first create the categories in Tickets > Contact group categories.
To create a personal contact group, fill in the fields as shown below and click Save.
Your new group will appear on the list.
Now going to the email section, you can select the contact group.
When you add a contact group, it is displayed in the TO field.
By clicking the x button, the group will be removed from the TO field.
By clicking the + button instead of displaying the group, each single email will be added separately.
The effect of clicking +:
To create a shared contact group, fill in the fields as shown below and click Save.
Your new group will appear on the list.
A shared group can be visible to all agents. The following screen shows another agent’s Contact group list:
To use the shared group, another agent must select its category from the list:
The group then appears in the list and is available in ticket emails.
Click after editing your profile to save the changes. If you leave without saving, the following message appears.
Open ‘Notifications’ below ‘Profile’ to choose which notifications you receive. The administrator controls which options are available. Clear an option to stop receiving that notification.
Information: This functionality is available to Agents only.
The Pending Reminder section allows Agents to easily keep track of reminders that have been set in the system. Reminders are short notes added to a ticket by an Agent. When setting a reminder, the Agent specifies when it should be displayed. At the specified time, the system triggers the reminder notification.
Reminders are set individually for specific tickets. Once they have been created, their list can be easily tracked in this section. The tab displays all reminders set for tickets that the current Agent has access to.
The reminder list contains basic information, such as the Ticket Number, Subject, Reminder Date, and Reminder Note. The Action column also allows you to go directly to the relevant ticket.
To create single reminder, please click here to visit specific section.
The User type option is available only to users who have roles from at least two different user types: Admin, Agent, or Customer. If a user has roles from only one user type, the User type option is not available.
The User type, also referred to as Switch Context feature allows users with multiple user types to quickly switch between them from the user panel. With this feature, a single account can be assigned more than one user type. This means that the same user can have Admin, Agent, and Customer roles at the same time.
Switch Context allows one person to use the same account for different business purposes while keeping the views, features, and permissions specific to each user type separate.
Example scenario
A user has the following roles:
Admin – an administrative role
Agent – an agent role used for handling tickets
Customer – a customer role associated with a company
After signing in, the user can work in the selected context.
If they need to perform administrative tasks, they select the Admin user type.
If they need to handle tickets as a Service Desk employee, they select the Agent user type.
If they need to use the system as a customer associated with a specific company, they select the Customer user type.
The user can switch between these contexts from the user avatar without needing separate accounts.
The system has three main user types: Admin, Agent, and Customer. Each user type can have its own roles and permissions:
Admin – includes the Admin and Reviewer roles, which define the user’s administrative permissions.
Agent – can have multiple agent roles. These roles can be created and configured according to the required permissions.
Customer – customer roles are always associated with a specific company. A user can have roles for one or multiple companies, and each company can have multiple customer roles.
A single user account can have more than one user type. This means that the same person can use the system as an Admin, Agent, and/or Customer.
For example, a user can be:
Admin + Agent
Admin + Customer
Agent + Customer
Admin + Agent + Customer
A user can also have multiple roles within the same user type. For example, they can have several agent roles while also having a Customer role.
The user can switch between the available user types and use the system in the appropriate context.
Roles can be assigned or removed by an Administrator from the user management section.
To manage a user’s roles:
Go to Users → User Management
Find the user whose roles you want to manage and click the Role button next to the selected user
After clicking Role, a window with three role tabs will open:
Administrative – Admin roles
Agent – Agent roles
Customer – Customer roles
To assign or remove a role, select the appropriate tab and check or uncheck the required role.
Once all required roles have been selected, click Save to apply the changes.
If a user has roles from at least two different tabs, meaning they have more than one user type, the User type option will appear in their user profile.
For example, if a user is assigned roles from the Agent and Customer tabs, they will be able to switch between the Agent and Customer user types using the User type option.
If a user has roles from only one tab, the User type option will not be available.
The active user type can be changed from the user panel.
To switch to another user type, click the user avatar and select User type from the user menu. Then select the user type you want to work with.
The system will switch to the selected context. Switching the user type changes the active context in which the user works.
For example, a user with Admin, Agent and Customer roles can work as an Agent and use the features and permissions available to their assigned agent roles:
At any time, the user can switch to the Admin user type and use the system from the admin’s perspective:
And from this place can also easily switch to the Customer’s view
Switching the user type does not remove or change the roles assigned to the user. It only changes how the user interacts with the system and which permissions apply at a given time.
Access to individual system elements depends on the permissions assigned to the user’s roles.
This includes, among other things:
ticket types
queues
custom fields
available views
ticket management features
other system elements controlled by permissions.
Permissions are applied based on the currently selected user type. As a result, the availability of a particular feature or element may change when the user switches between user types.
Example – access to a ticket type
A user has an agent role that has access to the “Complaints” ticket type. At the same time, the user has a customer role that does not have access to this ticket type.
When the user switches to Agent, they can see “Complaints” tickets because their agent role has the required permission.
The user then switches to Customer. In this context, the permissions assigned to their customer role apply. Since this role does not have access to the “Complaints” ticket type, the user will not see this ticket type in the Customer view.
The same principle applies to other system elements whose availability depends on permissions, such as queues and custom fields.