Additional Security for Standard Programs
In addition to the standard role-based permissions, a number of other types of security can be defined for standard programs. These types of security apply in operational areas.
Using the system, you can:
• Specify user IDs that can update the value of specific program fields.
• Determine which users or roles can create operational transactions that affect:
• Sites, locations, inventory statuses, and other inventory-related attributes
• General ledger accounts
• Inventory movement codes
Note the following fundamental difference in the way role-based security works and the way these additional forms of operational security work:
• For role-based access to domains and entities or resources secured through Role Permissions Maintain, no one has access unless it is specifically granted.
• For other types of operational security, all users and roles have access unless specific access records have been defined. Once access records have been defined, other users and roles are automatically prevented from having access.
If you use the Sales and Use Tax Interface (SUTI) to communicate tax data between the system and Vertex’s Quantum for Sales and Use Tax product, set up similar access controls in Tax Interface Control (36.5.3.24). See Technical Reference: Sales and Use Tax Interface for information on SUTI.
Access records apply only to the current domain from which they are entered.