When policies are pushed from APIcast to the admin portal (which seems like the easiest way to get custom policies in the the ui), they never show up in the custom policies section. (They do show up in the policies section of an integration page)

We could 'fix' that by filtering out any policy that has 'built-in' as version number but that seems as a temp fix/hack.

Furthermore it wouldn't solve the problem where somebody editing the schema through the ui would still need to update his apicast. So all we are really giving the customer is a ui to test schema generated forms and I think that is not the purpose of the admin portal.

Also, for any onprem customer using 1 Apicast custom policies will automatically appear. No pushing needed.