How to Revoke Team Member Access on UniLink (Remove Users From Your Account)

Remove a team member's access from your UniLink account immediately — their login is disabled the moment you confirm.

When a contractor wraps up a project, an employee moves on, or a client relationship ends, removing their access to your UniLink account is not optional — it is a basic security hygiene step. An unused login with active team access is an unnecessary risk: credentials can be reused across platforms, phishing attacks happen, and former collaborators should not retain access to your live pages. UniLink makes revocation straightforward, instantaneous, and reversible if needed.

What Access Revocation Does

Revoking a team member's access removes them from your account's team list and immediately invalidates their permissions. On their next request to the UniLink API — including any already-open Dashboard tab — they receive an authorization error and are redirected to the login screen. Any action they attempt after revocation fails at the server level; they cannot complete a save, a publish, or a settings change even if they had one in progress at the moment of revocation.

Importantly, revocation does not delete the content they created. Pages, blocks, product entries, and other data associated with their work remain fully intact in your account. UniLink separates the access credential from the content. This design is intentional: a contractor who built ten pages for you should not be able to take those pages with them when their engagement ends, and you should not lose their work just because you need to remove their login.

Revocation is also reversible. If you remove someone by mistake, or if a returning collaborator needs access again, you can re-invite them from the same Team panel. They will receive a new invitation email and, upon accepting, have access again with whatever role you assign. The revocation is not a permanent blacklist — it is a removal of the current access grant, which can be re-granted at any time.

How to Get Started

1. Navigate to Dashboard → Team. Log in at app.unilink.us and click Team in the sidebar. This panel lists all current and pending team members with their roles and invitation status. You need Owner or Admin role to revoke access.
2. Locate the team member to remove. Find the member in the list by name or email. If you have a large team, use the search or filter controls at the top of the list to narrow the results. Verify you have selected the correct person before proceeding.
3. Click the three-dot menu (⋯) next to their name. This opens a small action menu with options for the member, including Change Role and Remove Access. Click Remove Access.
4. Read the confirmation dialog. UniLink displays a confirmation dialog that states the member's name, their current role, and the immediate effect of removal. It also notes that their content will not be deleted. Read this carefully before confirming.
5. Confirm the removal. Click Remove to confirm. The member disappears from the active team list immediately. If they have an active session, they will be unable to perform any further actions — the next API call they make will fail with an authorization error.

How to Use Access Revocation

1. Revoke access when an engagement ends. As soon as a contractor, employee, or agency relationship ends, revoke their access immediately. Do not wait until "after the transition period" — an unused login with active access is a liability. The revocation takes five seconds and can be undone if needed.
2. Revoke pending invitations that were never accepted. If you sent an invitation that was never accepted and the invitation period has expired or plans changed, you can also revoke pending invitations from the Team panel. Find the pending member (shown with a "Pending" badge), click the three-dot menu, and select Cancel Invitation.
3. Document the removal for audit purposes. After revoking access, note the removal in your internal team tracking document: member name, role they held, date of removal, and reason. This creates an audit trail that is useful for compliance reviews, security incidents, or client disputes.
4. Review remaining team members after a revocation. Use any access removal as a trigger to review the rest of your team list. Are all remaining members still active? Do their roles still match their current responsibilities? A revocation event is a natural checkpoint for a broader audit.
5. Re-invite if access needs to be restored. If you need to restore access to a removed member, go to Dashboard → Team → Invite Member, enter their email, and assign a role. They receive a new invitation email. There is no "restore" shortcut — it is a fresh invitation, and the role you assign now does not need to match their previous role.

Key Settings

Get the Most Out Of Access Revocation

The highest-risk moment for unauthorized access is the gap between a relationship ending and access being revoked. Most account breaches tied to former team members happen in this window — not out of malice, but because the person still has credentials and makes a change they thought was approved. Build a process where access revocation is the last step in any offboarding checklist, not an afterthought days later. If you manage an agency, include "revoke UniLink access" explicitly in your contractor offboarding checklist alongside revoking access to Slack, Google Workspace, and project management tools.

For agencies handing off client accounts to clients, the access flow typically runs in the opposite direction: you add the client as a team member, walk them through the platform, and then when they are ready to manage independently, you remove your own agency team members from their account. Coordinate this transition explicitly — make sure the client has Owner-level access and you have documented what is in their account before removing your team's access. Do not remove your access until the client confirms they can log in and navigate the Dashboard independently.

Content attribution after a team member leaves is worth a brief review. When you remove a member, their pages and blocks do not automatically reassign to another user — they remain as they are with the original attribution in the activity log, but there is no "unassigned content" flag. Create a habit of quickly scanning your Pages list after a significant team removal for any draft pages the departed member was working on. Draft pages that never get published are easy to miss, and a contractor's unfinished work can sit as an invisible draft for months.

Use the Viewer role as a step-down before full revocation when appropriate. If a team member is transitioning out over a two-week period — handing off work, answering questions, but no longer making changes — downgrade them to Viewer first. They can still see everything they need to support the transition but cannot make any changes. At the end of the transition window, revoke access completely. This staged approach reduces disruption while closing the risk window incrementally.

Troubleshooting