Guest Mode and Custom User System Integration Guide

1. Applicable Scenarios

This document applies to scenarios where the integrator already has a custom user system and wants viewers to first enter the Polyv viewing page as guests, then convert to formal user identities through the integrator's login process when login is required.

Typical requirements include:

• Unauthenticated viewers can enter the viewing page to browse content first.
• Viewers trigger the integrator's login process only when performing actions requiring identity, such as interaction or posting comments.
• After viewers complete login on the integrator's login page, their custom user identity is synchronized to the Polyv viewing page.
• The Polyv viewing page subsequently recognizes the viewer as a formal user.

Guest mode can be used for embedded SaaS viewing pages or integrated Web viewing page SDKs. The login trigger methods differ between these two integration approaches.

2. Solution 1: Embedded SaaS Viewing Page

2.1 Implementation Method

Suitable for scenarios where the Polyv SaaS viewing page is used directly and opened via embedding in a web page, app, or mini-program.

The integrator can reuse the guest access and login guidance capabilities of the SaaS viewing page while retaining the custom login system. When a viewer needs to log in, the viewing page guides them to the integrator's login page. After completing login and independent authorization of the user system, the viewer returns to the viewing page as a formal user.

Backend configuration reference:

2.2 Integration Process

Notes:

• The external login address and the post-login redirect method need to be adapted to the actual terminal, such as browser, app, or mini-program.
• The parameters and signatures required for independent authorization must be generated by the integrator's server according to the development documentation.

Technical integration: For independent authorization of the user system in the SaaS scenario, please refer to the User System - Independent Authorization development documentation. Interface parameters, signature rules, and calling methods are subject to that document.

3. Solution 2: Integrated Web Viewing Page SDK

3.1 Implementation Method

Suitable for scenarios where secondary development is performed using the viewing page SDK and its accompanying open-source live viewing page project, requiring customization of the viewing page and login interaction.

The integrator can integrate the custom login process into the login handling section of the open-source viewing page, combine it with existing page routing, pop-ups, and account systems to complete independent authorization of the user system, and handle the page state after login according to the development documentation.

Backend configuration reference:

3.2 Integration Process

Notes:

• Guest access has scenario limitations. Please refer to the development documentation for the specific supported scope. If in doubt, contact the Polyv after-sales team.
• Technical implementation must correspond to the actual project version in use.

Technical integration: For guest authorization, login integration, and post-login page handling, please refer to the "Three, Specific Steps" section of the User System - Guest Login development documentation. Related code locations, event handling, and authorization parameter configuration are uniformly subject to that document and its referenced "User System - Independent Authorization" document.

4. Solution Comparison