The first step is to choose the authentication and consent flow that your users and their parents will follow to access your app and all its great features. Review the flows listed below, and then contact your Implementation Manager for help with setting up your chosen flow.
Immediate access, consent per feature
Feature gate for kids – In this flow, all users get immediate (but limited) access, but kids require parental consent for additional features (progressive permission requests).
Feature gate for all users – This flow treats all users as kids. All users get immediate (but limited) access, but parental consent is required for additional features (progressive permission requests).
Consent for access and per feature
Access gate for kids – This flow treats kids and older users differently. Kids require parental consent before they can access the app. Additional features can then be requested within the app (progressive permission requests).
Access gate for all users – This flow treats all users as kids. It requires all users to get parental consent before they can access the app. Additional features can then be requested within the app (progressive permission requests).
Use KWS for kids only
KWS for kids only – This flow is for apps that use KWS as an account management system for kids only and use a different system to manage older users’ accounts.
Other use cases
Kids Web Services is a very versatile platform that can cater to many user flows. If you don’t see a flow that fits your use case, reach out to your Implementation Manager who will help you to build a custom flow that fits your business needs.