All Collections
Embedding the Seats Designer
Manage the chart name from your app
Manage the chart name from your app

Prevent users from editing the chart name in Seats Designer

Ben Verbeken avatar
Written by Ben Verbeken
Updated over a week ago

Note: This article is only relevant if you have embedded the floor plan designer in your back office application, so that your users - event organisers - can create their own floor plans. If you haven't, read more here.

When you embed the Designer, though, you may want to disallow your users from editing the chart name, and manage that from your own application instead.

To do so, you'll need to follow the steps below. You'll notice that the workflow is the same as when you want to manage categories from outside of the Seats Designer, and the two can effectively be combined together. 

Step 1: Chart Name

Have your users specify the chart name in your application.

Step 2: Create an empty chart with the specified name

Call the create chart API and pass in the seating chart name under a "name" key in the body. Check the documentation on how to do this. 

Step 3: embed the Designer with read-only name

Make the chart name input that’s shown in the top left corner read-only by providing the features flag when embedding the designer: 

new seatsio.SeatingChartDesigner({
    features: {
        readOnly: ['chartName']

Step 4: update the chart name when appropriate 

When the user updates the seating chart name in your application, call the update chart API

Important: don't omit this step. It's absolutely necessary to keep both your system and Seats in sync, to avoid any confusion and inconsistencies. 

Did this answer your question?