# \[Question\]How to use Project Scripts

**URL:** <https://forum.inductiveautomation.com/t/question-how-to-use-project-scripts/23354>\
**Category:** Ignition Early Access\
**Created:** [March 14, 2019, 7:23pm UTC](https://forum.inductiveautomation.com/t/question-how-to-use-project-scripts/23354 "2019-03-14T19:23:36Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\
**Post date:** [March 14, 2019, 8:00pm UTC](https://forum.inductiveautomation.com/t/question-how-to-use-project-scripts/23354/3 "2019-03-14T20:00:34Z")

</div>

You no longer reference “project” scripts with `project.package_name.method_name` any longer, unless your “Scripting/Project Library/\<package\_name\>” is actually “Scripting/Project Library/project”  
In the following screenshot I would reference THIS project’s scripts with `project.Security.<method_name>`  
 ![56%20PM](https://us1.discourse-cdn.com/inductiveautomation/original/2X/7/71b07ebefbe03e7b5917f618a7bbe860559eb958.png)  
And I would access shared scripts (which are located in the parent project) with `shared.<package_name>.<method_name>`

**Notes:**

- Inherited scripts are always under “shared” regardless of the parent project’s name.
- “project” only happens to be what I’ve named the package - you can name it anything else (within reason) and reference it with `<high_level_package_name>.<low-level_package_name>.<method_name>(**args)`

---

_[View the full topic](https://forum.inductiveautomation.com/t/question-how-to-use-project-scripts/23354)._