> 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/add-change-revoke-or-restore-user-access.md).

# Add, change, revoke, or restore user access

Invite a teammate and manage their Podigee Ad Server role, scope, access period, revocation, and restoration.

This task shows how to manage user access in the Podigee Audio Video Ad Server. Use it when a person joins your team, changes responsibilities, leaves, or returns.

Podigee separates two steps:

1. Add the person to your Podigee team.
2. Give the person a role and access scope in **Monetization**.

An invitation does not give Monetization access. The person must join your Podigee team before you can give them a Monetization role.

## Before you start

You need:

* Access to **Monetization** and permission to manage people and access.
* An available team seat if you must invite a new person.
* The role that matches the person's work.
* The areas where the person must work.
* The start and end time for the access.

If you work alone, you do not need to create a team. Your workspace can operate with one person.

## 1. Open people and access

1. Go to **Monetization > Monetization settings**.
2. Open **People and access**.
3. Review the **Podigee team** and **People with monetization access** sections.

The Podigee team contains people who can sign in to your organization. The Monetization list shows which of those people can work in the Ad Server.

## 2. Invite a new teammate

Skip this step when the person is already an active member of your Podigee team.

1. Select **Invite teammate**.
2. Enter the email address that the person will use to sign in.
3. Select **Send invitation**.

![The Invite a Podigee teammate dialog with a fictional teammate email address ready to send.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-18f4041c918f8f9afec7cdb8c58f8d6a4127a423%2Fdoc-monetization-016-invite-teammate.png?alt=media)

*The invitation adds the person to your Podigee team. It does not give Monetization access.*

The invitation appears under **Waiting to join Podigee**. Wait until the person accepts the invitation before you continue.

![The Podigee team section with one pending invitation and a visible team seat limit notice.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-e8db210543fb6354894d549a49823a969bc5d0da%2Fdoc-monetization-016-pending-invitation.png?alt=media)

*A pending invitation uses a team seat. Add or manage seats before you invite another person.*

## 3. Give Monetization access

1. Select **Give access**.
2. In **Person**, select an active Podigee teammate.
3. In **Role**, select the role that matches the person's work.
4. Select an **Access coverage** option:
   * Select **Entire monetization workspace** for access to all current and future work.
   * Select **Only selected areas** when the person must work only with named accounts, Campaigns, inventory, podcasts, or other available records.
5. Set **Access starts** and **Access ends**.
6. Complete the confirmation or review that your workspace requires.
7. Select **Give access**.

Use the smallest scope that lets the person complete their work. Do not limit access when the person must work across the full operation and update the scope each time a new record is added.

![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)

*Select the person, role, scope, and access period in one form.*

Podigee shows the person as **Active** after the access is saved.

## 4. Change existing access

1. Find the person in **People with monetization access**.
2. Select **Change access**.
3. Review the current role, access coverage, and access period.
4. Change only the values that must change.
5. Complete the required confirmation or review.
6. Select **Save access**.

The saved values replace the person's current assignment. Use a new access end time when the work has a known end date.

![The Change monetization access form for Maya Chen with the current role and workspace scope.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-bc33d9a199390707136322a3145c260505448d35%2Fdoc-monetization-016-change-access.png?alt=media)

*Review the complete assignment before you save a change.*

## 5. End access

Use this action when a person leaves, no longer works in Monetization, or must lose access at a known time.

1. Open **Change access** for the person.
2. Go to **End access**.
3. In **Access ends at**, use the current time for an immediate revocation or select a future time.
4. If this person is the last workspace administrator, select an active replacement administrator.
5. Complete the required confirmation or review.
6. Select **End access**.

Podigee does not let you remove the last workspace administrator without a valid replacement.

![The End access section with the access end time, replacement administrator, and confirmation controls.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-d335fec7070c7866db0d4ec9721f0fad7c59c2d8%2Fdoc-monetization-016-end-access.png?alt=media)

*End access now or select a future boundary. Keep at least one workspace administrator.*

For an immediate revocation, the person changes to **Revoked**. Podigee keeps the person's last role and scope visible so that an administrator can understand the previous access.

![The people list with Maya Chen shown as revoked and a Restore access action.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-27c54a1028210328e519e080546da5106d5d1db3%2Fdoc-monetization-016-revoked-access.png?alt=media)

*Revocation stops the access. It does not delete the person's earlier work or the business records.*

## 6. Restore access

Use restoration only when a revoked person returns and must use the same workspace again.

1. Find the person with the **Revoked** state.
2. Select **Restore access**.
3. Review or change the role and access coverage.
4. Set a new access start and end time.
5. Complete the required confirmation or review.
6. Select **Restore access**.

![The Restore monetization access form for Maya Chen with a new access period.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-57be867e369df49995265e42f7d3ec41c4d25a70%2Fdoc-monetization-016-restore-access.png?alt=media)

*Restoration reuses the person record but requires a new review of the complete assignment.*

Podigee shows the person as **Active** after the restoration is complete.

![The people list with Maya Chen active after restoration and a confirmation message.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-98d0b5bcb60d6048455e721bac4bfdd7bfe178fc%2Fdoc-monetization-016-restored-access.png?alt=media)

*The confirmation and Active state show that the restored access is available.*

## If Podigee blocks the action

* **The person is not available:** Refresh the page. Confirm that the person accepted the Podigee team invitation and is still an active teammate.
* **The team seat limit is reached:** Manage or add team seats before you send another invitation.
* **A limited scope has no area:** Select at least one area, or select the entire Monetization workspace.
* **The date or time is invalid:** Correct the value. Podigee keeps the other values in the form.
* **The person or assignment changed while the form was open:** Open **People and access** again. Review the current assignment before you save.
* **The last administrator cannot be revoked:** Select an active replacement administrator, then try again.
* **A review is required:** Ask an eligible teammate to review the exact access change. The current access stays unchanged until the required review is complete.
* **Your permission was removed while the page was open:** Podigee rejects the next protected action. Refresh the page and ask a workspace administrator for the access that your work needs.

## Result

The person has the correct Podigee team state, Monetization role, scope, and access period. A revoked person cannot continue protected Monetization work, and restoration requires a new check of the complete assignment.

Next, learn how to select a standard role for a user's work.


---

# 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/add-change-revoke-or-restore-user-access.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.