> For the complete documentation index, see [llms.txt](https://help.intangible.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.intangible.ai/teams-and-billing/workspaces.md). # Workspaces Personal workspace versus team workspace. What changes when you switch, and why team workspaces are the right home for shared client work. Each Intangible account has a personal workspace plus zero or more team workspaces. The dropdown at the top-left of the homepage switches between them. Switching workspaces changes what you see: different projects, different shared assets, different team members, different billing. ## Watch {% embed url="" %} ## What it does Personal and team workspaces are separate spaces. A project in your personal workspace is invisible from a team workspace and vice-versa. Team Assets, custom styles, and shared library items live in their team's workspace; they don't migrate when you switch. The intent is clean separation between what's yours and what's shared. ## Picking a workspace at sign-in If you belong to more than one workspace, signing in puts a **Choose a team** screen in front of you before the homepage. Each row names a workspace and its plan tier. Click one, and you land in that workspace with its projects, assets, and credit balance active. ![The Choose a team screen at sign-in, listing each workspace with its plan tier](https://1179478100-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSWrjIqlgVAblx6vHGJiM%2Fuploads%2Fgit-blob-e12ac251ddd63073cf1ec0328f52d65125c53f78%2Fchoose-a-team-01.png?alt=media) Pick deliberately. The workspace you choose here decides which credit balance a render bills against, so starting the day in the wrong workspace is how a client project ends up charged to a personal balance. If you get it wrong, switch with the dropdown described below; nothing is stuck. Opening a project takes you to the workspace that project belongs to, so a link from a teammate lands you in the right context regardless of what you picked at sign-in. ## How to switch The workspace dropdown sits at the top-left of every workspace, under the Intangible logo. Click; a list of every workspace you belong to appears. Click one to switch. When you switch: * The projects below the homepage fold change to that workspace's projects. * The asset library's My Assets and Team Assets categories swap to that workspace's assets. * Custom styles in the picker swap to that workspace's saved styles. * The credit counter shows that workspace's balance. * Notifications scope to that workspace. ## Personal vs team | Personal | Team | | ---------------------------------------------------------------------- | ---------------------------------------------------------------------------- | | Projects only you see | Projects every team member sees | | Renders bill against your personal credit balance | Renders bill against the team's credit balance | | Custom styles save under the Custom filter in your style preset picker | Custom styles save under the Custom filter and are available to team members | | Imports save to My Assets | Imports save to My Assets within the active team workspace | | No collaboration | Multi-user editing, owner / member permissions | If you're working solo, personal is fine. The moment a teammate or a contractor needs to be in the project with you, you need a team workspace, which requires a Business plan. See [Plans and billing](/teams-and-billing/plans-and-billing.md). ## When to use which * **Personal**: prototyping, learning, anything that won't go to a client. * **Team**: client work, agency work, anything that requires multi-user editing or shared review. For agency creatives, the common pattern is one team workspace per client (or per major client engagement). Saves cross-contamination of assets and credits, and lets you invite client-side reviewers as members of just their team. {% hint style="info" %} Once you create a team workspace, your default project home shifts to that workspace. You can still work in personal at any time by switching, but the team becomes the active default. Unselect by switching back. {% endhint %} ## Limits and known issues * **No cross-workspace asset sharing.** A custom style or imported model in Team A doesn't appear in Team B. Re-save in each workspace where you need it. * **Credit balances are per-workspace.** Personal credits don't subsidize team credits and vice-versa. * **No way to convert a personal project into a team project.** Once a project lives in a workspace, it stays there. Recreate in the other workspace if you need to move. ## Related * [Create and invite](/teams-and-billing/create-and-invite.md) * [Plans and billing](/teams-and-billing/plans-and-billing.md) * [Permissions](/teams-and-billing/permissions.md) * [Project ownership](/teams-and-billing/project-ownership.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.intangible.ai/teams-and-billing/workspaces.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.