Vigilbase Identity manages membership: invitations, accounts and the member's role. Vigilbase OS adds scoped grants on top, so you can give one member extra permissions for a specific connection, dataset, resource or action class.
Roles
| Role | Typical use |
|---|---|
| Owner | Full control, including membership, policy and deleting the organisation. Must use multi-factor authentication. |
| Admin | Integrations and operational configuration. Needs an explicit grant to approve actions. |
| Viewer | Read access to permitted pages and summaries. |
Analyst, approver and auditor rights are given with scoped grants, not roles.
Anyone who is an owner or holds privileged permissions, such as approving actions, must use multi-factor authentication.
Invite a member
You need the members.manage permission.
Open Settings, then Members, and choose Invite.
Enter the Email.
Choose the Role. New members are Viewers by default.
Choose Send invitation and confirm it's you.
Vigilbase Identity sends the invitation email. The member appears in the list once they accept.
Change a member's role
With the members.manage permission, choose a new role in the member's row and confirm it's you. You cannot change your own role.
Add a scoped grant
A grant gives one member a permission, optionally narrowed and optionally until a date. For example, give a member action.approve for one connection only.
Open Settings, then Grants, and choose New grant.
Choose the Member and the Permission. The permission defaults to
action.approve.Choose the Scope: All, Org unit, Connection, Dataset, Resource or Action class, and enter the scope value.
Optionally set Expires.
Choose Create grant and confirm it's you.
To remove a grant, use its delete button. Changes to members and grants are recorded in Activity.