Workspaces & members

A workspace is a tenant — its own roster of members, its own projects, sources, and widgets. Its limits come from the workspace owner's account plan (see Plans & billing). You can belong to several workspaces at once, switch between them in a click, and invite teammates into each one independently.

Creating a workspace

Open the workspace picker at the top of the sidebar → Create workspace. Give it a name; a URL slug is derived automatically as you type (until you edit the slug field yourself). Slugs are globally unique, 2–40 characters, lowercase letters, numbers, and hyphens — the dialog checks availability live and tells you if a slug is taken so you can pick another. You become the Owner of the new workspace.

How many workspaces you can own depends on your account plan: Free 1 · Pro 3 · Team 10 · Enterprise unlimited. Workspaces you were invited to never count against your quota — only ones you own. The limit gates creation only: if you downgrade while over the limit, nothing existing is locked or deleted.

Switching workspaces

The active workspace is in the URL — every dashboard URL starts with /w/<slug>, so bookmarks and shared links always deep-link to the right workspace. The workspace picker in the sidebar shows every workspace you're a member of with your role in each; picking one switches you over and Ploxir remembers it as your last-active workspace (that's where /dashboard drops you next time). The picker also shows a badge when you have pending invitations — they're listed at /dashboard/invitations.

Workspace name and URL

• Name — Admins and the Owner can rename the workspace from Settings → General. Renaming doesn't touch the slug, so existing URLs keep working.
• URL slug — Owner only, from the Workspace URL card in Settings → General. Changing it updates every workspace URL — old links and bookmarks stop working.

Roles

Roles are per-workspace, not global — you can be Owner of one workspace and Viewer in another. The ladder is Owner > Admin > Editor > Viewer, and permissions are checked again on the server for every action — hiding a button is never the only enforcement.

Two nuances worth knowing:

• Admins can't touch other Admins. An Admin can only flip members between Editor and Viewer, and can only remove Editors and Viewers. Promoting someone to Admin, demoting an Admin, or removing one requires the Owner.
• Editors create projects, Admins delete them. Creation is cheap and reversible-ish; deletion archives the project with its sources and widgets, so it sits one rung higher.

Inviting members

From Settings → Members (Admin or Owner), enter an email address and pick a role — Viewer, Editor (the default), or Admin. Owner isn't invitable; there is exactly one Owner per workspace, assigned only via ownership transfer. We email a single-use invitation link, and the accept URL is also shown to you so you can paste it into Slack yourself.

• Email-bound. The link only works for an account signed in with the invited email address — nobody else can accept it, even with the URL.
• Expires after 7 days. Resending issues a new token and a fresh 7 days; the old link stops working. Inviting the same email again does the same refresh rather than creating a duplicate.
• Revocable. Pending invitations are listed on the Members page with revoke and resend buttons until accepted.

Accepting an invitation

The link in the email looks like:

https://ploxir.com/invite/<token>

The page works signed-out — it shows the workspace name, who invited you, and the role you'd get, then branches:

• Not signed in — sign in or create an account with the invited email; you're returned to the invitation afterwards.
• Signed in as a different email — hard stop with a sign-out button. Invitations can't be accepted by an account they weren't addressed to.
• Signed in as the invited email — Accept or Decline. Accepting drops you straight into the workspace; declining deletes the invitation.

On accept, the inviter gets a notification that you joined, and the workspace's other Owners/Admins are informed in-app so the roster stays a shared source of truth.

Managing members

Settings → Members lists everyone in the workspace (sorted by role) plus all pending invitations. From the menu on each row, an Admin or Owner can — within the matrix above:

• Change role — the affected member is notified of their new access level. Nobody can change their own role, and the Owner role can't be assigned here (that's a transfer).
• Remove from workspace — access is revoked immediately and the removed person gets an email. Their Ploxir account and their other workspace memberships are untouched, and they can be re-invited later.

Transferring ownership

Owner only, from the Members page. Three rules apply, and the UI/server will tell you which one you're hitting:

1. The recipient must already be an Admin. Promote them to Admin first — the "Make owner" option only appears on Admin rows.
2. The recipient must have workspace headroom. Owning a workspace counts against the recipient's own plan quota (the same check as creating one), so the transfer is blocked if they're at their limit until they upgrade.
3. The workspace immediately follows the new owner's plan. Owner identity is billing identity: project and member limits switch to the recipient's account plan the moment the transfer completes. Your own subscription stays on your account and keeps covering the workspaces you still own.

The swap is atomic — you're demoted to Admin in the same operation that promotes them, so there's always exactly one Owner. Both parties are notified.

Leaving a workspace

Settings → Danger zone → Leave workspace, then confirm. You lose access immediately; the Owner and Admins are notified, and you land in your oldest remaining workspace (if it was your last one, a fresh personal workspace is created for you). You can be re-invited later. Owners can't leave directly — transfer ownership first, or delete the workspace.

Deleting a workspace

Owner only. Settings → Danger zone → Delete workspace, then type the workspace name to confirm. Everything inside is removed — projects, data sources, snapshots, widgets, memberships, pending invitations, and workspace notifications. This is irreversible — there is no trash or restore window. The other members are emailed that the workspace is gone (email is the only channel that survives the deletion).

Per-workspace isolation

Everything you'd expect to be isolated, is. Each workspace has its own:

• Projects, data sources, widgets, snapshots, webhook events.
• Member roster and pending invitations.
• Notification preferences — your settings in workspace A don't affect workspace B.
• Slack / Discord integration URLs.
• Seat usage — member limits apply per workspace, set by the owner's plan.

The one personal surface is the notification bell — it's a single per-account list that follows you across workspaces. You'll never see another workspace's metrics, members, or secrets in the current one, regardless of role.

FAQ

Can two workspaces share the same data sources?

No. Data sources live inside a project, which lives inside a workspace. If you need the same Stripe account aggregated into two workspaces, you connect it twice. This is intentional — it keeps the blast radius bounded if one workspace is compromised.

Why can't I invite anyone?

The most common reason is the seat limit: Free and Pro workspaces are single-member (just the owner), so inviting teammates requires the workspace owner to be on the Team plan (10 members per workspace) or Enterprise. The invite form tells you this explicitly when you hit the cap. The other reason: inviting requires Admin or Owner — Editors and Viewers don't see the invite form.

Do pending invitations count against the member limit?

No — only accepted members consume seats. The flip side: because the quota is re-checked at accept time, an invitation sent while a seat was free can still fail if the workspace fills up before it's accepted. The invitee sees a clear message to ask the owner for more seats and a fresh invite.

The invite page says "wrong account" — what do I do?

Invitations are bound to the email they were sent to. Sign out (there's a button on that page) and sign back in — or create an account — with the invited address. If the invite went to an address you don't use, ask the inviter to revoke it and send a new one to the right email.

Why is "Transfer ownership" not offered for my teammate?

Ownership can only be transferred to a current Admin — promote them first. If they're already an Admin and the transfer still fails, they're at their own plan's workspace limit (owning this workspace would exceed it); they need to upgrade or free up a slot before taking ownership.

What happens to billing when I transfer ownership?

The workspace switches to the new owner's account plan immediately — its project and member limits are theirs from that moment. Your subscription is not moved, cancelled, or changed; it stays on your account covering your remaining workspaces.

What happens to my workspaces if I delete my account?

Account deletion has a 7-day grace period you can cancel. When it executes: workspaces where you're the only member are deleted with the account; shared workspaces are preserved — ownership is automatically transferred to the highest-ranked remaining member (an Admin if there is one), and the workspace then follows that person's plan.

Can I rename a workspace or change its URL?

Rename: Admin or Owner, from Settings → General — the slug and all URLs are unaffected. Change the URL slug: Owner only, same page — old links and bookmarks stop working after a slug change, so tell your team.

Does removing a member delete their data or account?

No. Removal revokes their access to this workspace immediately (they're emailed about it) — their Ploxir account, their other workspaces, and everything they built here (projects, widgets) stay intact. Workspace content belongs to the workspace, not the person who created it.