Workspaces
A workspace is one GitHub organization or user account, the people who work in it, and the subscription that covers them. Everything else in Pealboard belongs to a workspace: portals, requests, customers, saved views, notification settings and API keys.
A workspace can never see another workspace’s data. That boundary is enforced in the database, not in the application, and it holds regardless of anyone’s role.
What is in a workspace
Section titled “What is in a workspace”| One GitHub connection | One installation of the Pealboard GitHub App. |
| Repositories | Whichever the installation grants and the plan allows. |
| Members | People who sign into Pealboard, each with a role. |
| Portals | Spaces where customers submit requests. |
| Views | Saved filters, sorts, groupings and layouts. |
| API keys | Credentials for scripts, integrations and the MCP server. |
| A subscription | Free, Team or Business. |
Who can change what
Section titled “Who can change what”- Roles decide what a member may do. See Roles.
- Billing and Delete workspace are the owner’s alone.
- Everything else an admin can do.
Billing, in one paragraph
Section titled “Billing, in one paragraph”A workspace is billed for its owner, admin and member roles. Viewers are free. Portal customers are never billed, on any plan, at any volume. Engineers who work in GitHub and never sign into Pealboard are never counted, because Pealboard has no idea they exist and does not need to. The quantity is recounted after every membership change and Stripe prorates the difference. See Billing.
Renaming and deleting
Section titled “Renaming and deleting”Both are in Settings → Workspace. Deleting a workspace removes portals, requests, customers, views and notification history. It changes nothing in GitHub.