We’re excited to announce a new capability in our Developer Portal: you can now include an Account System as an Essential Product, enabling deeper integrations with first-party account systems.

This unlocks a critical use case for developers who want parental consent flows to cover both their games and the account system powering them — a common requirement for developers with their own login ecosystems.

Why we built this

Many of our customers have account systems that are tightly integrated into the player experience. For younger players, this often means that before a game can be played, an account must be created and consented to by a trusted adult.

Previously, this relationship between a game and its account system wasn’t easy to represent in k-ID. But with this new release, you can ensure that when a game or app requires its own account system, the parent approves both together as part of a unified, compliant flow. 👨‍👩‍👧‍👦🔗

How it works in the Developer Portal

You can create a product in the Developer Portal that represents your account system. This account system product can be configured with its own permissions, data notices, age requirements and other compliance information — just like any other product.

But what’s magic is how we make it interact with your other products. Once your account system is marked as an Essential Product, this creates a required link between the account system product and any game or app that relies on that account system — this relationship is enforced and reflected across the Developer Portal, API responses and the parental consent flow.

Designating an account system product as an Essential Product means that:

• It cannot be removed from the bundle.

• It must be approved before or alongside any product that depends on it.

• If a parent tries to revoke access to the account system, they must first revoke access to any products that require it.

👉 Explore how it works in the Developer Portal using the interactive demo below.

What parents will see

From the parent’s perspective, this ensures a transparent and intuitive experience: when a parent is asked to approve a game, and that game relies on an account system, Family Connect will present a clear, unified view of what is being approved. The experience includes:

• An explanation that the approval includes both the game and the account system.

• An aggregated view of the permissions across both products.

• A clear display of the essential nature of the account system — it cannot be removed from the bundle.

• Enforcement of appropriate minimum age based on both the game and the account system.

• If the account system has already been approved, it’s not shown again. If it’s not, it’s clearly included and explained in the flow.

• If a parent later wants to revoke access, they will need to revoke access to any dependent products first before they can revoke access to the essential account system.

👉 Experience the parental consent flow for a bundled Account System product in the interactive demo below.

Questions or feedback?

As always, we’re here to help. If you’re not sure how to model your account system, or if you’re unsure whether this feature applies to your integration, reach out to your Client Relationship Manager or Contact Us.