Desk Manager
Build with AI Agent
Coworking Desk Manager Backend

Coworking Desk Manager Backend Template
Floor Plans, Tier Rules, and Room Logs

A production-ready coworking desk manager backend on Back4app with User, FloorPlan, SubscriptionTier, MeetingRoom, and RoomLog. Includes ER diagram, data dictionary, JSON schema, API sandbox, and an AI Agent prompt for rapid bootstrap.

Key Takeaways

This template gives you a coworking desk manager backend with User, FloorPlan, SubscriptionTier, MeetingRoom, and RoomLog so managers can keep floor plans, room status, and desk limits organized.

  1. Floor-aware desk mappingUse FloorPlan.floorLabel, FloorPlan.zoneName, FloorPlan.deskCapacity, and FloorPlan.mapImageUrl to keep each mapped area tied to the right floor.
  2. Tiered subscriptionsUse SubscriptionTier.tierName, SubscriptionTier.billingCycle, SubscriptionTier.deskLimit, and SubscriptionTier.meetingRoomCredits to control access by plan.
  3. Meeting room logsTrack MeetingRoom.roomName, MeetingRoom.status, and RoomLog.eventType, RoomLog.eventTime, and RoomLog.notes for room activity.

What Is the Coworking Desk Manager Template?

Returns and inspections close the loop in coworking desk manager — the system should capture condition and responsibility before the next rental starts. It is rarely a single bug — it is drift. This template models FloorPlan, SubscriptionTier, MeetingRoom, and RoomLog on Back4app so you can launch a working coworking desk manager platform without rebuilding booking logic from scratch. The schema covers User (username, email, password, role), FloorPlan (floorLabel, zoneName, deskCapacity, mapImageUrl, updatedBy), SubscriptionTier (tierName, billingCycle, deskLimit, meetingRoomCredits, active, createdBy), MeetingRoom (roomName, floorPlan, status, capacity, equipmentNotes, managedBy), and RoomLog (meetingRoom, user, eventType, eventTime, notes) with auth and operational controls built in. Connect your preferred frontend and ship faster.

Best for:

Coworking operations dashboardsFloor plan and desk mappingMembership and tier managementMeeting room logsMVP launchesWorkspace products on BaaS

How this Coworking Desk Manager backend is organized

coworking desk manager quality is a lagging indicator; the leading indicator is whether frontline updates flow into reporting the same day.

This summary orients teams around FloorPlan, SubscriptionTier, and MeetingRoom before anyone dives into ER diagrams or JSON exports.

Coworking Desk Manager Features

Every technology card in this hub uses the same coworking backend schema with User, FloorPlan, SubscriptionTier, MeetingRoom, and RoomLog.

Floor plan management

FloorPlan stores floorLabel, zoneName, deskCapacity, mapImageUrl, and updatedBy.

Desk zone tracking

FloorPlan keeps the mapped desk area count by zone and floor label.

Subscription tier rules

SubscriptionTier captures tierName, billingCycle, deskLimit, meetingRoomCredits, active, and createdBy.

Meeting room logs

MeetingRoom stores roomName, floorPlan, status, capacity, equipmentNotes, and managedBy while RoomLog stores eventType, eventTime, and notes.

Why Build Your Coworking Desk Manager Backend with Back4app?

Back4app gives you FloorPlan, SubscriptionTier, MeetingRoom, and RoomLog primitives so your team can focus on operations instead of server maintenance.

  • Floor and desk mapping: FloorPlan and MeetingRoom classes keep each floor label, zone name, room name, and room status queryable.
  • Subscription tier control: SubscriptionTier fields let you enforce deskLimit, billingCycle, and meetingRoomCredits for each plan.
  • Room log visibility: MeetingRoom and RoomLog records support check-ins, issues, cleanings, and audit-friendly room history.

Build and iterate on coworking operations with one backend contract across all platforms.

Desk Manager Benefits

A coworking backend that keeps floor operations and membership rules easy to inspect.

Faster floor setup

Start with FloorPlan.floorLabel, FloorPlan.zoneName, and FloorPlan.mapImageUrl instead of sketching a desk map table from scratch.

Clear tier enforcement

Use SubscriptionTier.tierName, SubscriptionTier.deskLimit, and SubscriptionTier.meetingRoomCredits to match access with the right desk and room allowances.

Room accountability

Store RoomLog.eventType, RoomLog.eventTime, and RoomLog.notes so room use stays visible.

Scoped workspace access

