Resources

Status: Implemented / controlled release

What it does

Represents operational capacity: desks, rooms, chairs, equipment, service capacity or similar assets.

Benefits

• one authority across verticals
• hierarchy/policy
• booking/QR integration

Typical usage

1. Create resource/category
2. Set capacity/policy
3. Expose public eligibility
4. Book/use/scan
5. Track state

Roles

Staff, Manager, Owner

API families

• /api/v1/public/resources
• /api/v1/public/resource-children/:resourceId
• /api/v1/resources/*

Endpoint presence does not automatically make an endpoint a Partner API. See API → API Overview.

Configuration

• Category/type
• Hierarchy
• Visibility
• Bookable/sellable policy
• Media

Current limitations / release notes

New integrations should use resource contracts rather than legacy table assumptions.

Related modules

Availability, Booking, QR, Inventory