This documentation applies to FastGPT v4.17.0.
What this category of data looks like
The core carriers of data for this category are four types of documents: collection plans, sample specifications, authorization statements, and task schedules. Data sources include customer requirements, public data sources, collection tools, and in-house sample libraries. Data updates follow a per-project cycle or weekly cadence. Fields include sample scope, collection fields, authorization boundaries, schedule nodes, etc. There are no unified fixed units; corresponding formats must be matched based on project requirements.
What constraints these characteristics impose on the "sharing and embedding" link
Documents such as collection plans and authorization statements involve customer customization requirements and compliance information. The sharing and embedding link must strictly control visibility to avoid sensitive data leaks. The weekly or per-project data update cadence requires that task configurations in external business systems be associated with corresponding project identifiers to prevent cross-project data confusion. Customized field specification requirements require external business systems to retain original field mapping relationships to avoid data format errors. The pre-procedure for collection legality verification requires external business systems to prompt compliance verification steps at the embedding entrance to avoid infringement risks.
How to set configurations
| Configuration Item | Recommended Approach | Basis for This Approach |
|---|---|---|
Sharing entrance shareId | Copy the complete share link generated by the system; do not replace the identifier manually | Identifies the sharing entrance; business records and data permissions for data collection task design must still be handled by external systems |
| Share link validity period | Test starting point: 7 days; adjust based on actual testing of the collaboration cycle and revocation requirements for data collection task design | Verify availability within the validity period and access behavior after expiration; this value is not an official default or industry statistic |
| QPM | Test starting point: 20 requests per user per minute; adjust based on actual load | Limits the access frequency of a single user; needs to be verified combined with request logs and actual load |
| Identity verification | When identity permission requirements exist, first verify commercial version capabilities and the uid returned by the third-party identity service | Holding a share link does not equal having business data permissions; third-party identity and data scope must be verified separately |
| Referenced content display | Select display configurations for referenced fragments, full text, and original text based on the sensitivity of data collection task design materials | Check displayed content within the authorized data range; do not use hidden interfaces as a substitute for data permission control |
| Conversation record verification | Test example: Prepare 10 question-and-answer samples for data collection task design, check in the same browser and another device respectively | Anonymous records rely on browser local identity; retention cannot be guaranteed across devices or after cache clearing |
Three Common Errors
- Failure to open the sharing entrance related to data collection task design. First verify the complete link generated by the system and its validity period, then check the browser request status; do not manually replace
shareId. - The visible range of data collection task design data does not match expectations. Verify third-party identity verification results, workflow request parameters, and data permissions of the external system respectively; the sharing entrance identifier itself does not provide business authorization.
- The same data collection task design question-and-answer pair is not visible on another device. For anonymous scenarios, first check the device, browser, and local identity status; retention cannot be guaranteed across devices or after cache clearing, and service abnormalities cannot be judged solely based on this phenomenon.
How to Confirm Proper Configuration
- Open the embedded page, check that the displayed collection plan fields match the documents of the target project, and confirm that no field mappings are lost.
- Verify that access complies with the permission rules configured by the external business system, and confirm that permission verification takes effect.
- Wait beyond the set share link validity period, attempt to access the link, confirm that the link cannot be opened normally, and verify that the validity period configuration is correct.
- Open the embedded page in IE browser, confirm that the page loads normally, and verify that the compatibility configuration takes effect.
The values provided are common starting points and should be measured against the reader's own samples.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-10-19.