Understanding Accounts & Permissions
Accounts & Permissions encompasses more than just adding your employees. Let's break down everything you can expect before we dive straight in.
User Accounts
Add your employees or 3rd party vendors helping to integrate and maintain your sticky.io account. You also manage your Employee Department Templates here.API Accounts
Create your API Accounts to whitelist the API calls you'll make for passing transactions and more to sticky.io.Single Sign On
Integrate supported call centers enabling them to seamlessly log in to your sticky.io account and manage your customer service.
Below is a quick video to cover the entirety of Accounts & Permissions with a glossary of everything discussed below.
Navigating to Accounts & Permissions
To begin, let's navigate over to Settings > Accounts & Permissions.
User Accounts & Employee Department Templates
Following, we'll land on the User Accounts tab. This has two sections,
Employees
Add your employees or 3rd party vendor users that will help you integrate and maintain day-to-day operations.Employee Department Templates
Out-of-box, we have a myriad of pre-defined departments each with their own set of permissions to help you easily integrate users. e.g. Customer Service, Administrators, financial.
Let's dig into adding your users and any nuance that may pop up along the way.
To begin, navigate to Actions > Add Employee.
Once loaded, we're met with a user creation screen that is mostly an industry-standard standard user interface.
Full Name
The name of the user you're adding. This is used in various reporting and logs.Username
What is used to sign into your sticky.io account.E-mail Address
Not used to sign in - useful for receiving system notifications, or reset password emails.Phone
Used for 2FA and system notifications delivered via SMS.Password
Must be a minimum of 8 characters. With at least an uppercase letter, number, and symbol.Allowed IP Address(es)
Whitelist the IP address that the user needs to be connected to in order to log in to your sticky.io account.
Note: Whitelisting IPs is an excellent security step and can be taken a step further by having a company VPN that can only be accessed through your email provider.
Department
What controls the overarching permissions assigned to your users.Time Zone
Date and time stamp on orders will change depending on the user's assigned timezone. Moreover, when reviewing reports that look back in time, they will pivot off of the user's assigned timezone.Grant Portal Access
The portal can be found at portal.sticky.io. This is used for SSO and purchasing additional corporate licenses.2 Factor Authentication
Or 2FA, receive a SMS code to authenticate your sign-in request.
Once you've finished, click Save. Following, we'll be redirected to the User Permissions table.
Understanding User Permissions
We briefly touched on user permissions above when mentioning the User Department. Once you've chosen a department, a set of predefined permissions are already applied to that user.
That means in most cases simply filling out the first form is sufficient and you can add entire teams within minutes. However before you successfully add someone, you'll always be given an opportunity to fine-tune specifically what it is that user can and can't do. e.g. A new team member may not be ready to handle refunds or returns.
Given the sheer size of sticky.io, there is a huge list of permissions that you can fine-tune on a per-user basis. What I would like to shed light on is Campaign Permissions.
This is visible at the top of the Permissions table.
What are Campaign Permissions?
At this point in our journey to understanding everything sticky.io, we've broken down and created Campaigns. With Campaign Permissions you can enable or restrict what campaigns a user has access to.
This is great if you're working with affiliate partners and want to restrict what campaigns that affiliate partners can see and interact with. Or you could have a dedicated campaign for Customer Support / Phone Sales and restrict everything else.
When drilling into Edit Permissions, an additional UI window will appear prompting you to either Allow Access or Restrict Access to your campaigns.
Note: This is a niche feature and if you do have a use for it, it's encouraged that you use Allow Access for campaigns and specify what the user can view versus Restrict Access.
They both essentially do the same thing, whereas if you opt to Restrict Access and end up creating new campaigns at a future date, you'll have to revisit this feature each time and add new campaigns to the restricted list.
Understanding API Accounts
API users are an essential part of launching your business with sticky.io. Creating API users is how you whitelist the types of API calls that can be made using a secure set of credentials.
Without this, bad actors could make API calls to your instance with devastating consequences.
It's encouraged that this part of the platform is restricted to Administrators and Technical Users (developers) only.
Navigating to API Accounts
To begin, let's navigate over to Settings > Account & Permissions.
Following, from User Accounts > API Accounts.
Creating API Accounts
Creating an API Account is similar to many other parts of sticky.io, simply click Actions > Add API User.
An additional UI window will appear prompting us to provide information for the following fields.
Username
Simply the username for the API User. Used when authenticating your API requests to your sticky.io account. (In addition to a password that is auto-generated after saving your user)Company Contact
Name of the third-party vendor or individual receiving API access.Email
The email address for the API user. Again, the vendor or individual receiving access.Phone
Phone number of the user receiving access.Department
Critical: Similar to regular user accounts, the department for API users handles the overarching rules and permissions assigned to this API user.Description
Internal - Just helps you to keep track of what account is handling what endpoints. e.g. Different API users that do the same functions but are for different companies or landing pages.
Understanding SSO
Also known as "Single Sign On", enables third-party Customer service providers the ability to login into your sticky.io account and help with things like order management.
There are URL based integrations that can be used to link call center software (e.g. Five9) to sticky.io Platform single sign on. When you are assigned a single sign on account as a call center, you will be assigned a group ID. Your system will also need to have knowledge of the client subdomain that you are attempting to access. The format for the "pop URL" will be:
For example, if you are assigned group_id=21 and are attempting to connect to client_subdomain=demoaws:
If the agent has not logged into my.sticky.io before, they will be prompted to login with their assigned username/password, but then be directed straight to the Platform for demoaws (e.g. https://demoaws.sticky.io). The next time the agent takes a call and is directed to a new Platform, they should not have to sign in as long as the session has not timed out. For example if the next call is for client_subdomain=sandboxdemo, the next pop URL will be:
This would take the agent straight into sandboxdemo (https://sandboxdemo.sticky.io) without logging in again.
In the case that a call center wants to directly implement the low-level SSO API, the following information would need to be provided by sticky.io to the call center partner.
Creating SSO
To create an SSO user, let's first navigate over to Settings > Accounts & Permissions.
Once loaded, we'll be presented with 3-tabs. We've already discussed the first two. Let's click Single Sign On.
