Skip to main content

Community

Add ability to apply snowflake tags to columns

Answered

Please sign in to leave a comment.

Comments

6 comments

    Hi John,

    Thanks for reaching out and sharing this suggestion! Handling PHI securely is very important, so I completely appreciate why you're looking for a smooth way to automate this across your tables and Quickstart views.

    Do your authorized Snowflake users actually need to view the unmasked, plain-text PHI, or are these columns primarily used for joining records / not needed for analytics at all? 

    Best,

    some snowflake users can see PHI and some cannot.  It's based on their snowflake role. 

    We use snowflake masking policies which automatically hide PHI data,  based on column tags and the user roles.   

    We have one tag that we apply to PHI columns in any database.  Users with PHI access have a special role they can use that will show PHI data.  For anyone else, the masking policies replace the actual values with blanks or hashed values.

    Our problem is if we tag columns in tables created by fivetran syncs, or views create by fivetran transformation,  those tags get lost if fivetran drops & recreates tableview when doing a resync.  

    lI'll add not just apply tags but honor existing tags. Snowflake has the `COPY TAGS` clause you can use with a `CREATE OR REPLACE` statement. So similar functionality if `fivetran` has to recreate a table would be ideal. 

    We desperately want this feature as well, for the same reasons.

    When we tag columns, a re-sync drops the tags and reveals all PHI until we re-tag them.

    This feature offered by Snowflake would be a quick win:  https://docs.snowflake.com/en/release-notes/2026/other/2026-04-02-create-table-copy-tags-ga

    Simply appending "COPY TAGS" to the "CREATE OR REPLACE TABLE" query will cause the replacement table to persist the same tags it had before, which we believe will totally solve the issue.

    +1 - we also use tag based masking policies to redact sensitive data.

    Without tags applied during the table creation there's a window of time where the masking policy doesn't apply - it is something that can be designed around, but would be simpler if we could just have fivetran apply the tags when the table is created

    Hi all,

    Thanks for the feedback, it’s been really helpful. This is now on our roadmap, starting with carrying tags over when a schema change requires recreating the table. I’ll keep you updated here.

    Best regards,