Who Can Remove Whom: Access Control Inside an Ahrefs Shared Workspace
Removal inside a shared workspace is rarely the simple act people imagine it to be. When a colleague leaves the agency, when a contractor’s engagement ends, or when a client decides to bring SEO in-house, the instinct is to look for a delete button and move on. In practice, what you are doing is not deleting a person. You are changing an access-control state, and that change ripples outward into seat counts, billing, project ownership, saved reports, and the historical record your team relies on for continuity. That is the frame I want to establish before we get anywhere near the mechanics, because operations leads who treat removal as a permissions event make fewer expensive mistakes than those who treat it as housekeeping.
This article is written from the perspective of someone who owns billing and workspace governance for a mid-size SEO agency. We run dozens of client projects, we onboard and offboard specialists constantly, and we have learned the hard way that the question is never simply “how do I remove someone.” The real questions are: who has the authority to remove whom, what happens to the work that person touched, and how do we avoid locking ourselves out of our own account in the process. If you want the official reference on what a shared workspace is and how membership is structured, the Ahrefs documentation on how to remove from ahrefs workspacew is the authoritative starting point, and it is worth reading alongside this governance discussion rather than instead of it.
What a Shared Workspace Actually Is
A shared workspace is a collaborative container. It holds projects, reports, saved views, and the members who are allowed to see and act on them. The important mental shift is that the workspace is the unit of governance, not the individual user account. A person can belong to several workspaces, and their permissions can differ in each one. Someone who is an administrator in your agency workspace might be a limited member in a client’s workspace, or might not appear there at all.
This matters for removal because it means you cannot think in terms of “removing a user from Ahrefs.” You are removing a membership from a specific workspace. The person’s own account, their personal projects, and their presence in other workspaces are separate concerns. Getting this distinction right prevents the most common overreach, which is assuming that a removal is global when it is actually scoped.
It also reframes the emotional side of offboarding. When someone leaves, managers often want a clean sweep. The workspace model does not really offer a clean sweep; it offers a set of scoped decisions. Your job is to make each of those decisions deliberately rather than in a panic on someone’s last afternoon.
Roles and Permission Levels Inside the Workspace
Before you can reason about who may remove whom, you need a working model of the roles. Shared workspaces typically distinguish between an owner or administrator tier and a member tier, with the member tier often subdivided by what a person can view versus what they can change. The exact labels matter less than the underlying logic: some roles govern the workspace itself, including membership, and some roles govern only the content inside it.
Administrators are the ones who can invite, adjust access levels, and remove members. Members can work within the projects and reports they have been granted, but they generally cannot restructure the workspace or eject other people. This is the separation of duties that makes a shared workspace safe to use with contractors and junior staff. If everyone could remove everyone, a single disgruntled or careless action could disrupt an entire client engagement.
It is worth mapping your actual team onto these tiers before you ever need to remove someone. Write down who is an administrator, who is a full member, and who is a limited viewer. Keep that map somewhere outside the tool. When an offboarding request arrives, you will be answering from a document rather than from memory, which is the difference between a controlled transition and an improvised one.
Who Has the Authority to Remove a Member
Removal authority flows from the administrator tier. If you are an administrator of the workspace, you can remove members and adjust their access levels. If you are a member, you cannot remove anyone, including yourself in most configurations, and you should not expect to. This is not a limitation to work around; it is the control that keeps the workspace stable.
The practical consequence is that every agency should have at least two administrators, and ideally no more than a handful. One administrator is a single point of failure. If that person leaves, loses access to their email, or simply becomes unavailable, the workspace can become difficult to govern. Too many administrators, on the other hand, dilutes accountability and increases the chance that a removal happens without the billing owner knowing.
There is also a client-side dimension. If you are a guest in a client’s workspace, you almost certainly do not have removal authority there, and you should not ask for it casually. Requesting administrator rights in a client’s workspace to solve a one-time offboarding problem is a poor trade. Ask the client’s administrator to perform the removal, or coordinate the timing so that your own workspace changes and theirs stay in sync.
What Happens to Data and History After Removal
This is where most teams get surprised. Removing a member does not necessarily delete the projects, reports, or saved views that person created. In a shared workspace, that content typically belongs to the workspace rather than to the individual. The removed person loses access, but the work they contributed usually remains available to the remaining members.
That is generally the outcome you want. If a contractor built a reporting dashboard that your team still uses, you do not want it to vanish when their engagement ends. The history stays, the access goes. Understanding this lets you reassure stakeholders that offboarding will not destroy institutional knowledge.
The corollary is that removal is not a cleanup mechanism for bad data. If someone created duplicate projects or messy saved views, removing them will not tidy those up. You still need a content hygiene pass, done separately, by someone with the appropriate access. Treat membership changes and content changes as two different workflows, because they are.
There is also a personal-data consideration. When a person is removed, their ability to see client data ends, which is usually the compliance outcome you are after. But any exports they made while a member are outside your control. This is why removal should happen promptly when an engagement ends, not weeks later after the final invoice clears.
Billing, Seats, and the Cost of Getting Removal Wrong
Seat counts and billing are the reason removal is a governance topic rather than a purely technical one. Workspaces are often priced or limited by the number of members, so a stale membership is not just an access risk; it is a recurring cost. An offboarded contractor who was never removed can sit on your plan for months, consuming a seat that a current team member needs.
The reverse error is more disruptive. Removing the wrong person, or removing an administrator without a successor, can interrupt access for people who are actively delivering work. I have seen agencies lock themselves out of reporting during a client’s busy season because an offboarding was executed in a hurry by someone who did not check the administrator list first.
The discipline that prevents both errors is a short pre-removal audit. Confirm the person’s role, confirm that at least one other administrator remains, confirm that any projects they solely owned are still accessible to the team, and confirm the billing impact of the seat change. None of these checks takes more than a few minutes, and together they turn a risky action into a routine one.
A Pre-Removal Audit Checklist for Operations Leads
Run this checklist every time, even for departures you consider obvious. Consistency is what makes governance reliable.
First, identify the workspace or workspaces the person belongs to. Remember that a single individual may hold memberships in several workspaces, and removing them from one does not remove them from the others. If the goal is a full offboarding, list every workspace before you start.
Second, confirm your own authority. Are you an administrator in each of those workspaces? If not, identify who is and coordinate with them. Do not attempt workarounds.
Third, verify administrator continuity. Count the remaining administrators after the removal. If the number drops to zero, promote a successor before you proceed. This single step prevents the most damaging failure mode in workspace governance.
Fourth, review content ownership. Check whether the departing member is the only person with access to critical projects or reports. If so, grant access to a remaining team member first, so that continuity is preserved the moment the removal takes effect.
Fifth, check the billing and seat implications. Know whether the removal frees a seat you intend to reassign, and whether any plan limits change as a result. If you are the billing owner, this is the step you care about most.
Sixth, schedule the removal to match the person’s actual last working day. Removing access before a handover is complete creates avoidable friction; removing it long after the engagement ends creates avoidable risk.
Seventh, record what you did. A short note in your internal operations log, capturing the date, the workspace, the person removed, and who authorized it, gives you an audit trail. When a client asks six months later why a former contractor no longer appears, you will have the answer.
Common Mistakes and How to Avoid Locking Your Team Out
The most serious mistake is removing the last administrator. It sounds unlikely until it happens, usually during a rushed offboarding when the departing person happens to be the one who originally set up the workspace. Always promote a successor first, and verify the promotion has taken effect before the removal.
The second mistake is confusing workspace removal with account deletion. Removing a membership does not delete the person’s own account, and deleting an account is a different action with different consequences. Be precise about which one the situation calls for. Most offboardings need only the membership change.
The third mistake is leaving stale memberships in place because the removal feels awkward. A polite message explaining that access is being adjusted as part of standard offboarding removes the awkwardness. Framing it as process rather than as a judgment about the person makes it routine, and routine is exactly what you want.
The fourth mistake is assuming that removal is reversible without effort. Re-adding someone is possible, but if their access level or project grants were customized, those details may need to be reconstructed. When a departure might be temporary, such as a parental leave or a sabbatical, consider whether an access-level adjustment is more appropriate than a full removal. Downgrading someone to a limited viewer preserves the membership and avoids a rebuild later, while still restricting what they can do.
The fifth mistake is letting removal authority drift. Over time, agencies accumulate administrators who no longer need the role. Review the administrator list quarterly. Fewer administrators with clear accountability beats a long list nobody maintains.
Frequently Asked Questions
Can a regular member remove another member from a shared workspace?
No. Removal is an administrator-level action. Regular members can work within the projects and reports they have been granted, but they cannot change the membership of the workspace. If a member needs someone removed, the request should go to an administrator, ideally through a documented process rather than an ad hoc message.
Does removing a member delete the projects and reports they created?
In a shared workspace, content generally belongs to the workspace rather than to the individual member. Removing the person ends their access, but the projects, reports, and saved views they contributed typically remain available to the remaining members. This is usually the desired outcome, because it preserves continuity for the team.
What happens if we remove the last administrator?
You risk losing the ability to manage membership, access levels, and other workspace settings, because those actions require administrator rights. Always promote a successor and confirm the change before removing the final administrator. Keeping at least two administrators at all times is the simplest safeguard.
Is removing a member the same as deleting their Ahrefs account?
No. Removing a membership ends that person’s access to a specific workspace. Their own account and any other workspace memberships they hold are separate. Deleting an account is a different action with broader consequences, and most offboardings only require the membership change.
Should we remove someone temporarily or just lower their access level?
For temporary absences such as leave or a sabbatical, adjusting the access level is often the better choice. It restricts what the person can do while preserving their membership and any customized grants, so restoring full access later is straightforward. Reserve full removal for genuine departures.