Access templates at the database level

Ideas & Features
1

Giving access to related entities can only be done on the entity level, I would like to give access to emails RELATED TO the contacts. Giving someone access to all the contacts, but only access to emails that are related to contacts, not all emails.

Bringing the power of access templates to database access.

I could set an automation that links to a user group, and add everyone to that user group, and just work with entity level access. But if it could be built in, that would be even better.

The use case is mainly for email integration. Syncing everything allows the whole team to see all your emails, but maybe we just want people to see emails related to the contacts you have in Fibery. This would solve this!

Maybe a nice flow could be:

  1. Make the access template.
  2. Assign people or groups / people or group fields.
2 Likes
2

We have a similar use case ourselves: granting access to Emails related to Workspaces and Candidates. We have ended up providing Database access to all Emails and just not syncing anything that shouldn’t be shared (we use sync label in Gmail for this).

If selective syncing is not an option (e.g., you use some Emails in your private workflows), then automatic access via a relation to a User Group, coupled with the automations you’ve mentioned, would be the best workaround.

Access templates on the Database level with de facto entity-level access propagation are unlikely.

2 Likes