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
  • Overview
  • Prerequisites
  • Step 1: Create the New Domain
  • Step 2: Add an Application to the Domain
  • Step 3: Add a User to the Domain
Export as PDF
  1. How To
  2. Backoffice

Add a Domain to PlaceOS

Steps required for adding a domain to PlaceOS

PreviousBackofficeNextBackoffice File Upload

Last updated 3 years ago

Overview

This guide will step through the process of creating a domain and the associated application(s) that will exist on it.

You must create a domain before adding authentication sources (such as ) to it.

Prerequisites

  1. PlaceOS has been deployed

  2. You know the domain(s) required for the deployment and the applications on them

Step 1: Create the New Domain

  1. Log in to Backoffice on the domain created during deployment and select the Domains tab

  2. Select the + button to bring up the New Domain form

  3. Add the following fields:

    • Name: Can be anything to identify the domain, like the domain itself i.e. placeos.domain.com

    • Domain: The actual domain, without a protocol i.e. placeos.domain.com

    • Login URL: The URL redirected to when a user logs in

      • You should usually set this to /login?continue={{url}}

    • Logout URL: The URL redirected to when a user logs out

      • You should usually set this to /auth/logout

Step 2: Add an Application to the Domain

  1. Select the Applications tab

  2. Choose New Application

  3. Add the following fields:

    • Name: Can be anything to identify the applications

      • Usually the folder path where the application resides but capitalized i.e. Backoffice

    • Scopes: Leave this blank

    • Skip Authorizaiton: Check the box to set this to true

    • Login URL: The location that users are redirected to after completing authentication

      • This will generally be something like https://<domain>/<application path>/oauth-resp.html

Step 3: Add a User to the Domain

  1. Select the Users tab

  2. Select the New User button

  3. Add or select the following fields:

    • Domain: Select the domain you created in Step 1

    • First Name: Add the first name of the user, this is required

    • Last Name: Add the last name of the user, this is required

    • Email: This will be the username and is required

    • System Admin: Denotes whether the user will be an admin (and thus can access and make changes in Backoffice)

      • This will usually be set to true when creating users in this interface

    • Password and Confirm Password: Enter the password which the user will use to login (when not using SSO)

You can now login with this new user on the domain created.

SAML
Add Domain
Add Application
Add Domain