⚠ As a best practice, we recommend avoiding the use of either of two default Privilege Sets [Data Entry Only] and [Read Only] for production use. Their names are somewhat misleading, especially considering there are elements of the Read-Only Privilege Set that allow a person to edit and change some data elements in a file, as well as taking other actions not generally associated with read-only privileges. You can either create your own custom privilege set from scratch or duplicate the read only set but then make the necessary modifications to protect the necessary attributes. Also note that our full professional course goes over all of these best practices and security details in a step-by-step method. What you see in the above video is really just the very basics and may be fine to use for learning and testing, but for live production systems, use custom privilege sets to allow you more protected and granular control.
⚠ As a best practice, we recommend avoiding the use of either of two default Privilege Sets [Data Entry Only] and [Read Only] for production use. Their names are somewhat misleading, especially considering there are elements of the Read-Only Privilege Set that allow a person to edit and change some data elements in a file, as well as taking other actions not generally associated with read-only privileges. You can either create your own custom privilege set from scratch or duplicate the read only set but then make the necessary modifications to protect the necessary attributes.
Also note that our full professional course goes over all of these best practices and security details in a step-by-step method. What you see in the above video is really just the very basics and may be fine to use for learning and testing, but for live production systems, use custom privilege sets to allow you more protected and granular control.