# Global Variables

**URL:** <https://community.fibery.io/t/global-variables/2129>\
**Category:** Ideas & Features\
**Created:** [October 19, 2021, 1:47pm UTC](https://community.fibery.io/t/global-variables/2129 "2021-10-19T13:47:56Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Paul\_Cleghorn](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/paul_cleghorn/32/23_2.png) [@Paul\_Cleghorn](https://community.fibery.io/u/Paul_Cleghorn)\
**Post date:** [October 19, 2021, 1:47pm UTC](https://community.fibery.io/t/global-variables/2129/1 "2021-10-19T13:47:56Z")

</div>

Do you have any plans to create global variables? I guess this is linked to the concept of shared code snippets. It would be great if I could create/set a variable for a given workspace and then use it in formulas.

---

<div class="post-metadata">

**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\
**Post date:** [October 19, 2021, 4:33pm UTC](https://community.fibery.io/t/global-variables/2129/2 "2021-10-19T16:33:55Z")

</div>

Related:

> [@Modules for scripting](https://community.fibery.io/t/modules-for-scripting/2123):
>
> It would be quite useful to have modules capability for scripting, so we could define our own modules for the workspace, which could then be easily included wherever needed in Button/Rule scripts.

> [@Can we have a "code library" for a Workspace?](https://community.fibery.io/t/can-we-have-a-code-library-for-a-workspace/1354/6):
>
> @mdubakov Yes @Chr1sG - that is what I meant! The point is to avoid copy-paste and have just one copy of your codebase/library that can be referenced globally wink

---

<div class="post-metadata">

**Author:** ![carson](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/carson/32/7503_2.png) [@carson](https://community.fibery.io/u/carson)\
**Post date:** [December 29, 2023, 10:37pm UTC](https://community.fibery.io/t/global-variables/2129/3 "2023-12-29T22:37:05Z")

</div>

Oh, this would be awesome. Right now, a workaround is to use scripts and loop through a “Config” database that has one entity. But that complicates the scripts and formulas quite a bit.

---

<div class="post-metadata">

**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\
**Post date:** [December 31, 2023, 9:20pm UTC](https://community.fibery.io/t/global-variables/2129/4 "2023-12-31T21:20:20Z")

</div>

FYI I have developed an [app to remotely manage script automations](https://community.fibery.io/t/beta-testers-wanted-for-fibery-script-management-tool/5466) on your local machine, allowing you to pull them from Fibery, manage them locally, and push them back to your Workspace.

LMK if you’re interested in testing this app.

---

<div class="post-metadata">

**Author:** ![carson](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/carson/32/7503_2.png) [@carson](https://community.fibery.io/u/carson)\
**Post date:** [December 31, 2023, 9:36pm UTC](https://community.fibery.io/t/global-variables/2129/5 "2023-12-31T21:36:17Z")

</div>

Oh heck yes. Send that my way!