Stitchflow
X Ads logo

X Ads SCIM guide

Connector Only

How to automate X Ads user provisioning, and what it actually costs

Native SCIM not available

Summary and recommendation

X Ads, the advertising platform formerly known as Twitter Ads, does not support SCIM provisioning on any plan. While X offers basic SSO integration through Okta for authentication, this only covers login—not user lifecycle management. User access to X Ads accounts must be managed manually through the platform's multi-user login feature at ads.X.com, where account administrators must individually invite users and assign permission levels (Account administrator, Ad manager, Campaign analyst, Organic analyst, Creative Manager). This manual process creates significant overhead for IT teams managing advertising access across multiple campaigns and teams.

The lack of automated provisioning becomes particularly problematic for enterprises running complex advertising operations with frequent team changes, seasonal contractors, or cross-functional campaign teams. IT administrators cannot automatically provision users when they join advertising projects or deprovision them when campaigns end, creating both security risks and administrative burden. Since X Ads operates on a pay-per-performance model where unauthorized access can directly impact advertising spend, manual user management introduces compliance risks around financial controls and access governance.

The strategic alternative

X Ads has no native SCIM. Automate offboarding, user access reviews, and license workflows across every app, including the ones without APIs. We maintain the integration layer underneath. You focus on judgment, not plumbing.

Quick SCIM facts

SCIM available?No
SCIM tier requiredN/A
SSO required first?No
SSO available?Yes
SSO protocolSAML 2.0
DocumentationNot available

Supported identity providers

IdPSSOSCIMNotes
OktaGeneral X (Twitter) integration for authentication. No SCIM provisioning for ads platform.
Microsoft Entra IDVia third-partyNo official Entra integration for X Ads
Google WorkspaceVia third-partyNo native support
OneLoginVia third-partyNo native support

The cost of not automating

Without SCIM (or an alternative like Stitchflow), your IT team manages X Ads accounts manually. Here's what that costs:

Source: Stitchflow research, normalized to 500 employees:
Orphaned accounts (ex-employees with access)5
Unused licenses12
IT hours spent on manual management/year85 hours
Unused license cost/year$3,500
IT labor cost/year$5,100
Cost of compliance misses/year$890
Total annual financial impact$9,490

The X Ads pricing problem

X Ads gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.

Tier comparison

PlanPriceSSOSCIM
Free accessFree platform access
Pay-per-click/impressionVariable ad spend

Pricing structure

PlanPriceSSOSCIM
Free accessFree platform access
Pay-per-click/impressionVariable ad spend

What this means in practice

Without SCIM provisioning, every user addition, role change, or removal requires manual intervention:

New hires
IT must manually invite users through the X Ads interface
Role changes
Permission updates (Account administrator, Ad manager, Campaign analyst, Organic analyst, Creative Manager) require manual reassignment
Offboarding
Departing employees must be manually removed from all ad accounts
Audit compliance
No automated provisioning logs or centralized user lifecycle management

This creates security risks when employees change roles or leave the company, as their X Ads access may not be immediately revoked.

Additional constraints

Multi-user login dependency
Access control relies entirely on X's built-in multi-user feature rather than enterprise-grade provisioning
Manual permission mapping
The five permission levels must be manually assigned and cannot be automated through IdP group membership
No centralized visibility
IT administrators have no single view of who has access to which X Ads accounts across the organization
Inconsistent integration support
While Okta offers basic SSO integration, Microsoft Entra has no official X Ads integration at all

Summary of challenges

  • X Ads does not provide native SCIM at any price tier
  • Organizations must rely on third-party tools or manual provisioning
  • Our research shows teams manually provisioning this app spend significant hidden costs annually

What X Ads actually offers for identity

Multi-user Access (All accounts)

X Ads provides basic multi-user functionality through their ads platform:

FeatureDetails
Access methodManual invitations via ads.x.com
Permission levelsAccount administrator, Ad manager, Campaign analyst, Organic analyst, Creative Manager
User managementManual invite/remove process
SSO supportNone for ads platform

Critical limitation: Every user addition, role change, or removal requires manual intervention through the X Ads interface. No automated provisioning exists.

Okta Integration (General X platform only)

The Okta Integration Network listing covers general X (Twitter) authentication, not the ads platform:

FeatureSupported?
SAML SSO✓ Yes (main X platform)
SCIM provisioning❌ No
Ads platform access❌ Not covered
User lifecycle management❌ No
Group management❌ No

Translation: The Okta integration handles authentication for personal/business X accounts, but provides zero identity management for the advertising platform where your team actually works.

Microsoft Entra Integration

No official integration exists between Microsoft Entra and X Ads. Organizations using Entra must manage X Ads access entirely outside their identity provider.

What IT admins are saying

X Ads's lack of automated provisioning creates operational overhead for IT teams managing advertising access:

  • Manual user invitations required for every new team member
  • No automated deprovisioning when employees leave the company
  • Permission management scattered across multiple X Ads accounts
  • SSO available but doesn't eliminate manual account creation steps

The multi-user login feature helps with collaboration, but we still have to manually invite each user and set their permission level. There's no way to sync this with our identity provider.

IT Director, Enterprise Software Company

When someone leaves the marketing team, we have to remember to remove them from all our X Ads accounts manually. It's easy to forget, especially with contractors.

