Summary and recommendation
Google DV360 user management can be run manually, but complexity usually increases with role models, licensing gates, and offboarding dependencies. This guide gives the exact mechanics and where automation has the biggest impact.
Google DV360 (Display & Video 360) is Google's demand-side platform for programmatic advertising, sitting under the Google Marketing Platform umbrella.
User management is handled entirely through the DV360 UI at displayvideo.google.com
there is no SCIM endpoint and no native IdP connector, so every app that relies on automated provisioning will hit a wall here.
Access requires a Google Marketing Platform contract;
pricing is CPM/media-spend-based with no per-seat fee.
Quick facts
| Admin console path | DV360 > Settings (gear icon) > Users |
| Admin console URL | Official docs |
| SCIM available | No |
| SCIM tier required | Google Marketing Platform |
| SSO prerequisite | No |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Admin | Full access to all partner and advertiser settings, including user management, billing, and all campaign operations within the partner. | Cannot grant access beyond the partner scope they themselves belong to. | Admin role is scoped to the partner level; an admin at one partner cannot manage users at another partner. | ||
| Standard | Can create, edit, and manage campaigns, insertion orders, line items, and creatives within assigned advertisers or partners. Can view reporting. | Cannot manage users, cannot access billing settings. | Access is further scoped by whether the user is granted partner-level or advertiser-level access. | ||
| Read-only | Can view campaigns, reporting, and settings within assigned scope. Cannot make any edits. | Cannot create, edit, or delete any entities. Cannot manage users. | Read-only users still consume a user seat within the platform. |
Permission model
- Model type: role-based
- Description: DV360 uses a role-based permission model with three fixed roles (Admin, Standard, Read-only). Roles are applied at either the partner level (granting access to all advertisers under that partner) or the advertiser level (scoped to specific advertisers). There are no custom roles.
- Custom roles: No
- Custom roles plan: Not documented
- Granularity: Role assigned per user, scoped to partner or one or more specific advertisers.
How to add users
- Sign in to DV360 at displayvideo.google.com.
- Click the Settings gear icon in the top navigation bar.
- Select 'Users' from the left-hand menu.
- Click the '+ New User' button.
- Enter the user's Google Account email address.
- Select the user role: Admin, Standard, or Read-only.
- Select the access scope: partner-level or specific advertiser(s).
- Click 'Save'.
Required fields: Google Account email address, User role, Access scope (partner or advertiser)
Watch out for:
- The invitee must have an existing Google Account (personal Gmail or Google Workspace account). DV360 does not create accounts.
- Users added at the partner level automatically receive access to all current and future advertisers under that partner.
- There is no email invitation flow; the user simply gains access upon being added and can log in immediately.
- Only users with the Admin role can add or manage other users.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | No | Not documented |
| Domain whitelisting | No | Automatic domain-based user add |
| IdP provisioning | No | Not documented |
How to remove or deactivate users
- Can delete users: Yes
- Delete/deactivate behavior: DV360 allows admins to delete (remove) users from the platform via the Users settings page. The DV360 API also exposes a users.delete method. Removed users lose access immediately. There is no separate 'deactivate' state documented; removal is the only offboarding action.
- Sign in to DV360 at displayvideo.google.com.
- Click the Settings gear icon in the top navigation bar.
- Select 'Users' from the left-hand menu.
- Locate the user in the list.
- Click the trash/delete icon or select the user and choose 'Remove'.
- Confirm the removal.
| Data impact | Behavior |
|---|---|
| Owned records | Campaigns, insertion orders, line items, and creatives created by the removed user remain intact and are not deleted. |
| Shared content | Shared assets such as creatives and audiences remain accessible to other users with appropriate access. |
| Integrations | Not documented |
| License freed | DV360 does not use named seat licenses in the traditional sense; pricing is CPM-based, so removing a user does not free a paid seat or reduce billing. |
Watch out for:
- Removing a user does not delete any campaign data or assets they created.
- There is no documented undo or restore function for a deleted user in the UI; the user would need to be re-added manually.
- If a user has partner-level access, they must be removed at the partner level, not the advertiser level.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Platform access | Access to DV360 UI and API for campaign management and reporting. | No per-seat fee; DV360 pricing is CPM-based (platform fee applied to media spend). Access is granted by Google Marketing Platform sales. |
- Where to check usage: DV360 > Settings > Users (lists all active users and their roles/scopes).
- How to identify unused seats: No built-in last-login or activity timestamp is displayed in the Users UI. Unused user identification requires manual review or use of the DV360 API (users.list) combined with audit logs if available.
- Billing notes: DV360 does not charge per user seat. Billing is based on media spend (CPM/platform fee model). Adding or removing users has no direct billing impact. Access to DV360 itself requires a Google Marketing Platform contract.
The cost of manual management
Because DV360 has no SCIM or IdP integration, every provisioning and deprovisioning action is a manual, one-at-a-time operation in the Users settings page. There is no bulk import, no CSV upload, and no last-login timestamp visible in the UI - identifying inactive accounts requires either a manual audit or scripting against the DV360 API.
For teams managing dozens of agency or advertiser users, this compounds quickly: a suspended Google Workspace account does not automatically revoke DV360 access, meaning offboarding requires a separate step in DV360 regardless of what happens upstream in your IdP.
What IT admins are saying
Community evidence is not specific enough to quote or summarize yet for this app.
The decision
DV360's permission model is straightforward: three fixed roles (Admin, Standard, Read-only) applied at either the partner or advertiser scope, with no custom roles available at any tier. Admin scope is bounded to the partner the admin belongs to - cross-partner user management is not possible from a single admin account.
Read-only users still consume a user seat, which matters for access-review hygiene even though there is no per-seat billing impact. Teams that need automated lifecycle management should plan to build or use an API-based workflow from day one, since no native automation path exists.
Bottom line
DV360 user management is functional but entirely manual by default. The three-role model is easy to understand, but the lack of SCIM support, bulk provisioning, and last-login visibility means access hygiene depends on deliberate process rather than tooling.
Teams operating at scale - multiple partners, frequent agency rotations, or strict offboarding SLAs - will need to invest in API-based automation to close the gaps the UI leaves open.
Automate Google DV360 workflows without one-off scripts
Stitchflow builds and maintains end-to-end IT automation across your SaaS stack, including apps without APIs. Built for exactly how your company works, with human approvals where they matter.
