GridGap For Business Workspaces

Use a Business workspace when GridGap stops being one person's private planning tool and becomes shared team work.

What changes in a workspace

Projects, versions, and results can sit in a shared company or workshop context instead of inside one user's personal account. That matters when one person owns billing, several people need access, and the work should stay with the business rather than with an individual.

A workspace is not just a shared folder. It has seat allocation, member roles, shared projects, workspace branding, and its own billing state.

Who should use it

Business workspaces are a good fit for installers, workshops, small businesses, project teams, and anyone who needs more than one person to work against the same project set. They also make sense when personal and business work need to stay separate instead of being mixed inside one account.

If you only need a private workflow, this may be more structure than you need. If several people need to collaborate, review, or manage projects, the workspace model earns its keep quickly.

How roles affect work

Owner, admin, member, and viewer are not cosmetic labels. Some people can edit projects. Some can manage members. Some can manage billing. Some are there mainly to review shared work.

A locked feature is not always a subscription problem. It may simply be a role problem. Billing and some workspace management tasks remain owner-only.

Why billing and workspace context matter

A Business workspace has its own billing context. That means it is separate from a user's personal Pro subscription. The same person can belong to both, but the workspace still has its own seat count, billing state, and member access rules.

That separation is useful because it keeps business work and personal work from bleeding into each other. It also means you should always check whether you are looking at personal billing, workspace billing, or workspace access when something does not look right.

How to get the most from it

Keep shared client or company work in the workspace. Leave personal projects private unless you intentionally import them. Use the members page to check access, the billing page to confirm subscription state, and workspace support tickets when the issue belongs to the shared context.

The workspace model works best when the team keeps one clear owner, clear roles, and a clean split between personal and shared work.