--- title: "Namely connector: setup and compatibility | Stacksync" description: "Namely integration guide: plan Groups and Events, record identity, setup, and compatibility." canonical: https://www.stacksync.com/connectors/namely last_modified: 2026-09-15 --- Human resources · Two-way sync platform # Namely integration. > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md Connect your Namely workflow to the systems your business runs on. Work with a Stacksync engineer to confirm the connection and required operations, starting with Groups and Events. Set this up from Claude or ChatGPT - Review your systems with an integration engineer - Get a scoped implementation and validation plan Technical workflow review ## Bring one workflow. Leave with a technical plan. An engineer will assess the required records, access method, and read/write operations before recommending an implementation. - **Profiles** - **Job Titles** - **Job Tiers** **What to bring** Bring a sample record, the other system, and the change your team needs to automate. [Talk through your workflow](https://www.stacksync.com/book-a-demo?connector=namely) ## Adopted by fast-scaling companies moving mission-critical data in real time - Gladia Case study - IDEXX - MedPro Migrated from MuleSoft - Eko Case study - Ubicloud - Vimeo - Codility Migrated from Celigo - ACERTUS Migrated from Heroku Connect - Syringa Migrated from Matillion - Truora - Streaam Case study - SEAL SQ - Rinsed Migrated from Fivetran - IA Capital Group Case study - Meter - Golden Pear Funding Migrated from Celigo Record types ## Namely records to discuss. These Namely record examples help scope a technical review. They are not a list of verified Stacksync operations. Profiles Identify this record type and the operation you need to review with Stacksync. Job Titles Identify this record type and the operation you need to review with Stacksync. Job Tiers Identify this record type and the operation you need to review with Stacksync. ### See 3 more record examples Groups Keep group IDs and membership relationships separately from group names. Teams Identify this record type and the operation you need to review with Stacksync. Reports Identify this record type and the operation you need to review with Stacksync. Connection setup ## Namely connection requirements. Review Namely access and the operations your workflow needs with Stacksync. The vendor API reference below can help your administrator prepare for that discussion. ### Prepare access and scope for the engineering review - Identify the Namely account, edition, environment, and business objects the integration must access. - Confirm a Stacksync connector or implementation path for Namely, including read/write support, authentication, and initial-load limits. Integration design ## Match records and fields for your Namely integration. Separate a person from employment records, assignments, and candidate applications. Decide how future-dated changes, transfers, and rehires reach downstream applications. Use these design questions to prepare a representative record and the business rules your integration must preserve. ### Explore record matching and field-mapping checks Namely **Source record ID** Keep the account and record type Record matching **Source ID ↔ destination ID** Link the same record across systems Selected destination **Destination record ID** Preserve its local key and rules *Conceptual identity model. Keep source and destination IDs linked so an update reaches the right record. Confirm the supported sync direction separately.* Match the same record in both systems Keep group IDs and membership relationships separately from group names. Load related records in the right order Resolve user and tenant identities before membership changes. ### Mapping checks by record type #### Groups Confirm object support with Stacksync Identity Keep group IDs and membership relationships separately from group names. Fields to consider Source group ID · Member references · Tenant reference · Group type Related records to resolve first Resolve user and tenant identities before membership changes. Test before going live Test removed membership, nested groups, and equal group names in different tenants. #### Events Confirm object support with Stacksync Identity Keep the source event ID, source system, occurrence time, and ingestion time. Use an explicit duplicate-detection key. Fields to consider Source event ID · Event type · Occurred-at time · Related record ID · Payload version Related records to resolve first Resolve the related customer, user, or transaction identity without assuming the event ID is the entity ID. Test before going live Deliver the same event twice, then an older event after a newer one; verify duplicate and ordering behavior. [Download the field-mapping workbook (CSV)](https://www.stacksync.com/downloads/sync-planning/field-mapping-workbook.csv) to capture the actual API fields, matching keys, owners, and test results. Use it as you build with your team or a Stacksync engineer. Setup and validation ## Validate the Namely integration in four steps. A future-dated change takes effect at the agreed time; a rehire links to the correct person without duplicating their employment history. ### View the four setup tests and expected results 1. ### Confirm the intended Namely account and grant After confirming an implementation path, validate the selected access method with the intended account and environment. Check that the authorizing user can grant access to the selected objects; test reauthorization without changing the mapped record identity. **Expected result:** The connection reaches the intended account, and the integration owner can renew or revoke the grant through the agreed procedure. 2. ### Test record matching for Groups Using the implementation established in the compatibility review, preserve the selected source ID and resolve the required references. Test removed membership, nested groups, and equal group names in different tenants. **Expected result:** A future-dated change takes effect at the agreed time; a rehire links to the correct person without duplicating their employment history. 3. ### Test the operation your workflow needs Review one Namely record with a Stacksync engineer. Confirm how it should reach the other system, how often it must update, and whether your workflow needs reads, creates, or updates. Test those operations before expanding the integration. **Expected result:** The selected operation is confirmed, addresses the intended record, and exposes rejected values for repair. 4. ### Test recovery and name the support owner For the confirmed implementation, interrupt a non-production transfer and restore access. Establish whether recovery uses the current source state or a stored historical event, and verify that repeated delivery preserves record identity. **Expected result:** The records have the expected current values, repeated delivery creates no duplicate business record, and your team knows who handles unresolved errors. [Use the production-readiness checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) to record test results, assign support owners, and agree on when to go live. Troubleshooting ## Troubleshoot your Namely integration. ### Diagnose record matching, delayed changes, and rejected operations A Namely record appears under the wrong destination record Keep group IDs and membership relationships separately from group names. Resolve user and tenant identities before membership changes. Repair the ID relationship before repeating the operation. The first load looks correct but later results differ Confirm the selected Namely implementation’s change-detection method for Groups and Events. Compare later changes with the original source rather than using a successful initial copy as evidence of ongoing capture. One operation succeeds while another is rejected Check the specific Namely object, field permissions, required references, and allowed operation. A successful read does not establish that a create, update, deletion, or business action is available. [Review retry, replay, and recovery behavior](https://www.stacksync.com/blog/two-way-sync-error-handling-retries-replay) before repeating an operation that may already have succeeded. [Review your Namely workflow with an engineer](https://www.stacksync.com/book-a-demo?connector=namely) ## Namely integration guides - [checklist Two-Way Sync Production-Readiness Checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) - [guide How Digital Innovation Is Reshaping Modern Business Operations](https://www.stacksync.com/blog/how-digital-innovation-is-reshaping-modern-business-operations) FAQ ## Namely connector FAQ ### How should I plan an integration with Namely? Separate a person from employment records, assignments, and candidate applications. Decide how future-dated changes, transfers, and rehires reach downstream applications. Confirm the connection and read/write operations with Stacksync. Start with one workflow, agree on which fields each system owns, then test initial data, later changes, and recovery before expanding. ### Can the Namely connector write changes back? Write-back support is not established for this connection. Review the Namely records and fields you need with a Stacksync engineer, then test the required operation with a representative record. ### Which identifiers should I preserve for Namely data? Keep group IDs and membership relationships separately from group names. ### Which related records should I load first for Namely? Resolve user and tenant identities before membership changes. ### How do I validate Namely changes after the initial load? Test removed membership, nested groups, and equal group names in different tenants. A future-dated change takes effect at the agreed time; a rehire links to the correct person without duplicating their employment history. ### What will we cover in a Namely integration demo? Start with one workflow and a sample record from Groups and Events. We can review how to identify the record, connect related data, set the update direction, and test recovery. Include the person who owns the source system and anyone who will maintain the integration; you do not need a finished requirements document. AI assistant ## Set up Namely from Claude or ChatGPT Connect the Stacksync MCP server to your AI assistant, then ask for the sync in plain language. You only sign in; there is no code to write and no API key to paste. ### 1. Add the Stacksync MCP server Server URL `https://mcp.stacksync.com/mcp` #### In Claude 1. Open Customize → Connectors, select + Add, then Add custom connector. 2. Name it Stacksync and enter https://mcp.stacksync.com/mcp. 3. Select Connect, sign in to Stacksync and choose your workspace. #### In ChatGPT 1. Open Settings → Apps → Advanced settings and turn on Developer mode. 2. Select Create app, name it Stacksync, enter https://mcp.stacksync.com/mcp and choose OAuth. 3. Sign in to Stacksync, then enable Stacksync from the tools menu in a chat. ##### Set up Codex or Claude Code #### Codex ``` codex mcp add stacksync --url https://mcp.stacksync.com/mcp codex mcp login stacksync ``` Complete the browser sign-in with your Stacksync account, then start a new Codex session. #### Claude Code ``` claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp ``` Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. Then ask: “List my Stacksync workspaces.” Sign-in connects your assistant; it does not create a sync yet. Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI and other assistants: [setup steps in the docs](https://docs.stacksync.com/mcp). ### 2. Ask your assistant > Create a sync between my Namely and another app or database. #### Also from the same chat You can also ask for workflows and AI agents (Genies) that use Namely. The assistant checks what each app supports, for example: - “Build a workflow that messages our team in Slack when a Namely record changes.” - “Create a Genie that answers questions about our Namely data in Slack.” #### What happens next - Signs you in with your Stacksync login (OAuth). No API key is pasted into the chat. - Gives you a secure sign-in link for each app it connects; you open it and sign in to that app. - Builds the sync with your permissions in Stacksync, nothing more. Turn on Ask before every change in the MCP settings to approve each change first. New to Stacksync? [Create an account](https://app.stacksync.com/signup) first, then sign in from your assistant. ## Explore Namely connections Choose the other system in your workflow. Each guide explains the connection options, available operations, field mapping, and setup checks for that pair. ### Start with these integration guides - [Namely and Okta](https://www.stacksync.com/integrations/namely-and-okta) - [Namely and Slack](https://www.stacksync.com/integrations/namely-and-slack) - [Namely and SAP Business ByDesign](https://www.stacksync.com/integrations/namely-and-sap-business-bydesign) - [Namely and NetSuite](https://www.stacksync.com/integrations/namely-and-netsuite) - [Namely and Xactly](https://www.stacksync.com/integrations/namely-and-xactly) - [Namely and Pendo](https://www.stacksync.com/integrations/namely-and-pendo) - [Microsoft Power BI and Namely](https://www.stacksync.com/integrations/microsoft-power-bi-and-namely) - [Lever and Namely](https://www.stacksync.com/integrations/lever-and-namely) ### CRM · 31 - [Namely and 6sense](https://www.stacksync.com/integrations/6sense-and-namely) - [Namely and Affinity](https://www.stacksync.com/integrations/affinity-and-namely) - [Namely and Attio](https://www.stacksync.com/integrations/attio-and-namely) - [Namely and Chorusai](https://www.stacksync.com/integrations/chorusai-and-namely) - [Namely and Clearbit](https://www.stacksync.com/integrations/clearbit-and-namely) - [Namely and Close](https://www.stacksync.com/integrations/close-and-namely) - [Namely and Copper CRM](https://www.stacksync.com/integrations/copper-crm-and-namely) - [Namely and Dun & Bradstreet](https://www.stacksync.com/integrations/dun-bradstreet-and-namely) - [Namely and Freshsales](https://www.stacksync.com/integrations/freshsales-and-namely) - [Namely and Freshworks CRM](https://www.stacksync.com/integrations/freshworks-crm-and-namely) - [Namely and Gong](https://www.stacksync.com/integrations/gong-and-namely) - [Namely and Gorgias](https://www.stacksync.com/integrations/gorgias-and-namely) - [Namely and HubSpot](https://www.stacksync.com/integrations/hubspot-and-namely) - [Namely and Infor CRM](https://www.stacksync.com/integrations/infor-crm-and-namely) - [Namely and Insightly](https://www.stacksync.com/integrations/insightly-and-namely) - [Namely and Intercom](https://www.stacksync.com/integrations/intercom-and-namely) - [Namely and Kommo](https://www.stacksync.com/integrations/kommo-and-namely) - [Namely and Outreach](https://www.stacksync.com/integrations/namely-and-outreach) - [Namely and Pipedrive](https://www.stacksync.com/integrations/namely-and-pipedrive) - [Namely and Salesforce](https://www.stacksync.com/integrations/namely-and-salesforce) - [Namely and Salesloft](https://www.stacksync.com/integrations/namely-and-salesloft) - [Namely and SAP Sales Cloud](https://www.stacksync.com/integrations/namely-and-sap-sales-cloud) - [Namely and Seismic](https://www.stacksync.com/integrations/namely-and-seismic) - [Namely and Shopify](https://www.stacksync.com/integrations/namely-and-shopify) - [Namely and SugarCRM](https://www.stacksync.com/integrations/namely-and-sugarcrm) - [Namely and Veeva CRM](https://www.stacksync.com/integrations/namely-and-veeva-crm) - [Namely and Vtiger CRM](https://www.stacksync.com/integrations/namely-and-vtiger-crm) - [Namely and Xactly](https://www.stacksync.com/integrations/namely-and-xactly) - [Namely and Zoho CRM](https://www.stacksync.com/integrations/namely-and-zoho-crm) - [Namely and Zoho SalesIQ](https://www.stacksync.com/integrations/namely-and-zoho-salesiq) - [Namely and ZoomInfo](https://www.stacksync.com/integrations/namely-and-zoominfo) ### ERP · 24 - [Namely and Acumatica](https://www.stacksync.com/integrations/acumatica-and-namely) - [Namely and Brightpearl](https://www.stacksync.com/integrations/brightpearl-and-namely) - [Namely and Cin7](https://www.stacksync.com/integrations/cin7-and-namely) - [Namely and Dynamics 365 Business Central](https://www.stacksync.com/integrations/microsoft-dynamics-365-business-central-and-namely) - [Namely and Epicor ERP](https://www.stacksync.com/integrations/epicor-erp-and-namely) - [Namely and Infor LN](https://www.stacksync.com/integrations/infor-ln-and-namely) - [Namely and Infor M3](https://www.stacksync.com/integrations/infor-m3-and-namely) - [Namely and Linnworks](https://www.stacksync.com/integrations/linnworks-and-namely) - [Namely and Microsoft Dynamics GP](https://www.stacksync.com/integrations/microsoft-dynamics-gp-and-namely) - [Namely and Microsoft Dynamics NAV](https://www.stacksync.com/integrations/microsoft-dynamics-nav-and-namely) - [Namely and NetSuite](https://www.stacksync.com/integrations/namely-and-netsuite) - [Namely and Odoo](https://www.stacksync.com/integrations/namely-and-odoo) - [Namely and Plex ERP](https://www.stacksync.com/integrations/namely-and-plex-erp) - [Namely and QAD ERP](https://www.stacksync.com/integrations/namely-and-qad-erp) - [Namely and Sage 100](https://www.stacksync.com/integrations/namely-and-sage-100) - [Namely and Sage 300](https://www.stacksync.com/integrations/namely-and-sage-300) - [Namely and Sage Intacct](https://www.stacksync.com/integrations/namely-and-sage-intacct) - [Namely and Sage X3](https://www.stacksync.com/integrations/namely-and-sage-x3) - [Namely and SAP](https://www.stacksync.com/integrations/namely-and-sap) - [Namely and SAP Business ByDesign](https://www.stacksync.com/integrations/namely-and-sap-business-bydesign) - [Namely and SAP Business One](https://www.stacksync.com/integrations/namely-and-sap-business-one) - [Namely and SAP S/4HANA](https://www.stacksync.com/integrations/namely-and-sap-s4hana) - [Namely and Syspro](https://www.stacksync.com/integrations/namely-and-syspro) - [Namely and TikTok Shop](https://www.stacksync.com/integrations/namely-and-tiktok) ### Database · 12 - [Namely and Airtable](https://www.stacksync.com/integrations/airtable-and-namely) - [Namely and Amazon DynamoDB](https://www.stacksync.com/integrations/amazon-dynamodb-and-namely) - [Namely and Elasticsearch](https://www.stacksync.com/integrations/elasticsearch-and-namely) - [Namely and Firebase](https://www.stacksync.com/integrations/firebase-and-namely) - [Namely and InfluxDB](https://www.stacksync.com/integrations/influxdb-and-namely) - [Namely and MongoDB](https://www.stacksync.com/integrations/mongodb-and-namely) - [Namely and MySQL](https://www.stacksync.com/integrations/mysql-and-namely) - [Namely and Neo4j](https://www.stacksync.com/integrations/namely-and-neo4j) - [Namely and PostgreSQL](https://www.stacksync.com/integrations/namely-and-postgresql) - [Namely and SAP HANA](https://www.stacksync.com/integrations/namely-and-sap-hana) - [Namely and SQL Server](https://www.stacksync.com/integrations/namely-and-sql-server) - [Namely and Supabase](https://www.stacksync.com/integrations/namely-and-supabase) ### Data warehouse · 8 - [Namely and Amazon Redshift](https://www.stacksync.com/integrations/amazon-redshift-and-namely) - [Namely and Amazon S3](https://www.stacksync.com/integrations/aws-s3-and-namely) - [Namely and Azure Synapse Analytics](https://www.stacksync.com/integrations/azure-synapse-analytics-and-namely) - [Namely and BigQuery](https://www.stacksync.com/integrations/bigquery-and-namely) - [Namely and ClickHouse](https://www.stacksync.com/integrations/clickhouse-and-namely) - [Namely and Databricks](https://www.stacksync.com/integrations/databricks-and-namely) - [Namely and Google Cloud Platform](https://www.stacksync.com/integrations/google-cloud-platform-and-namely) - [Namely and Snowflake](https://www.stacksync.com/integrations/namely-and-snowflake) ### Business productivity · 31 - [Namely and Adobe Sign](https://www.stacksync.com/integrations/adobe-sign-and-namely) - [Namely and Amazon Seller Central](https://www.stacksync.com/integrations/amazon-seller-central-and-namely) - [Namely and Asana](https://www.stacksync.com/integrations/asana-and-namely) - [Namely and Atlassian](https://www.stacksync.com/integrations/atlassian-and-namely) - [Namely and Braze](https://www.stacksync.com/integrations/braze-and-namely) - [Namely and Campfire](https://www.stacksync.com/integrations/campfire-and-namely) - [Namely and ConnectWise](https://www.stacksync.com/integrations/connectwise-and-namely) - [Namely and Docusign](https://www.stacksync.com/integrations/docusign-and-namely) - [Namely and eClinicalWorks](https://www.stacksync.com/integrations/eclinicalworks-and-namely) - [Namely and Front](https://www.stacksync.com/integrations/front-and-namely) - [Namely and Gainsight](https://www.stacksync.com/integrations/gainsight-and-namely) - [Namely and GitHub](https://www.stacksync.com/integrations/github-and-namely) - [Namely and Google Sheets](https://www.stacksync.com/integrations/google-sheets-and-namely) - [Namely and Ironclad](https://www.stacksync.com/integrations/ironclad-and-namely) - [Namely and Klaviyo](https://www.stacksync.com/integrations/klaviyo-and-namely) - [Namely and Lusha](https://www.stacksync.com/integrations/lusha-and-namely) - [Namely and Microsoft 365](https://www.stacksync.com/integrations/microsoft-365-and-namely) - [Namely and Microsoft Dynamics 365](https://www.stacksync.com/integrations/microsoft-dynamics-365-and-namely) - [Namely and Microsoft Teams](https://www.stacksync.com/integrations/microsoft-teams-and-namely) - [Namely and Monday](https://www.stacksync.com/integrations/monday-and-namely) - [Namely and Notion](https://www.stacksync.com/integrations/namely-and-notion) - [Namely and Quip](https://www.stacksync.com/integrations/namely-and-quip) - [Namely and SendGrid](https://www.stacksync.com/integrations/namely-and-sendgrid) - [Namely and ServiceMax](https://www.stacksync.com/integrations/namely-and-servicemax) - [Namely and ServiceNow](https://www.stacksync.com/integrations/namely-and-servicenow) - [Namely and Slack](https://www.stacksync.com/integrations/namely-and-slack) - [Namely and Smartsheet](https://www.stacksync.com/integrations/namely-and-smartsheet) - [Namely and SysAid](https://www.stacksync.com/integrations/namely-and-sysaid) - [Namely and Twilio](https://www.stacksync.com/integrations/namely-and-twilio) - [Namely and Wrike](https://www.stacksync.com/integrations/namely-and-wrike) - [Namely and Zendesk](https://www.stacksync.com/integrations/namely-and-zendesk) ### Accounting and finance · 13 - [Namely and Adyen](https://www.stacksync.com/integrations/adyen-and-namely) - [Namely and Anaplan](https://www.stacksync.com/integrations/anaplan-and-namely) - [Namely and BILL](https://www.stacksync.com/integrations/bill-and-namely) - [Namely and Braintree](https://www.stacksync.com/integrations/braintree-and-namely) - [Namely and Chargebee](https://www.stacksync.com/integrations/chargebee-and-namely) - [Namely and Coupa](https://www.stacksync.com/integrations/coupa-and-namely) - [Namely and Navan](https://www.stacksync.com/integrations/namely-and-navan) - [Namely and QuickBooks](https://www.stacksync.com/integrations/namely-and-quickbooks) - [Namely and Ramp](https://www.stacksync.com/integrations/namely-and-ramp) - [Namely and Recurly](https://www.stacksync.com/integrations/namely-and-recurly) - [Namely and Stripe](https://www.stacksync.com/integrations/namely-and-stripe) - [Namely and Workday](https://www.stacksync.com/integrations/namely-and-workday) - [Namely and Zuora](https://www.stacksync.com/integrations/namely-and-zuora) ### AI · 4 - [Namely and Autopilot](https://www.stacksync.com/integrations/autopilot-and-namely) - [Namely and Azure OpenAI](https://www.stacksync.com/integrations/azure-openai-and-namely) - [Namely and OpenAI](https://www.stacksync.com/integrations/namely-and-openai) - [Namely and Pinecone](https://www.stacksync.com/integrations/namely-and-pinecone) ### Analytics · 6 - [Namely and Adobe Analytics](https://www.stacksync.com/integrations/adobeanalytics-and-namely) - [Namely and Microsoft Power BI](https://www.stacksync.com/integrations/microsoft-power-bi-and-namely) - [Namely and Mixpanel](https://www.stacksync.com/integrations/mixpanel-and-namely) - [Namely and Pendo](https://www.stacksync.com/integrations/namely-and-pendo) - [Namely and Splunk](https://www.stacksync.com/integrations/namely-and-splunk) - [Namely and Tableau](https://www.stacksync.com/integrations/namely-and-tableau) ### Human resources · 12 - [Namely and BambooHR](https://www.stacksync.com/integrations/bamboohr-and-namely) - [Namely and Ceridian Dayforce](https://www.stacksync.com/integrations/ceridian-dayforce-and-namely) - [Namely and Greenhouse](https://www.stacksync.com/integrations/greenhouse-and-namely) - [Namely and Hibob](https://www.stacksync.com/integrations/hibob-and-namely) - [Namely and Jobvite](https://www.stacksync.com/integrations/jobvite-and-namely) - [Namely and Lever](https://www.stacksync.com/integrations/lever-and-namely) - [Namely and Oracle Fusion Cloud HCM](https://www.stacksync.com/integrations/namely-and-oracle-fusion-cloud-hcm) - [Namely and Paylocity](https://www.stacksync.com/integrations/namely-and-paylocity) - [Namely and SmartRecruiters](https://www.stacksync.com/integrations/namely-and-smartrecruiters) - [Namely and Success Factors](https://www.stacksync.com/integrations/namely-and-success-factors) - [Namely and UKG Pro](https://www.stacksync.com/integrations/namely-and-ukg-pro) - [Namely and UKG Ready](https://www.stacksync.com/integrations/namely-and-ukg-ready) ### Security and identity · 6 - [Namely and Active Directory](https://www.stacksync.com/integrations/active-directory-and-namely) - [Namely and Auth0](https://www.stacksync.com/integrations/auth0-and-namely) - [Namely and Azure Active Directory](https://www.stacksync.com/integrations/azure-active-directory-and-namely) - [Namely and JumpCloud](https://www.stacksync.com/integrations/jumpcloud-and-namely) - [Namely and Okta](https://www.stacksync.com/integrations/namely-and-okta) - [Namely and OneLogin](https://www.stacksync.com/integrations/namely-and-onelogin) ### Storage · 4 - [Namely and Amazon S3](https://www.stacksync.com/integrations/amazon-s3-and-namely) - [Namely and Box](https://www.stacksync.com/integrations/box-and-namely) - [Namely and Egnyte](https://www.stacksync.com/integrations/egnyte-and-namely) - [Namely and SharePoint](https://www.stacksync.com/integrations/namely-and-sharepoint) 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](https://www.stacksync.com/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](https://www.stacksync.com/security) [SSH Tunnelling](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ssh-tunneling) [SSL certificates](https://docs.stacksync.com/two-way-sync/connectors/postgres/authorize-postgres/amazon-rds/ensuring-secure-rds-connections-with-ssl-certificate) [IP Whitelisting](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ip-whitelisting) [VPN gateway](https://docs.stacksync.com/two-way-sync/legal/service-consumption-tables#:~:text=%E2%9C%93-,VPN%20gateway,-%2D) [VPC peering](https://www.stacksync.com/security) and more ## Connect the systems your business runs on. Build your next workflow with Stacksync. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)