Ofis Square – Panel Overview
Ofis Square provides separate experiences for platform administrators, building teams, members, and reception staff. The options visible to each person depend on their role, assigned buildings, and permissions.
This documentation describes behavior verified in the current Superadmin, Community, and Member web applications. Backend automations, native-app-only behavior, and the standalone Frontdesk experience require verification in their owning repositories.
Admin Panel
Permission-based administration for sales, billing, inventory, access, operations, and exits.
Community Panel
Building operations, visitors, bookings, access cards, inventory, events, and service requests.
Member Panel
Member bookings, day passes, billing, team, guests, support, events, printing, and notifications.
Frontdesk Web
Standalone visitor experience; current behavior is awaiting source verification.
Super Admin Panel
The Super Admin Panel provides cross-location administration. Available modules are permission-gated, so two staff users may see different navigation.
- Name
Sales & clients- Description
Work with leads, onboarding, clients, members, contracts, commercial terms, lead owners, and client migrations.
- Name
Inventory- Description
Manage buildings, cabin categories, cabins, meeting rooms, and common areas, including supported CSV imports.
- Name
Billing- Description
Review estimates, invoices, items, add-ons, credit notes, payments, security deposits, and monthly pro-forma drafts.
- Name
Access- Description
Manage WiFi records, Matrix access, and access policies for eligible users.
- Name
Operations- Description
Work with bookings, events, tickets, users, roles, reports, notification templates, activity logs, and API logs.
- Name
Exit Formalities- Description
Track exit cases, assigned exit tasks, role assignments, SLA policies, and waiver policies when the relevant exit permissions are present.
Open the Admin Panel or read the Admin Panel guide.
Community Panel
The Community Panel supports daily building operations. Its current navigation includes Dashboard, Tickets, Community Desk, Cards, Clients, Extended Hours, OD Leads, Bookings, Events, Printer Requests, Notifications, and Inventory.
Community users retrieve and inspect cabin, meeting-room, and common-area inventory. Inventory creation, editing, bulk import, allocation, and status administration are handled in the Admin Panel.
Open the Community Panel or read the Community Panel guide.
Member Web Panel
The Member Web Panel is the browser-based self-service experience for members, client administrators, and eligible on-demand users.
- Name
Bookings- Description
Reserve meeting rooms, buy or use day passes, review pass details, and manage upcoming activity from the schedule.
- Name
Workspace administration- Description
Eligible client administrators can invite team members, control booking permissions, manage access-card assignments, review billing, and view contracts.
- Name
Community services- Description
Invite guests, approve arriving visitors, RSVP to events, raise support requests, submit print jobs, view notifications, and access WiFi details.
Open the Member Web Panel or read the Member Web Panel guide.
Member App
The Member App is the mobile companion to the member experience. Shared account, booking, day-pass, support, and notification concepts are documented, but native navigation, push-delivery behavior, and store availability must be checked against the native-app source before publication as confirmed behavior.
See the Member App guide.
Frontdesk App
The Frontdesk App is intended for visitor registration and reception workflows. The supplied source set does not contain this standalone application, so its kiosk steps, device requirements, and notification behavior are currently marked as awaiting source verification.
Open the Frontdesk Web experience or see the Frontdesk guide.
Permissions
Ofis Square uses permission-based access control. Routes and navigation items are shown only when the signed-in user has the required read, create, update, access, reporting, or system-administration permission. A role name alone should not be used to assume that a feature is available.
Examples include separate permissions for clients, members, contracts, inventory, bookings, invoices, payments, tickets, events, reports, notification configuration, access management, and exit workflows.