Organizations and workspaces
An organization is your company or team. It has the plan, the billing and the members, and its slug starts every endpoint URL (in.webhookhq.dev/acme/…). One account can belong to several organizations; switch between them from the organization menu.
A workspace groups endpoints, like "Production" and "Staging". Every organization starts with a Default workspace. Create more on the Workspaces tab.
| Plan | Workspaces |
|---|---|
| Free, Developer | 1 |
| Pro | 3 |
| Team | 20 |
| Scale | 125 |
| Enterprise | Unlimited |
A workspace's managers can cap how many endpoints it has, under its settings ("Endpoint limit"), to keep it tidy.
Roles
Each member has a role in the organization:
| Role | Can |
|---|---|
| Owner | Everything, including billing and the plan |
| Admin | Manage members, workspaces, settings and service tokens; see billing |
| Member | Use the workspaces they've been added to |
Owners and admins manage every workspace. Workspaces are private: members see only the ones they're added to, with a workspace role. Giving members workspace roles is on Team and above.
| Workspace role | Can |
|---|---|
| Manager | Change the workspace's settings, endpoint limit and who has access |
| Editor | Create and change endpoints, destinations and secrets; replay and send test events |
| Viewer | Read endpoints and events, nothing more |
Add people in the workspace's settings, under Access, with Add someone. Example: contractors get viewer access to Staging only, so they can debug test events without seeing production data.
Invite people
On the Members tab, use Invite someone: enter their email, pick a role and click Send invitation. They get an email with a link; people who sign up from it join your organization directly. Pending invitations can be resent or revoked, and they count as seats until accepted.
| Plan | Seats |
|---|---|
| Free, Developer, Pro | 1 |
| Team | 10 |
| Scale | 25 |
| Enterprise | Unlimited |
Team trial: a Free organization can use Team free for 14 days, once, with no card: 10 seats, 20 workspaces and Team's features. It starts when you invite teammates or turn on a company email domain option during setup, approve a request to join, or click Start free Team trial on the Members tab. Afterwards the organization goes back to Free unless it upgrades.
Company email domain (Team and above): under Settings, an owner or admin whose own email is on the domain can claim it, such as acme.com, then:
- let people who sign up with an
@acme.comemail find the organization and ask to join. Their requests appear under Requests to join on the Members tab, to Approve or Decline; - only allow invitations to
@acme.comaddresses.
Personal email providers like Gmail can't be claimed.
Access tokens
The CLI, the API and the MCP server sign in with access tokens, not a password. Create one on the Access tokens tab:
- Personal: acts as you, with your role, and sees the workspaces you can open. Deleted if you leave the organization.
- Service: belongs to the organization, for CI and servers, and keeps working when people leave. Only owners and admins can create them.
Give it a name ("MacBook", "GitHub Actions"), choose when it expires (30 days, 90 days, 1 year or never), and click Create token. The token starts with whq_ and is shown once, right after you create it. The list shows when each token was last used. Revoke a token you no longer use, or one on a lost laptop: anything using it stops working at once.
whq login # paste whq_... when asked
export WHQ_TOKEN=whq_… # or set it in CI instead
Two-factor authentication
In Account settings, open Two-factor authentication and click Set up two-factor authentication. Scan the QR code with an authenticator app (1Password, Google Authenticator, Authy), enter the 6-digit code it shows, and save the ten one-time recovery codes for a lost phone.
From then on, signing in asks for a code after your password or after signing in with GitHub. Too many wrong codes lock the account, and resetting your password doesn't skip the code. Get new recovery codes replaces the old ones; turning two-factor off needs a current code and your password. It works on every plan.
Audit log
The audit log records who changed what and when: endpoints, destinations, secrets, members, access tokens, shares, billing and settings, whether by a member, through the API, by WebhookHQ staff or by WebhookHQ itself (a paused destination). It shows what changed from what to what; secrets only show that they changed.
Owners and admins open it from Settings with View audit log. It's on Team and above, but recorded on every plan and kept for a year, so upgrading shows the last year.
Example: deliveries to production stopped at 15:40. The audit log shows a teammate changed the destination URL at 15:39, so you know what to put back.
Share with people outside
Share a read-only view with someone who has no account, like a provider's support team:
- An event, on every plan: open it and expand Share.
- An endpoint, in its settings under Sharing, or a whole workspace, in the workspace's settings, on Team and above. These show webhooks as they arrive.
Choose who can see it: Anyone with the link (one link, shown once) or Specific people (each address gets its own link by email, and you can see who opened it and revoke people one by one). Shares expire in 1, 7 or 30 days, and Revoke ends one at once. Viewers never see your endpoint URLs, where webhooks are forwarded, or anything else in the organization. Each member can email shares to at most 30 people an hour, and an organization to 100; links aren't limited.