Get started
Concepts: workspace, company, portfolio, project, roles, plans
A handful of words carry most of the structure in WorkBOS. This page defines them once so the rest of the docs can use them without re-explaining each time.
| Term | What it means |
|---|---|
| Workspace (org) | Your account. Everything you create lives inside it, and it is isolated from every other workspace at the database level: nobody outside it can see into it, whatever they are allowed to do inside their own. |
| Company | An optional grouping under a workspace, used when a workspace runs more than one business entity. A project can belong to one company; each company keeps its own invoices, bills and ledger, and a consolidated view rolls every company up together. See Multi-entity. |
| Portfolio | An optional grouping of related projects, for programme-level tracking above the individual project. A project can belong to one portfolio. |
| Project | The core unit of delivery: tasks, risks, a budget and a discussion live on it. A project can optionally belong to one company and one portfolio, or neither. |
| Role (access level) | Owner, admin, member, viewer or guest, set per person. Owner and admin manage the workspace; member works in it; viewer reads all of it and changes nothing; guest is limited to the projects they are added to. See Access & permissions for how this stacks with role templates and per-page settings. |
| Plan | What you are paying for, or the Free plan. A plan sets which modules and capabilities are available to switch on; Billing, plans & renewals covers how plans, seats and usage charges work. |
Guests are the one seat-exempt role: they do not count against your plan’s seat limit, and they are fenced to only the projects they were invited to, with no access to the wider directory, HR or finance data.
Was this page useful?