I wanted to draw your attention to page load triggers because there are various pages in your app that only logged-in users should be able to view.

And even though our data is often protected with good developing practices, we still don't want certain pages to load.

For instance, someone can share with their friend this project page. That friend can then click the link and just land on this page.

And even though the data probably won't be shown—because we've set up our constraints correctly—we still don't want a page to load without data. It just won't look good.

We always want to set up page redirects on certain conditions.

So let's go ahead and set up one for Projects.

I'm going to go ahead and go to the Workflow tab, and I'm going to click on New—because this time our workflow has been created by an event such as a page load and not a button.

So I'd use this New button here to start it. And here we have some options.
​

We can do various things:

So what I definitely want is: when a user is logged out.
​

And the action I'm going to set is: navigate them (go to page).

And we can take them anywhere we like—so maybe we just take them to the Login page.

And this means that only logged-in users will be able to see the Projects page, and the data will only be viewable based on how we have set up our search constraints.

So go ahead—go to all of your pages that should be protected—and make sure that you at least have one event created such as this one.