About this demo
This resource helps teams clarify expectations around how Atlan will be used, who should contribute, and how responsibilities should be divided. By posing practical questions and providing best-practice suggestions, it guides organizations to plan their governance, ownership, and enrichment strategies more effectively.
The guide starts by asking teams to define sources of truth for different types of metadata. It suggests managing column and table descriptions in their creation software (e.g., dbt YAML files) and syncing them to Atlan, while business terms and KPI metric definitions should be maintained in the Atlan glossary for alignment and visibility. It also encourages enriching assets with additional resources like ERD diagrams or requirements documents, especially for frequently used models, to improve context and understanding.
Next, it covers contributors and ownership. The document advises looking across the org chart to identify partners from different teams, assigning owners to assets by domain or subject area, and using Atlan’s Usage tab to find top users as potential owners. For larger organizations, it recommends distinguishing between contributor and owner types—such as Technical Owners and Business Owners—using custom metadata and aligning responsibilities to frameworks like RACI or CRUD permissions.
Finally, the resource emphasizes clear rules and accountability. Teams are encouraged to define when documentation is considered “done,” outline responsibilities in a “How to use Atlan” glossary, and establish processes for handling edits and corrections. Suggestions include looping in asset owners for errors and leveraging Jira integrations to manage change requests.
By addressing these questions up front, organizations can create transparency, avoid confusion, and build a scalable governance model in Atlan where roles, responsibilities, and expectations are clearly defined and understood.