Managing members
Inviting people, changing a role and removing access. Only an Owner or an Admin can do any of it, and nobody can act on their own row.
Open Settings, then Members. The page lists everybody in the organisation with their role, and anybody invited who has not accepted yet.
Only an Owner or an Admin sees the controls. Everybody else reads the same list without them, and Cogentic enforces the same rule on the server, so a request from a member is refused whatever the screen shows.
The three roles
| Role | What it allows |
|---|---|
| Owner | Full control, including deleting the organisation and managing owners. |
| Admin | Manage members, settings, and every case. |
| Member | Work cases and documents; can’t manage the organisation. |
Invite somebody
- 1
Select Invite member
The Invite a colleague dialog opens.
- 2
Enter their Email
Cogentic shows the domain your organisation uses as a hint. It states no rule, and you can invite any address.
- 3
Choose a Role
An Admin can invite an Admin or a Member. Only an Owner can grant Owner, and that happens from the row afterwards rather than from this dialog.
- 4
Select Invite
The invitation is sent and the person appears in the list reading Pending, with the date the invitation expires.
Change a role
Choose the new role from the picker on that person’s row. The change applies at once.
Granting Owner is a separate action, Make owner, and only an Owner sees it. Cogentic asks you to confirm, because the person gets full control of the organisation including deleting it and changing who else owns it. You stay an owner.
Remove somebody
Select Remove on their row and confirm. They lose access immediately. On a row that is still Pending the action reads Revoke instead, which withdraws the invitation so it can no longer be accepted.
What Cogentic will not let you do
| Refused | Why |
|---|---|
| Acting on your own row | The role picker and Remove are disabled there. You cannot remove yourself from the organisation. |
| An Admin acting on an Owner | An Owner’s row is read-only to anybody who is not an Owner. |
| An Admin granting Owner | The picker offers an Admin only Admin and Member. An Admin who could make a peer an Owner could be promoted straight back. |
| Removing or demoting the last Owner | The row cannot predict this one, so it surfaces as an error rather than a hidden control. The organisation always keeps an owner. |
After you change somebody
Removing a member does not change the cases they worked. Their decisions, findings and notes stay on those cases under their name, and the audit log keeps every entry they made. What they lose is access.
A case still assigned to somebody you removed stays assigned to them and nobody else can decide it, because only the assignee can. Reassign it from the case before you remove them, or take it yourself afterwards.
Related
Last checked against the product on .