Workspace / Drive
One place for every business resource.
Drive is the integrated resource layer for Thunder SaaS. Files created by imports, exports, reports, uploads, records, chats, and applications can live in one place and be reused wherever permissions allow.
The resource layer behind the workspace.
Drive connects the files your applications create and use. Instead of scattering business resources across separate tools, the platform keeps them available to the applications, conversations, agents, and workflows that have permission to use them.
What Drive holds
Files from every part of the business can meet here.
Drive is not limited to manually uploaded documents. It is the shared resource layer that connects files generated or attached across the platform.
Import files
Files used to bring CSV or XLSX data into an application remain connected to the import process and its shared resource.
Export files
CSV and XLSX exports produce file resources that can be downloaded and reused by the applications and people with access.
Reports and documents
Generated report files and application documents can be stored as resources for later reference or sharing.
Uploads and attachments
Uploaded files can support chats, records, notes, emails, and other business workflows through the same resource model.
One integrated layer
The file stays connected to the work that created it.
A shared file resource can be referenced by more than one part of the workspace. That makes it easier to move from the original operation to the next business action.
Applications
Use resources created by business applications without creating disconnected copies for every workflow.
Conversations
Select files as context for chats and keep the relevant resource close to the discussion.
Agents
Let agents find or read accessible resources when the file is part of the configured task.
Workflows
Use shared resources in operational flows, notifications, reports, and record-based work.
Permission-aware access
One resource layer does not mean universal access.
Drive resources are organization-scoped and access is controlled by permissions and the context in which a file is used. A file can be shared across the platform without becoming public to every user, application, or agent.
Context decides what can be used.
When a user selects a resource for a conversation, record, email, or agent task, the platform checks whether that resource is available to the current organization and operation. Access should always follow the configured role and permissions.
Connected operations
Import and export history remain where the operation happens.
Import and export screens continue to show operation-specific details such as processing status, row counts, file format, errors, and download actions. Drive provides the shared file resource behind those operations; it does not replace their history views.
Import workflow
Choose an import file, map it to an existing table, process the rows, and keep the source file connected to the import details.
Export workflow
Start a CSV or XLSX export, monitor its processing in the application, and download the completed file from the shared resource.
Report workflow
Generate a report file, keep it available as an application resource, and reuse it where the workspace permissions allow.
Resource workflow
Find, read, attach, or reuse a file from the place where the next business action is taking place.
Example
From export to shared business context.
“Export this month’s open invoices and share the result with the finance team.”
The application processes the export, creates the resulting file resource, and makes it available for download or reuse by people and workflows that have permission to access it.
1. Generate
The Books application starts the export using the selected table, filters, and format.
2. Store
The completed CSV or XLSX file is linked to the shared application resource layer.
3. Reuse
The file can be downloaded, attached, or used as context where the operation permits it.
4. Control
Permission checks determine which people, applications, and agents can access the resource.
External portability
Keep resources inside the workspace—or export them when needed.
Thunder SaaS can provide external export paths such as Google Drive for portability and sharing. Treat those paths as exports or destinations, not as automatic two-way synchronization with the integrated Drive resource layer.