Systems Administrator, Digital Agency

The recurring theme

X Ads treats user management as an afterthought, forcing IT teams to maintain separate user lifecycles for advertising platform access alongside their primary identity management workflows.

The decision

Your SituationRecommendation
Small advertising team (<10 users) with stable membershipManual user management is workable
Medium advertising agency (10-30 users) with regular team changesUse Stitchflow: automation saves significant admin overhead
Enterprise marketing team with compliance requirementsUse Stitchflow: essential for audit trail and access governance
Multi-brand organization managing multiple X Ads accountsUse Stitchflow: automation critical for complex permission management
Agency managing client accounts with frequent contractor accessUse Stitchflow: automated provisioning prevents access sprawl

The bottom line

X Ads offers no SCIM provisioning—just manual user invitations through their multi-user login feature across five permission levels. For marketing teams that need automated user lifecycle management and proper access governance, Stitchflow delivers the provisioning automation that X Ads doesn't provide.

Make X Ads workflows AI-native

X Ads has no native SCIM. We build complete offboarding, user access reviews, and license workflows across every app, including the ones without APIs.

Covers apps without native SCIM, including the ones without APIs
Less than a week, start to finish (~2 hours of your time)
Built with your team; extend to anything else in the company
Book a Demo

Technical specifications

SCIM Version

Not specified

Supported Operations

Not specified

Supported Attributes

No SCIM provisioning supportUser access managed through multi-user login feature in ads.X.comPermission levels: Account administrator, Ad manager, Campaign analyst, Organic analyst, Creative ManagerManual user invitation required

Plan requirement

Not specified

Prerequisites

Not specified

Key limitations

  • No SCIM provisioning support
  • User access managed through multi-user login feature in ads.X.com
  • Permission levels: Account administrator, Ad manager, Campaign analyst, Organic analyst, Creative Manager
  • Manual user invitation required

Documentation not available.

Configuration for Okta

Integration type

Okta Integration Network (OIN) app

Where to enable

Okta Admin Console → Applications → X Ads → Sign On

General X (Twitter) integration for authentication. No SCIM provisioning for ads platform.

Use Stitchflow for automated provisioning.

Unlock SCIM for
X Ads

X Ads has no native SCIM. We still automate end-to-end workflows across every app, including the ones without APIs.

See how it works
Admin Console
Directory
Applications
X Ads logo
X Ads
via Stitchflow

Last updated: 2026-01-20

* Pricing and features sourced from public documentation.

Keep exploring

Related apps

Abnormal Security logo

Abnormal Security

No SCIM

Security / Email Security

ProvisioningNot Supported
Manual Cost$9,490/yr

Abnormal Security, the AI-powered email security platform protecting against BEC and phishing attacks, does not offer SCIM provisioning on any plan. While the platform supports SAML 2.0 SSO integration with identity providers like Okta and Entra ID, this only handles authentication—not automated user lifecycle management. Security teams must manually provision and deprovision analyst access through Abnormal's portal, creating operational overhead and potential security gaps in a platform specifically designed to protect against email-based threats. This manual provisioning model creates significant challenges for security operations. When new SOC analysts join or existing team members change roles, IT admins must coordinate manual account creation and permission updates in Abnormal Security. For a platform that's critical to threat detection and incident response, delays in provisioning can leave security gaps, while delayed deprovisioning creates compliance risks. The irony is stark: a security platform designed to prevent account takeover and credential abuse lacks the automated provisioning controls that prevent exactly these risks.

View full guide
Airwallex logo

Airwallex

No SCIM
ProvisioningNot Supported
Manual Cost$9,490/yr

Airwallex, the global payments and treasury platform, offers no SCIM provisioning support on any plan, including their custom Accelerate enterprise tier. Despite being positioned for enterprise use with features like multi-entity management and advanced treasury controls, Airwallex lacks any official identity provider integrations—no SSO, no provisioning, and no presence in major IdP galleries like Okta's OIN or Microsoft Entra. This creates a significant operational burden for IT teams managing financial access across growing organizations, where manual user provisioning and deprovisioning in a payments platform presents both efficiency and security risks. The absence of identity management capabilities means IT administrators must manually create, update, and remove user accounts in Airwallex—a particularly concerning gap given that this platform handles sensitive financial operations, cross-border payments, and treasury management. Without automated deprovisioning, former employees could retain access to financial systems, creating compliance risks and potential security vulnerabilities that most finance and IT teams cannot afford to overlook.

View full guide
Alkami logo

Alkami

No SCIM
ProvisioningNot Supported
Manual Cost$9,490/yr

Alkami, the digital banking platform used by banks and credit unions, does not offer SCIM provisioning or public SSO integrations. As an enterprise-only platform with custom pricing, Alkami appears to handle user management through direct account administration rather than standardized identity protocols. This creates significant challenges for financial institutions that need to integrate Alkami with their existing identity infrastructure—particularly problematic given the compliance requirements and security standards that banks must maintain. The lack of automated provisioning means IT teams at financial institutions must manually create, update, and deprovision user accounts in Alkami. For a platform handling sensitive financial data and customer information, this manual approach introduces compliance risks and operational overhead. Banks typically require seamless integration between their core identity systems and all applications accessing customer data.

View full guide