Skip to content
Security and identity ⇄ Accounting and finance

Active Directory to Pigment integration — real-time, two-way sync

Keep Active Directory and Pigment in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Active Directory and Pigment

Keep the people who can act on financial records in Pigment matched to their identities in Active Directory, so access is provisioned, updated, and revoked in real time.

Pigment runs the money — the ledgers, invoices, budgets, and payments — and every one of those actions is taken by a person with a login. Active Directory is where those people and their access actually live: who is employed, what team they belong to, and what they are allowed to do. The two systems rarely share customers or transactions, but they share the one thing that governs both — the user. When that overlap is maintained by hand, a departed employee keeps finance access for weeks and a new hire waits on a ticket to get any.

Stacksync keeps Scenarios, Data imports, Users and permissions, Applications in Pigment aligned with Users, Groups, Group memberships, Devices in Active Directory, field by field and in real time. A person added, moved, or deactivated on the identity side updates their matching user in the finance system within seconds, with the role or permission set mapped from the group they belong to. Direction is yours to set: lead provisioning from the directory, or let an HR-owned finance record drive the downstream accounts.

For a finance team, that alignment is an audit control rather than a convenience. When the user list in the books matches the identity source of truth, segregation-of-duties and access reviews start from data that is already correct instead of an export that was current last quarter.

Common use cases

  • 01 Export approved budgets and forecasts back to a warehouse or Postgres for downstream reporting.
  • 02 Keep dimension lists such as departments and cost centers consistent with master data in the ERP.
  • 03 Read Users, Groups, and directoryRole assignments into a warehouse for periodic access reviews and SOC 2 audit evidence.
  • 04 Keep security-group memberships aligned with application entitlement tables so access reflects the right teams as they change.

Common sync patterns

Where Active Directory is the identity source: offboarding reaches the books

When a person is deactivated in Active Directory, their matching user in Pigment is disabled in the same motion, so departed employees keep no standing access to financial records.

One user roster across both systems

People, their status, and their contact details stay matched between Pigment and Active Directory, so the finance system's login list reflects who actually works here instead of drifting out of date.

Group and role membership drives finance permissions

A person's group or role in Active Directory maps to their permission set in Pigment, so who can approve, post, or view is governed from one place instead of maintained twice.

What you can sync between Active Directory and Pigment

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Active Directory objects Pigment objects How this pairing syncs
Directory roles Admin role assignments (directoryRole); read for access reviews and least-privilege governance. Applications Planning models organized by domain such as finance, sales, or workforce Directory roles is specific to Active Directory and Applications to Pigment — each maps to any object or custom field on the other side.
Service principals & applications App registrations and enterprise apps; read-mostly for entitlement and license inventory. Metrics Multidimensional values holding plans and actuals; the main target for inbound data Service principals & applications is specific to Active Directory and Metrics to Pigment — each maps to any object or custom field on the other side.
Organizational units On-prem AD DS containers (LDAP organizationalUnit) used to scope which users and groups a sync includes. Dimension lists Master data like accounts, products, or employees that metrics are sliced by Organizational units is specific to Active Directory and Dimension lists to Pigment — each maps to any object or custom field on the other side.
Organizational contacts Directory contact objects (orgContact); synced for shared address-book and CRM person records. Tables Row-based transactional data loaded into models from source systems Organizational contacts is specific to Active Directory and Tables to Pigment — each maps to any object or custom field on the other side.
Users User accounts in Entra ID and on-prem AD DS; synced two-way to create, update attributes, and enable or disable accounts. Scenarios Versions such as budget, forecast, and actuals that give exported figures their context Users is specific to Active Directory and Scenarios to Pigment — each maps to any object or custom field on the other side.
Groups Security and Microsoft 365 groups; synced two-way including name, type, and owner, with membership tracked separately. Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model Groups is specific to Active Directory and Data imports to Pigment — each maps to any object or custom field on the other side.

How changes propagate between Active Directory and Pigment

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Active Directory Pigment Sub-second propagation

DetectionActive Directory notifies Stacksync of record changes through webhook events. Microsoft Graph delta query (change tracking) for Users and Groups, plus change-notification subscriptions (webhooks) for near-real-time triggers.

DeliveryEach detected change is written to Pigment through its API, with automatic retries and rate-limit backoff.

Pigment Active Directory Interval-based propagation

DetectionStacksync polls Pigment for changes on an incremental schedule, reading only records changed since the previous pass. No change feed.

DeliveryEach detected change is written to Active Directory through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Active Directory: Graph throttles by resource-unit cost per app per tenant in 10-second windows (about 3,500–8,000 units by tenant size); directory delta tokens expire after ~7 days.
  • Pigment: Subject to the platform's API rate limits.
What ships with Active Directory ⇄ Pigment

Connect Active Directory and Pigment for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Active Directory–Pigment connection.

Real-time

Two-way sync

Changes in Active Directory or Pigment instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Active Directory or Pigment data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Active Directory or Pigment record.

Observability

Monitoring

Track your Active Directory ⇄ Pigment sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Active Directory and Pigment.

How the Active Directory and Pigment connectors work

Active Directory

Integration surface
Microsoft Graph REST API (Entra ID / cloud) and LDAP/LDAPS (on-premises AD DS)
Authentication
OAuth 2.0 via the Microsoft identity platform — an app registration with application or delegated permissions (e.g. User.ReadWrite.All, Group.ReadWrite.All) and admin consent; on-prem AD DS uses a bound service account over LDAPS.
Change detection
Microsoft Graph delta query (change tracking) for Users and Groups, plus change-notification subscriptions (webhooks) for near-real-time triggers; on-prem AD DS uses the DirSync control and uSNChanged polling.
Capabilities
read · write · webhooks
Rate limits
Graph throttles by resource-unit cost per app per tenant in 10-second windows (about 3,500–8,000 units by tenant size); directory delta tokens expire after ~7 days.

Pigment

Integration surface
REST-based import and export API
Authentication
API keys, issued separately for import and export
Change detection
no change feed; syncs run scheduled imports and exports
Capabilities
read · write
Rate limits
subject to the platform's API rate limits
How it works

How to connect Active Directory to Pigment — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Active Directory and Pigment with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Active Directory connected
    Pigment connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Active Directory and Pigment objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Active Directory ⇄ Pigment
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Active Directory Pigment
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Active Directory and Pigment integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 409 integrations available for Active Directory and Pigment.

Popular · 8 of 409
All Active Directory integrations All Pigment integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own