V3.0-beta1

🚀 BISHENG 3.0 beta1

🔐 1. Permission System Improvements

Granting access to a member used to mean choosing one of four levels — Owner, Can Manage, Can Edit, Can View — and a combination such as "may view and download, but not delete" could not be expressed. Permissions are now composed of individual actions and can be combined as needed.

1.1 🧩 12 Actions × 9 Resource Types: use, edit, download, share, upload file, create folder, move, rename, delete, publish, unpublish, and manage permission — applicable to knowledge spaces, knowledge bases, folders, files, workflows, assistants, tools, dashboards, and channels.

1.2 🎛️ Custom Permission Models: administrators can combine frequently used actions into a permission model ("view + download", for example) and grant that model directly from then on, without configuring every resource and every member over and over.

1.3 📂 Permission Inheritance and Per-Resource Settings in Knowledge Spaces: folders and files inherit permissions from their parent resource by default, and can be switched to their own settings; the switch establishes an independent grant based on the members effective at that moment, and later changes to the parent's permissions no longer propagate down.

1.4 ⚡ Large List Performance: query performance improved for knowledge-space directories and for the app, dashboard, and channel lists.

🧠 2. Task Mode Improvements

2.1 📊 Built-in Office Skill Packs: PowerPoint, Excel, and Word skill packs adapted for BiSheng ship with the deployment and are ready to use on startup.

2.2 📁 Folder Upload and Data Files: upload an entire folder with its original directory structure preserved; data and code files such as csv, json, sql, and py can be uploaded directly for the code interpreter to work on.

2.3 ⏱️ Longer Task Runs and Stability Fixes: the step budget for a single task rises to 600. Fixed alongside it: navigating between pages within a conversation silently reset task mode, and execution steps went missing with certain models.

⚙️ 3. More Improvements

• Manual model status verification: click "Update status" in the model management list to trigger a status update and record the time it was updated.
• In-conversation image preview: uploaded images are shown as thumbnails and open full screen on click, in existing messages as well as new ones.
• Manual save and readable variables in workflow report templates: the report template editor gained a "Save" button, and inserted placeholders carry the source node's name.
• New role quota: cap how many knowledge spaces the members of a role may create, configured in role settings.

💡 4. Upgrade Notes

This permission upgrade requires a one-time data migration, so schedule a maintenance window in advance: after updating the image and completing the schema upgrade, an operator runs the permission data migration script once to convert the old permission data into the new system.