Join Gini von Courter for an in-depth discussion in this video Understanding permissions, part of Learning Jive Administration.
- Our next topic is permissions. Permissions indicate who can view and create, who can modify, delete, even who can administer different sections of content, different places, different spaces within your Jive site. By default, all registered users, and because this is a Jive-n site, an internal facing site, not an external site, all the users we have would be registered users by default. They can all view all of the content there is.
So whether we're talking about documents or posts, polls, videos, events, discussions, all of that, all registered users can view it. All registered users can also create all those different types of content. And all registered users can offer comments on content. Additionally, all of our users can create and store up to five avatars. To create a sixth, they have to get rid of one. They can have up to 10 different profile pictures that they use, and they can edit and view profiles of other users, except they can't see their cell phones unless they also have a specific connection to that person whose profile they want to look at.
Now in external facing communities, Jive-x communities, this looks a little bit different because you also have guest users then. But for our community, we have a lot of permissions that are available to all of our users. But this isn't all the permissions there are. This is simply permissions over your own profile, viewing profiles and content. We also have permissions that are administrative permissions, who gets to set up spaces, who gets to set up groups, who gets to add users. Permissions over spaces, for example, our solar team space.
And there are permissions for social groups, for global blogs, for home pages, and there are even some settings for mobile use. So there are a lot of different permissions and different levels of permissions in Jive. When we talk about setting up permissions, there's a process. We're going to start by creating a user group. We won't give permissions to individual users. It's too much to manage over time. So we'll start by creating a group. We'll add that group to one of those permission areas we just saw.
For example, we'll say this group has a particular type of relationship to the global blogs, or this is the group of people who can administer a space. We'll then assign permissions that give that group the right to do that. And then we'll add members to the group. And finally, we'll add at least one and potentially more administrators to the group. The administrators are the people who decide who can be members of the group. So when we look at a user group, this is very different from a social group.
Our social groups that we created earlier are around a particular type of community, a particular type of interest. We create user groups specifically so that we can administer our site more elegantly and more efficiently than if we were to simply give permissions to different individuals. How do we assign permissions? Well, in spaces, we'll actually say here's a permission level, a bundle of permissions that we will give to this user group. In social groups though, we don't have those built-in permission levels, so we can assign specific permissions.
For administrative functions, once again, we have access to permission levels. And in all events, if there's a special case, we can create an override for a particular individual. So we can assign a permission level to a group and then we can say this person's an exception, they either have less or they have more permissions. If you start doing a lot of that, it's a clue that you don't have enough user groups. Let's go create some user groups.
- Recognize the benefits of a members-only group.
- Review the steps you would take to customize a theme.
- Determine appropriate permission settings for different users.
- Explore different types of user relationships to improve team communication.
- Name three types of content that can be moderated.
- Identify a situation in which it is necessary to change abuse settings.