# Run Automation Rule Scripts and Custom Pages as a specific user **URL:** \ **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:** 5
**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 12, 2026, 5:50pm UTC](https://community.fibery.io/t/run-automation-rule-scripts-and-custom-pages-as-a-specific-user/10978/5 "2026-06-12T17:50:38Z")
> [@ID.000](#): > > With **Run as** , Architects could safely build scripts and custom pages for their own departments, but only within the data they already have access to. They would not need full Admin rights and would not get access to sensitive workspace data. It might be worth getting into some discussion about why architects are having to use scripting. Perhaps you want to add your input to the discussion here: [https://community.fibery.io/n/feedback-needed-scripts-in-automations-that-shouldnt-be-scripts/6560](https://community.fibery.io/n/feedback-needed-scripts-in-automations-that-shouldnt-be-scripts/6560) And potentially the need will diminish if we implement some of these requests… I can see that you previously mentioned [webhooks needing scripts](https://community.fibery.io/n/feedback-needed-scripts-in-automations-that-shouldnt-be-scripts/6560/74), which is thankfully no longer the case, but perhaps there are other things we should look into … --- _[View the full topic](https://community.fibery.io/t/run-automation-rule-scripts-and-custom-pages-as-a-specific-user/10978)._