Teams that want to show different widget content to individual readers currently have only one option: implement full JWT authentication. For teams without an existing identity/auth layer suited to JWT, this is a significant integration lift relative to the narrower need of restricting content per reader.

Suggested Enhancement:

Provide a lighter-weight mechanism for individual reader-level content restriction in the widget that does not require implementing a full JWT authentication flow, for example, a simpler token or invite-based reader identification method scoped specifically to the widget.

Customer Benefit:

Teams can tailor widget content to individual readers without needing to build and maintain a JWT authentication integration, lowering the technical barrier to adopting reader-level content control.