Heads up! To view this whole video, sign in with your Courses account or enroll in your free 7-day trial. Sign In Enroll
Preview
Start a free Courses trial
to watch this video
What exactly makes up a user role? A user role contains a name, description, list of rules, and any limitations.
Elements of a User Role
- Name
- Description
- Rules
- Limitations
Related Discussions
Have questions about this video? Start a discussion with the community and Treehouse staff.
Sign upRelated Discussions
Have questions about this video? Start a discussion with the community and Treehouse staff.
Sign up
Now that you have a broad understanding
of how user roles are used,
0:00
let's delve into the details.
0:04
What exactly makes up a user role?
0:07
A user role contains a name, description,
0:10
list of rules, and any limitations.
0:15
Let's check out Slack as an example.
0:19
Here we see the list of names such as
workspace owner, admin, and member.
0:22
Giving a role a name makes it easy for
people to understand and refer to.
0:29
A description is also included to help
users understand what it's used for.
0:35
And even what type of users
it's recommended for.
0:40
Now, a user role also
needs a list of rules.
0:44
Here's Slack's list of
permissions per user role.
0:48
Rules are often represented
as a chart with checks
0:51
to denote what functionality is allowed or
denied.
0:55
To add a layer of complexity,
0:58
it's worth noting that these rules
apply to regular Slack workspaces.
1:00
For business accounts,
1:06
the rules are tweaked a bit in
Slack's enterprise offering.
1:07
See the stars?
1:12
Those denote that features are only
available if an org owner or admin choses.
1:14
Enterprise products often allow this extra
layer of flexibility that isn't present
1:20
on their lower tiered to small business or
business-to-consumer oriented products.
1:25
User roles may include other relevant
information too such as seat count limits.
1:31
Perhaps, I'm limited to the number of
users, I can invite, to a given user role.
1:37
Here, I can see pending invitations.
1:42
These people have been invited but
they haven't accepted the invite.
1:45
Since I'm on the free Slack plan,
I don't have a seat limit.
1:50
But pending invitations could affect
seat counts and other products.
1:54
Here's an example from Abstract.
1:58
An app designers use to manage files.
2:01
Here we see that I've paid for
two contributor seats, and I've used both.
2:05
If I want to invite a new user,
I'll need to add another seat to my plan.
2:10
Great, now that you know more
about the makings of a user role
2:16
you're probably wondering how to
communicate all this complexity.
2:20
Products with user roles certainly
involve a lot of complexity,
2:24
with different sets of users being
able to see and do different things.
2:28
So how can we go about documenting it?
2:34
In the next video, I'll show
you how to diagram user roles.
2:37
You need to sign up for Treehouse in order to download course files.
Sign upYou need to sign up for Treehouse in order to set up Workspace
Sign up