Process Guide | App Checklist
When your app is ready to be published, we will validate your integration with Frog.
These are the key validation points we need to pass before publishing your app tile in the FrogStore and activating the integration for live schools.
Live sites must use https (at least for the AssertionConsumerService / ReplyTo URL)
|Single Sign On||
|Frog Logo||Your app should not use the Frog logo, even when a user is logged in through Frog; it should be clear that the app is provided by your company and not by Frog.
|User Management Functionality||
Where user management functionality is available in your app. Our recommendation is to hide any user management functionality that is redundant - e.g. pages for changing passwords, modifying user or school details, adding accounts.
Please note that if your app includes the facility to add a user who does not single sign on through Frog, we are not able to prevent this user from continuing to sign in if the school cancels their licence for your app.
Displayed with your app in our FrogStore. The description of your app should be clear, accurate and consice.
It should include:
If your app is hosted outside the European Economic Area, please make a clear statement to this effect, and ensure that either this statement or one of the linked documents is clear about the legal implications of this hosting location for customers' data.
If a user attempt to login fails due to incomplete or invalid extended data, the app should route to an information page explaining the issue and provide contact details for obtaining data such establishment keys.
|Help and Support Information||
It should be clear to a user in your app where to find help and support information (including a way to initiate a support request). It can be an email address, a phone number, or a link.
Please also include this info in your App Description.
|Terms & Conditions||
Please also include this link in your App Description.