# Global-props folder

**URL:** <https://forum.inductiveautomation.com/t/global-props-folder/29165>\
**Category:** Ignition\
**Created:** [October 17, 2019, 3:36pm UTC](https://forum.inductiveautomation.com/t/global-props-folder/29165 "2019-10-17T15:36:43Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jonathan](https://avatars.discourse-cdn.com/v4/letter/j/aeb1de/32.png) [@Jonathan](https://forum.inductiveautomation.com/u/Jonathan)\
**Post date:** [October 17, 2019, 3:36pm UTC](https://forum.inductiveautomation.com/t/global-props-folder/29165/1 "2019-10-17T15:36:43Z")

</div>

In an Ignition project I see a folder called global-props, which stores a binary file. What is the folder global-props used for?

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [October 17, 2019, 3:41pm UTC](https://forum.inductiveautomation.com/t/global-props-folder/29165/2 "2019-10-17T15:41:16Z")

</div>

It stores resources of the “global-props” type. All resource types are stored under a folder named for the type. You can’t really do anything with this one.

---

<div class="post-metadata">

**Author:** ![Jonathan](https://avatars.discourse-cdn.com/v4/letter/j/aeb1de/32.png) [@Jonathan](https://forum.inductiveautomation.com/u/Jonathan)\
**Post date:** [October 17, 2019, 3:46pm UTC](https://forum.inductiveautomation.com/t/global-props-folder/29165/3 "2019-10-17T15:46:08Z")

</div>

You lost me at “global-props”. What is a “global-props” type? Do you have an example?

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [October 17, 2019, 3:49pm UTC](https://forum.inductiveautomation.com/t/global-props-folder/29165/4 "2019-10-17T15:49:10Z")

</div>

Eh, we’re veering into internal implementation details here, but it’s the resource type that stores some of the “core” project properties like client poll rate, default datasource, default provider, required roles, etc…

It’s saved in an opaque binary format right now, which is why there’s nothing _you_ can really do with it.

---

<div class="post-metadata">

**Author:** ![AlexandreFG](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/alexandrefg/32/74162_2.png) [@AlexandreFG](https://forum.inductiveautomation.com/u/AlexandreFG)\
**Post date:** [March 25, 2025, 5:25pm UTC](https://forum.inductiveautomation.com/t/global-props-folder/29165/5 "2025-03-25T17:25:42Z")

</div>

Can I ignore the JSON file from this folder if I am using git to versioning the project?

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [March 25, 2025, 5:27pm UTC](https://forum.inductiveautomation.com/t/global-props-folder/29165/6 "2025-03-25T17:27:48Z")

</div>

You might get away with ignoring modifications to it, but if it doesn't exist then the resource would no longer be valid.

---

<div class="post-metadata">

**Author:** ![AlexandreFG](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/alexandrefg/32/74162_2.png) [@AlexandreFG](https://forum.inductiveautomation.com/u/AlexandreFG)\
**Post date:** [March 25, 2025, 9:30pm UTC](https://forum.inductiveautomation.com/t/global-props-folder/29165/7 "2025-03-25T21:30:42Z")

</div>

Thanks a lot!

I created a **hook** to handle the initial creation of `resource.json` files and then flagged those files as **"assume-unchanged"**. This way, future commits will ignore changes to those files while still keeping them in the repo.

Just out of curiosity, I tested ignoring the `resource.json` file inside a **View** folder (Perspective), and when I cloned the repository again, the view turned into a regular **folder** , haha. So you were 100% right when you said that wouldn't work! 😅
