InfoShip®
Security
InfoShip security controls who can do what from within the application.  Security is implemented at the application service level, meaning that not only do the inherent functions (such as Void, Closeout, etc) participate in the security model but also any resources that may have been added to the system (such as any business rules implemented using Behaviors or VB Script).  For instance, if a resource (such as a VB Script) has a policy that denies execute access, then any toolbar buttons or keyboard shortcuts associated with this resource are disabled.  In the event of a toolbar button, the button shows up grayed out.

The security model is made up of Users, User Groups, Resource Groups, and Policies.  If Active Directory is used on the network, the Users and User Groups can be tied directly into Active Directory instead of maintaining two separate lists.

Security Features:

Users The Users dialog allows for the management of users in the InfoShip system.  New users can be setup and existing users can be modified.

User Groups User Groups can be established that logically tie various users together.  In the example to the left, two typical user groups have been setup: Supervisor and General User.  A General User group could only allow access to shipping and rating, disallowing a user from modifying ship-to information, voiding, and closing out.  Such functions could be handled by the Supervisor group.   Resource Groups Resource Groups are a way of organizing resources into logical units.  For instance, you may want to control access to the consignee fields.  It would be tedious to add each individual consignee field to the policy and then setup the security rights for each individual field.  Instead, a Consignee Group could be setup and then the rights assigned for all members of the group by assigning them to the group itself.   Policies Policies control read, write, and execute access to a resource or a group of resources for a given user or group of users.  Since the policy is applied from a central server, any presentation of a resource can be controlled.  For instance, if a field or group of fields is allowed only read access, the field shows up disabled inside InfoShip as well as inside InfoShare, or anywhere else--such as on a custom dialog.