Setup timelines, integrations, and what IT actually needs to do

Standard SaaS deployment goes live in under 24 hours. This is not marketing language; the platform is off-the-shelf with no custom development required. For deployments requiring AD integration, HRMS sync, or private AWS account setup: 3–7 days. For complex configurations with multiple subsidiaries, custom email gateway, and private app store distribution: 2–4 weeks. The 14-day free trial is structured to match the evaluation and basic implementation timeline.

For standard SaaS + AD integration: ~4–8 hours of IT time over 3–5 days. Tasks: provide AD credentials for SSO configuration (30-minute task), configure email gateway for notification emails from your corporate domain (standard SMTP/relay), whitelist the PolicyCentral.ai domain on firewall if required, configure HRMS API integration for employee data sync. No custom development, no server provisioning, no code deployments on your side.

Migration is consistently the most over-estimated aspect. The workflow: upload existing PDFs in bulk (30 minutes for 200 policies), organize into department folders (2–4 hours depending on library size), apply AI enhancements (summaries, audio, translations) (1–2 clicks per policy or batch-processed), configure targeting (1–2 hours). A library of 100 policies is typically fully migrated and live within 2–3 working days without IT involvement.

Full feature access, not a limited sandbox. All 8 AI capabilities, admin dashboard with real compliance reporting, mobile app access for employees, AD integration setup, and the ability to publish real policies to real employees. By the time you make a commercial decision, you have actual data on employee engagement and attestation rates in your own organizational context, not simulated demo data.

HRMS integration works via API. PolicyCentral.ai connects to your HR system to sync employee data (name, department, designation, grade, location, gender, employment status). Enables automatic policy targeting and lifecycle automation (new joiners receive relevant policies automatically; terminated employees are deprovisioned). Supported platforms include: Darwinbox, SAP SuccessFactors, Oracle HCM, Workday, Keka, greytHR, and others.

The AD integration uses SAML 2.0 or LDAP depending on your AD configuration. From the employee's perspective: they open PolicyCentral.ai → redirected to your corporate login page → authenticate with AD credentials → returned to PolicyCentral.ai with a validated session token. Invisible to the employee, PolicyCentral.ai behaves like any other SSO-enabled enterprise application. Session management, password policies, and MFA requirements are governed by your AD configuration.

Yes. The platform can be linked from your existing HRMS or intranet, so employees access PolicyCentral.ai from within tools they already use daily (Darwinbox, SAP, SharePoint intranet) without navigating to a separate URL. This "embedded" access model significantly improves adoption: it removes the friction of remembering another URL. Integration is typically a simple link or iframe embed, requiring minimal IT effort.

The platform integrates with your corporate email gateway (SMTP relay). When a policy is published, employees receive a notification from your corporate domain, not a PolicyCentral.ai domain, maintaining brand consistency and avoiding spam filter issues. Admins configure the notification template, sender name, and email domain. Action buttons (Understood, Accept) require authentication, ensuring compliance records are linked to verified identities.

Yes. The platform can be white-labelled: your logo throughout portal and mobile app, hosted on your domain (e.g., policies.yourcompany.com), color scheme aligned with your brand guidelines. From an employee perspective, they interact with a branded company portal with no visible indication that PolicyCentral.ai is the underlying technology. Employees trust and engage more with a platform that looks like it's part of the company's own digital ecosystem.