Deleted the wrong lead? Open Settings › Recycle bin, find it and press Restore. It comes back exactly as it was, with its number, owner, stage, fields, notes and timeline, and with the tasks and visits that were deleted along with it. You have 60 days from the delete.
What goes into the bin
Records from the modules where deleting is only a delete:
- Leads
- Customers, companies and contacts
- Deals
- Tasks and visits
- Records in any module your business made for itself
Quotations, invoices and the other sales documents, purchase documents, items, stock, packages and bills of materials are not in it. Deleting one of those changes stock or the books, and putting the row back would not put the stock or the entries back. The delete dialog tells you which kind you have: for a record that goes to the bin it says so, and for the rest it says nothing will bring it back.
Who sees what
Recycle bin sits in the System group of Settings for everyone who can open Settings. What it lists follows the delete permission in each module. If your role may delete leads, deleted leads appear and you can restore them; if it may not, they do not. Contacts follow the permission on customers. The owner of the business sees everything. Somebody with no delete permission anywhere sees “The recycle bin is empty”, whatever is in it.
It goes by module, not by record. A salesperson whose role may delete leads, but whose lead list shows only their own, sees every deleted lead in the bin, colleagues’ included, and can restore any of them. Give the delete permission to the people you would trust with the whole module.
Reading the list
| On each row | What it tells you |
|---|---|
| The name, and a label such as Lead or Deal | What was deleted, and what kind of record it is |
| Deleted 28 Sep 2026, 16:12 by Priya | When, and who pressed Delete |
| 12 days left | How long until it can no longer be restored. It turns red at 7 days or fewer |
| Also brings back 3 tasks on the lead | What was deleted with it and will be restored with it |
Newest first, 30 to a page. The search box matches the record’s name, and the module menu narrows the list to one kind.
Restoring
- One record: Restore on its row.
- Several: tick them, or tick the box above the list to take the whole page, then press Restore with the count beside it. Up to 100 at a time.
Each record is restored on its own, so one that cannot come back does not hold up the rest. Anything refused is named in a message with its reason.
A restore is written to Settings › Audit log, for example “Restored lead Sharma Textiles from the recycle bin, with 3 tasks on the lead”. It is not an edit, so no assignment rule or notification runs because of it.
A lead's tasks and visits
Deleting a lead also deletes the tasks and visits recorded against it, so they stop reminding people and counting as overdue. Those do not appear in the bin as rows of their own. They come back only with the lead, and only the ones deleted in the same moment as the lead. A task you deleted by hand the week before is its own row in the bin, and restoring the lead leaves it where it is.
When a restore is refused
| It says | Why | What to do |
|---|---|---|
| Another record now uses the same number or name. Change that one, then restore this. | Since the delete, a new record has taken a value that has to be unique | Renumber or rename the newer record, then restore |
| It was deleted more than 60 days ago and can no longer be restored. | The 60 days ran out after the list was opened | Nothing in the product brings it back now |
| It is not in the recycle bin. | Somebody else restored it first | Refresh the list; it is already back |
| You cannot restore records of this kind. | Your role may not delete in that module | Ask somebody whose role may |
What does not come back
- Assignees and watchers. Deleting a single record takes off everybody on it except the owner, and restoring does not put them back. Leads, customers, deals and the rest removed together in a bulk delete keep theirs; records in a module of your own lose them either way.
- Links a rule cleared. Where a dependency rule is set to Detach, the delete blanked the link on the other records. Restoring does not fill it in again.
- Anything deleted further down. Only what a rule deleted directly with this record comes back, not what was deleted with those records in turn.
After 60 days
The record leaves the bin. It is not erased: the row stays in the database, marked deleted, for the audit trail. But no screen will bring it back after that, so if a record might be needed, restore it while the days are counting down.
The bin reads the latest 2,000 deletions in the 60 days. A business that deletes more than that in two months, after a bad import say, will find the oldest of them missing from the list.
Where to go next
- Deleting, and what refuses to delete
- Dependency rules: what a delete takes with it
- Who may delete, set in roles
Something missing or wrong here? Tell us. A question that needed asking usually means a page that needed writing.