Self-service account deactivation: why it’s harder than you would think

We’ve just introduced a self-service UI for deleting your Fly.io account. From time to time people ask us to deactivate their account. It happens! Maybe you just tried a walkthrough out of interest, or you created a new account with a different name

Fly.io logo
Fly.io
•
Lubien
•4 min read•beginner•
--
•View Original
Docker

Overview

The article discusses the challenges and considerations involved in implementing a self-service account deactivation feature for Fly.io. It highlights the complexities of user account management, particularly when users share organizations and have associated applications.

What You'll Learn

1

How to navigate the self-service account deactivation process on Fly.io

2

Why careful consideration is necessary before deactivating an account

3

When to seek support for account deactivation due to shared organizations

Key Questions Answered

What are the steps involved in deactivating a Fly.io account?
To deactivate a Fly.io account, users must delete their apps, manage DNS records, and address any organization ownership issues. The self-service UI guides users through these steps, ensuring they do not abandon important resources.
Why is self-service account deactivation more complex than it seems?
Self-service account deactivation is complex due to factors like shared organizations and the potential loss of important applications and data. Ensuring users understand the implications of their actions is crucial to prevent accidental data loss.
What should users do if they encounter issues during account deactivation?
If users face issues during account deactivation, especially related to shared organizations, they are prompted to contact support for assistance. The UI will indicate if manual intervention is required.

Technologies & Tools

Some links below are affiliate links. We may earn a commission if you make a purchase.

Backend
Docker
Used to run applications on Fly.io as micro-VMs.

Key Actionable Insights

1
Implement a guided UI for account deactivation to minimize user errors.
This approach helps users understand the consequences of their actions and ensures that they do not accidentally delete important data.
2
Consider the implications of shared resources when designing account management features.
Understanding how users interact with shared organizations can prevent complications during account deactivation and improve user experience.
3
Encourage users to review their applications and organizations before deactivation.
This ensures that users are aware of any dependencies that may be affected, reducing the risk of unintended data loss.

Common Pitfalls

1
Users may accidentally deactivate their accounts without understanding the consequences.
This can happen if the deactivation process is not clearly communicated, leading to loss of important applications and data.
2
Failing to manage shared organizations can complicate the deactivation process.
If users are admins of shared organizations, they may not be able to deactivate their accounts without transferring ownership, which can lead to frustration.