> 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/fix-missing-access-or-wrong-scope.md). # Fix missing access or the wrong Monetization scope Restore access to Monetization or correct the workspace and show scope without changing business data. Use this guide when Monetization is not visible, an action is unavailable, or the page shows the wrong workspace or show. Access has two parts: membership in the Podigee workspace and permission for the action in the selected scope. Do not create a new workspace, show, Campaign, or creative to work around an access problem. The original record may be hidden by the current scope or role. ## Check the current scope 1. Open the workspace selector in the Podigee sidebar. 2. Confirm the organization or workspace name. 3. Confirm whether the context is **All monetization** or one show. 4. If you work on one show, select that show again. 5. Check the breadcrumb and page title before you continue. ![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 workspaces and shows that your current access can use.* If the correct show is not listed, do not create a duplicate. Ask a workspace administrator to check your scope binding. Use [Set the workspace and show scope](/documentation/grow-and-monetize/monetization/set-the-workspace-and-show-scope.md) for the scope rules. ## Check whether Monetization is active Open **Monetization > Control Room**. * If the Control Room shows **Not configured**, the workspace has not been activated. Use [Activate your Podigee Ad Server workspace](/documentation/grow-and-monetize/monetization/activate-your-podigee-ad-server-workspace.md). * If the Control Room shows **Active** but the page is empty, keep the selected scope and continue with the permission checks. * If the Control Room is not visible, you may not have workspace access or Monetization access. ![An inactive Monetization Control Room with the workspace scope, Not configured state, Nothing is live notice, setup checklist, and activation action.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-bbd06e2bc571385ef21b4c86e7e9bc589f7dbb9e%2Fdoc-monetization-010-workspace-not-configured.jpg?alt=media) *Before activation, the Control Room confirms that no Campaign can serve and no listener request is affected.* ## Check your membership Ask a workspace administrator to check: * Your Podigee team membership is active. * Your invitation was accepted with the correct account. * Your access has not expired. * Your access has not been revoked or suspended. * Your role applies to the selected workspace or show. Use [Add, change, revoke, or restore user access](/documentation/grow-and-monetize/monetization/add-change-revoke-or-restore-user-access.md) to correct a membership or access assignment. A team invitation alone does not give Monetization permission. ## Check the action permission If you can open Monetization but cannot start an action, read the message near the action. It usually identifies the missing permission or scope. Ask an administrator to compare your role with the job you need to complete. Common examples: * **Campaign work:** campaign read, planning, or commit permission. * **Creative work:** creative read, upload, or suitability permission. * **Inventory work:** inventory read, prepare, or publish permission. * **Delivery work:** delivery read, enable, pause, or recovery permission. * **Reports and money:** report read, report management, reconciliation, invoice, or payout permission. * **Team and settings:** membership, role, policy, or workspace settings permission. The role must also cover the selected workspace, portfolio, business unit, or show. A role with the right action but the wrong scope cannot complete the task. ## Check an expired or scheduled boundary An access assignment can have a start or end time. Ask the administrator to check the current time zone, start time, end time, and the workspace membership state. Do not change the device clock to work around an expired assignment. If the administrator changes access, refresh the page and select the workspace and show again. Use the new access only after the page confirms the current scope. ## If the page still shows the wrong scope 1. Copy the visible workspace and show name, not a full internal identifier. 2. Record the page address, time, and action you tried. 3. Sign out and sign in with the account that received the workspace invitation. 4. Open Monetization again and select the workspace from the selector. 5. Ask the workspace administrator to compare the visible scope with the intended assignment. Do not change records while the scope is uncertain. A saved change in the wrong show can affect the wrong commercial operation. ## When to escalate Escalate to a workspace administrator when membership, role, or scope is wrong. Escalate to Podigee support when the administrator confirms the assignment but the page still denies access, shows an incorrect scope, or hides a known record. Include: * The workspace and show name. * Your account email. * The action and page where access failed. * The visible message. * The time and time zone. * The last confirmed scope and role. Do not include passwords, access tokens, or private provider credentials. ## Expected result You can open the intended Monetization workspace and show, see the records allowed by your role, and start only the actions covered by the current scope and permission. Business data remains unchanged while access is corrected. --- # 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/fix-missing-access-or-wrong-scope.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.