walk through of mockup: https://www.dropbox.com/s/ths7j0wmm85bsh6/Screen%20Recording%202019-02-06%20at%2013.02.41.mov?dl=0

• Policies will be accessible from the account section of the provider admin portal so logically only admins would be able to access.
• Where to link this new page from: page won't exist in master and will be in account > integration in provider admin portal.
• Admin Portal lets an admin user manage custom policy schemas (and custom policies schema's only). Built-in policies will show up in the Policy chain of a 3scale API but as they are not editable they don't figure in account settings > integration > custom policies.
• Custom Policies are not editable or deletable when in use.
• Admin user will receive a heads up when none of API's has APIcast self-managed
• The main use case we see for editing schema's through the ui is thought to be quickly fixing form related stuff, that's why after create/edit you land on preview (show). (the normal route would be to work on your policy in your code base and push the schema to the admin portal through the APIcast cli)
• Schema validation is included. Possibly in real time in the browser but at least after submitting on the server side. How well directed the error messages will be, I don't know at this moment.
• This happens at the tenant level - a tenant admin decides which custom policies will be available for all the API's in their account. We won't implement a master level admin for custom policies (for now).
• Custom policies will be available to all services/API's that have selected the self-managed option. It is the responsibility of the developer to make sure the various APIcasts that might be in use all have those custom policies installed.
• Goal is to makeOOTB policies available by default in each service. They won't show up in custom policies list as they are not custom.