Additional Types of Security
Some additional types of security can be configured for standard programs and component-based activities.
Additional Security for Standard Programs
The system has several types of security that apply to operational programs only. In these programs, security is defined by user ID, role, or a combination of both.
• Field Security Maintenance (36.3.15.1) limits who can update specific fields. For field security, specify a user ID.
• Update restrictions functions on the Update Restrictions menu (36.3.7) limit who can update specific records and create specific issue, receipt, and transfer transactions.
• GL Account Security Maintenance (36.3.13.1) restricts access to GL accounts from operational functions. Specify any combination of user IDs or roles.
• Site Security Maintenance (36.3.13.8) limits who can create inventory transactions at secured sites. Specify any combination of user IDs or roles.
• Inventory Movement Code Security (36.3.13.13) lets you grant or deny user access to shippers and other transactions using specific movement codes at a site. Specify any combination of user IDs or roles.
For details about setting up operational programs, see
Additional Security for Standard Programs.
Additional Security for Component-Based Functions
You can also set up field security for component-based functions. This type of field security is more complex and detailed than field security for standard programs. You define by role whether fields are enabled, disabled, or hidden.
To use field security, you must first enable the system-wide setting using System Maintain (36.24.3.1).
For details on component-based field security, see
Additional Security for Standard Programs.