# Run Automation Rule Scripts and Custom Pages as a specific user

**URL:** <https://community.fibery.io/t/run-automation-rule-scripts-and-custom-pages-as-a-specific-user/10978>\
**Category:** Ideas & Features\
**Tags:** permissions\
**Created:** [June 12, 2026, 10:56am UTC](https://community.fibery.io/t/run-automation-rule-scripts-and-custom-pages-as-a-specific-user/10978 "2026-06-12T10:56:08Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [June 15, 2026, 1:20pm UTC](https://community.fibery.io/t/run-automation-rule-scripts-and-custom-pages-as-a-specific-user/10978/7 "2026-06-15T13:20:08Z")

</div>

> [@ID.000](#):
>
> a simple permission model for **Automation Rule Scripts** and **Custom Pages / Future Apps**.

I expect that Custom Pages/Apps will not have the option to Run as… another user. They are already designed to run as the logged in user (just as Buttons do) and I’m not sure what the use case is for this (apart from as a subset of this [general behaviour](https://community.fibery.io/n/view-as-another-user-for-admins/6111)).

> [@ID.000](#):
>
> Right now, if a team has Architects or junior automation builders, there are two bad options:
> 
> 1. Only Admins can build Automation Rule Scripts and Custom Pages.

We plan to allow Architects to create Custom Apps.

---

_[View the full topic](https://community.fibery.io/t/run-automation-rule-scripts-and-custom-pages-as-a-specific-user/10978)._