Skip to main content
Best answer by Celine_

Hey ​@Damian_Summersall , thanks for follow up here! I can see that our support team has replied to you.
Sharing here for others in the community who encounter similar issue.

Our support team has checked internally, and unfortunately, there is currently no functionality that prevents users from inserting non-preferred instances.
We’ve gone ahead and submit a feature request on your behalf and send it over to our product and engineering teams for review and consideration.


Thanks for your understanding, I am marking as ‘Best Answer’ so others in the community can see the latest update about this request.

12 replies

Show previous replies
Jaycee Lewis
Figmate
Jaycee Lewis
Figmate
August 19, 2026

Thanks for the feedback ​@jbrycedavis I’ll take this to the team and get it shared. I don’t have insight into changes to this behaviour or help text at this time. And I will add it here if I do. We appreciate you! — Jaycee

jbrycedavis
jbrycedavis
New Participant
August 19, 2026

Thanks, Jaycee. Appreciate it. 

My final thought is this - and a co-worker pointed it out to me. If that checkbox is not intended to be restrictive - why does it even exist? If anything can always go in there even if I say not to - why would this even be necessary as a check box? I am by no way advocating for it’s removal - but the mental model of the labeling versus the actual functionality (not restricting the user) seems flawed.

    Terms & ConditionsAccessibility statement