LogoLogo
  • PlaceOS Documentation
  • Overview
    • Key Concepts
      • Drivers
      • Interfaces
      • Modules
      • Settings
      • Systems
      • Triggers
      • Zones
    • Languages
      • Crystal
      • TypeScript
    • Protocols
      • MQTT
      • SAML
      • OAuth2
  • How To
    • Configure PlaceOS for Microsoft 365
      • Step 1: Room Calendar Access
        • Create Azure App Registration (Application Permissions)
        • Exchange Calendar Group
        • Limit Application Permissions
        • Configure PlaceOS Calendar Driver
      • Step 2: User Authentication & Calendar Access
        • Create a PlaceOS Authentication Source
        • Create Azure App Registration (Delegated Permissions)
        • Configure PlaceOS Authentication Source
        • Add User Login Redirects
      • Concierge Access
      • Troubleshooting
        • Blocked or Blacklisted IP Error
    • Configure PlaceOS for Google Workspace
      • Google Configuration
        • Create Google Cloud Project & Enable API
        • Configure Google Cloud Service Account
        • Add Google Workplace Permissions
        • Create Google Marketplace App (optional)
        • Google Workspace Service User (RBAC)
        • Configure Access to Google Resource Calendars
      • User Authentication
        • Create a PlaceOS Authentication Source for Google
        • Create Google Cloud OAuth2 Client App
        • Configure PlaceOS Auth Source for Google
        • Add User Login Redirects
    • Deployment
      • Deploy AWS Fargate on Modular CloudFormation Stacks
      • Deploy AWS Fargate on Nested CloudFormation Stacks
      • Writing Import Scripts
    • Analytics
      • MQTT Integration
    • Backoffice
      • Add a Domain to PlaceOS
      • Backoffice File Upload
      • Configure Staff API
      • Calendar Driver
      • Enable Sensor UI
      • Bookings Driver
      • Configure a webhook
    • Authentication
      • Azure B2C
        • Azure B2C Custom Policy Framework
        • Configure PlaceOS for Azure B2C
        • 365 Room Resources on Azure B2C
      • Configure SAML SSO
        • Configure SAML2 with AD FS
        • Configure SAML2 with Auth0
        • Configure SAML2 with Azure AD
        • Configure SAML2 with Google Workspace
      • Configure OAuth2 SSO
      • X-API Keys
      • Bearer tokens
    • Location Services
      • Location Services
      • Area Management
      • Discovering User Devices
      • Locating Users on a Network
      • People Finding with Cisco Meraki on PlaceOS
      • People Finding with Juniper Mist on PlaceOS
    • Notifications
      • Catering Orders
    • User Interfaces
      • Booking Panel App
      • Workplace App
      • Native Booking Panel App
      • Deploy a Frontend Interface
      • Microsoft Outlook Plugin
      • Configure Endpoint Auto Login
      • SVG Map Creation
      • Configuring a default UI
  • Tutorials
    • Setup a dev environment
    • Backend
      • Troubleshooting Backend Failures
      • Import Bookable Rooms
      • Writing A Driver
        • Testing drivers
        • ChatGPT / LLM Capabilities
          • Native GPT Plugins
      • Testing Internal Builds
    • Backoffice
      • Adding Drivers & Modules
      • Add Zone Structure
    • Common Configurations
      • Asset Manager
      • Catering
      • Locker Booking
      • Webex Instant Connect
      • Desk booking
      • Sensor Data Collection
        • Configure Kontakt IO
        • Configuring Meraki
        • Configuring DNA Spaces
      • Elevated Privileges
  • Reference
    • API
      • Real-time Websocket
      • Rest API
      • Staff API
    • Drivers
      • PlaceOS
        • Bookings
        • Staff API
        • Visitor Mailer
        • Lockers
      • Microsoft
        • Graph API
    • PlaceOS Skills
    • Privacy Policy
    • Recommended Products
    • Supported Integrations
    • System Architecture
    • System Functionality & Requirements
    • Infrastructure Requirements
    • Security Compliance
      • FAQ
      • GDPR
      • Security
    • Microsoft Azure Permissions
  • Glossary
  • 🎯PlaceOS Roadmap
  • 🆘PlaceOS Support
  • 👩‍💻PlaceOS Github
  • 📝PlaceOS Changelog
Powered by GitBook
On this page
  • Prerequisites
  • Org Zone
  • Building Zones
  • Level Zones
  • System Zones
Export as PDF
  1. Tutorials
  2. Backoffice

Add Zone Structure

This document outlines creating zone structure in Backoffice

PreviousAdding Drivers & ModulesNextCommon Configurations

Last updated 2 years ago

An important step in setting up PlaceOS is to create your organizations physical structure as .

You can think of Zones as creating your digital twin of your physical organization structure.

