Glossary
These words mean one thing each, on every screen, in every email, in this documentation and in the API. Where a word has a common synonym, the synonym is listed as what the product does not say, so that a support person quoting this page and a member reading a screen are using the same vocabulary.
Product nouns
Section titled “Product nouns”| Word | Meaning | Not |
|---|---|---|
| workspace | The tenant. One workspace is connected to one GitHub organization or user account. A person can belong to several workspaces. | organization (that is GitHub’s word, used only for the GitHub object), team, account |
| member | A person who belongs to a workspace, with a role. Members may or may not have a GitHub account. | user, teammate |
| role | What a member may do: owner, admin, member, viewer. |
permission level |
| issue | The GitHub object. Everything in the Issues screen is a GitHub issue in one of the connected repositories. | ticket, task, card, story |
| project | A GitHub Project belonging to the connected organization or account. Pealboard reads and writes its fields and items; it has no project type of its own. | board, epic |
| field | A GitHub project field: Status, Priority, Iteration, and custom fields. |
property, attribute |
| view | A saved filter, sort, grouping and layout over issues. Layouts are list, board and table. | filter, dashboard |
| board | The board layout of a view: columns grouped by a field, label group, assignee, milestone or state. Board is a layout, never an object. | kanban |
| portal | A space at <slug>.pealboard.com where customers submit and follow requests. A workspace can have many. |
help center, site, hub |
| customer | A person who signs into a portal. Customers are never workspace members and are never billed. | end user, portal user |
| requester | The customer who submitted a particular request. A per-request role, not a kind of person. | reporter, author |
| manager | A customer who may see every request in their company and invite other customers. | admin, lead |
| company | A customer organization inside a portal. Customers belong to one company per portal; company visibility is scoped to it. | organization, account, client |
| request | What a customer submits in a portal. Every request is an issue in GitHub; the portal shows the customer’s view of it. | ticket, feedback, submission, case |
| request type | A kind of request a portal offers — Bug report, Feature request, Question — with its form and its destination. | category, form, intake |
| form | The fields a customer fills in for a request type. | template |
| destination | Where a request type’s issues go: a repository, labels, optionally a project and initial field values, optionally an issue type. | mapping, route, routing rule |
| status | The word a portal shows for a request, derived from the issue’s state and the mapped project Status. |
stage, state (GitHub’s word for open and closed, used only for that) |
| public comment | A comment a customer can see: written in the portal, or written by a member with Reply to portal. | external comment |
| internal comment | Any other comment on the issue. Customers never see one. | private note |
| attachment | A file a customer or member adds to a request, stored by Pealboard. | upload |
| API key | A credential for scripts, integrations and the MCP server. Prefix pb_. |
token |
| installation | The GitHub App installation that connects a workspace to GitHub. In screen copy, “GitHub connection”. | integration |
| sync | Pealboard keeping its copy equal to GitHub. Every object shows when it was last synced. | import, refresh (allowed as a verb for a manual sync) |
GitHub’s words, used unchanged
Section titled “GitHub’s words, used unchanged”repository, organization, issue, pull request, label, milestone,
assignee, project, field, iteration, issue type, sub-issue, open,
closed, completed, not planned, installation.
When one of these names a GitHub object, it is GitHub’s word and Pealboard does not translate it.
The seven status words
Section titled “The seven status words”The only words a portal customer ever reads for the state of a request:
Open · Planned · In progress · Waiting on you · Completed · Merged · Closed
They are derived from the issue and the project’s Status field, and never
stored. See Statuses.
Words that do not appear
Section titled “Words that do not appear”ticket, kanban, epic, story, sprint (the word is iteration, which is GitHub’s), seamless, effortless, supercharge, powerful, robust, leverage, journey, delight, simply, just.
If you find one of these on a screen or in an email, it is a defect. Report it to support@pealboard.com.