Each eRequest user can belong to one or many groups. The groups are arranging in a parent child hierarchy e.g. Each group has 1 parent and 0 or many child groups. Except for the top level group(s) which has no parent group.
There can be multiple ‘top level’ groups representing entirely separate approval hierarchies.
When a user submits a request for ‘Approval’ they can select a user from the requests current group’s parent group.
The Group structure also controls visibility of requests. A user can only see requests created by a user in the same group as them or by a user in a group lower in the tree structure. In this way a member of the top group and see all requests created by all users, in that hierarchy.
All users must belong to at least one group.
Group Name – Enter the name of the group
Top Level Group - This indicates this is the ‘Top level’ group. A top level group cannot have any parent groups.
Parent Group – Select a group, that is the parent of this group; if this isn’t the ‘Top Level’ group you must select a parent. Be careful not to setup a looping hierarchy.
Default User – Select a user from the list of users assigned to this group. When requests are ‘Submitted to’ this group, this will be the default user to send them to.
Group Users – The users assigned to this group
Enabled Group Approval Limits – When abled an additional group level Submit To / Approval limit can be setup per currency.
When enabled, these additional limits are applied to decide if the user can perform the action
NOTE: This is an additional limit. Both the user level and group level limit must pass for the action to be allowed.
