Shared Skedular concept
Understanding Skedular
Understand the shared concepts and domain model behind Skedular Teams, Skedular Spaces, and Skedular Host.
The Skedular domain model
Organization
The ownership boundary for the operation.
Inventory
The places and resources people can use.
Activity
How people use resources and how operators understand usage.
Commerce in Skedular Spaces
The commercial layer for selling access to resources.
This is the practical way to understand Skedular: an organization connects people, places, inventory, and usage. Skedular Spaces adds commerce when that inventory is sold.
Support legend: β Supported β Not available β Automatic π€ Owner or renter access
| Concept | Skedular Teams | Skedular Spaces | Skedular Host |
|---|---|---|---|
| Organization | β Supported | β Supported | β Supported |
| Location | β Supported | β Supported | β Supported |
| Resource | β Supported | β Supported | β Supported |
| Users | β Supported | β Supported | π€ Owner and renters |
| Teams | β Supported | β Not available | β Not available |
| Product | β Not available | β Supported | β Listing configuration |
| Product Tags | β Not available | β Supported | β Not available |
| Subscriptions | β Not available | β Supported | β Not available |
| Floor Plans | β Supported | β Supported | β Supported |
| Availability | β Supported | β Supported | β Supported |
| Analytics | β Supported | β Supported | β Supported |
Organization
An organization is the root of the Skedular domain model. Almost everything belongs to exactly one organization: locations, resources, users, teams, bookings, products, subscriptions, payments, and analytics.
Core rule: An organization is the ownership and access boundary for the operation.
Location
A location is a physical place managed by one organization. Its address, time zone, opening hours, and layout provide the context in which resources can be booked. One organization can operate more than one location, and each location can have its own availability rules.
Floor plan
A floor plan is the visual layout of a location. It places resources in context so people can understand where a desk, room, or other bookable space sits.
Resource
A resource is bookable inventory that belongs to exactly one location. A resource has a type and capacity, may have tags, may belong to zones, and may have Product Tags in Skedular Spaces. It inherits opening hours from its location unless an override applies. Resources are the things users and customers actually book.
Core rule: Every resource belongs to exactly one location.
User
A user is a person who has access to an organization or takes part in a booking workflow. Users may manage settings, configure resources, make bookings, or simply use a resource. Their role determines which actions and information are available to them.
Users in Skedular Teams
Skedular Teams uses users and teams to organize private workplace access. A team groups people who share a workplace context; individual roles determine what each person can manage or book. Read Organize your people for the product workflow.
Users in Skedular Spaces
Skedular Spaces separates the operator managing the Organization from registered Customers making commercial Bookings. Operator access controls workspace setup, while customer information belongs to the Booking or Subscription relationship. Read Customers in the Skedular domain model for the distinction.
Users in Skedular Host
Skedular Host keeps the setup focused on the person managing a place and the renters who book it. The host prepares the listing; renters interact with the published place through its booking flow. Read Host bookings and renters for that workflow.
Booking
A booking belongs to exactly one organization and reserves one or more resources for a defined period. Bookings cannot span multiple calendar days. Visibility, approval, payment, and cancellation behavior depend on the product: Skedular Teams centers private workplace bookings, Skedular Spaces supports marketplace bookings, and Skedular Host presents bookings for a published place. Recurring access is managed separately through subscriptions.
Availability
Availability answers whether a resource can be booked for a selected date. It can be used for historical dates, today, and future dates. It is calculated from opening hours, existing bookings, configured rules, and, where relevant, an offerβs availability. Use it for planning, reviewing historical bookings, and understanding resource utilization.
Tag
A tag is an organization-level label used to classify and find resources. For example, a resource might be tagged by equipment, room type, or accessibility. Tags describe the resource itself and support filtering and discovery.
Zone
A zone is a reusable grouping for an area or purpose within an organizationβs locations. Resources can be associated with more than one zone, allowing the same inventory to be grouped in different useful ways. Zones describe location structure; tags describe resource characteristics.
Analytics
Analytics explains what has happened across bookings and resource activity. It helps an operator understand usage, demand, and operational patterns over time. Analytics is different from availability: analytics reports on history, while availability supports the next booking decision.
Product and offer context
Products are the commercial layer of Skedular Spaces. They define what customers purchase. Product Tags determine which resources fulfil a purchase, and a product may contain multiple offers. Each offer can define pricing, billing rules, payment methods, and cancellation policies. Skedular Host exposes a simpler place-first listing configuration instead.
Spaces only: Products and Product Tags belong to the Skedular Spaces marketplace model.
Product Tags
Product Tags connect a Spaces product or offer to the resources that can fulfil it. They are different from ordinary resource tags: resource tags describe inventory, while Product Tags support commercial allocation.
Subscriptions and commerce
Subscriptions manage recurring customer access separately from one-time bookings. The associated payments, invoices, billing and payouts, Stripe Connect, bank accounts, and Xero integration belong to the Skedular Spaces commerce workflow.
How the concepts work together
The normal flow is: an organization owns a location; the location contains resources; resources have tags, belong to zones, and appear on a floor plan; availability determines when they can be used; a user or customer creates a booking; and analytics records the resulting activity. In Skedular Spaces, a product adds the commercial rules around that booking.
Product boundaries
π₯ Skedular Teams
- Private workplaces
- Employees and teams
- Internal bookings
π Skedular Spaces
- Marketplace operations
- Products and customers
- Payments and commerce
π Skedular Host
- Place-first listings
- Availability and pricing
- Simple rentals
For a guided setup, choose Skedular Teams, Skedular Spaces, or Skedular Host.