# Security Level Access in Designer

**URL:** <https://forum.inductiveautomation.com/t/security-level-access-in-designer/77152>\
**Category:** Ignition\
**Tags:** ignition81, perspective\
**Created:** [July 31, 2023, 4:22pm UTC](https://forum.inductiveautomation.com/t/security-level-access-in-designer/77152 "2023-07-31T16:22:52Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Shea\_Molthen](https://avatars.discourse-cdn.com/v4/letter/s/c37758/32.png) [@Shea\_Molthen](https://forum.inductiveautomation.com/u/Shea_Molthen)\
**Post date:** [July 31, 2023, 4:22pm UTC](https://forum.inductiveautomation.com/t/security-level-access-in-designer/77152/1 "2023-07-31T16:22:52Z")

</div>

I'm going through and making security levels which have rules that follow user roles. For example, a user is assigned the "Operator" user role, and has a Security Level applied for HMI/GeneralConfig but not HMI/AdvancedConfig. For config components, I'd assign something like `isAuthorized(false, "HMI/GeneralConfig")` to the enabled property.

The only problem with this is when I'm working in the designer - I don't get any of the security levels applied. Doing something like `isAuthorized(false, "HMI/GeneralConfig") || {session.props.device.type} = 'designer'` works, however, I was wondering if there were any better options/recommendations.

Thanks!

---

<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:** [July 31, 2023, 4:29pm UTC](https://forum.inductiveautomation.com/t/security-level-access-in-designer/77152/2 "2023-07-31T16:29:54Z")

</div>

> [@Shea\_Molthen](#):
>
> I was wondering if there were any better options/recommendations.

The designer fundamentally has more privilege than a client and cannot properly emulate client security. (And a bunch of navigation and docking behaviors are also unavailable in the designer.) Just use a real client instance to test such things.