If your organisation runs more than one Access People Planner environment, you can connect all of them to a single Access Care Planning tenant. This means care planning, forms, and branch management can be handled from one place, rather than maintaining separate ACP setups for each People Planner environment.
This article explains what the feature does, what it means for your staff and data, and how to request it.
This feature requires configuration by our engineering team. It's not self-serve.
Why this matters
Some organisations manage most of their branches in one main People Planner environment, but have additional branches sitting in separate, standalone environments. Without this feature, each standalone environment needs its own ACP tenant. That means duplicating forms, managing settings in multiple places, and losing the ability to standardise care planning across your whole organisation.
With multi-environment support, you can:
Manage all branches from one ACP tenant, regardless of which People Planner environment they sit in.
Update a form once and have it apply across all connected branches.
Keep consistent care planning standards across your entire operation.
Maintain role-based access as it works today — branches remain separate in terms of visibility.
How it works
Each People Planner environment is connected to your ACP tenant using a unique prefix. That prefix is applied to all identifiers from that environment — usernames, visit IDs, and branch names — so records from different environments can coexist in one ACP tenant without conflict.
For example, if a branch called "Bristol" sits in a standalone People Planner environment, once connected it would appear in ACP as something like "SouthWest - Bristol". The exact naming convention is agreed with our team during setup.
Role-based access continues to work as normal. Staff in one branch can't see case files from another.
What changes for your staff
⚠️ Important: Usernames will change for staff coming from a People Planner environment being added to an existing ACP tenant. You'll need to communicate new login details to affected staff before they can access the app.
The prefix agreed during setup is added to each username from the new environment. Devices will also need to be re-linked for staff from those environments.
For staff already in your main ACP tenant, nothing changes. Their usernames, devices, and data stay as they are.
What happens to existing data
⚠️ Important: Existing records from standalone People Planner environments can't be migrated into the main ACP tenant. Staff and service users from those environments come through as new records in ACP.
Your old environment remains accessible, so you can refer back to historical data or archive it as needed. Nothing is deleted.
For your main existing ACP tenant — the one you're consolidating into — data and devices remain fully intact.
Adding new environments
Any new People Planner environment set up after your initial configuration can be connected to your existing ACP tenant from the start. This avoids a migration entirely for new branches coming online.
How to request this
Contact your Account Manager or Customer Success Manager and tell them you want to request multi-environment People Planner setup. They'll send you a configuration form to complete.
Once submitted, our team will review your requirements and confirm a timeline. Pricing is based on engineering time and can be covered using flex points if you have a balance available.
Frequently asked questions
Do I need a separate ACP account for each People Planner environment?
No. That's what this feature removes. One ACP tenant connects to all your People Planner environments.
Will my existing ACP data be affected?
No. Data and devices in your main tenant remain unchanged. Only the environments being added start fresh.
Can we move existing care records from a standalone environment into the main ACP tenant?
No. Historical records can't be migrated. Staff and service users from standalone environments come through as new records. You keep read access to the old environment for archiving.
Will usernames change?
Yes, for staff in the environments being added. Each environment gets a prefix, applied to usernames. Communicate new login details to affected staff before they switch over.
Will branch names change?
Yes. Branch names from added environments are prefixed with the People Planner environment name so they're distinguishable within ACP.
Will role-based access still work?
Yes. Branch visibility and access controls remain unchanged. Staff in one branch can't see cases in another.
Can different branches have different forms?
Yes, though it works through services and sections rather than directly at branch level. Forms are defined once at the tenant level, but their visibility is controlled by which service a branch is associated with. If a branch needs its own form set, it can be assigned a dedicated service with the relevant forms attached. Your CSM can advise on the right configuration approach for your setup.
Can we add just some environments and not others?
Yes. You don't have to connect every environment at once. Environments can be added individually, including new ones set up after your initial migration.
How long does setup take?
This depends on the number of environments and complexity. Your CSM will confirm a timeline once the configuration form is reviewed.
Can we use flex points to cover the cost?
Yes, where a flex point balance is available.