Administering the Community / Configuring Content-Related Settings |
Blogs and blog content can be managed in several ways depending on their location.
Generally speaking, blogs are managed by their authors. They can also be managed by the owners of the place (space, project, or social group) where the blog lives. For some blogs, including global blogs such as system and personal blogs, you can use the admin console to perform such tasks as creating blogs and managing its comments.
A blog can live in one of several different contexts. By default, these contexts include the global context and each of the places that can contain a blog. This is important because a blog's context determines how you manage permissions for the blog, how you configure its settings, and so on.
The table below describes how each of the areas is exposed based on the blog's context.
Blog Type | Scope | Creating | Permissions | Management | System-Wide Settings |
---|---|---|---|---|---|
System blog | Global; not contained in any space. A system blog is not connected with any particular space or person. | Administrators can create blogs and assign people as authors so they can post to it. | Administrators can set specific permissions, such as for creating and viewing system blogs. For more information, see Managing Blog Permissions. | Blog authors and administrators can manage the blog. | Settings are shared by all blogs. |
Personal blog | Global; not contained in any space. A personal blog is associated with a particular user, who is its owner. A user can have only one personal blog. | Administrators can create a personal blog using the Admin Console. A person who has been assigned permission to do so can also create their blog in the community. Only the blog's owner can post to it. | Administrators can set specific permissions, such as for creating and viewing personal blogs. For more information, see Managing Blog Permissions. | A blog's author can manage the blog. | Settings are shared by all blogs. |
Space blog | Associated with a particular space. A space can have only one blog. | A person with permission to administer a space can create a blog there. The blog's author list is determined by space permissions. For more information, see Managing Space Permissions. | Administrators can set fine-grained access for a space's blog. For more information, see Managing Space Permissions. | Blog authors and space administrators can manage the blog. | Settings are shared by all blogs. |
Project blog | Associated with a particular project (which is contained by another place). | Settings are inherited from the space that contains the project. | Settings are inherited from the space that contains the project. | Settings are inherited from the space that contains the project. | Settings are shared by all blogs. |
Social group blog | Associated with a social group. | A person with permission to administer a social group can create a blog there. Every member of the social group has full access to the blog's features except blog management. | Permissions are not editable. They provide full access to the blog for every member of the group. | Group administrators can manage the blog. | Settings are shared by all blogs. |