What This Category of Data Looks Like
Each entry in this category corresponds to a customer provisioning order. Data sources include CRM systems, contract orders, identity management systems, and the FastGPT product backend. Update frequency is once per order trigger or daily synchronization. Supporting documents include provisioning application forms, tenant configuration sheets, admin account lists, and delivery confirmation sheets. Fields include customer unique identifiers, tenant IDs, admin permission configurations, provisioning statuses, and more. No unified aggregated global data pool exists, and single-tenant data is isolated independently.
Constraints Imposed by These Characteristics on the Sharing and Embedding Workflow
This category of data is updated individually and sourced from multiple locations. Sharing and embedding must bind to the unique tenant identifier generated by the external system to prevent cross-tenant data leaks. Each data entry is associated with multiple supporting documents. During embedding, the external system filters associated documents by tenant dimension to ensure displayed content matches the corresponding order. Data updates occur frequently, so the sharing link authentication logic adapts to real-time synchronized tenant configuration changes from the external system, avoiding content failure caused by configuration updates. Additionally, information from the provisioning result confirmation step is generated by the external system and embedded in shared content, allowing recipients to directly check provisioning status without additional redirects or lookups.
How Configuration Is Determined
| Config Item | Suggested Setting | Rationale |
|---|---|---|
Sharing Entry shareId | The full sharing link generated by the system is copied, and the identifier is not replaced manually | Identifies the sharing entry; customer provisioning and tenant initialization business records and data permissions must still be handled by the external system |
| Sharing Link Validity Period | Test starting point: 7 days; adjust based on actual customer provisioning and tenant initialization collaboration cycles and revocation requirements | Verifies 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 access frequency for a single user; validation requires combining request logs and actual load |
| Identity Verification | When identity permission requirements exist, commercial edition capabilities and the uid returned by the third-party identity service are first verified | Holding a sharing link does not equal having business data permissions; third-party identity and data scope must be verified separately |
| Referenced Content Display | Display configurations for reference fragments, full text, and original text are selected based on the sensitivity of customer provisioning and tenant initialization materials | Checks displayed content within authorized data ranges; hidden interfaces cannot replace data permission controls |
| Conversation Record Validation | 10 customer provisioning and tenant initialization Q&A samples are prepared, and checks are performed on the same browser and another device respectively | Anonymous records rely on browser local identity; retention is not guaranteed across devices or after cache clearing |
Three Common Mistakes
- Sharing entries related to customer provisioning and tenant initialization fail to open. The full system-generated link and its validity period are first verified, followed by browser request status checks; the
shareIdparameter is not manually replaced. - The visible scope of customer provisioning and tenant initialization data does not match expectations. Third-party identity verification results, workflow request parameters, and external system data permissions are verified separately; the sharing entry identifier itself does not provide business authorization.
- The same customer provisioning and tenant initialization Q&A is not visible on another device. For anonymous scenarios, device, browser, and local identity status are first checked; retention is not guaranteed across devices or after clearing browser cache, and this phenomenon alone cannot be used to judge service anomalies.
How to Confirm Configuration Is Successfully Applied
- The full sharing link generated from Application Details > Publish Channels > Unauthenticated Window is copied, opened on a terminal not logged into FastGPT, and identity authentication verification is confirmed to trigger. Identity verification functionality is only supported in the commercial edition; when using anonymous local identity, localId on the same device and browser supports conversation records, and retention is not guaranteed across devices or after clearing browser cache.
- The
shareIdparameter in the embedded code is checked, and confirmation is made that it is the valid sharing entry identifier generated by the system. - The embedded page is visited, and confirmation is made that displayed documents match the current tenant’s supporting materials such as the provisioning application form and tenant configuration sheet.
- The embedded domain whitelist is modified, and verification is made that non-whitelist domains cannot load embedded content normally.
The values provided are common starting points and should be evaluated 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.