Security Attributes

---

These are the security attributes that conditionally update the users belonging to that team when you change them on a team:

General:

• Enter key acts as TAB
• Can Access ODBC
• Receive queue notifications
• Can remove users
• Allow system console
• Is queue administrator
• Drill down is read only
• Inspector

Menu Security:

• (Menu security) table
• AR
• GL
• AP
• PO
• Web access is permitted
• Allow email from address
• View users
• System info
• Explorer
• Objects to load
• Can send user messages
• Company Access:
• (Company access) table
• Module access

Data Entry:

• Allow posting to
• Edit external system transactions
• Save AP Invoices line by line
• Save AR Invoices line by line
• Prompt for unavailable inventory at AR Entry
• Override stop credit on import
• Save Purchase Orders line by line

Privileges:

(Privileges) table

Business Analyst:

• Analysis Tab in Masterfiles
• Load on startup

Sales Orders - Options:

• Allow link to purchase orders
• Set SO delivery date to PO expected date
• Allow link to factory orders
• Allow editing of exchange rate
• Warn on special price
• Warn on duplicated inventory item
• Enable companion item selection
• Allow cancelling of order/lines
• Expand line item in SO Enquiry table
• Allow credit card decryption
• Display quantities for all locations
• Always display alternative locations
• Customer status displays enquiry form
• Allow Forward Orders
• Display available only in SO Release Backorders
• Sales Orders - Settings - Sales Order:
• Display header as default
• Focus the cursor on the table
• (Sales Order) table

Sales Orders - Settings - Packing Slip:

• Display header as default
• (Packing Slip) table

Sales Orders - Order Entry Control:

• Always check
• Maximum order value
• Maximum discount%
• Check for 'Minimum GP %’
• Minimum gross profit%

Purchase Orders - Options:

All

Purchase Orders - Settings - Purchase Order:

• Display Header as Default
• (Purchase Order) table

Purchase Orders - Settings - Receipt:

(Receipt) table

Purchase Orders - Settings - Shipment:

(Shipment) table

Purchase Orders - Receipt Control:

Maximum order value

Inventory:

• Set default location for transfers to location to”
• Default location is read only for data entry
• Enable Bin suspense on receipting
• Enable Bin suspense on picking

Job Costing:

Permit invoicing

Manufacturing - Manufacturing:

• Allow link to sales orders
• Commit inventory only
• Load BOM structure for all bills
• Load when form loads

CRM - Bookings:

• Enable maximum allowed rate discount check
• Maximum rate discount

CRM - eCRM:

• Can search all Sales Orders
• Allow assigning unassigned Calls
• Allow assigning unassigned Service Requests

CRM - Privileges:

(Privileges) table

CRM - Integration:

(Integration) table

CRM - Sales:

• Quote Entry Control
• Change or View Costs
• Change or View Sell
• Access Stored Credit Cards on Quotes

Workflow - Privileges:

• (Privileges) table
• Parent Based Security

Workflow - Approvals & BPM:

Administrative rights for Approval

Workflow - Integration:

(Integration) table

SCM - Privileges:

(Privileges) table

SCM - More Privileges:

Can Receipt IN Transit Transfers

SCM - Requisitions:

• Create Requisitions On Hold
• Can Release On Hold Requisitions
• Limit Stock By Supplier
• Hide Requisition totals
• Hide Source Requisition button
• Generate Requisition from Sales Order
• Can Unsubmit Requisitions
• (Requisitions) table

eTimesheets:

Can unapprove eTimesheets

HR - Privileges:

(Privileges) table

HR - Data Entry:

Allow posting to

HR - Security:

• Show HR data in Explorer
• Allow reporting on Payroll Transactions

Point Of Sale:

• Access
• Limits
• Discount
• On change quantity

Where the team value being changed is:

• A boolean value from true to false. In this case the user value will be set to false only if the equivalent value on all of the other teams that the user belongs to have that value as false.
• A boolean value from false to true. In this case the user value will be set to true.
• A decimal or integer value where the higher the value, the less restrictive. For example, the Sales Order User Preference > Order Entry Control tab, Maximum Order Value. In this case, the user value will be set to the highest value against all the teams.
• A decimal or integer value where the lower the value, the less restrictive. For example, the Sales Order User Preference > Order Entry Control tab, Minimum gross profit %’. In this case, the user value will be set to the lowest value against all the teams.
• A dropdown security setting where options are Edit, View, Module Default, Hide ordered by increasing restrictiveness. In this case we again favour the least restrictive setting. If setting is changed to Hide for the team, but the other team that user belongs to has setting View, then the user setting will be changed to View.
• A dropdown security setting where options are Manual, Module Default, No ordered by increasing restrictiveness. In this case we again favour the least restrictive setting. So if setting is changed to No for the team, but the other team that user belongs to has setting Module Default, then the user setting will be changed to Module Default.
• A dropdown security setting where options are Generate and Print, Generate, Hide ordered by increasing restrictiveness. Again favour the least restrictive setting.

If a user is added or removed from a team, then all the security attributes will be updated against the user using the teams the user now belongs to. So the above rules applies to every single security attribute of the user and update the user.

Any team with the Ignore for security settings option selected is ignored for purposes of the above updating of user.

For each value that has changed (as shown in the table below), its results will be applied as the last column. This is the same no matter what is done, for example, a value changed on team B, team D removed or team C added.

The combinations of teams are respected when a change is made so if user A is in team A/B/C, and user B is in team B/C then for the setting per the top row (Boolean 1) user A would be enabled (true) while the other user B would be off (false) assuming a change was made to make the setting false for team B. An actual change must take place before security settings will be applied due to team information, and only the changed settings will be recalculated for each user that belongs to the team on which it was changed.

Where the value (of, for example, Can unsubmit requisitions) on a particular user is set to true on the user, whereas the value of that same boolean on all the teams the user belongs to is false, if some other value is changed on a team, the Can unsubmit requisitions option for the user is left as it is.

---