Application Console: login permissions
This section explains the difference in the Sterling Order Management System Software Console application when you are logged in for the following types of users:
- Hub Users (Users belonging to the "DEFAULT" organization)
- Enterprise Users
- Buyer and Seller Users
- Node Users
- Carrier User
It is important to note that the difference in behavior in the Sterling Order Management System Software Console screens is only a difference in what data that user can view and modify. Screen level access is only controlled by user group permissions. Therefore, a user can navigate to all screens within the Sterling Order Management System Software Console as dictated by the user groups that have been assigned to the user. The type of user does not affect this in any way. For example, if a node user has been assigned to the Administrator user group (which contains permissions for all screens), then that user will be able to view and modify orders in the sales order console.
Access to the Applications Manager is granted only to Hub and Enterprise users. However, access to the Applications Manager can be denied for a specific Hub or Enterprise user through user group definitions. Access to the Applications Manager is not allowed for any other type of user regardless of the user group definitions.
Hub users
Hub users are those belonging to the "DEFAULT" organization. By default, Hub users have access to all data for all enterprises. Individual Hub users can be restricted to view data for specific enterprises by creating a team for that user.
Enterprise users
By default, enterprise users have access to all data for:
- Itself
- Any enterprise that is a child organization in the organization hierarchy.
Individual enterprise users can be restricted to view data for a subset of the default list of enterprises by creating a team for that user.
Buyer and seller users
Users for Buyer or Seller organizations have access to data in which their organization plays the role of the buyer or seller on that data entity. For example, a particular seller user can only see orders in which that user's organization is the seller on the order document. Not all data elements have a seller or buyer associated to them. Therefore, certain screens that are not necessarily relevant for buyer or seller users, and permission should be revoked for such screens for buyer or seller users.
Node users
Node users have access to data in which they are the node associated with that data element. For example, a node user can view all order releases in which they are the ship node OR receiving node on the order release. Not all data elements have a node associated to them. Additionally, when viewing inventory in the inventory console, a node user can only view and modify inventory for its own node. Therefore, certain screens may not be relevant for a node user to view. For example, in the order console, node users can see all orders in which their node's owner organization is the buyer, seller, or enterprise on the order. If you do not want a particular node user to have access to these orders, permission for these screens should be revoked for that user.
Carrier user
Carrier users have access to data in which they are the carrier associated with that data element. For example, a carrier organization user can view all orders in which they are the carrier shipping the order. Not all data elements have a carrier associated to them. Therefore, certain screens will not be relevant for a carrier user and permission should be revoked for such screens for a carrier user (for example, inventory console screens).