🚫 Removing Team Members & Preserving Audit History

Venva allows you to remove team members from your workspace when they no longer need access. Once removed, the user is immediately disconnected from your Venva account and can no longer access your workspace.
​

Removing a team member does not erase the activity they already performed while they were part of your operation. Their historical activity remains available for internal review and auditability.
​

Inside My Team, you can remove a team member when you no longer want them to have access to your Venva workspace.

This is useful when:

To remove a team member:

Venva will show a confirmation prompt before the account is removed.
​

Team members can be removed from the Actions menu inside My Team.
​

Venva asks for confirmation before removing a team member from your workspace.
​

Once a team member is removed:

This is an access removal action. It prevents further activity from that user inside your Venva operation.
​

When a team member is removed, Venva does not delete the activity they already performed while they had access.

That means past records such as team activity logs remain available for review.

This helps preserve a clear internal history of actions that were already taken inside the workspace.
​

Venva preserves historical activity for accountability.

If a removed team member previously:

those historical records remain part of your internal activity trail.

Removing the user stops future access, but does not wipe the past actions they already performed.
​

Before removing a team member, it is a good idea to review:

If the user should no longer have any access at all, removal is the correct action.
​

Removing a team member revokes their access while preserving the historical activity records needed for oversight, accountability, and internal review. This gives vendors a clean way to protect workspace access while preserving the audit trail needed for oversight, accountability, and internal review.