# Editing Restrictions

The Scheduler provides multiple approaches to prevent or restrict its editing functionality, including event-based restrictions, conditional editing, and CSS-based visual restrictions.

## Event-Based and CSS-Based Restrictions

You can combine event handling and CSS styling to create comprehensive editing restrictions.

The following example demonstrates how to prevent users from creating, editing, moving, or resizing events in slots that are already occupied using both approaches.

[Demo Source](https://demos.telerik.com/kendo-angular-ui/demos/scheduler/editing/restrictions/source.txt)

### Preventable Events

The Scheduler provides the following events that you can handle to prevent editing operations by setting the [`preventDefault`](https://developer.mozilla.org/en-US/docs/Web/API/Event/preventDefault) property to `true`:

| Event                                                                                                                     | Description                                                 | Use Case                                                            |
| ------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ------------------------------------------------------------------- |
| [`add`](https://www.telerik.com/kendo-angular-ui-develop/components/scheduler/api/reactiveeditingdirective#add)           | Fires before the editing directive renders the Add dialog.  | Prevent creation in specific time slots or based on business rules. |
| [`edit`](https://www.telerik.com/kendo-angular-ui-develop/components/scheduler/api/reactiveeditingdirective#edit)         | Fires before the editing directive renders the Edit dialog. | Restrict editing of certain events or during specific conditions.   |
| [`remove`](https://www.telerik.com/kendo-angular-ui-develop/components/scheduler/api/schedulercomponent#remove)           | Fires when an event is removed.                             | Prevent deletion of important events or based on user permissions.  |
| [`dragStart`](https://www.telerik.com/kendo-angular-ui-develop/components/scheduler/api/schedulercomponent#dragstart)     | Fires when an event drag operation starts.                  | Prevent dragging of certain events or during restricted periods.    |
| [`dragEnd`](https://www.telerik.com/kendo-angular-ui-develop/components/scheduler/api/schedulercomponent#dragend)         | Fires when an event drag operation ends.                    | Prevent moving events to restricted areas or time periods.          |
| [`resizeStart`](https://www.telerik.com/kendo-angular-ui-develop/components/scheduler/api/schedulercomponent#resizestart) | Fires when an event resize operation starts.                | Block resizing in occupied slots or for specific event types.       |
| [`resizeEnd`](https://www.telerik.com/kendo-angular-ui-develop/components/scheduler/api/schedulercomponent#resizeend)     | Fires when an event resize operation ends.                  | Block resizing in occupied slots or for specific event types.       |

The `add` event fires only for the [full edit dialog](https://www.telerik.com/kendo-angular-ui-develop/components/scheduler/editing#built-in-edit-dialog). To restrict the [quick create functionality](https://www.telerik.com/kendo-angular-ui-develop/components/scheduler/editing#quick-create), you can turn it off in the affected views or add `FormGroup` validators. The popover cannot save an invalid form.

### CSS-Based Visual Restrictions

The example also shows how to use CSS styling to provide visual feedback for restricted areas:

* [`slotClass`](https://www.telerik.com/kendo-angular-ui-develop/components/scheduler/api/schedulercomponent#slotclass) property—Apply custom CSS classes to specific time slots to indicate restrictions.
* Custom CSS—Use `pointer-events: none` and visual styling to prevent interactions and show restricted areas.
* Event styling—Apply CSS to make certain events appear read-only or restricted.

## Read-Only Events

When the [`readonly`](https://www.telerik.com/kendo-angular-ui-develop/components/scheduler/api/schedulerevent#readonly) field of an event is `true`, users cannot edit the event in any way, including by dragging. The [event overview](https://www.telerik.com/kendo-angular-ui-develop/components/scheduler/editing#event-overview) popover still shows its details but hides the **Edit** and **Delete** actions.

```ts
public events: SchedulerEvent[] = [{
    id: 1,
    title: 'Board meeting',
    start: new Date(2026, 10, 9, 10),
    end: new Date(2026, 10, 9, 11),
    readonly: true
}];
```

## Conditional Editing

You can render a read-only Scheduler (for example, depending on user permissions) by setting the [`editable`](https://www.telerik.com/kendo-angular-ui-develop/components/scheduler/api/schedulercomponent#editable) attribute to `false`.

```html
<kendo-scheduler [editable]="false">
</kendo-scheduler>
```

## Suggested Links

* [Angular Scheduler Overview](https://www.telerik.com/kendo-angular-ui-develop/components/scheduler)
* [Overview of Editing](https://www.telerik.com/kendo-angular-ui-develop/components/scheduler/editing)
* [API Reference of the SchedulerComponent](https://www.telerik.com/kendo-angular-ui-develop/components/scheduler/api/schedulercomponent)
* [API Index of the Scheduler](https://www.telerik.com/kendo-angular-ui-develop/components/scheduler/api)
