Search

User Manual

GETTING STARTED


MODULES AND PLATFORM


APPENDIX


TUTORIALS & HELPFUL TRICKS


GLOSSARY


STRATEGIC PARTNER LINKS

Sepasoft - MES Modules
Cirrus Link - MQTT Modules

RESOURCES

Inductive University
Ignition Demo Project
Knowledge Base Articles
Forum
IA Support
SDK Documentation
SDK Examples

ALL USER MANUAL VERSIONS

Ignition 8.1
Ignition 7.9
Ignition 7.8

Deprecated Pages

Employees

Sign In

Skip to end of metadata
Go to start of metadata


When several users are all working on the same project, managing changes to the project can become cumbersome. By default, all users with Designer access can modify, delete, save, and publish all resources available in the Designer. In some situations, it is desirable to limit what each user can do in the Designer. Ignition has several built-in Designer restriction methods to help in these scenarios. 


Designer Project Permissions

Actions such as publishing, viewing, saving, deleting, and editing of project resources are restricted to users who have sufficient roles to do so. Editing of the these required roles is done in the permissions section of the Project Properties dialog in the Designer. If required roles are not set for an action, then all users with Designer access can perform the action. 

The Designer does not poll for role changes, so if a user who is currently logged into the Designer has their roles changed, they will need to re-launch the Designer for the new role(s) to take effect.

Controlling Project Edits by Role

You can control who gets to login to a project by assigning roles and giving permissions to those roles in the Required Designer Roles property which you set up in the Designer.

  1. In the Designer, from the menubar, choose Project > Properties.

  2. Go to the Project > Permissions area, and under the Required Designer Roles, enter the appropriate roles next to each project level restriction, as required.
    In the text boxes on this page, enter a comma-separated list of role names that are required to access the project. As you start typing, matching role names will pop up. 




    The following table describes each of these five options:

    Option

    Affect

    ViewUser must have at least one of these roles to view the project in the Designer.
    SaveUser must have at least one of these roles to save the project.
    DeleteUser must have at least one of these roles to delete the project.
    Protect ResourcesUser must have at least one of these roles to access protected resources.


On this page ...


IULocgo


Project Permissions



Protecting Project Resources

You can lock individual project resources from inside Designer by opening the Project Browser, and right clicking on any of the objects that you want to lock in. Select the Protect option to protect it. Once it's protected, it cannot be changed except by someone that has the permission to unprotect it, and modify it.

Protected resources are global or project resources that can only be edited by select users with the required roles. These roles are required to protect resources from being edited in the Designer, and do not apply to the clients. This means you can prevent a resource from being edited by other users who have Designer access. It is often used in scenarios where development work is finished on a window or object, and no further changes should be made to it. Other objects like Vision Templates or Alarm Pipelines are often protected so they may be used, but not modified.

Users without a required role will see the following message in the Designer when attempting to open a protected resource:

Users with a required role are allowed to modify the resource, but a message will appear informing them that the resource is protected, and will be asked how to proceed:

Additionally, a lock icon will appear on the resource informing users that it is protected. An example can be seen on the 'Audit Events' window below:



To remove the protection, simply right click the object and select the Protect option to unprotect it.



IULocgo


Locking Project Resources






  • No labels