docs: remove redundant permission table from README files

- Remove permission management table from both README.md and README_zh_CN.md
- The table content was redundant as permissions are already clearly described in the text
- Improves document readability by eliminating duplication
- Maintains all essential information in prose format

2 files changed, 0 insertions, 18 deletions

diff --git a/README.md b/README.md
index 0cd6ff7..ac0588b 100644
--- a/README.md
+++ b/README.md
@@ -31,15 +31,6 @@ Sheets are divided into two types, primarily differing in permission management:
 -   **Reference Sheet**: Stores files commonly used across the team, serving as a shared resource library. All members can acquire files from it into their own sheets. Members can submit their own files to the Reference Sheet; after approval by an administrator, they are added to the Reference Sheet for other members to import into their own sheets.
 -   **Member Sheet**: A member's own sheet, used to manage personal projects, tasks, and assets. The member has full management rights over the **sheet structure** (such as adding, moving mappings, etc.), but **edit rights** for the file itself remain exclusive to the file's holder, following the "Acquire First, Edit Later" principle. Typically, newly tracked files automatically grant ownership to the tracker.
 
-| Operation | Reference Sheet | Member Sheet |
-| :--- | :--- | :--- |
-| **Check-in** | All Members | All Members |
-| **Add Item** | All Members (to a staging area) | Owner |
-| **Move Item** | Administrator | Owner |
-| **Unlink** | Administrator | Owner |
-| **Merge** | Administrator | Owner |
-| **Clone** | All Members | All Members |
-
 ### Transferring Files Between Sheets
 
 ​	Through the **Import/Export mechanism** provided by the Sheet System, members can copy a file's **mapping relationship** from one sheet to another. This mechanism transfers the file's **mapping relationship** (i.e., the binding of `VirtualFileId` to a path), not the file entity itself. The file entity always resides in the Virtual File System. This mechanism supports cross-sheet collaboration, such as submitting completed work to the team for sharing, or recommending a file to a specific member for further processing.
diff --git a/README_zh_CN.md b/README_zh_CN.md
index 1fc3907..3e8f53f 100644
--- a/README_zh_CN.md
+++ b/README_zh_CN.md
@@ -31,15 +31,6 @@
 -   **参照表 \(Reference Sheet\)**：存储团队间通用的文件，作为共享资源库。所有成员都可以从中获取文件到自己的表中。成员可以将自己的文件提交到参照表，经管理员审核同意后，即可加入参照表中供其他成员导入到自己的表。
 -   **成员表 \(Member Sheet\)**：成员自身的表，用来管理个人的工程、项目和素材。成员拥有对**表结构**的完全管理权（如添加、移动映射关系等），但对文件本身的**编辑权**仍由该文件的持有者独占，遵循"先获取，后编辑"的原则。通常，新追踪的文件会自动将其所有权赋予追踪者。
 
-| 操作 | 参照表 | 成员表 |
-| :--- | :--- | :--- |
-| **签入** | 所有成员 | 所有成员 |
-| **添加项** | 所有成员（进入临时区域） | 所有者 |
-| **移动项** | 管理员 | 所有者 |
-| **断开链接** | 管理员 | 所有者 |
-| **合并** | 管理员 | 所有者 |
-| **克隆** | 所有成员 | 所有成员 |
-
 ### 表间传递文件
 
 ​	通过表系统提供的 **Import/Export 机制**，成员可以将文件的**映射关系**从一个表传复制到另一个表。此机制传递的是文件的**映射关系**（即 `VirtualFileId` 与路径的绑定），而非文件实体本身。文件实体始终存储在虚拟文件系统中。此机制支持跨表协作，例如将完成的工作成果提交给团队共享，或将文件推荐给特定成员进行后续处理。