> ## Documentation Index > Fetch the complete documentation index at: https://docs.valkyrieapp.azumo.com/llms.txt > Use this file to discover all available pages before exploring further. # Workspaces and teams > Work with your organization in a shared workspace: members, roles, teams, invitations, model sharing, and a shared wallet. A **workspace** is where your models, endpoints, datasets, API keys, and wallet live. Everyone has a **personal workspace**, created with the account. To work with other people, create an **organization workspace** and invite them. Each workspace has its own: * **Wallet**, with its own balance, top-ups, and monthly spend limits. * **Members**, each with one [role](#roles). * **Teams**, groups of members you can share models with. * **Models, endpoints, datasets, and API keys.** Nothing crosses from one workspace to another. ## Personal and organization workspaces | | Personal workspace | Organization workspace | | - | - | - | | Created | With your account | By anyone, from the workspace switcher | | Members | Only you, as Owner | Anyone you invite | | Teams, invitations, sharing | No | Yes | | Rename, leave, delete | No | Yes, by role | ### Create an organization workspace **1. Open the workspace switcher** Click the workspace name in the top bar. **2. Create workspace** Click **Create workspace**, enter a **Name**, and click **Create workspace**. Workspace names are unique across Valkyrie. **3. Invite people** You're the new workspace's Owner, and it opens on **Settings**. It starts with an empty wallet, so [add funds](https://docs.valkyrieapp.azumo.com/guides/wallet-billing.md#adding-funds) before anyone trains or deploys. ## Switch workspaces The workspace switcher in the top bar lists every workspace you belong to. Pick one to switch: the dashboard reloads on **Home** in that workspace, and Valkyrie remembers it for your next sign-in. The **Balance** chip always shows the active workspace's wallet. Pending invitations also appear in the switcher, under **Invitations**, with **Join** and **Decline**. ## Roles Every member has one workspace role. | Role | In short | | - | - | | **Owner** | Everything, including transferring and deleting the workspace | | **Admin** | Members, teams, models, and billing | | **Billing** | Wallet, top-ups, and spend limits | | **Builder** | Fine-tunes and deploys models, and shares their own | | **User** | Uses the models shared with them | | **Viewer** | Sees everything, changes nothing | In detail: | Can they... | Owner | Admin | Billing | Builder | User | Viewer | | - | :-: | :-: | :-: | :-: | :-: | :-: | | See the workspace's models and endpoints | ✓ | ✓ | ✓ | ✓ | Shared ones | ✓ | | Call models and create API keys | ✓ | ✓ | | ✓ | Shared ones | | | Start fine-tunes and deploy (spends from the wallet) | ✓ | ✓ | | ✓ | | | | Manage a model and share it | ✓ | ✓ | | Their own | | | | Invite and remove members, manage teams | ✓ | ✓ | | | | | | Add funds and set spend limits | ✓ | ✓ | ✓ | | | | | Change roles | ✓ | Below Owner | | | | | | Transfer ownership, delete the workspace | ✓ | | | | | | * **Billing** and **Viewer** are read-only for models: a share or a team role never lets them call or change one. * A role that can't spend sees a notice instead of the **New fine-tune** and deploy forms, explaining what the role allows and suggesting asking an Owner or Admin for the Builder role. * A workspace can have several Owners. Admins can change or remove anyone except Owners, and only an Owner can make someone an Owner. The last Owner can't be demoted or removed. Change a member's role, or remove them, under **Settings > Members**. A removed member loses access straight away: their API keys in the workspace are revoked and they leave its teams. If they were using the workspace at the time, they are moved to their personal workspace with a notice. ## Teams A team is a group of members in one workspace. Share a model with a team and everyone on it can use it. A team can also have its own [monthly spend cap](https://docs.valkyrieapp.azumo.com/guides/wallet-billing.md#spend-limits). | Team role | What it adds | | - | - | | **Member** | Use the team's models and create keys for them | | **Maintainer** | Also manage the team's models and their access, and add or remove team members | Being on a team never lets anyone spend. Spending comes only from the workspace role. Owners and Admins create, rename, and delete teams under **Settings > Teams**. Only existing workspace members can join a team. Deleting a team moves the models it owns to the workspace, stops sharing models with it, and removes its spend cap; its members stay in the workspace. ## Invite people Owners and Admins invite people under **Settings > Invites**. **1. Enter the addresses** Under **Invite people**, enter up to 50 **Email addresses**, separated by commas or new lines. **2. Pick a role and a team** Choose the **Role** (User by default) and, optionally, a **Team**. Admins can invite with any role except Owner. **3. Send** Click **Send invitations**. Each person gets an email with a link. * **Links last 7 days** and work once. Someone without an account signs up from the link and doesn't need to verify their email again. * Signed in with the invited address, the link shows **Accept and join**. Signed in with another address, it asks you to sign out first. * **Resend** sends a fresh link and restarts the 7 days; the old link stops working. **Revoke** cancels an invitation. * Inviting the same address again replaces its pending invitation. * Invitations are rate-limited per person and per workspace. Over the limit, you're asked to try again later. People already signed in can also accept from the workspace switcher, under **Invitations**. ## Share a model A model's **Access** tab, shown to people who can manage the model, controls who can use it. * **Can use**: call the model and create their own API keys for it. * **Can manage**: also start, stop, and schedule it, and share it. Share with members, teams, or email addresses. The workspace wallet pays for the GPU while the model runs, whoever calls it. An email address that isn't in the workspace yet needs an invitation. Tick **Send invitations to emails outside this workspace**, pick the role they **Join as** and, optionally, a team. They get access to the model when they accept. Without the tick, the address is reported as not shared. Removing someone's access revokes the API keys they hold for that model at once. ## Who owns new work In an organization workspace, the **New fine-tune** and deploy forms have an **Owner** field: | Owner | Who manages it | Whose spend cap it counts against | | - | - | - | | **Me** | You, and anyone you share it with | The workspace's | | **Team: *name*** | The team's maintainers | The team's, then the workspace's | | **The workspace** | Owners and Admins | The workspace's | You can pick teams you're on; Owners and Admins can pick any team and the workspace. Under the field, the form shows the wallet balance and how much is left this month under the cap that applies. A fine-tuned version deploys with the owner of its fine-tune. ## API keys and MCP * An API key belongs to the workspace it was created in. It reaches only that workspace's models and stops working if you leave the workspace. See [API keys](https://docs.valkyrieapp.azumo.com/dashboard/api-keys.md). * The MCP key on the **API keys** screen acts in your personal workspace. ## Join by email domain An organization workspace can be linked to a company email domain. When someone verifies an address on that domain, they join that workspace as a **Builder**, alongside their personal workspace. Addresses that aren't verified never join. Linking a domain is done by the Valkyrie team: contact support to set it up. ## Leave, transfer, or delete a workspace Under **Settings > General**: * **Leave**: any member can leave an organization workspace. You lose access to its models, keys, and wallet, and need a new invitation to come back. If you're the last Owner, ownership passes to the longest-serving Admin, or else the longest-serving member. The last member can't leave; delete the workspace instead. * **Transfer ownership** (Owners): make another member an Owner, and optionally step down to Admin. * **Rename** (Owners and Admins). * **Delete** (Owners): type the workspace's name to confirm. Running deployments stop, every API key is revoked, pending invitations are cancelled, and the remaining balance is frozen.