Community Resources
Participate
Learn
Support
User Groups and Events
We’re excited to share the improved Collibra Community ! Based on feedback from our members, we’ve made big improvements to enhance your experience and make it easier to collaborate, find information, and stay connected. What’s new? A modern, updated design for more straightforward navigation A better forum experience with improved discussion filtering A more robust customer user group experience for deeper engagement Improved email communications and notifications to keep you informed A new Welcome Center to help members get started Note: As we update the back-end, your points and badges will not be available on the platform until mid-to-late 2025. Once complete, your gamification information will be restored. What’s stayed the same? The Community URL, email ([email protected] ), and login process remain unchanged. All discussions, knowledge base article,s and resources are still available If you have any questions, please reach out to [email protected] . We’re here to help! Please see this post on how to start a discussion We can’t wait for you to explore the new Collibra Community! Best, The Collibra Community Team Happy Friday, Collibra Community Before you head into the weekend, here’s your weekly roundup of what’s happening across the Collibra. Whether you’re looking to sharpen your skills, connect with fellow Data Citizens, find out about events or catch up on recent highlights, you’ll find it all right here. Here’s what’s ahead this week: Collibra | Seattle Customer meet-up | June 12, 2025 | Join us for an engaging Seattle customer meetup, featuring interactive sessions and discussions with fellow data governance professionals. Webinar | BCBS 239: Why now? Navigating the resurgence with Collibra and Deloitte | June 11, 2025 | Collibra Workflow Developer Certification | Prove your Workflow expertise by earning the Workflow Developer certification! Learn more about the benefits, requirements, and learning resources here. On-demand webinar | NAB is treating data like electricity with Collibra and Databricks to power innovation | Unlock this on-demand webinar to learn how NAB is transforming its data strategy to drive innovation, compliance, and customer-centricity across Australia and New Zealand using Collibra and Databricks Upcoming webinar | Data quality and observability: creating confidence in your data warehouse and lake | May 21, 2025 | Your data warehouse or lake is a primary data source for your business intelligence and analytics, AI and agents, data products, and regulatory reporting. Yet 62% of organizations say data quality needs improvement in the year ahead. In this webinar, we will demonstrate how Collibra can assist you. That’s a wrap for this week’s highlights! Got questions, ideas, or something to share? Reach out—we’re always excited to hear from you ([email protected] ) Hey there, How bad would it be performance-wise (or otherwise) to have ~150-200 multi-day workflows running at one time? For context, I'm considering whether we should build complex, multi-day approval workflows in Collibra vs. another tool. Coming from an Appian background, my approach has always been to store request state (created, approved, returned for revision, etc.) in a record/database entity, and use "workflows" only to move the request between states (kicking a new workflow off when someone takes action, and completing it when the action is finished & new request state is written to the database). Is this a common practice with Collibra workflows as well? If not, have you seen/heard about any performance issues that may come from hundreds of workflows sitting in memory for days at a time? Thank you!
