To create user roles, go to:
controls and click on "user rolls"
Click on "new role" and give it a name that represents the group of users it applies to
Set up permissions for the role by turning on or off access to different tabs or features in the platform
If the role is for a client that will have their own users, check the "client" permission
Set up payment link or redirect payment as needed for the role
Repeat the process for additional roles as needed
To create a parent account for users that will have their own users, set them up as a parent account
To create a child account for users that will not have their own users, set them up as a child account under the appropriate role

Video Transcript:
Now that we have our marketing dashboard set up, why don't we move into creating users and how you can create those accounts within the platform?
So first step: before you create any type of user, you you need to set up some user rolls. Now our system allows you to create what are called parent accounts. Those are accounts that are not associated with roles. So when you start thinking about bringing users into your platform, there's two different types of users. There's a user that is just like you, that can have their own brand, have their own child users. You know sales organizations that have multiple sales people. You know those types of users are what we call parent accounts. So if you have any user that you're going to need to create users within that account, so child users, you would always want to set them up as parent accounts.
In this example I'm setting up child account. So you need to set up a user role. So user role only applies to users you're going to create inside your own account. That would be in this example here if I was going to set support raps or if I'm going to set up. You know my marketing group or my sales group or or my design group right. You can create several different roles for your internal users and then you may also have clients right. So you may have clients need login to access the project management system, login to have their own. You know reporting dashboard for your marketing efforts that you may be doing for them, and so there's a lot of different ways that you would have child users.
But just think of it as this. You know, if I have an account that i'm bringing on that needs to have their own users, then you would always set them up as a parent account. If you have users that will not have multiple users, they just need access to your system. You can set them up as child users.
So first step you need to create a user role, so you're going to go to controls and then click on user rolls. And here you have a button, a new role. So click that this is the actual role of the client, of the user. So you know, if you're creating products maybe you're creating, you know different back office pages or different functionality and you're creating different subscription. You definitely want to. You know, call that role, name what that group of users are.
In this example, I'm just going to put client user. We'll set up an actual client, use a role first and then I'll set up some internal role, so client use and again you can call it however, whatever you want. Once you get create, you can go in through the edit button or go directly through the Ida here.
So once you go in here, you're presented with a lot of different permissions. Essentially, these are turning off tabs that these users have access to. So, in this case, I'm setting up a client user. In the use case, for this could be. I'm a marketing agency, now need to build them their website, a need to set up automation. I need to set up. You know there's so they can manage their leads that come in through the system. You know I need to build websites for them, so I'm I'm going to give them access to everything. I also want them to create tickets within the platform. You know, maybe setting up a call tracking line may allow them to use the system. But all this sits underneath my brand as my client and I want to know that this is a client.
So we have, first and foremost, if you're creating a role that's associated with a client, we have permission called client. This only should ever be used if you want to designate those child users as clients, and what I mean by that is inside the project management system in different parts of the system. Track this permission, called client, and and you can also designate you know the project who is assigned to, based on the client right. So it's important to only have this checked if in fact this is a client of yours, if not don't even check it right. So in this case this is a client role for me. So I'm setting it up with this permission.
Next, I'm going to turn on everything except a few permissions, and I'll explain what those are. So I'm turning everything on this permission right here. Manage tickets. This means that this person can assign tickets, are assigned ticket, edit tickets, view tickets that are not assigned to them. So make sure for client users right. You're not going to want them to manage tickets only for internal users. So I'm not going to check this box.
Also manage users. This is important, our system. If you can manage users, you can actually login as that a user to troubleshoot or set their system up or do anything. You have access to their account. So do not check this for users that rolls. You don't want them to be able to manage any users right and be able to log into. So it's a very powerful feature there as far as a permission standpoint.
I'm going to turn on marketing, marketing dashboard, meetings, projects, project dashboard, sales, dashboard arranging, embed task activity tickets, voice and web activity. So these two manage tickets, manage users are the only ones that really give you outside permissions, other than seeing what you see on the left-hand side here and being able to access it. And at this point, this user role is set up.
Now, if I wanted to set up payment link or redirect payment as they go through the onboarding process, you can set up a payment link here. So if you have strive, you have pay power or whatever, you can put your payment link in here, and what that does is every role you create.
You have an onboarding link here. So if I copy this link and I go out to that, I have the ability to send this to anybody that I want, and when they sign up on this link they automatically get assigned to this user role. So if you have a payment link in here, when they sign up, it'll redirect them to the payment processing side of it. So you don't have to use this. But if you choose to use this, this is here for you to do that.
So let me just set up a couple of more rolls real quick. So in this case, I'm going to set up sales rosales user, so these will be sales reps that are selling for Wayne enterprises trying to get new clients to come on board, or you set up the client account. So I'm going to create the sales user role and in this role permission. I'm going to want activity box, no need for blogs so they don't have a blog cadences right. We definitely want some automation going with their sales activity. Definitely want them to see call activity. They're not a client. So I'm skipping that. No need for DNS conversations. This is where you're going to reply to text message and get your new text messages and anything related to projects and things like that.
Courses. I may set up courses for my salespeople to get trained on as far as how to sell better for Wayne enterprises. So yeah, I'm going to do courses, definitely email campaigns. So this is, you know, a preference here. If you want your cells, agents to be able to do email campaigns within their platform. So in this case, I'm just going to throw it in there. Funnel temples, funnels, knowledge-based definitely manage tickets, manage users, so this may be helpful. You may want your salespeople to access to clients and and see what's going on so they can see the reporting and things like that. So I do like my salespeople having access to the users, but you can turn that on and off, and then marketing dashboard. What's important? Marketing tab right, I have email campaign set, but marketing it's it's under here. So you need to make sure you have marketing selected. No need for marketing dashboard. I want them to see their sales side of it, so on, to have the sales dashboard. I'm not going to have my sale spoiling. You know what? I will have my salespeople part of projects because you know, as they bring on a new client, they may want to have visibility on what's going on with that project meeting pages. Definitely at them to be able to set up meeting pages. No need for such activity campaign. Sure timples. Yes, no need for social automation task activities. Yes, we want them to be able to see that. No need for tickets, and you know definitely voice and no need for web activity. So again I could put up no need for payment link for my internal sales person. But I can send them this link right and so you know they're the same. They look the same, but depending on which link you've sent will determine you know what use they going to.
Let me go back and add-in another role real quick. So now I'm going to put in, let's just say, a support role. So for support, you know I'm going to definitely want, you know phone right, so definitely want to call activity task, maybe definitely want the activity box. No need for meetings, projects, projects, dashboard. Let's see here it's task activities, managed tickets, of course manage users.
Of course, we definitely want them to be at least part of projects, and that's pretty much it. You may want your support people to have access to the car so they can manage leads. You know, assign them to lead and then they can come into that account. In this case, I'm not, and that's pretty much it. So support role, set up. Good to go on that.
And the last role that I would set up would be like enablement team. So use the role and so this person will work on clients. So they'll work on clients, they'll have projects, they may not need the phone system or car, and so in this case, I'm going to manage users. May want them to be able to manage tickets as well. That way, you know, if they get a ticket through the project management system, definitely task activities. So activity box and conversation.
So one thing about conversation, any comments on tickets, any comments on projects, any of that stuff you can actually, you know, get all that inside the conversation.
So definitely want to include that on every role that has access to Tickets projects no need for it. So they don't need void blind and I think this one is good. So yeah, that's that's pretty much it. On the roles you know, as we add more permissions and this grows here, you know it's going to be the same concept. You create these roles, you add users to those roles again. Just think about Roles: any user that's going to be a child user of your account. If you have a client or an account that you're setting up, that will have their own users. You need to set them up as parent accounts and the next video will cover that.