> For the complete documentation index, see [llms.txt](https://docs.podigee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podigee.com/documentation/grow-and-monetize/monetization/set-the-workspace-and-show-scope.md).

# Set the workspace and show scope

Choose a workspace-wide or one-show view, and set stronger responsibility boundaries for larger teams.

This task shows how to select the correct working context in the Podigee Audio Video Ad Server. It also explains when an administrator must create a stronger organization boundary for a portfolio or business unit.

Changing the working context does not move records, publish ads, or change delivery.

## Before you start

You need:

* An active Monetization workspace.
* Access to each show that you need to manage.
* Workspace administrator access if you need to create or change a business unit.

If a show is missing from the selector, do not create another show. Ask the account owner or a workspace administrator to check your Podigee access.

## Understand the two types of scope

Podigee uses two related controls:

* **Working context** controls where you are working now. Select **All monetization** or one show from the selector in the left sidebar.
* **Organization scope** controls which resources a business unit may own and manage. A workspace administrator sets this scope in **Monetization settings > Organization**.

The working context does not grant permission. Your role and assigned organization scope still control which records and actions you can use.

## 1. Work across all authorized shows

1. Open **Monetization**.
2. Select the scope control at the top of the left sidebar.
3. Select **All monetization**.
4. Confirm that the breadcrumb starts with **All monetization**.

![The Monetization scope selector open with All monetization and three authorized shows.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-e3c719bfc4ebcc0c7fa0698dbd89000549207386%2Fdoc-monetization-011-all-and-show-scope.jpg?alt=media)

*All monetization is the workspace-wide context. The selector lists only shows that you are authorized to use.*

Use **All monetization** for work that spans several shows, such as shared Commercial accounts, creative libraries, Campaign planning, reports, or team administration.

Some records are shared across the workspace. They can remain visible when you select one show. This behavior prevents duplicate advertisers, creatives, policies, and reports.

## 2. Work with one show

1. Open the scope control.
2. Select the show that you want to manage.
3. Confirm that the sidebar shows the show name and **Show monetization**.
4. Confirm that the breadcrumb starts with the show name.

![The Revenue Brief selected as the current Show monetization context in the Podigee Ad Server.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-af8315d860e05724c035d24cd032bf492f520be3%2Fdoc-monetization-011-selected-show-scope.jpg?alt=media)

*The selected show stays visible in the sidebar and breadcrumb while you work in Monetization.*

Use one-show context for show-specific work, such as ad breaks, delivery connections, and content selection. Use the sidebar navigation to keep the selected show while you move between areas.

You can also select **Podcast** in the product context switch. Podigee opens the same show in the podcast management context. Select **Monetization** to return to the same show.

## 3. Set a portfolio or business-unit boundary

Use organization scope when a larger operation needs a stable responsibility boundary. For example, one sales team can manage a portfolio while another team manages a different set of resources.

1. Go to **Monetization > Monetization settings > Organization**.
2. Select **Add business unit**.
3. Enter a clear name.
4. Enter a short code.
5. Enter a cost center code if your finance process uses one.
6. Select a parent business unit if this unit is part of a hierarchy.
7. Under **Connected areas**, select the exact resources that this unit may own and manage.
8. Set **Change takes effect** if the new boundary must start later.
9. Review the impact notice.
10. Select **Save business unit**.

![A business unit form with a name, short code, cost center, parent unit, and connected areas for responsibility scope.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-df504dbe4a65075a1c055fd1d4094308d18e0206%2Fdoc-monetization-011-business-unit-scope-form.jpg?alt=media)

*A business unit connects an operating team to selected workspace resources.*

The saved organization page shows the unit, its parent, and the number of connected resources.

![The Organization page with a Sponsorship Sales business unit and two connected resources.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-01c87afcc5dbbbbfd22714d5f05a4e46ac67db3a%2Fdoc-monetization-011-business-unit-scope.jpg?alt=media)

*Use the connected-resource count to confirm that the unit has the intended operating boundary.*

A portfolio is not an item in the sidebar scope selector. Connect the portfolio to a business unit, then assign people to the correct organization scope. Use the sidebar selector only to change the current workspace or show context.

## What changes when you select a scope

| Control                 | What it changes                                                     | What it does not change                                 |
| ----------------------- | ------------------------------------------------------------------- | ------------------------------------------------------- |
| All monetization        | The current context is workspace-wide.                              | It does not grant access to a show or publish anything. |
| One show                | The current context follows that show through supported navigation. | It does not hide every shared workspace record.         |
| Business-unit resources | The responsibility boundary for ownership and assigned access.      | It does not move or delete existing versions.           |

Reports and access assignments have their own saved scope. Selecting a show in the sidebar does not rewrite those saved settings.

## If you selected the wrong scope

1. Open the scope control.
2. Select **All monetization** or the correct show.
3. Confirm the sidebar and breadcrumb before you continue.

Your unsaved page input can be lost when you change pages. Save a draft first when the current form supports drafts.

If a business unit has the wrong resources, open **Monetization settings > Organization**, edit the unit, and select the correct connected areas. A future effective time preserves the current structure until that time. If the save fails, Podigee keeps the previous structure.

## Result

The sidebar shows the correct workspace or show context. If your operation needs a portfolio or team boundary, its business unit now contains the intended connected resources.

Next, set the default currency and the controlled values that operators can select.


---

# 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://docs.podigee.com/documentation/grow-and-monetize/monetization/set-the-workspace-and-show-scope.md?ask=<question>&goal=<endgoal>
```

`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.