What the documents look like
Franchise filing management works with the commercial franchise information management system, enterprise licences, store lists and contract ledgers. The daily documents are franchise contracts, operations manuals, filing materials and information disclosure documents. Compared with head-office site selection and store opening, this category handles legal disclosure and the commerce department system, and does not handle specific premises engineering. Sharing and embedding in order fulfilment and after-sales question handling must keep the verification status of those materials separate from the external sharing entry point. A share link identifier is used for access only and does not act as business authorization. The no-login window generates a localId for each user, guarantees use only on the same device and same browser, loses records when the device changes or the browser cache is cleared, and allows pulling only the most recent 30 days and 20 records. Preparing filing materials, checking the two stores and one year condition, and updating franchise information are the most time-consuming steps. A share link does not complete that work automatically.
Constraints at the shared access step
The no-login window is created in the application details under publishing channels. After a name is entered, the link is generated, and the name is used only for record display. Expiry time, QPM, point cap, identity verification, real-time running status, viewing quoted chunks, viewing full quoted text, and downloading or opening the source original are configurable parameters, and some parameters are supported only in the commercial edition. Identity verification is a POST request root address. Initialization, conversation start and conversation end each send a request to a specific interface under that address. The server only needs to return whether verification succeeded. On success, data.uid must be returned, and uid must be a string that does not contain the characters "|", "/" or "\" and is no longer than 255 bytes; otherwise an Invalid UID error is returned. The authToken is passed as an extra query parameter on the share link, and FastGPT carries the token parameter in the body of the authentication interface. The conversation result reporting interface has no specified return value, and totalPoints and token can be observed. A similarity setting does not perform permission or entity isolation, and retrieval is not authorization.
Hypothetical paper exercise sample: a franchisor head office plans to embed an information disclosure document verification note into an internal after-sales question page. The material text is: "This note corresponds to Section 4 of the March 2025 version of the Information Disclosure Document. The verification scope is the operating records of two directly operated stores for a full year. The material status is that it has been reviewed by franchise legal affairs and has not been submitted to the commerce department." The draft sentence to be assessed is: "This disclosure document has completed filing and can be shared directly with prospective franchisees." A separate handover request states: "Add authToken to the share link; after opening it, the user is considered authorized to view."
Configuration and implementation checks
| Configuration item | Use on this page | Verification method |
|---|---|---|
| Name | Records the display name of the share link | Compare word by word with the title of the information disclosure document verification note |
| Expiry time | Controls the usable time range of the link | Compare with the validity range stated in the material; the hypothetical starting point for this exercise is set to the period corresponding to the March 2025 version, because the sample uses the version date to define its scope |
| QPM | Maximum access count per user per minute | Confirm against the actual edition whether it is configurable; no default value is set |
| Point cap | Maximum billing data produced by the link | Confirm with the team that owns the cost; no value is specified here |
| Identity verification | Connects to a third-party system for verification and callback | Commercial edition only; judge by the official interface returning success and uid |
| View full quoted text | Controls display of the full quoted text | Compare with the quoted scope of the information disclosure document verification note |
Three common errors
- Treating the share link identifier as business authorization. The input is the draft sentence above. Compare "has completed filing" with the material text "has not been submitted to the commerce department". The sentence does not match the source status and is unsupported.
- Treating authToken concatenation as execution of authorization. The input is the handover request. Compare "considered authorized" with the identity verification description that the interface returns only success and uid. Opening the link does not constitute authorization; authorization status requires separate verification.
- Treating similarity or retrieval results as a permission filter. The input is a quoted chunk returned by retrieval. Compare it with the verification scope of the information disclosure document. Retrieval does not exclude unauthorized records, and material status requires manual verification.
How to verify the setup
- Input the material text and the draft sentence. Compare "has completed filing" with "has not been submitted to the commerce department". If the statuses do not match, judge the sentence unsupported.
- Input the handover request and the identity verification description. Compare "considered authorized" with the interface returning only success and uid. If the request equates opening the link with authorization, judge it as pending verification.
- Input the share link configuration and the validity range stated in the material. Compare the expiry time with the version date. If the two do not match, record it for manual review.