Multi-tenant Beacons are location Beacons that are shared between one location and one or more other locations.
If you’d like to set up multi-tenant Beacons, please email us at email@example.com.
How Multi-tenant Beacons Work
In some situations, it’s useful to share location Beacons between different locations.
Multi-tenant Beacons only support location Beacons. Proximity Beacons can’t be shared between locations.
For example, if you’re a hospital, you may want to create a Meridian-powered app for your staff and another app for your patients. By using multi-tenant Beacons, you could provide blue dot location-aware routing to your staff and patients using the same location Beacon deployment.
Multi-tenant Beacons uses a parent/child model for deployment. Once a parent location has been enabled by the Meridian team, any number of child locations can share those location Beacons using either the same or a different map image.
Child locations must use either the same map image as a parent location or an image that is the same dimensions as the parent map.
Multi-Tenant Beacons Limitations
There are several limitations to multi-tenant Beacons that are worth mentioning.
- Only one parent location can be created for each Organization. Multi-tenant Beacons only use location Beacons.
- Map images can be shared between parent and child locations, but routing and placemarks aren’t shared.
- Campaigns aren’t shared between parent and child locations.
- In the Meridian Editor, Beacons Management isn’t available for child locations.
- Aruba Tags aren’t currently available for child locations.
When a floor becomes a parent, the map image can no longer be edited. If you need to edit a parent map image, please email us at firstname.lastname@example.org.
Learn More About Multi-tenant Beacons
If you’d like to learn more about deploying Multi-tenant Beacons, see Multi-tenant Beacon Deployment.