Security Level Access in Designer

[Shea_Molthen]

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!

[pturmel]

@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.