# Page Specific Security in SPA SDK

**URL:** <https://community.bloomreach.com/t/page-specific-security-in-spa-sdk/3543>\
**Category:** Experience Manager (PaaS/OnPrem)\
**Created:** [December 5, 2022, 6:19pm UTC](https://community.bloomreach.com/t/page-specific-security-in-spa-sdk/3543 "2022-12-05T18:19:50Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![mkjp2011](https://yyz1.discourse-cdn.com/flex027/user_avatar/community.bloomreach.com/mkjp2011/32/1102_2.png) [@mkjp2011](https://community.bloomreach.com/u/mkjp2011)\
**Post date:** [December 5, 2022, 6:19pm UTC](https://community.bloomreach.com/t/page-specific-security-in-spa-sdk/3543/1 "2022-12-05T18:19:50Z")

</div>

Hello, we have a requirement to mark a page as protected. As in, require that the user needs to be logged in or a part of a specific role outside of the Experience manager. Some concerns/approaches:

1. We could create a page document to define these rules for each page/route.
2. We could create a Custom Page Tool to control these types of settings.

Problems with both approaches. If we want to lock down the page/route if a user is logged in or a part of a role, we don’t want to expose the page model for people to inspect. This would defeat the purpose and expose the page contents when we don’t want to.

Is there a way to achieve this? @machak @jasper.floor