# Hide workflows/templates for external users

**URL:** <https://community.silverfin.com/t/hide-workflows-templates-for-external-users/2495>\
**Category:** Templates\
**Created:** [March 7, 2024, 2:15pm UTC](https://community.silverfin.com/t/hide-workflows-templates-for-external-users/2495 "2024-03-07T14:15:11Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![JelleBe](https://avatars.discourse-cdn.com/v4/letter/j/c4cdca/32.png) [@JelleBe](https://community.silverfin.com/u/JelleBe)\
**Post date:** [March 7, 2024, 2:15pm UTC](https://community.silverfin.com/t/hide-workflows-templates-for-external-users/2495/1 "2024-03-07T14:15:11Z")

</div>

Hi,

We would like to add some external users to a specific (client) environment (not client file, but environment). But we want to limit the access of the external users.

What’s the most efficient way to limit the access to templates and workflows?

Thanks in advance.

Kind regards  
Jelle

---

<div class="post-metadata">

**Author:** ![JelleBe](https://avatars.discourse-cdn.com/v4/letter/j/c4cdca/32.png) [@JelleBe](https://community.silverfin.com/u/JelleBe)\
**Post date:** [July 8, 2025, 12:03pm UTC](https://community.silverfin.com/t/hide-workflows-templates-for-external-users/2495/2 "2025-07-08T12:03:51Z")

</div>

Anyone? Maybe you @Romy_Vermeeren 🙂 ?

Can we limit the access to templates for external users?

---

<div class="post-metadata">

**Author:** ![Romy\_Vermeeren](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.silverfin.com/romy_vermeeren/32/2295_2.png) [@Romy\_Vermeeren](https://community.silverfin.com/u/Romy_Vermeeren)\
**Post date:** [July 9, 2025, 7:48am UTC](https://community.silverfin.com/t/hide-workflows-templates-for-external-users/2495/3 "2025-07-09T07:48:11Z")

</div>

Hi @JelleBe

User access is managed on a file level, not on template level. You can find more info on external contributors in our general knowledge base. [Silverfin Support](https://silverfin.freshdesk.com/en/support/home)

The only access you could “limit/grant” with Liquid in templates is hiding or showing code based on the email address of the user. Not that I recommend it.

KR  
Romy

---

<div class="post-metadata">

**Author:** ![JelleBe](https://avatars.discourse-cdn.com/v4/letter/j/c4cdca/32.png) [@JelleBe](https://community.silverfin.com/u/JelleBe)\
**Post date:** [July 10, 2025, 11:51am UTC](https://community.silverfin.com/t/hide-workflows-templates-for-external-users/2495/4 "2025-07-10T11:51:02Z")

</div>

Ok thanks Romy. For a good understanding we cannot hide template X and template Y for external users for all files within an environment?

Thanks.  
Jelle

---

<div class="post-metadata">

**Author:** ![Romy\_Vermeeren](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.silverfin.com/romy_vermeeren/32/2295_2.png) [@Romy\_Vermeeren](https://community.silverfin.com/u/Romy_Vermeeren)\
**Post date:** [July 10, 2025, 12:08pm UTC](https://community.silverfin.com/t/hide-workflows-templates-for-external-users/2495/5 "2025-07-10T12:08:14Z")

</div>

Hi @JelleBe

No you can’t query with liquid whether that user is internal or external.  
[user](https://developer.silverfin.com/docs/user) we’re limited to name and email.

You could… if you really want to… have a check on the email and whether it contains “@externalcompany.com” and incorporate that in the autohide formula on template X and Y.  
Or the other way around check whether the email has “@be.ey.com”.

But I think you can already see the limitations with that workaround.