This message was deleted.

@busy-fireman-86564 I'd recommend the following: 1. Create a "Data Team" which you can create as a group in https://app.secoda.co/settings/members 2. Update the global share settings in https://app.secoda.co/settings/sharing that only shares resources by default with the Data Team 3. If you open the share settings (top right corner of collection page) for a collection that contains the dictionary terms that you'd like the share, then you can set specific share permissions on that collection which will take precedent over the global share settings

I changed the global permissions to Data Team.

@busy-fireman-86564 after investigating, the issue is that we are not able to link the user that's requesting the Slack search request to the user in Secoda. There are two options that we can do to resolve this: 1. We can infer who the user is based on their Slack email, but this could be inaccurate if there are inconsistencies 2. We can allow a user to manually specify their Slack ID in Secoda but this requires more user input We can prioritize #1 since I imagine it will work for almost all cases since the users sign up to Secoda with their business email.

Ohhh I was hoping I could get there through the slack channel. I connected the Sigma Users channel to a separate

#tmp-secoda-sigma-users

. #1 is for sure the preferred option of the two you mentioned, we all use a consistent email across SaaS products.

It will send updates for the collection, i.e, description change, to the respective Slack channel

ah