Capacity, skills & roles
Describe both how much work a resource can accept and which work it is qualified to perform. Weighted event demand and resource requirements support decisions beyond simple visual overlap.
Loading interactive demo…
What you configure
- capacity / resourceUnits
- Describe resource capacity and the units consumed by assigned events.
- assignmentPolicy
- Declare allowed event types, available skills, and roles.
- resourceRequirements
- Carry an event's type, skill, and role requirements with its assignment.
Essential integration
This assumes the shared Quick start already provides premiumLicense and, for UI views, premiumCalendarOptions. Only the feature-specific setup is shown.
import { WtsCalendar } from '@wts-calendar/core';
import { resourceSchedulingModule } from '@wts-calendar/core/resource-scheduling';
const calendar = new WtsCalendar({
...premiumCalendarOptions,
plugins: [resourceSchedulingModule],
view: 'resource-time-grid-day',
resources: [
{
id: 'design',
title: 'Design studio',
capacity: 2,
assignmentPolicy: { skills: ['research'], roles: ['reviewer'] },
},
],
events: [],
});
calendar.addEvent({
id: 'review',
title: 'Research review',
resourceId: 'design',
resourceUnits: 1,
resourceRequirements: { skills: ['research'], roles: ['reviewer'] },
start: '2026-09-07T09:00:00Z',
end: '2026-09-07T10:00:00Z',
});Behavior and lifecycle
- Requirements are considered across resource-aware mutation and interaction paths.
- Resource summaries expose booked units and capacity conflicts for the visible range.
Limits and responsibilities
- The application defines what a unit, skill, or role means; the package does not certify qualifications.
- Capacity rules require reliable input data and server-side validation for shared scheduling.
Premium
Enable this capability
- Optional module
- @wts-calendar/core/resource-scheduling
- Local capability ID
- resource-scheduling · enabled by package-wide Premium
Use the request form to describe your project and deployment origins. Pricing and terms are confirmed privately. A WTS license is separate from provider credentials; do not send passwords or production access tokens.
The live example uses a browser-visible deployment key restricted to this package and approved origins. It does not collect license keys or visitor credentials.