> 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/organize-portfolios-business-units-shows-and-teams.md). # Organize portfolios, business units, shows, and teams Create clear operating boundaries for portfolios, business units, shows, and team members. Podigee Audio Video Ad Server gives larger operations clear boundaries for people and supply. After the first mention, this article uses Podigee Ad Server for the product name. Use a working context for the task in front of you, and use organization scope to control which records a team may manage. This structure prevents duplicate Commercial accounts, Campaigns, Creatives, and delivery records. It also helps a solo operator keep the workspace simple. Create a boundary only when it improves ownership or access. ## Before you start * You have an active Monetization workspace. * You know which shows, portfolios, Campaigns, or other resources belong together. * You have workspace administrator access to create or change a business unit. * You know which team members need access and which role matches their work. Use the existing workspace and show records. Do not create a second show or Commercial account to represent a team boundary. ## Choose the working context 1. Open **Monetization**. 2. Open the scope selector in the left sidebar. 3. Choose **All monetization** for work across the workspace. 4. Choose one show for show-specific work. 5. Check the sidebar and breadcrumb before you edit a record. ![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) *The selector lists only the shows that you can use.* The working context changes where you work now. It does not grant permission and it does not move, copy, or publish a record. Shared records remain shared when a show context is selected. ## Create a business unit Use a business unit for a stable operating boundary, such as a sales team, regional operation, or portfolio owner. 1. Open **Monetization > Monetization settings > Organization**. 2. Choose **Add business unit**. 3. Enter a clear name and a short code. 4. Add a cost center code when your finance process uses one. 5. Select a parent business unit when this unit belongs to a hierarchy. 6. Under **Connected areas**, select the exact resources that the unit may own and manage. 7. Set the effective time. 8. Review the impact notice. 9. Choose **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) *Connect only the resources that the unit must manage.* The resource selector can include the workspace, business units, Commercial accounts, brands, orders, Campaigns, portfolios, content, and legal entities that exist in your workspace. Select a portfolio when the portfolio is the correct responsibility boundary. Select a show-related content resource when the boundary must follow a show. The saved organization page shows the 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 check the boundary.* A change creates a new version of the business unit and its resource scope. It does not rewrite an older version. A future effective time keeps the current boundary active until the new time. ## Assign people to the correct boundary 1. Open **Monetization > Monetization settings > People and access**. 2. Choose **Give access** or **Change access**. 3. Select the person and the role that matches the work. 4. Select the entire workspace or only the business-unit resources. 5. Check that the selected scope includes the required shows, portfolios, and Campaigns. 6. Set the access period. 7. Complete the review or confirmation that your workspace requires. 8. Save the access assignment. ![The Give monetization access form with Maya Chen, the Monetization operator role, and the entire workspace selected.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-e7f16137d9ecbc548ed2b1b55d1334dbe97c807b%2Fdoc-monetization-016-assign-role-and-scope.png?alt=media) *Give each person the smallest scope that lets them complete the work.* The role controls what a person can do. The scope controls where the person can do it. A person needs both. A selected show does not override a narrower access assignment. ## Check the boundary in daily work 1. Switch to the business unit or show context that represents the team. 2. Open **Campaigns**, **Inventory**, **Creatives**, and **Evidence & Money**. 3. Confirm that the same records are visible in each area. 4. Open **Flightboard** and check that the expected shows and Campaigns are available. 5. Ask one operator to confirm that a record outside the boundary is not available for protected actions. Do not use a copied Campaign to make a record appear in another team view. Change the business-unit scope or the person's access assignment instead. ## Change a boundary safely 1. Open **Monetization > Monetization settings > Organization**. 2. Choose **Change** for the business unit. 3. Add or remove only the required connected resources. 4. Review the impact counts for assignments and resources. 5. Choose an effective time that does not interrupt work in progress. 6. Save the new version. 7. Check the people and access assignments that use the boundary. If the change fails, Podigee keeps the previous boundary. If an operator loses access after a boundary change, restore the missing resource or give the operator a narrower direct assignment. Do not create a duplicate team or show as a workaround. ## Expected result Each portfolio or business unit has a clear owner, connected resources, and a versioned boundary. People have roles and scopes that match their work. Shows, Campaigns, Creatives, reports, and delivery records remain single records with one source of truth. ## Next useful task Use [Add, change, revoke, or restore user access](/documentation/grow-and-monetize/monetization/add-change-revoke-or-restore-user-access.md) to manage a person's assignment. Use [Set the workspace and show scope](/documentation/grow-and-monetize/monetization/set-the-workspace-and-show-scope.md) when an operator needs to change the working context for one task. --- # 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/organize-portfolios-business-units-shows-and-teams.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.