File Management

Menu path: Resource Management → File Management. This guide targets tkl-main 2.00.083 and its matching frontend. Administrators must confirm deployed frontend/backend capabilities and database migrations first. The management permission is 1402.

Store models, textures, images, videos and documents here. Keep code and necessary small assets in Micro Applications, and reference large resources by file ID. Ordinary files and micro-application files have separate quotas.

Upload and maintain files

1. Open File Management and check the organization's current usage.
2. Click Upload Files, select files, and optionally enter aliases, tags and remarks. Enable sharing only when needed.
3. Click Start Upload. Multiple files upload individually; inspect each result rather than treating a partial upload as complete.
4. Check file names, sizes and sharing states. Preview or download to verify content; unsupported formats require a suitable local viewer.
5. Edit changes only alias, tags and remark. Use Replace File to change content.

Limit	Current maximum
One ordinary file	50 MiB
All ordinary files in one organization	50 MiB

The UI may show MB, but limits use 1024 × 1024 bytes. Read /thinklink/custom-file/quota before uploading; compress or reduce oversized resources.

Replace content while preserving links

1. Choose Replace File in the target file's action menu.
2. Select and confirm the new file. Download a backup first if the old content is needed.
3. Check the preview and applications that reference the resource.

Replacement preserves the file ID, original filename, alias, tags, remark, sharing state and share code. Existing valid links return new content. Quota usage is recalculated as current usage minus old size plus new size. There is no user-facing historical version recovery.

Invalidate application caches using update_time or an application resource version after replacement. An unchanged file ID or URL does not mean unchanged content.

Shared and private access

• Authorized signed-in users can obtain a private access ticket, valid for 7200 seconds. Obtain another after expiry.
• Enabling Sharing permits anonymous access for anyone holding the public link.
• Disabling sharing invalidates old public links. Re-enabling creates a new share code. Copy the current link instead of repeatedly enabling sharing to retrieve it.
• Disabling sharing does not revoke previously issued private tickets that have not expired.

Persist the file ID in application configuration, not a temporary URL. Show an unavailable state when permissions or sharing changes prevent access.

Use the file API in micro applications

All paths below have the /thinklink/custom-file prefix and use the current organization's authenticated context.

Method and path	Purpose and request
POST /quota, /find-page	Read quota and paginated file list
POST /upload	multipart file; optional alias, JSON-array-string tags, remark, shared
POST /replace	multipart id and file; preserve identity while replacing content
POST /batch-save-update	{dataList:[{id,alias?,tags?,remark?}]}; metadata only
POST /change-share	{id,shared:boolean}; change sharing
POST /access-ticket	{id}; returns ticket and expires_in
GET /v/:ticket	Read the file stream with a valid ticket
POST /download	{id}; download the file stream
POST /batch-delete-by-ids	{ids:[...]}; delete selected files

Use quota → upload and persist file ID → request ticket when needed → load content. Do not construct public URLs from object-storage paths. Load and reuse resources by scene and visibility; alarm or online-status polling must not download models again. Release unused resources and Blob URLs on scene exit. See Micro-application Data and Resources.

Deletion and errors

Check dependent applications and back up needed content before deletion. An error can occur after database deletion but during object-storage cleanup. Re-read the list and inspect the failed stage before reporting either no deletion or complete cleanup.