Workspaces

Everything you build in Vaulter lives in a workspace. Alone, you can ignore that fact entirely: your personal workspace is invisible plumbing. The moment you work with other people, the workspace becomes the thing you share: its projects, its token pool, its connected services, and its rules. This page is the map.

Personal and shared

• Your personal workspace is created with your account. It is just yours; the sidebar shows it as Personal, and member management does not appear because there is nobody to manage.
• A shared workspace is where a team builds together. Everyone you add works in the same set of projects, spends from the same token pool, and uses the same connected services. Adding people needs the Teams plan; every other plan is single-member.

Switch between workspaces from the sidebar; each keeps its own projects, plan, and settings. A workspace can carry its own logo, set on the workspace settings page, so teams are recognizable at a glance.

One role everywhere

Membership is the access boundary: your role in the workspace applies to every project in it. There is no per-project permission matrix to maintain, which is a feature: adding someone to the workspace is one decision, made once. If someone should only ever see one project, that is a reason to keep that project in a different workspace.

Moving a project between workspaces

Projects can move between workspaces, but there is no self-serve move button yet: contact support and we move it for you. Everything travels together (code, database, domain, published app), and from then on the destination workspace's members, pool, and rules apply. If a handoff to a client is what you are after, Handing off an app covers the options.

Private templates

A Teams workspace can save its own templates: when creating a template from a project, choose to share it with your workspace instead of publishing it to the marketplace. Workspace members can then start new projects from it; nobody outside the workspace ever sees it. Saving one is recorded in the audit log, since it copies the project's source where every member can clone it.

Running a workspace

The day-to-day operations, and where they live:

• Create a shared workspace from the sidebar's New workshop button.
• Switch between your workspaces in the sidebar; each remembers where you were.
• Rename a workspace, change its URL handle, or set its logo on the workspace settings page (owner or admin).
• Leave a workspace from its settings page. An owner cannot leave; they transfer ownership first, which promotes the new owner and steps them down to admin.

Deleting a workspace

Only the owner can delete a shared workspace, and the confirmation is explicit that its projects go with it: deleting the workspace deletes every project it contains. Move anything you want to keep out first.

Frequently asked

Do I need Teams to collaborate at all?

To build together, yes: Free, Starter, and Pro workspaces are single-member. What you can always share is the result; a published app has its own users, on any plan.

Can one account be in several workspaces?

Yes. You keep your personal workspace and can be a member of any number of shared ones, each with whatever role its owner gave you.

What happens to my personal projects if I join a team?

Nothing. Joining a shared workspace adds it beside your personal one; your own projects stay yours. Move a project into the team only when you want the team to have it.