SupportRemove an imported Ask360 kit
Use the import ledger to remove resources created by a kit only when later changes and dependencies do not block safe cleanup.
How this fits into Lead360Explore Ask360See how Pieces, memory, channels, playbooks, learning, and kits work together.- 01
How Lead360 helps
- 02
Before you begin
- 03
Complete the workflow
- 04
Understand the key controls
How Lead360 helps
Kit removal uses the recorded import ledger to identify the bot and resources created by a specific import. Lead360 checks for dependencies and later changes so cleanup does not erase unrelated work, shared resources, or configuration that administrators added after installation.
When to use this workflow
Use kit removal when an imported bot should be decommissioned and the team wants to clean up import-created resources that remain safe to remove.
Before you begin
Start with the exact sub-account and the smallest set of permissions, records, and resources required for the task.
- Disable related channels, schedules, and automations.
- Review the import ledger and current owners of every created resource.
- Export or retain required audit, run, and business records before removal.
Complete the workflow
Follow the steps in order and stop when a required resource, permission, review, or approval is missing.
- Open the imported bot and its kit import details.
- Review resources listed in the import ledger.
- Resolve active channels, schedules, dependencies, ownership, and later edits.
- Run the supported kit removal action.
- Review removed, retained, and blocked items and verify the remaining workspace.
Understand the key controls
Ledger-based cleanup
Removal targets resources recorded as created by the import rather than searching by name or deleting broadly.
Dependency blockers
Shared use, later edits, active channels, and other dependencies can require a resource to remain.
History preservation
Removing configuration does not imply erasing legally or operationally required audit and execution history.
Confirm the result
Do not rely on a success message alone. Confirm the saved state and any live effect in the product area that owns the final record.
- Confirm the bot is no longer available through channels.
- Review every retained or blocked resource and assign an owner.
- Test that unrelated bots and workflows still function.
Troubleshooting
Removal is blocked
Open each blocker and resolve active use, ownership, later edits, or shared dependencies rather than deleting around the check.
A resource remains after removal
Compare it with the import ledger. It may be retained because it existed before import, changed later, or is used elsewhere.
Frequently asked questions
Does kit removal delete everything with the same name?
No. It uses the import ledger and dependency checks to target import-created resources safely.
Can kit removal erase run history?
Configuration cleanup and audit retention are separate concerns. Preserve required execution, approval, and business records according to the applicable retention policy.
Continue with Lead360
Use this workflow in Lead360
Put this guide into practice with a 14-day free trial of Lead360 Pro early access, or continue learning through the related collection.