This message was deleted.

Sure, • Dictionary: this a place you can define your metrics and common terms • Documents: This is a place you can use for general analysis and documentation. Some examples include ◦ How to onboard to snowflake ◦ Analysis of why DAU is lower ◦ Everything you need to know about x • Collections: This is a place to group any information into one place. Some common use cases for collections are: ◦ Team spaces (data team collection, marketing team collection etc.) ◦ Project spaces ◦ Onboarding collections ◦ Collections for “blessed” dashboards

Are resources in collections only visible to groups assigned to the collection? Or is it more like a tagging solution? (why is this different than tags?)

Correct. We think about the differences between tags and collections as: • Tags: Static ways to label resources with useful context that others will want to know about a resource (ie. PII, Do not delete, dbt data) etc. • Collections: ways to assign visibility and add context around groupings of resources (ie. this is a folder of resources that only the sales team should know about and see)

ooh i didn’t realize adding resources to collections would remove them from general access. Is there a way to turn this off, or does it not apply (aka available to all) if there is no group added?

That’s correct, it does not apply (aka available to all) if there is no group added

Thanks Etai!