Application groups
Groups organize applications into named business units or teams and provide a reusable way to assign application access.
Choose names that people recognize, such as Claims or Retail lending. Before changing a group, review its applications and the members whose access depends on it.
Create a group
Add the group
Select Add Group, enter a name, and add an optional description.
Review its link identifier
VeriProof creates the link identifier from the original name. It stays fixed because links and integrations may rely on it. You can change the display name and description without changing that identifier.
Review applications and ownership
Review the group’s application list before assigning members. Confirm that the group contains the applications those members should be able to access.
Group fields and group rules
Select Fields to open the group’s field contract. Every application in the group inherits these fields, so a Developer confirms them once for the group. Group rules read these fields and apply to every application in the group, including applications added later. Moving an application into or out of a group changes which group rules apply to it. See Apply one rule to an application group.
Deactivate a group
Deactivating a group stops its group rules for every application in it. Move the group’s applications before confirming deactivation:
- Open the group’s deactivate action.
- Choose another group for its applications, or leave the destination empty to make them ungrouped.
- Confirm the reassignment, then select Deactivate.
Check affected member access after the move. Do not assume access through the old group carries over to the destination group. Deactivation does not delete application data. Demo and sandbox views do not permit group changes.
Assigning a group to a member allows access to applications in that group. Application restrictions can narrow that access, while the member’s role determines what actions are available.