A Gladly user is someone inside your company whose job is to help Customers, manage teams, or manage Gladly. Every user should be assigned a role — or multiple roles — to determine their access to Gladly’s capabilities. Below is a list of roles available in Gladly:
Compliance Administrator2
Administrator
Team Manager
Agent Plus
Agent
Analyst1, 4
Task User
Answer Administrator
API User1
Developer1, 4
Liveboards Only
Permissions are attached to roles, which determine what a user can do. For example, the Administrator role has abundant rights (add, edit, update, and delete), whereas a Team Manager role has rights limited to certain Gladly features. The role with the highest permission set supersedes roles with fewer permissions. If an Agent + Administrator role is assigned, they can access the Administrator permission set.
Gladly charges usage fees based on user activities rather than solely by role. For example, there’s no charge to assign someone Administrator access as this role usually doesn’t interact with Customers directly. However, because this role has access to everything, there will only be a charge if the Administrator interacts with Customers by performing tasks such as sending an email, answering a call, or creating Tasks. Another example is assigning the API User role combined with Agent. This user won’t be billed as an Agent as long as they do not interact or perform actions for Customers.
Your chosen method depends mainly on the number of users you want to invite. If you’re adding one or two users, adding them one at a time would be easier. However, a bulk upload is faster and more efficient if you want to add 25, 50, or hundreds of users.
Note – Account invitations expire in 24 hours
Resend an invitation if the previous one has expired.
Watch Out – Make sure your user’s email address is valid before sending an invitation
If you are setting up a user via email / password access (as opposed to SSO), ensure your user’s email address is valid and can receive emails before sending an invitation. Invalid email addresses will be added to a bounce-suppression list, preventing the invitation email from sending to the user. If you need to remove an email address from the bounce-suppression list, please contact Gladly Support with a P4 designation. If you have implemented SSO, email address on Gladly do not need to be valid before sending an invitation but please ensure the user has been set up with proper SSO configuration beforehand.
Click on the top left corner of the screen.
Click Settings.
Under the People category, click Users. The Users page will show you a list of your Gladly users. For ease, you can also preview the roles assigned to users, the number of Teams and Inboxes they belong to, and their account status.
Use the search feature to find users by name, email, or role quickly.
Click the header name to sort the Name, Email, Roles, Teams, Inboxes, and Status columns.
Click Add User.
Complete the following fields on the Add User page:
Email – Enter the user’s email address. This is also used to invite them to Gladly.
Name – Enter the user’s full name.
Roles – Check the box next to the role(s) that apply to this user. The affected roles are automatically unchecked if an incompatible combination of roles is selected. See Roles and Responsibilities to learn more about each role.
Inboxes – Assign/unassign Inbox(es) to the user.
Use the search feature to search all of your available Inboxes.
Every Inbox the user is assigned to appears below the search bar. To unassign an Inbox, click X.
An Inbox that has since been deactivated Inbox but is still assigned to an Agent appears as Inbox Name (deactivated).
Deactivate a user’s account when they leave your company or no longer need access to Gladly. You cannot delete users in Gladly, even if their account is deactivated.
Click on the top left corner of the screen.
Click Settings.
Under People, click Users.
Use the search feature to find the user you need to deactivate. Hover over the user you want to deactivate, click, then select Edit User.
Under the Status section, mark the user as Deactivated. This option only appears for existing users.
Click Save.
What happens to Conversations and Tasks when a user is deactivated#
Open and Waiting – Conversations in Open and Waiting state when an Agent is deactivated are automatically unassigned from the deactivated Agent and go back as a New Conversation to re-route to another Agent. The Conversation Timeline of re-routed Conversations due to the deactivation will say “Routed from <agent> to <channel> because <agent> were deactivated” to indicate the Conversation was re-routed because of the user deactivation.
Tasks – Open Tasks are re-queued in the same Inbox to be assigned to another Agent.
1Cannot log into Gladly without another accompanying role, such as Team Manager, Administrator, or Compliance Administrator, to access the Settings page or access Agent UI.
2Compliance Administrator enhances the Administrator role with access to Data Retention settings.
3Analyst role is made available upon activation of Insight Builder, a feature add-on that incurs additional licensing cost per Analyst user. See Invoices and Billing for more information.
4Developer role is limited to accessing Lookup Adaptor Debugger and Apps. Assign Agent or Administratorrole with Developer to provide access to Search or to create Customer Profiles.
5Task User role cannot be combined with other roles.
aInsight Builder is an add-on feature.
bInsight Builder is an add-on feature. Shared dashboards are only available if Insight Builder is active. Team Managers and Administrator user roles can view shared dashboards/reports built by Analysts.
This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
Cookie
Duration
Description
__cf_bm
29 minutes
This cookie, set by Cloudflare, is used to support Cloudflare Bot Management.
_wpfuuid
1 year 1 month 4 days
This cookie is used by the WPForms WordPress plugin. The cookie is used to allows the paid version of the plugin to connect entries by the same user and is used for some additional features like the Form Abandonment addon.
BIGipServer*
session
Marketo sets this cookie to collect information about the user's online activity and build a profile about their interests to provide advertisements relevant to the user.
cookielawinfo-checkbox-advertisement
1 year
Set by the GDPR Cookie Consent plugin, this cookie records the user consent for the cookies in the "Advertisement" category.
cookielawinfo-checkbox-analytics
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional
11 months
The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
CookieLawInfoConsent
1 year
CookieYes sets this cookie to record the default button state of the corresponding category and the status of CCPA. It works only in coordination with the primary cookie.
PHPSESSID
session
This cookie is native to PHP applications. The cookie stores and identifies a user's unique session ID to manage user sessions on the website. The cookie is a session cookie and will be deleted when all the browser windows are closed.
viewed_cookie_policy
11 months
The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Cookie
Duration
Description
li_gc
5 months 27 days
Linkedin set this cookie for storing visitor's consent regarding using cookies for non-essential purposes.
lidc
1 day
LinkedIn sets the lidc cookie to facilitate data center selection.
UserMatchHistory
1 month
LinkedIn sets this cookie for LinkedIn Ads ID syncing.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Cookie
Duration
Description
_ga
1 year 1 month 4 days
Google Analytics sets this cookie to calculate visitor, session and campaign data and track site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors.
_ga_*
1 year 1 month 4 days
Google Analytics sets this cookie to store and count page views.
_gd_session
4 hours
This cookie is used for collecting information on users visit to the website. It collects data such as total number of visits, average time spent on the website and the pages loaded.
_gd_visitor
1 year 1 month 4 days
This cookie is used for collecting information on the users visit such as number of visits, average time spent on the website and the pages loaded for displaying targeted ads.
_sp_id.*
1 year 1 month 4 days
Snowplow sets this cookie to store user information that is created when a user first visits a site and is updated on subsequent visits.
_sp_ses.*
30 minutes
Snowplow sets this cookie to store user information that is created when a user first visits a site and is updated on subsequent visits.
AnalyticsSyncHistory
1 month
Linkedin set this cookie to store information about the time a sync took place with the lms_analytics cookie.
mf_user
3 months
Mouseflow sets this cookie to identify whether a visitor is new or returning.
vuid
1 year 1 month 4 days
Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos on the website.
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
Cookie
Duration
Description
_mkto_trk
1 year 1 month 4 days
This cookie, provided by Marketo, has information (such as a unique user ID) that is used to track the user's site usage. The cookies set by Marketo are readable only by Marketo.
bcookie
1 year
LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser IDs.
bscookie
1 year
LinkedIn sets this cookie to store performed actions on the website.
li_sugr
3 months
LinkedIn sets this cookie to collect user behaviour data to optimise the website and make advertisements on the website more relevant.