# Global variables

**URL:** <https://forum.ansible.com/t/global-variables/36510>\
**Category:** AWX Project\
**Created:** [April 5, 2022, 11:46am UTC](https://forum.ansible.com/t/global-variables/36510 "2022-04-05T11:46:02Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bill\_Nolf](https://avatars.discourse-cdn.com/v4/letter/b/a9adbd/32.png) [@Bill\_Nolf](https://forum.ansible.com/u/Bill_Nolf)\
**Post date:** [April 5, 2022, 11:46am UTC](https://forum.ansible.com/t/global-variables/36510/1 "2022-04-05T11:46:02Z")

</div>

I want be able to create global variables in tower that can be used across multiple templates, so I don’t have to declare the variable value for each template. Is there a way to do this?

thanks

---

<div class="post-metadata">

**Author:** ![jowestco](https://avatars.discourse-cdn.com/v4/letter/j/85f322/32.png) [@jowestco](https://forum.ansible.com/u/jowestco)\
**Post date:** [April 13, 2022, 8:09pm UTC](https://forum.ansible.com/t/global-variables/36510/2 "2022-04-13T20:09:43Z")

</div>

There isn’t a global “extra\_vars” per say but there are global environment variables on the Settings =\> Jobs page.  
You could set environment variables there and then any playbook being run would pick them up.

-John

---

<div class="post-metadata">

**Author:** ![Wei-Yen\_Tan](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/wei-yen_tan/32/4111_2.png) [@Wei-Yen\_Tan](https://forum.ansible.com/u/Wei-Yen_Tan)\
**Post date:** [April 13, 2022, 8:26pm UTC](https://forum.ansible.com/t/global-variables/36510/3 "2022-04-13T20:26:42Z")

</div>

This is interesting. Are you saying that the environment variable changes into a variable??

---

<div class="post-metadata">

**Author:** ![jowestco](https://avatars.discourse-cdn.com/v4/letter/j/85f322/32.png) [@jowestco](https://forum.ansible.com/u/jowestco)\
**Post date:** [April 14, 2022, 1:23pm UTC](https://forum.ansible.com/t/global-variables/36510/4 "2022-04-14T13:23:50Z")

</div>

It does not change into a variable “on its own” but your playbook should be able to read the environment variable using the env lookup plugin.  
[https://docs.ansible.com/ansible/latest/collections/ansible/builtin/env\_lookup.html](https://docs.ansible.com/ansible/latest/collections/ansible/builtin/env_lookup.html)

-John