Delete Tenant

Step-by-step guide to safely deleting tenants in Authonomy Nexus with restrictions and safety measures

Delete Tenant

Permanently remove tenants from your Authonomy Nexus instance. This operation is destructive and cannot be undone.

Important Restrictions

Before attempting to delete a tenant, understand these critical limitations:

Current Tenant Protection

  • You cannot delete the tenant you’re currently operating in
  • The delete button will be disabled for the current/active tenant
  • Switch to a different tenant before attempting deletion

Data Loss Warning

  • Tenant deletion is permanent and cannot be undone
  • All data associated with the tenant will be lost, including:
    • User accounts and profiles
    • SAML/OIDC configurations
    • Application registrations
    • Audit logs and analytics
    • Custom policies and rules

System Dependencies

  • Ensure the tenant has no active integrations or dependencies
  • Verify no critical applications are exclusively configured for this tenant
  • Check for any scheduled jobs or automated processes tied to the tenant

Deletion Process

Step 1: Access Tenant Management

Navigate to Settings > Tenants tab to view your tenant list.

Tenant List Tenant list showing multiple tenants with delete buttons

Step 2: Locate Target Tenant

In the tenant list, find the tenant you want to delete. Note:

  • The current tenant will have a disabled “Delete” button
  • Only non-current tenants show an active “Delete” button
  • Tenant names and IDs are clearly displayed for identification

Step 3: Initiate Deletion

Click the “Delete” button for the target tenant.

A confirmation modal will appear with:

  • Tenant name and ID for verification
  • Warning about permanent data loss
  • Confirmation buttons (Delete/Cancel)

Step 4: Confirm Deletion

In the confirmation modal:

  1. Verify the tenant details - Ensure you’re deleting the correct tenant
  2. Read the warning message - Understand the permanent nature of this action
  3. Click “Delete” to confirm - Or “Cancel” to abort the operation

Step 5: Verify Removal

After successful deletion:

  • The tenant will be immediately removed from the tenant list
  • A success message may appear confirming the deletion
  • The tenant’s data is permanently destroyed

Safety Checklist

Before deleting any tenant, complete this safety checklist:

Pre-Deletion Verification

  • Backup critical data - Export any important configurations or user data
  • Document tenant purpose - Record what the tenant was used for
  • Check dependencies - Verify no systems rely exclusively on this tenant
  • Notify stakeholders - Inform team members who might be affected
  • Verify tenant identity - Double-check you’re deleting the correct tenant

Alternative Actions

Consider these alternatives before deletion:

  • Rename the tenant - Mark it as deprecated instead of deleting
  • Archive configurations - Export settings for potential future use
  • Disable instead of delete - If supported, disable rather than remove
  • Move users - Transfer users to another tenant before deletion

Troubleshooting Deletion Issues

Delete Button Disabled

Problem: Cannot click the delete button Possible Causes:

  • Trying to delete the current/active tenant
  • Insufficient permissions
  • Tenant has protected status

Solutions:

  1. Switch to a different tenant first
  2. Verify you have tenant management permissions
  3. Check with system administrator about tenant protection

Deletion Fails

Problem: Deletion process fails with error Possible Causes:

  • Active dependencies exist
  • Database constraints prevent deletion
  • System processes are using the tenant

Solutions:

  1. Check for active user sessions in the tenant
  2. Verify no applications are exclusively configured for this tenant
  3. Wait for any scheduled processes to complete
  4. Contact system administrator for manual cleanup

Accidental Deletion

Problem: Wrong tenant was deleted Immediate Actions:

  1. Stop all operations - Don’t make additional changes
  2. Contact system administrator - Immediate escalation required
  3. Check backups - Verify if recent backups exist
  4. Document the incident - Record what happened and when

Prevention:

  • Always verify tenant name and ID before confirming deletion
  • Use the confirmation modal as a final verification step
  • Consider implementing approval workflows for production environments

Best Practices

Naming Conventions for Deletion

  • Mark tenants for deletion with clear naming (e.g., “DEV-ToDelete-2024-01-15”)
  • Use consistent prefixes to identify tenants scheduled for removal
  • Document deletion dates and reasons

Environment-Specific Policies

  • Development: More lenient deletion policies for testing
  • Staging: Require team approval before deletion
  • Production: Implement strict approval workflows and waiting periods

Audit Trail

  • Document all tenant deletions with:
    • Deleted tenant name and ID
    • Date and time of deletion
    • Administrator who performed the deletion
    • Reason for deletion
    • Any data exported before deletion

Alternative Tenant Management Actions

Recovery Options

⚠️ Remember: Tenant deletion is permanent and irreversible. Always verify tenant identity and backup critical data before proceeding.