🏢 Organization
Organizations
The ownership boundary for people, locations, resources, settings, and reporting.
Overview
An organization is the root of the Skedular domain model. It owns the people, locations, resources, bookings, settings, and reporting for one operation. In commercial workflows, products, subscriptions, payments, and analytics also belong to the organization that operates them.
Where This Concept Fits
Why Organizations Exist
Organizations give Skedular a clear ownership and access boundary. They determine which people can manage a setup, which locations and resources appear together, and where booking and operational data is reported.
What Belongs to an Organization
Organization Types
Roles and Permissions
Users belong to an organization and receive access based on their role. Keep product-specific rules in the relevant guide.
| Role | Typical responsibility |
|---|---|
| Owner | Full organization management |
| Administrator | Day-to-day setup and administration |
| Member | Booking and standard access |
Read Organize your people in Skedular Teams, Customers in the Skedular domain model, and Host bookings and renters for product-specific behavior.
Typical Setup Workflow
Begin with the organization that should own the operation. Add only the people and locations you need for the first rollout, then verify resource availability and a test booking before expanding the setup.
Best Practices
- Use one organization for one clear operational boundary.
- Create a separate organization when ownership, billing, or reporting must remain independent.
- Avoid combining unrelated operations in one organization.
- Align permissions with each user’s responsibilities.
- Confirm the organization before changing locations, resources, or booking rules.
- Give users only the access they need for their role.
- Keep commercial configuration in the organization that owns the marketplace operation.
- Use the product-specific documentation when a workflow differs between Teams, Spaces, and Host.
Things to Know
- An organization can own multiple locations.
- Every location belongs to exactly one organization.
- A user can belong to multiple organizations.
- Resources cannot be shared across organizations.
- Billing, payments, analytics, and reporting are isolated per organization.
- Organizations are the primary security boundary within Skedular.
Frequently Asked Questions
Can I belong to multiple organizations?
Yes. A user can participate in multiple organizations, with access determined separately in each one.
Can one organization have multiple locations?
Yes. Each location still belongs to exactly one organization.
Can organizations share resources?
No. A resource belongs to one location, and that location belongs to one organization.