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 Channel Islands
The system has additional security for the Channel Islands UI. This security, which is defined by role, is managed through the Channel Islands UI.
• Granular-level security allows you to grant various levels of access to different roles for all defined resources, including business entities, individual reports, browses, and KPIs.
• Field security limits which roles have read and write access to fields and field groups.
• Channel Islands is designed to operate over the internet with a secure UI and secure APIs.
• All actions on the Channel Islands UI are determined by role security.
For details on setting Channel Islands security, see
Channel Islands UI Security.