Available in: Project development and Site production. Application Storage is configured for the actual environment. Chat and Agent working files, conversation Sources, and configuration Files use separate content services.
Application Storage holds objects your software uses, such as user uploads, generated documents, and media. It is separate from the File system used to develop the software and from the Files used as operator background context.
Enable Storage and check an upload
- As a Project admin, open Storage and choose Add storage.
- Choose Managed storage to start provisioning. If you use your own storage, select its provider under Or connect your own and follow the connection prompts.
- Save
sample-note.txtwith the single line “Delivery at noon”. Once storage is ready, choose Upload and select the file. - Reopen Storage, select
sample-note.txt, and check its name and size in the file details. From the Project backend, run the following command. The response should readDelivery at noon.
curl --fail-with-body "$PLAYBOOKS_STORAGE_URL/storage/files/content?key=sample-note.txt" \
-H "Authorization: Bearer $PLAYBOOKS_STORAGE_KEY"Choose the right place
| Material | Destination |
|---|---|
| Application source | File system |
| Application-managed uploads and objects | Storage |
| Input to a conversation | Sources |
| Reference documents for the operator | Configuration Files |
| Working report | File system |
Configure access
Configure Storage for the actual Project development or Site production scope. Use server-side credentials where required, validate uploads, and apply application authorization to object reads and writes.
An object path or a link is not a substitute for an access policy. Consider whether an object is private, shared with selected users, or deliberately public. Keep upload limits and supported formats close to the workflow that accepts them.
Retain and remove data
Define what should happen when an application record is deleted, a user removes an upload, or an export is replaced. Deleting a database row and deleting its associated object can be separate operations; verify both when the workflow requires it.
Production objects are not replaced by publishing a new code release. Runtime restarts also should not be treated as a way to clear durable application data.
Retained capacity and transfer can incur Storage usage according to applicable allowances. Review Usage and the selected provider's supported lifecycle before relying on retention or recovery behavior.
Example: attach a document to a record
A customer uploads a document associated with a request. Store its application object in the configured Storage scope and keep the record’s reference in the database. Check that a user cannot read another customer’s private object merely by obtaining its path.
Define what happens to the object when its record is deleted. See Databases and Security for the surrounding application responsibilities.
Check the complete upload flow
Try an allowed file and an unsupported file in development. Verify the application record, stored object, download access, and removal behavior together. A successful upload response alone does not show that the application protects later reads. Use Testing to define the workflow checks.