The three required zones required are:

  • org zone: your parent zone, named after your organization

  • building zone: your buildings within your organization

  • level zone: the levels (floors) within your buildings

A region zone is optional, and may be used to:

  • Group buildings in a country

  • Group buildings in a geographic region i.e. Europe

  • Group buildings in a country i.e. NSW

A region zone sits between the org zone and building zone. In this configuration, the building zones belong to a region zone and not the org zone.

If you are using a region zone, it is important to set a timezone or GPS Coordinates on your building zones to allow the app to correctly locate users.

In the following steps, we will walkthrough configuring your Zone structure including Organization, Building and Levels.

Prerequisites

  • PlaceOS Backoffice Administrator Access

  • (optional)

Org Zone

An Org Zone is the parent zone for all other zones.

The Org Zone is typically named after the organization.

Steps to create the org zone

  1. Login to PlaceOS Backoffice

  2. Navigate to Zones

  3. In the New Zone Modal, you will need to enter the following information:

  • Parent Zone: Your new org zone will be the parent, leave this blank

  • Name: The name of your org zone (typically your organization name)

  • Display Name: How you want the zone to appear to end users (optional)

  • Tags: Enter a single tag of org

The remaining fields are not required for org zones:

  • Description: Optional zone description

  • Location: GPS Coordinates for the building

  • Code: Cost Center or Building Code

  • Type: Code category

  • Capacity: Total building capacity

  • Map: A relevant map file

  1. Click Save

You have now created your org zone, this will be the parent for your building zones.

Building Zones

Building Zones represent your physical buildings.

The frontend will use Building Zones to allow end users to select buildings in your organization.

Create Building Zones

  1. Login to PlaceOS Backoffice

  2. Navigate to Zones

  3. In the New Zone Modal, you will need to enter the following information:

  • Parent Zone: Select your Org Zone we created in the previous step as the parent

  • Name: The name of your building zone (you could put an address or physical location)

  • Display Name: How you want the zone to appear to end users (optional)

  • Tags: Enter a single tag of building

The remaining fields are optional:

  • Description: Optional zone description

  • Location: GPS Coordinates for the building

  • Timezone: The timezone may be set on a building zone to allow users to be automatically located to the correct building.

  • Image: An image can be uploaded to display in various apps, or be used as the background on room booking panels.

  • Code: Cost Center or Building Code

  • Type: Code category

  • Capacity: Primarily for defining floor/level capacity

  1. Click Save

You have now created your building zone, this will be the parent for your level zones.

You will need to repeat this step to create all your buildings.

Level Zones

Level Zones represent your buildings levels (floors).

The frontend will use Level Zones (nested in building zones) to allow end users to select levels in your buildings.

Create Level Zones

  1. Login to PlaceOS Backoffice

  2. Navigate to Zones

  3. In the New Zone Modal, you will need to enter the following information:

  • Parent Zone: Select your Building Zone we created in the previous step as the parent

  • Name: The name of your Level zone (Typically this will be Level 1, Level 2 etc.)

  • Display Name: How you want the zone to appear to end users (optional)

  • Tags: Enter a single tag of level

The remaining fields are optional:

  • Description: Optional zone description

  • Location: GPS Coordinates for the building

  • Code: Cost Center or Building Code

  • Type: Code category

  • Image: An image can be uploaded to display in various apps, or be used as the background on room booking panels.

  • Capacity: Total level capacity

  1. Click Save

You have now created your first level zone, this will be the parent for your system zones.

You will need to repeat this step to create all your levels.

System Zones

System Zones group similar system types e.g. meeting rooms, video conference rooms etc.

These systems are optional.

System Zones will allow specific configuration for a group of similar systems.

Create a System Zone

  1. Login to PlaceOS Backoffice

  2. Navigate to Zones

  3. In the New Zone Modal, you will need to enter the following information:

  • Parent Zone: Select your Building or Org Zone we created in the previous step as the parent

  • Name: The name of your System zone (Typically this will be 4 Person Meeting Room, MS Teams Rooms etc.)

The remaining fields are optional:

  • Display Name: How you want the zone to appear to end users

  • Description: Optional zone description

  • Tags: Add tags e.g. 4-pax or videoconference etc.

  1. Click Save

You will now need to add systems to the zone.

Click the + button to create a new zone

Click the + button to create a new zone

Map: A relevant map file (see )

Click the + button to create a new zone

Map: A relevant map file for the level (see )

Click the + button to create a new zone

How to Upload Files to Backoffice
How to Upload Files to Backoffice
Zones
SVG Floor Plans
Add new org zone
Building Selector
Add new building zone
Level Selector
Add new level zone
Add new system zone
Add new org zone
Add new org zone
Add new org zone
Add new org zone