# Workspaces Source: https://modulify.ai/docs/reference/workspaces The container that owns your projects, credits, billing and people. A workspace owns projects, folders, credits, billing and members. Every project belongs to exactly one workspace, and the workspace is the boundary for who can see what. The switcher at the top of the sidebar is where all of this starts. It shows the workspace you are in, and opening it lists every workspace you belong to. ## What a workspace holds Credits belong to the workspace, not to you. Everyone working in it draws from the same balance, and the switcher shows that balance as a bar reading `Credits` on the left and `N left` on the right, with the reset date underneath. Billing also belongs to the workspace. The plan is the plan of whoever owns it, which is why the switcher header reads something like `Pro ยท 4 members` under the workspace name. ## Your default workspace One of your workspaces is marked as the default, shown with a filled star in the switcher list and the tooltip `Default workspace`. Your free plan lives there: the free credits, the free project and the free site. That has two consequences. The default workspace cannot be deleted, and it cannot be transferred to someone else. Making a different workspace your default moves the free plan with it, and the dialog says so: `Your free plan moves to this workspace. Projects and sites in your current default lock until you subscribe or switch back.` ## Create a workspace Open the switcher and choose **Create Workspace** at the bottom of the menu. The dialog asks for a **Name** between 2 and 48 characters, with `Mdlfy, Inc.` as the placeholder. Pressing Enter in the field is the same as clicking **Create**. You can own up to 5 workspaces. Once you hit that, the menu item is disabled and reads `Workspace limit reached (5)`, and the API answers `You can create up to 5 workspaces!`. A new workspace starts on the Free plan with no subscription credits of its own, and it is not your default. It becomes the workspace you are in straight away and drops you back on the dashboard. If you have no workspaces at all, the menu shows `No workspaces` with `Create a workspace to start building projects.` and a **Create Workspace** button. ## Switch workspaces Open the switcher and click any row under **All workspaces**. Each row shows the avatar, the name, a star if it is your default, and the plan of its owner. If you are inside a project or a folder when you switch, you land back on the dashboard rather than on a page belonging to the workspace you just left. Switching also resets the connectors you had loaded. The same menu carries three shortcuts to the workspace pages: **Settings**, **Members** and **Plans**. ## Rename a workspace or change its avatar Go to **Settings** in the switcher menu, or the **Settings** link in the sidebar. The page is headed `Workspace settings` with `Workspaces allow you to collaborate on projects in real time.` The card has two rows. **Avatar** takes an image up to 10MB and shows a **Remove** button once one is set. **Name** is the same 2 to 48 character field as at creation, with a live character counter. Click **Save changes**, or press Enter in the name field. Both rows need the **Edit workspace** permission. Without it the field and the button are disabled and the button carries the tooltip `You do not have permission to do this.` ## Set a workspace as default Below the settings card is a **Default workspace** row. If this is already the default, the button reads `Default workspace` and is disabled with the tooltip `This is already your default workspace.` Otherwise it reads **Set as default** and opens a confirmation. Only the workspace owner sees this row. ## Transfer a workspace **Transfer workspace** sits in the red **Danger zone** at the bottom of Settings, and only the owner sees it. It is disabled for your default workspace, with the tooltip `You cannot transfer your default workspace. Set another workspace as default first!` The dialog asks for a **Recipient email**, then **Send invite**. The invite is good for 7 days, and while it is outstanding the dialog shows the recipient with an X to cancel and the line `A transfer invite is pending. The workspace moves once they accept it.` When the recipient accepts, ownership moves to them, the workspace stops being anyone's default, and any active subscription on it is cancelled so the workspace lands on the Free plan under its new owner. The previous owner loses access. The recipient cannot accept if they already own 5 workspaces. ## Leave a workspace **Leave workspace** appears in the Danger zone for members, not for the owner. The confirmation warns `You will no longer have access to this workspace or any of its projects.` An owner cannot leave. The API is explicit: `Workspace owner cannot leave workspace! Transfer ownership or delete workspace!` ## Delete a workspace **Delete workspace** is owner only and permanent. The confirmation reads `This action cannot be undone. It will permanently delete all members, projects, and workspace data.` Two things block it. Your default workspace refuses with `Your primary workspace cannot be deleted!`, and if it is the only workspace you own the button is disabled with the tooltip `You cannot delete your last workspace. You must have at least one workspace.` ## From an AI client over MCP `list_workspaces` and `get_workspace` read them, and `create_workspace`, `rename_workspace`, `set_default_workspace` and `leave_workspace` manage them. `get_workspace_credits` and `get_workspace_credit_usage` answer where the AI credits went, and `get_site_usage` reports how close your own default workspace is to its site limit. Reads need `workspaces:read`, ticked by default. Changes need `workspaces:write`, which is not. Deleting a workspace is deliberately not available over MCP, because it cancels the subscription. See [MCP tools](/docs/mcp/tools). ## Next - [Members and roles](/docs/reference/members-and-roles) covers inviting people and what each role can do. - [Your account](/docs/reference/your-account) is the personal settings that sit outside any workspace. - [Core concepts](/docs/getting-started/core-concepts) puts workspaces next to the other words the docs assume.