Summary and recommendation
Magnite 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.
Magnite is a sell-side advertising platform operating on a revenue-share model with custom contracts.
Its admin documentation is fully gated behind authenticated sessions, so user management details are not publicly verifiable.
Based on available data, user provisioning and role assignment are handled through the Magnite UI with no self-serve automation documented.
Quick facts
| Admin console path | Settings / Administration > Users and Roles (exact labels vary by tenant) |
| SCIM available | No |
| SCIM tier required | Custom |
| SSO prerequisite | No |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Admin | Can manage tenant settings, integrations, and user access. | Cannot grant capabilities outside the modules or features enabled for the tenant. | Detailed built-in role names are not fully documented publicly. | ||
| Standard User | Can use the core product features exposed to their assigned role. | May not be able to manage tenant settings, integrations, or other users. | Exact privileges can vary by tenant configuration and contract scope. |
Permission model
- Model type: role-based
- Description: Magnite appears to use role-based access for tenant administration and general product use, but the detailed permission matrix is not publicly documented in full.
- Custom roles: Unknown
- Custom roles plan: Not documented
- Granularity: Expect administrative access to be separated from standard user access, with exact scopes configured per tenant.
How to add users
- Log in as an administrator.
- Open settings or administration and navigate to users.
- Choose the add or invite user action.
- Enter the user's work email and assign the appropriate role.
- Save the user and complete any activation or SSO steps required by the tenant.
Required fields: Work email address, Role
Watch out for:
- Public documentation for user administration is limited, so exact labels may vary by tenant.
- If SSO is enabled, upstream IdP assignment may still be required before the user can sign in.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | Unknown | Not documented |
| Domain whitelisting | Unknown | Automatic domain-based user add |
| IdP provisioning | Unknown | Not documented |
How to remove or deactivate users
- Can delete users: Unknown
- Delete/deactivate behavior: Public docs do not clearly document whether users are disabled, deleted, or both. Treat lifecycle behavior as tenant-specific unless confirmed in-product.
- Open the users area as an administrator.
- Locate the user to offboard.
- Disable, revoke, or remove the account using the controls available in that tenant.
- Review any integrations, service accounts, or credentials associated with the departing user.
| Data impact | Behavior |
|---|---|
| Owned records | Tenant data remains in the workspace; public docs do not describe user-owned content semantics in detail. |
| Shared content | Shared content and workspace records typically remain available unless separately removed or reassigned. |
| Integrations | Review service credentials, workflow ownership, and integrations separately during admin offboarding. |
| License freed | Seat reuse behavior is contract-dependent and not publicly documented in detail. |
Watch out for:
- Offboarding should include token, integration, and service-account review, not just interactive login removal.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Named User | Access to the tenant features exposed to the assigned role. Seat entitlements are generally tied to the subscription contract. | Custom pricing; determined by contract and plan. |
- Where to check usage: Settings / Administration > Users and Roles
- How to identify unused seats: Review the tenant user list and any visible login or activity metadata. No public unused-seat report was verified.
- Billing notes: Magnite operates on a revenue-share model for publishers. Seat-based licensing details are not publicly documented.
The cost of manual management
Because Magnite has no publicly documented SCIM support, no IdP connectors, and no user management API, every app lifecycle event - onboarding, role changes, offboarding - requires manual UI action or a support ticket routed through an account manager.
Across a growing team, this creates compounding overhead: each joiner, mover, or leaver in every app tied to Magnite's ecosystem demands individual attention. Seat-based licensing details are not publicly documented, so identifying unused access or reclaiming licenses adds a further layer of manual investigation.
The decision
Magnite suits organizations that already have an account relationship and can absorb the overhead of UI-only user management. Teams expecting IdP-driven provisioning or automated offboarding will find no native path here - every app access change requires a manual step or vendor engagement.
If your IT or security team requires auditable, automated lifecycle management, factor in the coordination cost of working through Magnite's account management layer for any provisioning request.
Bottom line
Magnite's user management is entirely manual and opaque by default: no SCIM, no public API for identity operations, and no self-serve documentation on roles or permissions.
Every app access event depends on UI actions or account manager coordination, making it a high-touch integration for any team running structured access reviews or automated onboarding workflows.
Organizations with strict provisioning requirements should confirm capabilities directly with Magnite's enterprise team before committing to a workflow design.
Automate Magnite 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.
