Upload, download, and delete files
Handle Workplace files with explicit checks for tenant, folder, classification, filename, and destructive-action impact.
Audience, roles, and scope
Workplace file listing and user actions; retention, backup, sharing policy, and external storage guarantees are separate.
Who this is for
- Workplace users with file access
Roles
- File user
Before you begin
- File-area access
- Authorization for the selected file and destination
Article tags
- files
- upload
- download
- delete
- data
Procedures
Follow the sequence and stop when identity, authorization, target, or result differs from the article.
Upload a file safely
Verify local content and remote destination before transfer.
- 1Inspect the file
Open the local file, confirm content and classification, and remove unnecessary embedded personal or confidential data.
- 2Choose the destination
Confirm tenant, folder, filename, and any visible access context before selecting the file.
- 3Upload and verify
Upload once, wait for completion, then confirm the expected name, size, and location in the file list.
The approved file appears once in the intended Workplace location.
Delete a file
Treat deletion as potentially irreversible.
- 1Identify the exact file
Verify name, location, owner, and content; check whether collaborators or processes depend on it.
- 2Confirm retention requirements
Follow organization retention, legal-hold, backup, and approval requirements before deletion.
- 3Delete once and verify
Use the displayed delete action, confirm only the intended target, and check the resulting list state.
Only the intended file is removed in accordance with retention and authorization requirements.
Security and data handling
- Use only the identity, tenant, role, and data scope approved for the task.
- Verify targets and expected effects before saving, sending, publishing, exporting, deleting, or approving.
- Keep secrets and regulated data out of screenshots, URLs, free-text diagnostics, and ordinary support messages.
- Scan and classify files according to organization policy before upload or download.
Known limitations
- The interface alone does not establish backup, recovery, retention, legal hold, malware scanning, or secure sharing guarantees.
- File size and type limits depend on connected storage and deployment configuration.
Troubleshooting
You cannot open Vianordis Workplace
Likely cause: The session expired, the account is not entitled, or the required tenant or role claim is missing.
- Open the service through the approved Vianordis entry point and sign in again.
- Confirm the intended organization, tenant, and account are in use.
- If access remains denied, record the time and request an entitlement check; do not attempt direct-URL bypasses.
A documented control or navigation item is not visible
Likely cause: The current role, subscription, tenant configuration, release status, or feature flag does not expose it.
- Confirm the audience, role, prerequisites, and limitations in this article.
- Refresh after a new sign-in and verify the correct tenant context.
- Ask the responsible administrator whether the capability is enabled before reporting a defect.
A saved change or background result is not visible
Likely cause: Validation failed, processing is incomplete, the view is stale, or the feature is locally simulated rather than persisted.
- Review inline validation, status indicators, filters, and the selected tenant or workspace.
- Refresh once and search by a stable identifier before repeating the action.
- Do not repeat irreversible or externally visible actions until the first operation's state is known.
Source verification
File listing, upload, download, and deletion controls were reviewed in the pinned source.
Reviewed paths at 5752ab1
src/app/files/page.tsxsrc/lib/dam/client.tssrc/app/api/dam/[...path]/route.ts
Contact support
Contact support when
- A repeatable Vianordis Workplace error blocks an approved task
- Expected access, tenant scope, data, or status appears incorrect
- A security, privacy, financial, compliance, or data-loss concern is suspected
Include
- The page, action, expected result, and exact error text
- The time of occurrence with time zone and whether it is reproducible
- Your tenant, role, browser, and sanitized record or correlation identifier
- The troubleshooting steps already completed
Never include
- Passwords, access tokens, API keys, recovery codes, session cookies, or private keys
- Unredacted personal, financial, health, student, employee, or other regulated data
- Confidential documents or message bodies unless support provides an approved secure channel