integrations Shipped
Multi-State Deployment — Tenant Config Import/Export
Bootstrap a new state program from a JSON bundle — workflow rules, templates, permissions, dashboards, localization, feature flags, routing rules, all in one export.
Key benefits
- · Complete tenant configuration exportable as a JSON bundle
- · Bundle covers workflow rules, document templates, permissions, dashboards, localization, benefit configs, feature flags, user groups, roles, routing rules, AI knowledge articles
- · Bootstrap a new state instance without custom development
- · Diff two tenants to understand their operational differences
- · Version configuration changes in git
Why this is rare
Onboarding a new state program is typically a months-long custom-implementation engagement. Each state has its own forms, its own review cadences, its own approval authorities. If those choices live in code, adding a state means a dev project. VCPMS lives those choices in configuration — so adding a state means importing a config bundle.
What’s in a tenant bundle
Every tenant-scoped decision:
- Workflow rules (
WorkItemManagerConfigfor every WorkItem type) - Document templates (letters, notices, agendas)
- Permission sets
- Dashboard layouts (default + per-role)
- Localization overrides (tenant-specific field labels and help text)
- Benefit category configurations (max amounts, coverage %, fee schedules)
- Feature flags (which optional modules are turned on)
- User groups and roles
- Incoming-document routing rules
- AI assistant knowledge articles
All as JSON, all diff-able, all version-control-friendly.
Operational wins
- Onboarding speed. New state → import a reference bundle → tweak.
- Environment parity. Staging and production use the same config format, enforcing “deploy config, not code.”
- Audit trail. Config changes land in git, reviewable per PR.