Auros Knowledge Systems › Welcome! Click on a forum topic to locate or start a new discussion › Expanding › Onboarding New Communities
- July 5, 2018 at 12:08 pm #17727Auros Knowledge SystemsKeymaster
There are several reasons that one may want to create more than one Community of Practice within their Auros site. Some of these reasons include: separation by interest, organization, configuration of Knowledge Packets (K-PACs), and different administration privileges.
Separating workflows into separate Communities of Practice (CoP) may not seem obvious to a new user. Having all your information in one place may appear to be advantageous in the beginning, but one may find that, as Auros becomes more integrated into their company’s processes, a single CoP can quickly become cluttered with various K-PACs that may not be useful to every user. For example, the users that work in product design may have no use for K-PACs that detail manufacturing assembly.
When K-PACs need to be applicable to different processes, it is useful to create CoPs that are aligned with users’ specific interests. When K-PACs are split up by interest, users will interact with information that is relevant to their responsibilities. Additionally, users are able to Push/Pull K-PACs to and from other CoPs, if needed, but the modification privileges remain tied to the CoPs that they were created in.
Another advantage to creating several CoPs that are aligned with users’ interests is that it allows various levels of configuration. Different areas of business might want to manage their knowledge differently. Creating a CoP for each area allows each team with common interests to configure how they create, share, reuse, and provision of knowledge packets.
Similarly, admins can configure different administration privileges in different CoPs. Communities may have different business rules and varying degrees of privilege restrictions. Configuring admin privileges based on the CoP means that the data within each community can be easily accessible or more secure, based on the users’ requirements.
Example of an Auros site with several CoPs