Skip to content
Interface language: English
Design / Signal

Close your account - but what happens to the team's projects?

Design account closure without confusing a person, a team and shared projects: dependencies, role transfer, confirmation and the resulting state.

Article language: English

Illustration of two people at a table before a large circular structure and mountains.
In this article

A "Delete account" button takes up little space. Its consequences can reach from one person to an entire studio. Will the person lose the ability to sign in? Their team membership? The projects they created? Or perhaps the shared workspace that five colleagues will return to tomorrow? Red answers none of those questions. It can raise the tension before a choice has even been made.

A well-designed exit starts by naming the action and its scope. Only then should the warning, confirmation and next steps be chosen. The aim is not to stop people leaving at any cost. Someone should be able to leave knowing what they are leaving to the team and what will actually stop working.

Consider a hypothetical portal for agreeing packaging designs. Marta is ending her work with a studio. She has a personal account and belongs to two teams. In one she is the sole owner. Shared projects contain client comments, files and deadlines. This is a fictional design example, not a description of a deployed portal or a promise of its features.

Name the thing before issuing the warning

"Account" can be a convenient shorthand for a designer and a trap for the person using the product. If one identity gives access to several teams, leaving one of them need not mean deleting that identity. The screen needs to show the team's name, the person's role and the effect of the chosen action. Closing the entire account can be offered elsewhere.

In our portal Marta selects "Leave the Print Shop team". She is told that her membership of that team will end, while her account will still give her access to the other studio. She should not see a generic "Your account will be deleted". If she chooses to close her account permanently, the scope is wider and both memberships need to be shown.

Slack describes account deactivation separately for each workspace and notes that messages and files already sent will not be deleted by it. That is how one particular service works. It shows why the end of a person's access and the fate of their contributions need separate names, rather than hiding both under "account".

Set out the distinctions in your own product model: a person's account, team membership, ownership of a project and the whole workspace. They need not be four adjacent red buttons. They may belong on different screens and be available to different roles. The description and confirmation should refer to the same thing that the system will actually change. "Leave Studio" and "Delete the Studio workspace and its projects" cannot lead to the same "Are you sure?" dialog. A person must be able to recognise the difference even when they reach the screen through an old link, without visiting settings first.

In an employee departure and access handover procedure (in Polish), the team also assigns responsibilities beyond any one tool. A self-service screen cannot replace that work. It can, however, show the dependencies the portal recognises before Marta confirms the end of her access.

Do not confuse this path with a moderation restriction and a request for review (in Polish). Someone who can no longer publish should not receive a message suggesting they voluntarily closed their account. They need to know their actual status and how to seek an explanation. The reason for a restriction belongs in the communication model, not just a technical list of error codes.

Keep collaboration possible

Marta is the sole owner of the second team. The leave button should not lead to an empty "Operation not possible". Show the specific dependency: "You are the only owner of the Studio team. Transfer this role before leaving the team." The next step should lead to the choice of an eligible person, not a general help page.

GitHub requires the sole owner of an organization to resolve its ownership before deleting their personal account. It also distinguishes resources owned by the person from their contributions in other people's repositories. We are not importing that entire rule into the packaging portal; we need our own decision for each kind of resource.

Transferring a role is a separate action. If the system requires the recipient to accept, sending an invitation means the transfer is pending, not complete. If the role changes immediately, the message should show the actual change. Marta needs to know whether she can leave yet, and the new owner needs to know what they have received.

Do not transfer the role to someone chosen only from a list of email addresses. In our example, the recipient must already belong to the relevant team and meet the role's requirements. If they must be invited first, show that dependency. Sending an invitation to collaborate, joining the team and becoming an owner are successive states that can finish at different times.

GitHub's instructions for transferring an organization recommend giving the new person the role and making sure they can access organization settings. This is a useful example of confirming that someone can act. A name appearing on a list is not an adequate description of a handover of responsibility.

In the fictional portal, consider what happens if the selected person loses their permissions before the transfer is completed. A list from a few minutes ago cannot unconditionally determine the present state. Show what changed and how to make another choice. Do not end Marta's membership while a required condition remains unmet.

Aeneia conceptual photography

