# Access templates at the database level

**URL:** <https://community.fibery.io/t/access-templates-at-the-database-level/9201>\
**Category:** Ideas & Features\
**Created:** [July 14, 2025, 4:32pm UTC](https://community.fibery.io/t/access-templates-at-the-database-level/9201 "2025-07-14T16:32:15Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\
**Post date:** [July 14, 2025, 4:32pm UTC](https://community.fibery.io/t/access-templates-at-the-database-level/9201/1 "2025-07-14T16:32:15Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![antoniokov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/antoniokov/32/201_2.png) [@antoniokov](https://community.fibery.io/u/antoniokov)\
**Post date:** [July 31, 2025, 2:39pm UTC](https://community.fibery.io/t/access-templates-at-the-database-level/9201/2 "2025-07-31T14:39:48Z")

</div>

> [@RonMakesSystems](#):
>
> 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.

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).

> [@RonMakesSystems](#):
>
> 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.

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](https://the.fibery.io/@public/User_Guide/Guide/Automatically-Share-Entities-with-linked-Groups-395), 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.