RumataManage project files
Keep uploaded files in project storage and understand capacity, access, and recovery.
Step-by-step guidance.
Before you start
- A project storage allowance.
- Permission to browse or manage the target storage.
Files and database records
Use project storage for file content such as documents and images. Use database records for structured information, such as who uploaded a document and which request it belongs to. They can work together, but they have different permissions and capacity rules.
A project can have separate storages for different purposes, each with a unique name within the project. Check which storage is selected before uploading, deleting, or changing its capacity.
Browse and manage files
- Open Storage in the product tools. Select the intended project storage or bucket.
- Browse its folders or object paths and inspect the file list.
- Upload a harmless test file using the available upload control. Check that it appears with the expected name and size.
- Preview or download it when the file type and permissions allow.
- Verify that your application’s authorized users can access the file and others cannot.
If a storage won’t open, read the error to check whether access is missing, storage is unavailable, or capacity is exhausted.
Reserved capacity and used space
| Measure | Meaning |
|---|---|
| Reserved storage | The capacity committed to a storage. This consumes the account’s storage allowance. |
| Used storage | The bytes actually occupied by files. Used space cannot exceed the reserved capacity. |
| Download transfer | File-body bytes served by an admitted download or workflow read; distinct from storage capacity. |
For example, a storage reserved at 5 GiB with 1 GiB of files has 1 GiB used, but still reserves 5 GiB. Deleting some files reduces used space; it does not necessarily resize the reservation.
If an upload fails for lack of space, inspect both this storage’s used/reserved values and the billing account’s available allowance. Resizing one storage can consume capacity that another storage needs.
Access files through the intended permissions
Grant access only to the groups and workflows that need the files. A file’s object path is its address within storage, not proof that every visitor may read it. Use Rumata-controlled downloads and file activities for authorized access.
Deletion and recovery
You have seven days to recover a deleted storage. During that time, it keeps its name and continues to count toward usage. Purging ends recovery and removes the storage from usage tracking.
This is whole-storage deletion recovery, not a promise of per-file version history or undo for every overwritten or deleted object. Read the confirmation for the specific operation before deleting.
Frequently asked questions
Should this information go in a table or a file?
Use a database table when the product needs to query structured records, such as request status or a due date. Use storage for file objects such as images, documents, and exports. A database record can retain the reference to a stored file.
Will uploading the same filename replace the existing file?
Check the target folder, object key, and Overwrite setting before uploading. The screenshot shows Overwrite off. Do not assume a filename is unique across folders or that overwrite is enabled.
Does a file being visible to me mean every user can access it?
No. Your access in the workspace and an application user’s access are different contexts. Review the storage permissions and the path your application uses to retrieve the file.
Technical reference
Object paths and ownership
Storage objects are addressed by project storage and object path. Keep ownership explicit when storing references in database rows. Do not confuse a frontend build artifact with project storage, or a development machine’s temporary filesystem with a persistent file store.
Server-side file operations
File activities apply Rumata-controlled access. Treat each read, upload, rename, and delete as an authorized operation. Handle capacity rejection and interrupted upload outcomes explicitly. Storage usage reconciliation can correct provider-measured usage; the UI may need a refresh after an operation.