Jive Places: Spaces, Groups, and Projects
A place in Jive is essentially a container that houses all the collaborative content for a certain subject or team. There are three types of places: Spaces, Groups, and Projects. The differences between them can sometimes be confusing, so here're the basics of each one.
Spaces
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 community administrators, to define who can see and do different things 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 community administrators. Due to their hierarchical nature, spaces are typically used to represent organizations and departments within a company, as well as other concepts that require a network of places linked together.
For more information about creating spaces, see Designing space hierarchies and Creating new space from Admin Console.
Social Groups
Groups, or social groups, are isolated containers within a community; they have no ties to other places and cannot have sub-groups. Permissions are managed on a per-group basis by the original group creator or the admins selected for the group, or both. Groups can also house any type of content unless one or more is turned off by community administrators. Because they are freely created containers, groups are used most often for topic-specific collaboration rather than something general to a team. They also cater to collaboration between specific teams or different departments that often work together closely and rely on each other.
For more information, see Using content and Types of groups in the User Guide.
For more information, see Using content and Types of groups in the User Guide.
Projects
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 community administrators. Permissions get inherited from the place in which the project was created. Projects also come with designated Start and End Dates and may include additional titles on their pages that display the progress being made in the project (if the project administrator keeps them up to date). Projects are generally used for short-term objectives that require collaboration and centralized content management.
For more information, see Using projects and tasks in the User Guide.
For more information, see Using projects and tasks in the User Guide.
What to Use
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
Comparison of Place Properties
| Spaces | Groups | Projects | |
|---|---|---|---|
| Hierarchical? | Yes | No | No |
| Can be private? | Yes, via permissions | Yes, via group settings. | Depends on parent place |
| Access permissions | Defined in the Admin Console. Inherited by sub-spaces | Defined in group settings. No inheritance | Inherited from containing place. Not customizable |
| Create permissions | Defined in the Admin Console. Inherited by sub-spaces | Any user | Inherited from containing place. Not customizable |
| Content allowed | Any; may be customized or restricted, or both by community administrators | Any; may be customized or restricted, or both by community administrators | Any; may be customized or restricted, or both by community administrators |
| Best uses | 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 |