Skip to main content
Your workspace is the organization boundary in Repost. Everything scoped to your team lives here: buckets, forwarders, event history, teammates, usage counters, and your subscription. The workspace area lets you manage access and billing without touching individual webhook streams.

What the workspace area covers

The workspace surfaces answer organization-wide questions. While a bucket page focuses on one webhook stream, the workspace area covers the state of the whole organization.

Dashboard

Monitor request volume, error rate, forwarding success, bandwidth, status mix, request geography, and top buckets across a selected time range.

Team

Invite teammates, assign roles, manage licensed seats, and handle pending invitations.

Plans & Billing

Compare plans, switch subscriptions, open the billing portal, and review invoices.

Who can manage workspace settings

Not every role has the same permissions in the workspace area. Understanding which actions belong to which role helps you know where to go and who to ask.
Owners have full control over the workspace. They can manage billing, change subscription plans, invite or remove team members, assign seats, create and revoke API tokens, and adjust any workspace setting. The workspace always protects at least one owner license so billing and access can always be recovered.

Reading the dashboard as a triage surface

Start at the workspace dashboard when you need a current health check for the whole organization. The aggregate cards surface the signal; you then navigate to the specific page where the action lives.
1

Choose a time range

Use the range selector to compare traffic across the window you care about — last hour, last 24 hours, or a custom range.
2

Spot the failing surface

Use the error rate, status mix, request geography, top buckets list, and failed forwarding count to identify which bucket or destination changed.
3

Navigate to the relevant page

Navigate to the bucket, forwarder history, team page, usage page, or billing page depending on what needs to change.
4

Keep workspace actions separate from ingestion actions

Use workspace pages for access, plan, and usage decisions. Use individual bucket and forwarder pages for webhook routing and delivery behavior.
The four dashboard summary cards show Requests (total accepted events), Error rate (share of 4xx and 5xx responses), Forwarded (successful delivery attempts), and Bandwidth (estimated payload bytes processed). Use these as starting points, not as the full picture.

Workspace guides

Each guide below covers one operational area and maps directly to what you see in the dashboard.

Team and seats

Invite members, assign roles, understand seat limits, and restore access after a plan change.

API tokens

Create personal and organization tokens for CLI use, CI jobs, and shared automation.

Account security

Manage your password, security settings, and active sessions from Account Settings.

Plans & billing

Upgrade, switch billing interval, handle downgrades, and open the billing portal.

Usage

Track current event consumption, quota limits, per-bucket breakdown, and overage.