---
title: Set up your workspace
display: 'Set up your *workspace*'
nav_title: Set up your workspace
summary:
  - "Tell the organization from its projects, and switch between them with the pill."
  - "Give each person an organization role (Admin or Member) and a role in each project (Owner, Contributor or Viewer)."
  - "Find every organization setting, and know that a project can only make it stricter."
description: How an organization, its projects and its members fit together, and the rules an enterprise sets once for every surface.
section: teams
order: 1
type: tutorial
level: Scale
roles: [admin]
time: { read: 2 }
models_checked: []
last_verified: 2026-11-11
# a lesson that points to its articles: their PDFs, not one of this page
pdf: false
video_caption: Set up your workspace
film_first: true
about: "How a Scenario workspace is built: the organization, the main level of governance, and its projects; the two roles every person has, one in the organization and one in each project; where settings live, and how a project can only narrow them; and how assets, models and workflows move between projects. The models and settings in this lesson are as of November 2026."
chapters:
  - { at: 0, title: "In this lesson", image: "/media/images/teams/set-up-your-workspace/ch-01-in-this-lesson.webp" }
  - { at: 17.1, title: "The workspace", image: "/media/images/teams/set-up-your-workspace/ch-02-the-workspace.webp" }
  - { at: 66.5, title: "Who can do what", image: "/media/images/teams/set-up-your-workspace/ch-03-who-can-do-what.webp" }
  - { at: 120.1, title: "Settings", image: "/media/images/teams/set-up-your-workspace/ch-04-settings.webp" }
  - { at: 169.4, title: "Moving work", image: "/media/images/teams/set-up-your-workspace/ch-05-moving-work.webp" }
articles: [set-up-your-workspace]
related: []
thumb: teams/set-up-your-workspace/thumb.webp
video: tutorials/set-up-your-workspace.mp4
steps:
  - title: "Read the pill"
    text: "Click the pill at the top left: Organizations on the left, the selected organization's Projects on the right with your role in each. Whatever you generate goes into the project selected here."
  - title: "Open Settings"
    text: "Click the gear next to the organization in the pill. The left panel has three layers: Organization for everything shared, Project for the project you are in, and You for your own preferences."
  - title: "Give each person an organization role"
    text: "Organization › Members lists seats, Invite Members, Import CSV, the Default usage limit and each person's Usage and Role. Each person is an Admin, who runs the organization, or a Member, who works in their projects only."
  - title: "Give each person a project role"
    text: "Project › Members: Invite a user to this project, pick a role and click Add. Owner manages the project, Contributor makes things, Viewer only looks."
  - title: "See how settings narrow"
    text: "Organization › Models is the list for the whole team, with Automatically enable new models and a switch per model in the Active column. Project › Models can only turn more models off; each shows Inherited until you change it."
  - title: "Know where every setting lives"
    text: "Under Organization: General, Members, Projects, Analytics, Activity Trail, Models, Quality Gate, IP Detection, Watermark, External Keys, Agent, API Keys, Webhooks, Billing and Compute planner. Most have a Project version that can only be stricter, including Usage limit for a project's spend cap."
  - title: "Move work between projects"
    text: "An asset: Transfer at the top right of the viewer, paste the other project's Project ID (from Organization › Projects) and click Transfer; a copy goes there. A model: Transfer Model in its menu; a workflow: export it, then Import it from the other project's Workflows page."
updated: 2026-11-11
canonical: https://learn.scenario.com/teams/set-up-your-workspace
---

Last updated: 2026-11-11

# Set up your workspace

> How an organization, its projects and its members fit together, and the rules an enterprise sets once for every surface.

In short:

- Tell the organization from its projects, and switch between them with the pill.
- Give each person an organization role (Admin or Member) and a role in each project (Owner, Contributor or Viewer).
- Find every organization setting, and know that a project can only make it stricter.


Before you invite anyone or set any rules, it helps to see how a Scenario workspace is built. This lesson walks through the Starforge Games organization: its projects, the two roles every person has, where the settings live, and how assets, models and workflows move from one project to another.

:::note As of November 2026
The models, settings and screens in this article are the ones Scenario offered in November 2026. New models and updates arrive often, so check the app for newer options before you choose.
:::

:::steps Quick version
1. Click the pill at the top left to see your organizations on the left and their projects on the right.
2. Click the gear next to the organization to open **Settings**: **Organization** for everything shared, **Project** for the project you are in.
3. Give each person an organization role (**Admin** or **Member**) and a role in each project (**Owner**, **Contributor** or **Viewer**).
4. Set rules at the organization level; a project can only make them stricter.
5. Move work on purpose: **Transfer** for an asset, **Transfer Model** for a model, export and import for a workflow.
:::

## Before you start

