We recommend that users be disabled, rather than deleted, in case you need to audit their prior activity, history, and settings. A disabled user will have activity, history, and settings log information retained whereas deleting a user will delete their corresponding information from activity, history, and settings logs.

Manual User Deletion

Site administrators can choose to completely delete a user from the site. A re-authentication prompt will appear to confirm the deletion. When a site administrator deletes a user manually, they can choose what to do with resources owned by the deleted user, such as Share Links, Automations, GPG Keys, Remote Servers, Custom Forms, or folder settings. The Site Administrator can either reassign these resources to another user to help maintain visibility and control, or leave them without an owner if reassignment isn’t needed.

Our Command Line Integration (CLI) App and SDKs can also be used to programmatically delete user accounts.

Automatic User Deletion

Users provisioned through LDAP or SCIM can be de-provisioned through the same LDAP or SCIM system used for provisioning.

User Lifecycle Rules enable automatic deletion of inactive users based on authentication method and inactivity duration. If a rule is configured with the delete action, eligible users will be removed, even if they were not previously disabled through other settings.

Disabled user accounts can also be automatically deleted using User Lifecycle Rules, which remove accounts that have remained disabled for a specified number of days.

User Lifecycle Rules help automatically delete user accounts that have been inactive or disabled for a specified number of days. This is useful for maintaining a well-managed user list by removing accounts that are no longer needed.

When a user is deleted automatically through any of these methods, their resources are not deleted and are not assigned to a new owner. These orphaned resources remain active and can be managed by a Site Administrator.

Effects of Deleting a User

Deleting a user account removes their login access but does not automatically delete the resources they own. If the user is deleted automatically through a User Lifecycle Rule, LDAP or SCIM provisioning, or automatic removal of disabled users, their login access is removed but their owned resources remain and are not reassigned. When deleting the user manually or through the CLI, the site administrator has the option to reassign those owned resources to another user or leave them without an owner.

Share Links

When deleting the user account, the Site Administrator can choose to revoke Share Links created by the user or assign them to another user. If not revoked or reassigned, the links remain active and continue to be manageable by Site Administrators.

Automations, GPG Keys, Remote Servers, and Custom Forms

Site Administrators can assign Automations, GPG Keys, Remote Servers, and Custom Forms to another user or choose to orphan them while deleting the user. Orphaned resources remain functional but will no longer have an assigned owner.

Files and Folders

Deleting a user does not remove their stored files or folders. Storage usage and access remain unaffected unless folder permissions are modified.

Folder Settings and Notifications

Folder settings configured by the deleted user will remain in effect. Notifications set for the deleted user will no longer function. Folder settings can be reassigned to a new owner when deleting the user.