Hi,

We should be able to hide this even if we want to use organizations.

And we should have the option to set the location if we do want to use this, as it's in a strange place when using forms. The field is always above the form used, this is illogical.

This is silly. Requests should be private  and not shared but I should be able to manage organizations on the back end for workflows, SLAs, reporting, etc.

We need to be able to DISABLE THIS.

Why do you close the other ticket which has much more vote without resolving it? This share with option is annoying and causing lots of issues as customer can accidently share with all the organization, we must have an option to disable it

I do not understand the workflow - you have closed the ticket which was suggesting the actual beneficial change - "Enable default selecting org" or any other change, marked it as relates (with note "We will do this") to this ticket, which talks about moving it to the top of the form. I am confused. 

We would like to hide the field completely and only use automations to add an org.
We are using a workaround right now that when anyone chooses an organization, it automatically gets removed so the entire company doesn't get spammed.  There is often confidential information being submitted in tickets.  

We do not want at the top of a form with potential sensitive information suggesting to a user that they should make available their form submission to everyone in their organization. Make it a field that can be added and linked to request participants (or organizations) if we choose to.

Moving from the bottom to the top just shifts to causing issues for us who have the opposite issue of it being overlooked by users.  Give us the choice.

The best would be to have the field 'Share with' directly in the 'Request form'. This way, the user will be able to create the ticket through the portal filling it all in one step.

Ability to hide the Field would be a must also