Understand file-storage responsibilities
Use supported upload/preview/delete actions and secure web-server permissions.
Before you start
Use the account and administrative authority appropriate to the data. Retention and legal holds are separate from routine record editing.
Follow these steps
- Identify the account, record type and evidence affected by this task.
- Use supported upload/preview/delete actions and secure web-server permissions.
- The module includes multiple attachment folders/actions; verify files are not directly enumerable.
- The relevant access, retention or evidence control has a verified result.
Fields, rules and limits
- The module includes multiple attachment folders/actions; verify files are not directly enumerable.
- Protected files resolve within the current workspace. SaaS tenants cannot fall back to shared legacy file paths merely because an older database row names one. Report a missing migration/link rather than exposing a direct filesystem URL.
Check it worked
The relevant access, retention or evidence control has a verified result.
If something does not look right
If the expected result is missing, check the saved record, the current workspace and the action’s permissions. Record the exact validation message; do not repeat a state-changing action until you know whether the first attempt saved.
Questions and answers
What should I verify for this task?
The module includes multiple attachment folders/actions; verify files are not directly enumerable. Protected files resolve within the current workspace. SaaS tenants cannot fall back to shared legacy file paths merely because an older database row names one. Report a missing migration/link rather than exposing a direct filesystem URL.
Why is the record or action unavailable?
Use the account and administrative authority appropriate to the data. Retention and legal holds are separate from routine record editing. Check the current company and record relationship before requesting additional access.