Personal Vs Business Workspace
GridGap separates personal work from shared business work. That separation is deliberate. It keeps private projects, team projects, billing, and access rules from getting mixed together.
What the personal workspace is for
The personal workspace is your private side of the app. It is where your own projects, your own personal subscription, and your own private working history live.
If you only need a private calculator workflow, this may be all you need. The personal workspace is also where private experiments or personal planning can stay separate from team work.
What a Business workspace is for
A Business workspace is the shared side of GridGap. It is designed for organisations or teams that need shared projects, shared member access, and a separate workspace billing context.
In the app, the workspaces area shows your Personal Workspace alongside any Business workspaces you belong to. Each Business workspace has its own name, status, role, and member count.
The two contexts stay separate
Personal and Business do not merge into one common pool of projects. A personal project is not automatically a workspace project, and a workspace project is not part of your personal workspace just because you belong to that workspace.
The same is true for billing. Personal billing stays separate from workspace billing even when the same login uses both.
Why the active workspace matters
GridGap uses an active workspace context. If you open a personal project, you should be in the personal workspace. If you open a Business project, you should be in that exact Business workspace.
This matters because project visibility, editing rights, PDF export access, and shared-workspace tools depend on the active context matching the project you are trying to work with.
How access works in a Business workspace
Business workspaces also use roles. The live app distinguishes between owner, admin, member, and viewer.
In normal active workspace use, owners, admins, and members can edit workspace projects. Viewers can review shared workspace content but do not have the same editing powers. Workspace billing remains owner-only, and member management is handled by owners and admins.
Seat limits and workspace state also matter
A Business workspace is not only about role. The workspace must also be active and within its seat limit. If a workspace goes over its paid seat count, some shared functions can be restricted until the owner or admin resolves that problem.
So if a feature is missing in a workspace, the cause may be the role, the workspace subscription state, or the seat limit rather than the project itself.
A simple way to think about it
Use the personal workspace for private work. Use the Business workspace for shared work. Switch deliberately between them and treat them as separate operating contexts, not as two views into the same project pool.