What lives in a workspace
| Lives in workspace | What it means |
|---|---|
| Projects | Every Vibely build — Web App, Mobile App, or Vibely Design — belongs to exactly one workspace |
| Members | Invited collaborators with roles (Owner, Admin, Editor, Viewer). The Admin role is available on Pro and Business; Free workspaces only have Owner, Editor, Viewer. |
| Member groups (Business) | Named groups used for bulk project access grants |
| Connected accounts | GitHub, Supabase, Vercel, EAS — shared across every project in the workspace |
| Connectors | Slack, HubSpot, Google, Notion tokens — workspace-scoped OAuth / API keys |
| Billing | Plan, monthly credit grant, top-up history, invoices, per-member caps |
| Workspace-wide settings | Name, slug, logo, default visibility, SSO (Business), audit log, Security Center (Business) |
Creating a workspace
Click your avatar → New workspace. Pick a name and a slug (the URL identifier used in share links), attach a payment method, choose a plan. The workspace is ready to use immediately — projects, members, and connectors can be added right away. You can be a member of many workspaces. The switcher in the top-left lets you jump between them; everything (project list, connectors, billing) swaps to the new context instantly.Free includes a single workspace. Pro and Business unlock unlimited workspaces — useful for separating client work, side projects, and your day job.
Personal vs. team workspaces
The structure is the same; the difference is intent.- Personal workspace — created automatically on sign-up. Just you, your projects, your billing. Most people stay here for solo work.
- Team workspace — you create it explicitly and invite people. Roles control who can do what. Billing is workspace-level, not per-member.
- Client workspace (agency pattern) — typically one workspace per client. The client pays (or you pay and bill them), you ship work, then transfer ownership at handoff.
When to split workspaces
Splitting workspaces is cheap; merging them later is not. A few rules of thumb:- Different products under the same umbrella usually belong in separate workspaces, especially if they have different stakeholders or budgets.
- Personal vs. work — keep weekend projects out of your company workspace. Tax records and project ownership get cleaner.
- Client work — one workspace per client lets you transfer ownership at handoff without exporting / importing anything.
Switching workspaces
The workspace picker in the top-left shows everything you have access to. Switching is instant — the project list, connectors, member list, and billing all swap to the new context. Each workspace remembers its own last-opened project, so coming back doesn’t lose where you were.Renaming or deleting a workspace
Admins can rename the workspace and update its slug from Settings → General. Slug changes update share URLs immediately; old URLs stop resolving, so plan the rename when you’re not mid-handoff. Deletion lives in the same panel under Danger zone and is owner-only. It cascades to every project, deploy, connector, and member access record — only the audit log of the deletion itself is preserved.Plan gating at a glance
| Feature | Free | Pro | Business |
|---|---|---|---|
| Multiple workspaces | — | ✅ | ✅ |
| Team seats + Admin role | — | ✅ | ✅ |
| Custom subdomain on deploys | — | ✅ | ✅ |
| Custom domains | — | ✅ | ✅ |
| Workspace templates | — | — | ✅ |
| Member groups + group grants | — | — | ✅ |
| Audit logs | — | — | ✅ |
| Security Center | — | — | ✅ |
| SSO (SAML / OIDC) | — | — | ✅ |
| MCP connector policy | — | — | ✅ |
| Domain-restricted invitations | — | — | ✅ |
| Branded subdomain | — | — | ✅ |
Next
People
Invite members, assign roles, and manage access.
Project settings
Per-project configuration: collaborators, GitHub, secrets, model pinning.
Admin settings
Billing, connected accounts, security policies, audit log.
Customize Vibely
Account-level personalization that follows you across workspaces.