- **You need to be an organization Admin** to change organization settings. Members can see and use the projects they belong to, and nothing else.
- **Two levels hold everything.** The organization is the top level: it holds the plan, the shared credits, the members and every rule your team works under. Projects sit inside it and hold the work: assets, models, workflows and collections.
- **Content stays inside its project.** What you generate or train in one project is not visible in another until you transfer it.
- **Admin settings depend on your plan.** Several of the controls shown here (Quality Gate, IP Detection, Watermark, the Solo project mode) are Enterprise features.

## Step 1: Read the pill

Everything starts from the pill at the top left of the top bar. It shows where you are: here, the organization **Starforge Games** and the project **Tour Demo**.

Click it. Two columns open:

- **Organizations**, on the left, lists every organization you belong to. The **+** at the top of the column creates a new one.
- **Projects**, on the right, lists the projects of the selected organization, with your role in each one. **Recent** projects come first, then **Other projects**. Use **Search...** or the **A-Z** sort when the list gets long.

A good rule is one project per product, client or campaign, plus a sandbox for trying things out. Admins create new projects with the **+** at the top of the **Projects** column.

Whatever you generate goes into the project selected here, so check the pill before you start.

![The pill open: Starforge Games selected under Organizations, with its 17 projects on the right and the gear next to the organization](https://ufgc0c9mhl4ueq76.public.blob.vercel-storage.com/academy/f3cac9f8dd84bc6b969623995fd1e7ee6b684046824ac808bfa434d1980ba114.webp)

## Step 2: Open Settings

To manage all of this, click the gear next to the organization in the pill. (Each project has its own gear too, which opens the same page on that project's settings.) **Settings** opens with a left panel in three layers, the same layers as the workspace:

- **Organization** ("Defaults for every project") is for everything shared.
- **Project** ("Settings for this project") is for the project you are in.
- **You** ("Your personal preferences"), further down, holds your own profile and preferences.

## Step 3: Give each person an organization role

Permissions work in layers too. Start with the organization: open **Organization** › **Members**. The page shows how many seats are used and available, the **Invite Members** and **Import CSV** buttons, a **Default usage limit** card, and the list of **Organization Members** with each person's **Usage** and **Role**.

Each person is an **Admin** or a **Member**:

| Organization role | What they can do | Best for |
|---|---|---|
| **Admin** | Run the organization: billing, members, settings, models and project creation | Team leads, administrators, the account owner |
| **Member** | Work in the projects they are added to, and nothing else; no organization settings | Everyone who makes things, collaborators, clients |

![Organization › Members: 9 of 15 seats used, the Invite Members and Import CSV buttons, and each member's usage and role](https://ufgc0c9mhl4ueq76.public.blob.vercel-storage.com/academy/f2b4c0c4514125f46683f6e719b098fabf7cc3f0f73e79d58f2328492753fbe4.webp)

## Step 4: Give each person a project role

Then each project has roles of its own. Open **Project** › **Members**. Here you add people who are already in the organization (**Invite a user to this project**, pick a role, **Add**) and set their role in this project:

| Project role | What they can do |
|---|---|
| **Owner** | Manage the project's members and settings, and see its analytics |
| **Contributor** | Make things: generate, train, import and edit assets |
| **Viewer** | Only look at the project and its assets |

So every person has two roles: one in the organization, and one in each project they join. An organization Member can be the Owner of one project and a Viewer in another. The next lesson invites people and sets these roles.

![Project › Members for Tour Demo, with the Role filter open on Owner, Contributor and Viewer](https://ufgc0c9mhl4ueq76.public.blob.vercel-storage.com/academy/776dfadf563490bc468d3cbcc81b2f46d9cfadd716362c2d102231c5b7991816.webp)

## Step 5: See how settings narrow from organization to project

Settings follow the same layers. Take models.

Under **Organization**, **Models** is the list your whole team can use. At the top, **Project overrides** lists the projects that narrow it. Two switches set the default for new releases: **Automatically enable new models** (new models are available to your team as soon as they launch; turn it off to approve each release yourself) and **Display disabled models (admins only)**. Below are **Disable All Models**, **Enable All Models**, filters, and a switch per model in the **Active** column.

![Organization › Models with Project overrides, Automatically enable new models switched on, and the model list](https://ufgc0c9mhl4ueq76.public.blob.vercel-storage.com/academy/d0de1bb350030c23f9963f6c970d13801d200dd34ce0b09c8415d9c69759865d.webp)

Under **Project**, **Models** narrows that list for one project. Its **Model access** card says it plainly: you can disable more models for this project, but models blocked by your organization stay unavailable. Each model here shows **Inherited** next to its switch until you change it, and **Organization Settings** takes you back up a level.

The organization sets the default, and a project can only be stricter, never looser. Lesson 3 covers models in detail.

![Project › Models for Tour Demo: the Model access card and every model marked Inherited](https://ufgc0c9mhl4ueq76.public.blob.vercel-storage.com/academy/41110fe779f2bac4864ac22f310b87b88adcf920939962c9aa224522cadfde90.webp)

## Step 6: Know where every organization setting lives

Organization settings is where admins decide everything for the organization. The left panel, under **Organization**:

| Setting | What it holds | Lesson |
|---|---|---|
| **General** | Organization name, logo and **Organization ID** | This one |
| **Members** | Who is in, their organization role, seats, per-member limits | [People and access](https://learn.scenario.com/teams/people-and-access.md) |
| **Projects** | Every project, and its ID | This one |
| **Analytics**, **Activity Trail** | Usage over time, and who did what | [Spend and usage](https://learn.scenario.com/teams/spend-and-usage.md) |
| **Models** | Which models your team can use | [Model access](https://learn.scenario.com/teams/model-access.md) |
| **Quality Gate**, **IP Detection**, **Watermark** | Content controls on what gets generated | [Content and security](https://learn.scenario.com/teams/content-and-security.md) |
| **External Keys** | Your own provider keys | [Model access](https://learn.scenario.com/teams/model-access.md) |
| **Agent**, **API Keys**, **Webhooks** | The agent, programmatic access and job notifications | [Share and roll out](https://learn.scenario.com/teams/share-and-roll-out.md) |
| **Billing**, **Compute planner** | Plan, seats, compute units and forecasts | [Spend and usage](https://learn.scenario.com/teams/spend-and-usage.md) |
| **Support**, **Danger zone** | Help channels, and deleting the organization | |

Most of these have a project version too, under **Project**, which can only be stricter: **General**, **Visibility**, **Usage limit**, **Members**, **Analytics**, **Models**, **Quality Gate**, **IP Detection**, **Task attribution**, **Watermark**, **External Keys**, **Webhooks**, **Agent** and **Danger zone**.

Spend can be capped at every level: per project here, under **Project** › **Usage limit**, and per member or per API key. The project limit caps the compute units (CU) the project can spend per billing period, across all its members and API keys. Leave it empty for no limit. Only organization admins can change it.

![Project › Usage limit for Tour Demo: the CU field and Save limit, with the CU used this billing period](https://ufgc0c9mhl4ueq76.public.blob.vercel-storage.com/academy/a664201f8323fe3bab2f04a7eb9249f58da655b0378c594f28c074df28f06ff0.webp)

## Step 7: Move work between projects

Work never moves between projects on its own. Each kind of work has its own way across:

- **An asset.** Open it and click **Transfer** at the top right of the viewer. In **Transfer 1 asset**, paste the **Project ID** of the other project and click **Transfer**. A copy goes there, and the original stays where it was. You'll find every project's ID under **Organization** › **Projects** in Settings. You can also transfer from an asset's **...** menu in the gallery, or select several assets and use **Transfer** in the bar at the bottom.
- **A custom model.** Use **Transfer Model** in the model's menu.
- **A workflow.** Export it, then **Import** it in the other project from the **Workflows** page.

A transferred asset keeps its prompt and the main settings of its generation, but it can't be regenerated in the new project. You can only transfer to projects in the same organization.

![The Transfer 1 asset dialog: the asset is copied to the project you choose and the original remains in Tour Demo](https://ufgc0c9mhl4ueq76.public.blob.vercel-storage.com/academy/d6805fb83e3eb3f152d116d556dc64614be7b5286f37aa9ff16890a68c498a93.webp)

![The Workflows page for the Tour Demo project, with Create and Import at the top right](https://ufgc0c9mhl4ueq76.public.blob.vercel-storage.com/academy/04850952f353c4fc0c4213bd1a4ad476b9713eaf3d3569bc1488489dd9afd3fa.webp)

## Projects in more detail

- **Visibility (Enterprise).** Under **Project** › **Visibility**, a project is **Collaborative** (everyone in it sees and edits every asset and model, the default) or **Solo** (each person sees only their own work). Owners can switch at any time, for example Solo for early concepting, then Collaborative for production.
- **Project analytics.** Owners see the project's own activity under **Project** › **Analytics**.
- **Deleting a project.** **Project** › **Danger zone** › **Delete project**, then type the project's name. It removes the project's models, uploads and outputs for good, with no trash. Transfer or download what you want to keep first. You can't delete the last project in an organization.
- **Deleting the organization.** **Organization** › **Danger zone**. You can't delete one with an active subscription or your only organization.

## Common problems

| What you see | What to do |
|---|---|
| A generation landed in the wrong project | Check the pill before you generate; transfer the asset to the right project |
| Someone can't see a project | Add them under **Project** › **Members**; they must already be in the organization |
| Someone can see the project but can't generate | Their project role is **Viewer**; make them a **Contributor** |
| A project can't turn a model on | The organization has it off; only an Admin can enable it under **Organization** › **Models** |
| You don't see **Organization** settings | You are a **Member**; ask an Admin |
| A transferred asset can't be regenerated | Expected: the prompt and settings come across, the generation can't be replayed |

## What's next

The organization is where admins govern everything, projects hold the work, and every person has a role at both levels. Next, [People and access](https://learn.scenario.com/teams/people-and-access.md) invites your team, sets those roles and turns on single sign-on.

Source: https://learn.scenario.com/teams/set-up-your-workspace