What the documents look like
Livestream after-sales work concentrates after a single broadcast ends. Refund applications and reshipment orders arrive in the same window, while customer-service IM, warehouse WMS records and logistics tracking each capture a different stage. Store service and internal training need the livestream order list, refund applications, reshipment orders and script templates in one shared place so store staff can review and practise. The supplied brief gives an update rhythm of after each session and daily; this page does not infer batch synchronisation or real-time triggering from that.
A share link identifier grants access to a page. It does not grant business authority. Anonymous conversation records rely on the same device and the same browser, and a local identifier is generated for each user to pull conversation history from the cloud. Cross-device use requires separate identity and session design.
Constraints at the shared access step
The no-login window is created under Application details - Publish channels - No-login window, and the system-generated full link is copied for use. Any internet user can use that address, and costs are incurred under the team that owns the application. The link name is for record display only. Expiry time, QPM, points cap and identity verification are parameters, and some parameters are configurable only in the commercial edition.
Identity verification is a POST root address. Once filled in, share-link initialisation, conversation start and conversation end each send a request to a specific endpoint under that address. The server only needs to return whether verification succeeded, in the unified response format with success, message or msg, and data.uid. FastGPT judges whether success is true to decide whether to allow the user to continue. The uid is the user's unique credential and must be returned; its format is a string containing no "|", "/" or "\" characters and no more than 255 bytes, otherwise an Invalid UID error is returned. The uid is used to pull and save conversation records.
An extra query parameter authToken can be appended to the share link. FastGPT carries token=[authToken] in the body of the authentication interface. Retrieval and identity verification are separate concerns; a similarity score does not carry permission or entity isolation.
Hypothetical paper exercise sample: a store training lead plans to place one livestream after-sales script template and one refund-application handling note into a no-login share link for store agents to review during a training period. Material source text, two sentences: "Refund applications for this session concentrated within two hours after the broadcast started, and reshipment orders must be checked against the warehouse WMS outbound record." "The reshipment time promised in the script template is based on the actual warehouse outbound time." Draft sentence to be judged: "This share link has passed identity verification, so store agents can confirm refunds on behalf of the store through the link." This sentence treats link access as business authorisation. The material states no authorisation clause, so the judgement is unsupported.
Configuration and implementation checks
The table lists only settings or implementation checks that the official document describes for this feature and this task. The values are hypothetical starting points for this paper exercise, chosen so they can be compared with another value; they are not official defaults.
| Configuration item | Hypothetical starting point for this exercise | Check method |
|---|---|---|
| Link name | Store after-sales training material | Used for record display only; unrelated to business authorisation |
| Expiry time | End date of the training period | Compare with the training plan date; after expiry the link cannot be used |
| QPM | 10 visits per user per minute | Compare with actual store-agent visit frequency; confirm the configurable range for the edition in use |
| Points cap | Covers the estimated usage for the training period | Compare with the usage limit of the share entry and the cost ownership |
| Identity verification | Fill in the third-party verification root address | Verification returns success and uid; check whether the uid format is compliant |
| authToken | Generated by the store system and appended | token is carried in the authentication interface body; check whether it matches the system credential |
Three common errors
- Treating link access as business authorisation. Input: the link and the draft sentence. Comparison object: the material source text. Observable result: the authorisation described in the draft sentence has no corresponding statement in the source text, so it is unsupported.
- Treating a similarity score as a permission or entity filter. Input: the score field returned by retrieval. Comparison object: success and uid returned by the identity verification interface. Observable result: score does not change the range of accessible records.
- Treating a pending state as a completed action. Input: a refund application in pending review. Comparison object: whether the material states that review is complete. Observable result: the material does not state completion, so the state remains to be verified.
How to verify the setup
- Input the two source sentences and the draft sentence from the sample. Compare whether the draft sentence exceeds the authorisation scope of the source text. Observable result: the authorisation described in the draft sentence has no basis in the source text, so it is judged unsupported.
- Input the full address after appending authToken to the share link, together with the authentication interface response. Compare whether success is true and whether the uid format is compliant. Observable result: verification passes when success is true and the uid contains no forbidden characters and is no more than 255 bytes.
- Input an empty result [] and check the downstream design. Compare whether the downstream presents the empty result as empty. Observable result: the downstream handles it as an empty result; this page does not claim that a fictional-rule retrieval will necessarily return []. For libraries using different vector models, first check the identifier and exclude those that do not match; do not run a cross-model retrieval to compare missed recall.