Manage links
Workspaces & roles
Separate personal links from shared work and understand who can change them.
Current product guide · Reviewed October 28, 2026
Personal and shared scopes
Personal links belong to your account. Workspaces group links for accepted members and an owner. Choose the scope when creating links, domains, API tokens and webhooks; those scopes must match. Seeing a workspace in one view does not mean you can write to it.
| Role | Capabilities |
|---|---|
| Owner | Manage workspace members and workspace links; delete the workspace after password confirmation. |
| Editor | Read and change workspace links; eligible integration actions remain tied to the creating account and scope. |
| Viewer | Read accessible workspace links; cannot create, edit or delete them. |
Invite an existing account
- Open Workspaces and create a named workspace.
- Invite an existing verified, unsuspended account by email with Editor or Viewer role.
- The invited user accepts the pending invitation in Workspaces. A pending invitation does not grant access.
The current flow looks up verified, unsuspended existing accounts and shows in-app invitations. Do not assume that adding an email automatically provisions a new account or sends a separate invitation email. Owners cannot assign the platform Admin role through workspace settings.
Remove access thoughtfully
Removing membership changes authorization on later requests. Tokens, domains and webhook endpoints remain subject to current eligibility; a lost role is not a permanent authorization grant. If a shared domain depends on the removed registrant’s write access, routing can stop.
Workspace deletion requires the owner and current password. It affects workspace content and integrations; export what you need and review the confirmation before proceeding. Do not use deletion as a reversible pause.
Still need a hand?
Use Help & support in your dashboard or support@li2.li. Share the action and a sanitized error, never a password, token or private reset link.