What this category of data looks like
This category of data primarily comes from interface management platforms, test environment logs, databases, and message queues. Teams produce daily documents including interface test cases, joint debugging issue tickets, test environment descriptions, and test reports. Data updates occur daily or with each version iteration. Document structures include interface addresses, request parameters, response formats, test steps, and exception log fields. No additional statistical quantitative indicators are included. Teams only record test execution processes and results.
What constraints these characteristics impose on permissions and data isolation workflows
This category of data covers interface configurations, test execution logs, and environment-sensitive information. Data from multiple sources is stored dispersedly. Administrators configure independent access permissions for different data sources. The high-frequency update feature of data requires administrators to adjust permission rules synchronously with interface versions and test environment changes. This prevents leaks caused by outdated permissions. Teams divide access boundaries for test personnel, developers, and platform maintainers with different roles. This prevents unauthorized personnel from modifying test cases or accessing production-level test environment data. Administrators restrict the access scope of sensitive logs and interface parameters generated during testing. Only authorized personnel within the project can view them.
How to configure settings
| Configuration Item | Recommended Approach | Rationale |
|---|---|---|
teamId | Bind the unique identifier of the current integration test project | Based on the FastGPT v4.17.0 team permission model, isolate test cases and log data from different test teams via project IDs |
tmbId | Bind the exclusive test environment identifier | Distinguish permission boundaries between development, test, and pre-production environments to prevent cross-environment data cross-access |
| Test case access permissions | Assign by role: only project maintainers can edit, test personnel can only view and execute | Prevent unauthorized modification of interface parameters or test steps, avoid joint debugging deviations |
| Sensitive log retention period | Retain for 7 days | Control the retention duration of sensitive logs in the test environment, meet compliance review requirements |
| Public access link validity period | Set to 1 hour | Limit the access duration of temporarily shared test links, reduce data leak risks |
| Test data storage limit | Do not exceed 1000 MB | Control the data storage scale of the test environment, avoid excessive resource occupation affecting other services |
Three common configuration errors
- Symptom: When deploying via intranet docker-compose, OneAPI prompts database connection refusal. MySQL logs show normal startup. Cause: Administrators do not bind database access permissions for the test environment via
teamId, causing the container group to fail to access the specified database instance. - Symptom: When adding a team member, entering the other party's account shows invalid username. Cause: Administrators do not configure the team member permission scope corresponding to
tmbId, so the system cannot recognize accounts outside the project. - Symptom: After generating a public access link, chat records between link users are not isolated. Cause: Administrators do not bind
teamIdto the test project, causing all shared links to share the same data storage pool.
How to confirm configuration is complete
- Project administrators view the project permission configuration page, confirm that
teamIdmatches the identifier of the current test project. - Project administrators attempt to access test cases using a non-project member account, confirm that content cannot be viewed or edited.
- Project administrators generate a public access link, verify that access is no longer available after the link validity period expires.
- Project administrators check the retention duration of test environment logs, confirm that logs exceeding the preset period have been automatically cleaned.
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.