Stitchflow
Partnerize logo

Partnerize User Management Guide

Manual workflow

How to add, remove, and manage users with operational caveats that matter in production.

UpdatedMar 18, 2026

Summary and recommendation

Partnerize 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.

Partnerize is an enterprise affiliate and partner management platform.

It does not support native SCIM provisioning, so every app user lifecycle action - onboarding, role changes, and offboarding - must be handled manually through the admin console at console.partnerize.com.

Public documentation for user management is behind a login wall, which limits pre-implementation visibility into exact steps and permission boundaries.

Quick facts

Admin console pathSettings / Administration > Users and Roles (exact labels vary by tenant)
Admin console URLOfficial docs
SCIM availableNo
SCIM tier requiredN/A
SSO prerequisiteNo

User types and roles

Role Permissions Cannot do Plan required Seat cost Watch out for
Administrator Full account access including user management, campaign configuration, reporting, and billing settings. Specific permission boundaries between Administrator and other roles are not publicly documented.
User / Standard User Access to campaign reporting and operational features as configured by an Administrator. Cannot manage other users or access billing settings. Exact permission scope is not publicly documented; varies by account configuration.

Permission model

  • Model type: role-based
  • Description: Partnerize uses a role-based access model within its advertiser and agency console. Specific role names, granularity, and custom-role availability are not publicly documented in accessible help articles.
  • 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

  1. Log in as an administrator.
  2. Open settings or administration and navigate to users.
  3. Choose the add or invite user action.
  4. Enter the user's work email and assign the appropriate role.
  5. Save the user and complete any activation or SSO steps required by the tenant.

Required fields: Work email address, Role

Watch out for:

  • User management documentation is behind a login wall; specific steps could not be verified from public sources.
  • Partnerize is an enterprise platform; user provisioning processes may be handled via account management rather than self-serve UI.
Bulk option Availability Notes
CSV import Unknown Not documented
Domain whitelisting Unknown Automatic domain-based user add
IdP provisioning No Not documented

How to remove or deactivate users

  • Can delete users: Unknown
  • Delete/deactivate behavior: Official documentation on user deletion or deactivation behavior is not publicly accessible; behavior cannot be confirmed.
  1. Open the users area as an administrator.
  2. Locate the user to offboard.
  3. Disable, revoke, or remove the account using the controls available in that tenant.
  4. 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:

  • No publicly available documentation describes what happens to data owned by a removed user.

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: Partnerize pricing is custom/enterprise (reported from ~$2,000/month). Seat-level billing details are not publicly documented.

The cost of manual management

Partnerize operates on a custom enterprise pricing model. Because seat-level billing details are not publicly documented, tracking unused licenses requires manual audits against your own records rather than any built-in usage dashboard.

Every app user who retains access after departure represents both a security exposure and a potential billing liability that cannot be quantified without direct engagement with your Partnerize account manager.

The decision

Partnerize suits organizations that already have a dedicated account management relationship and can absorb the overhead of manual provisioning workflows. Teams expecting self-serve user management or IdP-native connectors (Okta, Entra ID, Google Workspace) will find neither available out of the box.

If your IT or security team requires documented, auditable offboarding steps, plan to establish those procedures directly with Partnerize support before go-live.

Bottom line

Partnerize's manual user management path is workable but opaque: no public step-by-step provisioning docs, no native SCIM, and no self-serve license visibility. Every app user's access depends on administrator-driven console actions and, in many cases, coordination with a Partnerize account manager.

Organizations with strict joiner-mover-leaver requirements should document their own runbooks early and confirm deactivation versus deletion behavior with Partnerize support before relying on either approach at scale.

Automate Partnerize 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.

Every app coverage, including apps without APIs
60+ app integrations plus browser automation for apps without APIs
IT graph reconciliation across apps and your IdP
Less than a week to launch, maintained as APIs and admin consoles change
SOC 2 Type II. ~2 hours of your team's time

UpdatedMar 18, 2026

* Details sourced from official product documentation and admin references.

Keep exploring

Related apps

Abnormal Security logo

Abnormal Security

API Only
AutomationAPI only
Last updatedMar 2026

Abnormal Security is an enterprise email security platform focused on detecting and investigating threats such as phishing, account takeover (ATO), and vendor email compromise. It does not support SCIM provisioning, which means every app in your stack

ActiveCampaign logo

ActiveCampaign

API Only
AutomationAPI only
Last updatedFeb 2026

ActiveCampaign uses a group-based permission model: every user belongs to exactly one group, and all feature-area access (Contacts, Campaigns, Automations, Deals, Reports, Templates) is configured at the group level, not per individual. The default Adm

ADP logo

ADP

API Only
AutomationAPI only
Last updatedFeb 2026

ADP Workforce Now is a mid-market to enterprise HCM platform that serves as the HR source of record for employee data — payroll, benefits, time, and talent. User access is governed by a hybrid permission model: predefined security roles (Security Maste