LESSON

Project Permissions

Description

Learn how to use the Gateway authentication profile to lock down what is editable inside the Designer. Permissions are set on a per-project basis.

Video recorded using: Ignition 8.1

Transcript

(open in window)

[00:00] The Designer gives users the flexibility to configure a list of required roles, to be able to delete, protect, save and view project resources. Here in my Designer, I have a window open with a user management component. You can see all the users and roles associated with my default user source tied to this project. More specifically, I have delete, protect, save and view roles. If I go up here to project, project properties, under project permissions, I can configure this project to require roles to perform project related actions. Here, with the view section in focus, I can press the space key or begin typing and I will see a list of roles to choose from. I will select view. So now you need to have that view role in order to be able to view this project's resources. Similarly for the save action, I will select the save role which means you need to have the save role to save project resources. I will do the same and tie the delete and protect resources actions to their corresponding roles. If I wanted to require more than one role for a specific action, I can simply separate each with a comma. Of course, for any of this to take effect, I have to save my changes. Then, in order to do any of these actions, your users will have to have those specific roles. This allows you to fine tune your project security.

You are editing this transcript.

Make any corrections to improve this transcript. We'll review any changes before posting them.