When a user no longer requires access to Basecone, it is recommended to remove the account to keep your user administration up to date and prevent inactive users from remaining in the environment.
📌 Important: Only users with the Super User role can permanently delete users in Basecone.
Delete a User in Basecone
Required Permissions
To delete a user, you must have the Super User role.
If you do not see the delete option (trash-bin icon), you do not have sufficient permissions to remove users.
Steps to Delete a User
Navigate to Settings > Users.
Locate the user you want to remove.
Under the Actions column, click the trash-bin icon.
Confirm the deletion.
Once confirmed, the user will be permanently removed from Basecone.
Unable to Delete a User with the Authoriser Role?
If a user has the Authoriser role and cannot be deleted, there are usually outstanding approval tasks assigned to that user.
Check for Pending Authorisations
Before an Authoriser can be removed:
Open the Authorisation Overview.
Review whether documents are still awaiting approval from that user.
Reassign all pending documents to another Authoriser.
Attempt to delete the user again.
For information about reassigning documents, see the article:
No Permission to Delete the User?
If you do not have Super User permissions:
Open the user's settings.
Change the user role from Authoriser to Restricted Client User.
Contact a Super User and ask them to permanently delete the account.
📌 Changing the role does not delete the user. A Super User must still remove the account using the delete option.
Is the User Part of an Authorisation Flow?
A user cannot be deleted if they are still assigned within an Authorisation Flow.
Remove the User from the Workflow
Go to: Settings > Company > Actions (Edit) > Workflow
Scroll to Authorisation Flow.
Review all workflow filters and approval flows.
Remove the user from every workflow where they are assigned.
Save your changes.
Try deleting the user again.
📌 Any user referenced in an active Authorisation Flow must be removed from that flow before the account can be deleted.
Hidden Users in Basecone
Why Users Become Hidden
Users without permission to delete accounts sometimes remove a user's company access instead.
This does not delete the user.
Instead:
The account remains active.
The user may disappear from the user list.
The account can still exist within the Basecone environment.
How to Check for Hidden Users
If you are unsure whether a user has been deleted:
Review hidden users in your environment.
Confirm whether the account still exists.
Make the user visible again if necessary.
Contact a Super User to permanently delete the account.
📌 A user that is not visible in the user list is not necessarily deleted.
Deactivate a User Instead of Deleting
If you want to prevent a user from logging in without removing the account, you can deactivate the user.
How to Deactivate a User
Open the user's settings.
Go to the Settings tab.
Scroll to the bottom of the page.
Locate the User Active field.
Enter an End Date.
After the specified date:
The user can no longer log in to Basecone.
User settings and history remain available.
The account can easily be reactivated later.
Reactivate a User
To restore access:
Open the user's settings.
Remove the end date.
Save the changes.
The user will be able to log in again immediately.
Troubleshooting Checklist
If you cannot delete a user, verify the following:
✅ You have the Super User role.
✅ The user has no documents awaiting authorisation.
✅ All pending authorisations have been reassigned.
✅ The user is not included in an Authorisation Flow.
✅ The user is not simply hidden because company access was removed.
✅ Any required workflow changes have been saved.
Following this checklist resolves most user deletion issues in Basecone.
Need Additional Help?
If you still cannot delete a user after completing the steps above:
Contact your organization's Basecone Super User.
If the issue persists, contact Basecone Support through your organization's standard support channel.
When contacting support, be prepared to provide:
The user's email address.
The user's current role.
Any error message shown during deletion.
Whether the user is assigned to an Authorisation Flow or has pending authorisations.
