Component and Window Security

Role-based security inside of Ignition works on multiple levels: component, group, container, and window levels. Each of these levels also have special categories of security that help with tuning security to various design considerations.

Each window and component can define its own security settings. These settings determine who can see and/or use the component.  It's good business practice to have a well thought out security policy for your project.

Changing Security Settings on a Component

To define a security for a component that is different from that of the parent, use the following steps.  

1. Right-click on a component and select Security.
   The Security Settings panel is displayed in the bottom section of the Property Editor.
   
   
2. Deselect the Inherit Permissions check box to override the permission settings so no permissions are inherited from a group, container, or window. (By default, Inherit Permissions uses permissions from whatever container a component is in).  
    
3. Select the role that the user must have from the list of roles displayed under the Inherit Permissions section. If the roles you created do not appear, it's probably because the Designer was open before those roles were created, so right-click in the Inherit Permissions section and select Refresh.
    
4. In the Restrictions section, choose the option that will enact if the user does not have the selected role. 
   
   

   1. Disable - sets the Enabled property to false when the window opens up. 
      

      If you choose to disable the security on a component, make sure that it is a component that actually does something different when it is disabled. For example, buttons and input boxes can't be used when they are disabled, but disabling a Label component has no effect.

   2. Disable Events - prevents event scripts from running when the user doesn't have security clearance.
   3. Hide - acts the same way the Disable restriction does, but it sets the Visible property to false on the component.

   4. Access Denied Overlay - shows an opaque overlay on top of the component when the user doesn't have security clearance.
       
      

5. You can keep the panel open or close it. The security settings take effect immediately.
    

Here are several examples of what different security permissions and restrictions would look like on a Multi-State Button component in a Client.