Contents
If you're a space or system administrator, use this guide to learn about how to create and configure spaces, including setting up defaults for content and managing discussions and documents.
A space is a container for content such as documents, discussions, and blogs. A space can also contain projects (with tasks), polls, tags, and announcements. Typically, spaces are arranged in a hierarchy that reflects the organizational groups of people using Jive SBS. For example, in a company the human resources department might have its own space, with sub-spaces for content related to benefits and recruiting.
The concept of a space is essential in Jive SBS because spaces provide the context for organizing content, sharing information, collaborating, and generally getting things done. A space can reflect and support the distinctive characteristics of how the group using it interacts with each other. That includes who has access to the space, what content is allowed there, and how the content is exposed.
People can reach spaces from the Browse menu (although they'll only be able to visit a space that they have permission to view). A space's All Content page lists content and sub-spaces the space contains and provides links through which people can create new content. In practice, though, you'll probably find that it makes sense to customize the space's overview page to suit the needs of group of people using the space.
As a space administrator, you have access to features for a space you're administering. You can log in to the admin console to view and change settings for that space, although you can make some of those changes in the regular Jive SBS user interface.
The following table lists things space administrators can do with spaces, along with where you'll find the user interface for doing that task:
| Task | Location |
|---|---|
| Creating sub-spaces |
Admin console Space Actions list |
| Configuring allowed content and locale | Admin console |
| Setting discussion defaults | Admin console |
| Setting document defaults | Admin console |
| Archiving discussion threads | Admin console |
| Exposing discussions on another site | Admin console |
| Setting content permissions | Admin console |
| Setting admin and moderation permissions | Admin console |
| Managing discussions | Admin console |
| Managing documents | Admin console |
| Managing tag groups |
Admin console Space Actions list |
| Merging spaces | Admin console |
| Customizing the space overview | Space Overview tab |
One of the first things you'll likely do when setting up Jive SBS is create spaces and sub-spaces in hierarchies that reflect your group's functional areas or interests.
You'll likely find that you're defining spaces and their sub-spaces in ways that reflect how people organize themselves outside of Jive SBS. For example, at a high level, spaces could reflect organizational divisions. Sub-spaces are likely to reflect organizational subdivisions, but they could also mirror areas of interest or other more informal boundaries. For example, you might create a top-level Sales space to reflect the sales department, then create sub-spaces such as Channel Sales, Business Development, and Direct Sales. Other criteria by which to define sub-spaces include functional area and topic.
For more information on what you get with each of the access schemes, see Permission Defaults for New Spaces.
Each space features an Overview tab that you can customize using widgets. As shown below, you can drag widgets into the overview design space to add views on content in the space — or even from elsewhere on the Internet. For more on widgets, see Customizing Pages with Widgets.
You can change a space's name and description if the space's focus changes. You can also change the display name, which is the name used in URLs that link to the space.
For sub-spaces, you can also set which content types the space supports. For example, by clearing the Documents check box, you'll effectively remove the Create a document link from the space's Actions list. It also means that people won't be able to select that space when choosing where to put a new document they're creating using the New menu. Such a change also applies to existing content. So if people have created documents in the space, then you clear the Documents check box to remove support for them, existing documents will no longer be viewable in the space (although they'll still exist).
You can set up moderation so that the people who are moderators have the ability to approve or reject any content that's under moderation. Setting up moderation is a two-step process: granting moderation permission to people who'll be moderators and choosing which kinds of content should be moderated.
You can grant content moderation permission at a sub-space or root space level. You should consider having more than one moderator doing moderation wherever you need it. Here's why:
You might see how having just one moderator can mean a bottleneck if that person becomes unavailable.
You do have a failsafe for new moderation requests, however. New requests are routed in the following order:
This applies to new requests only. Existing requests won't be routed to the next queue up. Be sure to see the Content Moderation section of Managing Permissions for more on what happens if moderators are deleted from the system.
You grant moderation permission in the admin console at Spaces > Permissions > Admins & Moderators. For more on granting content moderation permission, see the Content Moderation section of Managing Permissions.
You choose content to moderate by using the admin console. Where you make those settings depends on which content you want moderated. For all, you choose types of content in the admin console at Spaces > Settings > Moderation Settings. But you'll choose a different scope by selecting the change space link on the Moderation Settings page.
| For This Content | Choose This Scope in the Admin Console | Who Typically Moderates |
|---|---|---|
| Documents and discussions in a space or project | Sub-space containing the content or project | Sub-space moderators |
| Documents and discussions in social groups | Root space (for content in all social groups) | Root space moderators |
| Personal blog posts everywhere | Root space (for posts to all personal blogs) | Root space moderators |
| Blog posts specific to a space or project | Sub-space containing the blog or project | Sub-space moderators |
| Blog posts in a system blog | Root space (for posts to all system blogs) | Root space moderators |
| Announcements created at the root space | Root space (for global announcements) | Root space moderators |
| Announcements created in a sub-space or project | Sub-space in which the announcements will be created | Sub-space moderators |
| Private messages | Root space (for all private messages) | Root space moderators |
Personal blog posts are moderated by the root space moderator; space blog posts are moderated by the space moderator.
Comments are moderated by either the designated moderator or the blog's owner (they'll both get requests for moderating comments). But comments and trackbacks are moderated only if the blog's owner sets up moderation for them. If they do, then comments and trackbacks will appear in moderation queues for both the owner and the root space moderator. The blog's owner can also moderate comments on their blog's Blog Management page.
Content in groups is moderated by the root space moderator. Unlike projects, social groups aren't "contained" by anything, so moderation requests are sent to the root space moderator's queue.
Content you can moderate in social groups includes documents, discussion threads (initial posts), and discussion messages (reply posts).
You can specify someone to approve all documents created in the space before they can be published and made visible to other people. With a space approver set, people will still be able to create new documents. Instead of being able to publish the document right away, however, they'll be able to "Submit for approval."
Note that a document can also have document-level approvers who've been designated through its Manage Collaboration page. All approvers must approve before a document is published.
When abuse reporting is enabled, people will have access to a link through which they can report content as abusive. Content reported as abusive will be sent to a moderator's queue so that it can be evaluated. Abuse reporting is a system-wide setting — if it's enabled, it's on for every piece of content on which abuse can be reported.
For more on abuse reporting and moderation, see Moderating Content.
You can "clean up" old discussion content by archiving it. When you turn archiving on for discussions in a space, you can specify how old a thread should before it's archived and whether archived threads are deleted or moved to another space. For example, you could create a space that's expressly for the purpose of holding archived threads.
You can expose certain discussions from your Jive SBS community through web pages that aren't part of Jive SBS by using the Community Everywhere feature. For example, if you've got a web site that describes products offered by your company, you might want to expose discussions related to tips for using the products. Visitors to your product page would be able to view a link to discussions in Jive SBS and optionally see recent posts as well as a box for adding a comment.
If you're wanting to encourage people to participate in your Jive SBS community, Community Everywhere can be a useful enticement. In the admin console, you can enable the feature, limit the sites that can use it, even generate the script code needed to add Community Everywhere links to web pages.
For more about Community Everywhere and how to set it up, see Using Community Everywhere.
Extended properties are name/value pairs that configure particular aspects of a space. Many of these are tied to other settings in the admin console, so that changing the value in the console will change the value of the corresponding property. Generally speaking, you should leave properties unchanged unless you're asked to change it by Jive's support team. You might also change a system property value if the change is part of a larger effort to customize Jive SBS.
Filters and macros both dynamically reformat the contents of messages, announcements and polls. Filters can be applied globally. They are similar concepts but filters can apply to the entire block of text and macros operate on a specific part (for example, {macro}will alter text in here{macro}).
This console page lists the filters and macros installed for your community. At the bottom of the page you can install others.
Use filters and interceptors. A filter dynamically formats message content before it posts to the space. In contrast, an interceptor uses specific criteria to accept, modify, or reject an entire incoming message before it enters the space. Filters and interceptors can be applied to discussions, document comments, and blog comments. Because you can't apply interceptors to documents (and to a blog post only when it's first created), make sure you're comfortable with the employees you allow to author those types of content when setting permissions. When you don't want any part of a post or comment with an offending word to enter the space before an action is taken, use an interceptor instead of a filter.
Apply a profanity filter. This filter automatically detects words in your profanity list and replaces them with ***. The profanity filter is the most commonly used filter; please consider using it. You use the filter by adding the words you want filtered out, then turning on the filter. On the Filters and Macros page, scroll to the profanity filter and click its Settings link. On the filter settings page, enter the list of words you want filtered out of your content. Be sure to select check boxes for the parts of the content you want filtered, then click Save Properties. Back on the Filters and Macros page, click the profanity filter's On button to turn it on.
Use the Permission tab in the admin console to determine who has access to the space, and what they can do there. Permissions are divided into two categories: those governing what kinds of access people have to content in the space and those governing what access people have to administrative or moderation features.
Note that permissions are inherited by sub-spaces. So if you create a space inside a space, the new contained space will have the same permissions setup unless you change them.
If you expect that a space will be accessible to a well-defined group of people (such as those on a particular team), or that certain features will be limited to that group, then you might want to consider using (or creating) a user group. A user group is a way to group people's user accounts into a single group that you can then assign permissions for. It's easier than doing it for each person one at a time. A group admin creates user groups. See Managing Users and Groups for more information.
Space content permissions determine people's access with regard to what they can see and create in the space. This includes whether people can create documents, announcements, and polls -- even whether they can see the space at all.
For more information on setting these, check out Examples: Setting Global and Space Permissions.
Admin and moderation permissions determine what access a person has to administrative and moderation features. You can assign space administrators for the current space or its sub-spaces. You can also designate someone to be a content moderator.
For more on moderation, see Moderating Content.
You have basic access to discussions and document in space from the admin console. A few of these features are also available in the Jive SBS user interface.
Note that settings you make at the root level apply to all social groups. From the document- and discussion-management perspective, you can think of social groups as being contained at the root.
Content moderators also have the ability to edit and delete discussions, as well as make other changes. You can view a list of the discussions in the space, even edit or delete each. As a space administrator, you're also able to edit or delete discussions when you're viewing them in Jive SBS.
For more on moderation, see Moderating Content.
You can view a list of the space's documents. From the list you can edit or delete each. As a space administrator, you're also able to edit or delete documents when you're viewing them in Jive SBS.
Content moderators also have the ability to edit and delete documents, as well as make other changes. For more on moderation, see Moderating Content.
By creating or editing tag groups, you can help ensure that content is organized in the best way for people using the space. Keep in mind as you work that the set of tags in space evolves in response to the way people use them.
Tagging is a way to apply keywords (of a sort) to content. When someone creates a new piece of content, they can apply tags that help capture what the content's about. Over time, as people apply the same tags to similar content, content is easier to find because it's grouped into a category represented by the tag. People can browse the tags to find content. (See the Wikipedia definition of "tag".)
Tag groups are a way to group tags so that all of the content associated with each of the tags is discoverable via the tag group. As a space administrator, you can create new tag groups in the admin console or from the space's overview in Jive SBS. You edit existing groups in the admin console.
You can merge the content from one space into another space. You'll need to be a space administrator for both spaces in order to do this. Merging content moves all of the content into the destination space, mixing it with content that's already in the destination space.
