Definition of Terms
- User: A user is a Console login account with customizable access
- Group: A group defines the transfer permissions of all its users.
- Transfer Path: A transfer path consists of two endpoints, the transfer direction
(one-way or two-way), and a set of permissions that authorize starting transfers, monitoring
transfers, and enabling email notifications.
OverviewConsole uses a combination of groups,
transfer paths, and user accounts to manage to user permissions. A user that belongs to a group
inherits permissions defined within the groups it belongs to. A group's permissions are defined
by its transfer paths. If you have a non-admin user and you want them to be able to see certain
transfers, you need to add them to a group. This group must have one or more transfer paths that
specify the kinds of transfers that members of the group are allowed to see or control.
Each group can contain one or more transfer paths. In the figure below, Group 1 contains two
transfer paths, #1 and #2. A Console user inherits transfer permissions from all of the groups
he or she belongs to. For example, Console User 2 belongs to both Group 1 and Group 2, and has
the permissions to use Transfer Paths #1, #2, and #3.
Tip: Console administrators are
able to view and control all transfers. They automatically inherit permissions of any existing
Console groups. They can add, edit, and delete any nodes, Console users, and Console
Default Console Groups
When adding a new node, you have the option of
creating three default groups associated with that node.
||The users in this group can monitor, control, and set up email notifications of all
transfers on the node. They can start simple and smart transfers between this node and any
node, and share smart transfer templates with other users.
||The users in this group can start simple and smart transfers between this node and any
||The users in this group can monitor and set up email notifications of all transfers on