Version update: March 31, 2025 What is the Collibra Community? The Collibra Community is your dedicated space to learn best practices, share insights and collaborate with 11,000+ data citizens worldwide. You can use the Community to access valuable content, tutorials, best practices, product documentation and more. How do I create an account and join the Community? Visit community.collibra.com and click on the person icon in the top left corner to register for the Community. How do I log in to the platform? Log in with this login link and use the SSO method, which allows you to use the same credentials as your other Collibra sites without creating new logins and passwords. How do I update my profile? Once you are logged into the Community, you can view your profile in the navigation menu. Click the person icon to the right of the bell icon. Click “View profile” and edit using the green “Edit” button. We encourage you to welcome your profile with a headshot and About description for a more engaged Community experience. How do I post a discussion? Visit community.collibra.com/discussion/ Click your preferred Category or view all categories from the left side panel Click ‘Start a discussion’ to create a post Visit this discussion post for more information. Can I edit my notification settings? Yes, you can edit your notification settings and customize your preferences for receiving updates, alerts, and notifications related to discussions, mentions, and activity within the community. Click your profile icon > “Profile Settings” > “Updates” to explore your options. How do I search for specific topics or discussions? Use our search bar to search for specific topics or visit the discussion page to view all of our active forums. How do I report bugs or issues on the new platform? If you encounter any bugs or issues on the new platform, please report them to [email protected]. Your feedback is invaluable in helping us improve the platform for everyone. What should I do if I encounter inappropriate behavior or content? If you encounter inappropriate behavior or content in the Collibra Community, please let us know by clicking on a discussion post and “Mark as Spam” or “Flag as Inappropriate.” You can also email us directly at [email protected] . Why can't I find my previous gamification points and badges in the Community? We recognize the importance of reputation points as a measure of community engagement. We are making improvements to our gamification to improve your Community experience. We plan to bring back your gamification information soon. Check back for more updates! How can I provide feedback on the Community? We strive to provide our community members with the best community experience possible. We would love your feedback to help identify areas for improvement and gather suggestions for new features and enhancements. We send a bi-annual Community member survey in July and December of each year. You can also email us directly at [email protected]. What are certified Data Citizen® User Groups? Data Citizens® User Groups are interactive virtual groups designed to bring together fellow Collibra data enthusiasts to share insights, collaborate on best practices and drive innovation. Certified groups gain exclusive access to resources, support, beta testing, product roadmaps and expert guidance, with Collibra providing the tools for success. How do I join a user group? Browse our user group list and select the group you are interested in joining. Sign up via the dedicated landing page, and we’ll send you next steps from there. Once you join, you can participate in discussions, attend events and connect with other members. How do I stay up to date with Community news? The Collibra Community sends our members a quarterly newsletter, including the latest community news, events and more. We also post weekly announcements on the Community. Domain structure is a critical aspect of a well-designed operating model. The recommendations here will help you design your domain structure to achieve these objectives. Impact Following these best practices will support platform adoption by improving: Platform usability. Clarity of governance responsibilities. Ease of system. Best practice recommendations Domains are collections of assets with similar characteristics, attributes or similar responsibilities or roles. When deciding how to group assets into domains, think about which assets will be acted on similarly within the system. For example, assets that have the same governance process or are assigned similar responsibilities. Since assets can only be a member of a single domain, you may run into situations where it is hard to decide between 2 or more possible domain assignments. For example, an asset that might have stewards in a geographically defined domain, such as the North America Group, and a business-function-defined domain, like Finance. In these cases, you should choose the domain of the ultimate “owner” of the asset. These decisions will sometimes drive the need to create new communities or even shared communities. For more information, go to the Community structure best practice article. Only create domains when you have a set of assets which will belong to them. Empty domains can cause clutter and confuse your users. Domain names must be unique within a single community but can be duplicated across communities. However, it is best to name each domain uniquely. For instance, instead of having a Glossary domain within multiple communities, give them specific names such as Finance Glossary and Marketing Glossary. Add a description to your domain. It is a best practice to provide a clear and useful description for users who may not otherwise be familiar with the content. While all domains are visible to everyone by default, it is possible to hide domains from view based on users or groups. However, it is a best practice to use this feature sparingly and only where it is clearly required. For example, a domain of sensitive reference data, like salary scales should have restricted visibility. While enabling automatic hyperlinking is not recommended, when using it, it is necessary not only to enable the system-level automatic hyperlinking but also specifically for the domains whose assets you want to be hyperlinked. This should be applied judiciously to smaller, business asset domains rather than broadly to avoid performance issues since the links are dynamically maintained. Validation criteria The Operating Model Diagnostic workflow, which is available from your Customer Success representative, will help identify empty domains and domains without descriptions, as well as domains without stewards and domains where automatic hyperlinking is enabled. The Operating Model Reverse Engineering , OMRE, available in Marketplace, can make it easier to find duplicate-named domains across communities. Additional information For more information, go to the following resources: See the Collibra Documentation Center for more information on any of the above elements. You can run the OMRE to help identify the existence of duplicate domain names across communities. Domain structure and community structure work together so our Community structure best practice is another useful resource. Limit the number of custom asset types and statuses to optimize both operating model maintenance and user experience. Impact Use out-of-the-box (OOTB) asset types as much as possible to ensure maximum compatibility with future product features. Custom asset types should be used to meet your specific business requirement, but it is best to avoid using too many. If there are a lot of custom asset types, you should review them and search for duplicates, as well as overlapping or unused asset types and confirm that custom asset types cannot be replaced by the use of OOTB asset types. Ensure that you have the relevant asset types available before creating a custom asset type. This is to avoid creating unused custom asset types which can complicate the governance of the operating model. Introduce a Data Office governance process for the creation of custom asset types. This process should provide guidance on when a custom asset type is absolutely necessary and reduce the risk of unused asset types. You should also review the number of users with permission to create custom asset types, as too many users can result in unused, duplicated or unnecessary custom asset types. Custom statuses are encouraged to support the asset life cycle. However, keep the number of possible statuses for a given asset type as small as possible to avoid confusing users. If there are more than 30, consider consolidating to fewer statuses. Topic area Operating Model → Metamodel → Asset Model → Asset types Operating Model → Execution and Monitoring Concepts → Status types Monitoring this practice For customers with established production models: Run the Operating Model Reverse Engineering , or OMRE, on a regular basis to identify the elements in this article. Contact your Collibra representative to run the Operating Model Diagnostic. Additional information For more information, go to the following resources: Asset types Overview of packaged asset types Create an asset type