ACL/CLP rules can limit who edits FloorPlan, changes SubscriptionTier, or closes a RoomLog.

One API for staff tools

Expose FloorPlan, SubscriptionTier, MeetingRoom, and RoomLog through REST and GraphQL for web and mobile admin panels.

AI-assisted bootstrap

Generate backend scaffolding and operations guidance fast with one structured prompt.

Ready to launch your coworking desk manager app?

Let the Back4app AI Agent scaffold your coworking backend and generate FloorPlan, SubscriptionTier, MeetingRoom, and RoomLog flows from one prompt.

Free to start — 50 AI Agent prompts/month, no credit card required

Stack for Workspace Apps

Everything included in this coworking desk manager backend template.

Frontend
13+ technologies
Backend
Back4app
Database
MongoDB
Auth
Built-in auth + sessions
API
REST and GraphQL
Realtime
Live Queries

Entity Map

Entity relationship model for the coworking desk manager backend schema.

View diagram source
Mermaid
erDiagram
    User ||--o{ FloorPlan : "updatedBy"
    User ||--o{ SubscriptionTier : "createdBy"
    User ||--o{ MeetingRoom : "managedBy"
    User ||--o{ RoomLog : "user"
    FloorPlan ||--o{ MeetingRoom : "floorPlan"
    MeetingRoom ||--o{ RoomLog : "meetingRoom"

    User {
        String objectId PK
        String username
        String email
        String password
        String role
        Date createdAt
        Date updatedAt
    }

    FloorPlan {
        String objectId PK
        String floorLabel
        String zoneName
        Number deskCapacity
        String mapImageUrl
        String updatedById FK
        Date createdAt
        Date updatedAt
    }

    SubscriptionTier {
        String objectId PK
        String tierName
        String billingCycle
        Number deskLimit
        Number meetingRoomCredits
        Boolean active
        String createdById FK
        Date createdAt
        Date updatedAt
    }

    MeetingRoom {
        String objectId PK
        String roomName
        String floorPlanId FK
        String status
        Number capacity
        String equipmentNotes
        String managedById FK
        Date createdAt
        Date updatedAt
    }

    RoomLog {
        String objectId PK
        String meetingRoomId FK
        String userId FK
        String eventType
        Date eventTime
        String notes
        Date createdAt
        Date updatedAt
    }

Workspace Flow

Typical runtime flow for login, floor plan sync, room review, tier lookup, and room logging.

View diagram source
Mermaid
sequenceDiagram
  participant User
  participant App as Coworking Desk Manager App
  participant Back4app as Back4app Cloud

  User->>App: Sign in as manager or coordinator
  App->>Back4app: POST /login
  Back4app-->>App: Session token

  User->>App: Open floor plan dashboard
  App->>Back4app: GET /classes/FloorPlan?include=updatedBy
  Back4app-->>App: FloorPlan rows and mapImageUrl values

  User->>App: Review subscription tiers
  App->>Back4app: GET /classes/SubscriptionTier?order=tierName
  Back4app-->>App: Tier limits, billingCycle, and meetingRoomCredits

  User->>App: Check meeting room activity
  App->>Back4app: GET /classes/MeetingRoom?include=floorPlan,managedBy
  Back4app-->>App: Room status and capacity

  User->>App: Add a room log entry
  App->>Back4app: POST /classes/RoomLog
  Back4app-->>App: RoomLog objectId and timestamps

Field Guide

Full field-level reference for every class in the coworking desk manager schema.

FieldTypeDescriptionRequired
objectIdStringAuto-generated unique identifierAuto
usernameStringUser login name
emailStringUser email address
passwordStringHashed password (write-only)
roleStringRole within the coworking operation (e.g., manager, coordinator, member)
createdAtDateAuto-generated creation timestampAuto
updatedAtDateAuto-generated last-update timestampAuto

7 fields in User

Permissions for Workspace Data

How ACL and CLP strategy secures floors, subscription tiers, rooms, and logs.

Manager-only floor edits

Only approved coordinators should create or update FloorPlan and MeetingRoom records.

Tier integrity

SubscriptionTier changes should be validated in Cloud Code so deskLimit and meetingRoomCredits stay consistent.

Room log visibility

RoomLog reads can be scoped to staff and the booking member, while destructive changes stay restricted.

JSON Schema

Raw JSON schema definition ready to copy into Back4app or use as implementation reference.

JSON
{
  "classes": [
    {
      "className": "User",
      "fields": {
        "objectId": {
          "type": "String",
          "required": false
        },
        "username": {
          "type": "String",
          "required": true
        },
        "email": {
          "type": "String",
          "required": true
        },
        "password": {
          "type": "String",
          "required": true
        },
        "role": {
          "type": "String",
          "required": true
        },
        "createdAt": {
          "type": "Date",
          "required": false
        },
        "updatedAt": {
          "type": "Date",
          "required": false
        }
      }
    },
    {
      "className": "FloorPlan",
      "fields": {
        "objectId": {
          "type": "String",
          "required": false
        },
        "floorLabel": {
          "type": "String",
          "required": true
        },
        "zoneName": {
          "type": "String",
          "required": true
        },
        "deskCapacity": {
          "type": "Number",
          "required": true
        },
        "mapImageUrl": {
          "type": "String",
          "required": true
        },
        "updatedBy": {
          "type": "Pointer",
          "required": true,
          "targetClass": "User"
        },
        "createdAt": {
          "type": "Date",
          "required": false
        },
        "updatedAt": {
          "type": "Date",
          "required": false
        }
      }
    },
    {
      "className": "SubscriptionTier",
      "fields": {
        "objectId": {
          "type": "String",
          "required": false
        },
        "tierName": {
          "type": "String",
          "required": true
        },
        "billingCycle": {
          "type": "String",
          "required": true
        },
        "deskLimit": {
          "type": "Number",
          "required": true
        },
        "meetingRoomCredits": {
          "type": "Number",
          "required": true
        },
        "active": {
          "type": "Boolean",
          "required": true
        },
        "createdBy": {
          "type": "Pointer",
          "required": true,
          "targetClass": "User"
        },
        "createdAt": {
          "type": "Date",
          "required": false
        },
        "updatedAt": {
          "type": "Date",
          "required": false
        }
      }
    },
    {
      "className": "MeetingRoom",
      "fields": {
        "objectId": {
          "type": "String",
          "required": false
        },
        "roomName": {
          "type": "String",
          "required": true
        },
        "floorPlan": {
          "type": "Pointer",
          "required": true,
          "targetClass": "FloorPlan"
        },
        "status": {
          "type": "String",
          "required": true
        },
        "capacity": {
          "type": "Number",
          "required": true
        },
        "equipmentNotes": {
          "type": "String",
          "required": true
        },
        "managedBy": {
          "type": "Pointer",
          "required": true,
          "targetClass": "User"
        },
        "createdAt": {
          "type": "Date",
          "required": false
        },
        "updatedAt": {
          "type": "Date",
          "required": false
        }
      }
    },
    {
      "className": "RoomLog",
      "fields": {
        "objectId": {
          "type": "String",
          "required": false
        },
        "meetingRoom": {
          "type": "Pointer",
          "required": true,
          "targetClass": "MeetingRoom"
        },
        "user": {
          "type": "Pointer",
          "required": true,
          "targetClass": "User"
        },
        "eventType": {
          "type": "String",
          "required": true
        },
        "eventTime": {
          "type": "Date",
          "required": true
        },
        "notes": {
          "type": "String",
          "required": true
        },
        "createdAt": {
          "type": "Date",
          "required": false
        },
        "updatedAt": {
          "type": "Date",
          "required": false
        }
      }
    }
  ]
}

Build with AI Agent

Use the Back4app AI Agent to generate a real coworking desk manager app from this template, including frontend, backend, auth, and floor, tier, and room flows.

Back4app AI Agent
Ready to build
Create a secure Coworking Desk Manager backend on Back4app with this exact schema and behavior.

Schema:
1. User (use Back4app built-in): username, email, password, role; objectId, createdAt, updatedAt (system).
2. FloorPlan: floorLabel (String, required), zoneName (String, required), deskCapacity (Number, required), mapImageUrl (String, required), updatedBy (Pointer to User, required); objectId, createdAt, updatedAt (system).
3. SubscriptionTier: tierName (String, required), billingCycle (String, required), deskLimit (Number, required), meetingRoomCredits (Number, required), active (Boolean, required), createdBy (Pointer to User, required); objectId, createdAt, updatedAt (system).
4. MeetingRoom: roomName (String, required), floorPlan (Pointer to FloorPlan, required), status (String, required), capacity (Number, required), equipmentNotes (String, required), managedBy (Pointer to User, required); objectId, createdAt, updatedAt (system).
5. RoomLog: meetingRoom (Pointer to MeetingRoom, required), user (Pointer to User, required), eventType (String, required), eventTime (Date, required), notes (String, required); objectId, createdAt, updatedAt (system).

Security:
- Managers can edit FloorPlan, SubscriptionTier, and MeetingRoom.
- Coordinators can create RoomLog entries and update MeetingRoom status.
- Members can view published FloorPlan rows, active SubscriptionTier rows, and available MeetingRoom rows.

Auth:
- Sign-up, login, logout.

Behavior:
- Map floors, manage subscription tiers, track meeting room logs, and surface room availability by floor and zone.

Deliver:
- Back4app app with schema, CLPs, ACLs; frontend for floor mapping, subscription setup, meeting room operations, and log review.

Press the button below to open the Agent with this template prompt pre-filled.

This is the base prompt without a technology suffix. You can adapt the generated frontend stack afterward.

Deploy in minutes50 free prompts / monthNo credit card required

API Sandbox

Try REST and GraphQL endpoints against the coworking desk manager schema. Responses use mock data and do not require a Back4app account.

Loading playground…

Uses the same schema as this template.

Pick a Stack

Expand each card to see how to integrate FloorPlan, SubscriptionTier, and MeetingRoom with your chosen stack.

Flutter Coworking Desk Manager Backend

React Coworking Desk Manager Backend

React Native Coworking Desk Manager Backend

Next.js Coworking Desk Manager Backend

JavaScript Coworking Desk Manager Backend

Android Coworking Desk Manager Backend

iOS Coworking Desk Manager Backend

Vue Coworking Desk Manager Backend

Angular Coworking Desk Manager Backend

GraphQL Coworking Desk Manager Backend

REST API Coworking Desk Manager Backend

PHP Coworking Desk Manager Backend

.NET Coworking Desk Manager Backend

What You Get with Every Technology

Every stack uses the same coworking desk manager backend schema and API contracts.

Unified coworking data structure

Manage users, floor plans, tiers, rooms, and room logs with one consistent schema.

Floor mapping for operations

Represent workspace levels, zones, desk capacity, and room locations in a form coordinators can query.

Subscription tier control

Match desk access and meeting room credits to the member's current tier.

Meeting room logging

Record room use, timestamps, and staff notes for each RoomLog.

REST/GraphQL APIs for workspace tools

Integrate dashboards, mobile apps, and kiosks with flexible APIs.

Extensible backend for operations

Add visitor passes, cleaning schedules, or desk audits without replacing the core model.

Coworking Stack Comparison

Compare setup speed, SDK style, and AI support across all supported technologies.

FrameworkSetup TimeCoworking BenefitSDK TypeAI Support
About 5 minSingle codebase for desk manager mobile and web.Typed SDKFull
Under 5 minutesFast admin dashboard for floor and room control.Typed SDKFull
~3–7 minCross-platform mobile app for desk coordination.Typed SDKFull
Rapid (5 min) setupServer-rendered web app for workspace operations.Typed SDKFull
~3–5 minLightweight web integration for desk management.Typed SDKFull
About 5 minNative Android app for desk and room staff.Typed SDKFull
Under 5 minutesNative iOS app for floor coordinators.Typed SDKFull
~3–7 minReactive web UI for workspace maps.Typed SDKFull
Rapid (5 min) setupEnterprise web app for desk operations.Typed SDKFull
Under 2 minFlexible GraphQL API for floor and room data.GraphQL APIFull
Quick (2 min) setupREST API integration for operations tools.REST APIFull
~3 minServer-side PHP backend for desk workflows.REST APIFull
~3–7 min.NET backend for workspace coordination.Typed SDKFull

Setup time reflects expected duration from project bootstrap to first FloorPlan, MeetingRoom, or RoomLog query using this template schema.

Coworking Desk Manager Questions

Common questions about building a coworking desk manager backend with this template.

Which coworking desk manager policies are hardest to enforce without structured booking data?
What is the right way to link floor plan management, desk zone tracking, subscription tier rules to fulfillment and return inspections?
Can we support coworking desk manager waitlists, holds, and priority customers in the same schema?
How do I load floor maps in Flutter?
How do I manage desk assignments with Next.js server actions?
Can React Native cache meeting room logs offline?
How do I prevent unauthorized tier changes?
What is the best way to show desk availability on Android?

Trusted by developers worldwide

Join teams shipping coworking operations products faster with Back4app templates

G2 Users Love Us Badge

Ready to Build Your Coworking Desk Manager App?

Start your coworking project in minutes. No credit card required.

Choose Technology