Also check projects assigned to a particular person. If Marta stops organising after transferring one of three projects, returning should show the two that remain and the result of the earlier change. Making her start over may encourage her to transfer the same resource again. The list should describe current dependencies, not reproduce the initial view regardless of actions already taken. "Team owner" and "person who approves a project for a client" can be different roles. Transferring the first need not change the second. The dependencies screen should distinguish them and identify tasks needing a decision, rather than promise to fix every connection automatically.

In an Aeneia Design project, this flow can be mapped as screen states and transitions: leaving, a dependency, a transfer and its result. It lets the team discuss scope with the delivery partner through concrete situations before deciding where the red button belongs.

What Marta needs to read before confirming

The final screen should describe the chosen operation. In our example, when leaving Studio it shows the team's name, the loss of access to shared projects and the fact that those projects remain available to others. Closing an account needs a broader scope covering all recognised memberships. Do not add one sentence saying "applies to everything" to a message about one team.

Show dependencies as specific items. Project "Box A" is waiting for the person who approves it to be reassigned. Project "Label B" already has a new person responsible. A generic "You have active projects" is not enough if, after clicking, the user still cannot tell which needs action or how to act.

Decide separately what happens to private drafts. Transferring a shared project should not quietly expose personal notes that their author never added to the team. The screen can separate "shared materials" and "private drafts" and offer the appropriate available actions. Design requires a map of actual rights to objects, not just a count of files assigned to a name.

The confirmation must match how the operation is carried out. If closure is immediate and irreversible, do not promise a later return via a button in an email. If there is a delay or cancellation is possible, give the correct time and route. Distinguish backing out before submitting a request from cancelling an operation that has already been scheduled.

Atlassian describes a fourteen-day period for cancelling a self-service account deletion request. After that, deletion is permanent. This is a feature of the service and account type described, not a deadline to paste automatically into any portal. Our screen must reflect its own process.

Typing the team name can be an additional confirmation for a particularly serious operation, but it cannot replace an explanation of the consequences. Someone can copy "Studio" perfectly and still believe they are removing only their own access. Explain the difference first, then choose a justified level of confirmation. Leaving a single project does not always require the same ceremony.

A reason for leaving may help improve a service, but it should not obscure the decision itself. If the question is optional, offer a way to skip it. Pausing or changing a plan (in Polish) may be a useful alternative when it meets the person's need. Do not place it so that the actual closure option becomes hard to find. Opening the screen alone should not change roles. But if Marta has already transferred a project separately, backing out of account closure must not hide that fact. On returning to work, show the current state: the account remains active, and previously confirmed transfers still apply under the portal's rules.

After the click, show the actual state

A submitted request does not always mean the action is complete. If an operation is pending, the screen should say so and identify the account or team concerned. If it fails, Marta needs to know whether she still belongs to the team. A generic sign-out after a lost connection can look like success even though nothing changed.

If confirmation has not arrived and the network is unavailable, the message should honestly say the outcome has not been confirmed. The result can only be checked once contact with the service returns. Do not make submitting another request the only suggested way out of uncertainty. The pending-state design needs to account for checking the previous operation's outcome, and the delivery team should confirm how the system recognises a repeated request.

Once a person has left, do not leave an editor open in a way that suggests they can still save. Another browser tab may remain on an old view. The design should provide for refusing further saves, explaining the change in access and giving a safe route to the current state. This does not itself guarantee technical revocation of every session; that implementation needs a separate check.

Describe what happens to materials according to confirmed rules. Retention and deletion of data copies (in Polish) involve more than the profile view. An avatar disappearing does not justify saying "all data has been deleted" if the operation does not have that scope. Questions about data rights and obligations need the appropriate resolution beyond the screen design itself.

Do not conflate closing a personal account with withdrawing an entire service from customers (in Polish). In the first case other users may continue working. In the second, their shared path changes. The operation's name, messages and contact route should match the situation that actually applies.

After account closure, a route to clarification cannot require signing into that same account. Point to a channel that the actual support service handles and a way to identify the case. A confirmation message need not include the names of every confidential project. It can confirm the scope of the action and let someone refer to it without sending team content outside the portal.

For acceptance, run a test with two people and a shared project. One leaves after the role is transferred correctly. The other can still open the project and carry out the intended task. The departing person sees confirmation of the correct scope. Record the outcome for the departing person and the remaining team separately. The button can be accepted only when it has ended the intended access and the project remains available according to the agreed decision.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear