Team Workspaces

A workspace holds your endpoints, your captured webhooks, and your credit balance. It's shared: everyone with access sees the same endpoints and the same capture history. Signing up creates a workspace for you and makes you its owner.

Invite a teammate

Only owners can send invites. The Invite member button is greyed out for everyone else.

1. Go to Team in the sidebar.
2. Click Invite member.
3. Type the teammate's address in the Email box and click Send invite.
4. SignalBin emails that address a link to accept.

The invite joins the table on the Workspace access page with a Pending badge in its Status column until it's accepted. It's tied to that one address and stops working after 7 days.

If it expires, send a new one to the same address. There's no way to extend an invite that's already out, and sending a fresh one to an address automatically cancels whatever invite was still pending for it. To cancel an invite without replacing it, open the three-dot menu at the end of its row, choose Revoke invite, and confirm with Revoke.

Everyone joins as a member. An invite can't grant owner directly, so promote the person once they've accepted.

Accept an invite

Whoever receives the email opens the link and either signs in to an existing SignalBin account or creates one. The account's email address has to match the address the invite was sent to. Acceptance takes effect immediately, with no approval step back on the owner's side.

Change a role or remove someone

Owners handle both from the three-dot menu at the end of a person's row in Team:

• Make owner promotes a member. For someone who's already an owner, the same slot reads Make member and demotes them.
• Remove member takes them out of the workspace, effective immediately. You'll be asked to confirm with Remove.

A workspace always needs at least one owner. When you're looking at the last remaining one, both menu items are disabled and the menu says so, so promote a second owner first if you're stepping back.

Removing someone revokes their access to that workspace and nothing else. Their SignalBin account survives, along with any other workspace they belong to.

Work in more than one workspace

The workspace switcher sits at the top of the sidebar, showing the current workspace's name and your role in it. Click it to see every workspace you belong to, with a checkmark against the one you're in. Click another to switch. Create workspace at the bottom of that menu opens a dialog asking for a Name; Create finishes it.

Creating a workspace makes you its owner and gives it its own welcome credit. There's no cap on how many you can create or belong to.

Switching changes what the rest of the app shows you. Endpoints, webhooks, billing, and team are all scoped to whichever workspace is currently selected.

Rename a workspace

Owners can rename one from Settings in the sidebar. Open the Workspace tab, edit the Name field under Operational settings, and click Save changes. Members see the same form with the fields disabled and a note that only owners can change these.

Roles and permissions

Every member holds one of two roles.

Capability	Owner	Member
Create and manage endpoints and destinations	Yes	Yes
View captured webhooks and replay them	Yes	Yes
View balance, usage, and purchase history	Yes	Yes
Buy traffic credit	Yes	Yes
View the team list and pending invites	Yes	Yes
Invite, revoke invites, change roles, remove members	Yes	No
Rename the workspace	Yes	No
Create, list, and revoke API tokens	Yes	No

INFO

Billing isn't owner-only. Any member can check the balance and start a checkout when credit runs low, which is worth knowing before you assume a teammate is blocked on you.

API tokens are owner-only, so anything driven by one is too, including the REST API and MCP. A member who needs programmatic access has to get a token from an owner or be promoted. A token's role is re-read from the workspace on every request rather than frozen at creation, so demoting the person who created it narrows what it can do straight away, and removing them from the workspace stops it working.

Signing in

SignalBin authenticates people either through Clerk or through its own email and password flow, depending on how the deployment is configured. That choice applies to the whole deployment rather than per member, and it doesn't change how membership or roles work. Either way, password and sign-in method changes happen through Manage account on the Account tab in Settings, not in SignalBin itself.

Next steps

• Billing, where credit and usage are tracked per workspace rather than per member
• MCP Integration, where API tokens are scoped to a single workspace, chosen when the token is created