What Data for This Category Looks Like
This data primarily comes from customer interviews, bidding documents, vendor product materials, and historical project plans. Four core document types are regularly produced: technical solution documents, customer requirement research forms, quotation lists, and demo scripts. Data updates follow a per-project cycle, with one update completed each time requirement clarification or quotation adjustment is finalized. Each single update covers all associated documents under a single project. Documents are organized by project dimension, including fields such as project number, customer name, technical roadmap, and quotation details. Some documents are linked to progress nodes of internal operation work orders, used by duty personnel to track preparation for pre-sales project implementation.
Constraints Imposed by These Characteristics on Permission and Data Isolation
Because this category of data is organized by single project and linked to internal operation work orders, permission boundaries must be strictly divided by project and team to prevent leakage of sensitive information such as cross-project pre-sales solutions and quotations. Since data updates occur once per project per week, permission configurations must support dynamic adjustments, synchronizing permission ranges with updates to project documents. Information access needs vary across pre-sales roles, so field-level permission differentiation is required. For example, sales personnel can only view quotation lists, while technical consultants can access complete technical solutions. Additionally, for scenarios with login-free demo links, the project scope bound to the link must be restricted to prevent unauthorized personnel from accessing confidential documents of specific projects.
Configuration Settings
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
teamId | Bind to the team ID of the current pre-sales project | Isolate data by project team, ensuring only authorized team members can access pre-sales documents for the corresponding project |
| Login-free link binding scope | Only associate document IDs of the current project | Restrict login-free links to only access pre-sales solutions for the corresponding project, avoiding cross-project data leakage |
| Role permission grouping | Configure field permissions by pre-sales role; sales personnel can only view quotation lists | Differentiate information access boundaries across different pre-sales roles, matching daily work information viewing requirements |
tmbId | Bind to the team identifier of internal operation work orders | Link to work order permissions for operation duty, ensuring duty personnel can only access pre-sales documents associated with the corresponding work order |
| Login-free link quantity limit | Default 10 for team edition, adjustable to 100 | Match demo requirements for different pre-sales projects, supporting on-demand adjustment of link creation quantity |
| Permission expiration time | 7 days | Adapt to temporary access needs for pre-sales demos, avoiding information security risks posed by long-valid links |
Three Common Misconfigurations
- Symptom: The interface prompts "No permission to operate this conversation record". Cause: The
teamIdof the current operating user is not bound to the team ID of the corresponding pre-sales project, causing the permission verification logic to fail to match the authorized scope. - Symptom: The login-free link cannot access the specified pre-sales document, and the prompt indicates that the link quantity has exceeded the limit. Cause: The login-free link quantity has not been adjusted according to the project subscription plan configuration, or the link is not bound to the document ID of the current project.
- Symptom: Cross-project pre-sales solutions are accessed by unauthorized team members. Cause: The
teamIdbinding rule is not configured by project dimension, causing the team permission coverage range to exceed the boundary of the current pre-sales project.
How to Verify Proper Configuration
- Access the permission management page of the FastGPT v4.17.0 backend, view the project list bound to
teamId, and confirm that the team ID of the current pre-sales project has been correctly associated with the corresponding role. - Create a login-free link, test that only pre-sales documents for the current project can be accessed, and that technical solutions or quotation lists for other projects cannot be opened.
- Switch to a test account with the sales role, confirm that only quotation list fields can be viewed, and that detailed technical roadmap content of the technical solution document cannot be accessed.
- Access the login-free link management interface, confirm that the link quantity can be adjusted to the upper limit allowed by the subscription plan as needed.
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.