Jive allows people within an organization to connect and collaborate by communicating and creating content. This article describes the different features of the Jive platform; specifically focusing on creating and managing places, the different types of content, the communication elements, and the user profile fields. After reviewing this article, you will be able to:
- Describe different types of places as well as how to create and manage them.
- Differentiate the types of content.
- Explain what blogs and events are and how they are managed.
- Use direct messages and the Inbox.
- Operate user profile fields.
Jive enables users to create different types of content in containers that house all the collaborative content for a certain subject or a team. These containers are called places and there are three kinds of places: Spaces, Social Groups, and Projects.
Jive also supports advanced communication and collaboration features such as direct messaging for private communication between users and displaying users' official, geographical, and other custom information on their profiles.
There are three types of places on the Jive Platform:
Spaces are built in a hierarchy, with the ability to have a network of multi-level sub-spaces underneath them. They also use permissions, set by the community administrators, to define who can see and do different things (create/view/comment) in the space. Permissions get inherited by any sub-spaces unless they are customized for that space, so if a user can do something in one space, this user can do it in the sub-spaces as well (unless the permissions have been customized).
Any type of content can be created in a Space unless it has been turned off for a particular space by the community administrators.
Social groups (also called Groups) are isolated containers within a community. They have no ties to other places and cannot have sub-groups. Permissions are managed on a peer-group basis by the original group creator, the admins selected for the group, or both. They can also house any type of content unless one or more is turned off by the community administrators. For more details on the social groups, please refer to this page on Types of groups.
Social groups and user groups are different. A social group is a place or a container, whereas a user group is where the users are grouped for managing their permission settings. Users will be unaware of what user group they are in, and the Admin users manage the user groups.
Projects can only reside within a space or a group; they cannot stand alone. However, they can still house any type of content unless one or more is turned off by the community administrators. Permissions are inherited from the place in which the project was created. Projects also get created with a Start and End Date and come with additional titles on their pages that display the progress being made in the project (if the project administrator keeps them up to date).
Which one to use when
Use a space if you:
- Need to share information about your department, program, or initiatives with the rest of the organization/larger audience.
- Need to add permissions controlling who can create which kinds of content in your place
- Need to create a hierarchical set of places.
- Need permissions for your place to be managed centrally.
Create a group if you:
- Want to collaborate privately with your team or project team.
- Want to invite individuals to collaborate, and don't need centrally managed permissions.
- Want to invite people from outside the organization to access your place.
Place Type Comparison
|Yes, via permissions.||
Yes, via the group settings.
|Inherited from the containing place.|
|Access permissions||Defined in the Admin Console. Inherited by sub-spaces.||Defined in group settings. Not inherited.||
Inherited from the containing place. Not customizable.
|Create permissions||Defined in the Admin Console. Inherited by sub-spaces.||Any user.||
Any user by default. Can be customized and restricted by the community administrators.
|Content||Any. May be customized and restricted by the community administrators.||
Any. May be customized and restricted by the community administrators.
|Any. May be customized and restricted by the community administrators.|
Large-scale collaborative needs with sub-space ability, such as those of an entire department or office, or an expansive topic.
Smaller-scale collaborative needs either by a specific audience or a more specialized topic.
|Short-term area to collaborate on a finite topic.|
Creating and Managing Places
In Jive, spaces can be created via the Admin Console, while social groups and projects can be created through the user interface. For more information on how to create and manage each type of place, please read through the following articles.
- Creating New Space from the Admin Console
- Creating Groups
- Deleting Groups
- Managing Features and Content Types in Social Groups
- Creating Projects
Two of the most commonly used content types are:
Blogs can exist in different places, such as System Place, a social group, or a personal container.
The place where the blog resides determines how and who can manage permissions for that blog. A blog can be managed in particular ways, depending on its location. In general, a blog is managed by its author. It can also be managed by the owner of the place (space, project, or social group) where the blog resides. Please see this page on Blogs by place for more details.
System-wide blog settings impact all the blogs in the community, irrespective of the place or owner of the blog. For details about the system-wide blog settings, visit this page on Configuring blogs system-wide.
Blogs can be migrated from one context to another. Read through this page on Migrating blog content for details on how to migrate blogs.
Events allow users to create and collaborate by invitation. Users can comment and provide their attendance (Yes/No/Maybe). Also, attendee limits can be set for events. Events can reside in several different places, such a space, social group, project, or a personal container.
Listed below are available event types.
In cloud instances, events are delivered as an inbuilt content type whereas in hosted/on-prem instances events module is delivered as plugins.
For more details on creating events and editing the event properties, please read through the following articles.
Messages and Inbox
Direct Messages allow users to send messages that are visible only to the receivers. Direct Messages do not appear in the Activity Stream. Direct message notifications appear in the Inbox of the recipient or recipients.
- To create Direct messages, go to Create (pencil icon) > Message or Inbox > Send message.
The Inbox is where the users get notified about the contents they follow and the direct messages they receive.
The Inbox helps the users to manage their notifications effectively with many options like unread, filter, comment, hide new activity, etc. For more information on the options you can use in the Inbox, please read through this article on Inbox Interface.
User Profile Fields
The default user profile fields contain the official and geographical details of the users. However, custom profile fields can also be created for additional information. For information on creating custom fields, please see the article on Creating New User Profile Fields.
There are also option settings that determine the level of control the user has over the user profile fields. You can set the visibility level of the users' profile information, or you can let users control who sees their profile information in the community.
To learn more about user profile settings, please visit this page on Letting users control their own settings.
Hover cards enable short information fields from users' profiles to be displayed when someone hovers over their name or avatar in a community.
For more information on hover cards and how to determine the fields that will be displayed, please visit this article on Selecting Fields for Hover Cards.