Issue Summary

Make it obvious that 'Object Schema Users permissions for JSM customers' need to be enabled for Insight CF on CP create request form to be usable to customers.

This is not really a bug because by enabling the 'Object Schema Users permissions for JSM customers' option, customers will no longer be blocked. However, due to the non-obviousness of this option to project admins/schema admins, they might miss it and leading to the following symptom. And that non-obviousness is a problem that should be addressed.

Steps to Reproduce

1. Create an Insight custom field and add it as a 'required' field to a JSM request type
2. Sign in as a user who is not an 'Object schema user' of the Insight object schema of which the custom field was related to
3. Try to create a request (of that specific request type) using the 'Create request' page on CP

Expected Results

User should not be blocked from creating the request.

Actual Results

User is blocked from creating the request due to them not having access to the object schema, thus unable to add a value to the 'required' custom field.

Workaround

Enabling the 'Object Schema Users permissions for JSM customers' option as a schema admin would unblock the user.

Suggested solution

As JSM project admins, when adding an Insight custom field to a request type form (without having the option already enabled), the system should prompt a warning message, informing them of the potential of a 'mis-configuration'. The project admin can either fix the config if it's a mis-configuration or acknowledge it's intended config by dismissing the warning.