Multi-company HR integrations need more than another company ID field. They need clear company context, isolated rules, controlled write operations, and auditability. PI WP Suite for Paylocity Developer includes everything in Standard and Business, then adds the advanced integration layer for agencies, technical teams, and organizations managing more than one Paylocity company.
Manage multiple Paylocity companies from one WordPress installation
Developer allows administrators to add company configurations one at a time and switch the active administrative context through a persistent company selector. That selected context determines which company’s synchronization, portal rules, LMS assignments, diagnostics, and advanced operations are being viewed or changed.
This is safer and clearer than a comma-separated company field. Each company is a managed configuration with its own settings, while company-scoped handling reduces the risk of viewing or applying one organization’s rules to another.
Build advanced identity and access rules
Standard and Business include base and department-to-role mapping. Developer adds stacked role rules and advanced identity mapping for scenarios where an employee may need multiple WordPress capabilities based on combinations of company, department, title, status, or other governed criteria.
These rules can support complex intranets, shared services, and multi-brand environments while keeping access decisions linked to the HR source of truth.
Enable employee profile write-back carefully
Developer can support governed employee profile updates back to Paylocity. Write operations are disabled by default and should only be enabled after write-readiness diagnostics confirm the required configuration and permissions.
Administrators control which fields are eligible and can route changes through a review workflow. This is intentionally different from allowing arbitrary profile editing: the goal is a limited, auditable write path for approved use cases.
Use the protected Developer REST API
The Developer REST API exposes governed employee list and profile endpoints for external applications. Header API-key authentication protects the interface, allowing technical teams to build approved dashboards, front ends, or operational tools without bypassing the plugin’s company and access controls.
This API is separate from Paylocity OAuth authentication. Paylocity credentials authorize the plugin’s upstream connection; the Developer API key controls approved downstream access to the plugin’s WordPress-facing endpoints.
Import time punches in controlled batches
Developer includes punch import for batches from one to 500 records. This creates a practical bridge for an approved time-tracking workflow that needs to submit data to Paylocity. Because punch import is a write operation, it depends on Paylocity permissions and should be enabled only after diagnostics confirm readiness.
Keep company-specific learning assignments isolated
Business and Developer integrate local LearnDash, Tutor LMS, and LearnPress activity. Developer adds company-specific LMS assignment-rule isolation, so departments with the same name in different Paylocity companies do not automatically inherit the same training rule unless that is intended.
Paylocity LMS content publishing is also represented as a Developer capability, but it requires the relevant Paylocity technology partnership and API access. It should not be confused with the local WordPress LMS integrations, which operate against installed WordPress LMS plugins.
Diagnose and audit advanced operations
Write-readiness checks, advanced audit logs, health reporting, and per-resource caching controls help technical teams understand what is enabled, what ran, and what failed. These controls matter most when an integration can write data, serve external applications, or manage several companies.
Who should choose Developer?
Choose Developer when the project requires multi-company administration, advanced identity rules, controlled write-back, external REST access, punch import, or company-isolated training logic. A single-company employee intranet without those capabilities is usually better served by Business.
Review the complete edition comparison on the PI WP Suite for Paylocity landing page and confirm the Paylocity scopes required for your planned write operations.
PI WP Suite for Paylocity is an independent PI Media product. Write operations and API data availability depend on the organization’s Paylocity contract, scopes, company configuration, and any required partner agreements.
