--- title: "Account closures" slug: admin/account-requests url: https://projectri.com/docs/admin/account-requests section: admin audience: admin app_route: "/[slug]/admin/account-requests" mobile: "/admin/account-requests" updated: 2026-09-08 source: Projectri documentation --- # Account closures The queue of members who have asked for their account to be closed, with a 30-day clock on each and a note back to the person when it is closed out. ![Account closures](https://projectri.com/docs-shots/admin-account-requests.png) ## What it is When somebody asks from their own Settings screen for their account to be closed, the admins of their workspace are notified and the request lands here. This is the only screen where that request is visible as a piece of outstanding work with a clock on it. The clock is **30 days**, and it is the Privacy Policy's figure rather than a preference. A request past it is shown as overdue because the promise being broken is one made in writing. ## How to get there **Admin → People → Account closures**. It needs the **ADMIN** role — this queue and its route are role-gated. It sits under People rather than Security because it is a piece of outstanding work about a person, and the action it leads to is on [Members](/docs/admin/members) two rows up. ## How to use it ### Work the queue 1. The **Pending** tab is the default and carries the count. **All** shows closed rows too. 2. Each row shows the person, their address, the date they asked, and the deadline — *"26 days left"*, *"Due today"*, or an overdue count in red. 3. If they gave a reason when they asked, it is shown under the row. ### Close a request out The order matters, because marking a request completed does **not** delete anybody: 1. Go to [Members](/docs/admin/members) — the link is in each pending row — and remove them from the workspace. 2. Come back and press **Mark completed** on their row. 3. Add a note if you want to. It is carried into the message they receive. 4. Confirm. ### Decline a request 1. Press **Decline**. 2. Write a note. Do write one: a decline leaves the account open, and without a reason there is nothing the person can do about it. The note is included in what they are told. 3. Confirm. ## What it affects - **The person is told either way.** A completed closure tells them their membership has been removed; a decline tells them their account stays open, repeats your note, and gives them a privacy address to write to. - **Two admins can work the same queue.** The list updates live, so a row another admin closes out disappears from your screen without a refresh, and a new request appears without one. - **Removal happens on Members, with its own rules.** That path ends sessions, drops project memberships, cancels pending invites for the address and pauses any agents the person owned. A second path to it from here that skipped all of that would be a way to lose work by accident. - **The bell and this list agree.** The notification that brings you here and the queue it points at are the same data. ## On mobile The **Account closures** screen in the app's Admin hub is the same queue, and it exists there because the notification that opens it is a push — an admin typically learns about a closure request on their phone. Pending rows link across to Members in the app for the removal step. ## Limits and gotchas > [!WARNING] > **Marking a request completed is not an erasure.** It closes the request and > notifies the person. It does not delete their account, and it is not the same > thing as a data-erasure request — that is a separate pipeline under > [Privacy](/docs/admin/privacy). - A completed closure usually means the membership has already been removed, and a notification is not delivered to somebody who is no longer an active member. Nothing is lost by that; the notice a removed person cannot read is one they no longer need. If you want them to see it, close the request out before removing them. - A request can only be closed once. Reopening it is not possible from this screen — the person has to ask again. - The note is capped at 1,000 characters. - The list shows the 200 most recent requests. - A request from somebody who has already been removed shows without a name. ## Related - [Members](/docs/admin/members) — where the removal actually happens. - [Privacy](/docs/admin/privacy) — data subject requests, exports and erasure. - [Your profile](/docs/account/profile) — where a member asks for closure. - [Data and privacy](/docs/features/data-and-privacy) — what is kept, and for how long. ## Related - [Members](https://projectri.com/docs/admin/members.md): The workspace roster and the pending invite list — invite people, change roles, suspend, remove, and do any of those to many people at once. - [Privacy](https://projectri.com/docs/admin/privacy.md): The data-subject request queue with its statutory clock, how long each category of data is kept, legal holds that suspend deletion, and where this workspace's data lives. - [Your profile and preferences](https://projectri.com/docs/account/profile.md): The settings screen that belongs to you — name, avatar, language and timezone, theme, pinned projects, notification delivery, skills, shortcuts and your data. - [Data and privacy](https://projectri.com/docs/features/data-and-privacy.md): Where a workspace's data lives, how long it is kept, how a person gets a copy or has it erased, and why closing an account is not the same as erasure.