# Navigate to a page does not trigger page startup script

**URL:** <https://forum.inductiveautomation.com/t/navigate-to-a-page-does-not-trigger-page-startup-script/115588>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [May 18, 2026, 7:53pm UTC](https://forum.inductiveautomation.com/t/navigate-to-a-page-does-not-trigger-page-startup-script/115588 "2026-05-18T19:53:49Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Eugene49](https://avatars.discourse-cdn.com/v4/letter/e/c6cbf5/32.png) [@Eugene49](https://forum.inductiveautomation.com/u/Eugene49)\
**Post date:** [May 18, 2026, 7:53pm UTC](https://forum.inductiveautomation.com/t/navigate-to-a-page-does-not-trigger-page-startup-script/115588/1 "2026-05-18T19:53:49Z")

</div>

Please remind me, is this really the case?

using system.perspective.navigate(), it does not trigger page startup script??

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [May 18, 2026, 7:59pm UTC](https://forum.inductiveautomation.com/t/navigate-to-a-page-does-not-trigger-page-startup-script/115588/2 "2026-05-18T19:59:08Z")

</div>

Not in a single tab. Try opening a new tab.

(A "page" life cycle is not tied to a particular URL, but to the unique browser environment it opens within.)

---

<div class="post-metadata">

**Author:** ![Eugene49](https://avatars.discourse-cdn.com/v4/letter/e/c6cbf5/32.png) [@Eugene49](https://forum.inductiveautomation.com/u/Eugene49)\
**Post date:** [May 18, 2026, 8:08pm UTC](https://forum.inductiveautomation.com/t/navigate-to-a-page-does-not-trigger-page-startup-script/115588/3 "2026-05-18T20:08:10Z")

</div>

Yes, on same tab, is what i meant..

I have existing implementation on page startup that check if user have access on page then redirect. But has a loop hole, when he has access on other page and navigate to desired page.

I wonder where you should add page DB-based authorization?

Thanks.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [May 18, 2026, 8:10pm UTC](https://forum.inductiveautomation.com/t/navigate-to-a-page-does-not-trigger-page-startup-script/115588/4 "2026-05-18T20:10:14Z")

</div>

You should be using native view permissions, so that we enforce invariants for you:

> **[Perspective Views Security​ - Security in Perspective | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.3/ignition-modules/perspective/security-in-perspective#perspective-views-security)**
>
> Security in Perspective is managed through Identity Providers (IdP). IdPs offers a way for users to log in to Ignition using credentials stored outside of Ignition. This level of security is set up through the Gateway. Setting up security is covered...

---

<div class="post-metadata">

**Author:** ![Eugene49](https://avatars.discourse-cdn.com/v4/letter/e/c6cbf5/32.png) [@Eugene49](https://forum.inductiveautomation.com/u/Eugene49)\
**Post date:** [May 18, 2026, 8:14pm UTC](https://forum.inductiveautomation.com/t/navigate-to-a-page-does-not-trigger-page-startup-script/115588/5 "2026-05-18T20:14:02Z")

</div>

But this not scalable, reason why existing implementation went away from this.  
in other words, site admin does not equal to a developer. and has no access to designer.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [May 18, 2026, 8:20pm UTC](https://forum.inductiveautomation.com/t/navigate-to-a-page-does-not-trigger-page-startup-script/115588/6 "2026-05-18T20:20:04Z")

</div>

If you are going to roll your own authentication, **you** are responsible for **every** corner case. Consider creating a true Identity Provider (SAML implementation) outside of Ignition, and set your project(s) to use it.

---

<div class="post-metadata">

**Author:** ![Eugene49](https://avatars.discourse-cdn.com/v4/letter/e/c6cbf5/32.png) [@Eugene49](https://forum.inductiveautomation.com/u/Eugene49)\
**Post date:** [May 18, 2026, 8:27pm UTC](https://forum.inductiveautomation.com/t/navigate-to-a-page-does-not-trigger-page-startup-script/115588/7 "2026-05-18T20:27:37Z")

</div>

Not authentication or login to project, but protecting page resources. Just thinking out loud if there was a one place to put the DB-based page authorization script.

If really insist, put on startUp script of each view, idk.

i guess, like you said this is a guard rail not a cage.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [May 18, 2026, 9:44pm UTC](https://forum.inductiveautomation.com/t/navigate-to-a-page-does-not-trigger-page-startup-script/115588/8 "2026-05-18T21:44:00Z")

</div>

> [@Eugene49](#):
>
> in other words, site admin does not equal to a developer. and has no access to designer.

Nothing says you have to use the same IdP for the Ignition gateway that you do for your individual Perspective projects.
