This message was deleted.

Hi @faint-continent-97669, By setting the field you are using for your Kanban columns to “Read” only, this should prevent users from being able to drag and drop the records. Hope this helps 🙂

@limited-megabyte-13687 fyi

I’ve asked for a better UX with that for a year, but nothing has been done yet. There is definitely something wrong with the current way things work. We need a setting at the view level to disable drag and drop, permissions are NOT enough.

@silly-pharmacist-44942 Will action buttons still be able to progress the records through the statuses? (if the field is set to read only?)

No, permissions would still need to be set to “update”. I created a feature request you can vote for here and add your use case. Thank you 🙂

Ok. If I were to use the read-only workaround, how would you suggest the status update?

That’s the edge case that makes this feature broken, and why Permissions aren’t enough... @faint-continent-97669 The only alternative I’ve found is to apply some custom JS/CSS to break the drag&drop feature... If it’s critical for your app, I could do that custom for you

I was thinking more along the lines of a zapier button instead of an action button that progresses the record through the statuses. Was just curious if someone at Stacker had a better solution.

I’ve found a way to reduce the delay of the data sync, it takes 10-30sec to refresh the value on Stacker UI, much better than 5-15mn

Should I decide to seek professional consultation or purchase a course, I am aware of how to reach out to you. In the meantime, I am looking to explore the collective wisdom of this community for possible solutions, as this is one of the main purposes of this platform.