Recent Posts from LiveConnections
title:Peoplebody:People (and their information) are the reason the LiveConnect platform exists. All content within a LiveConnect powered community is created and owned by its Members.
All Members in a LiveConnect Community have a display name, an associated avatar and a rich profile that may include: video, images, text areas and much more. Each Member has a "home page" that shows his or her personal profile and a record of his contributions to the community - which Applications, Types, Posts, Groups, and Comments are his.
The structure of a member's profile is defined by the Community Administrator. Example profile fields include: Name, Address, Phone Number, Email Address, Company, Title, Instant Message ID, Photo, T-shirt Size, vCard Attachment, Favorite Movie. Each Member can permission individual profile fields to the appropriate audience (wwww public, community, network, private).
A sample member profile. Note the permission icons on each field.
Members can belong to an infinite number of Groups. If empowered to do so they may create and manage Groups and/or Applications either from a curated template or on a custom ad hoc basis. Members can be individually permissioned to view and/or post new information in specific Applications, or can be permissioned to the Application as part of a Group.
Some LiveConnect powered communities allow Guests to browse appropriately permissioned content within the community. Guests are anonymous and do not have a personal profile, cannot post or comment in the community, and can view only the content that has been explicitly made available to non-members.
See a list of Members in this Community, or see your own network.
Below: a sampling of user images
navigation:-- previous feature | index | next feature -->
- title:Groupsbody:
Groups are containers for multiple members. Community Members can create Groups and, as Group Owners, add other members to the Group. (See Administrative Powers for more details.) Groups provide several key benefits:
- Better organization of the community. As an example, let's say that your company, a motorcycle manufacturer, has a thriving on-line community. Groups organized by location--"Bay Area Bikers", "Southwest Bikers", "Central Florida Bikers," etc.-- enables community members to a) identify other members with the same interests and b) to locate and share relevant resources and information much more efficiently. Alternatively, if members of a community are all employees of the same organization, Groups such as 'Product Marketing,' 'Engineering', or 'Sales' provide additional organization to the community.
- Reduced implementation burden. Groups may be templatized into a variety of formats and configurations and then quickly deployed as new community areas. For instance: "Bay Area Bikers" wants to start a new group. Through a group template they could start a new group with a: blog, discussion area, media library, contact form, calendar, etc... by simply completing a short form. This allows for quick, and potential, co-creation of large areas within a given community without the need to engage IT resources.
- Easier permissioning and information management. Create a new Application and permission it to the entire 'Bay Area Bikers' Group in one step. This is dramatically easier and less prone to error than individually inviting each of the members from the Bay Area.
- Easier invitation and spin-up process. New members to the community can be invited to one or more Groups during the invitation process. They can then instantly access any information that the Group(s) can access.
- Better organization of a Member's Network. Groups provide a mechanism for Members to organize their personal Network into, for example, 'Friends', 'Family', 'Work' etc.
Individual members can belong to an infinite number of groups.
Community administrators can define any number of Group Types, so that "Internal Departments" can be browsed separately from "Customer Segments" or whatever other Group sub-sets are relavant in the community.
Below: The HiveLive Group
navigation: - title:Hives / Community Applicationsbody:
Hives or Community Applications can be used to manage and share any type of information (e.g., discussion areas, product reviews, testimonials, community feedback on new product ideas, press clippings, bookmarks, notes, journal entries, contacts, or company profiles, profiles, even favorite wines, coffees, chocolates). Applications are easy to configure and can also be used for a wide range of familiar, community-based applications (e.g., blogs, forums, feedback forms, knowledge repositories, FAQs, and more).
Applications are the permissionable containers that hold and organize information in a LiveConnections Community in the form of semi-structured Posts. They can be public, private, or selectively shared with other members. Because of the flexibility of the posting structure of an Application each community can easily introduce domain specific language and interactions that increase connection and communication with community members.
An Application is owned by the Member who creates it, who can share administrative rights with other members, empowering them to add or remove Members or Groups (or, more generally, change visibility settings), assign Types and Tags, delete Comments, or change the default summary page view settings of an Application.
Community administrators can define any number of Application Types so that 'blogs' can be browsed separately from 'forums' or 'recipe exchanges' or whatever other Application Types are relevant to the community.
Below: a Discussion Area
Below: an Idea Center
navigation:
Resources
- A introduction to the Social Platform
- Catchy tagline
- thoughts on social software, design thinking, and business innovation, by John Kembel
- Create a quick and easy blog for your project, your department, or for yourself
- poetry 2.0
[JOIN] to participate
Join the HiveLive Community to comment on the Social by Design blog.
Welcome to the HiveLive Community
Read more about the Social by Design blog.
