{ "site": "巴别鸟企业网盘文档中心", "base_url": "https://www.babel.cc/babelwiki/", "generated": "2026-06-23", "canonical_language": "zh-CN", "latest_known_version": "v9.4.2.2606171439", "ai_entrypoints": [ "llms.txt", "llms-full.txt", "ai-index.json", "developer-api-index.json", "image-index.json", "content/zh/*.md", "content/en/*.md" ], "pages": [ { "lang": "en", "slug": "overview", "title": "Overview", "description": "Introduce the product positioning, core capabilities, applicable objects and typical usage scenarios of BabelBird Enterprise Drive.", "category": "Overview", "top_category": "使用指南", "keywords": [ "BabelBird", "Enterprise Drive", "File collaboration", "Permission security", "v9.4.2" ], "url": "en/overview.html", "source": "content/en/overview.md", "summary": "BabelBird Enterprise Drive overview BabelBird Enterprise Drive is a product platform for enterprise unstructured data management, file collaboration, security control, AI knowledge base and privatized deployment. It organizes corporate files, department materials, project materials, material libraries, archives, online editing, permission auditing, client synchronization, virtual mapping disks, and Zhichao AI into the same file collaboration system, helping companies turn scattered files into digital assets that are manageable, collaborative, traceable, and intelligently retrievable. BabelBird homepage and product entrance The home page shows BabelBird’s overall positioning around enterprise", "headings": [ { "level": 1, "title": "BabelBird Enterprise Drive overview", "id": "babelbird-enterprise-drive-overview" }, { "level": 2, "title": "Product positioning", "id": "product-positioning" }, { "level": 2, "title": "Main problems solved", "id": "main-problems-solved" }, { "level": 2, "title": "Core Competencies", "id": "core-competencies" }, { "level": 2, "title": "Typical usage objects", "id": "typical-usage-objects" }, { "level": 2, "title": "Version caliber", "id": "version-caliber" }, { "level": 2, "title": "Quick entry", "id": "quick-entry" } ], "images": [ { "src": "../assets/images/home.webp", "alt": "BabelBird homepage and product entrance", "caption": "The home page shows BabelBird’s overall positioning around enterprise network disk, AI knowledge base, privatized deployment and industry solutions." } ], "text": "BabelBird Enterprise Drive overview BabelBird Enterprise Drive is a product platform for enterprise unstructured data management, file collaboration, security control, AI knowledge base and privatized deployment. It organizes corporate files, department materials, project materials, material libraries, archives, online editing, permission auditing, client synchronization, virtual mapping disks, and Zhichao AI into the same file collaboration system, helping companies turn scattered files into digital assets that are manageable, collaborative, traceable, and intelligently retrievable. BabelBird homepage and product entrance The home page shows BabelBird’s overall positioning around enterprise network disk, AI knowledge base, privatized deployment and industry solutions. Product positioning BabelBird is not simply \"uploading and downloading to the network disk\". It is closer to an enterprise file operating system, covering the complete life cycle of files from creation, uploading, previewing, editing, synchronization, sharing, review, archiving to auditing. For privatized deployment customers, Babel can also be delivered in combination with enterprise organizational structure, unified identity authentication, object storage, intranet deployment, security policy, third party system integration and exclusive AI knowledge base. Main problems solved Corporate files are scattered on personal computers, chat tools, mobile hard drives, email attachments and different systems, making it difficult to manage them uniformly. File versions are repeatedly overwritten, and there is a lack of historical versions, change records, access records and traceable collaboration processes. Data needs to be shared between departments, projects, and external partners, but downloading, outgoing, previewing, editing, and validity must be controllable. There is a large amount of unstructured data such as pictures, drawings, contracts, scans, videos, and Office documents, and traditional directory retrieval is inefficient. Enterprises want to use AI on their own documents and knowledge bases, but need to adhere to original permissions, security and privatization requirements. Core Competencies Capabilities Description File management Personal files, corporate files, department folders, project folders, material libraries, archives, multi level directories, file details, tags, descriptions, sorting and batch operations Collaborative editing Office online editing, light document, Markdown/code/text, KM mind map, draw.io flow chart, local client editing and file locking Version and Preview Automatically generate historical versions, version rollback, version comparison, 100+ format online preview, transcoding, annotation, hand drawing and review Sharing and outgoing Invitation sharing, link sharing, snapshot sharing, external collaboration, sharing permissions, validity period, password, approval and sharing log Permission security Enterprise roles, department roles, project permissions, file access control, custom file permissions, watermarks, classification levels, audit logs, IP policies, Mac binding, encrypted folders and sensitive content recognition Client capabilities Windows, macOS, and Kirin clients, supporting upload and download, synchronized folders, virtual mapped disks, local editing and transfer task management Materials and archives Material library, waterfall flow image management, image metadata filtering, file archiving, reading room, loan approval and long term storage Automation tasks Auto clean, auto extract, auto rename, auto organize, auto PDF, signature creation and batch folder creation Zhichao AI AI search, smart search, text to image search, image to image search, OCR, document assistant, table Q&A, enterprise knowledge base, knowledge base robot, AI auto tagging, MCP interface and private AI deployment Privatization and integration Stand alone, cluster, object storage, Xinchuang environment, Enterprise WeChat/DingTalk/Feishu, SSO, API, data ferry and customized development Typical usage objects Role Focus Ordinary members Upload, find, preview, edit, share, sync and mobile access files Department head Department data accumulation, member permissions, project collaboration, sharing control and file statistics Project team Cross department collaboration, external member participation, version management, review comments and project discussions Administrator Organizational structure, accounts, roles, permissions, module switches, watermarks, security policies, logs and reports Implementation and operation and maintenance Private deployment, storage, backup, transcoding, search, AI, third party systems and upgrade maintenance Developer Authentication, file, sharing, enterprise organization, message push and material library related APIs Version caliber The current latest version is v9.4.2.2606171439 . The available capabilities of different customers will be affected by the actual deployment version, authorization module and administrator configuration. The current environment of the enterprise should prevail before use. Quick entry Basic concept of product Feature Matrix File Management Sync with client Virtual mapped drive material library Watermark function Encrypted Folder Sensitive Content Recognition Online editing Permission system Zhichao AI Automation tasks Private deployment Development API Overview FAQ Overview" }, { "lang": "en", "slug": "getting-started", "title": "Product basic concept", "description": "Explain basic concepts such as accounts, devices, personal files, corporate files, departments, projects, libraries, and archives.", "category": "Overview", "top_category": "使用指南", "keywords": [ "getting Started", "account", "department", "project", "Corporate documents" ], "url": "en/getting-started.html", "source": "content/en/getting-started.md", "summary": "Basic concept of product What can the Babel bird do? BabelBird mainly solves three types of problems: unified management of enterprise files, collaboration and data security. Users can synchronize work files to the cloud and access personal files, department files, and project files through browsers, clients, mobile terminals, or internal enterprise portals; they can also edit Office documents online, use local clients to edit files in any format, and avoid accidental overwriting through version management. Supported devices BabelBird supports browser access, and it is recommended to use a modern browser that complies with HTML5 specifications; it also provides Windows, macOS, and Kirin clie", "headings": [ { "level": 1, "title": "Basic concept of product", "id": "basic-concept-of-product" }, { "level": 2, "title": "What can the Babel bird do?", "id": "what-can-the-babel-bird-do" }, { "level": 2, "title": "Supported devices", "id": "supported-devices" }, { "level": 2, "title": "File space", "id": "file-space" }, { "level": 2, "title": "Departments and projects", "id": "departments-and-projects" }, { "level": 2, "title": "Typical entry level operations", "id": "typical-entry-level-operations" }, { "level": 2, "title": "Related questions", "id": "related-questions" } ], "images": [], "text": "Basic concept of product What can the Babel bird do? BabelBird mainly solves three types of problems: unified management of enterprise files, collaboration and data security. Users can synchronize work files to the cloud and access personal files, department files, and project files through browsers, clients, mobile terminals, or internal enterprise portals; they can also edit Office documents online, use local clients to edit files in any format, and avoid accidental overwriting through version management. Supported devices BabelBird supports browser access, and it is recommended to use a modern browser that complies with HTML5 specifications; it also provides Windows, macOS, and Kirin clients, as well as iOS and Android mobile terminals. Privatized deployment can be accessed through enterprise specific domain names, and integration portals such as Enterprise WeChat, DingTalk, and Feishu need to be configured according to modules. File space Space Ownership Typical uses Personal files Personal users Profiles, drafts, personal projects Corporate documents Enterprises and departments Long term sharing, department information, corporate public resources Department folders Departments Long term collaboration within departments, department authority control Project folder Project leader and project members Cross department, cross organization, and validity period collaboration Material library Enterprise material administrator or authorized member Pictures, materials, drawings, reusable assets Archives Archives Administrator Archiving, borrowing, long term preservation, compliance management Departments and projects Departments are the basic unit of enterprise organizational structure and long term file space. Projects are used for temporary or cross department collaboration. You can invite internal members, external members or unregistered users to join, and support project validity period, project leader, project assistant, member permissions and project discussion groups. Typical entry level operations 1. Log in to the address assigned by the enterprise or the official public cloud portal. 2. Go to Personal Files, Business Files, Department Files, or My Projects. 3. Upload files through drag and drop, new button, right click on the client, synchronized folder, mapped disk or mobile terminal. 4. Use the file right click menu to perform operations such as sharing, editing, versioning, permissions, comments, and archiving. 5. Administrators maintain organizational structure, members, roles, permissions, watermarks, logs, and system configurations from the enterprise console. Related questions For issues related to account registration, personal space, enterprise space and basic operations, you can continue to view [FAQ: Getting Started, Account and File Space] (faq basic.md)." }, { "lang": "en", "slug": "feature-matrix", "title": "Feature Matrix", "description": "Summarizes BabelBird Enterprise Drive capabilities across file management, collaboration, security, automation, Zhichao AI, clients, material libraries and private deployment.", "category": "Product Features", "top_category": "使用指南", "keywords": [ "feature list", "automation tasks", "Zhichao AI", "material library", "encrypted folder", "sensitive content recognition", "waterfall view" ], "url": "en/feature-matrix.html", "source": "content/en/feature-matrix.md", "summary": "Feature Matrix BabelBird Enterprise Drive can be understood through the full file lifecycle: upload, creation, preview, editing, synchronization, sharing, permission control, version retention, search, archiving, audit, automation and AI retrieval. Actual availability depends on the deployed version, licensed modules and administrator configuration. Core Capabilities Module Subfeatures Description Typical entry File management Upload, download, drag and drop upload, folder upload, resumable transfer, instant upload, incremental transfer Daily file collection, material accumulation and large file transfer File list, client, mobile app, mapped drive Creation Folders, Office files, light docume", "headings": [ { "level": 1, "title": "Feature Matrix", "id": "feature-matrix" }, { "level": 2, "title": "Core Capabilities", "id": "core-capabilities" }, { "level": 2, "title": "Key New Or Easily Missed Capabilities", "id": "key-new-or-easily-missed-capabilities" }, { "level": 3, "title": "Encrypted Folder", "id": "encrypted-folder" }, { "level": 3, "title": "Sensitive Content Recognition", "id": "sensitive-content-recognition" }, { "level": 3, "title": "Waterfall View", "id": "waterfall-view" }, { "level": 2, "title": "Zhichao AI Subfeatures", "id": "zhichao-ai-subfeatures" }, { "level": 2, "title": "Automation Tasks", "id": "automation-tasks" }, { "level": 2, "title": "Usage Guidance", "id": "usage-guidance" } ], "images": [], "text": "Feature Matrix BabelBird Enterprise Drive can be understood through the full file lifecycle: upload, creation, preview, editing, synchronization, sharing, permission control, version retention, search, archiving, audit, automation and AI retrieval. Actual availability depends on the deployed version, licensed modules and administrator configuration. Core Capabilities Module Subfeatures Description Typical entry File management Upload, download, drag and drop upload, folder upload, resumable transfer, instant upload, incremental transfer Daily file collection, material accumulation and large file transfer File list, client, mobile app, mapped drive Creation Folders, Office files, light documents, text/code files, mind maps, draw.io diagrams, templates Create business files and standard folders directly in the drive New menu File organization Personal files, enterprise files, department folders, project folders, subprojects, file tree, starred files, recent visits Organize files by organization and collaboration scenario Sidebar, file list, project channel File details Tags, descriptions, properties, uploader, versions, access logs, related files Make files searchable, traceable and reusable File details panel Versioning Automatic versions, upload new version, rollback, comparison, version comments Reduce overwrite risk and collaboration conflicts Details, previewer, desktop client Preview and annotation Office, PDF, images, video, audio, CAD, code, Markdown, KM, draw.io and more View and discuss files without downloading File previewer Online collaboration OnlyOffice, light documents, Markdown/code/text editing, KM/Xmind, draw.io Multi user online editing, local editing and file locking Online edit entry, client edit Sharing Invitation sharing, link sharing, snapshot sharing, inbox, upload only, approval, password, expiry Controlled internal, cross department and external collaboration Share menu, projects, inbox Permission system Enterprise roles, department roles, project permissions, file access control, custom file permissions, sharing permissions Control who can view, upload, edit, delete, download, comment and manage Console, department management, file access control Security enhancements Watermark, classification level, IP policy, Mac binding, audit log, allow/deny lists, encrypted folder, sensitive content recognition Protect contracts, finance, HR, R&D, drawings and customer data Console, folders, New menu Desktop client Windows, macOS, Kylin, local editing, transfer list, right click upload, right click sync, anonymous download Connect cloud files with local workflows Desktop client Synchronization Two way, upload only, download only, blacklist, schedule, conflict handling, 200k folder sync Offline editing, distribution and local working directories Client sync management Mapped drive On demand cloud access, virtual drive, local app opening, permission inheritance Access cloud files like a local disk Desktop mapped drive Material library Categories, sub libraries, access control, download approval, thumbnail visibility, image metadata Brand assets, design files, product images, marketing assets and galleries Material library under enterprise files Waterfall view Image heavy folders displayed as thumbnail waterfall Faster browsing of images, drawings, posters and material files File list, material library Archive library Archiving, reading room, borrowing approval, local archive, archive administrator Contracts, deliverables, policies and long term retention Archive library Automation tasks Auto clean, auto rename, auto organize, auto PDF, auto extract, signature creation, batch folder creation Move repetitive file work to background rules Folder context menu, automation channel Zhichao AI AI assistant, AI search, smart search, text to image search, image to image search, OCR, document assistant, table Q&A, deep research Search, read, answer and analyze enterprise files within permission boundaries AI entry, search, Zhichao AI channel Zhichao AI management Enterprise knowledge base, knowledge base robot, custom agent, MCP interface, private model, GPU resources Customer service, presales, training, knowledge bases and third party AI integration Zhichao AI, backend, API Enterprise console Organization, members, roles, tags, watermarks, logs, notices, statistics, module switches, enterprise settings Administer organization, permissions and security policies Enterprise console Private deployment Stand alone, cluster, object storage, Xinchuang, dedicated domain, SSO, WeCom/DingTalk/Feishu, data ferry Intranet, compliance, domestic stack and system integration scenarios Private deployment project Developer API Authentication, files, sharing, enterprise, departments, material library, following, logs Business integration, portal embedding, automation and secondary development API docs Key New Or Easily Missed Capabilities Encrypted Folder Encrypted folders are password protected folders inside shared enterprise drive spaces. Users create them from the New menu, enter a folder name and password, and receive a folder with a lock indicator. Opening the folder requires the password each time; even when files inside are shared, recipients still need the encrypted folder password to access the content. The password must be kept by the creator. The feature uses anonymous encryption, so a lost password cannot be recovered by operators or engineers. See Encrypted Folder. Sensitive Content Recognition Sensitive content recognition lets administrators configure sensitive keywords or recognition policies in the enterprise console. Files detected as sensitive can be marked and, depending on configuration, restricted from viewing, sharing or routed to manual handling. It is useful for contracts, certificates, personal data, customer materials, finance files, R&D materials and regulated content. See Sensitive Content Recognition. Waterfall View The waterfall view is designed for image heavy scenarios. It lets users browse material files, design images, product photos, drawings and campaign assets as thumbnails. Image heavy folders can be switched or adapted to waterfall mode and combined with material libraries, tags, image metadata, text to image search and image to image search. See Material Library. Zhichao AI Subfeatures Subfeature Purpose Related page AI assistant Answer questions from enterprise knowledge bases and optional web search Zhichao AI AI search Return answers and citations in search results AI Search and Smart Search Smart search Q&A, deep research and article drafting AI Search and Smart Search Text to image search Find drive images by text description Image Search and OCR Image to image search Find similar images by uploading or selecting an image Image Search and OCR Image OCR Extract text from images and make it searchable Image Search and OCR Document assistant Summarize, explain and answer questions for the current document AI Assistant and Document Assistant Table Q&A Ask questions, analyze data and assist formulas in Excel Standard Modules AI auto tagging Match files to the most relevant tags in the tag library Standard Modules Enterprise knowledge base Turn enterprise documents into searchable and answerable knowledge sources Knowledge Base Robots and Agents Knowledge base robot Create internal or external Q&A robots AI Customer Service and Knowledge Base Robot MCP interface Provide knowledge base access and file operations to external AI applications Standard Modules Automation Tasks Task Purpose Notes Auto clean folder Clean matching files by rule Temporary upload areas, collection boxes and periodic cleanup Auto extract Extract archives after upload Supplier packages, material packages and project deliveries Auto rename Standardize file names by rule Contracts, images, project files and deliverables Auto conversion Convert files to PDF or other target formats Archiving, approval, signatures and read only workflows Auto organize Move files to target folders by rule Collection, distribution, archiving and classification Signature creation Create or apply signature workflows Contracts, approvals and formal deliverables Batch folder creation Generate folders from templates or data Project setup, customer folders and department standards Usage Guidance 1. Map the workflow around file intake, collaboration, sharing, archiving and retrieval before choosing modules. 2. For sensitive files, combine permissions, file access control, watermarks, encrypted folders, sensitive content recognition, audit logs and download controls. 3. For image and material scenarios, prioritize material libraries, waterfall view, tags, image metadata, text to image search and image to image search. 4. For repetitive file handling, use automation tasks to standardize naming, organizing, PDF conversion, cleanup and folder creation. 5. For AI usage, confirm knowledge scope, permission inheritance, model deployment, data flow and audit requirements first." }, { "lang": "en", "slug": "file-transfer", "title": "file transfer", "description": "Data transmission mechanism for uploading, downloading, synchronizing disks, and mapping disks.", "category": "Product Features", "top_category": "使用指南", "keywords": [ "File Management", "file transfer", "BabelBird" ], "url": "en/file-transfer.html", "source": "content/en/file-transfer.md", "summary": "File transfer Data transmission mechanism for uploading, downloading, synchronizing disks, and mapping disks. Detailed description The data transmission module is the core component of BabelBird Enterprise Drive and is responsible for managing the data transmission of upload, download, synchronization disk and mapping disk. This module uses a variety of technologies to ensure data security, reliability and efficiency. Technical features File chunking: The data transfer module uses file chunking technology to break large files into small chunks for more efficient transmission and storage. This not only helps reduce network traffic and server resource consumption, but also supports resumed dow", "headings": [ { "level": 1, "title": "File transfer", "id": "file-transfer" }, { "level": 2, "title": "Detailed description", "id": "detailed-description" }, { "level": 3, "title": "Technical features", "id": "technical-features" }, { "level": 3, "title": "Advantages", "id": "advantages" } ], "images": [], "text": "File transfer Data transmission mechanism for uploading, downloading, synchronizing disks, and mapping disks. Detailed description The data transmission module is the core component of BabelBird Enterprise Drive and is responsible for managing the data transmission of upload, download, synchronization disk and mapping disk. This module uses a variety of technologies to ensure data security, reliability and efficiency. Technical features File chunking: The data transfer module uses file chunking technology to break large files into small chunks for more efficient transmission and storage. This not only helps reduce network traffic and server resource consumption, but also supports resumed downloads and incremental uploads and downloads. Hash verification (second transmission): Hash verification is used to ensure file integrity during data transfer. Each file block has a corresponding hash value, and the server and client verify these hashes against each other to detect any data corruption or tampering. At the same time, if there is already a file with the same hash code in the storage system, the file does not need to be uploaded again. Realize the instant transmission function. SSL transfer: The data transmission module uses the SSL (Secure Sockets Layer) protocol to encrypt data transmission to ensure the confidentiality and security of data during transmission. This is critical for the transfer of sensitive corporate data. Resume upload from breakpoint: BabelBird Enterprise Drive supports breakpoint resumption, allowing users to continue uploading or downloading files from the last interrupted point without restarting the entire process if the transmission is interrupted. This saves time and bandwidth. Incremental upload and download: The data transfer module also supports incremental uploads and downloads, allowing users to transfer only chunks of files that have changed, rather than the entire file. This is useful in cases of large files and frequent synchronization. Advantages Data integrity: File chunking and hash verification ensure data integrity, reducing the risk of data corruption or tampering. Data security: SSL transmission provides end to end encryption of data, ensuring that data will not be snooped or stolen during transmission. Efficiency: Breakpoint resumption and incremental upload and download improve the efficiency of data transmission, saving time and bandwidth. Save storage space: Using file hash code technology, only one copy of a file with the same hash can be stored on disk. No matter how the file path or file name changes, or how many file copies there are in the network disk, the actual storage space of the file only occupies the capacity of one file. (deduplication storage) High speed upload: Files with the same hash value do not need to be uploaded again. If you upload a file that already exists on the network disk, if the same hash value is detected, it will automatically be marked as uploaded successfully, and there is no need to upload it again. The data transfer module is a key component of BabelBird Enterprise Drive. By adopting these technical features, it ensures that users can upload, download and synchronize their files safely and efficiently. The function of this module is to make BabelBird Enterprise Drive a reliable data management platform." }, { "lang": "en", "slug": "file-create", "title": "Create new files and folders", "description": "Create new Office, text, code, mind maps, flowcharts, templates, departments, projects and folders.", "category": "Product Features", "top_category": "使用指南", "keywords": [ "File Management", "Create new files and folders", "BabelBird" ], "url": "en/file-create.html", "source": "content/en/file-create.md", "summary": "Create new files and folders Create new Office, text, code, mind maps, flowcharts, templates, departments, projects and folders. Detailed description The new module is mainly responsible for the creation of files, departments, projects, templates, and folders. In BabelBird, you can directly create new files to work without uploading files. New file creation Office files BabelBird supports creating blank word documents, Excel documents, and PPT documents online. Using the client to create a new document will open the corresponding components of the local office by default to create and edit documents. Creating a new document on the web page will use online office to create and edit documents.", "headings": [ { "level": 1, "title": "Create new files and folders", "id": "create-new-files-and-folders" }, { "level": 2, "title": "Detailed description", "id": "detailed-description" } ], "images": [], "text": "Create new files and folders Create new Office, text, code, mind maps, flowcharts, templates, departments, projects and folders. Detailed description The new module is mainly responsible for the creation of files, departments, projects, templates, and folders. In BabelBird, you can directly create new files to work without uploading files. New file creation Office files BabelBird supports creating blank word documents, Excel documents, and PPT documents online. Using the client to create a new document will open the corresponding components of the local office by default to create and edit documents. Creating a new document on the web page will use online office to create and edit documents. Office documents can be edited online (no need to install office) or edited locally using the client (edited using the office installed on your computer). Online editing supports real time collaborative editing by multiple people. When you use the client to call the local office for editing, the document will automatically be locked for editing to prevent others from editing the document and causing conflicts. Text code file Babel Text Editor can create and open all text files online, such as RTF, TXT, HTML, MD, CSS... For the convenience of customers, the public cloud version only supports creating new TXT and MD (markdown files). Private cloud users who need to create text files in other formats can ask for it to be opened. The text editor is different from the online office in that it does not support collaborative editing, but text files can be edited online. Mind maps and flow charts. BabelBird comes with its own mind map module, which can create and edit mind map files online. Mind map files are saved in KM format by default. It can also be exported to KM, TXT, MD, SVG, PNG, and Xmind formats. BabelBird can also optionally support the creation of flow charts, but you need to purchase the corresponding module license (the non standard version comes with it by default). Other third party modules. Internet applications that comply with WebAPI can theoretically connect to BabelBird and create new files. BabelBird provides third party application docking services. Create from template Many customers need to create a large number of folders with the same structure or create files from a specific template (such as a corporate PPT template). Babel supports creating folders and files from templates. Create templates. People with department file management rights can create templates in the New menu. After clicking Create Template, a template folder will be generated. The template folder is similar to an ordinary folder. You can drag files into the folder to upload, create new folders and departments. The files uploaded in the root directory of the template folder become file templates, and the folders created in the template folder are folder templates. As shown below: Figure: Displayed in the template folder Figure: Displayed when creating a new template Create from templates. Departments with permission to create files and folders can select a template when creating a new file to quickly create files or folders that are consistent with the template. Create new departments and projects Departments and projects can also be created using the New function. Create departments. Departments can only be created under the root department of the enterprise file. The department file belongs to the enterprise, and the super administrator can see the root department and the entire file tree. Users with sub department management rights (default department manager role) can create sub departments. Department folders can add department members and complete department level management. Only members who join the department (department members) and members of the superior department who have the \"View sub department files\" permission can access department files. Department members have basic permissions determined by their role in the department. You can use file permission management to manage permissions on files (folders). Project. Users can create projects under department folders in personal files or corporate files. Projects can invite project team members across departments and companies, and even non registered users from outside the company. Anyone with personal files can create personal projects. To create a project user role under a department, you need the \"Create Folder/Project\" permission. Support for creating subprojects in project folders. The parent of the project folder must be a department or a project, which means that departments cannot be created under ordinary folders. The project creator is the project administrator by default. The project can be transferred, and the project administrator can be transferred to other members and other departments. The permissions of members within the project are specified when the project is created. The project is relatively an independent shared folder. Create a new normal folder Create folders under personal files. Users can create any folders under their personal files and manage them by themselves. Create folders under corporate files Folders need to be created in departments under enterprise files (all folders belong to departments). Users with the \"Create Folder/Project\" role in their department can create folders. As long as the user whose role has the \"Create Folder/Project\" permission can create subfolders in any ordinary folder in the department." }, { "lang": "en", "slug": "files-management", "title": "File management", "description": "File list, sorting, details, tags, pins, shortcuts, copy and move, batch operations and file access.", "category": "Product Features", "top_category": "使用指南", "keywords": [ "File Management", "File Management", "BabelBird" ], "url": "en/files-management.html", "source": "content/en/files-management.md", "summary": "File management File list, sorting, details, tags, pins, shortcuts, copy and move, batch operations and file access. Web main interface The main interface of the web moderator uses left navigation, right file list and top functional area. Common file operations are concentrated in the file list and right click menu. Open file tree Tree view is suitable for scenarios where a large number of folders need to be managed hierarchically. Detailed description Introduction The file management module is one of the core functions of BabelBird Enterprise Drive. It is used for users to manage and operate files and folders, and pushes different file lists to users according to their permissions. It is al", "headings": [ { "level": 1, "title": "File management", "id": "file-management" }, { "level": 2, "title": "Detailed description", "id": "detailed-description" }, { "level": 3, "title": "Introduction", "id": "introduction" }, { "level": 3, "title": "Technical features", "id": "technical-features" } ], "images": [ { "src": "../assets/images/web-main.webp", "alt": "Web main interface", "caption": "The main interface of the web moderator uses left navigation, right file list and top functional area. Common file operations are concentrated in the file list and right-click menu." }, { "src": "../assets/images/web-tree.webp", "alt": "Open file tree", "caption": "Tree view is suitable for scenarios where a large number of folders need to be managed hierarchically." } ], "text": "File management File list, sorting, details, tags, pins, shortcuts, copy and move, batch operations and file access. Web main interface The main interface of the web moderator uses left navigation, right file list and top functional area. Common file operations are concentrated in the file list and right click menu. Open file tree Tree view is suitable for scenarios where a large number of folders need to be managed hierarchically. Detailed description Introduction The file management module is one of the core functions of BabelBird Enterprise Drive. It is used for users to manage and operate files and folders, and pushes different file lists to users according to their permissions. It is also the main interface for users to use the network disk. This module provides a wide range of features to meet the file management and organization needs of business users. Technical features A. File access and organization Paging loading technology: The file management module uses paging loading technology, and the server side database performs file sorting and query operations, and returns the file list to the front desk for paging loading. Such a file list can load hundreds of thousands of rows of data in pages, ensuring that users can efficiently load and browse large numbers of files without affecting performance and user experience. Tree display file list: Babel supports tree like display of file lists, making the organizational structure of files more intuitive and allowing users to easily navigate and manage folders. Permission control: Depending on the user's permissions, the file management module will dynamically display appropriate list items. The file list content seen by different users varies according to different permissions. to ensure that only authorized users can view, edit, or delete specific files and folders. B. File sorting and quick operations Multidimensional sorting: Supports multi dimensional sorting, users can sort by different dimensions such as file name, latest version, file size, etc. File name sorting: Unlike most network disk applications, Babel File Name Sorting supports multi digit sorting in order, so that files whose file names contain numerical numbers can be sorted accurately. (Most network disk file names are sorted only by the first letter, such as: 1, 2, 10, 3, 4, but in BabelBird, the order can be correctly displayed as: 1, 2, 3, 4, 10) Custom global sorting: Users can customize the sorting method suitable for their own global use in the settings. At the same time, the system will remember the sorting method selected by the user in the folder last time, and the next time the folder is opened, it will also be displayed according to the previous sorting. C. Document display and detailed management List mode and waterfall flow mode can be switched: Supports browsing folders in list mode, and can switch to waterfall flow mode for preview. Supports waterfall flow mode browsing of folders (file thumbnails), making file browsing smoother and more intuitive. Folders with many pictures will be automatically adapted to display in waterfall flow mode. File details page: Each file and folder has a detailed details page. Users can manage file information, add file comments, view file access logs, collect statistics on file access, and generate reports. The file details page can also manage file versions. Comment area: Each file or folder has its own comment area, which supports user comments and @mentions of other users to promote team collaboration and feedback. File association: Supports file associated files, allowing users to establish connections between related files for easier access to related information. File attention reminder: Users can remind people who have permission to view files to pay attention to files or folders to ensure that important files are not ignored. D. Advanced search and filtering Advanced search BabelBird supports advanced search function, which can conduct advanced search based on keywords, full text content, time, file format, uploader, search scope, search type and other dimensions." }, { "lang": "en", "slug": "file-versioning", "title": "Version management", "description": "File version generation, rollback, download, preview, comparison, logging and ransomware protection.", "category": "Product Features", "top_category": "使用指南", "keywords": [ "File Management", "Version management", "BabelBird" ], "url": "en/file-versioning.html", "source": "content/en/file-versioning.md", "summary": "Version management File version generation, rollback, download, preview, comparison, logging and ransomware protection. Detailed description Version Management Overview Version management is one of the important functions of BabelBird Enterprise Drive. It allows users to track and manage different versions of files, ensuring that file history and updates can be retained and viewed. Babel's version management function is very powerful and supports multiple update methods as well as version rollback and viewing. Technical implementation Version management uses file blocking and incremental saving techniques to store file versions. This means that each change to a file generates a new version t", "headings": [ { "level": 1, "title": "Version management", "id": "version-management" }, { "level": 2, "title": "Detailed description", "id": "detailed-description" }, { "level": 3, "title": "Version Management Overview", "id": "version-management-overview" }, { "level": 3, "title": "Technical implementation", "id": "technical-implementation" }, { "level": 3, "title": "Version update method", "id": "version-update-method" }, { "level": 3, "title": "Version management function", "id": "version-management-function" }, { "level": 3, "title": "Enterprise Control", "id": "enterprise-control" }, { "level": 3, "title": "Search module overview", "id": "search-module-overview" }, { "level": 3, "title": "Search with permission judgment", "id": "search-with-permission-judgment" }, { "level": 3, "title": "Technical basis", "id": "technical-basis" }, { "level": 3, "title": "Search function", "id": "search-function" }, { "level": 3, "title": "Performance optimization", "id": "performance-optimization" }, { "level": 3, "title": "Future development", "id": "future-development" } ], "images": [], "text": "Version management File version generation, rollback, download, preview, comparison, logging and ransomware protection. Detailed description Version Management Overview Version management is one of the important functions of BabelBird Enterprise Drive. It allows users to track and manage different versions of files, ensuring that file history and updates can be retained and viewed. Babel's version management function is very powerful and supports multiple update methods as well as version rollback and viewing. Technical implementation Version management uses file blocking and incremental saving techniques to store file versions. This means that each change to a file generates a new version that stores only the changed data blocks, reducing storage requirements and increasing efficiency. Enterprise administrators can set the number and storage time of file versions in the enterprise console to control version management policies. The version management feature enables users to flexibly manage file versions to ensure file integrity, history, and security. Version management is a core function of BabelBird Enterprise Drive, aiming to provide excellent user experience and data security. Version update method Babel allows users to update file versions in a variety of ways, including: Manually upload new version: Users can right click the file and select Upload New Version to manually upload the new file and save it as a new version of the file. Detection of files with the same name: When uploading, Babel can detect files with the same file name, and users can choose to upload the new file as a new version of the existing file. Client editing and saving: If a user edits a file using the client and saves it, Babel will save the changes as a new version of the file. Online editing and saving: If the user edits the file using the online editing function on the web page and saves it, a new version will also be generated. Sync folder editing: The Babel client will monitor the synchronized folder for updates. Editing or overwriting files in the synchronized folder and saving them will generate a new version. Map disk editing: Edit the file in the mapped disk and save it. The updated file will also be saved as a new version. Version management function The Babel version management module has the following functions: Version rollback: In the file version list, users can choose to set the old version as the current version to implement version rollback. Version download: Users can choose to download version history to access previous file versions. Version preview: The version management module allows users to preview an old version of a file when clicking on it to see the content of that version. Version comparison: When previewing files in the Babel Previewer, you can select the file comparison function, which supports selecting old and new versions for comparison. Version log: Users can add logs to each file version to record important information and change history of the version. Enterprise Control The version management function of BabelBird Enterprise Drive allows enterprise administrators to make advanced settings in the enterprise console to meet the specific needs of the enterprise. Enterprise administrators can set the number and retention time of file versions based on company policies and compliance requirements to meet the needs of different file types and departments. Such a version management system ensures the data consistency and traceability of files, as well as the integrity of user data. At the same time, it has strong protection against viruses such as ransomware that change the readability of files, because ransomware changes files and requires updated files, and the updated files will form a new version. Users only need to roll back the version to get the files before the attack. Search Search module overview The search module of BabelBird Enterprise Drive is a key function. It is developed based on powerful Elasticsearch technology and database query technology, and is designed to provide efficient, accurate and comprehensive document search functions. The search module not only supports full text search, but also searches the description, comments and file names of documents to meet the search needs of different users. Search with permission judgment Babel's search module not only has a powerful search function, but also uses advanced permission management technology to dynamically determine user permissions to ensure that users can only see files within their permissions. The search results are dynamically generated based on the user's permissions, which means that among the files shared by the user, only the files that the user has permission to view will be searched. This is a critical technology, especially in enterprise environments where permissions can change at any time. Technical basis Elasticsearch: Elasticsearch is an open source search engine known for its efficient distributed architecture and powerful full text search capabilities. Babel uses Elasticsearch as its core search engine to support full text search and advanced query capabilities. Database query: In addition to Elasticsearch, the search module also utilizes database query technology to search the metadata and tag information of documents to provide more comprehensive search results. Document analysis: The search module uses text extraction technology to extract text information from various types of files. This extracted text information is used for search engine indexing and querying. Keyword extraction. Word segmentation optimization: BabelBird has done a lot of word segmentation optimization work, especially for Chinese vocabulary, to improve the word segmentation accuracy and performance of search engines. The optimization of Chinese word segmentation plays a key role in the accuracy of search results. Search function The Babel search module includes the following main functions: Full text search: Users can perform full text searches to find textual content within documents to find files related to keywords. Document description and comment search: The search module supports searching for descriptions and comments added to Babel documents by users, making it easier for users to find specific information. File name search: Users can perform precise file name searches to find specific files. Tag search: Tag search, query, and classification display are available Advanced search BabelBird supports advanced search function, which can conduct advanced search based on keywords, full text content, time, file format, uploader, search scope, search type and other dimensions. Performance optimization The search module has high requirements on server performance. Therefore, for users with private deployment, it is recommended to deploy the search module on an independent virtual machine or server to reduce the performance consumption of other modules. Future development Future versions of Babel will continue to improve the search module and combine AI technology, such as ChatGPT, to implement question and answer chat dialogue search of document content, providing users with a more intelligent search experience. At present, the AI based document analysis and customer service system \"Zhichao AI\" has been launched. For details, please refer to the Zhichao AI chapter. The continuous improvement of the search module will help users find the files and information they need more quickly and accurately. After the introduction of the AI ​​system, users can obtain information in the form of questions and answers, and can cross the contents of multiple documents to draw complete conclusions, which can greatly improve production efficiency and work efficiency." }, { "lang": "en", "slug": "search-preview", "title": "search", "description": "Full text search, tags, descriptions, comments, file names, advanced search and search with permission judgment.", "category": "Product Features", "top_category": "使用指南", "keywords": [ "File Management", "search", "BabelBird" ], "url": "en/search-preview.html", "source": "content/en/search-preview.md", "summary": "Search Full text search, tags, descriptions, comments, file names, advanced search and search with permission judgment. Detailed description BabelBird also supports full text search, which can search for keywords in the file content. You can also use file name search and tag search to find the corresponding file. The search results can be searched again or filtered by filtering Filter function: You can filter based on file tags, types, file description keywords, size, version, uploader, photo metadata, etc. to quickly locate the required files. File tags and categories: Users can tag files to better organize and categorize them. Labels can be managed uniformly by the enterprise to ensure tha", "headings": [ { "level": 1, "title": "Search", "id": "search" }, { "level": 2, "title": "Detailed description", "id": "detailed-description" }, { "level": 3, "title": "Common file management functions", "id": "common-file-management-functions" } ], "images": [], "text": "Search Full text search, tags, descriptions, comments, file names, advanced search and search with permission judgment. Detailed description BabelBird also supports full text search, which can search for keywords in the file content. You can also use file name search and tag search to find the corresponding file. The search results can be searched again or filtered by filtering Filter function: You can filter based on file tags, types, file description keywords, size, version, uploader, photo metadata, etc. to quickly locate the required files. File tags and categories: Users can tag files to better organize and categorize them. Labels can be managed uniformly by the enterprise to ensure that labels comply with specifications. Tag shortcuts can be added to the left column. Common file management functions A. File transfer and operations Upload and download files: Users can upload and download files, ensuring flexible transfer of data. Supports dragging and uploading folders to facilitate the transfer of large batches of files. The browser supports folder packaging download (less than 100 files or folders less than 500MB in size) The client supports direct download of folders (transfer list) Creation of files and folders: Users can create new files and folders of various types, and also support creating new files or folders from templates to improve work efficiency. File copy and move: Users can copy and move files or folders to organize files easily. Supports copying files or folders to specified directories for file backup and management. Document archiving: Users can archive documents into an archive for long term preservation and retrieval. File pinned to top: Personal files support pinning files or folders to the top for quick access to important files. Department or project administrators can pin portal files or project files to facilitate department members and project members to quickly access important files. Create file or folder shortcuts: Users can create shortcuts to files or folders for quick access. Upload new version: Users can upload a new version of a file, and the system will automatically detect files with duplicate names and provide the option of uploading a new version or renaming the file. Click the Upload new version button to directly upload a new version. Print files as watermarked PDF: When watermarking is turned on, the file can be printed as a watermarked PDF file to ensure the security and confidentiality of the file. Lock files: When files are edited using the client, they are automatically locked to prevent conflicts. Users can also manually lock files in the file list to prevent editing and conflicts by other users. File preview: Supports preview of most files to quickly view file contents. To learn more, check out the Preview and Transcoding chapter. File list display thumbnails: The file management module can display thumbnails of files in the file list, making file browsing more intuitive. Batch file upload and download: BabelBird provides a client specific upload and download module, which supports the upload and download of batch files, and also provides a list display of transferred files. View file details and version management: BabelBird has a dedicated file details interface. In the file details, you can add file descriptions, view basic file information, and view metadata for image files. You can also view file logs, file access and usage, and manage file versions in the details. B. File security and permission control File access control: Department administrators or project administrators can set file access control to precisely control the access permissions of each file or folder for each user or a certain role. File access control takes precedence over members' department role permissions. For example, if a department member role has editing permissions on a certain file, but the department administrator uses file access control to change the member's permissions on the file to \"invisible\", the member will not be able to access the file. File sharing: Supports sharing files and folders, allowing users to set detailed access permissions to control file access. File snapshot sharing: For those who only want to share the current version, users can create a snapshot share of the file. The snapshot share will not be changed by updates to the file content and will maintain the version when the snapshot was created." }, { "lang": "en", "slug": "file-sharing", "title": "Share and send out", "description": "Invitation sharing, link sharing, snapshot sharing, outgoing, sharing logs and corporate strategies.", "category": "Product Features", "top_category": "使用指南", "keywords": [ "File Management", "Share and send out", "BabelBird" ], "url": "en/file-sharing.html", "source": "content/en/file-sharing.md", "summary": "Share and send out Invitation sharing, link sharing, snapshot sharing, outgoing, sharing logs and corporate strategies. Detailed description Sharing function BabelBird Enterprise Drive provides a variety of flexible sharing methods, including invitation sharing and link sharing, to meet the different needs of users. Invite to share: Invite sharing is a way to share a file or folder with specific people. Features are as follows: Identity verification: Invitees need to undergo identity verification. They can log in through their Babel account or receive a verification code to confirm their identity. Each invitee can independently manage permissions and set the permission validity period. This ", "headings": [ { "level": 1, "title": "Share and send out", "id": "share-and-send-out" }, { "level": 2, "title": "Detailed description", "id": "detailed-description" }, { "level": 3, "title": "Sharing function", "id": "sharing-function" }, { "level": 3, "title": "Outbound function (send files)", "id": "outbound-function-send-files" }, { "level": 3, "title": "User Controls and Enterprise Policies", "id": "user-controls-and-enterprise-policies" }, { "level": 3, "title": "Flexibility and convenience", "id": "flexibility-and-convenience" } ], "images": [], "text": "Share and send out Invitation sharing, link sharing, snapshot sharing, outgoing, sharing logs and corporate strategies. Detailed description Sharing function BabelBird Enterprise Drive provides a variety of flexible sharing methods, including invitation sharing and link sharing, to meet the different needs of users. Invite to share: Invite sharing is a way to share a file or folder with specific people. Features are as follows: Identity verification: Invitees need to undergo identity verification. They can log in through their Babel account or receive a verification code to confirm their identity. Each invitee can independently manage permissions and set the permission validity period. This means that for the same invitation sharing, different invitees can set different access rights. Permission control: Sharers can customize sharing permissions, including viewing, editing, downloading, etc. This helps to provide granular control over what is shared. Approval mechanism: If the user does not have sharing permissions, the sharing operation needs to be approved to ensure that only authorized personnel can share files. Link sharing: Link sharing allows users to create a public link for others to access a file or folder. Features are as follows: Allow anonymous access: Sharers can choose whether to allow anonymous access. If the anonymous access option is turned off, visitors will need to have a Babel account to access. Snapshot sharing: In snapshot sharing mode, the content shared is the current version at the time of sharing. Even if the file content is updated, the content shared by the snapshot will not change. Password protection: Users can set a password to ensure that only those who know the password can access the shared link. Validity period: Link sharing can set a validity period to ensure that the file will not be made public permanently. Once the validity period expires, the shared link will automatically expire. Custom settings: In the enterprise console, administrators can customize sharing permissions, set sharing behavior by department (support or prohibit sharing), set sharing rules by file (prohibit sharing of high confidence files), and turn off the external sharing function of the entire enterprise. Share log: All sharing behaviors and external access behaviors have independent logs, and each shared access log can be queried. You can know who accessed a shared file or folder when, and updated versions of shared files will alert users. Unified management and sharing: Department administrators can uniformly view and manage all shared files in the entire department. Shared personal files can also be uniformly viewed and managed in the \"My Shared Files\" column to ensure that no omitted shares will be leaked without knowledge. Outbound function (send files) The outgoing function is a way to send files to other users via email or mobile phone number for direct downloading. Outgoing is different from sharing. It is only used for the recipient to download outgoing files without configuring permissions. Features are as follows: Send files: Users can use the outgoing function to send files to other users' email addresses or mobile phone numbers so that they can download and use them directly. The file sending function can also send files to internal users. There will be a notification when the file is received. Click the notification to download or transfer the file. No permissions required: Outsourcing does not require configuration permissions and can be used as long as the user has sharing and download permissions. Email or SMS sending: Outsourcing can send file links via email or SMS to ensure that the recipient can easily obtain the files. Quick download: The recipient can directly download the file by clicking on the link, which is simple and convenient. User Controls and Enterprise Policies Users' sharing permissions can be controlled by enterprise administrators to ensure that file sharing and outgoing files are strictly managed. In addition, enterprise administrators can also customize sharing rules and permissions through the enterprise console to adapt to different enterprise needs. Security Sharing and outgoing functions are subject to strict security controls to protect corporate files from being accessed by unauthorized personnel. Administrators can flexibly configure sharing and outgoing permissions and rules according to the enterprise's security policy. Flexibility and convenience Sharing and outsourcing functions provide enterprises with flexibility and convenience, meeting the needs of different users and scenarios. Users can choose the most suitable sharing method according to specific situations to better manage and share files." }, { "lang": "en", "slug": "preview-annotation-review", "title": "Preview, annotate and review", "description": "BabelViewer, annotation, hand drawing, voice annotation, version comparison and review collaboration.", "category": "Product Features", "top_category": "使用指南", "keywords": [ "File Management", "Preview, annotate and review", "BabelBird" ], "url": "en/preview-annotation-review.html", "source": "content/en/preview-annotation-review.md", "summary": "Preview, annotate and review BabelViewer, annotation, hand drawing, voice annotation, version comparison and review collaboration. For details on supported preview formats, transcoding mechanisms, and preview queuing, see White Paper: Preview and Transcoding. Detailed description In order to allow users to more conveniently preview files and conduct collaborative discussions while previewing files to improve collaboration efficiency, Babel has developed BabelViewer. Most file formats that can be previewed on Babel can be opened with the previewer. Babel Previewer can not only preview files, but also communicate with collaborators on file content through hand drawing, text discussion, voice (", "headings": [ { "level": 1, "title": "Preview, annotate and review", "id": "preview-annotate-and-review" }, { "level": 2, "title": "Detailed description", "id": "detailed-description" }, { "level": 3, "title": "Technical architecture", "id": "technical-architecture" }, { "level": 3, "title": "Applicable file types", "id": "applicable-file-types" }, { "level": 3, "title": "Previewer type", "id": "previewer-type" }, { "level": 3, "title": "Comment type", "id": "comment-type" }, { "level": 3, "title": "Function module", "id": "function-module" } ], "images": [], "text": "Preview, annotate and review BabelViewer, annotation, hand drawing, voice annotation, version comparison and review collaboration. For details on supported preview formats, transcoding mechanisms, and preview queuing, see White Paper: Preview and Transcoding. Detailed description In order to allow users to more conveniently preview files and conduct collaborative discussions while previewing files to improve collaboration efficiency, Babel has developed BabelViewer. Most file formats that can be previewed on Babel can be opened with the previewer. Babel Previewer can not only preview files, but also communicate with collaborators on file content through hand drawing, text discussion, voice (only mobile APP supports the creation of voice annotations) and other methods. At the same time, BabelBird Previewer also supports version comparison, switching versions to view different version annotations, annotation management, approval management and other functions. Technical architecture Use canvas development and multi layer technology The previewer is developed based on Html5 Canvas technology and uses multi layer technology to add annotation and hand drawing layers on top of the file preview layer. It does not affect the file content but allows for annotation discussion and real time hand drawing. Real time collaboration module The real time collaboration module of the previewer ensures that the annotation discussions and hand drawings of multiple users are displayed in real time when previewing files, which means that users can discuss issues with documents or design manuscripts while annotating. Annotation point coordinate system positioning The Babel previewer uses coordinate system positioning to ensure that the annotation points are in the same position under different resolution screens and different browser sizes. Applicable file types BabelBird Previewer can open most pictures and office documents, PDF documents and vector graphics files. For specific supported file types, please refer to the File Types Supported for Online Preview in the Preview and Transcoding chapter. Previewer type Multi page document previewer Supports preview of multi page documents, such as word, PPT, PDF and other formats. For multi page documents, it provides functions such as table of contents, zooming in, and page rotation that are suitable for multi page documents. Image previewer Designed for better preview images. It has functions such as eagle eye, zoom in and out, display original proportion, rotation, etc. Right click to copy the image to the clipboard, making it easy to paste the image directly in WeChat or email. For images with transparency such as PNG, you can change the image background. Graphic previewer Designed to preview vector graphic files such as CAD, SVG, single page PDF, etc., it supports eagle eye, layered display, background change, mouse dragging area enlargement, and vector enlargement. You can switch the encoding mode for SVG files. 3D previewer In order to preview the 3D file design, you can rotate, zoom in and out the 3D file with the mouse wheel, explode the image, and support annotation in 3D space. Comment type Text discussion area Text discussion areas can be created in any area of the preview file (double click to create text discussion comments). Collaborators of the file who have permission to view comments can see the comments and participate in the discussion. The annotation content is displayed in real time, and a text annotation discussion area is equivalent to a group chat for the annotation content. Supports inserting attachments for discussion, and also supports @ and other chat functions. You can set the visibility of comments, such as: only visible to company members, visible to everyone, and only visible to the commenter himself. Text annotation Text annotation can add annotations to document content or photos. Selected text annotation For documents with text, such as word and PDF, you can select a piece of text for annotation. Special symbol insertion For manuscripts with special needs, revision symbols or welding marks (such as CAD drawings) can be inserted Create graphic annotations It also supports the use of graphic frame selection annotations, supporting rectangles, ellipses and arrows. Voice annotation The Babel mobile device APP can create voice annotations. Voice annotations can be viewed (listened to) on web pages and clients, but cannot be created. Hand drawn annotations Supports real time drawing on manuscripts or documents. Participants can see the drawn lines in real time and mark the artist's nickname. Function module Comment management module You can manage created comments and comment status, check other versions of comments, and switch to the corresponding version Review workspace Babel can use comments during document review and display review related panels, allowing reviewers to convey review information more accurately and conveniently. Eagle Eye Eagle Eye can display the area of the image viewport when the image is zoomed in. Version comparison Babel Previewer supports file comparison function and can also compare different versions of files. File directory For files with directories (word, pdf), BabelBird also supports displaying the file directory during preview." }, { "lang": "en", "slug": "file-review", "title": "Document review", "description": "Multiple document reviews, approval processes, external reviews, reports and signatures.", "category": "Product Features", "top_category": "使用指南", "keywords": [ "File Management", "Document review", "BabelBird" ], "url": "en/file-review.html", "source": "content/en/file-review.md", "summary": "File review Multiple document reviews, approval processes, external reviews, reports and signatures. Detailed description BabelBird Enterprise Drive provides a powerful document review function, designed to help users efficiently manage the document approval and revision process. Document review is a collaborative work process that allows users to initiate a document review, invite reviewers to view the document, provide comments and suggestions, and ultimately determine whether the document requires modification or approval. Main features Multi document review: Supports review of multiple documents at the same time. Users can initiate review of multiple documents at one time to ensure an ef", "headings": [ { "level": 1, "title": "File review", "id": "file-review" }, { "level": 2, "title": "Detailed description", "id": "detailed-description" }, { "level": 3, "title": "Main features", "id": "main-features" }, { "level": 3, "title": "Technical architecture", "id": "technical-architecture" }, { "level": 3, "title": "Advantages of document review", "id": "advantages-of-document-review" } ], "images": [], "text": "File review Multiple document reviews, approval processes, external reviews, reports and signatures. Detailed description BabelBird Enterprise Drive provides a powerful document review function, designed to help users efficiently manage the document approval and revision process. Document review is a collaborative work process that allows users to initiate a document review, invite reviewers to view the document, provide comments and suggestions, and ultimately determine whether the document requires modification or approval. Main features Multi document review: Supports review of multiple documents at the same time. Users can initiate review of multiple documents at one time to ensure an efficient review and approval process. File Lock: Files will be automatically locked during the review process to prevent other users from editing or uploading new versions, ensuring that the file content will not be changed during the review process. File preview and comments: Reviewers can add comments and fill in review comments when previewing the file to provide detailed feedback. This helps to better understand the file content and provide targeted recommendations. Review process: Users can choose different review processes, including freely defining the review process, using a preset review process, or restricting the use of specific review processes. This allows different departments to choose the appropriate approval process based on their needs. Multi stage approval: The approval process supports multiple stages, and one or more approvers can be set for each stage. Users can define a pass ratio, for example, if 50% of approvers pass, a certain stage can be passed. Invite external reviewers: Users can invite external members (via email or mobile phone number) to participate in document review to obtain more feedback from different perspectives, such as inviting external experts during thesis defense. Approval report: After each document review, an approval report will be generated to record the review opinions of participants at each stage for tracking and analysis of the approval results. Review signature: supports inserting a signature on the manuscript after the review is completed and downloading it as a PDF. My Review Column: Users can view and manage all stages of all review documents related to themselves in the \"My Review\" column, including initiated reviews and invited reviews. Technical architecture The implementation of the document review function involves the following technologies and modules: Review process definition: Different review processes are defined in the background, including stage setting, approver selection, passing ratio setting, etc. These processes are available to front end users for selection. Department specific approval processes: Different departments can choose different approval processes and choose to freely define, preset or limit specific approval processes as needed. Multi stage approval: Multi stage approval can be achieved, and each stage has different approval requirements, including the selection of approvers and the passing ratio. You can also set whether a certain stage can be skipped. Invitation of external approvers: Supports inviting external members to participate in document review, and invites via email or mobile phone number. Approval reports: Generate approval reports to record review opinions at each stage for tracking and analysis of approval results. Advantages of document review The document review function helps users efficiently manage the document approval and revision process to ensure the accuracy and compliance of document content. Users can use document reviews to ensure documents have been adequately reviewed and discussed to meet their work needs and compliance requirements. The introduction of this feature increases the depth of file collaboration and management, providing users with more powerful file collaboration tools." }, { "lang": "en", "slug": "archive-library", "title": "Archives", "description": "Archiving, reading room, lending, long-term preservation and archive search.", "category": "Product Features", "top_category": "使用指南", "keywords": [ "File Management", "Archives", "BabelBird" ], "url": "en/archive-library.html", "source": "content/en/archive-library.md", "summary": "Archives Archiving, reading room, lending, long term preservation and archive search. Detailed description BabelBird Enterprise Drive provides a powerful file management module for unified management and archiving of enterprise files. This module is designed to help businesses better organize and retain critical files while ensuring they are secure and accessible. Main features Archivist: Babel allows the super administrator to designate one or more company members as archivists. Archivists are responsible for managing archived documents and archives. Archive: Archived files are stored in the root directory of the archive. Archives are corporate libraries of materials used to retain and mana", "headings": [ { "level": 1, "title": "Archives", "id": "archives" }, { "level": 2, "title": "Detailed description", "id": "detailed-description" }, { "level": 3, "title": "Main features", "id": "main-features" }, { "level": 3, "title": "Technical architecture", "id": "technical-architecture" }, { "level": 3, "title": "Advantages of file management", "id": "advantages-of-file-management" } ], "images": [], "text": "Archives Archiving, reading room, lending, long term preservation and archive search. Detailed description BabelBird Enterprise Drive provides a powerful file management module for unified management and archiving of enterprise files. This module is designed to help businesses better organize and retain critical files while ensuring they are secure and accessible. Main features Archivist: Babel allows the super administrator to designate one or more company members as archivists. Archivists are responsible for managing archived documents and archives. Archive: Archived files are stored in the root directory of the archive. Archives are corporate libraries of materials used to retain and manage documents over the long term. Reading room: Archivists can create a reading room and move files from the root directory of the archive into the reading room. Only then can other company members borrow these documents. Borrowing permissions: The reading room can choose different borrowing methods, including public, borrowing required, open to departments only, borrowing within departments only, etc. When borrowing a file, you can set the permission level, such as reading only, copying, downloading, and specify the borrowing time. File archiving: Archived files cannot be changed, ensuring the integrity and credibility of the files. This is important for long term retention of legal and compliance documents. Archive search: The archive has an independent search function, and only files in the archive will be searched. Users can quickly find the archive files they need. File privacy: Non public files without borrowing permission will not display preview images to ensure file privacy. Technical architecture The Archives Management module uses the following key technologies and modules: Archive administrator permissions: Super administrators can designate company members as archive administrators, allowing them to manage archives and reading rooms. Reading Room Settings: Archivists can create reading rooms and configure different borrowing permissions and accessibility options. Archiving and retention: Once a document is archived, it needs to ensure that its contents cannot be changed. This requires technical measures to protect file integrity. Independent search: The archive has an independent search engine for searching files in the archive to ensure that users can quickly find the files they need. Advantages of file management The archive management module helps enterprises better manage the archiving and retention of documents. Through archives, reading rooms, and different borrowing permissions, enterprises can ensure that documents are retained long term, managed in an orderly manner, and can meet compliance and legal requirements. This module can also be used as a knowledge base to help enterprises save important information and knowledge." }, { "lang": "en", "slug": "logs-reports", "title": "Logs and reports", "description": "File logs, access statistics, department reports, enterprise logs and statistical analysis.", "category": "Product Features", "top_category": "使用指南", "keywords": [ "File Management", "Logs and reports", "BabelBird" ], "url": "en/logs-reports.html", "source": "content/en/logs-reports.md", "summary": "Logs and reports File logs, access statistics, department reports, enterprise logs and statistical analysis. Detailed description The log and report system of BabelBird Enterprise Drive provides comprehensive file usage management, monitoring, auditing and accountability functions. This module is designed to provide business managers and users with insights into file activity, access, and system usage to support compliance and security requirements. Main features File log: Each file and folder has an independent log, which records various operations in the life cycle of the file in detail, including creation, reading, modification, renaming, sharing, deletion, permission changes, etc. This e", "headings": [ { "level": 1, "title": "Logs and reports", "id": "logs-and-reports" }, { "level": 2, "title": "Detailed description", "id": "detailed-description" }, { "level": 3, "title": "Main features", "id": "main-features" }, { "level": 3, "title": "Technical architecture", "id": "technical-architecture" }, { "level": 3, "title": "Advantages of logs and reports", "id": "advantages-of-logs-and-reports" } ], "images": [], "text": "Logs and reports File logs, access statistics, department reports, enterprise logs and statistical analysis. Detailed description The log and report system of BabelBird Enterprise Drive provides comprehensive file usage management, monitoring, auditing and accountability functions. This module is designed to provide business managers and users with insights into file activity, access, and system usage to support compliance and security requirements. Main features File log: Each file and folder has an independent log, which records various operations in the life cycle of the file in detail, including creation, reading, modification, renaming, sharing, deletion, permission changes, etc. This even includes anonymous sharing operations and the IP address of the visitor. These logs can be exported as Excel reports for auditing and monitoring. File access statistics: The file details page provides statistics on the number of file comments, downloads, opens, number of visitors, and visitors. Folder list: You can export the list of files and sub files in the folder as an EXCEl file for auditing and management. Document Review Record Report: Document review operations are also recorded as reports to support auditing of document reviews. Department logs and reports: Department administrators can view the usage logs of the entire department, including detailed file access logs, statistics on the number of uploaded files, the number of sub departments created, or the number of projects. In addition, department administrators can count and manage files shared by the entire department and files with changed permissions. Enterprise level management: Enterprise administrators and security auditors can view the usage behavior of the entire enterprise, including logs and reports of various departments, and there are also two columns, access logs and statistical analysis, to uniformly view and manage the usage behavior of the entire enterprise. This helps maintain corporate compliance and security. Access log: The access log records the usage log of the entire enterprise network disk, including every operation of the user on the network disk. Administrators can conduct detailed queries and export reports. Statistical analysis: Provides statistical analysis chart tools, allowing administrators to view the usage activity of different departments, the number of files, the ranking of active files, statistics of new files, statistics of the number of uploaded files, and traffic usage statistics. Technical architecture Logging: The system needs to record detailed logs of each operation, including operation type, timestamp, executor, target file, IP address and other information. Report generation: Administrators are able to generate reports from log data, usually in Excel format, for auditing and monitoring. Data analysis tools: Statistical analysis tools are used to analyze and visualize data to help administrators better understand system usage. Log interface: Babel supports exporting log data through the interface to use third party log management and analysis tools. Advantages of logs and reports Logging and reporting systems help enterprises achieve the following goals: Compliance: Help enterprises comply with regulations and internal policies and ensure compliance of document operations. Security Auditing: Provides auditing capabilities that allow enterprises to inspect and monitor file access and operations to identify potential risks. Performance optimization: Through statistical analysis, it helps enterprises understand the performance bottlenecks of the system and take appropriate improvement measures. User behavior monitoring: allows business managers to understand employee behavior, including file access and operations, to ensure data security and confidentiality. Decision support: Help business managers make more informed decisions through data analysis, including resource allocation and document management. The log and report system is an important part of BabelBird Enterprise Drive, which provides comprehensive file usage management and monitoring functions to support the compliance and security needs of enterprises." }, { "lang": "en", "slug": "activity-notification", "title": "Updates and notifications", "description": "Dynamic feeds, notification types, notification settings, and collaboration reminders.", "category": "Product Features", "top_category": "使用指南", "keywords": [ "File Management", "Updates and notifications", "BabelBird" ], "url": "en/activity-notification.html", "source": "content/en/activity-notification.md", "summary": "Dynamics and notifications Dynamic feeds, notification types, notification settings, and collaboration reminders. Detailed description Dynamic column Overview: The dynamic column of BabelBird Enterprise Drive is an information flow used to display files and user dynamic information related to you. It provides a real time overview of your work and helps you track your colleagues' activities, including file changes, annotations, comments, etc. Real time information flow: The dynamic column presents the collaborative activities of you and your team in the form of real time information flow, helping you to understand what is happening in the team in a timely manner. Convenient interaction: Throu", "headings": [ { "level": 1, "title": "Dynamics and notifications", "id": "dynamics-and-notifications" }, { "level": 2, "title": "Detailed description", "id": "detailed-description" }, { "level": 3, "title": "Dynamic column", "id": "dynamic-column" }, { "level": 3, "title": "Notification section", "id": "notification-section" }, { "level": 3, "title": "Personalization", "id": "personalization" }, { "level": 3, "title": "Application scenarios", "id": "application-scenarios" } ], "images": [], "text": "Dynamics and notifications Dynamic feeds, notification types, notification settings, and collaboration reminders. Detailed description Dynamic column Overview: The dynamic column of BabelBird Enterprise Drive is an information flow used to display files and user dynamic information related to you. It provides a real time overview of your work and helps you track your colleagues' activities, including file changes, annotations, comments, etc. Real time information flow: The dynamic column presents the collaborative activities of you and your team in the form of real time information flow, helping you to understand what is happening in the team in a timely manner. Convenient interaction: Through the dynamic column, you can directly access files related to you, reply to comments, interact with colleagues, and complete collaboration tasks in a more convenient way. Dynamic search: You can search dynamic historical content and locate related dynamic items more accurately. Notification section Notification system: The notification system of BabelBird Enterprise Drive is used to send various reminders and notifications related to you. These notifications can be communicated to you in a variety of ways, including email notifications, mobile application notifications, desktop notifications, etc. Notification types: The notification system covers a variety of notification types, such as @mentions of you, file update notifications, approval requests, file authorization requests, etc. This helps you stay on top of your various workflows. Personalization Information type settings: Users can customize which updates and notification types they receive in the settings according to their own needs to ensure that the information is accurate and targeted. Application scenarios The dynamic column and notification column help users understand important developments and notifications at work, improve collaboration efficiency, and enable users to respond more quickly to colleagues' collaboration requests, reply to comments, and track file changes. The dynamic and notification columns of BabelBird Enterprise Drive are key collaboration tools. They provide a real time overview of collaboration and various notifications, allowing users to collaborate with their teams more effectively and maintain an understanding of the work process. These features help improve collaboration efficiency and ensure important information is not overlooked." }, { "lang": "en", "slug": "discussion-workbench", "title": "Discussion groups and workbench", "description": "Department/Project Discussion Groups and Personalized Workbench.", "category": "Product Features", "top_category": "使用指南", "keywords": [ "File Management", "Discussion groups and workbench", "BabelBird" ], "url": "en/discussion-workbench.html", "source": "content/en/discussion-workbench.md", "summary": "Discussion groups and workbench Department/Project Discussion Groups and Personalized Workbench. Detailed description Overview Discussion group function: BabelBird Enterprise Drive creates discussion groups for each department and project, which serve as a group chat space for internal members of the department or project. Discussion groups allow members to post text and images, conduct discussions, and share attachments. Member interaction: The discussion group provides a convenient platform for members to communicate, collaborate and discuss project related matters with each other, thereby enhancing teamwork and information sharing. Main functions Information publishing: Discussion group m", "headings": [ { "level": 1, "title": "Discussion groups and workbench", "id": "discussion-groups-and-workbench" }, { "level": 2, "title": "Detailed description", "id": "detailed-description" }, { "level": 3, "title": "Overview", "id": "overview" }, { "level": 3, "title": "Main functions", "id": "main-functions" }, { "level": 3, "title": "Application scenarios", "id": "application-scenarios" }, { "level": 3, "title": "Summary", "id": "summary" } ], "images": [], "text": "Discussion groups and workbench Department/Project Discussion Groups and Personalized Workbench. Detailed description Overview Discussion group function: BabelBird Enterprise Drive creates discussion groups for each department and project, which serve as a group chat space for internal members of the department or project. Discussion groups allow members to post text and images, conduct discussions, and share attachments. Member interaction: The discussion group provides a convenient platform for members to communicate, collaborate and discuss project related matters with each other, thereby enhancing teamwork and information sharing. Main functions Information publishing: Discussion group members can publish text messages and pictures to achieve real time discussion and communication. Attachment sharing: Members can easily share attachments such as documents, forms, and other files for sharing and discussion. Visibility: Information posted in the discussion group is visible to all members of the department or project to which it belongs, ensuring information sharing. Application scenarios Discussion groups are suitable for information exchange and discussion within departments and between project teams. They facilitate real time collaboration and help solve problems, share insights, and track progress. Summary Discussion groups provide a convenient collaboration platform for department and project members to share information, discuss matters, and work together. These discussion groups help enhance internal communication and increase the efficiency and productivity of your team." }, { "lang": "en", "slug": "admin-console", "title": "Enterprise console", "description": "Enterprise configuration, organizational structure, permissions, members, labels, watermarks, logs, IP policies and module management.", "category": "Product Features", "top_category": "使用指南", "keywords": [ "File Management", "Enterprise console", "BabelBird" ], "url": "en/admin-console.html", "source": "content/en/admin-console.md", "summary": "Enterprise Console Enterprise configuration, organizational structure, permissions, members, labels, watermarks, logs, IP policies and module management. Detailed description The BabelBird Enterprise Console centralizes the administrator's functions for managing the entire enterprise. Enterprise administrators can configure various options of the enterprise network disk in the enterprise console, turn on or off the required functional modules, set the organizational structure, customize roles and permissions, manage members, set watermarks, set department security policies, IP access policies, bind accounts and mac addresses, monitor network disk usage... Main columns Enterprise configuratio", "headings": [ { "level": 1, "title": "Enterprise Console", "id": "enterprise-console" }, { "level": 2, "title": "Detailed description", "id": "detailed-description" }, { "level": 3, "title": "Main columns", "id": "main-columns" } ], "images": [], "text": "Enterprise Console Enterprise configuration, organizational structure, permissions, members, labels, watermarks, logs, IP policies and module management. Detailed description The BabelBird Enterprise Console centralizes the administrator's functions for managing the entire enterprise. Enterprise administrators can configure various options of the enterprise network disk in the enterprise console, turn on or off the required functional modules, set the organizational structure, customize roles and permissions, manage members, set watermarks, set department security policies, IP access policies, bind accounts and mac addresses, monitor network disk usage... Main columns Enterprise configuration: Comprehensive management of enterprise network disk configuration items, such as space allocation, whether personal files are allowed, allowed file upload size, historical version validity period or number of historical versions, various administrator assignments, changing logo and login background, prohibiting or enabling external sharing, and whether to accept email notifications. Various enterprise configuration options can be found in the enterprise configuration column. Organizational structure: Unified management and maintenance of the enterprise's organizational structure and departments. Ability to view departments and management departments in a tree view. View department members, allocate department space, create sub departments, set department security policies... Permission management: Create roles and change role permissions, and manage custom file permissions. Member management: You can search and filter the member accounts of the entire enterprise, add new members, import members in batches, assign member departments and roles, view and manage the information and usage of each member in detail, handover when members leave, add, delete, modify and check member accounts, allocate and limit member space and traffic. Tag management: unified management of tags used by enterprises, adding tags and classifying tags to facilitate users to select tags. File configuration: Add an optional process for file approval and manage the already added approval process. It also has a file blacklist function that can prevent specific types of files from being uploaded. Corporate notifications: Create corporate notifications, manage historical corporate notification lists, and send corporate notifications. Group management: Create and manage groups. When sharing files in the frontend, you can choose which group to share them with. Watermark settings: manage document watermark types, adjust watermark parameters, and set watermark display range. Access log: Manage and query all access records of the entire enterprise network disk. Log reports can be exported. IP policy list: The upload and download behavior of corporate files can be managed through IP policies. For example: downloading files is prohibited in a certain IP range, and you can download files by returning to a certain IP range. Mac address binding: You can bind the user account to the mac address of a specific device, so that the account can only be used on the device bound to the mac address. You can also create a mac address pool. Statistical analysis: Statistically analyze the usage of network disk. Including system activity, file number statistics, active files, number of new files within a period of time, number of uploads per month, and traffic usage. Workbench push: Set the default display card of the workbench. System configuration (private deployment version only): configure the mail server, bind third party SSO authentication, and set the third party authentication login method. Third party account synchronization (private deployment version only): Set the third party account synchronization time and query the third party account synchronization record. Optional modules (private deployment version only): Select the functional modules that the enterprise needs to display and turn off some functional modules. Monitoring and warning: Set warnings for abnormal behavior, and notify administrators when abnormal behavior occurs (for example: users delete files in large numbers) Transfer file configuration: The configuration of the data ferry system allows data ferrying between multiple sets of BabelBirds. Configure the receiving port and sending port of data." }, { "lang": "en", "slug": "material-library", "title": "Material library", "description": "Introduces the enterprise material library, material classification, sub-material library, waterfall flow display, permission control, search filtering and AI image search collaboration.", "category": "Product Features", "top_category": "使用指南", "keywords": [ "Material library", "waterfall flow", "Picture material", "AI image search", "Material library API" ], "url": "en/material-library.html", "source": "content/en/material-library.md", "summary": "material library The material library is Babel's centralized management capability for pictures, brand assets, design materials, drawings, marketing materials and reusable digital assets. It inherits the same upload, preview, tag, search, sharing, version, log and permission capabilities as an ordinary enterprise folder, while adding classification, sub material library, waterfall flow display and material access control for material management. Material library interface The material library is suitable for unified management of pictures, design drafts, product pictures, brand assets, drawings and marketing materials by category. Waterfall material display Waterfall flow view is suitable fo", "headings": [ { "level": 1, "title": "material library", "id": "material-library" }, { "level": 2, "title": "Applicable scenarios", "id": "applicable-scenarios" }, { "level": 2, "title": "Structural model", "id": "structural-model" }, { "level": 2, "title": "Management entrance", "id": "management-entrance" }, { "level": 2, "title": "Permissions and Security", "id": "permissions-and-security" }, { "level": 2, "title": "Relationship with AI image search", "id": "relationship-with-ai-image-search" }, { "level": 2, "title": "Related APIs", "id": "related-apis" } ], "images": [ { "src": "../assets/images/web-assets.webp", "alt": "Material library interface", "caption": "The material library is suitable for unified management of pictures, design drafts, product pictures, brand assets, drawings and marketing materials by category." }, { "src": "../assets/images/waterfall.webp", "alt": "Waterfall material display", "caption": "Waterfall flow view is suitable for quick browsing, selection and preview of large amounts of picture materials." } ], "text": "material library The material library is Babel's centralized management capability for pictures, brand assets, design materials, drawings, marketing materials and reusable digital assets. It inherits the same upload, preview, tag, search, sharing, version, log and permission capabilities as an ordinary enterprise folder, while adding classification, sub material library, waterfall flow display and material access control for material management. Material library interface The material library is suitable for unified management of pictures, design drafts, product pictures, brand assets, drawings and marketing materials by category. Waterfall material display Waterfall flow view is suitable for quick browsing, selection and preview of large amounts of picture materials. Applicable scenarios Scenario Typical content Management objectives Brand material library Logo, VI, fonts, standard diagrams, activity diagrams Ensure that the same latest version of brand assets is used inside and outside the enterprise Design material library Pictures, PSD, AI, CAD, 3D, renderings Precipitate reusable materials by project, category, customer or product line Marketing database Posters, videos, product images, brochures Quickly search, preview, download and share with sales or channels Engineering drawing library Design drawings, scans, process drawings, delivery drawings Combined with authority, version, archiving and audit control flow AI picture knowledge base Pictures, pictures in PDF, tagged materials Used with AI image search, image search, OCR and automatic labeling Structural model The material library can be divided into multiple material categories according to corporate business. Sub material libraries can be established under each material category for further segmentation by brand, project, product line, customer, year, region or business department. Material files are still Babel file objects, with version, log, preview, download, share, move, copy, label, description, annotation and permission control. The API provides material library related interfaces, which can be used to automatically create categories, create sub material libraries, or control whether users have material library access rights. Management entrance Capabilities Description Set user material library permissions Control whether users have permission to access the material library through the management terminal or API Create material classifications Create enterprise level material classifications, such as branding, marketing, design, engineering, and product images Create a sub material library Continue to establish a business library under the category to facilitate authorization, operation and retrieval File upload and organization Supports web page, client, synchronization, drag and drop, right click upload and batch organization Waterfall browsing Provide a list method that is more suitable for visual filtering of picture materials Metadata and filtering Combine tags, descriptions, file names, image metadata, advanced search and AI image search filtering Permissions and Security The Material Library should not be understood as a public library. It is still subject to corporate accounts, departments, projects, file access controls, sharing permissions, security policies and audit logs: Administrators can control which users have access to the library. Files in the material library can continue to set folder permissions, member permissions, validity period permissions and sharing permissions. When sharing materials externally, you can combine passwords, validity periods, download permissions, preview permissions, watermarks and sharing logs. For sensitive pictures, design drafts, drawings or customer materials, watermarks, download control, confidentiality levels, access logs and security audits can be combined. AI image search, image search, OCR or automatic labeling should only return results within the range of materials that the user has permission to access. Relationship with AI image search The material library is naturally related to Zhichao AI’s text search, image search, image OCR, PDF image search and AI automatic tagging. For enterprises with a large number of pictures, irregular manual naming, and deep directory levels, the material library provides the basis for \"storage and authorization\", and AI image search provides the ability to \"understand and search\". Related APIs Set whether the user has access to material library Create material library class Create sub material folder" }, { "lang": "en", "slug": "watermark-security", "title": "Watermark function", "description": "Introduces text watermarks, registered account watermarks, picture watermarks, real watermarks, preview watermarks, download watermarks and enterprise console settings.", "category": "Product Features", "top_category": "使用指南", "keywords": [ "watermark", "True watermark", "Preview watermark", "Download watermark", "Security" ], "url": "en/watermark-security.html", "source": "content/en/watermark-security.md", "summary": "Watermark function The watermark function is used to reduce the risk of leakage during file preview, download, print, share and outgoing process. Babel's watermark capabilities are divided into interface/preview watermarks, output file watermarks, and real watermarks embedded in files, and work with permission control, sharing policies, audit logs, confidentiality levels, and enterprise console configurations. Web version file preview and operation entrance Watermarks usually take effect together with preview, download, print, share, and enterprise console policies. The actual display effect depends on the deployment configuration and administrator settings. Watermark type Type Description T", "headings": [ { "level": 1, "title": "Watermark function", "id": "watermark-function" }, { "level": 2, "title": "Watermark type", "id": "watermark-type" }, { "level": 2, "title": "Effective range", "id": "effective-range" }, { "level": 2, "title": "Preview, download and print", "id": "preview-download-and-print" }, { "level": 2, "title": "Relationship with permission system", "id": "relationship-with-permission-system" }, { "level": 2, "title": "Administrator configuration", "id": "administrator-configuration" }, { "level": 2, "title": "Watermark setting instructions", "id": "watermark-setting-instructions" }, { "level": 2, "title": "Related chapters", "id": "related-chapters" }, { "level": 2, "title": "White paper excerpt", "id": "white-paper-excerpt" }, { "level": 3, "title": "Main columns", "id": "main-columns" } ], "images": [ { "src": "../assets/images/web-main.webp", "alt": "Web version file preview and operation entrance", "caption": "Watermarks usually take effect together with preview, download, print, share, and enterprise console policies. The actual display effect depends on the deployment configuration and administrator settings." } ], "text": "Watermark function The watermark function is used to reduce the risk of leakage during file preview, download, print, share and outgoing process. Babel's watermark capabilities are divided into interface/preview watermarks, output file watermarks, and real watermarks embedded in files, and work with permission control, sharing policies, audit logs, confidentiality levels, and enterprise console configurations. Web version file preview and operation entrance Watermarks usually take effect together with preview, download, print, share, and enterprise console policies. The actual display effect depends on the deployment configuration and administrator settings. Watermark type Type Description Typical uses Text watermark The administrator can set fixed text, such as company name, project name, confidentiality level Enterprise unified confidentiality tips Register account watermark Display watermark based on current visitor account information Trace screenshots, photos or leaked sources Image watermark Use corporate logo or specified image overlay Brand recognition, copyright protection Mixed watermark Private cloud version can combine multiple watermarks according to configuration High security level files or outgoing data True watermark Watermark embedded in file content or output file Scenarios where the mark needs to be preserved as the file propagates Effective range The scope of use of watermarks can be configured by the administrator in the enterprise console. Common strategies include: Enable watermarks on all files. Enable watermarks only on all externally shared files. Allow file sharers to choose whether to enable watermarks when sharing. Enable for specific enterprises, departments, security policies, confidentiality levels or file transfer scenarios. Used in combination with permission policies such as \"preview only, prohibit downloading, and allow downloading of watermarked PDF\". Preview, download and print The white paper clearly mentions that the preview file can have an embedded watermark and can be saved as a watermarked PDF file. When watermarking is turned on, the preview transcoding server will preprocess the preview image and embed the watermark in the image; image files can also be saved as watermarked PDFs. For different formats such as Office, PDF, pictures, CAD, 3D, video screenshots, etc., the final effect depends on the preview/transcoding module, file format and deployment configuration. Relationship with permission system Watermarks are not a replacement for permissions, but part of permissions, auditing and leak tracing: Access controls determine who can view, edit, download, share or print. Watermarks are used to add visual cues and traceability identification when access has been authorized. Sharing permissions determine whether external visitors can preview, download, edit or continue sharing. Audit log records file access, sharing, downloading, permission adjustment and other behaviors. Confidentiality levels, IP policies, Mac binding, two factor authentication, and departmental security policies further tighten access boundaries. Administrator configuration Administrators can maintain watermark types, parameters, and display ranges in the enterprise console. Related capabilities listed in the feature list include \"Watermark type selection and watermark settings\" and \"Real watermark embedded in files.\" In the privatized deployment scenario, it can also be configured in combination with corporate logo, login background, module switches, security policies and customized transcoding services. Watermark setting instructions The Babel watermark is set by the administrator in the enterprise console. It can use one of text watermarks, registered account watermarks, and picture watermarks. The private cloud version supports three kinds of watermark overlays; after the setting is completed, the watermarks will be displayed on the files within the scope according to the administrator's configuration. Related chapters Permission system Security and Audit Preview, Annotation and Review Sharing and Outsourcing White paper excerpt The BabelBird Enterprise Console centralizes the administrator's functions for managing the entire enterprise. Enterprise administrators can configure various options of the enterprise network disk in the enterprise console, turn on or off the required functional modules, set the organizational structure, customize roles and permissions, manage members, set watermarks, set department security policies, IP access policies, bind accounts and mac addresses, monitor network disk usage... Main columns Enterprise configuration: Comprehensive management of enterprise network disk configuration items, such as space allocation, whether personal files are allowed, allowed file upload size, historical version validity period or number of historical versions, various administrator assignments, changing logo and login background, prohibiting or enabling external sharing, and whether to accept email notifications. Various enterprise configuration options can be found in the enterprise configuration column. Organizational structure: Unified management and maintenance of the enterprise's organizational structure and departments. Ability to view departments and management departments in a tree view. View department members, allocate department space, create sub departments, set department security policies... Permission management: Create roles and change role permissions, and manage custom file permissions. Member management: You can search and filter the member accounts of the entire enterprise, add new members, import members in batches, assign member departments and roles, view and manage the information and usage of each member in detail, handover when members leave, add, delete, modify and check member accounts, allocate and limit member space and traffic. Tag management: unified management of tags used by enterprises, adding tags and classifying tags to facilitate users to select tags. File configuration: Add an optional process for file approval and manage the already added approval process. It also has a file blacklist function that can prevent specific types of files from being uploaded. Corporate notifications: Create corporate notifications, manage historical corporate notification lists, and send corporate notifications. Group management: Create and manage groups. When sharing files in the frontend, you can choose which group to share them with. Watermark settings: manage document watermark types, adjust watermark parameters, and set watermark display range. Access log: Manage and query all access records of the entire enterprise network disk. Log reports can be exported. IP policy list: The upload and download behavior of corporate files can be managed through IP policies. For example: downloading files is prohibited in a certain IP range, and you can download files by returning to a certain IP range. Mac address binding: You can bind the user account to the mac address of a specific device, so that the account can only be used on the device bound to the mac address. You can also create a mac address pool. Statistical analysis: Statistically analyze the usage of network disk. Including system activity, file number statistics, active files, number of new files within a period of time, number of uploads per month, and traffic usage. Workbench push: Set the default display card of the workbench. System configuration (private deployment version only): configure the mail server, bind third party SSO authentication, and set the third party authentication login method. Third party account synchronization (private deployment version only): Set the third party account synchronization time and query the third party account synchronization record. Optional modules (private deployment version only): Select the functional modules that the enterprise needs to display and turn off some functional modules. Monitoring and warning: Set warnings for abnormal behavior, and notify administrators when abnormal behavior occurs (for example: users delete files in large numbers) Transfer file configuration: The configuration of the data ferry system allows data ferrying between multiple sets of BabelBirds. Configure the receiving port and sending port of data." }, { "lang": "en", "slug": "sync-client", "title": "Sync with clients", "description": "Introduces arbitrary folder synchronization, sync types, conflict handling, client transfer, locking, and 200,000 folder synchronization capabilities.", "category": "Product Features", "top_category": "使用指南", "keywords": [ "Sync", "Client", "Conflict Handling", "File Locking" ], "url": "en/sync-client.html", "source": "content/en/sync-client.md", "summary": "Synchronize with client The synchronization function is used to establish a continuous synchronization relationship between the local computer and the BabelBird cloud folder. It is not a simple \"whole disk copy\", but an enterprise synchronization capability composed of permissions, synchronization direction, automatic synchronization cycle, file locking, conflict handling, blacklist and client task management. Client sync create.webp Clients can create synchronization tasks from local folders and select cloud destinations. Client sync management Sync management is used to view sync status, errors, conflicts and multiple sync tasks. Core Competencies Capabilities Description Support Platforms", "headings": [ { "level": 1, "title": "Synchronize with client", "id": "synchronize-with-client" }, { "level": 2, "title": "Core Competencies", "id": "core-competencies" }, { "level": 2, "title": "Permission prerequisite", "id": "permission-prerequisite" }, { "level": 2, "title": "Conflicts and versions", "id": "conflicts-and-versions" }, { "level": 2, "title": "Differences from mapping disk", "id": "differences-from-mapping-disk" }, { "level": 2, "title": "Applicable suggestions", "id": "applicable-suggestions" }, { "level": 3, "title": "Overview", "id": "overview" }, { "level": 3, "title": "How to use", "id": "how-to-use" }, { "level": 3, "title": "Summary", "id": "summary" } ], "images": [ { "src": "../assets/images/client-sync-create.webp", "alt": "Client-sync-create.webp", "caption": "Clients can create synchronization tasks from local folders and select cloud destinations." }, { "src": "../assets/images/client-sync-manage.webp", "alt": "Client sync management", "caption": "Sync management is used to view sync status, errors, conflicts and multiple sync tasks." } ], "text": "Synchronize with client The synchronization function is used to establish a continuous synchronization relationship between the local computer and the BabelBird cloud folder. It is not a simple \"whole disk copy\", but an enterprise synchronization capability composed of permissions, synchronization direction, automatic synchronization cycle, file locking, conflict handling, blacklist and client task management. Client sync create.webp Clients can create synchronization tasks from local folders and select cloud destinations. Client sync management Sync management is used to view sync status, errors, conflicts and multiple sync tasks. Core Competencies Capabilities Description Support Platforms Cloud to local Any folder in the cloud can be synchronized to any local location, provided the user has download permission Windows client, Mac client Local to cloud Any local folder can be synchronized to any location in the cloud, provided the user has upload permission Windows client, Mac client Two way synchronization Local and cloud synchronization, suitable for long term maintenance of the same batch of working files Windows client, Mac client Upstream synchronization Upload local changes to the cloud, suitable for collection, backup, and centralized archiving Windows client, Mac client Downstream synchronization Cloud changes are downloaded locally, suitable for data distribution, offline use, and standard material delivery Windows client, Mac client Automatic synchronization time Can set automatic synchronization time or synchronization cycle Windows client, Mac client Sync blacklist Specify certain file types or temporary files not to participate in synchronization Windows client, Mac client Editing lock Files in synchronized folders are automatically locked when editing to reduce multi person conflicts Windows client, Mac client Permission prerequisite Synchronizing from cloud to local requires download permission for the target folder or file. Synchronizing from local to cloud requires upload permission to the cloud target directory. If folder permissions, sharing permissions, project permissions, or validity period permissions change, the synchronization behavior should also change. When the administrator closes the personal space, restricts downloads, restricts uploads, or adjusts module authorization, the synchronization entrance and capabilities may change with the configuration. Due to limitations of the system file management interface, the Linux/Xinchuang client does not support the ability to synchronize folders and mapped disks; the web client and mobile client do not support local folder synchronization. Conflicts and versions After the files in the synchronized folder are edited or overwritten, the client will monitor the local changes and upload them as new versions in the cloud. If local files and cloud files change at the same time, version conflicts may occur. Exclamation marks appearing in synchronized folders usually indicate that there is a version conflict between the local and the cloud. The system will generally try to process it after scanning for updates again. If it does not recover for a long time, you should manually confirm the version that needs to be retained, and then overwrite it by downloading or upload it as a new version. Differences from mapping disk Dimensions Sync folder Virtual mapped disk Local storage Files within the synchronization range will be saved locally By default, the local space will be incompletely occupied and cached on demand Offline capability Synced files can be used offline More dependent on network connection Applicable scenarios Fixed work data, local batch processing, offline office, data collection Browse cloud data like accessing local disk Risk points When the synchronization range is large, it occupies disk and needs to handle conflicts Network or permission changes will directly affect the access experience Applicable suggestions For directories that require long term offline editing or local batch processing, synchronization is preferred. If you only need to browse a large amount of cloud data at any time and do not want to occupy the local disk, use the mapped disk first. For large file scenarios such as design, engineering, video, materials, etc., the synchronization range and blacklist should be set appropriately. For confidential information, download permissions, watermarks, audits, confidentiality levels and departmental security policies should be combined. Overview File synchronization is one of the most popular functions of BabelBird Enterprise Drive. It allows users to synchronize any local folder to the cloud or any cloud folder to the local, achieving real time synchronization of cloud and local files. This section contains the following key functions: Synchronization management: Babel supports the creation of multiple synchronizations and can manage them uniformly in the synchronization management list. Multiplayer collaboration: Babel Sync is designed for multiplayer collaboration. It automatically locks files to prevent conflicts caused by multiple people editing at the same time, and also has a conflict handling mechanism and version management. Consistent with permissions: BabelBird Sync will determine the user's permissions. Users without download permission will not download files due to synchronization, ensuring the consistency and closed loop of permissions. This means that users can set which folders can be synchronized through permissions. Multiple synchronization types: Babel supports multiple synchronization types, and users can choose the appropriate synchronization method according to specific needs: Two way synchronization: the cloud and local folders keep the content consistent, and modifications on either side will be synchronized to the other side. One way upward synchronization: local updates will be synchronized to the cloud, but cloud updates will not affect the local. One way downward synchronization: Cloud updates will be synchronized to the local, but local updates will not affect the cloud. Powerful technical advantages: BabelBird's enterprise network disk synchronization function has a number of technical advantages to ensure performance and stability: Support large scale folders: Babel supports folder synchronization of up to 200,000 files. File editing lock: When editing a synchronized file, the file will be automatically locked to prevent conflicts caused by multiple edits. Conflict handling mechanism: For editing conflicts on the same file, Babel provides a conflict handling mechanism to ensure the integrity of the file version. Version management: The file synchronization function and version management work together to ensure that local folders will not be overwritten and lose content due to misoperations and other reasons. Even if a file conflict occurs, the two conflicting versions of the files will be saved. Error handling in asynchronous situations: The file synchronization function also includes error handling and repair in asynchronous situations. How to use Turn on synchronization: right click the local folder and select BabelBird Sync the folder. Select synchronization method: Users can choose the appropriate synchronization method during synchronization, including one way synchronization, two way synchronization, etc. Permission configuration: Through permission configuration, users can implement more customized synchronization methods and restrict file deletion or other operations as needed. Multi person collaboration: Under multi person collaboration, files will be automatically locked when editing to avoid conflicts caused by multiple people editing at the same time. The conflict handling mechanism ensures the consistency of file versions. Version management: The file synchronization function supports version management, and users can view previous file versions and restore them. Summary The file synchronization function of BabelBird Enterprise Drive is an excellent tool that can achieve real time synchronization of cloud and local files. Technical advantages such as multiple synchronization methods, permission configuration, multi person collaboration, and version management ensure high performance, stability, and security." }, { "lang": "en", "slug": "mapped-drive", "title": "virtual map disk", "description": "Introducing the ability of mapped disks to access cloud files like local disks, and the differences with WebDAV/SMB.", "category": "Product Features", "top_category": "使用指南", "keywords": [ "mapping disk", "Yunqiao", "WebDAV", "SMB" ], "url": "en/mapped-drive.html", "source": "content/en/mapped-drive.md", "summary": "Virtual mapping disk The virtual mapped disk allows users to access BabelBird cloud files in Windows Explorer or macOS Finder as if they were a local disk. It is suitable for scenarios where the directory level is deep, the number of files is large, and users are accustomed to opening files with local file managers and professional software. Client main interface The client carries desktop capabilities such as uploading and downloading, synchronization, disk mapping and local editing. Core Competencies Capabilities Description Support Platforms Explorer/Finder access Access the network disk directory in the system file manager Windows client, Mac client Virtual drive letter/virtual path Clou", "headings": [ { "level": 1, "title": "Virtual mapping disk", "id": "virtual-mapping-disk" }, { "level": 2, "title": "Core Competencies", "id": "core-competencies" }, { "level": 2, "title": "How to work", "id": "how-to-work" }, { "level": 2, "title": "Permissions and Network", "id": "permissions-and-network" }, { "level": 2, "title": "Differences from WebDAV/SMB", "id": "differences-from-webdav-smb" }, { "level": 2, "title": "Applicable suggestions", "id": "applicable-suggestions" }, { "level": 2, "title": "Detailed description of the white paper", "id": "detailed-description-of-the-white-paper" }, { "level": 3, "title": "Overview", "id": "overview" }, { "level": 3, "title": "Main features", "id": "main-features" }, { "level": 3, "title": "Technical advantages (comparing WebDAV and SMB)", "id": "technical-advantages-comparing-webdav-and-smb" }, { "level": 3, "title": "Application scenarios", "id": "application-scenarios" } ], "images": [ { "src": "../assets/images/client-main.webp", "alt": "Client main interface", "caption": "The client carries desktop capabilities such as uploading and downloading, synchronization, disk mapping and local editing." } ], "text": "Virtual mapping disk The virtual mapped disk allows users to access BabelBird cloud files in Windows Explorer or macOS Finder as if they were a local disk. It is suitable for scenarios where the directory level is deep, the number of files is large, and users are accustomed to opening files with local file managers and professional software. Client main interface The client carries desktop capabilities such as uploading and downloading, synchronization, disk mapping and local editing. Core Competencies Capabilities Description Support Platforms Explorer/Finder access Access the network disk directory in the system file manager Windows client, Mac client Virtual drive letter/virtual path Cloud files can be entered through drive letter or virtual path Windows client, Mac client Cache management On demand downloading and caching of files to reduce local disk usage Windows client, Mac client Editing automatically locks Automatically locks when opening a file for editing in the mapped disk to reduce multi person editing conflicts Windows client, Mac client File references and associated resources Click a file to open file references and associated resources Windows client, Mac client Third party program access Local applications can access mapped disk files just like local paths Windows client, Mac client How to work The virtual mapped disk uses local virtual disk technology similar to OneDrive and iCloud to present the cloud directory in the operating system. File icons, directory structures, and basic operations are visible in the system file manager, and users can open, copy, paste, delete, or access files with third party software. Unlike full synchronization, mapped disks usually do not save all cloud files locally in advance, but download or cache them when needed. Permissions and Network The range of files that users can see and operate is still determined by the Babel permission system. Access to the mapped disk relies on network connection; when the network is unavailable or permissions expire, uncached files cannot be opened normally. File editing, uploading new versions, deleting, moving, sharing, etc. should still be controlled by folder permissions, project permissions, and security policies. The Linux/Xinchuang client does not support the synchronization of folders and mapped disk functions, and is suitable for access through the web page, the client's regular file list, or other deployed portals. Differences from WebDAV/SMB Dimensions Virtual mapping disk WebDAV/SMB Permission consistency Consistent with Babel account, department, project, sharing and file access control Often requires separate gateway or protocol permission mapping Product integration Can be combined with versions, locks, logs, associated resources, and client editing Prefer common file protocols Experience goals Localized access experience for BabelBird cloud files Access to network file systems Applicable boundary Depends on client and enterprise configuration Depends on protocol service and network environment Applicable suggestions When browsing a large amount of cloud data but do not want to occupy the local disk, use the mapped disk first. When you need to process fixed directories offline, use synchronized folders first. When using CAD, design, video, engineering and office professional software, you can maintain local opening habits through mapping disks. For sensitive directories, file access permissions, download control, watermarks and log auditing should be combined. Detailed description of the white paper Overview Virtual mapped disk: BabelBird Enterprise Drive introduces the virtual mapped disk function, which provides a way to seamlessly connect cloud files. You can access the mapped disk in Windows Explorer or Mac Finder just like accessing a local disk, thereby achieving an easy access to cloud files. Technical implementation: BabelBird Virtual Mapping Disk uses a technical solution similar to OneDrive and iCloud. It creates a virtual disk in the operating system and maps cloud files to the user's local computer, making these files visible in the user's file browser. Main features Local access to cloud files: The virtual mapped disk allows users to access files and folders in their Babel Enterprise network disk through tools such as local file explorer or Finder. No local storage occupation: Unlike traditional file synchronization methods, virtual mapped disks do not actually store cloud files on the user's local disk, so they do not occupy local storage space. Files are cached or downloaded only when needed. Online access: Virtual mapped disks require a network connection to access cloud files. The file icon is actually just a link to the cloud file, so you need to be online to view and operate these files, and the permissions are the same as those in the cloud. Transparent operation: Users can operate files in the virtual mapped disk just like local files, including opening, copying, pasting, deleting and other operations. Automatic synchronization: File changes will be automatically synchronized to the cloud, thereby maintaining the consistency of the cloud files and the files in the virtual mapped disk. Associated files: When you open a file with an associated file in the Babel mapping disk, the associated file will be automatically loaded, achieving the same effect as opening a file in a local folder. For example: opening a DWG (AutoCAD file) containing a large number of reference files, or an Excel chart associated with other files. Technical advantages (comparing WebDAV and SMB) Permission consistency: Unlike WebDAV or SMB mounting (which must use permission rules compatible with WebDAV or SMB), the Babel mapping disk is implemented by directly calling the underlying file system of the operating system, which can achieve the same permission control as Babel. (For example: you can only preview but not download or save as.) In WebDAV and SMB, only the view permission is actually read only. As long as the file is visible, the user can open and obtain the file in read only mode, losing control of the file. Higher performance: The Babel mapping disk directly corresponds to the Babel server related interfaces. There is no forwarding and intermediate processing links. You can directly obtain the file list provided by the server and open the folder virtually, so it can provide higher performance, and there will be no lag when opening the file list and checking files. Using WebDAV, you can only open a folder to temporarily load a list. If the number of folder files exceeds a certain number (related to device performance and network speed, usually more than 300), severe freezes and slow access will occur. WebDAV does not support very large folders using object storage systems. More secure: Babel mapping disk can determine the folders and files in the folders that everyone can view based on permissions. People with different permissions can see different contents when viewing the same folder. SMB and WebDAV currently cannot do this. At the same time, Babel's files are encrypted and stored in object storage in blocks. However, if the files are encrypted and stored in blocks, using WebDAV, you need to decrypt the files in order to obtain the file list. This means that products that support WebDAV either do not store data encrypted, or the performance of WebDAV is extremely poor and the number of files exceeds a certain range and is unavailable. Controllability: Unlike WebDAV and SMB that use third party software to mount, the Babel mapping disk is a self developed drive. It has controllability over the drive's operation, menu, running mode, and function implementation, and is responsible for product quality and user experience consistency. There will be more functional expansions in the future. Mainstream enterprise level solutions: Whether it is Microsoft's OneDrive, Google's Google Drive, Apple's iCloud, BOX's BOX Drive, or domestic mainstream Internet enterprise network disk manufacturers, they all use solutions similar to Babel's mapping disks, rather than simply accessing WebDAV (to access WebDAV, you only need to make protocols compatible and open for access, and it is simple to implement. Why do mainstream enterprise level manufacturers spend a lot of energy to develop their own mapping disks?). The main application scenarios of WebDAV are individuals or small teams that do not need to make complex permission judgments, store encryption, and open all files. The main usage scenario of SMB is also open file sharing (plain text storage) for individuals and small teams. Application scenarios Virtual mapped disks are suitable for users who need to frequently access cloud files but do not want to change their local disk usage habits or occupy local storage space. This function allows users to access cloud files just like local files, and access network disks in other applications just like opening local folders, without changing usage habits, and facilitates file management and use." }, { "lang": "en", "slug": "encrypted-folder", "title": "Encrypted Folder", "description": "Introduces BabelBird encrypted folders, use cases, creation, access, password security and sharing restrictions.", "category": "Product Features", "top_category": "使用指南", "keywords": [ "encrypted folder", "file vault", "password access", "security" ], "url": "en/encrypted-folder.html", "source": "content/en/encrypted-folder.md", "summary": "Encrypted Folder Encrypted folders are special password protected folders inside shared enterprise drive spaces. They are suitable for unpublished files, private materials, contracts, HR documents, finance files, R&D data or project files that should not be broadly visible yet. Create encrypted folder entry Choose “Encrypted Folder” from the New menu to create a folder that requires a password. Positioning Encrypted folders do not replace BabelBird’s permission system. They add an extra “password required” layer on top of existing permissions. Even if a user can see the folder through a department, project or share, the password is still required to view its contents. Typical use cases: A sh", "headings": [ { "level": 1, "title": "Encrypted Folder", "id": "encrypted-folder" }, { "level": 2, "title": "Positioning", "id": "positioning" }, { "level": 2, "title": "How To Create", "id": "how-to-create" }, { "level": 2, "title": "Access", "id": "access" }, { "level": 2, "title": "Password Security", "id": "password-security" }, { "level": 2, "title": "Sharing Behavior", "id": "sharing-behavior" }, { "level": 2, "title": "Combined Security Controls", "id": "combined-security-controls" } ], "images": [ { "src": "../assets/images/encrypted-folder-create.png", "alt": "Create encrypted folder entry", "caption": "Choose “Encrypted Folder” from the New menu to create a folder that requires a password." }, { "src": "../assets/images/encrypted-folder-password.png", "alt": "Set encrypted folder password", "caption": "Creation requires a folder name and password. The creator must keep the password safely." }, { "src": "../assets/images/encrypted-folder-locked.png", "alt": "Encrypted folder lock indicator", "caption": "After creation, the folder shows a lock indicator and requires a password when opened." } ], "text": "Encrypted Folder Encrypted folders are special password protected folders inside shared enterprise drive spaces. They are suitable for unpublished files, private materials, contracts, HR documents, finance files, R&D data or project files that should not be broadly visible yet. Create encrypted folder entry Choose “Encrypted Folder” from the New menu to create a folder that requires a password. Positioning Encrypted folders do not replace BabelBird’s permission system. They add an extra “password required” layer on top of existing permissions. Even if a user can see the folder through a department, project or share, the password is still required to view its contents. Typical use cases: A shared department space contains a subset of files that only password holders should access. Project materials are not yet released and need temporary protection. Private files need a file vault style folder to reduce accidental access or misconfigured permissions. Files inside an encrypted folder are shared externally, but recipients still need the folder password. How To Create 1. Open the target directory and click “New”. 2. Choose “Encrypted Folder”. 3. Enter the folder name and password. 4. Save it. The file list will show a folder with a lock indicator. Set encrypted folder password Creation requires a folder name and password. The creator must keep the password safely. Access Opening the encrypted folder requires the password. After successful verification, users can upload, download, create, preview, edit, share and use normal file functions inside the folder, subject to their original permissions, file access control, sharing permissions and administrator settings. Encrypted folder lock indicator After creation, the folder shows a lock indicator and requires a password when opened. Password Security Encrypted folders use anonymous encryption. If the password is lost, it cannot be recovered. Operators and engineers cannot decrypt or restore it. If the password is lost, the folder usually cannot be opened and must be deleted and recreated. Usage notes: Do not store the password inside the same encrypted folder. Do not distribute the password in public chats or uncontrolled documents. For long term sensitive data, combine encrypted folders with department permissions, file access control, watermarks, audit logs and classification policies. When an employee leaves, a project ends or materials become public, clean up the password scope and migrate, archive or delete files according to company policy. Sharing Behavior Even if a file inside an encrypted folder is shared, recipients still need the encrypted folder password. Sharing permissions control whether the recipient may view, download, edit, comment or continue sharing; the encrypted folder password controls entry into the protected space. Combined Security Controls Feature Role File access control Assign permissions to members, roles or project members Watermark Add traceable marks during preview, download or output Sensitive content recognition Identify and mark files that may contain sensitive content Audit logs Record access, download, sharing and permission changes IP policy and Mac binding Restrict account use by network or device Classification and security policy Apply stronger confidentiality requirements to departments or files" }, { "lang": "en", "slug": "sensitive-content-recognition", "title": "Sensitive Content Recognition", "description": "Introduces BabelBird sensitive content recognition, configuration entry, detection strategy, handling behavior, scenarios and permission relationship.", "category": "Product Features", "top_category": "使用指南", "keywords": [ "sensitive content recognition", "sensitive keywords", "risk detection", "security audit", "admin tools" ], "url": "en/sensitive-content-recognition.html", "source": "content/en/sensitive-content-recognition.md", "summary": "Sensitive Content Recognition Sensitive content recognition helps identify files that may contain sensitive content and, depending on configuration, mark them, restrict viewing, restrict sharing or assist administrators in manual handling. The capability is included in the v9.4.2.2606171439 version scope, and the public changelog also records the addition of sensitive content recognition under enterprise console management tools. Sensitive content recognition settings Administrators can configure sensitive content recognition in management tools and view the list of detected files. Positioning Common high risk files in an enterprise drive include contracts, certificates, personal data, custo", "headings": [ { "level": 1, "title": "Sensitive Content Recognition", "id": "sensitive-content-recognition" }, { "level": 2, "title": "Positioning", "id": "positioning" }, { "level": 2, "title": "Admin Entry", "id": "admin-entry" }, { "level": 2, "title": "Detection And Handling", "id": "detection-and-handling" }, { "level": 2, "title": "Scenarios", "id": "scenarios" }, { "level": 2, "title": "Relationship With Permissions", "id": "relationship-with-permissions" }, { "level": 2, "title": "Version Note", "id": "version-note" } ], "images": [ { "src": "../assets/images/sensitive-content-recognition.jpg", "alt": "Sensitive content recognition settings", "caption": "Administrators can configure sensitive content recognition in management tools and view the list of detected files." } ], "text": "Sensitive Content Recognition Sensitive content recognition helps identify files that may contain sensitive content and, depending on configuration, mark them, restrict viewing, restrict sharing or assist administrators in manual handling. The capability is included in the v9.4.2.2606171439 version scope, and the public changelog also records the addition of sensitive content recognition under enterprise console management tools. Sensitive content recognition settings Administrators can configure sensitive content recognition in management tools and view the list of detected files. Positioning Common high risk files in an enterprise drive include contracts, certificates, personal data, customer materials, finance data, quotations, R&D documents, source code, confidential project materials and regulated industry content. Sensitive content recognition does not replace human judgement; it helps surface risky files first so administrators do not rely only on manual inspection. Admin Entry Public materials show that “File Settings” in the enterprise console was renamed to “Management Tools”, with a “Sensitive Content Recognition” tab added. Administrators can enable or disable the feature, maintain custom sensitive keywords and query detected files. Common settings include: Enable or disable sensitive content recognition. Maintain custom sensitive keywords, separated by delimiters. Upload a sensitive keyword file for batch maintenance. Configure handling behavior for detected files. Query and locate the sensitive content file list. Detection And Handling Capability Description File marking Detected files can be marked for administrator review and tracing Prohibit viewing Detected files can be restricted from viewing to reduce exposure Prohibit sharing Detected files can be restricted from sharing to prevent outbound leakage Detection list Administrators can view and locate files containing sensitive content Custom keywords Enterprises can maintain keyword lists by industry, department, project or policy Actual handling behavior depends on the deployed version, licensed modules and administrator configuration. False positives, business exceptions and compliance decisions should be reviewed by administrators, security officers or business owners. Scenarios Contracts, quotations, bidding and negotiation materials. Personal data such as ID numbers, phone numbers, emails, addresses and bank card information. Finance reports, salary data, invoices and payment information. Customer lists, channel data, sales leads and cooperation agreements. R&D documents, drawings, code, internal policies and unreleased content. Repositories subject to compliance, audit or confidentiality rules. Relationship With Permissions Sensitive content recognition discovers risk; the permission system controls access. Recommended combinations: Use department roles and project permissions for baseline access. Use file access control for extra authorization on high risk files. Use watermarks and logs for traceability. Use sharing approval, external sharing restrictions or download restrictions for outbound control. Use encrypted folders or classification policies for highly sensitive materials. Version Note The latest v9.4.2.2606171439 scope includes “sensitive content recognition”. Enterprises on earlier deployments may only see the console entry, internal testing behavior or no enabled module. Actual availability depends on deployment and licensing." }, { "lang": "en", "slug": "online-editing", "title": "Online editing", "description": "Independently introduce Office online editing, light document, Markdown/code text, KM mind map, draw.io flow chart and permission system.", "category": "Online Collaboration", "top_category": "使用指南", "keywords": [ "Online editing", "OnlyOffice", "light document", "Markdown", "KM", "draw.io", "Permissions" ], "url": "en/online-editing.html", "source": "content/en/online-editing.md", "summary": "Online editing Online editing covers Office document online collaborative editing, light document online editing, Markdown/code/text editing, KM mind maps, draw.io flow charts, as well as client editing and permission control. Web version file list Online editing is usually entered from the file list or right click menu and is controlled by file permissions, sharing permissions, lock status and enterprise module configuration. Capability Overview Type Default Capabilities Description Office online editing OnlyOffice OnlyOffice is used by default, supporting online editing and multi person collaboration of Word, Excel, PPT, WPS and other documents Other online Offices Accessible Private deplo", "headings": [ { "level": 1, "title": "Online editing", "id": "online-editing" }, { "level": 2, "title": "Capability Overview", "id": "capability-overview" }, { "level": 2, "title": "Permission system", "id": "permission-system" }, { "level": 2, "title": "Office Online Editing", "id": "office-online-editing" }, { "level": 3, "title": "Overview of online editing module", "id": "overview-of-online-editing-module" }, { "level": 3, "title": "Technical basis", "id": "technical-basis" }, { "level": 3, "title": "Main functions", "id": "main-functions" }, { "level": 3, "title": "User experience", "id": "user-experience" }, { "level": 3, "title": "Enterprise Collaboration", "id": "enterprise-collaboration" }, { "level": 3, "title": "Open API", "id": "open-api" }, { "level": 3, "title": "Other online editors", "id": "other-online-editors" }, { "level": 2, "title": "Client editing", "id": "client-editing" }, { "level": 3, "title": "Client editing overview", "id": "client-editing-overview" }, { "level": 3, "title": "Technical implementation", "id": "technical-implementation" }, { "level": 3, "title": "Main functions", "id": "main-functions-2" }, { "level": 3, "title": "User experience", "id": "user-experience-2" }, { "level": 3, "title": "technical challenges", "id": "technical-challenges" }, { "level": 2, "title": "Light document online editing", "id": "light-document-online-editing" }, { "level": 2, "title": "Markdown, code and text online editing", "id": "markdown-code-and-text-online-editing" }, { "level": 2, "title": "Mind map online editing", "id": "mind-map-online-editing" }, { "level": 2, "title": "Flow chart online editing", "id": "flow-chart-online-editing" } ], "images": [ { "src": "../assets/images/web-main.webp", "alt": "Web version file list", "caption": "Online editing is usually entered from the file list or right-click menu and is controlled by file permissions, sharing permissions, lock status and enterprise module configuration." } ], "text": "Online editing Online editing covers Office document online collaborative editing, light document online editing, Markdown/code/text editing, KM mind maps, draw.io flow charts, as well as client editing and permission control. Web version file list Online editing is usually entered from the file list or right click menu and is controlled by file permissions, sharing permissions, lock status and enterprise module configuration. Capability Overview Type Default Capabilities Description Office online editing OnlyOffice OnlyOffice is used by default, supporting online editing and multi person collaboration of Word, Excel, PPT, WPS and other documents Other online Offices Accessible Private deployment can be connected to Office 365, WPS Online, Yongzhong Office and other online Offices that support Web/API as needed Light document Can be used as an independent lightweight document form Suitable for fast recording, online collaboration, knowledge accumulation and scenarios that do not require traditional Office typesetting; Reference: Markdown/Code/Text Comes with text editor Can edit TXT, MD, RTF, as well as CSS, JS, JSP and other text/code files Mind map KM format Default saved as .KM , can export KM, TXT, MD, SVG, PNG, Xmind Flowchart draw.io Support online editing of draw.io flowchart; whether it is enabled by default depends on module authorization and deployment configuration Client editing Local application Call local software to edit cloud files, and automatically upload them as new versions after saving Permission system Online editing is not a separate entry point to bypass permissions. Whether a user can edit depends on the following permissions and status: Whether the user has online editing, editing, uploading new versions or corresponding customized file permissions for the file or folder. Whether the file is in client editing locked, online editing locked, approval locked, finalized or archived status. In the sharing scenario, whether the sharer grants online editing, annotation, downloading, viewing, etc. permissions. Whether the enterprise has enabled permission combinations such as \"Online Editing Only\", which allows collaborative editing but restricts source file downloads. Whether the corresponding online Office, light document, mind map, flow chart or third party editor module is enabled in the private deployment. Office Online Editing Overview of online editing module BabelBird Enterprise Drive has been an official partner of OnlyOffice for many years. The online editing module of BabelBird Enterprise Drive is developed based on OnlyOffice technology and optimizes the loading and display of Chinese fonts. Babel Online Editor supports a variety of document formats, including Microsoft Office (Word, Excel, PPT) and WPS Office. Details of the cooperation between BabelBird and OnlyOffice can be found on the official website of OnlyOffice: https://www.onlyoffice.com Technical basis The technical basis of the online editing module includes: OnlyOffice Editor: OnlyOffice is a powerful online office suite that supports online editing of multiple document formats. Babel integrates it into the network disk system to provide a high quality online editing experience. Chinese font optimization: In order to overcome the shortcomings in the loading efficiency of Chinese fonts in OnlyOffice, BabelBird has been optimized and adopted font localization technology to greatly improve the loading and display speed of Chinese fonts, thus improving the user experience. Document lock: Babel supports both client editing and online editing, which means that in order to prevent file version conflicts, files must be locked when being edited online and cannot be edited on the client side, and files must be locked when being edited on the client side and cannot be edited online. Main functions BabelBird's online editing module includes the following main functions: Multi format support: Users can edit and view documents in Microsoft Office (Word, Excel, PPT) and WPS Office formats online. Collaborative editing: The online editing module supports multiple users to collaboratively edit documents at the same time. Users can view the changes of other users in real time and edit documents together. This collaborative editing feature is great for team collaboration. Compatibility: BabelBird's online editing module is compatible with Microsoft Office and can restore the Office layout and fonts on web pages. Ensure good compatibility of document layout and format when opened in different editors. Open API: Babel opens the API of the online editor, allowing other enterprise software to call the API and integrate the online editing function into other applications. User experience The goal of the online editing module is to provide a user friendly and smooth online editing experience. Users can directly open the document that needs to be edited in the network disk, and save it immediately after editing without leaving the network disk interface. This seamless integration improves user efficiency and makes editing documents more convenient. At the same time, Babel's permission configuration supports \"online editing only\", which means that some users can only edit documents online but cannot download and obtain documents. Enterprise Collaboration BabelBird's online editing module is not only suitable for individual users, but also provides a collaborative office platform for enterprises. Team members can edit documents together, share ideas, and work more efficiently through real time collaboration. Open API Babel Online Editor API allows enterprises to integrate online editing functions into their own software or third party software, allowing enterprises to fully utilize online editing capabilities. Other online editors BabelBird Standard Edition also integrates other online editors for online editing and creation of MD files, TXT files and even mind maps (such as brain maps). At the same time, BabelBird can also integrate other online editing systems that support HTML5 by connecting to third party APIs, such as Microsoft Office 365 or Kingsoft's web office (WPS). Comes with text editor for online editing. The text editor that comes with BabelBird can edit and preview text files such as TXT, MD, RTF, etc. It can also edit code files such as CSS, JS, JSP... to facilitate users to quickly create document records. Comes with a mind map (mind map) editor. BabelBird comes with its own mind map module, which can create and edit mind map files online. Mind map files are saved in KM format by default. It can also be exported to KM, TXT, MD, SVG, PNG, and Xmind formats. BabelBird can also optionally support the creation of flow charts, but you need to purchase the corresponding module license (the non standard version comes with it by default). Client editing Client editing overview BabelBird Enterprise Drive provides powerful client side editing functions. Users can easily call local editing software to edit cloud documents. After editing and saving, the files will be automatically uploaded to the cloud. This feature not only improves user convenience, but also helps avoid file version conflicts, thereby improving work efficiency. Right click on the file to be edited in the client file list and select Edit to open client editing. The implementation principle of client side editing determines that as long as there is a local editing program, all types of files can be edited on the client side. Technical implementation Implementation technologies for client side editing functions include: Client integration: Both BabelBird's Win client and Mac client support the calling of local editing software, which allows users to open and edit cloud files directly in local software. Cache management: Client side editing uses caching technology to cache the files that need to be edited from the cloud to the local computer and call local applications to open them. When the system detects that the file being edited has been updated, it uploads the updated file as a new version. Good cache management technology can save users' local disk space while ensuring efficiency. Users can also manually clear the file cache in the Babel right click menu. File status detection: Before client side editing, the system checks the status of the file, including whether the file is locked by another user. This helps prevent multiple people from editing the same file at the same time and avoid version conflicts. Automatic locking and unlocking: When a user starts editing a file, the system automatically locks the file to ensure that other users cannot edit the same file at the same time. After editing is completed, the file will be automatically unlocked, a new version will be generated, and the modified file will be uploaded to the cloud. Version conflict handling: Despite the locking mechanism, file version conflicts may occur under certain circumstances, such as network problems or when the file has not been edited for a long time. BabelBird provides a conflict handling interface, allowing users to compare and choose whether to use the cloud version or the local version as the current version. Regardless of the user's choice, the system will ensure that the unselected version will also be uploaded to the cloud as a historical version to prevent data loss. Main functions The main functions of the client editing function include: Local editing: Users can cache the file locally by clicking the local edit button and edit it using the local default application. Babel theoretically supports local editing of all files as long as there is a corresponding local application. Automatic lock: Files are automatically locked while editing to prevent other users from editing at the same time, thus avoiding version conflicts. Automatically unlock: After editing is completed and the app is closed, the file will be automatically unlocked, a new version will be generated, and the modified file will be uploaded to the cloud. Version control: All edited and uploaded files will generate new versions so that users can view and restore previous versions at any time. User experience Client side editing capabilities provide an excellent user experience. Users can edit in the local editor without having to download the file, edit it and then upload it. At the same time, file formats that do not support online editing or online preview can also be opened for editing or preview through client editing. This improves editing efficiency and workflow smoothness. technical challenges The technical challenges of client side editing capabilities lie in detecting the status of files, automatically locking and unlocking, and handling conflicting file versions. The system needs to accurately determine whether a file is being edited by another user, while also providing user friendly solutions when conflicts occur. These challenges require a combination of user experience and data integrity. BabelBird client editing is one of the few functional modules in the industry that can handle these problems well. Light document online editing Light documents are designed for rapid writing, multi person collaboration, knowledge accumulation and lightweight publishing scenarios. Compared with traditional Office, light documents are more suitable for organizing information with structured paragraphs, lists, tables, links, and embedded content; compared with Markdown, light documents emphasize visual editing and low threshold collaboration for non technical people. In actual deployment, the entry, template, permissions and publishing method of light documents should be designed together with the enterprise document specifications, project collaboration methods and knowledge base accumulation process. Markdown, code and text online editing Babel comes with a text editor that can be used for text documents such as TXT, MD, and RTF, as well as code files such as CSS, JS, and JSP. Applicable scenarios include project descriptions, lightweight technical documents, configuration snippets, script descriptions, log snippets and team knowledge maintenance. Mind map online editing Mind maps are saved in .KM format by default and support exporting to KM, TXT, MD, SVG, PNG, and Xmind. It is suitable for requirements sorting, meeting minutes, knowledge structure, project dismantling and training materials. When working with project folders, mind maps will also participate in version management, permission control, sharing and synchronization. Flow chart online editing The flowchart uses the draw.io system, which is suitable for business processes, system architecture, approval flow, data flow and implementation flowcharts. This capability is available as an optional module, and its availability depends on authorization and deployment configuration." }, { "lang": "en", "slug": "permissions", "title": "Permission system", "description": "The system introduces department roles, project permissions, file access control, sharing permissions, customized file permissions and online editing permissions.", "category": "Permissions And Security", "top_category": "使用指南", "keywords": [ "Permissions", "ACL", "File access control", "Project permissions", "Sharing permissions" ], "url": "en/permissions.html", "source": "content/en/permissions.md", "summary": "Permission system Babel's permission system covers file list, search, preview, editing, synchronization, disk mapping, sharing, AI answering and automated tasks. Permissions are not a single switch, but are determined by corporate roles, department roles, project member permissions, file access control, custom file permissions, sharing permissions and corporate security policies. Permission Judgment Level Hierarchy Control Object Example Enterprise roles Enterprise level management behaviors Super administrator, security officer, security auditor, file administrator Department roles Department folders and department members View, upload, download, edit, delete, department file management, su", "headings": [ { "level": 1, "title": "Permission system", "id": "permission-system" }, { "level": 2, "title": "Permission Judgment Level", "id": "permission-judgment-level" }, { "level": 2, "title": "Detailed description of the white paper", "id": "detailed-description-of-the-white-paper" }, { "level": 3, "title": "Role permissions", "id": "role-permissions" }, { "level": 3, "title": "File permissions", "id": "file-permissions" }, { "level": 3, "title": "Summary", "id": "summary" }, { "level": 2, "title": "Relationship with online editors", "id": "relationship-with-online-editors" } ], "images": [], "text": "Permission system Babel's permission system covers file list, search, preview, editing, synchronization, disk mapping, sharing, AI answering and automated tasks. Permissions are not a single switch, but are determined by corporate roles, department roles, project member permissions, file access control, custom file permissions, sharing permissions and corporate security policies. Permission Judgment Level Hierarchy Control Object Example Enterprise roles Enterprise level management behaviors Super administrator, security officer, security auditor, file administrator Department roles Department folders and department members View, upload, download, edit, delete, department file management, sub department management Project permissions Project folder Project leader, project assistant, project members, member validity period File access control Single file or folder Set invisible, viewable, editable, and validity period permissions for a member or role Customize file permissions Share, project, access control Permission names and combinations defined by administrator Sharing permissions External or internal recipients View, download, edit, comment, validity period, password, anonymous access Security policy Enterprise or department IP policy, Mac binding, watermark, secret level, external sharing policy Detailed description of the white paper Permission management of BabelBird Enterprise Drive is one of its core functions. It runs through the entire system to ensure that users can access and manage files safely and compliantly. The Babel permission system includes two main aspects: role permissions and file permissions. Role permissions Define roles: Babel allows you to define different roles within the enterprise. Each role can include a specific set of permissions to control users' access and operations in department folders. These roles can be created based on department management needs, such as \"Department Administrator\", \"Department Member\", etc. Department role permissions: Each department member can be assigned different access permissions based on their roles in different departments. This means that users can have different levels of permissions in different departments. Flexible management: Babel's role permissions support multiple department roles, and the same role can be used in different departments at the same time. After the permission content of a role is changed, the permissions of members using the same role will also be changed accordingly. Permission combination: Babel bird role permissions support the combination of more than 30 optional permissions to achieve refined user permission control. These permissions cover various access and operation behaviors, such as preview, upload, download, edit, etc. List of optional permissions for roles: File permissions Custom permissions: File permissions can also be customized in the background, and users can choose specific permission types and names. These custom file permissions will be used for file sharing, project management, and file permission control. File access control: File access control allows department members to set specific access permissions on files and folders to override department role permissions. This means that the access behavior of a certain file or folder in the department can be more precisely controlled. File access control only applies to department members and project members. High priority: File access control permissions have a higher priority. If file access control is set, it will override the member's department role permissions or project permissions. Users can set file access permissions as needed. Department File and Folder Control: Users can enable file access control for department files and folders to control access to specific files or folders. Validity period: File access control can set a validity period. After the validity period, the constraints of file access control will become invalid. For example, if a department member who does not have file editing permissions is given the editing permissions for the file, the validity period is 3 days. After 3 days, the permissions granted by the file access control will expire, and the department members' permissions on the files will become the permissions of the member role. Summary The permission management of BabelBird Enterprise Drive is a comprehensive system that can meet the specific needs of different departments and projects of the enterprise. Role permissions and file permissions work together to ensure that users have precise control over file access and operations. This feature helps improve security, compliance and productivity. Relationship with online editors Online editing, online editing only, client download, client editing, upload new version, and preview permissions can be combined. A typical security policy is to allow outsiders to collaborate or preview online, but not to download source files; it can also allow project members to access certain project files only within the validity period." }, { "lang": "en", "slug": "security", "title": "Security and Audit", "description": "Introduce security architecture, SSO, encryption, log auditing, watermarking, backup, departmental security policies and risk control.", "category": "Permissions And Security", "top_category": "使用指南", "keywords": [ "Security", "SSO", "audit", "watermark", "encryption" ], "url": "en/security.html", "source": "content/en/security.md", "summary": "Security and Audit security User Authentication: Use strong user authentication mechanisms, including single sign on (SSO), OAuth authentication, and multi factor authentication (MFA). Authorization: Use an authorization framework such as Spring Security to define and enforce access control policies to ensure that users can only access the resources they are authorized to use. Data Encryption: Implement encryption of data transmission and storage to protect the security of user data. business logic File Management: Developed business logic to handle file upload, download, version control, sharing and collaboration functionality. User management: Implement user management, rights management a", "headings": [ { "level": 1, "title": "Security and Audit", "id": "security-and-audit" }, { "level": 2, "title": "Preview and transcode", "id": "preview-and-transcode" }, { "level": 3, "title": "Performance optimization", "id": "performance-optimization" }, { "level": 2, "title": "Security", "id": "security" }, { "level": 3, "title": "Secure architecture", "id": "secure-architecture" }, { "level": 3, "title": "User Authentication and Authorization (SSO)", "id": "user-authentication-and-authorization-sso" }, { "level": 3, "title": "User experience", "id": "user-experience" }, { "level": 3, "title": "Overview", "id": "overview" }, { "level": 3, "title": "Overview", "id": "overview-2" }, { "level": 3, "title": "Overview", "id": "overview-3" } ], "images": [], "text": "Security and Audit security User Authentication: Use strong user authentication mechanisms, including single sign on (SSO), OAuth authentication, and multi factor authentication (MFA). Authorization: Use an authorization framework such as Spring Security to define and enforce access control policies to ensure that users can only access the resources they are authorized to use. Data Encryption: Implement encryption of data transmission and storage to protect the security of user data. business logic File Management: Developed business logic to handle file upload, download, version control, sharing and collaboration functionality. User management: Implement user management, rights management and user organizational structure. Search function: An efficient search engine has been developed to support fast retrieval of files and metadata. Online editing: Responsible for online editing and collaborative editing of documents. File transcoding: Responsible for batch queuing transcoding of files and generating preview files. Object storage: file blocking and disk placement, storage system management. Web services RESTful API: Use RESTful API to support data interaction and collaboration between the front end and other clients. Cache management Caching strategy: Use caching to improve performance, including page caching, data caching, and session caching. Asynchronous task processing Message queue: Use the message queue system RabbitMQ to handle asynchronous tasks, such as file transcoding, file preview generation, etc. By using the Struts2 and Spring framework, combined with the above design considerations, a powerful, high performance, safe and reliable enterprise network disk back end system can be built to meet user needs and support future expansion and function additions. Cloud infrastructure selection (public cloud SAAS version BabelBird) The choice of public cloud infrastructure can directly affect the performance, reliability and security of enterprise network disk products. The Babel public cloud version selected Alibaba Cloud's ECS, OSS services and CDN distribution business after many comparisons. Currently (in 2023), the Babel system running in public cloud SAAS mode has been operating online with zero server failures for more than 10 years. Cloud service provider selection The business server SAAS version BabelBird uses Alibaba Cloud's ECS (cloud server) cluster Alibaba Cloud's ECS is an elastic computing service that provides you with virtual machine instances so that you can run applications in the cloud. These are some of the key advantages of choosing ECS: Flexibility: ECS allows you to create, start and stop virtual machine instances as needed. This means you can scale your computing resources up or down based on your traffic needs. Scalability: Alibaba Cloud provides a variety of ECS instances of different specifications to meet the needs of different workloads. You can choose based on the performance requirements of your application. Reliability: Alibaba Cloud's ECS instances are generally highly available, providing multiple data centers and availability zones to ensure business continuity. Security: Alibaba Cloud provides various security features, including network isolation, firewalls, and security groups, to help you protect your virtual machine instances from malicious attacks. The object storage SAAS version of Babel uses Alibaba Cloud's OSS (Object Storage Service) Alibaba Cloud's OSS is a highly scalable, safe and reliable cloud storage service suitable for storing and managing large amounts of files and data. Here are some advantages of choosing OSS: Scalable storage: OSS provides scalable storage capacity that can be dynamically expanded according to your needs. This is very important for file storage in enterprise network disk products. Data backup and recovery: Alibaba Cloud's OSS has data backup and version control functions that can help you protect your data from loss or damage. Security: Data stored in OSS is usually protected by encryption and access control to ensure data security. CDN integration: Integrating with CDN services can improve file distribution speed and user experience. To ensure smooth access around the world, BabelBird also uses CDN distribution A CDN (Content Delivery Network) service caches content to globally distributed edge nodes to reduce loading times and improve user experience. Alibaba Cloud's CDN service can bring the following benefits to enterprise network disk products: Fast distribution: Accelerate the distribution of files, ensuring that users can quickly access and download files, regardless of geographical location. Load balancing: CDN can help share the load of the server, reduce the pressure on the server, and improve the performance of the website. Security: CDN services usually have DDoS attack protection features to protect the website from malicious attacks. Global coverage: Alibaba Cloud's CDN service has global coverage, ensuring that your content is quickly delivered to users around the world. Data center location Currently, BabelBird uses two data centers of Alibaba Cloud: Hangzhou Data Center and Weihai Data Center The configuration of one south and one north can ensure the sustainability of services and disaster recovery needs. Database design Database type BabelBird Enterprise Drive uses various types of databases, and can also support Xinchuang's database products or large databases such as Oracle according to customer needs. The default product database of BabelBird is: The core database is a relational database mysql Auxiliary databases include: Redis database, MongoDB database Database schema Data architecture plays a vital role in enterprise network disk systems, ensuring high availability, performance and consistency of data. The following is the database structure of BabelBird: A. Master slave database architecture Master The main library is responsible for processing write operations, including users uploading files, modifying file information, etc. The main database provides high availability, data consistency and transaction processing. Slave The slave library is mainly used for reading operations, including file query and search. The slave library can provide load balancing and share the read load of the master library. Data synchronization: Use data replication mechanism to ensure that the data of the slave database and the master database are synchronized. Failover: The slave database can take over write operations when the master database fails, ensuring system continuity. B. Relational database (MySQL) Database design The database is designed to support file and user management, including the definition of tables such as file metadata, user information, and permissions. The relationship between data tables is clear, and foreign keys are used to maintain data consistency. Data redundancy The slave database in the master slave architecture is used for data redundancy to prevent data loss when the master database fails. The data synchronization mechanism ensures that the data of the slave database is consistent with that of the master database. C. NoSQL database (MongoDB) File metadata storage MongoDB can be used to store metadata of files, such as file name, size, version information, etc. MongoDB with elastic schema works well with changing data schemas. D. Cache database (Redis) Cache read data Redis is used to cache frequently read data to reduce the load on the database. Cached data can include user session information, popular files, access logs, etc. E. Data backup and recovery Backup strategy Regularly back up the data of the master and slave databases to ensure data security. Babel backup data is stored in reliable storage in various geographical locations. disaster recovery We develop detailed recovery plans that include steps and timelines for restoring data from backups. The Babel operations team regularly tests the disaster recovery process to ensure its effectiveness. F. Data consistency and transaction management Transaction support Use database transactions to ensure consistency across a range of operations, such as file uploads, sharing, and permission changes. Transactions should be managed correctly to avoid data corruption and inconsistency. Concurrency control Use database locks and isolation levels to manage concurrent access to avoid data races and conflicts. G. Monitoring and Performance Optimization Performance monitoring Implement database performance monitoring, including query response time, load, and resource utilization. Perform performance adjustments based on monitoring results to ensure database stability and performance. Query optimization Optimize complex queries to improve query performance, including index optimization and query plan analysis. These data architecture elements will help ensure that your enterprise network disk system can achieve high availability, excellent performance, and data security. With proper database design and maintenance, you can provide stable and reliable services that meet user needs and ensure data integrity. Data backup and recovery strategy (public cloud) A. Data backup Regular backup plan: BabelBird has a regular backup plan to ensure continuous backup of data (data backup in the early morning every day). Full backup and incremental backup: Babel adopts a combined strategy of full backup and incremental backup. A full backup backs up all data in the database, while an incremental backup only backs up data that has changed since the last backup to reduce backup time and storage space consumption. Multiple backup locations: The public cloud version of BabelBird has two geographical locations: Hangzhou computer room and Weihai computer room to cope with natural disasters or hardware failures. Cloud storage and remote data centers are common backup storage options. Automated backup: BabelBird's database backup adopts a fully automatic backup mechanism without manual intervention to improve reliability. Backup testing: We regularly test backups to ensure their integrity and availability. Test by restoring the backup data to a test environment and verifying the consistency of the data. B. Disaster recovery Recovery Plan: We create a detailed recovery plan that clearly identifies each step and responsibility. Make sure team members understand how to perform the recovery process. Backup and recovery testing: We regularly test our backup and recovery processes to ensure that data can be restored quickly and efficiently in the event of an emergency. Testing should include simulations of various failure scenarios. Backup monitoring: Monitor the running status of backup tasks, and automatically remind and report errors when problems occur to ensure the normal operation of the backup system. Disaster recovery team: We have a dedicated disaster recovery team, on call 24/7, responsible for taking action in emergencies to ensure the continued operation of the business. Communication plan: We have established an effective communication plan and automatic alert message delivery monitoring to inform relevant stakeholders about disaster events and recovery processes. Documentation and training: Ensure detailed documentation of recovery plans and procedures and provide training to team members on recovery strategies and procedures. The above strategies and efforts are based on ensuring the security and availability of database data and minimizing the risk of data loss and system downtime. Preview and transcode The file preview function allows users to open files directly on the network disk for preview without installing an application. In order to preview files on the web page and client and ensure the security of the file in a read only state (no content or source files can be obtained by others), file preview and transcoding are one of the core functions of the enterprise network disk system. This chapter will introduce how BabelBird implements online preview and transcoding of files to provide a more convenient user experience. File types supported for online preview Text, code and office files: Pdf, md, js, xml, htm, html, css, scss, jsp, c, cpp, java, php, m, h, hpp, mm, mail, msg, epub, doc, docx, ppt, pptx, xls, xlsx, txt, rtf, wps, wpt, dps, dpt, et, ett Xmind,km Optional support: (optional options require additional server and corresponding module fees) key, numbers, pages Audio and video: mp3, mp4, wav, asf, ape Optional support: (optional options require additional server and corresponding module fees) flv, f4v, mp4, m4v, webm, 3gp, 3gpp, wmv, avi, rm, rmvb, mkv, asf, mov, mpeg, swf, mpg, mts, m2ts, ogv 3D graphics: dae, 3ds, abc, fbx, mtl, obj, ply, stl, x3d Optional support 1: (Optional options require additional server and corresponding module fees) x3d, ply, 3ds, abc, m3d Optional support 2: revit, solidworks, 3DMax Image format: bmp, jpg, jpeg, gif, png, bmp, psd, tif, tiff, raw, cr2, arw, dng, nef, pef, dcm, ico dicom (medical images) Vector image: ai, svg, eps, indd, indt, idml CAD dwg, dwt, dxf, dcm Compressed file: Optional support: rar,zip Online preview tool (BabelBird Previewer) BabelBird Enterprise Drive uses the self developed BabelViewer online preview tool for online preview, which supports unified preview of different files after transcoding. Allows users to view file contents without downloading them locally. BabelViewer is a powerful H5 online preview tool developed for the needs of enterprise network disk users. It has the following features: Supports multiple libraries to facilitate rendering preview files in multiple ways. Supports multi layer technology, allowing multiple people to draw on the preview file. Supports online comments and can be discussed by multiple people in the comment area. The annotation list can be expanded to manage annotations of the current version and historical versions in a unified manner. Supports version comparison of multiple files. Vectorized rendering, vector files can be enlarged at high magnification without distortion. You can quickly switch to preview multiple files in the preview state. Use webGL technology to support online rendering of 3D files and online annotation of 3D files. File transcoding function Transcoding tools: Babel Transcoding Service integrates multiple transcoding tools to convert files from one format to another format that can be opened by Babel Previewer. Private deployment systems require a dedicated server (or virtual machine) to handle file transcoding. For example, convert high resolution pictures to web friendly JPEG format. Automatic transcoding: BabelBird has implemented an automatic transcoding function. Files uploaded by users will automatically be converted into appropriate formats and file list thumbnails will be extracted to save storage space and improve performance. For the transcoding processing of a large number of files uploaded at the same time, BabelBird has a unique scheduling mechanism, which strives to allow users to open previews in a more timely manner under limited resource usage. When the server is idle, user files uploaded will be automatically transcoded immediately and a preview file will be generated. When the server is busy, if the user uploads more than a certain number of files at the same time, these files will not be transcoded. When the user clicks on the file to prepare for preview, it will be added to the transcoding process first and the preview file will be generated in real time. Because the probability that users will preview a large number of files immediately after uploading them at once is very low, this setting can prevent users from being unable to open files that really need to be transcoded due to a busy server when uploading a large number of files at the same time. Transcoding queues and asynchronous processing: Add transcoding tasks to the queue and use asynchronous processing to perform transcoding operations to avoid blocking other system functions. Caching and performance optimization Preview and transcoding cache: Implement a caching mechanism to store transcoded files and preview data to reduce repeated transcoding and improve responsiveness. Load balancing: At the same time, the transcoding queue is configured with a load balancing policy to ensure that multiple preview and transcoding requests can be distributed to different processing nodes in a balanced manner. Performance optimization Performance monitoring: Real time performance monitoring, including transcoding speed, cache hit rate and response time, and automatic clearing of the queue and retry processing when errors occur. Notify operation and maintenance personnel via SMS of serious errors. Resource adjustment: Based on monitoring results and load conditions, preview and transcoding resources are dynamically adjusted to ensure high performance and availability. Integration testing Performance test: Conduct performance tests that simulate a large number of concurrent preview and transcoding requests to evaluate how the system performs under heavy load. office family files Babel supports online preview of files from the Microsoft office family and WPS. To ensure the display accuracy of office files, especially word files, Babel provides two ways to preview office files: Use the office transcoding module running on the Windows server to transcode the file and preview it (default). A window server needs to be deployed to generate preview files. It can open and preview word files and ppt files quite accurately with Microsoft Office or WPS. Supports using BabelViewer to annotate, discuss, circle, and compare versions of files. You can use the \"Zhichao AI\" document assistant function. Because there are no layout or font problems with Excel files, they are previewed using the preview function of the online office. All preview files can have embedded watermarks and can be saved as watermarked PDF files. Use the preview function of the online office running on the Linux server to provide online preview of office and wps files. For users who can only use Linux and do not have high requirements for the accuracy of the word file preview format. Due to differences in system fonts, online office parsing, etc., the online office in the Linux system cannot perfectly display the layout of the word file at 1:1. There will be slight differences in aspects such as bullet numbering, paragraph height, paging, and the position of inserted graphics. Because there are no layout or font problems with Excel files, they are previewed using the preview function of the online office. Word and ppt files opened using the online office preview function will no longer support the annotation function of the Babel previewer. The document assistant function of \"Zhichao AI\" is not supported. All preview files can have embedded watermarks and can be saved as watermarked PDF files. Taking into account the performance of the browser and the efficiency of the server, there will be a certain file size limit for online preview of office files. Files exceeding this limit cannot be previewed online. Private cloud users can customize these limits, but it is not recommended to increase them too high. The maximum previewable file size of Word (Document) documents is 200MB. The maximum preview size of PPT (slideshow) documents is 200MB. The maximum preview size of Excel (table) documents is 50MB. Pictures and graphics files Babel supports online preview of most image files, including psd, gif family, jpg family, bmp family, png, raw family (part), arw, tif, TIFF, dicom, ico and other files. It also supports the dicom format commonly used in medical graphics. And thanks to Babel's powerful image processing technology, Babel can preview ultra high resolution large pictures online in a 1:1 manner (optional component), annotate and discuss the pictures, and Babel supports reading the metadata of the photos. Image formats such as PSD, RAW, and BMP require automatic transcoding by the server before they can be previewed. Under normal circumstances (the large image display module is not turned on) large images with a resolution exceeding 4K will be processed by the server into a size and format that is convenient for web page display. After turning on the large image display module, the server will cut the large image into several small pieces and load them into 1:1 displays, which will consume a lot of server resources. Pictures with transparent backgrounds such as PNG can also show transparency in BabelBird, and the background can be changed. The BabelBird system will read image metadata information for search, query, and sorting. This information includes: resolution, size, shooting equipment, shooting time, shooting location. All previewable image formats will generate thumbnails for quick search in file list display and waterfall flow mode display. All image formats support annotation discussion, circle drawing and version comparison in BabelViewer. If the watermark function is turned on, the server will preprocess the previewed image and embed the watermark in the image. All image files can be saved as watermarked PDF files. BabelBird can also well support online preview of vector graphics, including but not limited to ai, dwg, dcm, dxf, dwt, pdf, eps, svg, idml, indd... and other vector graphics formats. More importantly, Babel can open documents in these formats in vector rendering, which means that such graphics can be enlarged dozens of times in Babel without blurring or distortion. AI, eps, ind and other files need to be automatically transcoded by the server before they can be previewed. Displayed in vector format, supporting changing background color. The graphics will not be distorted or blurred after enlargement. Other features are the same as images. It also supports embedding watermarks, saving as watermarked PDF, annotating discussions in BabelViewer, circle drawing and version comparison, and generating file list previews. 3D and CAD files Thanks to BabelViewer's support for 3D formats, we support online preview of dae, 3ds, abc, fbx, mtl, obj, ply, stl, x3d and other 3D graphics by default, and support annotation discussions in 3D space. Currently, BabelBird Previewer only supports single file 3D graphics. If the file has plug in files such as plug in skin, it will only be able to load the model itself. 3D files currently do not support generating previews, but custom development is supported if there is a need for this. 3D files can be rotated, enlarged, reduced, and split in the Babel Previewer, and annotation discussion points can be established. The system will remember the viewport when the annotation was created. Clicking an annotation will automatically rotate to the perspective when the annotation was created. If you need to support professional formats such as Revit, Solidworks, 3DMax, etc., private deployment users can choose to access third party 3D online display and transcoding plug ins (such as Autodesk viewer), which will incur related fees. Previewing 3D files on mobile devices is currently not supported. Only supports previewing 3D files on web pages and clients. Babel supports preview of CAD files. Such as: dwg, dwt, dxf formats. Currently on the public cloud, Babel provides powerful CAD preview services to professional and enterprise version users. Private users who want to preview CAD files need to purchase the corresponding CAD transcoding service privatization authorization. Babel CAD preview supports CAD version R12 2021. CAD files can generate preview thumbnails for file list and waterfall mode. Compatible with Tianzheng full professional T20V7 version. Supports previewing and annotating CAD files in browsers, clients, and mobile terminals. Supports drawing browsing above 100Mbps. Layer open/hide/multi select/select all. Layout switching, view pan, zoom, change background color, eagle eye view. Audio and video transcoding Without using a transcoding server BabelBird can directly play video files that support the HTML5 standard online without the need for transcoding services. The supported formats are as follows: Video file formats MP4: MPEG 4 Part 14, supports H.264 encoding. Almost all browsers support this format. WebM: A format developed by Google that uses VP8 or VP9 encoding and can be played in most modern browsers Ogg: Open media format, using Vorbis encoding, can be played in most modern browsers. Audio file formats MP3: MPEG 1 or MPEG 2 Audio Layer III, can be played in almost all browsers. AAC: Advanced Audio Coding, can be played in most modern browsers. Ogg: Open media format, using Vorbis encoding, can be played in most modern browsers. WAV: Waveform Audio File Format, can be played in almost all browsers, but the file size is large and not suitable for playing on the Internet. Compatibility Video compatibility Audio compatibility When using a transcoding server If you need to use BabelBird to manage and query a large number of video materials, you need to build a dedicated video transcoding server and purchase the corresponding video transcoding module authorization. (Currently this service only supports private deployment users) BabelBird video transcoding module uses FFmpeg solution. FFmpeg supports more than 40 encodings such as MPEG, DivX, MPEG4, AC3, DV, FLV, etc., and more than 90 decodings such as AVI, MPEG, OGG, Matroska, ASF, etc. FFmpeg supports more than 280 types of codecs, covering almost all common audio and video encoding formats, and can decode almost all audio and video. Hardware configuration required for video transcoding server Video transcoding is a service that consumes considerable computing resources and requires a dedicated physical machine to perform the transcoding operation. At the same time, server performance requirements are related to the type, duration and bit rate of the video that needs to be transcoded. Based on the daily conversion of 50 hours of HDR 4K video (using CUDA) to 1080P H.264 AC3 MP4, the required server hardware configuration is as follows: Server type Configuration requirements Operating system Server purpose Notes Video transcoding server Xeon Intel E5 2630v3CPU 2 64G memory 2TB SSD hard drive + Nvidia Tesla M4 4G graphics card Linux Video transcoding server Using GPU (CUDA) The transcoding time required varies depending on the video bit rate. Under normal circumstances, it takes 8 seconds to transcode a 100 second 2K video into 1080P MP4 (using the hardware configuration above). If there are many videos being transcoded at the same time, the server will perform multi thread queuing processing. After using the transcoding server, the video file can be played after the transcoding is completed, and the thumbnails can be viewed in the file list. Security Secure architecture Security is key to business! Babel prioritizes security from product design to architecture construction and server management, and includes many important security features. You can control the access behavior of each file and each member, add file watermarks, view access logs, classify important files into archives, and set encryption levels and security policies for files and departments... This series of measures can protect important digital assets to the greatest extent. At the same time, BabelBird uses EV SSL certification with the highest security level, bank level encrypted transmission, and distributed backup in multiple computer rooms to ensure that your data is safe and worry free. These measures have enabled BabelBird to obtain QUALYS security A+ certification, and we also have ISO27001 information security quality system certification. Since its launch, BabelBird has implemented full link encrypted transmission and storage from uploading, downloading, to disk. With detailed processing of rights management and file management, as well as risk analysis and corresponding functional response strategies encountered in various usage scenarios, BabelBird has become one of the most secure enterprise network disks on the market. Figure: Babel bird data transmission link Firewall, bastion host, VPN, SSL... In terms of transmission and server deployment architecture, we have more and more means to ensure the data security of the system. However, according to our many years of experience in providing enterprise security services, 80% of data breaches often originate from insider leaks and management chaos. Even if the system is physically isolated, there is no way to eliminate the risk of data leakage. Babel has considered this from the beginning of product design, providing a variety of safety designs and functions from the perspectives of management, personnel and equipment. A variety of optional settings and solutions are also provided at the contradiction between ease of use and security. Ensure data security as much as possible from the product structure and usage logic. Significantly eliminate the risk of data leakage due to insider negligence or sabotage. User Authentication and Authorization (SSO) Own user system Babel Free User System Authentication Types Account type Verification method Remarks Email Password, verification code Public cloud needs to be bound to a mobile phone number for verification Mobile phone number (global) Password, verification code The private cloud needs to be connected to the SMS sending platform User ID Password Only supported by private clouds. If you forget your password, it can only be reset by the administrator. When logging in for the first time, you will be asked to forcefully reset the password WeChat Scan code, APP jump (mobile) Only supported by public cloud, need to bind mobile phone number for verification Babel supports a mix of authentication types. Multi factor authentication (MFA) could be mandated to improve security Hybrid authentication: When using single sign on (SSO), it supports using your own user system and SSO at the same time. Users can choose to log in using their own credentials or log in through SSO (such as using corporate WeChat to scan the QR code to log in or using the account password to log in). Single Sign On (SSO) integration Single Sign On (SSO) integration is a key feature in enterprise network disk products. It allows users to access multiple different applications and services after one authentication, improving user experience and security. Babel supports OAuth2.0, CAS and other methods to integrate single sign on, and has been actually used in docking with various systems. Supported SSO standards and protocols BabelBird Enterprise Drive supports a variety of SSO standards and protocols, including but not limited to the following: ADFS integration: Babel supports integration with Active Directory Federation Services (ADFS), which makes Windows Authentication based SSO possible. This integration allows users within the enterprise to log in using their Windows credentials. AD domain controller integration: Babel also supports integration with an enterprise's local Active Directory (AD) domain controller. This allows internal enterprise users to log in using their local domain credentials. Enterprise WeChat integration: BabelBird supports docking with corporate WeChat, which allows companies to directly use corporate WeChat accounts to scan QR codes to authenticate and log in. And you can simultaneously import WeChat's organizational structure and users, use Enterprise WeChat to send notifications, and access BabelBird in the workbench. DingTalk integration: BabelBird supports docking with DingTalk, which allows enterprises to directly use DingTalk accounts to scan and authenticate login. You can also import DingTalk's organizational structure and users simultaneously, use DingTalk to send notifications, and access BabelBird in the DingTalk workbench. Feishu integration: BabelBird supports docking with Feishu, which allows enterprises to directly use Feishu accounts to scan and authenticate login. You can also import Feishu's organizational structure and users simultaneously, use Feishu to send notifications, and access BabelBird in the Feishu workbench. Integrated documentation: The integration of AD Domain Control, Enterprise WeChat, DingTalk, Feishu, and Zhiyuan OA has been embedded in the privatized version of BabelBird. After purchasing the corresponding modules, users only need to configure them according to the corresponding documents before they can be used. For relevant configuration documents, please consult BabelBird customer service personnel. Third party SSO integration: If your organization uses a third party SSO provider (such as Okta, OneLogin, Auth0, Qianfan, Panwei, etc.), we also support product integration with these providers. This means that external users can log in with SSO through these vendors' products. But this requires secondary development and a certain fee. Third party own user system integration We understand that many organizations may have their own user systems at the same time, so our SSO integration supports hybrid authentication: Hybrid authentication: Our system allows users to choose between logging in using their own credentials or using SSO. This provides maximum flexibility to adapt to different user needs. User mapping and synchronization: We ensure that user accounts in our own user system are synchronized with user accounts in SSO. This means that a user's attributes and permissions remain consistent across the system. Security and authorization We pay great attention to the enforcement of security and authorization policies to ensure that only authorized users have access to resources: Authentication strategy: We support flexible authentication strategies, including advanced options like multi factor authentication (MFA). This helps ensure that the user's identity is properly verified. Authorization and access control: We allow administrators to configure and manage user access rights, including authorization of files and resources. This ensures that only authorized users have access to sensitive data. Users imported from other platforms will only have the initial permissions of their department (default is department member). Administrators can uniformly change the initial permission scope of imported users by customizing the \"department member\" role permissions. User experience We focus on user experience and strive to provide a seamless login experience: Login page: Our login page is clear and intuitive, giving users the option to choose different login methods. Users can choose to log in using SSO or log in with their own credentials. At the same time, we also support using the user's own login page for single sign on system (such as the ADFS system authentication page) Single point of logout: If the connected single sign on system (SSO) supports single logout, we can also support single logout, which means that users can log out in any connected application, and the system will automatically log out of sessions in other applications. Access control list (ACL) design Overview In BabelBird Enterprise Drive, permission management is a core component to ensure the security and accessibility of files and resources. ACL (Access Control List) is used to define the access rights of users and roles to resources in different departments. This chapter will introduce our ACL design in detail, including role management, user assignment, role permissions and change management. role management Role definition: We allow administrators to customize roles. Each role represents a set of permissions. There are 32 optional combinations of permissions to form a role. Each role should have a clear name and description so administrators and users understand its functionality. Permission assignment: Each role is assigned specific permissions, which determine the role's ability to operate within the department. Permissions should be carefully chosen to ensure that users have the necessary permissions but are not over authorized. User management User role assignment: Each user can be assigned one or more roles, which determine the user's permissions in different departments. Allow one user to have different roles in different departments to accommodate diverse needs. Association between users and departments: Users should be associated with the departments they belong to so that appropriate permissions are automatically assigned based on department roles. Users can only access the department in which they are located, and have roles that determine access rights within the department. Whether you can access sub departments is also determined by role permissions (roles have permissions to access sub departments). Role permission management Role permission definition: Each role has clearly defined permissions, including readable, writable, deleteable, shareable and other operations. Roles can be added or deleted as needed. Permission inheritance: Our system supports inheritance of permissions. When a user is assigned to a role, they automatically inherit the permissions of that role. This reduces the effort of manually assigning permissions while ensuring consistency. Change management Role permission changes: When an administrator changes the permissions of a role, the permissions of all users with that role in the department also change accordingly. We will log these changes in detail for auditing and troubleshooting purposes. Permission audit: Security administrators can regularly audit roles and user permissions to ensure the accuracy and security of authorization. Permissions that are no longer needed should be canceled promptly. security Access control: The ACL system of BabelBird Enterprise Drive will strictly control users and roles' access to resources. Only authorized users with a role in the department can access department files. Departments are isolated from each other, and different confidentiality levels (department security policies) can be set to protect department files. Audit and Monitoring: All permission changes and role changes will leave log records. Convenient management and query. Implement monitoring and auditing mechanisms to monitor permission changes and access activities to detect and respond to potential risks in a timely manner. best practices Principle of least privilege: Follow the principle of least privilege, which means giving users and roles the minimum permissions required to reduce potential security risks. Department files can use file access control to accurately increase the permissions of a certain member (or a certain role) and set the permission validity period. Regular review: Regularly review role and permission configurations to ensure system security and performance. future expansion Multi tenant support: Public cloud systems support multi tenant control. Private cloud considers extending the ACL system to a multi tenant environment to support the needs of multiple customers or organizations. Data encryption Data transmission encryption (SSL/TLS) encryption protocol In BabelBird Enterprise Drive, we attach great importance to the security of data transmission. In order to ensure that data is protected during transmission, we use the Secure Socket Layer (SSL) protocol to implement transmission encryption. HTTPS: We use the HTTPS protocol, which is a secure version of HTTP, to encrypt all data transfers. HTTPS provides end to end data encryption through the TLS/SSL protocol, preventing third party malicious users from intercepting or eavesdropping on transmitted data. Certificate management SHA 256 certificate: Our SSL certificates are hashed with SHA 256, a powerful hashing algorithm that provides advanced security and integrity protection. SHA 256 certificates are critical for verifying the server's identity and protecting data transfers. Certificate update: BabelBird Enterprise Drive will regularly update the SSL certificate to ensure the validity and security of the certificate. We monitor certificate expiration dates and renew them in advance. Data encryption Data transmission encryption: All data transmission between BabelBird Enterprise Drive and user terminals will be encrypted by TLS/SSL. This includes user logins, file uploads and downloads, and the transmission of any sensitive data. Data integrity protection: TLS/SSL not only provides data encryption, but also verifies the integrity of the data during transmission to prevent data from being tampered with or damaged. security Strict encryption policy: We follow strict encryption policies to ensure that all data transmissions pass through secure channels and cannot be accessed by unauthorized parties. Protect user privacy: Encryption of data transmission helps protect users' privacy and sensitive information, including personally identifiable information and confidential documents. best practices Security upgrade: We will continue to monitor new security standards and best practices to ensure that the security of data transmission encryption is continuously improved. Security audit: We conduct regular security audits and vulnerability scans to ensure that our encryption mechanisms are not affected by potential threats. Pictured: BabelBird receives A+ security verification from Qualys SSL Scan Data storage encryption Overview In BabelBird Enterprise Drive, we use advanced block encryption technology to ensure the security and integrity of files. We use chunked encryption to break files into small chunks, each chunk is hashed and then stored in an object storage system. This technology ensures that even if control of the server or the hard drive is compromised, the attacker cannot obtain the complete file contents. Block encryption File chunking: Files uploaded to BabelBird Enterprise Drive will be divided into several small chunks (chunks). The size of each tile can be configured based on system needs to balance performance and security. Hash encryption: Each small block is hashed, using a powerful hashing algorithm to ensure data integrity. The hash value will be stored along with the stored chunk for subsequent verification. Storage security Object storage: The encrypted small blocks will be stored in the object storage system of BabelBird Enterprise Drive to ensure high availability and data redundancy. Unrecoverable encryption: We use an irreversible hash encryption algorithm to ensure that the small blocks stored cannot be restored to the original file content to ensure the security of file storage. Secure transmission: Small pieces of data are also encrypted when transferred to the object storage system to prevent man in the middle attacks. File download Temporary download link: When a user needs to download a file, the authentication system will dynamically combine the chunks to form a temporary download link. This link is unique and only valid for a short period of time for downloading. To download again, you need to regenerate the download link. This setting prevents files from being exposed by obtaining download links. Download decryption: When the user requests a download, BabelBird Enterprise Drive will decrypt the chunked data on the server side and then merge it into a complete file. This ensures that the file will not be exposed to any unauthorized accessor even if the hard drive is illegally read while the file is being stored. security Data isolation: Blocked encryption technology breaks data into small chunks, each of which is encrypted with an independent hash to prevent the entire file from being exposed. Irreducibility: The use of an irreversible hash algorithm ensures that the data is irreducible. Even if an attacker obtains a small piece of data, the original file cannot be restored due to missing data. Prevent data leakage Security audit log Overview In BabelBird Enterprise Drive, we emphasize the traceability and security of data access and operations. In order to achieve this goal, we have established a powerful access log system to record historical access logs of the entire system. These logs include file uploads and downloads, permission changes, user discussion comments, file additions, deletions, modifications, approvals, and department changes. This chapter will introduce our security audit log system and role management in detail. Access log function Comprehensive logging: Our log system records various access behaviors of the entire Babel Enterprise network disk, ensuring that every operation can be traced and audited. Recorded operations include but are not limited to file management, authority control, user operations and department management. For more information about BabelBird logs, please refer to: Logs and Reports chapter. Default save time: By default, we save complete access logs for 90 days. This ensures that sufficient historical data is available for auditing and inspection. Expandable storage time: If needed, administrators can extend the retention period of access logs based on specific compliance requirements (supported only on privatized systems). Third party log management system Integrated support: BabelBird can connect to third party log management systems to import access log data to external log platforms for further analysis and long term storage. Security administrator role Security Officer: Security officers have advanced permissions and can view and manage files of all departments at the front desk. In the enterprise management background, the security officer has the following permissions: Develop company security policy (exclusive authority). Manage organizational structure. Member management. Permission management. Security Auditor: Security auditors can view and manage all department files from the front desk. In the enterprise management backend, security auditors have the following permissions: Review corporate security policies. Review the organizational structure. View member permissions. View permission management. View file access logs. security Data isolation: Security audit log data is strictly isolated and only authorized administrators can access and manage them. Confidentiality: The roles of security security officers and security auditors are carefully designed. One is responsible for security policy and the other is responsible for security auditing. They supervise each other to ensure data confidentiality and compliance. Expand Automated alerts: Supports automated alarm mechanism, and monitoring items can be added to promptly notify super administrators when abnormal activities are discovered. The security audit log system of BabelBird Enterprise Drive, including functions, role management and security measures, ensures the traceability of data access and operations, and supports integration with third party log management systems to further improve security and compliance. Security review and testing Penetration testing Test delegate: BabelBird Enterprise Drive will regularly conduct penetration tests by itself or entrust third party organizations, such as NSFOCUS Technology, to conduct penetration tests to evaluate the security of the system. The goal of penetration testing is to use cutting edge attack techniques, mature hacker attack methods, and standard software testing techniques to test the security of the specified system and discover potential security vulnerabilities and risks. Testing phase: Penetration testing includes the following processes: Information collection: Testers collect necessary information, such as IP addresses, DNS records, software version information, IP segments, and public information. Penetration testing: Testers attempt to hack into networks and systems based on the results of the information gathering phase. If successful, normal permissions may be obtained. Flaw Exploitation: A tester attempts to escalate privileges to gain full control of the system. If necessary, they may go back to the information gathering phase and start over. Collection of results: Testers classify and organize the problems discovered in previous stages, such as weaknesses and vulnerabilities, and display them in a centralized manner. Threat analysis: Testers classify the threats found and analyze their potential impact. Output report: Testers write intuitive penetration testing service reports based on the results of testing and analysis. Main goals of penetration testing: Discover security vulnerabilities and potential risks in systems. Evaluate the security of the system, including authentication, access control, data protection, etc. Provides suggestions for improvements to enhance the security of the system. The results of the test will help us take appropriate measures to fix the problems found and improve the overall security of the system. best practices BabelBird Enterprise Drive will conduct regular penetration testing to maintain the security of the system. Use a combination of automated tools and manual testing to increase the comprehensiveness and accuracy of penetration testing. After the test is completed, make timely corrections based on the report to ensure the safety of the system. future expansion We will continue to evolve our penetration testing processes to adapt to evolving security threats. Consider introducing advanced analysis tools to more deeply assess the security of your system. Security vulnerability scanning In order to maintain the security of BabelBird Enterprise Drive, we conduct security vulnerability scans regularly. This measure is designed to automatically detect potential security vulnerabilities in the system and problems that may lead to security threats. We rely on professional scanning tools (such as Qualys, Rapid7 InsightVM, OpenVAS) to ensure that the system continues to remain in a highly secure state. Scanning process Security vulnerability scanning includes the following key stages: Regular scan: We scan our systems for security vulnerabilities on a regular basis, usually at scheduled intervals. Scanning tools automatically perform a series of tests to find potential vulnerabilities. Scan target: The targets of security vulnerability scanning include various aspects such as applications, operating systems, and network devices in the system. Scanning ensures the overall security of the system. Scan results: Scanning tools will identify and report vulnerabilities found in the system. The report will include the type of vulnerability, its severity, and possible remediation recommendations. Fixes: Based on the scan results, we take necessary remediation measures to address the discovered vulnerabilities and issues to ensure the security of the system. BabelBird safety related features" }, { "lang": "en", "slug": "ai-overview", "title": "Zhichao AI Overview", "description": "Completely introduces the positioning, modules, capability boundaries, permission control, training materials and applicable scenarios of Zhichao AI.", "category": "Zhichao AI", "top_category": "使用指南", "keywords": [ "Zhichao AI", "AI knowledge base", "AI search", "AI image search", "agent", "Document Assistant", "AI customer service", "MCP" ], "url": "en/ai-overview.html", "source": "content/en/ai-overview.md", "summary": "Zhichao AI Overview Zhichao AI is a collection of AI capabilities built by BabelBird Enterprise Drive around enterprise documents, knowledge base, search, customer service and data analysis. It is not an isolated chat tool, but is combined with Babel's file storage, permission system, search engine, material library, project collaboration, online preview and private deployment capabilities to allow AI to work on the company's existing data. Zhichao AI Column The Zhichao AI column aggregates entrances such as AI search, image search, agents, enterprise AI assistants, and knowledge bases. Module Overview Module Main capabilities Typical scenarios AI Search Learn corporate documents, search and", "headings": [ { "level": 1, "title": "Zhichao AI Overview", "id": "zhichao-ai-overview" }, { "level": 2, "title": "Module Overview", "id": "module-overview" }, { "level": 2, "title": "Standard version module list", "id": "standard-version-module-list" }, { "level": 2, "title": "Core Competencies", "id": "core-competencies" }, { "level": 2, "title": "Relationship with enterprise network disk", "id": "relationship-with-enterprise-network-disk" }, { "level": 2, "title": "Permission awareness", "id": "permission-awareness" }, { "level": 3, "title": "The three main modules of Zhichao AI", "id": "the-three-main-modules-of-zhichao-ai" }, { "level": 3, "title": "Technical Solutions", "id": "technical-solutions" }, { "level": 3, "title": "Advantages", "id": "advantages" }, { "level": 2, "title": "Permissions and usage boundaries", "id": "permissions-and-usage-boundaries" }, { "level": 2, "title": "Related information", "id": "related-information" } ], "images": [ { "src": "../assets/images/ai-column.webp", "alt": "Zhichao AI Column", "caption": "The Zhichao AI column aggregates entrances such as AI search, image search, agents, enterprise AI assistants, and knowledge bases." } ], "text": "Zhichao AI Overview Zhichao AI is a collection of AI capabilities built by BabelBird Enterprise Drive around enterprise documents, knowledge base, search, customer service and data analysis. It is not an isolated chat tool, but is combined with Babel's file storage, permission system, search engine, material library, project collaboration, online preview and private deployment capabilities to allow AI to work on the company's existing data. Zhichao AI Column The Zhichao AI column aggregates entrances such as AI search, image search, agents, enterprise AI assistants, and knowledge bases. Module Overview Module Main capabilities Typical scenarios AI Search Learn corporate documents, search and answer questions in natural language, support questioning, source citation, multi modality and authority judgment Corporate knowledge query, system query, project data retrieval, technical data Q&A AI Image Search Search for images in the network disk through text description or uploaded images. The search scope is filtered by permissions Material library, brand assets, design gallery, image files Intelligent Data Assistant Analyze Excel/table data, query, analyze, and generate charts across multiple Excel files, and support third party URL data sources Sales reports, project ledgers, supply chain data, and operational statistics Customized agent and knowledge base robot Customized persona, prompt words, response logic, learning folders, industry templates, multi Agent and website embedding Enterprise knowledge base, online customer service, industry assistant, internal expert system Enterprise AI Assistant Integrate most Zhichao applications in a conversational manner, answer corporate document knowledge points, and search network disk files in multiple dimensions Daily office assistant, file search, cross data Q&A AI Customer Service Learn product descriptions, FAQs, customer service documents, and generate intelligent customer service that can provide external services Official website customer service, product support, pre sales Q&A, and after sales knowledge base Standard Edition Modules Entrance, usage and functional boundaries of 16 standard modules Administrator selection, implementation scope confirmation, employee training AI deployment and customization Private deployment, dedicated agents, industry applications and development of AI applications according to enterprise processes Private cloud, dedicated model services, industry solutions Standard version module list The following modules constitute the main functional scope of Zhichao AI Standard Edition. Actual entry and availability may be affected by version, entitlement, and deployment configuration. Number Module Entry Function 1 Zhichao AI Assistant Top right AI assistant entrance Conduct AI conversations based on the enterprise knowledge base, and answer questions in combination with online searches 2 AI search Search bar The search results include AI search content and use natural language to find corporate information 3 Zhisou Zhichao AI column Provides question answering, in depth research and article writing capabilities 4 Wensoitu Zhichao AI Column Search for pictures in the network disk through text description 5 Image search Zhichao AI column, image thumbnail entrance Match similar images in the network disk by uploading or selecting images 6 Image OCR Search, Zhichao AI column Recognize the text in the image and let the image content participate in the search 7 Document Assistant File Preview Interface Summary, Q&A and reading assistance based on the current document 8 AI automatic tagging File list Match the closest tag in the tag library for the selected document 9 Table Q&A Excel file preview interface, Zhichao AI column Q&A, table generation and function operations based on Excel 10 Deep thinking AI assistant, form question and answer, document assistant Switch to a deeper reasoning mode for complex problems 11 Internet search AI assistant Search Internet content and answer with external knowledge 12 In depth research Intelligent search in the Zhichao AI column Research based answers are formed through multiple rounds of search and comprehensive sorting 13 Enterprise knowledge base Backend server Enterprise documents are automatically stored in the database to form a questionable and searchable knowledge base 14 Knowledge base robot Zhichao AI column \"Create an agent\" Create a customizable agent or knowledge base robot 15 PDF image search Search bar Search image content in PDF documents with images 16 MCP interface Interface Provides knowledge base access and network disk file operation capabilities to OpenClaw and other AI applications Core Competencies Enterprise specific AI assistant and AI customer service, which can serve internal employees or external customers through embedded codes. AI search and dialogue based compound query, users can inquire about information, find files, check systems, and check projects just like asking colleagues. AI automatic labeling and file classification is used to reduce the cost of manually organizing materials, information and archived documents. Customizable AI knowledge base and agents, you can specify learning folders, and you can also configure different assistants for different knowledge areas. AI image search, image search, text image search, OCR and multi modal understanding, used for pictures, materials and scans. AI document reading assistant, used to summarize single documents, extract key points, and answer document questions. Intelligent data assistant supporting Excel for multi table cross analysis, query and chart generation. Support on demand development and privatized deployment, adapting to industry knowledge, enterprise processes and deployment security requirements. Relationship with enterprise network disk The value of Zhichao AI comes from the combination of \"AI + enterprise file system\". Traditional general purpose chat tools usually don’t know where the company’s internal files are, who has permission to see them, which version is the latest, and which files belong to the same project; Zhichao AI can work around the files, projects, departments, material libraries and permission systems in BabelBird. For businesses, this means that AI doesn’t just answer general knowledge, but can provide help around the company’s own data and business context. Permission awareness Zhichao AI's search, question and answer, agents, and knowledge base need to be linked to the BabelBird permission system. What answers a user can get from AI should be limited by the following factors: The user's role within the enterprise, department, project, and folder. Access control, sharing permissions and validity period for a single file or folder. The learning scope specified by the administrator for the agent, knowledge base, or AI assistant. Enterprise external sharing, downloading, previewing, watermarking, confidentiality and auditing strategies. Configuration strategies for models, indexes, vector libraries and third party APIs in private deployments. Zhichao AI is the AI ​​platform of BabelBird Enterprise Drive, including three main modules: Zhichao AI customer service, Zhichao AI knowledge base, and Zhichao AI document assistant. These modules combine large model APIs and custom training to meet the enterprise's intelligent customer service, file content analysis and question answering needs. The three main modules of Zhichao AI Zhichao AI customer service: This module serves as the AI customer service of the enterprise. BabelBird Enterprise Drive itself also uses this module to answer the problems encountered by users when using BabelBird Enterprise Drive. We also open this service to corporate customers. Companies can provide product manuals, FAQs, customer service documents and other materials to Zhichao AI for learning and fine tuning to meet corporate customer service needs. Enterprises can also embed Zhichao AI's code blocks into their websites to quickly establish an external intelligent customer service system. Zhichao AI customer service can significantly reduce customer service costs and save time and resources. Zhichao AI Document Assistant: This module is used to answer questions about a single document. By analyzing the document content, Zhichao AI can answer various questions about the document content, from summarizing to revealing key findings. Users can ask questions to the AI ​​instead of having to read lengthy documents themselves, improving work efficiency. Zhichao AI knowledge base: This module allows companies to customize their own AI assistants. The Zhichao AI team will help prepare training sets and adjust parameters based on the company's data, thereby establishing an exclusive AI model that can provide answers within the scope of permissions for people with different permissions on BabelBird. It can be used as a corporate knowledge base assistant in the form of questions and answers. Technical Solutions Answer questions intelligently: Zhichao AI uses large models and custom training to ensure accuracy. It also uses small models to assist the work of large models, reducing problems such as talking nonsense, pretending not to understand, or leaking secrets. In addition, Zhichao AI follows BabelBird’s authority management mechanism to ensure that users can only obtain answers within their authority. Automatic learning: Zhichao AI can accumulate knowledge by studying the files provided by users and provide users with more accurate answers. All documents participating in training are specified and agreed to by the user to ensure data privacy and compliance. Advantages Reduced customer service costs: Zhichao AI customer service can significantly reduce the customer service costs of enterprises. There is no need to train personnel on a large scale, and AI can provide answers at any time. Quick question answering: Zhichao AI can answer users' questions instantly, improving work efficiency. Document content analysis: Zhichao AI Document Assistant can quickly analyze document content to help users quickly obtain information without reading the entire document. Customized AI assistant: Enterprises can customize their own AI assistant for the Zhichao AI knowledge base according to their own needs to meet specific knowledge management and question answering needs. Permission management: Zhichao AI is able to provide answers in different ranges based on user permissions to ensure data security and compliance. Permissions and usage boundaries Zhichao AI's answers, searches, and file references should follow BabelBird's existing permission system. Users can only access content within their account, department, project, share, and file access controls. Materials that participate in learning, training, indexing, or Q&A should be designated by the enterprise or administrator; all files should not be considered public knowledge sources by default. External customer service, website embedding, third party data sources, privatized models, and GPU computing power are optional deployment or customization capabilities and should be subject to actual authorization, implementation plan, and enterprise configuration. When AI answers involve high risk content such as contracts, finance, medical care, law, and engineering safety, the AI ​​output should be used as auxiliary information and reviewed by professionals. Related information Permission system Security and Audit FAQ: Deployment, AI and technical issues Public introduction:" }, { "lang": "en", "slug": "ai-standard-modules", "title": "Standard version module", "description": "The standard version module summarizes 16 entrances, functions and usage scenarios of Zhichao AI.", "category": "Zhichao AI", "top_category": "使用指南", "keywords": [ "Zhichao AI", "Standard version module", "MCP", "Knowledge base robot" ], "url": "en/ai-standard-modules.html", "source": "content/en/ai-standard-modules.md", "summary": "Standard version module The standard version module summarizes 16 entrances, functions and usage scenarios of Zhichao AI. Standard version module Interface diagram of the standard version module. Standard version module list The following modules constitute the main functional scope of Zhichao AI Standard Edition. Actual entry and availability may be affected by version, entitlement, and deployment configuration. Number Module Entry Function 1 Zhichao AI Assistant Top right AI assistant entrance Conduct AI conversations based on the enterprise knowledge base, and answer questions in combination with online searches 2 AI search Search bar The search results include AI search content and use n", "headings": [ { "level": 1, "title": "Standard version module", "id": "standard-version-module" }, { "level": 2, "title": "Standard version module list", "id": "standard-version-module-list" }, { "level": 2, "title": "Module relationship", "id": "module-relationship" }, { "level": 2, "title": "Implementation suggestions", "id": "implementation-suggestions" }, { "level": 2, "title": "Permissions and usage boundaries", "id": "permissions-and-usage-boundaries" }, { "level": 2, "title": "Related information", "id": "related-information" } ], "images": [ { "src": "../assets/images/ai-column.webp", "alt": "Standard version module", "caption": "Interface diagram of the standard version module." } ], "text": "Standard version module The standard version module summarizes 16 entrances, functions and usage scenarios of Zhichao AI. Standard version module Interface diagram of the standard version module. Standard version module list The following modules constitute the main functional scope of Zhichao AI Standard Edition. Actual entry and availability may be affected by version, entitlement, and deployment configuration. Number Module Entry Function 1 Zhichao AI Assistant Top right AI assistant entrance Conduct AI conversations based on the enterprise knowledge base, and answer questions in combination with online searches 2 AI search Search bar The search results include AI search content and use natural language to find corporate information 3 Zhisou Zhichao AI column Provides question answering, in depth research and article writing capabilities 4 Wensoitu Zhichao AI Column Search for pictures in the network disk through text description 5 Image search Zhichao AI column, image thumbnail entrance Match similar images in the network disk by uploading or selecting images 6 Image OCR Search, Zhichao AI column Recognize the text in the image and let the image content participate in the search 7 Document Assistant File Preview Interface Summary, Q&A and reading assistance based on the current document 8 AI automatic tagging File list Match the closest tag in the tag library for the selected document 9 Table Q&A Excel file preview interface, Zhichao AI column Q&A, table generation and function operations based on Excel 10 Deep thinking AI assistant, form question and answer, document assistant Switch to a deeper reasoning mode for complex problems 11 Internet search AI assistant Search Internet content and answer with external knowledge 12 In depth research Intelligent search in the Zhichao AI column Research based answers are formed through multiple rounds of search and comprehensive sorting 13 Enterprise knowledge base Backend server Enterprise documents are automatically stored in the database to form a questionable and searchable knowledge base 14 Knowledge base robot Zhichao AI column \"Create an agent\" Create a customizable agent or knowledge base robot 15 PDF image search Search bar Search image content in PDF documents with images 16 MCP interface Interface Provides knowledge base access and network disk file operation capabilities to OpenClaw and other AI applications Module relationship These 16 modules can be divided into four groups: the first group is dialogue, search, document reading and form question and answer for ordinary users; the second group is multi modal retrieval for images, PDF images and OCR; the third group is enterprise knowledge base, knowledge base robots and agent configuration for administrators and implementation teams; the fourth group is MCP interfaces, third party data sources and on demand development capabilities for development and integration. Implementation suggestions First, confirm whether the company needs to solve most problems: \"finding files\", \"reading documents\", \"doing customer service\", \"analyzing forms\" or \"external knowledge base\". AI assistant, AI search, document assistant and form Q&A are given priority to internal employees. Focus on enabling text search, image search, image OCR and PDF image search for material or brand teams. Focus on configuring knowledge base robots and custom agents for customer service, pre sales, training and institutional Q&A scenarios. For scenarios that require external AI applications to access the knowledge base or perform file operations, plan MCP interface permissions and audit policies. Permissions and usage boundaries Zhichao AI’s answers, searches, and file references should follow Babel’s existing permission system. Users can only access content within their account, department, project, share, and file access controls. Materials used for learning, training, indexing, or Q&A should be specified by the enterprise or administrator; all files should not be considered public knowledge sources by default. External customer service, website embedding, third party data sources, privatized models and GPU computing power are optional deployment or customization capabilities and should be subject to actual authorization, implementation plan and enterprise configuration. When AI answers involve high risk content such as contracts, finance, medical, legal, and engineering safety, the AI ​​output should be used as auxiliary information and reviewed by professionals. Related information Permission system Security and Audit FAQ: Deployment, AI and technical issues Public introduction:" }, { "lang": "en", "slug": "ai-search", "title": "AI search", "description": "AI search is used to retrieve corporate documents, materials and knowledge within scope of authority using natural language.", "category": "Zhichao AI", "top_category": "使用指南", "keywords": [ "Zhichao AI", "AI search", "Permission search", "RAG" ], "url": "en/ai-search.html", "source": "content/en/ai-search.md", "summary": "AISearch AI search is used to retrieve corporate documents, materials and knowledge within scope of authority using natural language. AI Search Interface diagram of AI search. Function description AI search is oriented to enterprise information question and answer and knowledge retrieval. Users can input natural language questions, and the system will retrieve relevant documents within the scope of authority and combine them with large models to generate answers. It is suitable for answering questions such as \"How is a certain system stipulated?\" \"Where are the design materials for a certain project?\" \"What are the key terms in a certain customer contract?\" \"What are similar contents in cert", "headings": [ { "level": 1, "title": "AISearch", "id": "aisearch" }, { "level": 2, "title": "Function description", "id": "function-description" }, { "level": 2, "title": "Main abilities", "id": "main-abilities" }, { "level": 2, "title": "Applicable scenarios", "id": "applicable-scenarios" }, { "level": 2, "title": "Permissions and usage boundaries", "id": "permissions-and-usage-boundaries" }, { "level": 2, "title": "Related information", "id": "related-information" } ], "images": [ { "src": "../assets/images/ai-search.webp", "alt": "AI Search", "caption": "Interface diagram of AI search." } ], "text": "AISearch AI search is used to retrieve corporate documents, materials and knowledge within scope of authority using natural language. AI Search Interface diagram of AI search. Function description AI search is oriented to enterprise information question and answer and knowledge retrieval. Users can input natural language questions, and the system will retrieve relevant documents within the scope of authority and combine them with large models to generate answers. It is suitable for answering questions such as \"How is a certain system stipulated?\" \"Where are the design materials for a certain project?\" \"What are the key terms in a certain customer contract?\" \"What are similar contents in certain types of documents?\" Main abilities Study documents, knowledge materials and file contents within the designated scope of the enterprise. Determine the retrieval range based on user permissions to avoid unauthorized responses. Supports follow up questions, users can continue to delve deeper into the last answer. The answer gives the source of the information, making it easier for the user to return to the corresponding file for verification. Supports recognition of text in pictures and can be combined with OCR and multi modal capabilities. Search results can include AI generated content, or go back to the original file to verify the source. Complementary with full text search, tag, description, annotation, file name search and other capabilities. Applicable scenarios Questions and answers about corporate systems, processes, contracts, project materials, product descriptions and customer service materials. Data retrieval for R&D, engineering, design, legal, administrative, human resources and other departments. Quick location of multi file, multi project, and multi version data. Allow new employees to ask questions to understand the company's information, rather than rummaging through directory after directory. Permissions and usage boundaries Zhichao AI’s answers, searches, and file references should follow Babel’s existing permission system. Users can only access content within their account, department, project, share, and file access controls. Materials used for learning, training, indexing, or Q&A should be specified by the enterprise or administrator; all files should not be considered public knowledge sources by default. External customer service, website embedding, third party data sources, privatized models and GPU computing power are optional deployment or customization capabilities and should be subject to actual authorization, implementation plan and enterprise configuration. When AI answers involve high risk content such as contracts, finance, medical, legal, and engineering safety, the AI ​​output should be used as auxiliary information and reviewed by professionals. Related information Permission system Security and Audit FAQ: Deployment, AI and technical issues Public introduction:" }, { "lang": "en", "slug": "ai-image-search", "title": "AI image search", "description": "AI image search is used to find images and visual assets in the network disk through text descriptions or uploaded images.", "category": "Zhichao AI", "top_category": "使用指南", "keywords": [ "Zhichao AI", "AI image search", "Picture search", "Wensotu", "OCR" ], "url": "en/ai-image-search.html", "source": "content/en/ai-image-search.md", "summary": "AI image search AI image search is used to find images and visual assets in the network disk through text descriptions or uploaded images. AI Image Search Interface diagram of AI image search. Function description AI image search is aimed at retrieving corporate images, materials, design drafts, product images, activity images and scanned data. It can not only search for pictures through text descriptions, but also upload a picture to search for similar pictures. It is suitable for companies with a large number of material libraries and visual assets. Main abilities Text search for pictures: Enter descriptions such as \"blue packaging box\", \"conference site photo\", \"white background picture o", "headings": [ { "level": 1, "title": "AI image search", "id": "ai-image-search" }, { "level": 2, "title": "Function description", "id": "function-description" }, { "level": 2, "title": "Main abilities", "id": "main-abilities" }, { "level": 2, "title": "Relationship with material library", "id": "relationship-with-material-library" }, { "level": 2, "title": "Permissions and usage boundaries", "id": "permissions-and-usage-boundaries" }, { "level": 2, "title": "Related information", "id": "related-information" } ], "images": [ { "src": "../assets/images/ai-image-search.webp", "alt": "AI Image Search", "caption": "Interface diagram of AI image search." } ], "text": "AI image search AI image search is used to find images and visual assets in the network disk through text descriptions or uploaded images. AI Image Search Interface diagram of AI image search. Function description AI image search is aimed at retrieving corporate images, materials, design drafts, product images, activity images and scanned data. It can not only search for pictures through text descriptions, but also upload a picture to search for similar pictures. It is suitable for companies with a large number of material libraries and visual assets. Main abilities Text search for pictures: Enter descriptions such as \"blue packaging box\", \"conference site photo\", \"white background picture of a certain product\", etc. to search for pictures. Image search: Upload reference images and find similar or related images. Filter the search scope by permissions, users can only search for images they can access. Can be combined with OCR to identify text in images, allowing scans, posters, and screenshots to be included in the search. PDF image search allows PDF documents with images to participate in image content retrieval. Suitable for material library, brand asset library, design files, marketing gallery and project drawing materials. Relationship with material library AI image search can be combined with the BabelBird material library, waterfall flow display, tags, descriptions, preview and sharing. For brand, marketing, design, engineering and archival teams, AI image search can reduce the workload of manual labeling and hierarchical directory searches. Permissions and usage boundaries Zhichao AI’s answers, searches, and file references should follow Babel’s existing permission system. Users can only access content within their account, department, project, share, and file access controls. Materials used for learning, training, indexing, or Q&A should be specified by the enterprise or administrator; all files should not be considered public knowledge sources by default. External customer service, website embedding, third party data sources, privatized models and GPU computing power are optional deployment or customization capabilities and should be subject to actual authorization, implementation plan and enterprise configuration. When AI answers involve high risk content such as contracts, finance, medical, legal, and engineering safety, the AI ​​output should be used as auxiliary information and reviewed by professionals. Related information Permission system Security and Audit FAQ: Deployment, AI and technical issues Public introduction:" }, { "lang": "en", "slug": "ai-data-assistant", "title": "Intelligent data assistant", "description": "Intelligent Data Assistant for querying, analysis, cross-statistics, and chart generation in Excel and third-party data sources.", "category": "Zhichao AI", "top_category": "使用指南", "keywords": [ "Zhichao AI", "Intelligent data assistant", "Excel", "data analysis", "chart" ], "url": "en/ai-data-assistant.html", "source": "content/en/ai-data-assistant.md", "summary": "Intelligent Data Assistant Intelligent Data Assistant for querying, analysis, cross statistics, and chart generation in Excel and third party data sources. Intelligent Data Assistant Interface diagram of intelligent data assistant. Function description The intelligent data assistant is designed for enterprise forms, ledgers, reports and business data queries. It can perform cross analysis around multiple Excel files, and can also be connected to third party data sources accessed as URLs depending on the implementation. Suitable for business users who don't want to manually write formulas, filter conditions or statistical scripts. Main abilities Supports cross analysis and comprehensive query", "headings": [ { "level": 1, "title": "Intelligent Data Assistant", "id": "intelligent-data-assistant" }, { "level": 2, "title": "Function description", "id": "function-description" }, { "level": 2, "title": "Main abilities", "id": "main-abilities" }, { "level": 2, "title": "Applicable scenarios", "id": "applicable-scenarios" }, { "level": 2, "title": "Notes", "id": "notes" }, { "level": 2, "title": "Permissions and usage boundaries", "id": "permissions-and-usage-boundaries" }, { "level": 2, "title": "Related information", "id": "related-information" } ], "images": [ { "src": "../assets/images/ai-assistant.webp", "alt": "Intelligent Data Assistant", "caption": "Interface diagram of intelligent data assistant." } ], "text": "Intelligent Data Assistant Intelligent Data Assistant for querying, analysis, cross statistics, and chart generation in Excel and third party data sources. Intelligent Data Assistant Interface diagram of intelligent data assistant. Function description The intelligent data assistant is designed for enterprise forms, ledgers, reports and business data queries. It can perform cross analysis around multiple Excel files, and can also be connected to third party data sources accessed as URLs depending on the implementation. Suitable for business users who don't want to manually write formulas, filter conditions or statistical scripts. Main abilities Supports cross analysis and comprehensive query of multiple Excel files. Supports access to third party data sources as URLs, depending on enterprise configuration. AI can automatically program data query, cleaning, statistics and analysis based on the problem. Charts can be generated based on query results to assist in report production or business analysis. Supports the use of table Q&A in the Excel file preview interface or Zhichao AI column. Can be combined with deep thinking mode to handle more complex statistics, functions and analysis tasks. Supports multi language interaction, suitable for cross regional or cross language teams. Applicable scenarios Summary analysis of sales orders, inventory, project ledgers, supplier lists, customer lists and financial details. Cross reference between Excel files maintained by multiple departments. Ask questions in natural language, such as \"Sales this month by region\", \"Find overdue items\", \"Compare missing customers in two tables\". Notes The scope of data processed by the intelligent data assistant should be confirmed by the enterprise. Sensitive data such as finance, personnel, and customer privacy should be used in conjunction with permissions, auditing, and desensitization strategies. Permissions and usage boundaries Zhichao AI’s answers, searches, and file references should follow Babel’s existing permission system. Users can only access content within their account, department, project, share, and file access controls. Materials used for learning, training, indexing, or Q&A should be specified by the enterprise or administrator; all files should not be considered public knowledge sources by default. External customer service, website embedding, third party data sources, privatized models and GPU computing power are optional deployment or customization capabilities and should be subject to actual authorization, implementation plan and enterprise configuration. When AI answers involve high risk content such as contracts, finance, medical, legal, and engineering safety, the AI ​​output should be used as auxiliary information and reviewed by professionals. Related information Permission system Security and Audit FAQ: Deployment, AI and technical issues Public introduction:" }, { "lang": "en", "slug": "ai-assistant-agent", "title": "Custom agents and knowledge base robots", "description": "Custom agents are used to build enterprise-specific knowledge bases, AI customer service, industry assistants, and multi-agent workflows.", "category": "Zhichao AI", "top_category": "使用指南", "keywords": [ "Zhichao AI", "Custom agent", "Knowledge base robot", "AI customer service", "Multiple Agents" ], "url": "en/ai-assistant-agent.html", "source": "content/en/ai-assistant-agent.md", "summary": "Custom agents and knowledge base robots Custom agents are used to build enterprise specific knowledge bases, AI customer service, industry assistants, and multi agent workflows. Customized agent and knowledge base robot Interface diagram of custom agents and knowledge base robots. Function description Custom agents are the core modules of Zhichao AI for enterprise knowledge bases and business assistants. Administrators or implementation teams can configure different agents for different business scenarios, such as customer service, knowledge base, analysts, writers, project assistants, pre sales consultants or industry experts. Customized knowledge base robot Knowledge base robots can be use", "headings": [ { "level": 1, "title": "Custom agents and knowledge base robots", "id": "custom-agents-and-knowledge-base-robots" }, { "level": 2, "title": "Function description", "id": "function-description" }, { "level": 2, "title": "Main abilities", "id": "main-abilities" }, { "level": 2, "title": "Knowledge base construction method", "id": "knowledge-base-construction-method" }, { "level": 2, "title": "Usage suggestions", "id": "usage-suggestions" }, { "level": 2, "title": "Permissions and usage boundaries", "id": "permissions-and-usage-boundaries" }, { "level": 2, "title": "Related information", "id": "related-information" } ], "images": [ { "src": "../assets/images/ai-agent.webp", "alt": "Customized agent and knowledge base robot", "caption": "Interface diagram of custom agents and knowledge base robots." }, { "src": "../assets/images/ai-bot.webp", "alt": "Customized knowledge base robot", "caption": "Knowledge base robots can be used in corporate information Q&A, online customer service and exclusive knowledge assistant scenarios." } ], "text": "Custom agents and knowledge base robots Custom agents are used to build enterprise specific knowledge bases, AI customer service, industry assistants, and multi agent workflows. Customized agent and knowledge base robot Interface diagram of custom agents and knowledge base robots. Function description Custom agents are the core modules of Zhichao AI for enterprise knowledge bases and business assistants. Administrators or implementation teams can configure different agents for different business scenarios, such as customer service, knowledge base, analysts, writers, project assistants, pre sales consultants or industry experts. Customized knowledge base robot Knowledge base robots can be used in corporate information Q&A, online customer service and exclusive knowledge assistant scenarios. Main abilities Customize the agent's personality, response logic and prompt words. Specify the target folder or data range for the agent to learn. Supports access to third party data sources as URLs, depending on implementation configuration. Provides preset templates for customer service, knowledge base, analysts, writing and other industries. Supports multiple agents, allowing different agents to serve different problems according to business division. Can generate embed code for use in third party websites or corporate portals. Can be used as an enterprise knowledge base robot to configure different assistants for different knowledge areas. Knowledge base construction method Enterprises can hand over product manuals, FAQs, customer service documents, system documents, training materials, project materials, etc. to designated agents for learning. Compared with traditional manual knowledge base compilation, Zhichao AI emphasizes directly using the company's existing documents to reduce the cost of repeatedly writing knowledge base entries. Usage suggestions Split agents according to business domains, such as \"customer service robot\", \"pre sales knowledge base\", \"internal system assistant\" and \"project data assistant\". Each agent specifies a clear learning scope and usage object to prevent one agent from carrying too much irrelevant knowledge. External customer service agents should set answer boundaries, disclaimers, manual transfers and sensitive issue handling rules. Permissions and usage boundaries Zhichao AI’s answers, searches, and file references should follow Babel’s existing permission system. Users can only access content within their account, department, project, share, and file access controls. Materials used for learning, training, indexing, or Q&A should be specified by the enterprise or administrator; all files should not be considered public knowledge sources by default. External customer service, website embedding, third party data sources, privatized models and GPU computing power are optional deployment or customization capabilities and should be subject to actual authorization, implementation plan and enterprise configuration. When AI answers involve high risk content such as contracts, finance, medical, legal, and engineering safety, the AI ​​output should be used as auxiliary information and reviewed by professionals. Related information Permission system Security and Audit FAQ: Deployment, AI and technical issues Public introduction:" }, { "lang": "en", "slug": "ai-assistant", "title": "Enterprise AI Assistant", "description": "The enterprise AI assistant integrates smart nest applications in the form of conversations to help users check files, ask for knowledge, read documents and complete office tasks.", "category": "Zhichao AI", "top_category": "使用指南", "keywords": [ "Zhichao AI", "Enterprise AI Assistant", "Document Assistant", "multimodal" ], "url": "en/ai-assistant.html", "source": "content/en/ai-assistant.md", "summary": "Enterprise AI Assistant The enterprise AI assistant integrates smart nest applications in the form of conversations to help users check files, ask for knowledge, read documents and complete office tasks. Enterprise AI Assistant Interface representation of enterprise AI assistant. Function description The enterprise AI assistant is a unified conversation portal for ordinary employees. Users do not need to first decide whether to use search, image search, document assistant or knowledge base robot. They can directly ask questions through dialogue, and AI will complete retrieval, reading, analysis or further guidance in corporate materials and enabled modules. Main abilities Integrate most Zhic", "headings": [ { "level": 1, "title": "Enterprise AI Assistant", "id": "enterprise-ai-assistant" }, { "level": 2, "title": "Function description", "id": "function-description" }, { "level": 2, "title": "Main abilities", "id": "main-abilities" }, { "level": 2, "title": "Relationship with Document Assistant", "id": "relationship-with-document-assistant" }, { "level": 2, "title": "Permissions and usage boundaries", "id": "permissions-and-usage-boundaries" }, { "level": 2, "title": "Related information", "id": "related-information" } ], "images": [ { "src": "../assets/images/ai-assistant.webp", "alt": "Enterprise AI Assistant", "caption": "Interface representation of enterprise AI assistant." } ], "text": "Enterprise AI Assistant The enterprise AI assistant integrates smart nest applications in the form of conversations to help users check files, ask for knowledge, read documents and complete office tasks. Enterprise AI Assistant Interface representation of enterprise AI assistant. Function description The enterprise AI assistant is a unified conversation portal for ordinary employees. Users do not need to first decide whether to use search, image search, document assistant or knowledge base robot. They can directly ask questions through dialogue, and AI will complete retrieval, reading, analysis or further guidance in corporate materials and enabled modules. Main abilities Integrate most Zhichao applications in the form of conversations. Answer the knowledge points involved in all documents within the scope of authorization of the enterprise. Search network disk files in multiple dimensions through multiple rounds of conversations. Can be combined with Internet search to answer external knowledge questions. Switch to deep thinking mode to deal with complex problems. Supports multi modal input and output capabilities, specific capabilities depend on deployment model and module configuration. Can be used as a data assistant, document assistant and knowledge Q&A portal for employees in their daily work. Relationship with Document Assistant The document assistant pays more attention to the reading and Q&A of \"single documents\"; the enterprise AI assistant pays more attention to comprehensive queries and task entries \"within the scope of enterprise data\". The two can complement each other: users first find files through the enterprise AI assistant, and then enter the document assistant to read in depth. Permissions and usage boundaries Zhichao AI’s answers, searches, and file references should follow Babel’s existing permission system. Users can only access content within their account, department, project, share, and file access controls. Materials used for learning, training, indexing, or Q&A should be specified by the enterprise or administrator; all files should not be considered public knowledge sources by default. External customer service, website embedding, third party data sources, privatized models and GPU computing power are optional deployment or customization capabilities and should be subject to actual authorization, implementation plan and enterprise configuration. When AI answers involve high risk content such as contracts, finance, medical, legal, and engineering safety, the AI ​​output should be used as auxiliary information and reviewed by professionals. Related information Permission system Security and Audit FAQ: Deployment, AI and technical issues Public introduction:" }, { "lang": "en", "slug": "ai-customer-service", "title": "AI customer service", "description": "AI customer service is used to learn product descriptions, FAQs, customer service documents and provide automated Q&A services to customers or employees.", "category": "Zhichao AI", "top_category": "使用指南", "keywords": [ "Zhichao AI", "AI customer service", "customer service robot", "website embedding" ], "url": "en/ai-customer-service.html", "source": "content/en/ai-customer-service.md", "summary": "AI Customer Service AI customer service is used to learn product descriptions, FAQs, customer service documents and provide automated Q&A services to customers or employees. AI Customer Service Interface diagram of AI customer service. Function description AI customer service is Zhichao AI’s module for external service and internal support. Enterprises can provide product manuals, FAQs, customer service documents, after sales procedures, policy descriptions and other materials to allow AI to learn and form conversational customer service capabilities. Main abilities Answer customer or employee questions based on company specific information. Access to corporate website, help center or busine", "headings": [ { "level": 1, "title": "AI Customer Service", "id": "ai-customer-service" }, { "level": 2, "title": "Function description", "id": "function-description" }, { "level": 2, "title": "Main abilities", "id": "main-abilities" }, { "level": 2, "title": "Data preparation", "id": "data-preparation" }, { "level": 2, "title": "Permissions and usage boundaries", "id": "permissions-and-usage-boundaries" }, { "level": 2, "title": "Related information", "id": "related-information" } ], "images": [ { "src": "../assets/images/ai-bot.webp", "alt": "AI Customer Service", "caption": "Interface diagram of AI customer service." } ], "text": "AI Customer Service AI customer service is used to learn product descriptions, FAQs, customer service documents and provide automated Q&A services to customers or employees. AI Customer Service Interface diagram of AI customer service. Function description AI customer service is Zhichao AI’s module for external service and internal support. Enterprises can provide product manuals, FAQs, customer service documents, after sales procedures, policy descriptions and other materials to allow AI to learn and form conversational customer service capabilities. Main abilities Answer customer or employee questions based on company specific information. Access to corporate website, help center or business portal through embedded code. Can be used as a portal for pre sales Q&A, after sales support, product descriptions, internal IT support or knowledge base. Supports improving answer stability through fine tuning, prompt words, question and answer range and manual review process. It can reduce the labor cost of repeated questions and answers and transfer complex questions to manual customer service or business personnel. Data preparation It is recommended that enterprises prepare information with clear structure, clear version, that can be disclosed or authorized for use, including product descriptions, FAQs, terms of service, operation manuals, troubleshooting, price specifications, delivery instructions, etc. In particular, external customer service must confirm which content can be answered publicly and which questions must be transferred manually. Permissions and usage boundaries Zhichao AI’s answers, searches, and file references should follow Babel’s existing permission system. Users can only access content within their account, department, project, share, and file access controls. Materials used for learning, training, indexing, or Q&A should be specified by the enterprise or administrator; all files should not be considered public knowledge sources by default. External customer service, website embedding, third party data sources, privatized models and GPU computing power are optional deployment or customization capabilities and should be subject to actual authorization, implementation plan and enterprise configuration. When AI answers involve high risk content such as contracts, finance, medical, legal, and engineering safety, the AI ​​output should be used as auxiliary information and reviewed by professionals. Related information Permission system Security and Audit FAQ: Deployment, AI and technical issues Public introduction:" }, { "lang": "en", "slug": "ai-deployment-customization", "title": "AI deployment and customization", "description": "Introducing Zhichao AI's privatized deployment, GPU computing power, dedicated agents, industry applications and on-demand development.", "category": "Zhichao AI", "top_category": "使用指南", "keywords": [ "Zhichao AI", "Private Deployment", "GPU", "Custom development", "agent" ], "url": "en/ai-deployment-customization.html", "source": "content/en/ai-deployment-customization.md", "summary": "AI Deployment and Customization Introducing Zhichao AI's privatized deployment, GPU computing power, dedicated agents, industry applications and on demand development. AI Deployment and Customization Interface diagram of AI deployment and customization. Private deployment method Zhichao AI privatization can be divided into three categories based on data security, budget, computing power, model calling and network search requirements. Actual projects should be subject to formal implementation evaluation. Method Description Applicable scenarios All privatized Deploy approximately 32B models such as DeepSeek and Qianwen on self built servers, and model inference and knowledge base capabilities ", "headings": [ { "level": 1, "title": "AI Deployment and Customization", "id": "ai-deployment-and-customization" }, { "level": 2, "title": "Private deployment method", "id": "private-deployment-method" }, { "level": 2, "title": "Reference server configuration", "id": "reference-server-configuration" }, { "level": 2, "title": "External models and network searches", "id": "external-models-and-network-searches" }, { "level": 2, "title": "Deployment form", "id": "deployment-form" }, { "level": 2, "title": "On demand development", "id": "on-demand-development" }, { "level": 2, "title": "Typical Delivery Content", "id": "typical-delivery-content" }, { "level": 2, "title": "Privatization considerations", "id": "privatization-considerations" }, { "level": 2, "title": "Permissions and usage boundaries", "id": "permissions-and-usage-boundaries" }, { "level": 2, "title": "Related information", "id": "related-information" } ], "images": [ { "src": "../assets/images/ai-column.webp", "alt": "AI Deployment and Customization", "caption": "Interface diagram of AI deployment and customization." } ], "text": "AI Deployment and Customization Introducing Zhichao AI's privatized deployment, GPU computing power, dedicated agents, industry applications and on demand development. AI Deployment and Customization Interface diagram of AI deployment and customization. Private deployment method Zhichao AI privatization can be divided into three categories based on data security, budget, computing power, model calling and network search requirements. Actual projects should be subject to formal implementation evaluation. Method Description Applicable scenarios All privatized Deploy approximately 32B models such as DeepSeek and Qianwen on self built servers, and model inference and knowledge base capabilities should be run within the customer environment as much as possible Customers who have strict restrictions on data going out of the domain and have sufficient budget and GPU computing power Vector localization Deploy vector models and knowledge base storage operations on self built servers, and use public network large model APIs for question and answer reasoning Customers who want the knowledge base storage process to be locally controllable and accept external model reasoning Vectors are only stored locally The self built server saves the vectorized knowledge base, and model inference and vector operations use the public network large model API Customers who want to reduce local GPU costs and accept external model services Reference server configuration Deployment method Server purpose Reference configuration Card counting configuration All privatized Computing server CPU 2 8368Q, 256G memory, 960G SSD 2, 8TB HDD 2 5880 ADA 48G 4 Vector localization Vector server CPU 2 4310, 128G memory, 480G SSD, 4TB HDD 2 3090 24G 2 Vectors are only stored locally Vector server CPU 2 4310, 128G memory, 480G SSD, 4TB HDD 2 None External models and network searches Some deployment methods will use the public network large model API, Internet search API or TokenPlan. Optional models and services can include Minmax, GLM, DeepSeek, and Tencent Cloud Internet Search API. The cost will vary with the model, call volume, number of Internet searches and enterprise usage intensity. The official cost is based on the commercial quotation and implementation plan. Deployment form Zhichao AI can be used as an optional module of BabelBird Enterprise Drive, and can also be deployed according to enterprise requirements in privatization projects. Private deployment usually requires additional GPU computing power, model services, vector retrieval or knowledge base indexing services, and needs to be combined with the enterprise's data security, network access and third party model policy design. On demand development Babel can develop exclusive AI applications around enterprise industry scenarios and business processes, such as exclusive agents, business data queries, industry specific Q&A, document processing processes, AI tags and classification rules, third party system access, etc. Typical Delivery Content Data scope confirmation, knowledge base design and agent role design. Configuration of capabilities such as models, vector libraries, OCR, multi modality, and third party data sources. Permission linkage, audit logs, access scope and security policy design. Agent embedding, enterprise portal integration or third party website access. Test question and answer set, effect optimization, online training and subsequent maintenance. Privatization considerations Whether the privatized Zhichao AI runs completely within the internal network, whether it calls external models, whether it uses third party APIs, and whether it supports offline models should be clarified in the implementation plan. Customers involving sensitive data should prioritize data flow, log retention, model training boundaries, and permission audits. Permissions and usage boundaries Zhichao AI’s answers, searches, and file references should follow Babel’s existing permission system. Users can only access content within their account, department, project, share, and file access controls. Materials used for learning, training, indexing, or Q&A should be specified by the enterprise or administrator; all files should not be considered public knowledge sources by default. External customer service, website embedding, third party data sources, privatized models and GPU computing power are optional deployment or customization capabilities and should be subject to actual authorization, implementation plan and enterprise configuration. When AI answers involve high risk content such as contracts, finance, medical, legal, and engineering safety, the AI ​​output should be used as auxiliary information and reviewed by professionals. Related information Permission system Security and Audit FAQ: Deployment, AI and technical issues Public introduction:" }, { "lang": "en", "slug": "automation-overview", "title": "Automate tasks", "description": "Automated task overview, permission drive, multi-task concatenation and execution weight.", "category": "Product Features", "top_category": "使用指南", "keywords": [ "automation", "Automate tasks", "Workflow" ], "url": "en/automation-overview.html", "source": "content/en/automation-overview.md", "summary": "Automate tasks Automated task overview, permission drive, multi task concatenation and execution weight. Automation tasks Automated tasks can be configured from the folder task entry or automated task list. Facing the growing number of digital assets, the traditional manual file management model can no longer meet the demand for efficient circulation. The \"automated task\" engine launched by BabelBird aims to hand over tedious and repetitive file processing actions to the system background for automatic execution. By establishing a \"self organizing and self standardizing\" intelligent circulation system, the cost of manual intervention is significantly reduced, allowing the team to focus on co", "headings": [ { "level": 1, "title": "Automate tasks", "id": "automate-tasks" }, { "level": 3, "title": "Multi task collaboration and execution flow weight", "id": "multi-task-collaboration-and-execution-flow-weight" } ], "images": [ { "src": "../assets/images/automation-list.webp", "alt": "Automation tasks", "caption": "Automated tasks can be configured from the folder task entry or automated task list." } ], "text": "Automate tasks Automated task overview, permission drive, multi task concatenation and execution weight. Automation tasks Automated tasks can be configured from the folder task entry or automated task list. Facing the growing number of digital assets, the traditional manual file management model can no longer meet the demand for efficient circulation. The \"automated task\" engine launched by BabelBird aims to hand over tedious and repetitive file processing actions to the system background for automatic execution. By establishing a \"self organizing and self standardizing\" intelligent circulation system, the cost of manual intervention is significantly reduced, allowing the team to focus on core business creation. Automated tasks are included in the standard version and users do not need to purchase it separately. Core operating mechanism: Flexible permission driven: Relying on the platform's extremely fine grained permission management system, users with corresponding permissions on the target network disk or folder can independently configure, turn on or off specific automation tasks as needed. Multi task flow concatenation (Workflow): Automated tasks do not run in isolation and support the free combination of multiple rules to form a workflow. For example: after a file is uploaded, the system can first trigger \"automatic rename\" to standardize the file name, and then immediately trigger \"automatic sorting\" to archive it to the relevant directory, achieving multiple steps in one go. Continuously expanding capability matrix: The automation engine is highly scalable. In addition to the existing basic functions, the platform will continue to access more automated processing nodes to meet increasingly complex business scenarios. Currently supported core tasks (including but not limited to): Automatic renaming: Unify and standardize naming according to preset rules (such as keyword replacement, case conversion). Automatic organization and cleaning: Automatically classify archived files based on trigger conditions, or clean up space regularly based on policies. Automatic PDF conversion and signature: Automatically generate a PDF copy of the source file, or stamp the company signature in the cloud. Create folders in batches: Generate a standard business directory tree with one click by importing data templates (such as Excel). Multi task collaboration and execution flow weight In complex business scenarios, multiple automated tasks are often configured in one folder. In order to ensure the logical rigor and security of data processing, a strict automated processing sequence is preset at the bottom of the system. The specific execution weight (the higher the value, the priority for execution) is as follows: Automatically clean folders (weight 10): highest system priority. If there are qualified cleaning tasks, they will be executed first to avoid investing subsequent computing power in invalid data that will be discarded. Automatic decompression (weight 9): Prioritize the release of packaged assets for subsequent circulation. Automatic renaming (weight 8): Priority is given to completing the standardization and unification of naming before files enter classification and archiving. Automatic format conversion category (weight 7): Prioritize conversion tasks such as transferring PDF, pictures or audio and video formats. Automatic sorting/sorting (weight 6): Executed as the end node of the flow. This means that core pre standardization operations such as cleaning, renaming and format conversion have been completed before files are moved and classified." }, { "lang": "en", "slug": "automation-clean", "title": "Automatically clean files", "description": "Clean up temporary files, process files and short-term circulating materials according to rules.", "category": "Product Features", "top_category": "使用指南", "keywords": [ "automation", "Automatically clean files", "Workflow" ], "url": "en/automation-clean.html", "source": "content/en/automation-clean.md", "summary": "Automatically clean files Clean up temporary files, process files and short term circulating materials according to rules. Automatic cleanup file Automated tasks can be configured from the folder task entry or automated task list. Function Overview In daily cross department collaboration or project cycle management, a large amount of temporary data, process files or short term circulation materials are often inevitably generated in the enterprise network disk. The \"Automatically Clean Files\" function is designed to provide enterprises with automated storage space optimization and directory slimming solutions. Through this function, the system can automatically delete redundant files in speci", "headings": [ { "level": 1, "title": "Automatically clean files", "id": "automatically-clean-files" }, { "level": 3, "title": "Function Overview", "id": "function-overview" }, { "level": 3, "title": "Core operation and configuration rules", "id": "core-operation-and-configuration-rules" }, { "level": 3, "title": "Permissions and data security control", "id": "permissions-and-data-security-control" }, { "level": 3, "title": "Typical business application scenarios", "id": "typical-business-application-scenarios" } ], "images": [ { "src": "../assets/images/automation-create.webp", "alt": "Automatic cleanup file", "caption": "Automated tasks can be configured from the folder task entry or automated task list." } ], "text": "Automatically clean files Clean up temporary files, process files and short term circulating materials according to rules. Automatic cleanup file Automated tasks can be configured from the folder task entry or automated task list. Function Overview In daily cross department collaboration or project cycle management, a large amount of temporary data, process files or short term circulation materials are often inevitably generated in the enterprise network disk. The \"Automatically Clean Files\" function is designed to provide enterprises with automated storage space optimization and directory slimming solutions. Through this function, the system can automatically delete redundant files in specified folders according to specific rules set by the user, keeping the project directory clean for a long time and releasing high value storage resources. Core operation and configuration rules This module uses a strict logical rule engine to perform file cleaning actions to ensure the accuracy and efficiency of data processing: Target directory locking: The task configuration needs to explicitly specify the target folder to which the rule applies. Users can choose to apply the rules only to newly entered files in the folder, or to apply the rules to historical files that already exist in the directory at the same time. Multi dimensional rule triggering: Supports precise filtering and elimination of files based on specific rules. Common determination rules can cover file types (such as temporary files with specific suffixes), life cycles (such as files entering a directory for more than a specified number of days), and other dimensions to achieve highly customized cleaning strategies. Workflow collaboration: As the end link of complete automated circulation, automatic cleaning can be seamlessly connected with other tasks. For example, after the \"automatic conversion to PDF\" task is completed, the system can immediately trigger the \"automatic cleaning\" rule to uniformly clean the original draft files, leaving only the standardized final version. Permissions and data security control Since the cleaning task involves the sensitive operation of file deletion, this function relies heavily on Babel's extremely fine grained permission management system: Configuration permissions: Only collaboration members with corresponding advanced permissions (such as management and deletion permissions) for the folder can create or modify automatic cleanup tasks to prevent data loss caused by unauthorized operations from the source. Senseless and safe execution: Cleaning tasks are performed silently in the background to reduce interference with user front end operations. At the same time, the company's established data compliance and recycle bin retention policies are strictly followed to ensure the absolute security of data assets. Typical business application scenarios Design and R&D projects: In architectural design or scientific research management, working software often automatically generates a large number of backup or cache files (such as .bak or temporary rendering files). By configuring automatic cleaning tasks, you can set up automatic identification and deletion of useless files with specific suffixes on a regular basis to keep core drawings and literature catalogs pure. Public data exchange area: For the \"temporary transfer station\" or \"temporary sharing area\" set up within the enterprise, automatic cleaning tasks based on the time dimension (such as \"automatic cleaning after 7 days of retention\") can be configured to achieve self organization and self purification of public spaces and reduce operation and maintenance management costs." }, { "lang": "en", "slug": "automation-rename", "title": "automatic rename", "description": "Automatically normalize file names by variables, metadata, numbering and text rules.", "category": "Product Features", "top_category": "使用指南", "keywords": [ "automation", "automatic rename", "Workflow" ], "url": "en/automation-rename.html", "source": "content/en/automation-rename.md", "summary": "Automatically rename Automatically normalize file names by variables, metadata, numbering and text rules. Auto rename Automated tasks can be configured from the folder task entry or automated task list. Function Overview In business scenarios involving multi party collaboration and multi frequency data collection, due to differences in operator habits, file naming often lacks unified standards, which brings great trouble to subsequent retrieval, archiving and auditing. The \"Auto Rename\" function allows the system to automatically rename files uploaded to a specified folder according to highly customized preset rules. This mechanism effectively eliminates naming confusion caused by human fact", "headings": [ { "level": 1, "title": "Automatically rename", "id": "automatically-rename" }, { "level": 3, "title": "Function Overview", "id": "function-overview" }, { "level": 3, "title": "Scope of application and permission control", "id": "scope-of-application-and-permission-control" }, { "level": 3, "title": "Core rule engine and configuration dimensions", "id": "core-rule-engine-and-configuration-dimensions" }, { "level": 3, "title": "Refined pruning and anti conflict mechanism of original names", "id": "refined-pruning-and-anti-conflict-mechanism-of-original-names" }, { "level": 3, "title": "Global formatted output control", "id": "global-formatted-output-control" } ], "images": [ { "src": "../assets/images/automation-create.webp", "alt": "Auto-rename", "caption": "Automated tasks can be configured from the folder task entry or automated task list." } ], "text": "Automatically rename Automatically normalize file names by variables, metadata, numbering and text rules. Auto rename Automated tasks can be configured from the folder task entry or automated task list. Function Overview In business scenarios involving multi party collaboration and multi frequency data collection, due to differences in operator habits, file naming often lacks unified standards, which brings great trouble to subsequent retrieval, archiving and auditing. The \"Auto Rename\" function allows the system to automatically rename files uploaded to a specified folder according to highly customized preset rules. This mechanism effectively eliminates naming confusion caused by human factors and ensures that enterprise data assets meet the standards as soon as they are stored in the database. Scope of application and permission control Permission driven: The enabling of this function strictly relies on the user's operation permissions. As long as the user has \"upload\" and \"rename\" permissions on the target folder (covering various folders such as personal, department, project or material library), the automatic renaming task can be configured for it. Traceability processing: The rules not only apply to newly uploaded files, users can also choose to apply traceability to historical files that already exist in the target directory and all its subfolders. To ensure system performance and execution stability, the upper limit for batch source traceability renaming is 5,000 files at a time. Core rule engine and configuration dimensions Babel provides a highly flexible visual rule splicing engine. Users can add multiple naming rules and sort the rules freely by dragging and dropping. The configuration interface provides real time changing \"sample file names\" throughout the entire process to help users visually preview the overlay results of renaming rules. The rules engine supports the following multi dimensional named elements: Standard attribute variables: Supports extraction and insertion of system level variables, including file uploader, file person in charge, parent folder name, and upload time. Multimedia metadata (Metadata): For files in specific formats such as images, the system can deeply analyze and extract their underlying metadata as the basis for naming, such as shooting date, camera manufacturer/model, lens model, size, and DPI/DPCM and other parameters. Custom text and continuous numbering: Users can freely insert custom text content. In terms of numbering mechanism, unlike traditional single batch renaming, automatic renaming has state memory (continuity). The system will automatically read the last number in the target list that meets the rules to ensure that files uploaded across batches and time periods can achieve seamless continuation of serial numbers. Users can accurately set the starting value, incremental value and specific digits of the number. Refined pruning and anti conflict mechanism of original names In addition to adding new prefixes/suffixes, the system also supports deep structural cleaning of the original names of files: Name pruning and replacement: You can perform \"replace specific content\" and \"delete specified content\" operations on the original file name. In addition, it also provides a one click \"Delete Characters\" function to accurately remove redundant spaces, numbers, quotation marks, dashes and underlines in file names. Mandatory anti collision protection: If the user chooses to completely delete the \"original file name\" in the rule (that is, the original name is not retained when uploading), in order to avoid the risk of files with the same name overwriting each other, the system will force and automatically add a \"numbering\" rule to the rule chain. Date logical mutual exclusion: When calling date class variables, the user can check \"Replace the date detected in the file name\". To prevent logical conflicts, in a single rename task, the replacement instruction is only allowed to be checked once by a certain time variable (such as \"upload time\" or \"shooting time\"). Global formatted output control After completing the splicing of rule variables, the system supports unified formatting specifications on the output end: Case standardization: Supports one click conversion of assembled file names into uppercase, lowercase, all uppercase or all lowercase to meet the visual specifications of different companies. Uniform word separation: Supports the uniform insertion of standardized separators (such as spaces, underscores or dashes) between each naming rule module to further improve the machine readable and human readable experience of file names." }, { "lang": "en", "slug": "automation-pdf", "title": "Automatically convert to PDF", "description": "Automatically generate standard PDF copies, supporting documents, pictures, engineering drawings and other formats.", "category": "Product Features", "top_category": "使用指南", "keywords": [ "automation", "Automatically convert to PDF", "Workflow" ], "url": "en/automation-pdf.html", "source": "content/en/automation-pdf.md", "summary": "Automatically convert to PDF Automatically generate standard PDF copies, supporting documents, pictures, engineering drawings and other formats. Automatically convert to PDF Automated tasks can be configured from the folder task entry or automated task list. Function Overview In business links such as cross enterprise collaboration, external data distribution, and project finalization and archiving, the PDF format has become a standard document exchange medium due to its consistency in cross device display and anti tampering properties. BabelBird's \"Auto to PDF\" function aims to establish an automated file format standardization channel. After configuring this task, when a file is added to t", "headings": [ { "level": 1, "title": "Automatically convert to PDF", "id": "automatically-convert-to-pdf" }, { "level": 3, "title": "Function Overview", "id": "function-overview" }, { "level": 3, "title": "Execution logic and boundary conditions", "id": "execution-logic-and-boundary-conditions" }, { "level": 3, "title": "Extensive format compatibility matrix", "id": "extensive-format-compatibility-matrix" } ], "images": [ { "src": "../assets/images/automation-create.webp", "alt": "Automatically convert to PDF", "caption": "Automated tasks can be configured from the folder task entry or automated task list." } ], "text": "Automatically convert to PDF Automatically generate standard PDF copies, supporting documents, pictures, engineering drawings and other formats. Automatically convert to PDF Automated tasks can be configured from the folder task entry or automated task list. Function Overview In business links such as cross enterprise collaboration, external data distribution, and project finalization and archiving, the PDF format has become a standard document exchange medium due to its consistency in cross device display and anti tampering properties. BabelBird's \"Auto to PDF\" function aims to establish an automated file format standardization channel. After configuring this task, when a file is added to the selected target directory, the system will silently trigger the conversion engine in the background to automatically convert it into a standard PDF file. This capability greatly eliminates the inefficient labor of manually exporting PDFs one by one, ensuring the standardization of data external output and internal archiving. Execution logic and boundary conditions In order to ensure the efficient operation of the underlying computing resources of the platform and the safe and controllable flow of enterprise data, the following execution logic and boundary restrictions are set for the automatic conversion task: Scope and traceability processing: This task can be overridden downwards and supports checking to apply to files in the target directory and all subfolders. In addition, the rules also support traceability to historical data and can be applied to existing files in the directory. However, to ensure execution stability, the number of files processed in a single traceability process is strictly limited to 5,000. System performance protection mechanism: In order to prevent extremely large source files from occupying computing power for a long time during the conversion process and causing the task queue to be blocked, the system has a built in file size threshold, that is, large files exceeding 30MB will not trigger the automatic conversion mechanism. Automatic release of storage space: For the specific business scenario of \"only keeping the final PDF\", users can check the \"Delete original file after successful conversion\" option in the task configuration interface. After turning on this policy, the system will automatically clean up the original files after confirming that the PDF copy is generated correctly, thereby greatly optimizing the utilization of network disk storage space. Extensive format compatibility matrix Babel's automatic conversion engine has powerful multi format parsing capabilities and supports automatic dumping of mainstream business documents in 32 different industries into PDF. Users can choose to perform conversion on \"all supported files\", or use the drop down menu to accurately select the extensions they need to convert by category. The specific supported format matrix is as follows: Document typesetting: fully compatible with source files generated by mainstream office and publishing software, including doc, docx, ppt, pptx, wps, epub, dpt, indd, rtf, docm and pptm. Pictures and images: Supports rendering and conversion of mainstream bitmaps, digital negatives and medical image formats, covering jpg, bmp, jpeg, jpg2, png, psd, tif, tiff, raw, cr2, dcm and heic. Graphics and engineering drawings: Deeply adapted to vector and CAD drawing conversion in the fields of design and construction engineering. Supported formats include ai, svg, eps, dwg, dwt and dxf." }, { "lang": "en", "slug": "automation-organize", "title": "Automatically organize files", "description": "Automatically classify and move files according to rules such as time, keywords, format, etc.", "category": "Product Features", "top_category": "使用指南", "keywords": [ "automation", "Automatically organize files", "Workflow" ], "url": "en/automation-organize.html", "source": "content/en/automation-organize.md", "summary": "Automatically organize files Automatically classify and move files according to rules such as time, keywords, format, etc. Automatically organize files Automated tasks can be configured from the folder task entry or automated task list. Function Overview With the accumulation of collaborative data in the platform, how to keep the underlying \"any folder synchronization\" architecture and permission control directory clean has become the key to enterprise digital asset management. The \"Automatically organize files\" function allows the system to automatically classify and route files to the corresponding target directory according to preset time periods or content characteristics. This function ", "headings": [ { "level": 1, "title": "Automatically organize files", "id": "automatically-organize-files" }, { "level": 3, "title": "Function Overview", "id": "function-overview" }, { "level": 3, "title": "Flexible triggering mechanism and scope", "id": "flexible-triggering-mechanism-and-scope" }, { "level": 3, "title": "Core intelligent sorting rule engine", "id": "core-intelligent-sorting-rule-engine" } ], "images": [ { "src": "../assets/images/automation-create.webp", "alt": "Automatically organize files", "caption": "Automated tasks can be configured from the folder task entry or automated task list." } ], "text": "Automatically organize files Automatically classify and move files according to rules such as time, keywords, format, etc. Automatically organize files Automated tasks can be configured from the folder task entry or automated task list. Function Overview With the accumulation of collaborative data in the platform, how to keep the underlying \"any folder synchronization\" architecture and permission control directory clean has become the key to enterprise digital asset management. The \"Automatically organize files\" function allows the system to automatically classify and route files to the corresponding target directory according to preset time periods or content characteristics. This function ensures that massive documents are highly structured during the circulation process and avoids the lag and errors of manual archiving. Flexible triggering mechanism and scope Users can enter the configuration through the \"Task\" option in the right click menu of the folder or the automated task list panel on the left. The configuration covers the following triggering and action rules: Event driven (default): When a file is uploaded or moved to a specified trigger folder, the system responds immediately and starts organizing actions. Period driven: Suitable for centralized data archiving scenarios. The system can uniformly perform file sorting according to a fixed period (for example, set to 23:00 every day). Historical traceability: Rules can be applied to new files and all subfolders, or you can check \"Apply to existing files\" to batch trace the historical inventory data. To ensure the stability of the system, traceability processing shall not exceed 5,000 files at a time. Core intelligent sorting rule engine The system provides three highly customized classification rules to meet data archiving needs in different dimensions: 1. Structured archiving based on time dimension (classified by month/year) The system can automatically create corresponding subfolders (such as \"2025\", \"2025 10\") according to the corresponding year or month when files are added to the network disk and move related files into . The same as when classifying by year or month, the system has the intelligence to create files on demand. If no files are generated within a specific period (such as a certain month), the system will not redundantly create empty folders for that month. 2. Content based intelligent routing (classified by keywords) Based on specific keywords contained in the file name, the system automatically distributes and moves files to preset destination folders. Format recognition: File extensions (such as \"jpg\") can also be configured as keywords to achieve targeted aggregation of specific types of materials. Multi line parallel routing: Users can continuously add multiple routing rules through the \"Add Keyword Classification\" button. It not only supports distributing files containing different keywords to different directories, but also supports pointing multiple keyword tasks to the same target folder. Anti duplication and priority control: Keyword matching is strictly processed in the order set by the task. For example, when the file name is \"123ABC final draft.jpg\", if the first rule in the keyword list is \"123\" and the second rule is \"final draft\", then the file will give priority to matching the rule of \"123\" and execute the move. The system has built in anti repetition detection. Each keyword is only allowed to be entered once. Repeated entry will trigger the \"Please re enter\" error interception. Same name conflict resolution: During the process of moving and organizing files, if a file with the same name is encountered in the target folder, the system will automatically append a number to the file name to ensure that the data is not accidentally overwritten." }, { "lang": "en", "slug": "automation-esign", "title": "Electronic signature", "description": "Cloud signing, signature/stamp assets, PDF output, and responsive signing interface.", "category": "Product Features", "top_category": "使用指南", "keywords": [ "automation", "Electronic signature", "Workflow" ], "url": "en/automation-esign.html", "source": "content/en/automation-esign.md", "summary": "electronic signature Cloud signing, signature/stamp assets, PDF output, and responsive signing interface. Electronic signature Automated tasks can be configured from the folder task entry or automated task list. Overview of business scenarios and functions In key links such as contract approval, drawing countersigning, and business compliance transfer, digital signatures with anti tampering properties are the core node for opening up the closed loop of online collaboration. Traditional cross system signing is often accompanied by cumbersome file downloads and format conversions. The \"Create Signature\" function launched by Babel allows users to stamp and sign documents directly in the cloud d", "headings": [ { "level": 1, "title": "electronic signature", "id": "electronic-signature" }, { "level": 3, "title": "Overview of business scenarios and functions", "id": "overview-of-business-scenarios-and-functions" }, { "level": 3, "title": "Signature asset library and personalized configuration", "id": "signature-asset-library-and-personalized-configuration" }, { "level": 3, "title": "Intelligent adaptive interaction and immersive guidance system", "id": "intelligent-adaptive-interaction-and-immersive-guidance-system" } ], "images": [ { "src": "../assets/images/automation-create.webp", "alt": "Electronic signature", "caption": "Automated tasks can be configured from the folder task entry or automated task list." } ], "text": "electronic signature Cloud signing, signature/stamp assets, PDF output, and responsive signing interface. Electronic signature Automated tasks can be configured from the folder task entry or automated task list. Overview of business scenarios and functions In key links such as contract approval, drawing countersigning, and business compliance transfer, digital signatures with anti tampering properties are the core node for opening up the closed loop of online collaboration. Traditional cross system signing is often accompanied by cumbersome file downloads and format conversions. The \"Create Signature\" function launched by Babel allows users to stamp and sign documents directly in the cloud disk workflow. The engine supports multiple mainstream file types to directly load printed signatures, and supports one click export of signed files to standard PDF format, ensuring the security, compliance and non tamperability of digital assets from the source. Signature asset library and personalized configuration The system provides users with a highly integrated digital signature management console to ensure the unified precipitation and rapid recall of electronic signature assets: Multi signature collection: In the \"Signature Settings\" module, users can call the terminal to \"add a handwritten signature\" online, or directly \"upload signature image files\" (such as PNG materials with transparent channels) to meet different levels of signing compliance requirements. Corporate seal management: In the \"Stamp Settings\" module, corporate users can upload business specific electronic official seals or compliance seal images as needed. Default priority status: For users who have multiple signature assets, the system supports one click \"setting a specific signature or stamp as currently used\" (default signature). In the subsequent document preview and circulation interface, the system will give priority to calling this default signature, which greatly improves the signing efficiency in high frequency approval scenarios. Intelligent adaptive interaction and immersive guidance system In order to take into account the display limits of different hardware terminals and lower the user's learning threshold, the signature configuration center adopts a multi breakpoint intelligent responsive interface architecture and deeply embeds multi language operation guides: Widescreen workstation mode (window width ≥ 1120px): When the user operates on a desktop widescreen device, the system not only retains the standard signature configuration panel on the left, but also automatically expands an independent video teaching area on the right. This area will automatically load and play the tutorial on how to use the signature in a loop without any sense (it will replay after a 3 second pause), providing users with an immersive experience of \"learning and matching at the same time.\" Compact focus mode (window width < 1100px): When on a narrow screen or mobile window, the system will intelligently collapse the video playback area on the right to maximize the visual focus of the core signature setting area. At the same time, the system provides a \"How to use signature?\" entry at the bottom of the interface, and users can click to trigger a full screen tutorial playback. International bilingual support: Considering the collaboration needs of multinational enterprises, the system has a built in localized teaching video library. In addition to the exclusive Chinese tutorials played in the Chinese language environment, all other multi language versions match and play standard English tutorials by default to ensure barrier free implementation for global business teams." }, { "lang": "en", "slug": "automation-batch-folders", "title": "Create folders in batches", "description": "Batch generate directory trees and project folders via Excel, CSV, TXT.", "category": "Product Features", "top_category": "使用指南", "keywords": [ "automation", "Create folders in batches", "Workflow" ], "url": "en/automation-batch-folders.html", "source": "content/en/automation-batch-folders.md", "summary": "Create folders in batches Batch generate directory trees and project folders via Excel, CSV, TXT. Create folders in batches Automated tasks can be configured from the folder task entry or automated task list. Function Overview and Business Value In business scenarios involving multi project concurrency or enterprise department structure adjustment, manually establishing complex standard directory trees one by one not only consumes a lot of operation time, but also easily leads to directory hierarchy confusion or non standard naming due to human oversight. The \"Batch Creation Folder\" function provided by Babel allows users to directly drive the generation of cloud directories through external", "headings": [ { "level": 1, "title": "Create folders in batches", "id": "create-folders-in-batches" }, { "level": 3, "title": "Function Overview and Business Value", "id": "function-overview-and-business-value" }, { "level": 3, "title": "Large scale generation of standard directory arrays", "id": "large-scale-generation-of-standard-directory-arrays" }, { "level": 3, "title": "\"One click deployment\" of project level folders and permissions", "id": "one-click-deployment-of-project-level-folders-and-permissions" }, { "level": 3, "title": "Real time status monitoring and intelligent fault tolerance mechanism", "id": "real-time-status-monitoring-and-intelligent-fault-tolerance-mechanism" } ], "images": [ { "src": "../assets/images/automation-create.webp", "alt": "Create folders in batches", "caption": "Automated tasks can be configured from the folder task entry or automated task list." } ], "text": "Create folders in batches Batch generate directory trees and project folders via Excel, CSV, TXT. Create folders in batches Automated tasks can be configured from the folder task entry or automated task list. Function Overview and Business Value In business scenarios involving multi project concurrency or enterprise department structure adjustment, manually establishing complex standard directory trees one by one not only consumes a lot of operation time, but also easily leads to directory hierarchy confusion or non standard naming due to human oversight. The \"Batch Creation Folder\" function provided by Babel allows users to directly drive the generation of cloud directories through external structured data (such as Excel, CSV, TXT text). This function can instantly transform a standardized business directory template into a network disk folder array that can be implemented, greatly improving the efficiency of initial file creation during the startup phase of large scale projects. Large scale generation of standard directory arrays This module has powerful data analysis capabilities and manual fault tolerant intervention mechanism: High concurrency support: The system supports importing files in xls, xlsx, csv or txt format and quickly reading directory lists according to newline character rules. The upper limit of a single batch processing task is up to 5,000 lines, which meets the generation needs of most enterprise level data structures. Visual pre review and dynamic intervention: Before the batch creation is officially executed, the system will complete the data analysis and visually render the folder list and hierarchical relationship to be generated in the interface. In this preview session, users can directly perform instant modification actions such as \"create subfolder\", \"rename\" or \"delete\" on a specific preset directory through the right mouse button or floating menu. This \"review before building\" mechanism ensures that the final directory tree is absolutely aligned with business needs. \"One click deployment\" of project level folders and permissions When the target path is set to the root directory of the department folder or personal folder, the system supports the creation of a more advanced \"Project Folder\" . This model is deeply integrated with the underlying permission management system of BabelBird to realize the synchronization of directory construction and member permission configuration: Exclusive standard template: To batch generate project folders, you need to download and use the system's exclusive template to import data. If the uploaded non standard file does not meet the parsing format, the system will strictly intercept it and prompt you to re upload it. Project role and permission preset: The template not only standardizes the \"project folder name\", but also supports the direct association of the account system to preset \"project leader\" and \"project member\". Assignment of person in charge: The filled in person in charge ID (supports mobile phone number, email address or specific work ID format) must be a registered company member; if this field is left blank or the filled in identity cannot be verified, the system will follow the security principle and set the operator of the currently created task as the project leader by default. Automatic member invitation and empowerment: Users can batch enter multiple project members in the template by separating them with commas. After the project directory is generated, the system will automatically send invitation notifications to these members and grant them basic \"upload and download\" default permissions, completely eliminating the cumbersome one by one authorization operations after file creation. Real time status monitoring and intelligent fault tolerance mechanism When executing large scale creation tasks, the system background will process it robustly in the form of a queue, and provide a full range of process monitoring and exception repair closed loops on the front end: Global progress tracking: During the creation process, the list node will update its execution status in real time (smooth transition from the circle animation representing ongoing execution to the confirmation check state representing success). The global status of the task will also clearly flow from \"Creating\" to \"Complete\". Accurate exception attribution and retry: After all tasks are executed, a clear summary of the results will be output at the top of the system (such as \"A total of XXX folders were created, and X failed\"). Users can check the \"Failed to Create File List\" with one click. The system will accurately classify the failure reasons as system level conflicts such as \"the file name contains characters that are not allowed\" or \"a folder with the same name already exists\". For these abnormal entries, users can not only find out the cause, but also click the green \"Retry\" button directly on the interface to trigger secondary creation, which greatly reduces the resistance to batch operation and maintenance." }, { "lang": "en", "slug": "doc-control-project", "title": "Document control project", "description": "Introduce document control projects, TRANSMITTAL, dispatch orders, recipients and automated document control processes in the engineering design industry.", "category": "Product Features", "top_category": "使用指南", "keywords": [ "text control", "DCC", "TRANSMITTAL", "Engineering design" ], "url": "en/doc-control-project.html", "source": "content/en/doc-control-project.md", "summary": "Document Control Project The document control project is an industry application independent module of BabelBird (needs to be purchased separately). The BabelBird document control project solves the problem of process management (DCC) and automation of document control standards in the engineering design industry. It improves the work efficiency of a large number of document control personnel and also reduces the possibility of human errors. Scope of use Industries or businesses that need to strictly manage every document sent. Every document sent to a customer is sent by a specific person (document control personnel). Every time a document is sent, there is a sending document that can be ch", "headings": [ { "level": 1, "title": "Document Control Project", "id": "document-control-project" }, { "level": 3, "title": "Scope of use", "id": "scope-of-use" }, { "level": 3, "title": "Problems that need to be solved", "id": "problems-that-need-to-be-solved" }, { "level": 3, "title": "BabelBird Solution", "id": "babelbird-solution" }, { "level": 3, "title": "Basic introduction", "id": "basic-introduction" } ], "images": [], "text": "Document Control Project The document control project is an industry application independent module of BabelBird (needs to be purchased separately). The BabelBird document control project solves the problem of process management (DCC) and automation of document control standards in the engineering design industry. It improves the work efficiency of a large number of document control personnel and also reduces the possibility of human errors. Scope of use Industries or businesses that need to strictly manage every document sent. Every document sent to a customer is sent by a specific person (document control personnel). Every time a document is sent, there is a sending document that can be checked, and the sending content can be clearly managed. Through the sending order number, you can check the specific information and files of each file sent to the recipient. At the same time, you can query whether the recipient has received the message and whether the sent content has been rejected. And the delivery order can be used as a voucher. Problems that need to be solved At present, the document control process of many enterprises is basically manual, and the files are stored in the EDMS system or locally on the computer of the document control personnel. Rely on folder classification to manage documents. Each time a file is sent, a folder is manually created and the folder is named according to the file name specification. After the file is sent by email, the sent file is placed in the folder and the TRANSMITTAL (file sending order) of this sending is attached. Each send will generate a folder and corresponding TRANSMITTAL. The manual operation of these tasks is quite cumbersome. In addition to sorting out files, you also need to manually fill in the document delivery form each time, manually write the delivery order number according to the rules, and manually check it in the future, which is extremely inefficient. BabelBird Solution New document control project types can be created. This means that different projects can set different TRANSMITTAL (sending order) rules to generate different sending orders and sending order numbers. Different projects can also manage different recipients (recipient companies) You can set the file recipient for each project and manage the file recipients in a unified manner. Documents in document control projects support the sending function, and the sending function supports multiple selections. After selecting a file or folder to send, the recipient can receive the download link and TRANSMITTAL of the sent file via email. And the file downloaded through the download link is the version when sent. Each file sent is the current version of the file. File upgrade will form a new version number, which will be displayed on the delivery note. After the file is sent, the TRANSMITTAL and TRANSMITTAL NO. will be automatically generated according to the preset rules. You can manage and query the TRANSMITTAL (delivery order), and export the delivery order to PDF. Instructions for use of the BabelBird Cultural Control Project: Basic introduction The BabelBird document control management system is based on the BabelBird enterprise private cloud version and adds a document control management module to realize the automation of document control work. The way of document control management is to establish a \"document control project\". Document control projects are special projects customized for document control needs and are managed on a project by project basis. Establish document control projects After logging in to the system, click \"New\" \"New Project\" in the department where you want to create a document control project Projects can only be created in the root directory (enterprise files) or department root directory Example: Establish a document control project under the document control department of HQSM Click New Project, and the project type selection interface will appear. Select \"Create Document Control Management Project\" At this time, the project initialization selection interface appears. Fill in the initialization information according to the requirements of the project Each item is introduced as follows: Project leader Manage, transfer projects, modify project permissions and basic information. Cannot be empty. TRANSMITTAL can be deleted Project Secretary The project cannot be transferred, other people in charge of the same project can have multiple people, and can be empty. TRANSMITTAL can be deleted Document control staff Can send files to recipients. Other permissions are configurable, can be for multiple people, and can be empty. After selecting a person, click the permission selection drop down box on the right to modify member permissions in batches (as shown in the figure). other members There is no option to send files. Others are the same as ordinary members of ordinary projects. The permissions are configurable and can be empty. Version number rules As shown in the figure, if the prefix is HQSM, the first version of the file is HQSM A, the second version is HQSM B and so on. Basic information The filled in basic information will be displayed in the TRANSMITTA header. As shown in the picture: The red circle is the basic information to be filled in. Recipient information The recipient information determines the options when sending and the TRANSMITTA number of the sent file. The recipient's name refers to the recipient's name in the system. Generally, the recipient's company abbreviation is filled in, such as MCC. You can add multiple mailboxes. After adding multiple mailboxes, you can send files and TRANSMITTA to multiple mailbox addresses in one send. ATTN can be entered at will and will also be displayed on TRANSMITTA The waybill number rule is actually the automatic generation rule of the TRANSMITTA number. Different recipients can generate different waybill numbers. Therefore, different waybill number rules need to be set at each recipient. The rules customization interface is as follows: The 3 columns are the three components of the TRANSMITTAL number. If the required TRANSMITTA number requires more codes to form, you can also click the + sign to add more columns. Example: Select to enter text in the first column, a text input box will pop up, enter \"HQSM \" Select the encoding rule in the second column as 1 2 3 numerical sequence Select text input in the third column and enter \" 2020\" Click the plus sign to add a column and select the alphabetical order of a b c The TRANSMITTAL number generated when sending for the first time is: HQSM 1 2020a The TRANSMITTAL number generated for the second transmission is: HQSM 2 2020b After selecting letters as numbers for more than 26 numbers, the next version of the z number automatically becomes a1 If the project has multiple recipients, you can also click to add them. (After the project is established, you can also add or delete recipients in the project management interface. After completing these fillings, click \"Add Project\" to complete the new project. You can see the newly created document control project in the file list of the created project path, click to enter Document control management projects are different from ordinary projects. A button for document control management is added to the top bar of the project homepage. Among them, the \"Sending Order List\" can query all TRANSMITTA issued by the project, and the management project can manage the project. Upload files Click on the newly created document control project to enter the project page. Just drag and drop the files you want to upload into the project to upload the files. Of course, you can also use the synchronization function to upload and download just like using ordinary folders. Send files Select the file to be sent (multiple selections are supported), then right click and select \"Send File\" to display the file sending interface. The maximum number of files sent at a time is 2,000 (including folders). If the project requires all files to be sent, it is recommended to send them in a compressed package. The recipient can drop down to select the recipient and ATTN filled in during project initialization. You can fill in any other email address for CC, or you can leave it blank. The selected submission file type will also be displayed in the generated TRANSMITTA The file list lists the files to be sent this time. The file name that the system wants to send TRANSMITTAL consists of file number + description. For example, if a file is named 1000+drawing.pdf, the file number displayed in TRANSMITTAL when sending is \"1000\" and the description is \"drawing\". If there is no + division in the file name of the sent file, the file number will display the file name. If the file name sent is \"+drawing.jpg\", the file number will not be displayed, and the description will be displayed as \"drawing\". Description can be changed midway. The postscript will be displayed in the email received by the recipient and will not be displayed in TRANSMITTAL. After filling in, click \"Send File\" and the system will automatically generate TRANSMITTAL and attach it as a link in the email and send it to the customer. Generate TRANSMITTAL After successful sending, the system will pop up a prompt Click View to view the TRANSMITTAL automatically generated for this send Click Export to PDF to save the TRANSMITTAL as a PDF file You can also view all TRANSMITTAL sent in the project in the TRANSMITTAL list The TRANSMITTAL received by the recipient in the mailbox is consistent with the TRANSMITTAL. View TRANSMITTAL Click on TRANSMITTAL list on the project homepage Open the list to see and query all dispatch orders for this project. Click on the delivery number to view details and download the PDF file of TRANSMITTAL Acceptance means that the recipient has not opened the sent email. If the other party opens the email and accesses TRANSMITTAL, the receiving status will change to received. View sending records Right click on any file to view the sending record of the file and its corresponding TRANSMITTAL" }, { "lang": "en", "slug": "developer-api-overview", "title": "Development API Overview", "description": "Introduces enterprise development accounts, authentication methods, API directories, calling specifications and developer indexes.", "category": "API Overview", "top_category": "API文档", "keywords": [ "API", "Developer", "OAuth", "JWT", "File interface" ], "url": "en/developer-api-overview.html", "source": "content/en/developer-api-overview.md", "summary": "Development API Overview BabelBird develops APIs to connect the authentication, file, sharing, organization, messaging and login capabilities of enterprise network disks to third party business systems. The left column is grouped by interface function, and the callable endpoints are listed directly in the group. Call overview The enterprise administrator creates a developer account in the private cloud enterprise management background and obtains client id , client secret and JWT related keys. In the OAuth callback method, use /api/authorize.do to obtain the authorization code, and then use /api/token.do to obtain access token . JWT login free method uses /api/authorizeByJWT.do or /account/t", "headings": [ { "level": 1, "title": "Development API Overview", "id": "development-api-overview" }, { "level": 2, "title": "Call overview", "id": "call-overview" }, { "level": 2, "title": "API Grouping", "id": "api-grouping" }, { "level": 2, "title": "Single interface page", "id": "single-interface-page" } ], "images": [], "text": "Development API Overview BabelBird develops APIs to connect the authentication, file, sharing, organization, messaging and login capabilities of enterprise network disks to third party business systems. The left column is grouped by interface function, and the callable endpoints are listed directly in the group. Call overview The enterprise administrator creates a developer account in the private cloud enterprise management background and obtains client id , client secret and JWT related keys. In the OAuth callback method, use /api/authorize.do to obtain the authorization code, and then use /api/token.do to obtain access token . JWT login free method uses /api/authorizeByJWT.do or /account/tokenLogin.do , and private deployment needs to enable the corresponding configuration. File access API requests need to carry Authorization: Bearer in the HTTP Header. POST, PUT, DELETE requests usually use Content Type: application/json . API Grouping Grouping Main purpose Typical entrance Authentication API Developer account, OAuth callback, JWT login free, Token acquisition and refresh Get token File API File list, file information, upload and download, version, move copy, recycle bin, material library classification Get file list Sharing API Sharing link, sharing permissions, participants, attention reminders Get file sharing url Enterprise API Enterprise information, departments, members, enterprise logs Get current enterprise information Message and login API Announcements, department discussions, JWT token login, common status codes JWT token login Single interface page Each API entry has an independent page, allowing developers to check paths, methods, parameters and return information by interface. GET authentication interface one (login callback method): /api/authorize.do GET authentication interface two (login free JWT token method): /api/authorizeByJWT.do POST Get token: /api/token.do POST refresh token: /api/refreshToken.do GET Get file list: /nd/api/file/list dir GET Get file information: /nd/api/file/fileinfo POST create folder: /nd/api/file/create folder GET preupload file: /api/file/preUploadFile.do GET Get download file address: /api/file/getFileDownloadUrl.do GET Get download multi file address: /api/file/downloadMultiFiles.do GET Get download file thumbnail address: /api/file/downloadThumbnail.do POST modify file information: /nd/api/file/update file POST modify file name: /nd/api/file/rename POST delete file (to recycle bin): /nd/api/file/remove file POST remove file (from trash): /nd/api/file/remove from trash POST Empty Trash: /nd/api/file/empty trash POST restore file (from recycle bin): /nd/api/file/restore file GET Get all version information of the file: /nd/api/file/versions POST setting file current version: /nd/api/file/version POST move file: /nd/api/file/move POST copy file: /nd/api/file/copy POST copy file progress: /nd/api/file/copy progress GET file log: /nd/api/file/file logs POST sets whether the user has permission to access the material library: /nd/api/file/set user access material library POST Create Material Library Classification: /nd/api/file/create material class POST create sub material library: /nd/api/file/create material folder GET Get the share url of the file: /nd/api/share/shareurl GET Get the shared permission list: /nd/api/share/share roles GET Get the sharing role that the user has permission to set for a single file: /nd/api/share/share role forfile POST Create Link Share: /nd/api/share/open link share POST close link sharing: /nd/api/share/close link share POST set link sharing password: /nd/api/share/set share password POST invite people to participate in sharing: /nd/api/share/invite share GET Get all sharing participants: /nd/api/share/share participants POST set permission roles of sharing participants: /nd/api/share/set participant role POST delete sharing participant: /nd/api/file/remove share participant POST reminder: /nd/api/file/focus file POST remove someone's attention: /nd/api/file/unfocus file GET Get the list of users focusing on the file: /nd/api/file/user focusfile GET Get the list of users who can focus on the file and mark the users who have focused on the file: /nd/api/file/user can focusfile GET Get current enterprise information: /nd/api/enterprise/current GET Get information about all departments of the enterprise: /nd/api/enterprise/departments POST Create Enterprise Department: /nd/api/enterprise/create department GET Get department role list: /nd/api/enterprise/dep role POST add department personnel: /nd/api/enterprise/add dep mem POST delete department personnel: /nd/api/enterprise/remove dep mem GET to obtain information about your own department: /nd/api/enterprise/mydeparments GET Get Department Members: /nd/api/enterprise/departmentmembers POST add enterprise members: /nd/api/enterprise/add ent mem POST update member information: /api/updateUserInfo.do GET Get enterprise member information: /api/getEnterpriseMember.do POST Get all members of the enterprise: /nd/api/enterprise/enterprise members POST Get Enterprise Logs: /nd/api/enterprise/enterprise logs POST Release Announcement: /nd/api/enterprise/broadcast GET Get published announcements: /nd/api/enterprise/broadcast POST Send Department Discussion: /nd/api/file/send dep discussion POST Get department discussion: /nd/api/file/dep discussion GET Get Enterprise Logs: /nd/api/enterprise/enterprise logs GET JWT token login: /account/tokenLogin.do" }, { "lang": "en", "slug": "developer-api-auth", "title": "Authentication and Token", "description": "Authentication and Token interface paths, methods, parameters and return fields.", "category": "Authentication API", "top_category": "API文档", "keywords": [ "API", "Authentication and Token", "Developer" ], "url": "en/developer-api-auth.html", "source": "content/en/developer-api-auth.md", "summary": "Authentication and Token PDF Page 1 Enterprise Development API V6.6 Shanghai Huaqing Information Technology Co., Ltd. Jiang Dajun PDF Page 2 Directory 1. Obtain an enterprise development account .................................................................................................................................................................................4 2. Authentication API ................................................................................................................................................................................................. 6 Authentication interface one (login callback method) .......................................................", "headings": [ { "level": 1, "title": "Authentication and Token", "id": "authentication-and-token" }, { "level": 3, "title": "PDF Page 1", "id": "pdf-page-1" }, { "level": 3, "title": "PDF Page 2", "id": "pdf-page-2" }, { "level": 3, "title": "PDF Page 3", "id": "pdf-page-3" }, { "level": 3, "title": "PDF Page 4", "id": "pdf-page-4" }, { "level": 2, "title": "1. Obtain an enterprise development account", "id": "1-obtain-an-enterprise-development-account" }, { "level": 3, "title": "PDF Page 5", "id": "pdf-page-5" }, { "level": 3, "title": "PDF Page 6", "id": "pdf-page-6" }, { "level": 2, "title": "2. Authentication API", "id": "2-authentication-api" }, { "level": 3, "title": "Authentication interface one (login callback method)", "id": "authentication-interface-one-login-callback-method" }, { "level": 3, "title": "PDF Page 7", "id": "pdf-page-7" }, { "level": 3, "title": "PDF Page 8", "id": "pdf-page-8" }, { "level": 3, "title": "Get token", "id": "get-token" }, { "level": 3, "title": "Refresh token", "id": "refresh-token" }, { "level": 2, "title": "3. File access API", "id": "3-file-access-api" }, { "level": 3, "title": "PDF Page 9", "id": "pdf-page-9" }, { "level": 3, "title": "Get file list", "id": "get-file-list" }, { "level": 3, "title": "Get file information", "id": "get-file-information" }, { "level": 3, "title": "PDF Page 10", "id": "pdf-page-10" }, { "level": 3, "title": "Create folder", "id": "create-folder" }, { "level": 3, "title": "Pre upload files", "id": "pre-upload-files" }, { "level": 3, "title": "PDF Page 11", "id": "pdf-page-11" }, { "level": 3, "title": "Upload files", "id": "upload-files" }, { "level": 3, "title": "PDF Page 12", "id": "pdf-page-12" }, { "level": 3, "title": "Get download file address", "id": "get-download-file-address" }, { "level": 3, "title": "Get download address of multiple files", "id": "get-download-address-of-multiple-files" }, { "level": 3, "title": "PDF Page 13", "id": "pdf-page-13" }, { "level": 3, "title": "Get download file thumbnail address", "id": "get-download-file-thumbnail-address" }, { "level": 3, "title": "Modify file information", "id": "modify-file-information" }, { "level": 3, "title": "Modify file information", "id": "modify-file-information-2" }, { "level": 3, "title": "Modify file name", "id": "modify-file-name" }, { "level": 3, "title": "Modify file information", "id": "modify-file-information-3" }, { "level": 3, "title": "PDF Page 14", "id": "pdf-page-14" }, { "level": 3, "title": "Delete files (to recycle bin)", "id": "delete-files-to-recycle-bin" }, { "level": 3, "title": "Delete files (from Recycle Bin)", "id": "delete-files-from-recycle-bin" }, { "level": 3, "title": "Empty the Recycle Bin", "id": "empty-the-recycle-bin" }, { "level": 3, "title": "Recover files (from Recycle Bin)", "id": "recover-files-from-recycle-bin" }, { "level": 3, "title": "PDF Page 15", "id": "pdf-page-15" }, { "level": 3, "title": "Get all version information of the file", "id": "get-all-version-information-of-the-file" }, { "level": 3, "title": "Set the current version of the file", "id": "set-the-current-version-of-the-file" }, { "level": 3, "title": "Move files", "id": "move-files" }, { "level": 3, "title": "Copy files", "id": "copy-files" }, { "level": 3, "title": "PDF Page 16", "id": "pdf-page-16" }, { "level": 3, "title": "Copy file progress", "id": "copy-file-progress" }, { "level": 3, "title": "File log", "id": "file-log" }, { "level": 3, "title": "Set whether the user has permission to access the material library", "id": "set-whether-the-user-has-permission-to-access-the-material-library" }, { "level": 3, "title": "PDF Page 17", "id": "pdf-page-17" }, { "level": 3, "title": "Create material library classification", "id": "create-material-library-classification" }, { "level": 3, "title": "Create sub material library", "id": "create-sub-material-library" }, { "level": 2, "title": "Shared file related API", "id": "shared-file-related-api" }, { "level": 3, "title": "PDF Page 18", "id": "pdf-page-18" }, { "level": 3, "title": "Get the sharing url of the file", "id": "get-the-sharing-url-of-the-file" }, { "level": 3, "title": "Get the sharing permission list", "id": "get-the-sharing-permission-list" }, { "level": 3, "title": "Get the sharing roles that the user has permission to set for a single file", "id": "get-the-sharing-roles-that-the-user-has-permission-to-set-for-a-single-file" }, { "level": 3, "title": "Create link to share", "id": "create-link-to-share" }, { "level": 3, "title": "PDF Page 19", "id": "pdf-page-19" }, { "level": 3, "title": "Close link sharing", "id": "close-link-sharing" }, { "level": 3, "title": "Set link sharing password", "id": "set-link-sharing-password" }, { "level": 3, "title": "Invite people to share", "id": "invite-people-to-share" }, { "level": 3, "title": "PDF Page 20", "id": "pdf-page-20" }, { "level": 3, "title": "Get all sharing participants", "id": "get-all-sharing-participants" }, { "level": 3, "title": "Set permission roles for sharing participants", "id": "set-permission-roles-for-sharing-participants" }, { "level": 3, "title": "Delete sharing participants", "id": "delete-sharing-participants" }, { "level": 3, "title": "PDF Page 21", "id": "pdf-page-21" }, { "level": 3, "title": "Reminder", "id": "reminder" }, { "level": 3, "title": "Remove someone’s attention", "id": "remove-someone-s-attention" }, { "level": 3, "title": "Get the list of users following the file", "id": "get-the-list-of-users-following-the-file" }, { "level": 3, "title": "Get the list of users who can follow the file, and mark the users who have followed the file", "id": "get-the-list-of-users-who-can-follow-the-file-and-mark-the-users-who-have-followed-the-file" }, { "level": 3, "title": "PDF Page 22", "id": "pdf-page-22" }, { "level": 2, "title": "Enterprise department related API", "id": "enterprise-department-related-api" }, { "level": 3, "title": "Get current enterprise information", "id": "get-current-enterprise-information" }, { "level": 3, "title": "Get information about all departments of the enterprise", "id": "get-information-about-all-departments-of-the-enterprise" }, { "level": 3, "title": "Create enterprise department", "id": "create-enterprise-department" }, { "level": 3, "title": "PDF Page 23", "id": "pdf-page-23" }, { "level": 3, "title": "Get the list of department roles", "id": "get-the-list-of-department-roles" }, { "level": 3, "title": "Add department personnel", "id": "add-department-personnel" }, { "level": 3, "title": "PDF Page 24", "id": "pdf-page-24" }, { "level": 3, "title": "Delete department personnel", "id": "delete-department-personnel" }, { "level": 3, "title": "Get information about your department", "id": "get-information-about-your-department" }, { "level": 3, "title": "Get department personnel", "id": "get-department-personnel" }, { "level": 3, "title": "PDF Page 25", "id": "pdf-page-25" }, { "level": 3, "title": "Add company members", "id": "add-company-members" }, { "level": 3, "title": "Update member information", "id": "update-member-information" }, { "level": 3, "title": "PDF Page 26", "id": "pdf-page-26" }, { "level": 3, "title": "Get enterprise member information", "id": "get-enterprise-member-information" }, { "level": 3, "title": "Get all members of the company", "id": "get-all-members-of-the-company" }, { "level": 3, "title": "Get enterprise logs", "id": "get-enterprise-logs" }, { "level": 3, "title": "PDF Page 27", "id": "pdf-page-27" }, { "level": 2, "title": "Message Push API", "id": "message-push-api" }, { "level": 3, "title": "Make an announcement", "id": "make-an-announcement" }, { "level": 3, "title": "Get published announcements", "id": "get-published-announcements" }, { "level": 3, "title": "Send department discussion", "id": "send-department-discussion" }, { "level": 3, "title": "PDF Page 28", "id": "pdf-page-28" }, { "level": 3, "title": "Get department discussion", "id": "get-department-discussion" }, { "level": 3, "title": "Get enterprise logs", "id": "get-enterprise-logs-2" }, { "level": 3, "title": "PDF Page 29", "id": "pdf-page-29" }, { "level": 2, "title": "4. JWT token login", "id": "4-jwt-token-login" }, { "level": 3, "title": "PDF Page 30", "id": "pdf-page-30" }, { "level": 2, "title": "5. Appendix Common API call return status code", "id": "5-appendix-common-api-call-return-status-code" }, { "level": 2, "title": "Status code result code", "id": "status-code-result-code" } ], "images": [], "text": "Authentication and Token PDF Page 1 Enterprise Development API V6.6 Shanghai Huaqing Information Technology Co., Ltd. Jiang Dajun PDF Page 2 Directory 1. Obtain an enterprise development account .................................................................................................................................................................................4 2. Authentication API ................................................................................................................................................................................................. 6 Authentication interface one (login callback method) ..................................................................................................................................................................6 Authentication interface two (login free method – JWT token method, in private cloud deployment, the jwt token login method needs to be enabled) .................................. 6 Get token .................................................................................................................................................................................................................8 Refresh token ..................................................................................................................................................................................................................8 3. File access API...................................................................................................................................................................................................... 8 Get file list ........................................................................................................................................................................................9 Get file information ........................................................................................................................................................................................9 Create a folder .................................................................................................................................................................................................10 Pre upload files ................................................................................................................................................................................................10 Uploading files .................................................................................................................................................................................................................11 Get the download file address .................................................................................................................................................................................12 Obtain the download address of multiple files .................................................................................................................................................................12 Get the download file thumbnail address .................................................................................................................................................................13 Modify file information .................................................................................................................................................................................13 Modify file name .................................................................................................................................................................................................13 Delete files (to Recycle Bin) ..................................................................................................................................................................................14 Deleting files (from Recycle Bin) ..................................................................................................................................................................14 Empty the Recycle Bin .................................................................................................................................................................................................14 Recovering files (from the Recycle Bin) ..................................................................................................................................................................14 Get all version information of a file .............................................................................................................................................................15 Current version of settings file .............................................................................................................................................................................15 Moving files .................................................................................................................................................................................................15 Copying files .................................................................................................................................................................................................15 Copying file progress ........................................................................................................................................................................................16 File Log .................................................................................................................................................................................................................16 Create library categories .................................................................................................................................................................................17 Create a sublibrary ............................................................................................................................................................................................17 Shared file related API ................................................................................................................................................................................. 17 Get the sharing url of the file ................................................................................................................................................................................. 18 Get the shared permission list .................................................................................................................................................................18 Obtain the sharing role that the user has permission to set for a single file .............................................................................................................................18 Create a link to share .................................................................................................................................................................................18 Turn off link sharing ........................................................................................................................................................................................19 Set link sharing password .................................................................................................................................................................................19 Invite people to share .................................................................................................................................................................19 Get all sharing participants .................................................................................................................................................................20 Set permission roles for sharing participants .............................................................................................................................................................20 Delete sharing participants ........................................................................................................................................................................20 Reminder...................................................................................................................................................................................................21 Remove someone from following .................................................................................................................................................................................21 Get the list of users following a file .................................................................................................................................................................21 Get the list of users who can follow the file and mark the users who have followed the file .............................................................................................21 Enterprise department related API ................................................................................................................................................................................. 22 Obtain current company information ..................................................................................................................................................................22 Obtain information from all departments of the enterprise ........................................................................................................................................................22 Creating a corporate division .................................................................................................................................................................................22 Get a list of department roles .................................................................................................................................................................................23 Add department personnel .................................................................................................................................................................................................23 Delete department personnel ................................................................................................................................................................................................24 Obtain information about your department .................................................................................................................................................................24 Obtain department personnel ................................................................................................................................................................................................24 Adding company members .................................................................................................................................................................................25 Update member information................................................................................................................................................................................25 Obtain enterprise member information .................................................................................................................................................................................26 Get all members of the company .................................................................................................................................................................................26 Obtain enterprise logs .................................................................................................................................................................................................26 Message push API................................................................................................................................................................................................................ 27 Announcement................................................................................................................................................................................................27 Get published announcements ................................................................................................................................................................................27 Send Department Discussion .................................................................................................................................................................................27 Get departmental discussions .................................................................................................................................................................................28 Obtain enterprise logs .................................................................................................................................................................................................28 4. JWT token login .................................................................................................................................................................................29 5. Appendix Common API call return status code ............................................................................................................................................................. 30 PDF Page 3 Status code result code .................................................................................................................................................................................................. 30 PDF Page 4 1. Obtain an enterprise development account Log in to the Babel Private Cloud Enterprise Management Backend and set up a developer account on the home page: After opening, fill in the callback function address: http://xxx.xxx.xxx.xxx/public/babelAuthResult.do After filling in and clicking OK, the developer ID (client id) and developer key (client secret) will be automatically generated: Note: jwtToken is the corresponding encryption key when generating jwtToken. PDF Page 5 PDF Page 6 2. Authentication API Authentication interface one (login callback method) /api/authorize.do HTTP request method GET URL parameters Parameter name Comment (description) response type must be code (required) string client id developer's id (required) string redirect uri callback function address, needs to be consistent with registration (required) string data: any data, string returned during callback For example: /api/authorize.do?response type=code&client id=xxxxx&redirect uri=http://xxx.xxx.xxx&data=xxx Access via browser Return results If the user is not logged in, it will jump to the login page. After logging in, if it is not authorized, it will 302 jump to the authorization page. If the user has been authorized, it will 302 jump to redirect uri and bring authorization code and data, similar to http://xxx.xxx.xxx?code=xxx&data=xxx The code is valid for 5 minutes. Authentication interface two (login free method – JWT token method. In private cloud deployment, the login method of jwt token needs to be enabled. formula) /api/authorizeByJWT.do HTTP request method GET URL parameters Parameter name Comment (description) response type must be code (required) string client id developer's id (required) string jwt token Jwt token, (required) string It is a string formed by encrypting {client id: xxxxxxx} email email (optional), enter the user's email address, log in as this user, leave it blank to log in as an enterprise administrator, string phone phone (optional), enter the user's mobile phone number and log in as this user. Leave it blank to log in as the enterprise administrator. string babelId babelId (optional), pass in the user's work ID, log in as this user, leave it blank to log in as the enterprise administrator, string PDF Page 7 For example: /api/authorizeByJWT.do?response type=code&client id=xxxxx&jwt token=xxx Note: When using this API, if you do not fill in email, phone, babelId, the system will automatically log in as an administrator, otherwise it will log in as the user corresponding to email, phone, babelId. Log in, the login interface will not be displayed to log in. Note (email, phone, babelId) only needs one of them. Return results { \"success\": true \"code\": \"xxxxxxxxxxxxxxxxxxxxxxxxxxx\", } jwt token is generated by writing your own program. The sample code is as follows: import java.util.Date; import java.util.HashMap; import java.util.Map; import javax.crypto.SecretKey; import javax.crypto.spec.SecretKeySpec; import io.jsonwebtoken.Claims; import io.jsonwebtoken.JwtBuilder; import io.jsonwebtoken.Jwts; import io.jsonwebtoken.SignatureAlgorithm; import net.sf.json.JSONObject; / Generate token used by standard jwt / public class JWT App { static String skey = \"babeldfdfer95840834 t8e 9 9 5934 5943 5886256\"; // The key is the jwtToken field filled in the developer account in the Babel backend. public static void main( String[] args ) { HashMap clientInfo = new HashMap (); clientInfo.put(\"client id\", \"7459492016147273\"); // is the client id in the developer account try { String token = createTokenJWT(clientInfo); System.out.println(\" login token:\" + token); String token1 = \"eyJhbGciOiJIUzI1NiJ9.eyJkdXJhdGlvbiI6NjAsInBheWxvYWQiOnsiY2xpZW50X2lk IjoiNzQ1OTQ5MjAxNjE0NzI3MyJ9LCJ0aW1lIjoxNjkxNDg4MzY4NTk0fQ.pRFCwXd2snMr IgFWOFwYbvyAeeNhoFINGk Wmv7d24g\"; JSONObject parsed = parseTokenJWT(token1); System.out.println(\" parsed:\" + parsed); System.out.println(\" Just put this token as a parameter in the url, such as: \"); } catch (Exception e) { System.out.println(e.getMessage()); } } public static String createTokenJWT(Map config) throws Exception { HashMap data = new HashMap (); data.put(\"time\", new Date().getTime()); data.put(\"duration\", 60); data.put(\"payload\", config); SignatureAlgorithm signatureAlgorithm = SignatureAlgorithm.HS256; SecretKey key = generalKey(); JwtBuilder builder = Jwts.builder() .setClaims(data) .signWith(signatureAlgorithm, key); System.out.println( \" builder : \" + builder); return builder.compact(); } public static JSONObject parseTokenJWT(String jwt) throws Exception { SecretKey key = generalKey(); Claims claims = Jwts.parser() .setSigningKey(key) .parseClaimsJws(jwt) .getBody(); System.out.println(\" claims:\" + claims.toString()); Long time = (Long)claims.get(\"time\"); long duration = (Integer)claims.get(\"duration\"); Long now = new Date().getTime(); if (now time 1000 duration) return null; // Tokens older than 10 minutes are invalid JSONObject obj = JSONObject.fromObject(claims.get(\"payload\")); return obj; } public static SecretKey generalKey(){ String stringKey = skey; byte[] encodedKey = stringKey.getBytes(); SecretKey key = new SecretKeySpec(encodedKey, 0, encodedKey.length, \"HmacSHA256\"); return key; } } PDF Page 8 Get token /api/token.do HTTP method: POST HTTP Header This interface uses Basic Auth to verify client information. The specific method is to add something like \"Authorization: Basic xxxxxxxxx\" in the header. Among them \"xxxxxxxxx\" is calculated from the developer id (client id) and developer secret key (client secret). The specific algorithm is Base64Encode(client id + \":\" + client secret) Base64Encode Choose your own tool for Base64 encoding URL parameters Parameter name Comment (description) grant type (required) must be authorization code string code (required) Authorization code, that is, the authorization code received by the callback address. The authorization code is valid for 5 minutes. It is used once, regardless of success. If it still fails, the authorization code will become invalid string For example: /api/token.do?grant type=authorization code&code=xxx&redirect uri=http://xxx.xxx.xxx Return results access token interface access token refresh token is used to refresh access token, valid for 30 days The validity time of expires in access token, unit is s Refresh token /api/refreshToken.do HTTP method: POST HTTP Header This interface uses Basic Auth to verify client information. The specific method is to add something like \"Authorization: Basic xxxxxxxxx\" in the header. Among them \"xxxxxxxxx\" is calculated through client id and client secret. The specific algorithm is Base64Encode(client id + \":\" + client secret) URL parameters Parameter name Comment (description) grant type (required) must be refresh token string refresh token (required) is the refresh token string obtained in interface 2 For example: /api/refreshToken.do?grant type=refresh token&refresh token=xxx Return results access token interface access identification, refresh token is used to refresh access token, valid for 30 days The validity time of expires in access token is 3600, the unit is s 3. File access API All interfaces need to carry access token in the HTTP header when accessing. For interfaces containing request parameters, usually some POST, PUT or DELETE interface, you also need to set Content Type to specify the format of the parameters. If you need to access different versions of the API, you need Specify a specific version on the request path. If you need to return a response body in a different format, you also need to set Accept. All parameters should be This should use utf 8 encoding. PDF Page 9 Headers: Authorization: stores access token, the format is: \"Bearer \" + access token. Content Type: Indicates the format of the request parameters. If it is a POST, PUT or DELETE request, you need to specify \"application/json\", I We currently do not support other request parameter formats, such as xml. If it is other types such as GET requests, it does not need to be set in the header. Content Type. Accept: used to specify the format of the response result and the version information of the api. Currently, only response in json format is supported, so in general Specify \"application/json\". If the interface access is successful, we will return a response in json format, and the HTTP status code is 200. All successful response responses All json will contain \"success: true\". The X Babel Version in the header of the response indicates the version number of the api accessed by this request. Get file list /nd/api/file/list dir HTTP method: GET URL parameters Parameter name Comment (description) parent id parent folder id (required) string When parent is 1, returns the contents of the corporate folder, 2 returns the contents of the personal folder, 3 returns my Project, 4 returns the share I added, and other fileId returns the contents of the normal folder. page size page size number page page number type type: divided into three types: 1 file, 2 folder, 0 all string Return field description Attribute name type description files array file information {fileId, name, …} total int total quantity page int page capacity success boolean gets the success mark code int returns error code 0 indicates success Get file information /nd/api/file/fileinfo HTTP method: GET URL parameters Parameter name Comment (description) id file id (required) string Return field description fileInfo information Attribute name type description file Object file information { id, name, …} PDF Page 10 success boolean gets the success mark code int returns error code 0 indicates success Create folder /nd/api/file/create folder HTTP method: POST POST request body parameters Parameter name Comment (description) parent id target folder id (required) string name file name (required) string Return field description Attribute name type description file Object file information { id, name, …} success boolean gets the success mark code int returns error code 0 indicates success Pre upload files Used to return the parameters (url, upload token) required when uploading files in the second step. /api/file/preUploadFile.do HTTP method: GET URL parameters Parameter name Comment (description) parent id target folder id (required) (you can ignore this when uploading in the root directory) string name file name (required) string file id When uploading a new version, you need to specify the new version of the file to upload (you can ignore this when uploading new files) string The correct return result is as follows {\"upload token\":\"92808ecfc2ac4e0ebc0b912edac3be4a\",\"url\":\"http://testdocument.babel.cc/api/file/uploadPdf.do\",\"su ccess\":true,\"code\":0} Return field description Attribute name type description url string This url can only be used once and is valid for 1 hour. Call this url to upload a file. After success, fileId, fileName, version, etc. will be returned. upload token string is used as a parameter of post when uploading files. PDF Page 11 Upload files Note that the URL of this API is returned by the pre upload interface. There is no specific URL here, just parameter description. https://xxx.xxx.xxx:xxx/api/file/uploadXXX.do (the specific URL is the URL returned by /api/file/preUploadFile.do in the previous section) POST POST request body parameters Parameter name Comment (description) file file binary data (upload data) Return value in upload token /api/file/preUploadFile.do request The return information is as follows {\"fileId\":\"7728538212615908\",\"version\":0,\"fileName\":\"mesos.pdf\",\"fileSize\":848854,\"success\":true,\"code\":0} Upload relevant code examples Add ‘com.squareup.okhttp3:okhttp:3.3.1’ package private void uploadFile(final String fileName, String parentId, final DaoCallback callback){ preUploadFile(fileName, parentId, new DaoCallback () { @Override public void onSuccess(JSONObject data) { int code = data.optInt(\"code\", 1); final String url = data.optString(\"url\", null); final String uploadToken = data.optString(\"upload token\"); if (code == 0) { // File file = new File(filePath); RequestBody fileContent = RequestBody.create(MultipartBody.FORM, file); RequestBody requestBody = new MultipartBody.Builder() .setType(MultipartBody.FORM) .addFormDataPart(\"file\", fileName, fileContent) .addFormDataPart(\"upload token\", uploadToken) .build(); Request request = new Request.Builder() .url(url) .post(requestBody) .build(); // Uploading takes a long time, so you need to set a longer timeout OkHttpClient okHttpClient = new OkHttpClient(); okHttpClient.newCall(request) .enqueue(new okhttp3.Callback() { @Override public void onFailure(okhttp3.Call call, IOException e) { callback.onFailure( 1, null); } @Override public void onResponse(okhttp3.Call call, okhttp3.Response response) throws IOException { int httpCode = response.code(); if (httpCode == 200) { try { JSONObject result = new JSONObject(response.body().string()); response.body().close(); boolean success = result.getBoolean(\"success\"); if (success) { callback.onSuccess(null); } else { int code = result.getInt(\"code\"); String msg = result.optString(\"msg\"); callback.onFailure(code, msg); } } catch (JSONException e) { callback.onFailure( 2, null); } } else { callback.onFailure(httpCode, null); } } }); } } @Override public void onFailure( int errorCode, String msg){ Log.e(\"FileTransfer\", \"filePreUpload failed errorCode=\" + errorCode); } }); } PDF Page 12 private void preUploadFile(String fileName, String parentId, final DaoCallback callback) { String preUploadUrl = \"http://private.babel.cc:80/api/file/preUploadFile.do?name=1234.jpg&parent id=0\"; // Pass in the corresponding parameters name, parent id String authorization = \"Bearer d48d0a0e253c4a2985d8c5653f717d71\"; //Generate according to the instructions Request request = new Request.Builder().url(preUploadUrl) .addHeader(\"Authorization\", authorization) .build(); OkHttpClient okHttpClient = new OkHttpClient(); okHttpClient.newCall(request).enqueue(new okhttp3.Callback() { @Override public void onFailure(okhttp3.Call call, IOException e) { Log.d(\"\", \"\"); } @Override public void onResponse(okhttp3.Call call, okhttp3.Response response) throws IOException { Log.d(\"\",\"\"); int httpCode = response.code(); if (httpCode == 200) { JSONObject result = null; try { result = new JSONObject(response.body().string()); } catch (JSONException e) { e.printStackTrace(); } try { boolean success = result.getBoolean(\"success\"); if (success) { String url = result.getString(\"url\"); callback.onSuccess(result); } else { int code = result.getInt(\"code\"); String msg = result.optString(\"msg\"); callback.onFailure(code, msg); } } catch (JSONException e) { callback.onFailure( 2, null); } } else { callback.onFailure(httpCode, null); } } }); } Get download file address /api/file/getFileDownloadUrl.do HTTP method: GET URL parameters Parameter name Comment (description) fileId file id to be downloaded (required) string version The version number of the file (optional) number The return information is as follows {\"code\":0,\"success\":true,\"type\":\"File type\",\"url\":\"File download address\"} Get download address of multiple files /api/file/downloadMultiFiles.do HTTP method: GET URL parameters Parameter name Comment (description) fileIdArr is a string composed of the id of the file to be downloaded, separated by the symbol \"!\" (half width), for example, the download ids are 133 and 233. file, the value of fileIdArr is \"133!233\" string type PDF Page 13 The return information is as follows {\"code\":0,\"success\":true,\"type\":\"File type\",\"url\":\"File download address\"} The return value url is the download address of multiple files packaged. Get download file thumbnail address /api/file/downloadThumbnail.do HTTP method: GET URL parameters Parameter name Comment (description) fileId file id to be downloaded (required) string version The version number of the file (optional) number size is the size of the thumbnail to be displayed, taking the maximum value of width and height. The return information is as follows {\"code\":0,\"success\":true, \"url\":\"File download address\"} The return value url is the download address of multiple files packaged. Modify file information /nd /api/file/update file HTTP method: POST Modify file information POST request body parameters Parameter name Comment (description) file id file id (required) string name new file name (optional) string description file description (optional) string The return information is as follows {\"code\":0,\"success\":true} Modify file name /nd /api/file/rename HTTP method: POST Modify file information POST request body parameters Parameter name Comment (description) file id file id (required) string name new file name string The return information is as follows {\"code\":0,\"success\":true} PDF Page 14 Delete files (to recycle bin) /nd /api/file/remove file HTTP method: POST POST request body parameters Parameter name Comment (description) file ids[] target file id array (required) string[] The return information is as follows {\"code\":0,\"success\":true} Delete files (from Recycle Bin) /nd /api/file/remove from trash HTTP method: POST POST request body parameters Parameter name Comment (description) file ids[] target file id array (required) string[] The return information is as follows {\"code\":0,\"success\":true} Empty the Recycle Bin /nd /api/file/empty trash HTTP method: POST POST request body parameters Parameter name Description The return information is as follows {\"code\":0,\"success\":true} Recover files (from Recycle Bin) /nd /api/file/restore file HTTP method: POST POST request body parameters Parameter name Comment (description) file ids[] target file id array string[] restoreAll If file ids is not filled in, restoreAll is true to restore all files in the recycle bin, boolean The return information is as follows PDF Page 15 {\"code\":0,\"success\":true} Get all version information of the file /nd /api/file/versions HTTP method: GET URL parameters Parameter name Comment (description) file id target file id (required) string The return information is as follows {\"code\":0,\"versions\":[],\"success\":true} Set the current version of the file /nd /api/file/version HTTP method: POST POST request body parameters Parameter name Comment (description) file id target file id (required) string version version number (required) number The return information is as follows {\"code\":0,\"success\":true} Move files /nd /api/file/move HTTP method: POST POST request body parameters Parameter name Comment (description) file ids Target file id array to be moved (required) string target id The target folder id that needs to be moved to (required) string The return information is as follows {\"code\":0,\"success\":true} Copy files /nd /api/file/copy HTTP method: POST POST request body parameters Parameter name Comment (description) PDF Page 16 file ids Target file id array to be copied (required) string target id The id of the target folder to be copied to (required) string The return information is as follows { \"code\": 0, \"copyKey\": \"81427630 054a 11ef 8355 db93b4b1d006\", \"fileNum\": 10, \"success\": true} Copy file progress /nd /api/file/copy progress HTTP method: POST POST request body parameters Parameter name Comment (description) copyKey Check the copy progress copyKey is returned by the copy interface (required) string The return information is as follows { \"code\": 0, \"completed\": 10, \"total\": 10, \"result\": {}, \"success\": true} File log /nd /api/file/file logs HTTP method: GET GET request body parameters Parameter name Comment (description) file id target file id array (required) string startIndex gets the starting order of logs. Which log should be returned (optional) int defaults to 0. pageSize The number of items returned per page (optional) int type Log type (optional) int Default 0, view all records, 1 only view access records, 2 only view uploads and downloads, 3 only view anonymous users Users, 4 only view sharing and invitations, 5 only view deletion records userName A username (optional) string, returns the log of a certain user lang language (optional) default cn, string language of returned log cn (Chinese) en (English) The return information is as follows {\"code\":0,\"success\":true, \"logs\":[], \"total\":50} Set whether the user has permission to access the material library /nd /api/file/ set user access material library HTTP method: POST GET request body parameters Parameter name Comment (description) userId user's id array type [usrId1, userId2] (required) string can Whether it is accessible Numeric type (required) int Default 0, 0: Inaccessible, 1: Accessible The return information is as follows {\"code\":0,\"success\":true} PDF Page 17 Create material library classification /nd /api/file/create material class HTTP method: POST POST request body parameters Parameter name Comment (description) destDirFileId fileId of the destination folder (required) string name The name of the created category library (required) string accessType Classification visibility (optional) Defaults to public 0. 0: // public 1: // Need to apply 2: // Department is public 3: // Department application 4: // Confidential managerIds The id array type of the person in charge [usrId1,userId2] departmentIds Classification visibility limited department id of department (optional) Array type [departmentId1,departmentId2] The return information is as follows {\"code\":0, \"success\":true, \"materialClass\": {}} Create sub material library /nd /api/file/create material folder HTTP method: POST POST request body parameters Parameter name Comment (description) destDirFileId fileId of the destination folder (required) string name The name of the created category library (required) string accessType Classification visibility (optional) Defaults to public 0. 0: // public 1: // Need to apply 2: // Department is public 3: // Department application 4: // Confidential managerId The id of the person in charge (optional) string departmentIds Classification visibility limited department id of department (optional) Array type [departmentId1,departmentId2] assistantIds ID of the material library assistant (optional) Array type [usrId1,userId2] The return information is as follows {\"code\":0, \"success\":true, \"materialFolder\": {}} Shared file related API PDF Page 18 Get the sharing url of the file /nd/api/share/shareurl HTTP method: GET Get the sharing link of the file (open the sharing first, and then get the link) URL parameters Parameter name Comment (description) file id file id string is https Whether the returned share url protocol is https 0 means http, 1 means https, default 0 number Return field description {\"code\":0,\"url\":\"https://private.babel.cc/share.do?s=http://private.babel.cc/share.do?s=MjY2OTYzNTk3OTU2NzEzOTtXZWQgSnVsIDAxIDIwMj AgMTg6MzM6NTAgR01UKzA4MDAgKEhvbmcgS29uZyBTdGFuZGFyZCBUaW1lKQ%3D%3D\",\"success\":true} Get the sharing permission list /nd/api/share/share roles HTTP method: GET URL parameters Parameter name Comment (description) Return field description {\"code\":0,\"roles\":[],\"success\":true} Get the sharing roles that the user has permission to set for a single file /nd/api/share/share role forfile HTTP method: GET URL parameters Parameter name Comment (description) file id file id string Return field description {\"code\":0,\"roles\":[],\"success\":true} Create link to share /nd/api/share/open link share HTTP method: POST Open sharing and get a new sharing link. The previous link will be invalid. PDF Page 19 POST request body parameters Parameter name Comment (description) file id pre shared file id (required) string link role id shared role string is https Whether the returned share url protocol is https number anonymousVisit Whether to allow anonymous access, 1 means allowed, 0 means not allowed (optional, default is 1) number Return field description {\"code\":0,\"share url\":\"http://private.babel.cc/share.do?s=http://private.babel.cc/share.do?s=MjY2OTYzNTk3OTU2NzEzOTtXZWQgSnV sIDAxIDIwMjAgMTg6MzM6NTAgR01UKzA4MDAgKEhvbmcgS29uZyBTdGFuZGFyZCBUaW1lKQ%3D%3D\",\"password\":\"\",\"success\":tru e} Close link sharing /nd/api/share/close link share HTTP method: POST Close the shared link I opened POST request body parameters Parameter name Comment (description) file id shared file id (required) string Return field description {\"code\":0,\"success\":true} Set link sharing password /nd/api/share/set share password HTTP method: POST File link sharing is turned on, set a password for link sharing. POST request body parameters Parameter name Comment (description) file id pre shared file id (required) string password password for link sharing string is https Whether the returned share url protocol is https number Return field description {\"code\":0,\"success\":true, \"share url\": \"http://private.babel.cc/share.do?s=xxxxxxxxxxx\"} Invite people to share /nd/api/share/invite share HTTP method: POST PDF Page 20 You can invite certain people to access files based on the user's email or mobile phone POST request body parameters Parameter name Comment (description) file id file id (required) string share role ID of the shared permission (all the above people share this permission) (required) string emails[] email array string[] phones[] array of mobile phone numbers string[] Return field description {\"code\":0,\"success\":true} Get all sharing participants /nd/api/share/share participants HTTP method: GET URL parameters Parameter name Comment (description) file id file id (required) string Return field description {\"code\":0,\"users\":[],\"success\":true} Set permission roles for sharing participants /nd/api/share/set participant role HTTP method: POST POST request body parameters Parameter name Comment (description) file id file id (required) string babelshare id int (required) user id string role id int (required) role id string Return field description {\"code\":0,\"success\":true} Delete sharing participants /nd/api/file/remove share participant HTTP method: POST POST request body parameters Parameter name Comment (description) PDF Page 21 file id file id (required) string babelshare ids[] int (required) user id string Return field description {\"code\":0,\"success\":true} Reminder /nd/api/file/focus file HTTP method: POST POST request body parameters Parameter name Comment (description) file id file id (required) string user ids[] The id of the user to be reminded. This id should be selected among the file participants, otherwise the reminder will not work (required) string[] Return field description {\"code\":0,\"success\":true} Remove someone’s attention /nd/api/file/unfocus file HTTP method: POST POST request body parameters Parameter name Comment (description) file id file id (required) string user ids[] The id of the user to be reminded. This id should be selected among the file participants, otherwise the reminder will not work (required) string[] Return field description {\"code\":0,\"success\":true} Get the list of users following the file /nd/api/file/user focusfile HTTP method: GET URL parameters Parameter name Comment (description) file id file id (required) string Return field description {\"code\":0,\"users\":[],\"success\":true} Get the list of users who can follow the file, and mark the users who have followed the file /nd/api/file/user can focusfile PDF Page 22 HTTP method: GET URL parameters Parameter name Comment (description) file id file id (required) string Return field description Enterprise department related API Get current enterprise information /nd/api/enterprise/current HTTP method: GET URL parameters Parameter name Comment (description) None Return field description {\"code\":0,\"enterprise\":{},\"success\":true} Get information about all departments of the enterprise /nd/api/enterprise/departments HTTP method: GET URL parameters Parameter name Comment (description) None Return field description Attribute name type description departments [] array returns all department information tree {}json data returns the parent child structure information of the department code int successboolean Create enterprise department /nd/api/enterprise/create department HTTP method: POST PDF Page 23 POST request body parameters Parameter name Comment (description) parent dep parent department id, 0 means following department (required) string name department name (required) string description department description string Return field description Attribute name type description department {} json data structure code int successboolean Get the list of department roles /nd/api/enterprise/dep role HTTP method: GET URL parameters Parameter name Comment (description) Return field description Attribute name type description roles []array { id, filePermission,enterpriseId,filePermission,managerPermission, default,nameEn,name} code int successboolean Add department personnel /nd/api/enterprise/add dep mem HTTP method: POST POST request body parameters Parameter name Comment (description) department id department id (required) string user ids[] user list string[] role id The user's role in the department string PDF Page 24 Return field description Attribute name type description Delete department personnel /nd/api/enterprise/remove dep mem HTTP method: POST POST request body parameters Parameter name Comment (description) department id department id (required) string user ids[] Person’s id (required) string[] Return field description Attribute name type description Get information about your department /nd/api/enterprise/mydeparments HTTP method: GET URL parameters Parameter name Comment (description) None Return field description Attribute name type description departments [] array returns my department information code int successboolean Get department personnel /nd/api/enterprise/departmentmembers PDF Page 25 HTTP method: GET URL parameters Parameter name Comment (description) department id department id (required) string Return field description Attribute name type description users array: {id, name, avatrUrl,} Add company members /nd/api/enterprise/add ent mem HTTP method: POST POST request body parameters Parameter name Comment (description) email Email mailbox string password password string enterprise role enterprise member role, optional number department ids[] The user's department, optional string[] department roles[] Roles in the department, optional string[] sex 0 not set 1 male 2 female number name username string phone mobile phone number, optional string babelId employee ID, optional string spacelimit personal space limit, unit GB, 0 means no limit number can ownfile whether the user can have personal files, 1 use the overall enterprise settings, 0 no personal files, 1 have personal files number remarks user description, optional string join time The time when the user joined the enterprise, Unix time, unit number seconds password is md5 Whether the incoming password requires md5 encryption, 0 non md5 password, 1 md5 encrypted password number Update member information /api/updateUserInfo.do HTTP method: POST POST request body parameters Parameter name Comment (description) email email address (search keyword, required) string password password (change password, optional) string frozen 1 – means frozen, 0 – means unfrozen (freeze the account, optional) number password is md5 Whether the incoming password requires md5 encryption, 0 non md5 password, 1 md5 encrypted password number phone mobile phone number (optional) string PDF Page 26 Get enterprise member information /api/getEnterpriseMember.do HTTP method: GET URL parameters Parameter name Comment (description) email email address (search keyword) string phone mobile phone number (search keyword) string babelId employee number (search keyword) string email/phone/babelId you can choose one Return field description {\"code\":0,\"success\":true,\"user\":{}} Get all members of the company /nd/api/enterprise/enterprise members HTTP method: POST POST request body parameters Parameter name Comment (description) lang language type, cn Chinese, en English, optional options { departmentId: //Department id, if not filled in, it means all employees of the enterprise roleId: // Role id, if not filled in, there is no role limit \"userType\": 0, // 0 internal personnel, 1 external personnel \"keyName\": \"\", // Search keywords: name, mobile phone number, email address, if not filled in, it means all people \"startIndex\": 0, \"pageSize\": 20, status: // 0 all accounts, 1 deactivated accounts } Optional Return field description {\"code\":0,\"success\":true,\"members\":{},\"total\":xx} Get enterprise logs /nd/api/enterprise/enterprise logs HTTP method: POST POST request body parameters Parameter name Comment (description) department id department id, if not filled in, it will be the log of all departments string optional keyword related search keyword string optional PDF Page 27 startTime log starting time number optional endTime log end time number optional startIndex int optional pageSize int optional Return field description {\"code\":0,\"success\":true,\"logs\":{},\"total\":xx} Message Push API Make an announcement /nd/api/enterprise/broadcast HTTP method: POST POST request body parameters Parameter name Comment (description) title Announcement content string (required) string content content (required) string target users[] UserId array, if empty, it means all users will receive it, string[] target deps[] Target department, all members of this department and sub departments will receive notification, string[] Target users and target deps must be filled in at least 1 Return field description {\"code\":0,\"success\":true} Get published announcements /nd/api/enterprise/broadcast HTTP method: GET URL parameters Parameter name Comment (description) start index number pagesize number Return field description {\"code\":0,\"broadcasts\":[],\"total\":19,\"success\":true} Send department discussion /nd/api/file/send dep discussion HTTP method: POST PDF Page 28 POST request body parameters Parameter name Comment (description) dep id department id (required) string message information character (required) string json string, format {Type: “Text”, Body: “Hello” } Return field description {\"code\":0,\"messageId\":99,\"success\":true} Get department discussion /nd/api/file/dep discussion HTTP method: POST POST request body parameters Parameter name Comment (description) dep id department id (required) string pagesize page size string start id message id, only the messages before this message will be obtained, if it is empty, the latest message will be obtained string Return field description {\"msgArr\":[],\"gotMoreMessages\":1,\"code\":0,\"success\":true} Get enterprise logs /nd/api/enterprise/enterprise logs HTTP method: GET URL parameters Parameter name Comment (description) department id department id() string pagesize page size number, default value 1000 start index message starting position, number keyword log keyword string startTime start date: seconds number endTime expiration date seconds number Return field description {\"logs\":[],\"total\":0,\"code\":0,\"success\":true} total returns all those that meet the conditions (regardless of paging pageSize) PDF Page 29 4. JWT token login In private cloud deployment, the login method of jwt token can be enabled. In this case, the following url is allowed to directly enter the network disk system as a user without logging in. System: /account/tokenLogin.do Parameters: Parameter name Optional Description Optional value Default value userToken is required and contains the encrypted information of the logged in user (Constructor None See the instructions below for details) fileId optional The id of the file (folder) to be accessed, if not None If filled in, the user root directory will be opened. closeTitleBar optional Whether to close the title bar 1 Close 0 Do not close 0 disableEntMark Optional Whether to hide the corporate logo in the upper left corner 1 Hide 0 Do not hide 0 disableUserMark Optional Whether to hide the user settings entrance in the upper right corner 1 Hide 0 Do not hide 0 defaultLang optional Set the language used by the interface cn Chinese en English zh HK Traditional cn defaultClrTheme is optional and sets the interface color theme. normal is the standard mode, dark is the dark mode normal. For example, the following is the user root interface in English and dark mode with the user logo in the upper right corner hidden. /account/tokenLogin.do userToken=xxxxxxxxxxxxxxxx defaultClrTheme=dark defaultLang=en disableUserMark=1 Construction of userToken userToken is an encrypted string containing logged in user information. The encrypted information is a password created by JWT, a standard security mechanism for transmitting trusted data between two parties. The content of JWT encrypted user information JSONObject is as follows: { payload: { email: “xxx@xxx.com”/“135XXXXXXX”/“XXXX”} time: now } Note: email can be an email address, mobile phone number, or work number; The code is as follows: public static void main( String[] args ) { HashMap user = new HashMap (); user.put(\"email\", \"yuanchaozhao@qq.com\"); try { //token login String userToken = createTokenJWT(user); System.out.println(\" login token:\" + userToken); JSONObject parsed = parseTokenJWT(userToken); System.out.println(\" parsed:\" + parsed); System.out.println(\" Just put this token as a parameter in the url, such as: \"); System.out.println(\"/account/tokenLogin.do?userToken=\" + userToken); } catch (Exception e) { System.out.println(e.getMessage()); } } For other codes, please refer to the jwtToken generation code, which is provided in the authentication interface 2. Remarks: JWT is the abbreviation of JSON Web Tokens. It is a communication encryption and decryption mechanism that meets the industry standard RFC7519. Please refer to: https://jwt.io/ PDF Page 30 5. Appendix Common API call return status code Status code result code Code value Description 0 success 1 unknown error 2 parameter error 7 Not enough space 12 Prohibited user actions 13 invalid token the end" }, { "lang": "en", "slug": "developer-api-files", "title": "File API", "description": "Interface paths, methods, parameters, and return fields for the File API.", "category": "File API", "top_category": "API文档", "keywords": [ "API", "File API", "Developer" ], "url": "en/developer-api-files.html", "source": "content/en/developer-api-files.md", "summary": "File API PDF Page 1 Enterprise Development API V6.6 Shanghai Huaqing Information Technology Co., Ltd. Jiang Dajun PDF Page 2 Directory 1. Obtain an enterprise development account .................................................................................................................................................................................4 2. Authentication API ................................................................................................................................................................................................. 6 Authentication interface one (login callback method) .......................................................................", "headings": [ { "level": 1, "title": "File API", "id": "file-api" }, { "level": 3, "title": "PDF Page 1", "id": "pdf-page-1" }, { "level": 3, "title": "PDF Page 2", "id": "pdf-page-2" }, { "level": 3, "title": "PDF Page 3", "id": "pdf-page-3" }, { "level": 3, "title": "PDF Page 4", "id": "pdf-page-4" }, { "level": 2, "title": "1. Obtain an enterprise development account", "id": "1-obtain-an-enterprise-development-account" }, { "level": 3, "title": "PDF Page 5", "id": "pdf-page-5" }, { "level": 3, "title": "PDF Page 6", "id": "pdf-page-6" }, { "level": 2, "title": "2. Authentication API", "id": "2-authentication-api" }, { "level": 3, "title": "Authentication interface one (login callback method)", "id": "authentication-interface-one-login-callback-method" }, { "level": 3, "title": "PDF Page 7", "id": "pdf-page-7" }, { "level": 3, "title": "PDF Page 8", "id": "pdf-page-8" }, { "level": 3, "title": "Get token", "id": "get-token" }, { "level": 3, "title": "Refresh token", "id": "refresh-token" }, { "level": 2, "title": "3. File access API", "id": "3-file-access-api" }, { "level": 3, "title": "PDF Page 9", "id": "pdf-page-9" }, { "level": 3, "title": "Get file list", "id": "get-file-list" }, { "level": 3, "title": "Get file information", "id": "get-file-information" }, { "level": 3, "title": "PDF Page 10", "id": "pdf-page-10" }, { "level": 3, "title": "Create folder", "id": "create-folder" }, { "level": 3, "title": "Pre upload files", "id": "pre-upload-files" }, { "level": 3, "title": "PDF Page 11", "id": "pdf-page-11" }, { "level": 3, "title": "Upload files", "id": "upload-files" }, { "level": 3, "title": "PDF Page 12", "id": "pdf-page-12" }, { "level": 3, "title": "Get download file address", "id": "get-download-file-address" }, { "level": 3, "title": "Get download address of multiple files", "id": "get-download-address-of-multiple-files" }, { "level": 3, "title": "PDF Page 13", "id": "pdf-page-13" }, { "level": 3, "title": "Get download file thumbnail address", "id": "get-download-file-thumbnail-address" }, { "level": 3, "title": "Modify file information", "id": "modify-file-information" }, { "level": 3, "title": "Modify file information", "id": "modify-file-information-2" }, { "level": 3, "title": "Modify file name", "id": "modify-file-name" }, { "level": 3, "title": "Modify file information", "id": "modify-file-information-3" }, { "level": 3, "title": "PDF Page 14", "id": "pdf-page-14" }, { "level": 3, "title": "Delete files (to recycle bin)", "id": "delete-files-to-recycle-bin" }, { "level": 3, "title": "Delete files (from Recycle Bin)", "id": "delete-files-from-recycle-bin" }, { "level": 3, "title": "Empty the Recycle Bin", "id": "empty-the-recycle-bin" }, { "level": 3, "title": "Recover files (from Recycle Bin)", "id": "recover-files-from-recycle-bin" }, { "level": 3, "title": "PDF Page 15", "id": "pdf-page-15" }, { "level": 3, "title": "Get all version information of the file", "id": "get-all-version-information-of-the-file" }, { "level": 3, "title": "Set the current version of the file", "id": "set-the-current-version-of-the-file" }, { "level": 3, "title": "Move files", "id": "move-files" }, { "level": 3, "title": "Copy files", "id": "copy-files" }, { "level": 3, "title": "PDF Page 16", "id": "pdf-page-16" }, { "level": 3, "title": "Copy file progress", "id": "copy-file-progress" }, { "level": 3, "title": "File log", "id": "file-log" }, { "level": 3, "title": "Set whether the user has permission to access the material library", "id": "set-whether-the-user-has-permission-to-access-the-material-library" }, { "level": 3, "title": "PDF Page 17", "id": "pdf-page-17" }, { "level": 3, "title": "Create material library classification", "id": "create-material-library-classification" }, { "level": 3, "title": "Create sub material library", "id": "create-sub-material-library" }, { "level": 2, "title": "Shared file related API", "id": "shared-file-related-api" }, { "level": 3, "title": "PDF Page 18", "id": "pdf-page-18" }, { "level": 3, "title": "Get the sharing url of the file", "id": "get-the-sharing-url-of-the-file" }, { "level": 3, "title": "Get the sharing permission list", "id": "get-the-sharing-permission-list" }, { "level": 3, "title": "Get the sharing roles that the user has permission to set for a single file", "id": "get-the-sharing-roles-that-the-user-has-permission-to-set-for-a-single-file" }, { "level": 3, "title": "Create link to share", "id": "create-link-to-share" }, { "level": 3, "title": "PDF Page 19", "id": "pdf-page-19" }, { "level": 3, "title": "Close link sharing", "id": "close-link-sharing" }, { "level": 3, "title": "Set link sharing password", "id": "set-link-sharing-password" }, { "level": 3, "title": "Invite people to share", "id": "invite-people-to-share" }, { "level": 3, "title": "PDF Page 20", "id": "pdf-page-20" }, { "level": 3, "title": "Get all sharing participants", "id": "get-all-sharing-participants" }, { "level": 3, "title": "Set permission roles for sharing participants", "id": "set-permission-roles-for-sharing-participants" }, { "level": 3, "title": "Delete sharing participants", "id": "delete-sharing-participants" }, { "level": 3, "title": "PDF Page 21", "id": "pdf-page-21" }, { "level": 3, "title": "Reminder", "id": "reminder" }, { "level": 3, "title": "Remove someone’s attention", "id": "remove-someone-s-attention" }, { "level": 3, "title": "Get the list of users following the file", "id": "get-the-list-of-users-following-the-file" }, { "level": 3, "title": "Get the list of users who can follow the file, and mark the users who have followed the file", "id": "get-the-list-of-users-who-can-follow-the-file-and-mark-the-users-who-have-followed-the-file" }, { "level": 3, "title": "PDF Page 22", "id": "pdf-page-22" }, { "level": 2, "title": "Enterprise department related API", "id": "enterprise-department-related-api" }, { "level": 3, "title": "Get current enterprise information", "id": "get-current-enterprise-information" }, { "level": 3, "title": "Get information about all departments of the enterprise", "id": "get-information-about-all-departments-of-the-enterprise" }, { "level": 3, "title": "Create enterprise department", "id": "create-enterprise-department" }, { "level": 3, "title": "PDF Page 23", "id": "pdf-page-23" }, { "level": 3, "title": "Get the list of department roles", "id": "get-the-list-of-department-roles" }, { "level": 3, "title": "Add department personnel", "id": "add-department-personnel" }, { "level": 3, "title": "PDF Page 24", "id": "pdf-page-24" }, { "level": 3, "title": "Delete department personnel", "id": "delete-department-personnel" }, { "level": 3, "title": "Get information about your department", "id": "get-information-about-your-department" }, { "level": 3, "title": "Get department personnel", "id": "get-department-personnel" }, { "level": 3, "title": "PDF Page 25", "id": "pdf-page-25" }, { "level": 3, "title": "Add company members", "id": "add-company-members" }, { "level": 3, "title": "Update member information", "id": "update-member-information" }, { "level": 3, "title": "PDF Page 26", "id": "pdf-page-26" }, { "level": 3, "title": "Get enterprise member information", "id": "get-enterprise-member-information" }, { "level": 3, "title": "Get all members of the company", "id": "get-all-members-of-the-company" }, { "level": 3, "title": "Get enterprise logs", "id": "get-enterprise-logs" }, { "level": 3, "title": "PDF Page 27", "id": "pdf-page-27" }, { "level": 2, "title": "Message Push API", "id": "message-push-api" }, { "level": 3, "title": "Make an announcement", "id": "make-an-announcement" }, { "level": 3, "title": "Get published announcements", "id": "get-published-announcements" }, { "level": 3, "title": "Send department discussion", "id": "send-department-discussion" }, { "level": 3, "title": "PDF Page 28", "id": "pdf-page-28" }, { "level": 3, "title": "Get department discussion", "id": "get-department-discussion" }, { "level": 3, "title": "Get enterprise logs", "id": "get-enterprise-logs-2" }, { "level": 3, "title": "PDF Page 29", "id": "pdf-page-29" }, { "level": 2, "title": "4. JWT token login", "id": "4-jwt-token-login" }, { "level": 3, "title": "PDF Page 30", "id": "pdf-page-30" }, { "level": 2, "title": "5. Appendix Common API call return status code", "id": "5-appendix-common-api-call-return-status-code" }, { "level": 2, "title": "Status code result code", "id": "status-code-result-code" } ], "images": [], "text": "File API PDF Page 1 Enterprise Development API V6.6 Shanghai Huaqing Information Technology Co., Ltd. Jiang Dajun PDF Page 2 Directory 1. Obtain an enterprise development account .................................................................................................................................................................................4 2. Authentication API ................................................................................................................................................................................................. 6 Authentication interface one (login callback method) ..................................................................................................................................................................6 Authentication interface two (login free method – JWT token method, in private cloud deployment, the jwt token login method needs to be enabled) .................................. 6 Get token .................................................................................................................................................................................................................8 Refresh token ..................................................................................................................................................................................................................8 3. File access API...................................................................................................................................................................................................... 8 Get file list ........................................................................................................................................................................................9 Get file information ........................................................................................................................................................................................9 Create a folder .................................................................................................................................................................................................10 Pre upload files ................................................................................................................................................................................................10 Uploading files .................................................................................................................................................................................................................11 Get the download file address .................................................................................................................................................................................12 Obtain the download address of multiple files .................................................................................................................................................................12 Get the download file thumbnail address .................................................................................................................................................................13 Modify file information .................................................................................................................................................................................13 Modify file name .................................................................................................................................................................................................13 Delete files (to Recycle Bin) ..................................................................................................................................................................................14 Deleting files (from Recycle Bin) ..................................................................................................................................................................14 Empty the Recycle Bin .................................................................................................................................................................................................14 Recovering files (from the Recycle Bin) ..................................................................................................................................................................14 Get all version information of a file .............................................................................................................................................................15 Current version of settings file .............................................................................................................................................................................15 Moving files .................................................................................................................................................................................................15 Copying files .................................................................................................................................................................................................15 Copying file progress ........................................................................................................................................................................................16 File Log .................................................................................................................................................................................................................16 Create library categories .................................................................................................................................................................................17 Create a sublibrary ............................................................................................................................................................................................17 Shared file related API ................................................................................................................................................................................. 17 Get the sharing url of the file ................................................................................................................................................................................. 18 Get the shared permission list .................................................................................................................................................................18 Obtain the sharing role that the user has permission to set for a single file .............................................................................................................................18 Create a link to share .................................................................................................................................................................................18 Turn off link sharing ........................................................................................................................................................................................19 Set link sharing password .................................................................................................................................................................................19 Invite people to share .................................................................................................................................................................19 Get all sharing participants .................................................................................................................................................................20 Set permission roles for sharing participants .............................................................................................................................................................20 Delete sharing participants ........................................................................................................................................................................20 Reminder...................................................................................................................................................................................................21 Remove someone from following .................................................................................................................................................................................21 Get the list of users following a file .................................................................................................................................................................21 Get the list of users who can follow the file and mark the users who have followed the file .............................................................................................21 Enterprise department related API ................................................................................................................................................................................. 22 Obtain current company information ..................................................................................................................................................................22 Obtain information from all departments of the enterprise ........................................................................................................................................................22 Creating a corporate division .................................................................................................................................................................................22 Get a list of department roles .................................................................................................................................................................................23 Add department personnel .................................................................................................................................................................................................23 Delete department personnel ................................................................................................................................................................................................24 Obtain information about your department .................................................................................................................................................................24 Obtain department personnel ................................................................................................................................................................................................24 Adding company members .................................................................................................................................................................................25 Update member information................................................................................................................................................................................25 Obtain enterprise member information .................................................................................................................................................................................26 Get all members of the company .................................................................................................................................................................................26 Obtain enterprise logs .................................................................................................................................................................................................26 Message push API................................................................................................................................................................................................................ 27 Announcement................................................................................................................................................................................................27 Get published announcements ................................................................................................................................................................................27 Send Department Discussion .................................................................................................................................................................................27 Get departmental discussions .................................................................................................................................................................................28 Obtain enterprise logs .................................................................................................................................................................................................28 4. JWT token login .................................................................................................................................................................................29 5. Appendix Common API call return status code ............................................................................................................................................................. 30 PDF Page 3 Status code result code .................................................................................................................................................................................................. 30 PDF Page 4 1. Obtain an enterprise development account Log in to the Babel Private Cloud Enterprise Management Backend and set up a developer account on the home page: After opening, fill in the callback function address: http://xxx.xxx.xxx.xxx/public/babelAuthResult.do After filling in and clicking OK, the developer ID (client id) and developer key (client secret) will be automatically generated: Note: jwtToken is the corresponding encryption key when generating jwtToken. PDF Page 5 PDF Page 6 2. Authentication API Authentication interface one (login callback method) /api/authorize.do HTTP request method GET URL parameters Parameter name Comment (description) response type must be code (required) string client id developer's id (required) string redirect uri callback function address, needs to be consistent with registration (required) string data: any data, string returned during callback For example: /api/authorize.do?response type=code&client id=xxxxx&redirect uri=http://xxx.xxx.xxx&data=xxx Access via browser Return results If the user is not logged in, it will jump to the login page. After logging in, if it is not authorized, it will 302 jump to the authorization page. If the user has been authorized, it will 302 jump to redirect uri and bring authorization code and data, similar to http://xxx.xxx.xxx?code=xxx&data=xxx The code is valid for 5 minutes. Authentication interface two (login free method – JWT token method. In private cloud deployment, the login method of jwt token needs to be enabled. formula) /api/authorizeByJWT.do HTTP request method GET URL parameters Parameter name Comment (description) response type must be code (required) string client id developer's id (required) string jwt token Jwt token, (required) string It is a string formed by encrypting {client id: xxxxxxx} email email (optional), enter the user's email address, log in as this user, leave it blank to log in as an enterprise administrator, string phone phone (optional), enter the user's mobile phone number and log in as this user. Leave it blank to log in as the enterprise administrator. string babelId babelId (optional), pass in the user's work ID, log in as this user, leave it blank to log in as the enterprise administrator, string PDF Page 7 For example: /api/authorizeByJWT.do?response type=code&client id=xxxxx&jwt token=xxx Note: When using this API, if you do not fill in email, phone, babelId, the system will automatically log in as an administrator, otherwise it will log in as the user corresponding to email, phone, babelId. Log in, the login interface will not be displayed to log in. Note (email, phone, babelId) only needs one of them. Return results { \"success\": true \"code\": \"xxxxxxxxxxxxxxxxxxxxxxxxxxx\", } jwt token is generated by writing your own program. The sample code is as follows: import java.util.Date; import java.util.HashMap; import java.util.Map; import javax.crypto.SecretKey; import javax.crypto.spec.SecretKeySpec; import io.jsonwebtoken.Claims; import io.jsonwebtoken.JwtBuilder; import io.jsonwebtoken.Jwts; import io.jsonwebtoken.SignatureAlgorithm; import net.sf.json.JSONObject; / Generate token used by standard jwt / public class JWT App { static String skey = \"babeldfdfer95840834 t8e 9 9 5934 5943 5886256\"; // The key is the jwtToken field filled in the developer account in the Babel backend. public static void main( String[] args ) { HashMap clientInfo = new HashMap (); clientInfo.put(\"client id\", \"7459492016147273\"); // is the client id in the developer account try { String token = createTokenJWT(clientInfo); System.out.println(\" login token:\" + token); String token1 = \"eyJhbGciOiJIUzI1NiJ9.eyJkdXJhdGlvbiI6NjAsInBheWxvYWQiOnsiY2xpZW50X2lk IjoiNzQ1OTQ5MjAxNjE0NzI3MyJ9LCJ0aW1lIjoxNjkxNDg4MzY4NTk0fQ.pRFCwXd2snMr IgFWOFwYbvyAeeNhoFINGk Wmv7d24g\"; JSONObject parsed = parseTokenJWT(token1); System.out.println(\" parsed:\" + parsed); System.out.println(\" Just put this token as a parameter in the url, such as: \"); } catch (Exception e) { System.out.println(e.getMessage()); } } public static String createTokenJWT(Map config) throws Exception { HashMap data = new HashMap (); data.put(\"time\", new Date().getTime()); data.put(\"duration\", 60); data.put(\"payload\", config); SignatureAlgorithm signatureAlgorithm = SignatureAlgorithm.HS256; SecretKey key = generalKey(); JwtBuilder builder = Jwts.builder() .setClaims(data) .signWith(signatureAlgorithm, key); System.out.println( \" builder : \" + builder); return builder.compact(); } public static JSONObject parseTokenJWT(String jwt) throws Exception { SecretKey key = generalKey(); Claims claims = Jwts.parser() .setSigningKey(key) .parseClaimsJws(jwt) .getBody(); System.out.println(\" claims:\" + claims.toString()); Long time = (Long)claims.get(\"time\"); long duration = (Integer)claims.get(\"duration\"); Long now = new Date().getTime(); if (now time 1000 duration) return null; // Tokens older than 10 minutes are invalid JSONObject obj = JSONObject.fromObject(claims.get(\"payload\")); return obj; } public static SecretKey generalKey(){ String stringKey = skey; byte[] encodedKey = stringKey.getBytes(); SecretKey key = new SecretKeySpec(encodedKey, 0, encodedKey.length, \"HmacSHA256\"); return key; } } PDF Page 8 Get token /api/token.do HTTP method: POST HTTP Header This interface uses Basic Auth to verify client information. The specific method is to add something like \"Authorization: Basic xxxxxxxxx\" in the header. Among them \"xxxxxxxxx\" is calculated from the developer id (client id) and developer secret key (client secret). The specific algorithm is Base64Encode(client id + \":\" + client secret) Base64Encode Choose your own tool for Base64 encoding URL parameters Parameter name Comment (description) grant type (required) must be authorization code string code (required) Authorization code, that is, the authorization code received by the callback address. The authorization code is valid for 5 minutes. It is used once, regardless of success. If it still fails, the authorization code will become invalid string For example: /api/token.do?grant type=authorization code&code=xxx&redirect uri=http://xxx.xxx.xxx Return results access token interface access token refresh token is used to refresh access token, valid for 30 days The validity time of expires in access token, unit is s Refresh token /api/refreshToken.do HTTP method: POST HTTP Header This interface uses Basic Auth to verify client information. The specific method is to add something like \"Authorization: Basic xxxxxxxxx\" in the header. Among them \"xxxxxxxxx\" is calculated through client id and client secret. The specific algorithm is Base64Encode(client id + \":\" + client secret) URL parameters Parameter name Comment (description) grant type (required) must be refresh token string refresh token (required) is the refresh token string obtained in interface 2 For example: /api/refreshToken.do?grant type=refresh token&refresh token=xxx Return results access token interface access identification, refresh token is used to refresh access token, valid for 30 days The validity time of expires in access token is 3600, the unit is s 3. File access API All interfaces need to carry access token in the HTTP header when accessing. For interfaces containing request parameters, usually some POST, PUT or DELETE interface, you also need to set Content Type to specify the format of the parameters. If you need to access different versions of the API, you need Specify a specific version on the request path. If you need to return a response body in a different format, you also need to set Accept. All parameters should be This should use utf 8 encoding. PDF Page 9 Headers: Authorization: stores access token, the format is: \"Bearer \" + access token. Content Type: Indicates the format of the request parameters. If it is a POST, PUT or DELETE request, you need to specify \"application/json\", I We currently do not support other request parameter formats, such as xml. If it is other types such as GET requests, it does not need to be set in the header. Content Type. Accept: used to specify the format of the response result and the version information of the api. Currently, only response in json format is supported, so in general Specify \"application/json\". If the interface access is successful, we will return a response in json format, and the HTTP status code is 200. All successful response responses All json will contain \"success: true\". The X Babel Version in the header of the response indicates the version number of the api accessed by this request. Get file list /nd/api/file/list dir HTTP method: GET URL parameters Parameter name Comment (description) parent id parent folder id (required) string When parent is 1, returns the contents of the corporate folder, 2 returns the contents of the personal folder, 3 returns my Project, 4 returns the share I added, and other fileId returns the contents of the normal folder. page size page size number page page number type type: divided into three types: 1 file, 2 folder, 0 all string Return field description Attribute name type description files array file information {fileId, name, …} total int total quantity page int page capacity success boolean gets the success mark code int returns error code 0 indicates success Get file information /nd/api/file/fileinfo HTTP method: GET URL parameters Parameter name Comment (description) id file id (required) string Return field description fileInfo information Attribute name type description file Object file information { id, name, …} PDF Page 10 success boolean gets the success mark code int returns error code 0 indicates success Create folder /nd/api/file/create folder HTTP method: POST POST request body parameters Parameter name Comment (description) parent id target folder id (required) string name file name (required) string Return field description Attribute name type description file Object file information { id, name, …} success boolean gets the success mark code int returns error code 0 indicates success Pre upload files Used to return the parameters (url, upload token) required when uploading files in the second step. /api/file/preUploadFile.do HTTP method: GET URL parameters Parameter name Comment (description) parent id target folder id (required) (you can ignore this when uploading in the root directory) string name file name (required) string file id When uploading a new version, you need to specify the new version of the file to upload (you can ignore this when uploading new files) string The correct return result is as follows {\"upload token\":\"92808ecfc2ac4e0ebc0b912edac3be4a\",\"url\":\"http://testdocument.babel.cc/api/file/uploadPdf.do\",\"su ccess\":true,\"code\":0} Return field description Attribute name type description url string This url can only be used once and is valid for 1 hour. Call this url to upload a file. After success, fileId, fileName, version, etc. will be returned. upload token string is used as a parameter of post when uploading files. PDF Page 11 Upload files Note that the URL of this API is returned by the pre upload interface. There is no specific URL here, just parameter description. https://xxx.xxx.xxx:xxx/api/file/uploadXXX.do (the specific URL is the URL returned by /api/file/preUploadFile.do in the previous section) POST POST request body parameters Parameter name Comment (description) file file binary data (upload data) Return value in upload token /api/file/preUploadFile.do request The return information is as follows {\"fileId\":\"7728538212615908\",\"version\":0,\"fileName\":\"mesos.pdf\",\"fileSize\":848854,\"success\":true,\"code\":0} Upload relevant code examples Add ‘com.squareup.okhttp3:okhttp:3.3.1’ package private void uploadFile(final String fileName, String parentId, final DaoCallback callback){ preUploadFile(fileName, parentId, new DaoCallback () { @Override public void onSuccess(JSONObject data) { int code = data.optInt(\"code\", 1); final String url = data.optString(\"url\", null); final String uploadToken = data.optString(\"upload token\"); if (code == 0) { // File file = new File(filePath); RequestBody fileContent = RequestBody.create(MultipartBody.FORM, file); RequestBody requestBody = new MultipartBody.Builder() .setType(MultipartBody.FORM) .addFormDataPart(\"file\", fileName, fileContent) .addFormDataPart(\"upload token\", uploadToken) .build(); Request request = new Request.Builder() .url(url) .post(requestBody) .build(); // Uploading takes a long time, so you need to set a longer timeout OkHttpClient okHttpClient = new OkHttpClient(); okHttpClient.newCall(request) .enqueue(new okhttp3.Callback() { @Override public void onFailure(okhttp3.Call call, IOException e) { callback.onFailure( 1, null); } @Override public void onResponse(okhttp3.Call call, okhttp3.Response response) throws IOException { int httpCode = response.code(); if (httpCode == 200) { try { JSONObject result = new JSONObject(response.body().string()); response.body().close(); boolean success = result.getBoolean(\"success\"); if (success) { callback.onSuccess(null); } else { int code = result.getInt(\"code\"); String msg = result.optString(\"msg\"); callback.onFailure(code, msg); } } catch (JSONException e) { callback.onFailure( 2, null); } } else { callback.onFailure(httpCode, null); } } }); } } @Override public void onFailure( int errorCode, String msg){ Log.e(\"FileTransfer\", \"filePreUpload failed errorCode=\" + errorCode); } }); } PDF Page 12 private void preUploadFile(String fileName, String parentId, final DaoCallback callback) { String preUploadUrl = \"http://private.babel.cc:80/api/file/preUploadFile.do?name=1234.jpg&parent id=0\"; // Pass in the corresponding parameters name, parent id String authorization = \"Bearer d48d0a0e253c4a2985d8c5653f717d71\"; //Generate according to the instructions Request request = new Request.Builder().url(preUploadUrl) .addHeader(\"Authorization\", authorization) .build(); OkHttpClient okHttpClient = new OkHttpClient(); okHttpClient.newCall(request).enqueue(new okhttp3.Callback() { @Override public void onFailure(okhttp3.Call call, IOException e) { Log.d(\"\", \"\"); } @Override public void onResponse(okhttp3.Call call, okhttp3.Response response) throws IOException { Log.d(\"\",\"\"); int httpCode = response.code(); if (httpCode == 200) { JSONObject result = null; try { result = new JSONObject(response.body().string()); } catch (JSONException e) { e.printStackTrace(); } try { boolean success = result.getBoolean(\"success\"); if (success) { String url = result.getString(\"url\"); callback.onSuccess(result); } else { int code = result.getInt(\"code\"); String msg = result.optString(\"msg\"); callback.onFailure(code, msg); } } catch (JSONException e) { callback.onFailure( 2, null); } } else { callback.onFailure(httpCode, null); } } }); } Get download file address /api/file/getFileDownloadUrl.do HTTP method: GET URL parameters Parameter name Comment (description) fileId file id to be downloaded (required) string version The version number of the file (optional) number The return information is as follows {\"code\":0,\"success\":true,\"type\":\"File type\",\"url\":\"File download address\"} Get download address of multiple files /api/file/downloadMultiFiles.do HTTP method: GET URL parameters Parameter name Comment (description) fileIdArr is a string composed of the id of the file to be downloaded, separated by the symbol \"!\" (half width), for example, the download ids are 133 and 233. file, the value of fileIdArr is \"133!233\" string type PDF Page 13 The return information is as follows {\"code\":0,\"success\":true,\"type\":\"File type\",\"url\":\"File download address\"} The return value url is the download address of multiple files packaged. Get download file thumbnail address /api/file/downloadThumbnail.do HTTP method: GET URL parameters Parameter name Comment (description) fileId file id to be downloaded (required) string version The version number of the file (optional) number size is the size of the thumbnail to be displayed, taking the maximum value of width and height. The return information is as follows {\"code\":0,\"success\":true, \"url\":\"File download address\"} The return value url is the download address of multiple files packaged. Modify file information /nd /api/file/update file HTTP method: POST Modify file information POST request body parameters Parameter name Comment (description) file id file id (required) string name new file name (optional) string description file description (optional) string The return information is as follows {\"code\":0,\"success\":true} Modify file name /nd /api/file/rename HTTP method: POST Modify file information POST request body parameters Parameter name Comment (description) file id file id (required) string name new file name string The return information is as follows {\"code\":0,\"success\":true} PDF Page 14 Delete files (to recycle bin) /nd /api/file/remove file HTTP method: POST POST request body parameters Parameter name Comment (description) file ids[] target file id array (required) string[] The return information is as follows {\"code\":0,\"success\":true} Delete files (from Recycle Bin) /nd /api/file/remove from trash HTTP method: POST POST request body parameters Parameter name Comment (description) file ids[] target file id array (required) string[] The return information is as follows {\"code\":0,\"success\":true} Empty the Recycle Bin /nd /api/file/empty trash HTTP method: POST POST request body parameters Parameter name Description The return information is as follows {\"code\":0,\"success\":true} Recover files (from Recycle Bin) /nd /api/file/restore file HTTP method: POST POST request body parameters Parameter name Comment (description) file ids[] target file id array string[] restoreAll If file ids is not filled in, restoreAll is true to restore all files in the recycle bin, boolean The return information is as follows PDF Page 15 {\"code\":0,\"success\":true} Get all version information of the file /nd /api/file/versions HTTP method: GET URL parameters Parameter name Comment (description) file id target file id (required) string The return information is as follows {\"code\":0,\"versions\":[],\"success\":true} Set the current version of the file /nd /api/file/version HTTP method: POST POST request body parameters Parameter name Comment (description) file id target file id (required) string version version number (required) number The return information is as follows {\"code\":0,\"success\":true} Move files /nd /api/file/move HTTP method: POST POST request body parameters Parameter name Comment (description) file ids Target file id array to be moved (required) string target id The target folder id that needs to be moved to (required) string The return information is as follows {\"code\":0,\"success\":true} Copy files /nd /api/file/copy HTTP method: POST POST request body parameters Parameter name Comment (description) PDF Page 16 file ids Target file id array to be copied (required) string target id The id of the target folder to be copied to (required) string The return information is as follows { \"code\": 0, \"copyKey\": \"81427630 054a 11ef 8355 db93b4b1d006\", \"fileNum\": 10, \"success\": true} Copy file progress /nd /api/file/copy progress HTTP method: POST POST request body parameters Parameter name Comment (description) copyKey Check the copy progress copyKey is returned by the copy interface (required) string The return information is as follows { \"code\": 0, \"completed\": 10, \"total\": 10, \"result\": {}, \"success\": true} File log /nd /api/file/file logs HTTP method: GET GET request body parameters Parameter name Comment (description) file id target file id array (required) string startIndex gets the starting order of logs. Which log should be returned (optional) int defaults to 0. pageSize The number of items returned per page (optional) int type Log type (optional) int Default 0, view all records, 1 only view access records, 2 only view uploads and downloads, 3 only view anonymous users Users, 4 only view sharing and invitations, 5 only view deletion records userName A username (optional) string, returns the log of a certain user lang language (optional) default cn, string language of returned log cn (Chinese) en (English) The return information is as follows {\"code\":0,\"success\":true, \"logs\":[], \"total\":50} Set whether the user has permission to access the material library /nd /api/file/ set user access material library HTTP method: POST GET request body parameters Parameter name Comment (description) userId user's id array type [usrId1, userId2] (required) string can Whether it is accessible Numeric type (required) int Default 0, 0: Inaccessible, 1: Accessible The return information is as follows {\"code\":0,\"success\":true} PDF Page 17 Create material library classification /nd /api/file/create material class HTTP method: POST POST request body parameters Parameter name Comment (description) destDirFileId fileId of the destination folder (required) string name The name of the created category library (required) string accessType Classification visibility (optional) Defaults to public 0. 0: // public 1: // Need to apply 2: // Department is public 3: // Department application 4: // Confidential managerIds The id array type of the person in charge [usrId1,userId2] departmentIds Classification visibility limited department id of department (optional) Array type [departmentId1,departmentId2] The return information is as follows {\"code\":0, \"success\":true, \"materialClass\": {}} Create sub material library /nd /api/file/create material folder HTTP method: POST POST request body parameters Parameter name Comment (description) destDirFileId fileId of the destination folder (required) string name The name of the created category library (required) string accessType Classification visibility (optional) Defaults to public 0. 0: // public 1: // Need to apply 2: // Department is public 3: // Department application 4: // Confidential managerId The id of the person in charge (optional) string departmentIds Classification visibility limited department id of department (optional) Array type [departmentId1,departmentId2] assistantIds ID of the material library assistant (optional) Array type [usrId1,userId2] The return information is as follows {\"code\":0, \"success\":true, \"materialFolder\": {}} Shared file related API PDF Page 18 Get the sharing url of the file /nd/api/share/shareurl HTTP method: GET Get the sharing link of the file (open the sharing first, and then get the link) URL parameters Parameter name Comment (description) file id file id string is https Whether the returned share url protocol is https 0 means http, 1 means https, default 0 number Return field description {\"code\":0,\"url\":\"https://private.babel.cc/share.do?s=http://private.babel.cc/share.do?s=MjY2OTYzNTk3OTU2NzEzOTtXZWQgSnVsIDAxIDIwMj AgMTg6MzM6NTAgR01UKzA4MDAgKEhvbmcgS29uZyBTdGFuZGFyZCBUaW1lKQ%3D%3D\",\"success\":true} Get the sharing permission list /nd/api/share/share roles HTTP method: GET URL parameters Parameter name Comment (description) Return field description {\"code\":0,\"roles\":[],\"success\":true} Get the sharing roles that the user has permission to set for a single file /nd/api/share/share role forfile HTTP method: GET URL parameters Parameter name Comment (description) file id file id string Return field description {\"code\":0,\"roles\":[],\"success\":true} Create link to share /nd/api/share/open link share HTTP method: POST Open sharing and get a new sharing link. The previous link will be invalid. PDF Page 19 POST request body parameters Parameter name Comment (description) file id pre shared file id (required) string link role id shared role string is https Whether the returned share url protocol is https number anonymousVisit Whether to allow anonymous access, 1 means allowed, 0 means not allowed (optional, default is 1) number Return field description {\"code\":0,\"share url\":\"http://private.babel.cc/share.do?s=http://private.babel.cc/share.do?s=MjY2OTYzNTk3OTU2NzEzOTtXZWQgSnV sIDAxIDIwMjAgMTg6MzM6NTAgR01UKzA4MDAgKEhvbmcgS29uZyBTdGFuZGFyZCBUaW1lKQ%3D%3D\",\"password\":\"\",\"success\":tru e} Close link sharing /nd/api/share/close link share HTTP method: POST Close the shared link I opened POST request body parameters Parameter name Comment (description) file id shared file id (required) string Return field description {\"code\":0,\"success\":true} Set link sharing password /nd/api/share/set share password HTTP method: POST File link sharing is turned on, set a password for link sharing. POST request body parameters Parameter name Comment (description) file id pre shared file id (required) string password password for link sharing string is https Whether the returned share url protocol is https number Return field description {\"code\":0,\"success\":true, \"share url\": \"http://private.babel.cc/share.do?s=xxxxxxxxxxx\"} Invite people to share /nd/api/share/invite share HTTP method: POST PDF Page 20 You can invite certain people to access files based on the user's email or mobile phone POST request body parameters Parameter name Comment (description) file id file id (required) string share role ID of the shared permission (all the above people share this permission) (required) string emails[] email array string[] phones[] array of mobile phone numbers string[] Return field description {\"code\":0,\"success\":true} Get all sharing participants /nd/api/share/share participants HTTP method: GET URL parameters Parameter name Comment (description) file id file id (required) string Return field description {\"code\":0,\"users\":[],\"success\":true} Set permission roles for sharing participants /nd/api/share/set participant role HTTP method: POST POST request body parameters Parameter name Comment (description) file id file id (required) string babelshare id int (required) user id string role id int (required) role id string Return field description {\"code\":0,\"success\":true} Delete sharing participants /nd/api/file/remove share participant HTTP method: POST POST request body parameters Parameter name Comment (description) PDF Page 21 file id file id (required) string babelshare ids[] int (required) user id string Return field description {\"code\":0,\"success\":true} Reminder /nd/api/file/focus file HTTP method: POST POST request body parameters Parameter name Comment (description) file id file id (required) string user ids[] The id of the user to be reminded. This id should be selected among the file participants, otherwise the reminder will not work (required) string[] Return field description {\"code\":0,\"success\":true} Remove someone’s attention /nd/api/file/unfocus file HTTP method: POST POST request body parameters Parameter name Comment (description) file id file id (required) string user ids[] The id of the user to be reminded. This id should be selected among the file participants, otherwise the reminder will not work (required) string[] Return field description {\"code\":0,\"success\":true} Get the list of users following the file /nd/api/file/user focusfile HTTP method: GET URL parameters Parameter name Comment (description) file id file id (required) string Return field description {\"code\":0,\"users\":[],\"success\":true} Get the list of users who can follow the file, and mark the users who have followed the file /nd/api/file/user can focusfile PDF Page 22 HTTP method: GET URL parameters Parameter name Comment (description) file id file id (required) string Return field description Enterprise department related API Get current enterprise information /nd/api/enterprise/current HTTP method: GET URL parameters Parameter name Comment (description) None Return field description {\"code\":0,\"enterprise\":{},\"success\":true} Get information about all departments of the enterprise /nd/api/enterprise/departments HTTP method: GET URL parameters Parameter name Comment (description) None Return field description Attribute name type description departments [] array returns all department information tree {}json data returns the parent child structure information of the department code int successboolean Create enterprise department /nd/api/enterprise/create department HTTP method: POST PDF Page 23 POST request body parameters Parameter name Comment (description) parent dep parent department id, 0 means following department (required) string name department name (required) string description department description string Return field description Attribute name type description department {} json data structure code int successboolean Get the list of department roles /nd/api/enterprise/dep role HTTP method: GET URL parameters Parameter name Comment (description) Return field description Attribute name type description roles []array { id, filePermission,enterpriseId,filePermission,managerPermission, default,nameEn,name} code int successboolean Add department personnel /nd/api/enterprise/add dep mem HTTP method: POST POST request body parameters Parameter name Comment (description) department id department id (required) string user ids[] user list string[] role id The user's role in the department string PDF Page 24 Return field description Attribute name type description Delete department personnel /nd/api/enterprise/remove dep mem HTTP method: POST POST request body parameters Parameter name Comment (description) department id department id (required) string user ids[] Person’s id (required) string[] Return field description Attribute name type description Get information about your department /nd/api/enterprise/mydeparments HTTP method: GET URL parameters Parameter name Comment (description) None Return field description Attribute name type description departments [] array returns my department information code int successboolean Get department personnel /nd/api/enterprise/departmentmembers PDF Page 25 HTTP method: GET URL parameters Parameter name Comment (description) department id department id (required) string Return field description Attribute name type description users array: {id, name, avatrUrl,} Add company members /nd/api/enterprise/add ent mem HTTP method: POST POST request body parameters Parameter name Comment (description) email Email mailbox string password password string enterprise role enterprise member role, optional number department ids[] The user's department, optional string[] department roles[] Roles in the department, optional string[] sex 0 not set 1 male 2 female number name username string phone mobile phone number, optional string babelId employee ID, optional string spacelimit personal space limit, unit GB, 0 means no limit number can ownfile whether the user can have personal files, 1 use the overall enterprise settings, 0 no personal files, 1 have personal files number remarks user description, optional string join time The time when the user joined the enterprise, Unix time, unit number seconds password is md5 Whether the incoming password requires md5 encryption, 0 non md5 password, 1 md5 encrypted password number Update member information /api/updateUserInfo.do HTTP method: POST POST request body parameters Parameter name Comment (description) email email address (search keyword, required) string password password (change password, optional) string frozen 1 – means frozen, 0 – means unfrozen (freeze the account, optional) number password is md5 Whether the incoming password requires md5 encryption, 0 non md5 password, 1 md5 encrypted password number phone mobile phone number (optional) string PDF Page 26 Get enterprise member information /api/getEnterpriseMember.do HTTP method: GET URL parameters Parameter name Comment (description) email email address (search keyword) string phone mobile phone number (search keyword) string babelId employee number (search keyword) string email/phone/babelId you can choose one Return field description {\"code\":0,\"success\":true,\"user\":{}} Get all members of the company /nd/api/enterprise/enterprise members HTTP method: POST POST request body parameters Parameter name Comment (description) lang language type, cn Chinese, en English, optional options { departmentId: //Department id, if not filled in, it means all employees of the enterprise roleId: // Role id, if not filled in, there is no role limit \"userType\": 0, // 0 internal personnel, 1 external personnel \"keyName\": \"\", // Search keywords: name, mobile phone number, email address, if not filled in, it means all people \"startIndex\": 0, \"pageSize\": 20, status: // 0 all accounts, 1 deactivated accounts } Optional Return field description {\"code\":0,\"success\":true,\"members\":{},\"total\":xx} Get enterprise logs /nd/api/enterprise/enterprise logs HTTP method: POST POST request body parameters Parameter name Comment (description) department id department id, if not filled in, it will be the log of all departments string optional keyword related search keyword string optional PDF Page 27 startTime log starting time number optional endTime log end time number optional startIndex int optional pageSize int optional Return field description {\"code\":0,\"success\":true,\"logs\":{},\"total\":xx} Message Push API Make an announcement /nd/api/enterprise/broadcast HTTP method: POST POST request body parameters Parameter name Comment (description) title Announcement content string (required) string content content (required) string target users[] UserId array, if empty, it means all users will receive it, string[] target deps[] Target department, all members of this department and sub departments will receive notification, string[] Target users and target deps must be filled in at least 1 Return field description {\"code\":0,\"success\":true} Get published announcements /nd/api/enterprise/broadcast HTTP method: GET URL parameters Parameter name Comment (description) start index number pagesize number Return field description {\"code\":0,\"broadcasts\":[],\"total\":19,\"success\":true} Send department discussion /nd/api/file/send dep discussion HTTP method: POST PDF Page 28 POST request body parameters Parameter name Comment (description) dep id department id (required) string message information character (required) string json string, format {Type: “Text”, Body: “Hello” } Return field description {\"code\":0,\"messageId\":99,\"success\":true} Get department discussion /nd/api/file/dep discussion HTTP method: POST POST request body parameters Parameter name Comment (description) dep id department id (required) string pagesize page size string start id message id, only the messages before this message will be obtained, if it is empty, the latest message will be obtained string Return field description {\"msgArr\":[],\"gotMoreMessages\":1,\"code\":0,\"success\":true} Get enterprise logs /nd/api/enterprise/enterprise logs HTTP method: GET URL parameters Parameter name Comment (description) department id department id() string pagesize page size number, default value 1000 start index message starting position, number keyword log keyword string startTime start date: seconds number endTime expiration date seconds number Return field description {\"logs\":[],\"total\":0,\"code\":0,\"success\":true} total returns all those that meet the conditions (regardless of paging pageSize) PDF Page 29 4. JWT token login In private cloud deployment, the login method of jwt token can be enabled. In this case, the following url is allowed to directly enter the network disk system as a user without logging in. System: /account/tokenLogin.do Parameters: Parameter name Optional Description Optional value Default value userToken is required and contains the encrypted information of the logged in user (Constructor None See the instructions below for details) fileId optional The id of the file (folder) to be accessed, if not None If filled in, the user root directory will be opened. closeTitleBar optional Whether to close the title bar 1 Close 0 Do not close 0 disableEntMark Optional Whether to hide the corporate logo in the upper left corner 1 Hide 0 Do not hide 0 disableUserMark Optional Whether to hide the user settings entrance in the upper right corner 1 Hide 0 Do not hide 0 defaultLang optional Set the language used by the interface cn Chinese en English zh HK Traditional cn defaultClrTheme is optional and sets the interface color theme. normal is the standard mode, dark is the dark mode normal. For example, the following is the user root interface in English and dark mode with the user logo in the upper right corner hidden. /account/tokenLogin.do userToken=xxxxxxxxxxxxxxxx defaultClrTheme=dark defaultLang=en disableUserMark=1 Construction of userToken userToken is an encrypted string containing logged in user information. The encrypted information is a password created by JWT, a standard security mechanism for transmitting trusted data between two parties. The content of JWT encrypted user information JSONObject is as follows: { payload: { email: “xxx@xxx.com”/“135XXXXXXX”/“XXXX”} time: now } Note: email can be an email address, mobile phone number, or work number; The code is as follows: public static void main( String[] args ) { HashMap user = new HashMap (); user.put(\"email\", \"yuanchaozhao@qq.com\"); try { //token login String userToken = createTokenJWT(user); System.out.println(\" login token:\" + userToken); JSONObject parsed = parseTokenJWT(userToken); System.out.println(\" parsed:\" + parsed); System.out.println(\" Just put this token as a parameter in the url, such as: \"); System.out.println(\"/account/tokenLogin.do?userToken=\" + userToken); } catch (Exception e) { System.out.println(e.getMessage()); } } For other codes, please refer to the jwtToken generation code, which is provided in the authentication interface 2. Remarks: JWT is the abbreviation of JSON Web Tokens. It is a communication encryption and decryption mechanism that meets the industry standard RFC7519. Please refer to: https://jwt.io/ PDF Page 30 5. Appendix Common API call return status code Status code result code Code value Description 0 success 1 unknown error 2 parameter error 7 Not enough space 12 Prohibited user actions 13 invalid token the end" }, { "lang": "en", "slug": "developer-api-sharing", "title": "Share API", "description": "Share the API's interface paths, methods, parameters, and return fields.", "category": "Sharing API", "top_category": "API文档", "keywords": [ "API", "Share API", "Developer" ], "url": "en/developer-api-sharing.html", "source": "content/en/developer-api-sharing.md", "summary": "Share API PDF Page 1 Enterprise Development API V6.6 Shanghai Huaqing Information Technology Co., Ltd. Jiang Dajun PDF Page 2 Directory 1. Obtain an enterprise development account .................................................................................................................................................................................4 2. Authentication API ................................................................................................................................................................................................. 6 Authentication interface one (login callback method) ......................................................................", "headings": [ { "level": 1, "title": "Share API", "id": "share-api" }, { "level": 3, "title": "PDF Page 1", "id": "pdf-page-1" }, { "level": 3, "title": "PDF Page 2", "id": "pdf-page-2" }, { "level": 3, "title": "PDF Page 3", "id": "pdf-page-3" }, { "level": 3, "title": "PDF Page 4", "id": "pdf-page-4" }, { "level": 2, "title": "1. Obtain an enterprise development account", "id": "1-obtain-an-enterprise-development-account" }, { "level": 3, "title": "PDF Page 5", "id": "pdf-page-5" }, { "level": 3, "title": "PDF Page 6", "id": "pdf-page-6" }, { "level": 2, "title": "2. Authentication API", "id": "2-authentication-api" }, { "level": 3, "title": "Authentication interface one (login callback method)", "id": "authentication-interface-one-login-callback-method" }, { "level": 3, "title": "PDF Page 7", "id": "pdf-page-7" }, { "level": 3, "title": "PDF Page 8", "id": "pdf-page-8" }, { "level": 3, "title": "Get token", "id": "get-token" }, { "level": 3, "title": "Refresh token", "id": "refresh-token" }, { "level": 2, "title": "3. File access API", "id": "3-file-access-api" }, { "level": 3, "title": "PDF Page 9", "id": "pdf-page-9" }, { "level": 3, "title": "Get file list", "id": "get-file-list" }, { "level": 3, "title": "Get file information", "id": "get-file-information" }, { "level": 3, "title": "PDF Page 10", "id": "pdf-page-10" }, { "level": 3, "title": "Create folder", "id": "create-folder" }, { "level": 3, "title": "Pre upload files", "id": "pre-upload-files" }, { "level": 3, "title": "PDF Page 11", "id": "pdf-page-11" }, { "level": 3, "title": "Upload files", "id": "upload-files" }, { "level": 3, "title": "PDF Page 12", "id": "pdf-page-12" }, { "level": 3, "title": "Get download file address", "id": "get-download-file-address" }, { "level": 3, "title": "Get download address of multiple files", "id": "get-download-address-of-multiple-files" }, { "level": 3, "title": "PDF Page 13", "id": "pdf-page-13" }, { "level": 3, "title": "Get download file thumbnail address", "id": "get-download-file-thumbnail-address" }, { "level": 3, "title": "Modify file information", "id": "modify-file-information" }, { "level": 3, "title": "Modify file information", "id": "modify-file-information-2" }, { "level": 3, "title": "Modify file name", "id": "modify-file-name" }, { "level": 3, "title": "Modify file information", "id": "modify-file-information-3" }, { "level": 3, "title": "PDF Page 14", "id": "pdf-page-14" }, { "level": 3, "title": "Delete files (to recycle bin)", "id": "delete-files-to-recycle-bin" }, { "level": 3, "title": "Delete files (from Recycle Bin)", "id": "delete-files-from-recycle-bin" }, { "level": 3, "title": "Empty the Recycle Bin", "id": "empty-the-recycle-bin" }, { "level": 3, "title": "Recover files (from Recycle Bin)", "id": "recover-files-from-recycle-bin" }, { "level": 3, "title": "PDF Page 15", "id": "pdf-page-15" }, { "level": 3, "title": "Get all version information of the file", "id": "get-all-version-information-of-the-file" }, { "level": 3, "title": "Set the current version of the file", "id": "set-the-current-version-of-the-file" }, { "level": 3, "title": "Move files", "id": "move-files" }, { "level": 3, "title": "Copy files", "id": "copy-files" }, { "level": 3, "title": "PDF Page 16", "id": "pdf-page-16" }, { "level": 3, "title": "Copy file progress", "id": "copy-file-progress" }, { "level": 3, "title": "File log", "id": "file-log" }, { "level": 3, "title": "Set whether the user has permission to access the material library", "id": "set-whether-the-user-has-permission-to-access-the-material-library" }, { "level": 3, "title": "PDF Page 17", "id": "pdf-page-17" }, { "level": 3, "title": "Create material library classification", "id": "create-material-library-classification" }, { "level": 3, "title": "Create sub material library", "id": "create-sub-material-library" }, { "level": 2, "title": "Shared file related API", "id": "shared-file-related-api" }, { "level": 3, "title": "PDF Page 18", "id": "pdf-page-18" }, { "level": 3, "title": "Get the sharing url of the file", "id": "get-the-sharing-url-of-the-file" }, { "level": 3, "title": "Get the sharing permission list", "id": "get-the-sharing-permission-list" }, { "level": 3, "title": "Get the sharing roles that the user has permission to set for a single file", "id": "get-the-sharing-roles-that-the-user-has-permission-to-set-for-a-single-file" }, { "level": 3, "title": "Create link to share", "id": "create-link-to-share" }, { "level": 3, "title": "PDF Page 19", "id": "pdf-page-19" }, { "level": 3, "title": "Close link sharing", "id": "close-link-sharing" }, { "level": 3, "title": "Set link sharing password", "id": "set-link-sharing-password" }, { "level": 3, "title": "Invite people to share", "id": "invite-people-to-share" }, { "level": 3, "title": "PDF Page 20", "id": "pdf-page-20" }, { "level": 3, "title": "Get all sharing participants", "id": "get-all-sharing-participants" }, { "level": 3, "title": "Set permission roles for sharing participants", "id": "set-permission-roles-for-sharing-participants" }, { "level": 3, "title": "Delete sharing participants", "id": "delete-sharing-participants" }, { "level": 3, "title": "PDF Page 21", "id": "pdf-page-21" }, { "level": 3, "title": "Reminder", "id": "reminder" }, { "level": 3, "title": "Remove someone’s attention", "id": "remove-someone-s-attention" }, { "level": 3, "title": "Get the list of users following the file", "id": "get-the-list-of-users-following-the-file" }, { "level": 3, "title": "Get the list of users who can follow the file, and mark the users who have followed the file", "id": "get-the-list-of-users-who-can-follow-the-file-and-mark-the-users-who-have-followed-the-file" }, { "level": 3, "title": "PDF Page 22", "id": "pdf-page-22" }, { "level": 2, "title": "Enterprise department related API", "id": "enterprise-department-related-api" }, { "level": 3, "title": "Get current enterprise information", "id": "get-current-enterprise-information" }, { "level": 3, "title": "Get information about all departments of the enterprise", "id": "get-information-about-all-departments-of-the-enterprise" }, { "level": 3, "title": "Create enterprise department", "id": "create-enterprise-department" }, { "level": 3, "title": "PDF Page 23", "id": "pdf-page-23" }, { "level": 3, "title": "Get the list of department roles", "id": "get-the-list-of-department-roles" }, { "level": 3, "title": "Add department personnel", "id": "add-department-personnel" }, { "level": 3, "title": "PDF Page 24", "id": "pdf-page-24" }, { "level": 3, "title": "Delete department personnel", "id": "delete-department-personnel" }, { "level": 3, "title": "Get information about your department", "id": "get-information-about-your-department" }, { "level": 3, "title": "Get department personnel", "id": "get-department-personnel" }, { "level": 3, "title": "PDF Page 25", "id": "pdf-page-25" }, { "level": 3, "title": "Add company members", "id": "add-company-members" }, { "level": 3, "title": "Update member information", "id": "update-member-information" }, { "level": 3, "title": "PDF Page 26", "id": "pdf-page-26" }, { "level": 3, "title": "Get enterprise member information", "id": "get-enterprise-member-information" }, { "level": 3, "title": "Get all members of the company", "id": "get-all-members-of-the-company" }, { "level": 3, "title": "Get enterprise logs", "id": "get-enterprise-logs" }, { "level": 3, "title": "PDF Page 27", "id": "pdf-page-27" }, { "level": 2, "title": "Message Push API", "id": "message-push-api" }, { "level": 3, "title": "Make an announcement", "id": "make-an-announcement" }, { "level": 3, "title": "Get published announcements", "id": "get-published-announcements" }, { "level": 3, "title": "Send department discussion", "id": "send-department-discussion" }, { "level": 3, "title": "PDF Page 28", "id": "pdf-page-28" }, { "level": 3, "title": "Get department discussion", "id": "get-department-discussion" }, { "level": 3, "title": "Get enterprise logs", "id": "get-enterprise-logs-2" }, { "level": 3, "title": "PDF Page 29", "id": "pdf-page-29" }, { "level": 2, "title": "4. JWT token login", "id": "4-jwt-token-login" }, { "level": 3, "title": "PDF Page 30", "id": "pdf-page-30" }, { "level": 2, "title": "5. Appendix Common API call return status code", "id": "5-appendix-common-api-call-return-status-code" }, { "level": 2, "title": "Status code result code", "id": "status-code-result-code" } ], "images": [], "text": "Share API PDF Page 1 Enterprise Development API V6.6 Shanghai Huaqing Information Technology Co., Ltd. Jiang Dajun PDF Page 2 Directory 1. Obtain an enterprise development account .................................................................................................................................................................................4 2. Authentication API ................................................................................................................................................................................................. 6 Authentication interface one (login callback method) ..................................................................................................................................................................6 Authentication interface two (login free method – JWT token method, in private cloud deployment, the jwt token login method needs to be enabled) .................................. 6 Get token .................................................................................................................................................................................................................8 Refresh token ..................................................................................................................................................................................................................8 3. File access API...................................................................................................................................................................................................... 8 Get file list ........................................................................................................................................................................................9 Get file information ........................................................................................................................................................................................9 Create a folder .................................................................................................................................................................................................10 Pre upload files ................................................................................................................................................................................................10 Uploading files .................................................................................................................................................................................................................11 Get the download file address .................................................................................................................................................................................12 Obtain the download address of multiple files .................................................................................................................................................................12 Get the download file thumbnail address .................................................................................................................................................................13 Modify file information .................................................................................................................................................................................13 Modify file name .................................................................................................................................................................................................13 Delete files (to Recycle Bin) ..................................................................................................................................................................................14 Deleting files (from Recycle Bin) ..................................................................................................................................................................14 Empty the Recycle Bin .................................................................................................................................................................................................14 Recovering files (from the Recycle Bin) ..................................................................................................................................................................14 Get all version information of a file .............................................................................................................................................................15 Current version of settings file .............................................................................................................................................................................15 Moving files .................................................................................................................................................................................................15 Copying files .................................................................................................................................................................................................15 Copying file progress ........................................................................................................................................................................................16 File Log .................................................................................................................................................................................................................16 Create library categories .................................................................................................................................................................................17 Create a sublibrary ............................................................................................................................................................................................17 Shared file related API ................................................................................................................................................................................. 17 Get the sharing url of the file ................................................................................................................................................................................. 18 Get the shared permission list .................................................................................................................................................................18 Obtain the sharing role that the user has permission to set for a single file .............................................................................................................................18 Create a link to share .................................................................................................................................................................................18 Turn off link sharing ........................................................................................................................................................................................19 Set link sharing password .................................................................................................................................................................................19 Invite people to share .................................................................................................................................................................19 Get all sharing participants .................................................................................................................................................................20 Set permission roles for sharing participants .............................................................................................................................................................20 Delete sharing participants ........................................................................................................................................................................20 Reminder...................................................................................................................................................................................................21 Remove someone from following .................................................................................................................................................................................21 Get the list of users following a file .................................................................................................................................................................21 Get the list of users who can follow the file and mark the users who have followed the file .............................................................................................21 Enterprise department related API ................................................................................................................................................................................. 22 Obtain current company information ..................................................................................................................................................................22 Obtain information from all departments of the enterprise ........................................................................................................................................................22 Creating a corporate division .................................................................................................................................................................................22 Get a list of department roles .................................................................................................................................................................................23 Add department personnel .................................................................................................................................................................................................23 Delete department personnel ................................................................................................................................................................................................24 Obtain information about your department .................................................................................................................................................................24 Obtain department personnel ................................................................................................................................................................................................24 Adding company members .................................................................................................................................................................................25 Update member information................................................................................................................................................................................25 Obtain enterprise member information .................................................................................................................................................................................26 Get all members of the company .................................................................................................................................................................................26 Obtain enterprise logs .................................................................................................................................................................................................26 Message push API................................................................................................................................................................................................................ 27 Announcement................................................................................................................................................................................................27 Get published announcements ................................................................................................................................................................................27 Send Department Discussion .................................................................................................................................................................................27 Get departmental discussions .................................................................................................................................................................................28 Obtain enterprise logs .................................................................................................................................................................................................28 4. JWT token login .................................................................................................................................................................................29 5. Appendix Common API call return status code ............................................................................................................................................................. 30 PDF Page 3 Status code result code .................................................................................................................................................................................................. 30 PDF Page 4 1. Obtain an enterprise development account Log in to the Babel Private Cloud Enterprise Management Backend and set up a developer account on the home page: After opening, fill in the callback function address: http://xxx.xxx.xxx.xxx/public/babelAuthResult.do After filling in and clicking OK, the developer ID (client id) and developer key (client secret) will be automatically generated: Note: jwtToken is the corresponding encryption key when generating jwtToken. PDF Page 5 PDF Page 6 2. Authentication API Authentication interface one (login callback method) /api/authorize.do HTTP request method GET URL parameters Parameter name Comment (description) response type must be code (required) string client id developer's id (required) string redirect uri callback function address, needs to be consistent with registration (required) string data: any data, string returned during callback For example: /api/authorize.do?response type=code&client id=xxxxx&redirect uri=http://xxx.xxx.xxx&data=xxx Access via browser Return results If the user is not logged in, it will jump to the login page. After logging in, if it is not authorized, it will 302 jump to the authorization page. If the user has been authorized, it will 302 jump to redirect uri and bring authorization code and data, similar to http://xxx.xxx.xxx?code=xxx&data=xxx The code is valid for 5 minutes. Authentication interface two (login free method – JWT token method. In private cloud deployment, the login method of jwt token needs to be enabled. formula) /api/authorizeByJWT.do HTTP request method GET URL parameters Parameter name Comment (description) response type must be code (required) string client id developer's id (required) string jwt token Jwt token, (required) string It is a string formed by encrypting {client id: xxxxxxx} email email (optional), enter the user's email address, log in as this user, leave it blank to log in as an enterprise administrator, string phone phone (optional), enter the user's mobile phone number and log in as this user. Leave it blank to log in as the enterprise administrator. string babelId babelId (optional), pass in the user's work ID, log in as this user, leave it blank to log in as the enterprise administrator, string PDF Page 7 For example: /api/authorizeByJWT.do?response type=code&client id=xxxxx&jwt token=xxx Note: When using this API, if you do not fill in email, phone, babelId, the system will automatically log in as an administrator, otherwise it will log in as the user corresponding to email, phone, babelId. Log in, the login interface will not be displayed to log in. Note (email, phone, babelId) only needs one of them. Return results { \"success\": true \"code\": \"xxxxxxxxxxxxxxxxxxxxxxxxxxx\", } jwt token is generated by writing your own program. The sample code is as follows: import java.util.Date; import java.util.HashMap; import java.util.Map; import javax.crypto.SecretKey; import javax.crypto.spec.SecretKeySpec; import io.jsonwebtoken.Claims; import io.jsonwebtoken.JwtBuilder; import io.jsonwebtoken.Jwts; import io.jsonwebtoken.SignatureAlgorithm; import net.sf.json.JSONObject; / Generate token used by standard jwt / public class JWT App { static String skey = \"babeldfdfer95840834 t8e 9 9 5934 5943 5886256\"; // The key is the jwtToken field filled in the developer account in the Babel backend. public static void main( String[] args ) { HashMap clientInfo = new HashMap (); clientInfo.put(\"client id\", \"7459492016147273\"); // is the client id in the developer account try { String token = createTokenJWT(clientInfo); System.out.println(\" login token:\" + token); String token1 = \"eyJhbGciOiJIUzI1NiJ9.eyJkdXJhdGlvbiI6NjAsInBheWxvYWQiOnsiY2xpZW50X2lk IjoiNzQ1OTQ5MjAxNjE0NzI3MyJ9LCJ0aW1lIjoxNjkxNDg4MzY4NTk0fQ.pRFCwXd2snMr IgFWOFwYbvyAeeNhoFINGk Wmv7d24g\"; JSONObject parsed = parseTokenJWT(token1); System.out.println(\" parsed:\" + parsed); System.out.println(\" Just put this token as a parameter in the url, such as: \"); } catch (Exception e) { System.out.println(e.getMessage()); } } public static String createTokenJWT(Map config) throws Exception { HashMap data = new HashMap (); data.put(\"time\", new Date().getTime()); data.put(\"duration\", 60); data.put(\"payload\", config); SignatureAlgorithm signatureAlgorithm = SignatureAlgorithm.HS256; SecretKey key = generalKey(); JwtBuilder builder = Jwts.builder() .setClaims(data) .signWith(signatureAlgorithm, key); System.out.println( \" builder : \" + builder); return builder.compact(); } public static JSONObject parseTokenJWT(String jwt) throws Exception { SecretKey key = generalKey(); Claims claims = Jwts.parser() .setSigningKey(key) .parseClaimsJws(jwt) .getBody(); System.out.println(\" claims:\" + claims.toString()); Long time = (Long)claims.get(\"time\"); long duration = (Integer)claims.get(\"duration\"); Long now = new Date().getTime(); if (now time 1000 duration) return null; // Tokens older than 10 minutes are invalid JSONObject obj = JSONObject.fromObject(claims.get(\"payload\")); return obj; } public static SecretKey generalKey(){ String stringKey = skey; byte[] encodedKey = stringKey.getBytes(); SecretKey key = new SecretKeySpec(encodedKey, 0, encodedKey.length, \"HmacSHA256\"); return key; } } PDF Page 8 Get token /api/token.do HTTP method: POST HTTP Header This interface uses Basic Auth to verify client information. The specific method is to add something like \"Authorization: Basic xxxxxxxxx\" in the header. Among them \"xxxxxxxxx\" is calculated from the developer id (client id) and developer secret key (client secret). The specific algorithm is Base64Encode(client id + \":\" + client secret) Base64Encode Choose your own tool for Base64 encoding URL parameters Parameter name Comment (description) grant type (required) must be authorization code string code (required) Authorization code, that is, the authorization code received by the callback address. The authorization code is valid for 5 minutes. It is used once, regardless of success. If it still fails, the authorization code will become invalid string For example: /api/token.do?grant type=authorization code&code=xxx&redirect uri=http://xxx.xxx.xxx Return results access token interface access token refresh token is used to refresh access token, valid for 30 days The validity time of expires in access token, unit is s Refresh token /api/refreshToken.do HTTP method: POST HTTP Header This interface uses Basic Auth to verify client information. The specific method is to add something like \"Authorization: Basic xxxxxxxxx\" in the header. Among them \"xxxxxxxxx\" is calculated through client id and client secret. The specific algorithm is Base64Encode(client id + \":\" + client secret) URL parameters Parameter name Comment (description) grant type (required) must be refresh token string refresh token (required) is the refresh token string obtained in interface 2 For example: /api/refreshToken.do?grant type=refresh token&refresh token=xxx Return results access token interface access identification, refresh token is used to refresh access token, valid for 30 days The validity time of expires in access token is 3600, the unit is s 3. File access API All interfaces need to carry access token in the HTTP header when accessing. For interfaces containing request parameters, usually some POST, PUT or DELETE interface, you also need to set Content Type to specify the format of the parameters. If you need to access different versions of the API, you need Specify a specific version on the request path. If you need to return a response body in a different format, you also need to set Accept. All parameters should be This should use utf 8 encoding. PDF Page 9 Headers: Authorization: stores access token, the format is: \"Bearer \" + access token. Content Type: Indicates the format of the request parameters. If it is a POST, PUT or DELETE request, you need to specify \"application/json\", I We currently do not support other request parameter formats, such as xml. If it is other types such as GET requests, it does not need to be set in the header. Content Type. Accept: used to specify the format of the response result and the version information of the api. Currently, only response in json format is supported, so in general Specify \"application/json\". If the interface access is successful, we will return a response in json format, and the HTTP status code is 200. All successful response responses All json will contain \"success: true\". The X Babel Version in the header of the response indicates the version number of the api accessed by this request. Get file list /nd/api/file/list dir HTTP method: GET URL parameters Parameter name Comment (description) parent id parent folder id (required) string When parent is 1, returns the contents of the corporate folder, 2 returns the contents of the personal folder, 3 returns my Project, 4 returns the share I added, and other fileId returns the contents of the normal folder. page size page size number page page number type type: divided into three types: 1 file, 2 folder, 0 all string Return field description Attribute name type description files array file information {fileId, name, …} total int total quantity page int page capacity success boolean gets the success mark code int returns error code 0 indicates success Get file information /nd/api/file/fileinfo HTTP method: GET URL parameters Parameter name Comment (description) id file id (required) string Return field description fileInfo information Attribute name type description file Object file information { id, name, …} PDF Page 10 success boolean gets the success mark code int returns error code 0 indicates success Create folder /nd/api/file/create folder HTTP method: POST POST request body parameters Parameter name Comment (description) parent id target folder id (required) string name file name (required) string Return field description Attribute name type description file Object file information { id, name, …} success boolean gets the success mark code int returns error code 0 indicates success Pre upload files Used to return the parameters (url, upload token) required when uploading files in the second step. /api/file/preUploadFile.do HTTP method: GET URL parameters Parameter name Comment (description) parent id target folder id (required) (you can ignore this when uploading in the root directory) string name file name (required) string file id When uploading a new version, you need to specify the new version of the file to upload (you can ignore this when uploading new files) string The correct return result is as follows {\"upload token\":\"92808ecfc2ac4e0ebc0b912edac3be4a\",\"url\":\"http://testdocument.babel.cc/api/file/uploadPdf.do\",\"su ccess\":true,\"code\":0} Return field description Attribute name type description url string This url can only be used once and is valid for 1 hour. Call this url to upload a file. After success, fileId, fileName, version, etc. will be returned. upload token string is used as a parameter of post when uploading files. PDF Page 11 Upload files Note that the URL of this API is returned by the pre upload interface. There is no specific URL here, just parameter description. https://xxx.xxx.xxx:xxx/api/file/uploadXXX.do (the specific URL is the URL returned by /api/file/preUploadFile.do in the previous section) POST POST request body parameters Parameter name Comment (description) file file binary data (upload data) Return value in upload token /api/file/preUploadFile.do request The return information is as follows {\"fileId\":\"7728538212615908\",\"version\":0,\"fileName\":\"mesos.pdf\",\"fileSize\":848854,\"success\":true,\"code\":0} Upload relevant code examples Add ‘com.squareup.okhttp3:okhttp:3.3.1’ package private void uploadFile(final String fileName, String parentId, final DaoCallback callback){ preUploadFile(fileName, parentId, new DaoCallback () { @Override public void onSuccess(JSONObject data) { int code = data.optInt(\"code\", 1); final String url = data.optString(\"url\", null); final String uploadToken = data.optString(\"upload token\"); if (code == 0) { // File file = new File(filePath); RequestBody fileContent = RequestBody.create(MultipartBody.FORM, file); RequestBody requestBody = new MultipartBody.Builder() .setType(MultipartBody.FORM) .addFormDataPart(\"file\", fileName, fileContent) .addFormDataPart(\"upload token\", uploadToken) .build(); Request request = new Request.Builder() .url(url) .post(requestBody) .build(); // Uploading takes a long time, so you need to set a longer timeout OkHttpClient okHttpClient = new OkHttpClient(); okHttpClient.newCall(request) .enqueue(new okhttp3.Callback() { @Override public void onFailure(okhttp3.Call call, IOException e) { callback.onFailure( 1, null); } @Override public void onResponse(okhttp3.Call call, okhttp3.Response response) throws IOException { int httpCode = response.code(); if (httpCode == 200) { try { JSONObject result = new JSONObject(response.body().string()); response.body().close(); boolean success = result.getBoolean(\"success\"); if (success) { callback.onSuccess(null); } else { int code = result.getInt(\"code\"); String msg = result.optString(\"msg\"); callback.onFailure(code, msg); } } catch (JSONException e) { callback.onFailure( 2, null); } } else { callback.onFailure(httpCode, null); } } }); } } @Override public void onFailure( int errorCode, String msg){ Log.e(\"FileTransfer\", \"filePreUpload failed errorCode=\" + errorCode); } }); } PDF Page 12 private void preUploadFile(String fileName, String parentId, final DaoCallback callback) { String preUploadUrl = \"http://private.babel.cc:80/api/file/preUploadFile.do?name=1234.jpg&parent id=0\"; // Pass in the corresponding parameters name, parent id String authorization = \"Bearer d48d0a0e253c4a2985d8c5653f717d71\"; //Generate according to the instructions Request request = new Request.Builder().url(preUploadUrl) .addHeader(\"Authorization\", authorization) .build(); OkHttpClient okHttpClient = new OkHttpClient(); okHttpClient.newCall(request).enqueue(new okhttp3.Callback() { @Override public void onFailure(okhttp3.Call call, IOException e) { Log.d(\"\", \"\"); } @Override public void onResponse(okhttp3.Call call, okhttp3.Response response) throws IOException { Log.d(\"\",\"\"); int httpCode = response.code(); if (httpCode == 200) { JSONObject result = null; try { result = new JSONObject(response.body().string()); } catch (JSONException e) { e.printStackTrace(); } try { boolean success = result.getBoolean(\"success\"); if (success) { String url = result.getString(\"url\"); callback.onSuccess(result); } else { int code = result.getInt(\"code\"); String msg = result.optString(\"msg\"); callback.onFailure(code, msg); } } catch (JSONException e) { callback.onFailure( 2, null); } } else { callback.onFailure(httpCode, null); } } }); } Get download file address /api/file/getFileDownloadUrl.do HTTP method: GET URL parameters Parameter name Comment (description) fileId file id to be downloaded (required) string version The version number of the file (optional) number The return information is as follows {\"code\":0,\"success\":true,\"type\":\"File type\",\"url\":\"File download address\"} Get download address of multiple files /api/file/downloadMultiFiles.do HTTP method: GET URL parameters Parameter name Comment (description) fileIdArr is a string composed of the id of the file to be downloaded, separated by the symbol \"!\" (half width), for example, the download ids are 133 and 233. file, the value of fileIdArr is \"133!233\" string type PDF Page 13 The return information is as follows {\"code\":0,\"success\":true,\"type\":\"File type\",\"url\":\"File download address\"} The return value url is the download address of multiple files packaged. Get download file thumbnail address /api/file/downloadThumbnail.do HTTP method: GET URL parameters Parameter name Comment (description) fileId file id to be downloaded (required) string version The version number of the file (optional) number size is the size of the thumbnail to be displayed, taking the maximum value of width and height. The return information is as follows {\"code\":0,\"success\":true, \"url\":\"File download address\"} The return value url is the download address of multiple files packaged. Modify file information /nd /api/file/update file HTTP method: POST Modify file information POST request body parameters Parameter name Comment (description) file id file id (required) string name new file name (optional) string description file description (optional) string The return information is as follows {\"code\":0,\"success\":true} Modify file name /nd /api/file/rename HTTP method: POST Modify file information POST request body parameters Parameter name Comment (description) file id file id (required) string name new file name string The return information is as follows {\"code\":0,\"success\":true} PDF Page 14 Delete files (to recycle bin) /nd /api/file/remove file HTTP method: POST POST request body parameters Parameter name Comment (description) file ids[] target file id array (required) string[] The return information is as follows {\"code\":0,\"success\":true} Delete files (from Recycle Bin) /nd /api/file/remove from trash HTTP method: POST POST request body parameters Parameter name Comment (description) file ids[] target file id array (required) string[] The return information is as follows {\"code\":0,\"success\":true} Empty the Recycle Bin /nd /api/file/empty trash HTTP method: POST POST request body parameters Parameter name Description The return information is as follows {\"code\":0,\"success\":true} Recover files (from Recycle Bin) /nd /api/file/restore file HTTP method: POST POST request body parameters Parameter name Comment (description) file ids[] target file id array string[] restoreAll If file ids is not filled in, restoreAll is true to restore all files in the recycle bin, boolean The return information is as follows PDF Page 15 {\"code\":0,\"success\":true} Get all version information of the file /nd /api/file/versions HTTP method: GET URL parameters Parameter name Comment (description) file id target file id (required) string The return information is as follows {\"code\":0,\"versions\":[],\"success\":true} Set the current version of the file /nd /api/file/version HTTP method: POST POST request body parameters Parameter name Comment (description) file id target file id (required) string version version number (required) number The return information is as follows {\"code\":0,\"success\":true} Move files /nd /api/file/move HTTP method: POST POST request body parameters Parameter name Comment (description) file ids Target file id array to be moved (required) string target id The target folder id that needs to be moved to (required) string The return information is as follows {\"code\":0,\"success\":true} Copy files /nd /api/file/copy HTTP method: POST POST request body parameters Parameter name Comment (description) PDF Page 16 file ids Target file id array to be copied (required) string target id The id of the target folder to be copied to (required) string The return information is as follows { \"code\": 0, \"copyKey\": \"81427630 054a 11ef 8355 db93b4b1d006\", \"fileNum\": 10, \"success\": true} Copy file progress /nd /api/file/copy progress HTTP method: POST POST request body parameters Parameter name Comment (description) copyKey Check the copy progress copyKey is returned by the copy interface (required) string The return information is as follows { \"code\": 0, \"completed\": 10, \"total\": 10, \"result\": {}, \"success\": true} File log /nd /api/file/file logs HTTP method: GET GET request body parameters Parameter name Comment (description) file id target file id array (required) string startIndex gets the starting order of logs. Which log should be returned (optional) int defaults to 0. pageSize The number of items returned per page (optional) int type Log type (optional) int Default 0, view all records, 1 only view access records, 2 only view uploads and downloads, 3 only view anonymous users Users, 4 only view sharing and invitations, 5 only view deletion records userName A username (optional) string, returns the log of a certain user lang language (optional) default cn, string language of returned log cn (Chinese) en (English) The return information is as follows {\"code\":0,\"success\":true, \"logs\":[], \"total\":50} Set whether the user has permission to access the material library /nd /api/file/ set user access material library HTTP method: POST GET request body parameters Parameter name Comment (description) userId user's id array type [usrId1, userId2] (required) string can Whether it is accessible Numeric type (required) int Default 0, 0: Inaccessible, 1: Accessible The return information is as follows {\"code\":0,\"success\":true} PDF Page 17 Create material library classification /nd /api/file/create material class HTTP method: POST POST request body parameters Parameter name Comment (description) destDirFileId fileId of the destination folder (required) string name The name of the created category library (required) string accessType Classification visibility (optional) Defaults to public 0. 0: // public 1: // Need to apply 2: // Department is public 3: // Department application 4: // Confidential managerIds The id array type of the person in charge [usrId1,userId2] departmentIds Classification visibility limited department id of department (optional) Array type [departmentId1,departmentId2] The return information is as follows {\"code\":0, \"success\":true, \"materialClass\": {}} Create sub material library /nd /api/file/create material folder HTTP method: POST POST request body parameters Parameter name Comment (description) destDirFileId fileId of the destination folder (required) string name The name of the created category library (required) string accessType Classification visibility (optional) Defaults to public 0. 0: // public 1: // Need to apply 2: // Department is public 3: // Department application 4: // Confidential managerId The id of the person in charge (optional) string departmentIds Classification visibility limited department id of department (optional) Array type [departmentId1,departmentId2] assistantIds ID of the material library assistant (optional) Array type [usrId1,userId2] The return information is as follows {\"code\":0, \"success\":true, \"materialFolder\": {}} Shared file related API PDF Page 18 Get the sharing url of the file /nd/api/share/shareurl HTTP method: GET Get the sharing link of the file (open the sharing first, and then get the link) URL parameters Parameter name Comment (description) file id file id string is https Whether the returned share url protocol is https 0 means http, 1 means https, default 0 number Return field description {\"code\":0,\"url\":\"https://private.babel.cc/share.do?s=http://private.babel.cc/share.do?s=MjY2OTYzNTk3OTU2NzEzOTtXZWQgSnVsIDAxIDIwMj AgMTg6MzM6NTAgR01UKzA4MDAgKEhvbmcgS29uZyBTdGFuZGFyZCBUaW1lKQ%3D%3D\",\"success\":true} Get the sharing permission list /nd/api/share/share roles HTTP method: GET URL parameters Parameter name Comment (description) Return field description {\"code\":0,\"roles\":[],\"success\":true} Get the sharing roles that the user has permission to set for a single file /nd/api/share/share role forfile HTTP method: GET URL parameters Parameter name Comment (description) file id file id string Return field description {\"code\":0,\"roles\":[],\"success\":true} Create link to share /nd/api/share/open link share HTTP method: POST Open sharing and get a new sharing link. The previous link will be invalid. PDF Page 19 POST request body parameters Parameter name Comment (description) file id pre shared file id (required) string link role id shared role string is https Whether the returned share url protocol is https number anonymousVisit Whether to allow anonymous access, 1 means allowed, 0 means not allowed (optional, default is 1) number Return field description {\"code\":0,\"share url\":\"http://private.babel.cc/share.do?s=http://private.babel.cc/share.do?s=MjY2OTYzNTk3OTU2NzEzOTtXZWQgSnV sIDAxIDIwMjAgMTg6MzM6NTAgR01UKzA4MDAgKEhvbmcgS29uZyBTdGFuZGFyZCBUaW1lKQ%3D%3D\",\"password\":\"\",\"success\":tru e} Close link sharing /nd/api/share/close link share HTTP method: POST Close the shared link I opened POST request body parameters Parameter name Comment (description) file id shared file id (required) string Return field description {\"code\":0,\"success\":true} Set link sharing password /nd/api/share/set share password HTTP method: POST File link sharing is turned on, set a password for link sharing. POST request body parameters Parameter name Comment (description) file id pre shared file id (required) string password password for link sharing string is https Whether the returned share url protocol is https number Return field description {\"code\":0,\"success\":true, \"share url\": \"http://private.babel.cc/share.do?s=xxxxxxxxxxx\"} Invite people to share /nd/api/share/invite share HTTP method: POST PDF Page 20 You can invite certain people to access files based on the user's email or mobile phone POST request body parameters Parameter name Comment (description) file id file id (required) string share role ID of the shared permission (all the above people share this permission) (required) string emails[] email array string[] phones[] array of mobile phone numbers string[] Return field description {\"code\":0,\"success\":true} Get all sharing participants /nd/api/share/share participants HTTP method: GET URL parameters Parameter name Comment (description) file id file id (required) string Return field description {\"code\":0,\"users\":[],\"success\":true} Set permission roles for sharing participants /nd/api/share/set participant role HTTP method: POST POST request body parameters Parameter name Comment (description) file id file id (required) string babelshare id int (required) user id string role id int (required) role id string Return field description {\"code\":0,\"success\":true} Delete sharing participants /nd/api/file/remove share participant HTTP method: POST POST request body parameters Parameter name Comment (description) PDF Page 21 file id file id (required) string babelshare ids[] int (required) user id string Return field description {\"code\":0,\"success\":true} Reminder /nd/api/file/focus file HTTP method: POST POST request body parameters Parameter name Comment (description) file id file id (required) string user ids[] The id of the user to be reminded. This id should be selected among the file participants, otherwise the reminder will not work (required) string[] Return field description {\"code\":0,\"success\":true} Remove someone’s attention /nd/api/file/unfocus file HTTP method: POST POST request body parameters Parameter name Comment (description) file id file id (required) string user ids[] The id of the user to be reminded. This id should be selected among the file participants, otherwise the reminder will not work (required) string[] Return field description {\"code\":0,\"success\":true} Get the list of users following the file /nd/api/file/user focusfile HTTP method: GET URL parameters Parameter name Comment (description) file id file id (required) string Return field description {\"code\":0,\"users\":[],\"success\":true} Get the list of users who can follow the file, and mark the users who have followed the file /nd/api/file/user can focusfile PDF Page 22 HTTP method: GET URL parameters Parameter name Comment (description) file id file id (required) string Return field description Enterprise department related API Get current enterprise information /nd/api/enterprise/current HTTP method: GET URL parameters Parameter name Comment (description) None Return field description {\"code\":0,\"enterprise\":{},\"success\":true} Get information about all departments of the enterprise /nd/api/enterprise/departments HTTP method: GET URL parameters Parameter name Comment (description) None Return field description Attribute name type description departments [] array returns all department information tree {}json data returns the parent child structure information of the department code int successboolean Create enterprise department /nd/api/enterprise/create department HTTP method: POST PDF Page 23 POST request body parameters Parameter name Comment (description) parent dep parent department id, 0 means following department (required) string name department name (required) string description department description string Return field description Attribute name type description department {} json data structure code int successboolean Get the list of department roles /nd/api/enterprise/dep role HTTP method: GET URL parameters Parameter name Comment (description) Return field description Attribute name type description roles []array { id, filePermission,enterpriseId,filePermission,managerPermission, default,nameEn,name} code int successboolean Add department personnel /nd/api/enterprise/add dep mem HTTP method: POST POST request body parameters Parameter name Comment (description) department id department id (required) string user ids[] user list string[] role id The user's role in the department string PDF Page 24 Return field description Attribute name type description Delete department personnel /nd/api/enterprise/remove dep mem HTTP method: POST POST request body parameters Parameter name Comment (description) department id department id (required) string user ids[] Person’s id (required) string[] Return field description Attribute name type description Get information about your department /nd/api/enterprise/mydeparments HTTP method: GET URL parameters Parameter name Comment (description) None Return field description Attribute name type description departments [] array returns my department information code int successboolean Get department personnel /nd/api/enterprise/departmentmembers PDF Page 25 HTTP method: GET URL parameters Parameter name Comment (description) department id department id (required) string Return field description Attribute name type description users array: {id, name, avatrUrl,} Add company members /nd/api/enterprise/add ent mem HTTP method: POST POST request body parameters Parameter name Comment (description) email Email mailbox string password password string enterprise role enterprise member role, optional number department ids[] The user's department, optional string[] department roles[] Roles in the department, optional string[] sex 0 not set 1 male 2 female number name username string phone mobile phone number, optional string babelId employee ID, optional string spacelimit personal space limit, unit GB, 0 means no limit number can ownfile whether the user can have personal files, 1 use the overall enterprise settings, 0 no personal files, 1 have personal files number remarks user description, optional string join time The time when the user joined the enterprise, Unix time, unit number seconds password is md5 Whether the incoming password requires md5 encryption, 0 non md5 password, 1 md5 encrypted password number Update member information /api/updateUserInfo.do HTTP method: POST POST request body parameters Parameter name Comment (description) email email address (search keyword, required) string password password (change password, optional) string frozen 1 – means frozen, 0 – means unfrozen (freeze the account, optional) number password is md5 Whether the incoming password requires md5 encryption, 0 non md5 password, 1 md5 encrypted password number phone mobile phone number (optional) string PDF Page 26 Get enterprise member information /api/getEnterpriseMember.do HTTP method: GET URL parameters Parameter name Comment (description) email email address (search keyword) string phone mobile phone number (search keyword) string babelId employee number (search keyword) string email/phone/babelId you can choose one Return field description {\"code\":0,\"success\":true,\"user\":{}} Get all members of the company /nd/api/enterprise/enterprise members HTTP method: POST POST request body parameters Parameter name Comment (description) lang language type, cn Chinese, en English, optional options { departmentId: //Department id, if not filled in, it means all employees of the enterprise roleId: // Role id, if not filled in, there is no role limit \"userType\": 0, // 0 internal personnel, 1 external personnel \"keyName\": \"\", // Search keywords: name, mobile phone number, email address, if not filled in, it means all people \"startIndex\": 0, \"pageSize\": 20, status: // 0 all accounts, 1 deactivated accounts } Optional Return field description {\"code\":0,\"success\":true,\"members\":{},\"total\":xx} Get enterprise logs /nd/api/enterprise/enterprise logs HTTP method: POST POST request body parameters Parameter name Comment (description) department id department id, if not filled in, it will be the log of all departments string optional keyword related search keyword string optional PDF Page 27 startTime log starting time number optional endTime log end time number optional startIndex int optional pageSize int optional Return field description {\"code\":0,\"success\":true,\"logs\":{},\"total\":xx} Message Push API Make an announcement /nd/api/enterprise/broadcast HTTP method: POST POST request body parameters Parameter name Comment (description) title Announcement content string (required) string content content (required) string target users[] UserId array, if empty, it means all users will receive it, string[] target deps[] Target department, all members of this department and sub departments will receive notification, string[] Target users and target deps must be filled in at least 1 Return field description {\"code\":0,\"success\":true} Get published announcements /nd/api/enterprise/broadcast HTTP method: GET URL parameters Parameter name Comment (description) start index number pagesize number Return field description {\"code\":0,\"broadcasts\":[],\"total\":19,\"success\":true} Send department discussion /nd/api/file/send dep discussion HTTP method: POST PDF Page 28 POST request body parameters Parameter name Comment (description) dep id department id (required) string message information character (required) string json string, format {Type: “Text”, Body: “Hello” } Return field description {\"code\":0,\"messageId\":99,\"success\":true} Get department discussion /nd/api/file/dep discussion HTTP method: POST POST request body parameters Parameter name Comment (description) dep id department id (required) string pagesize page size string start id message id, only the messages before this message will be obtained, if it is empty, the latest message will be obtained string Return field description {\"msgArr\":[],\"gotMoreMessages\":1,\"code\":0,\"success\":true} Get enterprise logs /nd/api/enterprise/enterprise logs HTTP method: GET URL parameters Parameter name Comment (description) department id department id() string pagesize page size number, default value 1000 start index message starting position, number keyword log keyword string startTime start date: seconds number endTime expiration date seconds number Return field description {\"logs\":[],\"total\":0,\"code\":0,\"success\":true} total returns all those that meet the conditions (regardless of paging pageSize) PDF Page 29 4. JWT token login In private cloud deployment, the login method of jwt token can be enabled. In this case, the following url is allowed to directly enter the network disk system as a user without logging in. System: /account/tokenLogin.do Parameters: Parameter name Optional Description Optional value Default value userToken is required and contains the encrypted information of the logged in user (Constructor None See the instructions below for details) fileId optional The id of the file (folder) to be accessed, if not None If filled in, the user root directory will be opened. closeTitleBar optional Whether to close the title bar 1 Close 0 Do not close 0 disableEntMark Optional Whether to hide the corporate logo in the upper left corner 1 Hide 0 Do not hide 0 disableUserMark Optional Whether to hide the user settings entrance in the upper right corner 1 Hide 0 Do not hide 0 defaultLang optional Set the language used by the interface cn Chinese en English zh HK Traditional cn defaultClrTheme is optional and sets the interface color theme. normal is the standard mode, dark is the dark mode normal. For example, the following is the user root interface in English and dark mode with the user logo in the upper right corner hidden. /account/tokenLogin.do userToken=xxxxxxxxxxxxxxxx defaultClrTheme=dark defaultLang=en disableUserMark=1 Construction of userToken userToken is an encrypted string containing logged in user information. The encrypted information is a password created by JWT, a standard security mechanism for transmitting trusted data between two parties. The content of JWT encrypted user information JSONObject is as follows: { payload: { email: “xxx@xxx.com”/“135XXXXXXX”/“XXXX”} time: now } Note: email can be an email address, mobile phone number, or work number; The code is as follows: public static void main( String[] args ) { HashMap user = new HashMap (); user.put(\"email\", \"yuanchaozhao@qq.com\"); try { //token login String userToken = createTokenJWT(user); System.out.println(\" login token:\" + userToken); JSONObject parsed = parseTokenJWT(userToken); System.out.println(\" parsed:\" + parsed); System.out.println(\" Just put this token as a parameter in the url, such as: \"); System.out.println(\"/account/tokenLogin.do?userToken=\" + userToken); } catch (Exception e) { System.out.println(e.getMessage()); } } For other codes, please refer to the jwtToken generation code, which is provided in the authentication interface 2. Remarks: JWT is the abbreviation of JSON Web Tokens. It is a communication encryption and decryption mechanism that meets the industry standard RFC7519. Please refer to: https://jwt.io/ PDF Page 30 5. Appendix Common API call return status code Status code result code Code value Description 0 success 1 unknown error 2 parameter error 7 Not enough space 12 Prohibited user actions 13 invalid token the end" }, { "lang": "en", "slug": "developer-api-enterprise", "title": "Enterprise API", "description": "Interface paths, methods, parameters, and return fields for enterprise APIs.", "category": "Enterprise API", "top_category": "API文档", "keywords": [ "API", "Enterprise API", "Developer" ], "url": "en/developer-api-enterprise.html", "source": "content/en/developer-api-enterprise.md", "summary": "Enterprise API PDF Page 1 Enterprise Development API V6.6 Shanghai Huaqing Information Technology Co., Ltd. Jiang Dajun PDF Page 2 Directory 1. Obtain an enterprise development account .................................................................................................................................................................................4 2. Authentication API ................................................................................................................................................................................................. 6 Authentication interface one (login callback method) .................................................................", "headings": [ { "level": 1, "title": "Enterprise API", "id": "enterprise-api" }, { "level": 3, "title": "PDF Page 1", "id": "pdf-page-1" }, { "level": 3, "title": "PDF Page 2", "id": "pdf-page-2" }, { "level": 3, "title": "PDF Page 3", "id": "pdf-page-3" }, { "level": 3, "title": "PDF Page 4", "id": "pdf-page-4" }, { "level": 2, "title": "1. Obtain an enterprise development account", "id": "1-obtain-an-enterprise-development-account" }, { "level": 3, "title": "PDF Page 5", "id": "pdf-page-5" }, { "level": 3, "title": "PDF Page 6", "id": "pdf-page-6" }, { "level": 2, "title": "2. Authentication API", "id": "2-authentication-api" }, { "level": 3, "title": "Authentication interface one (login callback method)", "id": "authentication-interface-one-login-callback-method" }, { "level": 3, "title": "PDF Page 7", "id": "pdf-page-7" }, { "level": 3, "title": "PDF Page 8", "id": "pdf-page-8" }, { "level": 3, "title": "Get token", "id": "get-token" }, { "level": 3, "title": "Refresh token", "id": "refresh-token" }, { "level": 2, "title": "3. File access API", "id": "3-file-access-api" }, { "level": 3, "title": "PDF Page 9", "id": "pdf-page-9" }, { "level": 3, "title": "Get file list", "id": "get-file-list" }, { "level": 3, "title": "Get file information", "id": "get-file-information" }, { "level": 3, "title": "PDF Page 10", "id": "pdf-page-10" }, { "level": 3, "title": "Create folder", "id": "create-folder" }, { "level": 3, "title": "Pre upload files", "id": "pre-upload-files" }, { "level": 3, "title": "PDF Page 11", "id": "pdf-page-11" }, { "level": 3, "title": "Upload files", "id": "upload-files" }, { "level": 3, "title": "PDF Page 12", "id": "pdf-page-12" }, { "level": 3, "title": "Get download file address", "id": "get-download-file-address" }, { "level": 3, "title": "Get download address of multiple files", "id": "get-download-address-of-multiple-files" }, { "level": 3, "title": "PDF Page 13", "id": "pdf-page-13" }, { "level": 3, "title": "Get download file thumbnail address", "id": "get-download-file-thumbnail-address" }, { "level": 3, "title": "Modify file information", "id": "modify-file-information" }, { "level": 3, "title": "Modify file information", "id": "modify-file-information-2" }, { "level": 3, "title": "Modify file name", "id": "modify-file-name" }, { "level": 3, "title": "Modify file information", "id": "modify-file-information-3" }, { "level": 3, "title": "PDF Page 14", "id": "pdf-page-14" }, { "level": 3, "title": "Delete files (to recycle bin)", "id": "delete-files-to-recycle-bin" }, { "level": 3, "title": "Delete files (from Recycle Bin)", "id": "delete-files-from-recycle-bin" }, { "level": 3, "title": "Empty the Recycle Bin", "id": "empty-the-recycle-bin" }, { "level": 3, "title": "Recover files (from Recycle Bin)", "id": "recover-files-from-recycle-bin" }, { "level": 3, "title": "PDF Page 15", "id": "pdf-page-15" }, { "level": 3, "title": "Get all version information of the file", "id": "get-all-version-information-of-the-file" }, { "level": 3, "title": "Set the current version of the file", "id": "set-the-current-version-of-the-file" }, { "level": 3, "title": "Move files", "id": "move-files" }, { "level": 3, "title": "Copy files", "id": "copy-files" }, { "level": 3, "title": "PDF Page 16", "id": "pdf-page-16" }, { "level": 3, "title": "Copy file progress", "id": "copy-file-progress" }, { "level": 3, "title": "File log", "id": "file-log" }, { "level": 3, "title": "Set whether the user has permission to access the material library", "id": "set-whether-the-user-has-permission-to-access-the-material-library" }, { "level": 3, "title": "PDF Page 17", "id": "pdf-page-17" }, { "level": 3, "title": "Create material library classification", "id": "create-material-library-classification" }, { "level": 3, "title": "Create sub material library", "id": "create-sub-material-library" }, { "level": 2, "title": "Shared file related API", "id": "shared-file-related-api" }, { "level": 3, "title": "PDF Page 18", "id": "pdf-page-18" }, { "level": 3, "title": "Get the sharing url of the file", "id": "get-the-sharing-url-of-the-file" }, { "level": 3, "title": "Get the sharing permission list", "id": "get-the-sharing-permission-list" }, { "level": 3, "title": "Get the sharing roles that the user has permission to set for a single file", "id": "get-the-sharing-roles-that-the-user-has-permission-to-set-for-a-single-file" }, { "level": 3, "title": "Create link to share", "id": "create-link-to-share" }, { "level": 3, "title": "PDF Page 19", "id": "pdf-page-19" }, { "level": 3, "title": "Close link sharing", "id": "close-link-sharing" }, { "level": 3, "title": "Set link sharing password", "id": "set-link-sharing-password" }, { "level": 3, "title": "Invite people to share", "id": "invite-people-to-share" }, { "level": 3, "title": "PDF Page 20", "id": "pdf-page-20" }, { "level": 3, "title": "Get all sharing participants", "id": "get-all-sharing-participants" }, { "level": 3, "title": "Set permission roles for sharing participants", "id": "set-permission-roles-for-sharing-participants" }, { "level": 3, "title": "Delete sharing participants", "id": "delete-sharing-participants" }, { "level": 3, "title": "PDF Page 21", "id": "pdf-page-21" }, { "level": 3, "title": "Reminder", "id": "reminder" }, { "level": 3, "title": "Remove someone’s attention", "id": "remove-someone-s-attention" }, { "level": 3, "title": "Get the list of users following the file", "id": "get-the-list-of-users-following-the-file" }, { "level": 3, "title": "Get the list of users who can follow the file, and mark the users who have followed the file", "id": "get-the-list-of-users-who-can-follow-the-file-and-mark-the-users-who-have-followed-the-file" }, { "level": 3, "title": "PDF Page 22", "id": "pdf-page-22" }, { "level": 2, "title": "Enterprise department related API", "id": "enterprise-department-related-api" }, { "level": 3, "title": "Get current enterprise information", "id": "get-current-enterprise-information" }, { "level": 3, "title": "Get information about all departments of the enterprise", "id": "get-information-about-all-departments-of-the-enterprise" }, { "level": 3, "title": "Create enterprise department", "id": "create-enterprise-department" }, { "level": 3, "title": "PDF Page 23", "id": "pdf-page-23" }, { "level": 3, "title": "Get the list of department roles", "id": "get-the-list-of-department-roles" }, { "level": 3, "title": "Add department personnel", "id": "add-department-personnel" }, { "level": 3, "title": "PDF Page 24", "id": "pdf-page-24" }, { "level": 3, "title": "Delete department personnel", "id": "delete-department-personnel" }, { "level": 3, "title": "Get information about your department", "id": "get-information-about-your-department" }, { "level": 3, "title": "Get department personnel", "id": "get-department-personnel" }, { "level": 3, "title": "PDF Page 25", "id": "pdf-page-25" }, { "level": 3, "title": "Add company members", "id": "add-company-members" }, { "level": 3, "title": "Update member information", "id": "update-member-information" }, { "level": 3, "title": "PDF Page 26", "id": "pdf-page-26" }, { "level": 3, "title": "Get enterprise member information", "id": "get-enterprise-member-information" }, { "level": 3, "title": "Get all members of the company", "id": "get-all-members-of-the-company" }, { "level": 3, "title": "Get enterprise logs", "id": "get-enterprise-logs" }, { "level": 3, "title": "PDF Page 27", "id": "pdf-page-27" }, { "level": 2, "title": "Message Push API", "id": "message-push-api" }, { "level": 3, "title": "Make an announcement", "id": "make-an-announcement" }, { "level": 3, "title": "Get published announcements", "id": "get-published-announcements" }, { "level": 3, "title": "Send department discussion", "id": "send-department-discussion" }, { "level": 3, "title": "PDF Page 28", "id": "pdf-page-28" }, { "level": 3, "title": "Get department discussion", "id": "get-department-discussion" }, { "level": 3, "title": "Get enterprise logs", "id": "get-enterprise-logs-2" }, { "level": 3, "title": "PDF Page 29", "id": "pdf-page-29" }, { "level": 2, "title": "4. JWT token login", "id": "4-jwt-token-login" }, { "level": 3, "title": "PDF Page 30", "id": "pdf-page-30" }, { "level": 2, "title": "5. Appendix Common API call return status code", "id": "5-appendix-common-api-call-return-status-code" }, { "level": 2, "title": "Status code result code", "id": "status-code-result-code" } ], "images": [], "text": "Enterprise API PDF Page 1 Enterprise Development API V6.6 Shanghai Huaqing Information Technology Co., Ltd. Jiang Dajun PDF Page 2 Directory 1. Obtain an enterprise development account .................................................................................................................................................................................4 2. Authentication API ................................................................................................................................................................................................. 6 Authentication interface one (login callback method) ..................................................................................................................................................................6 Authentication interface two (login free method – JWT token method, in private cloud deployment, the jwt token login method needs to be enabled) .................................. 6 Get token .................................................................................................................................................................................................................8 Refresh token ..................................................................................................................................................................................................................8 3. File access API...................................................................................................................................................................................................... 8 Get file list ........................................................................................................................................................................................9 Get file information ........................................................................................................................................................................................9 Create a folder .................................................................................................................................................................................................10 Pre upload files ................................................................................................................................................................................................10 Uploading files .................................................................................................................................................................................................................11 Get the download file address .................................................................................................................................................................................12 Obtain the download address of multiple files .................................................................................................................................................................12 Get the download file thumbnail address .................................................................................................................................................................13 Modify file information .................................................................................................................................................................................13 Modify file name .................................................................................................................................................................................................13 Delete files (to Recycle Bin) ..................................................................................................................................................................................14 Deleting files (from Recycle Bin) ..................................................................................................................................................................14 Empty the Recycle Bin .................................................................................................................................................................................................14 Recovering files (from the Recycle Bin) ..................................................................................................................................................................14 Get all version information of a file .............................................................................................................................................................15 Current version of settings file .............................................................................................................................................................................15 Moving files .................................................................................................................................................................................................15 Copying files .................................................................................................................................................................................................15 Copying file progress ........................................................................................................................................................................................16 File Log .................................................................................................................................................................................................................16 Create library categories .................................................................................................................................................................................17 Create a sublibrary ............................................................................................................................................................................................17 Shared file related API ................................................................................................................................................................................. 17 Get the sharing url of the file ................................................................................................................................................................................. 18 Get the shared permission list .................................................................................................................................................................18 Obtain the sharing role that the user has permission to set for a single file .............................................................................................................................18 Create a link to share .................................................................................................................................................................................18 Turn off link sharing ........................................................................................................................................................................................19 Set link sharing password .................................................................................................................................................................................19 Invite people to share .................................................................................................................................................................19 Get all sharing participants .................................................................................................................................................................20 Set permission roles for sharing participants .............................................................................................................................................................20 Delete sharing participants ........................................................................................................................................................................20 Reminder...................................................................................................................................................................................................21 Remove someone from following .................................................................................................................................................................................21 Get the list of users following a file .................................................................................................................................................................21 Get the list of users who can follow the file and mark the users who have followed the file .............................................................................................21 Enterprise department related API ................................................................................................................................................................................. 22 Obtain current company information ..................................................................................................................................................................22 Obtain information from all departments of the enterprise ........................................................................................................................................................22 Creating a corporate division .................................................................................................................................................................................22 Get a list of department roles .................................................................................................................................................................................23 Add department personnel .................................................................................................................................................................................................23 Delete department personnel ................................................................................................................................................................................................24 Obtain information about your department .................................................................................................................................................................24 Obtain department personnel ................................................................................................................................................................................................24 Adding company members .................................................................................................................................................................................25 Update member information................................................................................................................................................................................25 Obtain enterprise member information .................................................................................................................................................................................26 Get all members of the company .................................................................................................................................................................................26 Obtain enterprise logs .................................................................................................................................................................................................26 Message push API................................................................................................................................................................................................................ 27 Announcement................................................................................................................................................................................................27 Get published announcements ................................................................................................................................................................................27 Send Department Discussion .................................................................................................................................................................................27 Get departmental discussions .................................................................................................................................................................................28 Obtain enterprise logs .................................................................................................................................................................................................28 4. JWT token login .................................................................................................................................................................................29 5. Appendix Common API call return status code ............................................................................................................................................................. 30 PDF Page 3 Status code result code .................................................................................................................................................................................................. 30 PDF Page 4 1. Obtain an enterprise development account Log in to the Babel Private Cloud Enterprise Management Backend and set up a developer account on the home page: After opening, fill in the callback function address: http://xxx.xxx.xxx.xxx/public/babelAuthResult.do After filling in and clicking OK, the developer ID (client id) and developer key (client secret) will be automatically generated: Note: jwtToken is the corresponding encryption key when generating jwtToken. PDF Page 5 PDF Page 6 2. Authentication API Authentication interface one (login callback method) /api/authorize.do HTTP request method GET URL parameters Parameter name Comment (description) response type must be code (required) string client id developer's id (required) string redirect uri callback function address, needs to be consistent with registration (required) string data: any data, string returned during callback For example: /api/authorize.do?response type=code&client id=xxxxx&redirect uri=http://xxx.xxx.xxx&data=xxx Access via browser Return results If the user is not logged in, it will jump to the login page. After logging in, if it is not authorized, it will 302 jump to the authorization page. If the user has been authorized, it will 302 jump to redirect uri and bring authorization code and data, similar to http://xxx.xxx.xxx?code=xxx&data=xxx The code is valid for 5 minutes. Authentication interface two (login free method – JWT token method. In private cloud deployment, the login method of jwt token needs to be enabled. formula) /api/authorizeByJWT.do HTTP request method GET URL parameters Parameter name Comment (description) response type must be code (required) string client id developer's id (required) string jwt token Jwt token, (required) string It is a string formed by encrypting {client id: xxxxxxx} email email (optional), enter the user's email address, log in as this user, leave it blank to log in as an enterprise administrator, string phone phone (optional), enter the user's mobile phone number and log in as this user. Leave it blank to log in as the enterprise administrator. string babelId babelId (optional), pass in the user's work ID, log in as this user, leave it blank to log in as the enterprise administrator, string PDF Page 7 For example: /api/authorizeByJWT.do?response type=code&client id=xxxxx&jwt token=xxx Note: When using this API, if you do not fill in email, phone, babelId, the system will automatically log in as an administrator, otherwise it will log in as the user corresponding to email, phone, babelId. Log in, the login interface will not be displayed to log in. Note (email, phone, babelId) only needs one of them. Return results { \"success\": true \"code\": \"xxxxxxxxxxxxxxxxxxxxxxxxxxx\", } jwt token is generated by writing your own program. The sample code is as follows: import java.util.Date; import java.util.HashMap; import java.util.Map; import javax.crypto.SecretKey; import javax.crypto.spec.SecretKeySpec; import io.jsonwebtoken.Claims; import io.jsonwebtoken.JwtBuilder; import io.jsonwebtoken.Jwts; import io.jsonwebtoken.SignatureAlgorithm; import net.sf.json.JSONObject; / Generate token used by standard jwt / public class JWT App { static String skey = \"babeldfdfer95840834 t8e 9 9 5934 5943 5886256\"; // The key is the jwtToken field filled in the developer account in the Babel backend. public static void main( String[] args ) { HashMap clientInfo = new HashMap (); clientInfo.put(\"client id\", \"7459492016147273\"); // is the client id in the developer account try { String token = createTokenJWT(clientInfo); System.out.println(\" login token:\" + token); String token1 = \"eyJhbGciOiJIUzI1NiJ9.eyJkdXJhdGlvbiI6NjAsInBheWxvYWQiOnsiY2xpZW50X2lk IjoiNzQ1OTQ5MjAxNjE0NzI3MyJ9LCJ0aW1lIjoxNjkxNDg4MzY4NTk0fQ.pRFCwXd2snMr IgFWOFwYbvyAeeNhoFINGk Wmv7d24g\"; JSONObject parsed = parseTokenJWT(token1); System.out.println(\" parsed:\" + parsed); System.out.println(\" Just put this token as a parameter in the url, such as: \"); } catch (Exception e) { System.out.println(e.getMessage()); } } public static String createTokenJWT(Map config) throws Exception { HashMap data = new HashMap (); data.put(\"time\", new Date().getTime()); data.put(\"duration\", 60); data.put(\"payload\", config); SignatureAlgorithm signatureAlgorithm = SignatureAlgorithm.HS256; SecretKey key = generalKey(); JwtBuilder builder = Jwts.builder() .setClaims(data) .signWith(signatureAlgorithm, key); System.out.println( \" builder : \" + builder); return builder.compact(); } public static JSONObject parseTokenJWT(String jwt) throws Exception { SecretKey key = generalKey(); Claims claims = Jwts.parser() .setSigningKey(key) .parseClaimsJws(jwt) .getBody(); System.out.println(\" claims:\" + claims.toString()); Long time = (Long)claims.get(\"time\"); long duration = (Integer)claims.get(\"duration\"); Long now = new Date().getTime(); if (now time 1000 duration) return null; // Tokens older than 10 minutes are invalid JSONObject obj = JSONObject.fromObject(claims.get(\"payload\")); return obj; } public static SecretKey generalKey(){ String stringKey = skey; byte[] encodedKey = stringKey.getBytes(); SecretKey key = new SecretKeySpec(encodedKey, 0, encodedKey.length, \"HmacSHA256\"); return key; } } PDF Page 8 Get token /api/token.do HTTP method: POST HTTP Header This interface uses Basic Auth to verify client information. The specific method is to add something like \"Authorization: Basic xxxxxxxxx\" in the header. Among them \"xxxxxxxxx\" is calculated from the developer id (client id) and developer secret key (client secret). The specific algorithm is Base64Encode(client id + \":\" + client secret) Base64Encode Choose your own tool for Base64 encoding URL parameters Parameter name Comment (description) grant type (required) must be authorization code string code (required) Authorization code, that is, the authorization code received by the callback address. The authorization code is valid for 5 minutes. It is used once, regardless of success. If it still fails, the authorization code will become invalid string For example: /api/token.do?grant type=authorization code&code=xxx&redirect uri=http://xxx.xxx.xxx Return results access token interface access token refresh token is used to refresh access token, valid for 30 days The validity time of expires in access token, unit is s Refresh token /api/refreshToken.do HTTP method: POST HTTP Header This interface uses Basic Auth to verify client information. The specific method is to add something like \"Authorization: Basic xxxxxxxxx\" in the header. Among them \"xxxxxxxxx\" is calculated through client id and client secret. The specific algorithm is Base64Encode(client id + \":\" + client secret) URL parameters Parameter name Comment (description) grant type (required) must be refresh token string refresh token (required) is the refresh token string obtained in interface 2 For example: /api/refreshToken.do?grant type=refresh token&refresh token=xxx Return results access token interface access identification, refresh token is used to refresh access token, valid for 30 days The validity time of expires in access token is 3600, the unit is s 3. File access API All interfaces need to carry access token in the HTTP header when accessing. For interfaces containing request parameters, usually some POST, PUT or DELETE interface, you also need to set Content Type to specify the format of the parameters. If you need to access different versions of the API, you need Specify a specific version on the request path. If you need to return a response body in a different format, you also need to set Accept. All parameters should be This should use utf 8 encoding. PDF Page 9 Headers: Authorization: stores access token, the format is: \"Bearer \" + access token. Content Type: Indicates the format of the request parameters. If it is a POST, PUT or DELETE request, you need to specify \"application/json\", I We currently do not support other request parameter formats, such as xml. If it is other types such as GET requests, it does not need to be set in the header. Content Type. Accept: used to specify the format of the response result and the version information of the api. Currently, only response in json format is supported, so in general Specify \"application/json\". If the interface access is successful, we will return a response in json format, and the HTTP status code is 200. All successful response responses All json will contain \"success: true\". The X Babel Version in the header of the response indicates the version number of the api accessed by this request. Get file list /nd/api/file/list dir HTTP method: GET URL parameters Parameter name Comment (description) parent id parent folder id (required) string When parent is 1, returns the contents of the corporate folder, 2 returns the contents of the personal folder, 3 returns my Project, 4 returns the share I added, and other fileId returns the contents of the normal folder. page size page size number page page number type type: divided into three types: 1 file, 2 folder, 0 all string Return field description Attribute name type description files array file information {fileId, name, …} total int total quantity page int page capacity success boolean gets the success mark code int returns error code 0 indicates success Get file information /nd/api/file/fileinfo HTTP method: GET URL parameters Parameter name Comment (description) id file id (required) string Return field description fileInfo information Attribute name type description file Object file information { id, name, …} PDF Page 10 success boolean gets the success mark code int returns error code 0 indicates success Create folder /nd/api/file/create folder HTTP method: POST POST request body parameters Parameter name Comment (description) parent id target folder id (required) string name file name (required) string Return field description Attribute name type description file Object file information { id, name, …} success boolean gets the success mark code int returns error code 0 indicates success Pre upload files Used to return the parameters (url, upload token) required when uploading files in the second step. /api/file/preUploadFile.do HTTP method: GET URL parameters Parameter name Comment (description) parent id target folder id (required) (you can ignore this when uploading in the root directory) string name file name (required) string file id When uploading a new version, you need to specify the new version of the file to upload (you can ignore this when uploading new files) string The correct return result is as follows {\"upload token\":\"92808ecfc2ac4e0ebc0b912edac3be4a\",\"url\":\"http://testdocument.babel.cc/api/file/uploadPdf.do\",\"su ccess\":true,\"code\":0} Return field description Attribute name type description url string This url can only be used once and is valid for 1 hour. Call this url to upload a file. After success, fileId, fileName, version, etc. will be returned. upload token string is used as a parameter of post when uploading files. PDF Page 11 Upload files Note that the URL of this API is returned by the pre upload interface. There is no specific URL here, just parameter description. https://xxx.xxx.xxx:xxx/api/file/uploadXXX.do (the specific URL is the URL returned by /api/file/preUploadFile.do in the previous section) POST POST request body parameters Parameter name Comment (description) file file binary data (upload data) Return value in upload token /api/file/preUploadFile.do request The return information is as follows {\"fileId\":\"7728538212615908\",\"version\":0,\"fileName\":\"mesos.pdf\",\"fileSize\":848854,\"success\":true,\"code\":0} Upload relevant code examples Add ‘com.squareup.okhttp3:okhttp:3.3.1’ package private void uploadFile(final String fileName, String parentId, final DaoCallback callback){ preUploadFile(fileName, parentId, new DaoCallback () { @Override public void onSuccess(JSONObject data) { int code = data.optInt(\"code\", 1); final String url = data.optString(\"url\", null); final String uploadToken = data.optString(\"upload token\"); if (code == 0) { // File file = new File(filePath); RequestBody fileContent = RequestBody.create(MultipartBody.FORM, file); RequestBody requestBody = new MultipartBody.Builder() .setType(MultipartBody.FORM) .addFormDataPart(\"file\", fileName, fileContent) .addFormDataPart(\"upload token\", uploadToken) .build(); Request request = new Request.Builder() .url(url) .post(requestBody) .build(); // Uploading takes a long time, so you need to set a longer timeout OkHttpClient okHttpClient = new OkHttpClient(); okHttpClient.newCall(request) .enqueue(new okhttp3.Callback() { @Override public void onFailure(okhttp3.Call call, IOException e) { callback.onFailure( 1, null); } @Override public void onResponse(okhttp3.Call call, okhttp3.Response response) throws IOException { int httpCode = response.code(); if (httpCode == 200) { try { JSONObject result = new JSONObject(response.body().string()); response.body().close(); boolean success = result.getBoolean(\"success\"); if (success) { callback.onSuccess(null); } else { int code = result.getInt(\"code\"); String msg = result.optString(\"msg\"); callback.onFailure(code, msg); } } catch (JSONException e) { callback.onFailure( 2, null); } } else { callback.onFailure(httpCode, null); } } }); } } @Override public void onFailure( int errorCode, String msg){ Log.e(\"FileTransfer\", \"filePreUpload failed errorCode=\" + errorCode); } }); } PDF Page 12 private void preUploadFile(String fileName, String parentId, final DaoCallback callback) { String preUploadUrl = \"http://private.babel.cc:80/api/file/preUploadFile.do?name=1234.jpg&parent id=0\"; // Pass in the corresponding parameters name, parent id String authorization = \"Bearer d48d0a0e253c4a2985d8c5653f717d71\"; //Generate according to the instructions Request request = new Request.Builder().url(preUploadUrl) .addHeader(\"Authorization\", authorization) .build(); OkHttpClient okHttpClient = new OkHttpClient(); okHttpClient.newCall(request).enqueue(new okhttp3.Callback() { @Override public void onFailure(okhttp3.Call call, IOException e) { Log.d(\"\", \"\"); } @Override public void onResponse(okhttp3.Call call, okhttp3.Response response) throws IOException { Log.d(\"\",\"\"); int httpCode = response.code(); if (httpCode == 200) { JSONObject result = null; try { result = new JSONObject(response.body().string()); } catch (JSONException e) { e.printStackTrace(); } try { boolean success = result.getBoolean(\"success\"); if (success) { String url = result.getString(\"url\"); callback.onSuccess(result); } else { int code = result.getInt(\"code\"); String msg = result.optString(\"msg\"); callback.onFailure(code, msg); } } catch (JSONException e) { callback.onFailure( 2, null); } } else { callback.onFailure(httpCode, null); } } }); } Get download file address /api/file/getFileDownloadUrl.do HTTP method: GET URL parameters Parameter name Comment (description) fileId file id to be downloaded (required) string version The version number of the file (optional) number The return information is as follows {\"code\":0,\"success\":true,\"type\":\"File type\",\"url\":\"File download address\"} Get download address of multiple files /api/file/downloadMultiFiles.do HTTP method: GET URL parameters Parameter name Comment (description) fileIdArr is a string composed of the id of the file to be downloaded, separated by the symbol \"!\" (half width), for example, the download ids are 133 and 233. file, the value of fileIdArr is \"133!233\" string type PDF Page 13 The return information is as follows {\"code\":0,\"success\":true,\"type\":\"File type\",\"url\":\"File download address\"} The return value url is the download address of multiple files packaged. Get download file thumbnail address /api/file/downloadThumbnail.do HTTP method: GET URL parameters Parameter name Comment (description) fileId file id to be downloaded (required) string version The version number of the file (optional) number size is the size of the thumbnail to be displayed, taking the maximum value of width and height. The return information is as follows {\"code\":0,\"success\":true, \"url\":\"File download address\"} The return value url is the download address of multiple files packaged. Modify file information /nd /api/file/update file HTTP method: POST Modify file information POST request body parameters Parameter name Comment (description) file id file id (required) string name new file name (optional) string description file description (optional) string The return information is as follows {\"code\":0,\"success\":true} Modify file name /nd /api/file/rename HTTP method: POST Modify file information POST request body parameters Parameter name Comment (description) file id file id (required) string name new file name string The return information is as follows {\"code\":0,\"success\":true} PDF Page 14 Delete files (to recycle bin) /nd /api/file/remove file HTTP method: POST POST request body parameters Parameter name Comment (description) file ids[] target file id array (required) string[] The return information is as follows {\"code\":0,\"success\":true} Delete files (from Recycle Bin) /nd /api/file/remove from trash HTTP method: POST POST request body parameters Parameter name Comment (description) file ids[] target file id array (required) string[] The return information is as follows {\"code\":0,\"success\":true} Empty the Recycle Bin /nd /api/file/empty trash HTTP method: POST POST request body parameters Parameter name Description The return information is as follows {\"code\":0,\"success\":true} Recover files (from Recycle Bin) /nd /api/file/restore file HTTP method: POST POST request body parameters Parameter name Comment (description) file ids[] target file id array string[] restoreAll If file ids is not filled in, restoreAll is true to restore all files in the recycle bin, boolean The return information is as follows PDF Page 15 {\"code\":0,\"success\":true} Get all version information of the file /nd /api/file/versions HTTP method: GET URL parameters Parameter name Comment (description) file id target file id (required) string The return information is as follows {\"code\":0,\"versions\":[],\"success\":true} Set the current version of the file /nd /api/file/version HTTP method: POST POST request body parameters Parameter name Comment (description) file id target file id (required) string version version number (required) number The return information is as follows {\"code\":0,\"success\":true} Move files /nd /api/file/move HTTP method: POST POST request body parameters Parameter name Comment (description) file ids Target file id array to be moved (required) string target id The target folder id that needs to be moved to (required) string The return information is as follows {\"code\":0,\"success\":true} Copy files /nd /api/file/copy HTTP method: POST POST request body parameters Parameter name Comment (description) PDF Page 16 file ids Target file id array to be copied (required) string target id The id of the target folder to be copied to (required) string The return information is as follows { \"code\": 0, \"copyKey\": \"81427630 054a 11ef 8355 db93b4b1d006\", \"fileNum\": 10, \"success\": true} Copy file progress /nd /api/file/copy progress HTTP method: POST POST request body parameters Parameter name Comment (description) copyKey Check the copy progress copyKey is returned by the copy interface (required) string The return information is as follows { \"code\": 0, \"completed\": 10, \"total\": 10, \"result\": {}, \"success\": true} File log /nd /api/file/file logs HTTP method: GET GET request body parameters Parameter name Comment (description) file id target file id array (required) string startIndex gets the starting order of logs. Which log should be returned (optional) int defaults to 0. pageSize The number of items returned per page (optional) int type Log type (optional) int Default 0, view all records, 1 only view access records, 2 only view uploads and downloads, 3 only view anonymous users Users, 4 only view sharing and invitations, 5 only view deletion records userName A username (optional) string, returns the log of a certain user lang language (optional) default cn, string language of returned log cn (Chinese) en (English) The return information is as follows {\"code\":0,\"success\":true, \"logs\":[], \"total\":50} Set whether the user has permission to access the material library /nd /api/file/ set user access material library HTTP method: POST GET request body parameters Parameter name Comment (description) userId user's id array type [usrId1, userId2] (required) string can Whether it is accessible Numeric type (required) int Default 0, 0: Inaccessible, 1: Accessible The return information is as follows {\"code\":0,\"success\":true} PDF Page 17 Create material library classification /nd /api/file/create material class HTTP method: POST POST request body parameters Parameter name Comment (description) destDirFileId fileId of the destination folder (required) string name The name of the created category library (required) string accessType Classification visibility (optional) Defaults to public 0. 0: // public 1: // Need to apply 2: // Department is public 3: // Department application 4: // Confidential managerIds The id array type of the person in charge [usrId1,userId2] departmentIds Classification visibility limited department id of department (optional) Array type [departmentId1,departmentId2] The return information is as follows {\"code\":0, \"success\":true, \"materialClass\": {}} Create sub material library /nd /api/file/create material folder HTTP method: POST POST request body parameters Parameter name Comment (description) destDirFileId fileId of the destination folder (required) string name The name of the created category library (required) string accessType Classification visibility (optional) Defaults to public 0. 0: // public 1: // Need to apply 2: // Department is public 3: // Department application 4: // Confidential managerId The id of the person in charge (optional) string departmentIds Classification visibility limited department id of department (optional) Array type [departmentId1,departmentId2] assistantIds ID of the material library assistant (optional) Array type [usrId1,userId2] The return information is as follows {\"code\":0, \"success\":true, \"materialFolder\": {}} Shared file related API PDF Page 18 Get the sharing url of the file /nd/api/share/shareurl HTTP method: GET Get the sharing link of the file (open the sharing first, and then get the link) URL parameters Parameter name Comment (description) file id file id string is https Whether the returned share url protocol is https 0 means http, 1 means https, default 0 number Return field description {\"code\":0,\"url\":\"https://private.babel.cc/share.do?s=http://private.babel.cc/share.do?s=MjY2OTYzNTk3OTU2NzEzOTtXZWQgSnVsIDAxIDIwMj AgMTg6MzM6NTAgR01UKzA4MDAgKEhvbmcgS29uZyBTdGFuZGFyZCBUaW1lKQ%3D%3D\",\"success\":true} Get the sharing permission list /nd/api/share/share roles HTTP method: GET URL parameters Parameter name Comment (description) Return field description {\"code\":0,\"roles\":[],\"success\":true} Get the sharing roles that the user has permission to set for a single file /nd/api/share/share role forfile HTTP method: GET URL parameters Parameter name Comment (description) file id file id string Return field description {\"code\":0,\"roles\":[],\"success\":true} Create link to share /nd/api/share/open link share HTTP method: POST Open sharing and get a new sharing link. The previous link will be invalid. PDF Page 19 POST request body parameters Parameter name Comment (description) file id pre shared file id (required) string link role id shared role string is https Whether the returned share url protocol is https number anonymousVisit Whether to allow anonymous access, 1 means allowed, 0 means not allowed (optional, default is 1) number Return field description {\"code\":0,\"share url\":\"http://private.babel.cc/share.do?s=http://private.babel.cc/share.do?s=MjY2OTYzNTk3OTU2NzEzOTtXZWQgSnV sIDAxIDIwMjAgMTg6MzM6NTAgR01UKzA4MDAgKEhvbmcgS29uZyBTdGFuZGFyZCBUaW1lKQ%3D%3D\",\"password\":\"\",\"success\":tru e} Close link sharing /nd/api/share/close link share HTTP method: POST Close the shared link I opened POST request body parameters Parameter name Comment (description) file id shared file id (required) string Return field description {\"code\":0,\"success\":true} Set link sharing password /nd/api/share/set share password HTTP method: POST File link sharing is turned on, set a password for link sharing. POST request body parameters Parameter name Comment (description) file id pre shared file id (required) string password password for link sharing string is https Whether the returned share url protocol is https number Return field description {\"code\":0,\"success\":true, \"share url\": \"http://private.babel.cc/share.do?s=xxxxxxxxxxx\"} Invite people to share /nd/api/share/invite share HTTP method: POST PDF Page 20 You can invite certain people to access files based on the user's email or mobile phone POST request body parameters Parameter name Comment (description) file id file id (required) string share role ID of the shared permission (all the above people share this permission) (required) string emails[] email array string[] phones[] array of mobile phone numbers string[] Return field description {\"code\":0,\"success\":true} Get all sharing participants /nd/api/share/share participants HTTP method: GET URL parameters Parameter name Comment (description) file id file id (required) string Return field description {\"code\":0,\"users\":[],\"success\":true} Set permission roles for sharing participants /nd/api/share/set participant role HTTP method: POST POST request body parameters Parameter name Comment (description) file id file id (required) string babelshare id int (required) user id string role id int (required) role id string Return field description {\"code\":0,\"success\":true} Delete sharing participants /nd/api/file/remove share participant HTTP method: POST POST request body parameters Parameter name Comment (description) PDF Page 21 file id file id (required) string babelshare ids[] int (required) user id string Return field description {\"code\":0,\"success\":true} Reminder /nd/api/file/focus file HTTP method: POST POST request body parameters Parameter name Comment (description) file id file id (required) string user ids[] The id of the user to be reminded. This id should be selected among the file participants, otherwise the reminder will not work (required) string[] Return field description {\"code\":0,\"success\":true} Remove someone’s attention /nd/api/file/unfocus file HTTP method: POST POST request body parameters Parameter name Comment (description) file id file id (required) string user ids[] The id of the user to be reminded. This id should be selected among the file participants, otherwise the reminder will not work (required) string[] Return field description {\"code\":0,\"success\":true} Get the list of users following the file /nd/api/file/user focusfile HTTP method: GET URL parameters Parameter name Comment (description) file id file id (required) string Return field description {\"code\":0,\"users\":[],\"success\":true} Get the list of users who can follow the file, and mark the users who have followed the file /nd/api/file/user can focusfile PDF Page 22 HTTP method: GET URL parameters Parameter name Comment (description) file id file id (required) string Return field description Enterprise department related API Get current enterprise information /nd/api/enterprise/current HTTP method: GET URL parameters Parameter name Comment (description) None Return field description {\"code\":0,\"enterprise\":{},\"success\":true} Get information about all departments of the enterprise /nd/api/enterprise/departments HTTP method: GET URL parameters Parameter name Comment (description) None Return field description Attribute name type description departments [] array returns all department information tree {}json data returns the parent child structure information of the department code int successboolean Create enterprise department /nd/api/enterprise/create department HTTP method: POST PDF Page 23 POST request body parameters Parameter name Comment (description) parent dep parent department id, 0 means following department (required) string name department name (required) string description department description string Return field description Attribute name type description department {} json data structure code int successboolean Get the list of department roles /nd/api/enterprise/dep role HTTP method: GET URL parameters Parameter name Comment (description) Return field description Attribute name type description roles []array { id, filePermission,enterpriseId,filePermission,managerPermission, default,nameEn,name} code int successboolean Add department personnel /nd/api/enterprise/add dep mem HTTP method: POST POST request body parameters Parameter name Comment (description) department id department id (required) string user ids[] user list string[] role id The user's role in the department string PDF Page 24 Return field description Attribute name type description Delete department personnel /nd/api/enterprise/remove dep mem HTTP method: POST POST request body parameters Parameter name Comment (description) department id department id (required) string user ids[] Person’s id (required) string[] Return field description Attribute name type description Get information about your department /nd/api/enterprise/mydeparments HTTP method: GET URL parameters Parameter name Comment (description) None Return field description Attribute name type description departments [] array returns my department information code int successboolean Get department personnel /nd/api/enterprise/departmentmembers PDF Page 25 HTTP method: GET URL parameters Parameter name Comment (description) department id department id (required) string Return field description Attribute name type description users array: {id, name, avatrUrl,} Add company members /nd/api/enterprise/add ent mem HTTP method: POST POST request body parameters Parameter name Comment (description) email Email mailbox string password password string enterprise role enterprise member role, optional number department ids[] The user's department, optional string[] department roles[] Roles in the department, optional string[] sex 0 not set 1 male 2 female number name username string phone mobile phone number, optional string babelId employee ID, optional string spacelimit personal space limit, unit GB, 0 means no limit number can ownfile whether the user can have personal files, 1 use the overall enterprise settings, 0 no personal files, 1 have personal files number remarks user description, optional string join time The time when the user joined the enterprise, Unix time, unit number seconds password is md5 Whether the incoming password requires md5 encryption, 0 non md5 password, 1 md5 encrypted password number Update member information /api/updateUserInfo.do HTTP method: POST POST request body parameters Parameter name Comment (description) email email address (search keyword, required) string password password (change password, optional) string frozen 1 – means frozen, 0 – means unfrozen (freeze the account, optional) number password is md5 Whether the incoming password requires md5 encryption, 0 non md5 password, 1 md5 encrypted password number phone mobile phone number (optional) string PDF Page 26 Get enterprise member information /api/getEnterpriseMember.do HTTP method: GET URL parameters Parameter name Comment (description) email email address (search keyword) string phone mobile phone number (search keyword) string babelId employee number (search keyword) string email/phone/babelId you can choose one Return field description {\"code\":0,\"success\":true,\"user\":{}} Get all members of the company /nd/api/enterprise/enterprise members HTTP method: POST POST request body parameters Parameter name Comment (description) lang language type, cn Chinese, en English, optional options { departmentId: //Department id, if not filled in, it means all employees of the enterprise roleId: // Role id, if not filled in, there is no role limit \"userType\": 0, // 0 internal personnel, 1 external personnel \"keyName\": \"\", // Search keywords: name, mobile phone number, email address, if not filled in, it means all people \"startIndex\": 0, \"pageSize\": 20, status: // 0 all accounts, 1 deactivated accounts } Optional Return field description {\"code\":0,\"success\":true,\"members\":{},\"total\":xx} Get enterprise logs /nd/api/enterprise/enterprise logs HTTP method: POST POST request body parameters Parameter name Comment (description) department id department id, if not filled in, it will be the log of all departments string optional keyword related search keyword string optional PDF Page 27 startTime log starting time number optional endTime log end time number optional startIndex int optional pageSize int optional Return field description {\"code\":0,\"success\":true,\"logs\":{},\"total\":xx} Message Push API Make an announcement /nd/api/enterprise/broadcast HTTP method: POST POST request body parameters Parameter name Comment (description) title Announcement content string (required) string content content (required) string target users[] UserId array, if empty, it means all users will receive it, string[] target deps[] Target department, all members of this department and sub departments will receive notification, string[] Target users and target deps must be filled in at least 1 Return field description {\"code\":0,\"success\":true} Get published announcements /nd/api/enterprise/broadcast HTTP method: GET URL parameters Parameter name Comment (description) start index number pagesize number Return field description {\"code\":0,\"broadcasts\":[],\"total\":19,\"success\":true} Send department discussion /nd/api/file/send dep discussion HTTP method: POST PDF Page 28 POST request body parameters Parameter name Comment (description) dep id department id (required) string message information character (required) string json string, format {Type: “Text”, Body: “Hello” } Return field description {\"code\":0,\"messageId\":99,\"success\":true} Get department discussion /nd/api/file/dep discussion HTTP method: POST POST request body parameters Parameter name Comment (description) dep id department id (required) string pagesize page size string start id message id, only the messages before this message will be obtained, if it is empty, the latest message will be obtained string Return field description {\"msgArr\":[],\"gotMoreMessages\":1,\"code\":0,\"success\":true} Get enterprise logs /nd/api/enterprise/enterprise logs HTTP method: GET URL parameters Parameter name Comment (description) department id department id() string pagesize page size number, default value 1000 start index message starting position, number keyword log keyword string startTime start date: seconds number endTime expiration date seconds number Return field description {\"logs\":[],\"total\":0,\"code\":0,\"success\":true} total returns all those that meet the conditions (regardless of paging pageSize) PDF Page 29 4. JWT token login In private cloud deployment, the login method of jwt token can be enabled. In this case, the following url is allowed to directly enter the network disk system as a user without logging in. System: /account/tokenLogin.do Parameters: Parameter name Optional Description Optional value Default value userToken is required and contains the encrypted information of the logged in user (Constructor None See the instructions below for details) fileId optional The id of the file (folder) to be accessed, if not None If filled in, the user root directory will be opened. closeTitleBar optional Whether to close the title bar 1 Close 0 Do not close 0 disableEntMark Optional Whether to hide the corporate logo in the upper left corner 1 Hide 0 Do not hide 0 disableUserMark Optional Whether to hide the user settings entrance in the upper right corner 1 Hide 0 Do not hide 0 defaultLang optional Set the language used by the interface cn Chinese en English zh HK Traditional cn defaultClrTheme is optional and sets the interface color theme. normal is the standard mode, dark is the dark mode normal. For example, the following is the user root interface in English and dark mode with the user logo in the upper right corner hidden. /account/tokenLogin.do userToken=xxxxxxxxxxxxxxxx defaultClrTheme=dark defaultLang=en disableUserMark=1 Construction of userToken userToken is an encrypted string containing logged in user information. The encrypted information is a password created by JWT, a standard security mechanism for transmitting trusted data between two parties. The content of JWT encrypted user information JSONObject is as follows: { payload: { email: “xxx@xxx.com”/“135XXXXXXX”/“XXXX”} time: now } Note: email can be an email address, mobile phone number, or work number; The code is as follows: public static void main( String[] args ) { HashMap user = new HashMap (); user.put(\"email\", \"yuanchaozhao@qq.com\"); try { //token login String userToken = createTokenJWT(user); System.out.println(\" login token:\" + userToken); JSONObject parsed = parseTokenJWT(userToken); System.out.println(\" parsed:\" + parsed); System.out.println(\" Just put this token as a parameter in the url, such as: \"); System.out.println(\"/account/tokenLogin.do?userToken=\" + userToken); } catch (Exception e) { System.out.println(e.getMessage()); } } For other codes, please refer to the jwtToken generation code, which is provided in the authentication interface 2. Remarks: JWT is the abbreviation of JSON Web Tokens. It is a communication encryption and decryption mechanism that meets the industry standard RFC7519. Please refer to: https://jwt.io/ PDF Page 30 5. Appendix Common API call return status code Status code result code Code value Description 0 success 1 unknown error 2 parameter error 7 Not enough space 12 Prohibited user actions 13 invalid token the end" }, { "lang": "en", "slug": "developer-api-jwt-status", "title": "Messaging and Login API", "description": "Interface paths, methods, parameters and return fields of the messaging and login API.", "category": "Messages And Login API", "top_category": "API文档", "keywords": [ "API", "Messaging and Login API", "Developer" ], "url": "en/developer-api-jwt-status.html", "source": "content/en/developer-api-jwt-status.md", "summary": "Message and login API PDF Page 1 Enterprise Development API V6.6 Shanghai Huaqing Information Technology Co., Ltd. Jiang Dajun PDF Page 2 Directory 1. Obtain an enterprise development account .................................................................................................................................................................................4 2. Authentication API ................................................................................................................................................................................................. 6 Authentication interface one (login callback method) ..........................................................", "headings": [ { "level": 1, "title": "Message and login API", "id": "message-and-login-api" }, { "level": 3, "title": "PDF Page 1", "id": "pdf-page-1" }, { "level": 3, "title": "PDF Page 2", "id": "pdf-page-2" }, { "level": 3, "title": "PDF Page 3", "id": "pdf-page-3" }, { "level": 3, "title": "PDF Page 4", "id": "pdf-page-4" }, { "level": 2, "title": "1. Obtain an enterprise development account", "id": "1-obtain-an-enterprise-development-account" }, { "level": 3, "title": "PDF Page 5", "id": "pdf-page-5" }, { "level": 3, "title": "PDF Page 6", "id": "pdf-page-6" }, { "level": 2, "title": "2. Authentication API", "id": "2-authentication-api" }, { "level": 3, "title": "Authentication interface one (login callback method)", "id": "authentication-interface-one-login-callback-method" }, { "level": 3, "title": "PDF Page 7", "id": "pdf-page-7" }, { "level": 3, "title": "PDF Page 8", "id": "pdf-page-8" }, { "level": 3, "title": "Get token", "id": "get-token" }, { "level": 3, "title": "Refresh token", "id": "refresh-token" }, { "level": 2, "title": "3. File access API", "id": "3-file-access-api" }, { "level": 3, "title": "PDF Page 9", "id": "pdf-page-9" }, { "level": 3, "title": "Get file list", "id": "get-file-list" }, { "level": 3, "title": "Get file information", "id": "get-file-information" }, { "level": 3, "title": "PDF Page 10", "id": "pdf-page-10" }, { "level": 3, "title": "Create folder", "id": "create-folder" }, { "level": 3, "title": "Pre upload files", "id": "pre-upload-files" }, { "level": 3, "title": "PDF Page 11", "id": "pdf-page-11" }, { "level": 3, "title": "Upload files", "id": "upload-files" }, { "level": 3, "title": "PDF Page 12", "id": "pdf-page-12" }, { "level": 3, "title": "Get download file address", "id": "get-download-file-address" }, { "level": 3, "title": "Get download address of multiple files", "id": "get-download-address-of-multiple-files" }, { "level": 3, "title": "PDF Page 13", "id": "pdf-page-13" }, { "level": 3, "title": "Get download file thumbnail address", "id": "get-download-file-thumbnail-address" }, { "level": 3, "title": "Modify file information", "id": "modify-file-information" }, { "level": 3, "title": "Modify file information", "id": "modify-file-information-2" }, { "level": 3, "title": "Modify file name", "id": "modify-file-name" }, { "level": 3, "title": "Modify file information", "id": "modify-file-information-3" }, { "level": 3, "title": "PDF Page 14", "id": "pdf-page-14" }, { "level": 3, "title": "Delete files (to recycle bin)", "id": "delete-files-to-recycle-bin" }, { "level": 3, "title": "Delete files (from Recycle Bin)", "id": "delete-files-from-recycle-bin" }, { "level": 3, "title": "Empty the Recycle Bin", "id": "empty-the-recycle-bin" }, { "level": 3, "title": "Recover files (from Recycle Bin)", "id": "recover-files-from-recycle-bin" }, { "level": 3, "title": "PDF Page 15", "id": "pdf-page-15" }, { "level": 3, "title": "Get all version information of the file", "id": "get-all-version-information-of-the-file" }, { "level": 3, "title": "Set the current version of the file", "id": "set-the-current-version-of-the-file" }, { "level": 3, "title": "Move files", "id": "move-files" }, { "level": 3, "title": "Copy files", "id": "copy-files" }, { "level": 3, "title": "PDF Page 16", "id": "pdf-page-16" }, { "level": 3, "title": "Copy file progress", "id": "copy-file-progress" }, { "level": 3, "title": "File log", "id": "file-log" }, { "level": 3, "title": "Set whether the user has permission to access the material library", "id": "set-whether-the-user-has-permission-to-access-the-material-library" }, { "level": 3, "title": "PDF Page 17", "id": "pdf-page-17" }, { "level": 3, "title": "Create material library classification", "id": "create-material-library-classification" }, { "level": 3, "title": "Create sub material library", "id": "create-sub-material-library" }, { "level": 2, "title": "Shared file related API", "id": "shared-file-related-api" }, { "level": 3, "title": "PDF Page 18", "id": "pdf-page-18" }, { "level": 3, "title": "Get the sharing url of the file", "id": "get-the-sharing-url-of-the-file" }, { "level": 3, "title": "Get the sharing permission list", "id": "get-the-sharing-permission-list" }, { "level": 3, "title": "Get the sharing roles that the user has permission to set for a single file", "id": "get-the-sharing-roles-that-the-user-has-permission-to-set-for-a-single-file" }, { "level": 3, "title": "Create link to share", "id": "create-link-to-share" }, { "level": 3, "title": "PDF Page 19", "id": "pdf-page-19" }, { "level": 3, "title": "Close link sharing", "id": "close-link-sharing" }, { "level": 3, "title": "Set link sharing password", "id": "set-link-sharing-password" }, { "level": 3, "title": "Invite people to share", "id": "invite-people-to-share" }, { "level": 3, "title": "PDF Page 20", "id": "pdf-page-20" }, { "level": 3, "title": "Get all sharing participants", "id": "get-all-sharing-participants" }, { "level": 3, "title": "Set permission roles for sharing participants", "id": "set-permission-roles-for-sharing-participants" }, { "level": 3, "title": "Delete sharing participants", "id": "delete-sharing-participants" }, { "level": 3, "title": "PDF Page 21", "id": "pdf-page-21" }, { "level": 3, "title": "Reminder", "id": "reminder" }, { "level": 3, "title": "Remove someone’s attention", "id": "remove-someone-s-attention" }, { "level": 3, "title": "Get the list of users following the file", "id": "get-the-list-of-users-following-the-file" }, { "level": 3, "title": "Get the list of users who can follow the file, and mark the users who have followed the file", "id": "get-the-list-of-users-who-can-follow-the-file-and-mark-the-users-who-have-followed-the-file" }, { "level": 3, "title": "PDF Page 22", "id": "pdf-page-22" }, { "level": 2, "title": "Enterprise department related API", "id": "enterprise-department-related-api" }, { "level": 3, "title": "Get current enterprise information", "id": "get-current-enterprise-information" }, { "level": 3, "title": "Get information about all departments of the enterprise", "id": "get-information-about-all-departments-of-the-enterprise" }, { "level": 3, "title": "Create enterprise department", "id": "create-enterprise-department" }, { "level": 3, "title": "PDF Page 23", "id": "pdf-page-23" }, { "level": 3, "title": "Get the list of department roles", "id": "get-the-list-of-department-roles" }, { "level": 3, "title": "Add department personnel", "id": "add-department-personnel" }, { "level": 3, "title": "PDF Page 24", "id": "pdf-page-24" }, { "level": 3, "title": "Delete department personnel", "id": "delete-department-personnel" }, { "level": 3, "title": "Get information about your department", "id": "get-information-about-your-department" }, { "level": 3, "title": "Get department personnel", "id": "get-department-personnel" }, { "level": 3, "title": "PDF Page 25", "id": "pdf-page-25" }, { "level": 3, "title": "Add company members", "id": "add-company-members" }, { "level": 3, "title": "Update member information", "id": "update-member-information" }, { "level": 3, "title": "PDF Page 26", "id": "pdf-page-26" }, { "level": 3, "title": "Get enterprise member information", "id": "get-enterprise-member-information" }, { "level": 3, "title": "Get all members of the company", "id": "get-all-members-of-the-company" }, { "level": 3, "title": "Get enterprise logs", "id": "get-enterprise-logs" }, { "level": 3, "title": "PDF Page 27", "id": "pdf-page-27" }, { "level": 2, "title": "Message Push API", "id": "message-push-api" }, { "level": 3, "title": "Make an announcement", "id": "make-an-announcement" }, { "level": 3, "title": "Get published announcements", "id": "get-published-announcements" }, { "level": 3, "title": "Send department discussion", "id": "send-department-discussion" }, { "level": 3, "title": "PDF Page 28", "id": "pdf-page-28" }, { "level": 3, "title": "Get department discussion", "id": "get-department-discussion" }, { "level": 3, "title": "Get enterprise logs", "id": "get-enterprise-logs-2" }, { "level": 3, "title": "PDF Page 29", "id": "pdf-page-29" }, { "level": 2, "title": "4. JWT token login", "id": "4-jwt-token-login" }, { "level": 3, "title": "PDF Page 30", "id": "pdf-page-30" }, { "level": 2, "title": "5. Appendix Common API call return status code", "id": "5-appendix-common-api-call-return-status-code" }, { "level": 2, "title": "Status code result code", "id": "status-code-result-code" } ], "images": [], "text": "Message and login API PDF Page 1 Enterprise Development API V6.6 Shanghai Huaqing Information Technology Co., Ltd. Jiang Dajun PDF Page 2 Directory 1. Obtain an enterprise development account .................................................................................................................................................................................4 2. Authentication API ................................................................................................................................................................................................. 6 Authentication interface one (login callback method) ..................................................................................................................................................................6 Authentication interface two (login free method – JWT token method, in private cloud deployment, the jwt token login method needs to be enabled) .................................. 6 Get token .................................................................................................................................................................................................................8 Refresh token ..................................................................................................................................................................................................................8 3. File access API...................................................................................................................................................................................................... 8 Get file list ........................................................................................................................................................................................9 Get file information ........................................................................................................................................................................................9 Create a folder .................................................................................................................................................................................................10 Pre upload files ................................................................................................................................................................................................10 Uploading files .................................................................................................................................................................................................................11 Get the download file address .................................................................................................................................................................................12 Obtain the download address of multiple files .................................................................................................................................................................12 Get the download file thumbnail address .................................................................................................................................................................13 Modify file information .................................................................................................................................................................................13 Modify file name .................................................................................................................................................................................................13 Delete files (to Recycle Bin) ..................................................................................................................................................................................14 Deleting files (from Recycle Bin) ..................................................................................................................................................................14 Empty the Recycle Bin .................................................................................................................................................................................................14 Recovering files (from the Recycle Bin) ..................................................................................................................................................................14 Get all version information of a file .............................................................................................................................................................15 Current version of settings file .............................................................................................................................................................................15 Moving files .................................................................................................................................................................................................15 Copying files .................................................................................................................................................................................................15 Copying file progress ........................................................................................................................................................................................16 File Log .................................................................................................................................................................................................................16 Create library categories .................................................................................................................................................................................17 Create a sublibrary ............................................................................................................................................................................................17 Shared file related API ................................................................................................................................................................................. 17 Get the sharing url of the file ................................................................................................................................................................................. 18 Get the shared permission list .................................................................................................................................................................18 Obtain the sharing role that the user has permission to set for a single file .............................................................................................................................18 Create a link to share .................................................................................................................................................................................18 Turn off link sharing ........................................................................................................................................................................................19 Set link sharing password .................................................................................................................................................................................19 Invite people to share .................................................................................................................................................................19 Get all sharing participants .................................................................................................................................................................20 Set permission roles for sharing participants .............................................................................................................................................................20 Delete sharing participants ........................................................................................................................................................................20 Reminder...................................................................................................................................................................................................21 Remove someone from following .................................................................................................................................................................................21 Get the list of users following a file .................................................................................................................................................................21 Get the list of users who can follow the file and mark the users who have followed the file .............................................................................................21 Enterprise department related API ................................................................................................................................................................................. 22 Obtain current company information ..................................................................................................................................................................22 Obtain information from all departments of the enterprise ........................................................................................................................................................22 Creating a corporate division .................................................................................................................................................................................22 Get a list of department roles .................................................................................................................................................................................23 Add department personnel .................................................................................................................................................................................................23 Delete department personnel ................................................................................................................................................................................................24 Obtain information about your department .................................................................................................................................................................24 Obtain department personnel ................................................................................................................................................................................................24 Adding company members .................................................................................................................................................................................25 Update member information................................................................................................................................................................................25 Obtain enterprise member information .................................................................................................................................................................................26 Get all members of the company .................................................................................................................................................................................26 Obtain enterprise logs .................................................................................................................................................................................................26 Message push API................................................................................................................................................................................................................ 27 Announcement................................................................................................................................................................................................27 Get published announcements ................................................................................................................................................................................27 Send Department Discussion .................................................................................................................................................................................27 Get departmental discussions .................................................................................................................................................................................28 Obtain enterprise logs .................................................................................................................................................................................................28 4. JWT token login .................................................................................................................................................................................29 5. Appendix Common API call return status code ............................................................................................................................................................. 30 PDF Page 3 Status code result code .................................................................................................................................................................................................. 30 PDF Page 4 1. Obtain an enterprise development account Log in to the Babel Private Cloud Enterprise Management Backend and set up a developer account on the home page: After opening, fill in the callback function address: http://xxx.xxx.xxx.xxx/public/babelAuthResult.do After filling in and clicking OK, the developer ID (client id) and developer key (client secret) will be automatically generated: Note: jwtToken is the corresponding encryption key when generating jwtToken. PDF Page 5 PDF Page 6 2. Authentication API Authentication interface one (login callback method) /api/authorize.do HTTP request method GET URL parameters Parameter name Comment (description) response type must be code (required) string client id developer's id (required) string redirect uri callback function address, needs to be consistent with registration (required) string data: any data, string returned during callback For example: /api/authorize.do?response type=code&client id=xxxxx&redirect uri=http://xxx.xxx.xxx&data=xxx Access via browser Return results If the user is not logged in, it will jump to the login page. After logging in, if it is not authorized, it will 302 jump to the authorization page. If the user has been authorized, it will 302 jump to redirect uri and bring authorization code and data, similar to http://xxx.xxx.xxx?code=xxx&data=xxx The code is valid for 5 minutes. Authentication interface two (login free method – JWT token method. In private cloud deployment, the login method of jwt token needs to be enabled. formula) /api/authorizeByJWT.do HTTP request method GET URL parameters Parameter name Comment (description) response type must be code (required) string client id developer's id (required) string jwt token Jwt token, (required) string It is a string formed by encrypting {client id: xxxxxxx} email email (optional), enter the user's email address, log in as this user, leave it blank to log in as an enterprise administrator, string phone phone (optional), enter the user's mobile phone number and log in as this user. Leave it blank to log in as the enterprise administrator. string babelId babelId (optional), pass in the user's work ID, log in as this user, leave it blank to log in as the enterprise administrator, string PDF Page 7 For example: /api/authorizeByJWT.do?response type=code&client id=xxxxx&jwt token=xxx Note: When using this API, if you do not fill in email, phone, babelId, the system will automatically log in as an administrator, otherwise it will log in as the user corresponding to email, phone, babelId. Log in, the login interface will not be displayed to log in. Note (email, phone, babelId) only needs one of them. Return results { \"success\": true \"code\": \"xxxxxxxxxxxxxxxxxxxxxxxxxxx\", } jwt token is generated by writing your own program. The sample code is as follows: import java.util.Date; import java.util.HashMap; import java.util.Map; import javax.crypto.SecretKey; import javax.crypto.spec.SecretKeySpec; import io.jsonwebtoken.Claims; import io.jsonwebtoken.JwtBuilder; import io.jsonwebtoken.Jwts; import io.jsonwebtoken.SignatureAlgorithm; import net.sf.json.JSONObject; / Generate token used by standard jwt / public class JWT App { static String skey = \"babeldfdfer95840834 t8e 9 9 5934 5943 5886256\"; // The key is the jwtToken field filled in the developer account in the Babel backend. public static void main( String[] args ) { HashMap clientInfo = new HashMap (); clientInfo.put(\"client id\", \"7459492016147273\"); // is the client id in the developer account try { String token = createTokenJWT(clientInfo); System.out.println(\" login token:\" + token); String token1 = \"eyJhbGciOiJIUzI1NiJ9.eyJkdXJhdGlvbiI6NjAsInBheWxvYWQiOnsiY2xpZW50X2lk IjoiNzQ1OTQ5MjAxNjE0NzI3MyJ9LCJ0aW1lIjoxNjkxNDg4MzY4NTk0fQ.pRFCwXd2snMr IgFWOFwYbvyAeeNhoFINGk Wmv7d24g\"; JSONObject parsed = parseTokenJWT(token1); System.out.println(\" parsed:\" + parsed); System.out.println(\" Just put this token as a parameter in the url, such as: \"); } catch (Exception e) { System.out.println(e.getMessage()); } } public static String createTokenJWT(Map config) throws Exception { HashMap data = new HashMap (); data.put(\"time\", new Date().getTime()); data.put(\"duration\", 60); data.put(\"payload\", config); SignatureAlgorithm signatureAlgorithm = SignatureAlgorithm.HS256; SecretKey key = generalKey(); JwtBuilder builder = Jwts.builder() .setClaims(data) .signWith(signatureAlgorithm, key); System.out.println( \" builder : \" + builder); return builder.compact(); } public static JSONObject parseTokenJWT(String jwt) throws Exception { SecretKey key = generalKey(); Claims claims = Jwts.parser() .setSigningKey(key) .parseClaimsJws(jwt) .getBody(); System.out.println(\" claims:\" + claims.toString()); Long time = (Long)claims.get(\"time\"); long duration = (Integer)claims.get(\"duration\"); Long now = new Date().getTime(); if (now time 1000 duration) return null; // Tokens older than 10 minutes are invalid JSONObject obj = JSONObject.fromObject(claims.get(\"payload\")); return obj; } public static SecretKey generalKey(){ String stringKey = skey; byte[] encodedKey = stringKey.getBytes(); SecretKey key = new SecretKeySpec(encodedKey, 0, encodedKey.length, \"HmacSHA256\"); return key; } } PDF Page 8 Get token /api/token.do HTTP method: POST HTTP Header This interface uses Basic Auth to verify client information. The specific method is to add something like \"Authorization: Basic xxxxxxxxx\" in the header. Among them \"xxxxxxxxx\" is calculated from the developer id (client id) and developer secret key (client secret). The specific algorithm is Base64Encode(client id + \":\" + client secret) Base64Encode Choose your own tool for Base64 encoding URL parameters Parameter name Comment (description) grant type (required) must be authorization code string code (required) Authorization code, that is, the authorization code received by the callback address. The authorization code is valid for 5 minutes. It is used once, regardless of success. If it still fails, the authorization code will become invalid string For example: /api/token.do?grant type=authorization code&code=xxx&redirect uri=http://xxx.xxx.xxx Return results access token interface access token refresh token is used to refresh access token, valid for 30 days The validity time of expires in access token, unit is s Refresh token /api/refreshToken.do HTTP method: POST HTTP Header This interface uses Basic Auth to verify client information. The specific method is to add something like \"Authorization: Basic xxxxxxxxx\" in the header. Among them \"xxxxxxxxx\" is calculated through client id and client secret. The specific algorithm is Base64Encode(client id + \":\" + client secret) URL parameters Parameter name Comment (description) grant type (required) must be refresh token string refresh token (required) is the refresh token string obtained in interface 2 For example: /api/refreshToken.do?grant type=refresh token&refresh token=xxx Return results access token interface access identification, refresh token is used to refresh access token, valid for 30 days The validity time of expires in access token is 3600, the unit is s 3. File access API All interfaces need to carry access token in the HTTP header when accessing. For interfaces containing request parameters, usually some POST, PUT or DELETE interface, you also need to set Content Type to specify the format of the parameters. If you need to access different versions of the API, you need Specify a specific version on the request path. If you need to return a response body in a different format, you also need to set Accept. All parameters should be This should use utf 8 encoding. PDF Page 9 Headers: Authorization: stores access token, the format is: \"Bearer \" + access token. Content Type: Indicates the format of the request parameters. If it is a POST, PUT or DELETE request, you need to specify \"application/json\", I We currently do not support other request parameter formats, such as xml. If it is other types such as GET requests, it does not need to be set in the header. Content Type. Accept: used to specify the format of the response result and the version information of the api. Currently, only response in json format is supported, so in general Specify \"application/json\". If the interface access is successful, we will return a response in json format, and the HTTP status code is 200. All successful response responses All json will contain \"success: true\". The X Babel Version in the header of the response indicates the version number of the api accessed by this request. Get file list /nd/api/file/list dir HTTP method: GET URL parameters Parameter name Comment (description) parent id parent folder id (required) string When parent is 1, returns the contents of the corporate folder, 2 returns the contents of the personal folder, 3 returns my Project, 4 returns the share I added, and other fileId returns the contents of the normal folder. page size page size number page page number type type: divided into three types: 1 file, 2 folder, 0 all string Return field description Attribute name type description files array file information {fileId, name, …} total int total quantity page int page capacity success boolean gets the success mark code int returns error code 0 indicates success Get file information /nd/api/file/fileinfo HTTP method: GET URL parameters Parameter name Comment (description) id file id (required) string Return field description fileInfo information Attribute name type description file Object file information { id, name, …} PDF Page 10 success boolean gets the success mark code int returns error code 0 indicates success Create folder /nd/api/file/create folder HTTP method: POST POST request body parameters Parameter name Comment (description) parent id target folder id (required) string name file name (required) string Return field description Attribute name type description file Object file information { id, name, …} success boolean gets the success mark code int returns error code 0 indicates success Pre upload files Used to return the parameters (url, upload token) required when uploading files in the second step. /api/file/preUploadFile.do HTTP method: GET URL parameters Parameter name Comment (description) parent id target folder id (required) (you can ignore this when uploading in the root directory) string name file name (required) string file id When uploading a new version, you need to specify the new version of the file to upload (you can ignore this when uploading new files) string The correct return result is as follows {\"upload token\":\"92808ecfc2ac4e0ebc0b912edac3be4a\",\"url\":\"http://testdocument.babel.cc/api/file/uploadPdf.do\",\"su ccess\":true,\"code\":0} Return field description Attribute name type description url string This url can only be used once and is valid for 1 hour. Call this url to upload a file. After success, fileId, fileName, version, etc. will be returned. upload token string is used as a parameter of post when uploading files. PDF Page 11 Upload files Note that the URL of this API is returned by the pre upload interface. There is no specific URL here, just parameter description. https://xxx.xxx.xxx:xxx/api/file/uploadXXX.do (the specific URL is the URL returned by /api/file/preUploadFile.do in the previous section) POST POST request body parameters Parameter name Comment (description) file file binary data (upload data) Return value in upload token /api/file/preUploadFile.do request The return information is as follows {\"fileId\":\"7728538212615908\",\"version\":0,\"fileName\":\"mesos.pdf\",\"fileSize\":848854,\"success\":true,\"code\":0} Upload relevant code examples Add ‘com.squareup.okhttp3:okhttp:3.3.1’ package private void uploadFile(final String fileName, String parentId, final DaoCallback callback){ preUploadFile(fileName, parentId, new DaoCallback () { @Override public void onSuccess(JSONObject data) { int code = data.optInt(\"code\", 1); final String url = data.optString(\"url\", null); final String uploadToken = data.optString(\"upload token\"); if (code == 0) { // File file = new File(filePath); RequestBody fileContent = RequestBody.create(MultipartBody.FORM, file); RequestBody requestBody = new MultipartBody.Builder() .setType(MultipartBody.FORM) .addFormDataPart(\"file\", fileName, fileContent) .addFormDataPart(\"upload token\", uploadToken) .build(); Request request = new Request.Builder() .url(url) .post(requestBody) .build(); // Uploading takes a long time, so you need to set a longer timeout OkHttpClient okHttpClient = new OkHttpClient(); okHttpClient.newCall(request) .enqueue(new okhttp3.Callback() { @Override public void onFailure(okhttp3.Call call, IOException e) { callback.onFailure( 1, null); } @Override public void onResponse(okhttp3.Call call, okhttp3.Response response) throws IOException { int httpCode = response.code(); if (httpCode == 200) { try { JSONObject result = new JSONObject(response.body().string()); response.body().close(); boolean success = result.getBoolean(\"success\"); if (success) { callback.onSuccess(null); } else { int code = result.getInt(\"code\"); String msg = result.optString(\"msg\"); callback.onFailure(code, msg); } } catch (JSONException e) { callback.onFailure( 2, null); } } else { callback.onFailure(httpCode, null); } } }); } } @Override public void onFailure( int errorCode, String msg){ Log.e(\"FileTransfer\", \"filePreUpload failed errorCode=\" + errorCode); } }); } PDF Page 12 private void preUploadFile(String fileName, String parentId, final DaoCallback callback) { String preUploadUrl = \"http://private.babel.cc:80/api/file/preUploadFile.do?name=1234.jpg&parent id=0\"; // Pass in the corresponding parameters name, parent id String authorization = \"Bearer d48d0a0e253c4a2985d8c5653f717d71\"; //Generate according to the instructions Request request = new Request.Builder().url(preUploadUrl) .addHeader(\"Authorization\", authorization) .build(); OkHttpClient okHttpClient = new OkHttpClient(); okHttpClient.newCall(request).enqueue(new okhttp3.Callback() { @Override public void onFailure(okhttp3.Call call, IOException e) { Log.d(\"\", \"\"); } @Override public void onResponse(okhttp3.Call call, okhttp3.Response response) throws IOException { Log.d(\"\",\"\"); int httpCode = response.code(); if (httpCode == 200) { JSONObject result = null; try { result = new JSONObject(response.body().string()); } catch (JSONException e) { e.printStackTrace(); } try { boolean success = result.getBoolean(\"success\"); if (success) { String url = result.getString(\"url\"); callback.onSuccess(result); } else { int code = result.getInt(\"code\"); String msg = result.optString(\"msg\"); callback.onFailure(code, msg); } } catch (JSONException e) { callback.onFailure( 2, null); } } else { callback.onFailure(httpCode, null); } } }); } Get download file address /api/file/getFileDownloadUrl.do HTTP method: GET URL parameters Parameter name Comment (description) fileId file id to be downloaded (required) string version The version number of the file (optional) number The return information is as follows {\"code\":0,\"success\":true,\"type\":\"File type\",\"url\":\"File download address\"} Get download address of multiple files /api/file/downloadMultiFiles.do HTTP method: GET URL parameters Parameter name Comment (description) fileIdArr is a string composed of the id of the file to be downloaded, separated by the symbol \"!\" (half width), for example, the download ids are 133 and 233. file, the value of fileIdArr is \"133!233\" string type PDF Page 13 The return information is as follows {\"code\":0,\"success\":true,\"type\":\"File type\",\"url\":\"File download address\"} The return value url is the download address of multiple files packaged. Get download file thumbnail address /api/file/downloadThumbnail.do HTTP method: GET URL parameters Parameter name Comment (description) fileId file id to be downloaded (required) string version The version number of the file (optional) number size is the size of the thumbnail to be displayed, taking the maximum value of width and height. The return information is as follows {\"code\":0,\"success\":true, \"url\":\"File download address\"} The return value url is the download address of multiple files packaged. Modify file information /nd /api/file/update file HTTP method: POST Modify file information POST request body parameters Parameter name Comment (description) file id file id (required) string name new file name (optional) string description file description (optional) string The return information is as follows {\"code\":0,\"success\":true} Modify file name /nd /api/file/rename HTTP method: POST Modify file information POST request body parameters Parameter name Comment (description) file id file id (required) string name new file name string The return information is as follows {\"code\":0,\"success\":true} PDF Page 14 Delete files (to recycle bin) /nd /api/file/remove file HTTP method: POST POST request body parameters Parameter name Comment (description) file ids[] target file id array (required) string[] The return information is as follows {\"code\":0,\"success\":true} Delete files (from Recycle Bin) /nd /api/file/remove from trash HTTP method: POST POST request body parameters Parameter name Comment (description) file ids[] target file id array (required) string[] The return information is as follows {\"code\":0,\"success\":true} Empty the Recycle Bin /nd /api/file/empty trash HTTP method: POST POST request body parameters Parameter name Description The return information is as follows {\"code\":0,\"success\":true} Recover files (from Recycle Bin) /nd /api/file/restore file HTTP method: POST POST request body parameters Parameter name Comment (description) file ids[] target file id array string[] restoreAll If file ids is not filled in, restoreAll is true to restore all files in the recycle bin, boolean The return information is as follows PDF Page 15 {\"code\":0,\"success\":true} Get all version information of the file /nd /api/file/versions HTTP method: GET URL parameters Parameter name Comment (description) file id target file id (required) string The return information is as follows {\"code\":0,\"versions\":[],\"success\":true} Set the current version of the file /nd /api/file/version HTTP method: POST POST request body parameters Parameter name Comment (description) file id target file id (required) string version version number (required) number The return information is as follows {\"code\":0,\"success\":true} Move files /nd /api/file/move HTTP method: POST POST request body parameters Parameter name Comment (description) file ids Target file id array to be moved (required) string target id The target folder id that needs to be moved to (required) string The return information is as follows {\"code\":0,\"success\":true} Copy files /nd /api/file/copy HTTP method: POST POST request body parameters Parameter name Comment (description) PDF Page 16 file ids Target file id array to be copied (required) string target id The id of the target folder to be copied to (required) string The return information is as follows { \"code\": 0, \"copyKey\": \"81427630 054a 11ef 8355 db93b4b1d006\", \"fileNum\": 10, \"success\": true} Copy file progress /nd /api/file/copy progress HTTP method: POST POST request body parameters Parameter name Comment (description) copyKey Check the copy progress copyKey is returned by the copy interface (required) string The return information is as follows { \"code\": 0, \"completed\": 10, \"total\": 10, \"result\": {}, \"success\": true} File log /nd /api/file/file logs HTTP method: GET GET request body parameters Parameter name Comment (description) file id target file id array (required) string startIndex gets the starting order of logs. Which log should be returned (optional) int defaults to 0. pageSize The number of items returned per page (optional) int type Log type (optional) int Default 0, view all records, 1 only view access records, 2 only view uploads and downloads, 3 only view anonymous users Users, 4 only view sharing and invitations, 5 only view deletion records userName A username (optional) string, returns the log of a certain user lang language (optional) default cn, string language of returned log cn (Chinese) en (English) The return information is as follows {\"code\":0,\"success\":true, \"logs\":[], \"total\":50} Set whether the user has permission to access the material library /nd /api/file/ set user access material library HTTP method: POST GET request body parameters Parameter name Comment (description) userId user's id array type [usrId1, userId2] (required) string can Whether it is accessible Numeric type (required) int Default 0, 0: Inaccessible, 1: Accessible The return information is as follows {\"code\":0,\"success\":true} PDF Page 17 Create material library classification /nd /api/file/create material class HTTP method: POST POST request body parameters Parameter name Comment (description) destDirFileId fileId of the destination folder (required) string name The name of the created category library (required) string accessType Classification visibility (optional) Defaults to public 0. 0: // public 1: // Need to apply 2: // Department is public 3: // Department application 4: // Confidential managerIds The id array type of the person in charge [usrId1,userId2] departmentIds Classification visibility limited department id of department (optional) Array type [departmentId1,departmentId2] The return information is as follows {\"code\":0, \"success\":true, \"materialClass\": {}} Create sub material library /nd /api/file/create material folder HTTP method: POST POST request body parameters Parameter name Comment (description) destDirFileId fileId of the destination folder (required) string name The name of the created category library (required) string accessType Classification visibility (optional) Defaults to public 0. 0: // public 1: // Need to apply 2: // Department is public 3: // Department application 4: // Confidential managerId The id of the person in charge (optional) string departmentIds Classification visibility limited department id of department (optional) Array type [departmentId1,departmentId2] assistantIds ID of the material library assistant (optional) Array type [usrId1,userId2] The return information is as follows {\"code\":0, \"success\":true, \"materialFolder\": {}} Shared file related API PDF Page 18 Get the sharing url of the file /nd/api/share/shareurl HTTP method: GET Get the sharing link of the file (open the sharing first, and then get the link) URL parameters Parameter name Comment (description) file id file id string is https Whether the returned share url protocol is https 0 means http, 1 means https, default 0 number Return field description {\"code\":0,\"url\":\"https://private.babel.cc/share.do?s=http://private.babel.cc/share.do?s=MjY2OTYzNTk3OTU2NzEzOTtXZWQgSnVsIDAxIDIwMj AgMTg6MzM6NTAgR01UKzA4MDAgKEhvbmcgS29uZyBTdGFuZGFyZCBUaW1lKQ%3D%3D\",\"success\":true} Get the sharing permission list /nd/api/share/share roles HTTP method: GET URL parameters Parameter name Comment (description) Return field description {\"code\":0,\"roles\":[],\"success\":true} Get the sharing roles that the user has permission to set for a single file /nd/api/share/share role forfile HTTP method: GET URL parameters Parameter name Comment (description) file id file id string Return field description {\"code\":0,\"roles\":[],\"success\":true} Create link to share /nd/api/share/open link share HTTP method: POST Open sharing and get a new sharing link. The previous link will be invalid. PDF Page 19 POST request body parameters Parameter name Comment (description) file id pre shared file id (required) string link role id shared role string is https Whether the returned share url protocol is https number anonymousVisit Whether to allow anonymous access, 1 means allowed, 0 means not allowed (optional, default is 1) number Return field description {\"code\":0,\"share url\":\"http://private.babel.cc/share.do?s=http://private.babel.cc/share.do?s=MjY2OTYzNTk3OTU2NzEzOTtXZWQgSnV sIDAxIDIwMjAgMTg6MzM6NTAgR01UKzA4MDAgKEhvbmcgS29uZyBTdGFuZGFyZCBUaW1lKQ%3D%3D\",\"password\":\"\",\"success\":tru e} Close link sharing /nd/api/share/close link share HTTP method: POST Close the shared link I opened POST request body parameters Parameter name Comment (description) file id shared file id (required) string Return field description {\"code\":0,\"success\":true} Set link sharing password /nd/api/share/set share password HTTP method: POST File link sharing is turned on, set a password for link sharing. POST request body parameters Parameter name Comment (description) file id pre shared file id (required) string password password for link sharing string is https Whether the returned share url protocol is https number Return field description {\"code\":0,\"success\":true, \"share url\": \"http://private.babel.cc/share.do?s=xxxxxxxxxxx\"} Invite people to share /nd/api/share/invite share HTTP method: POST PDF Page 20 You can invite certain people to access files based on the user's email or mobile phone POST request body parameters Parameter name Comment (description) file id file id (required) string share role ID of the shared permission (all the above people share this permission) (required) string emails[] email array string[] phones[] array of mobile phone numbers string[] Return field description {\"code\":0,\"success\":true} Get all sharing participants /nd/api/share/share participants HTTP method: GET URL parameters Parameter name Comment (description) file id file id (required) string Return field description {\"code\":0,\"users\":[],\"success\":true} Set permission roles for sharing participants /nd/api/share/set participant role HTTP method: POST POST request body parameters Parameter name Comment (description) file id file id (required) string babelshare id int (required) user id string role id int (required) role id string Return field description {\"code\":0,\"success\":true} Delete sharing participants /nd/api/file/remove share participant HTTP method: POST POST request body parameters Parameter name Comment (description) PDF Page 21 file id file id (required) string babelshare ids[] int (required) user id string Return field description {\"code\":0,\"success\":true} Reminder /nd/api/file/focus file HTTP method: POST POST request body parameters Parameter name Comment (description) file id file id (required) string user ids[] The id of the user to be reminded. This id should be selected among the file participants, otherwise the reminder will not work (required) string[] Return field description {\"code\":0,\"success\":true} Remove someone’s attention /nd/api/file/unfocus file HTTP method: POST POST request body parameters Parameter name Comment (description) file id file id (required) string user ids[] The id of the user to be reminded. This id should be selected among the file participants, otherwise the reminder will not work (required) string[] Return field description {\"code\":0,\"success\":true} Get the list of users following the file /nd/api/file/user focusfile HTTP method: GET URL parameters Parameter name Comment (description) file id file id (required) string Return field description {\"code\":0,\"users\":[],\"success\":true} Get the list of users who can follow the file, and mark the users who have followed the file /nd/api/file/user can focusfile PDF Page 22 HTTP method: GET URL parameters Parameter name Comment (description) file id file id (required) string Return field description Enterprise department related API Get current enterprise information /nd/api/enterprise/current HTTP method: GET URL parameters Parameter name Comment (description) None Return field description {\"code\":0,\"enterprise\":{},\"success\":true} Get information about all departments of the enterprise /nd/api/enterprise/departments HTTP method: GET URL parameters Parameter name Comment (description) None Return field description Attribute name type description departments [] array returns all department information tree {}json data returns the parent child structure information of the department code int successboolean Create enterprise department /nd/api/enterprise/create department HTTP method: POST PDF Page 23 POST request body parameters Parameter name Comment (description) parent dep parent department id, 0 means following department (required) string name department name (required) string description department description string Return field description Attribute name type description department {} json data structure code int successboolean Get the list of department roles /nd/api/enterprise/dep role HTTP method: GET URL parameters Parameter name Comment (description) Return field description Attribute name type description roles []array { id, filePermission,enterpriseId,filePermission,managerPermission, default,nameEn,name} code int successboolean Add department personnel /nd/api/enterprise/add dep mem HTTP method: POST POST request body parameters Parameter name Comment (description) department id department id (required) string user ids[] user list string[] role id The user's role in the department string PDF Page 24 Return field description Attribute name type description Delete department personnel /nd/api/enterprise/remove dep mem HTTP method: POST POST request body parameters Parameter name Comment (description) department id department id (required) string user ids[] Person’s id (required) string[] Return field description Attribute name type description Get information about your department /nd/api/enterprise/mydeparments HTTP method: GET URL parameters Parameter name Comment (description) None Return field description Attribute name type description departments [] array returns my department information code int successboolean Get department personnel /nd/api/enterprise/departmentmembers PDF Page 25 HTTP method: GET URL parameters Parameter name Comment (description) department id department id (required) string Return field description Attribute name type description users array: {id, name, avatrUrl,} Add company members /nd/api/enterprise/add ent mem HTTP method: POST POST request body parameters Parameter name Comment (description) email Email mailbox string password password string enterprise role enterprise member role, optional number department ids[] The user's department, optional string[] department roles[] Roles in the department, optional string[] sex 0 not set 1 male 2 female number name username string phone mobile phone number, optional string babelId employee ID, optional string spacelimit personal space limit, unit GB, 0 means no limit number can ownfile whether the user can have personal files, 1 use the overall enterprise settings, 0 no personal files, 1 have personal files number remarks user description, optional string join time The time when the user joined the enterprise, Unix time, unit number seconds password is md5 Whether the incoming password requires md5 encryption, 0 non md5 password, 1 md5 encrypted password number Update member information /api/updateUserInfo.do HTTP method: POST POST request body parameters Parameter name Comment (description) email email address (search keyword, required) string password password (change password, optional) string frozen 1 – means frozen, 0 – means unfrozen (freeze the account, optional) number password is md5 Whether the incoming password requires md5 encryption, 0 non md5 password, 1 md5 encrypted password number phone mobile phone number (optional) string PDF Page 26 Get enterprise member information /api/getEnterpriseMember.do HTTP method: GET URL parameters Parameter name Comment (description) email email address (search keyword) string phone mobile phone number (search keyword) string babelId employee number (search keyword) string email/phone/babelId you can choose one Return field description {\"code\":0,\"success\":true,\"user\":{}} Get all members of the company /nd/api/enterprise/enterprise members HTTP method: POST POST request body parameters Parameter name Comment (description) lang language type, cn Chinese, en English, optional options { departmentId: //Department id, if not filled in, it means all employees of the enterprise roleId: // Role id, if not filled in, there is no role limit \"userType\": 0, // 0 internal personnel, 1 external personnel \"keyName\": \"\", // Search keywords: name, mobile phone number, email address, if not filled in, it means all people \"startIndex\": 0, \"pageSize\": 20, status: // 0 all accounts, 1 deactivated accounts } Optional Return field description {\"code\":0,\"success\":true,\"members\":{},\"total\":xx} Get enterprise logs /nd/api/enterprise/enterprise logs HTTP method: POST POST request body parameters Parameter name Comment (description) department id department id, if not filled in, it will be the log of all departments string optional keyword related search keyword string optional PDF Page 27 startTime log starting time number optional endTime log end time number optional startIndex int optional pageSize int optional Return field description {\"code\":0,\"success\":true,\"logs\":{},\"total\":xx} Message Push API Make an announcement /nd/api/enterprise/broadcast HTTP method: POST POST request body parameters Parameter name Comment (description) title Announcement content string (required) string content content (required) string target users[] UserId array, if empty, it means all users will receive it, string[] target deps[] Target department, all members of this department and sub departments will receive notification, string[] Target users and target deps must be filled in at least 1 Return field description {\"code\":0,\"success\":true} Get published announcements /nd/api/enterprise/broadcast HTTP method: GET URL parameters Parameter name Comment (description) start index number pagesize number Return field description {\"code\":0,\"broadcasts\":[],\"total\":19,\"success\":true} Send department discussion /nd/api/file/send dep discussion HTTP method: POST PDF Page 28 POST request body parameters Parameter name Comment (description) dep id department id (required) string message information character (required) string json string, format {Type: “Text”, Body: “Hello” } Return field description {\"code\":0,\"messageId\":99,\"success\":true} Get department discussion /nd/api/file/dep discussion HTTP method: POST POST request body parameters Parameter name Comment (description) dep id department id (required) string pagesize page size string start id message id, only the messages before this message will be obtained, if it is empty, the latest message will be obtained string Return field description {\"msgArr\":[],\"gotMoreMessages\":1,\"code\":0,\"success\":true} Get enterprise logs /nd/api/enterprise/enterprise logs HTTP method: GET URL parameters Parameter name Comment (description) department id department id() string pagesize page size number, default value 1000 start index message starting position, number keyword log keyword string startTime start date: seconds number endTime expiration date seconds number Return field description {\"logs\":[],\"total\":0,\"code\":0,\"success\":true} total returns all those that meet the conditions (regardless of paging pageSize) PDF Page 29 4. JWT token login In private cloud deployment, the login method of jwt token can be enabled. In this case, the following url is allowed to directly enter the network disk system as a user without logging in. System: /account/tokenLogin.do Parameters: Parameter name Optional Description Optional value Default value userToken is required and contains the encrypted information of the logged in user (Constructor None See the instructions below for details) fileId optional The id of the file (folder) to be accessed, if not None If filled in, the user root directory will be opened. closeTitleBar optional Whether to close the title bar 1 Close 0 Do not close 0 disableEntMark Optional Whether to hide the corporate logo in the upper left corner 1 Hide 0 Do not hide 0 disableUserMark Optional Whether to hide the user settings entrance in the upper right corner 1 Hide 0 Do not hide 0 defaultLang optional Set the language used by the interface cn Chinese en English zh HK Traditional cn defaultClrTheme is optional and sets the interface color theme. normal is the standard mode, dark is the dark mode normal. For example, the following is the user root interface in English and dark mode with the user logo in the upper right corner hidden. /account/tokenLogin.do userToken=xxxxxxxxxxxxxxxx defaultClrTheme=dark defaultLang=en disableUserMark=1 Construction of userToken userToken is an encrypted string containing logged in user information. The encrypted information is a password created by JWT, a standard security mechanism for transmitting trusted data between two parties. The content of JWT encrypted user information JSONObject is as follows: { payload: { email: “xxx@xxx.com”/“135XXXXXXX”/“XXXX”} time: now } Note: email can be an email address, mobile phone number, or work number; The code is as follows: public static void main( String[] args ) { HashMap user = new HashMap (); user.put(\"email\", \"yuanchaozhao@qq.com\"); try { //token login String userToken = createTokenJWT(user); System.out.println(\" login token:\" + userToken); JSONObject parsed = parseTokenJWT(userToken); System.out.println(\" parsed:\" + parsed); System.out.println(\" Just put this token as a parameter in the url, such as: \"); System.out.println(\"/account/tokenLogin.do?userToken=\" + userToken); } catch (Exception e) { System.out.println(e.getMessage()); } } For other codes, please refer to the jwtToken generation code, which is provided in the authentication interface 2. Remarks: JWT is the abbreviation of JSON Web Tokens. It is a communication encryption and decryption mechanism that meets the industry standard RFC7519. Please refer to: https://jwt.io/ PDF Page 30 5. Appendix Common API call return status code Status code result code Code value Description 0 success 1 unknown error 2 parameter error 7 Not enough space 12 Prohibited user actions 13 invalid token the end" }, { "lang": "en", "slug": "api-get-api-authorize-do", "title": "Authentication interface one (login callback method)", "description": "GET /api/authorize.do: Authentication interface one (login callback method) Interface description, including path, method, parameters and return information.", "category": "Authentication API", "top_category": "API文档", "keywords": [ "API", "Authentication interface one (login callback method)", "/api/authorize.do" ], "url": "en/api-get-api-authorize-do.html", "source": "content/en/api-get-api-authorize-do.md", "summary": "Authentication interface one (login callback method) Properties Values HTTP methods GET Interface path /api/authorize.do Category Authentication API Interface description Interface path: /api/authorize.do HTTP method: GET HTTP request method GET URL parameters Parameter name Comment (description) response type must be code (required) string client id developer's id (required) string redirect uri callback function address, needs to be consistent with registration (required) string data: any data, string returned during callback For example: /api/authorize.do?response type=code&client id=xxxxx&redirect uri=http://xxx.xxx.xxx&data=xxx Access via browser Return results If the user is not logged ", "headings": [ { "level": 1, "title": "Authentication interface one (login callback method)", "id": "authentication-interface-one-login-callback-method" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Authentication interface one (login callback method) Properties Values HTTP methods GET Interface path /api/authorize.do Category Authentication API Interface description Interface path: /api/authorize.do HTTP method: GET HTTP request method GET URL parameters Parameter name Comment (description) response type must be code (required) string client id developer's id (required) string redirect uri callback function address, needs to be consistent with registration (required) string data: any data, string returned during callback For example: /api/authorize.do?response type=code&client id=xxxxx&redirect uri=http://xxx.xxx.xxx&data=xxx Access via browser Return results If the user is not logged in, it will jump to the login page. After logging in, if it is not authorized, it will 302 jump to the authorization page. If the user has been authorized, it will 302 jump to redirect uri and bring authorization code and data, similar to http://xxx.xxx.xxx?code=xxx&data=xxx The code is valid for 5 minutes. Authentication interface two (login free method – JWT token method. In private cloud deployment, the login method of jwt token needs to be enabled. formula) Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Authentication API." }, { "lang": "en", "slug": "api-get-api-authorizebyjwt-do", "title": "Authentication interface two (login-free JWT token method)", "description": "GET /api/authorizeByJWT.do: Authentication interface two (login-free JWT token method) interface description, including path, method, parameters and return information.", "category": "Authentication API", "top_category": "API文档", "keywords": [ "API", "Authentication interface two (login-free JWT token method)", "/api/authorizeByJWT.do" ], "url": "en/api-get-api-authorizebyjwt-do.html", "source": "content/en/api-get-api-authorizebyjwt-do.md", "summary": "Authentication interface two (login free JWT token method) Properties Values HTTP methods GET Interface path /api/authorizeByJWT.do Category Authentication API Interface description Interface path: /api/authorizeByJWT.do HTTP method: GET Section to which it belongs: Authentication interface one (login callback method) HTTP request method GET URL parameters Parameter name Comment (description) response type must be code (required) string client id developer's id (required) string jwt token Jwt token, (required) string It is a string formed by encrypting {client id: xxxxxxx} email email (optional), enter the user's email address, log in as this user, leave it blank to log in as an enterprise a", "headings": [ { "level": 1, "title": "Authentication interface two (login free JWT token method)", "id": "authentication-interface-two-login-free-jwt-token-method" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Authentication interface two (login free JWT token method) Properties Values HTTP methods GET Interface path /api/authorizeByJWT.do Category Authentication API Interface description Interface path: /api/authorizeByJWT.do HTTP method: GET Section to which it belongs: Authentication interface one (login callback method) HTTP request method GET URL parameters Parameter name Comment (description) response type must be code (required) string client id developer's id (required) string jwt token Jwt token, (required) string It is a string formed by encrypting {client id: xxxxxxx} email email (optional), enter the user's email address, log in as this user, leave it blank to log in as an enterprise administrator, string phone phone (optional), enter the user's mobile phone number and log in as this user. Leave it blank to log in as the enterprise administrator. string babelId babelId (optional), pass in the user's work ID, log in as this user, leave it blank to log in as the enterprise administrator, string Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Authentication API." }, { "lang": "en", "slug": "api-post-api-token-do", "title": "Get token", "description": "POST /api/token.do: Get the token interface description, including path, method, parameters and return information.", "category": "Authentication API", "top_category": "API文档", "keywords": [ "API", "Get token", "/api/token.do" ], "url": "en/api-post-api-token-do.html", "source": "content/en/api-post-api-token-do.md", "summary": "Get token Properties Values HTTP method POST Interface path /api/token.do Category Authentication API Interface description Interface path: /api/token.do HTTP method: POST HTTP method: POST HTTP Header This interface uses Basic Auth to verify client information. The specific method is to add something like \"Authorization: Basic xxxxxxxxx\" in the header. Among them \"xxxxxxxxx\" is calculated from the developer id (client id) and developer secret key (client secret). The specific algorithm is Base64Encode(client id + \":\" + client secret) Base64Encode Choose your own tool for Base64 encoding URL parameters Parameter name Comment (description) grant type (required) must be authorization code stri", "headings": [ { "level": 1, "title": "Get token", "id": "get-token" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Get token Properties Values HTTP method POST Interface path /api/token.do Category Authentication API Interface description Interface path: /api/token.do HTTP method: POST HTTP method: POST HTTP Header This interface uses Basic Auth to verify client information. The specific method is to add something like \"Authorization: Basic xxxxxxxxx\" in the header. Among them \"xxxxxxxxx\" is calculated from the developer id (client id) and developer secret key (client secret). The specific algorithm is Base64Encode(client id + \":\" + client secret) Base64Encode Choose your own tool for Base64 encoding URL parameters Parameter name Comment (description) grant type (required) must be authorization code string code (required) Authorization code, that is, the authorization code received by the callback address. The authorization code is valid for 5 minutes. It is used once, regardless of success. If it still fails, the authorization code will become invalid string For example: /api/token.do?grant type=authorization code&code=xxx&redirect uri=http://xxx.xxx.xxx Return results access token interface access token refresh token is used to refresh access token, valid for 30 days The validity time of expires in access token, unit is s Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Authentication API." }, { "lang": "en", "slug": "api-post-api-refreshtoken-do", "title": "refresh token", "description": "POST /api/refreshToken.do: Refresh token interface description, including path, method, parameters and return information.", "category": "Authentication API", "top_category": "API文档", "keywords": [ "API", "refresh token", "/api/refreshToken.do" ], "url": "en/api-post-api-refreshtoken-do.html", "source": "content/en/api-post-api-refreshtoken-do.md", "summary": "Refresh token Properties Values HTTP method POST Interface path /api/refreshToken.do Category Authentication API Interface description Interface path: /api/refreshToken.do HTTP method: POST HTTP method: POST HTTP Header This interface uses Basic Auth to verify client information. The specific method is to add something like \"Authorization: Basic xxxxxxxxx\" in the header. Among them \"xxxxxxxxx\" is calculated through client id and client secret. The specific algorithm is Base64Encode(client id + \":\" + client secret) URL parameters Parameter name Comment (description) grant type (required) must be refresh token string refresh token (required) is the refresh token string obtained in interface 2 ", "headings": [ { "level": 1, "title": "Refresh token", "id": "refresh-token" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "3. File access API", "id": "3-file-access-api" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Refresh token Properties Values HTTP method POST Interface path /api/refreshToken.do Category Authentication API Interface description Interface path: /api/refreshToken.do HTTP method: POST HTTP method: POST HTTP Header This interface uses Basic Auth to verify client information. The specific method is to add something like \"Authorization: Basic xxxxxxxxx\" in the header. Among them \"xxxxxxxxx\" is calculated through client id and client secret. The specific algorithm is Base64Encode(client id + \":\" + client secret) URL parameters Parameter name Comment (description) grant type (required) must be refresh token string refresh token (required) is the refresh token string obtained in interface 2 For example: /api/refreshToken.do?grant type=refresh token&refresh token=xxx Return results access token interface access identification, refresh token is used to refresh access token, valid for 30 days The validity time of expires in access token is 3600, the unit is s 3. File access API All interfaces need to carry access token in the HTTP header when accessing. For interfaces containing request parameters, usually some POST, PUT or DELETE interface, you also need to set Content Type to specify the format of the parameters. If you need to access different versions of the API, you need Specify a specific version on the request path. If you need to return a response body in a different format, you also need to set Accept. All parameters should be This should use utf 8 encoding. Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Authentication API." }, { "lang": "en", "slug": "api-get-nd-api-file-list-dir", "title": "Get file list", "description": "GET /nd/api/file/list_dir: Get the file list interface description, including path, method, parameters and return information.", "category": "File API", "top_category": "API文档", "keywords": [ "API", "Get file list", "/nd/api/file/list_dir" ], "url": "en/api-get-nd-api-file-list-dir.html", "source": "content/en/api-get-nd-api-file-list-dir.md", "summary": "Get file list Properties Values HTTP methods GET Interface path /nd/api/file/list dir Category File API Interface description Interface path: /nd/api/file/list dir HTTP method: GET HTTP method: GET URL parameters Parameter name Comment (description) parent id parent folder id (required) string When parent is 1, returns the contents of the corporate folder, 2 returns the contents of the personal folder, 3 returns my Project, 4 returns the share I added, and other fileId returns the contents of the normal folder. page size page size number page page number type type: divided into three types: 1 file, 2 folder, 0 all string Return field description Attribute name type description files array fi", "headings": [ { "level": 1, "title": "Get file list", "id": "get-file-list" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Get file list Properties Values HTTP methods GET Interface path /nd/api/file/list dir Category File API Interface description Interface path: /nd/api/file/list dir HTTP method: GET HTTP method: GET URL parameters Parameter name Comment (description) parent id parent folder id (required) string When parent is 1, returns the contents of the corporate folder, 2 returns the contents of the personal folder, 3 returns my Project, 4 returns the share I added, and other fileId returns the contents of the normal folder. page size page size number page page number type type: divided into three types: 1 file, 2 folder, 0 all string Return field description Attribute name type description files array file information {fileId, name, …} total int total quantity page int page capacity success boolean gets the success mark code int returns error code 0 indicates success Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: File API." }, { "lang": "en", "slug": "api-get-nd-api-file-fileinfo", "title": "Get file information", "description": "GET /nd/api/file/fileinfo: Get file information interface description, including path, method, parameters and return information.", "category": "File API", "top_category": "API文档", "keywords": [ "API", "Get file information", "/nd/api/file/fileinfo" ], "url": "en/api-get-nd-api-file-fileinfo.html", "source": "content/en/api-get-nd-api-file-fileinfo.md", "summary": "Get file information Properties Values HTTP methods GET Interface path /nd/api/file/fileinfo Category File API Interface description Interface path: /nd/api/file/fileinfo HTTP method: GET HTTP method: GET URL parameters Parameter name Comment (description) id file id (required) string Return field description fileInfo information Attribute name type description file Object file information { id, name, …} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents ", "headings": [ { "level": 1, "title": "Get file information", "id": "get-file-information" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Get file information Properties Values HTTP methods GET Interface path /nd/api/file/fileinfo Category File API Interface description Interface path: /nd/api/file/fileinfo HTTP method: GET HTTP method: GET URL parameters Parameter name Comment (description) id file id (required) string Return field description fileInfo information Attribute name type description file Object file information { id, name, …} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: File API." }, { "lang": "en", "slug": "api-post-nd-api-file-create-folder", "title": "Create folder", "description": "POST /nd/api/file/create_folder: Create folder interface description, including path, method, parameters and return information.", "category": "File API", "top_category": "API文档", "keywords": [ "API", "Create folder", "/nd/api/file/create_folder" ], "url": "en/api-post-nd-api-file-create-folder.html", "source": "content/en/api-post-nd-api-file-create-folder.md", "summary": "Create folder Properties Values HTTP method POST Interface path /nd/api/file/create folder Category File API Interface description Interface path: /nd/api/file/create folder HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) parent id target folder id (required) string name file name (required) string Return field description Attribute name type description file Object file information { id, name, …} success boolean gets the success mark code int returns error code 0 indicates success Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request", "headings": [ { "level": 1, "title": "Create folder", "id": "create-folder" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Create folder Properties Values HTTP method POST Interface path /nd/api/file/create folder Category File API Interface description Interface path: /nd/api/file/create folder HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) parent id target folder id (required) string name file name (required) string Return field description Attribute name type description file Object file information { id, name, …} success boolean gets the success mark code int returns error code 0 indicates success Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: File API." }, { "lang": "en", "slug": "api-get-api-file-preuploadfile-do", "title": "Pre-upload files", "description": "GET /api/file/preUploadFile.do: Pre-upload file interface description, including path, method, parameters and return information.", "category": "File API", "top_category": "API文档", "keywords": [ "API", "Pre-upload files", "/api/file/preUploadFile.do" ], "url": "en/api-get-api-file-preuploadfile-do.html", "source": "content/en/api-get-api-file-preuploadfile-do.md", "summary": "Pre upload files Properties Values HTTP methods GET Interface path /api/file/preUploadFile.do Category File API Interface description Interface path: /api/file/preUploadFile.do HTTP method: GET HTTP method: GET URL parameters Parameter name Comment (description) parent id target folder id (required) (you can ignore this when uploading in the root directory) string name file name (required) string file id When uploading a new version, you need to specify the new version of the file to upload (you can ignore this when uploading new files) string The correct return result is as follows {\"upload token\":\"92808ecfc2ac4e0ebc0b912edac3be4a\",\"url\":\"http://testdocument.babel.cc/api/file/uploadPdf.do\",", "headings": [ { "level": 1, "title": "Pre upload files", "id": "pre-upload-files" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Pre upload files Properties Values HTTP methods GET Interface path /api/file/preUploadFile.do Category File API Interface description Interface path: /api/file/preUploadFile.do HTTP method: GET HTTP method: GET URL parameters Parameter name Comment (description) parent id target folder id (required) (you can ignore this when uploading in the root directory) string name file name (required) string file id When uploading a new version, you need to specify the new version of the file to upload (you can ignore this when uploading new files) string The correct return result is as follows {\"upload token\":\"92808ecfc2ac4e0ebc0b912edac3be4a\",\"url\":\"http://testdocument.babel.cc/api/file/uploadPdf.do\",\"su ccess\":true,\"code\":0} Return field description Attribute name type description url string This url can only be used once and is valid for 1 hour. Call this url to upload a file. After success, fileId, fileName, version, etc. will be returned. upload token string is used as a parameter of post when uploading files. Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: File API." }, { "lang": "en", "slug": "api-get-api-file-getfiledownloadurl-do", "title": "Get download file address", "description": "GET /api/file/getFileDownloadUrl.do: Get the download file address. Interface description, including path, method, parameters and return information.", "category": "File API", "top_category": "API文档", "keywords": [ "API", "Get download file address", "/api/file/getFileDownloadUrl.do" ], "url": "en/api-get-api-file-getfiledownloadurl-do.html", "source": "content/en/api-get-api-file-getfiledownloadurl-do.md", "summary": "Get the download file address Properties Values HTTP methods GET Interface path /api/file/getFileDownloadUrl.do Category File API Interface description Interface path: /api/file/getFileDownloadUrl.do HTTP method: GET HTTP method: GET URL parameters Parameter name Comment (description) fileId file id to be downloaded (required) string version The version number of the file (optional) number The return information is as follows {\"code\":0,\"success\":true,\"type\":\"File type\",\"url\":\"File download address\"} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in", "headings": [ { "level": 1, "title": "Get the download file address", "id": "get-the-download-file-address" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Get the download file address Properties Values HTTP methods GET Interface path /api/file/getFileDownloadUrl.do Category File API Interface description Interface path: /api/file/getFileDownloadUrl.do HTTP method: GET HTTP method: GET URL parameters Parameter name Comment (description) fileId file id to be downloaded (required) string version The version number of the file (optional) number The return information is as follows {\"code\":0,\"success\":true,\"type\":\"File type\",\"url\":\"File download address\"} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: File API." }, { "lang": "en", "slug": "api-get-api-file-downloadmultifiles-do", "title": "Get download address of multiple files", "description": "GET /api/file/downloadMultiFiles.do: Get the download address of multiple files. Interface description, including path, method, parameters and return information.", "category": "File API", "top_category": "API文档", "keywords": [ "API", "Get download address of multiple files", "/api/file/downloadMultiFiles.do" ], "url": "en/api-get-api-file-downloadmultifiles-do.html", "source": "content/en/api-get-api-file-downloadmultifiles-do.md", "summary": "Get download address of multiple files Properties Values HTTP methods GET Interface path /api/file/downloadMultiFiles.do Category File API Interface description Interface path: /api/file/downloadMultiFiles.do HTTP method: GET HTTP method: GET URL parameters Parameter name Comment (description) fileIdArr is a string composed of the id of the file to be downloaded, separated by the symbol \"!\" (half width), for example, the download ids are 133 and 233. file, the value of fileIdArr is \"133!233\" string type Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are difference", "headings": [ { "level": 1, "title": "Get download address of multiple files", "id": "get-download-address-of-multiple-files" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Get download address of multiple files Properties Values HTTP methods GET Interface path /api/file/downloadMultiFiles.do Category File API Interface description Interface path: /api/file/downloadMultiFiles.do HTTP method: GET HTTP method: GET URL parameters Parameter name Comment (description) fileIdArr is a string composed of the id of the file to be downloaded, separated by the symbol \"!\" (half width), for example, the download ids are 133 and 233. file, the value of fileIdArr is \"133!233\" string type Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: File API." }, { "lang": "en", "slug": "api-get-api-file-downloadthumbnail-do", "title": "Get download file thumbnail address", "description": "GET /api/file/downloadThumbnail.do: Get the download file thumbnail address. Interface description, including path, method, parameters and return information.", "category": "File API", "top_category": "API文档", "keywords": [ "API", "Get download file thumbnail address", "/api/file/downloadThumbnail.do" ], "url": "en/api-get-api-file-downloadthumbnail-do.html", "source": "content/en/api-get-api-file-downloadthumbnail-do.md", "summary": "Get the download file thumbnail address Properties Values HTTP methods GET Interface path /api/file/downloadThumbnail.do Category File API Interface description Interface path: /api/file/downloadThumbnail.do HTTP method: GET HTTP method: GET URL parameters Parameter name Comment (description) fileId file id to be downloaded (required) string version The version number of the file (optional) number size is the size of the thumbnail to be displayed, taking the maximum value of width and height. The return information is as follows {\"code\":0,\"success\":true, \"url\":\"File download address\"} The return value url is the download address of multiple files packaged. Call instructions Before calling, y", "headings": [ { "level": 1, "title": "Get the download file thumbnail address", "id": "get-the-download-file-thumbnail-address" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Get the download file thumbnail address Properties Values HTTP methods GET Interface path /api/file/downloadThumbnail.do Category File API Interface description Interface path: /api/file/downloadThumbnail.do HTTP method: GET HTTP method: GET URL parameters Parameter name Comment (description) fileId file id to be downloaded (required) string version The version number of the file (optional) number size is the size of the thumbnail to be displayed, taking the maximum value of width and height. The return information is as follows {\"code\":0,\"success\":true, \"url\":\"File download address\"} The return value url is the download address of multiple files packaged. Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: File API." }, { "lang": "en", "slug": "api-post-nd-api-file-update-file", "title": "Modify file information", "description": "POST /nd/api/file/update_file: Modify file information interface description, including path, method, parameters and return information.", "category": "File API", "top_category": "API文档", "keywords": [ "API", "Modify file information", "/nd/api/file/update_file" ], "url": "en/api-post-nd-api-file-update-file.html", "source": "content/en/api-post-nd-api-file-update-file.md", "summary": "Modify file information Properties Values HTTP method POST Interface path /nd/api/file/update file Category File API Interface description Interface path: /nd/api/file/update file HTTP method: POST HTTP method: POST Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: File API.", "headings": [ { "level": 1, "title": "Modify file information", "id": "modify-file-information" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Modify file information Properties Values HTTP method POST Interface path /nd/api/file/update file Category File API Interface description Interface path: /nd/api/file/update file HTTP method: POST HTTP method: POST Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: File API." }, { "lang": "en", "slug": "api-post-nd-api-file-rename", "title": "Modify file name", "description": "POST /nd/api/file/rename: Modify the file name interface description, including path, method, parameters and return information.", "category": "File API", "top_category": "API文档", "keywords": [ "API", "Modify file name", "/nd/api/file/rename" ], "url": "en/api-post-nd-api-file-rename.html", "source": "content/en/api-post-nd-api-file-rename.md", "summary": "Modify file name Properties Values HTTP method POST Interface path /nd/api/file/rename Category File API Interface description Interface path: /nd/api/file/rename HTTP method: POST HTTP method: POST Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: File API.", "headings": [ { "level": 1, "title": "Modify file name", "id": "modify-file-name" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Modify file name Properties Values HTTP method POST Interface path /nd/api/file/rename Category File API Interface description Interface path: /nd/api/file/rename HTTP method: POST HTTP method: POST Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: File API." }, { "lang": "en", "slug": "api-post-nd-api-file-remove-file", "title": "Delete files (to recycle bin)", "description": "POST /nd/api/file/remove_file: delete file (to the recycle bin) interface description, including path, method, parameters and return information.", "category": "File API", "top_category": "API文档", "keywords": [ "API", "Delete files (to recycle bin)", "/nd/api/file/remove_file" ], "url": "en/api-post-nd-api-file-remove-file.html", "source": "content/en/api-post-nd-api-file-remove-file.md", "summary": "Delete files (to the recycle bin) Properties Values HTTP method POST Interface path /nd/api/file/remove file Category File API Interface description Interface path: /nd/api/file/remove file HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) file ids[] target file id array (required) string[] The return information is as follows {\"code\":0,\"success\":true} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents a", "headings": [ { "level": 1, "title": "Delete files (to the recycle bin)", "id": "delete-files-to-the-recycle-bin" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Delete files (to the recycle bin) Properties Values HTTP method POST Interface path /nd/api/file/remove file Category File API Interface description Interface path: /nd/api/file/remove file HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) file ids[] target file id array (required) string[] The return information is as follows {\"code\":0,\"success\":true} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: File API." }, { "lang": "en", "slug": "api-post-nd-api-file-remove-from-trash", "title": "Delete files (from Recycle Bin)", "description": "POST /nd/api/file/remove_from_trash: Delete files (from the trash bin) Interface description, including path, method, parameters and return information.", "category": "File API", "top_category": "API文档", "keywords": [ "API", "Delete files (from Recycle Bin)", "/nd/api/file/remove_from_trash" ], "url": "en/api-post-nd-api-file-remove-from-trash.html", "source": "content/en/api-post-nd-api-file-remove-from-trash.md", "summary": "Delete files (from recycle bin) Properties Values HTTP method POST Interface path /nd/api/file/remove from trash Category File API Interface description Interface path: /nd/api/file/remove from trash HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) file ids[] target file id array (required) string[] The return information is as follows {\"code\":0,\"success\":true} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API d", "headings": [ { "level": 1, "title": "Delete files (from recycle bin)", "id": "delete-files-from-recycle-bin" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Delete files (from recycle bin) Properties Values HTTP method POST Interface path /nd/api/file/remove from trash Category File API Interface description Interface path: /nd/api/file/remove from trash HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) file ids[] target file id array (required) string[] The return information is as follows {\"code\":0,\"success\":true} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: File API." }, { "lang": "en", "slug": "api-post-nd-api-file-empty-trash", "title": "Empty Recycle Bin", "description": "POST /nd/api/file/empty_trash: clear the recycle bin interface description, including path, method, parameters and return information.", "category": "File API", "top_category": "API文档", "keywords": [ "API", "Empty Recycle Bin", "/nd/api/file/empty_trash" ], "url": "en/api-post-nd-api-file-empty-trash.html", "source": "content/en/api-post-nd-api-file-empty-trash.md", "summary": "Empty the recycle bin Properties Values HTTP method POST Interface path /nd/api/file/empty trash Category File API Interface description Interface path: /nd/api/file/empty trash HTTP method: POST HTTP method: POST POST request body parameters Parameter name Description The return information is as follows {\"code\":0,\"success\":true} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: File API.", "headings": [ { "level": 1, "title": "Empty the recycle bin", "id": "empty-the-recycle-bin" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Empty the recycle bin Properties Values HTTP method POST Interface path /nd/api/file/empty trash Category File API Interface description Interface path: /nd/api/file/empty trash HTTP method: POST HTTP method: POST POST request body parameters Parameter name Description The return information is as follows {\"code\":0,\"success\":true} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: File API." }, { "lang": "en", "slug": "api-post-nd-api-file-restore-file", "title": "Recover files (from Recycle Bin)", "description": "POST /nd/api/file/restore_file: Restore files (from the recycle bin) interface description, including path, method, parameters and return information.", "category": "File API", "top_category": "API文档", "keywords": [ "API", "Recover files (from Recycle Bin)", "/nd/api/file/restore_file" ], "url": "en/api-post-nd-api-file-restore-file.html", "source": "content/en/api-post-nd-api-file-restore-file.md", "summary": "Restore files (from recycle bin) Properties Values HTTP method POST Interface path /nd/api/file/restore file Category File API Interface description Interface path: /nd/api/file/restore file HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) file ids[] target file id array string[] restoreAll If file ids is not filled in, restoreAll is true to restore all files in the recycle bin, boolean The return information is as follows Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fi", "headings": [ { "level": 1, "title": "Restore files (from recycle bin)", "id": "restore-files-from-recycle-bin" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Restore files (from recycle bin) Properties Values HTTP method POST Interface path /nd/api/file/restore file Category File API Interface description Interface path: /nd/api/file/restore file HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) file ids[] target file id array string[] restoreAll If file ids is not filled in, restoreAll is true to restore all files in the recycle bin, boolean The return information is as follows Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: File API." }, { "lang": "en", "slug": "api-get-nd-api-file-versions", "title": "Get all version information of a file", "description": "GET /nd/api/file/versions: Get all version information of the file. Interface description, including path, method, parameters and return information.", "category": "File API", "top_category": "API文档", "keywords": [ "API", "Get all version information of a file", "/nd/api/file/versions" ], "url": "en/api-get-nd-api-file-versions.html", "source": "content/en/api-get-nd-api-file-versions.md", "summary": "Get all version information of the file Properties Values HTTP methods GET Interface path /nd/api/file/versions Category File API Interface description Interface path: /nd/api/file/versions HTTP method: GET HTTP method: GET URL parameters Parameter name Comment (description) file id target file id (required) string The return information is as follows {\"code\":0,\"versions\":[],\"success\":true} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debu", "headings": [ { "level": 1, "title": "Get all version information of the file", "id": "get-all-version-information-of-the-file" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Get all version information of the file Properties Values HTTP methods GET Interface path /nd/api/file/versions Category File API Interface description Interface path: /nd/api/file/versions HTTP method: GET HTTP method: GET URL parameters Parameter name Comment (description) file id target file id (required) string The return information is as follows {\"code\":0,\"versions\":[],\"success\":true} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: File API." }, { "lang": "en", "slug": "api-post-nd-api-file-version", "title": "Set the current version of the file", "description": "POST /nd/api/file/version: Set the current version of the file. Interface description, including path, method, parameters and return information.", "category": "File API", "top_category": "API文档", "keywords": [ "API", "Set the current version of the file", "/nd/api/file/version" ], "url": "en/api-post-nd-api-file-version.html", "source": "content/en/api-post-nd-api-file-version.md", "summary": "Set the current version of the file Properties Values HTTP method POST Interface path /nd/api/file/version Category File API Interface description Interface path: /nd/api/file/version HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) file id target file id (required) string version version number (required) number The return information is as follows {\"code\":0,\"success\":true} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual priva", "headings": [ { "level": 1, "title": "Set the current version of the file", "id": "set-the-current-version-of-the-file" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Set the current version of the file Properties Values HTTP method POST Interface path /nd/api/file/version Category File API Interface description Interface path: /nd/api/file/version HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) file id target file id (required) string version version number (required) number The return information is as follows {\"code\":0,\"success\":true} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: File API." }, { "lang": "en", "slug": "api-post-nd-api-file-move", "title": "Move files", "description": "POST /nd/api/file/move: Move file interface description, including path, method, parameters and return information.", "category": "File API", "top_category": "API文档", "keywords": [ "API", "Move files", "/nd/api/file/move" ], "url": "en/api-post-nd-api-file-move.html", "source": "content/en/api-post-nd-api-file-move.md", "summary": "Move files Properties Values HTTP method POST Interface path /nd/api/file/move Category File API Interface description Interface path: /nd/api/file/move HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) file ids Target file id array to be moved (required) string target id The target folder id that needs to be moved to (required) string The return information is as follows {\"code\":0,\"success\":true} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment vers", "headings": [ { "level": 1, "title": "Move files", "id": "move-files" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Move files Properties Values HTTP method POST Interface path /nd/api/file/move Category File API Interface description Interface path: /nd/api/file/move HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) file ids Target file id array to be moved (required) string target id The target folder id that needs to be moved to (required) string The return information is as follows {\"code\":0,\"success\":true} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: File API." }, { "lang": "en", "slug": "api-post-nd-api-file-copy", "title": "Copy files", "description": "POST /nd/api/file/copy: Copy file interface description, including path, method, parameters and return information.", "category": "File API", "top_category": "API文档", "keywords": [ "API", "Copy files", "/nd/api/file/copy" ], "url": "en/api-post-nd-api-file-copy.html", "source": "content/en/api-post-nd-api-file-copy.md", "summary": "copy files Properties Values HTTP method POST Interface path /nd/api/file/copy Category File API Interface description Interface path: /nd/api/file/copy HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: File API.", "headings": [ { "level": 1, "title": "copy files", "id": "copy-files" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "copy files Properties Values HTTP method POST Interface path /nd/api/file/copy Category File API Interface description Interface path: /nd/api/file/copy HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: File API." }, { "lang": "en", "slug": "api-post-nd-api-file-copy-progress", "title": "Copy file progress", "description": "POST /nd/api/file/copy_progress: Copy file progress interface description, including path, method, parameters and return information.", "category": "File API", "top_category": "API文档", "keywords": [ "API", "Copy file progress", "/nd/api/file/copy_progress" ], "url": "en/api-post-nd-api-file-copy-progress.html", "source": "content/en/api-post-nd-api-file-copy-progress.md", "summary": "Copy file progress Properties Values HTTP method POST Interface path /nd/api/file/copy progress Category File API Interface description Interface path: /nd/api/file/copy progress HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) copyKey Check the copy progress copyKey is returned by the copy interface (required) string The return information is as follows { \"code\": 0, \"completed\": 10, \"total\": 10, \"result\": {}, \"success\": true} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and retur", "headings": [ { "level": 1, "title": "Copy file progress", "id": "copy-file-progress" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Copy file progress Properties Values HTTP method POST Interface path /nd/api/file/copy progress Category File API Interface description Interface path: /nd/api/file/copy progress HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) copyKey Check the copy progress copyKey is returned by the copy interface (required) string The return information is as follows { \"code\": 0, \"completed\": 10, \"total\": 10, \"result\": {}, \"success\": true} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: File API." }, { "lang": "en", "slug": "api-get-nd-api-file-file-logs", "title": "file log", "description": "GET /nd/api/file/file_logs: File log interface description, including path, method, parameters and return information.", "category": "File API", "top_category": "API文档", "keywords": [ "API", "file log", "/nd/api/file/file_logs" ], "url": "en/api-get-nd-api-file-file-logs.html", "source": "content/en/api-get-nd-api-file-file-logs.md", "summary": "File log Properties Values HTTP methods GET Interface path /nd/api/file/file logs Category File API Interface description Interface path: /nd/api/file/file logs HTTP method: GET HTTP method: GET GET request body parameters Parameter name Comment (description) file id target file id array (required) string startIndex gets the starting order of logs. Which log should be returned (optional) int defaults to 0. pageSize The number of items returned per page (optional) int type Log type (optional) int Default 0, view all records, 1 only view access records, 2 only view uploads and downloads, 3 only view anonymous users Users, 4 only view sharing and invitations, 5 only view deletion records userNa", "headings": [ { "level": 1, "title": "File log", "id": "file-log" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "File log Properties Values HTTP methods GET Interface path /nd/api/file/file logs Category File API Interface description Interface path: /nd/api/file/file logs HTTP method: GET HTTP method: GET GET request body parameters Parameter name Comment (description) file id target file id array (required) string startIndex gets the starting order of logs. Which log should be returned (optional) int defaults to 0. pageSize The number of items returned per page (optional) int type Log type (optional) int Default 0, view all records, 1 only view access records, 2 only view uploads and downloads, 3 only view anonymous users Users, 4 only view sharing and invitations, 5 only view deletion records userName A username (optional) string, returns the log of a certain user lang language (optional) default cn, string language of returned log cn (Chinese) en (English) The return information is as follows {\"code\":0,\"success\":true, \"logs\":[], \"total\":50} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: File API." }, { "lang": "en", "slug": "api-post-nd-api-file-set-user-access-material-library", "title": "Set whether the user has access to the material library", "description": "POST /nd/api/file/set_user_access_material_library: Set whether the user has the right to access the material library. Interface description, including path, method, parameters and return information.", "category": "File API", "top_category": "API文档", "keywords": [ "API", "Set whether the user has access to the material library", "/nd/api/file/set_user_access_material_library" ], "url": "en/api-post-nd-api-file-set-user-access-material-library.html", "source": "content/en/api-post-nd-api-file-set-user-access-material-library.md", "summary": "Set whether the user has permission to access the material library Properties Values HTTP method POST Interface path /nd/api/file/set user access material library Category File API Interface description Interface path: /nd/api/file/set user access material library HTTP method: POST HTTP method: POST GET request body parameters Parameter name Comment (description) userId user's id array type [usrId1, userId2] (required) string can Whether it is accessible Numeric type (required) int Default 0, 0: Inaccessible, 1: Accessible The return information is as follows {\"code\":0,\"success\":true} Call instructions Before calling, you need to complete Get token or the corresponding login free authenticat", "headings": [ { "level": 1, "title": "Set whether the user has permission to access the material library", "id": "set-whether-the-user-has-permission-to-access-the-material-library" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Set whether the user has permission to access the material library Properties Values HTTP method POST Interface path /nd/api/file/set user access material library Category File API Interface description Interface path: /nd/api/file/set user access material library HTTP method: POST HTTP method: POST GET request body parameters Parameter name Comment (description) userId user's id array type [usrId1, userId2] (required) string can Whether it is accessible Numeric type (required) int Default 0, 0: Inaccessible, 1: Accessible The return information is as follows {\"code\":0,\"success\":true} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: File API." }, { "lang": "en", "slug": "api-post-nd-api-file-create-material-class", "title": "Create library categories", "description": "POST /nd/api/file/create_material_class: Create material library classification interface description, including path, method, parameters and return information.", "category": "File API", "top_category": "API文档", "keywords": [ "API", "Create library categories", "/nd/api/file/create_material_class" ], "url": "en/api-post-nd-api-file-create-material-class.html", "source": "content/en/api-post-nd-api-file-create-material-class.md", "summary": "Create material library classification Properties Values HTTP method POST Interface path /nd/api/file/create material class Category File API Interface description Interface path: /nd/api/file/create material class HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) destDirFileId fileId of the destination folder (required) string name The name of the created category library (required) string accessType Classification visibility (optional) Defaults to public 0. 0: // public 1: // Need to apply 2: // Department is public 3: // Department application 4: // Confidential managerIds The id array type of the person in charge [usrId1,userId2] depart", "headings": [ { "level": 1, "title": "Create material library classification", "id": "create-material-library-classification" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Create material library classification Properties Values HTTP method POST Interface path /nd/api/file/create material class Category File API Interface description Interface path: /nd/api/file/create material class HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) destDirFileId fileId of the destination folder (required) string name The name of the created category library (required) string accessType Classification visibility (optional) Defaults to public 0. 0: // public 1: // Need to apply 2: // Department is public 3: // Department application 4: // Confidential managerIds The id array type of the person in charge [usrId1,userId2] departmentIds Classification visibility limited department id of department (optional) Array type [departmentId1,departmentId2] The return information is as follows {\"code\":0, \"success\":true, \"materialClass\": {}} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: File API." }, { "lang": "en", "slug": "api-post-nd-api-file-create-material-folder", "title": "Create sub-library", "description": "POST /nd/api/file/create_material_folder: Create sub-material library interface description, including path, method, parameters and return information.", "category": "File API", "top_category": "API文档", "keywords": [ "API", "Create sub-library", "/nd/api/file/create_material_folder" ], "url": "en/api-post-nd-api-file-create-material-folder.html", "source": "content/en/api-post-nd-api-file-create-material-folder.md", "summary": "Create sub material library Properties Values HTTP method POST Interface path /nd/api/file/create material folder Category File API Interface description Interface path: /nd/api/file/create material folder HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) destDirFileId fileId of the destination folder (required) string name The name of the created category library (required) string accessType Classification visibility (optional) Defaults to public 0. 0: // public 1: // Need to apply 2: // Department is public 3: // Department application 4: // Confidential managerId The id of the person in charge (optional) string departmentIds Classificati", "headings": [ { "level": 1, "title": "Create sub material library", "id": "create-sub-material-library" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Shared file related API", "id": "shared-file-related-api" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Create sub material library Properties Values HTTP method POST Interface path /nd/api/file/create material folder Category File API Interface description Interface path: /nd/api/file/create material folder HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) destDirFileId fileId of the destination folder (required) string name The name of the created category library (required) string accessType Classification visibility (optional) Defaults to public 0. 0: // public 1: // Need to apply 2: // Department is public 3: // Department application 4: // Confidential managerId The id of the person in charge (optional) string departmentIds Classification visibility limited department id of department (optional) Array type [departmentId1,departmentId2] assistantIds ID of the material library assistant (optional) Array type [usrId1,userId2] The return information is as follows {\"code\":0, \"success\":true, \"materialFolder\": {}} Shared file related API Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: File API." }, { "lang": "en", "slug": "api-get-nd-api-share-shareurl", "title": "Get the sharing url of the file", "description": "GET /nd/api/share/shareurl: Get the file sharing url interface description, including path, method, parameters and return information.", "category": "Sharing API", "top_category": "API文档", "keywords": [ "API", "Get the sharing url of the file", "/nd/api/share/shareurl" ], "url": "en/api-get-nd-api-share-shareurl.html", "source": "content/en/api-get-nd-api-share-shareurl.md", "summary": "Get the sharing url of the file Properties Values HTTP methods GET Interface path /nd/api/share/shareurl Category Share API Interface description Interface path: /nd/api/share/shareurl HTTP method: GET HTTP method: GET Get the sharing link of the file (open the sharing first, and then get the link) URL parameters Parameter name Comment (description) file id file id string is https Whether the returned share url protocol is https 0 means http, 1 means https, default 0 number Return field description {\"code\":0,\"url\":\"https://private.babel.cc/share.do?s=http://private.babel.cc/share.do?s=MjY2OTYzNTk3OTU2NzEzOTtXZWQgSnVsIDAxIDIwMj AgMTg6MzM6NTAgR01UKzA4MDAgKEhvbmcgS29uZyBTdGFuZGFyZCBUaW1lKQ%3D%3", "headings": [ { "level": 1, "title": "Get the sharing url of the file", "id": "get-the-sharing-url-of-the-file" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Get the sharing url of the file Properties Values HTTP methods GET Interface path /nd/api/share/shareurl Category Share API Interface description Interface path: /nd/api/share/shareurl HTTP method: GET HTTP method: GET Get the sharing link of the file (open the sharing first, and then get the link) URL parameters Parameter name Comment (description) file id file id string is https Whether the returned share url protocol is https 0 means http, 1 means https, default 0 number Return field description {\"code\":0,\"url\":\"https://private.babel.cc/share.do?s=http://private.babel.cc/share.do?s=MjY2OTYzNTk3OTU2NzEzOTtXZWQgSnVsIDAxIDIwMj AgMTg6MzM6NTAgR01UKzA4MDAgKEhvbmcgS29uZyBTdGFuZGFyZCBUaW1lKQ%3D%3D\",\"success\":true} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Sharing API." }, { "lang": "en", "slug": "api-get-nd-api-share-share-roles", "title": "Get a list of shared permissions", "description": "GET /nd/api/share/share_roles: Get the shared permission list interface description, including path, method, parameters and return information.", "category": "Sharing API", "top_category": "API文档", "keywords": [ "API", "Get a list of shared permissions", "/nd/api/share/share_roles" ], "url": "en/api-get-nd-api-share-share-roles.html", "source": "content/en/api-get-nd-api-share-share-roles.md", "summary": "Get the shared permission list Properties Values HTTP methods GET Interface path /nd/api/share/share roles Category Share API Interface description Interface path: /nd/api/share/share roles HTTP method: GET HTTP method: GET URL parameters Parameter name Comment (description) Return field description {\"code\":0,\"roles\":[],\"success\":true} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Sharing API.", "headings": [ { "level": 1, "title": "Get the shared permission list", "id": "get-the-shared-permission-list" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Get the shared permission list Properties Values HTTP methods GET Interface path /nd/api/share/share roles Category Share API Interface description Interface path: /nd/api/share/share roles HTTP method: GET HTTP method: GET URL parameters Parameter name Comment (description) Return field description {\"code\":0,\"roles\":[],\"success\":true} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Sharing API." }, { "lang": "en", "slug": "api-get-nd-api-share-share-role-forfile", "title": "Get the sharing roles that the user has permission to set for a single file", "description": "GET /nd/api/share/share_role_forfile: Get the sharing role interface description that the user has the right to set for a single file, including path, method, parameters and return information.", "category": "Sharing API", "top_category": "API文档", "keywords": [ "API", "Get the sharing roles that the user has permission to set for a single file", "/nd/api/share/share_role_forfile" ], "url": "en/api-get-nd-api-share-share-role-forfile.html", "source": "content/en/api-get-nd-api-share-share-role-forfile.md", "summary": "Get the sharing roles that the user has permission to set for a single file Properties Values HTTP methods GET Interface path /nd/api/share/share role forfile Category Share API Interface description Interface path: /nd/api/share/share role forfile HTTP method: GET HTTP method: GET URL parameters Parameter name Comment (description) file id file id string Return field description {\"code\":0,\"roles\":[],\"success\":true} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud AP", "headings": [ { "level": 1, "title": "Get the sharing roles that the user has permission to set for a single file", "id": "get-the-sharing-roles-that-the-user-has-permission-to-set-for-a-single-file" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Get the sharing roles that the user has permission to set for a single file Properties Values HTTP methods GET Interface path /nd/api/share/share role forfile Category Share API Interface description Interface path: /nd/api/share/share role forfile HTTP method: GET HTTP method: GET URL parameters Parameter name Comment (description) file id file id string Return field description {\"code\":0,\"roles\":[],\"success\":true} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Sharing API." }, { "lang": "en", "slug": "api-post-nd-api-share-open-link-share", "title": "Create link to share", "description": "POST /nd/api/share/open_link_share: Create link sharing interface description, including path, method, parameters and return information.", "category": "Sharing API", "top_category": "API文档", "keywords": [ "API", "Create link to share", "/nd/api/share/open_link_share" ], "url": "en/api-post-nd-api-share-open-link-share.html", "source": "content/en/api-post-nd-api-share-open-link-share.md", "summary": "Create link to share Properties Values HTTP method POST Interface path /nd/api/share/open link share Category Share API Interface description Interface path: /nd/api/share/open link share HTTP method: POST HTTP method: POST Open sharing and get a new sharing link. The previous link will be invalid. Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Sharing API.", "headings": [ { "level": 1, "title": "Create link to share", "id": "create-link-to-share" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Create link to share Properties Values HTTP method POST Interface path /nd/api/share/open link share Category Share API Interface description Interface path: /nd/api/share/open link share HTTP method: POST HTTP method: POST Open sharing and get a new sharing link. The previous link will be invalid. Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Sharing API." }, { "lang": "en", "slug": "api-post-nd-api-share-close-link-share", "title": "Turn off link sharing", "description": "POST /nd/api/share/close_link_share: Close link sharing interface description, including path, method, parameters and return information.", "category": "Sharing API", "top_category": "API文档", "keywords": [ "API", "Turn off link sharing", "/nd/api/share/close_link_share" ], "url": "en/api-post-nd-api-share-close-link-share.html", "source": "content/en/api-post-nd-api-share-close-link-share.md", "summary": "Turn off link sharing Properties Values HTTP method POST Interface path /nd/api/share/close link share Category Share API Interface description Interface path: /nd/api/share/close link share HTTP method: POST HTTP method: POST Close the shared link I opened POST request body parameters Parameter name Comment (description) file id shared file id (required) string Return field description {\"code\":0,\"success\":true} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API do", "headings": [ { "level": 1, "title": "Turn off link sharing", "id": "turn-off-link-sharing" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Turn off link sharing Properties Values HTTP method POST Interface path /nd/api/share/close link share Category Share API Interface description Interface path: /nd/api/share/close link share HTTP method: POST HTTP method: POST Close the shared link I opened POST request body parameters Parameter name Comment (description) file id shared file id (required) string Return field description {\"code\":0,\"success\":true} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Sharing API." }, { "lang": "en", "slug": "api-post-nd-api-share-set-share-password", "title": "Set link sharing password", "description": "POST /nd/api/share/set_share_password: Set the link sharing password. Interface description, including path, method, parameters and return information.", "category": "Sharing API", "top_category": "API文档", "keywords": [ "API", "Set link sharing password", "/nd/api/share/set_share_password" ], "url": "en/api-post-nd-api-share-set-share-password.html", "source": "content/en/api-post-nd-api-share-set-share-password.md", "summary": "Set link sharing password Properties Values HTTP method POST Interface path /nd/api/share/set share password Category Share API Interface description Interface path: /nd/api/share/set share password HTTP method: POST HTTP method: POST File link sharing is turned on, set a password for link sharing. POST request body parameters Parameter name Comment (description) file id pre shared file id (required) string password password for link sharing string is https Whether the returned share url protocol is https number Return field description {\"code\":0,\"success\":true, \"share url\": \"http://private.babel.cc/share.do?s=xxxxxxxxxxx\"} Call instructions Before calling, you need to complete Get token or ", "headings": [ { "level": 1, "title": "Set link sharing password", "id": "set-link-sharing-password" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Set link sharing password Properties Values HTTP method POST Interface path /nd/api/share/set share password Category Share API Interface description Interface path: /nd/api/share/set share password HTTP method: POST HTTP method: POST File link sharing is turned on, set a password for link sharing. POST request body parameters Parameter name Comment (description) file id pre shared file id (required) string password password for link sharing string is https Whether the returned share url protocol is https number Return field description {\"code\":0,\"success\":true, \"share url\": \"http://private.babel.cc/share.do?s=xxxxxxxxxxx\"} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Sharing API." }, { "lang": "en", "slug": "api-post-nd-api-share-invite-share", "title": "Invite people to share", "description": "POST /nd/api/share/invite_share: Invite people to participate in sharing interface description, including path, method, parameters and return information.", "category": "Sharing API", "top_category": "API文档", "keywords": [ "API", "Invite people to share", "/nd/api/share/invite_share" ], "url": "en/api-post-nd-api-share-invite-share.html", "source": "content/en/api-post-nd-api-share-invite-share.md", "summary": "Invite people to share Properties Values HTTP method POST Interface path /nd/api/share/invite share Category Share API Interface description Interface path: /nd/api/share/invite share HTTP method: POST HTTP method: POST Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Sharing API.", "headings": [ { "level": 1, "title": "Invite people to share", "id": "invite-people-to-share" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Invite people to share Properties Values HTTP method POST Interface path /nd/api/share/invite share Category Share API Interface description Interface path: /nd/api/share/invite share HTTP method: POST HTTP method: POST Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Sharing API." }, { "lang": "en", "slug": "api-get-nd-api-share-share-participants", "title": "Get all sharing participants", "description": "GET /nd/api/share/share_participants: Get the interface description of all sharing participants, including path, method, parameters and return information.", "category": "Sharing API", "top_category": "API文档", "keywords": [ "API", "Get all sharing participants", "/nd/api/share/share_participants" ], "url": "en/api-get-nd-api-share-share-participants.html", "source": "content/en/api-get-nd-api-share-share-participants.md", "summary": "Get all sharing participants Properties Values HTTP methods GET Interface path /nd/api/share/share participants Category Share API Interface description Interface path: /nd/api/share/share participants HTTP method: GET HTTP method: GET URL parameters Parameter name Comment (description) file id file id (required) string Return field description {\"code\":0,\"users\":[],\"success\":true} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging resu", "headings": [ { "level": 1, "title": "Get all sharing participants", "id": "get-all-sharing-participants" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Get all sharing participants Properties Values HTTP methods GET Interface path /nd/api/share/share participants Category Share API Interface description Interface path: /nd/api/share/share participants HTTP method: GET HTTP method: GET URL parameters Parameter name Comment (description) file id file id (required) string Return field description {\"code\":0,\"users\":[],\"success\":true} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Sharing API." }, { "lang": "en", "slug": "api-post-nd-api-share-set-participant-role", "title": "Set permission roles for sharing participants", "description": "POST /nd/api/share/set_participant_role: Set the permission role of the sharing participant. Interface description, including path, method, parameters and return information.", "category": "Sharing API", "top_category": "API文档", "keywords": [ "API", "Set permission roles for sharing participants", "/nd/api/share/set_participant_role" ], "url": "en/api-post-nd-api-share-set-participant-role.html", "source": "content/en/api-post-nd-api-share-set-participant-role.md", "summary": "Set the permission roles of sharing participants Properties Values HTTP method POST Interface path /nd/api/share/set participant role Category Share API Interface description Interface path: /nd/api/share/set participant role HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) file id file id (required) string babelshare id int (required) user id string role id int (required) role id string Return field description {\"code\":0,\"success\":true} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameter", "headings": [ { "level": 1, "title": "Set the permission roles of sharing participants", "id": "set-the-permission-roles-of-sharing-participants" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Set the permission roles of sharing participants Properties Values HTTP method POST Interface path /nd/api/share/set participant role Category Share API Interface description Interface path: /nd/api/share/set participant role HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) file id file id (required) string babelshare id int (required) user id string role id int (required) role id string Return field description {\"code\":0,\"success\":true} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Sharing API." }, { "lang": "en", "slug": "api-post-nd-api-file-remove-share-participant", "title": "Delete sharing participants", "description": "POST /nd/api/file/remove_share_participant: Delete sharing participant interface description, including path, method, parameters and return information.", "category": "Sharing API", "top_category": "API文档", "keywords": [ "API", "Delete sharing participants", "/nd/api/file/remove_share_participant" ], "url": "en/api-post-nd-api-file-remove-share-participant.html", "source": "content/en/api-post-nd-api-file-remove-share-participant.md", "summary": "Delete sharing participants Properties Values HTTP method POST Interface path /nd/api/file/remove share participant Category Share API Interface description Interface path: /nd/api/file/remove share participant HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Sharing API.", "headings": [ { "level": 1, "title": "Delete sharing participants", "id": "delete-sharing-participants" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Delete sharing participants Properties Values HTTP method POST Interface path /nd/api/file/remove share participant Category Share API Interface description Interface path: /nd/api/file/remove share participant HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Sharing API." }, { "lang": "en", "slug": "api-post-nd-api-file-focus-file", "title": "remind attention", "description": "POST /nd/api/file/focus_file: Remind attention to the interface description, including path, method, parameters and return information.", "category": "Sharing API", "top_category": "API文档", "keywords": [ "API", "remind attention", "/nd/api/file/focus_file" ], "url": "en/api-post-nd-api-file-focus-file.html", "source": "content/en/api-post-nd-api-file-focus-file.md", "summary": "Remind attention Properties Values HTTP method POST Interface path /nd/api/file/focus file Category Share API Interface description Interface path: /nd/api/file/focus file HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) file id file id (required) string user ids[] The id of the user to be reminded. This id should be selected among the file participants, otherwise the reminder will not work (required) string[] Return field description {\"code\":0,\"success\":true} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are d", "headings": [ { "level": 1, "title": "Remind attention", "id": "remind-attention" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Remind attention Properties Values HTTP method POST Interface path /nd/api/file/focus file Category Share API Interface description Interface path: /nd/api/file/focus file HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) file id file id (required) string user ids[] The id of the user to be reminded. This id should be selected among the file participants, otherwise the reminder will not work (required) string[] Return field description {\"code\":0,\"success\":true} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Sharing API." }, { "lang": "en", "slug": "api-post-nd-api-file-unfocus-file", "title": "Remove someone from following", "description": "POST /nd/api/file/unfocus_file: Remove someone's attention. Interface description, including path, method, parameters and return information.", "category": "Sharing API", "top_category": "API文档", "keywords": [ "API", "Remove someone from following", "/nd/api/file/unfocus_file" ], "url": "en/api-post-nd-api-file-unfocus-file.html", "source": "content/en/api-post-nd-api-file-unfocus-file.md", "summary": "Remove someone's attention Properties Values HTTP method POST Interface path /nd/api/file/unfocus file Category Share API Interface description Interface path: /nd/api/file/unfocus file HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) file id file id (required) string user ids[] The id of the user to be reminded. This id should be selected among the file participants, otherwise the reminder will not work (required) string[] Return field description {\"code\":0,\"success\":true} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. ", "headings": [ { "level": 1, "title": "Remove someone's attention", "id": "remove-someone-s-attention" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Remove someone's attention Properties Values HTTP method POST Interface path /nd/api/file/unfocus file Category Share API Interface description Interface path: /nd/api/file/unfocus file HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) file id file id (required) string user ids[] The id of the user to be reminded. This id should be selected among the file participants, otherwise the reminder will not work (required) string[] Return field description {\"code\":0,\"success\":true} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Sharing API." }, { "lang": "en", "slug": "api-get-nd-api-file-user-focusfile", "title": "Get the list of users following a file", "description": "GET /nd/api/file/user_focusfile: Get the list of users focusing on the file. Interface description, including path, method, parameters and return information.", "category": "Sharing API", "top_category": "API文档", "keywords": [ "API", "Get the list of users following a file", "/nd/api/file/user_focusfile" ], "url": "en/api-get-nd-api-file-user-focusfile.html", "source": "content/en/api-get-nd-api-file-user-focusfile.md", "summary": "Get the list of users following the file Properties Values HTTP methods GET Interface path /nd/api/file/user focusfile Category Share API Interface description Interface path: /nd/api/file/user focusfile HTTP method: GET HTTP method: GET URL parameters Parameter name Comment (description) file id file id (required) string Return field description {\"code\":0,\"users\":[],\"success\":true} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging re", "headings": [ { "level": 1, "title": "Get the list of users following the file", "id": "get-the-list-of-users-following-the-file" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Get the list of users following the file Properties Values HTTP methods GET Interface path /nd/api/file/user focusfile Category Share API Interface description Interface path: /nd/api/file/user focusfile HTTP method: GET HTTP method: GET URL parameters Parameter name Comment (description) file id file id (required) string Return field description {\"code\":0,\"users\":[],\"success\":true} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Sharing API." }, { "lang": "en", "slug": "api-get-nd-api-file-user-can-focusfile", "title": "Get the list of users who can follow the file and mark the users who have followed the file", "description": "GET /nd/api/file/user_can_focusfile: Get the list of users who can focus on the file, and mark the user interface description of the focused file, including path, method, parameters and return information.", "category": "Sharing API", "top_category": "API文档", "keywords": [ "API", "Get the list of users who can follow the file and mark the users who have followed the file", "/nd/api/file/user_can_focusfile" ], "url": "en/api-get-nd-api-file-user-can-focusfile.html", "source": "content/en/api-get-nd-api-file-user-can-focusfile.md", "summary": "Get the list of users who can follow the file, and mark the users who have followed the file Properties Values HTTP methods GET Interface path /nd/api/file/user can focusfile Category Share API Interface description Interface path: /nd/api/file/user can focusfile HTTP method: GET Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Sharing API.", "headings": [ { "level": 1, "title": "Get the list of users who can follow the file, and mark the users who have followed the file", "id": "get-the-list-of-users-who-can-follow-the-file-and-mark-the-users-who-have-followed-the-file" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Get the list of users who can follow the file, and mark the users who have followed the file Properties Values HTTP methods GET Interface path /nd/api/file/user can focusfile Category Share API Interface description Interface path: /nd/api/file/user can focusfile HTTP method: GET Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Sharing API." }, { "lang": "en", "slug": "api-get-nd-api-enterprise-current", "title": "Get current company information", "description": "GET /nd/api/enterprise/current: Get current enterprise information interface description, including path, method, parameters and return information.", "category": "Enterprise API", "top_category": "API文档", "keywords": [ "API", "Get current company information", "/nd/api/enterprise/current" ], "url": "en/api-get-nd-api-enterprise-current.html", "source": "content/en/api-get-nd-api-enterprise-current.md", "summary": "Get current company information Properties Values HTTP methods GET Interface path /nd/api/enterprise/current Category Enterprise API Interface description Interface path: /nd/api/enterprise/current HTTP method: GET HTTP method: GET URL parameters Parameter name Comment (description) None Return field description {\"code\":0,\"enterprise\":{},\"success\":true} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category", "headings": [ { "level": 1, "title": "Get current company information", "id": "get-current-company-information" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Get current company information Properties Values HTTP methods GET Interface path /nd/api/enterprise/current Category Enterprise API Interface description Interface path: /nd/api/enterprise/current HTTP method: GET HTTP method: GET URL parameters Parameter name Comment (description) None Return field description {\"code\":0,\"enterprise\":{},\"success\":true} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Enterprise API." }, { "lang": "en", "slug": "api-get-nd-api-enterprise-departments", "title": "Obtain information from all departments of the enterprise", "description": "GET /nd/api/enterprise/departments: Get information about all departments of the enterprise. Interface description, including path, method, parameters and return information.", "category": "Enterprise API", "top_category": "API文档", "keywords": [ "API", "Obtain information from all departments of the enterprise", "/nd/api/enterprise/departments" ], "url": "en/api-get-nd-api-enterprise-departments.html", "source": "content/en/api-get-nd-api-enterprise-departments.md", "summary": "Get information about all departments of the enterprise Properties Values HTTP methods GET Interface path /nd/api/enterprise/departments Category Enterprise API Interface description Interface path: /nd/api/enterprise/departments HTTP method: GET HTTP method: GET URL parameters Parameter name Comment (description) None Return field description Attribute name type description departments [] array returns all department information tree {}json data returns the parent child structure information of the department code int successboolean Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request ", "headings": [ { "level": 1, "title": "Get information about all departments of the enterprise", "id": "get-information-about-all-departments-of-the-enterprise" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Get information about all departments of the enterprise Properties Values HTTP methods GET Interface path /nd/api/enterprise/departments Category Enterprise API Interface description Interface path: /nd/api/enterprise/departments HTTP method: GET HTTP method: GET URL parameters Parameter name Comment (description) None Return field description Attribute name type description departments [] array returns all department information tree {}json data returns the parent child structure information of the department code int successboolean Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Enterprise API." }, { "lang": "en", "slug": "api-post-nd-api-enterprise-create-department", "title": "Create corporate division", "description": "POST /nd/api/enterprise/create_department: Create enterprise department interface description, including path, method, parameters and return information.", "category": "Enterprise API", "top_category": "API文档", "keywords": [ "API", "Create corporate division", "/nd/api/enterprise/create_department" ], "url": "en/api-post-nd-api-enterprise-create-department.html", "source": "content/en/api-post-nd-api-enterprise-create-department.md", "summary": "Create enterprise department Properties Values HTTP method POST Interface path /nd/api/enterprise/create department Category Enterprise API Interface description Interface path: /nd/api/enterprise/create department HTTP method: POST HTTP method: POST Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Enterprise API.", "headings": [ { "level": 1, "title": "Create enterprise department", "id": "create-enterprise-department" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Create enterprise department Properties Values HTTP method POST Interface path /nd/api/enterprise/create department Category Enterprise API Interface description Interface path: /nd/api/enterprise/create department HTTP method: POST HTTP method: POST Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Enterprise API." }, { "lang": "en", "slug": "api-get-nd-api-enterprise-dep-role", "title": "Get a list of department roles", "description": "GET /nd/api/enterprise/dep_role: Get the department role list interface description, including path, method, parameters and return information.", "category": "Enterprise API", "top_category": "API文档", "keywords": [ "API", "Get a list of department roles", "/nd/api/enterprise/dep_role" ], "url": "en/api-get-nd-api-enterprise-dep-role.html", "source": "content/en/api-get-nd-api-enterprise-dep-role.md", "summary": "Get the list of department roles Properties Values HTTP methods GET Interface path /nd/api/enterprise/dep role Category Enterprise API Interface description Interface path: /nd/api/enterprise/dep role HTTP method: GET HTTP method: GET URL parameters Parameter name Comment (description) Return field description Attribute name type description roles []array { id, filePermission,enterpriseId,filePermission,managerPermission, default,nameEn,name} code int successboolean Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due ", "headings": [ { "level": 1, "title": "Get the list of department roles", "id": "get-the-list-of-department-roles" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Get the list of department roles Properties Values HTTP methods GET Interface path /nd/api/enterprise/dep role Category Enterprise API Interface description Interface path: /nd/api/enterprise/dep role HTTP method: GET HTTP method: GET URL parameters Parameter name Comment (description) Return field description Attribute name type description roles []array { id, filePermission,enterpriseId,filePermission,managerPermission, default,nameEn,name} code int successboolean Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Enterprise API." }, { "lang": "en", "slug": "api-post-nd-api-enterprise-add-dep-mem", "title": "Add department personnel", "description": "POST /nd/api/enterprise/add_dep_mem: Add department personnel interface description, including path, method, parameters and return information.", "category": "Enterprise API", "top_category": "API文档", "keywords": [ "API", "Add department personnel", "/nd/api/enterprise/add_dep_mem" ], "url": "en/api-post-nd-api-enterprise-add-dep-mem.html", "source": "content/en/api-post-nd-api-enterprise-add-dep-mem.md", "summary": "Add department personnel Properties Values HTTP method POST Interface path /nd/api/enterprise/add dep mem Category Enterprise API Interface description Interface path: /nd/api/enterprise/add dep mem HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) department id department id (required) string user ids[] user list string[] role id The user's role in the department string Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cl", "headings": [ { "level": 1, "title": "Add department personnel", "id": "add-department-personnel" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Add department personnel Properties Values HTTP method POST Interface path /nd/api/enterprise/add dep mem Category Enterprise API Interface description Interface path: /nd/api/enterprise/add dep mem HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) department id department id (required) string user ids[] user list string[] role id The user's role in the department string Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Enterprise API." }, { "lang": "en", "slug": "api-post-nd-api-enterprise-remove-dep-mem", "title": "Delete department personnel", "description": "POST /nd/api/enterprise/remove_dep_mem: Delete department personnel interface description, including path, method, parameters and return information.", "category": "Enterprise API", "top_category": "API文档", "keywords": [ "API", "Delete department personnel", "/nd/api/enterprise/remove_dep_mem" ], "url": "en/api-post-nd-api-enterprise-remove-dep-mem.html", "source": "content/en/api-post-nd-api-enterprise-remove-dep-mem.md", "summary": "Delete department personnel Properties Values HTTP method POST Interface path /nd/api/enterprise/remove dep mem Category Enterprise API Interface description Interface path: /nd/api/enterprise/remove dep mem HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) department id department id (required) string user ids[] Person’s id (required) string[] Return field description Attribute name type description Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment v", "headings": [ { "level": 1, "title": "Delete department personnel", "id": "delete-department-personnel" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Delete department personnel Properties Values HTTP method POST Interface path /nd/api/enterprise/remove dep mem Category Enterprise API Interface description Interface path: /nd/api/enterprise/remove dep mem HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) department id department id (required) string user ids[] Person’s id (required) string[] Return field description Attribute name type description Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Enterprise API." }, { "lang": "en", "slug": "api-get-nd-api-enterprise-mydeparments", "title": "Get information about your department", "description": "GET /nd/api/enterprise/mydeparments: Get information about your department. Interface description, including path, method, parameters and return information.", "category": "Enterprise API", "top_category": "API文档", "keywords": [ "API", "Get information about your department", "/nd/api/enterprise/mydeparments" ], "url": "en/api-get-nd-api-enterprise-mydeparments.html", "source": "content/en/api-get-nd-api-enterprise-mydeparments.md", "summary": "Get information about your department Properties Values HTTP methods GET Interface path /nd/api/enterprise/mydeparments Category Enterprise API Interface description Interface path: /nd/api/enterprise/mydeparments HTTP method: GET HTTP method: GET URL parameters Parameter name Comment (description) None Return field description Attribute name type description departments [] array returns my department information code int successboolean Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the ac", "headings": [ { "level": 1, "title": "Get information about your department", "id": "get-information-about-your-department" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Get information about your department Properties Values HTTP methods GET Interface path /nd/api/enterprise/mydeparments Category Enterprise API Interface description Interface path: /nd/api/enterprise/mydeparments HTTP method: GET HTTP method: GET URL parameters Parameter name Comment (description) None Return field description Attribute name type description departments [] array returns my department information code int successboolean Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Enterprise API." }, { "lang": "en", "slug": "api-get-nd-api-enterprise-departmentmembers", "title": "Get department personnel", "description": "GET /nd/api/enterprise/departmentmembers: Get department personnel interface description, including path, method, parameters and return information.", "category": "Enterprise API", "top_category": "API文档", "keywords": [ "API", "Get department personnel", "/nd/api/enterprise/departmentmembers" ], "url": "en/api-get-nd-api-enterprise-departmentmembers.html", "source": "content/en/api-get-nd-api-enterprise-departmentmembers.md", "summary": "Get department personnel Properties Values HTTP methods GET Interface path /nd/api/enterprise/departmentmembers Category Enterprise API Interface description Interface path: /nd/api/enterprise/departmentmembers HTTP method: GET Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Enterprise API.", "headings": [ { "level": 1, "title": "Get department personnel", "id": "get-department-personnel" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Get department personnel Properties Values HTTP methods GET Interface path /nd/api/enterprise/departmentmembers Category Enterprise API Interface description Interface path: /nd/api/enterprise/departmentmembers HTTP method: GET Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Enterprise API." }, { "lang": "en", "slug": "api-post-nd-api-enterprise-add-ent-mem", "title": "Add company members", "description": "POST /nd/api/enterprise/add_ent_mem: Add enterprise member interface description, including path, method, parameters and return information.", "category": "Enterprise API", "top_category": "API文档", "keywords": [ "API", "Add company members", "/nd/api/enterprise/add_ent_mem" ], "url": "en/api-post-nd-api-enterprise-add-ent-mem.html", "source": "content/en/api-post-nd-api-enterprise-add-ent-mem.md", "summary": "Add company members Properties Values HTTP method POST Interface path /nd/api/enterprise/add ent mem Category Enterprise API Interface description Interface path: /nd/api/enterprise/add ent mem HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) email Email mailbox string password password string enterprise role enterprise member role, optional number department ids[] The user's department, optional string[] department roles[] Roles in the department, optional string[] sex 0 not set 1 male 2 female number name username string phone mobile phone number, optional string babelId employee ID, optional string spacelimit personal space limit, unit ", "headings": [ { "level": 1, "title": "Add company members", "id": "add-company-members" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Add company members Properties Values HTTP method POST Interface path /nd/api/enterprise/add ent mem Category Enterprise API Interface description Interface path: /nd/api/enterprise/add ent mem HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) email Email mailbox string password password string enterprise role enterprise member role, optional number department ids[] The user's department, optional string[] department roles[] Roles in the department, optional string[] sex 0 not set 1 male 2 female number name username string phone mobile phone number, optional string babelId employee ID, optional string spacelimit personal space limit, unit GB, 0 means no limit number can ownfile whether the user can have personal files, 1 use the overall enterprise settings, 0 no personal files, 1 have personal files number remarks user description, optional string join time The time when the user joined the enterprise, Unix time, unit number seconds password is md5 Whether the incoming password requires md5 encryption, 0 non md5 password, 1 md5 encrypted password number Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Enterprise API." }, { "lang": "en", "slug": "api-post-api-updateuserinfo-do", "title": "Update member information", "description": "POST /api/updateUserInfo.do: Update member information interface description, including path, method, parameters and return information.", "category": "Enterprise API", "top_category": "API文档", "keywords": [ "API", "Update member information", "/api/updateUserInfo.do" ], "url": "en/api-post-api-updateuserinfo-do.html", "source": "content/en/api-post-api-updateuserinfo-do.md", "summary": "Update member information Properties Values HTTP method POST Interface path /api/updateUserInfo.do Category Enterprise API Interface description Interface path: /api/updateUserInfo.do HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) email email address (search keyword, required) string password password (change password, optional) string frozen 1 – means frozen, 0 – means unfrozen (freeze the account, optional) number password is md5 Whether the incoming password requires md5 encryption, 0 non md5 password, 1 md5 encrypted password number phone mobile phone number (optional) string Call instructions Before calling, you need to complete Get", "headings": [ { "level": 1, "title": "Update member information", "id": "update-member-information" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Update member information Properties Values HTTP method POST Interface path /api/updateUserInfo.do Category Enterprise API Interface description Interface path: /api/updateUserInfo.do HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) email email address (search keyword, required) string password password (change password, optional) string frozen 1 – means frozen, 0 – means unfrozen (freeze the account, optional) number password is md5 Whether the incoming password requires md5 encryption, 0 non md5 password, 1 md5 encrypted password number phone mobile phone number (optional) string Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Enterprise API." }, { "lang": "en", "slug": "api-get-api-getenterprisemember-do", "title": "Get enterprise member information", "description": "GET /api/getEnterpriseMember.do: Get enterprise member information. Interface description, including path, method, parameters and return information.", "category": "Enterprise API", "top_category": "API文档", "keywords": [ "API", "Get enterprise member information", "/api/getEnterpriseMember.do" ], "url": "en/api-get-api-getenterprisemember-do.html", "source": "content/en/api-get-api-getenterprisemember-do.md", "summary": "Get enterprise member information Properties Values HTTP methods GET Interface path /api/getEnterpriseMember.do Category Enterprise API Interface description Interface path: /api/getEnterpriseMember.do HTTP method: GET HTTP method: GET URL parameters Parameter name Comment (description) email email address (search keyword) string phone mobile phone number (search keyword) string babelId employee number (search keyword) string email/phone/babelId you can choose one Return field description {\"code\":0,\"success\":true,\"user\":{}} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If", "headings": [ { "level": 1, "title": "Get enterprise member information", "id": "get-enterprise-member-information" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Get enterprise member information Properties Values HTTP methods GET Interface path /api/getEnterpriseMember.do Category Enterprise API Interface description Interface path: /api/getEnterpriseMember.do HTTP method: GET HTTP method: GET URL parameters Parameter name Comment (description) email email address (search keyword) string phone mobile phone number (search keyword) string babelId employee number (search keyword) string email/phone/babelId you can choose one Return field description {\"code\":0,\"success\":true,\"user\":{}} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Enterprise API." }, { "lang": "en", "slug": "api-post-nd-api-enterprise-enterprise-members", "title": "Get all members of the company", "description": "POST /nd/api/enterprise/enterprise_members: Get the interface description of all members of the enterprise, including path, method, parameters and return information.", "category": "Enterprise API", "top_category": "API文档", "keywords": [ "API", "Get all members of the company", "/nd/api/enterprise/enterprise_members" ], "url": "en/api-post-nd-api-enterprise-enterprise-members.html", "source": "content/en/api-post-nd-api-enterprise-enterprise-members.md", "summary": "Get all members of the company Properties Values HTTP method POST Interface path /nd/api/enterprise/enterprise members Category Enterprise API Interface description Interface path: /nd/api/enterprise/enterprise members HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) lang language type, cn Chinese, en English, optional options { departmentId: //Department id, if not filled in, it means all employees of the enterprise roleId: // Role id, if not filled in, there is no role limit \"userType\": 0, // 0 internal personnel, 1 external personnel \"keyName\": \"\", // Search keywords: name, mobile phone number, email address, if not filled in, it means ", "headings": [ { "level": 1, "title": "Get all members of the company", "id": "get-all-members-of-the-company" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Get all members of the company Properties Values HTTP method POST Interface path /nd/api/enterprise/enterprise members Category Enterprise API Interface description Interface path: /nd/api/enterprise/enterprise members HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) lang language type, cn Chinese, en English, optional options { departmentId: //Department id, if not filled in, it means all employees of the enterprise roleId: // Role id, if not filled in, there is no role limit \"userType\": 0, // 0 internal personnel, 1 external personnel \"keyName\": \"\", // Search keywords: name, mobile phone number, email address, if not filled in, it means all people \"startIndex\": 0, \"pageSize\": 20, status: // 0 all accounts, 1 deactivated accounts } Optional Return field description {\"code\":0,\"success\":true,\"members\":{},\"total\":xx} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Enterprise API." }, { "lang": "en", "slug": "api-post-nd-api-enterprise-enterprise-logs", "title": "Get enterprise logs", "description": "POST /nd/api/enterprise/enterprise_logs: Get the enterprise log interface description, including path, method, parameters and return information.", "category": "Enterprise API", "top_category": "API文档", "keywords": [ "API", "Get enterprise logs", "/nd/api/enterprise/enterprise_logs" ], "url": "en/api-post-nd-api-enterprise-enterprise-logs.html", "source": "content/en/api-post-nd-api-enterprise-enterprise-logs.md", "summary": "Get enterprise logs Properties Values HTTP method POST Interface path /nd/api/enterprise/enterprise logs Category Enterprise API Interface description Interface path: /nd/api/enterprise/enterprise logs HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) department id department id, if not filled in, it will be the log of all departments string optional keyword related search keyword string optional Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versi", "headings": [ { "level": 1, "title": "Get enterprise logs", "id": "get-enterprise-logs" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Get enterprise logs Properties Values HTTP method POST Interface path /nd/api/enterprise/enterprise logs Category Enterprise API Interface description Interface path: /nd/api/enterprise/enterprise logs HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) department id department id, if not filled in, it will be the log of all departments string optional keyword related search keyword string optional Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Enterprise API." }, { "lang": "en", "slug": "api-post-nd-api-enterprise-broadcast", "title": "Make an announcement", "description": "POST /nd/api/enterprise/broadcast: Publish announcement interface description, including path, method, parameters and return information.", "category": "Enterprise API", "top_category": "API文档", "keywords": [ "API", "Make an announcement", "/nd/api/enterprise/broadcast" ], "url": "en/api-post-nd-api-enterprise-broadcast.html", "source": "content/en/api-post-nd-api-enterprise-broadcast.md", "summary": "Make an announcement Properties Values HTTP method POST Interface path /nd/api/enterprise/broadcast Category Enterprise API Interface description Interface path: /nd/api/enterprise/broadcast HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) title Announcement content string (required) string content content (required) string target users[] UserId array, if empty, it means all users will receive it, string[] target deps[] Target department, all members of this department and sub departments will receive notification, string[] Target users and target deps must be filled in at least 1 Return field description {\"code\":0,\"success\":true} Call ins", "headings": [ { "level": 1, "title": "Make an announcement", "id": "make-an-announcement" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Make an announcement Properties Values HTTP method POST Interface path /nd/api/enterprise/broadcast Category Enterprise API Interface description Interface path: /nd/api/enterprise/broadcast HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) title Announcement content string (required) string content content (required) string target users[] UserId array, if empty, it means all users will receive it, string[] target deps[] Target department, all members of this department and sub departments will receive notification, string[] Target users and target deps must be filled in at least 1 Return field description {\"code\":0,\"success\":true} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Enterprise API." }, { "lang": "en", "slug": "api-get-nd-api-enterprise-broadcast", "title": "Get published announcements", "description": "GET /nd/api/enterprise/broadcast: Get the published announcement interface description, including path, method, parameters and return information.", "category": "Enterprise API", "top_category": "API文档", "keywords": [ "API", "Get published announcements", "/nd/api/enterprise/broadcast" ], "url": "en/api-get-nd-api-enterprise-broadcast.html", "source": "content/en/api-get-nd-api-enterprise-broadcast.md", "summary": "Get published announcements Properties Values HTTP methods GET Interface path /nd/api/enterprise/broadcast Category Enterprise API Interface description Interface path: /nd/api/enterprise/broadcast HTTP method: GET HTTP method: GET URL parameters Parameter name Comment (description) start index number pagesize number Return field description {\"code\":0,\"broadcasts\":[],\"total\":19,\"success\":true} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint d", "headings": [ { "level": 1, "title": "Get published announcements", "id": "get-published-announcements" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Get published announcements Properties Values HTTP methods GET Interface path /nd/api/enterprise/broadcast Category Enterprise API Interface description Interface path: /nd/api/enterprise/broadcast HTTP method: GET HTTP method: GET URL parameters Parameter name Comment (description) start index number pagesize number Return field description {\"code\":0,\"broadcasts\":[],\"total\":19,\"success\":true} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Enterprise API." }, { "lang": "en", "slug": "api-post-nd-api-file-send-dep-discussion", "title": "Send department discussion", "description": "POST /nd/api/file/send_dep_discussion: Send department discussion interface description, including path, method, parameters and return information.", "category": "Messages And Login API", "top_category": "API文档", "keywords": [ "API", "Send department discussion", "/nd/api/file/send_dep_discussion" ], "url": "en/api-post-nd-api-file-send-dep-discussion.html", "source": "content/en/api-post-nd-api-file-send-dep-discussion.md", "summary": "Send department discussion Properties Values HTTP method POST Interface path /nd/api/file/send dep discussion Category Message and Login API Interface description Interface path: /nd/api/file/send dep discussion HTTP method: POST HTTP method: POST Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Message and Login API.", "headings": [ { "level": 1, "title": "Send department discussion", "id": "send-department-discussion" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Send department discussion Properties Values HTTP method POST Interface path /nd/api/file/send dep discussion Category Message and Login API Interface description Interface path: /nd/api/file/send dep discussion HTTP method: POST HTTP method: POST Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Message and Login API." }, { "lang": "en", "slug": "api-post-nd-api-file-dep-discussion", "title": "Get department discussions", "description": "POST /nd/api/file/dep_discussion: Get the department discussion interface description, including path, method, parameters and return information.", "category": "Messages And Login API", "top_category": "API文档", "keywords": [ "API", "Get department discussions", "/nd/api/file/dep_discussion" ], "url": "en/api-post-nd-api-file-dep-discussion.html", "source": "content/en/api-post-nd-api-file-dep-discussion.md", "summary": "Get department discussions Properties Values HTTP method POST Interface path /nd/api/file/dep discussion Category Message and Login API Interface description Interface path: /nd/api/file/dep discussion HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) dep id department id (required) string pagesize page size string start id message id, only the messages before this message will be obtained, if it is empty, the latest message will be obtained string Return field description {\"msgArr\":[],\"gotMoreMessages\":1,\"code\":0,\"success\":true} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication,", "headings": [ { "level": 1, "title": "Get department discussions", "id": "get-department-discussions" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Get department discussions Properties Values HTTP method POST Interface path /nd/api/file/dep discussion Category Message and Login API Interface description Interface path: /nd/api/file/dep discussion HTTP method: POST HTTP method: POST POST request body parameters Parameter name Comment (description) dep id department id (required) string pagesize page size string start id message id, only the messages before this message will be obtained, if it is empty, the latest message will be obtained string Return field description {\"msgArr\":[],\"gotMoreMessages\":1,\"code\":0,\"success\":true} Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Message and Login API." }, { "lang": "en", "slug": "api-get-nd-api-enterprise-enterprise-logs", "title": "Get enterprise logs", "description": "GET /nd/api/enterprise/enterprise_logs: Get the enterprise log interface description, including path, method, parameters and return information.", "category": "Enterprise API", "top_category": "API文档", "keywords": [ "API", "Get enterprise logs", "/nd/api/enterprise/enterprise_logs" ], "url": "en/api-get-nd-api-enterprise-enterprise-logs.html", "source": "content/en/api-get-nd-api-enterprise-enterprise-logs.md", "summary": "Get enterprise logs Properties Values HTTP methods GET Interface path /nd/api/enterprise/enterprise logs Category Enterprise API Interface description Interface path: /nd/api/enterprise/enterprise logs HTTP method: GET HTTP method: GET URL parameters Parameter name Comment (description) department id department id() string pagesize page size number, default value 1000 start index message starting position, number keyword log keyword string startTime start date: seconds number endTime expiration date seconds number Return field description {\"logs\":[],\"total\":0,\"code\":0,\"success\":true} total returns all those that meet the conditions (regardless of paging pageSize) Call instructions Before cal", "headings": [ { "level": 1, "title": "Get enterprise logs", "id": "get-enterprise-logs" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "Get enterprise logs Properties Values HTTP methods GET Interface path /nd/api/enterprise/enterprise logs Category Enterprise API Interface description Interface path: /nd/api/enterprise/enterprise logs HTTP method: GET HTTP method: GET URL parameters Parameter name Comment (description) department id department id() string pagesize page size number, default value 1000 start index message starting position, number keyword log keyword string startTime start date: seconds number endTime expiration date seconds number Return field description {\"logs\":[],\"total\":0,\"code\":0,\"success\":true} total returns all those that meet the conditions (regardless of paging pageSize) Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Enterprise API." }, { "lang": "en", "slug": "api-get-account-tokenlogin-do", "title": "JWT token login", "description": "GET /account/tokenLogin.do: JWT token login interface description, including path, method, parameters and return information.", "category": "Messages And Login API", "top_category": "API文档", "keywords": [ "API", "JWT token login", "/account/tokenLogin.do" ], "url": "en/api-get-account-tokenlogin-do.html", "source": "content/en/api-get-account-tokenlogin-do.md", "summary": "JWT token login Properties Values HTTP methods GET Interface path /account/tokenLogin.do Category Message and Login API Interface description Interface path: /account/tokenLogin.do HTTP method: GET Section: PDF page 29 userToken=xxxxxxxxxxxxxxxx defaultClrTheme=dark defaultLang=en disableUserMark=1 Construction of userToken userToken is an encrypted string containing logged in user information. The encrypted information is a password created by JWT, a standard security mechanism for transmitting trusted data between two parties. The content of JWT encrypted user information JSONObject is as follows: { payload: { email: “xxx@xxx.com”/“135XXXXXXX”/“XXXX”} time: now } Note: email can be an emai", "headings": [ { "level": 1, "title": "JWT token login", "id": "jwt-token-login" }, { "level": 2, "title": "Interface description", "id": "interface-description" }, { "level": 2, "title": "Call instructions", "id": "call-instructions" } ], "images": [], "text": "JWT token login Properties Values HTTP methods GET Interface path /account/tokenLogin.do Category Message and Login API Interface description Interface path: /account/tokenLogin.do HTTP method: GET Section: PDF page 29 userToken=xxxxxxxxxxxxxxxx defaultClrTheme=dark defaultLang=en disableUserMark=1 Construction of userToken userToken is an encrypted string containing logged in user information. The encrypted information is a password created by JWT, a standard security mechanism for transmitting trusted data between two parties. The content of JWT encrypted user information JSONObject is as follows: { payload: { email: “xxx@xxx.com”/“135XXXXXXX”/“XXXX”} time: now } Note: email can be an email address, mobile phone number, or work number; The code is as follows: public static void main( String[] args ) { HashMap user = new HashMap (); user.put(\"email\", \"yuanchaozhao@qq.com\"); try { //token login String userToken = createTokenJWT(user); System.out.println(\" login token:\" + userToken); JSONObject parsed = parseTokenJWT(userToken); System.out.println(\" parsed:\" + parsed); System.out.println(\" Just put this token as a parameter in the url, such as: \"); System.out.println(\"/account/tokenLogin.do?userToken=\" + userToken); } catch (Exception e) { System.out.println(e.getMessage()); } } For other codes, please refer to the jwtToken generation code, which is provided in the authentication interface 2. Remarks: JWT is the abbreviation of JSON Web Tokens. It is a communication encryption and decryption mechanism that meets the industry standard RFC7519. Please refer to: https://jwt.io/ Call instructions Before calling, you need to complete Get token or the corresponding login free authentication, and carry Authorization: Bearer in the request header. If there are differences in parameters and return fields due to deployment versions, the actual private cloud API documents and joint debugging results should prevail. Category: Message and Login API." }, { "lang": "en", "slug": "reference-api-pdf-full", "title": "API complete interface information", "description": "Babel development API complete interface information.", "category": "Source References", "top_category": "API文档", "keywords": [ "API", "PDF", "original" ], "url": "en/reference-api-pdf-full.html", "source": "content/en/reference-api-pdf-full.md", "summary": "API 完整接口资料 PDF 第 1 页 企业开发 API V6.6 上海画擎信息科技有限公司 姜大军 PDF 第 2 页 目录 一、 获取企业开发账号 ..............................................................................................................................................................................4 二、 认证 API ............................................................................................................................................................................................. 6 认证接口一（登录回调方式） ................................................................................................................................................................6 认证接口二（免登录方式 – JWT token 方式，在私有云部署中，需要开启 jwt token 的登录方式） ............", "headings": [ { "level": 1, "title": "API 完整接口资料", "id": "api" }, { "level": 3, "title": "PDF 第 1 页", "id": "pdf-1" }, { "level": 3, "title": "PDF 第 2 页", "id": "pdf-2" }, { "level": 3, "title": "PDF 第 3 页", "id": "pdf-3" }, { "level": 3, "title": "PDF 第 4 页", "id": "pdf-4" }, { "level": 2, "title": "一、 获取企业开发账号", "id": "section" }, { "level": 3, "title": "PDF 第 5 页", "id": "pdf-5" }, { "level": 3, "title": "PDF 第 6 页", "id": "pdf-6" }, { "level": 2, "title": "二、 认证 API", "id": "api-2" }, { "level": 3, "title": "认证接口一（登录回调方式）", "id": "section-2" }, { "level": 3, "title": "PDF 第 7 页", "id": "pdf-7" }, { "level": 3, "title": "PDF 第 8 页", "id": "pdf-8" }, { "level": 3, "title": "获取 token", "id": "token" }, { "level": 3, "title": "刷新 token", "id": "token-2" }, { "level": 2, "title": "三、 文件访问 API", "id": "api-3" }, { "level": 3, "title": "PDF 第 9 页", "id": "pdf-9" }, { "level": 3, "title": "获取文件列表", "id": "section-3" }, { "level": 3, "title": "获取文件信息", "id": "section-5" }, { "level": 3, "title": "PDF 第 10 页", "id": "pdf-10" }, { "level": 3, "title": "创建文件夹", "id": "section-7" }, { "level": 3, "title": "预上传文件", "id": "section-9" }, { "level": 3, "title": "PDF 第 11 页", "id": "pdf-11" }, { "level": 3, "title": "上传文件", "id": "section-12" }, { "level": 3, "title": "PDF 第 12 页", "id": "pdf-12" }, { "level": 3, "title": "获取下载文件地址", "id": "section-14" }, { "level": 3, "title": "获取下载多文件地址", "id": "section-16" }, { "level": 3, "title": "PDF 第 13 页", "id": "pdf-13" }, { "level": 3, "title": "获取下载文件缩略图地址", "id": "section-18" }, { "level": 3, "title": "修改文件信息", "id": "section-20" }, { "level": 3, "title": "修改文件信息", "id": "section-21" }, { "level": 3, "title": "修改文件名", "id": "section-23" }, { "level": 3, "title": "修改文件信息", "id": "section-24" }, { "level": 3, "title": "PDF 第 14 页", "id": "pdf-14" }, { "level": 3, "title": "删除文件(到回收站）", "id": "section-26" }, { "level": 3, "title": "删除文件（从回收站）", "id": "section-28" }, { "level": 3, "title": "清空回收站", "id": "section-30" }, { "level": 3, "title": "恢复文件（从回收站）", "id": "section-32" }, { "level": 3, "title": "PDF 第 15 页", "id": "pdf-15" }, { "level": 3, "title": "获取文件的所有版本信息", "id": "section-34" }, { "level": 3, "title": "设置文件当前版本", "id": "section-36" }, { "level": 3, "title": "移动文件", "id": "section-38" }, { "level": 3, "title": "拷贝文件", "id": "section-40" }, { "level": 3, "title": "PDF 第 16 页", "id": "pdf-16" }, { "level": 3, "title": "拷贝文件进度", "id": "section-42" }, { "level": 3, "title": "文件日志", "id": "section-44" }, { "level": 3, "title": "设置用户是否有权访问素材库", "id": "section-46" }, { "level": 3, "title": "PDF 第 17 页", "id": "pdf-17" }, { "level": 3, "title": "创建素材库分类", "id": "section-48" }, { "level": 3, "title": "创建子素材库", "id": "section-50" }, { "level": 2, "title": "共享文件相关 API", "id": "api-4" }, { "level": 3, "title": "PDF 第 18 页", "id": "pdf-18" }, { "level": 3, "title": "获取文件的分享 url", "id": "url-12" }, { "level": 3, "title": "获取分享的权限列表", "id": "section-53" }, { "level": 3, "title": "获取用户对于单个文件有权设置的分享角色", "id": "section-55" }, { "level": 3, "title": "创建链接分享", "id": "section-57" }, { "level": 3, "title": "PDF 第 19 页", "id": "pdf-19" }, { "level": 3, "title": "关闭链接分享", "id": "section-59" }, { "level": 3, "title": "设置链接分享密码", "id": "section-61" }, { "level": 3, "title": "邀请人员参与分享", "id": "section-63" }, { "level": 3, "title": "PDF 第 20 页", "id": "pdf-20" }, { "level": 3, "title": "获取所有分享参与人", "id": "section-65" }, { "level": 3, "title": "设置分享参与人的权限角色", "id": "section-67" }, { "level": 3, "title": "删除分享参与人", "id": "section-69" }, { "level": 3, "title": "PDF 第 21 页", "id": "pdf-21" }, { "level": 3, "title": "提醒关注", "id": "section-71" }, { "level": 3, "title": "移除某人的关注", "id": "section-73" }, { "level": 3, "title": "获取关注文件的用户列表", "id": "section-75" }, { "level": 3, "title": "获取可以关注文件的用户列表，并且标记已关注文件的用户", "id": "section-77" }, { "level": 3, "title": "PDF 第 22 页", "id": "pdf-22" }, { "level": 2, "title": "企业部门相关 API", "id": "api-5" }, { "level": 3, "title": "获取当前企业信息", "id": "section-79" }, { "level": 3, "title": "获取企业所有部门信息", "id": "section-81" }, { "level": 3, "title": "创建企业部门", "id": "section-83" }, { "level": 3, "title": "PDF 第 23 页", "id": "pdf-23" }, { "level": 3, "title": "获取部门角色列表", "id": "section-85" }, { "level": 3, "title": "添加部门人员", "id": "section-87" }, { "level": 3, "title": "PDF 第 24 页", "id": "pdf-24" }, { "level": 3, "title": "删除部门人员", "id": "section-89" }, { "level": 3, "title": "获取自己所在部门信息", "id": "section-91" }, { "level": 3, "title": "获取部门人员", "id": "section-93" }, { "level": 3, "title": "PDF 第 25 页", "id": "pdf-25" }, { "level": 3, "title": "添加企业成员", "id": "section-95" }, { "level": 3, "title": "更新成员信息", "id": "section-96" }, { "level": 3, "title": "PDF 第 26 页", "id": "pdf-26" }, { "level": 3, "title": "获取企业成员信息", "id": "section-97" }, { "level": 3, "title": "获取企业所有成员", "id": "section-99" }, { "level": 3, "title": "获取企业日志", "id": "section-101" }, { "level": 3, "title": "PDF 第 27 页", "id": "pdf-27" }, { "level": 2, "title": "消息推送 API", "id": "api-6" }, { "level": 3, "title": "发布公告", "id": "section-103" }, { "level": 3, "title": "获取发布的公告", "id": "section-105" }, { "level": 3, "title": "发送部门讨论", "id": "section-107" }, { "level": 3, "title": "PDF 第 28 页", "id": "pdf-28" }, { "level": 3, "title": "获取部门讨论", "id": "section-109" }, { "level": 3, "title": "获取企业日志", "id": "section-111" }, { "level": 3, "title": "PDF 第 29 页", "id": "pdf-29" }, { "level": 2, "title": "四、 JWT token 登录", "id": "jwt-token" }, { "level": 3, "title": "PDF 第 30 页", "id": "pdf-30" }, { "level": 2, "title": "五、 附录 通用 API 调用返回状态码", "id": "api-7" }, { "level": 2, "title": "状态码 result code", "id": "result-code" } ], "images": [], "text": "API 完整接口资料 PDF 第 1 页 企业开发 API V6.6 上海画擎信息科技有限公司 姜大军 PDF 第 2 页 目录 一、 获取企业开发账号 ..............................................................................................................................................................................4 二、 认证 API ............................................................................................................................................................................................. 6 认证接口一（登录回调方式） ................................................................................................................................................................6 认证接口二（免登录方式 – JWT token 方式，在私有云部署中，需要开启 jwt token 的登录方式） ....................................... 6 获取 token .................................................................................................................................................................................................8 刷新 token .................................................................................................................................................................................................8 三、 文件访问 API ..................................................................................................................................................................................... 8 获取文件列表 ............................................................................................................................................................................................9 获取文件信息 ............................................................................................................................................................................................9 创建文件夹 ..............................................................................................................................................................................................10 预上传文件 ..............................................................................................................................................................................................10 上传文件 ..................................................................................................................................................................................................11 获取下载文件地址 ..................................................................................................................................................................................12 获取下载多文件地址 ..............................................................................................................................................................................12 获取下载文件缩略图地址 ......................................................................................................................................................................13 修改文件信息 ..........................................................................................................................................................................................13 修改文件名 ..............................................................................................................................................................................................13 删除文件(到回收站） .............................................................................................................................................................................14 删除文件（从回收站） ..........................................................................................................................................................................14 清空回收站 ..............................................................................................................................................................................................14 恢复文件（从回收站） ..........................................................................................................................................................................14 获取文件的所有版本信息 ......................................................................................................................................................................15 设置文件当前版本 ..................................................................................................................................................................................15 移动文件 ..................................................................................................................................................................................................15 拷贝文件 ..................................................................................................................................................................................................15 拷贝文件进度 ..........................................................................................................................................................................................16 文件日志 ..................................................................................................................................................................................................16 创建素材库分类 ......................................................................................................................................................................................17 创建子素材库 ..........................................................................................................................................................................................17 共享文件相关 API ................................................................................................................................................................................. 17 获取文件的分享 url ................................................................................................................................................................................ 18 获取分享的权限列表 ..............................................................................................................................................................................18 获取用户对于单个文件有权设置的分享角色 ......................................................................................................................................18 创建链接分享 ..........................................................................................................................................................................................18 关闭链接分享 ..........................................................................................................................................................................................19 设置链接分享密码 ..................................................................................................................................................................................19 邀请人员参与分享 ..................................................................................................................................................................................19 获取所有分享参与人 ..............................................................................................................................................................................20 设置分享参与人的权限角色 ..................................................................................................................................................................20 删除分享参与人 ......................................................................................................................................................................................20 提醒关注 ..................................................................................................................................................................................................21 移除某人的关注 ......................................................................................................................................................................................21 获取关注文件的用户列表 ......................................................................................................................................................................21 获取可以关注文件的用户列表，并且标记已关注文件的用户 ..........................................................................................................21 企业部门相关 API ................................................................................................................................................................................. 22 获取当前企业信息 ..................................................................................................................................................................................22 获取企业所有部门信息 ..........................................................................................................................................................................22 创建企业部门 ..........................................................................................................................................................................................22 获取部门角色列表 ..................................................................................................................................................................................23 添加部门人员 ..........................................................................................................................................................................................23 删除部门人员 ..........................................................................................................................................................................................24 获取自己所在部门信息 ..........................................................................................................................................................................24 获取部门人员 ..........................................................................................................................................................................................24 添加企业成员 ..........................................................................................................................................................................................25 更新成员信息 ..........................................................................................................................................................................................25 获取企业成员信息 ..................................................................................................................................................................................26 获取企业所有成员 ..................................................................................................................................................................................26 获取企业日志 ..........................................................................................................................................................................................26 消息推送 API ......................................................................................................................................................................................... 27 发布公告 ..................................................................................................................................................................................................27 获取发布的公告 ......................................................................................................................................................................................27 发送部门讨论 ..........................................................................................................................................................................................27 获取部门讨论 ..........................................................................................................................................................................................28 获取企业日志 ..........................................................................................................................................................................................28 四、 JWT token 登录 .................................................................................................................................................................................29 五、 附录 通用 API 调用返回状态码 ............................................................................................................................................... 30 PDF 第 3 页 状态码 result code ................................................................................................................................................................................. 30 PDF 第 4 页 一、 获取企业开发账号 登录巴别鸟私有云企业管理后台，在首页中设置开发者账号： 打开后填写回调函数地址：http://xxx.xxx.xxx.xxx/public/babelAuthResult.do 填写后点击确定后自动产生开发者 id (client id)和开发者密钥(client secret)： 注：jwtToken 为相应的生成 jwtToken 时的加密密钥。 PDF 第 5 页 PDF 第 6 页 二、 认证 API 认证接口一（登录回调方式） /api/authorize.do HTTP 请求方式 GET URL 参数 参数名 Comment(说明) response type 必须为 code（必填） string client id 开发者的 id（必填） string redirect uri 回调函数地址，需要和注册时保持一致（必填） string data 任意数据，回调时传回 string 例如： /api/authorize.do?response type=code&client id=xxxxx&redirect uri=http://xxx.xxx.xxx&data=xxx 通过浏览器访问 返回结果 如果用户未登录，则会跳转到登录页，登录后如果未授权，则会 302 跳转到授权页，如果用户已经授权，则会 302 跳转到 redirect uri 并且带上授权码和 data，类似于 http://xxx.xxx.xxx?code=xxx&data=xxx code 有效期 5 分钟。 认证接口二（免登录方式 – JWT token 方式，在私有云部署中，需要开启 jwt token 的登录方 式） /api/authorizeByJWT.do HTTP 请求方式 GET URL 参数 参数名 Comment(说明) response type 必须为 code（必填） string client id 开发者的 id（必填） string jwt token Jwt token，（必填） string 是对{client id: xxxxxxx} 加密 形成的字符串 email email(可选), 传入用户的邮箱，以该用户进行登录，不填以企业管理员进行登录，string phone phone(可选), 传入用户的手机号，以该用户进行登录，不填以企业管理员进行登录， string babelId babelId(可选), 传入用户的工号，以该用户进行登录，不填以企业管理员进行登录， string PDF 第 7 页 例如： /api/authorizeByJWT.do?response type=code&client id=xxxxx&jwt token=xxx 说明：使用这个 api，如果不填 email, phone, babelId 系统将自动以管理员身份登录，否则会以 email, phone, babelId 对应的用户去 登录，不会显示登录界面去登录。注（email, phone, babelId）只需其中一个就可。 返回结果 { \"success\": true \"code\": \"xxxxxxxxxxxxxxxxxxxxxxxxx\", } jwt token 为 自己写程序生成 样例代码如下: import java.util.Date; import java.util.HashMap; import java.util.Map; import javax.crypto.SecretKey; import javax.crypto.spec.SecretKeySpec; import io.jsonwebtoken.Claims; import io.jsonwebtoken.JwtBuilder; import io.jsonwebtoken.Jwts; import io.jsonwebtoken.SignatureAlgorithm; import net.sf.json.JSONObject; / 生成标准 jwt 使用的 token / public class JWT App { static String skey = \"babeldfdfer95840834 t8e 9 9 5934 5943 5886256\"; // 密钥 在巴别鸟后台 开发者账号处 填入的 jwtToken 字段。 public static void main( String[] args ) { HashMap clientInfo = new HashMap (); clientInfo.put(\"client id\", \"7459492016147273\"); // 为开发者账户中的 client id try { String token = createTokenJWT(clientInfo); System.out.println(\" login token:\" + token); String token1 = \"eyJhbGciOiJIUzI1NiJ9.eyJkdXJhdGlvbiI6NjAsInBheWxvYWQiOnsiY2xpZW50X2lkIjoiNzQ1OTQ5MjAxNjE0NzI3MyJ9LCJ0aW1lIjoxNjkxNDg4MzY4NTk0fQ.pRFCwXd2snMr IgFWOFwYbvyAeeNhoFINGk Wmv7d24g\"; JSONObject parsed = parseTokenJWT(token1); System.out.println(\" parsed:\" + parsed); System.out.println(\" 将此 token 作为参数放在 url 中即可， 如:\"); } catch (Exception e) { System.out.println(e.getMessage()); } } public static String createTokenJWT(Map config) throws Exception { HashMap data = new HashMap (); data.put(\"time\", new Date().getTime()); data.put(\"duration\", 60); data.put(\"payload\", config); SignatureAlgorithm signatureAlgorithm = SignatureAlgorithm.HS256; SecretKey key = generalKey(); JwtBuilder builder = Jwts.builder() .setClaims(data) .signWith(signatureAlgorithm, key); System.out.println( \" builder :\" + builder); return builder.compact(); } public static JSONObject parseTokenJWT(String jwt) throws Exception { SecretKey key = generalKey(); Claims claims = Jwts.parser() .setSigningKey(key) .parseClaimsJws(jwt) .getBody(); System.out.println(\" claims:\" + claims.toString()); Long time = (Long)claims.get(\"time\"); long duration = (Integer)claims.get(\"duration\"); Long now = new Date().getTime(); if (now time 1000 duration) return null; // 超过 10 分钟的 token 无效 JSONObject obj = JSONObject.fromObject(claims.get(\"payload\")); return obj; } public static SecretKey generalKey(){ String stringKey = skey; byte[] encodedKey = stringKey.getBytes(); SecretKey key = new SecretKeySpec(encodedKey, 0, encodedKey.length, \"HmacSHA256\"); return key; } } PDF 第 8 页 获取 token /api/token.do HTTP 方法： POST HTTP Header 该接口使用 Basic Auth 的方式校验 client 的信息。具体做法是在 header 中添加类似于\"Authorization: Basic xxxxxxxxx\"。其中 \"xxxxxxxxx\"是通过开发者 id (client id)和开发者秘钥(client secret)算出来的，具体算法为 Base64Encode(client id + \":\" + client secret) Base64Encode 自行选择工具进行 Base64 编码 URL 参数 参数名 Comment(说明) grant type（必填） 必须为 authorization code string code（必填） 授权码，即回调地址接收到的授权码，授权码的有效期为 5 分钟，用过一次，无论成功 还是失败，授权码都会失效 string 例如： /api/token.do?grant type=authorization code&code=xxx&redirect uri=http://xxx.xxx.xxx 返回结果 access token 接口访问标识 refresh token 用来刷新 access token，有效时间为 30 天 expires in access token 的有效时间，单位为 s 刷新 token /api/refreshToken.do HTTP 方法： POST HTTP Header 该接口使用 Basic Auth 的方式校验 client 的信息。具体做法是在 header 中添加类似于\"Authorization: Basic xxxxxxxxx\"。其中 \"xxxxxxxxx\"是通过 client id 和 client secret 算出来的，具体算法为 Base64Encode(client id + \":\" + client secret) URL 参数 参数名 Comment(说明) grant type（必填） 必须为 refresh token string refresh token（必填） 即接口 2 中获取到的 refresh token string 例如： /api/refreshToken.do?grant type=refresh token&refresh token=xxx 返回结果 access token 接口访问标识, refresh token 用来刷新 access token，有效时间为 30 天 expires in access token 的有效时间 为 3600，单位为 s 三、 文件访问 API 所有的接口在访问时需要在 HTTP header 中带上 access token。对于含有请求参数的接口，通常是一些 POST、 PUT 或者 DELETE 接口，还需要设置 Content Type 来指定参数的格式。如果需要访问不同版本的 API，就需要 在请求路径上指定具体版本，如果需要返回不同格式的 response body，那么还需要设置 Accept。所有的参数都应 该采用 utf 8 的编码。 PDF 第 9 页 Headers： Authorization：存放 access token，格式为：\"Bearer \" + access token。 Content Type：指明请求参数的格式。如果是 POST、PUT 或者 DELETE 请求，需要指定\"application/json\"，我 们目前不支持其他请求参数的格式，比如 xml。如果是其他类型比如 GET 请求，可以不在 header 中设置 Content Type。 Accept：用于指定响应结果的格式以及 api 的版本信息。目前只支持返回 json 格式的 response，所以一般情况下 指定\"application/json\"。 若接口访问成功，我们会返回 json 格式的 response，并且 HTTP 的 status code 为 200。所有请求成功的 response 的 json 都会带有\"success: true”。response 的 header 里的 X Babel Version 表示此次请求访问的 api 的版本号。 获取文件列表 /nd/api/file/list dir HTTP 方法： GET URL 参数 参数名 Comment(说明) parent id 父文件夹 id（必填） string 当 parent 为 1 时返回企业文件夹内容，2 返回个人文件夹内容，3 返回我的 项目，4 返回我加入的分享，其它 fileId 返回正常的文件夹中的内容。 page size 页的大小 number page 页号 number type 类型：分为 1 file，2 folder，0 all 三种类型 string 返回字段说明 属性名 类型 说明 files 数组 文件信息 {fileId, name, …} total int 总数量 page int 页容量 success boolean 获取成功标记 code int 返回错误码 0 表示成功 获取文件信息 /nd/api/file/fileinfo HTTP 方法： GET URL 参数 参数名 Comment(说明) id 文件 id（必填） string 返回字段说明 fileInfo 信息 属性名 类型 说明 file Object 文件信息 { id, name, …} PDF 第 10 页 success boolean 获取成功标记 code int 返回错误码 0 表示成功 创建文件夹 /nd/api/file/create folder HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) parent id 目标文件夹 id（必填） string name 文件名（必填） string 返回字段说明 属性名 类型 说明 file Object 文件信息 { id, name, …} success boolean 获取成功标记 code int 返回错误码 0 表示成功 预上传文件 用于返回第二步上传文件时所需要的参数(url、upload token) /api/file/preUploadFile.do HTTP 方法： GET URL 参数 参数名 Comment(说明) parent id 目标文件夹 id（必填）(在根目录下上传可忽略此项) string name 文件名（必填） string file id 上传新版本时需要指定上传那个文件的新版本(上传新文件可忽略此项) string 正确的返回结果如下 {\"upload token\":\"92808ecfc2ac4e0ebc0b912edac3be4a\",\"url\":\"http://testdocument.babel.cc/api/file/uploadPdf.do\",\"su ccess\":true,\"code\":0} 返回字段说明 属性名 类型 说明 url string 该 url 仅能使用 1 次，且有效期为 1 小时 调用此 url 上传文件，成功后会返回 fileId， fileName、version 等 upload token string 上传文件时作为 post 的参数 PDF 第 11 页 上传文件 注意，本 api 的 url 是预上传接口返回的, 这里没有具体的 url，只是参数说明 https://xxx.xxx.xxx:xxx/api/file/uploadXXX.do（具体的 url 是由上一节 /api/file/preUploadFile.do 中返回的 url） POST POST 请求体参数 参数名 Comment(说明) file 文件二进制数据(上传数据) upload token /api/file/preUploadFile.do 请求中的返回值 返回信息如下 {\"fileId\":\"7728538212615908\",\"version\":0,\"fileName\":\"mesos.pdf\",\"fileSize\":848854,\"success\":true,\"code\":0} 上传相关代码 示例 加入 ‘com.squareup.okhttp3:okhttp:3.3.1’ 包 private void uploadFile(final String fileName, String parentId, final DaoCallback callback){ preUploadFile(fileName, parentId, new DaoCallback () { @Override public void onSuccess(JSONObject data) { int code = data.optInt(\"code\", 1); final String url = data.optString(\"url\", null); final String uploadToken = data.optString(\"upload token\"); if (code == 0) { // File file = new File(filePath); RequestBody fileContent = RequestBody.create(MultipartBody.FORM, file); RequestBody requestBody = new MultipartBody.Builder() .setType(MultipartBody.FORM) .addFormDataPart(\"file\", fileName, fileContent) .addFormDataPart(\"upload token\", uploadToken) .build(); Request request = new Request.Builder() .url(url) .post(requestBody) .build(); // 上传需要较长的时间，因此需要设置较长的 timeout OkHttpClient okHttpClient = new OkHttpClient(); okHttpClient.newCall(request) .enqueue(new okhttp3.Callback() { @Override public void onFailure(okhttp3.Call call, IOException e) { callback.onFailure( 1, null); } @Override public void onResponse(okhttp3.Call call, okhttp3.Response response) throws IOException { int httpCode = response.code(); if (httpCode == 200) { try { JSONObject result = new JSONObject(response.body().string()); response.body().close(); boolean success = result.getBoolean(\"success\"); if (success) { callback.onSuccess(null); } else { int code = result.getInt(\"code\"); String msg = result.optString(\"msg\"); callback.onFailure(code, msg); } } catch (JSONException e) { callback.onFailure( 2, null); } } else { callback.onFailure(httpCode, null); } } }); } } @Override public void onFailure( int errorCode, String msg){ Log.e(\"FileTransfer\", \"filePreUpload 失败 errorCode=\" + errorCode); } }); } PDF 第 12 页 private void preUploadFile(String fileName, String parentId, final DaoCallback callback) { String preUploadUrl = \"http://private.babel.cc:80/api/file/preUploadFile.do?name=1234.jpg&parent id=0\"; // 传入相应的参数 name, parent id String authorization = \"Bearer d48d0a0e253c4a2985d8c5653f717d71\"; //根据说明 生成 Request request = new Request.Builder().url(preUploadUrl) .addHeader(\"Authorization\", authorization) .build(); OkHttpClient okHttpClient = new OkHttpClient(); okHttpClient.newCall(request).enqueue(new okhttp3.Callback() { @Override public void onFailure(okhttp3.Call call, IOException e) { Log.d(\"\", \"\"); } @Override public void onResponse(okhttp3.Call call, okhttp3.Response response) throws IOException { Log.d(\"\",\"\"); int httpCode = response.code(); if (httpCode == 200) { JSONObject result = null; try { result = new JSONObject(response.body().string()); } catch (JSONException e) { e.printStackTrace(); } try { boolean success = result.getBoolean(\"success\"); if (success) { String url = result.getString(\"url\"); callback.onSuccess(result); } else { int code = result.getInt(\"code\"); String msg = result.optString(\"msg\"); callback.onFailure(code, msg); } } catch (JSONException e) { callback.onFailure( 2, null); } } else { callback.onFailure(httpCode, null); } } }); } 获取下载文件地址 /api/file/getFileDownloadUrl.do HTTP 方法： GET URL 参数 参数名 Comment(说明) fileId 需要下载的文件 id（必填） string version 文件的版本号（可选） number 返回信息如下 {\"code\":0,\"success\":true,\"type\":\"文件类型\",\"url\":\"文件下载地址\"} 获取下载多文件地址 /api/file/downloadMultiFiles.do HTTP 方法： GET URL 参数 参数名 Comment(说明) fileIdArr 由需要下载的文件 id 组成的字符串，由符号“!“(半角)分割，比如下载 id 为 133 与 233 的两 个文件，则 fileIdArr 的值为“133!233” string 类型 PDF 第 13 页 返回信息如下 {\"code\":0,\"success\":true,\"type\":\"文件类型\",\"url\":\"文件下载地址\"} 返回值 url 为多个文件打包后的下载地址。 获取下载文件缩略图地址 /api/file/downloadThumbnail.do HTTP 方法： GET URL 参数 参数名 Comment(说明) fileId 需要下载的文件 id（必填） string version 文件的版本号（可选） number size 需要显示的缩略图尺寸，取宽高中的最大值 返回信息如下 {\"code\":0,\"success\":true, \"url\":\"文件下载地址\"} 返回值 url 为多个文件打包后的下载地址。 修改文件信息 /nd /api/file/update file HTTP 方法： POST 修改文件信息 POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填） string name 新文件名 （可选） string description 文件说明 （可选） string 返回信息如下 {\"code\":0,\"success\":true} 修改文件名 /nd /api/file/rename HTTP 方法： POST 修改文件信息 POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填） string name 新文件名 string 返回信息如下 {\"code\":0,\"success\":true} PDF 第 14 页 删除文件(到回收站） /nd /api/file/remove file HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file ids[] 目标文件 id 数组（必填） string[] 返回信息如下 {\"code\":0,\"success\":true} 删除文件（从回收站） /nd /api/file/remove from trash HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file ids[] 目标文件 id 数组（必填） string[] 返回信息如下 {\"code\":0,\"success\":true} 清空回收站 /nd /api/file/empty trash HTTP 方法： POST POST 请求体参数 参数名 说明 返回信息如下 {\"code\":0,\"success\":true} 恢复文件（从回收站） /nd /api/file/restore file HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file ids[] 目标文件 id 数组 string[] restoreAll 不填写 file ids, restoreAll 为 true，时恢复回收站中所有文件，boolean 返回信息如下 PDF 第 15 页 {\"code\":0,\"success\":true} 获取文件的所有版本信息 /nd /api/file/versions HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 目标文件 id（必填） string 返回信息如下 {\"code\":0,\"versions\":[],\"success\":true} 设置文件当前版本 /nd /api/file/version HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file id 目标文件 id （必填） string version 版本号（必填） number 返回信息如下 {\"code\":0,\"success\":true} 移动文件 /nd /api/file/move HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file ids 需要移动的目标文件 id 数组（必填） string target id 需要移动到的目标文件夹 id（必填） string 返回信息如下 {\"code\":0,\"success\":true} 拷贝文件 /nd /api/file/copy HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) PDF 第 16 页 file ids 需要拷贝的目标文件 id 数组（必填） string target id 需要拷贝到的目标文件夹 id（必填） string 返回信息如下 { \"code\": 0, \"copyKey\": \"81427630 054a 11ef 8355 db93b4b1d006\",\"fileNum\": 10, \"success\": true} 拷贝文件进度 /nd /api/file/copy progress HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) copyKey 查看拷贝进度 copyKey 由 copy 接口返回（必填） string 返回信息如下 { \"code\": 0, \"completed\": 10,\"total\": 10, \"result\": {}, \"success\": true} 文件日志 /nd /api/file/file logs HTTP 方法： GET GET 请求体参数 参数名 Comment(说明) file id 目标文件 id 数组（必填） string startIndex 获取日志的起始顺序 第几条日志开始返回（选填） int 默认 0， pageSize 每页返回的个数（选填） int type 日志类型(选填) int 默认 0, 查看所有记录， 1 仅查看访问记录，2 仅查看上传下载，3 仅查看匿名用 户，4 仅查看分享及邀请，5 仅查看删除记录 userName 某个用户名 (选填) string, 返回某个用户的日志 lang 语言(选填) 默认 cn, string 返回日志的语言 cn(中文) en(英文) 返回信息如下 {\"code\":0,\"success\":true, \"logs\":[], \"total\":50} 设置用户是否有权访问素材库 /nd /api/file/ set user access material library HTTP 方法： POST GET 请求体参数 参数名 Comment(说明) userId 用户的 id 数组数型 [usrId1, userId2]（必填） string can 是否可访问 数值类型 （必填） int 默认 0， 0： 不可访问， 1:可以访问 返回信息如下 {\"code\":0,\"success\":true} PDF 第 17 页 创建素材库分类 /nd /api/file/create material class HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) destDirFileId 目标文件夹 的 fileId（必填） string name 创建分类库的名称（必填） string accessType 分类可见性 (选填) 默认为公开 0. 0: // 公开 1: // 需要申请 2: // 部门公开 3: // 部门申请 4: // 保密 managerIds 负责人的 id 数组类型 [usrId1,userId2] departmentIds 分类可见性 限定部门 的部门 id (选填) 数组类型 [departmentId1,departmentId2] 返回信息如下 {\"code\":0, \"success\":true, \"materialClass\": {}} 创建子素材库 /nd /api/file/create material folder HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) destDirFileId 目标文件夹 的 fileId（必填） string name 创建分类库的名称（必填） string accessType 分类可见性 (选填) 默认为公开 0. 0: // 公开 1: // 需要申请 2: // 部门公开 3: // 部门申请 4: // 保密 managerId 负责人的 id (选填) string departmentIds 分类可见性 限定部门 的部门 id (选填) 数组类型 [departmentId1,departmentId2] assistantIds 素材库助理人员的 id （选填） 数组类型 [usrId1,userId2] 返回信息如下 {\"code\":0, \"success\":true, \"materialFolder\": {}} 共享文件相关 API PDF 第 18 页 获取文件的分享 url /nd/api/share/shareurl HTTP 方法： GET 获取文件的分享链接（先打开分享后，再获取该链接） URL 参数 参数名 Comment(说明) file id 文件 id string is https 返回的 share url 协议是否为 https 0 为 http, 1 为 https， 默认 0 number 返回字段说明 {\"code\":0,\"url\":\"https://private.babel.cc/share.do?s=http://private.babel.cc/share.do?s=MjY2OTYzNTk3OTU2NzEzOTtXZWQgSnVsIDAxIDIwMj AgMTg6MzM6NTAgR01UKzA4MDAgKEhvbmcgS29uZyBTdGFuZGFyZCBUaW1lKQ%3D%3D\",\"success\":true} 获取分享的权限列表 /nd/api/share/share roles HTTP 方法： GET URL 参数 参数名 Comment(说明) 返回字段说明 {\"code\":0,\"roles\":[],\"success\":true} 获取用户对于单个文件有权设置的分享角色 /nd/api/share/share role forfile HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 文件 id string 返回字段说明 {\"code\":0,\"roles\":[],\"success\":true} 创建链接分享 /nd/api/share/open link share HTTP 方法： POST 打开分享，获取新的分享链接，之前的链接失效。 PDF 第 19 页 POST 请求体参数 参数名 Comment(说明) file id 预分享的文件 id（必填） string link role id 分享的角色 string is https 返回的 share url 协议是否为 https number anonymousVisit 是否允许匿名访问，1 为允许，0 为不允许（可选，默认为 1） number 返回字段说明 {\"code\":0,\"share url\":\"http://private.babel.cc/share.do?s=http://private.babel.cc/share.do?s=MjY2OTYzNTk3OTU2NzEzOTtXZWQgSnV sIDAxIDIwMjAgMTg6MzM6NTAgR01UKzA4MDAgKEhvbmcgS29uZyBTdGFuZGFyZCBUaW1lKQ%3D%3D\",\"password\":\"\",\"success\":tru e} 关闭链接分享 /nd/api/share/close link share HTTP 方法： POST 关闭我打开的分享链接 POST 请求体参数 参数名 Comment(说明) file id 分享的文件 id（必填） string 返回字段说明 {\"code\":0,\"success\":true} 设置链接分享密码 /nd/api/share/set share password HTTP 方法： POST 文件链接分享已打开，设置链接分享的密码。 POST 请求体参数 参数名 Comment(说明) file id 预分享的文件 id（必填） string password 链接分享的密码 string is https 返回的 share url 协议是否为 https number 返回字段说明 {\"code\":0,\"success\":true, \"share url\": \"http://private.babel.cc/share.do?s=xxxxxxxxxxx\"} 邀请人员参与分享 /nd/api/share/invite share HTTP 方法： POST PDF 第 20 页 可以根据用户的邮箱或者手机来邀请某些人来访问文件 POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填） string share role 分享的权限的 id（以上所有人共享此权限）（必填） string emails[] 邮箱数组 string[] phones[] 手机号的数组 string[] 返回字段说明 {\"code\":0,\"success\":true} 获取所有分享参与人 /nd/api/share/share participants HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 文件 id（必填） string 返回字段说明 {\"code\":0,\"users\":[],\"success\":true} 设置分享参与人的权限角色 /nd/api/share/set participant role HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填） string babelshare id int（必填） 用户 id string role id int（必填） 角色 id string 返回字段说明 {\"code\":0,\"success\":true} 删除分享参与人 /nd/api/file/remove share participant HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) PDF 第 21 页 file id 文件 id（必填） string babelshare ids[] int （必填） 用户 id string 返回字段说明 {\"code\":0,\"success\":true} 提醒关注 /nd/api/file/focus file HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填） string user ids[] 提醒的用户的 id，此 id 应该在文件参与人中选取，否则提醒不会起作用（必填）string[] 返回字段说明 {\"code\":0,\"success\":true} 移除某人的关注 /nd/api/file/unfocus file HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填）string user ids[] 提醒的用户的 id，此 id 应该在文件参与人中选取，否则提醒不会起作用（必填） string[] 返回字段说明 {\"code\":0,\"success\":true} 获取关注文件的用户列表 /nd/api/file/user focusfile HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 文件 id（必填） string 返回字段说明 {\"code\":0,\"users\":[],\"success\":true} 获取可以关注文件的用户列表，并且标记已关注文件的用户 /nd/api/file/user can focusfile PDF 第 22 页 HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 文件 id（必填） string 返回字段说明 企业部门相关 API 获取当前企业信息 /nd/api/enterprise/current HTTP 方法： GET URL 参数 参数名 Comment(说明) 无 返回字段说明 {\"code\":0,\"enterprise\":{},\"success\":true} 获取企业所有部门信息 /nd/api/enterprise/departments HTTP 方法： GET URL 参数 参数名 Comment(说明) 无 返回字段说明 属性名 类型 说明 departments []数组 返回所有的部门信息 tree {}json 数据 返回部门的父子结构信息 code int sucess boolean 创建企业部门 /nd/api/enterprise/create department HTTP 方法： POST PDF 第 23 页 POST 请求体参数 参数名 Comment(说明) parent dep 父部门 id， 0 表示跟部门（必填）string name 部门名称（必填）string description 部门描述 string 返回字段说明 属性名 类型 说明 department {} json 数据结构 code int sucess boolean 获取部门角色列表 /nd/api/enterprise/dep role HTTP 方法： GET URL 参数 参数名 Comment(说明) 返回字段说明 属性名 类型 说明 roles []数组 { id, filePermission,enterpriseId,filePermission,managerPermission, default,nameEn,name} code int sucess boolean 添加部门人员 /nd/api/enterprise/add dep mem HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) department id 部门 id（必填）string user ids[] 用户列表 string[] role id 用户在部门中的角色 string PDF 第 24 页 返回字段说明 属性名 类型 说明 删除部门人员 /nd/api/enterprise/remove dep mem HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) department id 部门 id（必填）string user ids[] 人员的 id（必填）string[] 返回字段说明 属性名 类型 说明 获取自己所在部门信息 /nd/api/enterprise/mydeparments HTTP 方法： GET URL 参数 参数名 Comment(说明) 无 返回字段说明 属性名 类型 说明 departments []数组 返回我所在的部门信息 code int sucess boolean 获取部门人员 /nd/api/enterprise/departmentmembers PDF 第 25 页 HTTP 方法： GET URL 参数 参数名 Comment(说明) department id 部门 id（必填）string 返回字段说明 属性名 类型 说明 users 数组 ： {id, name, avatrUrl,} 添加企业成员 /nd/api/enterprise/add ent mem HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) email Email 邮箱 string password 密码 string enterprise role 企业成员角色, 可选 number department ids[] 该用户的部门， 可选 string[] department roles[] 在部门中的角色， 可选 string[] sex 性别 0 未设置 1 男 2 女 number name 用户名 string phone 手机号， 可选 string babelId 工号，可选 string spacelimit 个人空间限制，单位 GB, 0 表示不限制 number can ownfile 用户能否拥有个人文件， 1 使用企业总体设置, 0 没有个人文件, 1 有个人文件 number remarks 用户描述， 可选 string join time 用户加入企业时间，Unix time, 单位秒 number password is md5 传入密码是否需要 md5 加密, 0 非 md5 密码， 1 md5 加密过的密码 number 更新成员信息 /api/updateUserInfo.do HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) email 邮箱地址（搜索关键字，必须）string password 密码（修改密码，可选）string frozen 1 – 表示冻结， 0 – 表示解冻 （冻结该账号，可选）number password is md5 传入密码是否需要 md5 加密, 0 非 md5 密码， 1 md5 加密过的密码 number phone 手机号 (可选) string PDF 第 26 页 获取企业成员信息 /api/getEnterpriseMember.do HTTP 方法： GET URL 参数 参数名 Comment(说明) email 邮箱地址（搜索关键字）string phone 手机号（搜索关键字）string babelId 工号（搜索关键字）string email/phone/babelId 可选择其一 返回字段说明 {\"code\":0,\"success\":true,\"user\":{}} 获取企业所有成员 /nd/api/enterprise/enterprise members HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) lang 语言类型，cn 中文 ，en 英文 , 可选 options { departmentId: // 部门 id，不填写就是企业所有人员 roleId: // 角色 id， 不填写就是不限角色 \"userType\": 0, // 0 企业内人员， 1 外部人员 \"keyName\": \"\", // 搜索关键字： 人名，手机号，邮箱， 不填写就是所有人员 \"startIndex\": 0， \"pageSize\": 20, status: // 0 所有账号， 1 停用的账号 } 可选 返回字段说明 {\"code\":0,\"success\":true,\"members\":{},\"total\":xx} 获取企业日志 /nd/api/enterprise/enterprise logs HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) department id 部门 id，不填写就是所有部门的日志 string 可选 keyword 日志的相关搜索关键字 string 可选 PDF 第 27 页 startTime 日志起始时间 number 可选 endTime 日志截止时间 number 可选 startIndex int 可选 pageSize int 可选 返回字段说明 {\"code\":0,\"success\":true,\"logs\":{},\"total\":xx} 消息推送 API 发布公告 /nd/api/enterprise/broadcast HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) title 公告内容字符串（必填） string content 内容（必填）string target users[] UserId 数组，如果为空则表示全部人员接收，string[] target deps[] 目标部门，该部门及子部门所有成员都会收到通知，string[] target users 与 target deps 至少要填 1 个 返回字段说明 {\"code\":0,\"success\":true} 获取发布的公告 /nd/api/enterprise/broadcast HTTP 方法： GET URL 参数 参数名 Comment(说明) start index number pagesize number 返回字段说明 {\"code\":0,\"broadcasts\":[],\"total\":19,\"success\":true} 发送部门讨论 /nd/api/file/send dep discussion HTTP 方法： POST PDF 第 28 页 POST 请求体参数 参数名 Comment(说明) dep id 部门 id（必填） string message 信息字符（必填） string json 字符串, 格式{Type: “Text”, Body:”你好” } 返回字段说明 {\"code\":0,\"messageId\":99,\"success\":true} 获取部门讨论 /nd/api/file/dep discussion HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) dep id 部门 id（必填）string pagesize 页的大小 string start id 消息 id,只会获取此消息之前的消息，为空则获取最新消息 string 返回字段说明 {\"msgArr\":[],\"gotMoreMessages\":1,\"code\":0,\"success\":true} 获取企业日志 /nd/api/enterprise/enterprise logs HTTP 方法： GET URL 参数 参数名 Comment(说明) department id 部门 id（）string pagesize 页的大小 number，默认值 1000 start index 消息起始位置, number keyword 日志关键词 string startTime 起始日期: 秒 number endTime 截止日期 秒 number 返回字段说明 {\"logs\":[],\"total\":0,\"code\":0,\"success\":true} total 返回所有符合条件的(与分页 pageSize 无关) PDF 第 29 页 四、 JWT token 登录 在私有云部署中，可以开启 jwt token 的登录方式，在这种情况下，允许通过下面的 url 直接以某用户的身份免登录进入网盘系 统： /account/tokenLogin.do 参数： 参数名称 可选性 说明 可选值 默认值 userToken 必填 含有登录用户的加密信息（构造方 无 法详见下面的说明） fileId 可选 要访问的文件（夹）的 id，如果不 无 填写则打开用户根目录 closeTitleBar 可选 是否关闭标题栏 1 关闭 0 不关闭 0 disableEntMark 可选 是否隐藏左上角企业标识 1 隐藏 0 不隐藏 0 disableUserMark 可选 是否隐藏右上角用户设置入口 1 隐藏 0 不隐藏 0 defaultLang 可选 设置界面使用的语言 cn 中文 en 英文 zh HK 繁体 cn defaultClrTheme 可选 设置界面颜色主题 normal 标准模式，dark 暗色模式 normal 比如下面是以英文及暗色模式并隐藏右上角用户标志进入用户根目录界面 /account/tokenLogin.do userToken=xxxxxxxxxxxxxxxx defaultClrTheme=dark defaultLang=en disableUserMark=1 userToken 的构建 userToken 是含有登录用户信息的加密字符串，加密信息是通过标准的双方传输可信数据的安全机制 JWT 创建的口令字， JWT 加密的用户信息 JSONObject 内容如下： { payload: { email: “xxx@xxx.com”/“135XXXXXXX”/“XXXX”} time: now } 说明：其中 email, 可以是邮箱，手机号，工号； 代码如下： public static void main( String[] args ) { HashMap user = new HashMap (); user.put(\"email\", \"yuanchaozhao@qq.com\"); try { //token login String userToken = createTokenJWT(user); System.out.println(\" login token:\" + userToken); JSONObject parsed = parseTokenJWT(userToken); System.out.println(\" parsed:\" + parsed); System.out.println(\" 将此 token 作为参数放在 url 中即可， 如:\"); System.out.println(\"/account/tokenLogin.do?userToken=\" + userToken); } catch (Exception e) { System.out.println(e.getMessage()); } } 其它代码 参考 jwtToken 的生成代码，在认证接口二处有提供。 备注： JWT 即 JSON Web Tokens 的简写， 是满足工业标准 RFC7519 的一种通信加密解密机制，请参考： https://jwt.io/ PDF 第 30 页 五、 附录 通用 API 调用返回状态码 状态码 result code 码值 说明 0 成功 1 未知错误 2 参数错误 7 空间不足 12 禁止的用户操作 13 无效的 token 结束 the end" }, { "lang": "en", "slug": "private-package-overview", "title": "Private plan overview", "description": "Introducing the applicable scenarios, components, modules and quotation caliber of the BabelBird privatization package.", "category": "Private Plans", "top_category": "私有套餐", "keywords": [ "Private package", "Private Deployment", "Authorize", "module" ], "url": "en/private-package-overview.html", "source": "content/en/private-package-overview.md", "summary": "Private package overview BabelBird's privatization package is aimed at customers who need to integrate and deploy enterprise network disks, permissions, security, AI, online editing and business systems in their own servers, private clouds or controlled cloud environments. The package content usually consists of basic privatization authorization, deployment and implementation, standard function modules, optional value added modules, third party service access, maintenance services and customized development services. Applicable scenarios Enterprises require file data to be stored in their own computer rooms, government and enterprise clouds, dedicated clouds or isolated networks. Requires ac", "headings": [ { "level": 1, "title": "Private package overview", "id": "private-package-overview" }, { "level": 2, "title": "Applicable scenarios", "id": "applicable-scenarios" }, { "level": 2, "title": "Package composition", "id": "package-composition" }, { "level": 2, "title": "Price and quotation caliber", "id": "price-and-quotation-caliber" } ], "images": [], "text": "Private package overview BabelBird's privatization package is aimed at customers who need to integrate and deploy enterprise network disks, permissions, security, AI, online editing and business systems in their own servers, private clouds or controlled cloud environments. The package content usually consists of basic privatization authorization, deployment and implementation, standard function modules, optional value added modules, third party service access, maintenance services and customized development services. Applicable scenarios Enterprises require file data to be stored in their own computer rooms, government and enterprise clouds, dedicated clouds or isolated networks. Requires access to Enterprise WeChat, DingTalk, Feishu, OA, ERP, PDM, AD/SSO or unified identity authentication system. Requires stronger controls such as object storage, data ferrying, departmental security policies, auditing, watermarks, IP policies, and Mac binding. Modular capabilities such as online Office, CAD preview, AI knowledge base, document control projects, automated tasks or electronic signatures are required. Requires white label OEM, process customization, API docking or secondary development around enterprise business. Package composition Composition Description Privatized authorization Product authorization for the Babel Enterprise Private Cloud version, deployed in a server environment prepared by the customer or managed by the customer Standard functions Enterprise network disk, department/project files, permissions, sharing, version, preview, synchronization, mapping disk, log, console, etc. Deployment and implementation The Babel team deploys remotely or on site, issues certificates, debugs services and assists with initialization Optional modules Zhichao AI, document control projects, online Office, data ferry, third party platform access, SMS, signature, CAD/OCR, etc. Storage solutions Local disk, NFS, S3, MinIO object storage or third party object storage Maintenance services Training, Q&A, troubleshooting, version upgrades, configuration support and operation and maintenance cooperation Customized development API docking, process customization, interface reshaping, business system integration and white label services Price and quotation caliber The actual quotation will be affected by the number of users, authorized modules, deployment methods, storage scale, whether on site services are required, and whether customized development and maintenance service cycles are required. The formal business quotation and contract should prevail." }, { "lang": "en", "slug": "private-package-standard", "title": "Standard Privatization Package", "description": "Describe the base product capabilities and default delivery scope included in the standard privatization package.", "category": "Private Plans", "top_category": "私有套餐", "keywords": [ "Standard privatization", "Enterprise Drive", "private deployment" ], "url": "en/private-package-standard.html", "source": "content/en/private-package-standard.md", "summary": "Standard privatization package The standard privatization package inherits the core capabilities of the public cloud Babel and runs in the customer's own environment. It is suitable for organizations that need to uniformly manage corporate files, protect data security, access internal systems, and maintain long term maintainability. Standard capabilities Corporate files, personal files, department folders, project folders and material libraries. File upload, download, chunked transfer, breakpoint resume, incremental upload and download, and deduplication storage. File preview, BabelViewer, annotations, comments, version management, version rollback and version comparison. Department roles, p", "headings": [ { "level": 1, "title": "Standard privatization package", "id": "standard-privatization-package" }, { "level": 2, "title": "Standard capabilities", "id": "standard-capabilities" }, { "level": 2, "title": "Privatized Delivery Instructions", "id": "privatized-delivery-instructions" }, { "level": 2, "title": "Private deployment", "id": "private-deployment" } ], "images": [], "text": "Standard privatization package The standard privatization package inherits the core capabilities of the public cloud Babel and runs in the customer's own environment. It is suitable for organizations that need to uniformly manage corporate files, protect data security, access internal systems, and maintain long term maintainability. Standard capabilities Corporate files, personal files, department folders, project folders and material libraries. File upload, download, chunked transfer, breakpoint resume, incremental upload and download, and deduplication storage. File preview, BabelViewer, annotations, comments, version management, version rollback and version comparison. Department roles, project permissions, file access control, customized file permissions, sharing permissions and log auditing. Windows, macOS, and Kirin clients, including synchronization, transfer management, and virtual mapping disk capabilities. Enterprise console, manages organizational structure, members, roles, tags, watermarks, access logs, statistical analysis, etc. Privatized Delivery Instructions Private deployment The BabelBird public cloud network disk system needs to provide continuous and uninterrupted services to 600,000 users including free users at the same time, block various attacks on the public network, and continuously improve system efficiency to reduce the high cost of public cloud servers. As many as 10 years of experience in uninterrupted public cloud services have made the Babel system time tested. The Babel private cloud system is developed on the basis of the Babel public cloud system. It inherits all the functions and features of the public cloud Babel, and is updated synchronously with the public cloud Babel, providing you with high stability and high availability that other private network disks cannot match. Deployment plan In response to the different IT system construction needs of different enterprises, the Babel privatization system supports a variety of flexible deployment methods and deployment requirements. Whether it is single server, multi server, cluster, hyper converged system, distributed system, third party cloud platform or even Docker deployment, we support it. Our deployment team can work with you to develop a deployment plan based on your needs. At the same time, because private cloud only serves a single enterprise, we can provide optional customization settings that far exceed those of public cloud systems. From interface operations to processes to permissions, everything can be adjusted according to your needs. Recommended server configuration and performance requirements Server type and function: The hardware system required by BabelBird Enterprise Drive consists of two parts: business servers and storage servers. Business servers can be divided into 4 types. These 4 types of services can be deployed in one physical machine or virtual machine according to needs, or can be deployed dispersedly in four or more servers. Therefore, the minimum unit for deploying the Babel system is two physical servers or two virtual machines (one for business and one for storage) Service name Purpose Operating system Main business server web services, load balancing, main business function implementation Linux Database Server Database Service Linux Search server Provides file full text search and advanced search functions Linux Transcoding server Transcode and add watermarks to files that require transcoding preview windows 2012, Linux Storage server Provides file storage Linux In extreme cases, if the hard disk mounted on the server is used as storage space, Babel also supports deploying all services and storage in a physical machine or virtual machine (all in one machine mode). However, considering performance and disaster recovery or future upgrade and expansion issues, such a deployment method is not recommended. The best deployment method we recommend is a small cluster deployment of 4 servers (virtual machines). The main business services and database services are placed on one server, the search server and transcoding server are independent, and then a storage server is added. If the storage space requirement is less than 10TB, a storage server is not required. You can directly mount a hard disk or NFS disk for storage. BabelBird also supports access to third party storage. In theory, as long as the third party storage system supports the NFS or S3 protocol, it can be connected to BabelBird as a storage service. Most storage systems support both protocols. Each server must ensure smooth communication between each other. If the intranet has higher security requirements, please refer to 9.1.2 Ports that need to be opened Minimum performance configuration: The lowest performance configuration of BabelBird can support normal use by about 100 users and manage less than 10TB of data. cpu memory system disk storage disk network operating system 8 core CPU (reference benchmark E5 2609) 32G ECC memory 500G Below 10TB Gigabit Linux Recommended performance configuration examples: The recommended performance configuration of BabelBird can support normal use by 1000 2000 users and manage documents up to 1PB. Babel supports multiple deployment methods, and this instance is the standard deployment method. Use virtual machines to deploy business servers to connect to independent single or multiple object storage servers. Business servers and storage servers are managed separately. Business server: It is recommended that business servers be deployed using virtual machines Number Server type Configuration requirements Operating system Server purpose 1 Virtual machine 8 core CPU 64G memory 500G SSD system disk CentOS8 or openeuler22 Main business server/database 2 Virtual machine 8 core CPU 32G memory 500G SSD system disk CentOS8 or openeuler22 Search server 3 Virtual machine 8 core CPU 16G memory 200G SSD system disk windows 2012 R2 transcoding server The performance of the 8 core CPU should be close to that of the Zhiqiang 4410 BabelBird Enterprise Drive is deployed using Docker. In theory, it can be deployed as long as it is a Linux operating system. CentOS or open Euler is recommended. If there are no ready made virtual machine resources, you need to purchase a new business server. The business server hardware configuration requirements are as follows: Number Server type Configuration requirements Operating system Server purpose 1 Business server Xeon Silver 4210 2 20 core CPU 64G memory 2TB SSD hard drive Linux Main business server It is best to purchase VM for business servers and use virtualization for management. Storage server (object storage): Babel supports building an object storage system on a general purpose server. If the storage space is expected to be less than 100TB, it is recommended to use a single server to build the object storage system. A single object storage can use disks for data verification redundancy, and can be horizontally expanded by adding one storage server at a time. (The expansion operation can be done without stopping the server) It is recommended to use an independent physical machine for the object storage server, and the recommended configuration is as follows: Server type Configuration requirements Operating system Server purpose Notes Storage server If storage density and future expansion investment are considered, a 12T hard drive can be used. Linux Object Storage Server It is recommended to add a server with the same disk capacity for future expansion. If the required storage space is greater than 300TB, multiple servers are required to build a distributed object storage system. BabelBird also supports building distributed object storage systems for customers. To learn about distributed object storage, please refer to the \"Self Built Object Storage\" chapter. Need to open the port For the security of the server system, we need to open only specific ports. The following are the ports that need to be opened: Ports open to the outside world (ports required for external network access): Port number Port purpose Protocol Open host 80 Network disk main business web external access port, not encrypted http main business server 443 Network disk main business web external access port, encrypted https Main business server 3060 Network disk main business node external access port, not encrypted TCP Main business server 3080 Network disk main business node external access port, encryption TCP Main business server Open ports are required between servers (open ports are required for internal server communication): Generally, during actual deployment, only external network ports (external) will be restricted, and internal ports between servers will not be restricted. However, some users who deploy across networks and computer rooms will also need to limit internal ports. Host Port number Port purpose Protocol Target network segment Business server 6379 redis access port for windows transcoding and search server TCP transcoding server and search server Business server 8080 Used by windows transcoding server to access network disk business server TCP Transcoding server and search server Business server 3306 Database port, used by the search server to access the database TCP Transcoding server and search server Business server 9000 Docker cluster deployment, internal visual interface port TCP Transcoding server and search server Business server 111 portmap port TCP+UDP Transcoding server and search server Business server 2049 TCP+UDP TCP+UDP Transcoding server and search server Business server 35000 mountd port TCP+UDP Transcoding server and search server Business Server 2376 docker REST API port for TLS encryption TCP Native Business server 2377 TCP port used for communication related to docker cluster management TCP+UDP Native Business server 7946 TCP and UDP ports, used for communication between docker swarm nodes TCP+UDP Local machine Business server 4789 docker overlay network default port TCP+UDP Local machine Search server 9200 elastic port, used by the main business server TCP business server Search server 5601 Kibana port, internal visual elastic interface access port TCP Business server Search server 9998 tika port, extract document text server port TCP Business server Search server 9000 Docker cluster deployment, internal visual interface port TCP Transcoding server and search server Search Server 2376 docker REST API port for TLS encryption TCP Native Search server 2377 TCP port used for communication related to docker cluster management TCP Native Search server 7946 TCP and UDP ports, used for communication between docker swarm nodes TCP+UDP Local machine Search server 4789 docker overlay network default port TCP+UDP Native Transcoding server Transcoding server Can access the business server Can access the business server Can access the business server Ports that need to be opened during deployment: Port number Port purpose Open server Destination IP address 22 SSH port number, used for SSH access All servers Springboard machine for deployment 443 Obtain authorization All servers 47.96.234.200 443 Get installation source All servers 120.27.245.68 443 Docker installation source All servers 13.35.121.100 POC deployment POC deployment is suitable for users to conduct POC testing in the production environment before selection. POC deployment requirements:" }, { "lang": "en", "slug": "private-package-modules", "title": "Optional modules and value-added capabilities", "description": "Lists optional modules such as Zhichao AI, online editing, data ferrying, document control, third-party access, CAD/OCR/signature, etc.", "category": "Private Plans", "top_category": "私有套餐", "keywords": [ "Optional modules", "Zhichao AI", "Data ferry", "Document control project" ], "url": "en/private-package-modules.html", "source": "content/en/private-package-modules.md", "summary": "Optional modules and value added capabilities The privatized version can enable or access different modules according to enterprise needs. Whether it is actually included in the contract should be based on the quotation, authorization list and implementation plan. Common optional modules Module Description Zhichao AI AI search, AI image search, document assistant, knowledge base robot, custom agent and AI customer service Online Office The default is OnlyOffice, you can also access Office 365, WPS Online, and Yongzhong Office on demand Light document/text/mind map/flow chart Light document, Markdown/code text, KM mind map, draw.io flow chart Data Ferry Secure, auditable, and approvable file ", "headings": [ { "level": 1, "title": "Optional modules and value added capabilities", "id": "optional-modules-and-value-added-capabilities" }, { "level": 2, "title": "Common optional modules", "id": "common-optional-modules" }, { "level": 2, "title": "Third party service access conditions", "id": "third-party-service-access-conditions" } ], "images": [], "text": "Optional modules and value added capabilities The privatized version can enable or access different modules according to enterprise needs. Whether it is actually included in the contract should be based on the quotation, authorization list and implementation plan. Common optional modules Module Description Zhichao AI AI search, AI image search, document assistant, knowledge base robot, custom agent and AI customer service Online Office The default is OnlyOffice, you can also access Office 365, WPS Online, and Yongzhong Office on demand Light document/text/mind map/flow chart Light document, Markdown/code text, KM mind map, draw.io flow chart Data Ferry Secure, auditable, and approvable file transfer between confidential and non confidential areas Document control project Engineering design industry DCC, TRANSMITTAL, dispatch order, recipient and dispatch record management Automated tasks Automatic cleaning, automatic renaming, automatic conversion to PDF, automatic organization, signature, and batch creation of folders Third party platform Enterprise WeChat, DingTalk, Feishu, OA, ERP, PDM, ADFS, SSO Third party capabilities Advanced CAD preview, CAD online editing, OCR, image recognition, electronic signature, DLP Third party service access conditions Access third party services As an office platform centered on corporate documents, the privatized BabelBird Enterprise Drive can easily integrate various third party services into BabelBird to meet different needs by accessing third party APIs. These services include but are not limited to: electronic signature, advanced CAD preview, office, text recognition, image recognition... and other third party services to solve your needs. Conditions for accessing third party services In theory, third party applications or service modules that support the BS architecture can be accessed. Third party services must provide open APIs so that BabelBird Enterprise Drive can be integrated with them If it is an Internet service, the server needs to be able to access the external network. Enterprises need to authorize themselves or entrust us to purchase third party services for access. Recommended accessible services File anti leakage system: ipguard Online office editing: onlyoffice (self contained), office365, WPS Online, Yongzhong office Advanced CAD preview: Haochen Cloud Atlas, Dream CAD CAD online editing: Dream CAD Online signature: Sign on Text recognition and image recognition: Baidu Qianfan (Smart Cloud) AI related: Zhichao AI (self owned), ChatGPT, Zhipu AI" }, { "lang": "en", "slug": "private-package-service", "title": "Service and Maintenance", "description": "Describe the scope of privatized deployment, maintenance, training, upgrades and after-sales services.", "category": "Private Plans", "top_category": "私有套餐", "keywords": [ "maintenance services", "After-sales", "Private Deployment" ], "url": "en/private-package-service.html", "source": "content/en/private-package-service.md", "summary": "Service and Maintenance The privatized system not only includes software licensing, but also includes deployment implementation, initialization, training, maintenance, upgrades and fault response services. The service scope should be confirmed in conjunction with the contract, service order and maintenance period agreement. Excerpt from Private Cloud Service Terms Babel Enterprise Privatization Services Shanghai Huaqing Information Technology Co., Ltd. only provides BabelBird deployment and BabelBird privatization authorization services. The hardware and environment required for deployment shall be prepared and maintained by Party A. Deploy enterprise private cloud version. After Party A pur", "headings": [ { "level": 1, "title": "Service and Maintenance", "id": "service-and-maintenance" }, { "level": 2, "title": "Excerpt from Private Cloud Service Terms", "id": "excerpt-from-private-cloud-service-terms" }, { "level": 2, "title": "After sales and maintenance", "id": "after-sales-and-maintenance" } ], "images": [], "text": "Service and Maintenance The privatized system not only includes software licensing, but also includes deployment implementation, initialization, training, maintenance, upgrades and fault response services. The service scope should be confirmed in conjunction with the contract, service order and maintenance period agreement. Excerpt from Private Cloud Service Terms Babel Enterprise Privatization Services Shanghai Huaqing Information Technology Co., Ltd. only provides BabelBird deployment and BabelBird privatization authorization services. The hardware and environment required for deployment shall be prepared and maintained by Party A. Deploy enterprise private cloud version. After Party A purchases the BabelBird enterprise private cloud version, Shanghai Huaqing Information Technology will deploy and debug it based on the project selected by Party A when signing the contract (see the agreement attachment service order for details). Enterprise private cloud version service time limit. The account authorization period for the enterprise private cloud version is lifetime authorization, and customer service support and upgrade services are provided on an annual basis. Maintenance fee is free for the first year after purchase. Enterprise private cloud version service upgrade. When Shanghai Huaqing Information Technology Co., Ltd. upgrades the BabelBird Enterprise Private Cloud Edition service, it will notify Party A as soon as possible, and Party A will decide whether to upgrade. If Party A agrees to the upgrade, the service will be upgraded remotely without paying other fees. Enterprise private cloud version maintenance fee. The BabelBird enterprise private cloud version is a lifetime license, but if you need Shanghai Huaqing Information Technology Co., Ltd. to provide corresponding training, Q&A, system bug correction, and system upgrade services, you will need to pay maintenance fees. After purchasing the enterprise private cloud version, maintenance fees are free in the first year. Starting from the second year, Party A needs to pay corresponding maintenance fees as stipulated in the contract. If Party A fails to pay the maintenance fee overdue, it will be deemed that Party A has given up all services under these Terms of Service. Babel Order Contract. After purchasing the BabelBird Enterprise Private Cloud Edition service, Party A can sign the [BabelBird Private Cloud Software License Agreement] with Shanghai Huaqing Information Co., Ltd. [BabelBird Private Cloud Software License Agreement] is a written agreement between Shanghai Huaqing Information Co., Ltd. and Party A regarding BabelBird services and fees. After sales and maintenance After sales service provided by BabelBird Babel adopts a one on one dedicated service model, with a dedicated account manager responsible for providing services to customers. Name of maintenance unit: Shanghai Huaqing Information Technology Co., Ltd. The software maintenance period is one year. After the second year, customers need to pay the maintenance fee and enter the next round of software maintenance period. If the customer does not pay the service fee after the maintenance period expires, the customer can continue to use the system, but our company will no longer provide maintenance services until the annual service fee is paid. The service will continue. During the maintenance period, Shanghai Huaqing is responsible for providing maintenance and support for the program code and system configuration information of the software version within the scope of the contract, excluding the development of new functions caused by business changes and other factors. If the China Japan Friendship Hospital requires new functions and customized development services due to changes in business processes, the two parties will negotiate and determine the implementation plan. Free service content and scope Babel provides all paying customers with a lifetime free warranty service during the product life cycle, including: 5 24 hours telephone technical support service 24/7 emergency disaster recovery services Free online training, system usage guidance Report bugs as soon as possible and handle them quickly Software updates and upgrade services For enterprise users with more than 1,000 users, Babel provides lifetime free VIP services during the product life cycle, including: All free services for paying customers System construction and demand corresponding solution consulting services Initialize the system and complete the configuration on behalf of the customer Free data migration service (data less than 10TB) Free on site training once a year (if the number of users exceeds 10,000, there will be three free on site training opportunities per year) Exclusive key account manager responsibility system service For privatized users, on the premise that users pay normal annual service fees, they can enjoy the following free services: All free services for paying customers Free system upgrade and update service. Pure intranet users (intranet cannot connect to the Internet) can receive free on site upgrade and update service once a year. Initialize the system and complete the configuration on behalf of the customer Server performance optimization and troubleshooting Free on site training once a year and unlimited remote training For users of secondary development and function customization based on the BabelBird system, enjoy the following free services: All free services for paying customers Functional warranty and bug correction for the secondary development part Interface and function joint debugging services Comments and guidance services for secondary development codes and interfaces to facilitate redevelopment by users After completion acceptance, fine tuning and functional corrections (non bugs) will be made within our cost tolerance Charged services For redevelopment work on the existing system, the development hours and difficulty will be assessed based on needs, and settlement will be based on hours of work. Product design services. Help customers design product architecture, functions and interactions based on their new needs, and provide technical consultation. Paid on site training and debugging services. Users who have exhausted their free quota or do not meet the conditions for free door to door service can apply for a fee. The fee is 2,000 yuan per person for one day and reimbursement of transportation costs to the user's premises (high speed rail and local taxis) Services provided include the following: Serial number Service items Service content 1 First visit service Service staff proactively carry out first visit service 2 Return visit service Service staff proactively carry out return visit service 3 Routine software operation and maintenance services Program code maintenance of purchased software, such as patching software defects and installing and debugging software patches 4 System upgrade technical consulting Technical consulting services provided when the system is upgraded 5 Software upgrade notification When this version of the software is upgraded, customers will be notified in a timely manner Service methods include: Hotline support: Provide customers with answers to technical questions through the 400 hotline; E MAIL support: answer customer questions via E MAIL; Remote maintenance: remotely debug the Babel software in the customer environment. The customer needs to provide the environment required for remote maintenance. Otherwise, the customer will bear the responsibility for the resulting delay in after sales response time. On site service: If the problem cannot be solved by remote maintenance, our company will provide on site service. It is an on site service caused by problems of the application software itself and falls within the scope of free maintenance. Troubleshooting process When problems arise during customer use: Call the dedicated account manager immediately (or contact us via WeChat), and any issues that can be resolved will be resolved immediately; If the problem cannot be solved immediately, contact the technical personnel immediately, and the technical personnel will remotely assist the customer to solve the problem; If the problem is still unresolved, please report it to the account manager, who will arrange for technicians to provide on site service. Others If any provision of these Terms of Service is wholly or partially invalid or unenforceable for any reason, the remaining provisions of these Terms of Service shall remain valid and binding, and efforts shall be made to give effect to the intentions reflected in such provision. These Terms of Service constitute the entire agreement between Party A and Shanghai Huaqing Information Technology Co., Ltd., regulate your use of this service, and replace all previous agreements between you and Shanghai Huaqing Information Technology Co., Ltd. However, when Party A uses relevant services or uses content or software provided by third parties, it shall also comply with the applicable additional terms and rights. Shanghai Huaqing Information Technology Co., Ltd. reserves all rights of interpretation of these Terms of Service. Party A (seal): Party B (seal): Representative of Party A (signature): Representative of Party B (signature): Date: Date:" }, { "lang": "en", "slug": "deployment-overview", "title": "Private deployment", "description": "Introduces the privatized deployment solution, server roles, performance configuration, object storage, POC, implementation process and Xinchuang support.", "category": "Deployment Implementation", "top_category": "部署指南", "keywords": [ "Private deployment", "object storage", "POC", "Xinchuang" ], "url": "en/deployment-overview.html", "source": "content/en/deployment-overview.md", "summary": "Private deployment Private deployment The BabelBird public cloud network disk system needs to provide continuous and uninterrupted services to 600,000 users including free users at the same time, block various attacks on the public network, and continuously improve system efficiency to reduce the high cost of public cloud servers. As many as 10 years of experience in uninterrupted public cloud services have made the Babel system time tested. The Babel private cloud system is developed on the basis of the Babel public cloud system. It inherits all the functions and features of the public cloud Babel, and is updated synchronously with the public cloud Babel, providing you with high stability a", "headings": [ { "level": 1, "title": "Private deployment", "id": "private-deployment" }, { "level": 2, "title": "Private deployment", "id": "private-deployment-2" } ], "images": [], "text": "Private deployment Private deployment The BabelBird public cloud network disk system needs to provide continuous and uninterrupted services to 600,000 users including free users at the same time, block various attacks on the public network, and continuously improve system efficiency to reduce the high cost of public cloud servers. As many as 10 years of experience in uninterrupted public cloud services have made the Babel system time tested. The Babel private cloud system is developed on the basis of the Babel public cloud system. It inherits all the functions and features of the public cloud Babel, and is updated synchronously with the public cloud Babel, providing you with high stability and high availability that other private network disks cannot match. Deployment plan In response to the different IT system construction needs of different enterprises, the Babel privatization system supports a variety of flexible deployment methods and deployment requirements. Whether it is single server, multi server, cluster, hyper converged system, distributed system, third party cloud platform or even Docker deployment, we support it. Our deployment team can work with you to develop a deployment plan based on your needs. At the same time, because private cloud only serves a single enterprise, we can provide optional customization settings that far exceed those of public cloud systems. From interface operations to processes to permissions, everything can be adjusted according to your needs. Recommended server configuration and performance requirements Server type and function: The hardware system required by BabelBird Enterprise Drive consists of two parts: business servers and storage servers. Business servers can be divided into 4 types. These 4 types of services can be deployed in one physical machine or virtual machine according to needs, or can be deployed dispersedly in four or more servers. Therefore, the minimum unit for deploying the Babel system is two physical servers or two virtual machines (one for business and one for storage) Service name Purpose Operating system Main business server web services, load balancing, main business function implementation Linux Database Server Database Service Linux Search server Provides file full text search and advanced search functions Linux Transcoding server Transcode and add watermarks to files that require transcoding preview windows 2012, Linux Storage server Provides file storage Linux In extreme cases, if the hard disk mounted on the server is used as storage space, Babel also supports deploying all services and storage in a physical machine or virtual machine (all in one machine mode). However, considering performance and disaster recovery or future upgrade and expansion issues, such a deployment method is not recommended. The best deployment method we recommend is a small cluster deployment of 4 servers (virtual machines). The main business services and database services are placed on one server, the search server and transcoding server are independent, and then a storage server is added. If the storage space requirement is less than 10TB, a storage server is not required. You can directly mount a hard disk or NFS disk for storage. BabelBird also supports access to third party storage. In theory, as long as the third party storage system supports the NFS or S3 protocol, it can be connected to BabelBird as a storage service. Most storage systems support both protocols. Each server must ensure smooth communication between each other. If the intranet has higher security requirements, please refer to 9.1.2 Ports that need to be opened Minimum performance configuration: The lowest performance configuration of BabelBird can support normal use by about 100 users and manage less than 10TB of data. cpu memory system disk storage disk network operating system 8 core CPU (reference benchmark E5 2609) 32G ECC memory 500G Below 10TB Gigabit Linux Recommended performance configuration examples: The recommended performance configuration of BabelBird can support normal use by 1000 2000 users and manage documents up to 1PB. Babel supports multiple deployment methods, and this instance is the standard deployment method. Use virtual machines to deploy business servers to connect to independent single or multiple object storage servers. Business servers and storage servers are managed separately. Business server: It is recommended that business servers be deployed using virtual machines Number Server type Configuration requirements Operating system Server purpose 1 Virtual machine 8 core CPU 64G memory 500G SSD system disk CentOS8 or openeuler22 Main business server/database 2 Virtual machine 8 core CPU 32G memory 500G SSD system disk CentOS8 or openeuler22 Search server 3 Virtual machine 8 core CPU 16G memory 200G SSD system disk windows 2012 R2 transcoding server The performance of the 8 core CPU should be close to that of the Zhiqiang 4410 BabelBird Enterprise Drive is deployed using Docker. In theory, it can be deployed as long as it is a Linux operating system. CentOS or open Euler is recommended. If there are no ready made virtual machine resources, you need to purchase a new business server. The business server hardware configuration requirements are as follows: Number Server type Configuration requirements Operating system Server purpose 1 Business server Xeon Silver 4210 2 20 core CPU 64G memory 2TB SSD hard drive Linux Main business server It is best to purchase VM for business servers and use virtualization for management. Storage server (object storage): Babel supports building an object storage system on a general purpose server. If the storage space is expected to be less than 100TB, it is recommended to use a single server to build the object storage system. A single object storage can use disks for data verification redundancy, and can be horizontally expanded by adding one storage server at a time. (The expansion operation can be done without stopping the server) It is recommended to use an independent physical machine for the object storage server, and the recommended configuration is as follows: Server type Configuration requirements Operating system Server purpose Notes Storage server If storage density and future expansion investment are considered, a 12T hard drive can be used. Linux Object Storage Server It is recommended to add a server with the same disk capacity for future expansion. If the required storage space is greater than 300TB, multiple servers are required to build a distributed object storage system. BabelBird also supports building distributed object storage systems for customers. To learn about distributed object storage, please refer to the \"Self Built Object Storage\" chapter. Need to open the port For the security of the server system, we need to open only specific ports. The following are the ports that need to be opened: Ports open to the outside world (ports required for external network access): Port number Port purpose Protocol Open host 80 Network disk main business web external access port, not encrypted http main business server 443 Network disk main business web external access port, encrypted https Main business server 3060 Network disk main business node external access port, not encrypted TCP Main business server 3080 Network disk main business node external access port, encryption TCP Main business server Open ports are required between servers (open ports are required for internal server communication): Generally, during actual deployment, only external network ports (external) will be restricted, and internal ports between servers will not be restricted. However, some users who deploy across networks and computer rooms will also need to limit internal ports. Host Port number Port purpose Protocol Target network segment Business server 6379 redis access port for windows transcoding and search server TCP transcoding server and search server Business server 8080 Used by windows transcoding server to access network disk business server TCP Transcoding server and search server Business server 3306 Database port, used by the search server to access the database TCP Transcoding server and search server Business server 9000 Docker cluster deployment, internal visual interface port TCP Transcoding server and search server Business server 111 portmap port TCP+UDP Transcoding server and search server Business server 2049 TCP+UDP TCP+UDP Transcoding server and search server Business server 35000 mountd port TCP+UDP Transcoding server and search server Business Server 2376 docker REST API port for TLS encryption TCP Native Business server 2377 TCP port used for communication related to docker cluster management TCP+UDP Native Business server 7946 TCP and UDP ports, used for communication between docker swarm nodes TCP+UDP Local machine Business server 4789 docker overlay network default port TCP+UDP Local machine Search server 9200 elastic port, used by the main business server TCP business server Search server 5601 Kibana port, internal visual elastic interface access port TCP Business server Search server 9998 tika port, extract document text server port TCP Business server Search server 9000 Docker cluster deployment, internal visual interface port TCP Transcoding server and search server Search Server 2376 docker REST API port for TLS encryption TCP Native Search server 2377 TCP port used for communication related to docker cluster management TCP Native Search server 7946 TCP and UDP ports, used for communication between docker swarm nodes TCP+UDP Local machine Search server 4789 docker overlay network default port TCP+UDP Native Transcoding server Transcoding server Can access the business server Can access the business server Can access the business server Ports that need to be opened during deployment: Port number Port purpose Open server Destination IP address 22 SSH port number, used for SSH access All servers Springboard machine for deployment 443 Obtain authorization All servers 47.96.234.200 443 Get installation source All servers 120.27.245.68 443 Docker installation source All servers 13.35.121.100 POC deployment POC deployment is suitable for users to conduct POC testing in the production environment before selection. POC deployment requirements: Basic POC deployment can test software functions, concurrency, API interfaces, security, and trial in the production environment. It is recommended to use standard deployment as POC test. If you need object storage, data transfer in different density areas, and high availability POC, you need to add corresponding servers and network segments. Environmental preparation It is recommended to use a virtual machine for deployment: BabelBird's privatized enterprise network disk is deployed using Docker. In theory, it can be deployed as long as it is a Linux operating system. It is recommended to use CentOS or open Euler. After preparing the virtual machine as required, contact us to make an appointment and you can start POC deployment. Number Server type Configuration requirements Operating system Server purpose Remarks 1 Virtual machine 8 core CPU 32G memory 500G system disk +500G storage disk CentOS8 or openeuler22 and above Main business server 2 Virtual machine 8 core CPU 16G memory 500G system disk CentOS8 or openeuler22 and above Search server 3 Virtual machine 8 core CPU 8G memory 200G system disk windows 2012 R2 transcoding server CAD, office transcoding Win server is for better office file preview effect. BabelBird also supports pure Linux environment deployment Other requirements for POC deployment are as follows: Number Project Requirements Remarks 1 Remote access You can remotely access the server for deployment You can use a bastion machine or springboard machine or Sunflower or VPN, and you can remotely access the server for deployment. 2 External network connection The server needs to be able to connect to the external network, pull the installation package, and obtain authorization The external network address that needs to be connected: software.babel.cc docker.babel.cc The authorization period for POC deployment is 30 days, and the number of authorized accounts is 100. initialization After the deployment is completed, the Babel team will help users initialize the system and initialize the system according to user needs. Including but not limited to: Initialize the administrator account. (You need to prepare an email address as a super administrator account) Initialize the notification sending email address. (The user needs to prepare an email address that can provide password and SMTP server address as the system default outbox) Initialize department structure. (Connect with AD or import department) Initialize basic configuration. logo, company name, various configuration items. training BabelBird is a professional enterprise level application and requires certain training to help customers implement it. After POC, it is recommended to contact our sales staff for usage training. Training is divided into 3 categories: Administrator training (training administrators on configuration, use, and realization of required functions. It takes 1 2 hours) Department manager training. (Training department managers on daily management methods such as authority allocation, member addition and reduction, etc. It takes 1 hour) User training. (Training of using members. It takes 1 hour) Start POC trial After the training is completed, the formal POC trial can be started. Any questions encountered during use can be directly asked in the relevant group, and the BabelBird team will respond and answer within 2 hours. The POC system is valid for 30 days. If you need to extend it, please contact our sales staff. Introduction to common deployment methods of BabelBird BabelBird can support multiple deployment methods on demand. Here we introduce the commonly used deployment methods of BabelBird. Deployed on public platforms such as Alibaba Cloud, Tencent Cloud, Huawei Cloud, etc.: Babel supports deployment on virtual machines (ECS) and object storage (OSS, OBS...) of public cloud service providers such as Alibaba Cloud, Tencent Cloud, Baidu Cloud, Huawei Cloud, and Tianyi Cloud, and provides services to users on the Internet. The difference compared with purely private deployment is as follows: Advantages and Disadvantages/Deployment Method Image Service Video Service Public Network Access Stability Hardware Cost Using Alibaba Cloud storage and Alibaba Cloud servers You can use the picture service provided by Alibaba Cloud You can use Alibaba Cloud's video transcoding service, but it requires an additional fee (expensive) It can be accessed on the public network. The speed of user access depends on the user's own bandwidth and the purchased Alibaba Cloud bandwidth. The system is very stable, simple to deploy and easy to manage. You need to pay Alibaba Cloud's storage and server fees, which can be paid monthly or annually. Users can be responsible for the maintenance of the server themselves, or they can entrust us to perform maintenance and upgrades. Storage and servers are built on your own intranet Use self built image processing services (requires customers to provide high performance servers) Use self built transcoding services (requires customers to provide high performance servers). If the user does not have this requirement, you can ignore it. If there is no external network exit, users cannot access the external network. But intranet access is very fast. Stable, customized development for modules such as storage systems. The security of data is the responsibility of the user. Requires independent host and storage systems. The server can be purchased by the user or by us. Server maintenance is the responsibility of the user, and we can provide corresponding software upgrade services. Public cloud deployment (1000+ users) requirements: Number Server type Configuration requirements Operating system Server purpose 1 ECS 16 core CPU 32G memory 500G SSD system disk CentOS8 or openeuler22 Main business server 2 ECS 8 core CPU 16G memory 500G SSD system disk CentOS8 or openeuler22 Database server 3 ECS 8 core CPU 16G memory 500G SSD system disk CentOS8 or openeuler22 Search server 4 Storage Object storage system. Such as Alibaba Cloud OSS, Huawei Cloud OBS Object Storage System. Such as Alibaba Cloud OSS, Huawei Cloud OBS Object Storage System. Such as Alibaba Cloud OSS, Huawei Cloud OBS The main advantages of deploying on a public cloud platform are that it does not require dedicated maintenance, top level disaster recovery can be achieved without purchasing hardware, access to the Internet is fast, and servers and data are managed by oneself. The main disadvantages of deploying on a public cloud platform are: data is not localized, and annual server rental fees and corresponding bandwidth storage costs need to be paid. Self purchased servers (2 physical machines) for deployment: If you want to deploy a purely private BabelBird in your own computer room and do not have spare virtual machine resources, you need to purchase hardware deployment. The requirements are as follows: Physical server brand recommendation: It is recommended to use 2 DELL T440 servers to complete the system setup. And purchase DELL 3 year gold service. The server's system disk can optionally use raid to enhance redundancy. If you use the raid1 solution, the number of hard disks required needs to be increased by 2 times. (2TB SSD becomes 2TB SSD 2) Physical server brand recommendation: It is recommended to use 2 DELL T440 servers to complete the system construction. And purchase DELL 3 year gold service. The server's system disk can optionally use raid to enhance redundancy. If you use the raid1 solution, the number of hard disks required needs to be increased by 2 times. (2TB SSD becomes 2TB SSD 2) Physical server brand recommendation: It is recommended to use 2 DELL T440 servers to complete the system construction. And purchase DELL 3 year gold service. The server's system disk can optionally use raid to enhance redundancy. If you use the raid1 solution, the number of hard disks required needs to be increased by 2 times. (2TB SSD becomes 2TB SSD 2) Physical server brand recommendation: It is recommended to use 2 DELL T440 servers to complete the system construction. And purchase DELL 3 year gold service. The server's system disk can optionally use raid to enhance redundancy. If you use the raid1 solution, the number of hard disks required needs to be increased by 2 times. (2TB SSD becomes 2TB SSD 2) Physical server brand recommendation: It is recommended to use 2 DELL T440 servers to complete the system construction. And purchase DELL 3 year gold service. The server's system disk can optionally use raid to enhance redundancy. If you use the raid1 solution, the number of hard disks required needs to be increased by 2 times. (2TB SSD becomes 2TB SSD 2) Physical server brand recommendation: It is recommended to use 2 DELL T440 servers to complete the system construction. And purchase DELL 3 year gold service. The server's system disk can optionally use raid to enhance redundancy. If you use the raid1 solution, the number of hard disks required needs to be increased by 2 times. (2TB SSD becomes 2TB SSD 2) Two server plan business + storage Two server plan business + storage Two server plan business + storage Two server plan business + storage Two server plan business + storage Two server plan business + storage Number Server type Configuration requirements Operating system Server purpose Remarks 1 Server Zhiqiang Silver 4410 2 16 core CPU, 64G memory, 2TB SSD hard drive open Euler, Ubuntu, CentOS Main business server It is recommended to install VM 2 Storage 4410 2 16 core CPU, 64G memory, 500G SSD hard disk + required hard disk space (no raid or raid0 required) open Euler, Ubuntu, CentOS Storage server Hard disk capacity is configured according to storage space requirements The above configuration can support 1000+ users and about 150TB of storage space. Babel storage server uses an object storage system and supports distributed deployment (multiple storage servers) with a minimum requirement of one physical server. Supports the use of hard disk groups for verification, and supports multiple verification types such as 2+1, 3+1, 4+1... etc. See the self built object storage chapter for details. If you need to expand the storage space, just add a single storage server. You can also add a storage server as a backup server to synchronize the backup in real time. If there is a problem with the main storage server, switch to the backup server and it can be used normally. Single server (1 physical machine) deployment: Some customers who do not have a computer room but need to deploy BabelBird privately and have small storage space requirements (less than 10TB) can choose to deploy BabelBird on a single server. Just purchase a tower server that meets the requirements and place it in your company to meet the needs of using BabelBird. Physical server brand recommendations: If there is no computer room, it is recommended to use tower servers for deployment. It is recommended that the server storage hard disk is raid1 or raid5+1. The system disk of the server can optionally use raid to enhance redundancy. If you use the raid1 solution, the number of hard disks required needs to be increased by 2 times. (2TB SSD becomes 2TB SSD 2) Physical server brand recommendations: If there is no computer room, it is recommended to use tower servers for deployment. It is recommended that the server storage hard disk is raid1 or raid5+1. The system disk of the server can optionally use raid to enhance redundancy. If you use the raid1 solution, the number of hard disks required needs to be increased by 2 times. (2TB SSD becomes 2TB SSD 2) Physical server brand recommendations: If there is no computer room, it is recommended to use tower servers for deployment. It is recommended that the server storage hard disk is raid1 or raid5+1. The system disk of the server can optionally use raid to enhance redundancy. If you use the raid1 solution, the number of hard disks required needs to be increased by 2 times. (2TB SSD becomes 2TB SSD 2) Physical server brand recommendations: If there is no computer room, it is recommended to use tower servers for deployment. It is recommended that the server storage hard disk is raid1 or raid5+1. The system disk of the server can optionally use raid to enhance redundancy. If you use the raid1 solution, the number of hard disks required needs to be increased by 2 times. (2TB SSD becomes 2TB SSD 2) Physical server brand recommendations: If there is no computer room, it is recommended to use tower servers for deployment. It is recommended that the server storage hard disk is raid1 or raid5+1. The system disk of the server can optionally use raid to enhance redundancy. If you use the raid1 solution, the number of hard disks required needs to be increased by 2 times. (2TB SSD becomes 2TB SSD 2) Physical server brand recommendations: If there is no computer room, it is recommended to use tower servers for deployment. It is recommended that the server storage hard disk is raid1 or raid5+1. The system disk of the server can optionally use raid to enhance redundancy. If you use the raid1 solution, the number of hard disks required needs to be increased by 2 times. (2TB SSD becomes 2TB SSD 2) One server (all in one solution) One server (all in one solution) One server (all in one solution) One server (all in one solution) One server (all in one solution) One server (all in one solution) Number Server type Configuration requirements Operating system Server purpose Remarks 1 Server The entire Babel system deployed on a single server does not support object storage and uses read only hard disks or NFS for storage. It is recommended to use raid1 to improve system reliability. A backup server can be added for data synchronization and backup. If there is a problem with the main server, you can use the backup server to reconstruct the data. Deploy on existing virtual machine (hyperconverged) system: This is currently the most commonly used deployment method. It is deployed under the existing servers and hardware of the enterprise without purchasing new equipment. Deployment is completed in the customer's existing VM or virtual machine allocated by the hyper converged platform, which is suitable for users who already have certain IT construction and management. It is deployed in a small cluster, and the virtual machine platform is responsible for the unified management of the server. Supports most virtualized systems. It is recommended to deploy four virtual machines with storage space mounted. Number Server type Configuration requirements Operating system Server purpose 1 Virtual machine 8 core CPU 32G memory 500G SSD system disk CentOS8 or openeuler22 Main business server 2 Virtual machine 8 core CPU 16G memory 500G SSD system disk CentOS8 or openeuler22 Database server 3 Virtual machine 8 core CPU 16G memory 500G SSD system disk CentOS8 or openeuler22 Search server 4 Virtual machine 8 core CPU 16G memory 200G SSD system disk windows 2012 R2 transcoding server 5 Storage Support NFS or S3 interface storage system or virtual machine mounting disk as storage disk Support NFS or S3 interface storage system or virtual machine mounting disk as storage disk Support NFS or S3 interface storage system or virtual machine mounting disk as storage disk If there is a need for system redundancy, you can prepare 6 virtual machines to complete database backup and system redundancy. Number Server type Configuration requirements Operating system Server purpose 1 Virtual machine 8 core CPU 32G memory 500G SSD system disk CentOS8 or openeuler22 Main business server 2 Virtual machine 8 core CPU 32G memory 500G SSD system disk CentOS8 or openeuler22 From business server 3 Virtual machine 8 core CPU 16G memory 500G SSD system disk CentOS8 or openeuler22 Main database server 4 Virtual machine 8 core CPU 16G memory 500G SSD system disk CentOS8 or openeuler22 From database server 5 Virtual machine 8 core CPU 16G memory 500G SSD system disk CentOS8 or openeuler22 Database server 6 Virtual machine 8 core CPU 16G memory 200G SSD system disk windows 2012 R2 transcoding server 7 Storage Distributed Object Storage Distributed Object Storage Distributed Object Storage Supports virtual machine mounting disks to use the mounted disk as storage space. It can also be connected to third party storage systems such as san storage or object storage systems. BabelBird also provides customers with self built object storage services. Self built object storage server and virtual machine deployment: Babel supports customers to build object storage on general purpose servers. Because of the advantages of object storage software defined storage (high availability, easy horizontal expansion), it is recommended that users without object storage can purchase a new server and deploy the Babel object storage system to use it with the Babel business system running on a virtual machine (hyper convergence). The business server requirements are the same as those in the previous section \"Deployment on Existing Virtual Machine (Hyper Converged) System\". For a detailed introduction to Babel object storage, please see the \"Self Built Object Storage Server\" chapter. Most of our customers end up choosing object storage servers for storage. At least a single server is supported to build an object storage system (space requirement is less than 150TB). Server type Configuration requirements Operating system Server purpose Notes Storage server If storage density and future expansion investment are considered, a 12T hard drive can be used. Linux Object Storage Server It is recommended to add a server with the same disk capacity for future expansion. Single server object storage network topology diagram: We also support building a distributed object storage system composed of multiple servers. The minimum requirement for a distributed storage system is 2+1, which means three storage servers need to be prepared. The performance requirements are consistent with those of a single object storage. The currently recommended minimum unit for physical distributed storage is 3 storage servers. The 2+1 error correction code means that every time two storage nodes are expanded, one server needs to be added as an error correction server. In this way, 4+1 means that adding 4 storage servers requires adding an error correction server. So the disk utilization of 4+1 is higher than that of 2+1. The first construction using the 4+1 solution requires 5 storage servers. The minimum unit added for each expansion is the same as the minimum server unit required for the first construction. Multi server distributed object storage network topology diagram: You can add a new storage server or a set of storage servers for real time backup. If there is a problem with the primary storage server, quickly switch to the backup server and it can be used normally. Distributed high availability and high redundancy deployment: Because financial institutions, hospitals, energy, and very large enterprises have hard targets for uninterrupted business, they need systems that can achieve high availability and high redundancy. Services will not be interrupted due to a single point failure of the server, and hot switching and hot repair can be performed. In extreme cases, even network equipment such as switches need to be separated from active and backup, which requires the use of distributed high availability and high redundancy deployment. Babel supports a variety of high availability and high redundancy solutions and can be deployed in traditional distributed systems to achieve high availability and high redundancy. We can also build a distributed system suitable for Babel for customers. (Customers need to purchase hardware by themselves as required) Babel distributed deployment can ensure that any single point of failure will not affect the normal use of the system. The recommended distributed and easy to deploy solution uses active active active backup for the business server and distributed storage for the storage system. If there is a need for management and control of confidential and non confidential areas, please see the \"Data Ferry Chapter\" for details. Babel High Availability System Network Topology Off site disaster recovery deployment For users who have higher requirements for data preservation, BabelBird also supports off site disaster recovery solutions. It means backing up important database and file storage contents to an off site backup system. If there is a problem in the local computer room, as long as the backup data is there, the system can be rebuilt anywhere and restored to normal use. BabelBird can build off site disaster recovery servers for customers, but it does not support advanced backup methods such as hot and cold data separation. If the amount of data is very large (above 1PB) and considering cost effectiveness, it is recommended to use a professional backup system (such as NBU, Yunqi). BabelBird has a backup API that supports the NBU standard and can be called. Off site disaster recovery deployment has higher requirements on the network environment. It is best to have dedicated lines or stable VPN connections between computer rooms in different locations. Using the backup system can only restore and reconstruct data through backup after a problem occurs. Direct switching to backup data is not supported. Generally, the data reconstruction cycle will take a long time. Schematic diagram of using backup system for off site disaster recovery: If hot and cold data do not need to be classified and saved, BabelBird can also use the off site disaster recovery function of object storage to complete off site disaster recovery deployment for customers. Use object storage for remote disaster recovery. When the main system has a problem, you can quickly switch to the disaster recovery server. Self built object storage server Babel object storage is an object storage system developed on the open source MinIO system. It inherits MinIO's advantages of high performance, scalability, and data security, and is more suitable for the application scenarios of BabelBird Enterprise Drive. As an advanced object storage system, Babel object storage system has unparalleled advantages over traditional storage systems in terms of speed, security, stability, high availability, and horizontal expansion. Advantages of Babel object storage system Performance MinIO is claimed to be the fastest object storage server in the world. Published GET/PUT results of over 325 GiB/sec and 165 GiB/sec on 32 NVMe drive nodes and 100Gbe network, a clear advantage compared to Amazon S3 and far superior to traditional HDFS. High availability: MinIO ensures high reliability and availability through multiple copies of data, failover and automatic recovery, thereby ensuring that data is not lost and business is not interrupted. Low redundancy and high tolerance for disk damage: the standard and highest data redundancy coefficient is 2 (that is, storing a 1 M data object actually takes up 2 MB of disk space). However, data can still be read even if any n/2 disks are damaged (n is the number of disks in an erasure coding set). And this damage recovery is based on a single object, not based on the entire storage volume. Security: MinIO delivers more functionality with the highest levels of encryption and extensive optimizations that virtually eliminate the overhead typically associated with storage encryption operations. Data is stored in blocks and on each hard disk, and data cannot be restored even if you obtain read and write permissions from the hard disk or server. Extremely high scalability: MinIO supports distributed deployment and can be expanded horizontally. When more storage space or higher performance is needed, MinIO can be easily expanded by adding new nodes. At least it supports the deployment of object storage systems on a single machine, instead of the traditional requirement of three independent servers. Object storage system and erasure coding About erasure coding Babel Object Storage System (MinIO) uses erasure coding and checksums to protect data from hardware failures and silent data corruption. Even if half (N/2) of the hard drives are lost in the highest redundancy state, you can still recover data. Erasure coding is a mathematical algorithm for recovering lost and damaged data. MinIO uses Reed Solomon code to split objects into N/2 data and N/2 parity blocks. This means that if there are 12 disks, an object will be divided into 6 data blocks and 6 parity blocks. Any 6 disks can be lost (regardless of whether they store data blocks or parity blocks) and can still be recovered from the data in the remaining disks. We call the data storage D and the erasure code (parity) P. By default, the drive is sliced in N/2 data and N/2 parity blocks (customizable to support higher space utilization) Erasure coding is different from traditional multi copy technology. It has higher disk utilization and higher data recovery efficiency. (However, many storage manufacturers promote erasure coding as multiple copies and refer to the P number as the number of copies. This is inaccurate and will cause a lot of misunderstandings.) Multiple copies in the context of Babel refers to adding backup servers to fully synchronize and store data. Characteristics of erasure coding and differences from raid technology Erasure coding protects data from multiple drive failures RAID6 tolerates two drive failures while MinIO erasure coding allows the loss of half the drives RAID is a volume level erasure code, while MinIO erasure code is an object based erasure code (without downtime). Effective space calculation (space utilization) Assuming you need 100TB of storage space, how many hard drives you need to buy depends on the redundancy standard you choose. For example: using the 3+1 redundancy method, 100TB of available space requires the purchase of 12 12TB hard drives, 4 hard drives forming 3 groups, 9 data disks and 3 parity disks, the available space is 9 12, a total of 108TB available. If 2+1 redundancy is adopted, 15 10TB hard drives, 10 data disks, and 5 parity disks are required. In the 3+1 plan, only 3 of the 12 hard disks can fail without affecting system usage and data restoration. However, if you use the 2+1 plan, although you need to purchase more hard disks, any 5 of the 15 hard disks can fail without affecting the system usage. After replacing the damaged hard drive, the system can automatically repair the data. Please refer to the table below for space utilization. If the space requirement is large (more than 150TB) and continues to grow, considering storage density and cost performance, it is recommended that a server be equipped with 16 hard disks at a time. Different numbers of disks and space utilization can be calculated by clicking the link below https://min.io/product/erasure code calculator?ref=docs Hardware preparation Required hardware configuration. Babel supports a single server to build an object storage system (single node), using hard disk groups as redundant objects. Up to half of the hard drive can be damaged without affecting the normal use of the system. The Babel object storage system requires customers to prepare hardware servers in advance for deployment as required. The minimum configuration requires 2 Xhiqiang CPUs, 64GB memory and 400G solid state drives (system disks), and then the mechanical hard drives required to increase the corresponding storage capacity. To calculate the storage space required and the number of hard drives to purchase, click the link below to calculate it. https://min.io/product/erasure code calculator?ref=docs The recommended hardware configuration is as follows: Server type Configuration requirements Operating system Server purpose Notes Storage server If storage density and future expansion investment are considered, a 12T hard drive can be used. Linux Object Storage Server It is recommended to add a server with the same disk capacity for future expansion. Babel object storage uses software defined storage technology, so the hard disk does not require RAID. Considering that some servers require RAID to support multiple disks, in this case, each hard disk can be set to RAID0 pass through mode. Each expansion in single server mode requires adding a server with the same configuration. Uninterrupted service is possible during capacity expansion. Single server deployment also supports adding a server with the same configuration to establish active standby mode for real time synchronization. If the hardware of a server is damaged, it can be quickly switched to the backup server. The effective disk space capacity is related to the selected redundancy method. For example: use 8 10T hard drives to build an object storage system, and adopt a 3+1 redundancy scheme, which is equivalent to a group of 4 hard drives, divided into 2 groups, with an effective available space of 60TB. At the same time, if any two of the 8 hard drives are damaged, the data and system usage will not be affected. The damaged hard drive can be automatically rebuilt. If a 7+1 redundancy scheme is adopted, the effective available space is 70TB. Any damage to one of the eight hard drives will not affect data and system usage. Multi server deployment (distributed). Babel object storage system supports multi server deployment. If the server is used as a redundant unit, at least 3 servers are required, that is, 2+1 mode. However, considering the space utilization, it is recommended to adopt the 3+1 solution (that is, 4 servers). The configuration requirements for each node (server) are consistent with the single server deployment above. It is recommended that the node configuration be consistent (same operating system, same number of disks and same network connection) The number of drives provided by each node must be the same The time difference between nodes cannot be greater than 15 minutes (it is recommended to use NTP to ensure time consistency) The space utilization calculation is the same as for a single server. Privatization requirements and service procedures In order to ensure the experience and quality of using the BabelBird system, all privatized deployment work of BabelBird is deployed remotely or on site and certificates are issued by the BabelBird team. Deployment by an agent team or self deployment by customers is not currently supported. At the same time, the maintenance work of the system is also carried out by the Babel operation and maintenance team on a regular basis remotely. Customers only need to prepare the hardware and access resources as required, and leave the rest to the Babel team. Things that need to be prepared in the early stage of privatized deployment: Calculate the approximate number of users, concurrency, storage space and space growth rate and let the Babel account manager evaluate the required configuration. The customer evaluates the remaining resources (if any) of the existing server and selects a deployment method based on the actual situation. Babel issued a privatization deployment plan. Customers prepare corresponding servers and access resources according to the plan, allocate servers, and install operating systems. Ensure that the server can be accessed via external remote desktop (you can also use Sunflower) and ssh, and open the corresponding port (our deployment technicians will put forward specific port requirements) It is best for the user to provide a domain name. If there is no domain name, a fixed IP address is required. The solution using IP address to access needs to ensure that the IP address will not change during use. If you need to access your email to retrieve your password or send a verification code to your mobile phone number, you need to prepare the corresponding email access or SMS gateway. Number Project Requirements Remarks 1 Domain name An independent primary domain name or secondary domain name is required A secondary domain name can be set based on the company's original domain name. Such as yun.company.com 2 Email An email address that can send notification emails is required An email address that supports SMTP is sufficient Email push related MailUser=xxxx@mail.com MailPassword=password MailHost=Mail server address MailPort=Port number 3 Remote access Remote access to the server for configuration Support remote access and control of the server 4 SSl certificate https needs to apply for an SSL certificate Apply like a digital certificate authority CA. Recommended Application OV Wildcard 5 SMS interface If you need a mobile invitation, please register with your mobile phone. You need to activate the SMS interface service (optional) Cloud service providers such as Alibaba Cloud and Tencent Cloud also provide SMS service interfaces, which can be activated by applying implementation stage Notify us after the preparation work is completed, and we will give users a specific implementation time schedule. Please maintain smooth access to the external network during the implementation time period. Implementation generally takes 2 3 working days. On the first day, Babel is deployed and installed remotely, on the second day it is tested and accepted, and on the third day, problems encountered are corrected. Once the implementation is complete we will notify the user and then start the initialization phase Initialize service Babel provides initialization services to all private cloud customers, including: Maintenance personnel training (remote or on site) Help users with data migration, user import, permission assignment, etc. (remotely or on site) User training (remote or on site) Access third party services As an office platform centered on corporate documents, the privatized BabelBird Enterprise Drive can easily integrate various third party services into BabelBird to meet different needs by accessing third party APIs. These services include but are not limited to: electronic signature, advanced CAD preview, office, text recognition, image recognition... and other third party services to solve your needs. Conditions for accessing third party services In theory, third party applications or service modules that support the BS architecture can be accessed. Third party services must provide open APIs so that BabelBird Enterprise Drive can be integrated with them If it is an Internet service, the server needs to be able to access the external network. Enterprises need to authorize themselves or entrust us to purchase third party services for access. Recommended accessible services File anti leakage system: ipguard Online office editing: onlyoffice (self contained), office365, WPS Online, Yongzhong office Advanced CAD preview: Haochen Cloud Atlas, Dream CAD CAD online editing: Dream CAD Online signature: Sign on Text recognition and image recognition: Baidu Qianfan (Smart Cloud) AI related: Zhichao AI (self owned), ChatGPT, Zhipu AI Open API (unified storage platform) The private version of BabelBird provides an open API. Using the BabelBird API, you can use almost all capabilities of BabelBird in your system. And build custom applications and integrations in the cloud without having to build and maintain your own content management service. Unified storage platform Unified management of unstructured data: The core value of BabelBird Enterprise Drive's open API is that it can be used as a unified storage platform to integrate and manage unstructured data from various enterprise platforms. This includes but is not limited to OA (office automation), CRM (customer relationship management), ERP (enterprise resource planning) and other applications, so that all unstructured data of an enterprise can be managed uniformly on one platform, improving security and saving storage resources. Enterprise grade object storage: BabelBird Enterprise Drive can also open its own object storage interface as a unified storage management platform for enterprises. This means that enterprises can store data from different sources, including documents, media, reports, etc., in BabelBird Enterprise Drive, and access and manage these data through APIs. Documentation and support Detailed documentation: BabelBird Enterprise Drive provides detailed API documentation, including sample code and use cases, to help developers quickly integrate APIs. Attachment 2: Babel API document https://www.babel.cc/p/api integration.do Development support: We provide development support services, and technical staff will participate in joint debugging to solve one on one problems and challenges that may be encountered during the API integration process. Single sign on SSO The BabelBird privatization system supports docking with the SSO single sign on platform or third party platforms such as Enterprise WeChat, DingTalk, Feishu, OA, ADFS, and ERP to achieve single sign on. For more information about single sign on, please refer to the security chapter above: Single Sign On (SSO) integration Data ferry BabelBird can use the \"department security policy\" method to isolate a certain department's data to implement functions such as security and outbound approval of confidential departments. However, when it comes to file transfer between confidential and non confidential areas isolated by the network, data ferrying is required to ensure safe and controllable exchange of files between confidential and non confidential areas. Here, the BabelBird data ferry function needs to be deployed. In BabelBird, this functional module is named \"Transfer File\" to make it easier for ordinary users to understand. Implementation method Deploy one set of Babel birds in each of the secret area (R&D area) and the non confidential area (office area), and transfer files between the two sets of Babel birds: Need to install the Babel data ferry module Transmission ports need to be configured between the two sets of servers Transfers are encrypted using SSL Support file transfer between multiple sets of BabelBirds Super administrator can set specific document recipients and reviewers Can be configured to transfer files from non confidential area to confidential area without approval All transfers are recorded and logged Multiple sets of Babel birds transmit files across multiple networks: Simplified file transfer method for single set of BabelBird : The core requirement of some customers is to transfer files quickly and easily from the non confidential area to the confidential area. They only want to deploy a set of BabelBirds in the confidential area and have no need to use a network disk in the non confidential area. In this case, a simplified data ferrying method can be used. For security reasons, this method only supports transferring files from non confidential areas to encrypted areas, but does not support transferring files from encrypted areas to unencrypted areas. In addition to deploying a complete Babel system in the secret area, a file transfer service also needs to be deployed in the non confidential area. Transferring files from non confidential areas to confidential areas does not require approval. Usage steps After deploying the data ferry module, Babel will add a \"Transfer File Configuration\" module to the enterprise console. If you can see the module entry in the enterprise console, it means that the data ferry module has been deployed successfully. Create a new receiving port and sending port in the \"Transfer File Configuration\" of the enterprise console. The receiving end and sending end of the data ferry have been determined. If one set of Babel birds is only configured with an interface port and no sending port, then it can only receive files but cannot send files. For example: the secret area can only receive files but cannot send files. When a new receiving end is created, a token will be automatically generated, and the sending end must fill in the token to achieve encrypted transmission. A Babel bird can establish multiple receivers, and each receiver can choose different members. For example: the receiving ends of the R&D department and the technology department are separated. After passing the review, the recipient can find the transferred files in the \"Transfer Files\" column of his or her Babel account. Users can directly right click \"Send File\" in the BabelBird Enterprise Drive and select the receiving end to send the file (send). And check the files that have been sent and passed the review under the \"Send Files\" column. To ensure security, files are transferred in file units (important files are entrained in multi layer folders to cheat the review). Folder selection is not supported for transfer, but multiple file selection is supported for transfer. Administrators or department managers with approval authority can review received and sent files under the \"Transfer Files\" column. Only files that pass the review can be transferred. Customized development The private version of BabelBird can provide customers with professional customized development (secondary development) services. Based on BabelBird's existing products, we will launch products more suitable for customers based on their specific needs. Advantages of customized development of BabelBird Help you design products based on product thinking Different industries have different work processes and usage habits, and there is often a deep gap between demand and final products. Only demand without good product design will often delay the implementation of the project. In order to better suit your usage scenarios, our Babel care team led by professional product managers will customize your own solutions and secondary development support for your company. Refined time estimate management We have a refined time estimation management system that has served Peking University Founder, which can accurately manage development time estimates and improve project success rate and implementation efficiency. Project estimates are clear and well documented, effectively reducing corporate costs and improving efficiency. Transparent project follow up and acceptance At every stage of the project, we have dedicated project managers and product managers to follow up. Ensure project progress and acceptance standards. And we can open our Jira (project management tool) to customers so that customers can know the progress and time consuming of the project at any time. Keep it updated and maintained The most common problem with custom development is future updates and maintenance. Because traditional custom development is quite different from standard products, new branches are often used, and the development team does not have the energy to maintain new branches. This causes custom development products to lose continuous maintenance and feature updates, become increasingly difficult to use or isolated, and are eventually abandoned. Babel noticed and solved this problem. We will use a modular approach to develop new customized requirements based on standard products, or integrate customized requirements into standard products and manage them in the form of configuration items. In this way, even customized products can enjoy the update and maintenance services of standard products, achieving sustainable development. Support white label service (OEM) For commercial purposes or brand building needs, some companies need to use their own product names and logos. Babel can provide a white label (OEM) version that meets the company's requirements. Transparent, professional and responsible Responsibility is what our customers give us the most and the highest praise. During the project maintenance period, we will consider it from the perspective of the enterprise, correct bugs and complete functional adjustments in a timely manner. Provide long term sustainable maintenance services for enterprises. Babel bird custom development scope API based system docking: such as docking and integration with OA, CRM, PDM and other systems. Custom development of API: open API for a certain function of BabelBird Enterprise Drive. Customized development of independent functional modules or subsystems using the Babel API interface. Focusing on the functional expansion, process customization and data exchange of the existing functions of BabelBird Enterprise Drive. Interface reshaping and functional customization development based on Babel bird source code. Babel bird custom development process Determine needs and technical implementation plans with customers. Issue: \"Requirements Analysis Instructions\" Product managers have in depth discussions with customers to design prototypes and interactions. Issue \"Secondary Development Plan\", \"Product Prototype\", \"Detailed Modules and Time Estimation Schedule\" In the business and contract phase, the customer pays the advance payment. Design drawings and development started. Internal testing and joint debugging. Trial launch and user testing. User training. User acceptance and delivery The customer pays the balance. Xinchuang support BabelBird has been actively responding to the call for localization for many years, and BabelBird's products can also run in most innovative environments. Especially for the server side, whether it is CPU, operating system or database, BabelBird has corresponding Xinchuang solutions. CPU and server architecture support. Babel supports domestic CPUs with X86 and ARM instruction sets, such as X86's Loongson, Feiteng, Kirin, and Haiguang... It also supports domestic CPUs with ARM architecture, such as Kunpeng architecture and Feiteng ARM architecture. operating system. Babel uses docker for deployment and supports all Linux operating systems that support docker. Such as open Euler, Galaxy Kirin, and Tongxin UOS database. Babel recommends using AliSQL database or other MySQL compatible databases such as: open Causs (Gauss). BabelBird can also access other domestic databases for customization. Such as: Dameng, Renmin University Jincang, Nanda General... client. The Babel client can run on Linux systems and supports domestic systems such as Kirin and Tongxin. Since the Linux system file management interface is not unified, the Linux version of Babel does not support the synchronization of folders and mapped disk functions. Classification Classification Standard deployment system (non Xinchuang) BabelBird Xinchuang solution (x86) BabelBird Xinchuang solution (arm) Functions not supported by Xinchuang version Business Server Operating System Centos, openEuler, Ubuntu openEuler, Kirin Kunpeng, Kirin, Tongxin None Business Server BabelBird Version Standard Edition BabelBird Xin Chuang Edition (X86) BabelBird Xin Chuang Edition (arm) None Business Server Database MySQL Gaussian, TiDB, aliSql Gaussian arm None Business Server Component/Middleware tomcat tomcat, TongWeb7 tomcat None Business Server Component/Middleware pomleo pomleo (Xinchuang) pomleo (Xinchuang) None Business Server Component/Middleware Elastic Search Elastic Search (Xinchuang) Elastic Search (arm) None Business Server Component/Middleware Redis Babel readis Babel readis None storage server storage system minio minio minio arm none Client Client Babel win/mac client Babel linux/Kilin/Ubuntu client Need to be transplanted Linux version client does not support mapping disk and synchronizing folder functions" }, { "lang": "en", "slug": "architecture", "title": "System architecture", "description": "Introduces front-end, client, back-end, database, object storage, backup, and service split architectures.", "category": "Architecture And Storage", "top_category": "部署指南", "keywords": [ "Architecture", "Docker", "SOA", "object storage" ], "url": "en/architecture.html", "source": "content/en/architecture.md", "summary": "System architecture System architecture Architecture overview Front end architecture Front end architecture includes the following key components and technologies: Backbone.js was chosen as the main architecture, which provides component based development, state management, routing control and other functions. On its basis, Gulp, Babel, browserify, Scss, jQuery, underscore, ES6, etc. are introduced to build maintainable and high performance front end applications. The WebSocket protocol and background are used for instant messaging of messages. Designed with a unified style, user friendly and intuitive interface, including search, folder management, file preview and other functions. The webs", "headings": [ { "level": 1, "title": "System architecture", "id": "system-architecture" }, { "level": 2, "title": "System architecture", "id": "system-architecture-2" } ], "images": [], "text": "System architecture System architecture Architecture overview Front end architecture Front end architecture includes the following key components and technologies: Backbone.js was chosen as the main architecture, which provides component based development, state management, routing control and other functions. On its basis, Gulp, Babel, browserify, Scss, jQuery, underscore, ES6, etc. are introduced to build maintainable and high performance front end applications. The WebSocket protocol and background are used for instant messaging of messages. Designed with a unified style, user friendly and intuitive interface, including search, folder management, file preview and other functions. The website supports full platform preview and uses CSS media query and mobile optimization technology to create a responsive layout to ensure that network disk products have consistent appearance and functionality on different devices. Considering multi language support, the system currently supports Chinese and English languages, which can be switched at any time on the interface or through the browser language. Front end performance optimization technologies such as code splitting, lazy loading, resource compression, and CDN acceleration are adopted to improve page loading speed and response time. Implement front end security best practices, including XSS (cross site scripting) and CSRF (cross site request forgery) protection. Ensure data transmission is encrypted and stored securely. Cross platform and multi language: The front end part of the BabelBird system includes: BabelBird iOS version (iPhone, iPad), BabelBird Android version, BabelBird web version, BabelBird WeChat version (H5), BabelBird mac client, BabelBird windows client, and BabelBird Linux (Kirin) client. The native iOS client is developed using Object C and Swift. The native Android client and Hongmeng are developed using Java (Android studio). Windows, mac, and Kirin clients are developed using Electron and C++, and include four components: client interface, synchronization terminal, transmission management, and mapping disk. Backend architecture Server topology Babel's back end architecture is mainly responsible for business logic, data processing and interaction with the front end. It meets the following key objectives: Modular design: The backend adopts a modular design to divide different functions and business logic into independent modules. This helps with code maintainability and scalability. Performance: The Babel backend has good performance and can handle large scale file uploads, downloads, searches, and collaboration requests. Appropriate load balancing and caching strategies and optimization techniques are adopted to improve response times. Security: The Babel backend focuses on strengthening security, including user authentication, authorization, data encryption, and defensive programming to protect user data from attacks. Scalability: The Babel backend architecture is scalable to accommodate future business needs and the addition of new features. Adopts SOA service architecture and modular component design to support flexible expansion of functions. Data Management: The Babel backend efficiently manages user data, file data, and metadata. This includes database design, backup strategies and data cleansing. Frame selection Babel adopts a loose, service oriented architecture model. Different services are designed, developed, and deployed independently, thus ensuring the stability and scalability of the system. Eventually, we will use docker to containerize these services for unified management and deployment. For services with simple logic and high frequency access, we choose Nodejs and the corresponding development framework. For services with complex logic and low consumption, we will choose Struts2+Spring framework. For services with complex logic and high consumption (such as MD5 calculation, file blocking, encryption), we will choose the Rust language for development. data layer Database: Babel chose MySQL as the database management system, and also supports the use of other databases (Gaussian, PostgreSQL, Oracle can be supported on demand) At the same time, Babel adopts ORM (Object Relational Mapping): using the ORM framework (Hibernate) to map database tables to Java objects to simplify data access and persistence. security User Authentication: Use strong user authentication mechanisms, including single sign on (SSO), OAuth authentication, and multi factor authentication (MFA). Authorization: Use an authorization framework such as Spring Security to define and enforce access control policies to ensure that users can only access the resources they are authorized to use. Data Encryption: Implement encryption of data transmission and storage to protect the security of user data. business logic File Management: Developed business logic to handle file upload, download, version control, sharing and collaboration functionality. User management: Implement user management, rights management and user organizational structure. Search function: An efficient search engine has been developed to support fast retrieval of files and metadata. Online editing: Responsible for online editing and collaborative editing of documents. File transcoding: Responsible for batch queuing transcoding of files and generating preview files. Object storage: file blocking and disk placement, storage system management. Web services RESTful API: Use RESTful API to support data interaction and collaboration between the front end and other clients. Cache management Caching strategy: Use caching to improve performance, including page caching, data caching, and session caching. Asynchronous task processing Message queue: Use the message queue system RabbitMQ to handle asynchronous tasks, such as file transcoding, file preview generation, etc. By using the Struts2 and Spring framework, combined with the above design considerations, a powerful, high performance, safe and reliable enterprise network disk back end system can be built to meet user needs and support future expansion and function additions. Cloud infrastructure selection (public cloud SAAS version BabelBird) The choice of public cloud infrastructure can directly affect the performance, reliability and security of enterprise network disk products. The Babel public cloud version selected Alibaba Cloud's ECS, OSS services and CDN distribution business after many comparisons. Currently (in 2023), the Babel system running in public cloud SAAS mode has been operating online with zero server failures for more than 10 years. Cloud service provider selection The business server SAAS version BabelBird uses Alibaba Cloud's ECS (cloud server) cluster Alibaba Cloud's ECS is an elastic computing service that provides you with virtual machine instances so that you can run applications in the cloud. These are some of the key advantages of choosing ECS: Flexibility: ECS allows you to create, start and stop virtual machine instances as needed. This means you can scale your computing resources up or down based on your traffic needs. Scalability: Alibaba Cloud provides a variety of ECS instances of different specifications to meet the needs of different workloads. You can choose based on the performance requirements of your application. Reliability: Alibaba Cloud's ECS instances are generally highly available, providing multiple data centers and availability zones to ensure business continuity. Security: Alibaba Cloud provides various security features, including network isolation, firewalls, and security groups, to help you protect your virtual machine instances from malicious attacks. The object storage SAAS version of Babel uses Alibaba Cloud's OSS (Object Storage Service) Alibaba Cloud's OSS is a highly scalable, safe and reliable cloud storage service suitable for storing and managing large amounts of files and data. Here are some advantages of choosing OSS: Scalable storage: OSS provides scalable storage capacity that can be dynamically expanded according to your needs. This is very important for file storage in enterprise network disk products. Data backup and recovery: Alibaba Cloud's OSS has data backup and version control functions that can help you protect your data from loss or damage. Security: Data stored in OSS is usually protected by encryption and access control to ensure data security. CDN integration: Integrating with CDN services can improve file distribution speed and user experience. To ensure smooth access around the world, BabelBird also uses CDN distribution A CDN (Content Delivery Network) service caches content to globally distributed edge nodes to reduce loading times and improve user experience. Alibaba Cloud's CDN service can bring the following benefits to enterprise network disk products: Fast distribution: Accelerate the distribution of files, ensuring that users can quickly access and download files, regardless of geographical location. Load balancing: CDN can help share the load of the server, reduce the pressure on the server, and improve the performance of the website. Security: CDN services usually have DDoS attack protection features to protect the website from malicious attacks. Global coverage: Alibaba Cloud's CDN service has global coverage, ensuring that your content is quickly delivered to users around the world. Data center location Currently, BabelBird uses two data centers of Alibaba Cloud: Hangzhou Data Center and Weihai Data Center The configuration of one south and one north can ensure the sustainability of services and disaster recovery needs. Database design Database type BabelBird Enterprise Drive uses various types of databases, and can also support Xinchuang's database products or large databases such as Oracle according to customer needs. The default product database of BabelBird is: The core database is a relational database mysql Auxiliary databases include: Redis database, MongoDB database Database schema Data architecture plays a vital role in enterprise network disk systems, ensuring high availability, performance and consistency of data. The following is the database structure of BabelBird: A. Master slave database architecture Master The main library is responsible for processing write operations, including users uploading files, modifying file information, etc. The main database provides high availability, data consistency and transaction processing. Slave The slave library is mainly used for reading operations, including file query and search. The slave library can provide load balancing and share the read load of the master library. Data synchronization: Use data replication mechanism to ensure that the data of the slave database and the master database are synchronized. Failover: The slave database can take over write operations when the master database fails, ensuring system continuity. B. Relational database (MySQL) Database design The database is designed to support file and user management, including the definition of tables such as file metadata, user information, and permissions. The relationship between data tables is clear, and foreign keys are used to maintain data consistency. Data redundancy The slave database in the master slave architecture is used for data redundancy to prevent data loss when the master database fails. The data synchronization mechanism ensures that the data of the slave database is consistent with that of the master database. C. NoSQL database (MongoDB) File metadata storage MongoDB can be used to store metadata of files, such as file name, size, version information, etc. MongoDB with elastic schema works well with changing data schemas. D. Cache database (Redis) Cache read data Redis is used to cache frequently read data to reduce the load on the database. Cached data can include user session information, popular files, access logs, etc. E. Data backup and recovery Backup strategy Regularly back up the data of the master and slave databases to ensure data security. Babel backup data is stored in reliable storage in various geographical locations. disaster recovery We develop detailed recovery plans that include steps and timelines for restoring data from backups. The Babel operations team regularly tests the disaster recovery process to ensure its effectiveness. F. Data consistency and transaction management Transaction support Use database transactions to ensure consistency across a range of operations, such as file uploads, sharing, and permission changes. Transactions should be managed correctly to avoid data corruption and inconsistency. Concurrency control Use database locks and isolation levels to manage concurrent access to avoid data races and conflicts. G. Monitoring and Performance Optimization Performance monitoring Implement database performance monitoring, including query response time, load, and resource utilization. Perform performance adjustments based on monitoring results to ensure database stability and performance. Query optimization Optimize complex queries to improve query performance, including index optimization and query plan analysis. These data architecture elements will help ensure that your enterprise network disk system can achieve high availability, excellent performance, and data security. With proper database design and maintenance, you can provide stable and reliable services that meet user needs and ensure data integrity. Data backup and recovery strategy (public cloud) A. Data backup Regular backup plan: BabelBird has a regular backup plan to ensure continuous backup of data (data backup in the early morning every day). Full backup and incremental backup: Babel adopts a combined strategy of full backup and incremental backup. A full backup backs up all data in the database, while an incremental backup only backs up data that has changed since the last backup to reduce backup time and storage space consumption. Multiple backup locations: The public cloud version of BabelBird has two geographical locations: Hangzhou computer room and Weihai computer room to cope with natural disasters or hardware failures. Cloud storage and remote data centers are common backup storage options. Automated backup: BabelBird's database backup adopts a fully automatic backup mechanism without manual intervention to improve reliability. Backup testing: We regularly test backups to ensure their integrity and availability. Test by restoring the backup data to a test environment and verifying the consistency of the data. B. Disaster recovery Recovery Plan: We create a detailed recovery plan that clearly identifies each step and responsibility. Make sure team members understand how to perform the recovery process. Backup and recovery testing: We regularly test our backup and recovery processes to ensure that data can be restored quickly and efficiently in the event of an emergency. Testing should include simulations of various failure scenarios. Backup monitoring: Monitor the running status of backup tasks, and automatically remind and report errors when problems occur to ensure the normal operation of the backup system. Disaster recovery team: We have a dedicated disaster recovery team, on call 24/7, responsible for taking action in emergencies to ensure the continued operation of the business. Communication plan: We have established an effective communication plan and automatic alert message delivery monitoring to inform relevant stakeholders about disaster events and recovery processes. Documentation and training: Ensure detailed documentation of recovery plans and procedures and provide training to team members on recovery strategies and procedures. The above strategies and efforts are based on ensuring the security and availability of database data and minimizing the risk of data loss and system downtime." }, { "lang": "en", "slug": "performance-scalability", "title": "Performance optimization and scalability", "description": "Introduction to load balancing, caching, asynchronous tasks, file chunking, deduplication, clustering, containerization, and SOA service architecture.", "category": "Architecture And Storage", "top_category": "部署指南", "keywords": [ "performance", "Scalability", "load balancing", "cache" ], "url": "en/performance-scalability.html", "source": "content/en/performance-scalability.md", "summary": "Performance optimization and scalability Performance optimization Performance monitoring: Real time performance monitoring, including transcoding speed, cache hit rate and response time, and automatic clearing of the queue and retry processing when errors occur. Notify operation and maintenance personnel via SMS of serious errors. Resource adjustment: Based on monitoring results and load conditions, preview and transcoding resources are dynamically adjusted to ensure high performance and availability. Integration testing Performance test: Conduct performance tests that simulate a large number of concurrent preview and transcoding requests to evaluate how the system performs under heavy load.", "headings": [ { "level": 1, "title": "Performance optimization and scalability", "id": "performance-optimization-and-scalability" }, { "level": 3, "title": "Performance optimization", "id": "performance-optimization" }, { "level": 2, "title": "Security", "id": "security" }, { "level": 3, "title": "Secure architecture", "id": "secure-architecture" }, { "level": 3, "title": "User Authentication and Authorization (SSO)", "id": "user-authentication-and-authorization-sso" }, { "level": 3, "title": "User experience", "id": "user-experience" }, { "level": 3, "title": "Overview", "id": "overview" }, { "level": 3, "title": "Overview", "id": "overview-2" }, { "level": 3, "title": "Overview", "id": "overview-3" }, { "level": 2, "title": "Main functional modules", "id": "main-functional-modules" }, { "level": 3, "title": "Technical features", "id": "technical-features" }, { "level": 3, "title": "Advantages", "id": "advantages" }, { "level": 3, "title": "Introduction", "id": "introduction" }, { "level": 3, "title": "Technical features", "id": "technical-features-2" }, { "level": 3, "title": "Common file management functions", "id": "common-file-management-functions" }, { "level": 3, "title": "Version Management Overview", "id": "version-management-overview" }, { "level": 3, "title": "Technical implementation", "id": "technical-implementation" }, { "level": 3, "title": "Version update method", "id": "version-update-method" }, { "level": 3, "title": "Version management function", "id": "version-management-function" }, { "level": 3, "title": "Enterprise Control", "id": "enterprise-control" }, { "level": 3, "title": "Search module overview", "id": "search-module-overview" }, { "level": 3, "title": "Search with permission judgment", "id": "search-with-permission-judgment" }, { "level": 3, "title": "Technical basis", "id": "technical-basis" }, { "level": 3, "title": "Search function", "id": "search-function" }, { "level": 3, "title": "Performance optimization", "id": "performance-optimization-2" }, { "level": 3, "title": "Future development", "id": "future-development" }, { "level": 3, "title": "Overview of online editing module", "id": "overview-of-online-editing-module" }, { "level": 3, "title": "Technical basis", "id": "technical-basis-2" }, { "level": 3, "title": "Main functions", "id": "main-functions" }, { "level": 3, "title": "user experience", "id": "user-experience-2" }, { "level": 3, "title": "Enterprise collaboration", "id": "enterprise-collaboration" }, { "level": 3, "title": "Open API", "id": "open-api" }, { "level": 3, "title": "Other online editors", "id": "other-online-editors" }, { "level": 3, "title": "Client editing overview", "id": "client-editing-overview" }, { "level": 3, "title": "Technical implementation", "id": "technical-implementation-2" }, { "level": 3, "title": "Main functions", "id": "main-functions-2" }, { "level": 3, "title": "User experience", "id": "user-experience-3" }, { "level": 3, "title": "Technical Challenges", "id": "technical-challenges" }, { "level": 3, "title": "Sharing function", "id": "sharing-function" }, { "level": 3, "title": "Outbound function (send files)", "id": "outbound-function-send-files" }, { "level": 3, "title": "User Controls and Enterprise Policies", "id": "user-controls-and-enterprise-policies" }, { "level": 3, "title": "Flexibility and convenience", "id": "flexibility-and-convenience" }, { "level": 3, "title": "Technical architecture", "id": "technical-architecture" }, { "level": 3, "title": "Applicable file types", "id": "applicable-file-types" }, { "level": 3, "title": "Previewer type", "id": "previewer-type" }, { "level": 3, "title": "Comment type", "id": "comment-type" }, { "level": 3, "title": "Function module", "id": "function-module" }, { "level": 3, "title": "Main features", "id": "main-features" }, { "level": 3, "title": "Technical architecture", "id": "technical-architecture-2" }, { "level": 3, "title": "Advantages of document review", "id": "advantages-of-document-review" }, { "level": 3, "title": "Role permissions", "id": "role-permissions" }, { "level": 3, "title": "File permissions", "id": "file-permissions" }, { "level": 3, "title": "Summary", "id": "summary" }, { "level": 3, "title": "Overview", "id": "overview-4" }, { "level": 3, "title": "How to use", "id": "how-to-use" }, { "level": 3, "title": "Summary", "id": "summary-2" }, { "level": 3, "title": "Overview", "id": "overview-5" }, { "level": 3, "title": "Main features", "id": "main-features-2" }, { "level": 3, "title": "Technical advantages (compared to WebDAV and SMB)", "id": "technical-advantages-compared-to-webdav-and-smb" }, { "level": 3, "title": "Application scenarios", "id": "application-scenarios" }, { "level": 3, "title": "Main features", "id": "main-features-3" }, { "level": 3, "title": "Technical architecture", "id": "technical-architecture-3" }, { "level": 3, "title": "Advantages of file management", "id": "advantages-of-file-management" }, { "level": 3, "title": "Main features", "id": "main-features-4" }, { "level": 3, "title": "Technical architecture", "id": "technical-architecture-4" }, { "level": 3, "title": "Advantages of logs and reports", "id": "advantages-of-logs-and-reports" }, { "level": 3, "title": "Dynamic column", "id": "dynamic-column" }, { "level": 3, "title": "Notification section", "id": "notification-section" }, { "level": 3, "title": "Personalization", "id": "personalization" }, { "level": 3, "title": "Application scenarios", "id": "application-scenarios-2" }, { "level": 3, "title": "Overview", "id": "overview-6" }, { "level": 3, "title": "Main functions", "id": "main-functions-3" }, { "level": 3, "title": "Application scenarios", "id": "application-scenarios-3" }, { "level": 3, "title": "Summary", "id": "summary-3" }, { "level": 3, "title": "Overview", "id": "overview-7" }, { "level": 3, "title": "Main functions", "id": "main-functions-4" }, { "level": 3, "title": "Application scenarios", "id": "application-scenarios-4" }, { "level": 3, "title": "Main columns", "id": "main-columns" }, { "level": 3, "title": "The three main modules of Zhichao AI", "id": "the-three-main-modules-of-zhichao-ai" }, { "level": 3, "title": "Technical Solutions", "id": "technical-solutions" }, { "level": 3, "title": "Advantages", "id": "advantages-2" }, { "level": 3, "title": "Multi task collaboration and execution flow weight", "id": "multi-task-collaboration-and-execution-flow-weight" }, { "level": 3, "title": "Function Overview", "id": "function-overview" }, { "level": 3, "title": "Core operation and configuration rules", "id": "core-operation-and-configuration-rules" }, { "level": 3, "title": "Permissions and data security control", "id": "permissions-and-data-security-control" }, { "level": 3, "title": "Typical business application scenarios", "id": "typical-business-application-scenarios" }, { "level": 3, "title": "Function Overview", "id": "function-overview-2" }, { "level": 3, "title": "Scope of application and permission control", "id": "scope-of-application-and-permission-control" }, { "level": 3, "title": "Core rule engine and configuration dimensions", "id": "core-rule-engine-and-configuration-dimensions" }, { "level": 3, "title": "Refined pruning and anti conflict mechanism of original names", "id": "refined-pruning-and-anti-conflict-mechanism-of-original-names" }, { "level": 3, "title": "Global formatted output control", "id": "global-formatted-output-control" }, { "level": 3, "title": "Function Overview", "id": "function-overview-3" }, { "level": 3, "title": "Execution logic and boundary conditions", "id": "execution-logic-and-boundary-conditions" }, { "level": 3, "title": "Extensive format compatibility matrix", "id": "extensive-format-compatibility-matrix" }, { "level": 3, "title": "Function Overview", "id": "function-overview-4" }, { "level": 3, "title": "Flexible triggering mechanism and scope", "id": "flexible-triggering-mechanism-and-scope" }, { "level": 3, "title": "Core intelligent sorting rule engine", "id": "core-intelligent-sorting-rule-engine" }, { "level": 3, "title": "Business scenarios and function overview", "id": "business-scenarios-and-function-overview" }, { "level": 3, "title": "Signature asset library and personalized configuration", "id": "signature-asset-library-and-personalized-configuration" }, { "level": 3, "title": "Intelligent adaptive interaction and immersive guidance system", "id": "intelligent-adaptive-interaction-and-immersive-guidance-system" }, { "level": 3, "title": "Function Overview and Business Value", "id": "function-overview-and-business-value" }, { "level": 3, "title": "Large scale generation of standard directory arrays", "id": "large-scale-generation-of-standard-directory-arrays" }, { "level": 3, "title": "\"One click deployment\" of project level folders and permissions", "id": "one-click-deployment-of-project-level-folders-and-permissions" }, { "level": 3, "title": "Real time status monitoring and intelligent fault tolerance mechanism", "id": "real-time-status-monitoring-and-intelligent-fault-tolerance-mechanism" }, { "level": 3, "title": "Scope of use", "id": "scope-of-use" }, { "level": 3, "title": "Problems that need to be solved", "id": "problems-that-need-to-be-solved" }, { "level": 3, "title": "BabelBird Solution", "id": "babelbird-solution" }, { "level": 3, "title": "Basic introduction", "id": "basic-introduction" }, { "level": 2, "title": "User interface", "id": "user-interface" }, { "level": 2, "title": "Performance optimization", "id": "performance-optimization-3" }, { "level": 3, "title": "Advantages", "id": "advantages-3" }, { "level": 3, "title": "Advantages", "id": "advantages-4" }, { "level": 3, "title": "Advantages", "id": "advantages-5" }, { "level": 3, "title": "Advantages", "id": "advantages-6" }, { "level": 2, "title": "Scalability", "id": "scalability" } ], "images": [], "text": "Performance optimization and scalability Performance optimization Performance monitoring: Real time performance monitoring, including transcoding speed, cache hit rate and response time, and automatic clearing of the queue and retry processing when errors occur. Notify operation and maintenance personnel via SMS of serious errors. Resource adjustment: Based on monitoring results and load conditions, preview and transcoding resources are dynamically adjusted to ensure high performance and availability. Integration testing Performance test: Conduct performance tests that simulate a large number of concurrent preview and transcoding requests to evaluate how the system performs under heavy load. office family files Babel supports online preview of files from the Microsoft office family and WPS. To ensure the display accuracy of office files, especially word files, Babel provides two ways to preview office files: Use the office transcoding module running on the Windows server to transcode the file and preview it (default). A window server needs to be deployed to generate preview files. It can open and preview word files and ppt files quite accurately with Microsoft Office or WPS. Supports using BabelViewer to annotate, discuss, circle, and compare versions of files. You can use the \"Zhichao AI\" document assistant function. Because there are no layout or font problems with Excel files, they are previewed using the preview function of the online office. All preview files can have embedded watermarks and can be saved as watermarked PDF files. Use the preview function of the online office running on the Linux server to provide online preview of office and wps files. For users who can only use Linux and do not have high requirements for the accuracy of the word file preview format. Due to differences in system fonts, online office parsing, etc., the online office in the Linux system cannot perfectly display the layout of the word file at 1:1. There will be slight differences in aspects such as bullet numbering, paragraph height, paging, and the position of inserted graphics. Because there are no layout or font problems with Excel files, they are previewed using the preview function of the online office. Word and ppt files opened using the online office preview function will no longer support the annotation function of the Babel previewer. The document assistant function of \"Zhichao AI\" is not supported. All preview files can have embedded watermarks and can be saved as watermarked PDF files. Taking into account the performance of the browser and the efficiency of the server, there will be a certain file size limit for online preview of office files. Files exceeding this limit cannot be previewed online. Private cloud users can customize these limits, but it is not recommended to increase them too high. The maximum previewable file size of Word (Document) documents is 200MB. The maximum preview size of PPT (slideshow) documents is 200MB. The maximum preview size of Excel (table) documents is 50MB. Pictures and graphics files Babel supports online preview of most image files, including psd, gif family, jpg family, bmp family, png, raw family (part), arw, tif, TIFF, dicom, ico and other files. It also supports the dicom format commonly used in medical graphics. And thanks to Babel's powerful image processing technology, Babel can preview ultra high resolution large pictures online in a 1:1 manner (optional component), annotate and discuss the pictures, and Babel supports reading the metadata of the photos. Image formats such as PSD, RAW, and BMP require automatic transcoding by the server before they can be previewed. Under normal circumstances (the large image display module is not turned on) large images with a resolution exceeding 4K will be processed by the server into a size and format that is convenient for web page display. After turning on the large image display module, the server will cut the large image into several small pieces and load them into 1:1 displays, which will consume a lot of server resources. Pictures with transparent backgrounds such as PNG can also show transparency in BabelBird, and the background can be changed. The BabelBird system will read image metadata information for search, query, and sorting. This information includes: resolution, size, shooting equipment, shooting time, shooting location. All previewable image formats will generate thumbnails for quick search in file list display and waterfall flow mode display. All image formats support annotation discussion, circle drawing and version comparison in BabelViewer. If the watermark function is turned on, the server will preprocess the previewed image and embed the watermark in the image. All image files can be saved as watermarked PDF files. BabelBird can also well support online preview of vector graphics, including but not limited to ai, dwg, dcm, dxf, dwt, pdf, eps, svg, idml, indd... and other vector graphics formats. More importantly, Babel can open documents in these formats in vector rendering, which means that such graphics can be enlarged dozens of times in Babel without blurring or distortion. AI, eps, ind and other files need to be automatically transcoded by the server before they can be previewed. Displayed in vector format, supporting changing background color. The graphics will not be distorted or blurred after enlargement. Other features are the same as images. It also supports embedding watermarks, saving as watermarked PDF, annotating discussions in BabelViewer, circle drawing and version comparison, and generating file list previews. 3D and CAD files Thanks to BabelViewer's support for 3D formats, we support online preview of dae, 3ds, abc, fbx, mtl, obj, ply, stl, x3d and other 3D graphics by default, and support annotation discussions in 3D space. Currently, BabelBird Previewer only supports single file 3D graphics. If the file has plug in files such as plug in skin, it will only be able to load the model itself. 3D files currently do not support generating previews, but custom development is supported if there is a need for this. 3D files can be rotated, enlarged, reduced, and split in the Babel Previewer, and annotation discussion points can be established. The system will remember the viewport when the annotation was created. Clicking an annotation will automatically rotate to the perspective when the annotation was created. If you need to support professional formats such as Revit, Solidworks, 3DMax, etc., private deployment users can choose to access third party 3D online display and transcoding plug ins (such as Autodesk viewer), which will incur related fees. Previewing 3D files on mobile devices is currently not supported. Only supports previewing 3D files on web pages and clients. Babel supports preview of CAD files. Such as: dwg, dwt, dxf formats. Currently on the public cloud, Babel provides powerful CAD preview services to professional and enterprise version users. Private users who want to preview CAD files need to purchase the corresponding CAD transcoding service privatization authorization. Babel CAD preview supports CAD version R12 2021. CAD files can generate preview thumbnails for file list and waterfall mode. Compatible with Tianzheng full professional T20V7 version. Supports previewing and annotating CAD files in browsers, clients, and mobile terminals. Supports drawing browsing above 100Mbps. Layer open/hide/multi select/select all. Layout switching, view pan, zoom, change background color, eagle eye view. Audio and video transcoding Without using a transcoding server BabelBird can directly play video files that support the HTML5 standard online without the need for transcoding services. The supported formats are as follows: Video file formats MP4: MPEG 4 Part 14, supports H.264 encoding. Almost all browsers support this format. WebM: A format developed by Google that uses VP8 or VP9 encoding and can be played in most modern browsers Ogg: Open media format, using Vorbis encoding, can be played in most modern browsers. Audio file formats MP3: MPEG 1 or MPEG 2 Audio Layer III, can be played in almost all browsers. AAC: Advanced Audio Coding, can be played in most modern browsers. Ogg: Open media format, using Vorbis encoding, can be played in most modern browsers. WAV: Waveform Audio File Format, can be played in almost all browsers, but the file size is large and not suitable for playing on the Internet. Compatibility Video compatibility Audio compatibility When using a transcoding server If you need to use BabelBird to manage and query a large number of video materials, you need to build a dedicated video transcoding server and purchase the corresponding video transcoding module authorization. (Currently this service only supports private deployment users) BabelBird video transcoding module uses FFmpeg solution. FFmpeg supports more than 40 encodings such as MPEG, DivX, MPEG4, AC3, DV, FLV, etc., and more than 90 decodings such as AVI, MPEG, OGG, Matroska, ASF, etc. FFmpeg supports more than 280 types of codecs, covering almost all common audio and video encoding formats, and can decode almost all audio and video. Hardware configuration required for video transcoding server Video transcoding is a service that consumes considerable computing resources and requires a dedicated physical machine to perform the transcoding operation. At the same time, server performance requirements are related to the type, duration and bit rate of the video that needs to be transcoded. Based on the daily conversion of 50 hours of HDR 4K video (using CUDA) to 1080P H.264 AC3 MP4, the required server hardware configuration is as follows: Server type Configuration requirements Operating system Server purpose Notes Video transcoding server Xeon Intel E5 2630v3CPU 2 64G memory 2TB SSD hard drive + Nvidia Tesla M4 4G graphics card Linux Video transcoding server Using GPU (CUDA) The transcoding time required varies depending on the video bit rate. Under normal circumstances, it takes 8 seconds to transcode a 100 second 2K video into 1080P MP4 (using the hardware configuration above). If there are many videos being transcoded at the same time, the server will perform multi thread queuing processing. After using the transcoding server, the video file can be played after the transcoding is completed, and the thumbnails can be viewed in the file list. Security Secure architecture Security is key to business! Babel prioritizes security from product design to architecture construction and server management, and includes many important security features. You can control the access behavior of each file and each member, add file watermarks, view access logs, classify important files into archives, and set encryption levels and security policies for files and departments... This series of measures can protect important digital assets to the greatest extent. At the same time, BabelBird uses EV SSL certification with the highest security level, bank level encrypted transmission, and distributed backup in multiple computer rooms to ensure that your data is safe and worry free. These measures have enabled BabelBird to obtain QUALYS security A+ certification, and we also have ISO27001 information security quality system certification. Since its launch, BabelBird has implemented full link encrypted transmission and storage from uploading, downloading, to disk. With detailed processing of rights management and file management, as well as risk analysis and corresponding functional response strategies encountered in various usage scenarios, BabelBird has become one of the most secure enterprise network disks on the market. Figure: Babel bird data transmission link Firewall, bastion host, VPN, SSL... In terms of transmission and server deployment architecture, we have more and more means to ensure the data security of the system. However, according to our many years of experience in providing enterprise security services, 80% of data breaches often originate from insider leaks and management chaos. Even if the system is physically isolated, there is no way to eliminate the risk of data leakage. Babel has considered this from the beginning of product design, providing a variety of safety designs and functions from the perspectives of management, personnel and equipment. A variety of optional settings and solutions are also provided at the contradiction between ease of use and security. Ensure data security as much as possible from the product structure and usage logic. Significantly eliminate the risk of data leakage due to insider negligence or sabotage. User Authentication and Authorization (SSO) Own user system Babel Free User System Authentication Types Account type Verification method Remarks Email Password, verification code Public cloud needs to be bound to a mobile phone number for verification Mobile phone number (global) Password, verification code The private cloud needs to be connected to the SMS sending platform User ID Password Only supported by private clouds. If you forget your password, it can only be reset by the administrator. When logging in for the first time, you will be asked to forcefully reset the password WeChat Scan code, APP jump (mobile) Only supported by public cloud, need to bind mobile phone number for verification Babel supports a mix of authentication types. Multi factor authentication (MFA) could be mandated to improve security Hybrid authentication: When using single sign on (SSO), it supports using your own user system and SSO at the same time. Users can choose to log in using their own credentials or log in through SSO (such as using corporate WeChat to scan the QR code to log in or using the account password to log in). Single Sign On (SSO) integration Single Sign On (SSO) integration is a key feature in enterprise network disk products. It allows users to access multiple different applications and services after one authentication, improving user experience and security. Babel supports OAuth2.0, CAS and other methods to integrate single sign on, and has been actually used in docking with various systems. Supported SSO standards and protocols BabelBird Enterprise Drive supports a variety of SSO standards and protocols, including but not limited to the following: ADFS integration: Babel supports integration with Active Directory Federation Services (ADFS), which makes Windows Authentication based SSO possible. This integration allows users within the enterprise to log in using their Windows credentials. AD domain controller integration: Babel also supports integration with an enterprise's local Active Directory (AD) domain controller. This allows internal enterprise users to log in using their local domain credentials. Enterprise WeChat integration: BabelBird supports docking with corporate WeChat, which allows companies to directly use corporate WeChat accounts to scan QR codes to authenticate and log in. And you can simultaneously import WeChat's organizational structure and users, use Enterprise WeChat to send notifications, and access BabelBird in the workbench. DingTalk integration: BabelBird supports docking with DingTalk, which allows enterprises to directly use DingTalk accounts to scan and authenticate login. You can also import DingTalk's organizational structure and users simultaneously, use DingTalk to send notifications, and access BabelBird in the DingTalk workbench. Feishu integration: BabelBird supports docking with Feishu, which allows enterprises to directly use Feishu accounts to scan and authenticate login. You can also import Feishu's organizational structure and users simultaneously, use Feishu to send notifications, and access BabelBird in the Feishu workbench. Integrated documentation: The integration of AD Domain Control, Enterprise WeChat, DingTalk, Feishu, and Zhiyuan OA has been embedded in the privatized version of BabelBird. After purchasing the corresponding modules, users only need to configure them according to the corresponding documents before they can be used. For relevant configuration documents, please consult BabelBird customer service personnel. Third party SSO integration: If your organization uses a third party SSO provider (such as Okta, OneLogin, Auth0, Qianfan, Panwei, etc.), we also support product integration with these providers. This means that external users can log in with SSO through these vendors' products. But this requires secondary development and a certain fee. Third party own user system integration We understand that many organizations may have their own user systems at the same time, so our SSO integration supports hybrid authentication: Hybrid authentication: Our system allows users to choose between logging in using their own credentials or using SSO. This provides maximum flexibility to adapt to different user needs. User mapping and synchronization: We ensure that user accounts in our own user system are synchronized with user accounts in SSO. This means that a user's attributes and permissions remain consistent across the system. Security and authorization We pay great attention to the enforcement of security and authorization policies to ensure that only authorized users have access to resources: Authentication strategy: We support flexible authentication strategies, including advanced options like multi factor authentication (MFA). This helps ensure that the user's identity is properly verified. Authorization and access control: We allow administrators to configure and manage user access rights, including authorization of files and resources. This ensures that only authorized users have access to sensitive data. Users imported from other platforms will only have the initial permissions of their department (default is department member). Administrators can uniformly change the initial permission scope of imported users by customizing the \"department member\" role permissions. User experience We focus on user experience and strive to provide a seamless login experience: Login page: Our login page is clear and intuitive, giving users the option to choose different login methods. Users can choose to log in using SSO or log in with their own credentials. At the same time, we also support using the user's own login page for single sign on system (such as the ADFS system authentication page) Single point of logout: If the connected single sign on system (SSO) supports single logout, we can also support single logout, which means that users can log out in any connected application, and the system will automatically log out of sessions in other applications. Access control list (ACL) design Overview In BabelBird Enterprise Drive, permission management is a core component to ensure the security and accessibility of files and resources. ACL (Access Control List) is used to define the access rights of users and roles to resources in different departments. This chapter will introduce our ACL design in detail, including role management, user assignment, role permissions and change management. role management Role definition: We allow administrators to customize roles. Each role represents a set of permissions. There are 32 optional combinations of permissions to form a role. Each role should have a clear name and description so administrators and users understand its functionality. Permission assignment: Each role is assigned specific permissions, which determine the role's ability to operate within the department. Permissions should be carefully chosen to ensure that users have the necessary permissions but are not over authorized. User management User role assignment: Each user can be assigned one or more roles, which determine the user's permissions in different departments. Allow one user to have different roles in different departments to accommodate diverse needs. Association between users and departments: Users should be associated with the departments they belong to so that appropriate permissions are automatically assigned based on department roles. Users can only access the department in which they are located, and have roles that determine access rights within the department. Whether you can access sub departments is also determined by role permissions (roles have permissions to access sub departments). Role permission management Role permission definition: Each role has clearly defined permissions, including readable, writable, deleteable, shareable and other operations. Roles can be added or deleted as needed. Permission inheritance: Our system supports inheritance of permissions. When a user is assigned to a role, they automatically inherit the permissions of that role. This reduces the effort of manually assigning permissions while ensuring consistency. Change management Role permission changes: When an administrator changes the permissions of a role, the permissions of all users with that role in the department also change accordingly. We will log these changes in detail for auditing and troubleshooting purposes. Permission audit: Security administrators can regularly audit roles and user permissions to ensure the accuracy and security of authorization. Permissions that are no longer needed should be canceled promptly. security Access control: BabelBird Enterprise Drive's ACL system will strictly control user and role access to resources. Only authorized users with a role in the department can access department files. Departments are isolated from each other, and different confidentiality levels (department security policies) can be set to protect department files. Audit and Monitoring: All permission changes and role changes will leave log records. Convenient management and query. Implement monitoring and auditing mechanisms to monitor permission changes and access activities to detect and respond to potential risks in a timely manner. best practices Principle of least privilege: Follow the principle of least privilege, which means giving users and roles the minimum permissions required to reduce potential security risks. Department files can use file access control to accurately increase the permissions of a certain member (or a certain role) and set the permission validity period. Regular review: Regularly review role and permission configurations to ensure system security and performance. future expansion Multi tenant support: Public cloud systems support multi tenant control. Private cloud considers extending the ACL system to a multi tenant environment to support the needs of multiple customers or organizations. Data encryption Data transmission encryption (SSL/TLS) encryption protocol At BabelBird Enterprise Drive, we take the security of data transmission very seriously. In order to ensure that data is protected during transmission, we use the Secure Socket Layer (SSL) protocol to implement transmission encryption. HTTPS: We use the HTTPS protocol, which is a secure version of HTTP, to encrypt all data transfers. HTTPS provides end to end data encryption through the TLS/SSL protocol, preventing third party malicious users from intercepting or eavesdropping on transmitted data. Certificate management SHA 256 certificate: Our SSL certificates are hashed with SHA 256, a powerful hashing algorithm that provides advanced security and integrity protection. SHA 256 certificates are critical for verifying the server's identity and protecting data transfers. Certificate update: BabelBird Enterprise Drive will regularly update the SSL certificate to ensure the validity and security of the certificate. We monitor certificate expiration dates and renew them in advance. Data encryption Data transmission encryption: All data transmission between BabelBird Enterprise Drive and user terminals will be encrypted by TLS/SSL. This includes user logins, file uploads and downloads, and the transmission of any sensitive data. Data integrity protection: TLS/SSL not only provides data encryption, but also verifies the integrity of the data during transmission to prevent data from being tampered with or damaged. security Strict encryption policy: We follow strict encryption policies to ensure that all data transmissions pass through secure channels and cannot be accessed by unauthorized parties. Protect user privacy: Encryption of data transmission helps protect users' privacy and sensitive information, including personally identifiable information and confidential documents. best practices Security upgrade: We will continue to monitor new security standards and best practices to ensure that the security of data transmission encryption is continuously improved. Security audit: We conduct regular security audits and vulnerability scans to ensure that our encryption mechanisms are not affected by potential threats. Pictured: BabelBird receives A+ security verification from Qualys SSL Scan Data storage encryption Overview In BabelBird Enterprise Drive, we use advanced block encryption technology to ensure the security and integrity of files. We use chunked encryption to break files into small chunks, each chunk is hashed and then stored in an object storage system. This technology ensures that even if control of the server or the hard drive is compromised, the attacker cannot obtain the complete file contents. Block encryption File chunking: Files uploaded to BabelBird Enterprise Drive will be divided into several small chunks (chunks). The size of each tile can be configured based on system needs to balance performance and security. Hash encryption: Each small block is hashed, using a powerful hashing algorithm to ensure data integrity. The hash value will be stored along with the stored chunk for subsequent verification. Storage security Object storage: The encrypted small blocks will be stored in the object storage system of BabelBird Enterprise Drive to ensure high availability and data redundancy. Unrecoverable encryption: We use an irreversible hash encryption algorithm to ensure that the small blocks stored cannot be restored to the original file content to ensure the security of file storage. Secure transmission: Small pieces of data are also encrypted when transferred to the object storage system to prevent man in the middle attacks. File download Temporary download link: When a user needs to download a file, the authentication system will dynamically combine the chunks to form a temporary download link. This link is unique and only valid for a short period of time for downloading. To download again, you need to regenerate the download link. This setting prevents files from being exposed by obtaining download links. Download decryption: When the user requests a download, BabelBird Enterprise Drive will decrypt the chunked data on the server side and then merge it into a complete file. This ensures that the file will not be exposed to any unauthorized accessor even if the hard drive is illegally read while the file is being stored. security Data isolation: Blocked encryption technology breaks data into small chunks, each of which is encrypted with an independent hash to prevent the entire file from being exposed. Irreducibility: The use of an irreversible hash algorithm ensures that the data is irreducible. Even if an attacker obtains a small piece of data, the original file cannot be restored due to missing data. Prevent data leakage Security audit log Overview In BabelBird Enterprise Drive, we emphasize the traceability and security of data access and operations. In order to achieve this goal, we have established a powerful access log system to record historical access logs of the entire system. These logs include file uploads and downloads, permission changes, user discussion comments, file additions, deletions, modifications, approvals, and department changes. This chapter will introduce our security audit log system and role management in detail. Access log function Comprehensive logging: Our log system records various access behaviors of the entire Babel Enterprise network disk, ensuring that every operation can be traced and audited. Recorded operations include but are not limited to file management, authority control, user operations and department management. For more information about BabelBird logs, please refer to: Logs and Reports chapter. Default save time: By default, we save complete access logs for 90 days. This ensures that sufficient historical data is available for auditing and inspection. Expandable storage time: If needed, administrators can extend the retention period of access logs based on specific compliance requirements (supported only on privatized systems). Third party log management system Integrated support: BabelBird can connect to third party log management systems to import access log data to external log platforms for further analysis and long term storage. Security administrator role Security Officer: Security officers have advanced permissions and can view and manage files of all departments at the front desk. In the enterprise management background, the security officer has the following permissions: Develop company security policy (exclusive authority). Manage organizational structure. Member management. Permission management. Security Auditor: Security auditors can view and manage all department files from the front desk. In the enterprise management backend, security auditors have the following permissions: Review corporate security policies. Review the organizational structure. View member permissions. View permission management. View file access logs. security Data isolation: Security audit log data is strictly isolated and only authorized administrators can access and manage them. Confidentiality: The roles of security security officers and security auditors are carefully designed. One is responsible for security policy and the other is responsible for security auditing. They supervise each other to ensure data confidentiality and compliance. Expand Automated alerts: Supports automated alarm mechanism, and monitoring items can be added to promptly notify super administrators when abnormal activities are discovered. The security audit log system of BabelBird Enterprise Drive, including functions, role management and security measures, ensures the traceability of data access and operations, and supports integration with third party log management systems to further improve security and compliance. Security review and testing Penetration testing Test delegate: BabelBird Enterprise Drive will regularly conduct penetration tests by itself or entrust third party organizations, such as NSFOCUS Technology, to conduct penetration tests to evaluate the security of the system. The goal of penetration testing is to use cutting edge attack techniques, mature hacker attack methods, and standard software testing techniques to test the security of the specified system and discover potential security vulnerabilities and risks. Testing phase: Penetration testing includes the following processes: Information collection: Testers collect necessary information, such as IP addresses, DNS records, software version information, IP segments, and public information. Penetration testing: Testers attempt to hack into networks and systems based on the results of the information gathering phase. If successful, normal permissions may be obtained. Flaw Exploitation: A tester attempts to escalate privileges to gain full control of the system. If necessary, they may go back to the information gathering phase and start over. Collection of results: Testers classify and organize the problems discovered in previous stages, such as weaknesses and vulnerabilities, and display them in a centralized manner. Threat analysis: Testers classify the threats found and analyze their potential impact. Output report: Testers write intuitive penetration testing service reports based on the results of testing and analysis. Main goals of penetration testing: Discover security vulnerabilities and potential risks in systems. Evaluate the security of the system, including authentication, access control, data protection, etc. Provides suggestions for improvements to enhance the security of the system. The results of the test will help us take appropriate measures to fix the problems found and improve the overall security of the system. best practices BabelBird Enterprise Drive will conduct regular penetration testing to maintain the security of the system. Use a combination of automated tools and manual testing to increase the comprehensiveness and accuracy of penetration testing. After the test is completed, make timely corrections based on the report to ensure the safety of the system. future expansion We will continue to evolve our penetration testing processes to adapt to evolving security threats. Consider introducing advanced analysis tools to more deeply assess the security of your system. Security vulnerability scanning In order to maintain the security of BabelBird Enterprise Drive, we conduct security vulnerability scans regularly. This measure is designed to automatically detect potential security vulnerabilities in the system and problems that may lead to security threats. We rely on professional scanning tools (such as Qualys, Rapid7 InsightVM, OpenVAS) to ensure that the system continues to remain in a highly secure state. Scanning process Security vulnerability scanning includes the following key stages: Regular scan: We scan our systems for security vulnerabilities on a regular basis, usually at scheduled intervals. Scanning tools automatically perform a series of tests to find potential vulnerabilities. Scan target: The targets of security vulnerability scanning include various aspects such as applications, operating systems, and network devices in the system. Scanning ensures the overall security of the system. Scan results: Scanning tools will identify and report vulnerabilities found in the system. The report will include the type of vulnerability, its severity, and possible remediation recommendations. Fixes: Based on the scan results, we take necessary remediation measures to address the discovered vulnerabilities and issues to ensure the security of the system. BabelBird safety related features Main functional modules Data transfer module The data transmission module is the core component of BabelBird Enterprise Drive and is responsible for managing the data transmission of upload, download, synchronization disk and mapping disk. This module uses a variety of technologies to ensure data security, reliability and efficiency. Technical features File chunking: The data transfer module uses file chunking technology to break large files into small chunks for more efficient transmission and storage. This not only helps reduce network traffic and server resource consumption, but also supports resumed downloads and incremental uploads and downloads. Hash verification (second transmission): Hash verification is used to ensure file integrity during data transfer. Each file block has a corresponding hash value, and the server and client verify these hashes against each other to detect any data corruption or tampering. At the same time, if there is already a file with the same hash code in the storage system, the file does not need to be uploaded again. Realize the instant transmission function. SSL transfer: The data transmission module uses the SSL (Secure Sockets Layer) protocol to encrypt data transmission to ensure the confidentiality and security of data during transmission. This is critical for the transfer of sensitive corporate data. Resume upload from breakpoint: BabelBird Enterprise Drive supports breakpoint resumption, allowing users to continue uploading or downloading files from the last interrupted point without restarting the entire process if the transmission is interrupted. This saves time and bandwidth. Incremental upload and download: The data transfer module also supports incremental uploads and downloads, allowing users to transfer only chunks of files that have changed, rather than the entire file. This is useful in cases of large files and frequent synchronization. Advantages Data integrity: File chunking and hash verification ensure data integrity, reducing the risk of data corruption or tampering. Data security: SSL transmission provides end to end encryption of data, ensuring that data will not be snooped or stolen during transmission. Efficiency: Breakpoint resumption and incremental upload and download improve the efficiency of data transmission, saving time and bandwidth. Save storage space: Using file hash code technology, only one copy of a file with the same hash can be stored on disk. No matter how the file path or file name changes, or how many file copies there are in the network disk, the actual storage space of the file only occupies the capacity of one file. (deduplication storage) High speed upload: Files with the same hash value do not need to be uploaded again. If you upload a file that already exists on the network disk, if the same hash value is detected, it will automatically be marked as uploaded successfully, and there is no need to upload it again. The data transfer module is a key component of BabelBird Enterprise Drive. By adopting these technical features, it ensures that users can upload, download and synchronize their files safely and efficiently. The function of this module is to make BabelBird Enterprise Drive a reliable data management platform. New module The new module is mainly responsible for the creation of files, departments, projects, templates, and folders. In BabelBird, you can directly create new files to work without uploading files. New file creation Office files BabelBird supports creating blank word documents, Excel documents, and PPT documents online. Using the client to create a new document will open the corresponding components of the local office by default to create and edit documents. Creating a new document on the web page will use online office to create and edit documents. Office documents can be edited online (no need to install office) or edited locally using the client (edited using the office installed on your computer). Online editing supports real time collaborative editing by multiple people. When you use the client to call the local office for editing, the document will automatically be locked for editing to prevent others from editing the document and causing conflicts. Text code file Babel Text Editor can create and open all text files online, such as RTF, TXT, HTML, MD, CSS... For the convenience of customers, the public cloud version only supports creating new TXT and MD (markdown files). Private cloud users who need to create text files in other formats can ask for it to be opened. The text editor is different from the online office in that it does not support collaborative editing, but text files can be edited online. Mind maps and flow charts. BabelBird comes with its own mind map module, which can create and edit mind map files online. Mind map files are saved in KM format by default. It can also be exported to KM, TXT, MD, SVG, PNG, and Xmind formats. BabelBird can also optionally support the creation of flow charts, but you need to purchase the corresponding module license (the non standard version comes with it by default). Other third party modules. Internet applications that comply with WebAPI can theoretically connect to BabelBird and create new files. BabelBird provides third party application docking services. Create from template Many customers need to create a large number of folders with the same structure or create files from a specific template (such as a corporate PPT template). Babel supports creating folders and files from templates. Create templates. People with department file management rights can create templates in the New menu. After clicking Create Template, a template folder will be generated. The template folder is similar to an ordinary folder. You can drag files into the folder to upload, create new folders and departments. The files uploaded in the root directory of the template folder become file templates, and the folders created in the template folder are folder templates. As shown below: Figure: Displayed in the template folder Figure: Displayed when creating a new template Create from templates. Departments with permission to create files and folders can select a template when creating a new file to quickly create files or folders that are consistent with the template. Create new departments and projects Departments and projects can also be created using the New function. Create departments. Departments can only be created under the root department of the enterprise file. The department file belongs to the enterprise, and the super administrator can see the root department and the entire file tree. Users with sub department management rights (default department manager role) can create sub departments. Department folders can add department members and complete department level management. Only members who join the department (department members) and members of the superior department who have the \"View sub department files\" permission can access department files. Department members have basic permissions determined by their role in the department. You can use file permission management to manage permissions on files (folders). Project. Users can create projects under department folders in personal files or corporate files. Projects can invite project team members across departments and companies, and even non registered users from outside the company. Anyone with personal files can create personal projects. To create a project user role under a department, you need the \"Create Folder/Project\" permission. Support for creating subprojects in project folders. The parent of the project folder must be a department or a project, which means that departments cannot be created under ordinary folders. The project creator is the project administrator by default. The project can be transferred, and the project administrator can be transferred to other members and other departments. The permissions of members within the project are specified when the project is created. The project is relatively an independent shared folder. Create a new normal folder Create folders under personal files. Users can create any folders under their personal files and manage them by themselves. Create folders under corporate files Folders need to be created in departments under enterprise files (all folders belong to departments). Users with the \"Create Folder/Project\" role in their department can create folders. As long as the user whose role has the \"Create Folder/Project\" permission can create subfolders in any ordinary folder in the department. File management Introduction The file management module is one of the core functions of BabelBird Enterprise Drive. It is used for users to manage and operate files and folders, and pushes different file lists to users according to their permissions. It is also the main interface for users to use the network disk. This module provides a wide range of features to meet the file management and organization needs of business users. Technical features A. File access and organization Paging loading technology: The file management module uses paging loading technology, and the server side database performs file sorting and query operations, and returns the file list to the front desk for paging loading. Such a file list can load hundreds of thousands of rows of data in pages, ensuring that users can efficiently load and browse large numbers of files without affecting performance and user experience. Tree display file list: Babel supports tree like display of file lists, making the organizational structure of files more intuitive and allowing users to easily navigate and manage folders. Permission control: Depending on the user's permissions, the file management module will dynamically display appropriate list items. The file list content seen by different users varies according to different permissions. to ensure that only authorized users can view, edit, or delete specific files and folders. B. File sorting and quick operations Multidimensional sorting: Supports multi dimensional sorting, users can sort by different dimensions such as file name, latest version, file size, etc. File name sorting: Unlike most network disk applications, Babel File Name Sorting supports multi digit sorting in order, so that files whose file names contain numerical numbers can be sorted accurately. (Most network disk file names are sorted only by the first letter, such as: 1, 2, 10, 3, 4, but in BabelBird, the order can be correctly displayed as: 1, 2, 3, 4, 10) Custom global sorting: Users can customize the sorting method suitable for their own global use in the settings. At the same time, the system will remember the sorting method selected by the user in the folder last time, and the next time the folder is opened, it will also be displayed according to the previous sorting. C. Document display and detailed management List mode and waterfall flow mode can be switched: Supports browsing folders in list mode, and can switch to waterfall flow mode for preview. Supports waterfall flow mode browsing of folders (file thumbnails), making file browsing smoother and more intuitive. Folders with many pictures will be automatically adapted to display in waterfall flow mode. File details page: Each file and folder has a detailed details page. Users can manage file information, add file comments, view file access logs, collect statistics on file access, and generate reports. The file details page can also manage file versions. Comment area: Each file or folder has its own comment area, which supports user comments and @mentions of other users to promote team collaboration and feedback. File association: Supports file associated files, allowing users to establish connections between related files for easier access to related information. File attention reminder: Users can remind people who have permission to view files to pay attention to files or folders to ensure that important files are not ignored. D. Advanced search and filtering Advanced search BabelBird supports advanced search function, which can conduct advanced search based on keywords, full text content, time, file format, uploader, search scope, search type and other dimensions. Search BabelBird also supports full text search, which can search for keywords in the file content. You can also use file name search and tag search to find the corresponding file. The search results can be searched again or filtered by filtering Filter function: You can filter based on file tags, types, file description keywords, size, version, uploader, photo metadata, etc. to quickly locate the required files. File tags and categories: Users can tag files to better organize and categorize them. Labels can be managed uniformly by the enterprise to ensure that labels comply with specifications. Tag shortcuts can be added to the left column. Common file management functions A. File transfer and operations Upload and download files: Users can upload and download files, ensuring flexible transfer of data. Supports dragging and uploading folders to facilitate the transfer of large batches of files. The browser supports folder packaging download (less than 100 files or folders less than 500MB in size) The client supports direct download of folders (transfer list) Creation of files and folders: Users can create new files and folders of various types, and also support creating new files or folders from templates to improve work efficiency. File copy and move: Users can copy and move files or folders to organize files easily. Supports copying files or folders to specified directories for file backup and management. Document archiving: Users can archive documents into an archive for long term preservation and retrieval. File pinned to top: Personal files support pinning files or folders to the top for quick access to important files. Department or project administrators can pin portal files or project files to facilitate department members and project members to quickly access important files. Create file or folder shortcuts: Users can create shortcuts to files or folders for quick access. Upload new version: Users can upload a new version of a file, and the system will automatically detect files with duplicate names and provide the option of uploading a new version or renaming the file. Click the Upload new version button to directly upload a new version. Print files as watermarked PDF: When watermarking is turned on, the file can be printed as a watermarked PDF file to ensure the security and confidentiality of the file. Lock files: When files are edited using the client, they are automatically locked to prevent conflicts. Users can also manually lock files in the file list to prevent editing and conflicts by other users. File preview: Supports preview of most files to quickly view file contents. To learn more, check out the Preview and Transcoding chapter. File list display thumbnails: The file management module can display thumbnails of files in the file list, making file browsing more intuitive. Batch file upload and download: BabelBird provides a client specific upload and download module, which supports the upload and download of batch files, and also provides a list display of transferred files. View file details and version management: BabelBird has a dedicated file details interface. In the file details, you can add file descriptions, view basic file information, and view metadata for image files. You can also view file logs, file access and usage, and manage file versions in the details. B. File security and permission control File access control: Department administrators or project administrators can set file access control to precisely control the access permissions of each file or folder for each user or a certain role. File access control takes precedence over members' department role permissions. For example, if a department member role has editing permissions on a certain file, but the department administrator uses file access control to change the member's permissions on the file to \"invisible\", the member will not be able to access the file. File sharing: Supports sharing files and folders, allowing users to set detailed access permissions to control file access. File snapshot sharing: For those who only want to share the current version, users can create a snapshot share of the file. The snapshot share will not be changed by updates to the file content and will maintain the version when the snapshot was created. Version management Version Management Overview Version management is one of the important functions of BabelBird Enterprise Drive. It allows users to track and manage different versions of files, ensuring that file history and updates can be retained and viewed. Babel's version management function is very powerful and supports multiple update methods as well as version rollback and viewing. Technical implementation Version management uses file blocking and incremental saving techniques to store file versions. This means that each change to a file generates a new version that stores only the changed data blocks, reducing storage requirements and increasing efficiency. Enterprise administrators can set the number and storage time of file versions in the enterprise console to control version management policies. The version management feature enables users to flexibly manage file versions to ensure file integrity, history, and security. Version management is a core function of BabelBird Enterprise Drive, aiming to provide excellent user experience and data security. Version update method Babel allows users to update file versions in a variety of ways, including: Manually upload new version: Users can right click the file and select Upload New Version to manually upload the new file and save it as a new version of the file. Detection of files with the same name: When uploading, Babel can detect files with the same file name, and users can choose to upload the new file as a new version of the existing file. Client editing and saving: If a user edits a file using the client and saves it, Babel will save the changes as a new version of the file. Online editing and saving: If the user edits the file using the online editing function on the web page and saves it, a new version will also be generated. Sync folder editing: The Babel client will monitor the synchronized folder for updates. Editing or overwriting files in the synchronized folder and saving them will generate a new version. Map disk editing: Edit the file in the mapped disk and save it. The updated file will also be saved as a new version. Version management function The Babel version management module has the following functions: Version rollback: In the file version list, users can choose to set the old version as the current version to implement version rollback. Version download: Users can choose to download version history to access previous file versions. Version preview: The version management module allows users to preview an old version of a file when clicking on it to see the content of that version. Version comparison: When previewing files in the Babel Previewer, you can select the file comparison function, which supports selecting old and new versions for comparison. Version log: Users can add logs to each file version to record important information and change history of the version. Enterprise Control The version management function of BabelBird Enterprise Drive allows enterprise administrators to make advanced settings in the enterprise console to meet the specific needs of the enterprise. Enterprise administrators can set the number and retention time of file versions based on company policies and compliance requirements to meet the needs of different file types and departments. Such a version management system ensures the data consistency and traceability of files, as well as the integrity of user data. At the same time, it has strong protection against viruses such as ransomware that change the readability of files, because ransomware changes files and requires updated files, and the updated files will form a new version. Users only need to roll back the version to get the files before the attack. Search Search module overview The search module of BabelBird Enterprise Drive is a key function. It is developed based on powerful Elasticsearch technology and database query technology, and is designed to provide efficient, accurate and comprehensive document search functions. The search module not only supports full text search, but also searches the description, comments and file names of documents to meet the search needs of different users. Search with permission judgment Babel's search module not only has a powerful search function, but also uses advanced permission management technology to dynamically determine user permissions to ensure that users can only see files within their permissions. The search results are dynamically generated based on the user's permissions, which means that among the files shared by the user, only the files that the user has permission to view will be searched. This is a critical technology, especially in enterprise environments where permissions can change at any time. Technical basis Elasticsearch: Elasticsearch is an open source search engine known for its efficient distributed architecture and powerful full text search capabilities. Babel uses Elasticsearch as its core search engine to support full text search and advanced query capabilities. Database query: In addition to Elasticsearch, the search module also utilizes database query technology to search the metadata and tag information of documents to provide more comprehensive search results. Document analysis: The search module uses text extraction technology to extract text information from various types of files. This extracted text information is used for search engine indexing and querying. Keyword extraction. Word segmentation optimization: BabelBird has done a lot of word segmentation optimization work, especially for Chinese vocabulary, to improve the word segmentation accuracy and performance of search engines. The optimization of Chinese word segmentation plays a key role in the accuracy of search results. Search function The Babel search module includes the following main functions: Full text search: Users can perform full text searches to find textual content within documents to find files related to keywords. Document description and comment search: The search module supports searching for descriptions and comments added to Babel documents by users, making it easier for users to find specific information. File name search: Users can perform precise file name searches to find specific files. Tag search: Tag search, query, and classification display are available Advanced search BabelBird supports advanced search function, which can conduct advanced search based on keywords, full text content, time, file format, uploader, search scope, search type and other dimensions. Performance optimization The search module has high requirements on server performance. Therefore, for users with private deployment, it is recommended to deploy the search module on an independent virtual machine or server to reduce the performance consumption of other modules. Future development Future versions of Babel will continue to improve the search module and combine AI technology, such as ChatGPT, to implement question and answer chat dialogue search of document content, providing users with a more intelligent search experience. At present, the AI based document analysis and customer service system \"Zhichao AI\" has been launched. For details, please refer to the Zhichao AI chapter. The continuous improvement of the search module will help users find the files and information they need more quickly and accurately. After the introduction of the AI ​​system, users can obtain information in the form of questions and answers, and can cross the contents of multiple documents to draw complete conclusions, which can greatly improve production efficiency and work efficiency. office online editing Overview of online editing module BabelBird Enterprise Drive has been an official partner of OnlyOffice for many years. The online editing module of BabelBird Enterprise Drive is developed based on OnlyOffice technology and optimizes the loading and display of Chinese fonts. Babel Online Editor supports a variety of document formats, including Microsoft Office (Word, Excel, PPT) and WPS Office. Details of the cooperation between BabelBird and OnlyOffice can be found on the official website of OnlyOffice: https://www.onlyoffice.com Technical basis The technical basis of the online editing module includes: OnlyOffice Editor: OnlyOffice is a powerful online office suite that supports online editing of multiple document formats. BabelBird integrates it into the network disk system to provide a high quality online editing experience. Chinese font optimization: In order to overcome the lack of Chinese font loading efficiency in OnlyOffice, BabelBird has been optimized and uses font localization technology to greatly improve the loading and display speed of Chinese fonts, thus improving the user experience. Document lock: BabelBird supports both client editing and online editing, which means that in order to prevent file version conflicts, files must be locked when being edited online and cannot be edited on the client side, and files must be locked when being edited on the client side and cannot be edited online. Main functions BabelBird’s online editing module includes the following main features: Multi format support: Users can edit and view documents in Microsoft Office (Word, Excel, PPT) and WPS Office formats online. Co edit: The online editing module supports multiple users to collaboratively edit documents at the same time. Users can view the changes of other users in real time and edit documents together. This collaborative editing feature is great for team collaboration. compatibility: BabelBird's online editing module is compatible with Microsoft Office and can restore the Office layout and fonts on web pages. Ensure good compatibility of document layout and format when opened in different editors. Open API: BabelBird opens the API of the online editor, allowing other enterprise software to call the API and integrate the online editing function into other applications. user experience The goal of the online editing module is to provide a user friendly and smooth online editing experience. Users can directly open the document that needs to be edited in the network disk, and save it immediately after editing without leaving the network disk interface. This seamless integration improves user efficiency and makes editing documents more convenient. At the same time, BabelBird permission configuration supports \"online editing only\", which means that some users can only edit documents online but cannot download and obtain documents. Enterprise collaboration The BabelBird online editing module is not only suitable for individual users, but also provides a collaborative office platform for enterprises. Team members can edit documents together, share ideas, and work more efficiently through real time collaboration. Open API BabelBird Online Editor API allows enterprises to integrate online editing functions into their own software or third party software, allowing enterprises to fully utilize online editing capabilities. Other online editors BabelBird Standard Edition also integrates other online editors for online editing and creation of MD files, TXT files and even mind maps (such as brain maps). At the same time, BabelBird can also integrate other online editing systems that support HTML5 by connecting to third party APIs, such as Microsoft Office 365 or Kingsoft's web office (WPS). Comes with text editor for online editing. The text editor that comes with BabelBird can edit and preview text files such as TXT, MD, RTF, etc. It can also edit code files such as CSS, JS, JSP... to facilitate users to quickly create document records. Comes with a mind map (mind map) editor. BabelBird comes with its own mind map module, which can create and edit mind map files online. Mind map files are saved in KM format by default. It can also be exported to KM, TXT, MD, SVG, PNG, and Xmind formats. BabelBird can also optionally support the creation of flow charts, but you need to purchase the corresponding module license (the non standard version comes with it by default). Client editing Client editing overview BabelBird Enterprise Drive provides powerful client side editing functions. Users can easily call local editing software to edit cloud documents. After editing and saving, the files will be automatically uploaded to the cloud. This feature not only improves user convenience, but also helps avoid file version conflicts, thereby improving work efficiency. Right click on the file to be edited in the client file list and select Edit to open client editing. The implementation principle of client side editing determines that as long as there is a local editing program, all types of files can be edited on the client side. Technical implementation Implementation technologies for client side editing functions include: Client integration: Both BabelBird's Win client and Mac client support the calling of local editing software, which allows users to open and edit cloud files directly in local software. Cache management: Client side editing uses caching technology to cache the files that need to be edited from the cloud to the local computer and call local applications to open them. When the system detects that the file being edited has been updated, it uploads the updated file as a new version. Good cache management technology can save users' local disk space while ensuring efficiency. Users can also manually clear the file cache in the Babel right click menu. File status detection: Before client side editing, the system checks the status of the file, including whether the file is locked by another user. This helps prevent multiple people from editing the same file at the same time and avoid version conflicts. Automatic locking and unlocking: When a user starts editing a file, the system automatically locks the file to ensure that other users cannot edit the same file at the same time. After editing is completed, the file will be automatically unlocked, a new version will be generated, and the modified file will be uploaded to the cloud. Version conflict handling: Despite the locking mechanism, file version conflicts may occur under certain circumstances, such as network problems or when the file has not been edited for a long time. BabelBird provides a conflict handling interface, allowing users to compare and choose whether to use the cloud version or the local version as the current version. Regardless of the user's choice, the system will ensure that the unselected version will also be uploaded to the cloud as a historical version to prevent data loss. Main functions The main functions of the client editing function include: Local editing: Users can cache the file locally by clicking the local edit button and edit it using the local default application. Babel theoretically supports local editing of all files as long as there is a corresponding local application. Automatic lock: Files are automatically locked while editing to prevent other users from editing at the same time, thus avoiding version conflicts. Automatically unlock: After editing is completed and the app is closed, the file will be automatically unlocked, a new version will be generated, and the modified file will be uploaded to the cloud. Version control: All edited and uploaded files will generate new versions so that users can view and restore previous versions at any time. User experience Client side editing capabilities provide an excellent user experience. Users can edit in the local editor without having to download the file, edit it and then upload it. At the same time, file formats that do not support online editing or online preview can also be opened for editing or preview through client editing. This improves editing efficiency and workflow smoothness. Technical Challenges The technical challenges of client side editing capabilities lie in detecting the status of files, automatically locking and unlocking, and handling conflicting file versions. The system needs to accurately determine whether a file is being edited by another user, while also providing user friendly solutions when conflicts occur. These challenges require a combination of user experience and data integrity. Babel client editor is one of the few functional modules in the industry that can handle these problems well. Share and send out Sharing function BabelBird Enterprise Drive provides a variety of flexible sharing methods, including invitation sharing and link sharing, to meet the different needs of users. Invite to share: Invite sharing is a way to share a file or folder with specific people. Features are as follows: Identity verification: Invitees need to undergo identity verification. They can log in through their Babel account or receive a verification code to confirm their identity. Each invitee can independently manage permissions and set the permission validity period. This means that for the same invitation sharing, different invitees can set different access rights. Permission control: Sharers can customize sharing permissions, including viewing, editing, downloading, etc. This helps to provide granular control over what is shared. Approval mechanism: If the user does not have sharing permissions, the sharing operation needs to be approved to ensure that only authorized personnel can share files. Link sharing: Link sharing allows users to create a public link for others to access a file or folder. Features are as follows: Allow anonymous access: Sharers can choose whether to allow anonymous access. If the anonymous access option is turned off, visitors will need to have a Babel account to access. Snapshot sharing: In snapshot sharing mode, the content shared is the current version at the time of sharing. Even if the file content is updated, the content shared by the snapshot will not change. Password protection: Users can set a password to ensure that only those who know the password can access the shared link. Validity period: Link sharing can set a validity period to ensure that the file will not be made public permanently. Once the validity period expires, the shared link will automatically expire. Custom settings: In the enterprise console, administrators can customize sharing permissions, set sharing behavior by department (support or prohibit sharing), set sharing rules by file (prohibit sharing of high confidence files), and turn off the external sharing function of the entire enterprise. Share log: All sharing behaviors and external access behaviors have independent logs, and each shared access log can be queried. You can know who accessed a shared file or folder when, and updated versions of shared files will alert users. Unified management and sharing: Department administrators can uniformly view and manage all shared files in the entire department. Shared personal files can also be uniformly viewed and managed in the \"My Shared Files\" column to ensure that no omitted shares will be leaked without knowledge. Outbound function (send files) The outgoing function is a way to send files to other users via email or mobile phone number for direct downloading. Outgoing is different from sharing. It is only used for the recipient to download outgoing files without configuring permissions. Features are as follows: Send files: Users can use the outgoing function to send files to other users' email addresses or mobile phone numbers so that they can download and use them directly. The file sending function can also send files to internal users. There will be a notification when the file is received. Click the notification to download or transfer the file. No permissions required: Outsourcing does not require configuration permissions and can be used as long as the user has sharing and download permissions. Email or SMS sending: Outsourcing can send file links via email or SMS to ensure that the recipient can easily obtain the files. Quick download: The recipient can directly download the file by clicking on the link, which is simple and convenient. User Controls and Enterprise Policies Users' sharing permissions can be controlled by enterprise administrators to ensure that file sharing and outgoing files are strictly managed. In addition, enterprise administrators can also customize sharing rules and permissions through the enterprise console to adapt to different enterprise needs. Security Sharing and outgoing functions are subject to strict security controls to protect corporate files from being accessed by unauthorized personnel. Administrators can flexibly configure sharing and outgoing permissions and rules according to the enterprise's security policy. Flexibility and convenience Sharing and outsourcing functions provide enterprises with flexibility and convenience, meeting the needs of different users and scenarios. Users can choose the most suitable sharing method according to specific situations to better manage and share files. Previewer, annotations, and discussions In order to allow users to more conveniently preview files and conduct collaborative discussions while previewing files to improve collaboration efficiency, Babel has developed BabelViewer. Most file formats that can be previewed on Babel can be opened with the previewer. Babel Previewer can not only preview files, but also communicate with collaborators on file content through hand drawing, text discussion, voice (only mobile APP supports the creation of voice annotations) and other methods. At the same time, BabelBird Previewer also supports version comparison, switching versions to view different version annotations, annotation management, approval management and other functions. Technical architecture Use canvas development and multi layer technology The previewer is developed based on Html5 Canvas technology and uses multi layer technology to add annotation and hand drawing layers on top of the file preview layer. It does not affect the file content but allows for annotation discussion and real time hand drawing. Real time collaboration module The real time collaboration module of the previewer ensures that the annotation discussions and hand drawings of multiple users are displayed in real time when previewing files, which means that users can discuss issues with documents or design manuscripts while annotating. Annotation point coordinate system positioning The Babel previewer uses coordinate system positioning to ensure that the annotation points are in the same position under different resolution screens and different browser sizes. Applicable file types BabelBird Previewer can open most pictures and office documents, PDF documents and vector graphics files. For specific supported file types, please refer to the File Types Supported for Online Preview in the Preview and Transcoding chapter. Previewer type Multi page document previewer Supports preview of multi page documents, such as word, PPT, PDF and other formats. For multi page documents, it provides functions such as table of contents, zooming in, and page rotation that are suitable for multi page documents. Image previewer Designed for better preview images. It has functions such as eagle eye, zoom in and out, display original proportion, rotation, etc. Right click to copy the image to the clipboard, making it easy to paste the image directly in WeChat or email. For images with transparency such as PNG, you can change the image background. Graphic previewer Designed to preview vector graphic files such as CAD, SVG, single page PDF, etc., it supports eagle eye, layered display, background change, mouse dragging area enlargement, and vector enlargement. You can switch the encoding mode for SVG files. 3D previewer In order to preview the 3D file design, you can rotate, zoom in and out the 3D file with the mouse wheel, explode the image, and support annotation in 3D space. Comment type Text discussion area Text discussion areas can be created in any area of the preview file (double click to create text discussion comments). Collaborators of the file who have permission to view comments can see the comments and participate in the discussion. The annotation content is displayed in real time, and a text annotation discussion area is equivalent to a group chat for the annotation content. Supports inserting attachments for discussion, and also supports @ and other chat functions. You can set the visibility of comments, such as: only visible to company members, visible to everyone, and only visible to the commenter himself. Text annotation Text annotation can add annotations to document content or photos. Selected text annotation For documents with text, such as word and PDF, you can select a piece of text for annotation. Special symbol insertion For manuscripts with special needs, revision symbols or welding marks (such as CAD drawings) can be inserted Create graphic annotations It also supports the use of graphic frame selection annotations, supporting rectangles, ellipses and arrows. Voice annotation The Babel mobile device APP can create voice annotations. Voice annotations can be viewed (listened to) on web pages and clients, but cannot be created. Hand drawn annotations Supports real time drawing on manuscripts or documents. Participants can see the drawn lines in real time and mark the artist's nickname. Function module Comment management module You can manage created comments and comment status, check other versions of comments, and switch to the corresponding version Review workspace Babel can use comments during document review and display review related panels, allowing reviewers to convey review information more accurately and conveniently. Eagle Eye Eagle Eye can display the area of the image viewport when the image is zoomed in. Version comparison Babel Previewer supports file comparison function and can also compare different versions of files. File directory For files with directories (word, pdf), BabelBird also supports displaying the file directory during preview. Document review BabelBird Enterprise Drive provides a powerful document review function, designed to help users efficiently manage the document approval and revision process. Document review is a collaborative work process that allows users to initiate a document review, invite reviewers to view the document, provide comments and suggestions, and ultimately determine whether the document requires modification or approval. Main features Multi document review: Supports review of multiple documents at the same time. Users can initiate review of multiple documents at one time to ensure an efficient review and approval process. File Lock: Files will be automatically locked during the review process to prevent other users from editing or uploading new versions, ensuring that the file content will not be changed during the review process. File preview and comments: Reviewers can add comments and fill in review comments when previewing the file to provide detailed feedback. This helps to better understand the file content and provide targeted recommendations. Review process: Users can choose different review processes, including freely defining the review process, using a preset review process, or restricting the use of specific review processes. This allows different departments to choose the appropriate approval process based on their needs. Multi stage approval: The approval process supports multiple stages, and one or more approvers can be set for each stage. Users can define a pass ratio, for example, if 50% of approvers pass, a certain stage can be passed. Invite external reviewers: Users can invite external members (via email or mobile phone number) to participate in document review to obtain more feedback from different perspectives, such as inviting external experts during thesis defense. Approval report: After each document review, an approval report will be generated to record the review opinions of participants at each stage for tracking and analysis of the approval results. Review signature: supports inserting a signature on the manuscript after the review is completed and downloading it as a PDF. My Review Column: Users can view and manage all stages of all review documents related to themselves in the \"My Review\" column, including initiated reviews and invited reviews. Technical architecture The implementation of the document review function involves the following technologies and modules: Review process definition: Different review processes are defined in the background, including stage setting, approver selection, passing ratio setting, etc. These processes are available to front end users for selection. Department specific approval processes: Different departments can choose different approval processes and choose to freely define, preset or limit specific approval processes as needed. Multi stage approval: Multi stage approval can be achieved, and each stage has different approval requirements, including the selection of approvers and the passing ratio. You can also set whether a certain stage can be skipped. Invitation of external approvers: Supports inviting external members to participate in document review by email or mobile phone number. Approval reports: Generate approval reports to record review opinions at each stage for tracking and analysis of approval results. Advantages of document review The document review function helps users efficiently manage the document approval and revision process to ensure the accuracy and compliance of document content. Users can use document reviews to ensure documents have been adequately reviewed and discussed to meet their work needs and compliance requirements. The introduction of this feature increases the depth of file collaboration and management, providing users with more powerful file collaboration tools. Permission management Permission management of BabelBird Enterprise Drive is one of its core functions. It runs through the entire system to ensure that users can access and manage files safely and compliantly. The Babel permission system includes two main aspects: role permissions and file permissions. Role permissions Define roles: Babel allows you to define different roles within the enterprise. Each role can include a specific set of permissions to control users' access and operations in department folders. These roles can be created based on department management needs, such as \"Department Administrator\", \"Department Member\", etc. Department role permissions: Each department member can be assigned different access permissions based on their roles in different departments. This means that users can have different levels of permissions in different departments. Flexible management: Babel's role permissions support multiple department roles, and the same role can be used in different departments at the same time. After the permission content of a role is changed, the permissions of members using the same role will also be changed accordingly. Permission combination: Babel bird role permissions support the combination of more than 30 optional permissions to achieve refined user permission control. These permissions cover various access and operation behaviors, such as preview, upload, download, edit, etc. List of optional permissions for roles: File permissions Custom permissions: File permissions can also be customized in the background, and users can choose specific permission types and names. These custom file permissions will be used for file sharing, project management, and file permission control. File access control: File access control allows department members to set specific access permissions on files and folders to override department role permissions. This means that the access behavior of a certain file or folder in the department can be more precisely controlled. File access control only applies to department members and project members. High priority: File access control permissions have a higher priority. If file access control is set, it will override the member's department role permissions or project permissions. Users can set file access permissions as needed. Department File and Folder Control: Users can enable file access control for department files and folders to control access to specific files or folders. Validity period: File access control can set a validity period. After the validity period, the constraints of file access control will become invalid. For example, if a department member who does not have file editing permissions is given the editing permissions for the file, the validity period is 3 days. After 3 days, the permissions granted by the file access control will expire, and the department members' permissions on the files will become the permissions of the member role. Summary The permission management of BabelBird Enterprise Drive is a comprehensive system that can meet the specific needs of different departments and projects of the enterprise. Role permissions and file permissions work together to ensure that users have precise control over file access and operations. This feature helps improve security, compliance and productivity. sync Overview File synchronization is one of the most popular functions of BabelBird Enterprise Drive. It allows users to synchronize any local folder to the cloud or any cloud folder to the local, achieving real time synchronization of cloud and local files. This section contains the following key functions: Synchronization management: Babel supports the creation of multiple synchronizations and can manage them uniformly in the synchronization management list. Multiplayer collaboration: Babel Sync is designed for multiplayer collaboration. It automatically locks files to prevent conflicts caused by multiple people editing at the same time, and also has a conflict handling mechanism and version management. Consistent with permissions: BabelBird Sync will determine the user's permissions. Users without download permission will not download files due to synchronization, ensuring the consistency and closed loop of permissions. This means that users can set which folders can be synchronized through permissions. Multiple synchronization types: Babel supports multiple synchronization types, and users can choose the appropriate synchronization method according to specific needs: Two way synchronization: the cloud and local folders keep the content consistent, and modifications on either side will be synchronized to the other side. One way upward synchronization: local updates will be synchronized to the cloud, but cloud updates will not affect the local. One way downward synchronization: Cloud updates will be synchronized to the local, but local updates will not affect the cloud. Powerful technical advantages: BabelBird's enterprise network disk synchronization function has a number of technical advantages to ensure performance and stability: Support large scale folders: Babel supports folder synchronization of up to 200,000 files. File editing lock: When editing a synchronized file, the file will be automatically locked to prevent conflicts caused by multiple edits. Conflict handling mechanism: For editing conflicts on the same file, Babel provides a conflict handling mechanism to ensure the integrity of the file version. Version management: The file synchronization function and version management work together to ensure that local folders will not be overwritten and lose content due to misoperations and other reasons. Even if a file conflict occurs, the two conflicting versions of the files will be saved. Error handling in asynchronous situations: The file synchronization function also includes error handling and repair in asynchronous situations. How to use Turn on synchronization: right click the local folder and select BabelBird Sync the folder. Select synchronization method: Users can choose the appropriate synchronization method during synchronization, including one way synchronization, two way synchronization, etc. Permission configuration: Through permission configuration, users can implement more customized synchronization methods and restrict file deletion or other operations as needed. Multi person collaboration: Under multi person collaboration, files will be automatically locked when editing to avoid conflicts caused by multiple people editing at the same time. The conflict handling mechanism ensures the consistency of file versions. Version management: The file synchronization function supports version management, and users can view previous file versions and restore them. Summary The file synchronization function of BabelBird Enterprise Drive is an excellent tool that can achieve real time synchronization of cloud and local files. Technical advantages such as multiple synchronization methods, permission configuration, multi person collaboration, and version management ensure high performance, stability, and security. virtual map disk Overview Virtual mapped disk: BabelBird Enterprise Drive introduces the virtual mapped disk function, which provides a way to seamlessly connect cloud files. You can access the mapped disk in Windows Explorer or Mac Finder just like accessing a local disk, thereby achieving an easy access to cloud files. Technical implementation: BabelBird Virtual Mapping Disk uses a technical solution similar to OneDrive and iCloud. It creates a virtual disk in the operating system and maps cloud files to the user's local computer, making these files visible in the user's file browser. Main features Local access to cloud files: The virtual mapped disk allows users to access files and folders in their Babel Enterprise network disk through tools such as local file explorer or Finder. No local storage occupation: Unlike traditional file synchronization methods, virtual mapped disks do not actually store cloud files on the user's local disk, so they do not occupy local storage space. Files are cached or downloaded only when needed. Online access: Virtual mapped disks require a network connection to access cloud files. The file icon is actually just a link to the cloud file, so you need to be online to view and operate these files, and the permissions are the same as those in the cloud. Transparent operation: Users can operate files in the virtual mapped disk just like local files, including opening, copying, pasting, deleting and other operations. Automatic synchronization: File changes will be automatically synchronized to the cloud, thereby maintaining the consistency of the cloud files and the files in the virtual mapped disk. Associated files: When you open a file with an associated file in the BabelBird mapping disk, the associated file will be automatically loaded, achieving the same effect as opening a file in a local folder. For example: opening a DWG (AutoCAD file) containing a large number of reference files, or an Excel chart associated with other files. Technical advantages (compared to WebDAV and SMB) Permission consistency: Unlike WebDAV or SMB mounting (which must use permission rules compatible with WebDAV or SMB), BabelBird mapping disks are implemented by directly calling the underlying file system of the operating system, which can achieve permission control consistent with BabelBird. (For example: you can only preview but not download or save as.) In WebDAV and SMB, only the view permission is actually read only. As long as the file is visible, the user can open and obtain the file in read only mode, losing control of the file. Higher performance: The Babel mapping disk directly corresponds to the Babel server related interfaces. There is no forwarding and intermediate processing links. You can directly obtain the file list provided by the server and open the folder virtually, so it can provide higher performance, and there will be no lag when opening the file list and checking files. Using WebDAV, you can only open a folder to temporarily load a list. If the number of folder files exceeds a certain number (related to device performance and network speed, usually more than 300), severe freezes and slow access will occur. WebDAV does not support very large folders using object storage systems. More secure: Babel mapping disk can determine the folders and files in the folders that everyone can view based on permissions. People with different permissions can see different contents when viewing the same folder. SMB and WebDAV currently cannot do this. At the same time, Babel's files are encrypted and stored in object storage in blocks. However, if the files are encrypted and stored in blocks, using WebDAV, you need to decrypt the files in order to obtain the file list. This means that products that support WebDAV either do not store data encrypted, or the performance of WebDAV is extremely poor and the number of files exceeds a certain range and is unavailable. Controllability: Unlike WebDAV and SMB that use third party software to mount, the Babel mapping disk is a self developed drive. It has controllability over the drive's operation, menu, running mode, and function implementation, and is responsible for product quality and user experience consistency. There will be more functional expansions in the future. Mainstream enterprise level solutions: Whether it is Microsoft's OneDrive, Google's Google Drive, Apple's iCloud, BOX's BOX Drive, or domestic mainstream Internet enterprise network disk manufacturers, they all use solutions similar to Babel's mapping disks, rather than simply accessing WebDAV (to access WebDAV, you only need to make protocols compatible and open for access, and it is simple to implement. Why do mainstream enterprise level manufacturers spend a lot of energy to develop their own mapping disks?). The main application scenarios of WebDAV are individuals or small teams that do not need to make complex permission judgments, store encryption, and open all files. The main usage scenario of SMB is also open file sharing (plain text storage) for individuals and small teams. Application scenarios Virtual mapped disks are suitable for users who need to frequently access cloud files but do not want to change their local disk usage habits or occupy local storage space. This function allows users to access cloud files just like local files, and access network disks in other applications just like opening local folders, without changing usage habits, and facilitates file management and use. File management BabelBird Enterprise Drive provides a powerful file management module for unified management and archiving of enterprise files. This module is designed to help businesses better organize and retain critical files while ensuring they are secure and accessible. Main features Archivist: Babel allows the super administrator to designate one or more company members as archivists. Archivists are responsible for managing archived documents and archives. Archive: Archived files are stored in the root directory of the archive. Archives are corporate libraries of materials used to retain and manage documents over the long term. Reading room: Archivists can create a reading room and move files from the root directory of the archive into the reading room. Only then can other company members borrow these documents. Borrowing permissions: The reading room can choose different borrowing methods, including public, borrowing required, open to departments only, borrowing within departments only, etc. When borrowing a file, you can set the permission level, such as reading only, copying, downloading, and specify the borrowing time. File archiving: Archived files cannot be changed, ensuring the integrity and credibility of the files. This is important for long term retention of legal and compliance documents. Archive search: The archive has an independent search function, and only files in the archive will be searched. Users can quickly find the archive files they need. File privacy: Non public files without borrowing permission will not display preview images to ensure file privacy. Technical architecture The Archives Management module uses the following key technologies and modules: Archive administrator permissions: Super administrators can designate company members as archive administrators, allowing them to manage archives and reading rooms. Reading Room Settings: Archivists can create reading rooms and configure different borrowing permissions and accessibility options. Archiving and retention: Once a document is archived, it needs to ensure that its contents cannot be changed. This requires technical measures to protect file integrity. Independent search: The archive has an independent search engine for searching files in the archive to ensure that users can quickly find the files they need. Advantages of file management The archive management module helps enterprises better manage the archiving and retention of documents. Through archives, reading rooms, and different borrowing permissions, enterprises can ensure that documents are retained long term, managed in an orderly manner, and can meet compliance and legal requirements. This module can also be used as a knowledge base to help enterprises save important information and knowledge. Logs and reports The log and report system of BabelBird Enterprise Drive provides comprehensive file usage management, monitoring, auditing and accountability functions. This module is designed to provide business managers and users with insights into file activity, access, and system usage to support compliance and security requirements. Main features File log: Each file and folder has an independent log, which records various operations in the life cycle of the file in detail, including creation, reading, modification, renaming, sharing, deletion, permission changes, etc. This even includes anonymous sharing operations and the IP address of the visitor. These logs can be exported as Excel reports for auditing and monitoring. File access statistics: The file details page provides statistics on the number of file comments, downloads, opens, number of visitors, and visitors. Folder list: You can export the list of files and sub files in the folder as an EXCEl file for auditing and management. Document Review Record Report: Document review operations are also recorded as reports to support auditing of document reviews. Department logs and reports: Department administrators can view the usage logs of the entire department, including detailed file access logs, statistics on the number of uploaded files, the number of sub departments created, or the number of projects. In addition, department administrators can count and manage files shared by the entire department and files with changed permissions. Enterprise level management: Enterprise administrators and security auditors can view the usage behavior of the entire enterprise, including logs and reports of various departments, and there are also two columns, access logs and statistical analysis, to uniformly view and manage the usage behavior of the entire enterprise. This helps maintain corporate compliance and security. Access log: The access log records the usage log of the entire enterprise network disk, including every operation of the user on the network disk. Administrators can conduct detailed queries and export reports. Statistical analysis: Provides statistical analysis chart tools, allowing administrators to view the usage activity of different departments, the number of files, the ranking of active files, statistics of new files, statistics of the number of uploaded files, and traffic usage statistics. Technical architecture Logging: The system needs to record detailed logs of each operation, including operation type, timestamp, executor, target file, IP address and other information. Report generation: Administrators are able to generate reports from log data, usually in Excel format, for auditing and monitoring. Data analysis tools: Statistical analysis tools are used to analyze and visualize data to help administrators better understand system usage. Log interface: Babel supports exporting log data through the interface to use third party log management and analysis tools. Advantages of logs and reports Logging and reporting systems help enterprises achieve the following goals: Compliance: Help enterprises comply with regulations and internal policies and ensure compliance of document operations. Security Auditing: Provides auditing capabilities that allow enterprises to inspect and monitor file access and operations to identify potential risks. Performance optimization: Through statistical analysis, it helps enterprises understand the performance bottlenecks of the system and take appropriate improvement measures. User behavior monitoring: allows business managers to understand employee behavior, including file access and operations, to ensure data security and confidentiality. Decision support: Help business managers make more informed decisions through data analysis, including resource allocation and document management. The log and report system is an important part of BabelBird Enterprise Drive, which provides comprehensive file usage management and monitoring functions to support the compliance and security needs of enterprises. Updates and notifications Dynamic column Overview: The dynamic column of BabelBird Enterprise Drive is an information flow used to display files and user dynamic information related to you. It provides a real time overview of your work and helps you track your colleagues' activities, including file changes, annotations, comments, etc. Real time information flow: The dynamic column presents the collaborative activities of you and your team in the form of real time information flow, helping you to understand what is happening in the team in a timely manner. Convenient interaction: Through the dynamic column, you can directly access files related to you, reply to comments, interact with colleagues, and complete collaboration tasks in a more convenient way. Dynamic search: You can search dynamic historical content and locate related dynamic items more accurately. Notification section Notification system: The notification system of BabelBird Enterprise Drive is used to send various reminders and notifications related to you. These notifications can be communicated to you in a variety of ways, including email notifications, mobile application notifications, desktop notifications, etc. Notification types: The notification system covers a variety of notification types, such as @mentions of you, file update notifications, approval requests, file authorization requests, etc. This helps you stay on top of your various workflows. Personalization Information type settings: Users can customize which updates and notification types they receive in the settings according to their own needs to ensure that the information is accurate and targeted. Application scenarios The dynamic column and notification column help users understand important developments and notifications at work, improve collaboration efficiency, and enable users to respond more quickly to colleagues' collaboration requests, reply to comments, and track file changes. The dynamic and notification columns of BabelBird Enterprise Drive are key collaboration tools. They provide a real time overview of collaboration and various notifications, allowing users to collaborate with their teams more effectively and maintain an understanding of the work process. These features help improve collaboration efficiency and ensure important information is not overlooked. discussion group Overview Discussion group function: BabelBird Enterprise Drive creates discussion groups for each department and project, which serve as a group chat space for internal members of the department or project. Discussion groups allow members to post text and images, conduct discussions, and share attachments. Member interaction: The discussion group provides a convenient platform for members to communicate, collaborate and discuss project related matters with each other, thereby enhancing teamwork and information sharing. Main functions Information publishing: Discussion group members can publish text messages and pictures to achieve real time discussion and communication. Attachment sharing: Members can easily share attachments such as documents, forms, and other files for sharing and discussion. Visibility: Information posted in the discussion group is visible to all members of the department or project to which it belongs, ensuring information sharing. Application scenarios Discussion groups are suitable for information exchange and discussion within departments and between project teams. They facilitate real time collaboration and help solve problems, share insights, and track progress. Summary Discussion groups provide a convenient collaboration platform for department and project members to share information, discuss matters, and work together. These discussion groups help enhance internal communication and increase the efficiency and productivity of your team. workbench Overview Workbench function: BabelBird's workbench is a personalized interface that allows users to display commonly used folders, work content, and various information on one interface in the form of cards. Each card directly presents content and can be manipulated. Users can freely adjust the position and sorting of cards as needed. Personalization: The workbench provides multiple alternative cards. Users can freely select the cards that need to be added to the workbench and customize them according to their own needs. This enables users to get information and functionality relevant to their work on one page. Main functions Card display: Each card represents a different type of information or work content, such as recently accessed files, uploaded files, followed files, shared files, annotated files, tag clouds, etc. Custom Charts: Users can customize charts or cards to add specific projects, folders, or other information to the workbench to meet their unique needs. Card sorting: Users can sort cards by dragging and dropping so that the most important or frequently used information is at the front. Application scenarios Workbench is suitable for situations where users need to centrally manage and access information and resources related to their work. Users can place frequently used files and projects on the workbench to improve work efficiency. Enterprise management backend (enterprise console) The BabelBird Enterprise Console centralizes the administrator's functions for managing the entire enterprise. Enterprise administrators can configure various options of the enterprise network disk in the enterprise console, turn on or off the required functional modules, set the organizational structure, customize roles and permissions, manage members, set watermarks, set department security policies, IP access policies, bind accounts and mac addresses, monitor network disk usage... Main columns Enterprise configuration: Comprehensive management of enterprise network disk configuration items, such as space allocation, whether personal files are allowed, allowed file upload size, historical version validity period or number of historical versions, various administrator assignments, changing logo and login background, prohibiting or enabling external sharing, and whether to accept email notifications. Various enterprise configuration options can be found in the enterprise configuration column. Organizational structure: Unified management and maintenance of the enterprise's organizational structure and departments. Ability to view departments and management departments in a tree view. View department members, allocate department space, create sub departments, set department security policies... Permission management: Create roles and change role permissions, and manage custom file permissions. Member management: You can search and filter the member accounts of the entire enterprise, add new members, import members in batches, assign member departments and roles, view and manage the information and usage of each member in detail, handover when members leave, add, delete, modify and check member accounts, allocate and limit member space and traffic. Tag management: unified management of tags used by enterprises, adding tags and classifying tags to facilitate users to select tags. File configuration: Add an optional process for file approval and manage the already added approval process. It also has a file blacklist function that can prevent specific types of files from being uploaded. Corporate notifications: Create corporate notifications, manage historical corporate notification lists, and send corporate notifications. Group management: Create and manage groups. When sharing files in the frontend, you can choose which group to share them with. Watermark settings: manage document watermark types, adjust watermark parameters, and set watermark display range. Access log: Manage and query all access records of the entire enterprise network disk. Log reports can be exported. IP policy list: The upload and download behavior of corporate files can be managed through IP policies. For example: downloading files is prohibited in a certain IP range, and you can download files by returning to a certain IP range. Mac address binding: You can bind the user account to the mac address of a specific device, so that the account can only be used on the device bound to the mac address. You can also create a mac address pool. Statistical analysis: Statistically analyze the usage of network disk. Including system activity, file number statistics, active files, number of new files within a period of time, number of uploads per month, and traffic usage. Workbench push: Set the default display card of the workbench. System configuration (private deployment version only): configure the mail server, bind third party SSO authentication, and set the third party authentication login method. Third party account synchronization (private deployment version only): Set the third party account synchronization time and query the third party account synchronization record. Optional modules (private deployment version only): Select the functional modules that the enterprise needs to display and turn off some functional modules. Monitoring and warning: Set warnings for abnormal behavior, and notify administrators when abnormal behavior occurs (for example: users delete files in large numbers) Transfer file configuration: The configuration of the data ferry system allows data ferrying between multiple sets of BabelBirds. Configure the receiving port and sending port of data. API The Babel API module is responsible for Babel's open API. Private cloud users can apply for and open a developer account for free on the enterprise console, obtain the developer ID, key and token, and set the callback URL. Callback URL setting rules: http://customer domain name /public/babelAuthResult.do For example: http://testqiyeban.babel.cc/public/babelAuthResult.do Setting path: Enterprise Console Enterprise Configuration Developer Account Visit the following link to get the latest API documentation: https://www.babel.cc/p/api integration.do Third Party Login (SSO) Babel supports the integration of third party login (SSO) platforms to achieve single sign on and unified login. And Babel supports the integration of multiple third party login platforms. For example: You can scan the QR code to log in via corporate WeChat, log in with your OA account and password, or scan the QR code to log in to DingTalk. SSO integration is divided into two modules. Third party authorized login and third party organizational structure synchronization. Among them, third party authorized login allows multiple sources to authorize login. However, in order to prevent user account conflicts, third party organizational structure synchronization only allows synchronization of one source. For example: the organizational structure of the OA system is synchronized, but SSO login of OA and Enterprise WeChat is supported (the organizational structures of OA and Enterprise WeChat need to use the same userID) For more information about third party login of BabelBird, please refer to the User Authentication and Authorization (SSO) chapter Data ferry Babel Data Ferry supports Babel birds deployed in secret areas and Babel birds deployed in non confidential areas to transfer data to each other in a secure and approved manner. To achieve data exchange between confidential and non confidential areas under corporate supervision. For detailed information about BabelBird Data Ferry, please refer to the BabelBird Data Ferry chapter. Zhichao AI Zhichao AI is the AI platform of BabelBird Enterprise Drive, including three main modules: Zhichao AI customer service, Zhichao AI knowledge base, and Zhichao AI document assistant. These modules combine large model APIs and custom training to meet the enterprise's intelligent customer service, file content analysis and question answering needs. The three main modules of Zhichao AI Zhichao AI customer service: This module serves as the AI customer service of the enterprise. BabelBird Enterprise Drive itself also uses this module to answer the problems encountered by users when using BabelBird Enterprise Drive. We also open this service to corporate customers. Companies can provide product manuals, FAQs, customer service documents and other materials to Zhichao AI for learning and fine tuning to meet corporate customer service needs. Enterprises can also embed Zhichao AI's code blocks into their websites to quickly establish an external intelligent customer service system. Zhichao AI customer service can significantly reduce customer service costs and save time and resources. Zhichao AI Document Assistant: This module is used to answer questions about a single document. By analyzing the document content, Zhichao AI can answer various questions about the document content, from summarizing to revealing key findings. Users can ask questions to the AI ​​instead of having to read lengthy documents themselves, improving work efficiency. Zhichao AI knowledge base: This module allows companies to customize their own AI assistants. The Zhichao AI team will help prepare training sets and adjust parameters based on the company's data, thereby establishing an exclusive AI model that can provide answers within the scope of permissions for people with different permissions on BabelBird. It can be used as a corporate knowledge base assistant in the form of questions and answers. Technical Solutions Answer questions intelligently: Zhichao AI uses large models and custom training to ensure accuracy. It also uses small models to assist the work of large models, reducing problems such as talking nonsense, pretending not to understand, or leaking secrets. In addition, Zhichao AI follows BabelBird’s authority management mechanism to ensure that users can only obtain answers within their authority. Automatic learning: Zhichao AI can accumulate knowledge by studying the files provided by users and provide users with more accurate answers. All documents participating in training are specified and agreed to by the user to ensure data privacy and compliance. Advantages Reduced customer service costs: Zhichao AI customer service can significantly reduce the customer service costs of enterprises. There is no need to train personnel on a large scale, and AI can provide answers at any time. Quick question answering: Zhichao AI can answer users' questions instantly, improving work efficiency. Document content analysis: Zhichao AI Document Assistant can quickly analyze document content to help users quickly obtain information without reading the entire document. Customized AI assistant: Enterprises can customize exclusive AI assistants for Zhichao AI knowledge base according to their own needs to meet specific knowledge management and question answering needs. Permission management: Zhichao AI can provide answers within different ranges based on user permissions to ensure data security and compliance. Automate tasks Facing the growing number of digital assets, the traditional manual file management model can no longer meet the demand for efficient circulation. The \"automated task\" engine launched by BabelBird aims to hand over tedious and repetitive file processing actions to the system background for automatic execution. By establishing a \"self organizing and self standardizing\" intelligent circulation system, the cost of manual intervention is significantly reduced, allowing the team to focus on core business creation. Automated tasks are included in the standard version and users do not need to purchase it separately. Core operating mechanism: Flexible permission driven: Relying on the platform's extremely fine grained permission management system, users with corresponding permissions on the target network disk or folder can independently configure, turn on or off specific automation tasks as needed. Multi task flow concatenation (Workflow): Automated tasks do not run in isolation and support the free combination of multiple rules to form a workflow. For example: after a file is uploaded, the system can first trigger \"automatic rename\" to standardize the file name, and then immediately trigger \"automatic sorting\" to archive it to the relevant directory, achieving multiple steps in one go. Continuously expanding capability matrix: The automation engine is highly scalable. In addition to the existing basic functions, the platform will continue to access more automated processing nodes to meet increasingly complex business scenarios. Currently supported core tasks (including but not limited to): Automatic renaming: Unify and standardize naming according to preset rules (such as keyword replacement, case conversion). Automatic organization and cleaning: Automatically classify archived files based on trigger conditions, or clean up space regularly based on policies. Automatic PDF conversion and signature: Automatically generate a PDF copy of the source file, or stamp the company signature in the cloud. Create folders in batches: Generate a standard business directory tree with one click by importing data templates (such as Excel). Multi task collaboration and execution flow weight In complex business scenarios, multiple automated tasks are often configured in one folder. In order to ensure the logical rigor and security of data processing, a strict automated processing sequence is preset at the bottom of the system. The specific execution weight (the higher the value, the priority for execution) is as follows: Automatically clean folders (weight 10): highest system priority. If there are qualified cleaning tasks, they will be executed first to avoid investing subsequent computing power in invalid data that will be discarded. Automatic decompression (weight 9): Prioritize the release of packaged assets for subsequent circulation. Automatic renaming (weight 8): Priority is given to completing the standardization and unification of naming before files enter classification and archiving. Automatic format conversion category (weight 7): Prioritize conversion tasks such as transferring PDF, pictures or audio and video formats. Automatic sorting/sorting (weight 6): Executed as the end node of the flow. This means that core pre standardization operations such as cleaning, renaming and format conversion have been completed before files are moved and classified. Automatically clean files (Auto Clean) Function Overview In daily cross department collaboration or project cycle management, a large amount of temporary data, process files or short term circulation materials are often inevitably generated in the enterprise network disk. The \"Automatically Clean Files\" function is designed to provide enterprises with automated storage space optimization and directory slimming solutions. Through this function, the system can automatically delete redundant files in specified folders according to specific rules set by the user, keeping the project directory clean for a long time and releasing high value storage resources. Core operation and configuration rules This module uses a strict logical rule engine to perform file cleaning actions to ensure the accuracy and efficiency of data processing: Target directory locking: The task configuration needs to explicitly specify the target folder to which the rule applies. Users can choose to apply the rules only to newly entered files in the folder, or to apply the rules to historical files that already exist in the directory at the same time. Multi dimensional rule triggering: Supports precise filtering and elimination of files based on specific rules. Common determination rules can cover file types (such as temporary files with specific suffixes), life cycles (such as files entering a directory for more than a specified number of days), and other dimensions to achieve highly customized cleaning strategies. Workflow collaboration: As the end link of complete automated circulation, automatic cleaning can be seamlessly connected with other tasks. For example, after the \"automatic conversion to PDF\" task is completed, the system can immediately trigger the \"automatic cleaning\" rule to uniformly clean the original draft files, leaving only the standardized final version. Permissions and data security control Since the cleaning task involves the sensitive operation of file deletion, this function relies heavily on Babel's extremely fine grained permission management system: Configuration permissions: Only collaboration members with corresponding advanced permissions (such as management and deletion permissions) for the folder can create or modify automatic cleanup tasks to prevent data loss caused by unauthorized operations from the source. Senseless and safe execution: Cleaning tasks are performed silently in the background to reduce interference with user front end operations. At the same time, the company's established data compliance and recycle bin retention policies are strictly followed to ensure the absolute security of data assets. Typical business application scenarios Design and R&D projects: In architectural design or scientific research management, working software often automatically generates a large number of backup or cache files (such as .bak or temporary rendering files). By configuring automatic cleaning tasks, you can set up automatic identification and deletion of useless files with specific suffixes on a regular basis to keep core drawings and literature catalogs pure. Public data exchange area: For the \"temporary transfer station\" or \"temporary sharing area\" set up within the enterprise, automatic cleaning tasks based on the time dimension (such as \"automatic cleaning after 7 days of retention\") can be configured to achieve self organization and self purification of public spaces and reduce operation and maintenance management costs. Auto Rename Function Overview In business scenarios involving multi party collaboration and multi frequency data collection, due to differences in operator habits, file naming often lacks unified standards, which brings great trouble to subsequent retrieval, archiving and auditing. The \"Auto Rename\" function allows the system to automatically rename files uploaded to a specified folder according to highly customized preset rules. This mechanism effectively eliminates naming confusion caused by human factors and ensures that enterprise data assets meet the standards as soon as they are stored in the database. Scope of application and permission control Permission driven: The enabling of this function strictly relies on the user's operation permissions. As long as the user has \"upload\" and \"rename\" permissions on the target folder (covering various folders such as personal, department, project or material library), the automatic renaming task can be configured for it. Traceability processing: The rules not only apply to newly uploaded files, users can also choose to apply traceability to historical files that already exist in the target directory and all its subfolders. To ensure system performance and execution stability, the upper limit for batch source traceability renaming is 5,000 files at a time. Core rule engine and configuration dimensions Babel provides a highly flexible visual rule splicing engine. Users can add multiple naming rules and sort the rules freely by dragging and dropping. The configuration interface provides real time changing \"sample file names\" throughout the entire process to help users visually preview the overlay results of renaming rules. The rules engine supports the following multi dimensional named elements: Standard attribute variables: Supports extraction and insertion of system level variables, including file uploader, file person in charge, parent folder name, and upload time. Multimedia metadata (Metadata): For files in specific formats such as images, the system can deeply analyze and extract their underlying metadata as the basis for naming, such as shooting date, camera manufacturer/model, lens model, size, and DPI/DPCM and other parameters. Custom text and continuous numbering: Users can freely insert custom text content. In terms of numbering mechanism, unlike traditional single batch renaming, automatic renaming has state memory (continuity). The system will automatically read the last number in the target list that meets the rules to ensure that files uploaded across batches and time periods can achieve seamless continuation of serial numbers. Users can accurately set the starting value, incremental value and specific digits of the number. Refined pruning and anti conflict mechanism of original names In addition to adding new prefixes/suffixes, the system also supports deep structural cleaning of the original names of files: Name pruning and replacement: You can perform \"replace specific content\" and \"delete specified content\" operations on the original file name. In addition, it also provides a one click \"Delete Characters\" function to accurately remove redundant spaces, numbers, quotation marks, dashes and underlines in file names. Mandatory anti collision protection: If the user chooses to completely delete the \"original file name\" in the rule (that is, the original name is not retained when uploading), in order to avoid the risk of files with the same name overwriting each other, the system will force and automatically add a \"numbering\" rule to the rule chain. Date logical mutual exclusion: When calling date class variables, the user can check \"Replace the date detected in the file name\". To prevent logical conflicts, in a single rename task, the replacement instruction is only allowed to be checked once by a certain time variable (such as \"upload time\" or \"shooting time\"). Global formatted output control After completing the splicing of rule variables, the system supports unified formatting specifications on the output end: Case standardization: Supports one click conversion of assembled file names into uppercase, lowercase, all uppercase or all lowercase to meet the visual specifications of different companies. Uniform word separation: Supports the uniform insertion of standardized separators (such as spaces, underscores or dashes) between each naming rule module to further improve the machine readable and human readable experience of file names. Auto to PDF Function Overview In business links such as cross enterprise collaboration, external data distribution, and project finalization and archiving, the PDF format has become a standard document exchange medium due to its consistency in cross device display and anti tampering properties. BabelBird's \"Auto to PDF\" function aims to establish an automated file format standardization channel. After configuring this task, when a file is added to the selected target directory, the system will silently trigger the conversion engine in the background to automatically convert it into a standard PDF file. This capability greatly eliminates the inefficient labor of manually exporting PDFs one by one, ensuring the standardization of data external output and internal archiving. Execution logic and boundary conditions In order to ensure the efficient operation of the underlying computing resources of the platform and the safe and controllable flow of enterprise data, the following execution logic and boundary restrictions are set for the automatic conversion task: Scope and traceability processing: This task can be overridden downwards and supports checking to apply to files in the target directory and all subfolders. In addition, the rules also support traceability to historical data and can be applied to existing files in the directory. However, to ensure execution stability, the number of files processed in a single traceability process is strictly limited to 5,000. System performance protection mechanism: In order to prevent extremely large source files from occupying computing power for a long time during the conversion process and causing the task queue to be blocked, the system has a built in file size threshold, that is, large files exceeding 30MB will not trigger the automatic conversion mechanism. Automatic release of storage space: For the specific business scenario of \"only keeping the final PDF\", users can check the \"Delete original file after successful conversion\" option in the task configuration interface. After turning on this policy, the system will automatically clean up the original files after confirming that the PDF copy is generated correctly, thereby greatly optimizing the utilization of network disk storage space. Extensive format compatibility matrix Babel's automatic conversion engine has powerful multi format parsing capabilities and supports automatic dumping of mainstream business documents in 32 different industries into PDF. Users can choose to perform conversion on \"all supported files\", or use the drop down menu to accurately select the extensions they need to convert by category. The specific supported format matrix is as follows: Document typesetting: fully compatible with source files generated by mainstream office and publishing software, including doc, docx, ppt, pptx, wps, epub, dpt, indd, rtf, docm and pptm. Pictures and images: Supports rendering and conversion of mainstream bitmaps, digital negatives and medical image formats, covering jpg, bmp, jpeg, jpg2, png, psd, tif, tiff, raw, cr2, dcm and heic. Graphics and engineering drawings: Deeply adapted to vector and CAD drawing conversion in the fields of design and construction engineering. Supported formats include ai, svg, eps, dwg, dwt and dxf. Auto Organize Function Overview With the accumulation of collaborative data in the platform, how to keep the underlying \"any folder synchronization\" architecture and permission control directory clean has become the key to enterprise digital asset management. The \"Automatically organize files\" function allows the system to automatically classify and route files to the corresponding target directory according to preset time periods or content characteristics. This function ensures that massive documents are highly structured during the circulation process and avoids the lag and errors of manual archiving. Flexible triggering mechanism and scope Users can enter the configuration through the \"Task\" option in the right click menu of the folder or the automated task list panel on the left. The configuration covers the following triggering and action rules: Event driven (default): When a file is uploaded or moved to a specified trigger folder, the system responds immediately and starts organizing actions. Period driven: Suitable for centralized data archiving scenarios. The system can uniformly perform file sorting according to a fixed period (for example, set to 23:00 every day). Historical traceability: Rules can be applied to new files and all subfolders, or you can check \"Apply to existing files\" to batch trace the historical inventory data. To ensure the stability of the system, traceability processing shall not exceed 5,000 files at a time. Core intelligent sorting rule engine The system provides three highly customized classification rules to meet data archiving needs in different dimensions: 1. Structured archiving based on time dimension (classified by month/year) The system can automatically create corresponding subfolders (such as \"2025\", \"2025 10\") according to the corresponding year or month when files are added to the network disk and move related files into . The same as when classifying by year or month, the system has the intelligence to create files on demand. If no files are generated within a specific period (such as a certain month), the system will not redundantly create empty folders for that month. 2. Content based intelligent routing (categorized by keywords) Based on specific keywords contained in the file name, the system automatically distributes and moves files to preset destination folders. Format recognition: File extensions (such as \"jpg\") can also be configured as keywords to achieve targeted aggregation of specific types of materials. Multi line parallel routing: Users can continuously add multiple routing rules through the \"Add Keyword Classification\" button. It not only supports distributing files containing different keywords to different directories, but also supports pointing multiple keyword tasks to the same target folder. Anti duplication and priority control: Keyword matching is strictly processed in the order set by the task. For example, when the file name is \"123ABC final draft.jpg\", if the first rule in the keyword list is \"123\" and the second rule is \"final draft\", then the file will give priority to matching the rule of \"123\" and execute the move. The system has built in anti repetition detection. Each keyword is only allowed to be entered once. Repeated entry will trigger the \"Please re enter\" error interception. Same name conflict resolution: During the process of moving and organizing files, if a file with the same name is encountered in the target folder, the system will automatically append a number to the file name to ensure that the data is not accidentally overwritten. Create signature (E Sign) Business scenarios and function overview In key links such as contract approval, drawing countersigning, and business compliance transfer, digital signatures with anti tampering properties are the core node for opening up the closed loop of online collaboration. Traditional cross system signing is often accompanied by cumbersome file downloads and format conversions. The \"Create Signature\" function launched by BabelBird allows users to stamp and sign documents directly in the cloud disk workflow. The engine supports multiple mainstream file types to directly load printed signatures, and supports one click export of signed files to standard PDF format, ensuring the security, compliance and non tamperability of digital assets from the source. Signature asset library and personalized configuration The system provides users with a highly integrated digital signature management console to ensure the unified precipitation and rapid recall of electronic signature assets: Multi signature collection: In the \"Signature Settings\" module, users can call the terminal to \"add a handwritten signature\" online, or directly \"upload signature image files\" (such as PNG materials with transparent channels) to meet different levels of signing compliance requirements. Corporate seal management: In the \"Stamp Settings\" module, corporate users can upload business specific electronic official seals or compliance seal images as needed. Default priority status: For users who have multiple signature assets, the system supports one click \"setting a specific signature or stamp as currently used\" (default signature). In the subsequent document preview and circulation interface, the system will give priority to calling this default signature, which greatly improves the signing efficiency in high frequency approval scenarios. Intelligent adaptive interaction and immersive guidance system In order to take into account the display limits of different hardware terminals and lower the user's learning threshold, the signature configuration center adopts a multi breakpoint intelligent responsive interface architecture and deeply embeds multi language operation guides: Widescreen workstation mode (window width ≥ 1120px): When the user operates on a desktop widescreen device, the system not only retains the standard signature configuration panel on the left, but also automatically expands an independent video teaching area on the right. This area will automatically load and play the tutorial on how to use the signature in a loop without any sense (it will replay after a 3 second pause), providing users with an immersive experience of \"learning and matching at the same time.\" Compact focus mode (window width < 1100px): When on a narrow screen or mobile window, the system will intelligently collapse the video playback area on the right to maximize the visual focus of the core signature setting area. At the same time, the system provides a \"How to use signature?\" entry at the bottom of the interface, and users can click to trigger a full screen tutorial playback. International bilingual support: Considering the collaboration needs of multinational enterprises, the system has a built in localized teaching video library. In addition to the exclusive Chinese tutorials played in the Chinese language environment, all other multi language versions match and play standard English tutorials by default to ensure barrier free implementation for global business teams. Batch Create Folders Function Overview and Business Value In business scenarios involving multi project concurrency or enterprise department structure adjustment, manually establishing complex standard directory trees one by one not only consumes a lot of operation time, but also easily leads to directory hierarchy confusion or non standard naming due to human oversight. The \"Batch Creation Folder\" function provided by Babel allows users to directly drive the generation of cloud directories through external structured data (such as Excel, CSV, TXT text). This function can instantly transform a standardized business directory template into a network disk folder array that can be implemented, greatly improving the efficiency of initial file creation during the startup phase of large scale projects. Large scale generation of standard directory arrays This module has powerful data analysis capabilities and manual fault tolerant intervention mechanism: High concurrency support: The system supports importing files in xls, xlsx, csv or txt format and quickly reading directory lists according to newline character rules. The upper limit of a single batch processing task is up to 5,000 lines, which meets the generation needs of most enterprise level data structures. Visual pre review and dynamic intervention: Before the batch creation is officially executed, the system will complete the data analysis and visually render the folder list and hierarchical relationship to be generated in the interface. In this preview session, users can directly perform instant modification actions such as \"create subfolder\", \"rename\" or \"delete\" on a specific preset directory through the right mouse button or floating menu. This \"review before building\" mechanism ensures that the final directory tree is absolutely aligned with business needs. \"One click deployment\" of project level folders and permissions When the target path is set to the root directory of the department folder or personal folder, the system supports the creation of a more advanced \"Project Folder\" . This model is deeply integrated with the underlying permission management system of BabelBird to realize the synchronization of directory construction and member permission configuration: Exclusive standard template: To batch generate project folders, you need to download and use the system's exclusive template to import data. If the uploaded non standard file does not meet the parsing format, the system will strictly intercept it and prompt you to re upload it. Project role and permission preset: The template not only standardizes the \"project folder name\", but also supports the direct association of the account system to preset \"project leader\" and \"project member\". Assignment of person in charge: The filled in person in charge ID (supports mobile phone number, email address or specific work ID format) must be a registered company member; if this field is left blank or the filled in identity cannot be verified, the system will follow the security principle and set the operator of the currently created task as the project leader by default. Automatic member invitation and empowerment: Users can batch enter multiple project members in the template by separating them with commas. After the project directory is generated, the system will automatically send invitation notifications to these members and grant them basic \"upload and download\" default permissions, completely eliminating the cumbersome one by one authorization operations after file creation. Real time status monitoring and intelligent fault tolerance mechanism When executing large scale creation tasks, the system background will process it robustly in the form of a queue, and provide a full range of process monitoring and exception repair closed loops on the front end: Global progress tracking: During the creation process, the list node will update its execution status in real time (smooth transition from the circle animation representing ongoing execution to the confirmation check state representing success). The global status of the task will also clearly flow from \"Creating\" to \"Complete\". Accurate exception attribution and retry: After all tasks are executed, a clear summary of the results will be output at the top of the system (such as \"A total of XXX folders were created, and X failed\"). Users can check the \"Failed to Create File List\" with one click. The system will accurately classify the failure reasons as system level conflicts such as \"the file name contains characters that are not allowed\" or \"a folder with the same name already exists\". For these abnormal entries, users can not only find out the cause, but also click the green \"Retry\" button directly on the interface to trigger secondary creation, which greatly reduces the resistance to batch operation and maintenance. Document control project The document control project is an industry application independent module of BabelBird (needs to be purchased separately). The BabelBird document control project solves the problem of process management (DCC) and automation of document control standards in the engineering design industry. It improves the work efficiency of a large number of document control personnel and also reduces the possibility of human errors. Scope of use Industries or businesses that need to strictly manage every document sent. Every document sent to a customer is sent by a specific person (document control personnel). Every time a document is sent, there is a sending document that can be checked, and the sending content can be clearly managed. Through the sending order number, you can check the specific information and files of each file sent to the recipient. At the same time, you can query whether the recipient has received the message and whether the sent content has been rejected. And the delivery order can be used as a voucher. Problems that need to be solved At present, the document control process of many enterprises is basically manual, and the files are stored in the EDMS system or locally on the computer of the document control personnel. Rely on folder classification to manage documents. Each time a file is sent, a folder is manually created and the folder is named according to the file name specification. After the file is sent by email, the sent file is placed in the folder and the TRANSMITTAL (file sending order) of this sending is attached. Each send will generate a folder and corresponding TRANSMITTAL. The manual operation of these tasks is quite cumbersome. In addition to sorting out files, you also need to manually fill in the document delivery form each time, manually write the delivery order number according to the rules, and manually check it in the future, which is extremely inefficient. BabelBird Solution New document control project types can be created. This means that different projects can set different TRANSMITTAL (sending order) rules to generate different sending orders and sending order numbers. Different projects can also manage different recipients (recipient companies) You can set the file recipient for each project and manage the file recipients in a unified manner. Documents in document control projects support the sending function, and the sending function supports multiple selections. After selecting a file or folder to send, the recipient can receive the download link and TRANSMITTAL of the sent file via email. And the file downloaded through the download link is the version when sent. Each file sent is the current version of the file. File upgrade will form a new version number, which will be displayed on the delivery note. After the file is sent, the TRANSMITTAL and TRANSMITTAL NO. will be automatically generated according to the preset rules. You can manage and query the TRANSMITTAL (delivery order), and export the delivery order to PDF. Instructions for use of the BabelBird Cultural Control Project: Basic introduction The BabelBird document control management system is based on the BabelBird enterprise private cloud version and adds a document control management module to realize the automation of document control work. The way of document control management is to establish a \"document control project\". Document control projects are special projects customized for document control needs and are managed on a project by project basis. Establish document control projects After logging in to the system, click \"New\" \"New Project\" in the department where you want to create a document control project Projects can only be created in the root directory (enterprise files) or department root directory Example: Establish a document control project under the document control department of HQSM Click New Project, and the project type selection interface will appear. Select \"Create Document Control Management Project\" At this time, the project initialization selection interface appears. Fill in the initialization information according to the requirements of the project Each item is introduced as follows: Project leader Manage, transfer projects, modify project permissions and basic information. Cannot be empty. TRANSMITTAL can be deleted Project Secretary The project cannot be transferred, other people in charge of the same project can have multiple people, and can be empty. TRANSMITTAL can be deleted Document control staff Can send files to recipients. Other permissions are configurable, can be for multiple people, and can be empty. After selecting a person, click the permission selection drop down box on the right to modify member permissions in batches (as shown in the figure). other members There is no option to send files. Others are the same as ordinary members of ordinary projects. The permissions are configurable and can be empty. Version number rules As shown in the figure, if the prefix is HQSM, the first version of the file is HQSM A, the second version is HQSM B and so on. Basic information The filled in basic information will be displayed in the TRANSMITTA header. As shown in the picture: The red circle is the basic information to be filled in. Recipient information The recipient information determines the options when sending and the TRANSMITTA number of the sent file. The recipient's name refers to the recipient's name in the system. Generally, the recipient's company abbreviation is filled in, such as MCC. You can add multiple mailboxes. After adding multiple mailboxes, you can send files and TRANSMITTA to multiple mailbox addresses in one send. ATTN can be entered at will and will also be displayed on TRANSMITTA The waybill number rule is actually the automatic generation rule of the TRANSMITTA number. Different recipients can generate different waybill numbers. Therefore, different waybill number rules need to be set at each recipient. The rules customization interface is as follows: The 3 columns are the three components of the TRANSMITTAL number. If the required TRANSMITTA number requires more codes to form, you can also click the + sign to add more columns. Example: Select to enter text in the first column, a text input box will pop up, enter \"HQSM \" Select the encoding rule in the second column as 1 2 3 numerical sequence Select text input in the third column and enter \" 2020\" Click the plus sign to add a column and select the alphabetical order of a b c The TRANSMITTAL number generated when sending for the first time is: HQSM 1 2020a The TRANSMITTAL number generated for the second transmission is: HQSM 2 2020b After selecting letters as numbers for more than 26 numbers, the next version of the z number automatically becomes a1 If the project has multiple recipients, you can also click to add them. (After the project is established, you can also add or delete recipients in the project management interface. After completing these fillings, click \"Add Project\" to complete the new project. You can see the newly created document control project in the file list of the created project path, click to enter Document control management projects are different from ordinary projects. A button for document control management is added to the top bar of the project homepage. Among them, the \"Sending Order List\" can query all TRANSMITTA issued by the project, and the management project can manage the project. Upload files Click on the newly created document control project to enter the project page. Just drag and drop the files you want to upload into the project to upload the files. Of course, you can also use the synchronization function to upload and download just like using ordinary folders. Send files Select the file to be sent (multiple selections are supported), then right click and select \"Send File\" to display the file sending interface. The maximum number of files sent at a time is 2,000 (including folders). If the project requires all files to be sent, it is recommended to send them in a compressed package. The recipient can drop down to select the recipient and ATTN filled in during project initialization. You can fill in any other email address for CC, or you can leave it blank. The selected submission file type will also be displayed in the generated TRANSMITTA The file list lists the files to be sent this time. The file name that the system wants to send TRANSMITTAL consists of file number + description. For example, if a file is named 1000+drawing.pdf, the file number displayed in TRANSMITTAL when sending is \"1000\" and the description is \"drawing\". If there is no + division in the file name of the sent file, the file number will display the file name. If the file name sent is \"+drawing.jpg\", the file number will not be displayed, and the description will be displayed as \"drawing\". Description can be changed midway. The postscript will be displayed in the email received by the recipient and will not be displayed in TRANSMITTAL. After filling in, click \"Send File\" and the system will automatically generate TRANSMITTAL and attach it as a link in the email and send it to the customer. Generate TRANSMITTAL After successful sending, the system will pop up a prompt Click View to view the TRANSMITTAL automatically generated for this send Click Export to PDF to save the TRANSMITTAL as a PDF file You can also view all TRANSMITTAL sent in the project in the TRANSMITTAL list The TRANSMITTAL received by the recipient in the mailbox is consistent with the TRANSMITTAL. View TRANSMITTAL Click on TRANSMITTAL list on the project homepage Open the list to see and query all dispatch orders for this project. Click on the delivery number to view details and download the PDF file of TRANSMITTAL Acceptance means that the recipient has not opened the sent email. If the other party opens the email and accesses TRANSMITTAL, the receiving status will change to received. View sending records Right click on any file to view the sending record of the file and its corresponding TRANSMITTAL User interface user interface design Babel bird interface design concept There are many functions integrated into the enterprise network disk. How to reasonably allocate function entrances to make it more convenient for users to actually use it? This is an issue that needs to be considered during interface design and interaction. Currently, there are two conflicting design concepts. Interface design concept Advantages and disadvantages Hide very commonly used functions to ensure a simple interface, reduce learning difficulty, make it easy to use, and provide a friendly first time user experience. (Representative: 2C products such as Weiyun and Tencent Documents) The learning curve is gentle at first and steep at the end. Users have a good experience during the first trial, but it is inconvenient for long term use The function entrance is explicit and the interface is complex, but the required functions can be found quickly. The interface is heavy, the learning cost is slightly high, and the first time user experience is not friendly. (Represents: office, CAD and other professional software) The learning curve is steep at the beginning and slow at the end. The user experience is complicated for the first time, but it is actually convenient for long term use. Not good for marketing. Considering that enterprise network disk is a professional product for long term use by enterprises, although the steep learning curve in the early stage is not conducive to marketing (the abandonment rate increases when users simply try it out), it is friendly to users who choose BabelBird for long term use. After getting familiar with it, it can be used better and more organized. As a productivity tool, the convenience of daily use and reducing the probability of errors are more important. Therefore, BabelBird Enterprise Drive chose the second design concept: As a professional product for enterprise scenarios, the complexity of getting started can be appropriately increased for the convenience of long term daily use. Interface design principles User friendliness: On the premise of ensuring that the use of functions is given priority, user friendliness is emphasized to ensure that users can easily use the enterprise network disk. Consistency: Maintain a consistent interface design to provide a consistent user experience. Simplicity: Use a simple design to reduce redundancy and complexity so that users can quickly understand the interface. Availability: Ensure that the functional modules are easy for users to find and have corresponding guidance, and can be used directly within 3 steps. user interface elements Web version (web) It adopts the layout of left menu, right file list, and top functional partition. It is convenient for users to focus on the file list. The left menu can be collapsed to display more file list content, providing an immersive experience. In order to better manage files in a tree view, you can also open a tree view to manage files like Windows Explorer. If there are a large number of image files in the folder, the waterfall preview mode can be automatically turned on to facilitate user viewing. The left menu (shortcut) can be customized by users, making it easier for users to customize shortcut entries according to their daily usage habits. All functional operations of files/folders are concentrated on the right click and are easy to find. Commonly used functions are displayed on the file list. At the same time, there are corresponding buttons in the file list bar to prevent user operations from being affected by the failure of the right mouse button. Client (windows, mac, Kirin) The client uses Electron and C++ for cross platform development, which ensures style consistency and operation consistency. And there are also optimizations for each platform. The client also includes synchronization module, upload and download list and virtual mapping disk (cloud bridge) module. The main operation interface continues the style and layout of the web version, but the layout has been improved based on the usage habits of local software and the unique modules of the client. The top functional partitions are concentrated in the left column to make the top display more concise. The left column adds two client specific function buttons and entrances: transmission and synchronization. The file transfer module manages the synchronization process and upload and download tasks. Shortcuts for synchronizing, uploading, and sending files are integrated on the right click menu of Windows and MacOS system files, allowing users to quickly create synchronized and uploaded files (folders). A virtual mapped disk is integrated on Windows and MacOS, allowing users to access cloud files just like a local hard drive. Responsive design Responsive design principles Multi device compatibility: The user interface of BabelBird Enterprise Drive is designed to obtain the best experience on various devices, including desktops, mobile devices and tablets, to ensure that users can have a good experience on various devices anytime, anywhere. Picture: BabelBird has been cross platform since its birth. Adaptive layout User interface elements automatically adjust to screen size and orientation to ensure content visibility and usability. Touch friendliness: Optimize touch interactions on mobile devices, including gesture controls, swiping, and zooming. Image and media optimization: Preloading, image transcoding to generate thumbnails, and media compression techniques are used to reduce page load times and bandwidth usage. Mobile support Web version mobile device optimization Mobile interface design: The BabelBird web version has an H5 page designed for mobile devices, as well as a mobile version of the promotional website and mobile version download interface for sharing links, and supports common touch gestures such as sliding, zooming and clicking. Figure: Mobile device accessing Babel H5 page Mobile APP: In order to obtain a better user experience, BabelBird has developed a mobile specific APP that supports Android and iOS systems. In order to ensure good performance, BabelBird APP is developed as a native application. The interaction, interface, and functional modules of the APP have all been redesigned to be suitable for access on mobile devices. Figure: Mobile interface Tablet optimization The Babel iOS APP has a redesigned interface for the iPad to make it more suitable for working on a large screen. Performance optimization Load balancing strategy Separation of authentication and services Separate authentication: In order to improve the performance and security of the system, BabelBird Enterprise Drive adopts the strategy of separating authentication and core services. This means that the user's authentication request will be routed to a dedicated authentication server, and core service requests such as uploading, downloading, and query browsing will be routed to the corresponding core service server. Request routing: We use a load balancer to route requests to different servers based on the request type. This ensures that the authentication server does not become a performance bottleneck for core services and allows us to scale authentication and core services independently as needed. Multiple server deployments for the same type of requests Multi server support: BabelBird Enterprise Drive allows the same type of requests to be deployed on multiple servers to improve performance and availability. This multi server support strategy ensures that even if one server fails, the other servers can still handle requests. Requests are evenly distributed: We use a load balancing algorithm to evenly distribute the same type of requests across multiple servers to avoid server overload and provide faster response times. load balancer Load balancer configuration: We use professional load balancers to distribute and route requests. The load balancer sends requests to the appropriate server based on predetermined rules. Monitoring and automatic failover: The load balancer is equipped with monitoring features that can detect the health status of the server. If a server fails, the load balancer automatically routes requests to other available servers to ensure system continuity. Advantages Performance improvements: Load balancing strategies improve system performance, allowing requests to be processed in parallel on multiple servers, reducing the load on a single server. High availability: The deployment of multiple servers and automatic failover ensure the high availability of the system, and services can still be provided even in the event of a failure. Scalability: Load balancing strategies allow more servers to be added as needed to accommodate growing users and requests. Cache management File buffer management File buffer settings: In order to optimize performance and reduce the burden on CPU resources, BabelBird Enterprise Drive implements file buffer management. The decrypted files will be temporarily stored in the buffer to reduce repeated decryption operations. LRU strategy: We adopt the least recently used (LRU) policy to manage the file buffer. This means that the least frequently used files are cached, thus maintaining efficient buffer utilization. File authentication buffer management File authentication buffer: Authentication checking for file access permissions is complex and time consuming. Comprehensive authentication testing is required based on multiple factors such as the department, project, sharing, and confidentiality level of the file. In order to improve performance, we implemented file authentication buffering to cache the authentication results. Expiration elimination mechanism: The file authentication buffer adopts an expiration elimination mechanism. Each cache entry has a predetermined expiration time, and once this time is exceeded, the cache will be automatically evicted. This ensures freshness of cached data and reduces memory usage. Advantages Performance optimization: Cache management reduces the repeated execution of decryption operations and authentication checks, thereby improving system response speed and performance. Resource saving: By using the LRU policy and expiration mechanism, we effectively manage memory resources and avoid memory leaks and over occupancy problems. Quick response to complex authentication: The file authentication buffer ensures fast response to complex authentication test results and reduces the pressure on the authentication service. Data compression and transmission optimization File chunking technology File storage in chunks: To optimize file transfer and storage, BabelBird Enterprise Drive uses file chunking technology. Large files are broken into smaller chunks and stored separately on the server. This helps improve file transfer efficiency and supports breakpoint resume downloads. Parallel block request: Chunked file storage allows the front end to make requests for multiple chunks in parallel when downloading a file. Once all chunks have been downloaded, the front end assembles them into a complete file, significantly increasing download speeds. File storage deduplication technology based on hash code File deduplication: BabelBird Enterprise Drive uses hash code based file storage deduplication technology. When a user uploads a file, the file's hash code is calculated and compared with the hash code of an existing file. If the same hash code is found, the system will keep only one copy of the file, thus saving storage space. Save storage space: File deduplication technology effectively reduces storage redundancy, especially files that are frequently shared and transferred in enterprises, thereby reducing storage costs. Advantages Transmission efficiency: File chunking technology and parallel block requests speed up file transfers, especially for large files and high bandwidth connections. Storage savings: File storage deduplication technology based on hash codes reduces storage requirements and maintenance costs. User experience: Fast file transfer and storage space savings improve user experience, providing more efficient file management and sharing. Asynchronous task processing Background asynchronous processing Task time consuming processing: In order to handle tasks issued by the front desk that may be time consuming or even cause HTTP requests to time out, BabelBird Enterprise Drive adopts a background asynchronous processing strategy. These tasks do not block the main HTTP request response, but are executed asynchronously in the background. Improve response speed: Background asynchronous processing ensures that the response speed of foreground requests is not affected by time consuming tasks, improving user experience. Configurable management of asynchronous tasks Task queue: In order to prevent server resource constraints, we have configured and managed asynchronous tasks. Asynchronous tasks can be configured as one or more processing queues, which can execute tasks independently. Task queues can be configured and managed based on task type and priority. Message queue: Another way to manage asynchronous tasks is to use message queues. BabelBird Enterprise Drive can be configured to use message queues to store and schedule asynchronous tasks. This mechanism ensures orderly execution and controllability of tasks. Message processing mechanism: Asynchronous tasks are controlled and executed through message processing mechanisms. After the task is added to the queue or message queue, it is processed and executed by a specialized processor. Advantages Responsiveness: Background asynchronous processing improves the system's response speed and avoids long waits. Resource control: Configurable management of asynchronous tasks allows effective control of server resources to prevent resource exhaustion. Scalability: The message queue and message processing mechanism provide system extensibility, and new asynchronous task types can be easily added. Scalability Horizontal expansion Cluster deployment: BabelBird Enterprise Drive Business Server adopts a cluster deployment model, which allows us to easily expand the capacity and performance of the system. Multiple servers in a cluster work together to share load and provide high availability. This model allows us to add new nodes as needed to meet growing user and data needs. Private cloud deployment customers can also expand performance by adding virtual machines or physical servers to meet high concurrency requirements as their users grow. For more information about the scalability of Babel Cluster deployment, see the Distributed Deployment chapter. Object storage system: Babel's storage system uses object storage technology, which is very suitable for large scale data storage and horizontal expansion. Object storage systems are highly scalable and can accommodate large amounts of data and automatically expand storage capacity by adding storage nodes when needed. For more information about the scalability of Babel object storage, see the self built object storage chapter. Load balancing: We have implemented a load balancing strategy to ensure that user requests are evenly distributed to various nodes in the cluster to avoid single points of failure and provide faster response times. Auto scaling (public cloud): Thanks to Alibaba Cloud ECS elastic computing service, our system is configured with an automatic scaling mechanism to automatically increase or decrease server nodes according to load conditions. This automatic scaling ensures system stability and performance. vertical expansion Hardware upgrade: In addition to horizontal expansion, for private cloud users we can also perform vertical expansion, that is, upgrading server hardware to increase the performance and capacity of a single server. This is an effective solution in situations where more computing power or memory is required. Database optimization: We can also optimize the database system to improve performance by adjusting configurations, using higher performance hardware, or upgrading the database management system. These improvements provide better query performance and data processing capabilities. Cache: We use caching technology to speed up data access and reduce the load on databases and storage systems. Caching supports memory caching, CDN caching and other methods, and you can choose the most suitable caching strategy according to your needs. Containerization and SOA service architecture Docker containerization Docker deployment: We use Docker containerization technology to deploy various components and modules of BabelBird Enterprise Drive. This approach allows us to package each major module as an independent Docker container, providing greater flexibility and scalability. Container orchestration: We use container orchestration tools to manage and coordinate individual containers to ensure they work together to achieve high availability and resiliency. Container image management: BabelBird Enterprise Drive uses the container image warehouse to store and manage Docker images so that new container instances can be deployed at any time. SOA service architecture Service split: We split the main functional modules of BabelBird Enterprise Drive into independent services, and each service is responsible for performing specific tasks or functions. This split improves the maintainability and scalability of the system. API communication: Services communicate through APIs, using compatible RESTful API protocols. This loosely coupled communication method allows services to be developed, tested, and deployed independently. Standalone deployment: Each service can be deployed and scaled independently, which means we can horizontally scale specific services based on demand without affecting the operation of other services. Advantages of containerization and SOA service architecture High availability: Containerization and SOA service architecture provide high availability, allowing us to quickly restore services in the event of a failure. flexibility: Containerization allows us to easily deploy, upgrade and maintain each container, while SOA service architecture provides flexible modular development and deployment options. Resource utilization: We can allocate resources as needed to avoid resource waste and achieve higher resource utilization. Fast delivery: Containerization and SOA service architecture enable new features and improvements to be delivered to users faster. Private cloud users can also enjoy fast update and upgrade services that are comparable to public cloud systems. Challenges of containerization and SOA service architecture Complexity: Managing multiple containers and services can introduce a level of complexity that requires appropriate management tools and strategies. Monitoring and logging: We use monitoring and logging tools to ensure the normal operation of containers and services, and to identify and solve problems in a timely manner. We are equipped with an automatic restart mechanism. If there is a problem with the service, the problematic module will be automatically restarted to ensure the smooth flow of the overall service." }, { "lang": "en", "slug": "integrations", "title": "Integration and open capabilities", "description": "Introducing Enterprise WeChat, DingTalk, Feishu, SSO, OA/ERP/PDM, third-party services and data ferry.", "category": "Integrations And Extensions", "top_category": "部署指南", "keywords": [ "integrated", "SSO", "Enterprise WeChat", "DingTalk", "Feishu", "Data ferry" ], "url": "en/integrations.html", "source": "content/en/integrations.md", "summary": "Integration and open capabilities The private version of BabelBird can be connected to enterprise WeChat, DingTalk, Feishu, OA, ERP, PDM, ADFS, online Office, CAD preview, OCR, AI models and other third party business systems. SSO sync with organization Babel supports the integration of third party login (SSO) platforms to achieve single sign on and unified login. And Babel supports the integration of multiple third party login platforms. For example: You can scan the QR code to log in via corporate WeChat, log in with your OA account and password, or scan the QR code to log in to DingTalk. SSO integration is divided into two modules. Third party authorized login and third party organization", "headings": [ { "level": 1, "title": "Integration and open capabilities", "id": "integration-and-open-capabilities" }, { "level": 2, "title": "SSO sync with organization", "id": "sso-sync-with-organization" }, { "level": 2, "title": "Data Ferry", "id": "data-ferry" }, { "level": 2, "title": "Enterprise WeChat, DingTalk, Feishu Access Guide", "id": "enterprise-wechat-dingtalk-feishu-access-guide" } ], "images": [], "text": "Integration and open capabilities The private version of BabelBird can be connected to enterprise WeChat, DingTalk, Feishu, OA, ERP, PDM, ADFS, online Office, CAD preview, OCR, AI models and other third party business systems. SSO sync with organization Babel supports the integration of third party login (SSO) platforms to achieve single sign on and unified login. And Babel supports the integration of multiple third party login platforms. For example: You can scan the QR code to log in via corporate WeChat, log in with your OA account and password, or scan the QR code to log in to DingTalk. SSO integration is divided into two modules. Third party authorized login and third party organizational structure synchronization. Among them, third party authorized login allows multiple sources to authorize login. However, in order to prevent user account conflicts, third party organizational structure synchronization only allows synchronization of one source. For example: the organizational structure of the OA system is synchronized, but SSO login of OA and Enterprise WeChat is supported (the organizational structures of OA and Enterprise WeChat need to use the same userID) For more information about third party login of BabelBird, please refer to the User Authentication and Authorization (SSO) chapter Data Ferry Babel Data Ferry supports Babel birds deployed in secret areas and Babel birds deployed in non confidential areas to transfer data to each other in a secure and approved manner. To achieve data exchange between confidential and non confidential areas under corporate supervision. For detailed information about BabelBird Data Ferry, please refer to the BabelBird Data Ferry chapter. Enterprise WeChat, DingTalk, Feishu Access Guide For the complete integration guide, see Reference: Enterprise WeChat, DingTalk and Feishu Access Guide." }, { "lang": "en", "slug": "deployment-requirements", "title": "Server configuration and performance requirements", "description": "Configuration recommendations and performance boundaries for business servers, databases, search, transcoding, and storage servers.", "category": "Deployment Implementation", "top_category": "部署指南", "keywords": [ "Deployment", "Server configuration and performance requirements", "Private Deployment" ], "url": "en/deployment-requirements.html", "source": "content/en/deployment-requirements.md", "summary": "Server configuration and performance requirements Recommended server configuration and performance requirements Server type and function: The hardware system required by BabelBird Enterprise Drive consists of two parts: business servers and storage servers. Business servers can be divided into 4 types. These 4 types of services can be deployed in one physical machine or virtual machine according to needs, or can be deployed dispersedly in four or more servers. Therefore, the minimum unit for deploying the Babel system is two physical servers or two virtual machines (one for business and one for storage) Service name Purpose Operating system Main business server web services, load balancing, ", "headings": [ { "level": 1, "title": "Server configuration and performance requirements", "id": "server-configuration-and-performance-requirements" } ], "images": [], "text": "Server configuration and performance requirements Recommended server configuration and performance requirements Server type and function: The hardware system required by BabelBird Enterprise Drive consists of two parts: business servers and storage servers. Business servers can be divided into 4 types. These 4 types of services can be deployed in one physical machine or virtual machine according to needs, or can be deployed dispersedly in four or more servers. Therefore, the minimum unit for deploying the Babel system is two physical servers or two virtual machines (one for business and one for storage) Service name Purpose Operating system Main business server web services, load balancing, main business function implementation Linux Database Server Database Service Linux Search server Provides file full text search and advanced search functions Linux Transcoding server Transcode and add watermarks to files that require transcoding preview windows 2012, Linux Storage server Provides file storage Linux In extreme cases, if the hard disk mounted on the server is used as storage space, Babel also supports deploying all services and storage in a physical machine or virtual machine (all in one machine mode). However, considering performance and disaster recovery or future upgrade and expansion issues, such a deployment method is not recommended. The best deployment method we recommend is a small cluster deployment of 4 servers (virtual machines). The main business services and database services are placed on one server, the search server and transcoding server are independent, and then a storage server is added. If the storage space requirement is less than 10TB, a storage server is not required. You can directly mount a hard disk or NFS disk for storage. BabelBird also supports access to third party storage. In theory, as long as the third party storage system supports the NFS or S3 protocol, it can be connected to BabelBird as a storage service. Most storage systems support both protocols. Each server must ensure smooth communication between each other. If the intranet has higher security requirements, please refer to 9.1.2 Ports that need to be opened Minimum performance configuration: The lowest performance configuration of BabelBird can support normal use by about 100 users and manage less than 10TB of data. cpu memory system disk storage disk network operating system 8 core CPU (reference benchmark E5 2609) 32G ECC memory 500G Below 10TB Gigabit Linux Recommended performance configuration examples: The recommended performance configuration of BabelBird can support normal use by 1000 2000 users and manage documents up to 1PB. Babel supports multiple deployment methods, and this instance is the standard deployment method. Use virtual machines to deploy business servers to connect to independent single or multiple object storage servers. Business servers and storage servers are managed separately. Business server: It is recommended that business servers be deployed using virtual machines Number Server type Configuration requirements Operating system Server purpose 1 Virtual machine 8 core CPU 64G memory 500G SSD system disk CentOS8 or openeuler22 Main business server/database 2 Virtual machine 8 core CPU 32G memory 500G SSD system disk CentOS8 or openeuler22 Search server 3 Virtual machine 8 core CPU 16G memory 200G SSD system disk windows 2012 R2 transcoding server The performance of the 8 core CPU should be close to that of the Zhiqiang 4410 BabelBird Enterprise Drive is deployed using Docker. In theory, it can be deployed as long as it is a Linux operating system. CentOS or open Euler is recommended. If there are no ready made virtual machine resources, you need to purchase a new business server. The business server hardware configuration requirements are as follows: Number Server type Configuration requirements Operating system Server purpose 1 Business server Xeon Silver 4210 2 20 core CPU 64G memory 2TB SSD hard drive Linux Main business server It is best to purchase VM for business servers and use virtualization for management. Storage server (object storage): Babel supports building an object storage system on a general purpose server. If the storage space is expected to be less than 100TB, it is recommended to use a single server to build the object storage system. A single object storage can use disks for data verification redundancy, and can be horizontally expanded by adding one storage server at a time. (The expansion operation can be done without stopping the server) It is recommended to use an independent physical machine for the object storage server, and the recommended configuration is as follows: Server type Configuration requirements Operating system Server purpose Notes Storage server If storage density and future expansion investment are considered, a 12T hard drive can be used. Linux Object Storage Server It is recommended to add a server with the same disk capacity for future expansion. If the required storage space is greater than 300TB, multiple servers are required to build a distributed object storage system. BabelBird also supports building distributed object storage systems for customers. To learn about distributed object storage, please refer to the \"Self Built Object Storage\" chapter." }, { "lang": "en", "slug": "deployment-ports", "title": "Port and network requirements", "description": "Open port descriptions are required for external network access, server internal communication, and deployment stages.", "category": "Deployment Guide", "top_category": "部署指南", "keywords": [ "Deployment", "Port and network requirements", "Private Deployment" ], "url": "en/deployment-ports.html", "source": "content/en/deployment-ports.md", "summary": "Port and network requirements Need to open the port For the security of the server system, we need to open only specific ports. The following are the ports that need to be opened: Ports open to the outside world (ports required for external network access): port number Port usage protocol open hosting 80 Network disk main business web external access port, not encrypted http main business server 443 Network disk main business web external access port, encrypted https Main business server 3060 Network disk main business node external access port, not encrypted TCP Main business server 3080 Network disk main business node external access port, encryption TCP Main business server Open ports are", "headings": [ { "level": 1, "title": "Port and network requirements", "id": "port-and-network-requirements" } ], "images": [], "text": "Port and network requirements Need to open the port For the security of the server system, we need to open only specific ports. The following are the ports that need to be opened: Ports open to the outside world (ports required for external network access): port number Port usage protocol open hosting 80 Network disk main business web external access port, not encrypted http main business server 443 Network disk main business web external access port, encrypted https Main business server 3060 Network disk main business node external access port, not encrypted TCP Main business server 3080 Network disk main business node external access port, encryption TCP Main business server Open ports are required between servers (open ports are required for internal server communication): Generally, during actual deployment, only external network ports (external) will be restricted, and internal ports between servers will not be restricted. However, some users who deploy across networks and computer rooms will also need to limit internal ports. Host Port number Port purpose Protocol Target network segment Business server 6379 redis access port for windows transcoding and search server TCP transcoding server and search server Business server 8080 Used by windows transcoding server to access network disk business server TCP Transcoding server and search server Business server 3306 Database port, used by the search server to access the database TCP Transcoding server and search server Business server 9000 Docker cluster deployment, internal visual interface port TCP Transcoding server and search server Business server 111 portmap port TCP+UDP Transcoding server and search server Business server 2049 TCP+UDP TCP+UDP Transcoding server and search server Business server 35000 mountd port TCP+UDP Transcoding server and search server Business Server 2376 docker REST API port for TLS encryption TCP Native Business server 2377 TCP port used for communication related to docker cluster management TCP+UDP Native Business server 7946 TCP and UDP ports, used for communication between docker swarm nodes TCP+UDP Local machine Business server 4789 docker overlay network default port TCP+UDP Local machine Search server 9200 elastic port, used by the main business server TCP business server Search server 5601 Kibana port, internal visual elastic interface access port TCP Business server Search server 9998 tika port, extract document text server port TCP Business server Search server 9000 Docker cluster deployment, internal visual interface port TCP Transcoding server and search server Search Server 2376 docker REST API port for TLS encryption TCP Native Search server 2377 TCP port used for communication related to docker cluster management TCP Native Search server 7946 TCP and UDP ports, used for communication between docker swarm nodes TCP+UDP Local machine Search server 4789 docker overlay network default port TCP+UDP Native Transcoding server Transcoding server Can access the business server Can access the business server Can access the business server Ports that need to be opened during deployment: Port number Port purpose Open server Destination IP address 22 SSH port number, used for SSH access All servers Springboard machine for deployment 443 Obtain authorization All servers 47.96.234.200 443 Get installation source All servers 120.27.245.68 443 Docker installation source All servers 13.35.121.100" }, { "lang": "en", "slug": "deployment-poc", "title": "POC deployment", "description": "POC environment, initialization, training, piloting and validation recommendations.", "category": "Deployment Implementation", "top_category": "部署指南", "keywords": [ "Deployment", "POC deployment", "Private Deployment" ], "url": "en/deployment-poc.html", "source": "content/en/deployment-poc.md", "summary": "POC deployment POC deployment POC deployment is suitable for users to conduct POC testing in the production environment before selection. POC deployment requirements: Basic POC deployment can test software functions, concurrency, API interfaces, security, and trial in the production environment. It is recommended to use standard deployment as POC test. If you need object storage, data transfer in different density areas, and high availability POC, you need to add corresponding servers and network segments. Environmental preparation It is recommended to use a virtual machine for deployment: BabelBird's privatized enterprise network disk is deployed using Docker. In theory, it can be deployed ", "headings": [ { "level": 1, "title": "POC deployment", "id": "poc-deployment" } ], "images": [], "text": "POC deployment POC deployment POC deployment is suitable for users to conduct POC testing in the production environment before selection. POC deployment requirements: Basic POC deployment can test software functions, concurrency, API interfaces, security, and trial in the production environment. It is recommended to use standard deployment as POC test. If you need object storage, data transfer in different density areas, and high availability POC, you need to add corresponding servers and network segments. Environmental preparation It is recommended to use a virtual machine for deployment: BabelBird's privatized enterprise network disk is deployed using Docker. In theory, it can be deployed as long as it is a Linux operating system. It is recommended to use CentOS or open Euler. After preparing the virtual machine as required, contact us to make an appointment and you can start POC deployment. Number Server type Configuration requirements Operating system Server purpose Remarks 1 Virtual machine 8 core CPU 32G memory 500G system disk +500G storage disk CentOS8 or openeuler22 and above Main business server 2 Virtual machine 8 core CPU 16G memory 500G system disk CentOS8 or openeuler22 and above Search server 3 Virtual machine 8 core CPU 8G memory 200G system disk windows 2012 R2 transcoding server CAD, office transcoding Win server is for better office file preview effect. BabelBird also supports pure Linux environment deployment Other requirements for POC deployment are as follows: Number Project Requirements Remarks 1 Remote access You can remotely access the server for deployment You can use a bastion machine or springboard machine or Sunflower or VPN, and you can remotely access the server for deployment. 2 External network connection The server needs to be able to connect to the external network, pull the installation package, and obtain authorization The external network address that needs to be connected: software.babel.cc docker.babel.cc The authorization period for POC deployment is 30 days, and the number of authorized accounts is 100. initialization After the deployment is completed, the Babel team will help users initialize the system and initialize the system according to user needs. Including but not limited to: Initialize the administrator account. (You need to prepare an email address as a super administrator account) Initialize the notification sending email address. (The user needs to prepare an email address that can provide password and SMTP server address as the system default outbox) Initialize department structure. (Connect with AD or import department) Initialize basic configuration. logo, company name, various configuration items. training BabelBird is a professional enterprise level application and requires certain training to help customers implement it. After POC, it is recommended to contact our sales staff for usage training. Training is divided into 3 categories: Administrator training (training administrators on configuration, use, and realization of required functions. It takes 1 2 hours) Department manager training. (Training department managers on daily management methods such as authority allocation, member addition and reduction, etc. It takes 1 hour) User training. (Training of using members. It takes 1 hour) Start POC trial After the training is completed, the formal POC trial can be started. Any questions encountered during use can be directly asked in the relevant group, and the BabelBird team will respond and answer within 2 hours. The POC system is valid for 30 days. If you need to extend it, please contact our sales staff." }, { "lang": "en", "slug": "deployment-modes", "title": "Common deployment methods", "description": "Public cloud platform, self-purchased server, single server, virtualization, object storage, distributed and disaster recovery deployment methods.", "category": "Deployment Guide", "top_category": "部署指南", "keywords": [ "Deployment", "Common deployment methods", "Private Deployment" ], "url": "en/deployment-modes.html", "source": "content/en/deployment-modes.md", "summary": "Common deployment methods Introduction to common deployment methods of BabelBird BabelBird can support multiple deployment methods on demand. Here we introduce the commonly used deployment methods of BabelBird. Deployed on public platforms such as Alibaba Cloud, Tencent Cloud, Huawei Cloud, etc.: Babel supports deployment on virtual machines (ECS) and object storage (OSS, OBS...) of public cloud service providers such as Alibaba Cloud, Tencent Cloud, Baidu Cloud, Huawei Cloud, and Tianyi Cloud, and provides services to users on the Internet. The difference compared with purely private deployment is as follows: Advantages and Disadvantages/Deployment Method Image Service Video Service Public ", "headings": [ { "level": 1, "title": "Common deployment methods", "id": "common-deployment-methods" } ], "images": [], "text": "Common deployment methods Introduction to common deployment methods of BabelBird BabelBird can support multiple deployment methods on demand. Here we introduce the commonly used deployment methods of BabelBird. Deployed on public platforms such as Alibaba Cloud, Tencent Cloud, Huawei Cloud, etc.: Babel supports deployment on virtual machines (ECS) and object storage (OSS, OBS...) of public cloud service providers such as Alibaba Cloud, Tencent Cloud, Baidu Cloud, Huawei Cloud, and Tianyi Cloud, and provides services to users on the Internet. The difference compared with purely private deployment is as follows: Advantages and Disadvantages/Deployment Method Image Service Video Service Public Network Access Stability Hardware Cost Using Alibaba Cloud storage and Alibaba Cloud servers You can use the picture service provided by Alibaba Cloud You can use Alibaba Cloud's video transcoding service, but it requires an additional fee (expensive) It can be accessed on the public network. The speed of user access depends on the user's own bandwidth and the purchased Alibaba Cloud bandwidth. The system is very stable, simple to deploy and easy to manage. You need to pay Alibaba Cloud's storage and server fees, which can be paid monthly or annually. Users can be responsible for the maintenance of the server themselves, or they can entrust us to perform maintenance and upgrades. Storage and servers are built on your own intranet Use self built image processing services (requires customers to provide high performance servers) Use self built transcoding services (requires customers to provide high performance servers). If the user does not have this requirement, you can ignore it. If there is no external network exit, users cannot access the external network. But intranet access is very fast. Stable, customized development for modules such as storage systems. The security of data is the responsibility of the user. Requires independent host and storage systems. The server can be purchased by the user or by us. Server maintenance is the responsibility of the user, and we can provide corresponding software upgrade services. Public cloud deployment (1000+ users) requirements: Number Server type Configuration requirements Operating system Server purpose 1 ECS 16 core CPU 32G memory 500G SSD system disk CentOS8 or openeuler22 Main business server 2 ECS 8 core CPU 16G memory 500G SSD system disk CentOS8 or openeuler22 Database server 3 ECS 8 core CPU 16G memory 500G SSD system disk CentOS8 or openeuler22 Search server 4 Storage Object storage system. Such as Alibaba Cloud OSS, Huawei Cloud OBS Object Storage System. Such as Alibaba Cloud OSS, Huawei Cloud OBS Object Storage System. Such as Alibaba Cloud OSS, Huawei Cloud OBS The main advantages of deploying on a public cloud platform are that it does not require dedicated maintenance, top level disaster recovery can be achieved without purchasing hardware, access to the Internet is fast, and servers and data are managed by oneself. The main disadvantages of deploying on a public cloud platform are: data is not localized, and annual server rental fees and corresponding bandwidth storage costs need to be paid. Self purchased servers (2 physical machines) for deployment: If you want to deploy a purely private BabelBird in your own computer room and do not have spare virtual machine resources, you need to purchase hardware deployment. The requirements are as follows: Physical server brand recommendation: It is recommended to use 2 DELL T440 servers to complete the system setup. And purchase DELL 3 year gold service. The server's system disk can optionally use raid to enhance redundancy. If you use the raid1 solution, the number of hard disks required needs to be increased by 2 times. (2TB SSD becomes 2TB SSD 2) Physical server brand recommendation: It is recommended to use 2 DELL T440 servers to complete the system construction. And purchase DELL 3 year gold service. The server's system disk can optionally use raid to enhance redundancy. If you use the raid1 solution, the number of hard disks required needs to be increased by 2 times. (2TB SSD becomes 2TB SSD 2) Physical server brand recommendation: It is recommended to use 2 DELL T440 servers to complete the system construction. And purchase DELL 3 year gold service. The server's system disk can optionally use raid to enhance redundancy. If you use the raid1 solution, the number of hard disks required needs to be increased by 2 times. (2TB SSD becomes 2TB SSD 2) Physical server brand recommendation: It is recommended to use 2 DELL T440 servers to complete the system construction. And purchase DELL 3 year gold service. The server's system disk can optionally use raid to enhance redundancy. If you use the raid1 solution, the number of hard disks required needs to be increased by 2 times. (2TB SSD becomes 2TB SSD 2) Physical server brand recommendation: It is recommended to use 2 DELL T440 servers to complete the system construction. And purchase DELL 3 year gold service. The server's system disk can optionally use raid to enhance redundancy. If you use the raid1 solution, the number of hard disks required needs to be increased by 2 times. (2TB SSD becomes 2TB SSD 2) Physical server brand recommendation: It is recommended to use 2 DELL T440 servers to complete the system construction. And purchase DELL 3 year gold service. The server's system disk can optionally use raid to enhance redundancy. If you use the raid1 solution, the number of hard disks required needs to be increased by 2 times. (2TB SSD becomes 2TB SSD 2) Two server plan business + storage Two server plan business + storage Two server plan business + storage Two server plan business + storage Two server plan business + storage Two server plan business + storage Number Server type Configuration requirements Operating system Server purpose Remarks 1 Server Zhiqiang Silver 4410 2 16 core CPU, 64G memory, 2TB SSD hard drive open Euler, Ubuntu, CentOS Main business server It is recommended to install VM 2 Storage 4410 2 16 core CPU, 64G memory, 500G SSD hard disk + required hard disk space (no raid or raid0 required) open Euler, Ubuntu, CentOS Storage server Hard disk capacity is configured according to storage space requirements The above configuration can support 1000+ users and about 150TB of storage space. Babel storage server uses an object storage system and supports distributed deployment (multiple storage servers) with a minimum requirement of one physical server. Supports the use of hard disk groups for verification, and supports multiple verification types such as 2+1, 3+1, 4+1... etc. See the self built object storage chapter for details. If you need to expand the storage space, just add a single storage server. You can also add a storage server as a backup server to synchronize the backup in real time. If there is a problem with the main storage server, switch to the backup server and it can be used normally. Single server (1 physical machine) deployment: Some customers who do not have a computer room but need to deploy BabelBird privately and have small storage space requirements (less than 10TB) can choose to deploy BabelBird on a single server. Just purchase a tower server that meets the requirements and place it in your company to meet the needs of using BabelBird. Physical server brand recommendations: If there is no computer room, it is recommended to use tower servers for deployment. It is recommended that the server storage hard disk is raid1 or raid5+1. The system disk of the server can optionally use raid to enhance redundancy. If you use the raid1 solution, the number of hard disks required needs to be increased by 2 times. (2TB SSD becomes 2TB SSD 2) Physical server brand recommendations: If there is no computer room, it is recommended to use tower servers for deployment. It is recommended that the server storage hard disk is raid1 or raid5+1. The system disk of the server can optionally use raid to enhance redundancy. If you use the raid1 solution, the number of hard disks required needs to be increased by 2 times. (2TB SSD becomes 2TB SSD 2) Physical server brand recommendations: If there is no computer room, it is recommended to use tower servers for deployment. It is recommended that the server storage hard disk is raid1 or raid5+1. The system disk of the server can optionally use raid to enhance redundancy. If you use the raid1 solution, the number of hard disks required needs to be increased by 2 times. (2TB SSD becomes 2TB SSD 2) Physical server brand recommendations: If there is no computer room, it is recommended to use tower servers for deployment. It is recommended that the server storage hard disk is raid1 or raid5+1. The system disk of the server can optionally use raid to enhance redundancy. If you use the raid1 solution, the number of hard disks required needs to be increased by 2 times. (2TB SSD becomes 2TB SSD 2) Physical server brand recommendations: If there is no computer room, it is recommended to use tower servers for deployment. It is recommended that the server storage hard disk is raid1 or raid5+1. The system disk of the server can optionally use raid to enhance redundancy. If you use the raid1 solution, the number of hard disks required needs to be increased by 2 times. (2TB SSD becomes 2TB SSD 2) Physical server brand recommendations: If there is no computer room, it is recommended to use tower servers for deployment. It is recommended that the server storage hard disk is raid1 or raid5+1. The system disk of the server can optionally use raid to enhance redundancy. If you use the raid1 solution, the number of hard disks required needs to be increased by 2 times. (2TB SSD becomes 2TB SSD 2) One server (all in one solution) One server (all in one solution) One server (all in one solution) One server (all in one solution) One server (all in one solution) One server (all in one solution) serial number Server type Configuration requirements operating system Server purpose Remark 1 server Zhiqiang Silver 4410 2 16 core CPU 64G memory 2TB SSD hard drive + hard drive that requires storage capacity 2 (hard drives can also be added in the future) openEuler, Ubuntu, CentOS 8.5 and above All in one machine It is recommended to install VM with 2 CPU authorization. The entire BabelBird system deployed on a single server does not support object storage and uses read only hard disks or NFS for storage. It is recommended to use raid1 to improve system reliability. A backup server can be added for data synchronization and backup. If there is a problem with the main server, you can use the backup server to reconstruct the data. Deploy on existing virtual machine (hyperconverged) system: This is currently the most commonly used deployment method. It is deployed under the existing servers and hardware of the enterprise without purchasing new equipment. Deployment is completed in the customer's existing VM or virtual machine allocated by the hyper converged platform, which is suitable for users who already have certain IT construction and management. It is deployed in a small cluster, and the virtual machine platform is responsible for the unified management of the server. Supports most virtualized systems. It is recommended to deploy four virtual machines with storage space mounted. Number Server type Configuration requirements Operating system Server purpose 1 Virtual machine 8 core CPU 32G memory 500G SSD system disk CentOS8 or openeuler22 Main business server 2 Virtual machine 8 core CPU 16G memory 500G SSD system disk CentOS8 or openeuler22 Database server 3 Virtual machine 8 core CPU 16G memory 500G SSD system disk CentOS8 or openeuler22 Search server 4 Virtual machine 8 core CPU 16G memory 200G SSD system disk windows 2012 R2 transcoding server 5 Storage Support NFS or S3 interface storage system or virtual machine mounting disk as storage disk Support NFS or S3 interface storage system or virtual machine mounting disk as storage disk Support NFS or S3 interface storage system or virtual machine mounting disk as storage disk If there is a need for system redundancy, you can prepare 6 virtual machines to complete database backup and system redundancy. Number Server type Configuration requirements Operating system Server purpose 1 Virtual machine 8 core CPU 32G memory 500G SSD system disk CentOS8 or openeuler22 Main business server 2 Virtual machine 8 core CPU 32G memory 500G SSD system disk CentOS8 or openeuler22 From business server 3 Virtual machine 8 core CPU 16G memory 500G SSD system disk CentOS8 or openeuler22 Main database server 4 Virtual machine 8 core CPU 16G memory 500G SSD system disk CentOS8 or openeuler22 From database server 5 Virtual machine 8 core CPU 16G memory 500G SSD system disk CentOS8 or openeuler22 Database server 6 Virtual machine 8 core CPU 16G memory 200G SSD system disk windows 2012 R2 transcoding server 7 Storage Distributed Object Storage Distributed Object Storage Distributed Object Storage Supports virtual machine mounting disks to use the mounted disk as storage space. It can also be connected to third party storage systems such as san storage or object storage systems. BabelBird also provides customers with self built object storage services. Self built object storage server and virtual machine deployment: Babel supports customers to build object storage on general purpose servers. Because of the advantages of object storage software defined storage (high availability, easy horizontal expansion), it is recommended that users without object storage can purchase a new server and deploy the Babel object storage system to use it with the Babel business system running on a virtual machine (hyper convergence). The business server requirements are the same as those in the previous section \"Deployment on Existing Virtual Machine (Hyper Converged) System\". For a detailed introduction to Babel object storage, please see the \"Self Built Object Storage Server\" chapter. Most of our customers end up choosing object storage servers for storage. At least a single server is supported to build an object storage system (space requirement is less than 150TB). Server type Configuration requirements Operating system Server purpose Notes Storage server If storage density and future expansion investment are considered, a 12T hard drive can be used. Linux Object Storage Server It is recommended to add a server with the same disk capacity for future expansion. Single server object storage network topology diagram: We also support building a distributed object storage system composed of multiple servers. The minimum requirement for a distributed storage system is 2+1, which means three storage servers need to be prepared. The performance requirements are consistent with those of a single object storage. The currently recommended minimum unit for physical distributed storage is 3 storage servers. The 2+1 error correction code means that every time two storage nodes are expanded, one server needs to be added as an error correction server. In this way, 4+1 means that adding 4 storage servers requires adding an error correction server. So the disk utilization of 4+1 is higher than that of 2+1. The first construction using the 4+1 solution requires 5 storage servers. The minimum unit added for each expansion is the same as the minimum server unit required for the first construction. Multi server distributed object storage network topology diagram: You can add a new storage server or a set of storage servers for real time backup. If there is a problem with the primary storage server, quickly switch to the backup server and it can be used normally. Distributed high availability and high redundancy deployment: Because financial institutions, hospitals, energy, and very large enterprises have hard targets for uninterrupted business, they need systems that can achieve high availability and high redundancy. Services will not be interrupted due to a single point failure of the server, and hot switching and hot repair can be performed. In extreme cases, even network equipment such as switches need to be separated from active and backup, which requires the use of distributed high availability and high redundancy deployment. Babel supports a variety of high availability and high redundancy solutions and can be deployed in traditional distributed systems to achieve high availability and high redundancy. We can also build a distributed system suitable for Babel for customers. (Customers need to purchase hardware by themselves as required) Babel distributed deployment can ensure that any single point of failure will not affect the normal use of the system. The recommended distributed and easy to deploy solution uses active active active backup for the business server and distributed storage for the storage system. If there is a need for management and control of confidential and non confidential areas, please see the \"Data Ferry Chapter\" for details. Babel High Availability System Network Topology Off site disaster recovery deployment For users who have higher requirements for data preservation, BabelBird also supports off site disaster recovery solutions. It means backing up important database and file storage contents to an off site backup system. If there is a problem in the local computer room, as long as the backup data is there, the system can be rebuilt anywhere and restored to normal use. BabelBird can build off site disaster recovery servers for customers, but it does not support advanced backup methods such as hot and cold data separation. If the amount of data is very large (above 1PB) and considering cost effectiveness, it is recommended to use a professional backup system (such as NBU, Yunqi). BabelBird has a backup API that supports the NBU standard and can be called. Off site disaster recovery deployment has higher requirements on the network environment. It is best to have dedicated lines or stable VPN connections between computer rooms in different locations. Using the backup system can only restore and reconstruct data through backup after a problem occurs. Direct switching to backup data is not supported. Generally, the data reconstruction cycle will take a long time. Schematic diagram of using backup system for off site disaster recovery: If hot and cold data do not need to be classified and saved, BabelBird can also use the off site disaster recovery function of object storage to complete off site disaster recovery deployment for customers. Use object storage for remote disaster recovery. When the main system has a problem, you can quickly switch to the disaster recovery server." }, { "lang": "en", "slug": "deployment-object-storage", "title": "Object storage and erasure coding", "description": "MinIO object storage, erasure coding, space utilization, hardware preparation and expansion instructions.", "category": "Architecture And Storage", "top_category": "部署指南", "keywords": [ "Deployment", "Object storage and erasure coding", "Private Deployment" ], "url": "en/deployment-object-storage.html", "source": "content/en/deployment-object-storage.md", "summary": "Object storage and erasure coding Self built object storage server Babel object storage is an object storage system developed on the open source MinIO system. It inherits MinIO's advantages of high performance, scalability, and data security, and is more suitable for the application scenarios of BabelBird Enterprise Drive. As an advanced object storage system, Babel object storage system has unparalleled advantages over traditional storage systems in terms of speed, security, stability, high availability, and horizontal expansion. Advantages of Babel object storage system Performance MinIO is claimed to be the fastest object storage server in the world. Published GET/PUT results of over 325 ", "headings": [ { "level": 1, "title": "Object storage and erasure coding", "id": "object-storage-and-erasure-coding" } ], "images": [], "text": "Object storage and erasure coding Self built object storage server Babel object storage is an object storage system developed on the open source MinIO system. It inherits MinIO's advantages of high performance, scalability, and data security, and is more suitable for the application scenarios of BabelBird Enterprise Drive. As an advanced object storage system, Babel object storage system has unparalleled advantages over traditional storage systems in terms of speed, security, stability, high availability, and horizontal expansion. Advantages of Babel object storage system Performance MinIO is claimed to be the fastest object storage server in the world. Published GET/PUT results of over 325 GiB/sec and 165 GiB/sec on 32 NVMe drive nodes and 100Gbe network, a clear advantage compared to Amazon S3 and far superior to traditional HDFS. High availability: MinIO ensures high reliability and availability through multiple copies of data, failover and automatic recovery, thereby ensuring that data is not lost and business is not interrupted. Low redundancy and high tolerance for disk damage: the standard and highest data redundancy coefficient is 2 (that is, storing a 1 M data object actually takes up 2 MB of disk space). However, data can still be read even if any n/2 disks are damaged (n is the number of disks in an erasure coding set). And this damage recovery is based on a single object, not based on the entire storage volume. Security: MinIO delivers more functionality with the highest levels of encryption and extensive optimizations that virtually eliminate the overhead typically associated with storage encryption operations. Data is stored in blocks and on each hard disk, and data cannot be restored even if you obtain read and write permissions from the hard disk or server. Extremely high scalability: MinIO supports distributed deployment and can be expanded horizontally. When more storage space or higher performance is needed, MinIO can be easily expanded by adding new nodes. At least it supports the deployment of object storage systems on a single machine, instead of the traditional requirement of three independent servers. Object storage system and erasure coding About erasure coding Babel Object Storage System (MinIO) uses erasure coding and checksums to protect data from hardware failures and silent data corruption. Even if half (N/2) of the hard drives are lost in the highest redundancy state, you can still recover data. Erasure coding is a mathematical algorithm for recovering lost and damaged data. MinIO uses Reed Solomon code to split objects into N/2 data and N/2 parity blocks. This means that if there are 12 disks, an object will be divided into 6 data blocks and 6 parity blocks. Any 6 disks can be lost (regardless of whether they store data blocks or parity blocks) and can still be recovered from the data in the remaining disks. We call the data storage D and the erasure code (parity) P. By default, the drive is sliced in N/2 data and N/2 parity blocks (customizable to support higher space utilization) Erasure coding is different from traditional multi copy technology. It has higher disk utilization and higher data recovery efficiency. (However, many storage manufacturers promote erasure coding as multiple copies and refer to the P number as the number of copies. This is inaccurate and will cause a lot of misunderstandings.) Multiple copies in the context of Babel refers to adding backup servers to fully synchronize and store data. Characteristics of erasure coding and differences from raid technology Erasure coding protects data from multiple drive failures RAID6 tolerates two drive failures while MinIO erasure coding allows the loss of half the drives RAID is a volume level erasure code, while MinIO erasure code is an object based erasure code (without downtime). Effective space calculation (space utilization) Assuming you need 100TB of storage space, how many hard drives you need to buy depends on the redundancy standard you choose. For example: using the 3+1 redundancy method, 100TB of available space requires the purchase of 12 12TB hard drives, 4 hard drives forming 3 groups, 9 data disks and 3 parity disks, the available space is 9 12, a total of 108TB available. If 2+1 redundancy is adopted, 15 10TB hard drives, 10 data disks, and 5 parity disks are required. In the 3+1 plan, only 3 of the 12 hard disks can fail without affecting system usage and data restoration. However, if you use the 2+1 plan, although you need to purchase more hard disks, any 5 of the 15 hard disks can fail without affecting the system usage. After replacing the damaged hard drive, the system can automatically repair the data. Please refer to the table below for space utilization. If the space requirement is large (more than 150TB) and continues to grow, considering storage density and cost performance, it is recommended that a server be equipped with 16 hard disks at a time. Different numbers of disks and space utilization can be calculated by clicking the link below https://min.io/product/erasure code calculator?ref=docs Hardware preparation Required hardware configuration. Babel supports a single server to build an object storage system (single node), using hard disk groups as redundant objects. Up to half of the hard drive can be damaged without affecting the normal use of the system. The Babel object storage system requires customers to prepare hardware servers in advance for deployment as required. The minimum configuration requires 2 Xhiqiang CPUs, 64GB memory and 400G solid state drives (system disks), and then the mechanical hard drives required to increase the corresponding storage capacity. To calculate the storage space required and the number of hard drives to purchase, click the link below to calculate it. https://min.io/product/erasure code calculator?ref=docs The recommended hardware configuration is as follows: Server type Configuration requirements Operating system Server purpose Notes Storage server If storage density and future expansion investment are considered, a 12T hard drive can be used. Linux Object Storage Server It is recommended to add a server with the same disk capacity for future expansion. Babel object storage uses software defined storage technology, so the hard disk does not require RAID. Considering that some servers require RAID to support multiple disks, in this case, each hard disk can be set to RAID0 pass through mode. Each expansion in single server mode requires adding a server with the same configuration. Uninterrupted service is possible during capacity expansion. Single server deployment also supports adding a server with the same configuration to establish active standby mode for real time synchronization. If the hardware of a server is damaged, it can be quickly switched to the backup server. The effective disk space capacity is related to the selected redundancy method. For example: use 8 10T hard drives to build an object storage system, and adopt a 3+1 redundancy scheme, which is equivalent to a group of 4 hard drives, divided into 2 groups, with an effective available space of 60TB. At the same time, if any two of the 8 hard drives are damaged, the data and system usage will not be affected. The damaged hard drive can be automatically rebuilt. If a 7+1 redundancy scheme is adopted, the effective available space is 70TB. Any damage to one of the eight hard drives will not affect data and system usage. Multi server deployment (distributed). Babel object storage system supports multi server deployment. If the server is used as a redundant unit, at least 3 servers are required, that is, 2+1 mode. However, considering the space utilization, it is recommended to adopt the 3+1 solution (that is, 4 servers). The configuration requirements for each node (server) are consistent with the single server deployment above. It is recommended that the node configuration be consistent (same operating system, same number of disks and same network connection) The number of drives provided by each node must be the same The time difference between nodes cannot be greater than 15 minutes (it is recommended to use NTP to ensure time consistency) The space utilization calculation is the same as for a single server." }, { "lang": "en", "slug": "deployment-service-flow", "title": "Implementation process and initialization services", "description": "Pre-deployment preparation, implementation phase, initialization, training and data migration.", "category": "Deployment Implementation", "top_category": "部署指南", "keywords": [ "Deployment", "Implementation process and initialization services", "Private Deployment" ], "url": "en/deployment-service-flow.html", "source": "content/en/deployment-service-flow.md", "summary": "Implementation process and initialization service Privatization requirements and service procedures In order to ensure the experience and quality of using the BabelBird system, all privatized deployment work of BabelBird is deployed remotely or on site and certificates are issued by the BabelBird team. Deployment by an agent team or self deployment by customers is not currently supported. At the same time, the maintenance work of the system is also carried out by the Babel operation and maintenance team on a regular basis remotely. Customers only need to prepare the hardware and access resources as required, and leave the rest to the Babel team. Things that need to be prepared in the early s", "headings": [ { "level": 1, "title": "Implementation process and initialization service", "id": "implementation-process-and-initialization-service" } ], "images": [], "text": "Implementation process and initialization service Privatization requirements and service procedures In order to ensure the experience and quality of using the BabelBird system, all privatized deployment work of BabelBird is deployed remotely or on site and certificates are issued by the BabelBird team. Deployment by an agent team or self deployment by customers is not currently supported. At the same time, the maintenance work of the system is also carried out by the Babel operation and maintenance team on a regular basis remotely. Customers only need to prepare the hardware and access resources as required, and leave the rest to the Babel team. Things that need to be prepared in the early stage of privatized deployment: Calculate the approximate number of users, concurrency, storage space and space growth rate and let the Babel account manager evaluate the required configuration. The customer evaluates the remaining resources (if any) of the existing server and selects a deployment method based on the actual situation. Babel issued a privatization deployment plan. Customers prepare corresponding servers and access resources according to the plan, allocate servers, and install operating systems. Ensure that the server can be accessed via external remote desktop (you can also use Sunflower) and ssh, and open the corresponding port (our deployment technicians will put forward specific port requirements) It is best for the user to provide a domain name. If there is no domain name, a fixed IP address is required. The solution using IP address to access needs to ensure that the IP address will not change during use. If you need to access your email to retrieve your password or send a verification code to your mobile phone number, you need to prepare the corresponding email access or SMS gateway. Number Project Requirements Remarks 1 Domain name An independent primary domain name or secondary domain name is required A secondary domain name can be set based on the company's original domain name. Such as yun.company.com 2 Email An email address that can send notification emails is required An email address that supports SMTP is sufficient Email push related MailUser=xxxx@mail.com MailPassword=password MailHost=Mail server address MailPort=Port number 3 Remote access Remote access to the server for configuration Support remote access and control of the server 4 SSl certificate https needs to apply for an SSL certificate Apply like a digital certificate authority CA. Recommended Application OV Wildcard 5 SMS interface If you need a mobile invitation, please register with your mobile phone. You need to activate the SMS interface service (optional) Cloud service providers such as Alibaba Cloud and Tencent Cloud also provide SMS service interfaces, which can be activated by applying implementation stage Notify us after the preparation work is completed, and we will give users a specific implementation time schedule. Please maintain smooth access to the external network during the implementation time period. Implementation generally takes 2 3 working days. On the first day, Babel is deployed and installed remotely, on the second day it is tested and accepted, and on the third day, problems encountered are corrected. Once the implementation is complete we will notify the user and then start the initialization phase Initialize service Babel provides initialization services to all private cloud customers, including: Maintenance personnel training (remote or on site) Help users with data migration, user import, permission assignment, etc. (remotely or on site) User training (remote or on site)" }, { "lang": "en", "slug": "deployment-third-party", "title": "Third-party service access", "description": "Access conditions for third-party services such as online Office, CAD, signature, OCR, DLP, and AI.", "category": "Integrations And Extensions", "top_category": "部署指南", "keywords": [ "Deployment", "Third-party service access", "Private Deployment" ], "url": "en/deployment-third-party.html", "source": "content/en/deployment-third-party.md", "summary": "Third party service access Access third party services As an office platform centered on corporate documents, the privatized BabelBird Enterprise Drive can easily integrate various third party services into BabelBird to meet different needs by accessing third party APIs. These services include but are not limited to: electronic signature, advanced CAD preview, office, text recognition, image recognition... and other third party services to solve your needs. Conditions for accessing third party services In theory, third party applications or service modules that support the BS architecture can be accessed. Third party services must provide open APIs so that BabelBird Enterprise Drive can be i", "headings": [ { "level": 1, "title": "Third party service access", "id": "third-party-service-access" } ], "images": [], "text": "Third party service access Access third party services As an office platform centered on corporate documents, the privatized BabelBird Enterprise Drive can easily integrate various third party services into BabelBird to meet different needs by accessing third party APIs. These services include but are not limited to: electronic signature, advanced CAD preview, office, text recognition, image recognition... and other third party services to solve your needs. Conditions for accessing third party services In theory, third party applications or service modules that support the BS architecture can be accessed. Third party services must provide open APIs so that BabelBird Enterprise Drive can be integrated with them If it is an Internet service, the server needs to be able to access the external network. Enterprises need to authorize themselves or entrust us to purchase third party services for access. Recommended accessible services File anti leakage system: ipguard Online office editing: onlyoffice (self contained), office365, WPS Online, Yongzhong office Advanced CAD preview: Haochen Cloud Atlas, Dream CAD CAD online editing: Dream CAD Online signature: Sign on Text recognition and image recognition: Baidu Qianfan (Smart Cloud) AI related: Zhichao AI (self owned), ChatGPT, Zhipu AI" }, { "lang": "en", "slug": "deployment-data-ferry", "title": "Data ferry deployment", "description": "Transfer files, approvals, ports, tokens and audit processes between confidential and non-confidential zones.", "category": "Integrations And Extensions", "top_category": "部署指南", "keywords": [ "Deployment", "Data ferry deployment", "Private Deployment" ], "url": "en/deployment-data-ferry.html", "source": "content/en/deployment-data-ferry.md", "summary": "Data ferry deployment Data ferry Babel Data Ferry supports Babel birds deployed in secret areas and Babel birds deployed in non confidential areas to transfer data to each other in a secure and approved manner. To achieve data exchange between confidential and non confidential areas under corporate supervision. For detailed information about BabelBird Data Ferry, please refer to the BabelBird Data Ferry chapter. Zhichao AI Zhichao AI is the AI platform of BabelBird Enterprise Drive, including three main modules: Zhichao AI customer service, Zhichao AI knowledge base, and Zhichao AI document assistant. These modules combine large model APIs and custom training to meet the enterprise's intelli", "headings": [ { "level": 1, "title": "Data ferry deployment", "id": "data-ferry-deployment" }, { "level": 3, "title": "The three main modules of Zhichao AI", "id": "the-three-main-modules-of-zhichao-ai" }, { "level": 3, "title": "Technical Solutions", "id": "technical-solutions" }, { "level": 3, "title": "Advantages", "id": "advantages" }, { "level": 3, "title": "Multi task collaboration and execution flow weight", "id": "multi-task-collaboration-and-execution-flow-weight" }, { "level": 3, "title": "Function Overview", "id": "function-overview" }, { "level": 3, "title": "Core operation and configuration rules", "id": "core-operation-and-configuration-rules" }, { "level": 3, "title": "Permissions and data security control", "id": "permissions-and-data-security-control" }, { "level": 3, "title": "Typical business application scenarios", "id": "typical-business-application-scenarios" }, { "level": 3, "title": "Function Overview", "id": "function-overview-2" }, { "level": 3, "title": "Scope of application and permission control", "id": "scope-of-application-and-permission-control" }, { "level": 3, "title": "Core rule engine and configuration dimensions", "id": "core-rule-engine-and-configuration-dimensions" }, { "level": 3, "title": "Refined pruning and anti conflict mechanism of original names", "id": "refined-pruning-and-anti-conflict-mechanism-of-original-names" }, { "level": 3, "title": "Global formatted output control", "id": "global-formatted-output-control" }, { "level": 3, "title": "Function Overview", "id": "function-overview-3" }, { "level": 3, "title": "Execution logic and boundary conditions", "id": "execution-logic-and-boundary-conditions" }, { "level": 3, "title": "Extensive format compatibility matrix", "id": "extensive-format-compatibility-matrix" }, { "level": 3, "title": "Function Overview", "id": "function-overview-4" }, { "level": 3, "title": "Flexible triggering mechanism and scope", "id": "flexible-triggering-mechanism-and-scope" }, { "level": 3, "title": "Core intelligent sorting rule engine", "id": "core-intelligent-sorting-rule-engine" }, { "level": 3, "title": "Overview of business scenarios and functions", "id": "overview-of-business-scenarios-and-functions" }, { "level": 3, "title": "Signature asset library and personalized configuration", "id": "signature-asset-library-and-personalized-configuration" }, { "level": 3, "title": "Intelligent adaptive interaction and immersive guidance system", "id": "intelligent-adaptive-interaction-and-immersive-guidance-system" }, { "level": 3, "title": "Function Overview and Business Value", "id": "function-overview-and-business-value" }, { "level": 3, "title": "Large scale generation of standard directory arrays", "id": "large-scale-generation-of-standard-directory-arrays" }, { "level": 3, "title": "\"One click deployment\" of project level folders and permissions", "id": "one-click-deployment-of-project-level-folders-and-permissions" }, { "level": 3, "title": "Real time status monitoring and intelligent fault tolerance mechanism", "id": "real-time-status-monitoring-and-intelligent-fault-tolerance-mechanism" }, { "level": 3, "title": "Scope of use", "id": "scope-of-use" }, { "level": 3, "title": "Problems that need to be solved", "id": "problems-that-need-to-be-solved" }, { "level": 3, "title": "BabelBird Solution", "id": "babelbird-solution" }, { "level": 3, "title": "Basic introduction", "id": "basic-introduction" }, { "level": 2, "title": "User interface", "id": "user-interface" }, { "level": 2, "title": "Performance optimization", "id": "performance-optimization" }, { "level": 3, "title": "Advantages", "id": "advantages-2" }, { "level": 3, "title": "Advantages", "id": "advantages-3" }, { "level": 3, "title": "Advantages", "id": "advantages-4" }, { "level": 3, "title": "Advantages", "id": "advantages-5" }, { "level": 2, "title": "Scalability", "id": "scalability" }, { "level": 2, "title": "Private deployment", "id": "private-deployment" } ], "images": [], "text": "Data ferry deployment Data ferry Babel Data Ferry supports Babel birds deployed in secret areas and Babel birds deployed in non confidential areas to transfer data to each other in a secure and approved manner. To achieve data exchange between confidential and non confidential areas under corporate supervision. For detailed information about BabelBird Data Ferry, please refer to the BabelBird Data Ferry chapter. Zhichao AI Zhichao AI is the AI platform of BabelBird Enterprise Drive, including three main modules: Zhichao AI customer service, Zhichao AI knowledge base, and Zhichao AI document assistant. These modules combine large model APIs and custom training to meet the enterprise's intelligent customer service, file content analysis and question answering needs. The three main modules of Zhichao AI Zhichao AI customer service: This module serves as the AI customer service of the enterprise. BabelBird Enterprise Drive itself also uses this module to answer the problems encountered by users when using BabelBird Enterprise Drive. We also open this service to corporate customers. Companies can provide product manuals, FAQs, customer service documents and other materials to Zhichao AI for learning and fine tuning to meet corporate customer service needs. Enterprises can also embed Zhichao AI's code blocks into their websites to quickly establish an external intelligent customer service system. Zhichao AI customer service can significantly reduce customer service costs and save time and resources. Zhichao AI Document Assistant: This module is used to answer questions about a single document. By analyzing the document content, Zhichao AI can answer various questions about the document content, from summarizing to revealing key findings. Users can ask questions to the AI ​​instead of having to read lengthy documents themselves, improving work efficiency. Zhichao AI knowledge base: This module allows companies to customize their own AI assistants. The Zhichao AI team will help prepare training sets and adjust parameters based on the company's data, thereby establishing an exclusive AI model that can provide answers within the scope of permissions for people with different permissions on BabelBird. It can be used as a corporate knowledge base assistant in the form of questions and answers. Technical Solutions Answer questions intelligently: Zhichao AI uses large models and custom training to ensure accuracy. It also uses small models to assist the work of large models, reducing problems such as talking nonsense, pretending not to understand, or leaking secrets. In addition, Zhichao AI follows BabelBird’s authority management mechanism to ensure that users can only obtain answers within their authority. Automatic learning: Zhichao AI can accumulate knowledge by studying the files provided by users and provide users with more accurate answers. All documents participating in training are specified and agreed to by the user to ensure data privacy and compliance. Advantages Reduced customer service costs: Zhichao AI customer service can significantly reduce the customer service costs of enterprises. There is no need to train personnel on a large scale, and AI can provide answers at any time. Quick question answering: Zhichao AI can answer users' questions instantly, improving work efficiency. Document content analysis: Zhichao AI Document Assistant can quickly analyze document content to help users quickly obtain information without reading the entire document. Customized AI assistant: Enterprises can customize exclusive AI assistants for Zhichao AI knowledge base according to their own needs to meet specific knowledge management and question answering needs. Permission management: Zhichao AI can provide answers within different ranges based on user permissions to ensure data security and compliance. Automate tasks Facing the growing number of digital assets, the traditional manual file management model can no longer meet the demand for efficient circulation. The \"automated task\" engine launched by BabelBird aims to hand over tedious and repetitive file processing actions to the system background for automatic execution. By establishing a \"self organizing and self standardizing\" intelligent circulation system, the cost of manual intervention is significantly reduced, allowing the team to focus on core business creation. Automated tasks are included in the standard version and users do not need to purchase it separately. Core operating mechanism: Flexible permission driven: Relying on the platform's extremely fine grained permission management system, users with corresponding permissions on the target network disk or folder can independently configure, turn on or off specific automation tasks as needed. Multi task flow concatenation (Workflow): Automated tasks do not run in isolation and support the free combination of multiple rules to form a workflow. For example: after a file is uploaded, the system can first trigger \"automatic rename\" to standardize the file name, and then immediately trigger \"automatic sorting\" to archive it to the relevant directory, achieving multiple steps in one go. Continuously expanding capability matrix: The automation engine is highly scalable. In addition to the existing basic functions, the platform will continue to access more automated processing nodes to meet increasingly complex business scenarios. Currently supported core tasks (including but not limited to): Automatic renaming: Unify and standardize naming according to preset rules (such as keyword replacement, case conversion). Automatic organization and cleaning: Automatically classify archived files based on trigger conditions, or clean up space regularly based on policies. Automatic PDF conversion and signature: Automatically generate a PDF copy of the source file, or stamp the company signature in the cloud. Create folders in batches: Generate a standard business directory tree with one click by importing data templates (such as Excel). Multi task collaboration and execution flow weight In complex business scenarios, multiple automated tasks are often configured in one folder. In order to ensure the logical rigor and security of data processing, a strict automated processing sequence is preset at the bottom of the system. The specific execution weight (the higher the value, the priority for execution) is as follows: Automatically clean folders (weight 10): highest system priority. If there are qualified cleaning tasks, they will be executed first to avoid investing subsequent computing power in invalid data that will be discarded. Automatic decompression (weight 9): Prioritize the release of packaged assets for subsequent circulation. Automatic renaming (weight 8): Priority is given to completing the standardization and unification of naming before files enter classification and archiving. Automatic format conversion category (weight 7): Prioritize conversion tasks such as transferring PDF, pictures or audio and video formats. Automatic sorting/sorting (weight 6): Executed as the end node of the flow. This means that core pre standardization operations such as cleaning, renaming and format conversion have been completed before files are moved and classified. Automatically clean files (Auto Clean) Function Overview In daily cross department collaboration or project cycle management, a large amount of temporary data, process files or short term circulation materials are often inevitably generated in the enterprise network disk. The \"Automatically Clean Files\" function is designed to provide enterprises with automated storage space optimization and directory slimming solutions. Through this function, the system can automatically delete redundant files in specified folders according to specific rules set by the user, keeping the project directory clean for a long time and releasing high value storage resources. Core operation and configuration rules This module uses a strict logical rule engine to perform file cleaning actions to ensure the accuracy and efficiency of data processing: Target directory locking: The task configuration needs to explicitly specify the target folder to which the rule applies. Users can choose to apply the rules only to newly entered files in the folder, or to apply the rules to historical files that already exist in the directory at the same time. Multi dimensional rule triggering: Supports precise filtering and elimination of files based on specific rules. Common determination rules can cover file types (such as temporary files with specific suffixes), life cycles (such as files entering a directory for more than a specified number of days), and other dimensions to achieve highly customized cleaning strategies. Workflow collaboration: As the end link of complete automated circulation, automatic cleaning can be seamlessly connected with other tasks. For example, after the \"automatic conversion to PDF\" task is completed, the system can immediately trigger the \"automatic cleaning\" rule to uniformly clean the original draft files, leaving only the standardized final version. Permissions and data security control Since the cleaning task involves the sensitive operation of file deletion, this function relies heavily on Babel's extremely fine grained permission management system: Configuration permissions: Only collaboration members with corresponding advanced permissions (such as management and deletion permissions) for the folder can create or modify automatic cleanup tasks to prevent data loss caused by unauthorized operations from the source. Senseless and safe execution: Cleaning tasks are performed silently in the background to reduce interference with user front end operations. At the same time, the company's established data compliance and recycle bin retention policies are strictly followed to ensure the absolute security of data assets. Typical business application scenarios Design and R&D projects: In architectural design or scientific research management, working software often automatically generates a large number of backup or cache files (such as .bak or temporary rendering files). By configuring automatic cleaning tasks, you can set up automatic identification and deletion of useless files with specific suffixes on a regular basis to keep core drawings and literature catalogs pure. Public data exchange area: For the \"temporary transfer station\" or \"temporary sharing area\" set up within the enterprise, automatic cleaning tasks based on the time dimension (such as \"automatic cleaning after 7 days of retention\") can be configured to achieve self organization and self purification of public spaces and reduce operation and maintenance management costs. Auto Rename Function Overview In business scenarios involving multi party collaboration and multi frequency data collection, due to differences in operator habits, file naming often lacks unified standards, which brings great trouble to subsequent retrieval, archiving and auditing. The \"Auto Rename\" function allows the system to automatically rename files uploaded to a specified folder according to highly customized preset rules. This mechanism effectively eliminates naming confusion caused by human factors and ensures that enterprise data assets meet the standards as soon as they are stored in the database. Scope of application and permission control Permission driven: The enabling of this function strictly relies on the user's operation permissions. As long as the user has \"upload\" and \"rename\" permissions on the target folder (covering various folders such as personal, department, project or material library), the automatic renaming task can be configured for it. Traceability processing: The rules not only apply to newly uploaded files, users can also choose to apply traceability to historical files that already exist in the target directory and all its subfolders. To ensure system performance and execution stability, the upper limit for batch source traceability renaming is 5,000 files at a time. Core rule engine and configuration dimensions Babel provides a highly flexible visual rule splicing engine. Users can add multiple naming rules and sort the rules freely by dragging and dropping. The configuration interface provides real time changing \"sample file names\" throughout the entire process to help users visually preview the overlay results of renaming rules. The rules engine supports the following multi dimensional named elements: Standard attribute variables: Supports extraction and insertion of system level variables, including file uploader, file person in charge, parent folder name, and upload time. Multimedia metadata (Metadata): For files in specific formats such as images, the system can deeply analyze and extract their underlying metadata as the basis for naming, such as shooting date, camera manufacturer/model, lens model, size, and DPI/DPCM and other parameters. Custom text and continuous numbering: Users can freely insert custom text content. In terms of numbering mechanism, unlike traditional single batch renaming, automatic renaming has state memory (continuity). The system will automatically read the last number in the target list that meets the rules to ensure that files uploaded across batches and time periods can achieve seamless continuation of serial numbers. Users can accurately set the starting value, incremental value and specific digits of the number. Refined pruning and anti conflict mechanism of original names In addition to adding new prefixes/suffixes, the system also supports deep structural cleaning of the original names of files: Name pruning and replacement: You can perform \"replace specific content\" and \"delete specified content\" operations on the original file name. In addition, it also provides a one click \"Delete Characters\" function to accurately remove redundant spaces, numbers, quotation marks, dashes and underlines in file names. Mandatory anti collision protection: If the user chooses to completely delete the \"original file name\" in the rule (that is, the original name is not retained when uploading), in order to avoid the risk of files with the same name overwriting each other, the system will force and automatically add a \"numbering\" rule to the rule chain. Date logical mutual exclusion: When calling date class variables, the user can check \"Replace the date detected in the file name\". To prevent logical conflicts, in a single rename task, the replacement instruction is only allowed to be checked once by a certain time variable (such as \"upload time\" or \"shooting time\"). Global formatted output control After completing the splicing of rule variables, the system supports unified formatting specifications on the output end: Case standardization: Supports one click conversion of assembled file names into uppercase, lowercase, all uppercase or all lowercase to meet the visual specifications of different companies. Uniform word separation: Supports the uniform insertion of standardized separators (such as spaces, underscores or dashes) between each naming rule module to further improve the machine readable and human readable experience of file names. Auto to PDF Function Overview In business links such as cross enterprise collaboration, external data distribution, and project finalization and archiving, the PDF format has become a standard document exchange medium due to its consistency in cross device display and anti tampering properties. BabelBird's \"Auto to PDF\" function aims to establish an automated file format standardization channel. After configuring this task, when a file is added to the selected target directory, the system will silently trigger the conversion engine in the background to automatically convert it into a standard PDF file. This capability greatly eliminates the inefficient labor of manually exporting PDFs one by one, ensuring the standardization of data external output and internal archiving. Execution logic and boundary conditions In order to ensure the efficient operation of the underlying computing resources of the platform and the safe and controllable flow of enterprise data, the following execution logic and boundary restrictions are set for the automatic conversion task: Scope and traceability processing: This task can be overridden downwards and supports checking to apply to files in the target directory and all subfolders. In addition, the rules also support traceability to historical data and can be applied to existing files in the directory. However, to ensure execution stability, the number of files processed in a single traceability process is strictly limited to 5,000. System performance protection mechanism: In order to prevent extremely large source files from occupying computing power for a long time during the conversion process and causing the task queue to be blocked, the system has a built in file size threshold, that is, large files exceeding 30MB will not trigger the automatic conversion mechanism. Automatic release of storage space: For the specific business scenario of \"only keeping the final PDF\", users can check the \"Delete original file after successful conversion\" option in the task configuration interface. After turning on this policy, the system will automatically clean up the original files after confirming that the PDF copy is generated correctly, thereby greatly optimizing the utilization of network disk storage space. Extensive format compatibility matrix Babel's automatic conversion engine has powerful multi format parsing capabilities and supports automatic dumping of mainstream business documents in 32 different industries into PDF. Users can choose to perform conversion on \"all supported files\", or use the drop down menu to accurately select the extensions they need to convert by category. The specific supported format matrix is as follows: Document typesetting: fully compatible with source files generated by mainstream office and publishing software, including doc, docx, ppt, pptx, wps, epub, dpt, indd, rtf, docm and pptm. Pictures and images: Supports rendering and conversion of mainstream bitmaps, digital negatives and medical image formats, covering jpg, bmp, jpeg, jpg2, png, psd, tif, tiff, raw, cr2, dcm and heic. Graphics and engineering drawings: Deeply adapted to vector and CAD drawing conversion in the fields of design and construction engineering. Supported formats include ai, svg, eps, dwg, dwt and dxf. Auto Organize Function Overview With the accumulation of collaborative data in the platform, how to keep the underlying \"any folder synchronization\" architecture and permission control directory clean has become the key to enterprise digital asset management. The \"Automatically organize files\" function allows the system to automatically classify and route files to the corresponding target directory according to preset time periods or content characteristics. This function ensures that massive documents are highly structured during the circulation process and avoids the lag and errors of manual archiving. Flexible triggering mechanism and scope Users can enter the configuration through the \"Task\" option in the right click menu of the folder or the automated task list panel on the left. The configuration covers the following triggering and action rules: Event driven (default): When a file is uploaded or moved to a specified trigger folder, the system responds immediately and starts organizing actions. Period driven: Suitable for centralized data archiving scenarios. The system can uniformly perform file sorting according to a fixed period (for example, set to 23:00 every day). Historical traceability: Rules can be applied to new files and all subfolders, or you can check \"Apply to existing files\" to batch trace the historical inventory data. To ensure the stability of the system, traceability processing shall not exceed 5,000 files at a time. Core intelligent sorting rule engine The system provides three highly customized classification rules to meet data archiving needs in different dimensions: 1. Structured archiving based on time dimension (classified by month/year) The system can automatically create corresponding subfolders (such as \"2025\", \"2025 10\") according to the corresponding year or month when files are added to the network disk and move related files into . The same as when classifying by year or month, the system has the intelligence to create files on demand. If no files are generated within a specific period (such as a certain month), the system will not redundantly create empty folders for that month. 2. Content based intelligent routing (classified by keywords) Based on specific keywords contained in the file name, the system automatically distributes and moves files to preset destination folders. Format recognition: File extensions (such as \"jpg\") can also be configured as keywords to achieve targeted aggregation of specific types of materials. Multi line parallel routing: Users can continuously add multiple routing rules through the \"Add Keyword Classification\" button. It not only supports distributing files containing different keywords to different directories, but also supports pointing multiple keyword tasks to the same target folder. Anti duplication and priority control: Keyword matching is strictly processed in the order set by the task. For example, when the file name is \"123ABC final draft.jpg\", if the first rule in the keyword list is \"123\" and the second rule is \"final draft\", then the file will give priority to matching the rule of \"123\" and execute the move. The system has built in anti repetition detection. Each keyword is only allowed to be entered once. Repeated entry will trigger the \"Please re enter\" error interception. Same name conflict resolution: During the process of moving and organizing files, if a file with the same name is encountered in the target folder, the system will automatically append a number to the file name to ensure that the data is not accidentally overwritten. Create signature (E Sign) Overview of business scenarios and functions In key links such as contract approval, drawing countersigning, and business compliance transfer, digital signatures with anti tampering properties are the core node for opening up the closed loop of online collaboration. Traditional cross system signing is often accompanied by cumbersome file downloads and format conversions. The \"Create Signature\" function launched by Babel allows users to stamp and sign documents directly in the cloud disk workflow. The engine supports multiple mainstream file types to directly load printed signatures, and supports one click export of signed files to standard PDF format, ensuring the security, compliance and non tamperability of digital assets from the source. Signature asset library and personalized configuration The system provides users with a highly integrated digital signature management console to ensure the unified precipitation and rapid recall of electronic signature assets: Multi signature collection: In the \"Signature Settings\" module, users can call the terminal to \"add a handwritten signature\" online, or directly \"upload signature image files\" (such as PNG materials with transparent channels) to meet different levels of signing compliance requirements. Corporate seal management: In the \"Stamp Settings\" module, corporate users can upload business specific electronic official seals or compliance seal images as needed. Default priority status: For users who have multiple signature assets, the system supports one click \"setting a specific signature or stamp as currently used\" (default signature). In the subsequent document preview and circulation interface, the system will give priority to calling this default signature, which greatly improves the signing efficiency in high frequency approval scenarios. Intelligent adaptive interaction and immersive guidance system In order to take into account the display limits of different hardware terminals and lower the user's learning threshold, the signature configuration center adopts a multi breakpoint intelligent responsive interface architecture and deeply embeds multi language operation guides: Widescreen workstation mode (window width ≥ 1120px): When the user operates on a desktop widescreen device, the system not only retains the standard signature configuration panel on the left, but also automatically expands an independent video teaching area on the right. This area will automatically load and play the tutorial on how to use the signature in a loop without any sense (it will replay after a 3 second pause), providing users with an immersive experience of \"learning and matching at the same time.\" Compact focus mode (window width < 1100px): When on a narrow screen or mobile window, the system will intelligently collapse the video playback area on the right to maximize the visual focus of the core signature setting area. At the same time, the system provides a \"How to use signature?\" entry at the bottom of the interface, and users can click to trigger a full screen tutorial playback. International bilingual support: Considering the collaboration needs of multinational enterprises, the system has a built in localized teaching video library. In addition to the exclusive Chinese tutorials played in the Chinese language environment, all other multi language versions match and play standard English tutorials by default to ensure barrier free implementation for global business teams. Batch Create Folders Function Overview and Business Value In business scenarios involving multi project concurrency or enterprise department structure adjustment, manually establishing complex standard directory trees one by one not only consumes a lot of operation time, but also easily leads to directory hierarchy confusion or non standard naming due to human oversight. The \"Batch Creation Folder\" function provided by Babel allows users to directly drive the generation of cloud directories through external structured data (such as Excel, CSV, TXT text). This function can instantly transform a standardized business directory template into a network disk folder array that can be implemented, greatly improving the efficiency of initial file creation during the startup phase of large scale projects. Large scale generation of standard directory arrays This module has powerful data analysis capabilities and manual fault tolerant intervention mechanism: High concurrency support: The system supports importing files in xls, xlsx, csv or txt format and quickly reading directory lists according to newline character rules. The upper limit of a single batch processing task is up to 5,000 lines, which meets the generation needs of most enterprise level data structures. Visual pre review and dynamic intervention: Before the batch creation is officially executed, the system will complete the data analysis and visually render the folder list and hierarchical relationship to be generated in the interface. In this preview session, users can directly perform instant modification actions such as \"create subfolder\", \"rename\" or \"delete\" on a specific preset directory through the right mouse button or floating menu. This \"review before building\" mechanism ensures that the final directory tree is absolutely aligned with business needs. \"One click deployment\" of project level folders and permissions When the target path is set to the root directory of the department folder or personal folder, the system supports the creation of a more advanced \"Project Folder\" . This model is deeply integrated with the underlying permission management system of BabelBird to realize the synchronization of directory construction and member permission configuration: Exclusive standard template: To batch generate project folders, you need to download and use the system's exclusive template to import data. If the uploaded non standard file does not meet the parsing format, the system will strictly intercept it and prompt you to re upload it. Project role and permission preset: The template not only standardizes the \"project folder name\", but also supports the direct association of the account system to preset \"project leader\" and \"project member\". Assignment of person in charge: The filled in person in charge ID (supports mobile phone number, email address or specific work ID format) must be a registered company member; if this field is left blank or the filled in identity cannot be verified, the system will follow the security principle and set the operator of the currently created task as the project leader by default. Automatic member invitation and empowerment: Users can batch enter multiple project members in the template by separating them with commas. After the project directory is generated, the system will automatically send invitation notifications to these members and grant them basic \"upload and download\" default permissions, completely eliminating the cumbersome one by one authorization operations after file creation. Real time status monitoring and intelligent fault tolerance mechanism When executing large scale creation tasks, the system background will process it robustly in the form of a queue, and provide a full range of process monitoring and exception repair closed loops on the front end: Global progress tracking: During the creation process, the list node will update its execution status in real time (smooth transition from the circle animation representing ongoing execution to the confirmation check state representing success). The global status of the task will also clearly flow from \"Creating\" to \"Complete\". Accurate exception attribution and retry: After all tasks are executed, a clear summary of the results will be output at the top of the system (such as \"A total of XXX folders were created, and X failed\"). Users can check the \"Failed to Create File List\" with one click. The system will accurately classify the failure reasons as system level conflicts such as \"the file name contains characters that are not allowed\" or \"a folder with the same name already exists\". For these abnormal entries, users can not only find out the cause, but also click the green \"Retry\" button directly on the interface to trigger secondary creation, which greatly reduces the resistance to batch operation and maintenance. Document control project The document control project is an industry application independent module of BabelBird (needs to be purchased separately). The BabelBird document control project solves the problem of process management (DCC) and automation of document control standards in the engineering design industry. It improves the work efficiency of a large number of document control personnel and also reduces the possibility of human errors. Scope of use Industries or businesses that need to strictly manage every document sent. Every document sent to a customer is sent by a specific person (document control personnel). Every time a document is sent, there is a sending document that can be checked, and the sending content can be clearly managed. Through the sending order number, you can check the specific information and files of each file sent to the recipient. At the same time, you can query whether the recipient has received the message and whether the sent content has been rejected. And the delivery order can be used as a voucher. Problems that need to be solved At present, the document control process of many enterprises is basically manual, and the files are stored in the EDMS system or locally on the computer of the document control personnel. Rely on folder classification to manage documents. Each time a file is sent, a folder is manually created and the folder is named according to the file name specification. After the file is sent by email, the sent file is placed in the folder and the TRANSMITTAL (file sending order) of this sending is attached. Each send will generate a folder and corresponding TRANSMITTAL. The manual operation of these tasks is quite cumbersome. In addition to sorting out files, you also need to manually fill in the document delivery form each time, manually write the delivery order number according to the rules, and manually check it in the future, which is extremely inefficient. BabelBird Solution New document control project types can be created. This means that different projects can set different TRANSMITTAL (sending order) rules to generate different sending orders and sending order numbers. Different projects can also manage different recipients (recipient companies) You can set the file recipient for each project and manage the file recipients in a unified manner. Documents in document control projects support the sending function, and the sending function supports multiple selections. After selecting a file or folder to send, the recipient can receive the download link and TRANSMITTAL of the sent file via email. And the file downloaded through the download link is the version when sent. Each file sent is the current version of the file. File upgrade will form a new version number, which will be displayed on the delivery note. After the file is sent, the TRANSMITTAL and TRANSMITTAL NO. will be automatically generated according to the preset rules. You can manage and query the TRANSMITTAL (delivery order), and export the delivery order to PDF. Instructions for use of the BabelBird Cultural Control Project: Basic introduction The BabelBird document control management system is based on the BabelBird enterprise private cloud version and adds a document control management module to realize the automation of document control work. The way of document control management is to establish a \"document control project\". Document control projects are special projects customized for document control needs and are managed on a project by project basis. Establish document control projects After logging in to the system, click \"New\" \"New Project\" in the department where you want to create a document control project Projects can only be created in the root directory (enterprise files) or department root directory Example: Establish a document control project under the document control department of HQSM Click New Project, and the project type selection interface will appear. Select \"Create Document Control Management Project\" At this time, the project initialization selection interface appears. Fill in the initialization information according to the requirements of the project Each item is introduced as follows: Project leader Manage, transfer projects, modify project permissions and basic information. Cannot be empty. TRANSMITTAL can be deleted Project Secretary The project cannot be transferred, other people in charge of the same project can have multiple people, and can be empty. TRANSMITTAL can be deleted Document control staff Can send files to recipients. Other permissions are configurable, can be for multiple people, and can be empty. After selecting a person, click the permission selection drop down box on the right to modify member permissions in batches (as shown in the figure). other members There is no option to send files. Others are the same as ordinary members of ordinary projects. The permissions are configurable and can be empty. Version number rules As shown in the figure, if the prefix is HQSM, the first version of the file is HQSM A, the second version is HQSM B and so on. Basic information The filled in basic information will be displayed in the TRANSMITTA header. As shown in the picture: The red circle is the basic information to be filled in. Recipient information The recipient information determines the options when sending and the TRANSMITTA number of the sent file. The recipient's name refers to the recipient's name in the system. Generally, the recipient's company abbreviation is filled in, such as MCC. You can add multiple mailboxes. After adding multiple mailboxes, you can send files and TRANSMITTA to multiple mailbox addresses in one send. ATTN can be entered at will and will also be displayed on TRANSMITTA The waybill number rule is actually the automatic generation rule of the TRANSMITTA number. Different recipients can generate different waybill numbers. Therefore, different waybill number rules need to be set at each recipient. The rules customization interface is as follows: The 3 columns are the three components of the TRANSMITTAL number. If the required TRANSMITTA number requires more codes to form, you can also click the + sign to add more columns. Example: Select to enter text in the first column, a text input box will pop up, enter \"HQSM \" Select the encoding rule in the second column as 1 2 3 numerical sequence Select text input in the third column and enter \" 2020\" Click the plus sign to add a column and select the alphabetical order of a b c The TRANSMITTAL number generated when sending for the first time is: HQSM 1 2020a The TRANSMITTAL number generated for the second transmission is: HQSM 2 2020b After selecting letters as numbers for more than 26 numbers, the next version of the z number automatically becomes a1 If the project has multiple recipients, you can also click to add them. (After the project is established, you can also add or delete recipients in the project management interface. After completing these fillings, click \"Add Project\" to complete the new project. You can see the newly created document control project in the file list of the created project path, click to enter Document control management projects are different from ordinary projects. A button for document control management is added to the top bar of the project homepage. Among them, the \"Sending Order List\" can query all TRANSMITTA issued by the project, and the management project can manage the project. Upload files Click on the newly created document control project to enter the project page. Just drag and drop the files you want to upload into the project to upload the files. Of course, you can also use the synchronization function to upload and download just like using ordinary folders. Send files Select the file to be sent (multiple selections are supported), then right click and select \"Send File\" to display the file sending interface. The maximum number of files sent at a time is 2,000 (including folders). If the project requires all files to be sent, it is recommended to send them in a compressed package. The recipient can drop down to select the recipient and ATTN filled in during project initialization. You can fill in any other email address for CC, or you can leave it blank. The selected submission file type will also be displayed in the generated TRANSMITTA The file list lists the files to be sent this time. The file name that the system wants to send TRANSMITTAL consists of file number + description. For example, if a file is named 1000+drawing.pdf, the file number displayed in TRANSMITTAL when sending is \"1000\" and the description is \"drawing\". If there is no + division in the file name of the sent file, the file number will display the file name. If the file name sent is \"+drawing.jpg\", the file number will not be displayed, and the description will be displayed as \"drawing\". Description can be changed midway. The postscript will be displayed in the email received by the recipient and will not be displayed in TRANSMITTAL. After filling in, click \"Send File\" and the system will automatically generate TRANSMITTAL and attach it as a link in the email and send it to the customer. Generate TRANSMITTAL After successful sending, the system will pop up a prompt Click View to view the TRANSMITTAL automatically generated for this send Click Export to PDF to save the TRANSMITTAL as a PDF file You can also view all TRANSMITTAL sent in the project in the TRANSMITTAL list The TRANSMITTAL received by the recipient in the mailbox is consistent with the TRANSMITTAL. View TRANSMITTAL Click on TRANSMITTAL list on the project homepage Open the list to see and query all dispatch orders for this project. Click on the delivery number to view details and download the PDF file of TRANSMITTAL Acceptance means that the recipient has not opened the sent email. If the other party opens the email and accesses TRANSMITTAL, the receiving status will change to received. View sending records Right click on any file to view the sending record of the file and its corresponding TRANSMITTAL User interface user interface design Babel bird interface design concept There are many functions integrated into the enterprise network disk. How to reasonably allocate function entrances to make it more convenient for users to actually use it? This is an issue that needs to be considered during interface design and interaction. Currently, there are two conflicting design concepts. Interface design concept Advantages and disadvantages Hide very commonly used functions to ensure a simple interface, reduce learning difficulty, make it easy to use, and provide a friendly first time user experience. (Representative: 2C products such as Weiyun and Tencent Documents) The learning curve is gentle at first and steep at the end. Users have a good experience during the first trial, but it is inconvenient for long term use The function entrance is explicit and the interface is complex, but the required functions can be found quickly. The interface is heavy, the learning cost is slightly high, and the first time user experience is not friendly. (Represents: office, CAD and other professional software) The learning curve is steep at the beginning and slow at the end. The user experience is complicated for the first time, but it is actually convenient for long term use. Not good for marketing. Considering that enterprise network disk is a professional product for long term use by enterprises, although the steep learning curve in the early stage is not conducive to marketing (the abandonment rate increases when users simply try it out), it is friendly to users who choose BabelBird for long term use. After getting familiar with it, it can be used better and more organized. As a productivity tool, the convenience of daily use and reducing the probability of errors are more important. Therefore, BabelBird Enterprise Drive chose the second design concept: As a professional product for enterprise scenarios, the complexity of getting started can be appropriately increased for the convenience of long term daily use. Interface design principles User friendliness: On the premise of ensuring that the use of functions is given priority, user friendliness is emphasized to ensure that users can easily use the enterprise network disk. Consistency: Maintain a consistent interface design to provide a consistent user experience. Simplicity: Use a simple design to reduce redundancy and complexity so that users can quickly understand the interface. Availability: Ensure that the functional modules are easy for users to find and have corresponding guidance, and can be used directly within 3 steps. user interface elements Web version (web) It adopts the layout of left menu, right file list, and top functional partition. It is convenient for users to focus on the file list. The left menu can be collapsed to display more file list content, providing an immersive experience. In order to better manage files in a tree view, you can also open a tree view to manage files like Windows Explorer. If there are a large number of image files in the folder, the waterfall preview mode can be automatically turned on to facilitate user viewing. The left menu (shortcut) can be customized by users, making it easier for users to customize shortcut entries according to their daily usage habits. All functional operations of files/folders are concentrated on the right click and are easy to find. Commonly used functions are displayed on the file list. At the same time, there are corresponding buttons in the file list bar to prevent user operations from being affected by the failure of the right mouse button. Client (windows, mac, Kirin) The client uses Electron and C++ for cross platform development, which ensures style consistency and operation consistency. And there are also optimizations for each platform. The client also includes synchronization module, upload and download list and virtual mapping disk (cloud bridge) module. The main operation interface continues the style and layout of the web version, but the layout has been improved based on the usage habits of local software and the unique modules of the client. The top functional partitions are concentrated in the left column to make the top display more concise. The left column adds two client specific function buttons and entrances: transmission and synchronization. The file transfer module manages the synchronization process and upload and download tasks. Shortcuts for synchronizing, uploading, and sending files are integrated on the right click menu of Windows and MacOS system files, allowing users to quickly create synchronized and uploaded files (folders). A virtual mapped disk is integrated on Windows and MacOS, allowing users to access cloud files just like a local hard drive. Responsive design Responsive design principles Multi device compatibility: The user interface of BabelBird Enterprise Drive is designed to obtain the best experience on various devices, including desktops, mobile devices and tablets, to ensure that users can have a good experience on various devices anytime, anywhere. Picture: BabelBird has been cross platform since its birth. Adaptive layout User interface elements automatically adjust to screen size and orientation to ensure content visibility and usability. Touch friendliness: Optimize touch interactions on mobile devices, including gesture controls, swiping, and zooming. Image and media optimization: Preloading, image transcoding to generate thumbnails, and media compression techniques are used to reduce page load times and bandwidth usage. Mobile support Web version mobile device optimization Mobile interface design: The BabelBird web version has an H5 page designed for mobile devices, as well as a mobile version of the promotional website and mobile version download interface for sharing links, and supports common touch gestures such as sliding, zooming and clicking. Figure: Mobile device accessing Babel H5 page Mobile APP: In order to obtain a better user experience, BabelBird has developed a mobile specific APP that supports Android and iOS systems. In order to ensure good performance, BabelBird APP is developed as a native application. The interaction, interface, and functional modules of the APP have all been redesigned to be suitable for access on mobile devices. Figure: Mobile interface Tablet optimization The Babel iOS APP has a redesigned interface for the iPad to make it more suitable for working on a large screen. Performance optimization Load balancing strategy Separation of authentication and services Separate authentication: In order to improve the performance and security of the system, BabelBird Enterprise Drive adopts the strategy of separating authentication and core services. This means that the user's authentication request will be routed to a dedicated authentication server, and core service requests such as uploading, downloading, and query browsing will be routed to the corresponding core service server. Request routing: We use a load balancer to route requests to different servers based on the request type. This ensures that the authentication server does not become a performance bottleneck for core services and allows us to scale authentication and core services independently as needed. Multiple server deployments for the same type of requests Multi server support: BabelBird Enterprise Drive allows the same type of requests to be deployed on multiple servers to improve performance and availability. This multi server support strategy ensures that even if one server fails, the other servers can still handle requests. Requests are evenly distributed: We use a load balancing algorithm to evenly distribute the same type of requests across multiple servers to avoid server overload and provide faster response times. load balancer Load balancer configuration: We use professional load balancers to distribute and route requests. The load balancer sends requests to the appropriate server based on predetermined rules. Monitoring and automatic failover: The load balancer is equipped with monitoring features that can detect the health status of the server. If a server fails, the load balancer automatically routes requests to other available servers to ensure system continuity. Advantages Performance improvements: Load balancing strategies improve system performance, allowing requests to be processed in parallel on multiple servers, reducing the load on a single server. High availability: The deployment of multiple servers and automatic failover ensure the high availability of the system, and services can still be provided even in the event of a failure. Scalability: Load balancing strategies allow more servers to be added as needed to accommodate growing users and requests. Cache management File buffer management File buffer settings: In order to optimize performance and reduce the burden on CPU resources, BabelBird Enterprise Drive implements file buffer management. The decrypted files will be temporarily stored in the buffer to reduce repeated decryption operations. LRU strategy: We adopt the least recently used (LRU) policy to manage the file buffer. This means that the least frequently used files are cached, thus maintaining efficient buffer utilization. File authentication buffer management File authentication buffer: Authentication checking for file access permissions is complex and time consuming. Comprehensive authentication testing is required based on multiple factors such as the department, project, sharing, and confidentiality level of the file. In order to improve performance, we implemented file authentication buffering to cache the authentication results. Expiration elimination mechanism: The file authentication buffer adopts an expiration elimination mechanism. Each cache entry has a predetermined expiration time, and once this time is exceeded, the cache will be automatically evicted. This ensures freshness of cached data and reduces memory usage. Advantages Performance optimization: Cache management reduces the repeated execution of decryption operations and authentication checks, thereby improving system response speed and performance. Resource saving: By using the LRU policy and expiration mechanism, we effectively manage memory resources and avoid memory leaks and over occupancy problems. Quick response to complex authentication: The file authentication buffer ensures fast response to complex authentication test results and reduces the pressure on the authentication service. Data compression and transmission optimization File chunking technology File storage in chunks: In order to optimize the transmission and storage of files, BabelBird Enterprise Drive adopts file blocking technology. Large files are broken into smaller chunks and stored separately on the server. This helps improve file transfer efficiency and supports breakpoint resume downloads. Parallel block request: Chunked file storage allows the front end to make requests for multiple chunks in parallel when downloading a file. Once all chunks have been downloaded, the front end assembles them into a complete file, significantly increasing download speeds. File storage deduplication technology based on hash code File deduplication: BabelBird Enterprise Drive uses hash code based file storage deduplication technology. When a user uploads a file, the file's hash code is calculated and compared with the hash code of an existing file. If the same hash code is found, the system will keep only one copy of the file, thus saving storage space. Save storage space: File deduplication technology effectively reduces storage redundancy, especially files that are frequently shared and transferred in enterprises, thereby reducing storage costs. Advantages Transmission efficiency: File chunking technology and parallel block requests speed up file transfers, especially for large files and high bandwidth connections. Storage savings: File storage deduplication technology based on hash codes reduces storage requirements and maintenance costs. User experience: Fast file transfer and storage space savings improve user experience, providing more efficient file management and sharing. Asynchronous task processing Background asynchronous processing Task time consuming processing: In order to handle tasks issued by the front desk that may be time consuming or even cause HTTP requests to time out, BabelBird Enterprise Drive adopts a background asynchronous processing strategy. These tasks do not block the main HTTP request response, but are executed asynchronously in the background. Improve response speed: Background asynchronous processing ensures that the response speed of foreground requests is not affected by time consuming tasks, improving user experience. Configurable management of asynchronous tasks Task queue: In order to prevent server resource constraints, we have configured and managed asynchronous tasks. Asynchronous tasks can be configured as one or more processing queues, which can execute tasks independently. Task queues can be configured and managed based on task type and priority. Message queue: Another way to manage asynchronous tasks is to use message queues. BabelBird Enterprise Drive can be configured to use message queues to store and schedule asynchronous tasks. This mechanism ensures orderly execution and controllability of tasks. Message processing mechanism: Asynchronous tasks are controlled and executed through message processing mechanisms. After the task is added to the queue or message queue, it is processed and executed by a specialized processor. Advantages Responsiveness: Background asynchronous processing improves the system's response speed and avoids long waits. Resource control: Configurable management of asynchronous tasks allows effective control of server resources to prevent resource exhaustion. Scalability: The message queue and message processing mechanism provide system extensibility, and new asynchronous task types can be easily added. Scalability Horizontal expansion Cluster deployment: BabelBird Enterprise Drive Business Server adopts a cluster deployment model, which allows us to easily expand the capacity and performance of the system. Multiple servers in a cluster work together to share load and provide high availability. This model allows us to add new nodes as needed to meet growing user and data needs. Private cloud deployment customers can also expand performance by adding virtual machines or physical servers to meet high concurrency requirements as their users grow. For more information about the scalability of Babel Cluster deployment, see the Distributed Deployment chapter. Object storage system: Babel's storage system uses object storage technology, which is very suitable for large scale data storage and horizontal expansion. Object storage systems are highly scalable and can accommodate large amounts of data and automatically expand storage capacity by adding storage nodes when needed. For more information about the scalability of Babel object storage, see the self built object storage chapter. Load balancing: We have implemented a load balancing strategy to ensure that user requests are evenly distributed to various nodes in the cluster to avoid single points of failure and provide faster response times. Auto scaling (public cloud): Thanks to Alibaba Cloud ECS elastic computing service, our system is configured with an automatic scaling mechanism to automatically increase or decrease server nodes according to load conditions. This automatic scaling ensures system stability and performance. vertical expansion Hardware upgrade: In addition to horizontal expansion, for private cloud users we can also perform vertical expansion, that is, upgrading server hardware to increase the performance and capacity of a single server. This is an effective solution in situations where more computing power or memory is required. Database optimization: We can also optimize the database system to improve performance by adjusting configurations, using higher performance hardware, or upgrading the database management system. These improvements provide better query performance and data processing capabilities. Cache: We use caching technology to speed up data access and reduce the load on databases and storage systems. Caching supports memory caching, CDN caching and other methods, and you can choose the most suitable caching strategy according to your needs. Containerization and SOA service architecture Docker containerization Docker deployment: We use Docker containerization technology to deploy various components and modules of BabelBird Enterprise Drive. This approach allows us to package each major module as an independent Docker container, providing greater flexibility and scalability. Container orchestration: We use container orchestration tools to manage and coordinate individual containers to ensure they work together to achieve high availability and resiliency. Container image management: BabelBird Enterprise Drive uses the container image warehouse to store and manage Docker images so that new container instances can be deployed at any time. SOA service architecture Service split: We split the main functional modules of BabelBird Enterprise Drive into independent services, and each service is responsible for performing specific tasks or functions. This split improves the maintainability and scalability of the system. API communication: Services communicate through APIs, using compatible RESTful API protocols. This loosely coupled communication method allows services to be developed, tested, and deployed independently. Standalone deployment: Each service can be deployed and scaled independently, which means we can horizontally scale specific services based on demand without affecting the operation of other services. Advantages of containerization and SOA service architecture High availability: Containerization and SOA service architecture provide high availability, allowing us to quickly restore services in the event of a failure. Flexibility: Containerization allows us to easily deploy, upgrade and maintain each container, while SOA service architecture provides flexible modular development and deployment options. Resource utilization: We can allocate resources as needed to avoid resource waste and achieve higher resource utilization. Fast delivery: Containerization and SOA service architecture enable new features and improvements to be delivered to users faster. Private cloud users can also enjoy fast update and upgrade services that are comparable to public cloud systems. Challenges of containerization and SOA service architecture Complexity: Managing multiple containers and services can introduce a level of complexity that requires appropriate management tools and strategies. Monitoring and logging: We use monitoring and logging tools to ensure the normal operation of containers and services, and to identify and solve problems in a timely manner. We are equipped with an automatic restart mechanism. If there is a problem with the service, the problematic module will be automatically restarted to ensure the smooth flow of the overall service. Private deployment The BabelBird public cloud network disk system needs to provide continuous and uninterrupted services to 600,000 users including free users at the same time, block various attacks on the public network, and continuously improve system efficiency to reduce the high cost of public cloud servers. As many as 10 years of experience in uninterrupted public cloud services have made the Babel system time tested. The Babel private cloud system is developed on the basis of the Babel public cloud system. It inherits all the functions and features of the public cloud Babel, and is updated synchronously with the public cloud Babel, providing you with high stability and high availability that other private network disks cannot match. Deployment plan In response to the different IT system construction needs of different enterprises, the Babel privatization system supports a variety of flexible deployment methods and deployment requirements. Whether it is single server, multi server, cluster, hyper converged system, distributed system, third party cloud platform or even Docker deployment, we support it. Our deployment team can work with you to develop a deployment plan based on your needs. At the same time, because private cloud only serves a single enterprise, we can provide optional customization settings that far exceed those of public cloud systems. From interface operations to processes to permissions, everything can be adjusted according to your needs. Recommended server configuration and performance requirements Server type and function: The hardware system required by BabelBird Enterprise Drive consists of two parts: business servers and storage servers. Business servers can be divided into 4 types. These 4 types of services can be deployed in one physical machine or virtual machine according to needs, or can be deployed dispersedly in four or more servers. Therefore, the minimum unit for deploying the Babel system is two physical servers or two virtual machines (one for business and one for storage) Service name Purpose Operating system Main business server web services, load balancing, main business function implementation Linux Database Server Database Service Linux Search server Provides file full text search and advanced search functions Linux Transcoding server Transcode and add watermarks to files that require transcoding preview windows 2012, Linux Storage server Provides file storage Linux In extreme cases, if the hard disk mounted on the server is used as storage space, Babel also supports deploying all services and storage in a physical machine or virtual machine (all in one machine mode). However, considering performance and disaster recovery or future upgrade and expansion issues, such a deployment method is not recommended. The best deployment method we recommend is a small cluster deployment of 4 servers (virtual machines). The main business services and database services are placed on one server, the search server and transcoding server are independent, and then a storage server is added. If the storage space requirement is less than 10TB, a storage server is not required. You can directly mount a hard disk or NFS disk for storage. BabelBird also supports access to third party storage. In theory, as long as the third party storage system supports the NFS or S3 protocol, it can be connected to BabelBird as a storage service. Most storage systems support both protocols. Each server must ensure smooth communication between each other. If the intranet has higher security requirements, please refer to 9.1.2 Ports that need to be opened Minimum performance configuration: The lowest performance configuration of BabelBird can support normal use by about 100 users and manage less than 10TB of data. cpu memory system disk storage disk network operating system 8 core CPU (reference benchmark E5 2609) 32G ECC memory 500G Below 10TB Gigabit Linux Recommended performance configuration examples: The recommended performance configuration of BabelBird can support normal use by 1000 2000 users and manage documents up to 1PB. Babel supports multiple deployment methods, and this instance is the standard deployment method. Use virtual machines to deploy business servers to connect to independent single or multiple object storage servers. Business servers and storage servers are managed separately. Business server: It is recommended that business servers be deployed using virtual machines Number Server type Configuration requirements Operating system Server purpose 1 Virtual machine 8 core CPU 64G memory 500G SSD system disk CentOS8 or openeuler22 Main business server/database 2 Virtual machine 8 core CPU 32G memory 500G SSD system disk CentOS8 or openeuler22 Search server 3 Virtual machine 8 core CPU 16G memory 200G SSD system disk windows 2012 R2 transcoding server The performance of the 8 core CPU should be close to that of the Zhiqiang 4410 BabelBird Enterprise Drive is deployed using Docker. In theory, it can be deployed as long as it is a Linux operating system. CentOS or open Euler is recommended. If there are no ready made virtual machine resources, you need to purchase a new business server. The business server hardware configuration requirements are as follows: Number Server type Configuration requirements Operating system Server purpose 1 Business server Xeon Silver 4210 2 20 core CPU 64G memory 2TB SSD hard drive Linux Main business server It is best to purchase VM for business servers and use virtualization for management. Storage server (object storage): Babel supports building an object storage system on a general purpose server. If the storage space is expected to be less than 100TB, it is recommended to use a single server to build the object storage system. A single object storage can use disks for data verification redundancy, and can be horizontally expanded by adding one storage server at a time. (The expansion operation can be done without stopping the server) It is recommended to use an independent physical machine for the object storage server, and the recommended configuration is as follows: Server type Configuration requirements Operating system Server purpose Notes Storage server If storage density and future expansion investment are considered, a 12T hard drive can be used. Linux Object Storage Server It is recommended to add a server with the same disk capacity for future expansion. If the required storage space is greater than 300TB, multiple servers are required to build a distributed object storage system. BabelBird also supports building distributed object storage systems for customers. To learn about distributed object storage, please refer to the \"Self Built Object Storage\" chapter. Need to open the port For the security of the server system, we need to open only specific ports. The following are the ports that need to be opened: Ports open to the outside world (ports required for external network access): Port number Port purpose Protocol Open host 80 Network disk main business web external access port, not encrypted http main business server 443 Network disk main business web external access port, encrypted https Main business server 3060 Network disk main business node external access port, not encrypted TCP Main business server 3080 Network disk main business node external access port, encryption TCP Main business server Open ports are required between servers (open ports are required for internal server communication): Generally, during actual deployment, only external network ports (external) will be restricted, and internal ports between servers will not be restricted. However, some users who deploy across networks and computer rooms will also need to limit internal ports. Host Port number Port purpose Protocol Target network segment Business server 6379 redis access port for windows transcoding and search server TCP transcoding server and search server Business server 8080 Used by windows transcoding server to access network disk business server TCP Transcoding server and search server Business server 3306 Database port, used by the search server to access the database TCP Transcoding server and search server Business server 9000 Docker cluster deployment, internal visual interface port TCP Transcoding server and search server Business server 111 portmap port TCP+UDP Transcoding server and search server Business server 2049 TCP+UDP TCP+UDP Transcoding server and search server Business server 35000 mountd port TCP+UDP Transcoding server and search server Business Server 2376 docker REST API port for TLS encryption TCP Native Business server 2377 TCP port used for communication related to docker cluster management TCP+UDP Native Business server 7946 TCP and UDP ports, used for communication between docker swarm nodes TCP+UDP Local machine Business server 4789 docker overlay network default port TCP+UDP Local machine Search server 9200 elastic port, used by the main business server TCP business server Search server 5601 Kibana port, internal visual elastic interface access port TCP Business server Search server 9998 tika port, extract document text server port TCP Business server Search server 9000 Docker cluster deployment, internal visual interface port TCP Transcoding server and search server Search Server 2376 docker REST API port for TLS encryption TCP Native Search server 2377 TCP port used for communication related to docker cluster management TCP Native Search server 7946 TCP and UDP ports, used for communication between docker swarm nodes TCP+UDP Local machine Search server 4789 docker overlay network default port TCP+UDP Native Transcoding server Transcoding server Can access the business server Can access the business server Can access the business server Ports that need to be opened during deployment: Port number Port purpose Open server Destination IP address 22 SSH port number, used for SSH access All servers Springboard machine for deployment 443 Obtain authorization All servers 47.96.234.200 443 Get installation source All servers 120.27.245.68 443 Docker installation source All servers 13.35.121.100 POC deployment POC deployment is suitable for users to conduct POC testing in the production environment before selection. POC deployment requirements: Basic POC deployment can test software functions, concurrency, API interfaces, security, and trial in the production environment. It is recommended to use standard deployment as POC test. If you need object storage, data transfer in different density areas, and high availability POC, you need to add corresponding servers and network segments. Environmental preparation It is recommended to use a virtual machine for deployment: BabelBird's privatized enterprise network disk is deployed using Docker. In theory, it can be deployed as long as it is a Linux operating system. It is recommended to use CentOS or open Euler. After preparing the virtual machine as required, contact us to make an appointment and you can start POC deployment. Number Server type Configuration requirements Operating system Server purpose Remarks 1 Virtual machine 8 core CPU 32G memory 500G system disk +500G storage disk CentOS8 or openeuler22 and above Main business server 2 Virtual machine 8 core CPU 16G memory 500G system disk CentOS8 or openeuler22 and above Search server 3 Virtual machine 8 core CPU 8G memory 200G system disk windows 2012 R2 transcoding server CAD, office transcoding Win server is for better office file preview effect. BabelBird also supports pure Linux environment deployment Other requirements for POC deployment are as follows: Number Project Requirements Remarks 1 Remote access You can remotely access the server for deployment You can use a bastion machine or springboard machine or Sunflower or VPN, and you can remotely access the server for deployment. 2 External network connection The server needs to be able to connect to the external network, pull the installation package, and obtain authorization The external network address that needs to be connected: software.babel.cc docker.babel.cc The authorization period for POC deployment is 30 days, and the number of authorized accounts is 100. initialization After the deployment is completed, the Babel team will help users initialize the system and initialize the system according to user needs. Including but not limited to: Initialize the administrator account. (You need to prepare an email address as a super administrator account) Initialize the notification sending email address. (The user needs to prepare an email address that can provide password and SMTP server address as the system default outbox) Initialize department structure. (Connect with AD or import department) Initialize basic configuration. logo, company name, various configuration items. training BabelBird is a professional enterprise level application and requires certain training to help customers implement it. After POC, it is recommended to contact our sales staff for usage training. Training is divided into 3 categories: Administrator training (training administrators on configuration, use, and realization of required functions. It takes 1 2 hours) Department manager training. (Training department managers on daily management methods such as authority allocation, member addition and reduction, etc. It takes 1 hour) User training. (Training of using members. It takes 1 hour) Start POC trial After the training is completed, the formal POC trial can be started. Any questions encountered during use can be directly asked in the relevant group, and the BabelBird team will respond and answer within 2 hours. The POC system is valid for 30 days. If you need to extend it, please contact our sales staff. Introduction to common deployment methods of BabelBird BabelBird can support multiple deployment methods on demand. Here we introduce the commonly used deployment methods of BabelBird. Deployed on public platforms such as Alibaba Cloud, Tencent Cloud, Huawei Cloud, etc.: Babel supports deployment on virtual machines (ECS) and object storage (OSS, OBS...) of public cloud service providers such as Alibaba Cloud, Tencent Cloud, Baidu Cloud, Huawei Cloud, and Tianyi Cloud, and provides services to users on the Internet. The difference compared with purely private deployment is as follows: Advantages and Disadvantages/Deployment Method Image Service Video Service Public Network Access Stability Hardware Cost Using Alibaba Cloud storage and Alibaba Cloud servers You can use the picture service provided by Alibaba Cloud You can use Alibaba Cloud's video transcoding service, but it requires an additional fee (expensive) It can be accessed on the public network. The speed of user access depends on the user's own bandwidth and the purchased Alibaba Cloud bandwidth. The system is very stable, simple to deploy and easy to manage. You need to pay Alibaba Cloud's storage and server fees, which can be paid monthly or annually. Users can be responsible for the maintenance of the server themselves, or they can entrust us to perform maintenance and upgrades. Storage and servers are built on your own intranet Use self built image processing services (requires customers to provide high performance servers) Use self built transcoding services (requires customers to provide high performance servers). If the user does not have this requirement, you can ignore it. If there is no external network exit, users cannot access the external network. But intranet access is very fast. Stable, customized development for modules such as storage systems. The security of data is the responsibility of the user. Requires independent host and storage systems. The server can be purchased by the user or by us. Server maintenance is the responsibility of the user, and we can provide corresponding software upgrade services. Public cloud deployment (1000+ users) requirements: Number Server type Configuration requirements Operating system Server purpose 1 ECS 16 core CPU 32G memory 500G SSD system disk CentOS8 or openeuler22 Main business server 2 ECS 8 core CPU 16G memory 500G SSD system disk CentOS8 or openeuler22 Database server 3 ECS 8 core CPU 16G memory 500G SSD system disk CentOS8 or openeuler22 Search server 4 Storage Object storage system. Such as Alibaba Cloud OSS, Huawei Cloud OBS Object Storage System. Such as Alibaba Cloud OSS, Huawei Cloud OBS Object Storage System. Such as Alibaba Cloud OSS, Huawei Cloud OBS The main advantages of deploying on a public cloud platform are that it does not require dedicated maintenance, top level disaster recovery can be achieved without purchasing hardware, access to the Internet is fast, and servers and data are managed by oneself. The main disadvantages of deploying on a public cloud platform are: data is not localized, and annual server rental fees and corresponding bandwidth storage costs need to be paid. Self purchased servers (2 physical machines) for deployment: If you want to deploy a purely private BabelBird in your own computer room and do not have spare virtual machine resources, you need to purchase hardware deployment. The requirements are as follows: Physical server brand recommendation: It is recommended to use 2 DELL T440 servers to complete the system setup. And purchase DELL 3 year gold service. The server's system disk can optionally use raid to enhance redundancy. If you use the raid1 solution, the number of hard disks required needs to be increased by 2 times. (2TB SSD becomes 2TB SSD 2) Physical server brand recommendation: It is recommended to use 2 DELL T440 servers to complete the system construction. And purchase DELL 3 year gold service. The server's system disk can optionally use raid to enhance redundancy. If you use the raid1 solution, the number of hard disks required needs to be increased by 2 times. (2TB SSD becomes 2TB SSD 2) Physical server brand recommendation: It is recommended to use 2 DELL T440 servers to complete the system construction. And purchase DELL 3 year gold service. The server's system disk can optionally use raid to enhance redundancy. If you use the raid1 solution, the number of hard disks required needs to be increased by 2 times. (2TB SSD becomes 2TB SSD 2) Physical server brand recommendation: It is recommended to use 2 DELL T440 servers to complete the system construction. And purchase DELL 3 year gold service. The server's system disk can optionally use raid to enhance redundancy. If you use the raid1 solution, the number of hard disks required needs to be increased by 2 times. (2TB SSD becomes 2TB SSD 2) Physical server brand recommendation: It is recommended to use 2 DELL T440 servers to complete the system construction. And purchase DELL 3 year gold service. The server's system disk can optionally use raid to enhance redundancy. If you use the raid1 solution, the number of hard disks required needs to be increased by 2 times. (2TB SSD becomes 2TB SSD 2) Physical server brand recommendation: It is recommended to use 2 DELL T440 servers to complete the system construction. And purchase DELL 3 year gold service. The server's system disk can optionally use raid to enhance redundancy. If you use the raid1 solution, the number of hard disks required needs to be increased by 2 times. (2TB SSD becomes 2TB SSD 2) Two server plan business + storage Two server plan business + storage Two server plan business + storage Two server plan business + storage Two server plan business + storage Two server plan business + storage Number Server type Configuration requirements Operating system Server purpose Remarks 1 Server Zhiqiang Silver 4410 2 16 core CPU, 64G memory, 2TB SSD hard drive open Euler, Ubuntu, CentOS Main business server It is recommended to install VM 2 Storage 4410 2 16 core CPU, 64G memory, 500G SSD hard disk + required hard disk space (no raid or raid0 required) open Euler, Ubuntu, CentOS Storage server Hard disk capacity is configured according to storage space requirements The above configuration can support 1000+ users and about 150TB of storage space. Babel storage server uses an object storage system and supports distributed deployment (multiple storage servers) with a minimum requirement of one physical server. Supports the use of hard disk groups for verification, and supports multiple verification types such as 2+1, 3+1, 4+1... etc. See the self built object storage chapter for details. If you need to expand the storage space, just add a single storage server. You can also add a storage server as a backup server to synchronize the backup in real time. If there is a problem with the main storage server, switch to the backup server and it can be used normally. Single server (1 physical machine) deployment: Some customers who do not have a computer room but need to deploy BabelBird privately and have small storage space requirements (less than 10TB) can choose to deploy BabelBird on a single server. Just purchase a tower server that meets the requirements and place it in your company to meet the needs of using BabelBird. Physical server brand recommendations: If there is no computer room, it is recommended to use tower servers for deployment. It is recommended that the server storage hard disk is raid1 or raid5+1. The system disk of the server can optionally use raid to enhance redundancy. If you use the raid1 solution, the number of hard disks required needs to be increased by 2 times. (2TB SSD becomes 2TB SSD 2) Physical server brand recommendations: If there is no computer room, it is recommended to use tower servers for deployment. It is recommended that the server storage hard disk is raid1 or raid5+1. The system disk of the server can optionally use raid to enhance redundancy. If you use the raid1 solution, the number of hard disks required needs to be increased by 2 times. (2TB SSD becomes 2TB SSD 2) Physical server brand recommendations: If there is no computer room, it is recommended to use tower servers for deployment. It is recommended that the server storage hard disk is raid1 or raid5+1. The system disk of the server can optionally use raid to enhance redundancy. If you use the raid1 solution, the number of hard disks required needs to be increased by 2 times. (2TB SSD becomes 2TB SSD 2) Physical server brand recommendations: If there is no computer room, it is recommended to use tower servers for deployment. It is recommended that the server storage hard disk is raid1 or raid5+1. The system disk of the server can optionally use raid to enhance redundancy. If you use the raid1 solution, the number of hard disks required needs to be increased by 2 times. (2TB SSD becomes 2TB SSD 2) Physical server brand recommendations: If there is no computer room, it is recommended to use tower servers for deployment. It is recommended that the server storage hard disk is raid1 or raid5+1. The system disk of the server can optionally use raid to enhance redundancy. If you use the raid1 solution, the number of hard disks required needs to be increased by 2 times. (2TB SSD becomes 2TB SSD 2) Physical server brand recommendations: If there is no computer room, it is recommended to use tower servers for deployment. It is recommended that the server storage hard disk is raid1 or raid5+1. The system disk of the server can optionally use raid to enhance redundancy. If you use the raid1 solution, the number of hard disks required needs to be increased by 2 times. (2TB SSD becomes 2TB SSD 2) One server (all in one solution) One server (all in one solution) One server (all in one solution) One server (all in one solution) One server (all in one solution) One server (all in one solution) Number Server type Configuration requirements Operating system Server purpose Remarks 1 Server The entire Babel system deployed on a single server does not support object storage and uses read only hard disks or NFS for storage. It is recommended to use raid1 to improve system reliability. A backup server can be added for data synchronization and backup. If there is a problem with the main server, you can use the backup server to reconstruct the data. Deploy on existing virtual machine (hyperconverged) system: This is currently the most commonly used deployment method. It is deployed under the existing servers and hardware of the enterprise without purchasing new equipment. Deployment is completed in the customer's existing VM or virtual machine allocated by the hyper converged platform, which is suitable for users who already have certain IT construction and management. It is deployed in a small cluster, and the virtual machine platform is responsible for the unified management of the server. Supports most virtualized systems. It is recommended to deploy four virtual machines with storage space mounted. Number Server type Configuration requirements Operating system Server purpose 1 Virtual machine 8 core CPU 32G memory 500G SSD system disk CentOS8 or openeuler22 Main business server 2 Virtual machine 8 core CPU 16G memory 500G SSD system disk CentOS8 or openeuler22 Database server 3 Virtual machine 8 core CPU 16G memory 500G SSD system disk CentOS8 or openeuler22 Search server 4 Virtual machine 8 core CPU 16G memory 200G SSD system disk windows 2012 R2 transcoding server 5 Storage Support NFS or S3 interface storage system or virtual machine mounting disk as storage disk Support NFS or S3 interface storage system or virtual machine mounting disk as storage disk Support NFS or S3 interface storage system or virtual machine mounting disk as storage disk If there is a need for system redundancy, you can prepare 6 virtual machines to complete database backup and system redundancy. Number Server type Configuration requirements Operating system Server purpose 1 Virtual machine 8 core CPU 32G memory 500G SSD system disk CentOS8 or openeuler22 Main business server 2 Virtual machine 8 core CPU 32G memory 500G SSD system disk CentOS8 or openeuler22 From business server 3 Virtual machine 8 core CPU 16G memory 500G SSD system disk CentOS8 or openeuler22 Main database server 4 Virtual machine 8 core CPU 16G memory 500G SSD system disk CentOS8 or openeuler22 From database server 5 Virtual machine 8 core CPU 16G memory 500G SSD system disk CentOS8 or openeuler22 Database server 6 Virtual machine 8 core CPU 16G memory 200G SSD system disk windows 2012 R2 transcoding server 7 Storage Distributed Object Storage Distributed Object Storage Distributed Object Storage Supports virtual machine mounting disks to use the mounted disk as storage space. It can also be connected to third party storage systems such as san storage or object storage systems. BabelBird also provides customers with self built object storage services. Self built object storage server and virtual machine deployment: Babel supports customers to build object storage on general purpose servers. Because of the advantages of object storage software defined storage (high availability, easy horizontal expansion), it is recommended that users without object storage can purchase a new server and deploy the Babel object storage system to use it with the Babel business system running on a virtual machine (hyper convergence). The business server requirements are the same as those in the previous section \"Deployment on Existing Virtual Machine (Hyper Converged) System\". For a detailed introduction to Babel object storage, please see the \"Self Built Object Storage Server\" chapter. Most of our customers end up choosing object storage servers for storage. At least a single server is supported to build an object storage system (space requirement is less than 150TB). Server type Configuration requirements Operating system Server purpose Notes Storage server If storage density and future expansion investment are considered, a 12T hard drive can be used. Linux Object Storage Server It is recommended to add a server with the same disk capacity for future expansion. Single server object storage network topology diagram: We also support building a distributed object storage system composed of multiple servers. The minimum requirement for a distributed storage system is 2+1, which means three storage servers need to be prepared. The performance requirements are consistent with those of a single object storage. The currently recommended minimum unit for physical distributed storage is 3 storage servers. The 2+1 error correction code means that every time two storage nodes are expanded, one server needs to be added as an error correction server. In this way, 4+1 means that adding 4 storage servers requires adding an error correction server. So the disk utilization of 4+1 is higher than that of 2+1. The first construction using the 4+1 solution requires 5 storage servers. The minimum unit added for each expansion is the same as the minimum server unit required for the first construction. Multi server distributed object storage network topology diagram: You can add a new storage server or a set of storage servers for real time backup. If there is a problem with the primary storage server, quickly switch to the backup server and it can be used normally. Distributed high availability and high redundancy deployment: Because financial institutions, hospitals, energy, and very large enterprises have hard targets for uninterrupted business, they need systems that can achieve high availability and high redundancy. Services will not be interrupted due to a single point failure of the server, and hot switching and hot repair can be performed. In extreme cases, even network equipment such as switches need to be separated from active and backup, which requires the use of distributed high availability and high redundancy deployment. Babel supports a variety of high availability and high redundancy solutions and can be deployed in traditional distributed systems to achieve high availability and high redundancy. We can also build a distributed system suitable for Babel for customers. (Customers need to purchase hardware by themselves as required) Babel distributed deployment can ensure that any single point of failure will not affect the normal use of the system. The recommended distributed and easy to deploy solution uses active active active backup for the business server and distributed storage for the storage system. If there is a need for management and control of confidential and non confidential areas, please see the \"Data Ferry Chapter\" for details. Babel High Availability System Network Topology Off site disaster recovery deployment For users who have higher requirements for data preservation, BabelBird also supports off site disaster recovery solutions. It means backing up important database and file storage contents to an off site backup system. If there is a problem in the local computer room, as long as the backup data is there, the system can be rebuilt anywhere and restored to normal use. BabelBird can build off site disaster recovery servers for customers, but it does not support advanced backup methods such as hot and cold data separation. If the amount of data is very large (above 1PB) and considering cost effectiveness, it is recommended to use a professional backup system (such as NBU, Yunqi). BabelBird has a backup API that supports the NBU standard and can be called. Off site disaster recovery deployment has higher requirements on the network environment. It is best to have dedicated lines or stable VPN connections between computer rooms in different locations. Using the backup system can only restore and reconstruct data through backup after a problem occurs. Direct switching to backup data is not supported. Generally, the data reconstruction cycle will take a long time. Schematic diagram of using backup system for off site disaster recovery: If hot and cold data do not need to be classified and saved, BabelBird can also use the off site disaster recovery function of object storage to complete off site disaster recovery deployment for customers. Use object storage for remote disaster recovery. When the main system has a problem, you can quickly switch to the disaster recovery server. Self built object storage server Babel object storage is an object storage system developed on the open source MinIO system. It inherits MinIO's advantages of high performance, scalability, and data security, and is more suitable for the application scenarios of BabelBird Enterprise Drive. As an advanced object storage system, Babel object storage system has unparalleled advantages over traditional storage systems in terms of speed, security, stability, high availability, and horizontal expansion. Advantages of Babel object storage system Performance MinIO is claimed to be the fastest object storage server in the world. Published GET/PUT results of over 325 GiB/sec and 165 GiB/sec on 32 NVMe drive nodes and 100Gbe network, a clear advantage compared to Amazon S3 and far superior to traditional HDFS. High availability: MinIO ensures high reliability and availability through multiple copies of data, failover and automatic recovery, thereby ensuring that data is not lost and business is not interrupted. Low redundancy and high tolerance for disk damage: the standard and highest data redundancy coefficient is 2 (that is, storing a 1 M data object actually takes up 2 MB of disk space). However, data can still be read even if any n/2 disks are damaged (n is the number of disks in an erasure coding set). And this damage recovery is based on a single object, not based on the entire storage volume. Security: MinIO delivers more functionality with the highest levels of encryption and extensive optimizations that virtually eliminate the overhead typically associated with storage encryption operations. Data is stored in blocks and on each hard disk, and data cannot be restored even if you obtain read and write permissions from the hard disk or server. Extremely high scalability: MinIO supports distributed deployment and can be expanded horizontally. When more storage space or higher performance is needed, MinIO can be easily expanded by adding new nodes. At least it supports the deployment of object storage systems on a single machine, instead of the traditional requirement of three independent servers. Object storage system and erasure coding About erasure coding Babel Object Storage System (MinIO) uses erasure coding and checksums to protect data from hardware failures and silent data corruption. Even if half (N/2) of the hard drives are lost in the highest redundancy state, you can still recover data. Erasure coding is a mathematical algorithm for recovering lost and damaged data. MinIO uses Reed Solomon code to split objects into N/2 data and N/2 parity blocks. This means that if there are 12 disks, an object will be divided into 6 data blocks and 6 parity blocks. Any 6 disks can be lost (regardless of whether they store data blocks or parity blocks) and can still be recovered from the data in the remaining disks. We call the data storage D and the erasure code (parity) P. By default, the drive is sliced in N/2 data and N/2 parity blocks (customizable to support higher space utilization) Erasure coding is different from traditional multi copy technology. It has higher disk utilization and higher data recovery efficiency. (However, many storage manufacturers promote erasure coding as multiple copies and refer to the P number as the number of copies. This is inaccurate and will cause a lot of misunderstandings.) Multiple copies in the context of Babel refers to adding backup servers to fully synchronize and store data. Characteristics of erasure coding and differences from raid technology Erasure coding protects data from multiple drive failures RAID6 tolerates two drive failures while MinIO erasure coding allows the loss of half the drives RAID is a volume level erasure code, while MinIO erasure code is an object based erasure code (without downtime). Effective space calculation (space utilization) Assuming you need 100TB of storage space, how many hard drives you need to buy depends on the redundancy standard you choose. For example: using the 3+1 redundancy method, 100TB of available space requires the purchase of 12 12TB hard drives, 4 hard drives forming 3 groups, 9 data disks and 3 parity disks, the available space is 9 12, a total of 108TB available. If 2+1 redundancy is adopted, 15 10TB hard drives, 10 data disks, and 5 parity disks are required. In the 3+1 plan, only 3 of the 12 hard disks can fail without affecting system usage and data restoration. However, if you use the 2+1 plan, although you need to purchase more hard disks, any 5 of the 15 hard disks can fail without affecting the system usage. After replacing the damaged hard drive, the system can automatically repair the data. Please refer to the table below for space utilization. If the space requirement is large (more than 150TB) and continues to grow, considering storage density and cost performance, it is recommended that a server be equipped with 16 hard disks at a time. Different numbers of disks and space utilization can be calculated by clicking the link below https://min.io/product/erasure code calculator?ref=docs Hardware preparation Required hardware configuration. Babel supports a single server to build an object storage system (single node), using hard disk groups as redundant objects. Up to half of the hard drive can be damaged without affecting the normal use of the system. The Babel object storage system requires customers to prepare hardware servers in advance for deployment as required. The minimum configuration requires 2 Xhiqiang CPUs, 64GB memory and 400G solid state drives (system disks), and then the mechanical hard drives required to increase the corresponding storage capacity. To calculate the storage space required and the number of hard drives to purchase, click the link below to calculate it. https://min.io/product/erasure code calculator?ref=docs The recommended hardware configuration is as follows: Server type Configuration requirements Operating system Server purpose Notes Storage server If storage density and future expansion investment are considered, a 12T hard drive can be used. Linux Object Storage Server It is recommended to add a server with the same disk capacity for future expansion. Babel object storage uses software defined storage technology, so the hard disk does not require RAID. Considering that some servers require RAID to support multiple disks, in this case, each hard disk can be set to RAID0 pass through mode. Each expansion in single server mode requires adding a server with the same configuration. Uninterrupted service is possible during capacity expansion. Single server deployment also supports adding a server with the same configuration to establish active standby mode for real time synchronization. If the hardware of a server is damaged, it can be quickly switched to the backup server. The effective disk space capacity is related to the selected redundancy method. For example: use 8 10T hard drives to build an object storage system, and adopt a 3+1 redundancy scheme, which is equivalent to a group of 4 hard drives, divided into 2 groups, with an effective available space of 60TB. At the same time, if any two of the 8 hard drives are damaged, the data and system usage will not be affected. The damaged hard drive can be automatically rebuilt. If a 7+1 redundancy scheme is adopted, the effective available space is 70TB. Any damage to one of the eight hard drives will not affect data and system usage. Multi server deployment (distributed). Babel object storage system supports multi server deployment. If the server is used as a redundant unit, at least 3 servers are required, that is, 2+1 mode. However, considering the space utilization, it is recommended to adopt the 3+1 solution (that is, 4 servers). The configuration requirements for each node (server) are consistent with the single server deployment above. It is recommended that the node configuration be consistent (same operating system, same number of disks and same network connection) The number of drives provided by each node must be the same The time difference between nodes cannot be greater than 15 minutes (it is recommended to use NTP to ensure time consistency) The space utilization calculation is the same as for a single server. Privatization requirements and service procedures In order to ensure the experience and quality of using the BabelBird system, all privatized deployment work of BabelBird is deployed remotely or on site and certificates are issued by the BabelBird team. Deployment by an agent team or self deployment by customers is not currently supported. At the same time, the maintenance work of the system is also carried out by the Babel operation and maintenance team on a regular basis remotely. Customers only need to prepare the hardware and access resources as required, and leave the rest to the Babel team. Things that need to be prepared in the early stage of privatized deployment: Calculate the approximate number of users, concurrency, storage space and space growth rate and let the Babel account manager evaluate the required configuration. The customer evaluates the remaining resources (if any) of the existing server and selects a deployment method based on the actual situation. Babel issued a privatization deployment plan. Customers prepare corresponding servers and access resources according to the plan, allocate servers, and install operating systems. Ensure that the server can be accessed via external remote desktop (you can also use Sunflower) and ssh, and open the corresponding port (our deployment technicians will put forward specific port requirements) It is best for the user to provide a domain name. If there is no domain name, a fixed IP address is required. The solution using IP address to access needs to ensure that the IP address will not change during use. If you need to access your email to retrieve your password or send a verification code to your mobile phone number, you need to prepare the corresponding email access or SMS gateway. Number Project Requirements Remarks 1 Domain name An independent primary domain name or secondary domain name is required A secondary domain name can be set based on the company's original domain name. Such as yun.company.com 2 Email An email address that can send notification emails is required An email address that supports SMTP is sufficient Email push related MailUser=xxxx@mail.com MailPassword=password MailHost=Mail server address MailPort=Port number 3 Remote access Remote access to the server for configuration Support remote access and control of the server 4 SSl certificate https needs to apply for an SSL certificate Apply like a digital certificate authority CA. Recommended Application OV Wildcard 5 SMS interface If you need a mobile invitation, please register with your mobile phone. You need to activate the SMS interface service (optional) Cloud service providers such as Alibaba Cloud and Tencent Cloud also provide SMS service interfaces, which can be activated by applying implementation stage Notify us after the preparation work is completed, and we will give users a specific implementation time schedule. Please maintain smooth access to the external network during the implementation time period. Implementation generally takes 2 3 working days. On the first day, Babel is deployed and installed remotely, on the second day it is tested and accepted, and on the third day, problems encountered are corrected. Once the implementation is complete we will notify the user and then start the initialization phase Initialize service Babel provides initialization services to all private cloud customers, including: Maintenance personnel training (remote or on site) Help users with data migration, user import, permission assignment, etc. (remotely or on site) User training (remote or on site) Access third party services As an office platform centered on corporate documents, the privatized BabelBird Enterprise Drive can easily integrate various third party services into BabelBird to meet different needs by accessing third party APIs. These services include but are not limited to: electronic signature, advanced CAD preview, office, text recognition, image recognition... and other third party services to solve your needs. Conditions for accessing third party services In theory, third party applications or service modules that support the BS architecture can be accessed. Third party services must provide open APIs so that BabelBird Enterprise Drive can be integrated with them If it is an Internet service, the server needs to be able to access the external network. Enterprises need to authorize themselves or entrust us to purchase third party services for access. Recommended accessible services File anti leakage system: ipguard Online office editing: onlyoffice (self contained), office365, WPS Online, Yongzhong office Advanced CAD preview: Haochen Cloud Atlas, Dream CAD CAD online editing: Dream CAD Online signature: Sign on Text recognition and image recognition: Baidu Qianfan (Smart Cloud) AI related: Zhichao AI (self owned), ChatGPT, Zhipu AI Open API (unified storage platform) The private version of BabelBird provides an open API. Using the BabelBird API, you can use almost all capabilities of BabelBird in your system. And build custom applications and integrations in the cloud without having to build and maintain your own content management service. Unified storage platform Unified management of unstructured data: The core value of BabelBird Enterprise Drive's open API is that it can be used as a unified storage platform to integrate and manage unstructured data from various enterprise platforms. This includes but is not limited to OA (office automation), CRM (customer relationship management), ERP (enterprise resource planning) and other applications, so that all unstructured data of an enterprise can be managed uniformly on one platform, improving security and saving storage resources. Enterprise grade object storage: BabelBird Enterprise Drive can also open its own object storage interface as a unified storage management platform for enterprises. This means that enterprises can store data from different sources, including documents, media, reports, etc., in BabelBird Enterprise Drive, and access and manage these data through APIs. Documentation and support Detailed documentation: BabelBird Enterprise Drive provides detailed API documentation, including sample code and use cases, to help developers quickly integrate APIs. Attachment 2: Babel API document https://www.babel.cc/p/api integration.do Development support: We provide development support services, and technical staff will participate in joint debugging to solve one on one problems and challenges that may be encountered during the API integration process. Single sign on SSO The BabelBird privatization system supports docking with the SSO single sign on platform or third party platforms such as Enterprise WeChat, DingTalk, Feishu, OA, ADFS, and ERP to achieve single sign on. For more information about single sign on, please refer to the security chapter above: Single Sign On (SSO) integration Data ferry BabelBird can use the \"department security policy\" method to isolate a certain department's data to implement functions such as security and outbound approval of confidential departments. However, when it comes to file transfer between confidential and non confidential areas isolated by the network, data ferrying is required to ensure safe and controllable exchange of files between confidential and non confidential areas. Here, the BabelBird data ferry function needs to be deployed. In BabelBird, this functional module is named \"Transfer File\" to make it easier for ordinary users to understand. Implementation method Deploy one set of Babel birds in each of the secret area (R&D area) and the non confidential area (office area), and transfer files between the two sets of Babel birds: Need to install the Babel data ferry module Transmission ports need to be configured between the two sets of servers Transfers are encrypted using SSL Support file transfer between multiple sets of BabelBirds Super administrator can set specific document recipients and reviewers Can be configured to transfer files from non confidential area to confidential area without approval All transfers are recorded and logged Multiple sets of Babel birds transmit files across multiple networks: Simplified file transfer method for single set of BabelBird : The core requirement of some customers is to transfer files quickly and easily from the non confidential area to the confidential area. They only want to deploy a set of BabelBirds in the confidential area and have no need to use a network disk in the non confidential area. In this case, a simplified data ferrying method can be used. For security reasons, this method only supports transferring files from non confidential areas to encrypted areas, but does not support transferring files from encrypted areas to unencrypted areas. In addition to deploying a complete Babel system in the secret area, a file transfer service also needs to be deployed in the non confidential area. Transferring files from non confidential areas to confidential areas does not require approval. Usage steps After deploying the data ferry module, Babel will add a \"Transfer File Configuration\" module to the enterprise console. If you can see the module entry in the enterprise console, it means that the data ferry module has been deployed successfully. Create a new receiving port and sending port in the \"Transfer File Configuration\" of the enterprise console. The receiving end and sending end of the data ferry have been determined. If one set of Babel birds is only configured with an interface port and no sending port, then it can only receive files but cannot send files. For example: the secret area can only receive files but cannot send files. When a new receiving end is created, a token will be automatically generated, and the sending end must fill in the token to achieve encrypted transmission. A Babel bird can establish multiple receivers, and each receiver can choose different members. For example: the receiving ends of the R&D department and the technology department are separated. After passing the review, the recipient can find the transferred files in the \"Transfer Files\" column of his or her Babel account. Users can directly right click \"Send File\" in the BabelBird Enterprise Drive and select the receiving end to send the file (send). And check the files that have been sent and passed the review under the \"Send Files\" column. To ensure security, files are transferred in file units (important files are entrained in multi layer folders to cheat the review). Folder selection is not supported for transfer, but multiple file selection is supported for transfer. Administrators or department managers with approval authority can review received and sent files under the \"Transfer Files\" column. Only files that pass the review can be transferred." }, { "lang": "en", "slug": "deployment-custom-development", "title": "Custom development and white label services", "description": "Secondary development, API docking, process customization, interface reshaping, white-label OEM and project management methods.", "category": "Integrations And Extensions", "top_category": "部署指南", "keywords": [ "Deployment", "Custom development and white label services", "Private Deployment" ], "url": "en/deployment-custom-development.html", "source": "content/en/deployment-custom-development.md", "summary": "Custom development and white label services Customized development The private version of BabelBird can provide customers with professional customized development (secondary development) services. Based on BabelBird's existing products, we will launch products more suitable for customers based on their specific needs. Advantages of customized development of BabelBird Help you design products based on product thinking Different industries have different work processes and usage habits, and there is often a deep gap between demand and final products. Only demand without good product design will often delay the implementation of the project. In order to better suit your usage scenarios, our Bab", "headings": [ { "level": 1, "title": "Custom development and white label services", "id": "custom-development-and-white-label-services" } ], "images": [], "text": "Custom development and white label services Customized development The private version of BabelBird can provide customers with professional customized development (secondary development) services. Based on BabelBird's existing products, we will launch products more suitable for customers based on their specific needs. Advantages of customized development of BabelBird Help you design products based on product thinking Different industries have different work processes and usage habits, and there is often a deep gap between demand and final products. Only demand without good product design will often delay the implementation of the project. In order to better suit your usage scenarios, our Babel care team led by professional product managers will customize your own solutions and secondary development support for your company. Refined time estimate management We have a refined time estimation management system that has served Peking University Founder, which can accurately manage development time estimates and improve project success rate and implementation efficiency. Project estimates are clear and well documented, effectively reducing corporate costs and improving efficiency. Transparent project follow up and acceptance At every stage of the project, we have dedicated project managers and product managers to follow up. Ensure project progress and acceptance standards. And we can open our Jira (project management tool) to customers so that customers can know the progress and time consuming of the project at any time. Keep it updated and maintained The most common problem with custom development is future updates and maintenance. Because traditional custom development is quite different from standard products, new branches are often used, and the development team does not have the energy to maintain new branches. This causes custom development products to lose continuous maintenance and feature updates, become increasingly difficult to use or isolated, and are eventually abandoned. Babel noticed and solved this problem. We will use a modular approach to develop new customized requirements based on standard products, or integrate customized requirements into standard products and manage them in the form of configuration items. In this way, even customized products can enjoy the update and maintenance services of standard products, achieving sustainable development. Support white label service (OEM) For commercial purposes or brand building needs, some companies need to use their own product names and logos. Babel can provide a white label (OEM) version that meets the company's requirements. Transparent, professional and responsible Responsibility is what our customers give us the most and the highest praise. During the project maintenance period, we will consider it from the perspective of the enterprise, correct bugs and complete functional adjustments in a timely manner. Provide long term sustainable maintenance services for enterprises. Babel bird custom development scope API based system docking: such as docking and integration with OA, CRM, PDM and other systems. Custom development of API: open API for a certain function of BabelBird Enterprise Drive. Customized development of independent functional modules or subsystems using the Babel API interface. Focusing on the functional expansion, process customization and data exchange of the existing functions of BabelBird Enterprise Drive. Interface reshaping and functional customization development based on Babel bird source code. Babel bird custom development process Determine needs and technical implementation plans with customers. Issue: \"Requirements Analysis Instructions\" Product managers have in depth discussions with customers to design prototypes and interactions. Issue \"Secondary Development Plan\", \"Product Prototype\", \"Detailed Modules and Time Estimation Schedule\" In the business and contract phase, the customer pays the advance payment. Design drawings and development started. Internal testing and joint debugging. Trial launch and user testing. User training. User acceptance and delivery The customer pays the balance." }, { "lang": "en", "slug": "deployment-xinchuang", "title": "Xinchuang support", "description": "Domestic CPU, operating system, database and client environment support.", "category": "Integrations And Extensions", "top_category": "部署指南", "keywords": [ "Deployment", "Xinchuang support", "Private Deployment" ], "url": "en/deployment-xinchuang.html", "source": "content/en/deployment-xinchuang.md", "summary": "xinchuangsupport Xinchuang support BabelBird has been actively responding to the call for localization for many years, and BabelBird's products can also run in most innovative environments. Especially for the server side, whether it is CPU, operating system or database, BabelBird has corresponding Xinchuang solutions. CPU and server architecture support. Babel supports domestic CPUs with X86 and ARM instruction sets, such as X86's Loongson, Feiteng, Kirin, and Haiguang... It also supports domestic CPUs with ARM architecture, such as Kunpeng architecture and Feiteng ARM architecture. operating system. Babel uses docker for deployment and supports all Linux operating systems that support docke", "headings": [ { "level": 1, "title": "xinchuangsupport", "id": "xinchuangsupport" } ], "images": [], "text": "xinchuangsupport Xinchuang support BabelBird has been actively responding to the call for localization for many years, and BabelBird's products can also run in most innovative environments. Especially for the server side, whether it is CPU, operating system or database, BabelBird has corresponding Xinchuang solutions. CPU and server architecture support. Babel supports domestic CPUs with X86 and ARM instruction sets, such as X86's Loongson, Feiteng, Kirin, and Haiguang... It also supports domestic CPUs with ARM architecture, such as Kunpeng architecture and Feiteng ARM architecture. operating system. Babel uses docker for deployment and supports all Linux operating systems that support docker. Such as open Euler, Galaxy Kirin, and Tongxin UOS database. Babel recommends using AliSQL database or other MySQL compatible databases such as: open Causs (Gauss). BabelBird can also access other domestic databases for customization. Such as: Dameng, Renmin University Jincang, Nanda General... client. The Babel client can run on Linux systems and supports domestic systems such as Kirin and Tongxin. Since the Linux system file management interface is not unified, the Linux version of Babel does not support the synchronization of folders and mapped disk functions. Classification Classification Standard deployment system (non Xinchuang) BabelBird Xinchuang solution (x86) BabelBird Xinchuang solution (arm) Functions not supported by Xinchuang version Business Server Operating System Centos, openEuler, Ubuntu openEuler, Kirin Kunpeng, Kirin, Tongxin None Business Server BabelBird Version Standard Edition BabelBird Xin Chuang Edition (X86) BabelBird Xin Chuang Edition (arm) None Business Server Database MySQL Gaussian, TiDB, aliSql Gaussian arm None Business Server Component/Middleware tomcat tomcat, TongWeb7 tomcat None Business Server Component/Middleware pomleo pomleo (Xinchuang) pomleo (Xinchuang) None Business Server Component/Middleware Elastic Search Elastic Search (Xinchuang) Elastic Search (arm) None Business Server Component/Middleware Redis Babel readis Babel readis None storage server storage system minio minio minio arm none Client Client Babel win/mac client Babel linux/Kilin/Ubuntu client Need to be transplanted Linux version client does not support mapping disk and synchronizing folder functions" }, { "lang": "en", "slug": "changelog", "title": "Changelog", "description": "Versioned release notes for BabelBird Enterprise Drive, including the latest known version v9.4.2.2606171439.", "category": "Changelog", "top_category": "更新日志", "keywords": [ "changelog", "release notes", "v9.4.2", "sensitive content recognition", "automation tasks" ], "url": "en/changelog.html", "source": "content/en/changelog.md", "summary": "Changelog The latest known version scope is v9.4.2.2606171439 . The public changelog page may still display an earlier current version, so this page merges the public release notes with the latest confirmed version information. Public changelog source: Current Version v9.4.2.2606171439 Type Update Mapped drive Optimized mapped drive access for more stable on demand cloud file access Security Released sensitive content recognition for detecting, marking and restricting risky files Languages Added Hong Kong Traditional Chinese and Russian support Automation Optimized automation tasks and added batch folder creation Recent Versions v9.4.1 2026 02 14 Module Update Automation tasks Added signatur", "headings": [ { "level": 1, "title": "Changelog", "id": "changelog" }, { "level": 2, "title": "Current Version", "id": "current-version" }, { "level": 3, "title": "v9.4.2.2606171439", "id": "v9-4-2-2606171439" }, { "level": 2, "title": "Recent Versions", "id": "recent-versions" }, { "level": 3, "title": "v9.4.1 2026 02 14", "id": "v9-4-1-2026-02-14" }, { "level": 3, "title": "v9.4.0 2026 01 04", "id": "v9-4-0-2026-01-04" }, { "level": 3, "title": "v9.3.6 2025 11 11", "id": "v9-3-6-2025-11-11" }, { "level": 3, "title": "v9.3.2 2025 07 19", "id": "v9-3-2-2025-07-19" }, { "level": 3, "title": "v9.3.1 2025 06 27", "id": "v9-3-1-2025-06-27" }, { "level": 3, "title": "v9.3.0 March To May 2025", "id": "v9-3-0-march-to-may-2025" }, { "level": 2, "title": "Important Historical Versions", "id": "important-historical-versions" }, { "level": 3, "title": "v9.2.x", "id": "v9-2-x" }, { "level": 3, "title": "v9.1.x", "id": "v9-1-x" }, { "level": 3, "title": "v9.0.x", "id": "v9-0-x" }, { "level": 3, "title": "v8.x To v7.9.5", "id": "v8-x-to-v7-9-5" }, { "level": 2, "title": "Feature Evolution Index", "id": "feature-evolution-index" } ], "images": [], "text": "Changelog The latest known version scope is v9.4.2.2606171439 . The public changelog page may still display an earlier current version, so this page merges the public release notes with the latest confirmed version information. Public changelog source: Current Version v9.4.2.2606171439 Type Update Mapped drive Optimized mapped drive access for more stable on demand cloud file access Security Released sensitive content recognition for detecting, marking and restricting risky files Languages Added Hong Kong Traditional Chinese and Russian support Automation Optimized automation tasks and added batch folder creation Recent Versions v9.4.1 2026 02 14 Module Update Automation tasks Added signature creation and batch folder creation tasks Electronic signatures Adjusted the signature UI and added signature tutorial video playback Sensitive content recognition Added sensitive content recognition under enterprise console management tools External sharing Department files and personal files can be configured as disallowed, no approval required, or approval required with designated reviewers Enterprise control Added a setting to prevent users from changing personal information themselves Online editing Displays the online PDF editing button when OnlyOffice version is greater than 9.2 File access Any file can get an access link from the context menu Fixes Fixed issues and refined UI details v9.4.0 2026 01 04 Module Update Automation entry Added automation task menus to folders, departments, projects, material libraries and categories Task types Supported auto clean folder, auto rename, auto organize and auto PDF conversion Task management Added an Automation Tasks sidebar channel for viewing, editing, canceling and creating tasks Permission control Departments, projects, material libraries and categories require file access control permission to configure automation File selection UI Added search, clear search, list mode and tile mode to the related file selection UI Fixes Fixed issues and refined UI details v9.3.6 2025 11 11 Module Update Electronic signatures Added personal stamp settings and frontend signing for PDF, Office and image files, with signed PDF output File access control Added inheritance option for all subdepartments or subfolders Languages Added Russian display support Enterprise file entry Personal settings can open the user's department directly when entering enterprise files Light documents Supported Markdown paste and Markdown file import File list Tile mode shows file counts inside folders File lock Added auto unlock configuration for locks older than two hours Batch selection Fixed selection behavior after filtering large file lists v9.3.2 2025 07 19 Module Update Smart recommendations Personal files, enterprise files and material libraries can show up to six recommended files File filters Added recent visits and starred file filters Preview Added preview support for .sh , .py , .bash and .sql Categories Supported batch category assignment Fixes Fixed issues and improved the UI v9.3.1 2025 06 27 Module Update Link files Added link files with thumbnails and preview support Light documents Added light document creation and online editing Folder display Personal and enterprise folders can show subfolder contents v9.3.0 March To May 2025 Module Update Zhichao AI Added AI search, AI image search, single document Q&A, side panel chat, deep thinking and web search Excel data assistant Added spreadsheet Q&A, deep thinking mode and table assistance Image OCR Extract text from images and make it searchable AI search mode Added fast search and deep research modes AI auto tagging Match files to predefined tags and support batch tagging Image retrieval Improved AI image search and similar image search UI Adjusted context menu style and related interfaces Important Historical Versions v9.2.x Version Highlights v9.2.1 2025 01 13 Search results display tags; follow reminders send bell notifications; issue fixes v9.2.0 2024 12 15 Added material library, categories, sub libraries, access approval, download approval, thumbnail controls, upload allow/deny lists and material library access control v9.1.x Version Highlights v9.1.8 2024 10 19 Archive search improvements, thumbnail and advanced search speedups, strict permission check option, draw.io display improvements v9.1.7 2024 09 14 Private cloud password change checks, MP4 thumbnails, short share links, folder access logs, draw.io creation, hide thumbnails without download permission v9.1.6 2024 08 07 Tag list optimization, client transfer list improvements, project notification changes, enterprise short name in system title, sync entry, XSS and privilege fixes v9.1.5 2024 06 17 Department and project upload allow/deny lists, online editing restrictions, external sharing restrictions, two way Mac binding, personal private file restrictions v9.1.3 2024 04 22 Local archive, share management entry, tag set filtering, audio/video playback and upload speed improvement v9.1.2 2024 03 23 Multi device login limit, faster downloads, keyboard shortcuts, Zhichao reading assistant, folder upload and batch rename v9.1.1 2024 02 07 Sharing approval, enterprise only link access, recycle bin improvements, file upload allow list, approval stage movement, batch security level setting, tag filter enhancements v9.1.0 2024 01 26 Web CAD preview and anonymous folder download in client v9.0.x Version Highlights v9.0.4 December 2023 Multi level recycle bin, dark/light theme, XSS fixes, file access control paging and anonymous client downloads v9.0.3 2023 10 21 Department template folder deletion, enterprise storage statistics refresh, access control share button, numeric filename sorting, client access to share links v9.0.2 2023 09 29 Added Zhichao AI beta entry on website, PDF search fixes and access control share button v9.0.0 September 2023 Sorting supports mixing folders and files; global default sorting controls in personal settings v8.x To v7.9.5 Version Highlights v8.7.1 2023 07 07 Console views for account projects, shares, login history and access controlled files; other device login prompt v8.7 2023 05 07 Permission details in access control, filename only sharing permission, custom permission only option, custom tag style v8.6.6 Enterprise console log search for move/copy, advanced search, image metadata, copy/cut/paste and operation admin permissions v8.6.5 2023 01 16 Private cloud send file, monitoring alerts, shortcut customization, default notification off, project storage path and 30 day professional recycle bin v8.6.4 2022 11 14 Expired project indicator, clear account permissions, OnlyOffice preview configuration, anonymous online editing, archive entry and maintenance mode v8.6.3 2022 09 30 Local archive, license over limit login control and project transfer restrictions v8.6.2 2022 08 26 Upload list UI, project transfer option, virus file handling and personal storage quota v8.6.1 2022 07 15 Used license count, over license restrictions, deleting departments with subdepartments, upload permission and online editing relationship changes v8.6.0 2022 06 11 Convert personal folders to projects, session configuration, anonymous sharing prohibition, approver self selection and traffic statistics export v8.5.x 2022 Department templates, IP policy login option, mind map save as, enterprise email edit, unregistered user sharing switch, mind map creation, hidden organization structure and snapshot sharing v8.2 2021 05 21 Faster archiving, OnlyOffice read only preview, manage sharing permission, project assistant, open dropbox and restore all recycle bin v8.1 2021 04 04 Restore all from recycle bin, overseas login improvement and separate icons for client editing and online editing v8.0 January 2021 OnlyOffice read only preview and online editing, password error limit, external project users, traffic throttling, upload blacklist and video speed playback v7.9.5 Add group members by department, project channel consistency, hidden files in upload only shares, batch access control, watermarked PDF download and XSS fixes Feature Evolution Index Topic Representative versions Related pages Automation tasks v9.4.0, v9.4.1, v9.4.2 Automation Tasks Sensitive content recognition v9.4.1, v9.4.2 Sensitive Content Recognition Material library v9.2.0, v9.4.0 Material Library Zhichao AI v9.3.0 onward Zhichao AI Online editing and light documents v8.0, v9.3.1, v9.3.6 Online Editing Permission and security v8.7, v9.1.1, v9.1.5, v9.4.1 Permission System, Security and Audit Client, sync and mapped drive v9.1.6, v9.4.2 Sync And Client, Virtual Mapped Drive" }, { "lang": "en", "slug": "faq-index", "title": "FAQ Overview", "description": "Category entrance to BabelBird's frequently asked questions and an index of all questions.", "category": "FAQ", "top_category": "常见问题", "keywords": [ "FAQ", "User Manual", "question" ], "url": "en/faq-index.html", "source": "content/en/faq-index.md", "summary": "FAQ Overview This page summarizes common questions about BabelBird Enterprise Drive. You can start from a scenario below or jump directly to the numbered index. Browse By Scenario Scenario Questions covered Entry Getting started Registration, login, upload, new folders, enterprise files, personal files, departments and projects Getting Started, Accounts and File Spaces Permissions Roles, department permissions, file access control, upload permissions, upload only, classification levels and approval Permissions, Departments and Projects Sharing and collaboration Invitation sharing, link sharing, avatars, notifications, locks, versions, activity, discussions and workbench Sharing, Collaboratio", "headings": [ { "level": 1, "title": "FAQ Overview", "id": "faq-overview" }, { "level": 2, "title": "Browse By Scenario", "id": "browse-by-scenario" }, { "level": 2, "title": "Troubleshooting Paths", "id": "troubleshooting-paths" }, { "level": 3, "title": "Login fails or user does not exist", "id": "login-fails-or-user-does-not-exist" }, { "level": 3, "title": "Cannot upload or create folders", "id": "cannot-upload-or-create-folders" }, { "level": 3, "title": "Sync or mapped drive issues", "id": "sync-or-mapped-drive-issues" }, { "level": 3, "title": "Share link fails or permissions look wrong", "id": "share-link-fails-or-permissions-look-wrong" }, { "level": 3, "title": "Online editing or preview issues", "id": "online-editing-or-preview-issues" }, { "level": 2, "title": "Full Question Index", "id": "full-question-index" }, { "level": 3, "title": "Getting Started, Accounts And File Space", "id": "getting-started-accounts-and-file-space" }, { "level": 3, "title": "Permissions, Departments And Online Editing", "id": "permissions-departments-and-online-editing" }, { "level": 3, "title": "Sharing, Notifications, Versions And Workbench", "id": "sharing-notifications-versions-and-workbench" }, { "level": 3, "title": "Sync, Client And Mapped Drive", "id": "sync-client-and-mapped-drive" }, { "level": 3, "title": "Department Management, Projects And File Collection", "id": "department-management-projects-and-file-collection" }, { "level": 3, "title": "Preview, Online Editing, Search And Tags", "id": "preview-online-editing-search-and-tags" }, { "level": 3, "title": "Archive, Annotation, Review And Badges", "id": "archive-annotation-review-and-badges" }, { "level": 3, "title": "Deployment, AI, Limits And Troubleshooting", "id": "deployment-ai-limits-and-troubleshooting" } ], "images": [], "text": "FAQ Overview This page summarizes common questions about BabelBird Enterprise Drive. You can start from a scenario below or jump directly to the numbered index. Browse By Scenario Scenario Questions covered Entry Getting started Registration, login, upload, new folders, enterprise files, personal files, departments and projects Getting Started, Accounts and File Spaces Permissions Roles, department permissions, file access control, upload permissions, upload only, classification levels and approval Permissions, Departments and Projects Sharing and collaboration Invitation sharing, link sharing, avatars, notifications, locks, versions, activity, discussions and workbench Sharing, Collaboration and Notifications Client and local access Sync, mapped drive, deletion behavior, conflicts, permissions, drag and drop and missing mapped drive Synchronization, Client and Mapped Drive Departments and projects Department members, department files, temporary projects, file collection, external users, WeCom and DingTalk Department Management, Projects and File Collection Viewing and retrieval PPT, video, accidental deletion, resigned employee files, online editing, tags, advanced search and tree view Preview, Online Editing, Search and Tags Archive and review Archive library, comments, replies, comment permissions, badges, upload limits, CAD and preview generation Archives, Annotations, Review and Badges Deployment and troubleshooting Professional plan, private deployment, object storage, Zhichao AI, preview formats, verification codes, upload speed and member invitation Deployment, AI, Limits and Troubleshooting Troubleshooting Paths Login fails or user does not exist 1. Confirm whether you should use the public cloud login, enterprise subdomain or private cloud domain. 2. Confirm that the account is the email or phone number assigned by the administrator. 3. Private cloud users should use the private cloud entry or the company specific URL. 4. If it still fails, ask an administrator to check account status, department membership and initial password notifications. Cannot upload or create folders 1. Confirm that you are not in the enterprise file root. Enterprise files require entering a department folder first. 2. Confirm that your department role allows upload, folder creation or project creation. 3. Check file access control, allow/deny lists, storage limits and upload only permissions. 4. Client, sync and mapped drive upload follow the same permission system. Sync or mapped drive issues 1. Confirm that the client is logged into the correct enterprise and the sync or mapped drive task is running. 2. Check local path, cloud path, sync direction, sync blacklist and file permissions. 3. If conflicts or partial failures occur, identify the latest local and cloud versions before overwriting, restoring or uploading a new version. 4. Mapped drives depend more on live network and permissions; sync folders are better for offline editing and long term local work directories. Share link fails or permissions look wrong 1. Check whether the share expired, was closed, was restricted by administrators or requires enterprise member access. 2. Check whether the share allows preview, download, edit, comment or upload. 3. If external sharing approval is enabled for department or personal files, wait for approval. 4. Files inside encrypted folders still require the encrypted folder password even if the share link is available. Online editing or preview issues 1. Confirm that the file format is supported. Office online editing also depends on OnlyOffice or the online Office module. 2. Large files, complex PPT files, CAD files and video transcoding may take time to generate previews. 3. If the file is locked, confirm whether someone is editing it and ask an administrator to unlock it if needed. 4. If preview generation is stuck, check transcoding service, file format, file size and browser compatibility. Full Question Index Getting Started, Accounts And File Space 1. What can the Babel bird do? 2. What devices can BabelBird be used on? 3. Where to register a BabelBird account? 4. How to log into my BabelBird? 5. When logging in, it prompts \"The user does not exist.\" What's going on? 6. How to upload files? 7. Why can't I upload files or create folders in Enterprise Files? 8. How to create a new folder? 9. How to enter the enterprise console? 10. What is a role? 11. What is the difference between the blue folder and the yellow folder? 12. Where are my personal files stored? 13. What is a department folder? 14. What is a project folder? 15. How to set up a project? 16. What is the difference between departments and projects? 17. Why can’t I upload files in the department? 18. How to sort files? Permissions, Departments And Online Editing 19. How to use online editing? 20. How to collaboratively edit online with multiple people? 21. Why do documents edited by multiple people still have the version before editing (old version) after being downloaded? 22. How to use file access control? How to control access permissions of a file? 23. How to customize optional permissions for sharing? 24. How to control the authority of department members? 25. How can department documents be seen by members of other departments? 26. How does the department manager manage the department? 27. How do I know which department files have been shared? 28. What is the file confidentiality level (security level)? 29. How to view the department’s access log? 30. How to check the usage status of department members? 31. What does the approval process do? 32. What is the difference between upload permission and upload only permission? 33. Why can’t I see files uploaded by others? Sharing, Notifications, Versions And Workbench 34. How do I share a file with others? 35. How do I view files that others have shared with me? 36. What is the difference between invitation sharing and link sharing? 37. How to change my default avatar? 38. I want to receive prompt notifications after my colleagues update files. How do I do this? 39. Some files or folders have a \"control\" icon behind their icons. What does it mean? 40. Why can’t my newly uploaded files be searched? 41. Why does the folder size not show in the file list? 42. Why can’t the folder I uploaded overwrite the folder with the same name, but the file can? 43. Why does my file prompt that it is locked? 44. How to unlock locked files? 45. How to roll back a file version? 46. What is dynamics? 47. Can I search for updates? 48. What is a discussion group? 49. What is a workbench? How to use the workbench? 50. I don’t want to be harassed by too many dynamic messages, what should I do? Sync, Client And Mapped Drive 51. What is a mapping disk? What is the difference between synchronization and synchronization? 52. Why can’t I synchronize newly added files or not synchronize the latest file versions? 53. Why do I get the message that several files were not synchronized successfully when I synchronized? 54. What are the permissions related to synchronization? 55. I deleted a file locally when synchronizing files, will it still be there in the cloud? 56. During synchronization, if I delete a file in the cloud, will it still be there locally? 57. Can several people in our department synchronize a certain folder at the same time? 58. If I delete a file on the mapped disk, will it still be there in the cloud? 59. Why can’t I drag files on my mapped disk to WeChat and send them? 60. Why can’t I find my mapping disk? 61. Why can some files in my synchronized folder be synchronized, but some cannot? 62. Why can I edit some files in the department but not others? 63. I am a super administrator, why can’t I see the dynamics of some departments? 64. I am a super administrator, why do files appear in the Recycle Bin after I empty it? Department Management, Projects And File Collection 65. How does a department manager add new members? 66. How does a department manager change the permissions of department members? 67. How can department managers check which files in the department have been shared? 68. There is a file/folder in the department that I don’t want some people to see. What should I do? 69. I want people in our department to use BabelBird only on department computers. How to do this? 70. Does Babel support one user in multiple departments? 71. To temporarily establish a project team, it is necessary to transfer personnel from various departments of the company and share files. How to operate? 72. Why can't I create projects in my department? 73. There is a file in the department that I want to show to people in other departments, but I don’t want to invite them one by one. What should I do? 74. I want to collect some materials from various departments. How do I do this? 75. I want to send a file to everyone in the company so that they can view it, but it cannot be downloaded. What should I do? 76. How to use BabelBird to quickly collect user files? 77. The content in the sharing I sent to my customers is incorrect, what should I do? 78. I don’t want customers to download the files I share, but they can view them. What should I do? 79. I want to send files on BabelBird to contacts in WeChat. How do I do this? 80. Can I directly access BabelBird’s files using Enterprise WeChat/DingTalk? Preview, Online Editing, Search And Tags 81. Why can’t I play animation when previewing PPT? 82. Why can’t BabelBird play some video files? 83. I accidentally deleted a file, what should I do? 84. My colleague has resigned, what should I do with his files? 85. There are too many department files. I have uploaded a new file and want a colleague to take a look. How can I make it simple? 86. Why does the download folder not respond after a long time when I click to download it? 87. What is the difference between client side editing and online editing? 88. Why is my online editor so slow to open? 89. I want several colleagues to fill in a form together. How should I do this? 90. How can I view folders in a tree view? 91. Can I filter out the files I want to find based on conditions? 92. What is a label? 93. How to use the BabelBird tag? 94. How does Babel search for tags? 95. Does Babel support advanced search? 96. I want to send files on my computer to my colleagues. Is there any good way? Archive, Annotation, Review And Badges 97. How to manage corporate archives? 98. What types of files can be annotated? 99. How to create annotations? 100. How to delete comments? 101. How to reply to comments? 102. I uploaded a new version of the document, but the comments are missing? 103. How do I view comments from older versions? 104. If the file version is deleted, will the comments be deleted? 105. The comment I replied to is wrong, can it be revoked? 106. Why can't I create annotations? 107. Why can’t I give users the comment permission for link sharing, but they can’t comment? 108. Why can’t I create some types of comments on the APP? 109. Why can’t I create some types of annotations on my computer? 110. What should I do if the comments that I reply directly to in the dynamic cannot be displayed? 111. Various symbols will be displayed on the document. What do they mean? 112. What is the maximum size of a single file that can be uploaded? 113. CAD files cannot be previewed on the client, what should I do? 114. When previewing a file, I get stuck in the preview file generation interface. What should I do? Deployment, AI, Limits And Troubleshooting 115. How to renew the professional version when it expires? 116. Are there any restrictions on file types uploaded to BabelBird? 117. Is there a limit to the number of people who can edit online? 118. When sharing a file with others, the deadline has not yet reached, but the link cannot be opened. 119. The download speed suddenly slowed down. What’s going on? 120. When entering a folder, the lower right corner prompts that the file does not exist. 121. How to check the real time online editors of shared files? 122. Department roles have the permission to upload files, but files cannot be uploaded to a certain folder in the department. Why? 123. After a file in a team is deleted, whose recycle bin is it in? 124. After the team is deleted, will it be saved in the recycle bin? 125. Does Babel support privatized deployment? 126. How to privatize the BabelBird system? 127. Does Babel support object storage? 128. What hardware is needed to privatize the Babel system? 129. Does BabelBird support integration with Enterprise WeChat? 130. What is Zhichao AI? 131. I also want Zhichao AI Assistant, how to operate it? 132. Does Zhichao AI charge? How to charge? 133. Can Zhichao AI be privatized? 134. What file formats does Babel support for previewing? 135. How to use the client to download anonymously? 136. I uploaded a file to BabelBird, but after a while the file was automatically deleted. What happened? 137. Can BabelBird upload files on the mobile browser? 138. Can anonymous users upload files? 139. Why can’t I upload files in the personal file section? 140. Can departments be created in the front desk? 141. Is there a limit on the number or size of batch upload files? 142. When registering and logging in, I cannot receive the verification code (email, mobile phone)? 143. What is the difference between private and public? 144. Who has what authority to archive files? 145. Where is the electronic signature set? Can it be written by hand? 146. How can we chat? 147. Can file watermarks be added in batches? 148. The upload speed is very slow, what’s going on? 149. Why can’t I invite members?" }, { "lang": "en", "slug": "faq-basic", "title": "FAQ: Getting Started, Accounts and File Spaces", "description": "Covers frequently asked questions about getting started, accounts and file spaces.", "category": "FAQ", "top_category": "常见问题", "keywords": [ "FAQ", "FAQ: Getting Started, Accounts and File Spaces" ], "url": "en/faq-basic.html", "source": "content/en/faq-basic.md", "summary": "FAQ: Getting Started, Account and File Space The following questions cover common operations, permissions, collaboration and troubleshooting scenarios when users use BabelBird Enterprise Drive. 1. What can the Babel bird do? BabelBird is an enterprise network disk that mainly solves the three major problems of unified management of enterprise files, collaboration, and data security. BabelBird can automatically synchronize your work files to the cloud. You can use BabelBird to access your personal files or files in your department anywhere you have access to the Internet. In the Babel client, you can right click the edit button on the file, use local applications to edit cloud files, or edit ", "headings": [ { "level": 1, "title": "FAQ: Getting Started, Account and File Space", "id": "faq-getting-started-account-and-file-space" }, { "level": 2, "title": "1. What can the Babel bird do?", "id": "1-what-can-the-babel-bird-do" }, { "level": 2, "title": "2. What devices can BabelBird be used on?", "id": "2-what-devices-can-babelbird-be-used-on" }, { "level": 2, "title": "3. Where to register a BabelBird account?", "id": "3-where-to-register-a-babelbird-account" }, { "level": 2, "title": "4. How to log in to my BabelBird?", "id": "4-how-to-log-in-to-my-babelbird" }, { "level": 2, "title": "5. When logging in, it prompts \"The user does not exist.\" What's going on?", "id": "5-when-logging-in-it-prompts-the-user-does-not-exist-what-s-going-on" }, { "level": 2, "title": "6. How to upload files?", "id": "6-how-to-upload-files" }, { "level": 2, "title": "7. Why can't I upload files or create folders in Enterprise Files?", "id": "7-why-can-t-i-upload-files-or-create-folders-in-enterprise-files" }, { "level": 2, "title": "8. How to create a new folder?", "id": "8-how-to-create-a-new-folder" }, { "level": 2, "title": "9. How to enter the enterprise console?", "id": "9-how-to-enter-the-enterprise-console" }, { "level": 2, "title": "10. What is a role?", "id": "10-what-is-a-role" }, { "level": 2, "title": "11. What is the difference between the blue folder and the yellow folder?", "id": "11-what-is-the-difference-between-the-blue-folder-and-the-yellow-folder" }, { "level": 2, "title": "12. Where are my personal files stored?", "id": "12-where-are-my-personal-files-stored" }, { "level": 2, "title": "13. What is a department folder?", "id": "13-what-is-a-department-folder" }, { "level": 2, "title": "14. What is a project folder?", "id": "14-what-is-a-project-folder" }, { "level": 2, "title": "15. How to create a project?", "id": "15-how-to-create-a-project" }, { "level": 2, "title": "16. What is the difference between department and project?", "id": "16-what-is-the-difference-between-department-and-project" }, { "level": 2, "title": "17. Why can’t I upload files in the department?", "id": "17-why-can-t-i-upload-files-in-the-department" }, { "level": 2, "title": "18. How to sort files?", "id": "18-how-to-sort-files" } ], "images": [], "text": "FAQ: Getting Started, Account and File Space The following questions cover common operations, permissions, collaboration and troubleshooting scenarios when users use BabelBird Enterprise Drive. 1. What can the Babel bird do? BabelBird is an enterprise network disk that mainly solves the three major problems of unified management of enterprise files, collaboration, and data security. BabelBird can automatically synchronize your work files to the cloud. You can use BabelBird to access your personal files or files in your department anywhere you have access to the Internet. In the Babel client, you can right click the edit button on the file, use local applications to edit cloud files, or edit office documents online (you need to purchase the online office module). At the same time, you and your colleagues will also have a unified department space in BabelBird, and people in the entire department can access department files with different permissions. Everyone in the department can jointly annotate discussion files and collaboratively edit Office documents (you need to purchase the online office module). The editing operations of each file will be saved to form a new version, ensuring that your work will not be lost due to improper operation or equipment failure. 2. What devices can BabelBird be used on? BabelBird supports access using browsers (supports Html5 specification, Chrome browser is recommended), iOS devices (Apple phones and iPads), and Android devices. You can also install Windows client and Mac client. It also supports access to DingTalk and Enterprise WeChat (relevant modules need to be purchased separately). 3. Where to register a BabelBird account? Public cloud users can use the official website (website: https://www.babel.cc) to register for the enterprise public cloud version or personal version. The enterprise public cloud version only requires a mobile phone number to register, and other members of the enterprise are added by the administrator in the enterprise console. Registration address: https://www.babel.cc/p/signin entry.do At the same time, you can also download the client and use BabelBird on the client. The download address is below: https://www.babel.cc/p/download.do Private cloud users can ask the IT administrator to obtain the login address of their enterprise. You can download the corresponding client on our website, click the private cloud entrance button, enter your company's domain name, and jump to the login interface to log in. The private cloud account is created by our deployment personnel when deploying the privatized Babel system, and other members of the enterprise are also added by the administrator in the enterprise console. Download address: https://www.babel.cc/p/download.do 4. How to log in to my BabelBird? The login account and password for the public cloud enterprise version of BabelBird are assigned by the administrator. Just click to log in on the official website homepage. You may have received the corresponding account password in your email or mobile phone. Enter it on the BabelBird public cloud login interface to log in to your company. Login entrance: https://www.babel.cc/account/signin.do BabelBird will allocate an exclusive second level domain name to enterprises on the public cloud. You can also log in through this domain name. The usual format of the domain name is as follows: https://xxx.babel.cc If your company has purchased privatized BabelBird, you can enter your company's exclusive cloud disk address in the browser to log in. If you do not know the cloud disk address (enterprise domain name), please contact the enterprise IT personnel. If you use the client or APP, please click the \"Private Cloud Portal\" button and enter the domain name before logging in. The private cloud entrance button is usually below the login box. After clicking on the privatization portal, a domain name input box will appear, requiring you to enter the privatized domain name (just enter the domain name header directly, without adding http or https). The https protocol is selected by default. At this time, enter your company's cloud disk domain name and click OK to enter the private cloud login interface. The BabelBird enterprise account is assigned by the administrator. After the administrator assigns it, it will automatically send an email or text message. Use the email address to which the email was received and the initial password attached to the email or the mobile phone number and the initial password in the text message to log in. If your company uses domain control single sign on, enter your user name and password to log in. Generally, the user name is your domain control email address and the password is your domain control password. After setting up the domain name address to log in to the private cloud, the system will remember the private cloud address. You can log in directly by clicking on it next time without having to enter it again. 5. When logging in, it prompts \"The user does not exist.\" What's going on? Check the account number you entered to make sure it is entered correctly. Check whether your account is the login account assigned by the administrator. The BabelBird login account is usually an email or mobile phone number. If you are a private cloud customer, the most likely problem is that you entered your login account and password into the public cloud login portal. If you are a private cloud user, you need to use the private cloud login portal. How to log in to a private cloud account, please refer to FAQ Question 4: How to log in to my BabelBird? 6. How to upload files? BabelBird supports a variety of ways to upload files, but BabelBird will determine whether you have upload permission in the upload target directory. If you do not have upload permission, it will give a prompt or not respond depending on the upload method. Commonly used upload methods are as follows: Browser and client drag and drop upload: Open the target folder on BabelBird, and directly drag the file or folder to be uploaded to the target folder for upload. (Some browsers do not support drag and drop upload of folders. If you need to drag and drop upload in the browser, it is recommended to use the Chrome browser) Click the \"New\" button in the upper left corner to upload: Open the directory to be uploaded on BabelBird, click the \"New\" button and select \"Upload File\" to select the file to upload. After installing the client, right click the file or folder you want to upload locally and select BabelBird Upload the file. Use the client synchronization function to upload: After the folder is synchronized, drag the file to be uploaded directly into the folder, and the file will be automatically uploaded to the corresponding folder of BabelBird. Use the mapping disk to upload: Open the target folder in the mapping disk and drag the files to the mapping disk. As long as your account has the upload permission for the folder, the files in the mapping disk will be automatically uploaded. Open the BabelBird target folder on the mobile APP, click the + sign in the upper right corner to select the upload file to upload. Open the file on WeChat on your mobile phone, select the \"More\" button in the upper right corner, select \"Open with other apps\" and select \"BabelBird\" to upload. 7. Why can't I upload files or create folders in Enterprise Files? Babel's corporate files are managed on a department by department basis, so the root directory of the corporate file column is used to display the department to which you belong. You cannot upload or create new files in the root directory. To upload files to the enterprise, you need to click on the department you are in and upload it in the department. If you cannot upload files in a department (you do not see the upload button) or the drag and drop upload does not work, please contact the administrator to confirm whether you have upload permission in the department. 8. How to create a new folder? Members who have the permission to create new folders in the department can create new folders in the department folder. You can create any folders in your personal files (some corporate settings do not allow users to upload personal private files. If this setting is turned on, you cannot create new folders in your personal space) Right click the blank space where you want to create a new folder, and a new menu will pop up. Select the new folder in You can also click the \"New\" button in the upper left corner to create a new folder. 9. How to enter the enterprise console? The administrator clicks on the avatar in the upper left corner and selects the enterprise console to enter 10. What is a role? Roles are a collection of permissions of members in a department. After setting roles, different members can be assigned different roles according to the management needs of the department. If the member is in the department assigned the role, access to the department folder will be based on the permissions the role has. Babel allows a company member to have different roles in different departments, that is, different access rights. Multiple department members can use the same role. Just set the role and assign it to members as needed. But this also means that after the permission content of a role is changed, the permissions of members using the same role will also be changed. Administrators can customize or modify role permissions in the enterprise console permission management department permission list. 11. What is the difference between the blue folder and the yellow folder? The blue folder with the word \"Enterprise\" is an enterprise folder, and everyone in the entire enterprise (except those who are restricted members) can access the contents. There are two types of enterprise folders: enterprise publishing folders and co publishing folders. Only enterprise administrators, security officers, and archivists can upload files to the enterprise publishing folder. All members of the company can upload files to the common publishing folder. Generally, some corporate announcements or commonly used software and other common corporate resources will be placed in the corporate folder. The other blue ones are department folders. The files in the blue folders belong to departments and enterprises. Generally, users will see a blue folder named after their own department in the \"Enterprise Files\" column. This folder can only be created by parent department administrators or enterprise super administrators, operation and maintenance administrators, and security officers. Files placed in this folder are usually visible to everyone in the entire department. Department folders can be understood as shared folders for the entire department. The yellow folder is a normal folder. Any role in the department (under the department folder) with permission to create new folders can create it. Generally, people in the entire department can access and upload files to the yellow folder created under the department folder. The yellow folder created under \"Personal Files\" is a personal folder and will only be visible to you if you do not share it. The dark blue folder is the project folder. The project folder is the personal project in the personal file and the enterprise project in the department. Project folders are assigned project member permissions by the project leader and project assistant. A validity period can be set for the project folder. After the validity period, only the project leader and project assistant will be able to see it. For projects under department folders, department managers (roles with department file management permissions) can also manage and view and download all files inside. 12. Where are my personal files stored? If your company has turned on \"Allow users to upload personal private files\" (usually turned on by default), you can upload your personal files in the \"Personal Files\" column on the left side of BabelBird. Personal files are only visible to you as long as you don't open them for sharing. When an employee leaves the company, the administrator can transfer the member's files to the designated company member. This transfer includes personal files. 13. What is a department folder? In the Babel document system, the file/folder system has two types of ownership: personal files and corporate files. Enterprise files are organized into departments. According to the organizational structure, each department will have a department folder belonging to the department. Department folders have the following characteristics: Members of the same department, as long as the permissions allow, can access the department folders of their own department and use the files in them. Department files belong to the enterprise, and the department administrator (a person with department file management authority, usually the department manager) has jurisdiction over all files within the department. Department managers can add or remove members from the department and change members' permissions. Members of the parent department can set whether they can view sub departments based on role permissions. After department members delete department files, they can view and restore them in the recycle bins of themselves, department managers, and enterprise administrators. For all files/folders in the department, the department manager can turn on file access control to precisely control the operation permissions of department members and roles on the files/folders. Department managers (people with department file management rights) do not need to log in to the enterprise backend and can directly manage departments from the front desk. Only members of the department, super administrators, and security officers can access the files of the department. If you have file sharing permissions in your department, you can invite members of other departments or external users to access department files. If there is no file sharing permission in the department, link sharing and invitation sharing require the consent of the department administrator. Non department members cannot view the department's updates and join department discussions. Department folders have independent logs and management, which can be viewed by department managers. 14. What is a project folder? Many times, we need to cooperate with multiple departments and share files across departments. At this time, we need to create project folders. You can create a personal project in the \"Personal Files\" root column, or you can create a project under your department (only roles with the permission to create folders/projects can create department projects). Personal projects belong to the creator, and department projects belong to the department. The department manager can view and manage the content under the department project, regardless of whether the project was created by the department manager or whether the department manager belongs to the project. Both personal projects and department projects can invite internal members or external personnel of the entire enterprise, or mobile phones or email addresses that are not registered with BabelBird to join. The project folder has the following characteristics: Projects have a validity period, after which project members will no longer be able to see the project. The project leader can change the validity period of the project midway. At the same time, the project can set the validity period of project members respectively. After the validity period of the project member's permission expires, the project member will not be able to access the project, but the files uploaded by the member in the project will be retained. Both the project leader and the project itself can be transferred. Individual projects can also be transferred to departments or other individuals through transfer, and department project leaders can also be transferred to other departments or other members. If the project is transferred to another department, project ownership and project management rights will also be transferred. The permissions of personnel within the project are not affected by department roles (except for roles with department file management permissions). The project leader can arbitrarily change the permissions of project members in the project and set the deadline for project members to access the project. However, in departmental projects, roles with \"Department File Management\" permissions (usually department managers) can access the project without being subject to project permissions. Project creators and project leaders can invite any member within the enterprise to join the project. It also supports inviting external members to join the project. The project has an independent project discussion group where group chats can be held. Department projects can only be created in the department root directory (for ease of management) and cannot be created in other folders of the department. Personal projects can only be created in the root directory of \"Personal Files\" and cannot be created in other personal folders. The project supports creating subprojects. Sub projects can have independent project management permissions and project leaders. Members of the parent project can view the content of the sub project, and the permissions follow the parent project. Click on the person's avatar in the discussion group to view the list of files uploaded by the person in the project. After the project is created, it will be displayed in the \"My Projects\" root directory of project members. Project members can access the project in the My Project section. You can also view the projects you have joined or managed in the My Projects column. 15. How to create a project? Click the New button in the upper left corner in the blank space where a project can be created (personal projects are created in the root directory of \"Personal Files\", department projects are created in the root directory of the department folder), select the New Project button, and follow the guidance to create the project and add project members. After members are added, they will receive a notification to join the project and can access the project in the \"My Projects\" column. You can create a personal project in the \"Personal Files\" root column, or you can create a project under your department (only roles with the permission to create folders/projects can create department projects). Personal projects belong to the creator, and department projects belong to the department. The department manager can view and manage the content under the department project, regardless of whether the project was created by the department manager or whether the department manager belongs to the project. Both personal projects and department projects can invite internal members or external personnel of the entire enterprise, or mobile phones or email addresses that are not registered with BabelBird to join. 16. What is the difference between department and project? In Babel, department is the basic unit of enterprise files, and enterprise files are organized in a tree like manner by root departments and sub departments under the root department. If you import an organization from a third party application, the organization will also exist in the form of departments in Babel. Therefore, department folders are suitable for relatively fixed organizations (commonly known as departments) in enterprises that need to share files for a long time. Departments have the following properties in Babel: Departments at the same level are independent of each other, and each department can be managed independently or managed by a superior department. Each department has a corresponding department folder, and department members have corresponding access rights to the department folder through role permissions. Member roles in the management department need to have the \"Department File Management\" and \"Manage Department Personnel\" permissions. If you want to manage subordinate departments, you need the role permission \"Subdepartment Management\". To view sub department files, members of the parent department need the role to have the \"View sub department files\" permission. The administrator allocates the upper limit of storage space to each department. The security officer sets the overall security policy of the enterprise or department. The access rights of department members in the department are determined by the department members' role rights in the department. Files in a department can also be controlled by file access control to control members' access rights. File access control rights have a higher priority than members' role rights in the department. Department members can only see the department they joined in the root column of the enterprise file. For example: If the member joins both the parent department and the sub department, the two departments will be displayed in the root column of the enterprise file. If only one department is added, only one department will be displayed in the root column of the enterprise file. The super administrator will display the enterprise root department (named after the enterprise name) in the enterprise file root column, which contains all departments of the enterprise. Deleting a department will lose all department files for that department. Sub departments and projects can be created in departments, and ordinary folders can also be created or uploaded. Projects can only be created in department folders, not ordinary folders in departments. In Babel, projects are suitable for cross department collaboration, or temporarily formed project teams to share files. The project can include other department members or external members, making it more flexible. The Babel project folder has the following characteristics: They are divided into personal projects and enterprise projects. Personal projects can be created in the personal file root directory and managed by the creator. Enterprise projects can only be created under department folders. Different departments can create different projects. Anyone with personal private files can create personal projects (whether users are allowed to upload personal private files can be turned on or off in the enterprise console) Enterprise projects need to be created by department members in the root directory of the department, and the member role needs to have the \"Create Folder/Project\" permission. Projects are managed by a project leader (default is the project creator), who can be transferred to others. Projects can invite other department members or external members to join Project access rights are equivalent to sharing rights. Optional project access permissions can be customized in the Enterprise Console Permission Management File Permissions List. There is a \"My Projects\" column in the left column of the main interface of all users, which contains a list of all projects created and joined by the user. Role members with the \"Department File Management\" permission in the department where the project is located can access and manage the project. External members can join the project through email or mobile phone number verification (the email or mobile phone number used to invite them to join the project). Files within the project can also have fine grained control over permissions through \"File Access Control\". Projects can be transferred from individuals to departments and from departments to other departments using transfer methods. A project can have a validity period. After the validity period expires, except for the project leader, administrators of the department where the project is located and other project members will not be able to access the project. Multiple sub projects can also be created under a project, and sub projects can be converted into parent projects. Projects without sub projects can also be converted into sub projects of other projects. In summary, the main differences between departments and projects are: Departments are relatively fixed and have powerful functions. Only department members can access department files through roles and access control permissions, making management more refined. Suitable for long term organizational structure management. The project belongs to a certain department or individual and is relatively flexible. Members can be invited across departments or even external members, and are managed by the project leader. Project member permissions are consistent with file sharing permissions, making it easy to use. Suitable for project teams managed on a project by project basis. If department members and project members do not perform \"file access control\", they can access all files in the department or project by default. 17. Why can’t I upload files in the department? Your department role does not have file upload permissions. You can contact the department manager to change your role. You do not have file upload permission for a folder under this department, and permissions are controlled on this folder. 18. How to sort files? The files in the Babel file list can be sorted according to user needs, and the system will remember the last user's sorting selection under the folder and use the same sorting the next time it is opened. The way to sort files is: click the \"Sort\" icon on the far right at the top of the file list and select the desired sorting method. The default sorting method is \"Recent Version\", that is, the latest updated files first. You can also choose to sort by name or size. Users can also customize the global default sorting method. The operation method is: click the avatar settings account information global default sorting, and select the required sorting method in the drop down box. Pinned files are not affected by sorting and are always at the top. The default is to sort departments first, followed by inboxes, ordinary folders, and finally files. There is a switch button for mixing folders and files. If this switch is turned on, when sorting, files and folders will be mixed and sorted according to the specified sorting method." }, { "lang": "en", "slug": "faq-permissions", "title": "FAQ: Permissions, departments and projects", "description": "Covers frequently asked questions about permissions, departments, and projects.", "category": "FAQ", "top_category": "常见问题", "keywords": [ "FAQ", "FAQ: Permissions, departments and projects" ], "url": "en/faq-permissions.html", "source": "content/en/faq-permissions.md", "summary": "FAQ: Permissions, departments and projects The following questions cover common operations, permissions, collaboration and troubleshooting scenarios when users use BabelBird Enterprise Drive. 19. How to use online editing? BabelBird supports multi person online editing of office documents. Whether it is word, excel, ppt or wps documents, they can be edited online on BabelBird. The method of use is very simple. Create or upload an office file, right click on the file and select Online Editing to start online editing. If you cannot edit online, it may be due to the following situations: There is no online edit button. Please check if you have edit permissions for the file. Or whether the Babel", "headings": [ { "level": 1, "title": "FAQ: Permissions, departments and projects", "id": "faq-permissions-departments-and-projects" }, { "level": 2, "title": "19. How to use online editing?", "id": "19-how-to-use-online-editing" }, { "level": 2, "title": "20. How to collaboratively edit online with multiple people?", "id": "20-how-to-collaboratively-edit-online-with-multiple-people" }, { "level": 2, "title": "21. Why do documents edited by multiple people still have the version before editing (old version) after downloading?", "id": "21-why-do-documents-edited-by-multiple-people-still-have-the-version-before-editing-old-version-after-downloading" }, { "level": 2, "title": "22. How to use file access control? How to control access permissions of a file?", "id": "22-how-to-use-file-access-control-how-to-control-access-permissions-of-a-file" }, { "level": 2, "title": "23. How to customize sharing optional permissions?", "id": "23-how-to-customize-sharing-optional-permissions" }, { "level": 2, "title": "24. How to control the permissions of department members?", "id": "24-how-to-control-the-permissions-of-department-members" }, { "level": 2, "title": "25. How can department files be seen by members of other departments?", "id": "25-how-can-department-files-be-seen-by-members-of-other-departments" }, { "level": 2, "title": "26. How does the department manager manage the department?", "id": "26-how-does-the-department-manager-manage-the-department" }, { "level": 2, "title": "27. How to know which department files have been shared?", "id": "27-how-to-know-which-department-files-have-been-shared" }, { "level": 2, "title": "28. What is the file confidentiality level (security level)?", "id": "28-what-is-the-file-confidentiality-level-security-level" }, { "level": 2, "title": "29. How to view the department’s access log?", "id": "29-how-to-view-the-department-s-access-log" }, { "level": 2, "title": "30. How to check the usage status of department members?", "id": "30-how-to-check-the-usage-status-of-department-members" }, { "level": 2, "title": "31. What does the approval process do?", "id": "31-what-does-the-approval-process-do" }, { "level": 2, "title": "32. What is the difference between upload permission and upload only permission?", "id": "32-what-is-the-difference-between-upload-permission-and-upload-only-permission" }, { "level": 2, "title": "33. Why can’t I see the files uploaded by others?", "id": "33-why-can-t-i-see-the-files-uploaded-by-others" } ], "images": [], "text": "FAQ: Permissions, departments and projects The following questions cover common operations, permissions, collaboration and troubleshooting scenarios when users use BabelBird Enterprise Drive. 19. How to use online editing? BabelBird supports multi person online editing of office documents. Whether it is word, excel, ppt or wps documents, they can be edited online on BabelBird. The method of use is very simple. Create or upload an office file, right click on the file and select Online Editing to start online editing. If you cannot edit online, it may be due to the following situations: There is no online edit button. Please check if you have edit permissions for the file. Or whether the BabelBird account you are using has online editing authorization enabled. I clicked online editing but no response. If you use a browser to access BabelBird, please check whether the online editing window is blocked by the browser. Some browsers will block new windows. Usually, this type of browser will have a prompt that new windows are blocked at the far right of the address bar. Just click to open it. Prompt file is locked. In this case, there is often a user editing the document using the client. 20. How to collaboratively edit online with multiple people? BabelBird supports multi person online editing of office documents. Whether it is word, excel, ppt or wps documents, they can be edited online on BabelBird. Create or upload an office document that needs to be edited by multiple people, and share it with the members who need to collaborate (if it is a department file or project file, and the collaborators are also in the corresponding department or project, they can see the document without sharing). Be sure to give the other party editing permissions. At this time, everyone can use online editing to perform collaborative editing. 21. Why do documents edited by multiple people still have the version before editing (old version) after downloading? In order to ensure the integrity of online editing documents, Babel Online Editing has a system setting: it requires waiting for all editors to exit for 10 seconds before saving the collaboratively edited document as the latest version. If you exit in the middle of collaborative editing while there are other collaborators editing at this time, the version of the downloaded document will be the version before the online editing. Therefore, if you want to download the latest version, you need to ensure that all collaborators have logged out and closed the online editing interface. (The ID of the member being edited at the moment will be displayed in the upper right corner of the online editing interface) If you want to save the latest version during the editing process, you can also click File Download As select the format you want to download directly in the online editing interface. This way you download the latest version. (The downloader needs to have download permission for the file) The online editing permissions and downloading permissions of BabelBird can be separated to meet the special needs of some users who need to be able to edit online but not download. 22. How to use file access control? How to control access permissions of a file? File access control can be turned on for Babel's project files/folders and department files/folders to limit specific project members or department members' access to the files/folders. File access control is only for members within the department. If you need people from other departments to access the file, please use the sharing function. File access control takes precedence over a member's department role permissions or project member permissions. For example: a member has editing permissions on a certain file in the department, but if the member's permissions on the file are set to read only through the file access control, then the member will only have read only permissions on the file. File access control is also effective for folders. If file access control is set for a folder, the members whose access control is set will also follow the permissions set by the file access control for all files in the folder, including subfolders. Right click on the project file (folder) and department file (folder) and select \"File Access Control\" to turn on file access control for the file. There is a list of members who can access the file in the file access control interface. Just select the permissions you want to control for specific members. You can also set the validity period of access control. After the validity period, access control will become invalid. At the same time, department files can also set a role's access rights to specific files (folders) through file access control. Right click \"File Access Control\" on the department file (folder) and select the \"Role Permission Settings\" column at the top of the file access control interface to set file access control for a certain role. 23. How to customize sharing optional permissions? BabelBird has two permission systems that can be used in conjunction with each other. One is the \"role permissions\" that determines the use permissions within the department, and the other is the \"file permissions\" that are used to control sharing, projects, and file permissions. Both \"role permissions\" and \"file permissions\" can be customized in the background, and specific permission types and permission names can be selected. Unify management and customization in the enterprise console permission management. In the permission management column, select \"Department Permission List\" to manage role permissions, and select \"File Permission List\" to manage file permissions. The customized permissions in the file permission list correspond to the optional permissions when sharing files. (At the same time, the permissions controlled by project member permissions and file permissions are also common) For example: click the \"Customize Permissions\" button in the file permissions list, create a new permission, name it \"Intern\" and then check the specific permissions you want to give to interns (such as preview, upload, download). After clicking OK, a new permission called \"Intern\" will be added to the file permissions list. At the same time, when sharing files, adding members to projects, and controlling file permissions, the permission \"Intern\" can also be selected in the drop down permission selection box. 24. How to control the permissions of department members? You can change the member's permissions by changing the member's role in member management. If you want to control the access permissions of a specific file (folder), right click on the file (folder) and select \"File Access Control\" and then find the member whose permissions you want to control, pull down and select the permissions to give him. 25. How can department files be seen by members of other departments? Use the sharing feature to invite other department members to access the file (folder). Right click on the file (folder) that you want to show to other department members, select Share select the member you want to share with (or enter the member account or email address) in the invite share area, pull down and select to give him permission to access the file (folder) click Send. After the invitation is sent successfully, the invitee can receive the invitation notification, and the file (folder) can also be seen in the \"Sharing I Joined\" column on the left side of the invitee's BabelBird. 26. How does the department manager manage the department? Find the department folder in the enterprise file column, right click and select \"Department Management\" to open the department management interface. (Only people with the \"Department File Management\" role permission can see the \"Department Management\" option) 27. How to know which department files have been shared? The department manager (a person with the \"Department File Management\" role permission) right clicks on the department folder and selects \"Department Management\". Find \"Department Shared File Statistics\" in Department Management and click \"Open Shared File List\" to view a list of all shared files in the department. You can also click the blue button on the path to open it through the quick menu: 28. What is the file confidentiality level (security level)? The file confidentiality level (security level) can be set for BabelBird's department files, and the system limits the file's usage scope, sharing method, and permissions based on the file's security level. Suitable for setting files with relatively high security requirements. BabelBird's document security levels are divided into four levels: public documents, internal documents, restricted documents, and confidential documents. The default files are public files. Right click on the file More options Security level to change the security level of the file. Files with different security levels are handled as follows: Confidential files are not visible to anyone in the department except the creator, project leader, file leader and department manager by default. Sharing the file must be authorized by the security officer This file is restricted and can only be read by general personnel. Sharing this file must be authorized by your superior. Internal documents, sharing this document with people outside the department must be authorized by the superior supervisor The above three types of files do not support link sharing and only support invitation sharing. Confidential files, restricted files, general personnel cannot move/copy/upload new versions/download/rename/view versions, only superior supervisors and personnel with department file management permissions can 29. How to view the department’s access log? Department administrators (roles with \"Department File Management\" permissions) can view the file access logs of the entire department. There are two ways to view them. Open the department folder. There is a small blue icon in front of the department name in the path bar (breadcrumbs) at the top of the department folder. Click the icon to select file access statistics, and select \"Access Log\" at the top of the pop up window. Find the department folder in the enterprise file root directory, right click, select Department Management, find department file usage management file access statistics, and click \"Open File Access Log\" There is an \"Export Report\" button in the upper right corner of the access log, which can export the log to an excel file. 30. How to check the usage status of department members? Department administrators (roles with \"Department File Management\" permissions) can view the use of network disks by members of the entire department. There are two ways to view them. Open the department folder. There is a small blue icon in front of the department name in the path bar (breadcrumbs) at the top of the department folder. Click the icon to select file access statistics. Find the department folder in the enterprise file root directory, right click, select Department Management, find department file usage management member usage, and click \"Open Usage\" 31. What does the approval process do? Babel supports document review and approval, and the ultimate goal of review and approval is to finalize the document. The file approval process can be configured in the Enterprise Console File Configuration Approval Management to become a pre made approval process. Department roles with department file management rights can also set the approval process used when department members initiate approval in the department management column. There are 4 setting methods: the approval process can be freely defined (department members can customize the approvers of the approval process when they start approval), and all pre made approval processes can be selected process (department members can choose to preset all approval processes in the management backend when they start approval), limit specific approval processes (select a few approval processes to be used by the department in the preset processes in the management backend), and have the same restrictions as the parent department (use the approval process settings used by the upper level department). Babel document approval has the following characteristics: Department members can initiate approval by right clicking on the document to be approved More Options Open Approval. The finalized approval document can be exported to the approval report. Approvals can be managed in the \"My Approvals\" column on the left sidebar. The status of the document that has passed the approval will change to \"Finalized\". The finalized document can be updated to the \"To Be Started\" status, and the approval can be started again. Right click on multiple files and select Open Approval to approve multiple files at the same time. It is allowed to invite external members to approve documents. When filling in the approver, just enter the email or mobile phone number of the external member. 32. What is the difference between upload permission and upload only permission? In addition to uploading a new file, uploading also means that you can upload a new version over the original file. Babel's \"overwriting\" does not destroy the old file, but adds a new version to the old file as the current version. So the upload permission includes the permission to upload new versions. In BabelBird's permission system, uploading files includes the meaning of uploading new versions of other people's files. For example, if a share created by someone else gives you upload permission, it means that in addition to uploading files, you can also upload new versions (edit) of other people's files. Only upload permission means that you can only upload your own files, which means that you can upload new files and upload new versions of your own files, but you do not have permission to upload new versions of files uploaded by others (you cannot edit other people's files). 33. Why can’t I see the files uploaded by others? Your department role does not have permission to view files uploaded by others. You can contact your department manager to change your role." }, { "lang": "en", "slug": "faq-sharing", "title": "FAQ: Share, collaborate and notify", "description": "Covers frequently asked questions about sharing, collaboration, and notifications.", "category": "FAQ", "top_category": "常见问题", "keywords": [ "FAQ", "FAQ: Share, collaborate and notify" ], "url": "en/faq-sharing.html", "source": "content/en/faq-sharing.md", "summary": "FAQ: Share, Collaborate and Notify The following questions cover common operations, permissions, collaboration and troubleshooting scenarios when users use BabelBird Enterprise Drive. 34. How do I share a file with others? As long as the files have sharing permissions, they can be shared. Right click the file that needs to be shared and select \"Share\" to share it. You can also click the sharing shortcut when the mouse is over the file/folder to share it. An authorization window will pop up for files without sharing permissions. You can follow the window guidance to submit a sharing application. After approval by a member or administrator with file management permissions or the file creator o", "headings": [ { "level": 1, "title": "FAQ: Share, Collaborate and Notify", "id": "faq-share-collaborate-and-notify" }, { "level": 2, "title": "34. How do I share a file with others?", "id": "34-how-do-i-share-a-file-with-others" }, { "level": 2, "title": "35. How do I view files that others have shared with me?", "id": "35-how-do-i-view-files-that-others-have-shared-with-me" }, { "level": 2, "title": "36. What is the difference between invitation sharing and link sharing?", "id": "36-what-is-the-difference-between-invitation-sharing-and-link-sharing" }, { "level": 2, "title": "37. How to change my default avatar?", "id": "37-how-to-change-my-default-avatar" }, { "level": 2, "title": "38. I want to receive prompt notifications after my colleagues update files. How do I do this?", "id": "38-i-want-to-receive-prompt-notifications-after-my-colleagues-update-files-how-do-i-do-this" }, { "level": 2, "title": "39. Some files or folders have a \"control\" icon behind their icons. What does it mean?", "id": "39-some-files-or-folders-have-a-control-icon-behind-their-icons-what-does-it-mean" }, { "level": 2, "title": "40. Why can’t my newly uploaded files be searched?", "id": "40-why-can-t-my-newly-uploaded-files-be-searched" }, { "level": 2, "title": "41. Why does the folder size not show in the file list?", "id": "41-why-does-the-folder-size-not-show-in-the-file-list" }, { "level": 2, "title": "42. Why can’t the folder I uploaded overwrite the folder with the same name, but the file can?", "id": "42-why-can-t-the-folder-i-uploaded-overwrite-the-folder-with-the-same-name-but-the-file-can" }, { "level": 2, "title": "43. Why does my file prompt that it is locked?", "id": "43-why-does-my-file-prompt-that-it-is-locked" }, { "level": 2, "title": "44. How to unlock locked files?", "id": "44-how-to-unlock-locked-files" }, { "level": 2, "title": "45. How to roll back a file version?", "id": "45-how-to-roll-back-a-file-version" }, { "level": 2, "title": "46. ​​What is dynamics?", "id": "46-what-is-dynamics" }, { "level": 2, "title": "47. Can I search for updates?", "id": "47-can-i-search-for-updates" }, { "level": 2, "title": "48. What is a discussion group?", "id": "48-what-is-a-discussion-group" }, { "level": 2, "title": "49. What is a workbench? How to use the workbench?", "id": "49-what-is-a-workbench-how-to-use-the-workbench" }, { "level": 2, "title": "50. I don’t want to be harassed by too many dynamic messages, what should I do?", "id": "50-i-don-t-want-to-be-harassed-by-too-many-dynamic-messages-what-should-i-do" } ], "images": [], "text": "FAQ: Share, Collaborate and Notify The following questions cover common operations, permissions, collaboration and troubleshooting scenarios when users use BabelBird Enterprise Drive. 34. How do I share a file with others? As long as the files have sharing permissions, they can be shared. Right click the file that needs to be shared and select \"Share\" to share it. You can also click the sharing shortcut when the mouse is over the file/folder to share it. An authorization window will pop up for files without sharing permissions. You can follow the window guidance to submit a sharing application. After approval by a member or administrator with file management permissions or the file creator or person in charge, the sharing will be automatically sent to the invitee or the link to the requested file will be opened for sharing. 35. How do I view files that others have shared with me? In the left column of BabelBird, there is a column called \"Shares I added\". All the shares you added to other people's shares while logged in can be displayed uniformly in this column. In the same way, you can also click on the \"My Sharing\" column to view all the files you have opened for sharing. 36. What is the difference between invitation sharing and link sharing? There are two forms of BabelBird sharing, invitation sharing and link sharing. The difference is: To invite sharing, you must identify the sharing target. You need to have the email address or mobile phone number of the sharing target to share. Anyone who is not registered with BabelBird and receives an invitation to share needs to authenticate to access the file/folder that invited him or her. Identity verification is to use the email or mobile phone number you received the invitation (private deployment requires opening the SMS interface). You can only access after receiving the verification code and verifying it. The invitation initiator can freely set the access permissions and validity period of the invitee, and view the access log The invitation initiator can turn off an invitee's permission to view the shared content to interrupt sharing. Link sharing does not require authentication, but you can set a sharing password Anyone who receives the link share can open the share and view the file (anonymity is supported) When the link sharing settings do not allow anonymous access, anonymous users cannot access the link. To share a link, you need to copy and share the link and send it to the people you want to share it with. If link sharing is turned off, everyone with the link will not be able to access it. If you change the permissions for link sharing, the permissions of everyone who owns the link will also change. 37. How to change my default avatar? To modify the default avatar, click the avatar icon in the upper right corner and click Settings in the drop down menu. Click the Modify Avatar button in the settings to upload the avatar you want to modify. On the mobile APP, you can click \"My\" on the bottom bar, click on the avatar at the top, and click on the \"Avatar\" column to modify it. 38. I want to receive prompt notifications after my colleagues update files. How do I do this? BabelBird can send update notifications to relevant members when files are updated. In order to prevent excessive notification information from causing harassment, only files that users pay attention to will send update notifications to users. Click Reminder to Follow under the file that you need to be notified of when it is updated, and select yourself as the follower. Select yourself in the reminder attention list and confirm it to take effect. In the future, whenever a colleague updates this file or folder, you will receive a bell notification. 39. Some files or folders have a \"control\" icon behind their icons. What does it mean? It means that the file has been subject to \"file access control\", and the operation permissions on the file may be different from the default permissions of the role. 40. Why can’t my newly uploaded files be searched? Babel supports full text search, but it requires time and server resources to index search targets. In order to save server performance, the Babel search engine will index files every 30 minutes. Therefore, it takes up to 30 minutes for newly uploaded files to be searched in search engines. The text in some files is embedded in the document in the form of graphics or pictures (such as PDF scans). The content of such files cannot currently be searched. 41. Why does the folder size not show in the file list? The structure of the folder is uncontrollable. The folder hierarchy may be complex and the number of files may be large. Counting the sizes of massive folders will greatly waste server resources and cause slow loading of file lists. Therefore, the size of the folder is not displayed in the list (in fact, the Windows System Resource Manager does not display the size of the folder for the same reason). To check the size of a folder, right click \"View Details\" and the size of the folder can be counted on the details page. 42. Why can’t the folder I uploaded overwrite the folder with the same name, but the file can? When BabelBird uploads a file with the same name, it will prompt whether to generate a new version of the original file or upload it with a new name. After the file is modified on the synchronization end or the mapping disk, the file will be automatically uploaded as a new version. However, BabelBird does not support uploading a folder with the same name for overwriting or generating a new version of the file in the target folder. Therefore, using BabelBird to upload a folder with the same name will automatically add a suffix to the folder name as a distinction. This is a setting made to increase server efficiency, because folders can theoretically have infinite levels. Uploading a folder with a fairly complex structure may cause the system to freeze. Currently, mainstream enterprise network disks do not support folder upload and coverage. 43. Why does my file prompt that it is locked? When you use the BabelBird client to edit a document, the document is automatically locked to prevent other collaborating users from editing at the same time and causing version conflicts. If there is a lock mark on your file, it means that someone is editing the file and it is locked. Files will not be locked using the online office editing module. A locked file will be automatically unlocked if there is no content update within 30 minutes after the editor completes editing. It can also be unlocked manually. 44. How to unlock locked files? When you use the BabelBird client to edit a document, the document is automatically locked to prevent other collaborating users from editing at the same time and causing version conflicts. If there is a lock mark on your file, it means that someone is editing the file and it is locked. Only file editors and people with file management permissions (such as department managers) can manually unlock locked files. People with unlocking permissions right click the locked file and select \"Unlock File\". 45. How to roll back a file version? BabelBird supports historical version management and rollback of files. A file with a version mark in the lower right corner of the file icon means there are multiple versions. Right click the file and open \"View Version\" in the menu to view the version information of the file. Click the file icon or thumbnail in the version information to preview that version of the file. Click the \"Set as current version\" button to roll back the historical version to the current version. After the rollback operation, everyone who wants to access the file will open the current version of the file. 46. ​​What is dynamics? Dynamics is a streaming list in BabelBird used to display user related files and department updates. Use dynamics to intuitively understand what is happening to members, files, departments, and projects related to you throughout the enterprise. Dynamic information includes file upload, download, update, deletion and other information; file comments and discussion content; other members @you information. Comments and discussion messages within the dynamic can be replied to directly in the dynamic list. Dynamic information is usually kept for three months. 47. Can I search for updates? The search box on the right side of the top of the dynamic column is a dynamic search box, which can search for dynamic content. 48. What is a discussion group? The discussion group is equivalent to a group chat organized by department and project. Each project, department, or team (professional version) has its own discussion group. You can enter text in the discussion group for group chat. A discussion group is automatically created every time a department or project is created. Members who join a project or department automatically join that project or department's discussion group. You can view all discussion groups you have joined in the discussion group section. Discussion groups support sending files. 49. What is a workbench? How to use the workbench? The workbench is a column in BabelBird. It organizes and displays the columns and file lists that the user is interested in in the form of cards. The display content of the workbench can be customized. Proper use of the workbench can serve as an entrance to view files and manage work from more dimensions. The workbench can be customized, and each user can customize his own workbench according to his own needs. Cards on the workbench can be sorted by dragging them. Press and hold the mouse on the top of the card and drag to sort the cards as needed. If you feel that the content of the card is not displayed enough, you can click the more icon (three dots) on the upper right side of the card and select the \"More\" option to open more content of the card in a new window. Cards can be deleted by clicking on the more icon (three dots) on the upper right side of the card and selecting the \"Remove Card\" option to remove the card. Card removal does not affect the data displayed by the card. Click the Add Cards button to add more cards as needed. There are 17 card chart types available, and you can also customize a folder to be accessed as a card in the workbench. 50. I don’t want to be harassed by too many dynamic messages, what should I do? When you open the client, dynamic information will appear in the lower right corner in the form of a pop up window. If you need to turn off the dynamic information you do not want to receive, you can click the avatar Settings Notification settings, set it in the dynamic notification settings, and select the type of dynamic notifications you want to receive." }, { "lang": "en", "slug": "faq-sync", "title": "FAQ: Synchronization, client and mapped disk", "description": "Covers common issues related to synchronization, clients and mapped disks.", "category": "FAQ", "top_category": "常见问题", "keywords": [ "FAQ", "FAQ: Synchronization, client and mapped disk" ], "url": "en/faq-sync.html", "source": "content/en/faq-sync.md", "summary": "FAQ: Synchronization, client and mapping disk The following questions cover common operations, permissions, collaboration and troubleshooting scenarios when users use BabelBird Enterprise Drive. 51. What is a mapping disk? What is the difference between synchronization and synchronization? After installing the BabelBird client, there will be a BabelBird mapping disk in the resource manager. After clicking it, you can access all the files that can be accessed within your permissions. The file contents in the mapped disk are not actually on your computer, but are mapped to your computer through the network. You still need to download these files to use them. The advantage of a mapped disk is t", "headings": [ { "level": 1, "title": "FAQ: Synchronization, client and mapping disk", "id": "faq-synchronization-client-and-mapping-disk" }, { "level": 2, "title": "51. What is a mapping disk? What is the difference between synchronization and synchronization?", "id": "51-what-is-a-mapping-disk-what-is-the-difference-between-synchronization-and-synchronization" }, { "level": 2, "title": "52. Why can't I synchronize newly added files or not synchronize the latest file versions?", "id": "52-why-can-t-i-synchronize-newly-added-files-or-not-synchronize-the-latest-file-versions" }, { "level": 2, "title": "53. Why do I get the message that several files were not synchronized successfully during synchronization?", "id": "53-why-do-i-get-the-message-that-several-files-were-not-synchronized-successfully-during-synchronization" }, { "level": 2, "title": "54. What are the permissions related to synchronization?", "id": "54-what-are-the-permissions-related-to-synchronization" }, { "level": 2, "title": "55. I deleted a file locally when synchronizing files. Will it still be there in the cloud?", "id": "55-i-deleted-a-file-locally-when-synchronizing-files-will-it-still-be-there-in-the-cloud" }, { "level": 2, "title": "56. During synchronization, if I delete a file in the cloud, will it still be there locally?", "id": "56-during-synchronization-if-i-delete-a-file-in-the-cloud-will-it-still-be-there-locally" }, { "level": 2, "title": "57. Can several people in our department synchronize a certain folder at the same time?", "id": "57-can-several-people-in-our-department-synchronize-a-certain-folder-at-the-same-time" }, { "level": 2, "title": "58. If I delete a file on the mapped disk, will it still be there in the cloud?", "id": "58-if-i-delete-a-file-on-the-mapped-disk-will-it-still-be-there-in-the-cloud" }, { "level": 2, "title": "59. Why can’t I drag files on my mapped disk to WeChat and send them?", "id": "59-why-can-t-i-drag-files-on-my-mapped-disk-to-wechat-and-send-them" }, { "level": 2, "title": "60. Why can’t I find my mapping disk?", "id": "60-why-can-t-i-find-my-mapping-disk" }, { "level": 2, "title": "61. Why can some files in my synchronized folder be synchronized, but some cannot?", "id": "61-why-can-some-files-in-my-synchronized-folder-be-synchronized-but-some-cannot" }, { "level": 2, "title": "62. Why can I edit some files in the department but not others?", "id": "62-why-can-i-edit-some-files-in-the-department-but-not-others" }, { "level": 2, "title": "63. I am a super administrator, why can’t I see the dynamics of some departments?", "id": "63-i-am-a-super-administrator-why-can-t-i-see-the-dynamics-of-some-departments" }, { "level": 2, "title": "64. I am a super administrator, why do files appear in the Recycle Bin after I empty it?", "id": "64-i-am-a-super-administrator-why-do-files-appear-in-the-recycle-bin-after-i-empty-it" } ], "images": [], "text": "FAQ: Synchronization, client and mapping disk The following questions cover common operations, permissions, collaboration and troubleshooting scenarios when users use BabelBird Enterprise Drive. 51. What is a mapping disk? What is the difference between synchronization and synchronization? After installing the BabelBird client, there will be a BabelBird mapping disk in the resource manager. After clicking it, you can access all the files that can be accessed within your permissions. The file contents in the mapped disk are not actually on your computer, but are mapped to your computer through the network. You still need to download these files to use them. The advantage of a mapped disk is that it does not occupy the local storage space of your computer, and only the files you use need to be downloaded and cached. At the same time, the disadvantage is that the mapped disk needs to be connected to the network to be used. Since the files inside are all in the cloud, the file icons you see are just shortcuts to the cloud files, so dragging the mapped disk files to the local disk directory is not supported. After installing the client, if you select a folder on the local disk, right click, select BabelBird, and then select Sync to BabelBird. At this time you have created a sync folder. The content in the synchronized folder will be automatically synchronized to the cloud. If the content in the cloud is updated (other people have synchronized this folder to their computer and uploaded files), the content in your folder will also be updated. The advantage of synchronization is that after synchronization, the files are downloaded locally and you can directly perform various operations. You can use and access the synchronization folder even without a network. If you are connected to the network, the updated content will be automatically synchronized. The disadvantage of synchronization is that it takes up local hard disk space, and because files need to be downloaded and updated, the real time performance of synchronization is not as good as that of the mapped disk. 52. Why can't I synchronize newly added files or not synchronize the latest file versions? What you are synchronizing should be files within the department. There are several possibilities: You do not have file upload permission in the synchronized folder The file you want to synchronize is in a folder you created locally, but you do not have permission to create a new folder. The file you want to synchronize is set to a file type that does not require synchronization The file type you want to synchronize is in the file blacklist and is not allowed to be uploaded. The size of the file you want to synchronize exceeds the maximum limit for a single file that can be uploaded The total size of the files you want to synchronize exceeds the department space limit The files you want to synchronize are file types that are prohibited from synchronization by BabelBird, such as files with tmp, swp, and lock as suffixes. If it is determined that none of the above reasons are the cause, you can try the following solutions one by one: Rename the files that have not been updated, and then change them back to their original names after the synchronization is successful. Move unsynchronized files out of the sync folder and wait until the synchronization status shows synchronized before moving them in. Find the synchronized items in the synchronization management, right click, and reset synchronization. Restart client If you still can't solve it, please contact our customer service staff. 53. Why do I get the message that several files were not synchronized successfully during synchronization? When synchronizing many files, occasionally some files will prompt \"Unsuccessful synchronization\". Generally, the files that cannot be successfully synchronized fall into the following categories: The file name of this file has special characters or is irregular. In order for BabelBird to be compatible with MAC, Linux, and Windows file systems at the same time, the file name rules need to be compatible with these systems. This results in files whose file names contain special characters, Chinese commas and other characters being unable to be synchronized. Solution: Modify the file name of the file that needs to be synchronized. The file is corrupted or the hash check fails. BabelBird has an instant transfer module, which will analyze the hash code of the file when the file is uploaded. Due to damage, format and other reasons, the hash code of some files cannot be read, causing synchronization failure. Solution: Re edit or export the file or upload the file into a zip package. The file is too large. BabelBird can stably support the upload of a single file up to 8G. When uploading files exceeding this size, 100% success rate cannot be guaranteed. Solution: Change the file to a smaller size or retry synchronization multiple times. The file is occupied by some application. Sometimes, certain applications restrict files from being read or copied, which can cause synchronization to fail. Solution: Restart the operating system and synchronize again, or find the application that opens the file and close it. The file is in the process of being written. Synchronization may also fail while the file is being written. Solution: Wait for the file to be saved before synchronizing or uploading it. The files are on other network drives. Synchronizing files that are not local can easily cause network errors, causing synchronization to fail or become unresponsive. Solution: Copy the file or folder to the local disk and then synchronize it. Use VPN to circumvent firewalls or network problems. VPN circumvention can easily cause the computer's local clock to be abnormal. Clock abnormalities can lead to synchronization failure or unknown problems. Solution: If the clock and server time do not match, please adjust the time and time zone on the computer and use the time in the time zone of the server. If it is not a clock problem, it may be a network abnormality caused by the VPN. Turn off the VPN, disconnect the network connection and try again (turn off the network card or wifi and then turn it on). 54. What are the permissions related to synchronization? If you are in a department and want to synchronize a folder in the department files, the permissions related to synchronization are: Upload files (synchronously upload local files) Download your own files Download other people's files Move your own files Move someone else's files Delete your own files Delete other people's files Create folder Only people with the above roles can perform complete synchronization. If a certain permission is missing, a certain operation during synchronization is missing. At the same time, if the synchronized folder has been set up with \"File Access Control\", the settings in File Access Control will prevail. 55. I deleted a file locally when synchronizing files. Will it still be there in the cloud? If you have full editing permissions (upload, download, delete) in the cloud sync folder, and you delete a file locally or move a file outside the sync folder, the corresponding file in the cloud sync folder will also be deleted. But this deleted file will be in BabelBird's Recycle Bin, where it can be found and restored. 56. During synchronization, if I delete a file in the cloud, will it still be there locally? If you have full editing permissions (upload, download, delete) in the cloud sync folder, and you delete a file in the cloud or move a file outside the sync folder, the corresponding file in the local sync folder will also be deleted. But the deleted file will be in BabelBird's recycle bin and can be restored. 57. Can several people in our department synchronize a certain folder at the same time? Yes, BabelBird supports multiple people to synchronize the same cloud folder. At the same time, if multiple users synchronizing the same folder have the same permissions, the files in the local synchronized folders of several users will be consistent. 58. If I delete a file on the mapped disk, will it still be there in the cloud? If you have the permission to delete files and you delete a file in the mapped disk, the cloud will delete it in real time. But there will be in the recycle bin. If you do not have permission to delete the file, the system will prompt you that you do not have permission to delete the file. 59. Why can’t I drag files on my mapped disk to WeChat and send them? In windows mapped disk, due to resource manager limitations, only cached files can be dragged. In the Mac mapped disk, files that are not cached can also be dragged into WeChat, where they will be automatically cached and sent. However, since WeChat's window capture does not support dragging network files, if the file exceeds the 10MB WeChat file sending limit, there is a high probability that unpredictable problems will occur (window deadlock). This is difficult to solve if Mac WeChat does not support it, and it is also a bug of WeChat. Apple iCloud simply does not support dragging uncached files to WeChat to avoid this problem. 60. Why can’t I find my mapping disk? Because the mapped disk needs to obtain the underlying permissions of the operating system, it is easily restricted by the operating system and cannot be accessed. The current version has solved this problem very well, but under some anti virus software or operating systems, problems such as the mapped disk cannot be found and the file icons in the mapped disk are incorrectly displayed may still occur. Solution: Put the BabelBird client into the whitelist of the firewall or anti virus software, uninstall and reinstall the BabelBird client with operating system administrator rights, follow the prompts and allow it to be blocked by the anti virus software or firewall. 61. Why can some files in my synchronized folder be synchronized, but some cannot? If some files in a synchronized folder cannot be synchronized, there are generally the following possibilities: You do not have the permission to download these files and cannot synchronize these files to the local computer (two permissions to download your own files and download other people's files) You do not have upload permissions for the sync folder or some folders in the sync folder. You cannot synchronize edited content and new files to the cloud. You do not have \"Create Folder\" permission in the department, and there are newly created folders in the local folder you want to synchronize. The size of the files you synchronize exceeds the single file upload size limit (please consult the administrator or BabelBird customer service for the single file size limit) Some file types are set as file types that do not require synchronization Some file types are in the file blacklist and are not allowed to be uploaded. If it is determined that none of the above reasons are the cause, you can try the following solutions one by one: Rename the files that have not been updated, and then change them back to their original names after the synchronization is successful. Move unsynchronized files out of the sync folder and wait until the synchronization status shows synchronized before moving them in. Find the synchronized items in the synchronization management, right click, and reset synchronization. Restart client If you still can't solve it, please contact our customer service staff. 62. Why can I edit some files in the department but not others? You do not have permission to edit the file. It is possible that your role in the department does not have the permission to \"edit other people's files\" and the creator of this file is not you. Or the file has file permission controls that prohibit editing. Files cannot be edited while locked. If the \"File Owner\" mode is turned on, non persons in charge cannot edit the file. 63. I am a super administrator, why can’t I see the dynamics of some departments? The super administrator can see the department folders of the entire company for management purposes, but the super administrator cannot see the dynamics of departments that he has not joined. In order to prevent a large amount of information harassment, BabelBird is set to push only the updates of the department, project, and sharing of the members. If the super administrator wants to see the dynamics of a certain department, he can add himself to that department. 64. I am a super administrator, why do files appear in the Recycle Bin after I empty it? BabelBird's recycling bin is a multi level recycling bin. In order to facilitate management, it is managed uniformly in the \"Recycle Bin\" at the front desk. The setting of multi level recycle bin is that department files deleted by department members can also be seen in the recycle bin of department managers and super administrators. Department files deleted by the department manager also exist in the super administrator's recycle bin. This mechanism can avoid the vicious event of \"deleting the database and running away\" to the greatest extent. However, because the super administrator also has a corresponding role in the department, and may even be the project manager of a certain department at the same time, this will cause a phenomenon: the super administrator empties the recycle bin (as a department member or department manager), and the files disappear, but if refreshed again, there will still be these files in the recycle bin (as seen by the super administrator). Therefore, the super administrator needs to operate twice to completely delete a department file. This setting is indeed a bit unsatisfactory. We have also noticed this problem and will correct it in future iterations." }, { "lang": "en", "slug": "faq-projects", "title": "FAQ: Department Management, Projects and Collection Documents", "description": "Covers FAQs related to department management, projects and collecting documents.", "category": "FAQ", "top_category": "常见问题", "keywords": [ "FAQ", "FAQ: Department Management, Projects and Collection Documents" ], "url": "en/faq-projects.html", "source": "content/en/faq-projects.md", "summary": "FAQ: Department Management, Projects and Collection Documents The following questions cover common operations, permissions, collaboration and troubleshooting scenarios when users use BabelBird Enterprise Drive. 65. How does the department manager add new members? There are two ways for department managers to add new members: Department managers can select some members from existing corporate members to join the department they manage. Here's how it works: Right click on the department folder you manage and select \"Manage Department Members\" in the department management interface. Select the \"Add from internal members\" button on the department member management interface In the pop up window,", "headings": [ { "level": 1, "title": "FAQ: Department Management, Projects and Collection Documents", "id": "faq-department-management-projects-and-collection-documents" }, { "level": 2, "title": "65. How does the department manager add new members?", "id": "65-how-does-the-department-manager-add-new-members" }, { "level": 2, "title": "66. How does the department manager change the permissions of department members?", "id": "66-how-does-the-department-manager-change-the-permissions-of-department-members" }, { "level": 2, "title": "67. How does the department manager check which files in the department have been shared?", "id": "67-how-does-the-department-manager-check-which-files-in-the-department-have-been-shared" }, { "level": 2, "title": "68. There is a file/folder in the department that I don’t want some people to see. What should I do?", "id": "68-there-is-a-file-folder-in-the-department-that-i-don-t-want-some-people-to-see-what-should-i-do" }, { "level": 2, "title": "69. I want people in our department to use BabelBird only on department computers. How to do this?", "id": "69-i-want-people-in-our-department-to-use-babelbird-only-on-department-computers-how-to-do-this" }, { "level": 2, "title": "70. Does Babel support one user in multiple departments?", "id": "70-does-babel-support-one-user-in-multiple-departments" }, { "level": 2, "title": "71. To temporarily establish a project team, it is necessary to transfer personnel from various departments of the company and share files. How to operate?", "id": "71-to-temporarily-establish-a-project-team-it-is-necessary-to-transfer-personnel-from-various-departments-of-the-company-and-share-files-how-to-operate" }, { "level": 2, "title": "72. Why can’t I create a project in a department?", "id": "72-why-can-t-i-create-a-project-in-a-department" }, { "level": 2, "title": "73. There is a file in the department that I want to show to people in other departments, but I don’t want to invite them one by one. What should I do?", "id": "73-there-is-a-file-in-the-department-that-i-want-to-show-to-people-in-other-departments-but-i-don-t-want-to-invite-them-one-by-one-what-should-i-do" }, { "level": 2, "title": "74. I want to collect some materials from various departments. How do I do this?", "id": "74-i-want-to-collect-some-materials-from-various-departments-how-do-i-do-this" }, { "level": 2, "title": "75. I want to send a file to everyone in the company so that they can view it, but it cannot be downloaded. How do I do this?", "id": "75-i-want-to-send-a-file-to-everyone-in-the-company-so-that-they-can-view-it-but-it-cannot-be-downloaded-how-do-i-do-this" }, { "level": 2, "title": "76. How to use BabelBird to quickly collect user files?", "id": "76-how-to-use-babelbird-to-quickly-collect-user-files" }, { "level": 2, "title": "77. The content in the sharing I sent to my customers is incorrect, what should I do?", "id": "77-the-content-in-the-sharing-i-sent-to-my-customers-is-incorrect-what-should-i-do" }, { "level": 2, "title": "78. I don’t want customers to download the files I share, but they can view them. What should I do?", "id": "78-i-don-t-want-customers-to-download-the-files-i-share-but-they-can-view-them-what-should-i-do" }, { "level": 2, "title": "79. I want to send files on BabelBird to contacts in WeChat. How do I do this?", "id": "79-i-want-to-send-files-on-babelbird-to-contacts-in-wechat-how-do-i-do-this" }, { "level": 2, "title": "80. Can I directly access BabelBird’s files using WeChat Business/DingTalk?", "id": "80-can-i-directly-access-babelbird-s-files-using-wechat-business-dingtalk" } ], "images": [], "text": "FAQ: Department Management, Projects and Collection Documents The following questions cover common operations, permissions, collaboration and troubleshooting scenarios when users use BabelBird Enterprise Drive. 65. How does the department manager add new members? There are two ways for department managers to add new members: Department managers can select some members from existing corporate members to join the department they manage. Here's how it works: Right click on the department folder you manage and select \"Manage Department Members\" in the department management interface. Select the \"Add from internal members\" button on the department member management interface In the pop up window, select the member who needs to join the department, and pay attention to the department role of the member to be added. After clicking OK, the selected members will automatically join this department. Members who join the department will also receive an email notification. If the department manager has the \"Add Corporate Members\" permission, the department manager can add corporate members in the department member management interface. This operation will add an enterprise member (occupying the number of enterprise member authorizations) to the department. The specific operation is as follows: Right click on the department folder you manage and select \"Manage Department Members\" in the department management interface Select the \"Add Member\" button on the department member management interface, and then fill in the email address, mobile phone number and other information of the new member you plan to add. After clicking OK, the system will send an invitation email or a mobile phone text message to the member's mailbox. Follow the instructions in the email or text message to log in and change the password to use. 66. How does the department manager change the permissions of department members? Department managers can change the role (permission set) of any department member. The roles are set uniformly by the super administrator. Department managers of each department can select corresponding roles for their department members from the preset roles in the enterprise console. Department managers cannot create new roles. If you need to create new special role permissions, you need to contact the super administrator, who will add a new role in the enterprise console. Department managers can query the role permissions to understand the specific permissions of each preset role, so as to decide which roles to assign to department members. Typically, department members using the default \"Department Member\" role will meet most needs. There are two steps to change the department role of department members: View the role's permissions. Right click on the department folder you manage and select \"Manage Department Members\" in the department management interface In the department member management interface, click the question mark icon to the right of \"Role\" This will expand the list of role permissions for the entire enterprise. You can view the permissions of each role in the list. Change a department member's role In the role area, click the inverted triangle of the department member whose role you want to change, and select the required role in the drop down list to change the member's role in the department. 67. How does the department manager check which files in the department have been shared? Right click on the department folder for which you have administrative rights, click Department Management in the menu, and click to open the shared file list in the pop up interface. You can see the shared files of the entire department, including sub departments. 68. There is a file/folder in the department that I don’t want some people to see. What should I do? A role with department file management permissions (usually a department manager) can use the \"File Access Control\" function to set the access permissions for a file/folder in the department to redefine the access permissions for the file. Right click the department folder where permission control needs to be set and select the \"File Access Control\" column In the file access control pop up window, you can control the access permissions of specific people or groups to the file/folder based on the dimension of members or roles. Selecting \"Don't set\" means not changing the member's access rights. If a department member's access permission to the file/folder is set to \"invisible\", the department member will not be able to see the file/folder in the department folder. Click \"Role Permission Settings\" to change the file access control for department members in a certain role. 69. I want people in our department to use BabelBird only on department computers. How to do this? This requirement requires the use of the \"mac address binding\" function. Only super administrators can set mac address binding. Super management can set the account of a specific user to access the device's mac address in the enterprise console mac address binding column. After binding the mac address, turn on the mac address binding switch. The account can only use the Babel client on the computer where the mac address is located, and the use of web pages and apps is not restricted. Then turn on the client access only switch. The account bound to the mac address cannot use the web page or mobile phone to log in, and can only use the client to access BabelBird on the computer where the mac address is located. (Due to limitations of the iOS system and browser, we cannot obtain the mac address of the device on the web page and iPhone, so devices bound to the mac address are only available to clients of Windows and Mac devices) 70. Does Babel support one user in multiple departments? Yes, administrators can click on member nicknames in the member management column of the enterprise management backend to add members to multiple departments, and set different roles in different departments. Department managers can also select other members within the company to join their department in the department member management interface of their department. 71. To temporarily establish a project team, it is necessary to transfer personnel from various departments of the company and share files. How to operate? It is recommended to use Babel's \"Project Folder\" to complete. You can create a personal project in the \"Personal Files\" root column, or you can create a project under your department (only roles with the permission to create folders/projects can create department projects). Personal projects belong to the creator, and department projects belong to the department. The department manager can view and manage the content under the department project, regardless of whether the project was created by the department manager or whether the department manager belongs to the project. Both personal projects and department projects can invite internal members or external personnel of the entire enterprise, or mobile phones or email addresses that are not registered with BabelBird to join. The project folder has the following characteristics: Projects have a validity period, after which project members will no longer be able to see the project. The project leader can change the validity period of the project midway. At the same time, the project can set the validity period of project members respectively. After the validity period of the project member's permission expires, the project member will not be able to access the project, but the files uploaded by the member in the project will be retained. Both the project leader and the project itself can be transferred. Individual projects can also be transferred to departments or other individuals through transfer, and department project leaders can also be transferred to other departments or other members. If the project is transferred to another department, project ownership and project management rights will also be transferred. The permissions of personnel within the project are not affected by department roles (except for roles with department file management permissions). The project leader can arbitrarily change the permissions of project members in the project and set the deadline for project members to access the project. However, in departmental projects, roles with \"Department File Management\" permissions (usually department managers) can access the project without being subject to project permissions. Project creators and project leaders can invite any member within the enterprise to join the project. It also supports inviting external members to join the project. The project has an independent project discussion group where group chats can be held. Department projects can only be created in the department root directory (for ease of management) and cannot be created in other folders of the department. Personal projects can only be created in the root directory of \"Personal Files\" and cannot be created in other personal folders. The project supports creating subprojects. Sub projects can have independent project management permissions and project leaders. Members of the parent project can view the content of the sub project, and the permissions follow the parent project. Click on the person's avatar in the discussion group to view the list of files uploaded by the person in the project. After the project is created, it will be displayed in the \"My Projects\" root directory of project members. Project members can access the project in the My Project section. You can also view the projects you have joined or managed in the My Projects column. How to set up a project: Click the New button in the upper left corner in the blank space where a project can be created (personal projects are created in the root directory of \"Personal Files\", department projects are created in the root directory of the department folder), select the New Project button, and follow the guidance to create the project and add project members. After members are added, they will receive a notification to join the project and can access the project in the \"My Projects\" column. 72. Why can’t I create a project in a department? You are trying to create a project in a normal folder (yellow folder) without creating the project in the department root. You do not have permission to create projects in the department. If you need to manage a project, you can contact the department manager, who will create the project and set you as the project leader. You can also create a personal project under \"Personal Files\". 73. There is a file in the department that I want to show to people in other departments, but I don’t want to invite them one by one. What should I do? Right click the file/folder you want to share select Share, and click the \"Add from corporate member list or group\" button in the invitation sharing. Click the company member column, find the department you want to share, click in front of the name of the department you want to share, add the department to the list, and click \"Send\". If you need to invite certain members from different departments, you can add these members to a group (click Settings in the inverted triangle of your personal avatar, find the group management column, and create a new personal private group for personal use; the super administrator can create an enterprise public group, which can be used by the entire enterprise), and just invite the group when inviting. 74. I want to collect some materials from various departments. How do I do this? It is recommended to use the inbox function of BabelBird. Enter the directory where you need to save these materials and click the \"New\" button in the upper left corner. Select \"Inbox Collection within the organization\" to open the inbox creation interface. Fill in the corresponding information and select the colleagues (submitters) who need to submit materials and click \"Create\" to create an inbox folder. At the same time, the system will send a submission notification to the submitter you selected. After clicking on the notification, the submitter can enter the drop box and upload files as required. The collection inbox within the organization has the following features: Submitters must log in before they can upload files Before the deadline, submitters can upload and edit their own files and upload new versions. After the deadline expires, submitters will not be able to upload files or modify submitted files. The sender cannot see other files except the files uploaded by himself (except files uploaded by the recipient) Another type of inbox is an open inbox. The open inbox will generate a link, and you can distribute the link. Anyone who knows the link can upload files without registering. 75. I want to send a file to everyone in the company so that they can view it, but it cannot be downloaded. How do I do this? Right click on this file, select Share, and click the \"Add from corporate member list or group\" button in the invitation sharing. Click on the company members column, find the root department of the organizational structure (usually your company name), click on the company name to add it to the list, set the permissions in the permission list on the right to \"can view\", and then click the send button at the bottom. 76. How to use BabelBird to quickly collect user files? For quick collection of files, Babel launched the inbox function. Click New Inbox in the directory where the collected files need to be placed. If you need to collect files from external users (non registered users), choose open collection. After clicking Next to perform relevant settings (set the validity period, upload the form content that needs to be filled in), a collection link and QR code will be formed. You can send this link and QR code to the corresponding users (in the group or public channels), and they can click and fill in a form to upload the file. If you want to collect within the enterprise, select within the organization. Members of the designated list will receive a notification and click to enter to upload the file. The target audience of the inbox can only see the recipient and the files uploaded by themselves, but not the files uploaded by other senders. Recipients can see everyone's uploaded files. 77. The content in the sharing I sent to my customers is incorrect, what should I do? You just need to directly modify the contents of the files or folders you share, or upload a new version. Customers who view your files only through the link sharing address will only see the latest version of the file. As long as you modify the file, all users who preview the file you share will see the latest version of the file. But if you give the sharing recipient the \"download file\" permission and the other party downloads the source file, the content that the other party has downloaded cannot be changed. 78. I don’t want customers to download the files I share, but they can view them. What should I do? When inviting or sharing a link, select \"Can view\" (invitation) or \"Anyone with the link can view\" (link sharing) permission, so that users who receive the invitation or link can only view the file and cannot download it. 79. I want to send files on BabelBird to contacts in WeChat. How do I do this? Use BabelBird APP to send files directly to contacts in WeChat. Find the file you want to send in the BabelBird APP, click the arrow button at the bottom on the right side of the file, and a drop down menu will pop up. Click Share to open the sharing interface. You can choose the sharing method in the sharing interface Among them: Select Copy Link to copy the sharing link to the clipboard. You can paste the sharing link in the business WeChat or DingTalk chat window. Select a WeChat friend and directly select the person to whom you want to send the sharing link in the WeChat friend list. Select WeChat Moments to directly send this sharing link to Moments. Select the QR code to scan the code for your friends to get this link. Select the source file to directly send the source file (not the link, but the source file of the file itself, which is equivalent to downloading the file) to the contact in the third party application. If you choose Enterprise WeChat, the system will automatically download the file and send it to your selected Enterprise WeChat contact. The source files sent are not subject to permission control, which is equivalent to sending files directly to others. If you want to send a file to someone on WeChat on your computer, you can right click the file you want to share, select \"Share\" Link Sharing, and turn on the open link sharing button. Then click on the QR code logo and scan the code using WeChat on your mobile phone to get the sharing link. After scanning the code, the sharing link will be opened on WeChat. Click the \"...\" more button in the upper right corner, Just select \"Send to a friend\". 80. Can I directly access BabelBird’s files using WeChat Business/DingTalk? Enterprises need to purchase BabelBird’s enterprise WeChat or DingTalk integration services. After activating the enterprise WeChat or DingTalk integration service, enterprise members can see the Babel bird icon on the workbench. Click this icon to access BabelBird, and you can view all the files that can be seen within the user's permissions. However, due to the restrictions on the network disk system of Enterprise WeChat and DingTalk, only limited operations such as preview, download, and sharing can be used." }, { "lang": "en", "slug": "faq-preview-search", "title": "FAQ: Preview, online editing, search and tags", "description": "Covers FAQs related to previewing, online editing, searching, and tagging.", "category": "FAQ", "top_category": "常见问题", "keywords": [ "FAQ", "FAQ: Preview, online editing, search and tags" ], "url": "en/faq-preview-search.html", "source": "content/en/faq-preview-search.md", "summary": "FAQ: Preview, online editing, search and tags The following questions cover common operations, permissions, collaboration and troubleshooting scenarios when users use BabelBird Enterprise Drive. 81. Why can’t I play animation when previewing PPT? BabelBird's PPT is presented in the form of a page and does not support the built in animation and link of PPT. If you want to play PPT animation, you can use the \"online editing\" function to open the PPT and play it (you need to purchase the online editing module), or click the edit button of the file after installing the client. 82. Why can’t BabelBird play some video files? BabelBird only supports the playback of video and audio files according t", "headings": [ { "level": 1, "title": "FAQ: Preview, online editing, search and tags", "id": "faq-preview-online-editing-search-and-tags" }, { "level": 2, "title": "81. Why can’t I play animation when previewing PPT?", "id": "81-why-can-t-i-play-animation-when-previewing-ppt" }, { "level": 2, "title": "82. Why can’t BabelBird play some video files?", "id": "82-why-can-t-babelbird-play-some-video-files" }, { "level": 2, "title": "83. What should I do if the file is accidentally deleted?", "id": "83-what-should-i-do-if-the-file-is-accidentally-deleted" }, { "level": 2, "title": "84. My colleague has resigned, what should I do with his files?", "id": "84-my-colleague-has-resigned-what-should-i-do-with-his-files" }, { "level": 2, "title": "85. There are too many department files. I have uploaded a new file and want a colleague to take a look. How can I make it simple?", "id": "85-there-are-too-many-department-files-i-have-uploaded-a-new-file-and-want-a-colleague-to-take-a-look-how-can-i-make-it-simple" }, { "level": 2, "title": "86. Why does the download folder not respond after a long time when I click to download it?", "id": "86-why-does-the-download-folder-not-respond-after-a-long-time-when-i-click-to-download-it" }, { "level": 2, "title": "87. What is the difference between client editing and online editing?", "id": "87-what-is-the-difference-between-client-editing-and-online-editing" }, { "level": 2, "title": "88. Why is my online editor so slow to open?", "id": "88-why-is-my-online-editor-so-slow-to-open" }, { "level": 2, "title": "89. I want several colleagues to fill in a form together. How should I do this?", "id": "89-i-want-several-colleagues-to-fill-in-a-form-together-how-should-i-do-this" }, { "level": 2, "title": "90. How to view folders in a tree view?", "id": "90-how-to-view-folders-in-a-tree-view" }, { "level": 2, "title": "91. Can I filter out the files I want to find based on conditions?", "id": "91-can-i-filter-out-the-files-i-want-to-find-based-on-conditions" }, { "level": 2, "title": "92. What is a label?", "id": "92-what-is-a-label" }, { "level": 2, "title": "93. How to use the BabelBird tag?", "id": "93-how-to-use-the-babelbird-tag" }, { "level": 2, "title": "94. How does Babel search for tags?", "id": "94-how-does-babel-search-for-tags" }, { "level": 2, "title": "95. Does BabelBird support advanced search?", "id": "95-does-babelbird-support-advanced-search" }, { "level": 2, "title": "96. I want to send files on my computer to my colleagues. Is there any good way?", "id": "96-i-want-to-send-files-on-my-computer-to-my-colleagues-is-there-any-good-way" } ], "images": [], "text": "FAQ: Preview, online editing, search and tags The following questions cover common operations, permissions, collaboration and troubleshooting scenarios when users use BabelBird Enterprise Drive. 81. Why can’t I play animation when previewing PPT? BabelBird's PPT is presented in the form of a page and does not support the built in animation and link of PPT. If you want to play PPT animation, you can use the \"online editing\" function to open the PPT and play it (you need to purchase the online editing module), or click the edit button of the file after installing the client. 82. Why can’t BabelBird play some video files? BabelBird only supports the playback of video and audio files according to Html5 rules, generally H264 video encoding and AAC audio encoding Mp4 files. If the video encoding does not meet the requirements, it cannot be played under H5. However, it can be played after transcoding using transcoding software such as Format Factory. The specific playable file types and browser corresponding rules are as follows: 83. What should I do if the file is accidentally deleted? You can recover accidentally deleted files in the recycle bin. The default retention period of the recycle bin is 60 days. It can also be set by the super administrator in the enterprise console. The setting range can be from 1 day to 999 days. If the file is not in the Recycle Bin, it means that the file has been completely deleted. 84. My colleague has resigned, what should I do with his files? Babel supports one click handover. Super administrators can use the one click handover function to handle the file handover of departing colleagues. Find the resigned colleague in the department member list (right click on the department folder, go to department management) or the member list of the enterprise console. Click on the name to open the member management interface In the transfer file ownership column, click the \"Transfer to\" button Select a transferee in the list and click OK to complete the transfer. After the files are transferred, the permissions and sharing relationships of the departing colleagues on the corresponding files/folders will be transferred to the transferee. This operation is irreversible. 85. There are too many department files. I have uploaded a new file and want a colleague to take a look. How can I make it simple? You can use the reminder to follow or the @ function. Right click on the file, select the \"Remind Attention\" button, and select the colleague you want to remind you to pay attention to. The colleague will receive a reminder notification, and the file will be in the \"My Following\" list on the left column of the member. You can also open file comments and @ this colleague in the comments, he will also receive @ notifications. Remind Follow and @ to only select people who have at least the permission to view the file. If the colleague is not in the list, it means that the colleague does not have access permission to the file. In this case, you can use the invitation sharing form to allow the colleague to read the file. 86. Why does the download folder not respond after a long time when I click to download it? When using a browser to download a folder on BabelBird, you need to package the folder into a ZIP compressed package on the server and then download it. Packaging takes time, so when you click on a folder to download, you need to wait for a while before the download starts. Moreover, in order to save server resources, Babel strictly limits the conditions for folder downloads: browser downloads are not supported for folders with more than 100 files in the folder or folders with a folder capacity greater than 500MB. If you need to download a folder, it is recommended to use the Babel client. The client does not need to be packaged and can directly download large folders, and there is no folder size limit. 87. What is the difference between client editing and online editing? The principle of client side editing is to cache the files on the network locally on the computer, and call the local application to open the edit. When the editing is completed and saved, it will automatically upload and create a new file version in the cloud. This means: To prevent version conflicts, the client does not support several users editing the same file at the same time. Therefore, files edited by the client will be automatically locked to prevent others from editing at the same time. Only after one editor has finished and unlocked can other editors continue editing. Whether the client can edit a file is determined by the computer on which the client is installed. If the computer on which the client is installed has various applications for editing files, theoretically all types of files can be edited using client editing. Because client side editing of files uses local programs to call the computing resources of the local computer, it is faster and has a better experience. The principle of online editing is to directly call the online editing server and open the file for editing in the cloud. This means: Currently, online editing can support office files (word, excel, ppt), wps files, txt files, markdown files, and km files. However, txt files, markdown files, and km files do not support online editing by multiple people at the same time. Because it is edited in real time in the cloud, multiple people can edit the same file at the same time, but it is possible for multiple people to edit at the same time and cause layout confusion. Because you edit in the cloud, many resources need to be cached on the server, which is related to network speed and connection rate, so the speed and experience are not as good as client side editing. Online editing does not require local installation of applications, and can be used by any browser that supports the Html5 specification. 88. Why is my online editor so slow to open? The first time you open an office document for online editing, it will be very slow (because cache files need to be loaded), but the second time you open it in the same browser, it will be much faster. BabelBird uses the office online editing module of Onlyoffice. The main reason why online editing is slow to open is that unlike local editing, online editing needs to transfer files to the cloud editing server and cache the online editor in the browser before editing. The speed of this cache is closely related to the file size and fonts used. The Chinese fonts we commonly use are not small (the average size of a Chinese font package is generally more than 30MB, and an English font package is generally only about 20KB). The more Chinese fonts supported, the slower the cache. This is also a dilemma currently faced by Chinese office online editors. We have optimized the Onlyoffice Chinese font library on BabelBird, but the speed of opening documents is still slower than that of client editing. 89. I want several colleagues to fill in a form together. How should I do this? You can fill out the form with your colleagues using the online editing feature. Upload the form that needs to be edited, remind colleagues to pay attention to the form or @colleagues. See FAQ for details: There are too many department files. I have uploaded a new file and want a colleague to take a look. How can I make it simple? Then right click on the Excel file you want to edit and select \"Online Edit\". At this time, the Excel online editor will open, and you can edit the table in it. If other colleagues also edit the form online, there will be a member prompt in the upper right corner of the Excel editor, and you can also see the content edited by the other party in real time. 90. How to view folders in a tree view? It's easy to view folders in a tree view, just click the \"Folder Directory\" button in the upper right corner of the folder list. After clicking this button, a tree directory will be opened to the left of the file list. 91. Can I filter out the files I want to find based on conditions? Under the folder you want to filter, click the \"Filter\" button on the toolbar in the upper right corner of the file list. You can filter the results under the current folder by a combination of tags, file types, file sizes, file update times, and uploading users. At the same time, the search results obtained using the search function can also be accurately positioned using the filter function. 92. What is a label? Babel supports tagging any files and folders, and Babel's tags are shared tags, which means that when you add a tag to a file, everyone who can access the file can see and use the tag to query the file. This is very useful in many scenarios. For example, you can use tags to classify materials. 93. How to use the BabelBird tag? There is an add tag button below the file name in the document list. Click to add tags. If there is no Add Tag button below the file name, it is likely that the concise file list is turned on. You can select the standard list from the settings button on the top right of the file list. Or right click on the file and \"View Details\" to add tags in the file details. BabelBird also supports only allowing the enterprise console to create tags. In the enterprise console tag management, turn on \"Only allow the enterprise console to create and manage tags\", so that administrators can create and manage tags in a unified manner. Ordinary members can only select tags from the tag library when adding tags. This setting prevents a large number of synonym tags from being added by different people. 94. How does Babel search for tags? Click the search option button on the far right of the search box and select \"Tag Only\". At this time, documents matching the tag will be searched. There is a tag search function in the left column. Click \"Tag Settings\" in the left column. In the tag management interface, you can select the tags displayed in the left column. After the settings are completed, click the tag in the left column, and the documents with the tag will be displayed on the file list. 95. Does BabelBird support advanced search? BabelBird supports advanced search. Click the \"Advanced Search\" button on the right side of the search box to open the advanced search window. Advanced search supports the following search methods: Multiple keyword compound search. Search to limit file update time range. Photos are searched by the time they were taken. Search for files of specific types and formats. Search files uploaded by a specific user. Supports manual selection of specific folders for search. Supports search type selection. Such as: full text search + tag search, search file description only. 96. I want to send files on my computer to my colleagues. Is there any good way? If you have installed the Babel client, it will be quite simple to send local files/folders on your computer to colleagues. Right click the file/folder you want to send and find \"BabelBird\" \"Quickly Send to\" in the pop up menu At this time, a quick send file selection box will pop up. Select the colleague you want to send it to and click Send. The colleague will receive a Babel notification in which the file you sent can be downloaded. Quick Send only supports folders with less than 50 files and a size less than 50MB. If you send files, the maximum file supported is 50MB." }, { "lang": "en", "slug": "faq-archive-annotation", "title": "FAQ: Archives, Comments, Reviews and Subscriptions", "description": "Covers common issues related to files, comments, reviews, and badges.", "category": "FAQ", "top_category": "常见问题", "keywords": [ "FAQ", "FAQ: Archives, Comments, Reviews and Subscriptions" ], "url": "en/faq-archive-annotation.html", "source": "content/en/faq-archive-annotation.md", "summary": "FAQ: Archives, Comments, Reviews and Subscriptions The following questions cover common operations, permissions, collaboration and troubleshooting scenarios when users use BabelBird Enterprise Drive. 97. How to manage corporate archives? BabelBird has a built in file management module, and all archived files are stored uniformly in the archives. Super administrators and archivists can create archive (reading room) categories for archived documents. The archiving operation is irreversible, and documents can be renamed, deleted, and borrowed after being archived. Borrowing has three permissions: online reading, downloading, and copying. The rules and properties used by the archive are: Only \"A", "headings": [ { "level": 1, "title": "FAQ: Archives, Comments, Reviews and Subscriptions", "id": "faq-archives-comments-reviews-and-subscriptions" }, { "level": 2, "title": "97. How to manage corporate archives?", "id": "97-how-to-manage-corporate-archives" }, { "level": 2, "title": "98. What types of files can be annotated?", "id": "98-what-types-of-files-can-be-annotated" }, { "level": 2, "title": "99. How to create annotations?", "id": "99-how-to-create-annotations" }, { "level": 2, "title": "100. How to delete comments?", "id": "100-how-to-delete-comments" }, { "level": 2, "title": "101. How to reply to comments?", "id": "101-how-to-reply-to-comments" }, { "level": 2, "title": "102. I uploaded a new version of the document, but the comments are missing?", "id": "102-i-uploaded-a-new-version-of-the-document-but-the-comments-are-missing" }, { "level": 2, "title": "103. How do I view comments from older versions?", "id": "103-how-do-i-view-comments-from-older-versions" }, { "level": 2, "title": "104. If the file version is deleted, will the comments be deleted?", "id": "104-if-the-file-version-is-deleted-will-the-comments-be-deleted" }, { "level": 2, "title": "105. The comment I replied to is wrong, can it be revoked?", "id": "105-the-comment-i-replied-to-is-wrong-can-it-be-revoked" }, { "level": 2, "title": "106. Why can't I create annotations?", "id": "106-why-can-t-i-create-annotations" }, { "level": 2, "title": "107. Why do I give users the comment permission for link sharing, but they cannot comment?", "id": "107-why-do-i-give-users-the-comment-permission-for-link-sharing-but-they-cannot-comment" }, { "level": 2, "title": "108. Why can’t I create some types of comments on the APP?", "id": "108-why-can-t-i-create-some-types-of-comments-on-the-app" }, { "level": 2, "title": "109. Why can’t I create some types of annotations on my computer?", "id": "109-why-can-t-i-create-some-types-of-annotations-on-my-computer" }, { "level": 2, "title": "110. What should I do if the comments directly replied to in the dynamic cannot be displayed?", "id": "110-what-should-i-do-if-the-comments-directly-replied-to-in-the-dynamic-cannot-be-displayed" }, { "level": 2, "title": "111. Various symbols will be displayed on the document. What do they mean?", "id": "111-various-symbols-will-be-displayed-on-the-document-what-do-they-mean" }, { "level": 2, "title": "112. What is the maximum size of a single file that can be uploaded?", "id": "112-what-is-the-maximum-size-of-a-single-file-that-can-be-uploaded" }, { "level": 2, "title": "113. What should I do if the CAD file cannot be previewed on the client?", "id": "113-what-should-i-do-if-the-cad-file-cannot-be-previewed-on-the-client" }, { "level": 2, "title": "114. When previewing a file, I get stuck in the preview file generation interface. What should I do?", "id": "114-when-previewing-a-file-i-get-stuck-in-the-preview-file-generation-interface-what-should-i-do" } ], "images": [], "text": "FAQ: Archives, Comments, Reviews and Subscriptions The following questions cover common operations, permissions, collaboration and troubleshooting scenarios when users use BabelBird Enterprise Drive. 97. How to manage corporate archives? BabelBird has a built in file management module, and all archived files are stored uniformly in the archives. Super administrators and archivists can create archive (reading room) categories for archived documents. The archiving operation is irreversible, and documents can be renamed, deleted, and borrowed after being archived. Borrowing has three permissions: online reading, downloading, and copying. The rules and properties used by the archive are: Only \"Archive Administrators\" and \"Super Administrators\" can manage enterprise archives, and other personnel cannot manage archives. The identity of the archive administrator needs to be added by the super administrator under \"Archive Administrator\" in the enterprise management background. Archivists and super administrators can create new reading rooms Archived documents must be moved to the reading room by the archivist or super administrator before other members can borrow them. People with the \"Department File Management\" permission can archive files in their department The archive has an independent \"dynamic\" module, in which the user's own borrowing history can be queried The \"dynamic\" module of file management contains all file borrowing records Archivists and super administrators can view all archived files without borrowing There are four open levels of the reading room: public, open to limited departments, borrowing required, and borrowing only to limited departments. The files in the public reading room are visible to everyone, and users can directly view, download, and other operations on the files in the reading room; the public reading rooms in restricted departments are only visible to members of the designated department, and users can directly view, download, and other operations on the files in the reading room; the readers who need to borrow Files in the reading room are visible to everyone, and users need to borrow them before they can view, download, and other operations on the files in the reading room; reading rooms that are restricted to departments that can be borrowed are only visible to members of the designated department, and users need to borrow them before they can view, download, and other operations on the files in the reading room. 98. What types of files can be annotated? In addition to video and audio files, as well as office files, MD, and TXT, any file that can be opened for preview in BabelBird can be annotated, including pictures, GIF animations, PDFs, 3D models, and CAD files. Babel bird annotations can only be made in the file preview state, and cannot be annotated in the editing interface when the file is being edited. The privatized system may cause some file types to not be able to use \"BabelBird\" annotations due to the following modules and settings, but can use annotations inside the viewer. (Such comments will not be notified or dynamically displayed in BabelBird). Such situations are: Annotations created during the online editing process in Office. Excel selected the table mode viewing module. View Excel as a spreadsheet preview. The CAD Advanced Display module is selected, using Autodesk's CAD Viewer. 99. How to create annotations? Only logged in or authenticated users can create annotations. Anonymous users are not currently supported to create annotations. Web version and client: In preview mode, double click the left mouse button on the place where you want to annotate to create annotations. Or use the left comment menu to select the corresponding button to create a comment. Mobile APP: In preview mode, touch (click) where you want to create an annotation, and select \"Annotation\" to create an annotation. (Mobile APP can only create annotation point annotations) Mobile H5 or Enterprise WeChat or DingTalk: In preview mode, long press the screen where you want to create, and select the \"Create Comment\" option in the menu. Currently supported annotation types include annotation point annotation, freehand pen, welding mark, graphic annotation, annotation and text annotation. Annotation point annotation: BabelBird's main annotation type. Double click the area in the preview where you want to create an annotation to create it. Each comment point is equivalent to a discussion area, and responses can also be created and browsed on mobile APPs and H5 pages. Hand drawn pen: You can hand draw circles on the preview file, and other collaborators can see the hand drawn content in real time. It only supports creation on web pages and clients, and can only be browsed on mobile APPs. Welding marks: International welding marks can be inserted and edited on the preview file. It only supports creation on the web page and client, and can only be browsed on the mobile APP. Graphical annotation: Use graphic frames to select areas and create annotation points. Annotation points can be discussed like standard annotation points. They are only supported on web pages and clients, and can only be browsed and replied on the mobile APP. Annotation: Create a text annotation or description on the preview file. Reply and discussion are not allowed. The annotation is a directly displayed text description, which can be created on both mobile APP and H5. Text annotation: You can select a piece of text and create a comment area to support discussion. At the same time, you can also copy the selected text, which is only supported on web pages and clients, and can only be browsed and replied on the mobile APP. 100. How to delete comments? Only those with the permission to delete comments can delete comments. For comments on department files: People with department file management permissions (department managers), super administrators, and comment creators (the permission to delete their own comments is turned on in the role) can delete comments. For comments on personal files: The file owner and the creator of the comment can delete the comment. The deletion method is as follows: Annotation point annotation: Web or client delete comments in comment list Open the comment on the web or client and select the delete button to delete it. Press and hold the comment point on the APP. When the delete button appears, click delete. Freehand pen: Delete from the hand drawn list in the upper right corner of the web or client in preview mode. Click to display the handwriting list move the mouse to the item you want to delete in the list click Delete when the delete button appears. Welding marks: Right click on the mark on the Web or client, a delete button will appear, click Delete. Annotation: Right click the annotation on the Web or client, and a delete button will appear. Click Delete. Long press the mark on the APP, click delete when the delete button appears. Text annotation: Open the text comment on the web or client and select the delete button to delete it. 101. How to reply to comments? After someone creates a comment in a document, if you have access to the document and have permission to view comments. You will receive a notification that the document has been commented. At the same time, in the file list, there will also be a red dot in front of the icon of the document with new comments. You can reply to the comments in two ways: Enter the document to view comments and reply. Click the file name on the dynamic message to enter the document. Click the word comment to enter the document and open the comment. Just reply directly after opening the comment. If you know what the other person's comment refers to and want to answer immediately, you can directly click the \"Reply\" button under the comment in the dynamic to reply to the comment directly. No need to open the document. 102. I uploaded a new version of the document, but the comments are missing? BabelBird's comments follow the document version, which means that when someone uploads a new version of the document and previews the content of the new version, the comments of the old version will not be visible. But as long as this old version still exists, you can still see the annotations of the old version when viewing the old version through the \"Version Management\" column. Or open the comment list and view all versions of comment records in the comment list. And when you click on a comment in the comment list, it will automatically jump to the old version. 103. How do I view comments from older versions? Click the annotation list in the upper left corner of the preview area, and you can view old versions of annotations in the list. After the comment list is expanded, you can see all comments from the historical version. Clicking on an annotation of a historical version will automatically open the version where the annotation is located and the annotation location for display. After the annotation is opened, the old version of the annotation can also be replied to, and there will also be a reply notification in the dynamic. If you switch to the old version in file version management, you can also view the comments of the old version. 104. If the file version is deleted, will the comments be deleted? meeting. Because comments follow the file version, the comment information is also part of the file version information. If the file version is deleted, the comments related to that version will also be deleted at the same time. 105. The comment I replied to is wrong, can it be revoked? Reply comments can be revoked, but they can only be revoked by the respondent himself within two minutes of replying to the comment. Currently, only the client and web version support the cancellation of comment replies, and the mobile APP does not support the cancellation of comment replies. Undo method: Right click on your reply in the comment dialog box. The undo button will pop up. Click Undo. (The system response will be slow due to the permission determination required for the undo operation. If you encounter the prompt \"Undo Failed\", close this annotation and open it again to complete the revocation). 106. Why can't I create annotations? There are several possibilities for the inability to create annotations: This file has the \"annotation\" authorization turned off (only for department files), and it is possible that the annotation authorization has been turned off for some people. When this file invitation or link was shared with you, you were not authorized to comment or view comments. You opened the document through a shared link and you are not logged in. Babel does not support anonymous comments. 107. Why do I give users the comment permission for link sharing, but they cannot comment? BabelBird does not support anonymous comments. Users need to log in to BabelBird to make comments. And since the private cloud does not have a public account system, external members cannot register as users of an enterprise, which means that members without the enterprise account cannot comment on the documents shared by the link. If you need external members of the enterprise to comment on the document, you can use the invitation sharing function and enter the external member's email address or mobile phone number (you need to purchase a mobile phone SMS module) to invite. After receiving the invitation, the other party can use the email address or mobile phone number that invited him to verify his identity. After passing the identity verification, he can annotate the document. 108. Why can’t I create some types of comments on the APP? BabelBird will optimize the versions of different terminals and streamline operations according to the usage habits and characteristics of different devices. For example: on the mobile client (APP), the operation should be convenient and simple and suitable for touch, so the mobile phone can quickly create annotation points by clicking to create annotations, and supports voice annotations (mobile phones have microphones), or can insert hand drawings into annotations. In the PC environment, other types of annotations are provided due to the convenience of mouse operation and demonstration needs, but there are no voice annotations on the PC (most work PCs do not have a microphone). At the same time, in order to ensure that the conveyed information is not lost, no matter what type of annotation, it can be viewed on the mobile APP, PC or Web. All annotation types created on the PC can be viewed on the APP, and voice annotations created on the mobile APP can also be played on the PC. 109. Why can’t I create some types of annotations on my computer? It is currently not possible to create voice annotations on the computer and Web. The main reason is that most work PCs do not have a microphone, and there is no habit of using voice on PCs. However, you can view and listen to the voice annotations created on the APP on both the computer and the Web. 110. What should I do if the comments directly replied to in the dynamic cannot be displayed? Refresh the dynamic page or switch to the file and then switch back to the dynamic page to display it. 111. Various symbols will be displayed on the document. What do they mean? BabelBird will display different subscripts according to different file statuses. The following are the meanings of various subscripts. (Due to the refresh rate and network conditions of each terminal, the display of the icon may not be real time. The icon is only used as a reference for the file status. At the same time, due to the interface UI adaptation, the icon color of different terminals will also be different) 1. Icons that appear on web pages and clients: New version icon in the lower right corner of the file: indicates that a new version of the file has been uploaded Share icon in the lower right corner of the file/folder: indicates that the file/folder has been opened for sharing. This icon will cover the new version icon of the file. Shortcut or archive icon in the lower left corner of the file/folder: indicates that this is a shortcut file, and the source file/folder does not need to be in the directory; it may also be an archive file/folder. \"Finalized\": The approval document has been finalized \"Reject\": The approval document was rejected \"To be started\": A new version of a finalized or rejected document is uploaded \"External file\": Indicates that the file/folder was not created by members of this company \"Note\": Indicates that the file/folder has a file description \"Control\": Indicates that the file/folder has been subject to \"File Access Control\" \"Secret\": Indicates that the security level of the file/folder is confidential \"Limited\": Indicates that the security level of the file/folder is restricted \"Internal\": Indicates that the security level of the file/folder is internal There is a red rectangle under the file/folder: it means that the file/folder has snapshot sharing enabled. There is a yellow U line area under the file/folder + \"Archived\": it means that the file/folder has been archived locally, and new versions of locally archived files cannot be uploaded. Five pointed star: indicates the file or folder that you are concerned about There is an orange circle in the upper right corner of the file/folder icon: it indicates that the file/folder inherits the file access control of the previous level. 2. The icon that appears when synchronizing files: There is a blue check mark in the lower left corner of the file/folder: it means the file/folder has been synchronized successfully (local synchronization folder) There is a red exclamation point in the lower left corner of the file: it indicates that the file synchronization failed. There is a lock icon in the lower left corner of the file: it indicates that the file is locked and can be opened in read only mode (local synchronization folder) There are two half arrow icons up and down on the folder: indicating that this is a synchronized folder (client) 3. Client program status bar corner mark: There is a check mark under the bird icon: it means synchronization is complete There are two semicircular arrows rotating under the bird icon: it indicates that files are being synchronized. There is a cross under the bird icon: it indicates an error causing synchronization to be interrupted. 4. Map the disk corner mark: There is a cloud icon in the lower left corner of the file: it means that the file is in the cloud (not downloaded or cached) There is a share icon in the lower left corner of the file: it indicates that the file has been shared, and this icon will cover other icons. There is a blue check mark in the lower left corner of the file: it means the file has been downloaded and is consistent with the cloud There is a lock icon in the lower left corner of the file: it indicates that the file has been locked and can be opened in read only mode. There is an exclamation mark in the lower left corner of the file: it indicates that there is a conflict between the local file and the cloud 112. What is the maximum size of a single file that can be uploaded? The personal and professional editions support a single file upload limit of 5GB, the enterprise public cloud version supports a single file upload limit of 10GB, and the private cloud version supports a customizable upload limit of a single file, ranging from 1GB to 100GB, or even larger. 113. What should I do if the CAD file cannot be previewed on the client? If you cannot open the preview by clicking on a CAD (dwg, dwt) file on the client, there are usually the following situations: The file exceeds the size limit and cannot be previewed. (greater than 100M) The file is damaged and the preview cannot be generated. The CAD version of the file produced is incompatible with BabelBird, and the preview fails to be generated. You can use the client edit button to call the AutoCad software installed on your computer for viewing, right click the file and select \"Edit\" (requires download permission for the file). The client will automatically call a local program that can open CAD to open the file. 114. When previewing a file, I get stuck in the preview file generation interface. What should I do? Close the interface and try again after 5 10 minutes. The Babel preview server has a queuing mechanism for transcoding. If there are many files that need to be transcoded, they need to be queued for transcoding. When you click on the file to preview, the transcoding priority will be increased. However, if there are too many files in the queue or there are many users requesting previews, this transcoding will last for a while, so wait for a while and try again to open the preview normally. The inability to preview files does not affect the editing and use of files, it only affects the online file preview function. Files can also be used normally." }, { "lang": "en", "slug": "faq-technical", "title": "FAQ: Deployment, AI, limitations and troubleshooting", "description": "Covers FAQs related to deployment, AI, limitations, and troubleshooting.", "category": "FAQ", "top_category": "常见问题", "keywords": [ "FAQ", "FAQ: Deployment, AI, limitations and troubleshooting" ], "url": "en/faq-technical.html", "source": "content/en/faq-technical.md", "summary": "FAQ: Deployment, AI, Limitations and Troubleshooting The following questions cover common operations, permissions, collaboration and troubleshooting scenarios when users use BabelBird Enterprise Drive. 115. How to renew the professional version when it expires? Click \"Settings\" in the inverted triangle next to the user's avatar in the upper right corner, and click the renewal button at the bottom of the account information. The default renewal period is one year, but you can also set the length of time yourself, such as 2 years, 3 years, etc. 116. Are there any restrictions on file types uploaded to BabelBird? There are no restrictions on file types uploaded to BabelBird. Only file types add", "headings": [ { "level": 1, "title": "FAQ: Deployment, AI, Limitations and Troubleshooting", "id": "faq-deployment-ai-limitations-and-troubleshooting" }, { "level": 2, "title": "115. How to renew the professional version when it expires?", "id": "115-how-to-renew-the-professional-version-when-it-expires" }, { "level": 2, "title": "116. Are there any restrictions on file types uploaded to BabelBird?", "id": "116-are-there-any-restrictions-on-file-types-uploaded-to-babelbird" }, { "level": 2, "title": "117. Is there a limit to the number of people who can edit online?", "id": "117-is-there-a-limit-to-the-number-of-people-who-can-edit-online" }, { "level": 2, "title": "118. When sharing files with others, the deadline has not yet reached, but the link cannot be opened.", "id": "118-when-sharing-files-with-others-the-deadline-has-not-yet-reached-but-the-link-cannot-be-opened" }, { "level": 2, "title": "119. The download speed suddenly slowed down. What happened?", "id": "119-the-download-speed-suddenly-slowed-down-what-happened" }, { "level": 2, "title": "120. Entering a folder, the lower right corner prompts that the file does not exist.", "id": "120-entering-a-folder-the-lower-right-corner-prompts-that-the-file-does-not-exist" }, { "level": 2, "title": "121. How to check the real time online editors of shared files?", "id": "121-how-to-check-the-real-time-online-editors-of-shared-files" }, { "level": 2, "title": "122. Department roles have the permission to upload files, but files cannot be uploaded to a certain folder in the department. Why?", "id": "122-department-roles-have-the-permission-to-upload-files-but-files-cannot-be-uploaded-to-a-certain-folder-in-the-department-why" }, { "level": 2, "title": "123. After a file in a team is deleted, whose recycle bin is it in?", "id": "123-after-a-file-in-a-team-is-deleted-whose-recycle-bin-is-it-in" }, { "level": 2, "title": "124. After the team is deleted, will it be saved in the recycle bin?", "id": "124-after-the-team-is-deleted-will-it-be-saved-in-the-recycle-bin" }, { "level": 2, "title": "125. Does Babel support privatized deployment?", "id": "125-does-babel-support-privatized-deployment" }, { "level": 2, "title": "126. How to privatize the Babel system?", "id": "126-how-to-privatize-the-babel-system" }, { "level": 2, "title": "127. Does Babel support object storage?", "id": "127-does-babel-support-object-storage" }, { "level": 2, "title": "128. What hardware is needed to privatize the Babel system?", "id": "128-what-hardware-is-needed-to-privatize-the-babel-system" }, { "level": 2, "title": "129. Does BabelBird support integration with corporate WeChat?", "id": "129-does-babelbird-support-integration-with-corporate-wechat" }, { "level": 2, "title": "130. What is Zhichao AI?", "id": "130-what-is-zhichao-ai" }, { "level": 2, "title": "131. I also want Zhichao AI assistant, how to operate it?", "id": "131-i-also-want-zhichao-ai-assistant-how-to-operate-it" }, { "level": 2, "title": "132. Does Zhichao AI charge? How to charge?", "id": "132-does-zhichao-ai-charge-how-to-charge" }, { "level": 2, "title": "133. Can Zhichao AI be privatized?", "id": "133-can-zhichao-ai-be-privatized" }, { "level": 2, "title": "134. What file formats does BabelBird support for preview?", "id": "134-what-file-formats-does-babelbird-support-for-preview" }, { "level": 2, "title": "135. How to use the client to download anonymously?", "id": "135-how-to-use-the-client-to-download-anonymously" }, { "level": 2, "title": "136. I uploaded a file on BabelBird, but after a while the file was automatically deleted. What happened?", "id": "136-i-uploaded-a-file-on-babelbird-but-after-a-while-the-file-was-automatically-deleted-what-happened" }, { "level": 2, "title": "137. Can BabelBird upload files on the mobile browser?", "id": "137-can-babelbird-upload-files-on-the-mobile-browser" }, { "level": 2, "title": "138. Can anonymous users upload files?", "id": "138-can-anonymous-users-upload-files" }, { "level": 2, "title": "139. Why can’t I upload files in the personal file section?", "id": "139-why-can-t-i-upload-files-in-the-personal-file-section" }, { "level": 2, "title": "140. Can departments be created in the front desk?", "id": "140-can-departments-be-created-in-the-front-desk" }, { "level": 2, "title": "141. Are there any quantity or size limits for batch upload files?", "id": "141-are-there-any-quantity-or-size-limits-for-batch-upload-files" }, { "level": 2, "title": "142. When registering and logging in, I cannot receive the verification code (email, mobile phone)?", "id": "142-when-registering-and-logging-in-i-cannot-receive-the-verification-code-email-mobile-phone" }, { "level": 2, "title": "143. What is the difference between private and public?", "id": "143-what-is-the-difference-between-private-and-public" }, { "level": 2, "title": "144. Who has what permissions to archive files?", "id": "144-who-has-what-permissions-to-archive-files" }, { "level": 2, "title": "145. Where is the electronic signature set? Can it be written by hand?", "id": "145-where-is-the-electronic-signature-set-can-it-be-written-by-hand" }, { "level": 2, "title": "146. How can I chat?", "id": "146-how-can-i-chat" }, { "level": 2, "title": "147. Can file watermarks be added in batches?", "id": "147-can-file-watermarks-be-added-in-batches" }, { "level": 2, "title": "148. The upload speed is very slow, what’s going on?", "id": "148-the-upload-speed-is-very-slow-what-s-going-on" }, { "level": 2, "title": "149. Why can’t I invite members?", "id": "149-why-can-t-i-invite-members" } ], "images": [], "text": "FAQ: Deployment, AI, Limitations and Troubleshooting The following questions cover common operations, permissions, collaboration and troubleshooting scenarios when users use BabelBird Enterprise Drive. 115. How to renew the professional version when it expires? Click \"Settings\" in the inverted triangle next to the user's avatar in the upper right corner, and click the renewal button at the bottom of the account information. The default renewal period is one year, but you can also set the length of time yourself, such as 2 years, 3 years, etc. 116. Are there any restrictions on file types uploaded to BabelBird? There are no restrictions on file types uploaded to BabelBird. Only file types added to the file blacklist are not allowed to be uploaded. File types added by the client system settings that do not need to be synchronized are not uploaded, and there are also some temporary files, such as files with tmp;swp;lock, etc. as the suffix. (Only in synchronization tasks, uploading is not allowed. Web page or client uploads are not subject to this restriction). 117. Is there a limit to the number of people who can edit online? Online editing can be edited by multiple people at the same time. There is no limit on the number of people, and it can be satisfied in a general working environment. 118. When sharing files with others, the deadline has not yet reached, but the link cannot be opened. The most likely reason is that the sharing link has been closed and reopened. In this case, the first shared link that was spread has become invalid. 119. The download speed suddenly slowed down. What happened? The following situations may occur: It may be a network problem, the network is stuck or the network speed suddenly slows down; Use VPN or other circumvention tools to occupy network resources; Or the high speed traffic allocated by BabelBird has been used up and the speed limit mode has started to be used; Or the administrator has set a download speed limit for a certain user. 120. Entering a folder, the lower right corner prompts that the file does not exist. There are many reasons for this situation. For example, the server hard disk is full. For example, the memory is full at some point and the system is abnormal. Network problems may also cause the above problems (such as turning on VPN or circumvention tools). You can wait a moment and try again, or contact BabelBird customer service. 121. How to check the real time online editors of shared files? Only Office files can be edited online by multiple people at the same time. When online editing is turned on, the upper right corner will display how many people are currently online in real time. Click View Users to display the users currently editing the file. 122. Department roles have the permission to upload files, but files cannot be uploaded to a certain folder in the department. Why? This folder has file access control, and certain users or certain roles or everyone in the department cannot upload files. 123. After a file in a team is deleted, whose recycle bin is it in? Files deleted in the group are in the recycle bin of the deleter and the group creator. If the team creator deletes the file, the file is only in the team creator's recycle bin. If a user belonging to a certain enterprise deletes a file in a team, the file will only be in the team creator's recycle bin. 124. After the team is deleted, will it be saved in the recycle bin? After the team is deleted, it is deleted directly and will not be saved to the Recycle Bin. 125. Does Babel support privatized deployment? BabelBird can not only be used in SAAS mode on public clouds, but also supports private deployment. The private version of BabelBird has all the functions of the public cloud version, as well as unique private cloud functions such as customized login background, customized third party platform docking, and customized usage modules. 126. How to privatize the Babel system? In order to ensure service quality and operational stability of the privatized system, Babel provides users with a full range of privatized deployment services. All privatized systems are deployed by BabelBird engineers, and users only need to prepare servers and related hardware equipment suitable for BabelBird's privatized deployment as required. We will also provide privatized deployment hardware solutions based on user needs. Users can purchase their own hardware or use existing servers to deploy BabelBird. At the same time, BabelBird also supports deployment on cloud services such as Huawei Cloud, Alibaba Cloud, and Tencent Cloud. If you need to deploy a privatized Babel system, please contact our customer service staff. Tel: 400 9204020 127. Does Babel support object storage? Taking into account performance and efficiency, scalability, security and cost effectiveness, Babel recommends privatized users to use object storage for deployment. At the same time, the Babel team also supports building object storage systems for customers on servers with complex requirements. This will save a lot of budget than purchasing a complete set of object storage devices, and is more cost effective. 128. What hardware is needed to privatize the Babel system? Depending on the number of files managed and the number of concurrent users used, BabelBird also has different hardware requirements, which need to be estimated based on specific needs. We provide free hardware needs assessment and hardware construction solution services. You can contact our customer service staff for details. Tel: 400 9204020 129. Does BabelBird support integration with corporate WeChat? The privatized version of BabelBird supports docking with third party systems such as Enterprise WeChat, DingTalk, Feishu, OA, ERP, PDM... to realize single sign on, import of users and organizations, use of BabelBird on third party workbench, notification delivery, mobile H5 access... and other functions. Among them, Enterprise WeChat, DingTalk, and Feishu are standard docking modules, and private cloud users can configure them themselves in the enterprise console. 130. What is Zhichao AI? Zhichao AI is a large model enterprise assistant module launched by the BabelBird team. Not only can it serve as BabelBird’s AI customer service to answer questions users encounter when using BabelBird, but it can also use the company’s files stored on the network disk to learn and become your company’s exclusive AI assistant. You can directly talk to Zhichao in the form of questions about company related information and issues. And can give answers within the scope of permissions according to people with different permissions. For example: Give your company's commonly used product manuals, FAQs, and customer service documents to Zhichao AI for learning. After fine tuning by the BabelBirdAI team, Zhichao AI can become your company's exclusive customer service. Your customers can obtain information about your company's products by talking to Zhichao AI, significantly saving customer service costs. 131. I also want Zhichao AI assistant, how to operate it? At present, in order for Zhichao AI to achieve good results, the BabelBirdAI team needs to fine tune and train Zhichao AI according to your needs and the documents you provide, in order to achieve good results. Therefore, if you also want to have an exclusive AI assistant for your industry and data, please contact our customer service staff. 132. Does Zhichao AI charge? How to charge? Yes, because artificial intelligence model calculation requires a lot of GPU resources, and it also requires a lot of manpower to assist the AI ​​in learning documents provided by customers. These are costs, so Zhichao AI charges. We will estimate the specific costs based on the user's needs and goals. 133. Can Zhichao AI be privatized? Zhichao AI can be privatized, but requires dedicated GPU servers to provide the computing power required by the AI. 134. What file formats does BabelBird support for preview? BabelBird supports the preview of most commonly used documents, as well as the storage and client editing of all types of files. The \"supported file formats\" here specifically refer to the file formats that can be opened for preview on Babbitt without the use of third party plug ins. BabelBird supports uploading, downloading and opening with clients in all formats. The formats listed below are formats that can be previewed directly on BabelBird without the use of third party applications. Text file: txt, md Office files: doc, docx, ppt, pptx, xls, xlsx, wps, wpt, dps, rtf, dpt, et, ett Code class: js, xml, htm, html, css, scss, jsp, c, cpp, java, php, m, h, hpp, mm Other commonly used format files: Pdf, mail, msg, epub Optional support: (need to add server) key, numbers, pages Audio and video categories: mp3, mp4, wav, asf, ape Optional support: (optional options require additional server and corresponding module fees, please contact our customer service staff) flv, f4v, mp4, m4v, webm, 3gp, 3gpp, wmv, avi, rm, rmvb, mkv, asf, mov, mpeg, swf, mpg, mts, m2ts, ogv 3D graphics classes: Dae, fbx, obj, stl Optional support: (optional options require additional server and corresponding module fees, please contact our customer service staff) x3d, ply, 3ds, abc, m3d (Optional support for revit, solidworks, 3DMax) Image format categories: bmp, jpg, jpeg, gif, png, bmp, psd, tif, tiff, raw, cr2, arw, dng, nef, pef, dcm, ico Vector picture categories: ai, svg, eps, indd, indt, idml CAD classes: dwg, dwt, dxf Compressed file class: Optional support: (optional options require additional server and corresponding module fees, please contact our customer service staff) rar,zip 135. How to use the client to download anonymously? When an anonymous user downloads a large file from a shared link and is prompted to use a client to download, how can I use the client to download? Download the latest version of the client. There is a Use Client to Access Sharing Links button at the bottom of the client login interface. Click this button and paste the share link address to download the file using the client. 136. I uploaded a file on BabelBird, but after a while the file was automatically deleted. What happened? BabelBird will not automatically delete files. This situation is likely to be caused by other users synchronizing the folder using an older client, and the deletion operation is triggered due to certain conditions. This bug exists in older clients and has been fixed in version 5.2. Just update the client. 137. Can BabelBird upload files on the mobile browser? Depending on the usage scenario, mobile browsers can preview files on BabelBird, but they do not support uploading files. You can open sharing and upload files through WeChat. 138. Can anonymous users upload files? Babel supports anonymous users to upload files. As long as link sharing is set to allow anonymous users to upload, anonymous users who get the link can upload files. 139. Why can’t I upload files in the personal file section? The administrator has turned off the \"Allow users to upload personal private files by default\" switch button on the enterprise console. Users in the entire enterprise cannot upload files in the personal file column. 140. Can departments be created in the front desk? Super administrators and security officers can create departments under any department in the front desk. Operation and maintenance managers can create departments under their own departments. The default department manager role can create departments under their own department, and department personnel with \"sub department management\" permissions in other roles can also create departments under their own departments. 141. Are there any quantity or size limits for batch upload files? There is no limit on the number or size of files you can upload in batches. If the number of files is particularly large, such as tens of thousands of files, it is recommended to use the Babel client to upload them. 142. When registering and logging in, I cannot receive the verification code (email, mobile phone)? If you are required to use a mobile phone number when registering, you will need a SMS verification code to complete the registration. When you cannot receive the verification code, obtain the verification code again, or check the interception information of the information module. If there is still no verification code, there may be a problem with Alibaba Cloud's SMS module. You can wait for a while and try again, or contact our customer personnel and we will handle it in time. When logging in, you can use your account password or SMS verification code. If the verification code cannot be received, please refer to the handling method of not receiving the verification code during registration. The situation where an email verification code is required is when a share or project invites an unregistered BabelBird's email. This email will receive an invitation link. Open the link and ask for identity verification. A verification code will be sent to the user's email. In this case, you can basically receive the verification code. If you do not receive it, you can resend it or check the trash can. 143. What is the difference between private and public? The private version of BabelBird is deployed on the user's own server. It has a unique domain name for the enterprise, an independent user system, and an exclusive UI interface. The background image of the login page can be set, there is no traffic limit for uploading and downloading, various functions can be customized (such as the file format that needs to be previewed), and it can be connected with third party platforms (Enterprise WeChat, DingTalk) , Feishu, OA, ERP, etc.), the upper limit of uploading a single file can be customized, the encryption protection method can be selected, the storage space can be customized unlimitedly as needed, the modules to be used can be set in the enterprise console, and the mixed display of text watermarks, registered account watermarks, and picture watermarks can be displayed. Work ID mode login can be supported, and strong passwords can be set. These are not available in the public cloud version. 144. Who has what permissions to archive files? For personal private files, folders, projects, etc., the creator of the file can archive them in the archive; for files/folders/projects within the department, generally users with department manager permissions can archive them. To be more precise, users with \"department file management\" permissions can archive files within the department. 145. Where is the electronic signature set? Can it be written by hand? The electronic signature is added in Personal Settings Signature Settings. Click the inverted triangle button on the user's avatar in the upper right corner to open the settings pop up box. You can add your own electronic signature in the signature settings. Electronic signatures are drawn with the mouse. If you want to write by hand, you can use auxiliary hardware such as a writing pad to write your electronic signature by hand. Electronic signatures are used during the approval process. After the document is approved and finalized, the approver can insert his or her own electronic signature. On the file preview page, right click the mouse to insert the signature. The inserted electronic signature can be resized, changed position, and oriented. 146. How can I chat? BabelBird chat can be held in the discussion group. Teams, projects, and departments have their own discussion groups. Team members, project personnel, and people in departments can see the discussion groups of their teams, projects, and departments in the discussion group channel. The discussion group also supports sending files. For apps, you can also send voice messages in discussion groups. 147. Can file watermarks be added in batches? The watermark of BabelBird is set by the administrator in the enterprise console. You can use one of text watermarks, registered account watermarks, and picture watermarks. The private cloud version supports the superposition of the three watermarks. The watermark can be set to use: all files/all externally shared files/set by the file sharer. After setting the watermark related information in the enterprise console, the watermarks will be displayed on all files within the scope as set. 148. The upload speed is very slow, what’s going on? There are several possibilities when the upload speed is slow: Internet speed is relatively slow; At the same time, many people are uploading files in large batches, which causes the server to occupy a large amount of memory and the CPU to be busy; The circumvention tool or VPN used seizes network resources. 149. Why can’t I invite members? Teams can invite members, and team invitation members can only enter their mobile phone numbers or add them from frequently used contacts. Project invitation members can enter their nickname, email address or mobile phone number, and it will be confirmed when the user is matched. Note: You need to click the OK button again in the project information box before the invitation is successful. When adding members to a project, you can also choose from common contacts, company members, external personnel, and groups. It supports adding a department or a group to the project. The mapping disk cannot be synchronized? The cloud files are updated but the mapped disk is not updated, or the files in the mapped disk are updated but the cloud is not updated. There are many reasons that may cause the above problems, which can be solved in the following ways: Check whether the disk where the mapped disk cache is located has free space. The directory where the cache is located can be viewed by clicking the \"Settings\" button in the upper right corner of the client. If there is no free space, you can right click on the mapped disk folder and \"Release Space\" to clear the cache as needed. For clients after version 7.1.0, check whether the entire path of the file that cannot be synchronized exceeds 260 characters, including the entire path name and folder name, because the Windows operating system does not allow paths to exceed 260 characters by default. If it exceeds, shorten the path (rename) Check whether you have permission to upload or download files in the corresponding directory of the mapped disk. The simplest way is to access the directory corresponding to the mapping disk through the client and try to upload or download a file. If there is no permission, the client will prompt. Click on the avatar, log out of the current account, log in again and try to see if synchronization can be done correctly. Try restarting your computer. If none of the above methods can restore mapping disk synchronization, you can contact BabelBird customer service and our engineers can solve the problem remotely. Exclamation marks keep showing up in synced folders? If the files in the synchronized folder display an exclamation mark, it means that there is a version conflict between the local file and the cloud file. Generally, the conflict will be automatically resolved after the synchronization is scanned and updated again (the version with the latest modification time is the current version). If the exclamation mark still appears after more than 2 hours, you can try the following operations: Click on the avatar, log out of the current account, log in again and wait for the synchronization scan to complete to see if the exclamation mark still appears. Click the \"Sync\" button in the left column, find the corresponding synchronization task in the synchronization task list, right click \"Reset this synchronization\" Manually check the cloud version of the file and the local version of the file to determine the current version you want. If the current version you want is the cloud version, download the file on the client, and then overwrite the file with the same name in the sync folder. If the current version you want is a local version, find the directory where the file is located on the client, manually upload the local file to the directory, and select \"Upload as a new version\"" }, { "lang": "en", "slug": "for-ai", "title": "AI Reading Guide", "description": "Explain how AI, search engines, and RAG systems read the Babel Documentation Center.", "category": "Overview", "top_category": "维护", "keywords": [ "AI", "llms.txt", "RAG", "search engine", "structured index" ], "url": "en/for-ai.html", "source": "content/en/for-ai.md", "summary": "AI Reading Guide One of the main readers of this wiki is AI systems, so in addition to HTML pages, Markdown, JSON and plain text corpora are also provided. Recommended reading order 1. Read llms.txt to understand the site entrance, page list and machine reading suggestions. 2. Read ai index.json to obtain the title, category, abstract, text, images and Markdown source file path of each page. 3. Read llms full.txt as the complete corpus of RAG, vectorization or offline knowledge base. 4. The developer scenario reads developer api index.json , obtains the API endpoint list, and then enters the corresponding API page. 5. When you need to compare the original text, read the reference page, which", "headings": [ { "level": 1, "title": "AI Reading Guide", "id": "ai-reading-guide" }, { "level": 2, "title": "Recommended reading order", "id": "recommended-reading-order" }, { "level": 2, "title": "File type description", "id": "file-type-description" }, { "level": 2, "title": "Semantics and permission reminders", "id": "semantics-and-permission-reminders" } ], "images": [], "text": "AI Reading Guide One of the main readers of this wiki is AI systems, so in addition to HTML pages, Markdown, JSON and plain text corpora are also provided. Recommended reading order 1. Read llms.txt to understand the site entrance, page list and machine reading suggestions. 2. Read ai index.json to obtain the title, category, abstract, text, images and Markdown source file path of each page. 3. Read llms full.txt as the complete corpus of RAG, vectorization or offline knowledge base. 4. The developer scenario reads developer api index.json , obtains the API endpoint list, and then enters the corresponding API page. 5. When you need to compare the original text, read the reference page, which contains the white paper, FAQ, feature list and PDF extracted text. File type description Documentation Purpose index.html Document home page, directly displays the Chinese overview zh/ .html Full Chinese document en/ .html English same structure document content/zh/ .md Chinese Markdown source document content/en/ .md English Markdown source document llms.txt AI entry list llms full.txt Full Markdown corpus ai index.json Page level structured index developer api index.json API endpoint structured index image index.json Structured index of product screenshots, white paper images and FAQ images search index.json Front end search and site search corpus sitemap.xml Search engine crawling entrance Semantics and permission reminders The document describes product capabilities and does not mean that all modules have been enabled in a certain enterprise deployment. Privatized deployment, Zhichao AI, document control projects, third party integration, SMS, online Office, signature and other functions may be affected by version, authorization, deployment module or enterprise configuration. When AI answers specific customer questions, users should be prompted to refer to actual deployment configurations and administrator policies." }, { "lang": "en", "slug": "reference-whitepaper", "title": "White paper reference entrance", "description": "Reference material entry divided into original chapters of the white paper.", "category": "Source References", "top_category": "维护", "keywords": [ "white paper", "References" ], "url": "en/reference-whitepaper.html", "source": "content/en/reference-whitepaper.md", "summary": "白皮书参考入口 以下页面按《巴别鸟企业网盘白皮书》的一级章节拆分，便于全文检索和原文对照。 白皮书：概述 白皮书：系统架构 白皮书：预览及转码 白皮书：安全性 白皮书：主要功能模块 白皮书：用户界面 白皮书：性能优化 白皮书：可扩展性 白皮书：私有化部署 白皮书：附件1:巴别鸟功能列表 白皮书：附件2:巴别鸟开放API（基础API）", "headings": [ { "level": 1, "title": "白皮书参考入口", "id": "section" } ], "images": [], "text": "白皮书参考入口 以下页面按《巴别鸟企业网盘白皮书》的一级章节拆分，便于全文检索和原文对照。 白皮书：概述 白皮书：系统架构 白皮书：预览及转码 白皮书：安全性 白皮书：主要功能模块 白皮书：用户界面 白皮书：性能优化 白皮书：可扩展性 白皮书：私有化部署 白皮书：附件1:巴别鸟功能列表 白皮书：附件2:巴别鸟开放API（基础API）" }, { "lang": "en", "slug": "reference-whitepaper-01-overview", "title": "White Paper: Overview", "description": "\"BabelBird Enterprise Drive White Paper\" Chapter: Overview.", "category": "Source References", "top_category": "维护", "keywords": [ "white paper", "Overview" ], "url": "en/reference-whitepaper-01-overview.html", "source": "content/en/reference-whitepaper-01-overview.md", "summary": "白皮书：概述 巴别鸟简介 巴别鸟是上海画擎信息科技有限公司的注册商标及主要产品，上海画擎成立于2012年，总部位于上海，2016年于北京设立分公司。画擎科技是一个以技术为主导的团队，创始人均来自北大方正，拥有极强的图形图像处理和云计算技术并专注于安全存储及办公协作系统的研发。目前，巴别鸟已经完成了B轮融资，用户数超过80万，文档数据量已突破100PB。 图形图像和云计算领域的孜孜耕耘，高效工作方式的不懈探索，以及对产品用户体验的极致追求，造就了巴别鸟文档管理及协作平台。你可以用巴别鸟解决 企业文件统一管理、协同协作、数据安全 三大问题，大幅提高企业工作效率及数据安全性。 巴别鸟功能列表 详见文末附件1《巴别鸟功能列表》", "headings": [ { "level": 1, "title": "白皮书：概述", "id": "section" } ], "images": [], "text": "白皮书：概述 巴别鸟简介 巴别鸟是上海画擎信息科技有限公司的注册商标及主要产品，上海画擎成立于2012年，总部位于上海，2016年于北京设立分公司。画擎科技是一个以技术为主导的团队，创始人均来自北大方正，拥有极强的图形图像处理和云计算技术并专注于安全存储及办公协作系统的研发。目前，巴别鸟已经完成了B轮融资，用户数超过80万，文档数据量已突破100PB。 图形图像和云计算领域的孜孜耕耘，高效工作方式的不懈探索，以及对产品用户体验的极致追求，造就了巴别鸟文档管理及协作平台。你可以用巴别鸟解决 企业文件统一管理、协同协作、数据安全 三大问题，大幅提高企业工作效率及数据安全性。 巴别鸟功能列表 详见文末附件1《巴别鸟功能列表》" }, { "lang": "en", "slug": "reference-whitepaper-02-architecture", "title": "White Paper: System Architecture", "description": "Chapter of \"BabelBird Enterprise Drive White Paper\": System Architecture.", "category": "Source References", "top_category": "维护", "keywords": [ "white paper", "System architecture" ], "url": "en/reference-whitepaper-02-architecture.html", "source": "content/en/reference-whitepaper-02-architecture.md", "summary": "白皮书：系统架构 架构概述 前端架构 前端架构包括以下关键组件和技术： 主架构选择了backbone.js，它提供了组件化开发、状态管理和路由控制等功能。又在其基础上引入了Gulp、Babel、browserify、Scss、jQuery、underscore、ES6等用以构建可维护和高性能的前端应用程序。 使用了WebSocket协议和后台进行消息的即时通讯。 设计了风格统一、用户友好、直观的界面，包括搜索、文件夹管理、文件预览等功能。 网站支持全平台预览，使用了CSS媒体查询和移动优化技术创建响应式布局，以确保网盘产品在不同设备上具备一致的外观和功能。 考虑多语言支持，目前系统支持中、英文两种语言，可在界面随时切换，也能通过浏览器语言进行切换。 采用了代码分割、懒加载、资源压缩和CDN加速等前端性能优化技术，以提高页面加载速度和响应时间。 实施前端安全性最佳实践，包括XSS（跨站脚本攻击）和CSRF（跨站请求伪造）防护。确保数据传输加密和安全存储。 跨平台和多语言： 巴别鸟系统前端部分包含了：巴别鸟iOS版（iPhone、iPad）、巴别鸟安卓版、巴别鸟web版、巴别鸟微信版（H5），巴别鸟mac客户端，巴别鸟windows客户端、巴别鸟Linux（麒麟）客户端。 原生iOS客户端使用Object C和Swift开发。 原生安卓客户端、鸿蒙使用Java开发（Android studio）。 windows、mac、麒麟 客户端使用Electron及C++进行开发，包含 客户端界面、同步端、传输管理、映射盘四个组件。 后端架构 服务器拓扑结构 巴别鸟的后端架构主要负责业务逻辑", "headings": [ { "level": 1, "title": "白皮书：系统架构", "id": "section" } ], "images": [], "text": "白皮书：系统架构 架构概述 前端架构 前端架构包括以下关键组件和技术： 主架构选择了backbone.js，它提供了组件化开发、状态管理和路由控制等功能。又在其基础上引入了Gulp、Babel、browserify、Scss、jQuery、underscore、ES6等用以构建可维护和高性能的前端应用程序。 使用了WebSocket协议和后台进行消息的即时通讯。 设计了风格统一、用户友好、直观的界面，包括搜索、文件夹管理、文件预览等功能。 网站支持全平台预览，使用了CSS媒体查询和移动优化技术创建响应式布局，以确保网盘产品在不同设备上具备一致的外观和功能。 考虑多语言支持，目前系统支持中、英文两种语言，可在界面随时切换，也能通过浏览器语言进行切换。 采用了代码分割、懒加载、资源压缩和CDN加速等前端性能优化技术，以提高页面加载速度和响应时间。 实施前端安全性最佳实践，包括XSS（跨站脚本攻击）和CSRF（跨站请求伪造）防护。确保数据传输加密和安全存储。 跨平台和多语言： 巴别鸟系统前端部分包含了：巴别鸟iOS版（iPhone、iPad）、巴别鸟安卓版、巴别鸟web版、巴别鸟微信版（H5），巴别鸟mac客户端，巴别鸟windows客户端、巴别鸟Linux（麒麟）客户端。 原生iOS客户端使用Object C和Swift开发。 原生安卓客户端、鸿蒙使用Java开发（Android studio）。 windows、mac、麒麟 客户端使用Electron及C++进行开发，包含 客户端界面、同步端、传输管理、映射盘四个组件。 后端架构 服务器拓扑结构 巴别鸟的后端架构主要负责业务逻辑、数据处理和与前端的交互。它满足了以下关键目标： 模块化设计: 后端采用了模块化的设计，以便将不同功能和业务逻辑划分为独立的模块。这有助于代码的可维护性和可扩展性。 性能: 巴别鸟后端具有良好的性能，能够处理大规模的文件上传、下载、搜索和协作请求。采用了适当的负载均衡及缓存策略和优化技术以提高响应时间。 安全性: 巴别鸟后端重点强化安全性，包括用户身份验证、授权、数据加密和防御性编程，以保护用户数据免受攻击。 可扩展性: 巴别鸟后端架构具备可扩展性，以适应未来的业务需求和新功能的添加。采用了SOA服务架构和模块化组件设计，以支持功能的灵活扩展。 数据管理: 巴别鸟后端有效地管理了用户数据、文件数据和元数据。这包括数据库设计、备份策略和数据清理。 框架选择 巴别鸟采用了松散的、面向服务的架构模式。不同的服务，其设计、开发、部署都是独立的，这样就确保了系统的稳定性和可扩展性。最终，我们会采用docker把这些服务容器化，进行统一的管理和部署。 对于逻辑简单、高频访问的服务，我们选择Nodejs及相应的开发框架。 对于逻辑复杂、低消耗的服务，我们会选择Struts2+Spring框架。 对于逻辑复杂、且高消耗(比如MD5计算、文件分块、加密)的服务，我们会选用Rust语言进行开发。 数据层 数据库: 巴别鸟选择了MySQL作为数据库管理系统，也支持使用其他数据库（可按需支持 高斯、PostgreSQL、Oracle） 同时，巴别采用ORM（对象关系映射）: 使用ORM框架（Hibernate）将数据库表映射到Java对象，以简化数据访问和持久化。 安全性 用户身份验证: 使用强大的用户身份验证机制，包括单一登录（SSO）、OAuth认证和多因素认证（MFA）。 授权: 使用Spring Security等授权框架来定义和强制访问控制策略，确保用户只能访问其授权的资源。 数据加密: 实施数据传输和存储的加密，以保护用户数据的安全性。 业务逻辑 文件管理: 开发了业务逻辑来处理文件上传、下载、版本控制、共享和协作功能。 用户管理: 实施用户管理、权限管理和用户组织结构。 搜索功能: 开发了高效的搜索引擎，支持文件和元数据的快速检索。 在线编辑：负责文件的在线编辑、协同编辑。 文件转码：负责文件的批量排队转码，生成预览文件。 对象存储：文件的分块及落盘，存储系统管理。 Web服务 RESTful API: 使用RESTful API，以支持前端和其他客户端的数据交互和协作。 缓存管理 缓存策略: 使用缓存来提高性能，包括页面缓存、数据缓存和会话缓存。 异步任务处理 消息队列: 使用消息队列系统RabbitMQ来处理异步任务，如文件转码、文件预览生成等。 通过采用Struts2和Spring框架，结合以上设计考虑，可以构建一个强大、高性能、安全可靠的企业网盘后端系统，满足用户的需求并支持未来的扩展和功能添加。 云基础设施选择（公有云 SAAS版本巴别鸟） 公有云基础设施选择可以直接影响到企业网盘产品的性能、可靠性和安全性。巴别鸟公有云版本经过多方对比，选择了阿里云的ECS、OSS服务以及CDN分发业务。目前（2023年）公有云SAAS模式运行的巴别鸟系统已经0服务器故障在线运作了超过10年。 云服务提供商选择 业务服务器SAAS版本巴别鸟使用了阿里云的ECS（云服务器）集群 阿里云的ECS是一种弹性计算服务，为你提供了虚拟机实例，使你能够在云中运行应用程序。这些是选择ECS的一些关键优势： 灵活性: ECS允许你根据需要创建、启动和停止虚拟机实例。这意味着你可以根据流量需求来扩展或缩减计算资源。 可扩展性: 阿里云提供了多种不同规格的ECS实例，以满足不同工作负载的需求。你可以根据应用程序的性能要求进行选择。 可靠性: 阿里云的ECS实例通常具有高可用性，提供了多个数据中心和可用区，以确保业务连续性。 安全性: 阿里云提供了各种安全性功能，包括网络隔离、防火墙和安全组，以帮助你保护你的虚拟机实例免受恶意攻击。 对象存储SAAS版本巴别鸟使用了阿里云的OSS（对象存储服务） 阿里云的OSS是一种高度可扩展、安全可靠的云存储服务，适用于存储和管理大量的文件和数据。以下是选择OSS的一些优势： 可扩展的存储: OSS提供了可扩展的存储容量，可以根据你的需要进行动态扩展。这对于企业网盘产品中的文件存储非常重要。 数据备份和恢复: 阿里云的OSS具有数据备份和版本控制功能，可以帮助你保护数据免受丢失或损坏。 安全性: 数据存储在OSS中通常会受到加密和访问控制的保护，以确保数据的安全性。 CDN整合: 与CDN服务集成，可以提高文件的分发速度和用户体验。 为确保全球各地的访问通畅，巴别鸟也使用了CDN分发 CDN（内容分发网络）服务是将内容缓存到全球分布的边缘节点，以降低加载时间并提高用户体验。阿里云的CDN服务可以为企业网盘产品带来以下好处： 快速分发: 加速文件的分发，确保用户能够快速访问和下载文件，不受地理位置的限制。 负载均衡: CDN可以帮助分担服务器的负载，降低服务器的压力，提高网站的性能。 安全性: CDN服务通常具有DDoS攻击防护功能，可保护网站免受恶意攻击。 全球覆盖: 阿里云的CDN服务具有全球性覆盖，可确保你的内容快速传递给全球用户。 数据中心地理位置 目前巴别鸟使用了阿里云的两个数据中心： 杭州数据中心 及 威海数据中心 一南一北的配置能保证服务的可持续性及灾备需求。 数据库设计 数据库类型 巴别鸟企业网盘采用了多种类型的数据库，同时也可根据客户需求支持信创的数据库产品或是Oracle等大型数据库。 巴别鸟默认的产品数据库为： 核心数据库为关系型数据库 mysql 辅助数据库有：Redis 数据库，MongoDB 数据库 数据库架构 数据架构在企业网盘系统中扮演着至关重要的角色，确保了数据的高可用性、性能和一致性。下面是巴别鸟的数据库架构： A. 主从数据库架构 主库（Master） 主库负责处理写入操作，包括用户上传文件、修改文件信息等。 主库提供高可用性、数据一致性和事务处理。 从库（Slave） 从库主要用于读取操作，包括文件的查询、搜索等。 从库可以提供负载均衡，分担主库的读取负载。 数据同步：采用数据复制机制确保从库与主库的数据保持同步。 故障转移：从库可以在主库故障时接管写入操作，确保系统的连续性。 B. 关系型数据库（MySQL） 数据库设计 数据库设计以支持文件和用户管理，包括文件元数据、用户信息、权限等表的定义。 数据表之间的关系清晰，使用外键来维护数据一致性。 数据冗余 主从架构中的从库用于数据冗余，以防止主库故障时的数据丢失。 数据同步机制确保从库的数据与主库保持一致。 C. NoSQL数据库（MongoDB） 文件元数据存储 MongoDB可用于存储文件的元数据，如文件名、大小、版本信息等。 具有弹性模式的MongoDB适用于不断变化的数据模式。 D. 缓存数据库（Redis） 缓存读取数据 Redis用于缓存频繁读取的数据，以减轻数据库的负载。 缓存的数据可以包括用户会话信息、热门文件、访问日志等。 E. 数据备份和恢复 备份策略 定期备份主库和从库的数据，以确保数据的安全性。 巴别鸟备份数据存储在不同地理位置的可靠存储中。 灾难恢复 我们制定详实的恢复计划，包括从备份中还原数据的步骤和时间表。 巴别鸟运维团队会定期测试灾难恢复过程以确保其有效性。 F. 数据一致性和事务管理 事务支持 使用数据库事务来确保一系列操作的一致性，如文件上传、共享和权限更改。 事务应该被正确地管理，以避免数据损坏和不一致性。 并发控制 使用数据库锁和隔离级别来管理并发访问，以避免数据竞争和冲突。 G. 监控和性能优化 性能监控 实施数据库性能监控，包括查询响应时间、负载和资源利用率。 根据监控结果进行性能调整，以确保数据库的稳定性和性能。 查询优化 优化复杂查询以提高查询性能，包括索引优化和查询计划分析。 这些数据架构的元素将有助于确保你的企业网盘系统能够具备高可用性、性能卓越和数据的安全性。通过合理的数据库设计和维护，你可以提供稳定可靠的服务，满足用户需求并确保数据的完整性。 数据备份和恢复策略（公有云） A. 数据备份 定期备份计划：巴别鸟有定期的备份计划，以确保数据的连续备份（每日凌晨数据备份）。 完整备份和增量备份：巴别鸟采用完整备份和增量备份的组合策略。完整备份将数据库的全部数据备份，而增量备份仅备份自上次备份以来发生更改的数据，以减少备份时间和存储空间的消耗。 多备份位置：公有云版本巴别鸟有杭州机房及威海机房两个地理位置，以应对自然灾害或硬件故障。云存储和远程数据中心是常见的备份存储选择。 自动化备份：巴别鸟的数据库备份采用全自动备份机制，无需人工干预，以提高可靠性。 备份测试：我们会定期测试备份以确保其完整性和可用性。通过还原备份数据到测试环境中并验证数据的一致性来进行测试。 B. 灾难恢复 恢复计划：我们建立了详细的恢复计划，明确每个步骤和责任。确保团队成员了解如何执行恢复过程。 备份恢复测试：我们会定期测试备份恢复过程，以确保在紧急情况下能够迅速有效地还原数据。测试应包括各种故障场景的模拟。 备份监控：监控备份任务的运行情况，出现问题会自动提醒及报错，确保备份系统正常运行。 灾难恢复团队：我们有专门的灾难恢复团队，7 24小时待命，负责在紧急情况下采取行动，确保业务的持续运行。 通信计划：我们建立了有效的通信计划，及自动告警信息送达监控，以通知相关利益相关者有关灾难事件和恢复过程的信息。 文档和培训：确保恢复计划和过程的详细文档，并为团队成员提供培训，使其了解恢复策略和步骤。 以上策略和努力立足于确保数据库数据的安全性和可用性，并最大程度地减少数据丢失和系统停机的风险。" }, { "lang": "en", "slug": "reference-whitepaper-03-preview-transcoding", "title": "White Paper: Preview and Transcoding", "description": "\"BabelBird Enterprise Drive White Paper\" Chapter: Preview and transcoding.", "category": "Source References", "top_category": "维护", "keywords": [ "white paper", "Preview and transcode" ], "url": "en/reference-whitepaper-03-preview-transcoding.html", "source": "content/en/reference-whitepaper-03-preview-transcoding.md", "summary": "白皮书：预览及转码 文件预览功能能让用户无需安装应用程序就能直接在网盘上直接打开文件进行预览，为了能在网页端及客户端上预览文件及保证文件在只读状态下的安全性（不被人获取内容或源文件），文件预览和转码是企业网盘系统的核心功能之一。这章将介绍巴别鸟如何实现文件的在线预览和转码，以提供更便捷的用户体验。 支持在线预览的文件类型 文本、代码及office文件： Pdf，md，js，xml，htm，html，css，scss，jsp，c，cpp，java，php，m，h，hpp，mm， mail ，msg ，epub，doc，docx，ppt，pptx，xls，xlsx，txt，rtf，wps，wpt，dps，dpt，et，ett Xmind，km 可选支持：（可选项需要增加服务器及相应模块费用） key，numbers，pages 音视频： mp3，mp4， wav，asf，ape 可选支持：（可选项需要增加服务器及相应模块费用） flv，f4v，mp4，m4v，webm，3gp，3gpp，wmv，avi，rm，rmvb，mkv，asf，mov，mpeg，swf，mpg，mts，m2ts，ogv 3D图形： dae、3ds、abc、fbx、mtl、obj、ply、stl、x3d 可选支持1：（可选项需要增加服务器及相应模块费用） x3d， ply，3ds，abc，m3d 可选支持2: revit、soildworks、3DMax 图片格式： bmp，jpg，jpeg，gif，png，bmp，psd，tif，tiff，raw，cr2，arw，dng，nef，pef，dcm，ico dic", "headings": [ { "level": 1, "title": "白皮书：预览及转码", "id": "section" }, { "level": 3, "title": "性能优化", "id": "section-2" } ], "images": [], "text": "白皮书：预览及转码 文件预览功能能让用户无需安装应用程序就能直接在网盘上直接打开文件进行预览，为了能在网页端及客户端上预览文件及保证文件在只读状态下的安全性（不被人获取内容或源文件），文件预览和转码是企业网盘系统的核心功能之一。这章将介绍巴别鸟如何实现文件的在线预览和转码，以提供更便捷的用户体验。 支持在线预览的文件类型 文本、代码及office文件： Pdf，md，js，xml，htm，html，css，scss，jsp，c，cpp，java，php，m，h，hpp，mm， mail ，msg ，epub，doc，docx，ppt，pptx，xls，xlsx，txt，rtf，wps，wpt，dps，dpt，et，ett Xmind，km 可选支持：（可选项需要增加服务器及相应模块费用） key，numbers，pages 音视频： mp3，mp4， wav，asf，ape 可选支持：（可选项需要增加服务器及相应模块费用） flv，f4v，mp4，m4v，webm，3gp，3gpp，wmv，avi，rm，rmvb，mkv，asf，mov，mpeg，swf，mpg，mts，m2ts，ogv 3D图形： dae、3ds、abc、fbx、mtl、obj、ply、stl、x3d 可选支持1：（可选项需要增加服务器及相应模块费用） x3d， ply，3ds，abc，m3d 可选支持2: revit、soildworks、3DMax 图片格式： bmp，jpg，jpeg，gif，png，bmp，psd，tif，tiff，raw，cr2，arw，dng，nef，pef，dcm，ico dicom（医疗图像） 矢量图片： ai，svg，eps，indd，indt，idml CAD dwg，dwt，dxf，dcm 压缩文件： 可选支持： rar, zip 在线预览工具（巴别鸟预览器） 巴别鸟企业网盘使用了自主研发的BabelViewer在线预览工具进行在线预览，支持不同文件转码后统一预览。允许用户查看文件内容，而无需下载到本地。 BabelViewer是针对企业网盘用户需求开发的强大的H5在线预览工具，有如下特性： 支持多个库，以便于多种方式渲染预览文件。 支持多图层技术，可以在预览文件上进行多人绘制。 支持在线批注，并可以在批注区内多人讨论。 可展开批注列表统一管理当前版本及历史版本的批注。 支持多种文件的版本对比。 矢量化的渲染，矢量文件可以高倍率放大不失真。 可以在预览状态下快速切换预览多个文件。 使用webGL技术支持3D文件的在线渲染，也支持3D文件的在线批注。 文件转码功能 转码工具： 巴别鸟转码服务集成了多个转码工具，以将文件从一种格式转换为另一种支持巴别鸟预览器打开的格式。私有部署系统需要一台专用的服务器（或虚拟机）来来处理文件的转码。 例如，将高分辨率图片转换为Web友好的JPEG格式。 自动转码： 巴别鸟实现了自动转码功能，用户上传的文件会自动转换为适当的格式并抽取文件列表缩略图，以节省存储空间和提高性能。针对大量文件同时上传的转码处理，巴别鸟有一套独特的调度机制，力求在有限的资源占用下让用户打开预览更及时。 服务器空闲时用户文件上传即刻自动转码，生成预览文件。 服务器繁忙时，如果用户同时上传的文件超过一定数量，这些文件将不会进行转码，当用户点击文件准备预览时，优先加入到转码进程，实时生成预览文件。 因为用户一次性上传大量文件后要马上预览的概率很低，这样的设定可以防止用户同时大量上传文件时因服务器繁忙造成真正需要转码的文件打不开的情况。 转码队列和异步处理： 将转码任务加入队列，并使用异步处理方式来执行转码操作，以避免阻塞其他系统功能。 缓存和性能优化 预览和转码缓存： 实施缓存机制，以存储已转码的文件和预览数据，以减少重复转码和提高响应速度。 负载均衡： 同时转码队列配置了负载均衡策略，以确保多个预览和转码请求能够平衡地分配到不同的处理节点。 性能优化 性能监控： 实时性能监控，包括转码速度、缓存命中率和响应时间，出错自动清空队列重试处理。严重错误短信通知运维人员。 资源调整： 根据监控结果和负载情况，动态调整预览和转码资源，以确保高性能和可用性。 集成测试 性能测试： 进行性能测试，模拟大量并发预览和转码请求，以评估系统在高负载下的表现。 office家族文件 巴别鸟支持微软office家族及WPS的文件的在线预览，为确保office文件特别是word文件的显示准确性，巴别鸟提供了2种office文件的预览方式： 使用运行于Windows服务器的office转码模块把文件转码后进行预览（默认）。 需要部署一台window服务器生成预览文件。 可以相当准确的与微软office或WPS打开无差别的预览word类文件和ppt类文件。 支持使用巴别鸟预览器(BabelViewer)对文件进行批注讨论、圈画及版本对比。 可使用“智巢AI”文档助理功能。 Excel文件因没有版式和字体问题，都使用在线office的预览功能进行预览。 所有的预览文件都可以内嵌水印，并可另存为带水印的PDF文件。 使用运行于Linux服务器的在线office的预览功能提供office及wps文件的在线预览。 针对只能使用Linux，并且对word文件预览版式准确度没有较高要求的用户。 因系统字体差异，在线office解析等原因，在Linux系统中的在线office并不能1：1完美显示word文件的版式，在譬如：项目符号编号、段落高度、分页、插入图形位置等方面会有少许差异。 Excel文件因没有版式和字体问题，都使用在线office的预览功能进行预览。 使用在线office预览功能打开的word类和ppt类文件将不再支持巴别鸟预览器的批注功能。 不支持使用“智巢AI”的文档助理功能。 所有的预览文件都可以内嵌水印，并可另存为带水印的PDF文件。 考虑到浏览器的性能及服务器的效率，在线预览office文件会有一定的文件尺寸大小限制，超过这个限制的文件就无法在线预览。私有云用户可以自定义这些限制，但不建议调过大。 Word（文档）类文档最大可预览文件大小为 200MB。 PPT（幻灯片）类文档最大可预览大小为 200MB。 Excel（表格）类文档最大可预览大小为 50MB。 图片及图形文件 巴别鸟支持绝大多数图片文件的在线预览，包括psd、gif家族、jpg家族、bmp家族、png、raw家族（部分）、arw、tif、TIFF、dicom、ico等文件，同时也支持医学图形常用的dicom格式。并且得益于巴别鸟强大的图片处理技术，巴别鸟可以以1：1的方式在线预览超高分辨率的大图（可选组件），并且在图片上批注讨论，并且巴别鸟支持读取照片的元数据。 PSD、RAW、BMP等图片格式需要服务器自动转码后才能预览。 通常情况下（没有开启大图显示模块）超过4K分辨率的大图片将会被服务器处理成便于网页展示的尺寸及格式。开启大图显示模块后，服务器将把大图切割成若干小块，分块载入1：1显示，这将耗费较大服务器资源。 PNG等透明背景的图在巴别鸟中也能显示出透明度，并且可以更改背景。 巴别鸟系统会读取图片元数据信息，供搜索、查询、排序。这些信息包括：分辨率、尺寸、拍摄设备、拍摄时间、拍摄地点。 所有可预览图片格式都会生成缩略图，供文件列表展示快速查找及瀑布流模式展示。 所有图片格式都支持在巴别鸟预览器(BabelViewer)中批注讨论、圈画及版本对比。 如开启水印功能，服务器将会对预览的图片进行预处理，在图片中嵌入水印。 所有图片类文件都可以另存为带水印的PDF文件。 巴别鸟也能很好的支持矢量图形的在线预览，包括但不限于ai、dwg、dcm、dxf 、dwt 、pdf、eps、svg、idml、indd…等矢量图形格式。更重要的是，巴别鸟能以矢量渲染的方式打开这些格式的文档，这意味着这类图形可以在巴别鸟中放大几十倍也不会模糊或失真。 AI、eps、indd等文件需要服务器自动转码后才能预览。 以矢量的方式显示，支持更改背景颜色。 放大后图形不会失真或模糊。 其他特性和图片一致，同样支持嵌入水印、另存为带水印PDF、在巴别鸟预览器(BabelViewer)中批注讨论、圈画及版本对比、生成文件列表预览图。 3D及CAD文件 得益于巴别鸟预览器(BabelViewer)对3D格式的支持，我们默认支持dae、3ds、abc、fbx、mtl、obj、ply、stl、x3d等3D图形的在线预览，并且支持在3D空间中的批注讨论。 目前，巴别鸟预览器仅支持单个文件3D图形，如果文件有外挂皮肤等外挂文件将只能载入模型本体。 3D文件目前还不支持生成预览图，但如果有这方面需求支持定制开发。 3D文件可以在巴别鸟预览器中旋转、放大、缩小、拆分，并可以建立批注讨论点，系统会记住建立批注时的视口，点击批注会自动旋转到建立批注时的视角。 如需对revit、soildworks、3DMax等专业格式进行支持，私有化部署用户可以选择接入第三方3D在线显示及转码插件，（如：Autodesk viewer）这会产生相关费用。 目前不支持在移动设备预览3D文件。仅支持在网页及客户端预览3D文件。 巴别鸟支持对CAD文件的预览。如: dwg，dwt，dxf 格式，目前在公有云上，巴别鸟向专业版及企业版用户提供强大的CAD预览服务，私有化用户想要预览CAD文件需要购买相应的CAD转码服务私有化授权。 巴别鸟CAD预览支持CAD版本R12 2021。 CAD文件可生成预览缩略图，用于文件列表及瀑布流模式。 兼容天正全专业T20V7版本。 支持在浏览器、客户端、移动端预览及批注CAD文件。 支持百兆以上图纸浏览。 图层打开/隐藏/多选/全选。 布局切换、视图平移、缩放、更改背景颜色、鹰眼鸟瞰视图。 音视频转码 不使用转码服务器的情况下 巴别鸟无须转码服务就可以直接在线播放支持HTML5标准的视频文件。 支持的格式如下： 视频文件格式 MP4：MPEG 4 Part 14，支持H.264编码。几乎所有的浏览器都支持该格式。 WebM：谷歌开发的格式，使用VP8或VP9编码，可以在大多数现代浏览器中播放 Ogg：开放媒体格式，使用Vorbis编码，可以在大多数现代浏览器中播放。 音频文件格式 MP3：MPEG 1或MPEG 2 Audio Layer III，可以在几乎所有的浏览器中播放。 AAC：Advanced Audio Coding，可以在大多数现代浏览器中播放。 Ogg：开放媒体格式，使用Vorbis编码，可以在大多数现代浏览器中播放。 WAV：Waveform Audio File Format，可以在几乎所有的浏览器中播放，但文件较大，不适合在网络上播放。 兼容性 视频兼容性 音频兼容性 使用转码服务器的情况下 如果需要使用巴别鸟管理查询大量视频素材，就需要搭建专用的视频转码服务器，并购买相应的视频转码模块授权。（目前此服务仅支持私有化部署用户） 巴别鸟视频转码模块采用FFmpeg解决方案，FFmpeg 支持 MPEG、 DivX、MPEG4、AC3、DV、FLV 等40多种编码，AVI、MPEG、OGG、Matroska、ASF 等90多种解码，FFmpeg 支持的编解码器种类共有 280 多种， 涵盖了几乎所有常见音视频编码格式， 能解码几乎所有的音视频。 视频转码服务器所需硬件配置 视频转码是一个相当耗费运算资源的服务，需要一台专门的物理机来执行转码操作。同时服务器性能要求和需要转码的视频类型，时长和码率都有关系。 按每天转换累计时长50小时的HDR 4K视频（使用CUDA）为1080P H.264 AC3 MP4为基准，所需的服务器硬件配置如下： 服务器类型 配置要求 操作系统 服务器用途 备注 视频转码服务器 至强Intel E5 2630v3CPU 2 64G内存 2TB SSD硬盘 + Nvidia Tesla M4 4G显卡 Linux 视频转码服务器 使用GPU（CUDA） 根据视频码率不同所需转码时间也不同，在通常情况下，一个100秒的2K视频转码成1080P MP4耗时为8秒（使用上文硬件配置），如果同时转码的视频多，服务器则会做多线程排队处理。 使用转码服务器后，视频文件转码完成后即可播放，并且可以在文件列表查看缩略图。" }, { "lang": "en", "slug": "reference-whitepaper-04-security", "title": "White Paper: Security", "description": "Chapter of \"BabelBird Enterprise Drive White Paper\": Security.", "category": "Source References", "top_category": "维护", "keywords": [ "white paper", "security" ], "url": "en/reference-whitepaper-04-security.html", "source": "content/en/reference-whitepaper-04-security.md", "summary": "白皮书：安全性 安全的架构 安全是业务的关键！巴别鸟从产品设计到架构搭建及服务器管理都优先考虑安全性，并且包含了许多重要的安全功能。您可以控制每个文件及每位成员的访问行为、添加文件水印、查看访问日志、重要文件归入档案库、给文件及部门设立加密等级及安全策略….这一系列举措可以最大限度保护重要数字资产。同时，巴别鸟使用了安全等级最高的EV SSL认证，银行级的加密传输，多机房分布式备份，确保你的数据安全无忧。这些举措使巴别鸟获得了QUALYS安全性A+认证，同时我们也拥有ISO27001信息安全质量体系认证。 巴别鸟从上线开始就实现了从上传、下载、到落盘的全链路的加密传输和存储，配合权限管理及文件管理的细节处理，以及各种使用场景所遇到的风险分析及相应的功能应对策略，使巴别鸟成为了市面上最安全的企业网盘之一。 图：巴别鸟数据传输链路 防火墙、堡垒机、VPN、SSL….在传输和服务器部署架构上我们有越来越多的手段保证系统的数据安全性。但是根据我们多年从事企业安全服务的经验来看，80%数据泄露事件往往来源于内部人员泄露及管理混乱。即使系统做到了物理隔离，也没办法杜绝数据泄露风险。巴别鸟从产品设计之初就考虑到了这一点，从管理、人员和设备的角度提供了多种安全设计及功能。在易用性和安全性的矛盾之处也提供了多种可选设置及方案。从产品结构和使用逻辑上尽可能保证数据安全性。大幅消除因内部人员疏忽或破坏产生的数据泄露风险。 用户身份验证和授权（SSO） 自有用户体系 巴别鸟自由用户体系身份验证种类 账号类型 验证方式 备注 邮箱 密码、验证码 公有云需绑定手机号验证 手机号（全球） 密码、验证码 私有", "headings": [ { "level": 1, "title": "白皮书：安全性", "id": "section" }, { "level": 3, "title": "安全的架构", "id": "section-2" }, { "level": 3, "title": "用户身份验证和授权（SSO）", "id": "sso" }, { "level": 3, "title": "用户体验", "id": "section-3" }, { "level": 3, "title": "概述", "id": "section-4" }, { "level": 3, "title": "概述", "id": "section-5" }, { "level": 3, "title": "概述", "id": "section-6" } ], "images": [], "text": "白皮书：安全性 安全的架构 安全是业务的关键！巴别鸟从产品设计到架构搭建及服务器管理都优先考虑安全性，并且包含了许多重要的安全功能。您可以控制每个文件及每位成员的访问行为、添加文件水印、查看访问日志、重要文件归入档案库、给文件及部门设立加密等级及安全策略….这一系列举措可以最大限度保护重要数字资产。同时，巴别鸟使用了安全等级最高的EV SSL认证，银行级的加密传输，多机房分布式备份，确保你的数据安全无忧。这些举措使巴别鸟获得了QUALYS安全性A+认证，同时我们也拥有ISO27001信息安全质量体系认证。 巴别鸟从上线开始就实现了从上传、下载、到落盘的全链路的加密传输和存储，配合权限管理及文件管理的细节处理，以及各种使用场景所遇到的风险分析及相应的功能应对策略，使巴别鸟成为了市面上最安全的企业网盘之一。 图：巴别鸟数据传输链路 防火墙、堡垒机、VPN、SSL….在传输和服务器部署架构上我们有越来越多的手段保证系统的数据安全性。但是根据我们多年从事企业安全服务的经验来看，80%数据泄露事件往往来源于内部人员泄露及管理混乱。即使系统做到了物理隔离，也没办法杜绝数据泄露风险。巴别鸟从产品设计之初就考虑到了这一点，从管理、人员和设备的角度提供了多种安全设计及功能。在易用性和安全性的矛盾之处也提供了多种可选设置及方案。从产品结构和使用逻辑上尽可能保证数据安全性。大幅消除因内部人员疏忽或破坏产生的数据泄露风险。 用户身份验证和授权（SSO） 自有用户体系 巴别鸟自由用户体系身份验证种类 账号类型 验证方式 备注 邮箱 密码、验证码 公有云需绑定手机号验证 手机号（全球） 密码、验证码 私有云需对接短信发送平台 工号（user ID） 密码 仅私有云支持，忘记密码只能管理员重置，首次登录会要求用户强制重置密码 微信 扫码、APP跳转（移动端） 仅公有云支持，需绑定手机号验证 巴别鸟支持多种身份验证类型混用。 可强制要求多因素认证（MFA）以提高安全性 混合身份验证: 在使用单点登录时（SSO）支持同时使用自有用户体系和SSO。用户可以选择使用自有凭据登录或通过SSO登录（如使用企业微信扫码登录及采用账户密码登录）。 单点登录（Single Sign On，SSO）集成 单点登录（Single Sign On，SSO）集成是企业网盘产品中的一个关键功能，它允许用户在一次身份验证后访问多个不同的应用程序和服务，提高了用户体验和安全性。 巴别鸟支持OAuth2.0、CAS等方式集成单点登录，并已实际应用于和多种系统的对接中。 支持的SSO标准和协议 巴别鸟企业网盘支持多种SSO标准和协议，包括但不限于以下内容： ADFS集成： 巴别鸟支持与Active Directory Federation Services（ADFS）的集成，这使得基于Windows身份验证的SSO成为可能。这种集成允许企业内部用户使用他们的Windows凭据进行登录。 AD域控制器集成： 巴别鸟还支持与企业的本地Active Directory（AD）域控制器的集成。这使得企业内部用户可以使用他们的本地域凭据进行登录。 企业微信集成： 巴别鸟支持对接企业微信，这使得企业可以直接用企业微信账号进行扫码认证登录。并且可以同步导入微信的组织结构及用户，使用企业微信发送通知，并在工作台中访问巴别鸟。 钉钉集成： 巴别鸟支持对接钉钉，这使得企业可以直接用钉钉账号进行扫码认证登录。并且可以同步导入钉钉的组织结构及用户，使用钉钉发送通知，并在钉钉工作台中访问巴别鸟。 飞书集成： 巴别鸟支持对接飞书，这使得企业可以直接用飞书账号进行扫码认证登录。并且可以同步导入飞书的组织结构及用户，使用飞书发送通知，并在飞书工作台中访问巴别鸟。 集成文档： AD域控、企业微信、钉钉、飞书、致远OA的集成已内嵌于巴别鸟私有化版本中，用户购买相应模块后只需要根据相应文档进行配置即可使用。相关配置文档可咨询巴别鸟客服人员。 第三方SSO集成： 如果你的组织使用第三方SSO供应商（如Okta、OneLogin、Auth0、千帆、泛微等），我们也支持与这些供应商的产品集成。这意味着外部用户可以通过这些供应商的产品进行SSO登录。但这需要二次开发并需要支付一定费用。 第三方自有用户体系集成 我们理解许多组织可能同时拥有自有用户体系，因此我们的SSO集成支持混合身份验证： 混合身份验证: 我们的系统允许用户选择使用自有凭据进行登录，或者使用SSO进行登录。这提供了最大的灵活性，以适应不同用户的需求。 用户映射和同步: 我们确保自有用户体系中的用户帐户与SSO中的用户帐户同步。这意味着用户的属性和权限在整个系统中保持一致。 安全性和授权 我们非常注重安全性和授权策略的实施，以确保只有授权用户能够访问资源： 身份验证策略: 我们支持灵活的身份验证策略，包括多因素认证（MFA）等高级选项。这有助于确保用户的身份得到妥善验证。 授权和访问控制: 我们允许管理员配置和管理用户的访问权限，包括文件和资源的授权。这确保了只有经过授权的用户能够访问敏感数据。从其他平台导入的用户仅会拥有所在部门的初始权限（默认为部门成员），管理员可以通过自定义“部门成员”角色权限的方式统一更改导入用户的初始权限范围。 用户体验 我们关注用户体验，努力提供无缝的登录体验： 登录页面: 我们的登录页面清晰直观，提供用户选择不同的登录方式的选项。用户可以选择使用SSO登录或使用自有凭据登录。同时，我们也支持使用用户单点登录系统自己的登录页面（如ADFS系统认证页面） 单点注销: 如果对接的单点登录系统（SSO）支持单点注销功能，我们也可支持单点注销，这意味着用户可以在任何一个连接的应用程序中注销，系统会自动注销其他应用程序的会话。 访问控制列表（ACL）设计 概述 在巴别鸟企业网盘中，权限管理是确保文件和资源的安全性和可访问性的核心组成部分。ACL（Access Control List）被用于定义用户和角色对于不同部门中的资源的访问权限。本章将详细介绍我们的ACL设计，包括角色管理、用户分配、角色权限和变更管理。 角色管理 角色定义: 我们允许管理员自定义角色，每个角色代表一组权限的集合，有32种权限可选组合成角色。 每个角色应有一个明确的名称和描述，以便管理员和用户了解其功能。 权限分配: 每个角色都被分配特定的权限，这些权限决定了角色在部门中的操作能力。 权限应该精心选择，以确保用户拥有必要的权限但又不会过度授权。 用户管理 用户角色分配: 每个用户都可以被分配一个或多个角色，这些角色决定了用户在不同部门中的权限。 允许一个用户在不同部门拥有不同的角色，以适应多样化的需求。 用户与部门的关联: 用户应与其所属部门建立关联，以便根据部门角色自动分配相应的权限。 用户仅能访问其所在的部门，并有角色决定在部门中的访问权限。 能否访问子部门，也由角色权限决定（角色有访问子部门权限）。 角色权限管理 角色权限定义: 每个角色有明确的权限定义，包括可读、可写、可删除、可共享等操作。 角色可以根据需要新增或删减。 权限继承: 我们的系统支持权限的继承，当用户分配到一个角色时，他们会自动继承该角色的权限。 这减少了手动分配权限的工作量，同时确保一致性。 变更管理 角色权限变更: 当管理员更改角色的权限时，所有拥有该角色的用户在部门中的权限也会相应更改。 我们将详细记录这些变更，以便进行审计和故障排除。 权限审计: 安全管理员可定期审计角色和用户的权限，以确保授权的准确性和安全性。 不再需要的权限应及时取消。 安全性 访问控制: 巴别鸟企业网盘的ACL系统将严格控制用户和角色对资源的访问。 只有经过授权的用户并拥有在该部门的角色才能访问部门文件。 部门间相互隔离，可以设定不同的密级（部门安全策略）来保护部门的文件。 审计和监控: 所有的权限变更角色变更都会留下日志记录。方便管理查询。 实施监控和审计机制，以监视权限变更和访问活动，及时检测和响应潜在的风险。 最佳实践 最小特权原则: 遵循最小特权原则，即给予用户和角色所需的最低权限，以降低潜在的安全风险。 部门文件可通过文件访问控制来精确增加某个成员（或某种角色）的权限，并设定权限有效期。 定期审查: 定期审查角色和权限配置，以确保系统的安全性和性能。 未来扩展 多租户支持: 公有云系统支持多租户控制。 私有云考虑将ACL系统扩展到多租户环境，以支持多个客户或组织的需求。 数据加密 数据传输加密（SSL/TLS） 加密协议 在巴别鸟企业网盘中，我们高度重视数据传输的安全性。为了确保数据在传输过程中得到保护，我们采用了安全套接字层（Secure Socket Layer，SSL）协议来实现传输加密。 HTTPS: 我们使用HTTPS协议，它是HTTP的安全版本，以加密所有数据传输。 HTTPS通过TLS/SSL协议提供端到端的数据加密，防止第三方恶意用户截取或窃听传输的数据。 证书管理 SHA 256证书: 我们的SSL证书采用SHA 256哈希算法，这是一种强大的哈希算法，提供了高级的安全性和完整性保护。 SHA 256证书对于验证服务器的身份以及保护数据传输非常关键。 证书更新: 巴别鸟企业网盘将定期更新SSL证书，以确保证书的有效性和安全性。 我们会监视证书的到期日期，提前进行续签。 数据加密 数据传输加密: 所有在巴别鸟企业网盘和用户终端之间的数据传输都会经过TLS/SSL加密。 这包括用户登录、文件上传和下载、以及任何敏感数据的传输。 数据完整性保护: TLS/SSL不仅提供了数据加密，还能够验证传输过程中数据的完整性，以防止数据被篡改或损坏。 安全性 严格的加密策略: 我们遵循严格的加密策略，确保所有数据传输都经过安全通道，无法被非授权方访问。 保护用户隐私: 数据传输加密有助于保护用户的隐私和敏感信息，包括个人身份信息和机密文件。 最佳实践 安全升级: 我们将继续关注新的安全标准和最佳实践，确保数据传输加密的安全性得到不断提升。 安全审计: 我们会定期进行安全审计和漏洞扫描，以确保我们的加密机制不受到潜在威胁的影响。 图：巴别鸟获得了Qualys SSL扫描的A+安全验证 数据存储加密 概述 在巴别鸟企业网盘中，我们采用了高级的分块加密技术，以确保文件的安全性和完整性。我们使用分块加密技术来将文件分成小块，每个小块都经过哈希加密，然后存储在对象存储系统中。这一技术确保即使在服务器控制权或硬盘被攻破的情况下，攻击者也无法获取到完整的文件内容。 分块加密 文件分块: 上传到巴别鸟企业网盘的文件会被分成若干小块（chunks）。 每个小块的大小可以根据系统需求进行配置，以平衡性能和安全性。 哈希加密: 每个小块都会经过哈希加密，使用强大的哈希算法确保数据的完整性。 哈希值将与存储的小块一起存储，以便后续验证。 存储安全 对象存储: 加密后的小块将存储在巴别鸟企业网盘的对象存储系统中，确保高可用性和数据冗余。 无法还原的加密: 我们使用不可逆的哈希加密算法来确保存储的小块无法还原为原始文件内容，以确保文件存储的安全性。 安全传输: 小块数据在传输到对象存储系统时也会经过加密，以防止中间人攻击。 文件下载 临时下载链接: 当用户需要下载文件时，鉴权通过系统会动态地拼合分块，形成一个临时下载链接。 这个链接是唯一的，只有很短的有效期用于下载。再次下载需要从新生成下载链接。这个设定可以防止通过获取下载链接暴露文件。 下载解密: 在用户请求下载时，巴别鸟企业网盘会将分块数据在服务器端解密，然后合并为完整的文件。 这确保了文件在存储过程中即使硬盘被非法读取内容也不会暴露文件给任何未授权的访问者。 安全性 数据隔离: 分块加密技术将数据分成小块，每个小块都经过独立的哈希加密，以防止整个文件被暴露。 无法还原性: 使用不可逆的哈希算法确保了数据的无法还原性，即使攻击者获取了一部分小块数据，但因数据缺失也无法还原原始文件。 防止数据泄漏 安全审计日志 概述 在巴别鸟企业网盘中，我们强调数据访问和操作的可追溯性和安全性。为了实现这一目标，我们建立了一个强大的访问日志系统，用于记录整个系统的历史访问日志。这些日志包括文件的上传和下载、权限的变更、用户讨论批注、文件的增删改查、审批以及部门变更等操作。本章将详细介绍我们的安全审计日志系统和角色管理。 访问日志功能 全面的日志记录: 我们的日志系统记录了整个巴别鸟企业网盘的各种访问行为，确保每个操作都可以被追溯和审计。 记录的操作包括但不限于文件管理、权限控制、用户操作和部门管理。 关于巴别鸟日志的更多信息，可查阅：日志及报表 章节。 默认保存时间: 默认情况下，我们保存完整访问日志的时间段为90天。 这确保了足够的历史数据可供审计和检查。 可扩展的保存时间: 根据需要，管理员可以根据特定合规性要求扩展访问日志的保存时间（仅私有化系统支持）。 第三方日志管理系统 集成支持: 巴别鸟可对接第三方日志管理系统，以便将访问日志数据导入到外部日志平台进行进一步分析和长期存储。 安全管理员角色 安全保密员: 安全保密员具有高级的权限，可以在前台查看和管理所有部门的文件。 在企业管理后台，安全保密员具备以下权限： 制定公司安全策略（独有权限）。 管理组织结构。 成员管理。 权限管理。 安全审计员: 安全审计员可以在前台查看和管理所有部门的文件。 在企业管理后台，安全审计员具备以下权限： 查看企业安全策略。 查看组织结构。 查看成员权限。 查看权限管理。 查看文件访问日志。 安全性 数据隔离: 安全审计日志数据被严格隔离，只有授权的管理员可以访问和管理它们。 保密性: 安全保密员和安全审计员的角色都经过精心设计，一个负责安全策略，一个负责安全审计，互相监督，以确保数据的保密性和合规性。 扩展 自动化告警: 支持自动化告警机制，可添加监控项目，以在发现异常活动时及时通知超级管理员。 巴别鸟企业网盘的安全审计日志系统，包括功能、角色管理和安全性措施确保了数据访问和操作的可追溯性，并支持与第三方日志管理系统的集成，以进一步提高安全性和合规性。 安全性审查和测试 渗透测试 测试委托: 巴别鸟企业网盘会定期自己进行渗透测试或委托第三方机构，如绿盟科技，进行渗透测试，以评估系统的安全性。 渗透测试的目标是使用前沿的攻击技术，成熟的黑客攻击手段，以及标准的软件测试技术，测试指定系统的安全性，发现潜在的安全漏洞和风险。 测试阶段: 渗透测试包括以下流程： 信息收集：测试人员进行必要的信息收集，如IP地址、DNS记录、软件版本信息、IP段以及公开信息等。 渗透测试：测试人员根据信息收集阶段的结果，尝试入侵网络和系统。成功的情况下，可能获得普通权限。 缺陷利用：测试人员尝试提升权限，以获取对系统的完全控制权。在必要时，他们可能会回到信息收集阶段重新开始。 成果收集：测试人员对之前阶段发现的问题，如弱点和漏洞进行分类整理，并集中展示。 威胁分析：测试人员对发现的问题进行威胁分类和分析其潜在影响。 输出报告：测试人员根据测试和分析的结果，编写直观的渗透测试服务报告。 渗透测试的主要目标： 发现系统中的安全漏洞和潜在风险。 评估系统的安全性，包括身份验证、访问控制、数据保护等方面。 提供改进建议，以加强系统的安全性。 测试的结果将有助于我们采取适当的措施来修复发现的问题，提高系统的整体安全性。 最佳实践 巴别鸟企业网盘将定期进行渗透测试，以保持系统的安全性。 使用自动化工具和手动测试相结合，以提高渗透测试的全面性和准确性。 测试完成后根据报告及时整改，以确保系统的安全性。 未来扩展 我们将继续改进渗透测试流程，以适应不断演进的安全威胁。 考虑引入高级分析工具，以更深入地评估系统的安全性。 安全漏洞扫描 为了维护巴别鸟企业网盘的安全性，我们定期进行安全漏洞扫描。这项措施旨在自动化地检测系统中的潜在安全漏洞，以及可能导致安全威胁的问题。我们依托专业的扫描工具（例如：Qualys、Rapid7 InsightVM、OpenVAS）来确保系统持续保持在一个高度安全的状态。 扫描过程 安全漏洞扫描包括以下关键阶段： 定期扫描: 我们定期（通常是按计划的时间间隔）对系统进行安全漏洞扫描。 扫描工具自动化地执行一系列测试来发现潜在的漏洞。 扫描目标: 安全漏洞扫描的目标包括系统中的应用程序、操作系统、网络设备等各个方面。 扫描确保系统的整体安全性。 扫描结果: 扫描工具将识别并报告系统中发现的漏洞。 报告会包括漏洞的类型、严重程度以及可能的修复建议。 修复措施: 基于扫描结果，我们采取必要的修复措施来解决发现的漏洞和问题，以确保系统的安全性。 巴别鸟安全相关功能" }, { "lang": "en", "slug": "reference-whitepaper-05-core-modules", "title": "White paper: Main functional modules", "description": "\"BabelBird Enterprise Drive White Paper\" Chapter: Main functional modules.", "category": "Source References", "top_category": "维护", "keywords": [ "white paper", "Main functional modules" ], "url": "en/reference-whitepaper-05-core-modules.html", "source": "content/en/reference-whitepaper-05-core-modules.md", "summary": "白皮书：主要功能模块 数据传输模块 数据传输模块是巴别鸟企业网盘的核心组成部分，负责管理上传、下载、同步盘和映射盘的数据传输。这一模块采用多种技术来确保数据的安全性、可靠性和高效性。 技术特点 文件分块: 数据传输模块采用文件分块技术，将大文件分成小块，以便更有效地传输和存储。这不仅有助于减少网络流量和服务器资源的消耗，还支持断点续传和增量上传下载。 哈希验证（秒传）: 在数据传输过程中，哈希验证用于确保文件的完整性。每个文件块都有相应的哈希值，服务器和客户端会相互验证这些哈希值，以检测是否有数据损坏或篡改。 同时，如果存储系统中已经有相同哈希码的文件，该文件就不用再次上传。实现秒传功能。 SSL传输: 数据传输模块使用SSL（安全套接层）协议来加密数据传输，以确保数据在传输过程中的保密性和安全性。这对于敏感企业数据的传输至关重要。 断点续传: 巴别鸟企业网盘支持断点续传，允许用户在传输中断的情况下从上次中断的地方继续上传或下载文件，而无需重新开始整个过程。这节省了时间和带宽。 增量上传下载: 数据传输模块还支持增量上传和下载，允许用户只传输发生更改的部分的文件分块，而不是整个文件。这在大型文件和频繁同步的情况下非常有用。 优势 数据完整性: 文件分块和哈希验证确保了数据的完整性，降低了数据损坏或篡改的风险。 数据安全: SSL传输提供了数据的端到端加密，确保数据在传输过程中不会被窥探或窃取。 效率: 断点续传和增量上传下载提高了数据传输的效率，节省了时间和带宽。 节约存储空间： 使用文件哈希码技术可以在磁盘上只存储一份相同哈希的文件。无论文件路径、文件名如何变化，或者在网盘中", "headings": [ { "level": 1, "title": "白皮书：主要功能模块", "id": "section" }, { "level": 3, "title": "技术特点", "id": "section-2" }, { "level": 3, "title": "优势", "id": "section-3" }, { "level": 3, "title": "简介", "id": "section-4" }, { "level": 3, "title": "技术特点", "id": "section-5" }, { "level": 3, "title": "常见文件管理功能", "id": "section-6" }, { "level": 3, "title": "版本管理概述", "id": "section-7" }, { "level": 3, "title": "技术实现", "id": "section-8" }, { "level": 3, "title": "版本更新方式", "id": "section-9" }, { "level": 3, "title": "版本管理功能", "id": "section-10" }, { "level": 3, "title": "企业控制", "id": "section-11" }, { "level": 3, "title": "搜索模块概述", "id": "section-12" }, { "level": 3, "title": "带权限判断的搜索", "id": "section-13" }, { "level": 3, "title": "技术基础", "id": "section-14" }, { "level": 3, "title": "搜索功能", "id": "section-15" }, { "level": 3, "title": "性能优化", "id": "section-16" }, { "level": 3, "title": "未来发展", "id": "section-17" }, { "level": 3, "title": "在线编辑模块概述", "id": "section-18" }, { "level": 3, "title": "技术基础", "id": "section-19" }, { "level": 3, "title": "主要功能", "id": "section-20" }, { "level": 3, "title": "用户体验", "id": "section-21" }, { "level": 3, "title": "企业协作", "id": "section-22" }, { "level": 3, "title": "开放API", "id": "api" }, { "level": 3, "title": "其他在线编辑器", "id": "section-23" }, { "level": 3, "title": "客户端编辑概述", "id": "section-24" }, { "level": 3, "title": "技术实现", "id": "section-25" }, { "level": 3, "title": "主要功能", "id": "section-26" }, { "level": 3, "title": "用户体验", "id": "section-27" }, { "level": 3, "title": "技术挑战", "id": "section-28" }, { "level": 3, "title": "分享功能", "id": "section-29" }, { "level": 3, "title": "外发功能（发送文件）", "id": "section-30" }, { "level": 3, "title": "用户控制和企业策略", "id": "section-31" }, { "level": 3, "title": "灵活性与便捷性", "id": "section-32" }, { "level": 3, "title": "技术架构", "id": "section-33" }, { "level": 3, "title": "适用的文件类型", "id": "section-34" }, { "level": 3, "title": "预览器类型", "id": "section-35" }, { "level": 3, "title": "批注种类", "id": "section-36" }, { "level": 3, "title": "功能模块", "id": "section-37" }, { "level": 3, "title": "主要特点", "id": "section-38" }, { "level": 3, "title": "技术架构", "id": "section-39" }, { "level": 3, "title": "文件评审的优势", "id": "section-40" }, { "level": 3, "title": "角色权限", "id": "section-41" }, { "level": 3, "title": "文件权限", "id": "section-42" }, { "level": 3, "title": "总结", "id": "section-43" }, { "level": 3, "title": "概述", "id": "section-44" }, { "level": 3, "title": "使用方式", "id": "section-45" }, { "level": 3, "title": "总结", "id": "section-46" }, { "level": 3, "title": "概述", "id": "section-47" }, { "level": 3, "title": "主要特点", "id": "section-48" }, { "level": 3, "title": "技术优势（对比WebDAV和SMB）", "id": "webdav-smb" }, { "level": 3, "title": "应用场景", "id": "section-49" }, { "level": 3, "title": "主要特点", "id": "section-50" }, { "level": 3, "title": "技术架构", "id": "section-51" }, { "level": 3, "title": "档案管理的优势", "id": "section-52" }, { "level": 3, "title": "主要特点", "id": "section-53" }, { "level": 3, "title": "技术架构", "id": "section-54" }, { "level": 3, "title": "日志与报表的优势", "id": "section-55" }, { "level": 3, "title": "动态栏目", "id": "section-56" }, { "level": 3, "title": "通知栏目", "id": "section-57" }, { "level": 3, "title": "个性化设置", "id": "section-58" }, { "level": 3, "title": "应用场景", "id": "section-59" }, { "level": 3, "title": "概述", "id": "section-60" }, { "level": 3, "title": "主要功能", "id": "section-61" }, { "level": 3, "title": "应用场景", "id": "section-62" }, { "level": 3, "title": "总结", "id": "section-63" }, { "level": 3, "title": "概述", "id": "section-64" }, { "level": 3, "title": "主要功能", "id": "section-65" }, { "level": 3, "title": "应用场景", "id": "section-66" }, { "level": 3, "title": "主要栏目", "id": "section-67" }, { "level": 3, "title": "智巢AI的三个主要模块", "id": "ai" }, { "level": 3, "title": "技术解决方案", "id": "section-68" }, { "level": 3, "title": "优势", "id": "section-69" }, { "level": 3, "title": "多任务协同与执行流转权重", "id": "section-70" }, { "level": 3, "title": "功能概述", "id": "section-71" }, { "level": 3, "title": "核心运作与配置规则", "id": "section-72" }, { "level": 3, "title": "权限与数据安全控制", "id": "section-73" }, { "level": 3, "title": "典型业务应用场景", "id": "section-74" }, { "level": 3, "title": "功能概述", "id": "section-75" }, { "level": 3, "title": "适用范围与权限控制", "id": "section-76" }, { "level": 3, "title": "核心规则引擎与配置维度", "id": "section-77" }, { "level": 3, "title": "原始名称的精细化修剪与防冲突机制", "id": "section-78" }, { "level": 3, "title": "全局格式化输出控制", "id": "section-79" }, { "level": 3, "title": "功能概述", "id": "section-80" }, { "level": 3, "title": "执行逻辑与边界条件", "id": "section-81" }, { "level": 3, "title": "广泛的格式兼容矩阵", "id": "section-82" }, { "level": 3, "title": "功能概述", "id": "section-83" }, { "level": 3, "title": "灵活的触发机制与作用域", "id": "section-84" }, { "level": 3, "title": "核心智能整理规则引擎", "id": "section-85" }, { "level": 3, "title": "业务场景与功能概述", "id": "section-86" }, { "level": 3, "title": "签章资产库与个性化配置", "id": "section-87" }, { "level": 3, "title": "智能自适应交互与沉浸式引导体系", "id": "section-88" }, { "level": 3, "title": "功能概述与业务价值", "id": "section-89" }, { "level": 3, "title": "标准目录阵列的大规模生成", "id": "section-90" }, { "level": 3, "title": "项目级文件夹与权限的“一键部署”", "id": "section-91" }, { "level": 3, "title": "实时状态监控与智能容错机制", "id": "section-92" }, { "level": 3, "title": "使用范围", "id": "section-93" }, { "level": 3, "title": "需要解决的问题", "id": "section-94" }, { "level": 3, "title": "巴别鸟解决方案", "id": "section-95" }, { "level": 3, "title": "基本介绍", "id": "section-96" } ], "images": [], "text": "白皮书：主要功能模块 数据传输模块 数据传输模块是巴别鸟企业网盘的核心组成部分，负责管理上传、下载、同步盘和映射盘的数据传输。这一模块采用多种技术来确保数据的安全性、可靠性和高效性。 技术特点 文件分块: 数据传输模块采用文件分块技术，将大文件分成小块，以便更有效地传输和存储。这不仅有助于减少网络流量和服务器资源的消耗，还支持断点续传和增量上传下载。 哈希验证（秒传）: 在数据传输过程中，哈希验证用于确保文件的完整性。每个文件块都有相应的哈希值，服务器和客户端会相互验证这些哈希值，以检测是否有数据损坏或篡改。 同时，如果存储系统中已经有相同哈希码的文件，该文件就不用再次上传。实现秒传功能。 SSL传输: 数据传输模块使用SSL（安全套接层）协议来加密数据传输，以确保数据在传输过程中的保密性和安全性。这对于敏感企业数据的传输至关重要。 断点续传: 巴别鸟企业网盘支持断点续传，允许用户在传输中断的情况下从上次中断的地方继续上传或下载文件，而无需重新开始整个过程。这节省了时间和带宽。 增量上传下载: 数据传输模块还支持增量上传和下载，允许用户只传输发生更改的部分的文件分块，而不是整个文件。这在大型文件和频繁同步的情况下非常有用。 优势 数据完整性: 文件分块和哈希验证确保了数据的完整性，降低了数据损坏或篡改的风险。 数据安全: SSL传输提供了数据的端到端加密，确保数据在传输过程中不会被窥探或窃取。 效率: 断点续传和增量上传下载提高了数据传输的效率，节省了时间和带宽。 节约存储空间： 使用文件哈希码技术可以在磁盘上只存储一份相同哈希的文件。无论文件路径、文件名如何变化，或者在网盘中有多少个文件副本，文件实际存储空间就只占用一个文件的容量。（去重存储） 高速上传： 相同哈希值的文件不需要再次上传，如上传网盘上已存在的文件，检测到同样哈希值就会自动标记为上传成功，无需再次上传。 数据传输模块是巴别鸟企业网盘的关键组成部分，通过采用这些技术特点，它确保了用户可以安全、高效地上传、下载和同步其文件。这一模块的功能是使巴别鸟企业网盘成为一个可信赖的数据管理平台。 新建模块 新建模块主要负责文件、部门、项目、模版、文件夹的创建。在巴别鸟中可以做到无需上传文件就直接新建文件进行工作。 文件的新建 Office文件 巴别鸟支持在线创建空白word文档、Excel文档、PPT文档。 使用客户端新建会默认打开本地office相应组件创建并编辑文档。 在网页上新建会使用在线office创建并编辑文档。 Office文档都可以使用在线编辑（无需安装office）或使用客户端选择本地编辑（使用电脑上安装的office编辑）。 在线编辑支持多人实时协同编辑。 使用客户端调取本地office编辑时文档会自动锁定编辑，防止其他人在编辑时也编辑该文档造成冲突。 文本代码类文件 巴别鸟文本编辑器可在线创建并打开所有的文本类文件，如RTF、TXT、HTML、MD、CSS… 为了客户使用方便，公有云版本仅支持新建TXT和MD（markdown文件），私有云用户如需要其他格式的文本文件创建可以要求开放。 文本编辑器不同于在线office，不支持协同编辑，但可以在线编辑文本类文件。 思维导图及流程图。 巴别鸟自带思维导图模块，可以在线新建及在线编辑思维导图文件。 思维导图文件默认保存为KM格式。也可以导出为KM、TXT、MD、SVG、PNG、Xmind格式。 巴别鸟也可选支持创建流程图，但需要购买相应的模块授权（非标准版默认自带）。 其他第三方模块。 符合WebAPI的互联网应用理论上都可以对接巴别鸟并新建文件。巴别鸟提供第三方应用对接服务。 从模版创建 不少客户需要大量创建相同结构的文件夹或从某个特定模版（如企业PPT模版）创建文件。巴别鸟支持从模版创建文件夹和文件。 创建模版。 拥有部门文件管理权限的人可以在新建菜单里创建模版。 点击创建模版后会生成一个模版文件夹，模版文件夹类似于普通文件夹，可以拖动文件到文件夹中上传、新建文件夹及部门。 在模版文件夹根目录中上传的文件即成为文件模版，在模版文件夹中创建的文件夹就是文件夹模版。如下图： 图：在模版文件夹中显示 图：在新建模版时显示 从模版创建。 有创建文件及文件夹权限的部门都可以新建时选择模版快速创建和模版一致的文件或文件夹。 新建部门、项目 使用新建功能也可以创建部门和项目。 创建部门。 只有在企业文件根部门下才能创建部门，部门文件属于企业，超级管理员能看到根部门和整个文件树。 拥有子部门管理权限的用户（默认部门经理角色）可以创建子部门。 部门文件夹可以新增部门成员，并完成部门级别的管理。 只有加入部门的成员（部门成员）及上级部门拥有“查看子部门文件”权限的成员才能访问部门文件。 部门成员由在该部门的角色决定基本权限。 可以用文件权限管理的方式针对文件（文件夹）做权限管理 项目。 用户可以在个人文件或企业文件的部门文件夹下创建项目。 项目可以跨部门、跨企业邀请项目组成员，甚至可以邀请企业外的非注册用户。 拥有个人文件的人都可以创建个人项目，要在部门下创建项目用户角色需要有“创建文件夹/项目“权限。 项目文件夹中支持创建子项目。 项目文件夹的上级一定是个部门或者是个项目，这意味着不能在普通文件夹下创建部门。 项目创建者默认为项目管理员，项目是可以转交的，可以把项目管理员转交给其他成员及其他部门。 项目内成员的权限由创建项目时指定。项目相对是一个独立的共享文件夹。 新建普通文件夹 个人文件下创建文件夹。 用户可以在个人文件下可以任意创建文件夹，并自行管理。 企业文件下创建文件夹 企业文件下需要在部门中创建文件夹（所有的文件夹都有归属部门）。 在所在部门中角色具有“创建文件夹/项目“权限的用户可以创建文件夹。 只要角色具有“创建文件夹/项目“权限的用户可以在部门中任意普通文件夹中创建子文件夹。 文件管理 简介 文件管理模块是巴别鸟企业网盘的核心功能之一，用于用户管理和操作文件及文件夹，并根据权限推送给用户不同的文件列表。也是用户使用网盘的主要界面。该模块提供了广泛的功能，以满足企业用户对文件的管理和组织需求。 技术特点 A．文件访问与组织 分页载入技术: 文件管理模块使用分页载入技术，由服务器端数据库进行文件的排序查询操作，并把文件列表返回前台进行分页载入。这样一个文件列表可以分页载入几十万行数据，确保用户能够高效载入和浏览大量文件，而不会影响性能和用户体验。 树状展示文件列表: 巴别鸟支持树状展示文件列表，使文件的组织结构更加直观，用户可以轻松导航和管理文件夹。 权限控制: 根据用户的权限不同，文件管理模块会动态显示适当的列表项目，不同用户看到的文件列表内容根据权限不同而不同。以确保只有授权用户可以查看、编辑或删除特定文件和文件夹。 B. 文件排序和快捷操作 多维度排序: 支持多维度排序，用户可以按照文件名称、最近版本、文件大小等不同维度进行排序。 文件名排序: 不同于大多数网盘应用，巴别鸟文件名排序支持多位数字按顺序排序，使文件名包含数字编号的文件能够准确排序。（大部分网盘文件名排序仅首字母排序如：1、2、10、3、4，但在巴别鸟可以正确显示排序为：1、2、3、4、10） 自定义全局排序: 用户在设置里可以自定义适合自己的全局使用的排序方式，同时系统会记住上一次用户在文件夹选择的排序方式，下一次打开文件夹也按上一次的排序显示。 C. 文件展示和详细管理 列表模式和瀑布流模式可切换: 支持列表模式浏览文件夹，同时可以切换为瀑布流模式预览。 支持瀑布流模式浏览文件夹（文件缩略图），使文件的浏览更加流畅和直观。 图片较多的文件夹会自动适配为瀑布流模式显示。 文件详情页面: 每个文件和文件夹都有详细的详情页面，用户可以管理文件信息，增加文件注释，查看文件访问日志，对文件访问进行统计并生成报表。 文件详情页面也能管理文件的版本。 评论区: 每个文件或文件夹都自带评论区，支持用户评论和@提及其他用户，促进团队协作和反馈。 文件关联: 支持文件关联文件，允许用户在相关文件之间建立连接，以便更方便地访问相关信息。 文件关注提醒: 用户可以提醒有权限查看文件的人关注文件或文件夹，确保重要文件不会被忽视。 D. 高级搜索和筛选 高级搜索 巴别鸟支持高级搜索功能，可以根据关键字、全文内容、时间、文件格式、上传者、搜索范围、搜索类型等维度进行高级搜索。 搜索 巴别鸟也支持全文搜索，可搜索文件内容里的关键字。 也可使用文件名搜索、标签搜索找到对应文件 搜索的结果可以通过筛选的方式再次搜索或筛选 筛选功能: 可以根据文件标签、类型、文件说明关键字、大小、版本、上传者、照片元数据等进行筛选，以快速定位所需文件。 文件标签和分类: 用户可以给文件打标签，以更好地组织和分类文件。 标签可以有企业统一管理，以保证标签符合规范。 左侧栏可以加入标签快捷方式使用。 常见文件管理功能 A. 文件传输和操作 上传和下载文件: 用户可以上传和下载文件，确保数据的灵活传输。 支持文件夹拖动上传，以方便大批量文件的传输。 浏览器支持文件夹打包下载（少于100个文件或小于500MB大小的文件夹） 客户端支持文件夹直接下载（传输列表） 文件和文件夹的新建: 用户可以新建各类文件和文件夹，同时支持从模版新建文件或文件夹，以提高工作效率。 文件复制和移动: 用户可以复制和移动文件或文件夹，以方便组织文件。 支持将文件或文件夹复制到指定目录，以便文件的备份和管理。 文件归档: 用户可以将文件归档到档案库，以便长期保存和检索。 文件置顶: 个人文件支持将文件或文件夹置顶，以便快速访问重要文件。 部门或项目管理员可以置顶部门文件或项目文件，方便部门成员和项目成员快速访问重要文件。 创建文件或文件夹快捷方式: 用户可以创建文件或文件夹的快捷方式，以方便快速访问。 上传新版本: 用户可以上传新版本的文件，系统会自动检测重名文件并提供是上传新版本还是重命名文件的选择。 点击上传新版本按钮可以直接上传新版本。 文件打印为加水印PDF: 开启水印的时候，支持将文件打印为加水印的PDF文件，以确保文件的传播安全性和保密性。 锁定文件: 文件使用客户端编辑时会自动锁定防止冲突。 用户也可以在文件列表中手动锁定文件，以防止其他用户的编辑和冲突。 文件预览: 支持大多数文件预览，以快速查看文件内容。要了解更多可查看 预览与转码 章节。 文件列表展示缩略图: 文件管理模块可以在文件列表中展示文件的缩略图，使文件的浏览更加直观。 批量文件上传下载: 巴别鸟提供客户端专用的上传下载模块，支持批量文件的上传和下载，同时提供传输文件列表展示。 查看文件详情及版本管理: 巴别鸟有专门的文件详情界面。在文件详情里可以添加文件说明，查看文件基础信息，图片文件可以查看元数据，同时还可以在详情里查看文件日志及文件访问、使用情况，管理文件的版本。 B. 文件安全和权限控制 文件访问控制： 部门管理员或项目管理员可以设定文件访问控制，精确的控制每一个文件或文件夹针对每一个用户或某个角色的访问权限。 文件访问控制的优先级高于成员的部门角色权限。譬如：一个部门成员角色拥有某文件的编辑权限，但部门管理员使用文件访问控制把该成员对该文件的权限改为“不可见”，该成员将不能访问该文件。 文件分享: 支持分享文件和文件夹，允许用户设置详细的访问权限，以控制文件的访问。 文件快照分享: 针对只想分享当前版本的需求，用户可以创建文件的快照分享，快照分享不会受文件内容更新而改变，保持建立快照时的版本。 版本管理 版本管理概述 版本管理是巴别鸟企业网盘的重要功能之一，它允许用户跟踪和管理文件的不同版本，确保文件的历史记录和更新能够得以保留和查看。巴别鸟的版本管理功能非常强大，支持多种更新方式以及版本的回滚和查看。 技术实现 版本管理使用文件分块和增量保存技术来存储文件版本。这意味着每次文件的更改都会生成一个新的版本，而这些版本仅存储所做更改的数据块，以减小存储需求并提高效率。企业管理员可以在企业控制台中设置文件版本的保存数量和保存时间，以控制版本管理的策略。 版本管理功能使用户能够灵活管理文件版本，从而确保文件的完整性、历史记录和安全性。版本管理是巴别鸟企业网盘的一项核心功能，旨在提供卓越的用户体验和数据安全性。 版本更新方式 巴别鸟允许用户使用多种方式更新文件版本，包括： 手动上传新版本: 用户可以右键点击文件，选择上传新版本，手动上传新文件，并将其保存为文件的新版本。 同名文件检测: 上传时巴别鸟可以检测到文件名相同的文件，用户可以选择将新文件上传为已有文件的新版本。 客户端编辑保存: 如果用户使用客户端编辑文件并保存，巴别鸟将保存所做的更改作为文件的新版本。 在线编辑保存: 如果用户在网页上使用在线编辑功能编辑文件并保存，也将生成新版本。 同步文件夹编辑: 巴别鸟客户端会监控同步文件夹的更新，在同步文件夹中编辑或覆盖文件并保存会生成新版本。 映射盘编辑: 编辑映射盘中的文件并保存，更新的文件也会保存为新的版本。 版本管理功能 巴别鸟版本管理模块具有以下功能： 版本回退: 在文件的版本列表中，用户可以选择将旧版本置为当前版本，实现版本回退的功能。 版本下载: 用户可以选择下载历史版本，以便访问以前的文件版本。 版本预览: 版本管理模块允许用户在点击旧版本文件时进行预览，以查看该版本的内容。 版本对比： 在巴别鸟预览器预览文件时，可以选择文件对比功能，该功能支持选择旧版本和新版本进行对比。 版本日志: 用户可以为每个文件版本添加日志，以记录版本的重要信息和更改历史。 企业控制 巴别鸟企业网盘的版本管理功能允许企业管理员在企业控制台中进行高级设置，以满足企业的特定需求。企业管理员可以根据公司政策和合规要求，设置文件版本的保留数量和保留时间，以满足不同文件类型和部门的需求。 这样的版本管理系统保障了文件的数据一致性、可追溯性，以及用户数据的完整性。同时对勒索病毒这类改变文件可读性的病毒具有强大的防护性，因为勒索病毒更改文件需要更新的文件，而更新的文件将形成新的版本，用户只要回退版本就能拿到被攻击前的文件。 搜索 搜索模块概述 巴别鸟企业网盘的搜索模块是一个关键的功能，它基于强大的Elasticsearch技术和数据库查询技术开发，旨在提供高效、精确和全面的文档搜索功能。搜索模块不仅支持全文搜索，还可以搜索文档的说明、注释和文件名，满足不同用户的搜索需求。 带权限判断的搜索 巴别鸟的搜索模块不仅具备强大的搜索功能，还采用高级权限管理技术，动态判断用户权限，确保用户只能看到其权限范围内的文件。搜索结果是根据用户的权限动态生成的，这意味着用户共享的文件中，只有用户有权限查看的文件才会被搜索到。这是一项关键的技术，特别在企业环境中，权限是随时变化的。 技术基础 Elasticsearch: Elasticsearch是一款开源搜索引擎，它以高效的分布式架构和强大的全文搜索能力而闻名。巴别鸟使用Elasticsearch作为核心搜索引擎，以支持全文搜索和高级查询功能。 数据库查询: 除了Elasticsearch，搜索模块还利用数据库查询技术来搜索文档的元数据和标签信息，以提供更全面的搜索结果。 文档解析: 搜索模块使用文本提取技术，可以从各种类型的文件中提取文本信息。这些提取的文本信息用于搜索引擎的索引和查询。关键字抽取。 分词优化: 巴别鸟进行了大量的分词优化工作，特别针对中文词汇，以提高搜索引擎的分词准确性和性能。中文分词的优化对搜索结果的准确性起到关键作用。 搜索功能 巴别鸟搜索模块包括以下主要功能： 全文搜索: 用户可以执行全文搜索，查找文档中的文字内容，以找到与关键字相关的文件。 文档描述和注释搜索: 搜索模块支持搜索用户添加到巴别鸟的文档的说明和注释，使用户可以更轻松地找到特定信息。 文件名搜索: 用户可以进行精确的文件名搜索，以查找特定文件。 标签搜索: 可进行标签的搜索、查询、分类显示 高级搜索 巴别鸟支持高级搜索功能，可以根据关键字、全文内容、时间、文件格式、上传者、搜索范围、搜索类型等维度进行高级搜索。 性能优化 搜索模块对服务器性能要求较高，因此对于私有化部署的用户，建议将搜索模块部署在独立的虚拟机或服务器上，以减少对其他模块的性能占用。 未来发展 未来版本的巴别鸟将继续改进搜索模块，结合AI技术，例如ChatGPT，实现文档内容的问答式聊天对话搜索，为用户提供更智能的搜索体验。目前基于AI的文档分析及客服系统“智巢AI”已经上线，详情可查阅智巢AI章节。 搜索模块的不断改进将有助于用户更快速、准确地找到所需的文件和信息，引入AI系统后，用户可以用问答的形式获取信息，并能交叉多个文档的内容得出完整的结论，能大幅度提高生产效率和工作效率。 office在线编辑 在线编辑模块概述 巴别鸟企业网盘是OnlyOffice多年的官方合作伙伴，巴别鸟企业网盘的在线编辑模块基于OnlyOffice技术研发并优化了中文字体的载入和显示问题。巴别鸟在线编辑器支持多种文档格式，包括Microsoft Office（Word、Excel、PPT）和WPS Office。 巴别鸟和OnlyOffice的合作详情可以参见OnlyOffice官方网站： https://www.onlyoffice.com 技术基础 在线编辑模块的技术基础包括： OnlyOffice编辑器: OnlyOffice是一个强大的在线办公套件，支持多种文档格式的在线编辑。巴别鸟将其集成到网盘系统中，以提供优质的在线编辑体验。 中文字体优化: 为了克服OnlyOffice中对中文字体载入效率的不足，巴别鸟进行了优化，通过采用字库本地化技术，大幅提高中文字体的载入和显示速度，从而提升用户体验。 文档锁定: 巴别鸟同时支持客户端编辑和在线编辑，这意味着为防止文件版本冲突文件在线编辑时要锁定不能客户端编辑，文件客户端编辑时要锁定不能在线编辑。 主要功能 巴别鸟的在线编辑模块包括以下主要功能： 多格式支持: 用户可以在线编辑和查看Microsoft Office（Word、Excel、PPT）和WPS Office格式的文档。 协同编辑: 在线编辑模块支持多用户同时协同编辑文档，用户可以实时查看其他用户的更改，并共同编辑文档。这种协同编辑功能对于团队协作非常有用。 兼容性: 巴别鸟的在线编辑模块兼容微软Office，能很好的在网页上还原office的版式和字体。确保文档排版和格式在不同编辑器中打开的良好兼容性。 开放API: 巴别鸟开放在线编辑器的API，允许其他企业软件调用该API，将在线编辑功能集成到其他应用中。 用户体验 在线编辑模块的目标是提供用户友好且流畅的在线编辑体验。用户可以直接在网盘中打开需要编辑的文档，编辑完后即时保存，而无需离开网盘界面。这种无缝集成提高了用户的效率，使编辑文档更加便捷。 同时巴别鸟权限配置支持“仅在线编辑”，这意味着可以让一些用户仅能在线编辑文档但不能下载获取文档。 企业协作 巴别鸟在线编辑模块不仅适用于个人用户，还为企业提供了一个协同办公的平台。团队成员可以一起编辑文档，共享想法，并通过实时协作提高工作效率。 开放API 巴别鸟在线编辑器API允许企业将在线编辑功能集成到其自有软件或第三方软件中，使企业能充分使用在线编辑的能力。 其他在线编辑器 巴别鸟标准版还集成了其他在线编辑器，用于在线编辑及创建如MD文件，TXT文件甚至思维导图（如脑图）同时，巴别鸟也可以通过接入第三方API的形式集成其他支持HTML5的在线编辑系统，譬如可以对接微软office365或金山的web office（WPS）。 自带文本编辑器在线编辑。 巴别鸟自带的文本编辑器可以编辑及预览如：TXT、MD、RTF等文本文件，同时也能编辑CSS、JS、JSP…等代码文件，便于用户快速创建文档记录。 自带脑图（思维导图）编辑器。 巴别鸟自带思维导图模块，可以在线新建及在线编辑思维导图文件。 思维导图文件默认保存为KM格式。也可以导出为KM、TXT、MD、SVG、PNG、Xmind格式。 巴别鸟也可选支持创建流程图，但需要购买相应的模块授权（非标准版默认自带）。 客户端编辑 客户端编辑概述 巴别鸟企业网盘提供了强大的客户端编辑功能，用户可以轻松调用本地编辑软件对云端文档进行编辑，编辑保存后文件会自动上传到云端。这个功能不仅提高了用户的便捷性，还有助于避免文件版本的冲突，从而提高工作效率。 在客户端文件列表要编辑的文件上点击右键，选择编辑即可打开客户端编辑。 客户端编辑的实现原理决定了只要本地有编辑程序，所有类型的文件都可以进行客户端编辑。 技术实现 客户端编辑功能的实现技术包括： 客户端集成: 巴别鸟的Win客户端和Mac客户端均支持本地编辑软件的调用，这使得用户可以直接在本地软件中打开并编辑云端文件。 缓存管理: 客户端编辑使用缓存技术，把需要编辑的文件从云端缓存到本地并调用本地应用打开。系统监测到正在编辑的文件更新就把更新文件作为新版本上传。良好的缓存管理技术能在保证效率的前提下节约用户本地的磁盘空间。用户也可以在巴别鸟右键菜单手动清除文件的缓存。 文件状态检测: 在进行客户端编辑之前，系统会检测文件的状态，包括文件是否已被其他用户锁定。这有助于防止多人同时编辑同一文件，避免版本冲突。 自动锁定和解锁: 当用户开始编辑文件时，系统会自动锁定文件，以确保其他用户无法同时编辑相同文件。编辑完成后，文件将自动解锁，同时生成一个新的版本，并将修改后的文件上传到云端。 版本冲突处理: 尽管存在锁定机制，但在某些情况下，如网络问题或长时间未编辑时可能出现文件版本冲突。巴别鸟提供了冲突处理界面，允许用户对比选择是使用云端版本还是本地版本作为当前版本。无论用户的选择如何，系统都会确保没有选择的版本也会上传至云端作为历史版本，以防止数据丢失。 主要功能 客户端编辑功能的主要功能包括： 本地编辑: 用户可以通过点击本地编辑按钮，将文件缓存到本地，并使用本地默认应用程序进行编辑。 只要本地有相应的应用程序，理论上巴别鸟支持所有文件的本地编辑。 自动锁定: 文件在编辑时会自动锁定，以防止其他用户同时编辑，从而避免版本冲突。 自动解锁: 编辑完成关闭应用后，文件将自动解锁，并生成一个新的版本，将修改后的文件上传到云端。 版本控制: 所有编辑和上传的文件都将生成新的版本，以便用户可以随时查看和还原以前的版本。 用户体验 客户端编辑功能提供了出色的用户体验。用户可以在本地编辑器中进行编辑，而不必下载文件编辑后再上传。同时不支持在线编辑或在线预览的文件格式也可以通过客户端编辑打开编辑或预览。这提高了编辑效率和工作流程的顺畅性。 技术挑战 客户端编辑功能的技术挑战在于检测文件的状态，自动锁定和解锁，以及文件版本的冲突处理。系统需要准确判断文件是否正在被其他用户编辑，同时在冲突发生时提供用户友好的解决方案。这些挑战需要综合考虑用户体验和数据完整性。巴别鸟客户端编辑是业内少有的能很好处理这些问题的功能模块。 分享及外发 分享功能 巴别鸟企业网盘提供了多种灵活的分享方式，包括邀请分享和链接分享，以满足用户的不同需求。 邀请分享： 邀请分享是一种将文件或文件夹分享给特定人员的方式。特点如下： 身份验证：被邀请者需要进行身份验证，可以通过巴别鸟账号登录或者接收验证码确认身份。 每个被邀请者可以独立管理权限，可设置权限有效期。这意味者同一个邀请分享，不同的被邀请者可以设定不同的访问权限。 权限控制：分享者可以自定义分享权限，包括查看、编辑、下载等权限。这有助于细化控制分享内容。 审批机制：如果用户没有分享权限，分享操作需要经过审批，确保只有授权的人员可以分享文件。 链接分享： 链接分享允许用户创建一个公开链接，供其他人访问文件或文件夹。特点如下： 允许匿名访问：分享者可以选择是否允许匿名访问。如果关闭匿名访问选项，访问者需要拥有巴别鸟账号才能访问。 快照分享：快照分享模式下，分享的内容是分享时的当前版本，即使文件内容更新，快照分享的内容也不会变化。 密码保护：用户可以设置密码，确保只有知晓密码的人能够访问分享链接。 有效期：链接分享可以设置有效期，确保文件不会永久公开。一旦有效期结束，分享链接将自动失效。 自定义设置： 在企业控制台中，管理员可以自定义分享权限、按部门设定分享行为（支持或禁止分享），按文件设定分享规则（禁止分享高密级文件），以及关闭整个企业的对外分享功能。 分享日志： 所有的分享行为和外界访问行为都有独立的日志，每个分享的访问日志都可以查询。你可以知道什么人什么时候访问了分享的文件或文件夹，分享文件更新版本会提醒用户。 统一管理分享： 部门管理员可以统一查看和管理整个部门所有被分享的文件，分享的个人文件也可以在“我分享的文件”栏目统一查看管理，确保不会有遗漏的分享在不知情的情况下泄露。 外发功能（发送文件） 外发功能是一种通过邮件或手机号将文件发送给其他用户以供直接下载使用的方式。外发不同于分享，仅用于接收方下载外发的文件，无需配置权限。特点如下： 发送文件：用户可以使用外发功能将文件发送到其他用户的邮箱或手机号，以便他们可以直接下载并使用。 发送文件功能也可以发送文件给内部用户，收到文件会有通知，点击通知就可以下载或转存文件。 无需权限：外发不需要配置权限，只要用户有分享和下载权限即可使用。 邮件或短信发送：外发可以通过电子邮件或短信发送文件链接，确保接收方可方便地获得文件。 快捷下载：接收方可以通过点击链接直接下载文件，简单便捷。 用户控制和企业策略 用户的分享权限可以由企业管理员进行控制，确保文件的分享和外发都受到严格管理。此外，企业管理员还可以通过企业控制台自定义分享规则和权限，以适应不同的企业需求。 安全性 分享和外发功能均受到严格的安全控制，保护企业文件不被未经授权的人员访问。管理员可以根据企业的安全策略，灵活配置分享和外发的权限和规则。 灵活性与便捷性 分享和外发功能提供了企业灵活性和便捷性，满足了不同用户及场景的需求。用户可以根据具体情况选择最适合的分享方式，从而更好地管理和共享文件。 预览器及批注、讨论 为了让用户能更方便的预览文件，并且可以在预览文件时进行协作讨论提高协作效率，巴别鸟开发了巴别鸟预览器BabelViewer，在巴别鸟上可以预览的大多数文件格式都可以用预览器打开，巴别鸟预览器不仅可以预览文件，还可以通过手绘、文字讨论、语音（仅手机APP支持建立语音批注）等方式在文件内容上和协作者进行交流。同时，巴别鸟预览器还支持版本对比，切换版本查看不同版本批注、批注管理、审批管理等功能。 技术架构 使用canvas开发及多图层技术 预览器基于Html5 Canvas技术开发，使用多图层技术，以在文件预览层上面增加批注和手绘图层，不影响文件内容但可以进行批注讨论和实时手绘。 实时协同模块 预览器的实时协同模块，保证多用户在文件预览时的批注讨论和手绘是实时展示的，这意味着用户可以边批注边讨论文档或设计稿件的问题。 批注点坐标系定位 巴别鸟预览器使用坐标系定位， 保证批注点在不同的分辨率屏幕下，不同浏览器尺寸下的位置一致。 适用的文件类型 巴别鸟预览器能打开绝大多数图片及office文档、PDF文档及矢量图形文件。具体支持的文件类型可参阅 预览转码章节里的 支持在线预览的文件类型 预览器类型 多页文档预览器 支持对多页文档的预览，如word、PPT、PDF等格式。针对多页文档提供适合多页文档的目录、放大、旋转页面等功能。 图片预览器 为更好的预览图片而设计。拥有鹰眼、放大缩小、显示原始比例、旋转等功能。 右键可以复制图片到剪贴版，方便在微信、邮箱里直接粘贴图片。 针对PNG等拥有透明度的图片，可以改变图片背景。 图形预览器 为预览CAD、SVG、单页PDF等矢量图形文件设计，支持鹰眼、分图层显示、更改背景、鼠标拖动区域放大、矢量放大。对SVG文件可以切换编码模式。 3D预览器 为预览3D文件设计，可以旋转、鼠标滚轮拉近放远3D文件、炸开图像、支持3D空间的批注。 批注种类 文字讨论区 文字讨论区可以在预览文件的任意区域创建（双击建立文字讨论批注）。 文件的协作者如果有查阅批注权限都可以看到批注，并参与讨论。 批注内容实时显示，一个文字批注讨论区相当于针对批注内容的群聊。 支持插入附件进行讨论，也支持@等聊天功能。 可以设定批注的可见性，如：仅企业成员可见、所有人可见、仅批注者自己可见。 文字标注 文字标注可以在文档内容或照片上添加标注 选定文字批注 针对有文字的文件，如word、PDF，可以选择一段文字进行批注。 特殊符号插入 针对特殊需求的稿件，可以插入修订符号或焊接标记（如CAD图纸） 建立图形批注 也支持使用图形框选批注，支持矩形、椭圆及箭头。 语音批注 巴别鸟移动设备APP可以建立语音批注。在网页和客户端可以查看（收听）语音批注，但不能创建。 手绘批注 支持在稿件或文档上实时绘制，参与者可以实时看到绘制的线条，并且标记手绘者昵称。 功能模块 批注管理模块 可以管理创建的批注和批注状态，查阅其他版本批注，并切换到相应的版本 评审工作区 巴别鸟可以在文件评审时使用批注，并显示评审的相关面板，让评审人员能更准确便捷的传达评审信息。 鹰眼 鹰眼可以在图像放大时显示图像视口所在的区域。 版本对比 巴别鸟预览器支持文件对比功能，也可以对比不同版本的文件。 文件目录 对于拥有目录的文件（word、pdf），巴别鸟也支持预览时显示文件目录。 文件评审 巴别鸟企业网盘提供了强大的文件评审功能，旨在帮助用户高效管理文件的审批和修订过程。文件评审是一种协同工作流程，允许用户发起文件评审，邀请评审人员查看文件，提供批注和建议，以最终确定文件是否需要修改或批准。 主要特点 多文件评审：支持同时评审多个文件，用户可以一次性发起对多个文件的评审，确保高效的审批过程。 文件锁定：文件在评审过程中会被自动锁定，以防止其他用户进行编辑或上传新版本，确保文件内容在评审期间不会被更改。 文件预览和批注：评审人员可以在预览文件时添加批注，填写评审意见，以提供详细的反馈。这有助于更好地理解文件内容和提供有针对性的建议。 评审流程：用户可以选择不同的评审流程，包括自由定义审批流程、使用预设审批流程，或限用特定审批流程。这允许不同部门根据其需求选择适当的审批流程。 多阶段审批：审批流程支持多个阶段，每个阶段可以设置一个或多个审批者。用户可以定义通过比例，例如，50%的审批者通过即可通过某个阶段。 邀请外部审批者：用户可以邀请外部成员（通过邮件或手机号）参与文件评审，以获得更多不同角度的反馈，譬如：论文答辩时邀请外部专家。 审批报表：每次文件评审后，会生成审批报表，记录每个阶段参与者的评审意见，以便审批结果的跟踪和分析。 评审签名：支持评审结束后在稿件上插入签名，并下载为PDF。 我的评审栏目：用户可以在“我的评审”栏目中查看和管理与自己相关的所有评审文件的各个阶段，包括发起的评审和邀请参与的评审。 技术架构 文件评审功能的实现涉及以下技术和模块： 评审流程定义：后台定义不同的评审流程，包括阶段设置、审批者选择、通过比例设定等。这些流程可供前台用户选择。 部门特定审批流程：不同部门可以选择不同的审批流程，根据需要选择自由定义、预设或限用特定审批流程。 多阶段审批：可实现多阶段审批，每个阶段具有不同的审批要求，包括审批者的选择和通过比例。也可以设定某阶段是否能跳过。 外部审批者邀请：支持邀请外部成员参与文件评审，通过邮件或手机号进行邀请。 审批报表：生成审批报表，记录每个阶段的评审意见，以便审批结果的跟踪和分析。 文件评审的优势 文件评审功能有助于用户高效管理文件的审批和修订过程，确保文件内容的准确性和合规性。用户可以通过文件评审，确保文件经过充分的审查和讨论，以满足其工作需求和合规要求。这个功能的引入增加了文件协作和管理的深度，为用户提供了更强大的文件协作工具。 权限管理 巴别鸟企业网盘的权限管理是其核心功能之一，它贯穿整个系统，确保用户能够安全、合规地访问和管理文件。巴别鸟权限体系包括角色权限和文件权限两个主要方面。 角色权限 定义角色：巴别鸟允许在企业内定义不同的角色，每个角色可以包括一组特定的权限，用于控制用户在部门文件夹的访问和操作。这些角色可以根据部门管理需求进行创建，例如“部门管理员”、“部门成员”等。 部门角色权限：每个部门成员可以根据其在不同部门的角色分配不同的访问权限。这意味着用户可以在不同部门享有不同级别的权限。 灵活管理：巴别鸟的角色权限支持多个部门角色，并且可以在不同部门内同时使用相同的角色。角色的权限内容更改后，使用相同角色的成员的权限也会相应更改。 权限组合：巴别鸟角色权限支持30多种可选权限进行组合，以实现精细化的用户权限控制。这些权限涵盖了各种访问和操作行为，如预览、上传、下载、编辑等。 角色可选权限列表： 文件权限 自定义权限：文件权限也可以在后台自定义，用户可以选择特定权限类型和名称。这些自定义文件权限将用于文件分享、项目管理和文件权限控制。 文件访问控制：文件访问控制允许部门成员在文件和文件夹上设置具体的访问权限，以覆盖部门角色权限。这意味着可以更精确的控制部门里某个文件或文件夹的访问行为，文件访问控制仅适用于部门成员和项目成员。 高优先级：文件访问控制的权限具有较高的优先级，如果设置了文件访问控制，将覆盖成员的部门角色权限或项目权限。用户可以根据需要设置文件的访问权限。 部门文件和文件夹控制：用户可以为部门文件和文件夹启用文件访问控制，以控制特定文件或文件夹的访问权限。 有效期：文件访问控制可以设定有效期，到有效期后，文件访问控制的约束失效。譬如：给某个没有文件编辑权限的部门成员该文件的编辑权限，有效期3天，3天后文件访问控制赋予的权限就会失效，部门成员对文件的权限就变成成员角色的权限。 总结 巴别鸟企业网盘的权限管理是一个全面的系统，可以满足企业不同部门和项目的特定需求。角色权限和文件权限相互配合，确保用户可以精确控制文件的访问和操作。这一功能有助于提高安全性、合规性和工作效率。 同步 概述 文件同步是巴别鸟企业网盘最受欢迎的功能之一。它允许用户将本地任意文件夹同步到云端或者把云端任意文件夹同步到本地，实现云端和本地文件的实时同步。这个部分包含了以下关键功能： 同步管理：巴别鸟支持创建多个同步，并可在同步管理列表里统一管理。 多人协作：巴别鸟同步是为多人协作而设计的。它自动锁定文件，防止多人同时编辑造成冲突，还有冲突处理机制和版本管理。 和权限一致：巴别鸟同步会判断用户的权限。没有下载权限的用户也不会因同步而下载文件，保证权限的一致性和闭环，这意味着，用户可以通过权限来设定哪些文件夹可以同步。 多种同步类型：巴别鸟支持多种同步类型，用户可以根据具体需求选择合适的同步方式： 双向同步：云端和本地文件夹保持内容一致，任何一侧的修改都将同步到另一侧。 单向向上同步：本地更新会同步到云端，但云端更新不影响本地。 单向向下同步：云端更新会同步到本地，但本地更新不影响云端。 强大技术优势：巴别鸟企业网盘同步功能拥有多项技术优势，确保性能和稳定性： 支持大规模文件夹：巴别鸟支持高达20万个文件的文件夹同步。 文件编辑锁定：编辑同步文件时，文件会自动锁定，以防止多人编辑引发冲突。 冲突处理机制：针对同一文件的编辑冲突，巴别鸟提供了冲突处理机制，确保文件版本的完整性。 版本管理：文件同步功能和版本管理配合，能保证本地的文件夹也不会因为误操作等原因被覆盖从而丢失内容，即使出现文件冲突，冲突的两个版本文件也都会得到保存。 异步情况下的错误处理：文件同步功能还包括对异步情况下的错误处理和修复。 使用方式 开启同步：本地文件夹右键菜单选择巴别鸟——同步该文件夹。 选择同步方式：用户可以在同步时选择合适的同步方式，包括单向同步、双向同步等。 权限配置：通过权限配置，用户可以实现更多的自定义同步方式，根据需要限制文件删除或其他操作。 多人协作：多人协作下，文件编辑时会自动锁定，以避免多人同时编辑造成冲突。冲突处理机制确保文件版本的一致性。 版本管理：文件同步功能支持版本管理，用户可以查看以前的文件版本并进行恢复。 总结 巴别鸟企业网盘的文件同步功能是一项出色的工具，可以实现云端和本地文件的实时同步。多种同步方式、权限配置、多人协作、版本管理等技术优势确保了高性能、稳定性和安全性。 虚拟映射盘 概述 虚拟映射盘：巴别鸟企业网盘引入了虚拟映射盘功能，提供了一种无缝连接云端文件的方式，在windows资源管理器或着mac的访达中都可以类似于访问本地磁盘一样访问映射盘，从而实现轻松访问云端文件的体验。 技术实现：巴别鸟虚拟映射盘使用了类似OneDrive、iCloud的技术方案，它在操作系统中创建了一个虚拟磁盘，将云端文件映射到用户的本地计算机上，使得这些文件在用户的文件浏览器中可见。 主要特点 本地访问云端文件：虚拟映射盘允许用户通过本地文件资源管理器或Finder等工具访问其巴别鸟企业网盘中的文件和文件夹。 无本地存储占用：与传统的文件同步方式不同，虚拟映射盘并不将云端文件实际存储在用户的本地磁盘上，因此不会占用本地存储空间。文件只在需要时进行缓存或下载。 在线访问：虚拟映射盘需要网络连接才能访问云端文件。文件图标实际上只是云端文件的链接，因此需要在线才能查看和操作这些文件，权限也和云端一致。 透明操作：用户可以像操作本地文件一样操作虚拟映射盘中的文件，包括打开、复制、粘贴、删除等操作。 自动同步：文件的更改会自动同步到云端，从而保持云端文件与虚拟映射盘中的文件的一致性。 关联文件：在巴别鸟映射盘中打开有关联文件的文件，会自动加载关联文件，实现和本地文件夹打开文件一样的效果。譬如：打开含有大量参照文件的DWG（AutoCAD文件）、或者有关联其他文件的Excel图表。 技术优势（对比WebDAV和SMB） 权限一致性：不同于WebDAV或SMB挂载（必须使用兼容WebDAV或SMB的权限规则），巴别鸟映射盘是直接调用操作系统底层文件系统实现的，可以实现和巴别鸟一致的权限控制。（譬如：只能预览但不能下载或另存为。）在WebDAV和SMB中，仅查看权限实际为只读，只要是可见的文件，用户都可以通过只读模式打开并获得文件，失去了对文件的管控。 更高的性能：巴别鸟映射盘直接对应巴别鸟服务器相关接口，没有转发和中间处理环节，可以直接获取服务器提供的文件列表以虚拟方式打开文件夹，所以能提供更高的性能，打开文件列表和查阅文件不会卡顿。使用WebDAV只能打开一个文件夹临时载入一个列表，文件夹文件数量超过一定数量（和设备性能及网速有关，一般数量是超过300个）就会发生严重的卡顿和访问缓慢。使用对象存储系统的超大文件夹WebDAV并不能很好支持。 更安全：巴别鸟映射盘能根据权限判断每个人可以查看的文件夹和文件夹中的文件，不同权限的人查看同一个文件夹看到的内容可以不同，SMB和WebDAV目前做不到。同时巴别鸟的文件分块加密存储于对象存储，但如果是分块加密存储的文件，使用WebDAV就需要分文件解密后才能获得文件列表，这意味着，支持WebDAV的产品要么数据存储没有加密，要么WebDAV性能极差文件数量超过一定范围即不可用。 可控性：不同于使用第三方软件挂载的WebDAV及SMB，巴别鸟映射盘为自主研发驱动器，对驱动器的操作、菜单及运行方式、功能实现都具有可控性，并且能对产品质量及使用体验一致性负责。未来也能有更多的功能扩展。 主流企业级解决方案：无论是微软的OneDrive、Google的Google Drive或是苹果的iCloud、BOX的BOX Drive还是国内主流互联网企业网盘厂商，都使用了类似巴别鸟映射盘的解决方案，而不是简单接入WebDAV（接入WebDAV只要做协议兼容并开放接入即可，实现简单，为什么主流企业级厂商还都花费大量精力自研映射盘呢？）。WebDAV主要应用场景还是不需要进行复杂权限判断也不需要存储加密并开放所有文件的个人或小团队使用。SMB的主要使用场景也是个人及小团队的开放文件共享（明文存储）。 应用场景 虚拟映射盘适用于需要频繁访问云端文件、但不想改变本地磁盘的使用习惯也不想占用本地存储空间的用户。这个功能使得用户可以像访问本地文件一样访问云端文件，并且在其他应用程序里如同打开本地文件夹一样访问网盘，不改变使用习惯，便于文件的管理和使用。 档案管理 巴别鸟企业网盘提供了强大的档案管理模块，用于统一管理和归档企业文件。这一模块旨在帮助企业更好地组织和保留关键文件，同时确保文件的安全性和可访问性。 主要特点 档案管理员：巴别鸟允许超级管理员指定一名或多名企业成员作为档案管理员。档案管理员负责管理归档的文件和档案库。 档案库：归档的文件存储在档案库的根目录中。档案库是企业的资料图书馆，用于长期保留和管理文件。 阅览室：档案管理员可以建立阅览室，将档案库根目录的文件移入阅览室。这样其他企业成员才可以借阅这些文件。 借阅权限：阅览室可以选择不同的借阅方式，包括公开、需要借阅、限定部门公开、限定部门内借阅等。借阅文件时，可以设定权限级别，如仅可阅读、可复制、可下载，并指定借阅时长。 文件归档：归档后的文件不可更改，确保文件的完整性和可信度。这对于长期保留法律和合规性文件非常重要。 档案库搜索：档案库拥有独立的搜索功能，只会搜索档案库内的文件。用户可以快速找到需要的归档文件。 文件隐私：没有借阅权限的非公开文件不会显示预览图，以确保文件隐私性。 技术架构 档案管理模块使用以下关键技术和模块： 档案管理员权限：超级管理员可以指定企业成员为档案管理员，允许他们管理档案库和阅览室。 阅览室设置：档案管理员可以创建阅览室并配置不同的借阅权限和可访问性选项。 归档和保留：文件归档后，需要确保其内容不可更改。这需要技术措施来保护文件完整性。 独立搜索：档案库拥有独立的搜索引擎，用于搜索档案库内的文件，确保用户可以快速找到需要的文件。 档案管理的优势 档案管理模块帮助企业更好地管理文件的归档和保留。通过档案库、阅览室、和不同的借阅权限，企业可以确保文件长期保留、有序管理，并能够满足合规性和法律要求。这一模块还可以作为知识库使用，帮助企业保存重要信息和知识。 日志及报表 巴别鸟企业网盘的日志与报表系统提供了全面的文件使用情况管理、监控、审计和追责功能。这一模块旨在帮助企业管理者及用户深入了解文件活动、访问情况以及系统使用情况，以支持合规性和安全性需求。 主要特点 文件日志：每个文件和文件夹都有独立的日志，详细记录了文件的生命周期内的各种操作，包括创建、阅读、修改、更名、分享、删除、权限更改等。甚至包括匿名分享操作以及访问者的IP地址。这些日志可以导出为Excel报表，用于审计和监控。 文件访问统计：文件详情页提供了文件批注数量、下载次数、打开次数、访问人数和访问人员的统计。 文件夹列表：可以导出文件夹内文件和子文件的列表为EXCEl文件，以便审计和管理。 文件评审记录报表：文件评审操作也被记录为报表，以支持文件评审的审计。 部门日志与报表：部门管理员可以查看整个部门的使用日志，包括文件详细访问日志、上传文件数量、创建子部门数量或项目数量的统计。此外，部门管理员可以统计及管理整个部门分享的文件以及更改过权限的文件。 企业级管理：企业管理员和安全审计员可以查看整个企业的使用行为，包括各个部门的日志和报表，并且还有访问日志和统计分析两个栏目统一查看及管理整个企业的使用行为。这有助于维护企业的合规性和安全性。 访问日志：访问日志记录了整个企业网盘的使用日志，包括用户在网盘中的每个操作。管理员可以进行详细的查询和导出报表。 统计分析：提供了统计分析图表工具，允许管理员查看不同部门的使用活跃度、文件数量、活跃文件排名、新建文件统计、上传文件数量统计以及流量使用统计等。 技术架构 日志记录：系统需要记录每个操作的详细日志，包括操作类型、时间戳、执行者、目标文件、IP地址等信息。 报表生成：管理员能够从日志数据中生成报表，通常以Excel格式呈现，以便审计和监控。 数据分析工具：统计分析工具用于分析和可视化数据，帮助管理员更好地了解系统使用情况。 日志接口：巴别鸟支持通过接口导出日志数据，以使用第三方日志管理及分析工具。 日志与报表的优势 日志与报表系统有助于企业实现以下目标： 合规性：帮助企业遵守法规和内部政策，确保文件操作的合规性。 安全审计：提供审计功能，允许企业检查和监视文件访问和操作，以发现潜在的风险。 性能优化：通过统计分析，帮助企业了解系统的性能瓶颈，以采取适当的改进措施。 用户行为监控：允许企业管理者了解员工的行为，包括文件访问和操作，以确保数据的安全性和保密性。 决策支持：通过数据分析，帮助企业管理者做出更明智的决策，包括资源分配和文件管理。 日志与报表系统是巴别鸟企业网盘的重要组成部分，提供了全面的文件使用情况管理和监控功能，以支持企业的合规性和安全性需求。 动态及通知 动态栏目 概述：巴别鸟企业网盘的动态栏目是一个信息流，用于展示与您有关的文件和用户的动态信息。它提供了一个实时的工作情况总览，帮助您跟踪同事的活动，包括文件的变更、批注、评论等。 实时信息流：动态栏目以实时信息流的方式呈现您和您的团队的协作活动，从而帮助您及时了解团队中发生的事情。 便捷互动：通过动态栏目，您可以直接访问与您有关的文件，回复批注，与同事互动，以更便捷的方式完成协作任务。 动态搜索：您可以搜索动态的历史内容，更精准的定位到相关的动态条目。 通知栏目 通知系统：巴别鸟企业网盘的通知系统用于发送各种与您有关的提醒和通知。这些通知可以以多种方式传达给您，包括邮件通知、手机应用程序通知、桌面通知等。 通知类型：通知系统涵盖了多种通知类型，如@提到您、文件更新通知、审批请求、文件授权请求等。这有助于您保持对各种工作流程的掌握。 个性化设置 信息类型设置：用户可以根据自己的需求在设置中自定义接收哪些动态和通知类型，以确保信息的准确性和有针对性。 应用场景 动态栏目和通知栏目帮助用户了解工作中的重要动态和通知，提高了协作效率，使用户能够更快速地回应同事的协作请求，回复评论以及跟踪文件的变化。 巴别鸟企业网盘的动态与通知栏目是关键的协作工具，它们提供了实时的协作情况总览和各种通知，使用户能够更有效地与团队协作，并保持对工作流程的了解。这些功能有助于提高协作效率，确保重要信息不被忽略。 讨论组 概述 讨论组功能：巴别鸟企业网盘为每个部门和项目创建了讨论组，作为部门或项目内部成员的群聊空间。讨论组允许成员在其中发布文本和图片，进行讨论，并分享附件。 成员互动：讨论组提供了一个方便的平台，使成员能够互相沟通、协作和讨论项目相关事项，从而增强团队合作和信息分享。 主要功能 信息发布：讨论组成员可以发布文本消息和图片，以实现实时的讨论和交流。 附件分享：成员可以轻松分享附件，如文档、表格和其他文件，以便共享和讨论。 可见性：讨论组中发布的信息对所属部门或项目的所有成员可见，从而确保信息共享。 应用场景 讨论组适用于部门内部和项目团队之间的信息交流和讨论。它们促进了实时协作，有助于解决问题、分享见解和跟踪进度。 总结 讨论组为部门和项目成员提供了一个便捷的协作平台，用于共享信息、讨论事务和协同工作。这些讨论组有助于加强内部沟通，提高团队的效率和生产力。 工作台 概述 工作台功能：巴别鸟的工作台是一个个性化的界面，允许用户将常用的文件夹、工作内容以及各种信息以卡片的形式集中在一个界面上展示。每个卡片直接呈现内容，可进行操作，用户可以根据需要自由调整卡片的位置和排序。 个性化：工作台提供了多个备选卡片，用户可以自由选择需要添加到工作台上的卡片，根据自己的需求进行定制。这使得用户能够在一个页面上获取与其工作相关的信息和功能。 主要功能 卡片展示：每个卡片代表不同类型的信息或工作内容，例如最近访问的文件、上传的文件、关注的文件、分享的文件、批注过的文件、标签云图等。 自定义图表：用户可以自定义图表或卡片，以便将特定项目、文件夹或其他信息添加到工作台上，以满足其独特的需求。 卡片排序：用户可以通过拖放方式对卡片进行排序，以便将最重要或最频繁使用的信息放在前面。 应用场景 工作台适用于用户需要集中管理和访问与其工作相关的信息和资源的情况。用户可以将常用的文件和项目放在工作台上，以提高工作效率。 企业管理后台（企业控制台） 巴别鸟企业控制台集中了管理员对整个企业进行管理的功能。企业管理员可以在企业控制台中配置企业网盘的各个选项、开启或关闭需要的功能模块、设定组织结构、自定义角色和权限，管理成员、设置水印、设定部门安全策略、iP访问策略、绑定账户和mac地址、监控网盘使用情况…. 主要栏目 企业配置：综合管理企业网盘的配置项，譬如空间分配、是否允许个人文件、允许的文件上传大小、历史版本有效期或历史版本数量、各种管理员分配、更改logo及登录背景、禁止或开启对外分享、是否接受邮件通知。各种企业配置选项里面都可以在企业配置栏目找到。 组织结构：统一管理和维护企业的组织结构及部门。能树状查看部门和管理部门。查看部门成员、分配部门空间、创建子部门、设定部门安全策略… 权限管理：创建角色和更改角色权限，同时可管理自定义文件权限。 成员管理：可以查找和筛选整个企业的成员账户，新增成员、批量导入成员、分配成员部门及角色、详细查看及管理每一个成员的信息及使用情况、成员离职一件交接、成员账户的增删改查、成员空间和流量的分配及限制。 标签管理：统一管理企业所使用的标签，添加标签和给标签分类，便于用户选择标签。 文件配置：添加文件审批可选流程，管理已经添加的审批流程。同时拥有文件黑名单功能，可以阻止特定类型的文件上传。 企业通知：创建企业通知，管理历史企业通知列表、发送企业通知。 分组管理：建立分组及管理分组。前台分享文件时可以选择分享给什么分组。 水印设置：管理文档的水印类型，水印参数调整，水印显示范围设定。 访问日志：管理及查询整个企业网盘的所有访问记录。可导出日志报表。 IP策略列表：可通过IP策略管理企业文件的上传下载行为。譬如：某个IP段禁止下载文件，回到某个IP段即可下载文件。 Mac地址绑定：可以把用户账号和特定设备mac地址绑定，让账号只能在绑定mac地址的设备上使用。也可以创建mac地址池。 统计分析：统计分析网盘的使用情况。包括系统活跃度、文件数量统计、活跃文件、一段时间内的新建文件数、每个月上传数、流量使用情况。 工作台推送：设定工作台的默认显示卡片。 系统配置（仅私有部署版本）：配置邮件服务器，绑定第三方SSO认证，设定第三方认证登录方式。 第三方账号同步（仅私有部署版本）：设置第三方账号同步时间，查询第三方账号同步记录。 可选模块（仅私有部署版本）：选择企业需要展现的功能模块，关闭某些功能模块。 监控预警：设定异常行为的预警，遇到异常行为通知管理员（譬如：用户大量删除文件） 传送文件配置：数据摆渡系统的配置，允许多套巴别鸟间进行数据摆渡。配置数据的接收端口及发送端口。 API 巴别鸟API模块负责巴别鸟开放API，私有云用户可以在企业控制台免费申请及开通开发者账号，获取开发者id、密钥几Token、并设定回调URL 回调URL设置规则：http://客户域名 /public/babelAuthResult.do 譬如：http://testqiyeban.babel.cc/public/babelAuthResult.do 设置路径：企业控制台——企业配置——开发者账号 访问以下链接获取最新API文档： https://www.babel.cc/p/api integration.do 第三方登录（SSO） 巴别鸟支持集成第三方登录（SSO）平台，以实现单点登录及统一登录。并且巴别鸟支持多个第三方登录平台集成。譬如：既可以企业微信扫码登录也可以OA账密登录、钉钉扫码登录。 SSO集成分为两个模块。第三方授权登录及第三方组织结构同步。其中第三方授权登录允许多个源进行授权登录。但第三方组织结构同步为了防止造成用户账户冲突，仅允许同步一个源。譬如：同步了OA系统的组织结构，但是支持OA和企业微信的SSO登录（OA和企业微信的的组织结构需要用一致的userID） 更多关于巴别鸟第三方登录的信息，可以查阅用户身份验证和授权（SSO）章节 数据摆渡 巴别鸟数据摆渡支持部署在密区的巴别鸟与部署在非密区的巴别鸟以安全并且带审批的方式互传数据。以实现在企业监管下的密区和非密区的数据交换。 关于巴别鸟数据摆渡的详细信息，可以查阅 巴别鸟数据摆渡 章节。 智巢AI 智巢AI是巴别鸟企业网盘的AI平台，包括智巢AI客服、智巢AI知识库和智巢AI文档助理三个主要模块。这些模块结合了大模型API和自定义训练，能够满足企业的智能客服、文件内容分析和问题回答需求。 智巢AI的三个主要模块 智巢AI客服：该模块充当企业的AI客服，巴别鸟企业网盘自己也用了该模块回答用户在巴别鸟网盘使用中遇到的问题。我们也向企业客户开放这个服务，企业可以将产品说明书、FAQ、客服文档等资料提供给智巢AI进行学习，并微调以满足企业客服需求。企业还可以将智巢AI的代码块嵌入其网站，快速建立对外智能客服系统。智巢AI客服能显著降低客服成本，节约时间和资源。 智巢AI文档助理：这一模块用于回答关于单个文档的问题。通过分析文档内容，智巢AI能够回答关于文档内容的各种问题，从总结到揭示关键发现。用户可以向AI提问，而不必亲自阅读冗长的文档，从而提高工作效率。 智巢AI知识库：这一模块允许企业为自己定制专属AI助手。智巢AI团队会根据企业的资料帮助准备训练集、调参，从而建立专属的AI模型，可以根据巴别鸟上不同权限的人提供权限范围内的答案。可以以问答的形式作为企业知识库助手。 技术解决方案 智能回答问题：智巢AI借助大模型和自定义训练，以保证准确性。它还利用小模型来辅助大模型的工作，减少瞎说话、不懂装懂或泄密等问题。此外，智巢AI遵循巴别鸟的权限管理机制，确保用户只能获取其权限范围内的答案。 自动学习：智巢AI可通过学习用户提供的文件来积累知识，为用户提供更准确的答案。所有参与训练的文档都是由用户指定并同意的，以确保数据隐私和合规性。 优势 客服成本降低：智巢AI客服可以显著减少企业的客服成本，无需大规模培训人员，AI可以随时提供答案。 快速问题回答：智巢AI能够即时回答用户的问题，提高了工作效率。 文件内容分析：智巢AI文档助理可以快速分析文档内容，帮助用户快速获取信息，而无需阅读整个文档。 自定义AI助手：企业可以根据自己的需求为智巢AI知识库定制专属AI助手，以满足特定的知识管理和问题回答需求。 权限管理：智巢AI能够根据用户权限提供不同范围内的答案，以确保数据安全和合规性。 自动化任务 面对日益增长的数字资产，传统的人工文件管理模式已难以满足高效流转的需求。巴别鸟推出的 “自动化任务”引擎，旨在将繁琐、重复的文件处理动作交由系统后台自动执行。通过建立“自组织、自规范”的智能流转体系，大幅降低人工干预成本，让团队将精力聚焦于核心业务创造。 自动化任务包含在标准版中，用户无需另行购买。 核心运作机制： 灵活的权限驱动： 依托平台极细颗粒度的权限管理体系，凡具备目标网盘或文件夹相应权限的用户，均可按需自主配置、开启或关闭特定的自动化任务。 多任务流串联 (Workflow)： 自动化任务并非孤立运行，支持多规则自由组合形成工作流。例如：文件上传后，系统可先触发“自动重命名”规范文件名称，随后立即触发“自动整理”将其归档至相关目录，实现多步骤一气呵成。 持续扩展的能力矩阵： 自动化引擎具备高度的扩展性。除了现有的基础功能外，平台将持续接入更多的自动化处理节点，以满足日益复杂的业务场景。 当前已支持的核心任务（包括但不限于）： 自动重命名： 按预设规则（如关键字替换、大小写转换）统一标准化命名。 自动整理与清理： 依据触发条件自动分类归档文件，或按策略定期清理空间。 自动转 PDF 与签章： 自动为源文件生成 PDF 副本，或在云端加盖企业签章。 批量创建文件夹： 通过导入数据模板（如 Excel）一键生成标准业务目录树。 多任务协同与执行流转权重 在复杂的业务场景中，一个文件夹往往会叠加配置多项自动化任务。为保障数据处理的逻辑严密性与安全性，系统底层预设了严格的自动化处理先后顺序 。 具体执行权重（数值越高越优先执行）规范如下： 自动清理文件夹（权重 10）： 系统最高优先级。如有符合条件的清理任务将率先执行，以避免对即将被废弃的无效数据投入后续算力 。 自动解压缩（权重 9）： 优先将打包资产释放，以便进入后续流转 。 自动更名（权重 8）： 在文件进入分类归档前，优先完成命名的标准化统一 。 自动格式转化类（权重 7）： 优先完成如转存 PDF、图片或音视频格式的转换任务 。 自动整理 / 排序（权重 6）： 作为流转的末端节点执行 。这意味着文件在被移动和分类前，均已完成了清洗、重命名与格式转换等核心前置标准化操作。 自动清理文件 (Auto Clean) 功能概述 在日常的跨部门协作或项目周期管理中，企业网盘内往往会不可避免地产生大量的临时数据、过程文件或短期流转素材。 “自动清理文件” 功能旨在为企业提供自动化的存储空间优化与目录瘦身方案。通过该功能，系统能够按照用户设定的特定规则，自动删除指定文件夹中的冗余文件，长效保持项目目录的整洁度并释放高价值的存储资源。 核心运作与配置规则 本模块通过严密的逻辑规则引擎执行文件的清理动作，确保数据处理的精准与高效： 目标目录锁定： 任务配置需明确指定应用该规则的目标文件夹。用户可选择将规则仅应用于新进入该文件夹的文件，或同时溯源应用于目录内已存在的历史文件。 多维规则触发： 支持基于特定规则对文件进行精准筛选与剔除。常见的判定规则可涵盖文件类型（如特定后缀的临时文件）、生命周期（如文件进入目录超过指定天数）等维度，实现高度定制化的清理策略。 工作流协同： 作为完整自动化流转的末端环节，自动清理可与其他任务无缝衔接。例如，在“自动转 PDF”任务完成后，系统可随即触发“自动清理”规则，将原始草稿文件进行统一清理，仅保留标准化定稿。 权限与数据安全控制 鉴于清理任务涉及文件删除这一敏感操作，该功能深度依托巴别鸟的极细颗粒度权限管理体系： 配置权限： 仅拥有该文件夹相应高级权限（如管理、删除权限）的协作成员，方可新建或修改自动清理任务，从源头杜绝越权操作造成的数据流失。 无感且安全的执行： 后台静默执行清理任务，减少对用户前端操作的干扰，同时严格遵循企业既定的数据合规与回收站保留策略，确保数据资产的绝对安全。 典型业务应用场景 设计与研发类项目： 在建筑设计或科研管理中，工作软件常会自动生成大量的备份或缓存文件（如 .bak 或临时渲染文件）。通过配置自动清理任务，可设定定期自动识别并删除特定后缀的无用文件，保持核心图纸与文献目录的纯净。 公共资料交换区： 针对企业内部设置的“临时中转站”或“临时分享区”，可配置按时间维度（如“保留 7 天后自动清理”）的自动清理任务，实现公共空间的自组织与自净化，降低运维管理成本。 自动重命名 (Auto Rename) 功能概述 在多方协作、多频次资料收集的业务场景中，由于操作人员习惯差异，文件命名往往缺乏统一规范，给后续的检索、归档与审计带来极大困扰。 “自动重命名” 功能允许系统对上传至指定文件夹的文件，按照高度定制化的预设规则进行自动化的名称重构 。该机制有效杜绝了因人为因素导致的命名混乱，确保企业数据资产入库即达标。 适用范围与权限控制 权限驱动： 该功能的启用严格依托于用户的操作权限。只要用户对目标文件夹（涵盖个人、部门、项目或素材库等各类文件夹）拥有“上传”及“重命名”权限，即可为其配置自动重命名任务 。 溯源处理： 规则不仅作用于新上传的文件，用户还可选择将其溯源应用于目标目录及其所有子文件夹中已存在的历史文件 。为保障系统性能与执行稳定性，批量溯源重命名的单次处理上限为 5000 个文件 。 核心规则引擎与配置维度 巴别鸟提供了一个高度灵活的可视化规则拼接引擎。用户可添加多个命名规则，并通过拖拽的方式对规则进行自由排序 。配置界面全程提供实时变化的“示例文件名”，帮助用户直观预览重命名规则的叠加结果 。 规则引擎支持以下多维度的命名元素： 标准属性变量： 支持提取并插入系统级变量，包括文件上传者、文件负责人、上级文件夹名称以及上传时间 。 多媒体元数据 (Metadata)： 针对图像等特定格式文件，系统可深度解析并提取其底层元数据作为命名依据，如拍摄日期、相机制造商/型号、镜头型号、尺寸以及 DPI/DPCM 等参数 。 自定义文本与连续编号： 用户可自由插入自定义文本内容 。在编号机制上，与传统的单次批量重命名不同，自动重命名具备状态记忆（延续性）。系统会自动读取目标列表中最后一个符合规则的编号，确保跨批次、跨时段上传的文件能够实现序号的无缝延续 。用户可精确设定编号的起始值、增量值及具体位数 。 原始名称的精细化修剪与防冲突机制 除了添加新前/后缀，系统同样支持对文件原有的名称进行深度结构化清洗： 名称修剪与替换： 可对原始文件名执行“替换特定内容”、“删除指定内容”操作 。此外，还提供一键“删除字符”功能，精准剔除文件名中的冗余空格、数字、引号、破折号及下划线 。 强制防冲突保护： 若用户在规则中选择完全删除“原始文件名”（即上传时不保留原名），为避免同名文件相互覆盖的风险，系统会强制要求并在规则链中自动追加一项“编号”规则 。 日期逻辑互斥： 在调用日期类变量时，用户可勾选“替换在文件名中检测到的日期” 。为防止逻辑冲突，在单一重命名任务中，该替换指令仅允许被某一时间变量（如“上传时间”或“拍摄时间”）勾选一次 。 全局格式化输出控制 在完成规则变量的拼接后，系统支持在输出端进行统一的格式化规范： 大小写标准化： 支持一键将拼装后的文件名转换为首字母大写、首字母小写、全部大写或全部小写，满足不同企业的视觉规范 。 字词分隔统一： 支持在各个命名规则模块之间统一插入标准化的分隔符（如空格、下划线或破折号），进一步提升文件名的机读与人读体验 。 自动转 PDF (Auto to PDF) 功能概述 在跨企业协作、外部资料分发以及项目定稿归档等业务环节中，PDF 格式因其跨设备显示的一致性与防篡改特性，成为了标准的文档交换媒介。巴别鸟的“自动转 PDF”功能，旨在建立一个自动化的文件格式标准化通道。配置该任务后，当文件被添加到选定的目标目录，系统将在后台静默触发转换引擎，将其自动转换为标准的 PDF 文件 。该能力大幅消除了人工逐一导出 PDF 的低效劳动，确保了数据对外输出与对内归档的规范性。 执行逻辑与边界条件 为保障平台底层计算资源的高效运转以及企业数据流转的安全可控，自动转换任务设定了以下执行逻辑与边界限制： 作用域与溯源处理： 该任务可向下覆盖，支持勾选应用于目标目录及其所有子文件夹中的文件 。此外，规则同样支持向历史数据溯源，可应用于目录内的现有文件，但为保障执行稳定性，单次溯源处理的文件数量被严格限制在 5000 个以内 。 系统性能保护机制： 为避免超大源文件在转换过程中长时间占用算力并导致任务队列阻塞，系统内置了文件体积阈值，即超过 30MB 的大体积文件将不会触发自动转换机制 。 存储空间自动释放： 针对“仅需保留定稿 PDF”的特定业务场景，用户可在任务配置界面勾选“转换成功后删除原文件”选项 。开启该策略后，系统将在确认 PDF 副本生成无误的前提下自动清理原始文件，从而大幅度优化网盘存储空间的利用率 。 广泛的格式兼容矩阵 巴别鸟自动转换引擎具备强大的多格式解析能力，支持将 32 种不同行业的主流业务文件自动化转储为 PDF 。用户可选择针对“所有支持的文件”执行转换，也可通过下拉菜单按类别精准勾选所需转换的扩展名 。具体支持的格式矩阵如下： 文档排版类： 全面兼容主流办公与出版软件产生的源文件，包括 doc、docx、ppt、pptx、wps、epub、dpt、indd、rtf、docm 以及 pptm 。 图片与影像类： 支持主流位图、数字底片及医疗影像格式的渲染转换，涵盖 jpg、bmp、jpeg、jpg2、png、psd、tif、tiff、raw、cr2、dcm 以及 heic 。 图形与工程图纸类： 深度适配设计与建筑工程领域的矢量及 CAD 图纸转换，支持的格式包含 ai、svg、eps、dwg、dwt 以及 dxf 。 自动整理文件 (Auto Organize) 功能概述 随着平台内协作数据的沉淀，如何保持底层“任意文件夹同步”架构与权限管控目录的整洁，成为了企业数字资产管理的关键。 “自动整理文件” 功能允许系统按预置的时间周期或内容特征，将文件自动分类并路由至相应的目标目录。该功能确保了海量文件在流转过程中的高度结构化，避免了人工归档的滞后性与错漏。 灵活的触发机制与作用域 用户可通过文件夹右键菜单中的“任务”选项 ，或左侧的自动化任务列表面板进入配置 。配置涵盖以下触发与作用规则： 事件驱动（默认）： 当文件被上传或者移动到指定的触发文件夹时，系统即刻响应并开始整理动作 。 周期驱动： 适用于集中式的数据归档场景，系统可按固定的周期（例如设定为每天 23:00）统一执行文件整理 。 历史溯源： 规则既可应用于新增文件及所有子文件夹，也可勾选“应用于现有文件”对历史存量数据进行批量溯源整理。为保障系统平稳，溯源处理单次不得超过 5000 个文件 。 核心智能整理规则引擎 系统提供三种高度自定义的分类规则，满足不同维度的数据归档需求： 1. 基于时间维度的结构化归档（按月 / 按年分类） 系统可按文件添加到网盘的对应年份或月份自动创建对应的子文件夹（例如“2025”、“2025 10”）并将相关文件移入 。 执行按年或按月分类时相同 ，系统具备按需建档的智能性，如果特定周期内（如某个月）没有产生文件，则系统不会冗余创建该月的空文件夹 。 2. 基于内容的智能路由（按关键字分类） 根据文件名中包含的特定关键字，系统将文件自动分发并移动至预设的目标文件夹 。 格式识别： 文件扩展名（如“jpg”）同样可作为关键字配置，实现特定类型素材的定向归集 。 多线并行路由： 用户可通过“添加关键字分类”按钮持续增加多条路由规则 。既支持将包含不同关键字的文件分别分发到不同的目录 ，也支持将多条关键字任务统一指向同一个目标文件夹 。 防重名与优先级控制： 关键字匹配严格按任务设定的先后顺序处理。例如，当文件名为“123ABC定稿.jpg”，若关键字列表第一项规则为“123”，第二项为“定稿”，则该文件将优先匹配“123”的规则并执行移动 。系统内置防重复检测，每个关键字仅允许输入一次，重复输入会触发“请重新输入”的错误拦截 。 同名冲突化解： 在执行文件移动与整理的过程中，如在目标文件夹内遇到重名文件，系统会自动在文件名后附加编号，以确保数据不被意外覆盖 。 创建签章 (E Sign) 业务场景与功能概述 在企业的合同审批、图纸会签及业务合规流转等关键环节中，具备防篡改属性的数字化签署是打通线上协作闭环的核心节点。传统的跨系统签署往往伴随繁琐的文件下载与格式转换。巴别鸟推出的 “创建签章” 功能，允许用户直接在云端网盘的工作流中对文件进行盖章与签署 。该引擎支持多种主流文件类型直接加载印签，并支持将签署完毕的文件一键导出为标准的 PDF 格式，从源头保障数字资产的安全、合规与不可篡改性 。 签章资产库与个性化配置 系统为用户提供了一个高度集成的数字印签管理控制台，确保电子签章资产的统一沉淀与快速调用： 多元签名采集： 在“签名设置”模块中，用户既可以调用终端进行在线“添加手写签名”，也支持直接“上传签名图片文件”（如含透明通道的 PNG 素材），以满足不同层级的签署合规要求 。 企业图章管理： 在“图章设置”模块，企业用户可按需上传业务专用的电子公章或合规图章图片 。 默认优先级状态： 针对拥有多个印签资产的用户，系统支持一键将其中的特定签名或图章“设置为当前使用”（默认印签） 。在后续的文档预览与流转界面中，系统将优先调用该默认印签，极大提升高频审批场景下的签署效率 。 智能自适应交互与沉浸式引导体系 为兼顾不同硬件终端的显示极限并降低用户的学习门槛，签章配置中心采用了多断点的智能响应式（Responsive）界面架构，并深度嵌入了多语言操作指引： 宽屏工作站模式（窗口宽度 ≥ 1120px）： 当用户在桌面级宽屏设备上操作时，系统不仅在左侧保留标准的签章配置面板，还会在右侧自动展开独立的视频教学区。该区域会自动加载并无感循环播放签章使用教程（播放完毕停顿 3 秒后重播），为用户提供“边学边配”的沉浸式体验 。 紧凑聚焦模式（窗口宽度 ＜ 1100px）： 当处于较窄的屏幕或移动端窗口时，系统会智能折叠右侧的视频播放区，以最大化保障核心签署设置区的视觉焦点 。同时，系统在界面底部提供“如何使用签章？”入口，用户点击后可唤起全屏教程播放 。 国际化双语支持： 考虑到跨国企业的协作需求，系统内置了本地化的教学视频库。除中文语言环境播放专属中文教程外，其他所有多语言版本均默认匹配并播放标准英文教程，保障全球业务团队的无障碍落地 。 批量创建文件夹 (Batch Create Folders) 功能概述与业务价值 在多项目并发或企业部门架构调整的业务场景中，由人工逐一建立复杂的标准目录树不仅耗费大量操作时间，且极易因人为疏漏导致目录层级错乱或命名不规范。巴别鸟提供的 “批量创建文件夹” 功能，允许用户通过外部结构化数据（如 Excel、CSV、TXT 文本）直接驱动云端目录的生成 。该功能可将标准化的业务目录模板瞬间转化为可落地的网盘文件夹阵列，极大提升了大型项目启动阶段的初始化建档效率。 标准目录阵列的大规模生成 该模块具备强大的数据解析能力与人工容错干预机制： 高并发支持： 系统支持通过导入 xls、xlsx、csv 或 txt 格式的文件，按换行符规则快速读取目录清单，单次批处理任务的上限高达 5000 行，满足绝大多数企业级数据结构的生成需求 。 可视化预审与动态干预： 在正式执行批量创建前，系统会完成数据解析并在界面中直观渲染出即将生成的文件夹列表与层级关系 。在此预览环节中，用户可直接通过鼠标右键或悬浮菜单，对特定的预设目录执行“创建子文件夹”、“重命名”或“删除”等即时修改动作 。这一“先审后建”的机制，确保了最终落地的目录树与业务需求绝对对齐。 项目级文件夹与权限的“一键部署” 当目标路径设定为部门文件夹或个人文件夹的根目录时，系统支持创建更为高阶的 “项目文件夹” 。该模式深度结合了巴别鸟的底层权限管理体系，实现了目录构建与成员权限配置的同步落地： 专属标准模板： 批量生成项目文件夹需下载并使用系统专属模板导入数据 。若上传的非标文件不符合解析格式，系统将严格拦截并提示重新上传 。 项目角色与权限预设： 模板不仅规范了“项目文件夹名字”，还支持直接关联账号系统预设“项目负责人”与“项目成员” 。 负责人指派： 填写的负责人 ID（支持手机号、邮箱或特定的工号格式）必须为已注册的企业成员；若该字段留空或填写的身份无法校验，系统将遵循安全保底原则，默认将当前创建任务的操作者设为项目负责人 。 成员自动化邀请与赋权： 用户可在模板中通过逗号分隔批量录入多位项目成员 。项目目录生成后，系统将自动向这些成员发送邀请通知，并为其赋予基础的“上传及下载”默认权限 ，彻底免除了建档后繁琐的逐一授权操作。 实时状态监控与智能容错机制 在执行大规模创建任务时，系统后台会以队列形式稳健处理，并在前端提供全方位的进程监控与异常修复闭环： 全局进度追踪： 创建过程中，列表节点会实时更新其执行状态（从代表正在执行的转圈动画，平滑过渡至代表成功的确认勾选状态） 。任务全局状态亦会从“创建中”明确流转至“完成” 。 精准异常归因与重试： 全部任务执行完毕后，系统顶部会输出清晰的结果汇总（如“共创建了 XXX 个文件夹，失败 X 个”） 。用户可一键查阅“创建失败文件列表” 。系统会将失败原因精确归类为“包含文件名不允许字符”或“已有同名文件夹”等系统级冲突 。针对这些异常条目，用户不仅可以查明原因，还能直接在界面上点击绿色的“重试”按钮触发二次创建 ，大幅降低了批量运维的阻力。 文控项目 文控项目是巴别鸟的一个行业应用独立模块（需要另行购买）。巴别鸟文控项目解决了工程设计行业中的文控标准的流程管理（DCC）及自动化问题。提高了大量文控人员的工作效率的同时也降低了人为失误的可能。 使用范围 需要严格管理每一次文件发送的行业或企业。每次发送给客户的文件都由特定人员发送（文控人员）每次发送都有发送单据可查，能明确的管理发送内容。通过发送单号可以查询到每次发送文件给接收方的具体信息和文件。同时对接收方是否收件，对发送过去的内容是否驳回都可管理查询。并且发送单可以作为凭据。 需要解决的问题 目前很多企业的文控流程基本是靠手动，文件存储于EDMS系统或文控人员电脑本地。依靠文件夹分类来管理文档，每次发送文件手动建立一个文件夹，按文件名规范命名文件夹，文件通过邮件发送后把发送的文件放入文件夹并附上本次发送的TRANSMITTAL（文件发送单）。 每次发送都会产生一个文件夹及相应的TRANSMITTAL。这些工作人工操作相当繁琐，除了整理文件，每次还需要手动填写文件发送单，手动按规则编写发送单编号，日后还要手动核对，效率极低。 巴别鸟解决方案 可新建新的文控项目类型。这意味着不同的项目可以设定不同的TRANSMITTAL（发送单）规则生成不同的发送单和发送单号。不同项目也可以管理不同的收件人（收件企业） 可设定每个项目的文件接收方，统一管理文件接收方。 文控项目中的文档支持发送功能，发送功能支持多选。选择文件或文件夹发送后，收件人可以通过邮箱收到所发送文件的下载link和TRANSMITTAL（发送单）。并且通过下载link下载到的文件是发送时的版本。 每次发送的文件都是文件当前版本，文件升版会形成新的版本号，并在发送单显示。 文件发送后根据预先设定的规则自动生成本次发送的TRANSMITTAL（发送单）和TRANSMITTAL NO.（发送单号） 可以管理及查询所由TRANSMITTAL（发送单），并可导出发送单为PDF。 巴别鸟文控项目使用指引： 基本介绍 巴别鸟文控管理系统是在巴别鸟企业私有云版的基础上增加文控管理模块，以实现文控工作的自动化。 文控管理的方式是以建立“文控项目”的方式来实现。文控项目是针对文控需求特别定制的特殊项目，以项目为单位进行管理。 建立文控项目 登录系统后，在要创建文控项目的部门中点击“新建”——“新建项目” 项目只能建立于根目录（企业文件）或部门根目录下 例：在HQSM文控这个部门下建立一个文控项目 点击新建项目，出现项目类型选择界面 选择“创建文控管理项目” 这时候出现项目初始化选择界面 按照项目的要求填写初始化信息 每项的介绍如下： 项目负责人 管理、转交项目、修改项目权限及基础信息。不可为空。可删除TRANSMITTAL 项目秘书 不可转交项目，其他同项目负责人，可多人，可为空。可删除TRANSMITTAL 文控人员 可以发送文件给接收人。其他权限可配置，可多人，可为空。选择人员后点击右侧权限选择下拉框可以批量修改成员权限（如图）。 其他成员 没有发送文件选项，其他同普通项目普通成员，权限可配置，可为空。 版本号规则 如图，如果前缀填写为HQSM，文件的第一个版本就为 HQSM A ，第二个版本为 HQSM B以此类推 基本信息 基本信息的填写内容将显示于TRANSMITTA头部。 如图：画红圈处就是填写的基本信息。 接收方信息 接收方信息决定了发件时的可选项和所发文件的TRANSMITTA号 收件方名字是指收件方在系统中的称呼，一般填写收件方的企业简称，如 MCC 邮箱支持添加多个，添加多个后，一次发送就可以向多个邮箱地址发送文件及TRANSMITTA ATTN可以任意输入，同时也会显示在TRANSMITTA上 运单号规则其实就是TRANSMITTA号的自动生成规则，不同的收件方可以生成不同的运单号。所以需要在每个收件方处设定不同的运单号规则。 规则自定义界面示意如下： 3栏分别为TRANSMITTAL号的3个组成部分，如果所需的TRANSMITTA号需要更多的编码来组成也可以点击+号来增加更多栏 例： 第一栏选择输入文字，弹出文字输入框，输入 “HQSM ” 第二栏选择编码规则为1 2 3数字顺序 第三栏选择 文字输入、输入“ 2020” 点加号新增一栏，选择a b c字母顺序 第一次发送生成的TRANSMITTAL号即为： HQSM 1 2020a 第二次发送生成的TRANSMITTAL号为：HQSM 2 2020b 选择字母作为编号超过26个后，z号的下一个版本自动变为a1 如果该项目有多个接收方，也可以点击来增加。（项目建立后也可以在项目管理界面中去增删接收方。 这些填写完成后，点击“新增项目”就完成了项目的新建 你可以在创建项目路径的文件列表中看到新建的文控项目，点击即可进入 文控管理项目不同于普通项目，项目首页顶部栏增加了文控管理的按钮 其中“发送单列表”可以查询该项目发出的所有TRANSMITTA，管理项目可以对项目进行管理。 上传文件 点击新建的文控项目，进入项目页面。 直接拖拽想要上传的文件到项目中即可上传文件，当然，你也可以和使用普通文件夹一样使用同步功能进行上传下载。 发送文件 选中要发送的文件（支持多选），然后点击右键，选择“发送文件”会出现文件发送界面 每次最多发送的文件为2000个（包含文件夹）。如项目需要全部文件发送，建议以压缩包形式进行发送。 收件人可以下拉选择项目初始化时填写的收件人及ATTN 抄送可以填写其他任意邮箱地址，也可以留空不填写 选择的提交文件类型也会在生成的TRANSMITTA中显示 文件列表罗列了本次要发送的文件。 系统要发送TRANSMITTAL的文件名构成为 文件编号+描述，如一个文件文件名为 1000+图纸.pdf，发送时显示在TRANSMITTAL的文件编号为“1000”，描述为“图纸”。如果发送的文件的文件名中没有+分割，文件编号就显示文件名，如果发送的文件名为“+图纸.jpg“就不显示文件编号，显示描述为“图纸”。描述可中途更改。 附言将会在收件人接受到的邮件中显示并不会显示在TRANSMITTAL中 填写完成后点击“发送文件”系统会自动生成TRANSMITTAL并作为link附在邮件中发送给客户。 生成TRANSMITTAL 发送成功后系统会弹出提示 点击查看，就能查看本次发送自动生成的TRANSMITTAL 点击导出为PDF就可以把该TRANSMITTAL保存为PDF文件 你也可以在传送单列表（TRANSMITTAL list）中去查看该项目中发送的所有TRANSMITTAL 收件人在邮箱中收到的TRANSMITTAL和该TRANSMITTAL一致。 查看TRANSMITTAL 在项目首页点击发送单列表（TRANSMITTAL list） 打开列表就可以看到及查询本项目的所有发送单。 点击传送单号可查看详情并下载TRANSMITTAL的PDF文件 为接受就是接受方并没有打开已发送的邮件，如对方打开邮件并访问了TRANSMITTAL，接收状态会变为已接收。 查看发送记录 在任意文件上右键点击，可查看该文件的发送记录及其对应的TRANSMITTAL" }, { "lang": "en", "slug": "reference-whitepaper-06-user-interface", "title": "White Paper: User Interface", "description": "\"BabelBird Enterprise Drive White Paper\" Chapter: User Interface.", "category": "Source References", "top_category": "维护", "keywords": [ "white paper", "user interface" ], "url": "en/reference-whitepaper-06-user-interface.html", "source": "content/en/reference-whitepaper-06-user-interface.md", "summary": "白皮书：用户界面 用户界面设计 巴别鸟界面设计理念 企业网盘集成的功能比较多，如何合理分配功能入口，让用户实际使用时更加方便？是一个界面设计和交互时需要重点考虑的问题，目前有两种互有冲突的设计理念。 界面设计理念 优缺点 隐藏非常用功能，保证界面简洁，降低学习难度，易上手，初次使用体验友好。（代表：微云、腾讯文档等2C产品） 前缓后陡的学习曲线，用户初次试用时体验好，但实际长期使用时不方便 功能入口显性化，界面复杂，但需要的功能可以快速找到。界面较重，学习成本稍高，初次使用体验不友好。（代表：office、CAD等专业软件） 前陡后缓的学习曲线，用户初次使用体验复杂，但实际长期使用方便。不利于营销。 考虑到企业网盘是一个面向企业长期使用的专业产品，前期陡峭的学习曲线虽然不利于营销（用户简单试用时弃用率增高）但是对应选择巴别鸟的用户长期使用是友好的，熟悉后能更好用更有条理，而作为一个生产力工具，日常使用的便捷度和降低出错概率更加重要。所以巴别鸟企业网盘选择了第二种设计理念： 作为一个专业面向企业场景的产品，为用户长期日常使用时的便捷性，可以适当增加上手复杂度。 界面设计原则 用户友好性: 在保证功能使用优先的前提下，强调用户友好性，确保用户能够轻松使用企业网盘。 一致性: 维持一致的界面设计，以提供一致的用户体验。 简洁性: 采用简洁的设计，减少冗余和复杂性，使用户能够迅速理解界面。 可用性: 确保功能模块容易被用户找到并有相应指引，3步内直接可以使用。 用户界面元素 网页版（web） 采用左菜单、右文件列表、顶部功能分区的布局。方便用户注意力集中在文件列表上。 左侧菜单可以收起", "headings": [ { "level": 1, "title": "白皮书：用户界面", "id": "section" } ], "images": [], "text": "白皮书：用户界面 用户界面设计 巴别鸟界面设计理念 企业网盘集成的功能比较多，如何合理分配功能入口，让用户实际使用时更加方便？是一个界面设计和交互时需要重点考虑的问题，目前有两种互有冲突的设计理念。 界面设计理念 优缺点 隐藏非常用功能，保证界面简洁，降低学习难度，易上手，初次使用体验友好。（代表：微云、腾讯文档等2C产品） 前缓后陡的学习曲线，用户初次试用时体验好，但实际长期使用时不方便 功能入口显性化，界面复杂，但需要的功能可以快速找到。界面较重，学习成本稍高，初次使用体验不友好。（代表：office、CAD等专业软件） 前陡后缓的学习曲线，用户初次使用体验复杂，但实际长期使用方便。不利于营销。 考虑到企业网盘是一个面向企业长期使用的专业产品，前期陡峭的学习曲线虽然不利于营销（用户简单试用时弃用率增高）但是对应选择巴别鸟的用户长期使用是友好的，熟悉后能更好用更有条理，而作为一个生产力工具，日常使用的便捷度和降低出错概率更加重要。所以巴别鸟企业网盘选择了第二种设计理念： 作为一个专业面向企业场景的产品，为用户长期日常使用时的便捷性，可以适当增加上手复杂度。 界面设计原则 用户友好性: 在保证功能使用优先的前提下，强调用户友好性，确保用户能够轻松使用企业网盘。 一致性: 维持一致的界面设计，以提供一致的用户体验。 简洁性: 采用简洁的设计，减少冗余和复杂性，使用户能够迅速理解界面。 可用性: 确保功能模块容易被用户找到并有相应指引，3步内直接可以使用。 用户界面元素 网页版（web） 采用左菜单、右文件列表、顶部功能分区的布局。方便用户注意力集中在文件列表上。 左侧菜单可以收起，显示更多文件列表内容，提供沉浸式体验。 为了更好的树状管理文件，也可以打开树状视图类似windows资源管理器一样管理文件。 如果文件夹图片文件数量多，可自动打开瀑布流预览模式，便于用户查看。 左侧菜单（快捷方式）用户可以自定义，便于用户日常按使用习惯自定义快捷入口。 文件/文件夹的所有功能操作集中在右键，容易找到，常用功能显示在文件列表上，同时文件列表栏也有相应按钮，防止因鼠标右键失效影响用户操作。 客户端（windows、mac、麒麟） 客户端使用Electron及C++进行跨平台开发，很好的保证了风格一致性和操作一致性。并且针对各平台也有各自的优化。客户端还包括同步模块、上传下载列表及虚拟映射盘（云桥）模块。 主操作界面延续网页版风格和布局，但针对本地软件的使用习惯及客户端独有模块进行了布局上的改进，把顶部功能分区集中在左侧栏，让顶部显示更简洁。 左侧栏增加了传输和同步两个客户端独有功能按钮及入口。 文件传输模块，管理同步进程和上传下载任务。 在windows和MacOS系统文件右键菜单上集成了同步和上传、发送文件的快捷方式，便于用户快速建立同步和上传文件（夹）。 在windows和MacOS上集成了虚拟映射盘，让用户可以像访问本地硬盘一样访问云端文件。 响应式设计 响应式设计原则 多设备兼容性: 巴别鸟企业网盘的用户界面被设计为在各种设备上获得最佳体验，包括桌面、移动设备和平板电脑，以保证用户随时随地用各种设备都能有良好的体验。 图：巴别鸟从诞生起就是跨平台的 自适应布局 用户界面元素会自动根据屏幕尺寸和方向进行调整，以确保内容的可见性和可用性。 触摸友好性: 优化移动设备上的触摸交互，包括手势控制、滑动和缩放。 图像和媒体优化: 使用了预载入、图像转码生成缩略图和媒体压缩技术，以减少页面加载时间和带宽使用。 移动端支持 网页版本移动设备优化 移动界面设计: 巴别鸟网页版本有针对移动设备打开设计的H5页面，及宣传网站移动版及分享链接移动版下载界面，支持常见触摸手势，如滑动、缩放和点击。 图：移动设备访问巴别鸟H5页面 移动APP: 为了获得更好的使用体验，巴别鸟开发了移动端专用的APP，支持安卓和iOS系统。 为保证良好的性能，巴别鸟APP都以原生应用的方式进行开发。 APP的交互、界面、功能模块都全部重新设计，以适合在移动设备上访问。 图：移动端界面 平板电脑优化 巴别鸟iOS APP针对iPad重新设计制作了界面，以更适应在大屏幕上工作。" }, { "lang": "en", "slug": "reference-whitepaper-07-performance", "title": "White Paper: Performance Optimization", "description": "Chapter of \"BabelBird Enterprise Drive White Paper\": Performance Optimization.", "category": "Source References", "top_category": "维护", "keywords": [ "white paper", "Performance optimization" ], "url": "en/reference-whitepaper-07-performance.html", "source": "content/en/reference-whitepaper-07-performance.md", "summary": "白皮书：性能优化 负载均衡策略 鉴权认证与服务分离 分离鉴权认证: 为了提高系统的性能和安全性，巴别鸟企业网盘采用了鉴权认证与核心服务分离的策略。这意味着用户的鉴权认证请求会被路由到专门的认证服务器上，而上传、下载以及查询浏览等核心服务请求会被路由到相应的核心服务服务器上。 请求路由: 我们使用负载均衡器来根据请求类型将请求路由到不同的服务器。这确保了鉴权认证服务器不会成为核心服务的性能瓶颈，并允许我们根据需求独立扩展认证和核心服务。 相同类型请求的多台服务器部署 多服务器支持: 巴别鸟企业网盘允许相同类型的请求在多台服务器上部署，以提高性能和可用性。这种多服务器支持策略确保了即使一台服务器出现故障，其他服务器仍然可以处理请求。 请求平均分配: 我们使用负载均衡算法将相同类型的请求均匀分配到多台服务器上，以避免服务器过载和提供更快的响应时间。 负载均衡器 负载均衡器配置: 我们使用专业的负载均衡器来实现请求的分发和路由。负载均衡器根据预定的规则将请求发送到适当的服务器。 监控和自动故障转移: 负载均衡器配备了监控功能，能够检测服务器的健康状态。如果某台服务器出现故障，负载均衡器会自动将请求路由到其他可用的服务器，以确保系统的连续性。 优势 性能提升: 负载均衡策略提高了系统的性能，允许请求在多台服务器上并行处理，减少了单一服务器的负载。 高可用性: 多台服务器的部署和自动故障转移确保了系统的高可用性，即使出现故障，仍然可以提供服务。 扩展性: 负载均衡策略允许根据需求添加更多的服务器，以满足不断增长的用户和请求。 缓存管理 文件缓冲区管理 文件缓冲区设置: 为了优化性能并减轻C", "headings": [ { "level": 1, "title": "白皮书：性能优化", "id": "section" }, { "level": 3, "title": "优势", "id": "section-2" }, { "level": 3, "title": "优势", "id": "section-3" }, { "level": 3, "title": "优势", "id": "section-4" }, { "level": 3, "title": "优势", "id": "section-5" } ], "images": [], "text": "白皮书：性能优化 负载均衡策略 鉴权认证与服务分离 分离鉴权认证: 为了提高系统的性能和安全性，巴别鸟企业网盘采用了鉴权认证与核心服务分离的策略。这意味着用户的鉴权认证请求会被路由到专门的认证服务器上，而上传、下载以及查询浏览等核心服务请求会被路由到相应的核心服务服务器上。 请求路由: 我们使用负载均衡器来根据请求类型将请求路由到不同的服务器。这确保了鉴权认证服务器不会成为核心服务的性能瓶颈，并允许我们根据需求独立扩展认证和核心服务。 相同类型请求的多台服务器部署 多服务器支持: 巴别鸟企业网盘允许相同类型的请求在多台服务器上部署，以提高性能和可用性。这种多服务器支持策略确保了即使一台服务器出现故障，其他服务器仍然可以处理请求。 请求平均分配: 我们使用负载均衡算法将相同类型的请求均匀分配到多台服务器上，以避免服务器过载和提供更快的响应时间。 负载均衡器 负载均衡器配置: 我们使用专业的负载均衡器来实现请求的分发和路由。负载均衡器根据预定的规则将请求发送到适当的服务器。 监控和自动故障转移: 负载均衡器配备了监控功能，能够检测服务器的健康状态。如果某台服务器出现故障，负载均衡器会自动将请求路由到其他可用的服务器，以确保系统的连续性。 优势 性能提升: 负载均衡策略提高了系统的性能，允许请求在多台服务器上并行处理，减少了单一服务器的负载。 高可用性: 多台服务器的部署和自动故障转移确保了系统的高可用性，即使出现故障，仍然可以提供服务。 扩展性: 负载均衡策略允许根据需求添加更多的服务器，以满足不断增长的用户和请求。 缓存管理 文件缓冲区管理 文件缓冲区设置: 为了优化性能并减轻CPU资源负担，巴别鸟企业网盘实施了文件缓冲区管理。解密后的文件将暂时存储在缓冲区中，以减少重复解密操作。 LRU策略: 我们采用最近最少使用（LRU）策略来管理文件缓冲区。这意味着最不常使用的文件缓存将被淘汰，从而保持缓冲区的高效利用。 文件鉴权缓冲管理 文件鉴权缓冲: 鉴权检测对于文件访问的权限是复杂而耗时的。针对文件所在部门、项目、分享以及保密级别等多个因素，需要进行综合性的鉴权检测。为了提高性能，我们实施了文件鉴权缓冲，将鉴权结果缓存起来。 过期淘汰机制: 文件鉴权缓冲采用过期淘汰机制。每个缓存条目都有一个预定的过期时间，一旦超过该时间，缓存将被自动淘汰。这确保了缓存数据的新鲜性，并降低了内存使用。 优势 性能优化: 缓存管理减少了解密操作和鉴权检测的重复执行，从而提高了系统的响应速度和性能。 资源节约: 通过使用LRU策略和过期淘汰机制，我们有效地管理了内存资源，避免了内存泄漏和过度占用的问题。 复杂鉴权的快速响应: 文件鉴权缓冲确保了复杂的鉴权检测结果的快速响应，减少了对鉴权服务的压力。 数据压缩和传输优化 文件分块技术 文件分块存储: 为了优化文件的传输和存储，巴别鸟企业网盘采用了文件分块技术。大文件会被分成小块，并分别存储在服务器上。这有助于提高文件的传输效率和断点续传的支持。 并行块请求: 文件分块存储允许前端在文件下载时并行发起多个块的请求。一旦所有块都被下载，前端将它们组装成完整的文件，从而显著提高了下载速度。 基于哈希码的文件存储去重技术 文件去重: 巴别鸟企业网盘采用基于哈希码的文件存储去重技术。当用户上传文件时，系统会计算文件的哈希码并与已有文件的哈希码进行比较。如果发现相同的哈希码，系统将只保留一份文件的副本，从而节省存储空间。 节省存储空间: 文件去重技术有效减少了存储冗余，特别是在企业中频繁共享和传输的文件，从而降低了存储成本。 优势 传输效率: 文件分块技术和并行块请求加速了文件的传输速度，特别是对于大文件和高带宽连接。 存储节省: 基于哈希码的文件存储去重技术降低了存储需求，降低了维护成本。 用户体验: 快速的文件传输和节省存储空间改善了用户体验，提供更高效的文件管理和共享。 异步任务处理 后台异步处理 任务耗时处理: 为了处理那些前台发出的可能比较耗时，甚至可能导致HTTP请求超时的任务，巴别鸟企业网盘采用了后台异步处理的策略。这些任务不会阻塞主要的HTTP请求响应，而是在后台异步执行。 提高响应速度: 后台异步处理确保了前台请求的响应速度不受到耗时任务的影响，提高了用户体验。 配置化管理异步任务 任务队列: 为了防止服务器资源紧张，我们对异步任务进行了配置化管理。可以将异步任务配置为一个或多个处理队列，这些队列可以独立执行任务。任务队列可以根据任务的类型和优先级进行配置和管理。 消息队列: 另一种管理异步任务的方式是使用消息队列。巴别鸟企业网盘可以配置为使用消息队列来存储和调度异步任务。这种机制可以确保任务的有序执行和可控制性。 消息处理机制: 异步任务通过消息处理机制进行控制和执行。任务被加入队列或消息队列后，由专门的处理器进行处理和执行。 优势 响应性: 后台异步处理提高了系统的响应速度，避免了长时间的等待。 资源控制: 配置化管理异步任务允许对服务器资源进行有效的控制，防止资源耗尽。 可扩展性: 消息队列和消息处理机制提供了系统的可扩展性，可以轻松添加新的异步任务类型。" }, { "lang": "en", "slug": "reference-whitepaper-08-scalability", "title": "White Paper: Scalability", "description": "Chapter of \"BabelBird Enterprise Drive White Paper\": Scalability.", "category": "Source References", "top_category": "维护", "keywords": [ "white paper", "Scalability" ], "url": "en/reference-whitepaper-08-scalability.html", "source": "content/en/reference-whitepaper-08-scalability.md", "summary": "白皮书：可扩展性 水平扩展 集群部署: 巴别鸟企业网盘业务服务器采用集群部署模型，这允许我们轻松扩展系统的容量和性能。集群中的多台服务器协同工作，以分担负载并提供高可用性。这种模型允许我们根据需求添加新节点，以满足不断增长的用户和数据需求。私有云部署客户在用户增长时也可以通过增加虚拟机或物理服务器的方式来扩充性能以满足高并发需求。关于巴别鸟集群部署可扩展性的更多信息，可以查看 分布式部署 章节。 对象存储系统: 巴别鸟的存储系统采用对象存储技术，这种技术非常适合大规模的数据存储和水平扩展。对象存储系统具有高度的可伸缩性，可以容纳大量的数据，并在需要时增加存储节点自动扩展存储容量。关于巴别鸟对象存储扩展性的更多信息，可以查看 自建对象存储 章节。 负载均衡: 我们实施了负载均衡策略，确保用户请求被均匀分配到集群中的各个节点，以避免单点故障和提供更快的响应时间。 自动伸缩（公有云）: 得益于阿里云ECS弹性计算服务，我们的系统配置了自动伸缩机制，根据负载情况自动增加或减少服务器节点。这种自动伸缩保证了系统的稳定性和性能。 垂直扩展 硬件升级: 除了水平扩展，针对私有云用户我们还可以进行垂直扩展，即升级服务器硬件以增加单个服务器的性能和容量。这在需要更多计算能力或内存的情况下是一种有效的解决方案。 数据库优化: 我们还可以优化数据库系统，通过调整配置、使用更高性能的硬件或升级数据库管理系统来提高性能。这些改进可以提供更好的查询性能和数据处理能力。 缓存: 我们使用缓存技术来加速数据访问，减轻数据库和存储系统的负载。缓存支持内存缓存、CDN缓存等多种方式，根据需要选择最适合的缓存策略。", "headings": [ { "level": 1, "title": "白皮书：可扩展性", "id": "section" } ], "images": [], "text": "白皮书：可扩展性 水平扩展 集群部署: 巴别鸟企业网盘业务服务器采用集群部署模型，这允许我们轻松扩展系统的容量和性能。集群中的多台服务器协同工作，以分担负载并提供高可用性。这种模型允许我们根据需求添加新节点，以满足不断增长的用户和数据需求。私有云部署客户在用户增长时也可以通过增加虚拟机或物理服务器的方式来扩充性能以满足高并发需求。关于巴别鸟集群部署可扩展性的更多信息，可以查看 分布式部署 章节。 对象存储系统: 巴别鸟的存储系统采用对象存储技术，这种技术非常适合大规模的数据存储和水平扩展。对象存储系统具有高度的可伸缩性，可以容纳大量的数据，并在需要时增加存储节点自动扩展存储容量。关于巴别鸟对象存储扩展性的更多信息，可以查看 自建对象存储 章节。 负载均衡: 我们实施了负载均衡策略，确保用户请求被均匀分配到集群中的各个节点，以避免单点故障和提供更快的响应时间。 自动伸缩（公有云）: 得益于阿里云ECS弹性计算服务，我们的系统配置了自动伸缩机制，根据负载情况自动增加或减少服务器节点。这种自动伸缩保证了系统的稳定性和性能。 垂直扩展 硬件升级: 除了水平扩展，针对私有云用户我们还可以进行垂直扩展，即升级服务器硬件以增加单个服务器的性能和容量。这在需要更多计算能力或内存的情况下是一种有效的解决方案。 数据库优化: 我们还可以优化数据库系统，通过调整配置、使用更高性能的硬件或升级数据库管理系统来提高性能。这些改进可以提供更好的查询性能和数据处理能力。 缓存: 我们使用缓存技术来加速数据访问，减轻数据库和存储系统的负载。缓存支持内存缓存、CDN缓存等多种方式，根据需要选择最适合的缓存策略。 容器化和SOA服务架构 Docker容器化 Docker部署: 我们采用Docker容器化技术来部署巴别鸟企业网盘的各个组件和模块。这种方式允许我们将每个主要模块打包为独立的Docker容器，提供了更高的灵活性和可扩展性。 容器编排: 我们使用容器编排工具来管理和协调各个容器，确保它们能够协同工作，实现高可用性和弹性。 容器镜像管理: 巴别鸟企业网盘使用容器镜像仓库来存储和管理Docker镜像，以便随时部署新的容器实例。 SOA服务架构 服务拆分: 我们将巴别鸟企业网盘的主要功能模块拆分为独立的服务，每个服务负责执行特定的任务或功能。这种拆分提高了系统的可维护性和可扩展性。 API通信: 服务之间通过API进行通信，使用兼容RESTful API协议。这种松耦合的通信方式使得服务可以独立开发、测试和部署。 独立部署: 每个服务可以独立部署和扩展，这意味着我们可以根据需求对特定服务进行水平扩展，而不影响其他服务的运行。 容器化和SOA服务架构的优势 高可用性: 容器化和SOA服务架构提供高可用性，允许我们在出现故障时快速恢复服务。 灵活性: 容器化允许我们轻松部署、升级和维护每个容器，而SOA服务架构提供了灵活的模块化开发和部署选项。 资源利用率: 我们可以根据需要分配资源，避免资源浪费，实现更高的资源利用率。 快速交付: 容器化和SOA服务架构使得新功能和改进可以更快地交付给用户。私有云用户也可以享有媲美公有云系统的快速更新及升级服务。 容器化和SOA服务架构的挑战 复杂性: 管理多个容器和服务可能会引入一定的复杂性，需要适当的管理工具和策略。 监控和日志: 我们使用监控和日志工具来确保容器和服务的正常运行，并及时识别和解决问题，并配备自动重启机制，如果服务有问题则自动重启有问题的模块以保证整体服务的畅通。" }, { "lang": "en", "slug": "reference-whitepaper-09-private-deployment", "title": "White Paper: Privatized Deployment", "description": "Chapter of \"BabelBird Enterprise Drive White Paper\": Privatization Deployment.", "category": "Source References", "top_category": "维护", "keywords": [ "white paper", "Private deployment" ], "url": "en/reference-whitepaper-09-private-deployment.html", "source": "content/en/reference-whitepaper-09-private-deployment.md", "summary": "白皮书：私有化部署 巴别鸟公有云网盘系统需要同时为包含免费用户在内的60万用户提供持续不间断服务、要挡住公网上的各种攻击、要不断提高系统效率以降低高昂的公有云服务器成本。多达10年的公有云不间断服务经验使巴别鸟系统久经考验。巴别鸟私有云系统是在巴别鸟公有云系统基础上发展起来的，继承了公有云巴别鸟的所有功能及特性，并与公有云巴别鸟保持同步更新，提供给您其他私有网盘无法比拟的高稳定性及高可用性。 部署方案 针对不同企业不同的IT系统建设需求，巴别鸟私有化系统支持多种灵活的部署方式及部署要求。无论是单服务器、多服务器、集群、超融合系统、分布式系统、第三方云平台甚至Docker方式的部署我们都支持。我们的部署团队可以根据你的需求和你共同制定部署方案。同时因为私有云只服务于单一企业的特性，我们可提供远超公有云系统的可选自定义设置，从界面操作到流程到权限都可以根据你的需求调整。 服务器建议配置及性能需求 服务器类型及作用： 巴别鸟网盘所需硬件系统由业务服务器及存储服务器两部份构成，其中业务服务器可以分为4种类型，这4种类型的服务可以根据需求部署在一台物理机或虚拟机中，也可以分散部署在四台甚至更多的服务器中。所以，部署巴别鸟系统最小单位是两台物理服务器或两台虚拟机（一台业务一台存储） 服务名 用途 操作系统 主业务服务器 web服务、负载均衡、主业务功能实现 Linux 数据库服务器 数据库服务 Linux 搜索服务器 提供文件全文搜索、高级搜索功能 Linux 转码服务器 为需要转码预览的文件进行转码及增加水印 windows 2012、Linux 存储服务器 提供文件存储 Linux 极", "headings": [ { "level": 1, "title": "白皮书：私有化部署", "id": "section" } ], "images": [], "text": "白皮书：私有化部署 巴别鸟公有云网盘系统需要同时为包含免费用户在内的60万用户提供持续不间断服务、要挡住公网上的各种攻击、要不断提高系统效率以降低高昂的公有云服务器成本。多达10年的公有云不间断服务经验使巴别鸟系统久经考验。巴别鸟私有云系统是在巴别鸟公有云系统基础上发展起来的，继承了公有云巴别鸟的所有功能及特性，并与公有云巴别鸟保持同步更新，提供给您其他私有网盘无法比拟的高稳定性及高可用性。 部署方案 针对不同企业不同的IT系统建设需求，巴别鸟私有化系统支持多种灵活的部署方式及部署要求。无论是单服务器、多服务器、集群、超融合系统、分布式系统、第三方云平台甚至Docker方式的部署我们都支持。我们的部署团队可以根据你的需求和你共同制定部署方案。同时因为私有云只服务于单一企业的特性，我们可提供远超公有云系统的可选自定义设置，从界面操作到流程到权限都可以根据你的需求调整。 服务器建议配置及性能需求 服务器类型及作用： 巴别鸟网盘所需硬件系统由业务服务器及存储服务器两部份构成，其中业务服务器可以分为4种类型，这4种类型的服务可以根据需求部署在一台物理机或虚拟机中，也可以分散部署在四台甚至更多的服务器中。所以，部署巴别鸟系统最小单位是两台物理服务器或两台虚拟机（一台业务一台存储） 服务名 用途 操作系统 主业务服务器 web服务、负载均衡、主业务功能实现 Linux 数据库服务器 数据库服务 Linux 搜索服务器 提供文件全文搜索、高级搜索功能 Linux 转码服务器 为需要转码预览的文件进行转码及增加水印 windows 2012、Linux 存储服务器 提供文件存储 Linux 极端情况下，如果使用服务器挂载的硬盘作为存储空间，巴别鸟也支持把全部服务及存储都部署在一台物理机或虚拟机中（一体机模式），但考虑到性能及灾备或是日后的升级扩容问题，不推荐这样的部署方式。 我们推荐的最佳部署方式是4台服务器（虚拟机）的小集群部署。主业务服务及数据库服务放在在一台服务器，搜索服务器和转码服务器独立，然后外加一台存储服务器。 如果存储的空间需求小于10TB，也可以不需要存储服务器。可以直接挂载硬盘或NFS磁盘进行存储。 巴别鸟也支持接入第三方存储，理论上，只要第三方存储系统支持NFS或S3协议都可以接入到巴别鸟作为存储服务。绝大多数存储系统都支持这两种协议。 各个服务器之间要保证互访的畅通。如内网有较高安全要求可以参阅 9.1.2需要开放的端口 最低性能配置： 巴别鸟的最低性能配置可以支持100左右用户正常使用，管理10TB以下的数据。 cpu 内存 系统盘 存储盘 网络 操作系统 8核CPU （参考基准E5 2609） 32G ECC 内存 500G 10TB以下 千兆 Linux 推荐性能配置实例： 巴别鸟的推荐性能配置可以支持1000 2000用户正常使用，管理最高可达1PB的文档。 巴别鸟支持多种部署方式，该实例是标准部署方式。使用虚拟机部署业务服务器对接独立的单台或多台对象存储服务器。业务服务器和存储服务器分开管理。 业务服务器： 建议业务服务器使用虚拟机进行部署 编号 服务器类型 配置要求 操作系统 服务器用途 1 虚拟机 8核CPU 64G内存 500G SSD系统盘 CentOS8或openeuler22 主业务服务器/数据库 2 虚拟机 8核CPU 32G内存 500G SSD系统盘 CentOS8或openeuler22 搜索服务器 3 虚拟机 8核CPU 16G内存 200G SSD系统盘 windows 2012 R2 转码服务器 8核cpu的性能应该接近志强4410 巴别鸟企业网盘采用Docker部署，理论上只要是Linux操作系统即可进行部署，推荐使用CentOS或open Euler。 如果没有现成的虚拟机资源，需要采购新的业务服务器，业务服务器硬件配置需求如下： 编号 服务器类型 配置要求 操作系统 服务器用途 1 业务服务器 至强银牌4210 2 20核CPU 64G内存 2TB SSD硬盘 Linux 主业务服务器 业务服务器最好购买VM，使用虚拟化进行管理。 存储服务器（对象存储）： 巴别鸟支持在通用服务器上搭建对象存储系统，如预计存储空间用量小于100TB，推荐使用单台服务器搭建对象存储系统。单台对象存储可以用磁盘进行数据校验冗余，并且可以以每次增加一台存储服务器的方式进行横向扩容。（扩容操作可以做到不停服） 对象存储服务器建议使用独立的物理机，建议配置如下： 服务器类型 配置要求 操作系统 服务器用途 备注 存储服务器 至强银牌4210 2 20核CPU 64G内存 480G SSD硬盘 +存储所需容量硬盘 硬盘如果考虑性价比，建议使用 8T 10（2U） 或 8T 24（4U）。如果考虑存储密度及未来扩容投入可使用12T硬盘。 Linux 对象存储服务器 未来扩展建议增加相同磁盘容量的服务器。 如所需存储空间大于300TB，需要多台服务器搭建分布式对象那个存储系统。 巴别鸟也支持为客户搭建分布式对象存储系统。要了解分布式对象存储可查阅“自建对象存储”章节。 需要开放的端口 为了服务器系统的安全，我们需要只开放特定的端口，下面是需要开放的端口： 对外开放的端口（外网访问需要使用的端口）： 端口号 端口用途 协议 开放的主机 80 网盘主业务 web外部访问端口，不加密 http 主业务服务器 443 网盘主业务 web外部访问端口，加密 https 主业务服务器 3060 网盘主业务node 外部访问端口，不加密 TCP 主业务服务器 3080 网盘主业务node 外部访问端口，加密 TCP 主业务服务器 服务器间需要开放的端口（服务器内部通讯需要开放的端口）： 一般实际部署时，只会限制外网端口（对外），服务器间内部端口不会限制。但一些跨网络跨机房部署的用户也会需要限定内部端口。 主机 端口号 端口用途 协议 目标网段 业务服务器 6379 redis访问端口，供windows转码与搜索服务器使用 TCP 转码服务器与搜索服务器 业务服务器 8080 供windows转码服务器，访问网盘业务服务器使用 TCP 转码服务器与搜索服务器 业务服务器 3306 数据库端口，供搜索服务器访问数据库使用 TCP 转码服务器与搜索服务器 业务服务器 9000 docker 集群部署，内部可视化界面端口 TCP 转码服务器与搜索服务器 业务服务器 111 portmap 端口 TCP+UDP 转码服务器与搜索服务器 业务服务器 2049 TCP+UDP TCP+UDP 转码服务器与搜索服务器 业务服务器 35000 mountd 端口 TCP+UDP 转码服务器与搜索服务器 业务服务器 2376 docker REST API端口，进行TLS加密 TCP 本机 业务服务器 2377 TCP端口 用来 docker 集群管理相关通信 TCP+UDP 本机 业务服务器 7946 TCP与UDP端口，用来docker swarm 各节点间的通信 TCP+UDP 本机 业务服务器 4789 docker overlay 网络默认端口 TCP+UDP 本机 搜索服务器 9200 elastic 端口，供主业务服务器调用使用 TCP 业务服务器 搜索服务器 5601 kibana端口，内部可视化elastic界面访问端口 TCP 业务服务器 搜索服务器 9998 tika端口，提取文档文本服务器端口 TCP 业务服务器 搜索服务器 9000 docker 集群部署，内部可视化界面端口 TCP 转码服务器与搜索服务器 搜索服务器 2376 docker REST API端口，进行TLS加密 TCP 本机 搜索服务器 2377 TCP端口 用来 docker 集群管理相关通信 TCP 本机 搜索服务器 7946 TCP与UDP端口，用来docker swarm 各节点间的通信 TCP+UDP 本机 搜索服务器 4789 docker overlay 网络默认端口 TCP+UDP 本机 转码服务器 转码服务器 可以访问业务服务器 可以访问业务服务器 可以访问业务服务器 部署时需要开放的端口： 端口号 端口用途 开放的服务器 目标IP地址 22 ssh端口号，ssh 访问使用 所有服务器 部署用跳板机 443 获取授权 所有服务器 47.96.234.200 443 获取安装源 所有服务器 120.27.245.68 443 Docker安装源 所有服务器 13.35.121.100 POC部署 POC部署适用于用户在选型前在生产环境进行POC测试而进行的部署方式。 POC部署需求： 基础POC部署，可测试软件功能，并发量，API接口，安全性，并进行生产环境试用。建议使用标准部署作为POC测试。 如需要进行对象存储、不同密区数据摆渡、高可用的POC，择需要增加相应的服务器和网段。 环境准备 推荐使用虚拟机进行部署： 巴别鸟私有化企业网盘采用Docker部署，理论上只要是Linux操作系统即可进行部署。推荐使用CentOS或open Euler。按要求准备好虚拟机后，联系我们预约时间后即可开始POC部署。 编号 服务器类型 配置要求 操作系统 服务器用途 备注 1 虚拟机 8核CPU 32G内存 500G系统盘 +500G存储盘 CentOS8或openeuler22及以上 主业务服务器 2 虚拟机 8核CPU 16G内存 500G系统盘 CentOS8或openeuler22及以上 搜索服务器 3 虚拟机 8核CPU 8G内存 200G系统盘 windows 2012 R2 转码服务器 CAD、office转码 win服务器是为了更好的office文件预览效果。巴别鸟也支持纯Linux环境部署 POC部署其他要求如下： 编号 项目 要求 备注 1 远程接入 可以远程接入服务器进行部署 可使用堡垒机或者跳板机或向日葵、VPN，能远程接入服务器部署即可。 2 外网连接 服务器需要能连接外网，拉取安装包，获取授权 需要连接的外网地址： software.babel.cc docker.babel.cc POC部署的使用授权时长为30天，授权账户数为100个。 初始化 部署完成后，巴别鸟团队会帮助用户进行系统初始化，根据用户需求初始化系统。包括不限于： 初始化管理员账号。（需要准备一个邮箱地址作为超级管理员账号） 初始化通知发件邮箱。（需要用户准备一个可提供密码和smtp服务器地址的邮箱作为系统默认发件箱） 初始化部门结构。（对接AD或导入部门） 初始化基础配置。logo、企业名、各类配置项。 培训 巴别鸟是一个专业的企业级应用，需要一定的培训工作帮助客户落地。POC后建议联系我方销售人员进行使用培训。 培训分为3类： 管理员培训（培训管理员的配置，使用，需求功能实现。耗时 1 2小时） 部门经理培训。（培训部门经理权限分配、成员增减等日常管理方式。耗时 1小时） 使用者培训。（使用成员的培训。耗时 1小时） 开启POC试用 培训完成后即可开始正式POC试用，使用中遇到的问题可以在相关群直接询问，巴别鸟团队会在2个小时内响应并解答。POC系统有效期为30天，如果需要延期，可联系我们销售人员。 巴别鸟常用部署方式介绍 巴别鸟可以按需支持多种部署方式，这里介绍下巴别鸟常用的部署方式。 在阿里云、腾讯云、华为云等公有平台部署： 巴别鸟支持在公有云服务商如：阿里云、腾讯云、百度云、华为云、天翼云的虚拟机（ECS）及对象存储（OSS、OBS...）上进行部署，在互联网上为用户提供服务。 和纯私有化部署的差别对比如下表： 优缺点/ 部署方式 图片服务 视频服务 公网访问 稳定性 硬件费用 采用阿里云存储和阿里云服务器 可以使用阿里云提供的图片服务 可以采用阿里云的视频转码服务，但是需要额外付费(价格贵) 可以在公网上访问，用户访问的快慢取决于用户自己的带宽和购买的阿里云的带宽。 系统很稳定，部署简单，便于管理。 需要支付阿里云的存储和服务器费用，可按月或按年付费等。服务器的维护即可由用户自己负责，也可以委托我们进行维护并负责升级。 存储和服务器均搭建在自己的内网 使用自建的图片处理服务(需要客户提供高性能的服务器) 使用自建的转码服务(需要客户提供高性能的服务器)，如果用户没有这方面的需求，可以忽略。 如果没有外网的出口，则用户不能在外网访问。但是在内网访问很快。 稳定，针对存储系统等的模块做了定制开发。数据的安全性由用户自己负责。 需要提供独立的主机和存储系统。服务器即可由用户选配购买，也可以由我们选配购买。服务器维护由用户负责，我们可以提供相应的软件升级服务。 公有云部署（1000+用户）要求： 编号 服务器类型 配置要求 操作系统 服务器用途 1 ECS 16核CPU 32G内存 500G SSD系统盘 CentOS8或openeuler22 主业务服务器 2 ECS 8核CPU 16G内存 500G SSD系统盘 CentOS8或openeuler22 数据库服务器 3 ECS 8核CPU 16G内存 500G SSD系统盘 CentOS8或openeuler22 搜索服务器 4 存储 对象存储系统。如阿里云OSS、华为云OBS 对象存储系统。如阿里云OSS、华为云OBS 对象存储系统。如阿里云OSS、华为云OBS 在公有云平台部署的主要优势是不需要专人维护、无需购买硬件就能做到顶级的灾备、在互联网上访问速度快、同时服务器和数据在自己手上管理。 在公有云平台部署的缺点主要为：数据没有本地化、每年需要支付服务器租用费用及相应的带宽存储成本。 自购服务器（2台物理机）进行部署： 如果想在自己机房部署纯私有的巴别鸟，并且没有富余的虚拟机资源，需要采购硬件部署，要求如下： 物理机服务器品牌建议：建议使用2台 DELL T440 服务器来完成系统搭建。并购买DELL3年金牌服务。 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：建议使用2台 DELL T440 服务器来完成系统搭建。并购买DELL3年金牌服务。 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：建议使用2台 DELL T440 服务器来完成系统搭建。并购买DELL3年金牌服务。 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：建议使用2台 DELL T440 服务器来完成系统搭建。并购买DELL3年金牌服务。 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：建议使用2台 DELL T440 服务器来完成系统搭建。并购买DELL3年金牌服务。 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：建议使用2台 DELL T440 服务器来完成系统搭建。并购买DELL3年金牌服务。 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 两台服务器方案 业务+存储 两台服务器方案 业务+存储 两台服务器方案 业务+存储 两台服务器方案 业务+存储 两台服务器方案 业务+存储 两台服务器方案 业务+存储 编号 服务器类型 配置要求 操作系统 服务器用途 备注 1 服务器 志强银牌4410 2 16核CPU、 64G内存、 2TB SSD硬盘 open Euler、Ubuntu、CentOS 主业务服务器 建议安装VM 2 存储 4410 2 16核CPU 、64G内存、 500G SSD硬盘+所需的硬盘空间（不需要raid或raid0） open Euler、Ubuntu、CentOS 存储服务器 硬盘容量按对存储空间需求进行配置 以上配置可支持1000+用户，150TB左右的存储空间 巴别鸟存储服务器使用对象存储系统，支持分布式部署（多台存储服务器）最低要求为一台物理服务器。支持使用硬盘组进行校验，支持2+1、3+1、4+1...等多种校验类型。详见 自建对象存储 章节 如需扩容存储空间，增加单台存储服务器即可。 也可增加一台存储服务器作为备份服务器，实时同步备份，主存储服务器出问题切换到备份服务器即可正常使用。 单服务器（1台物理机）部署： 一些没有机房但需要私有化部署巴别鸟，并且存储空间需求不大（10TB以下）的客户，可以选用单台服务器部署巴别鸟。只需购买一台符合要求的塔式服务器放置在公司也能满足使用巴别鸟的需求。 物理机服务器品牌建议：如果没有机房，建议使用塔式服务器进行部署。服务器存储硬盘建议raid1或者raid5+1 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：如果没有机房，建议使用塔式服务器进行部署。服务器存储硬盘建议raid1或者raid5+1 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：如果没有机房，建议使用塔式服务器进行部署。服务器存储硬盘建议raid1或者raid5+1 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：如果没有机房，建议使用塔式服务器进行部署。服务器存储硬盘建议raid1或者raid5+1 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：如果没有机房，建议使用塔式服务器进行部署。服务器存储硬盘建议raid1或者raid5+1 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：如果没有机房，建议使用塔式服务器进行部署。服务器存储硬盘建议raid1或者raid5+1 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 一台服务器（一体机方案） 一台服务器（一体机方案） 一台服务器（一体机方案） 一台服务器（一体机方案） 一台服务器（一体机方案） 一台服务器（一体机方案） 编号 服务器类型 配置要求 操作系统 服务器用途 备注 1 服务器 志强银牌4410 2 16核CPU 64G内存 2TB SSD硬盘 +需要存储容量的硬盘 2（未来也可增加硬盘） openEuler、Ubuntu、CentOS 8.5 及以上 一体机 建议安装VM，2个CPU授权。 单服务器部署整套巴别鸟系统不支持对象存储，采用只读硬盘或NFS的方式进行存储。建议使用raid1来提升系统可靠性。 可增加一台备份服务器用来进行数据同步备份。如主服务器出问题可以用备份服务器进行数据重建。 在现有虚拟机（超融合）系统上进行部署： 这是目前最常用的部署方式，在企业现有的服务器和硬件条件下进行部署，无需采购新的设备。 在客户现有的VM或超融合平台分配的虚拟机中完成部署，适合已经有一定IT建设及管理的用户。 采用小集群的方式部署，由虚拟机平台负责服务器的统一管理。 支持绝大多数虚拟化系统。 推荐采用4台虚拟机挂载存储空间的方式进行部署。 编号 服务器类型 配置要求 操作系统 服务器用途 1 虚拟机 8核CPU 32G内存 500G SSD系统盘 CentOS8或openeuler22 主业务服务器 2 虚拟机 8核CPU 16G内存 500G SSD系统盘 CentOS8或openeuler22 数据库服务器 3 虚拟机 8核CPU 16G内存 500G SSD系统盘 CentOS8或openeuler22 搜索服务器 4 虚拟机 8核CPU 16G内存 200G SSD系统盘 windows 2012 R2 转码服务器 5 存储 支持NFS或S3接口的存储系统或虚拟机挂载磁盘作为存储盘 支持NFS或S3接口的存储系统或虚拟机挂载磁盘作为存储盘 支持NFS或S3接口的存储系统或虚拟机挂载磁盘作为存储盘 如有系统冗余需求，可以准备6台虚拟机，就能很好的完成数据库备份及系统冗余。 编号 服务器类型 配置要求 操作系统 服务器用途 1 虚拟机 8核CPU 32G内存 500G SSD系统盘 CentOS8或openeuler22 主业务服务器 2 虚拟机 8核CPU 32G内存 500G SSD系统盘 CentOS8或openeuler22 从业务服务器 3 虚拟机 8核CPU 16G内存 500G SSD系统盘 CentOS8或openeuler22 主数据库服务器 4 虚拟机 8核CPU 16G内存 500G SSD系统盘 CentOS8或openeuler22 从数据库服务器 5 虚拟机 8核CPU 16G内存 500G SSD系统盘 CentOS8或openeuler22 数据库服务器 6 虚拟机 8核CPU 16G内存 200G SSD系统盘 windows 2012 R2 转码服务器 7 存储 分布式对象存储 分布式对象存储 分布式对象存储 支持虚拟机挂载磁盘的形式把挂载盘作为存储空间。 也可以对接san存储或者对象存储系统等第三方存储系统。 巴别鸟也为客户提供自建对象存储服务。 自建对象存储服务器配合虚拟机部署： 巴别鸟支持为客户在通用服务器上搭建对象存储，因为对象存储软件定义存储的优势（高可用、横向扩展容易），推荐没有对象存储的用户可以新购一台服务器部署巴别鸟对象存储系统配合在虚拟机（超融合）运行的巴别鸟业务系统一起使用。 业务服务器需求同上一节“在现有虚拟机（超融合）系统上进行部署”的要求。 关于巴别鸟对象存储的详细介绍可查看“自建对象存储服务器”章节。 我们大多数客户最终都选择对象存储服务器作为存储。 最低支持单服务器搭建对象存储系统（150TB以下空间需求）。 服务器类型 配置要求 操作系统 服务器用途 备注 存储服务器 至强银牌4210 2 20核CPU 64G内存 480G SSD硬盘 +存储所需容量硬盘 硬盘如果考虑性价比，建议使用 8T 10（2U） 或 8T 24（4U）。如果考虑存储密度及未来扩容投入可使用12T硬盘。 Linux 对象存储服务器 未来扩展建议增加相同磁盘容量的服务器。 单服务器对象存储网络拓扑图： 我们也支持搭建多台服务器组成的分布式对象存储系统。 分布式存储系统最小需求为2+1，就是需要准备三台存储服务器，性能要求和单台对象存储的要求一致。 物理分布式存储目前推荐最小单位是3台存储服务器。2+1纠错码意味着每扩充2台存储节点就需要增加1台服务器作为纠错服务器。以此，4+1意味着增加4台存储服务器就需要增加一台纠错服务器。所以4+1的磁盘利用率高于2+1。使用4+1方案首次建设就需要5台存储服务器。每次扩容增加的最小单位和首次建设需要的最小服务器单位一致。 多服务器分布对象存储网络拓扑图： 可以新增一台或一套存储服务器用来实时备份。主存储服务器出问题快速切换到备份服务器即可正常使用。 分布式高可用高冗余部署： 金融机构、医院、能源、超大型企业因为有业务不中断的硬性指标，需要系统能做到高可用、高冗余，不会因为服务器的单点故障而中断服务，并且能做到热切换及热修复，极端情况下，连交换机等网络设备都需要实现主备分离，这就需要使用分布式高可用高冗余部署。 巴别鸟支持多种高可用高冗余方案，可以部署在传统的分布式系统中实现高可用高冗余。 我们也可以为客户搭建适合巴别鸟的分布式系统。（硬件需要客户按要求自行采购） 巴别鸟分布式部署能确保任何一个单点故障都不会影响系统的正常使用。 推荐的分布式容易部署方案，业务服务器采用主备双活，存储系统采用分布式存储。 有密区及非密区管控需求的，详见 “数据摆渡章节” 巴别鸟高可用系统网络拓扑 异地灾备部署 对于对数据保全有着较高要求的用户，巴别鸟也支持异地灾备方案。就是把重要的数据库及文件存储内容备份到异地的备份系统中。如果本地机房出现问题，只要备份数据在，可以在任何地方重建系统并恢复正常使用。 巴别鸟可以为客户搭建异地灾备服务器，但不支持冷热数据分离等高级备份方式，如果数据量极大（1PB以上）考虑到性价比，建议使用专业的备份系统（如：NBU、云祺）。 巴别鸟有支持NBU标准的备份API可以调用。 异地灾备部署对网络环境要求较高，不同位置的机房间最好有专线或稳定的VPN连接。 使用备份系统只能在出问题后通过备份还原及重建数据，不支持直接切换到备份数据。一般情况下数据重建周期会比较久。 使用备份系统进行异地灾备示意图： 如果不需要冷热数据分类保存，巴别鸟也可以采用对象存储自带的异地灾备功能为客户完成异地灾备部署。 使用对象存储进行异地灾备，当主系统出问题可以快速切换到灾备服务器中。 自建对象存储服务器 巴别鸟对象存储是在开源MinIO系统上发展起来的对象存储系统。它继承了MinIO高性能、可扩展、数据安全的优势，同时更适配巴别鸟企业网盘的应用场景。 巴别鸟对象存储系统作为先进的对象存储系统，在速度、安全性、稳定性、高可用、横向扩展方面都有着传统存储系统无可比拟的优势。 巴别鸟对象存储系统优势 性能 MinIO号称是世界上速度最快的对象存储服务器，没有之一。在 32 个 NVMe 驱动器节点和 100Gbe 网络上发布的 GET/PUT 结果超过 325 GiB/秒和 165 GiB/秒，和亚马逊S3相比有明显优势，远远超越传统HDFS。 高可用性：MinIO通过数据的多副本、故障转移和自动恢复，保证高度可靠性和可用性，从而确保数据不丢失和业务不中断。 低冗余且磁盘损坏高容忍：标准且最高的数据冗余系数为2(即存储一个1 M的数据对象，实际占用磁盘空间为2M)。但在任意n/2块disk损坏的情况下依然可以读出数据(n为一个纠删码集合(Erasure Coding Set)中的disk数量)。并且这种损坏恢复是基于单个对象的,而不是基于整个存储卷的。 安全性： MinIO 通过最高级别的加密以及广泛的优化提供更多功能，几乎消除了通常与存储加密操作相关的开销。 数据分块存储与各个硬盘，获取硬盘或服务器读写权限也无法还原数据。 极高的可扩展性：MinIO支持分布式部署，并且可以水平扩展。在需要更多的存储空间或更高的性能时，可以通过添加新的节点轻松地扩展MinIO。 最低支持单机部署对象存储系统，而不是传统的需要三台独立服务器。 对象存储系统及纠删码 关于纠删码 巴别鸟对象存储系统(MinIO)使用纠删码erasure code 和校验和checksum来保护数据免受硬件故障和无声数据损坏。最高冗余状态下即便丢失一半数量(N/2)的硬盘,您仍然可以恢复数据。 纠删码是一种恢复丢失和损坏数据的数学算法，MinIO采用Reed Solomon code将对象拆分成N/2数据和N/2奇偶校验块。这就意味着如果是12块盘，一个对象会被分成6个数据块、6个奇偶校验块，可以丢失任意6块盘(不管其是存放的数据块还是奇偶校验块) , 仍可以从剩下的盘中的数据进行恢复，我们称数据存储为D、纠删码（奇偶校验）为P。 默认情况下会以N/2个数据和N/2奇偶校验块的方式来进行驱动器分片（支持自定义以支持更高的空间利用率） 纠删码不同于传统的多副本技术，它的磁盘利用率更高，数据恢复效率更高。（但是不少存储厂商把纠删码宣传为多副本，把P数说成是副本数，这是不准确的，会引起很多误解） 巴别鸟语境下的多副本是指增加备份服务器全量同步存储的数据。 纠删码特点及与raid技术区别 纠删码可以保护数据免受多个驱动器故障的影响 RAID6允许两个驱动器故障而MinIO纠删码允许丢失一半的驱动器 RAID属于卷级别的纠删码而MinIO纠删码是基于对象实现的纠删码（不用停机） 有效空间计算（空间利用率） 假设需要100TB的存储空间，需要购买多少个多大的硬盘取决于选择的冗余标准。譬如：采用3+1的冗余方式，100TB可用空间就需要购买12块12TB的硬盘，4块硬盘一组组成3组，9个数据盘3个校验盘，可用空间就是9 12一共108TB可用。如果采用2+1的冗余方式，就需要15块10TB的硬盘，10个数据盘，5个校验盘。 3+1方案中12块硬盘只能坏任意3块不影响系统使用及数据还原，但如果使用2+1方案，虽然需要购买更多硬盘，但15块硬盘里能坏任意5块也不影响系统使用。 更换坏掉的硬盘后系统能自动修复数据。 空间利用率可以参考下表。如果空间需求量大（超过150TB）并且在持续增长，考虑到存储密度和性价比，建议一台服务器一次性配16块硬盘。 不同数量的磁盘及空间利用率可以点击下方链接进行计算 https://min.io/product/erasure code calculator?ref=docs 硬件准备 所需硬件配置。 巴别鸟支持单台服务器搭建对象存储系统（单节点），以硬盘组作为冗余对象。最高可以损坏一半的硬盘也不影响系统的正常使用。 巴别鸟对象存储系统需要客户按要求事先准备好硬件服务器以供部署，最低配置需要2块志强CPU、64GB内存及400G固态硬盘（系统盘）然后增加相应存储容量所需的机械硬盘。 如要计算所需存储空间和购买的硬盘数，可点击下方链接进行计算。 https://min.io/product/erasure code calculator?ref=docs 建议硬件配置如下： 服务器类型 配置要求 操作系统 服务器用途 备注 存储服务器 至强银牌4210 2 20核CPU 64G内存 480G SSD硬盘 +存储所需容量硬盘 硬盘如果考虑性价比，建议使用 8T 12（2U） 或 8T 24（4U）。如果考虑存储密度及未来扩容投入可使用12T硬盘。 Linux 对象存储服务器 未来扩展建议增加相同磁盘容量的服务器。 巴别鸟对象存储使用软件定义存储技术，所以硬盘无需raid，考虑到一些服务器需要raid才能支持多磁盘，这种情况下每块硬盘都做成raid0直通模式即可。 单服务器模式每次扩容需要增加一台配置一致的服务器。扩容时可以不间断服务。 单服务器部署也支持增加一台配置一致的服务器搭建主备模式实时同步，如果一台服务器硬件损坏，可以快速切换到备用服务器。 磁盘有效空间容量和选择的冗余方式有关。譬如：使用8块10T硬盘来组建对象存储系统，采用3+1的冗余方案，相当于4块硬盘一个分组，分为2组，有效可用空间为60TB，同时8块硬盘损坏任意两块也不影响数据及系统使用，替换坏的硬盘即可自动重建。如果采用7+1的冗余方案，有效可用空间就为70TB，8块硬盘里任意损坏1块不影响数据及系统使用。 多服务器部署（分布式）。 巴别鸟对象存储系统支持多服务器部署，如使用服务器为冗余单位，最少要求3台服务器，即2+1模式，但考虑到空间利用率，推荐采用3+1方案（即4台服务器） 每个节点（服务器）的配置要求和上文单服务器部署一致。 建议节点配置一致（相同的操作系统、相同数量的磁盘和相同的网络连接） 每个节点提供的驱动器数量必须相同 节点间的时间差异不能大于15分钟（建议使用NTP确保时间的一致性） 空间利用率计算同单服务器。 私有化要求及服务流程 为了确保使用巴别鸟系统的体验和质量，巴别鸟所有的私有化部署工作都是由巴别鸟团队远程或现场进行部署及签发证书，暂不支持代理团队部署或客户自行部署。同时系统的维护工作也由巴别鸟运维团队进行定期远程维护。客户只需按要求准备好硬件及接入资源，其他事情就交给巴别鸟团队来完成。 私有化部署前期需要准备的： 计算大体使用人数、并发量、存储空间及空间增长率交由巴别鸟客户经理评估所需配置。 客户评估现有服务器剩余资源（如有），根据实际情况选择部署方式。 巴别鸟出具私有化部署方案。 客户根据方案准备相应的服务器及接入资源，分配服务器、安装操作系统。 保证服务器能够在外网远程桌面（也可以使用向日葵）和ssh访问，开启相应端口（我们的部署技术人员会提出具体端口要求） 用户最好能提供一个域名，没有域名的话需要一个固定的ip地址，用ip地址访问的方案需要保证在使用时期ip地址不会发生变动 如需接入邮箱找回密码或手机号发送验证码，需要准备相应的邮箱接入或短信网关。 编号 项目 要求 备注 1 域名 需要一个独立的主域名或二级域名 可以在公司原有域名的基础上设定一个二级域名。如yun.company.com 2 邮箱 需要一个可发送通知邮件的邮箱 支持smtp的邮箱地址即可 邮件推送相关 MailUser=xxxx@mail.com MailPassword=password MailHost=邮件服务器地址 MailPort=端口号 3 远程访问 可远程访问服务器进行配置 支持远程访问及控制服务器 4 SSl证书 https需要申请SSL证书 像数字证书颁发机构CA申请。推荐申请 OV 通配符 5 短信接口 如需要手机邀请，手机注册。则需开通短信接口服务（可选） 阿里云、腾讯云等云服务商也提供短信服务接口，申请即可开通 实施阶段 准备工作完成后通知我们，我们会给用户一个具体的实施时间安排，实施时间段内请保持外网访问的畅通 实施一般需要2 3个工作日，第一天远程部署安装巴别鸟，第二天测试和验收，第三天修正遇到的问题 实施完成后我们会通知用户，然后开始初始化阶段 初始化服务 巴别鸟为所有私有云客户提供了初始化服务，服务内容包括： 维护人员培训（远程或是现场） 帮助用户进行数据迁移、用户导入、权限分配等工作（远程或是现场） 使用人员培训 （远程或是现场） 接入第三方服务 作为一个围绕企业文件的办公平台，私有化的巴别鸟企业网盘通过接入第三方API的方式，可以轻松集成各种第三方服务到巴别鸟中，以满足不同的需求这些服务包括但不限于：电子签名、高级CAD预览、office、文字识别、图像识别....等第三方服务来解决您遇到的需求问题。 接入第三方服务的条件 理论上支持BS架构的第三方应用或者服务模块都可以接入。 第三方服务必须提供开放的API，以便巴别鸟企业网盘可以与之集成 如果是互联网服务，需要服务器能访问外网。 需要企业自行或委托我们购买接入的第三方服务的授权 推荐的可接入服务 文件防泄密系统： ipguard 在线office编辑：onlyoffice（自带）、office365、WPS Online、永中office 高级CAD预览：浩辰云图、梦想CAD CAD在线编辑：梦想CAD 在线签章：上上签 文字识别图像识别：百度千帆（智能云） AI相关：智巢AI（自有）、ChatGPT、智谱AI 开放API（统一存储平台） 巴别鸟私有化版本提供了开放API，使用巴别鸟API，您可以在您的系统中使用巴别鸟的几乎所有能力。并在云中构建自定义应用程序和集成，而无需构建和维护自己的内容管理服务。 统一存储平台 非结构化数据统一管理: 巴别鸟企业网盘的开放API的核心价值在于它可以作为一个统一的存储平台，用于整合和管理企业各个平台的非结构化数据。这包括但不限于OA（办公自动化）、CRM（客户关系管理）、ERP（企业资源规划）等应用，这样企业的所有非结构化数据都能在一个平台统一管理，提高安全性并节约存储资源。 企业级对象存储: 巴别鸟企业网盘还可以开放自带的对象存储接口，作为企业的统一存储管理平台。这意味着企业可以将不同来源的数据，包括文档、媒体、报表等，存储在巴别鸟企业网盘，并通过API访问和管理这些数据。 文档和支持 详细文档: 巴别鸟企业网盘提供详细的API文档，包括示例代码和用例，以帮助开发人员快速集成API。 附件2: 巴别鸟API文档 https://www.babel.cc/p/api integration.do 开发支持: 我们提供开发支持服务，技术人员会参与联调，一对一解决在API集成过程中可能遇到的问题和挑战。 单点登录SSO 巴别鸟私有化系统支持对接SSO单点登录平台或企业微信、钉钉、飞书、OA、ADFS、ERP等第三方平台以是实现单点登录。 更多关于单点登录的内容可以参见上文安全性章节的 ：单点登录（Single Sign On，SSO）集成 数据摆渡 巴别鸟可以使用“部门安全策略”的方式隔离某个部门数据，实现涉密部门的安全性和外发审批等功能，但是面对网络隔离的密区和非密区之间的文件传输，就需要用到数据摆渡的方式，确保密区和非密区之间可以安全可控的交换文件，这里就需要部署巴别鸟数据摆渡功能。在巴别鸟中，该功能模块命名为“传送文件“便于普通用户理解。 实现方式 在密区（研发区）和非密区（办公区）各部署一套巴别鸟，在两套巴别鸟之间传送文件: 需要安装巴别鸟数据摆渡模块 两套服务器间需要配置传输端口 传输使用SSL加密 支持多套巴别鸟之间互传文件 超级管理员可设定特定的文件接收者及审核人 可设定从非密区向密区传送文件无需审批 所有的传输都有记录及日志 多套巴别鸟在多个网络进行文件传送: 单套巴别鸟简化的文件传送方式 ： 有些客户的核心需求是非密区往密区便捷快速传输文件，仅想在密区部署一套巴别鸟，并没有在非密区使用网盘的需求，这时候就可以使用简化的数据摆渡方式。 出于安全考虑，该方式仅支持非密区向密区传送文件，并不支持密区向非密区传送文件。 除了在密区部署完整的巴别鸟系统，也需要在非密区部署一个文件传输服务。 非密区向密区传输文件无需审批。 使用步骤 部署完成数据摆渡模块的巴别鸟会在企业控制台增加一个“传送文件配置”模块，如果在企业控制台能看到该模块入口，说明已部署成功数据摆渡模块。 在企业控制台“传送文件配置”中新建接受端口和发送端口。已确定数据摆渡的接受端和发送端。 如果其中一套巴别鸟只配置了接口端口没有配置发送端口，那么就只能接收文件但不能发送文件。如：密区只能接收文件但不能发送文件。 新建了接收端会自动生成一个token，发送端要填入该token以实现加密传输。 一个巴别鸟可以建立多个接收端，每个接收端可以选择不同的成员。如：研发部和技术部的接收端分开。 通过审核后，接收人员能在自己的巴别鸟账号“传送文件”栏目找到摆渡过来的文件。 使用者在巴别鸟企业网盘中直接右键“传送文件”选择传送的接收端进行文件传送（发件）。并在“传送文件”栏目下查看发送过来并通过审核的文件。 为保证安全，传送文件以文件为单位（在多层文件夹中夹带重要文件，骗过审核），并不支持选择文件夹传送，但支持多选文件进行传送。 具有审批权限的管理员或部门经理可以在“传送文件”栏目下对接收和发送的文件进行审核，审核通过后文件才能传输。 定制化开发 巴别鸟私有化版本可以为客户提供专业的定制化开发（二次开发）服务。在巴别鸟现有产品的基础上针对客户具体需求推出更适合客户的产品。 巴别鸟定制开发优势 从产品思维出发帮助您设计产品 不同行业有不同的工作流程及使用习惯，同时需求和最终的产品间往往也隔着很深的鸿沟。只有需求没有好的产品设计往往会使项目迟迟无法落地。为了更好的适用于您的使用场景，我们职业产品经理带队的Babel care团队会为您的企业定制属于你的解决方案及二次开发支持。 精细化估时管理 我们拥有曾服务于北大方正的精细化估时管理体系，能精确的进行开发估时管理，提高项目成功率及落地效率。项目估时清晰有据可查，有效降低企业成本并提高效率。 透明的项目跟进及验收 在项目的每一个阶段，我们都有专职项目经理和产品经理跟进。确保项目进度及验收标准。并且我们可以开放我们的Jira（项目管理工具）给客户，让客户随时了解到项目的进度及耗时。 保持更新和维护 定制开发最普遍的问题是未来的更新和维护问题。传统的定制开发因为和标准产品有较大区别，所以往往会使用新的分支，开发团队也没有精力去维护新的分支，这就造成了定制开发产品会失去持续的维护及功能更新，越来越不好用或者孤立，最终被弃用。巴别鸟注意到并解决了这个问题，我们会在标准产品的基础上使用模块化的方式开发新的定制需求，或者把定制需求结合进标准产品以配置项的方式进行管理。这样，就是定制开发产品也能享受标准产品的更新及维护服务，做到可持续发展。 支持白牌服务（OEM） 出于商业目的或品牌建设需求，一些企业需要使用自己的产品名称及logo，巴别鸟可提供符合企业要求的白牌（OEM）版本。 透明、专业、负责 负责，是客户给我们最多的和最高的评价。在项目维护期内，我们会站在企业角度考虑，及时对应修正bug并完成功能调整。为企业提供长期可持续的维护服务。 巴别鸟定制开发范围 基于API的系统对接：如与OA、CRM、PDM等系统的对接整合。 API的定制开发：针对巴别鸟企业网盘某项功能开放API。 使用巴别鸟API接口的独立功能模块或子系统的定制开发。 围绕巴别鸟企业网盘现有功能的功能扩充，流程定制，数据交换。 基于巴别鸟源码的界面重塑及功能定制化开发。 巴别鸟定制开发流程 和客户确定需求及技术实现方案。出具：《需求分析说明书》 产品经理和客户深度讨论，设计原型和交互。出具《二次开发方案》、《产品原型》、《详细模块及估时表》 商务及合同环节，客户支付预付款项。 设计出图，开发启动。 内部测试及联调。 试上线及用户测试。 用户培训。 用户验收及交付 客户支付尾款。 信创支持 巴别鸟多年来一直积极响应国产化号召，巴别鸟的产品也能运行在大多数信创环境下。特别是针对服务器端，无论是CPU、操作系统还是数据库，巴别鸟都有相应的信创解决方案。 CPU及服务器架构支持。 巴别鸟支持X86和arm指令集的国产CPU，如X86的龙芯、飞腾、麒麟、海光…同时也支持arm架构的国产CPU，如：鲲鹏架构、飞腾arm架构。 操作系统。 巴别鸟使用docker部署，支持一切支持docker的Linux操作系统。如open Euler、银河麒麟、统信UOS 数据库。 巴别鸟推荐使用AliSQL数据库或其他兼容MySQL的数据库如：open Causs （高斯）。 巴别鸟也可以为定制接入其他国产数据库。如：达梦、人大金仓、南大通用….. 客户端。 巴别鸟客户端可以运行在Linux系统上，支持麒麟、统信等国产化系统。 由于Linux系统文件管理界面并没有统一，Linux版本的巴别鸟不支持同步文件夹及映射盘功能。 分类 分类 标准部署系统（非信创） 巴别鸟信创方案（x86) 巴别鸟信创方案（arm） 信创版本不支持的功能 业务服务器 操作系统 Centos、openEuler、Ubuntu openEuler 、麒麟 鲲鹏、麒麟、统信 无 业务服务器 巴别鸟版本 标准版 巴别鸟信创版（X86） 巴别鸟信创版（arm） 无 业务服务器 数据库 MySQL 高斯、TiDB、aliSql 高斯arm 无 业务服务器 组件/中间件 tomcat tomcat、TongWeb7 tomcat 无 业务服务器 组件/中间件 pomleo pomleo（信创） pomleo（信创） 无 业务服务器 组件/中间件 Elastic Search Elastic Search（ 信创） Elastic Search（arm） 无 业务服务器 组件/中间件 Redis Babel readis Babel readis 无 存储服务器 存储系统 minio minio minio arm 无 客户端 客户端 巴别鸟win/mac客户端 巴别鸟linux/麒麟/Ubuntu客户端 需要二开移植 linux版本客户端不支持映射盘、同步文件夹功能" }, { "lang": "en", "slug": "reference-whitepaper-10-feature-list", "title": "White paper: Attachment 1: Babel function list", "description": "Chapter of \"BabelBird Enterprise Drive White Paper\": Attachment 1: BabelBird function list.", "category": "Source References", "top_category": "维护", "keywords": [ "white paper", "Attachment 1: BabelBird function list" ], "url": "en/reference-whitepaper-10-feature-list.html", "source": "content/en/reference-whitepaper-10-feature-list.md", "summary": "白皮书：附件1:巴别鸟功能列表 功能大项 功能列表 备注说明 支持平台 （ALL指全平台支持） 数据传输 文件加密上传 SSL加密上传 ALL 数据传输 文件加密下载 SSL加密下载 ALL 数据传输 文件夹上传 ALL 数据传输 文件夹下载 ALL 数据传输 批量下载 网页、win客户端、Mac客户端、麒麟客户端 数据传输 批量打包下载 文件夹打包成zip文件下载，有文件数量限制 浏览器（网页） 数据传输 断点续传 win客户端、Mac客户端、麒麟客户端 数据传输 秒传（哈希验证去重） 同样哈希的文件仅保存一份 ALL 数据传输 增量上传下载 只上传下载文件的更改部分 ALL 数据传输 上传下载列表管理 ALL 数据传输 本地文件右键快速上传文件至网盘 win客户端、Mac客户端 数据传输 本地文件右键快速发送文件至其他用户 win客户端、Mac客户端 数据传输 网闸数据摆渡（多套巴别鸟间） 密区和非密区间的数据传输（带审批） 仅私有化部署支持 新建文件 从模版创建文件结构 支持文件模版和文件夹模版 网页、客户端 新建文件 创建模版 网页、客户端 新建文件 新建office文档（word、excel、ppt） 网页、客户端 新建文件 新建文本文件 网页、客户端 新建文件 新建思维导图 网页、客户端 新建文件 新建markdown 网页、客户端 新建文件 新建收件箱 网页、客户端 新建文件 发送消息 发送消息通知给特定用户 网页、客户端 新建文件 新建子部门 网页、客户端 新建文件 新建项目 网页、客户端 新建文件 自定义新建的类型 自定义需要新建的文件类型 仅私有化部署支持 ", "headings": [ { "level": 1, "title": "白皮书：附件1:巴别鸟功能列表", "id": "1" } ], "images": [], "text": "白皮书：附件1:巴别鸟功能列表 功能大项 功能列表 备注说明 支持平台 （ALL指全平台支持） 数据传输 文件加密上传 SSL加密上传 ALL 数据传输 文件加密下载 SSL加密下载 ALL 数据传输 文件夹上传 ALL 数据传输 文件夹下载 ALL 数据传输 批量下载 网页、win客户端、Mac客户端、麒麟客户端 数据传输 批量打包下载 文件夹打包成zip文件下载，有文件数量限制 浏览器（网页） 数据传输 断点续传 win客户端、Mac客户端、麒麟客户端 数据传输 秒传（哈希验证去重） 同样哈希的文件仅保存一份 ALL 数据传输 增量上传下载 只上传下载文件的更改部分 ALL 数据传输 上传下载列表管理 ALL 数据传输 本地文件右键快速上传文件至网盘 win客户端、Mac客户端 数据传输 本地文件右键快速发送文件至其他用户 win客户端、Mac客户端 数据传输 网闸数据摆渡（多套巴别鸟间） 密区和非密区间的数据传输（带审批） 仅私有化部署支持 新建文件 从模版创建文件结构 支持文件模版和文件夹模版 网页、客户端 新建文件 创建模版 网页、客户端 新建文件 新建office文档（word、excel、ppt） 网页、客户端 新建文件 新建文本文件 网页、客户端 新建文件 新建思维导图 网页、客户端 新建文件 新建markdown 网页、客户端 新建文件 新建收件箱 网页、客户端 新建文件 发送消息 发送消息通知给特定用户 网页、客户端 新建文件 新建子部门 网页、客户端 新建文件 新建项目 网页、客户端 新建文件 自定义新建的类型 自定义需要新建的文件类型 仅私有化部署支持 文件管理 个人文件 每个用户独立的个人空间 ALL 文件管理 个人项目 仅由创建者管理，在个人文件中 ALL 文件管理 个人文件管理 是否开启个人文件、个人空间大小限制、个人文件分享开关 管理后台（企业控制台） 文件管理 企业文件 企业文件列表 ALL 文件管理 企业发布文件夹 ALL 文件管理 共同发布文件夹 ALL 文件管理 部门文件 ALL 文件管理 多级部门管理 部门可分层级管理 ALL 文件管理 收件箱 ALL 文件管理 收件箱管理（我的收件箱） ALL 文件管理 部门项目 部门管理者和创建者管理，属于部门 ALL 文件管理 我的项目 ALL 文件管理 全部项目 ALL 文件管理 我的分享 ALL 文件管理 我加入的分享 ALL 文件管理 多级回收站 部门经理及管理员可恢复被删除文件 ALL 文件管理 关注文件（提醒关注文件） 提醒被关注的文件会在被提醒者我的关注列表中展现。 ALL 文件管理 我的关注 ALL 文件管理 文件列表设置 标准列表及简洁列表切换 网页、客户端 文件管理 文件平铺及列表模式切换 网页、客户端 文件管理 文件详情查看面板 网页、客户端 文件管理 文件夹树状目录模式展示 网页、客户端 文件管理 文件排序 ALL 文件管理 设置全局默认排序 ALL 文件管理 自定义快捷菜单 网页、客户端 文件管理 瀑布流模式 网页、客户端 版本管理 保存时自动生成文件新版本 ALL 版本管理 添加版本说明 ALL 版本管理 版本回滚（设定旧版本为当前版本） ALL 版本管理 删除某个旧版本 ALL 版本管理 预览旧版本 ALL 版本管理 版本对比 网页、客户端 版本管理 文件历史版本保存时长设置 管理后台（企业控制台） 版本管理 文件历史版本保存数量设置 管理后台（企业控制台） 搜索及筛选 添加标签 ALL 搜索及筛选 标签管理 网页、客户端 搜索及筛选 标签样式 网页、客户端 搜索及筛选 左侧栏自定义展示标签 网页、客户端 搜索及筛选 企业标签统一管理 管理后台（企业控制台） 搜索及筛选 共享标签 ALL 搜索及筛选 文件列表筛选 网页、客户端 搜索及筛选 图片文件元数据筛选 网页、客户端 搜索及筛选 文件说明及文件说明查找筛选 网页、客户端 搜索及筛选 全文搜索 ALL 搜索及筛选 文件名搜索 ALL 搜索及筛选 标签搜索 ALL 搜索及筛选 选定文件夹搜索 ALL 搜索及筛选 高级搜索 网页、客户端 搜索及筛选 动态搜索 网页、客户端 搜索及筛选 档案库搜索 网页、客户端 在线编辑 及 客户端编辑 office、wps文档在线编辑 ALL 在线编辑 及 客户端编辑 office、wps文档多人协同在线编辑 ALL 在线编辑 及 客户端编辑 思维导图、txt、markdown文件在线编辑 网页、win客户端、Mac客户端、麒麟客户端 在线编辑 及 客户端编辑 office多人在线编辑显示在线编辑者操作 ALL 在线编辑 及 客户端编辑 在线编辑时锁定文件防止非在线编辑冲突 ALL 在线编辑 及 客户端编辑 客户端调用本地程序编辑（支持所有文件） win客户端、Mac客户端、麒麟客户端 在线编辑 及 客户端编辑 客户端编辑自动锁定防止其他用户编辑冲突 win客户端、Mac客户端、麒麟客户端 在线编辑 及 客户端编辑 客户端编辑退出自动解锁 win客户端、Mac客户端、麒麟客户端 分享及协作 发送文件 网页、客户端 分享及协作 邀请分享（验证加入者身份） ALL 分享及协作 链接分享（支持匿名） ALL 分享及协作 快照分享（仅分享当前版本） 网页、客户端 分享及协作 分享可选权限自定义 管理后台（企业控制台） 分享及协作 分享审批 网页、客户端 分享及协作 关闭某部门分享权限 管理后台（企业控制台） 分享及协作 分享日志及统计 网页、客户端 分享及协作 文件评论 ALL 文件预览 及 批注讨论 支持100+种格式文件的在线预览 详见支持预览格式列表 ALL 文件预览 及 批注讨论 CAD文件在线预览及批注 客户端、iOS、安卓 APP端 文件预览 及 批注讨论 3D文件预览及批注支持 网页、客户端 文件预览 及 批注讨论 H5规格视频文件及音频文件在线播放 ALL 文件预览 及 批注讨论 特殊视频及音频文件支持（可选） 需增加视频转码服务器 文件预览 及 批注讨论 在预览界面建立文字批注讨论区 ALL 文件预览 及 批注讨论 在预览界面建立手绘批注 ALL 文件预览 及 批注讨论 在预览界面建立语音批注 iOS、安卓 APP端 文件预览 及 批注讨论 在预览界面标注 ALL 文件预览 及 批注讨论 在预览界面手绘 ALL 文件预览 及 批注讨论 批注管理 ALL 文件预览 及 批注讨论 版本对比 网页、客户端 文件预览 及 批注讨论 预览时文件内内容搜索 网页、客户端 文件预览 及 批注讨论 旋转预览文件 ALL 文件评审 自定义评审流程 网页、客户端 文件评审 多阶段评审 网页、客户端 文件评审 部门设定可选评审方式 网页、客户端 文件评审 评审时批注、手绘、评审完成插入签名 网页、客户端 文件评审 评审后文件定稿 ALL 文件评审 我的评审栏目 所有评审文件统一查看管理 ALL 文件评审 生成评审报告 网页、客户端 权限管理 自定义角色权限（32项权限自由搭配） 管理后台（企业控制台） 权限管理 自定义文件权限（分享、项目、文件） 管理后台（企业控制台） 权限管理 部门及项目文件文件访问控制权限 网页、客户端 权限管理 权限有效期（到期自动失效） ALL 权限管理 多级管理员 网页、客户端 权限管理 提权申请及批准 ALL 同步文件夹 云端任意文件夹可同步到本地任意位置（需要有下载权限） win客户端、Mac客户端 同步文件夹 本地任意文件夹可同步到云端任意位置（需要有上传权限） win客户端、Mac客户端 同步文件夹 双向同步、上行同步、下行同步可切换 win客户端、Mac客户端 同步文件夹 同步文件夹中文件编辑锁定，防止冲突 win客户端、Mac客户端 同步文件夹 同步任务管理列表 win客户端、Mac客户端 同步文件夹 设定自动同步时间 win客户端、Mac客户端 同步文件夹 同步黑名单（特定类型文件不同步） win客户端、Mac客户端 虚拟映射盘 访达及资源管理器访问映射盘 win客户端、Mac客户端 虚拟映射盘 虚拟盘符、虚拟路径 win客户端、Mac客户端 虚拟映射盘 虚拟盘缓存管理 win客户端、Mac客户端 虚拟映射盘 虚拟盘文件编辑自动锁定 win客户端、Mac客户端 虚拟映射盘 点击文件打开文件引用及关联资源 win客户端、Mac客户端 虚拟映射盘 第三方应用程序可访问虚拟盘 win客户端、Mac客户端 归档及档案库 文件、文件夹、项目右键一键归档 网页、客户端 归档及档案库 档案管理员整理及分类档案 网页、客户端 归档及档案库 创建阅览室、阅览室可见范围指定 网页、客户端 归档及档案库 档案搜索及查询 网页、客户端 归档及档案库 档案借阅及借阅审批 网页、客户端 归档及档案库 档案查看记录及日志 网页、客户端 归档及档案库 阅览室管理 网页、客户端 日志及报表 可查询每个文件独立日志 ALL 日志及报表 部门分享文件统计 网页、客户端 日志及报表 部门文件权限设置统计 网页、客户端 日志及报表 部门密级文件统计 网页、客户端 日志及报表 部门文件访问统计（部门文件日志） 网页、客户端 日志及报表 部门成员使用情况查询 网页、客户端 日志及报表 审批报告 网页、客户端 日志及报表 导出部门、文件夹的文件列表 网页、客户端 日志及报表 查询文件的所有可访问者 网页、客户端 日志及报表 导出用户可访问文件及权限列表 网页、客户端 日志及报表 导出成员报表 网页、客户端 日志及报表 系统活跃度统计分析 网页、客户端 日志及报表 文件统计、活跃文件、新建文件、上传统计 网页、客户端 日志及报表 流量使用情况统计 网页、客户端 日志及报表 全盘访问日志及日志导出 网页、客户端 动态及通知 动态栏目 ALL 动态及通知 动态搜索 ALL 动态及通知 文件状态动态 ALL 动态及通知 @用户动态 ALL 动态及通知 文件批注动态 ALL 动态及通知 批注动态直接回复 ALL 讨论组 每个部门及项目自动生成讨论组 ALL 讨论组 讨论组群聊功能 ALL 讨论组 讨论组上传附件功能 ALL 讨论组 讨论组管理列表 ALL 工作台 工作台卡片管理（添加、删除、排序） 网页、客户端 工作台 工作台图表（共17个可选图表） 网页、客户端 工作台 工作台自定义图表 网页、客户端 个人设置 账户信息修改 ALL 个人设置 个人存储空间查询 ALL 个人设置 自定义默认文件排序 网页、客户端 个人设置 密码更改 ALL 个人设置 自定义接收通知类型 网页、客户端 个人设置 分组管理（个人分组管理） 网页、客户端 个人设置 使用设备管理 网页、客户端 个人设置 远程登出某设备账号 网页、客户端 个人设置 邮件存储（自动转存邮箱内容） 网页、客户端 个人设置 个人访问控制文件统计 网页、客户端 个人设置 设定个人签名 网页、客户端 多级管理员 部门可设定部门管理角色 网页、客户端 多级管理员 超级管理员 网页、客户端 多级管理员 档案管理员 网页、客户端 多级管理员 安全保密员 网页、客户端 多级管理员 安全审计员 网页、客户端 多级管理员 运维管理员 网页、客户端 多级管理员 普通成员及受限用户 网页、客户端 企业管理后台 企业基础信息配置 管理后台（企业控制台） 企业管理后台 企业logo设定及更换 管理后台（企业控制台） 企业管理后台 企业登录背景图更换 管理后台（企业控制台） 企业管理后台 企业空间用量查询 管理后台（企业控制台） 企业管理后台 关闭个人空间按钮 管理后台（企业控制台） 企业管理后台 个人文件分享按钮（关闭即不允许个人文件分享） 管理后台（企业控制台） 企业管理后台 企业用户统计 管理后台（企业控制台） 企业管理后台 邮件通知配置 管理后台（企业控制台） 企业管理后台 组织结构树管理（新增、删除、排序、管理部门） 管理后台（企业控制台） 企业管理后台 企业及部门安全策略管理 管理后台（企业控制台） 企业管理后台 权限管理（自定义可选角色及权限） 管理后台（企业控制台） 企业管理后台 成员管理列表 管理后台（企业控制台） 企业管理后台 成员密码、用户名等基本信息修改 管理后台（企业控制台） 企业管理后台 一键交接（转移文件归属） 管理后台（企业控制台） 企业管理后台 一键清空账户权限 管理后台（企业控制台） 企业管理后台 停用及删除账户 管理后台（企业控制台） 企业管理后台 账户文件下载速率限制 管理后台（企业控制台） 企业管理后台 成员所属部门及权限管理 管理后台（企业控制台） 企业管理后台 成员个人文件空间上限设定 管理后台（企业控制台） 企业管理后台 成员文件使用情况及用量统计 管理后台（企业控制台） 企业管理后台 新增企业账号（成员） 管理后台（企业控制台） 企业管理后台 批量导入成员 管理后台（企业控制台） 企业管理后台 批量编辑成员 管理后台（企业控制台） 企业管理后台 企业标签管理 管理后台（企业控制台） 企业管理后台 企业默认审批流程管理 管理后台（企业控制台） 企业管理后台 文件黑名单（黑名单文件或黑名单文件类型不允许上传） 管理后台（企业控制台） 企业管理后台 企业通知管理列表 管理后台（企业控制台） 企业管理后台 发送企业通知 管理后台（企业控制台） 企业管理后台 企业分组管理 管理后台（企业控制台） 企业管理后台 水印类型选择及水印设置 管理后台（企业控制台） 企业管理后台 访问日志栏目（统一管理整个网盘访问日志） 管理后台（企业控制台） 企业管理后台 IP策略（通过客户登录的IP地址约束上传下载登录行为） 管理后台（企业控制台） 企业管理后台 mac地址绑定（限定仅能在特定设备登录） 管理后台（企业控制台） 企业管理后台 统计分析栏目 管理后台（企业控制台） 企业管理后台 工作台推送（推送工作台特定栏目给用户） 管理后台（企业控制台） 企业管理后台 文件使用行为监控预警 异常使用情况邮件或消息通知管理员 管理后台（企业控制台） 企业管理后台 自定义企业发件邮箱 管理后台（企业控制台） 企业管理后台 自定义使用的网盘功能模块 管理后台（企业控制台） 企业管理后台 配置接入第三系统单点登录 管理后台（企业控制台） 企业管理后台 配置从第三方系统导入组织结构 管理后台（企业控制台） 企业管理后台 账户信息同步管理 管理后台（企业控制台） 企业管理后台 安全登出 管理后台（企业控制台） 智巢AI 巴别鸟AI客服助理 网页、客户端 智巢AI 定制客户专属AI助理 仅私有化部署支持 智巢AI 指定文件进行学习并回答文件中的问题 网页、客户端 智巢AI 智巢AI私有化 仅私有化部署支持 账户及第三方对接 钉钉对接及钉钉内访问支持 网页端、客户端可使用钉钉扫码登录 仅私有化部署支持 账户及第三方对接 企业微信对接及企业微信内访问支持 网页端、客户端可使用企业微信扫码登录 仅私有化部署支持 账户及第三方对接 飞书对接及飞书内访问支持 网页端、客户端可使用飞书扫码登录 仅私有化部署支持 账户及第三方对接 第三方系统通知送达 仅私有化部署支持 账户及第三方对接 第三方系统用户同步 仅私有化部署支持 账户及第三方对接 ADFS、AD域控、OA、ERP、PDM对接支持 仅私有化部署支持 账户及第三方对接 第三方账户手机端登录支持 仅私有化部署支持 账户及第三方对接 对接第三方短信平台 仅私有化部署支持 API 标准web API支持 仅私有化部署支持 API API定制服务 仅私有化部署支持 API 对接第三方API实现更多功能 仅私有化部署支持 数据安全 文件SSL加密传输 ALL 数据安全 文件分块加密存储 ALL 数据安全 文件对象存储 ALL 数据安全 转码文件预览（和源文件分开） ALL 数据安全 企业及部门安全策略 ALL 数据安全 文件密级设定 ALL 数据安全 文件独立访问权限、日志、访问统计 ALL 数据安全 嵌入文件的真水印 ALL 数据安全 预览、在线编辑、下载、打印等权限都可以分开 ALL 数据安全 分享及邀请可授权 ALL 数据安全 多级回收站 ALL 数据安全 部门数据独立 ALL 数据安全 安全审计员独立 ALL 数据安全 所有日志后台管理可查询防篡改 ALL 数据安全 权限有效期、分享有效期、项目有效期，到期自动关闭 ALL 数据安全 文件哈希验证防篡改 ALL 数据安全 支持开启二次验证 ALL 数据安全 多管理员分级 ALL 数据安全 成员、受限成员、外部成员区分 ALL 数据安全 密级文件、企业文件、个人文件、外部文件区分 ALL 数据安全 外部成员管理列表 ALL 数据安全 成员空间使用精细化控制 ALL 数据安全 IP策略及MAC地址绑定限定使用设备及区域 ALL 数据安全 多重备份（公有云异地灾备） ALL 数据安全 服务器集群高可用部署 ALL 数据安全 容灾消灾 ALL 数据安全 分布式数据库 ALL 数据安全 云盾防护 仅公有云 数据安全 多监控平台 仅公有云 数据安全 第三方安全扫描 仅公有云 存储 支持S3标准的所有对象存储 私有化部署支持 存储 支持NFS及挂载磁盘存储 私有化部署支持 存储 支持SAN存储及块存储 私有化部署支持 存储 支持为客户在通用服务器上搭建对象存储 私有化部署支持 存储 支持分布式部署及分布式存储系统 私有化部署支持 存储 支持对接NBU等备份服务器 私有化部署支持 存储 支持使用双对象存储服务器同步备份 私有化部署支持 存储 文件分块加密落盘、文件去重 私有化部署支持 私有化部署 标准部署（单服务器或虚拟机部署） 私有化部署支持 私有化部署 分布式集群部署 私有化部署支持 私有化部署 对象存储部署 私有化部署支持 私有化部署 超融合及公有云平台部署（阿里云、腾讯云、华为云、金山云等...) 私有化部署支持 私有化部署 智巢AI私有化部署 私有化部署支持 私有化部署 高可用、高冗余系统部署 私有化部署支持 私有化部署 根据用户需求提供部署方案指导 私有化部署支持 语言 简体中文版 ALL 语言 英文版 ALL 语言 定制需要的语言 仅私有化部署支持 文控模块 （可选） 文控项目创建 工程行业文控规则下的文控管理项目创建 仅私有化部署支持 文控模块 （可选） 文控项目管理 仅私有化部署支持 文控模块 （可选） 文控人员管理 项目中可添加文控人员（可发送文控邮件） 仅私有化部署支持 文控模块 （可选） 收件人管理 管理文控发送邮件的收件人及对应的发送单号 仅私有化部署支持 文控模块 （可选） 发送单信息录入 发送单基本信息及发送单号规则 仅私有化部署支持 文控模块 （可选） 发送单号自动生成 发送文控邮件时按规则自动生成发送单号 仅私有化部署支持 文控模块 （可选） 发送单自动生成 发送文控邮件时按规则自动生成本次发送的发送单 仅私有化部署支持 文控模块 （可选） 文控发件 文控发送附有文件附件及发送单的邮件到指定邮箱。 仅私有化部署支持 文控模块 （可选） 发送单管理 每次发送的发送单及邮件附件统一查询管理，发送成功失败统计，接收状态统计 仅私有化部署支持" }, { "lang": "en", "slug": "reference-whitepaper-11-basic-api", "title": "White paper: Attachment 2: Babel Open API (Basic API)", "description": "Chapter of \"BabelBird Enterprise Drive White Paper\": Attachment 2: BabelBird Open API (Basic API).", "category": "Source References", "top_category": "维护", "keywords": [ "white paper", "Attachment 2: Babel Open API (Basic API)" ], "url": "en/reference-whitepaper-11-basic-api.html", "source": "content/en/reference-whitepaper-11-basic-api.md", "summary": "白皮书：附件2:巴别鸟开放API（基础API） 访问以下链接获取最新API文档： https://www.babel.cc/p/api integration.do", "headings": [ { "level": 1, "title": "白皮书：附件2:巴别鸟开放API（基础API）", "id": "2-api-api" } ], "images": [], "text": "白皮书：附件2:巴别鸟开放API（基础API） 访问以下链接获取最新API文档： https://www.babel.cc/p/api integration.do" }, { "lang": "en", "slug": "reference-feature-list", "title": "Feature list", "description": "The function list of BabelBird Enterprise Drive includes major functions, function list, description and support platform.", "category": "Source References", "top_category": "维护", "keywords": [ "Feature list", "Support platform" ], "url": "en/reference-feature-list.html", "source": "content/en/reference-feature-list.md", "summary": "功能列表 功能大项 功能列表 备注说明 支持平台 （ALL指全平台支持） 数据传输 文件加密上传 SSL加密上传 ALL 数据传输 文件加密下载 SSL加密下载 ALL 数据传输 文件夹上传 ALL 数据传输 文件夹下载 ALL 数据传输 批量下载 网页、win客户端、Mac客户端、麒麟客户端 数据传输 批量打包下载 文件夹打包成zip文件下载，有文件数量限制 浏览器（网页） 数据传输 断点续传 win客户端、Mac客户端、麒麟客户端 数据传输 秒传（哈希验证去重） 同样哈希的文件仅保存一份 ALL 数据传输 增量上传下载 只上传下载文件的更改部分 ALL 数据传输 上传下载列表管理 ALL 数据传输 本地文件右键快速上传文件至网盘 win客户端、Mac客户端 数据传输 本地文件右键快速发送文件至其他用户 win客户端、Mac客户端 数据传输 网闸数据摆渡（多套巴别鸟间） 密区和非密区间的数据传输（带审批） 仅私有化部署支持 新建文件 从模版创建文件结构 支持文件模版和文件夹模版 网页、客户端 新建文件 创建模版 网页、客户端 新建文件 新建office文档（word、excel、ppt） 网页、客户端 新建文件 新建文本文件 网页、客户端 新建文件 新建思维导图 网页、客户端 新建文件 新建markdown 网页、客户端 新建文件 新建收件箱 网页、客户端 新建文件 发送消息 发送消息通知给特定用户 网页、客户端 新建文件 新建子部门 网页、客户端 新建文件 新建项目 网页、客户端 新建文件 自定义新建的类型 自定义需要新建的文件类型 仅私有化部署支持 文件管理 个人文件 每", "headings": [ { "level": 1, "title": "功能列表", "id": "section" } ], "images": [], "text": "功能列表 功能大项 功能列表 备注说明 支持平台 （ALL指全平台支持） 数据传输 文件加密上传 SSL加密上传 ALL 数据传输 文件加密下载 SSL加密下载 ALL 数据传输 文件夹上传 ALL 数据传输 文件夹下载 ALL 数据传输 批量下载 网页、win客户端、Mac客户端、麒麟客户端 数据传输 批量打包下载 文件夹打包成zip文件下载，有文件数量限制 浏览器（网页） 数据传输 断点续传 win客户端、Mac客户端、麒麟客户端 数据传输 秒传（哈希验证去重） 同样哈希的文件仅保存一份 ALL 数据传输 增量上传下载 只上传下载文件的更改部分 ALL 数据传输 上传下载列表管理 ALL 数据传输 本地文件右键快速上传文件至网盘 win客户端、Mac客户端 数据传输 本地文件右键快速发送文件至其他用户 win客户端、Mac客户端 数据传输 网闸数据摆渡（多套巴别鸟间） 密区和非密区间的数据传输（带审批） 仅私有化部署支持 新建文件 从模版创建文件结构 支持文件模版和文件夹模版 网页、客户端 新建文件 创建模版 网页、客户端 新建文件 新建office文档（word、excel、ppt） 网页、客户端 新建文件 新建文本文件 网页、客户端 新建文件 新建思维导图 网页、客户端 新建文件 新建markdown 网页、客户端 新建文件 新建收件箱 网页、客户端 新建文件 发送消息 发送消息通知给特定用户 网页、客户端 新建文件 新建子部门 网页、客户端 新建文件 新建项目 网页、客户端 新建文件 自定义新建的类型 自定义需要新建的文件类型 仅私有化部署支持 文件管理 个人文件 每个用户独立的个人空间 ALL 文件管理 个人项目 仅由创建者管理，在个人文件中 ALL 文件管理 个人文件管理 是否开启个人文件、个人空间大小限制、个人文件分享开关 管理后台（企业控制台） 文件管理 企业文件 企业文件列表 ALL 文件管理 企业发布文件夹 ALL 文件管理 共同发布文件夹 ALL 文件管理 部门文件 ALL 文件管理 多级部门管理 部门可分层级管理 ALL 文件管理 收件箱 ALL 文件管理 收件箱管理（我的收件箱） ALL 文件管理 部门项目 部门管理者和创建者管理，属于部门 ALL 文件管理 我的项目 ALL 文件管理 全部项目 ALL 文件管理 我的分享 ALL 文件管理 我加入的分享 ALL 文件管理 多级回收站 部门经理及管理员可恢复被删除文件 ALL 文件管理 关注文件（提醒关注文件） 提醒被关注的文件会在被提醒者我的关注列表中展现。 ALL 文件管理 我的关注 ALL 文件管理 文件列表设置 标准列表及简洁列表切换 网页、客户端 文件管理 文件平铺及列表模式切换 网页、客户端 文件管理 文件详情查看面板 网页、客户端 文件管理 文件夹树状目录模式展示 网页、客户端 文件管理 文件排序 ALL 文件管理 设置全局默认排序 ALL 文件管理 自定义快捷菜单 网页、客户端 文件管理 瀑布流模式 网页、客户端 版本管理 保存时自动生成文件新版本 ALL 版本管理 添加版本说明 ALL 版本管理 版本回滚（设定旧版本为当前版本） ALL 版本管理 删除某个旧版本 ALL 版本管理 预览旧版本 ALL 版本管理 版本对比 网页、客户端 版本管理 文件历史版本保存时长设置 管理后台（企业控制台） 版本管理 文件历史版本保存数量设置 管理后台（企业控制台） 搜索及筛选 添加标签 ALL 搜索及筛选 标签管理 网页、客户端 搜索及筛选 标签样式 网页、客户端 搜索及筛选 左侧栏自定义展示标签 网页、客户端 搜索及筛选 企业标签统一管理 管理后台（企业控制台） 搜索及筛选 共享标签 ALL 搜索及筛选 文件列表筛选 网页、客户端 搜索及筛选 图片文件元数据筛选 网页、客户端 搜索及筛选 文件说明及文件说明查找筛选 网页、客户端 搜索及筛选 全文搜索 ALL 搜索及筛选 文件名搜索 ALL 搜索及筛选 标签搜索 ALL 搜索及筛选 选定文件夹搜索 ALL 搜索及筛选 高级搜索 网页、客户端 搜索及筛选 动态搜索 网页、客户端 搜索及筛选 档案库搜索 网页、客户端 在线编辑 及 客户端编辑 office、wps文档在线编辑 ALL 在线编辑 及 客户端编辑 office、wps文档多人协同在线编辑 ALL 在线编辑 及 客户端编辑 思维导图、txt、markdown文件在线编辑 网页、win客户端、Mac客户端、麒麟客户端 在线编辑 及 客户端编辑 office多人在线编辑显示在线编辑者操作 ALL 在线编辑 及 客户端编辑 在线编辑时锁定文件防止非在线编辑冲突 ALL 在线编辑 及 客户端编辑 客户端调用本地程序编辑（支持所有文件） win客户端、Mac客户端、麒麟客户端 在线编辑 及 客户端编辑 客户端编辑自动锁定防止其他用户编辑冲突 win客户端、Mac客户端、麒麟客户端 在线编辑 及 客户端编辑 客户端编辑退出自动解锁 win客户端、Mac客户端、麒麟客户端 分享及协作 发送文件 网页、客户端 分享及协作 邀请分享（验证加入者身份） ALL 分享及协作 链接分享（支持匿名） ALL 分享及协作 快照分享（仅分享当前版本） 网页、客户端 分享及协作 分享可选权限自定义 管理后台（企业控制台） 分享及协作 分享审批 网页、客户端 分享及协作 关闭某部门分享权限 管理后台（企业控制台） 分享及协作 分享日志及统计 网页、客户端 分享及协作 文件评论 ALL 文件预览 及 批注讨论 支持100+种格式文件的在线预览 详见支持预览格式列表 ALL 文件预览 及 批注讨论 CAD文件在线预览及批注 客户端、iOS、安卓 APP端 文件预览 及 批注讨论 3D文件预览及批注支持 网页、客户端 文件预览 及 批注讨论 H5规格视频文件及音频文件在线播放 ALL 文件预览 及 批注讨论 特殊视频及音频文件支持（可选） 需增加视频转码服务器 文件预览 及 批注讨论 在预览界面建立文字批注讨论区 ALL 文件预览 及 批注讨论 在预览界面建立手绘批注 ALL 文件预览 及 批注讨论 在预览界面建立语音批注 iOS、安卓 APP端 文件预览 及 批注讨论 在预览界面标注 ALL 文件预览 及 批注讨论 在预览界面手绘 ALL 文件预览 及 批注讨论 批注管理 ALL 文件预览 及 批注讨论 版本对比 网页、客户端 文件预览 及 批注讨论 预览时文件内内容搜索 网页、客户端 文件预览 及 批注讨论 旋转预览文件 ALL 文件评审 自定义评审流程 网页、客户端 文件评审 多阶段评审 网页、客户端 文件评审 部门设定可选评审方式 网页、客户端 文件评审 评审时批注、手绘、评审完成插入签名 网页、客户端 文件评审 评审后文件定稿 ALL 文件评审 我的评审栏目 所有评审文件统一查看管理 ALL 文件评审 生成评审报告 网页、客户端 权限管理 自定义角色权限（32项权限自由搭配） 管理后台（企业控制台） 权限管理 自定义文件权限（分享、项目、文件） 管理后台（企业控制台） 权限管理 部门及项目文件文件访问控制权限 网页、客户端 权限管理 权限有效期（到期自动失效） ALL 权限管理 多级管理员 网页、客户端 权限管理 提权申请及批准 ALL 同步文件夹 云端任意文件夹可同步到本地任意位置（需要有下载权限） win客户端、Mac客户端 同步文件夹 本地任意文件夹可同步到云端任意位置（需要有上传权限） win客户端、Mac客户端 同步文件夹 双向同步、上行同步、下行同步可切换 win客户端、Mac客户端 同步文件夹 同步文件夹中文件编辑锁定，防止冲突 win客户端、Mac客户端 同步文件夹 同步任务管理列表 win客户端、Mac客户端 同步文件夹 设定自动同步时间 win客户端、Mac客户端 同步文件夹 同步黑名单（特定类型文件不同步） win客户端、Mac客户端 虚拟映射盘 访达及资源管理器访问映射盘 win客户端、Mac客户端 虚拟映射盘 虚拟盘符、虚拟路径 win客户端、Mac客户端 虚拟映射盘 虚拟盘缓存管理 win客户端、Mac客户端 虚拟映射盘 虚拟盘文件编辑自动锁定 win客户端、Mac客户端 虚拟映射盘 点击文件打开文件引用及关联资源 win客户端、Mac客户端 虚拟映射盘 第三方应用程序可访问虚拟盘 win客户端、Mac客户端 归档及档案库 文件、文件夹、项目右键一键归档 网页、客户端 归档及档案库 档案管理员整理及分类档案 网页、客户端 归档及档案库 创建阅览室、阅览室可见范围指定 网页、客户端 归档及档案库 档案搜索及查询 网页、客户端 归档及档案库 档案借阅及借阅审批 网页、客户端 归档及档案库 档案查看记录及日志 网页、客户端 归档及档案库 阅览室管理 网页、客户端 日志及报表 可查询每个文件独立日志 ALL 日志及报表 部门分享文件统计 网页、客户端 日志及报表 部门文件权限设置统计 网页、客户端 日志及报表 部门密级文件统计 网页、客户端 日志及报表 部门文件访问统计（部门文件日志） 网页、客户端 日志及报表 部门成员使用情况查询 网页、客户端 日志及报表 审批报告 网页、客户端 日志及报表 导出部门、文件夹的文件列表 网页、客户端 日志及报表 查询文件的所有可访问者 网页、客户端 日志及报表 导出用户可访问文件及权限列表 网页、客户端 日志及报表 导出成员报表 网页、客户端 日志及报表 系统活跃度统计分析 网页、客户端 日志及报表 文件统计、活跃文件、新建文件、上传统计 网页、客户端 日志及报表 流量使用情况统计 网页、客户端 日志及报表 全盘访问日志及日志导出 网页、客户端 动态及通知 动态栏目 ALL 动态及通知 动态搜索 ALL 动态及通知 文件状态动态 ALL 动态及通知 @用户动态 ALL 动态及通知 文件批注动态 ALL 动态及通知 批注动态直接回复 ALL 讨论组 每个部门及项目自动生成讨论组 ALL 讨论组 讨论组群聊功能 ALL 讨论组 讨论组上传附件功能 ALL 讨论组 讨论组管理列表 ALL 工作台 工作台卡片管理（添加、删除、排序） 网页、客户端 工作台 工作台图表（共17个可选图表） 网页、客户端 工作台 工作台自定义图表 网页、客户端 个人设置 账户信息修改 ALL 个人设置 个人存储空间查询 ALL 个人设置 自定义默认文件排序 网页、客户端 个人设置 密码更改 ALL 个人设置 自定义接收通知类型 网页、客户端 个人设置 分组管理（个人分组管理） 网页、客户端 个人设置 使用设备管理 网页、客户端 个人设置 远程登出某设备账号 网页、客户端 个人设置 邮件存储（自动转存邮箱内容） 网页、客户端 个人设置 个人访问控制文件统计 网页、客户端 个人设置 设定个人签名 网页、客户端 多级管理员 部门可设定部门管理角色 网页、客户端 多级管理员 超级管理员 网页、客户端 多级管理员 档案管理员 网页、客户端 多级管理员 安全保密员 网页、客户端 多级管理员 安全审计员 网页、客户端 多级管理员 运维管理员 网页、客户端 多级管理员 普通成员及受限用户 网页、客户端 企业管理后台 企业基础信息配置 管理后台（企业控制台） 企业管理后台 企业logo设定及更换 管理后台（企业控制台） 企业管理后台 企业登录背景图更换 管理后台（企业控制台） 企业管理后台 企业空间用量查询 管理后台（企业控制台） 企业管理后台 关闭个人空间按钮 管理后台（企业控制台） 企业管理后台 个人文件分享按钮（关闭即不允许个人文件分享） 管理后台（企业控制台） 企业管理后台 企业用户统计 管理后台（企业控制台） 企业管理后台 邮件通知配置 管理后台（企业控制台） 企业管理后台 组织结构树管理（新增、删除、排序、管理部门） 管理后台（企业控制台） 企业管理后台 企业及部门安全策略管理 管理后台（企业控制台） 企业管理后台 权限管理（自定义可选角色及权限） 管理后台（企业控制台） 企业管理后台 成员管理列表 管理后台（企业控制台） 企业管理后台 成员密码、用户名等基本信息修改 管理后台（企业控制台） 企业管理后台 一键交接（转移文件归属） 管理后台（企业控制台） 企业管理后台 一键清空账户权限 管理后台（企业控制台） 企业管理后台 停用及删除账户 管理后台（企业控制台） 企业管理后台 账户文件下载速率限制 管理后台（企业控制台） 企业管理后台 成员所属部门及权限管理 管理后台（企业控制台） 企业管理后台 成员个人文件空间上限设定 管理后台（企业控制台） 企业管理后台 成员文件使用情况及用量统计 管理后台（企业控制台） 企业管理后台 新增企业账号（成员） 管理后台（企业控制台） 企业管理后台 批量导入成员 管理后台（企业控制台） 企业管理后台 批量编辑成员 管理后台（企业控制台） 企业管理后台 企业标签管理 管理后台（企业控制台） 企业管理后台 企业默认审批流程管理 管理后台（企业控制台） 企业管理后台 文件黑名单（黑名单文件或黑名单文件类型不允许上传） 管理后台（企业控制台） 企业管理后台 企业通知管理列表 管理后台（企业控制台） 企业管理后台 发送企业通知 管理后台（企业控制台） 企业管理后台 企业分组管理 管理后台（企业控制台） 企业管理后台 水印类型选择及水印设置 管理后台（企业控制台） 企业管理后台 访问日志栏目（统一管理整个网盘访问日志） 管理后台（企业控制台） 企业管理后台 IP策略（通过客户登录的IP地址约束上传下载登录行为） 管理后台（企业控制台） 企业管理后台 mac地址绑定（限定仅能在特定设备登录） 管理后台（企业控制台） 企业管理后台 统计分析栏目 管理后台（企业控制台） 企业管理后台 工作台推送（推送工作台特定栏目给用户） 管理后台（企业控制台） 企业管理后台 文件使用行为监控预警 异常使用情况邮件或消息通知管理员 管理后台（企业控制台） 企业管理后台 自定义企业发件邮箱 管理后台（企业控制台） 企业管理后台 自定义使用的网盘功能模块 管理后台（企业控制台） 企业管理后台 配置接入第三系统单点登录 管理后台（企业控制台） 企业管理后台 配置从第三方系统导入组织结构 管理后台（企业控制台） 企业管理后台 账户信息同步管理 管理后台（企业控制台） 企业管理后台 安全登出 管理后台（企业控制台） 智巢AI 巴别鸟AI客服助理 网页、客户端 智巢AI 定制客户专属AI助理 仅私有化部署支持 智巢AI 指定文件进行学习并回答文件中的问题 网页、客户端 智巢AI 智巢AI私有化 仅私有化部署支持 账户及第三方对接 钉钉对接及钉钉内访问支持 网页端、客户端可使用钉钉扫码登录 仅私有化部署支持 账户及第三方对接 企业微信对接及企业微信内访问支持 网页端、客户端可使用企业微信扫码登录 仅私有化部署支持 账户及第三方对接 飞书对接及飞书内访问支持 网页端、客户端可使用飞书扫码登录 仅私有化部署支持 账户及第三方对接 第三方系统通知送达 仅私有化部署支持 账户及第三方对接 第三方系统用户同步 仅私有化部署支持 账户及第三方对接 ADFS、AD域控、OA、ERP、PDM对接支持 仅私有化部署支持 账户及第三方对接 第三方账户手机端登录支持 仅私有化部署支持 账户及第三方对接 对接第三方短信平台 仅私有化部署支持 API 标准web API支持 仅私有化部署支持 API API定制服务 仅私有化部署支持 API 对接第三方API实现更多功能 仅私有化部署支持 数据安全 文件SSL加密传输 ALL 数据安全 文件分块加密存储 ALL 数据安全 文件对象存储 ALL 数据安全 转码文件预览（和源文件分开） ALL 数据安全 企业及部门安全策略 ALL 数据安全 文件密级设定 ALL 数据安全 文件独立访问权限、日志、访问统计 ALL 数据安全 嵌入文件的真水印 ALL 数据安全 预览、在线编辑、下载、打印等权限都可以分开 ALL 数据安全 分享及邀请可授权 ALL 数据安全 多级回收站 ALL 数据安全 部门数据独立 ALL 数据安全 安全审计员独立 ALL 数据安全 所有日志后台管理可查询防篡改 ALL 数据安全 权限有效期、分享有效期、项目有效期，到期自动关闭 ALL 数据安全 文件哈希验证防篡改 ALL 数据安全 支持开启二次验证 ALL 数据安全 多管理员分级 ALL 数据安全 成员、受限成员、外部成员区分 ALL 数据安全 密级文件、企业文件、个人文件、外部文件区分 ALL 数据安全 外部成员管理列表 ALL 数据安全 成员空间使用精细化控制 ALL 数据安全 IP策略及MAC地址绑定限定使用设备及区域 ALL 数据安全 多重备份（公有云异地灾备） ALL 数据安全 服务器集群高可用部署 ALL 数据安全 容灾消灾 ALL 数据安全 分布式数据库 ALL 数据安全 云盾防护 仅公有云 数据安全 多监控平台 仅公有云 数据安全 第三方安全扫描 仅公有云 存储 支持S3标准的所有对象存储 私有化部署支持 存储 支持NFS及挂载磁盘存储 私有化部署支持 存储 支持SAN存储及块存储 私有化部署支持 存储 支持为客户在普通服务器上搭建对象存储 私有化部署支持 存储 支持分布式部署及分布式存储系统 私有化部署支持 存储 支持对接NBU等备份服务器 私有化部署支持 存储 支持使用双对象存储服务器同步备份 私有化部署支持 存储 文件分块加密落盘、文件去重 私有化部署支持 私有化部署 标准部署（单服务器或虚拟机部署） 私有化部署支持 私有化部署 分布式集群部署 私有化部署支持 私有化部署 对象存储部署 私有化部署支持 私有化部署 超融合及公有云平台部署（阿里云、腾讯云、华为云、金山云等...) 私有化部署支持 私有化部署 智巢AI私有化部署 私有化部署支持 私有化部署 高可用、高冗余系统部署 私有化部署支持 私有化部署 根据用户需求提供部署方案指导 私有化部署支持 语言 简体中文版 ALL 语言 英文版 ALL 语言 定制需要的语言 仅私有化部署支持 文控模块 （可选） 文控项目创建 工程行业文控规则下的文控管理项目创建 仅私有化部署支持 文控模块 （可选） 文控项目管理 仅私有化部署支持 文控模块 （可选） 文控人员管理 项目中可添加文控人员（可发送文控邮件） 仅私有化部署支持 文控模块 （可选） 收件人管理 管理文控发送邮件的收件人及对应的发送单号 仅私有化部署支持 文控模块 （可选） 发送单信息录入 发送单基本信息及发送单号规则 仅私有化部署支持 文控模块 （可选） 发送单号自动生成 发送文控邮件时按规则自动生成发送单号 仅私有化部署支持 文控模块 （可选） 发送单自动生成 发送文控邮件时按规则自动生成本次发送的发送单 仅私有化部署支持 文控模块 （可选） 文控发件 文控发送附有文件附件及发送单的邮件到指定邮箱。 仅私有化部署支持 文控模块 （可选） 发送单管理 每次发送的发送单及邮件附件统一查询管理，发送成功失败统计，接收状态统计 仅私有化部署支持" }, { "lang": "en", "slug": "reference-integration-guide", "title": "Enterprise WeChat, DingTalk and Feishu Access Guide", "description": "Access guide reference content for Enterprise WeChat, DingTalk and Feishu.", "category": "Source References", "top_category": "维护", "keywords": [ "Enterprise WeChat", "DingTalk", "Feishu", "Access Guide" ], "url": "en/reference-integration-guide.html", "source": "content/en/reference-integration-guide.md", "summary": "企业微信、钉钉及飞书接入指南 巴别鸟企业微信、钉钉、飞书接入指南 企业微信接入配置说明 1. 获得相关信息 （提供给巴别鸟） 1）企业 CropId 在此获得企业的cropId 2）应用 AngentId， Secret 通过创建内部 添加完自己的应用后，点开 san 获得agentId 与secret 2. 配置工作台主 点击工作台应用主页 https://open.weixin.qq.com/connect/oauth2/authorize?appid=XXXXXXXXXXX&redirect uri=http%3A%2F%2Fprivate.babel.cc%2Faccount%2FentWechatInnerSigninRedirect.do&response type=code&scope=snsapi base&state=STATE wechat redirect 替换其中的 appid = “XXXXXXXXXXXX”;更改为自己的cropId //redirct uri替换成 自己 的 scheme 和 domain 如 http , private.babel.cc 3. 开发者接口 1). 网页授权及JS SDK 配置 可信域名 如 private.babel.cc （需要使用微信JS SDK, 需完成域名归属验证 ，并将验证文件发给巴别鸟） 点击 网页授权及JS SDK 可信域名中输入自己的域名 再 申请域名校验，并获得验证文件 2). 企业微信授权登录 点击企业微信授权登录 配置web网页 ，扫码登录， 在 授权回调域 中输入自己的企业域名(同 可信域", "headings": [ { "level": 1, "title": "企业微信、钉钉及飞书接入指南", "id": "section" } ], "images": [], "text": "企业微信、钉钉及飞书接入指南 巴别鸟企业微信、钉钉、飞书接入指南 企业微信接入配置说明 1. 获得相关信息 （提供给巴别鸟） 1）企业 CropId 在此获得企业的cropId 2）应用 AngentId， Secret 通过创建内部 添加完自己的应用后，点开 san 获得agentId 与secret 2. 配置工作台主 点击工作台应用主页 https://open.weixin.qq.com/connect/oauth2/authorize?appid=XXXXXXXXXXX&redirect uri=http%3A%2F%2Fprivate.babel.cc%2Faccount%2FentWechatInnerSigninRedirect.do&response type=code&scope=snsapi base&state=STATE wechat redirect 替换其中的 appid = “XXXXXXXXXXXX”;更改为自己的cropId //redirct uri替换成 自己 的 scheme 和 domain 如 http , private.babel.cc 3. 开发者接口 1). 网页授权及JS SDK 配置 可信域名 如 private.babel.cc （需要使用微信JS SDK, 需完成域名归属验证 ，并将验证文件发给巴别鸟） 点击 网页授权及JS SDK 可信域名中输入自己的域名 再 申请域名校验，并获得验证文件 2). 企业微信授权登录 点击企业微信授权登录 配置web网页 ，扫码登录， 在 授权回调域 中输入自己的企业域名(同 可信域名) 如 private.babel.cc 配置 ios应用 ，输入的BundleID 需从巴别鸟获得, 并将生成的schema 发送给巴别鸟 配置 android应用， 输入的 应用签名 与 应用包名 需从巴别鸟获得，并将生成的schema 发送给巴别鸟 (android 的schema 同ios 的schema) 钉钉企业内部应用配置说明 第一部分 新建H5微应用 登录钉钉企业管理后台 钉钉企业管理后台登录网址https://oa.dingtalk.com/ /login，没有企业账号的，先注册，注册按照钉钉的注册流程即可。注意需要钉钉的管理员账号登录，因为后面新建内部应用需要有管理员权限。 新建企业内部H5微应用 1，登录钉钉开放平台 第一种方式，管理员登录成功后，点击顶部的【工作台】，找到【自建应用】，然后点击自建应用按钮。 第二种方式，管理员登录成功后，在同一个浏览器中输入https://open dev.dingtalk.com/ /index，打开网址，进入到开钉钉开放平台，如果你未登录，再登录一次。 2，新建H5微应用 进入到开钉钉开放平台后，点击顶部的【应用开发】，然后在侧边栏点击【企业内部开发】下的【H5微应用】，最后点击【创建应用按钮】 按照钉钉的要求填写应用的基本信息，开发方式选择【企业内部自主开发】 点击下一步，进入以下界面，配置开发信息界面。开发模式选【开发应用】，开发应用类型选【微应用】，其它的按钉钉要求填写。应用首页地址填写巴别鸟文档管理系统私有化后的服务器网站首页网址，服务器出口IP填写上述网址对应的IP地址，这个地址必须填写正确，否则钉钉很多功能将无法使用。点击【创建】按钮，创建应用成功。 给应用开启权限 创建应用成功后进入以下界面。点击【接口权限】 在【接口权限】界面，基础权限是默认开通的。 高级权限 企业通信录权限，需要我们手动开通，点击后面每行权限对应的按钮开通相应的权限，我们需要企业通信录的所有权限，以实现巴别鸟账号与钉钉账号打通。权限开通后如下： 至此，应用的创建与配置已经完毕。 接入巴别鸟文档管理系统 巴别鸟文档管理系统与钉钉对接，需要提供钉钉应用的信息，CorpId，AppKey，AppSecret。 获取CorpId。 登录钉钉开放平台后，点击顶部【首页】，在首页页面就可以查看CorpId。 获取AppKey，AppSecret。 登录钉钉开放平台后，点击顶部【应用开发】，左边侧栏选择【企业内部开发】 【H5微应用】，然后点击自己新建的应用，进入应用详细页面。 应用详情页面： 在这里便可以查到AppKey，AppSecret： 将获取到的CorpId，AppKey，AppSecret提供给巴别鸟的相关人员即可。 应用发布 相关配置及巴别鸟文档管理服务器准备就绪后，就可以发布H5应用了。进入应用详情页面，选择【应用发布】，然后点击【确认发布按钮】。 第二部分 钉钉扫码登录 钉钉授权登录配置 登录钉钉开放平台后，点击顶部【应用开发】，左边侧栏选择【移动应用接入】 【登录】，然后点击按钮【创建扫码登录应用授权】，创建扫码登录应用授权。 获取登录appId，appSecret 创建扫码登录应用授权成功后，在【登录】页面的列表里可以查询到应用的appId，appSecret。 将获取到的appId，appSecret提供给巴别鸟的相关人员即可。 飞书企业内部应用配置说明 第一部分 新建H5微应用 一、登陆飞书管理后台，点击应用管理 创建企业自建应用 输入相应的信息并确定创建 获取凭证与基础信息，并将获得的APP ID与APP Secret 发给巴别鸟 在应用功能项下点击网页输入网页配置，配置相应的地址 https://open.feishu.cn/open apis/authen/v1/index?app id=XXXXXXXXXX&redirect uri=http%3a%2F%2Fprivate.babel.cc%2Faccount%2FfeishuQRScanRedirect.do&state=STATE app id与地址需要替换成相应自己应用的 应用功能下打开机器人功能，以实现消息发送 需打开相应的权限，在下面权限设置中添加 应用功能下打开移动应用登录功能，以实现巴别鸟APP端，以飞书应用授权登录 用户登录协议 OAuth2.0 iOS应用配置 iOS Bundle ID 联系巴别鸟获取 android应用配置 请联系巴别鸟获取 安全设置，需要设置重定向URL 与IP 白名单 重定向URL http://private.babel.cc/account/feishuQRScanRedirect.do，用自己网盘地址及http/https 替换private.babel.cc IP 白名单，为部署是务器的公网IP地址 H5 可信域名设置为相应的网盘服务器地址 权限管理 ，暂时开通的权限有： 以应用身份读取通讯录 获取部门基础信息 获取部门组织架构信息 获取用户基本信息 获取用户组织架构信息 获取用户邮箱信息 获取用户 user ID 通过手机号或邮箱获取用户 ID 获取用户手机号 获取与发送单聊、群组消息 获取用户在群组中@机器人的消息 接收群聊中@机器人消息事件 获取用户发给机器人的单聊消息 以应用的身份发消息 给一个或多个部门的成员批量发消息 给多个用户批量发消息 发布应用 创建版本，提交版本 应用审核" }, { "lang": "en", "slug": "reference-product-intro-cases", "title": "Product introduction and case information", "description": "Babel bird enterprise network disk product introduction, Zhichao AI and customer case information.", "category": "Source References", "top_category": "维护", "keywords": [ "Product introduction", "Case", "Zhichao AI" ], "url": "en/reference-product-intro-cases.html", "source": "content/en/reference-product-intro-cases.md", "summary": "产品介绍与案例资料 以下内容按原文页序整理，便于按关键词查找功能、案例和实施信息。 PDF 第 1 页 企业网盘及文件协同管理系统 PDF 第 2 页 巴别鸟 公司介绍 BabelBird PDF 第 3 页 巴别鸟 公司概述 BabelBird 优质客户： 部分资质： 巴别鸟是上海画擎信息科技有限公司的注册商标及 主要产品，上海画擎成立于2012年，总部位于上 海，2016年于北京设立分公司。画擎科技是一个 以技术为主导的团队，创始人均来自北大方正，拥 有极强的图形图像处理和云计算技术并专注于安全 存储及办公协作系统的研发。目前，巴别鸟已经完 成了B轮融资，用户数超过80万，文档数据量已突 破30PB。 图形图像和云计算领域的孜孜耕耘，高效工作方式 的不懈探索，以及对产品用户体验的极致追求，造 就了巴别鸟文档管理及协作平台。你可以用巴别鸟 解决 企业文件统一管理、协同协作、数据安全 三 大问题，大幅提高企业工作效率及数据安全性。 PDF 第 4 页 巴别鸟 产品介绍 BabelBird PDF 第 5 页 我们解决什么问题 文档混乱管理难 邮件工作效率低 来回讨论耗时长 文件异地编辑难 根据组织结构及成员权限统一管理 在所有设备版本一致。与伙伴同步 打开大多数格式文件，在文件内容 巴别鸟可以直接编辑在线文件 文件，全文搜索快速查找 共享文件，协同工作 上直接建立批注实时讨论 从office到CAD。高效完成协作 无权限不安全 OA审批太死板 档案管理成本高 系统培训费人工 角色、行为、部门、文件的权限 可按业务需求自定义各种审批流程 内置知识管理及档案管理模块 简单使用不改变", "headings": [ { "level": 1, "title": "产品介绍与案例资料", "id": "section" }, { "level": 2, "title": "PDF 第 1 页", "id": "pdf-1" }, { "level": 2, "title": "PDF 第 2 页", "id": "pdf-2" }, { "level": 2, "title": "PDF 第 3 页", "id": "pdf-3" }, { "level": 2, "title": "PDF 第 4 页", "id": "pdf-4" }, { "level": 2, "title": "PDF 第 5 页", "id": "pdf-5" }, { "level": 2, "title": "PDF 第 6 页", "id": "pdf-6" }, { "level": 2, "title": "PDF 第 7 页", "id": "pdf-7" }, { "level": 2, "title": "PDF 第 8 页", "id": "pdf-8" }, { "level": 2, "title": "PDF 第 9 页", "id": "pdf-9" }, { "level": 2, "title": "PDF 第 10 页", "id": "pdf-10" }, { "level": 2, "title": "PDF 第 11 页", "id": "pdf-11" }, { "level": 2, "title": "PDF 第 12 页", "id": "pdf-12" }, { "level": 2, "title": "PDF 第 13 页", "id": "pdf-13" }, { "level": 2, "title": "PDF 第 14 页", "id": "pdf-14" }, { "level": 2, "title": "PDF 第 15 页", "id": "pdf-15" }, { "level": 2, "title": "PDF 第 16 页", "id": "pdf-16" }, { "level": 2, "title": "PDF 第 17 页", "id": "pdf-17" }, { "level": 2, "title": "PDF 第 18 页", "id": "pdf-18" }, { "level": 2, "title": "PDF 第 19 页", "id": "pdf-19" }, { "level": 2, "title": "PDF 第 20 页", "id": "pdf-20" }, { "level": 2, "title": "PDF 第 21 页", "id": "pdf-21" }, { "level": 2, "title": "PDF 第 22 页", "id": "pdf-22" }, { "level": 2, "title": "PDF 第 23 页", "id": "pdf-23" }, { "level": 2, "title": "PDF 第 24 页", "id": "pdf-24" }, { "level": 2, "title": "PDF 第 25 页", "id": "pdf-25" }, { "level": 2, "title": "PDF 第 26 页", "id": "pdf-26" }, { "level": 2, "title": "PDF 第 27 页", "id": "pdf-27" }, { "level": 2, "title": "PDF 第 28 页", "id": "pdf-28" }, { "level": 2, "title": "PDF 第 29 页", "id": "pdf-29" }, { "level": 2, "title": "PDF 第 30 页", "id": "pdf-30" }, { "level": 2, "title": "PDF 第 31 页", "id": "pdf-31" }, { "level": 2, "title": "PDF 第 32 页", "id": "pdf-32" }, { "level": 2, "title": "PDF 第 33 页", "id": "pdf-33" }, { "level": 2, "title": "PDF 第 34 页", "id": "pdf-34" }, { "level": 2, "title": "PDF 第 35 页", "id": "pdf-35" }, { "level": 2, "title": "PDF 第 36 页", "id": "pdf-36" }, { "level": 2, "title": "PDF 第 37 页", "id": "pdf-37" }, { "level": 2, "title": "PDF 第 38 页", "id": "pdf-38" }, { "level": 2, "title": "PDF 第 39 页", "id": "pdf-39" }, { "level": 2, "title": "PDF 第 40 页", "id": "pdf-40" }, { "level": 2, "title": "PDF 第 41 页", "id": "pdf-41" }, { "level": 2, "title": "PDF 第 42 页", "id": "pdf-42" }, { "level": 2, "title": "PDF 第 43 页", "id": "pdf-43" }, { "level": 2, "title": "PDF 第 44 页", "id": "pdf-44" }, { "level": 2, "title": "PDF 第 45 页", "id": "pdf-45" }, { "level": 2, "title": "PDF 第 46 页", "id": "pdf-46" }, { "level": 2, "title": "PDF 第 47 页", "id": "pdf-47" }, { "level": 2, "title": "PDF 第 48 页", "id": "pdf-48" }, { "level": 2, "title": "PDF 第 49 页", "id": "pdf-49" }, { "level": 2, "title": "PDF 第 50 页", "id": "pdf-50" }, { "level": 2, "title": "PDF 第 51 页", "id": "pdf-51" }, { "level": 2, "title": "PDF 第 52 页", "id": "pdf-52" }, { "level": 2, "title": "PDF 第 53 页", "id": "pdf-53" }, { "level": 2, "title": "PDF 第 54 页", "id": "pdf-54" }, { "level": 2, "title": "PDF 第 55 页", "id": "pdf-55" }, { "level": 2, "title": "PDF 第 56 页", "id": "pdf-56" }, { "level": 2, "title": "PDF 第 57 页", "id": "pdf-57" }, { "level": 2, "title": "PDF 第 58 页", "id": "pdf-58" }, { "level": 2, "title": "PDF 第 59 页", "id": "pdf-59" }, { "level": 2, "title": "PDF 第 60 页", "id": "pdf-60" }, { "level": 2, "title": "PDF 第 61 页", "id": "pdf-61" } ], "images": [], "text": "产品介绍与案例资料 以下内容按原文页序整理，便于按关键词查找功能、案例和实施信息。 PDF 第 1 页 企业网盘及文件协同管理系统 PDF 第 2 页 巴别鸟 公司介绍 BabelBird PDF 第 3 页 巴别鸟 公司概述 BabelBird 优质客户： 部分资质： 巴别鸟是上海画擎信息科技有限公司的注册商标及 主要产品，上海画擎成立于2012年，总部位于上 海，2016年于北京设立分公司。画擎科技是一个 以技术为主导的团队，创始人均来自北大方正，拥 有极强的图形图像处理和云计算技术并专注于安全 存储及办公协作系统的研发。目前，巴别鸟已经完 成了B轮融资，用户数超过80万，文档数据量已突 破30PB。 图形图像和云计算领域的孜孜耕耘，高效工作方式 的不懈探索，以及对产品用户体验的极致追求，造 就了巴别鸟文档管理及协作平台。你可以用巴别鸟 解决 企业文件统一管理、协同协作、数据安全 三 大问题，大幅提高企业工作效率及数据安全性。 PDF 第 4 页 巴别鸟 产品介绍 BabelBird PDF 第 5 页 我们解决什么问题 文档混乱管理难 邮件工作效率低 来回讨论耗时长 文件异地编辑难 根据组织结构及成员权限统一管理 在所有设备版本一致。与伙伴同步 打开大多数格式文件，在文件内容 巴别鸟可以直接编辑在线文件 文件，全文搜索快速查找 共享文件，协同工作 上直接建立批注实时讨论 从office到CAD。高效完成协作 无权限不安全 OA审批太死板 档案管理成本高 系统培训费人工 角色、行为、部门、文件的权限 可按业务需求自定义各种审批流程 内置知识管理及档案管理模块 简单使用不改变使用习惯，可内嵌 都可自定义。更可分部门管理 并导出报表，支持手写签名 满足专业的档案存储及借阅管理 于windows资源管理器直接访问 PDF 第 6 页 为什选择我们？ 1.安全 公有云SAAS结构，支持私有化部署，分块加密技术 2.易用、高效、强大 海量文档统一管理能力、强大权限、一个平台集成所需功能 3.专业 10年+扎实技术后盾、一流企业级服务、快速迭代更新 PDF 第 7 页 我们的特点 l 企业海量文件统一存储 l 文件协作管理所需的所有模块 l 最新的技术栈——更高速度和性能 l 强大的安全及权限管理 l AI技术的应用及落地 l 数据安全及数据备份 巴别鸟iOS版（iPhone、iPad），巴别鸟安卓版，巴别鸟web版，巴别鸟微信版，巴别鸟mac同步端，巴别鸟windows同步端 l 全平台 l 支持信创 PDF 第 8 页 主要功能 • 企业文件统一管理，自动同步 • 企业专属AI助理、AI标签、AI知识库 • 在线预览大多数文件格式 • 可控的分享、协作、批注讨论 • 在线编辑office文件、批注讨论图片及PDF • 在线笔记、思维导图、流程图 • 按组织结构分级管理，强大权限管理体系 • 项目文件夹、动态、工作台等常用工具 • 全文搜索、高级搜索、标签、筛选 • 独立的档案库及备份机制 • 军用级安全 PDF 第 9 页 巴别鸟 智巢AI BabelBird PDF 第 10 页 巴别鸟 智巢AI BabelBird 让AI真正服务于你的企业 • 企业专属AI助理、AI客服 • AI搜索及基于对话的复合查询 • AI自动打标签文件分类 • 可自定义的AI知识库（智能体） • AI搜图（图搜图、文搜图） • AI OCR • AI文档阅读助理 • 支持excel文件的AI数据助理 PDF 第 11 页 巴别鸟 智巢AI 智搜AI搜索 BabelBird 学习企业的所有文档，按用户权限回答问题 • 精确的权限判断 • 可以以追问的形式深入回答问题 • 支持识别图片中的文字 • 回答都给出信息来源，便于找到对应文件 • 支持多模态 PDF 第 12 页 巴别鸟 智巢AI 智搜AI搜图 BabelBird 搜索你存储在网盘中的所有图片 • 通过文字描述搜索到相关图片 • 上传图片搜索相似的图片 • 按权限判断搜索范围 PDF 第 13 页 巴别鸟 智巢AI 智能数据助理 BabelBird 利用AI进行数据分析及数据查询 • 支持多个excel文件交叉分析 • 支持以URL的形式访问第三方数据源 • AI可自动编程进行数据查询及分析 • 可根据查询数据AI自编程生成图表 • 多语言 PDF 第 14 页 巴别鸟 智巢AI 智体 BabelBird 自定义智能体 打造专属AI客服及知识库 • 自定义智能体的人设及回复逻辑(prompt) • 可指定智能体学习的目标文件夹 • 支持以URL的形式访问第三方数据源 • 客服、知识库、分析师、作家…. 等多种行业预设模版 • 支持多Agent • 可生成嵌入代码，在第三方网站中使用 PDF 第 15 页 巴别鸟 智巢AI 助理 BabelBird • 以对话的形式集成多数智巢应用 • 使用对话完成交互 • 回答企业所有文档中涉及到的知识点 • 对话形式多维度查找网盘文件 • 多模态 PDF 第 16 页 巴别鸟 智巢AI 按需开发 BabelBird 专业团队打造符合企业使用场景及流 程的定制AI • 定制开发专属智能体 • 按企业需求开发AI应用 • 支持私有化部署 • 使用最前沿的技术栈 PDF 第 17 页 巴别鸟 功能介绍 BabelBird PDF 第 18 页 巴别鸟 服务也是功能的一部分 BabelBird • 根据客户实际情况制定最适合客户的方案 • 服务期内无限大版本免费升级 • 合理功能建议免费二开支持 • 专属客户经理 • 7 24小时远程技术支持 • 30分钟内应急响应 • 无限次远程培训 PDF 第 19 页 巴别鸟 文件管理 BabelBird • 个人文件、企业文件、归档文件分区管理 • 可基于组织结构分层管理（部门） • 细致的权限管理 • 项目文件夹 • 断点续传及增量上传技术 • 文件版本管理 • 多级回收站 • 收件箱 • 专用的素材库 • 提醒及关注文件 • 批处理文件 PDF 第 20 页 巴别鸟 高级搜索 BabelBird • 搜索文件内容（全文搜索） • 标签管理及标签搜索 • 高级搜索（多条件复合搜索） • 搜索结果可筛选 • 图片元数据搜索 • 文件说明搜索 • 文件列表筛选 • AI智能搜索（直接回答问题) PDF 第 21 页 巴别鸟 分享及协作 BabelBird Finished • 功能强大的链接分享 • 带身份验证的邀请分享 • 分享可选权限自定义 • 快照分享 • 分享文件审批级批注讨论 • 快速发送文件 • 项目分享 • 分享文件可统一管理 • 可按部门、加密等级开启/关闭分享 • 分享文件批注讨论、评论 • 分享日志及统计 PDF 第 22 页 巴别鸟 在线预览、编辑协同 BabelBird • 100+文件格式支持在线预览 • CAD、3D等专业文件格式在线预览 • 音视频文件在线播放 • 在线文件内容批注讨论（可实时） • 文件版本对比 • Office、WPS格式文件的在线编辑、协同编辑 • MD、思维导图、流程图 在线编辑 PDF 第 23 页 巴别鸟 同步及虚拟磁盘 BabelBird • 同步任意文件夹不改变本地路径 BabelBird • 同步方式切换（双向、仅上传、仅下载） • 同步文件夹中文件编辑时自动锁定防止冲突 • 设定自动同步时间 • 同步文件类型黑名单 • 和onedriver一样的虚拟映射盘 • Win和mac都支持 PDF 第 24 页 巴别鸟 AI知识库 BabelBird • 自定义智能体作为知识库及在线客服 • 不同类型的知识库可以用不同智能体（知识助理） • AI可学习指定范围的文档（无需人力整理撰写知识库文档） • 权限管理，可控制智能体使用范围 • 可内嵌于第三方网页中使用 PDF 第 25 页 巴别鸟 工作台及动态 BabelBird • 工作台卡片管理 • 工作台图表 • 可自定义的工作台栏目 • 动态栏目 • @用户功能 • 动态搜索 PDF 第 26 页 巴别鸟 工作流 BabelBird • 文件定稿审批 • 可自定义的审批流程 • 多阶段评审 • 审批支持文件流转 • 支持批注、手绘、评审完成插入签名 • 支持企业外成员参与审批 • 生成评审报告 • 文控模块 PDF 第 27 页 巴别鸟 管理 BabelBird • 强大的企业控制台 • 统计及分析 • 日志和报表 • Mac地址绑定及IP策略 • 部门管理及成员管理 • 自定义角色及自定义权限管理 • 大量可自定义选项 • 多语言 PDF 第 28 页 巴别鸟 安全 BabelBird • 文件密级 • 分块加密存储技术 • 部门安全策略 • 水印 • 哈希验证 • 在线杀毒 • 文件保险箱 • 服务器容灾(高可用） • 多级回收站 • 分布式数据库 • 详细日志及报表 • 分布式对象存储系统 PDF 第 29 页 巴别鸟 权限体系 BabelBird 由管理员及拥有部门文件管理权限的人设置 管理员后台管理 由拥有部门管理权限的人管理 部门角色 部门管理 自定义可选角色权限 部门成员对部门文件的基础权限 不同成员可以不同角色 自定义文件可选权限列表 由管理员/项目负责人/部门文件管理者 设置 文件访问控制 部门空间分配 项目或部门文件权限管理者精确控制 文件/文件夹的访问授权 部门权限及密级 由项目负责人/文件分享者 设置 组织结构及成员 分享/项目权限 加入项目和分享的成员权限 其他功能选项 权限优先级：文件访问控制 角色（基础权限） PDF 第 30 页 巴别鸟 扩展 BabelBird • 开放API • AD同步、SSO单点登录 • 对接OA、ERP、企业微信、钉钉、飞书…等系统 • 支持第三方应用接入 PDF 第 31 页 巴别鸟 案例集 BabelBird PDF 第 32 页 巴别鸟 成功案例 航空航天 BabelBird 中国空间技术研究院 中国空间技术研究院（中国航天科技集团公司五院）成立于 1968年2月20日，隶属中国航天科技集团公司，是中国主要的 空间技术及其产品研制基地，中国空间事业的骨干力量。 用户需求 • 安全合规的文件管理 • 多个地区的实验室资料统一管理 • 在线办公及高效协作 • 和钉钉打通，使用钉钉用户体系 • 纯私有化内网部署，通过VPN访问 ” 解决方案 钉钉+巴别鸟 是我们第一次尝试使用新的互 • 多个安全策略保证文件存储安全合规 联网产品来解决内部的沟通协作及文件统一 • 多层备份保证文件万无一失 管理问题。大幅提高了我们的协作效率及可 • 对接钉钉，使用钉钉用户体系及组织结构 • 自动同步保证各实验室数据统一 管理性。目前从我们实验室到整个中国空间 • 支持在线office文件实时协作 都开始使用巴别鸟产品。 中国空间 钱学森实验室 高主任 PDF 第 33 页 巴别鸟 行业案例 政府机构 BabelBird 国家体育总局体育彩票管理中心 体彩中心是隶属于国家体育总局的体育彩票管理机构。负责制定、 建立、管理、发行、销售等和体育彩票相关的主要事务。是全国 体育彩票运营的主管机构。 用户需求 • 数据安全要求合规 • 能在企业微信中分享源文件 • 可直接预览大多数文件 • 下载文件可输出为PDF文件并带水印 • 可通过API实现二开，对接其他系统 解决方案 ” • 强大的权限及文件密级设置 • 企业微信集成，可以在工作台中开启巴别鸟 能满足我们要求的网盘类产品并不 • 企业微信第三方APP集成，让第三方应用可读取巴 多，巴别鸟功能全面，在企业微信 别鸟中的数据 • 支持预览大多数所需文件 对接和安全性方面相当契合我们的 • 文件下载生成带水印的PDF，保证外发文件安全 需求 • 提供完善的API接口，并根据需要定制部分接口 体彩中心 韩经理 PDF 第 34 页 巴别鸟 行业案例 大型工程 BabelBird 中石油寰球胜科工程公司 寰球胜科工程公司（寰球胜科）是中国寰球工程公司与胜科海事工 程公司于2007年联合成立的合资公司，在新加坡商业注册局正式注 册，是中国寰球工程公司(HQCEC)的控股子公司。寰球胜科是一家 海上陆上一体化的石油化工工程设计及施工服务工程公司。 用户需求 • 对工程所需的文件精细化控制 • 分权限管理不同部门及不同成员 • 和项目发包方、外包方、业主间的所有文档发送接收做 到统一管理。 • 发送文件附带符合工程管理需求传送单及单号 • 统一管理所有发送接收记录，统一归档 ” 解决方案 我们和巴别鸟团队一起设计了适用于工程行 • 部署在华为云上，满足全球访问需求 业的文控管理系统，把复杂的文控管理流程 • 在标准版基础上和甲方一起设计产品原型 自动化，使以文控为核心的工程管理方法得 • 开发文控项目模块，引入文控所需的工作流 以落地，同时大幅简化了我们的工作。 • 不断迭代以满足用户需求 • 开发MDR管理系统自动生成MDR表单 HQSM文控部门 慕蓉总 PDF 第 35 页 巴别鸟 成功案例 医院 BabelBird 中日友好医院 中日友好医院（简称“中日医院”）是国家卫生健康委员会直 属大型综合性三级甲等医院，于1984年10月23日开院。时任中 共中央总书记胡耀邦同志、时任全国政协主席邓颖超同志分别 题写院名。 用户需求 • 安全合规的文件管理 • 医院非结构化数据统一管理 • 节约日益增长的存储空间 • 医生及教职工文件传输及存储 • 在线办公及高效协作 • 纯私有化内网部署 ” 解决方案 • 多个安全策略保证文件存储安全合规 经过多轮产品筛选后我们最终选择了巴别鸟 • 提供定制API接入医院其他系统作为数据存储核心 作为我们数据存储核心，细致的服务和功能 • 文件去重存储及数据迁移服务 全面的产品是我们做出选择的原因。 • 可管理容量的个人空间分配 • 利用闲置服务器构建分布式存储系统 中日友好医院 夏主任 PDF 第 36 页 巴别鸟 行业案例 建筑及制造 BabelBird 中冶京诚 由走过50多年光辉历程的中冶集团北京钢铁设计研究总院改制 用户需求 设立的股权多元化的大型国际化创新型工程技术公司。先后为 国内外500余家客户提供了近5000项工程技术服务。在历年国 家建设部、勘察设计协会等年度排名中，均位居前列，2007年、 • 公司拥有大量全球项目，项目管理混乱 2008年连续2年位列百强之首。 • 图文信息中心需要对整个公司的文件进行归档 • 各项目组组成复杂，大量上下游文件沟通需求，自有云存 储无法满足需求 解决方案 • 公有云部署，并且优化海外带宽，保证所需访问地 区的网络速度 • 引入不同于部门管理的项目管理机制，项目文件夹 ” 可组合、转交、指定外部参与者 • 强大的权限定制可以针对人、文件、组合、部门组 我选择巴别鸟的原因是他们家的权限管 合出各种访问策略，保证安全性的前提下提高效率 • 匿名上传、外部用户手机验证快速访问、邀请等机 理是最强大的，能满足下面项目团队各 制让外部团队也能可控的加入项目进行协作 种奇葩需求。 中冶京诚 何小姐 PDF 第 37 页 巴别鸟 成功案例 建筑行业 BabelBird MCC Singapore 中冶集团新加坡分公司 我们是中冶集团在新加坡的分公司，成立于2010年，一直积极参与新加 坡的房地产领域，并取得了良好的成绩。它已经开发了五个开发项目， 用户需求 共同开发了两个开发项目，并管理了五个开发项目。该公司连续三年被 评为新加坡十大房地产开发商，并获得了“亚洲最佳影响力品牌”奖。 • 内部协作办公 • 各分支机构统一管理文件，海量数据存储 • Revit中心文件云端共享协作 • 对文件权限的高粒度细节管理 • 文件的安全管控，防止外泄 • 英文版本要求 ” 解决方案 • 私有化，高冗余部署，使用独立存储 • 对Revit中心文件同步方式进行优化 我们试用了相。当多的企业网l盘类产品，巴别 • 不同部门使用不同的密级 鸟支持Revit后基本就是最好用的云平台了 • SSO单点登录，导入组织结构 • 在线office模块 MCC Singapore 苏先生 PDF 第 38 页 巴别鸟 行业案例 文创行业 BabelBird 泡泡玛特 北京泡泡玛特文化创意有限公司成立于2010年，是中国领先的潮流 文化娱乐公司 发展近十年来，围绕全球艺术家挖掘、IP孵化运营、 消费者触达、潮玩文化推广、关联产业投资整合五个领域POP MART 泡泡玛特旨在用“创造潮流，传递美好”的品牌文化构建了 用户需求 覆盖潮流玩具全产业链的综合运营平台 • 图稿批注讨论定稿 • 3D设计稿协同交流 • 合作设计师共享及管理 • 对外约稿管理 • 对接飞书 • 文档审批管理 • 大量数据灾备 解决方案 • 使用私有云巴别鸟+对象存储 保证大量数据存储 • 二次开发定制素材库，统一管理素材 • 使用同步功能，设计师图稿快速同步 • 使用3D预览批注讨论 • 对接飞书 • 使用巴别鸟进行定稿审批 PDF 第 39 页 巴别鸟 行业案例 文创行业案例分析 BabelBird 存储备份方案 泡泡玛特的重要数据都保存在巴别鸟上，所以系统的 灾备能力是一个重要的考量。要求在现有系统持续运 行过程中保证数据实时备份，并且当存储服务器损坏 后能快速切换到备用服务器。 解决方案 • 增加一台对象存储用于实时备份 • 新增的存储服务器和主存储互为主从，数据同时写入两台存储。 • 主存储服务器损坏可自动切换到从存储服务器 • 服务器恢复后可自动修复并同步数据 • 低成本实现了数据的备份+系统高可用 PDF 第 40 页 巴别鸟 行业案例 文创行业案例分析 BabelBird 素材库（资料库）开发方案 在使用了一段时间巴别鸟企业网盘后，泡泡玛特因业务需要提出了适合他们大量产品图片、素材安全有序管理的需 求。和巴别鸟团队合作推出了更适合他们生产管理流程中使用的素材库。 需求分析 解决方案 • 重要素材（如产品图片）防止内部泄漏 • 根据用户需求设计产品方案，和用户细致讨 • 可以按分类、素材库的维度来管理每一类产品 论，设计出产品原型。 • 支持公开、使用需要审批、内部绝密 三种不同 • 二次开发推出素材库模块，按分类 /子素材 类型素材库 库的模式来管理。 • 特定的素材库子库能设定加密有效期。过了有 • 素材库有独立的权限及管理选项。 效期会弹出审批请求，通过后自动公开 • 开发相应的接口，帮助用户完成数据迁移。 • 不同的成员可以按产品线组织对素材库的访问 权限。能对多个素材库进行有效管理 • 数据迁移需求 目前素材库已经在公有云版本上线，所有企业用户都可以使用。 PDF 第 41 页 巴别鸟 行业案例 文创行业 BabelBird 混知文化 混知是国内“知识娱乐化”的先锋创始者，致力于“娱乐化、 图像化、脉络化思维讲知识”代表作《混子曰》 《半小时漫画 》 用户需求 • 图稿统一管理共享空间 • 图稿批注讨论定稿 • 素材管理 • 办公文档管理 解决方案 • 使用公有云巴别鸟，能上网即能访问 • 使用同步功能，设计师图稿快速同步 • 直接可以开启PSD、AI、CAD等设计文件 • 批注讨论图稿内容，异地远程快速沟通 • 瀑布流快虚寻找素材 PDF 第 42 页 巴别鸟 行业案例 动漫游戏行业 BabelBird 叠纸游戏 叠纸游戏成立于2013年8月，是一家专注于互动娱乐领域的新型互联 网文化公司。公司以移动端女性向手游起步，当前拥有暖暖系列及恋 爱系列这两条主要产品线，并于2020年成立叠纸动画聚集顶尖动画电 用户需求 影艺术家团队的力量，打造原创3D动画电影。 • 和外包处理团队传输大批量文件 • 海量素材文件的管理 • 动画工程文件协作 • 3D模型在线预览 • 大文件及大批量小文件传输 • 私有化部署 解决方案 • 私有部署对象存储集群 • 优化大文件及海量小文件的传输及同步 • 优化大深度文件夹的文件同步 • 优化超高数量级的文件统一归档 • 素材管理，瀑布流预览 PDF 第 43 页 巴别鸟 行业案例 动漫游戏行业 BabelBird 吉比特 叠纸厦门吉比特网络技术股份有限公司是一家专业从事网络游戏创意 策划、研发制作及商业化运营的国家重点软件企业。公司已成功研发 或运营了《问道》《问道手游》《不思议迷宫》《地下城堡2：黑暗觉 醒（安卓版）》《异化之地》《奇葩战斗家》《贪婪洞窟2》《伊洛纳》 用户需求 《失落城堡》《魔渊之刃》 等多款游戏。 • 海量素材文件的管理 • 企业内大量文件统一管理 • 存储系统安全性要求 • 对接自研系统 • 大文件及大批量小文件传输 • 私有化部署 解决方案 • 私有部署对接吉比特自有对象存储 • 根据安全部门的要求优化安全设置 • 帮助完成数据迁移 • 按客户要求优化素材管理 PDF 第 44 页 巴别鸟 行业案例 动漫游戏行业 BabelBird 西山居 金山西山居创建于1995年初夏，是国内最早的游戏工作室。在美丽的海 滨小城珠海，一群西山居居士们十年如一日兢兢业业的奋斗。20年间， 西山居凭借其雄厚的研发实力，对游戏文化内涵、画面、音乐等方面的 用户需求 深刻理解，秉承一贯的精品风格 • 海量素材文件的管理 • 在家和团队协同工作 • 3D模型在线预览 • 各地工作室文件统一管理归档 • 项目文件统一管理及共享 • 大文件及大批量小文件传输 • 部署在金山云上 ” 解决方案 • 在金山云上进行私有化部署 • 优化大文件及海量小文件的传输及同步 巴别鸟功能方。面相当全面，l并且也支持部 • 优化超高数量级的文件统一归档 署在金山云上，能很好的满足我们需求 • 素材管理，瀑布流预览 • 在线office协同编辑模块 西山居 HANAKO PDF 第 45 页 巴别鸟 行业案例 直播平台 BabelBird 企鹅体育 腾讯旗下的体育直播平台 用户需求 • 市场部素材及品牌文件分发 • 大量视频文件存储及调用 • 产品及设计稿件沟通 • 和乙方共享资料及设计稿 • 前方记者的视频及稿件能够快速发回总部审核 解决方案 ” • 公有云部署，提高视频流量支持 使用巴别鸟工作已经成为我们团队的 • 支持开启MP4，AVI等视频文件，并提供视屏转码服务 • 可在线开启PSD、AI稿件，方便和设计沟通 日常，文件直接编辑，直接保存到云 • 稿件及视频材料快速审核系统支持 端，部门协作效率高很多 • 分享链接可以直接通过微信发送并打开，增强沟通效率 企鹅体育 市场经理 kitty PDF 第 46 页 巴别鸟 行业案例 教育行业 BabelBird SIA国际艺术学校 SIA国际艺术留学于2011年在纽约曼哈顿成立，2012年SIA正式进 军中国市场。SIA国际艺术留学在基于中西方艺术文化交流合作的 前提下，为国内广大学员提供接触、了解西方艺术教育的平台 用户需求 • 100多家分支机构的统一管理共享空间 • 新教案，教学资料的快速分发 • 最新的教学资料可以统一版本给各个教师 • 直接可以查看并评阅学生的设计稿件 解决方案 • 使用公有云巴别鸟，能上网即能访问 ” • 部门功能使每个分支机构都有自己可管理的独立空 作为一个有100多家分支机构的培训 间 • 版本管理使所有分支机构都使用统一更新的最新教 机构，巴别鸟帮助我们把散落在20多 学资料 个城市的分公司统一管理起来，保证 • 总公司可以了解各个分公司的文件管理情况并管理 课件能够版本统一，实时更新。 各个分公司的知识产权 • 直接可以开启PSD、AI、CAD等设计文件，便于教 师寻找文件并和学生沟通设计 SIA国际艺术学校 Aaron PDF 第 47 页 巴别鸟 行业案例 教育行业 BabelBird 上海市徐汇区爱菊小学 上海市徐汇区爱菊小学是全国“双有”先进集体、上海市中小学行 为规范示范校、上海市安全文明校园、上海市艺术教育工作先进单 用户需求 位、上海市少先队雏鹰大队、上海市华侨捐赠管理先进单位。 • 学校党政宣传资料统一管理 • 教师送印课件审批及管理 • 历年教学资料、音视频资料建档管理 • 教师所需的网络存储空间 • 商汤系统对接 解决方案 • 在商汤服务器上完成私有化部署 • 为学校开发了文件审批流转功能 • 每个老师分配私人文件空间 • 使用素材库、档案库管理学校大量多媒体材料 • 按年级/教研组为单位管理课件及教学报告 PDF 第 48 页 巴别鸟 行业案例 教育行业 BabelBird 河北农业大学 光绪二十八年（1902年）由直隶总督袁 世凯奏请慈禧太后恩准创立直隶农务学堂（河北农大前身）， 初建在保定霍家大院（现保定建华大街二道桥北），是中国成 立最早的高等农业院校之一，河北省建立最早的高等院校。 用户需求 • 分散在各处的教学资料，教案统一管理 • 低成本完成知识管理及查询系统 • 论文无纸化，在线答辩批改，论文管理 • 收发作业及师生材料共享及备份 • 对接教务系统，统一账号 解决方案 ” • 建立私有化的河北农大知识管理系统，对旧数据进 使用巴别鸟大幅提升了我们对教研材料 行数据迁移统一管理，新数据利用同步客户端无感 及学生论文的管理效率。低成本的完成 同步，不改变教师使用习惯 • 使用共享标签，全文搜索，档案管理模块创建知识 了我们非结构化数据上云管理的阶段目 库，并有序展现 标。 希望以后能和巴别鸟团队有更深入 • 在线开启论文并在线批注建立论文答辩系统 • 使用收件箱功能分发和收取学生作业并管理 的合作 • 打通教务系统，深度整合 河北农业大学 教学研究部 尹老师 PDF 第 49 页 巴别鸟 行业案例 医疗设备 BabelBird 佳能医疗系统（中国）有限公司 1997年3月，佳能（中国）有限公司成立，全面负责佳能在中 国市场销售的各项工作。经过多年努力，目前已经基本建成6大 区域总部。佳能（中国）将深深植根于中国市场，致力于成为 一家被中国人民信赖、尊敬的企业。 用户需求 • 全国各地分部能统一管理文件 • 分权限管理不同部门及不同成员 • 快速传送大文件，外发文件统一管理 • 部门内管理扁平化，跨部门协作可控制 • 销售及市场部门的项目信息强制同步 • 支持预览医学成像图片 ” 解决方案 • 公有云服务保证全国各地的访问速度 巴别鸟的权限管理功能非常强大，能很好的 • 权限管理的初始化建议及解决方案提供 满足我们多部门多地办公过程中的苛刻的权 • 组织机构同步及部门搭建 限管理要求。提高效率及文件共享安全性。 • 涉密部门MAC地址绑定 • 分享链接统一管理 • DICOM格式文件预览支持 佳能医疗科研部 朱亚新 PDF 第 50 页 巴别鸟 行业案例 金融行业 BabelBird 朗玛峰资本 国内领先的VC机构 用户需求 • 大量尽调材料的管理归档查询 • 大量合同文书的统一管理 • 投后材料的管理及定时汇总 • 投资经理资料收集及协同讨论 • 投资合同签订前的多方讨论 ” 巴别鸟让我们的文件管理变得高效 有序，版本管理功能大幅降低了管 解决方案 理法律文书的工作量。 • 公有云部署，高存储空间方案 • 档案库功能，归档管理历史文档 • 定时收件箱获取投后材料 朗玛峰 法务 尉迟 • 用项目文件夹管理被投企业 • 协同批注在统一版本上讨论合同细节 其他金融行业客户： PDF 第 51 页 巴别鸟 行业案例 制造业 BabelBird 西子洁能集团（原杭锅集团） 杭州锅炉集团股份有限公司（以下简称公司）是一家主要从事 锅炉、压力容器、环保设备等产品集研发、生产、销售、安装 及其它工程服务于一体的大型综合企业集团，上市公司。 用户需求 • 不可以从服务器硬盘上获取完整文件信息 • 对接OA及CRM，并可以独立管理文件 • 为其他系统提供文件预览服务 • 文件版本管理及回滚 • 某些部门只能在特定的电脑上使用巴别鸟 • 在线办公及高效协作 ” 解决方案 我们使用巴别鸟来作为整个集团的统一存储， • 单点登录支持 并对接OA和CRM系统，同时巴别鸟支持 • 私有化部署，文件分块加密存储 。l SSO且可独立管理。在相对低的成本上解决 • 通过完善的API对接OA及CRM系统 • Mac地址绑定限定使用电脑 了数据统一管理问题。 • 版本管理 • 支持DWG文件的在线批注，协同讨论 杭锅集团 CIO 张斌 PDF 第 52 页 巴别鸟 行业案例 建筑行业 BabelBird 卯丁科技 深圳卯丁科技时一家服务于建筑行业的SAAS 服务提供商，为建筑设计到施工提供一系列的软件服务。卯 丁通过和巴别鸟的白牌合作得以快速推出卯丁云为其行业客 户提供服务。 用户需求 • 通过接口获得巴别鸟的全部功能，服务于卯丁客户 • 界面支持iframe帮助开发快速调用 • 单点登录及支持域控对接，和卯丁用户体系打通 • 部署于卯丁控制的阿里云服务器上，并提供开发测试 环境和技术支持 ” 解决方案 “我们花了 1整年时间寻找能满足 • 在提供标准API的基础上为客户定制API接口，满足 和客户系统的无缝对接 我们要求的系统，最终巴别鸟私有 • 提供一系列组件供客户直接调用简化二次开发流程 化系统的API定制开发解决了我们 • 在阿里云上帮助用户部署可扩展的私有化系统 的问题。相见恨晚” • 提供白牌授权服务 卯丁科技—许经理 PDF 第 53 页 巴别鸟 行业案例 房地产 BabelBird 龙湖地产 龙湖集团1993年创建于重庆，发展于全国，业务涵盖地产开发、商业运 营、租赁住房、智慧服务、房屋租售、房屋装修六大主航道业务，并积 用户需求 极试水养老、产城等创新领域。 • 内部协作办公 • 各分支机构统一管理文件，海量数据存储 • 需要同步本地文件夹到云端 • 需要在映射盘中可以同步 • 结合现有的存储系统 ” 解决方案 巴别鸟的同步盘和映射盘特别契合我们的 • 私有化并根据用户需求二开客户端 。l • 对接现有存储系统的API 需求，同时他们提供了灵活的对接方式可以 • 实现在映射盘中建立同步文件夹功能 高效快速的嵌入我们现有系统。 • SSO单点登录 龙湖地产 程卓 PDF 第 54 页 巴别鸟 行业案例 新能源汽车 BabelBird 长城华冠 长城华冠是中国专业的汽车整车设计研发机构， 成立于2003年8月，新三板上市。2018年，长城华冠推出了自 有汽车品牌前途汽车 用户需求 • 能直接在Catia及CAD稿件上进行设计评审 • 无纸化办公，节约大量A0级图纸的打印工作 • 改版知识库弥补原有知识库的不足 • 对3D点图等三维总成图形进行讨论 解决方案 ” • 使用巴别鸟建立评审流程，用巴别鸟直接开启Catia 及CAD图纸并可以在打开的图纸上绘制讨论 我们单一供应商选择了巴别鸟。因 • 为高效评审增加的GB焊接符号插入系统，可快速按 为只有他们能够让我们的工程师快 国标标记图纸，增加评审效率 • 版本管理使所有图纸的各个版本都具有备份统一保 速审图，大幅提高效率的同时节约 存 大量印刷成本 • 知识库数据迁移到巴别鸟，利用巴别鸟的搜索引擎 及档案管理重建知识管理系统 • 直接开启转化为SLI文件的点图进行讨论 长城华冠 姚经理 PDF 第 55 页 巴别鸟 行业案例 大型连锁 BabelBird 无限极（中国）有限公司 无限极(中国)有限公司﹝简称“无限极(中国)”﹞是李锦记健康 产品集团旗下成员,成立于1992年,是一家从事健康产品研发、 生产、销售及服务的现代化大型企业。 用户需求 • 文件存储安全及系统长时间稳定使用 • 统一管理各个地区及部门的文件 • 为员工提供网盘及存储服务 • 协同办公及内部文件共享 • 对接单点登录及数据中台同步组织结构 • 对接企业微信 ” 解决方案 巴别鸟为无限极的员工提供了安全、好用、 • 私有化，高冗余部署 。l 高效的文件管理及协同平台。并且能和我们 • 员工占用存储空间分配 的ADFS及数据中台完美结合并无缝嵌入到 • 企业微信对接 • 杀毒软件对接 我们的企业微信中。 • 在线office模块 无限极 员工平台负责人 杨建业 PDF 第 56 页 巴别鸟 行业案例 生物制药 BabelBird 泛生子 泛生子（纳斯达克代码：GTH）是全球前沿的癌症精准医疗公司， 专注癌症基因组学的研究和应用，提供癌症早期筛查、用药指导、 预后监测、肿瘤新药研发服务等覆盖癌症全周期的产品与服务， 致力于将创新基因组学技术，应用于与癌症相关的诊断、治疗， 最终战胜癌症 用户需求 • 数据安全要求合规 • 对接已有对象存储和AD域控 • 保证研发部门的文件安全 • 下载文件可输出为PDF文件并带水印 • 可通过API实现二开，对接其他系统 ” 解决方案 • 强大的权限及文件密级设置 巴别鸟能很好的对接我们的对象存 • 通过S3接口对接对象存储 储系统，并且可以使用 API对接我 • 研发部门使用安全策略配置为绝密部门 们的业务系统。关键是他们提供了 • 文件下载生成带水印的PDF，保证外发文件安全 • 提供完善的API接口，并根据需要定制部分接口 相当棒的后期支持服务。 泛生子 杨经理 PDF 第 57 页 巴别鸟 案例分析 BabelBird 至纯科技 成立于2000年，是一家在上交所上市的高新 技术企业，证券代码603690.SH。公司坐落于上海紫竹这个 国家级科学园区内，注册资本2.08亿元，致力于为高端先进 制造业企业提供高纯工艺系统的解决方案。 ” 立项了一年多时间，我们最终选择了 巴别鸟，除了产品优秀外，他们的定 制化开发服务解决了我的后顾之忧。 至纯科技 iT经理 庄稼 PDF 第 58 页 巴别鸟 至纯科技文件共享及安全管理解决方案 BabelBird 异地办公共享文件 研发部门强安全管理 外发文件防泄漏 至纯科技总部在上海，生产工厂在江苏启东，在台湾和日本有研 研发部门作为核心部门，对安全要求最为强烈。但又要处理好 防止外发的可编辑文件被恶意泄露 发中心。客户需求多个办公地的文件需要像在同一个系统里一样 工作协作的效率问题 共享并协作，需要保证访问速度和安全性。系统使用人数为 1. 安装绿盾文件加密系统 3000人，采用私有云部署方式。 1. 研发部门的所有账号都使用mac地址绑定到相应成员的工 作电脑。使用其他设备无法登录。 2. 所有可编辑及下载权限的文件在下载时自动绿 多个方案比较后，至纯科技选择了超融合系统方案，在总部上 盾加密为绿盾外发文件 2. 研发部关闭文件分享功能，所有文件默认密级为高 海机房部署超融合系统，同时在江苏启东工厂部署一套镜像服 3. 外发文件按分享时设定的有效期设定绿盾外发 务器。公司内部用户通过VPN连接内网巴别鸟服务器。开启一 3. 研发部使用客户端编辑在线的设计文件，本地不留存文件， 文件有效期，到达有效期文件自动删除 个限制权限的外网服务器供外网访问。同步域控服务器导入组 关机即清空本地缓存。 织结构按部门单位进行文件共享。 4. 研发部所有跨部门文件分享都需要申请临时权限 4. 绿盾外发文件可以做到防copy，防另存，可编 辑 内部权限分级管理 上下游客户及供应商文件共享 至纯科技项目总述 每个部门对权限控制的要求不同，并且至纯拥有多家分公司和 销售需要自由分享文件，售后有很多临时项目组和上下游对接 事业部，管理员维护工作量大，需要能统一管理又能适当放权。 巴别鸟团队在和至纯的合作中，在各个细节处为至 巴别鸟团队和业务部门及职能多次会议沟通后，帮助至纯科技 1. 销售部门开启链接分享，但链接分享需要部门管理员授权 纯文件共享及安全管理中定制和调整了大量功能， IT部门初始化了巴别鸟系统。解决方案如下： 同意 并在产品使用及安全的角度给至纯科技提供了大量 1. 按涉密程度不同把部门分为三类。不涉密的部门部门管理 2. 使用“项目文件夹”进行项目管理，项目文件夹可以邀请 解决方案及现场培训，帮助至纯快速完成了私有化 员权限下放，部门经理不用登录后台在前台即可管理部门， 外界用户，并且有独立的权限管理，便于项目管理者自由 系统搭建及初始化工作。最终，至纯科技巴别鸟私 添加部门成员，管理部门角色，建立子部门。轻度涉密部 调整权限。项目文件夹可以根据项目阶段进行转交并最终 有化系统能较为完美的满足至纯科技各方面的需求， 门部门经理仅可管理部门文件权限。重度涉密部门由系统 存档 并且预留了如“档案管理”，“图纸审批”，“工 管理员进行所有管理。 作台”等扩展功能。至纯提出的“文件快速发送”， 3. 除项目文件夹外，所有对外分享权限限定为“仅批注”外 “部门管理员前台操作”等功能也应用在巴别鸟公 2. 设为不允许用户拥有个人空间，用户所有文件都自动同步 界用户仅可查看预览文件并批注。 有云平台上，为更多的客户提供便捷。巴别鸟团队 到部门空间。统一管理。 4. 所有对外分享文件都设定“查看者水印”水印为查看该文 也因杰出的产品及服务获得了至纯科技“优秀供应 3. 除部门经理，所有部门成员角色都设为“仅可查看其它人 件的用户的用户ID 商” 文件”当需要下载和编辑非自己创建的文件时需要临时申 请权限。 4. 跨部门文件分享统统限制为仅可使用邀请，并且需要部门 经理授权。分享必须设定有效期。 PDF 第 59 页 巴别鸟 至纯科技研发团队图纸管理及协作巴别鸟解决方案 BabelBird 实现方法 项目要求 至纯科技的设计稿件一般是CAD及SOLIDWORKS文件，这些文件只能使用本地应用程序进行编辑，很难有效管理副本不被copy丢失。至纯 科技上市后，对知识产权及设计稿安全管理的需求相当迫切，急需解决。首先想到的解决方案是使用桌面虚拟化来解决，工程师登录虚拟桌 面进行图纸编辑。但设计类软件对设备性能要求极高，要做到设计师满意的使用体验投入极大，并且，至纯科技除了总部外还有多个生产及 研发基地，如果使用桌面虚拟化在各个地区都需要安装强大的服务器并解决互联互通问题。最终，经过大量调研他们决定使用巴别鸟。可以 1. 设计文件的安全管理（不可带出公司） 充分利用现有硬件资源最大限度的解决文件安全问题。 2. 团队协同设计共享图纸 设计稿安全管理中主要使用的巴别鸟功能 3. 图纸下发至生产环节及合作伙伴 1. Mac地址绑定：通过mac地址绑定功能使工程师只能在特定的设备上访问巴别鸟。没有绑定mac的设备无法登录并获取文件。使用此功能 后可以保证工程师只有在研发部的设备上才能查看图纸。如果需要在其他远程设备上访问图纸需要管理员授权。 2. 客户端、映射盘（云桥）：工程师安装客户端后使用云桥可以在windows资源管理器中直接访问权限范围内可访问的文件，无需同步就可 以直接进行编辑修改。编辑后自动上传至云端保存。配合本地计算机U盘端口封禁及每次关机自动清除缓存的设置，可以确保设计文件保 存于云端而本地无副本。（映射盘可以不用下载访问文件，但是文件打开时会下载缓存文件，缓存文件严格意义上有被找出并copy的嫌疑， 所以需要配合禁用U盘端口及关机自动清除缓存设置来确保文件安全。） 3. 分享审批：研发部门关闭文件分享功能（安全保密员身份登录企业后台，在组织结构部门管理里把部门文件安全策略设为“一级保密”）， 所有需要分享的文件需要上级审批通过后才能分享。 4. 多级管理员：防止iT部门管理员权限过大访问研发部门文件内容造成文件泄露，iT部门仅使用“运维管理员”权限，无法查看研发部门文 件。研发部门文件管理由部门负责人（部门经理）管理。 5. 文件及文件夹权限可追加：对于一些密级要求更高的文件，巴别鸟除了控制人的权限（角色），部门的权限外，还可以进行每个文件或文 件夹的访问控制。在部门的文件（文件夹）上点击右键打开文件访问控制，就可以控制每个部门成员对这个文件（文件夹）的访问权限。 同一个部门的共享文件也可以做到部门中有的人能看有的人不可见。 6. 可以查看但不能下载图纸：没有编辑文件必要的用户都不给予编辑权限，但能在巴别鸟上打开图纸查看并讨论。如果需要也可开启水印。 7. 所有行为日志可查：对系统的所有访问及文件的操作都有日志可以查询，文件有文件日志，系统有系统日志，可导出报表 8. 文件碎片化存储：即使服务器系统被入侵后也不能获得文件信息。每个文件被打散成若干碎片进行存储 PDF 第 60 页 巴别鸟 至纯科技研发团队图纸管理及协作巴别鸟解决方案 BabelBird 实现方法 团队协同设计共享图纸中主要使用的巴别鸟功能 项目要求 1. 直接预览CAD并批注讨论：上海总部程师和启东设备生产工厂可使用巴别鸟在CAD图纸上批注直接沟通细节问题。在客户施工现场，施工 人员也可以用手机直接开启图纸讨论，并支持语音、绘制、图片等多种方式进行批注讨论。 1. 设计文件的安全管理（不可带出公司） 2. 客户端、映射盘（云桥）：可以直接使用客户端打开云端的文件进行编辑或直接使用资源管理器中的映射盘像正常访问本地磁盘一样打开 2. 团队协同设计共享图纸 编辑设计稿。 3. 图纸下发至生产环节及合作伙伴 3. 文件锁定及冲突管理：正在编辑的文件自动锁定，防止多方修改带来的冲突问题。偶尔因同步时间造成的冲突问题会弹出冲突界面。 4. 版本管理：无限保存的版本，随时可以回退版本。 5. 同步文件夹：针对一些文件需要多个关联文件才能启动的要求保留了同步文件夹功能，可以设定任意文件夹同步至云端也可以设定云端的 任意文件夹同步到本地。同步同时可以作为文件上传的快速手段。 6. 移动端同步及第三方应用打开：对于复杂度较高的SOLIDWORKS文件，施工现场也可以使用第三方应用打开的方式调用其他应用打开图 纸进行更多操作。安卓手机支持在手机上用第三方应用编辑后自动上传新版本。 7. 增量上传：只上传文件修改新增部分的数据，大幅节约上传时间及流量。 8. 更新提示：文件更新后（编辑，建立批注，讨论），文件相关人员的APP可以收到推送更新通知，网页版动态及邮箱也能看到通知。 9. 关联文件：相互有关系的文件可以建立关联关系，便于统一查找一系列文件（未解决多张图纸关联问题）。 10.快捷方式：不同文件夹需要引用同一个文件可以使用快捷方式，源更改了快捷方式的内容也跟随源进行更改。 11.快速发送文件：电脑本地的文件可以右键快速发送给相关同事。代替用邮件及微信来传送文件。 12.所有者模式：研发部门要求由所有者管理自己的稿件（owner），在所有者模式上，只有owner才有文件编辑权限，多人协同时通过移交 owner来进行文件的管控。巴别鸟在权限设置里支持两种模式的切换。 13.建立项目：能以项目文件夹的形式管理每个项目的稿件，项目支持独立管理，可转交，研发部门完成后可以直接整个项目转交工厂。 PDF 第 61 页 巴别鸟 私有化部署流程 BabelBird 确认需求 出部署方案 签署合同 甲方支付预付款 甲方按要求准备服务器 上门或远程部署（3 5工作日） 单点登录对接（1工作日） 测试及调优（1 2工作日） 企业管理员培训 初始化服务（配置权限部门及安全策略） 使用部门及员工培训 试运行 用户答疑及配置调整 系统验收 甲方支付尾款 上海画擎信息科技有限公司 www.babel.cc" }, { "lang": "en", "slug": "reference-service-terms", "title": "Terms of Service", "description": "BabelBird Terms of Service Document Reference Content.", "category": "Source References", "top_category": "维护", "keywords": [ "Terms of Service", "law", "References" ], "url": "en/reference-service-terms.html", "source": "content/en/reference-service-terms.md", "summary": "服务条款 服务条款 服务说明 上海画擎信息科技有限公司通过以下几种方式向企业客户提供服务： 域名为bable.cc的网站; 为客户私有部署于客户机房或客户管理的云空间内的巴别鸟私有化系统; 上海画擎信息科技有限公司已经发布的名为“巴别鸟”的桌面客户端程序; 上海画擎信息科技有限公司已经发布的名为“巴别鸟”的智能移动应用程序（包括但不限于iOS，Android系统）。 巴别鸟服务条款（以下简称“服务条款”）适用于巴别鸟中提供的所有应用程序，但当甲方使用巴别鸟某一特定服务时，如该服务另有单独的服务条款、指引或规则，应成为本条款的附加条款，甲方应与本条款一并遵守。 巴别鸟以及功能的正常实现以甲方正确履行管理行为，正确完成系统设置等为前提条件。如甲方违反有关法律法规及本服务条款的规定，须自行承担完全的法律责任、并承担因此给上海画擎信息科技有限公司造成的损失的法律责任。 巴别鸟免费服务（基于SaaS） 在了解并同意本条款的基础上，甲方可以申请注册巴别鸟账户使用巴别鸟免费服务。巴别鸟免费服务内容包括免费版基本功能、限期体验功能等，详情内容以巴别鸟网站公示为准。 甲方了解并同意在注册巴别鸟时，提供真实有效的企业信息（如联系人、联系电话，电子邮箱地址等）。上海画擎信息科技有限公司有权停止提供虚假注册信息用户的巴别鸟免费服务使用权限。 甲方清楚并同意甲方及甲方用户在注册使用巴别鸟免费服务前必须同时无条件接受本服务条款所有条款项的约束，并对违反国家法律规定及本服务条款所产生的一切后果承担法律责任。 巴别鸟企业公有云版服务（基于SaaS） 开通企业公有云版服务。甲方购买巴别鸟企业公有云版时，可联系相", "headings": [ { "level": 1, "title": "服务条款", "id": "section" } ], "images": [], "text": "服务条款 服务条款 服务说明 上海画擎信息科技有限公司通过以下几种方式向企业客户提供服务： 域名为bable.cc的网站; 为客户私有部署于客户机房或客户管理的云空间内的巴别鸟私有化系统; 上海画擎信息科技有限公司已经发布的名为“巴别鸟”的桌面客户端程序; 上海画擎信息科技有限公司已经发布的名为“巴别鸟”的智能移动应用程序（包括但不限于iOS，Android系统）。 巴别鸟服务条款（以下简称“服务条款”）适用于巴别鸟中提供的所有应用程序，但当甲方使用巴别鸟某一特定服务时，如该服务另有单独的服务条款、指引或规则，应成为本条款的附加条款，甲方应与本条款一并遵守。 巴别鸟以及功能的正常实现以甲方正确履行管理行为，正确完成系统设置等为前提条件。如甲方违反有关法律法规及本服务条款的规定，须自行承担完全的法律责任、并承担因此给上海画擎信息科技有限公司造成的损失的法律责任。 巴别鸟免费服务（基于SaaS） 在了解并同意本条款的基础上，甲方可以申请注册巴别鸟账户使用巴别鸟免费服务。巴别鸟免费服务内容包括免费版基本功能、限期体验功能等，详情内容以巴别鸟网站公示为准。 甲方了解并同意在注册巴别鸟时，提供真实有效的企业信息（如联系人、联系电话，电子邮箱地址等）。上海画擎信息科技有限公司有权停止提供虚假注册信息用户的巴别鸟免费服务使用权限。 甲方清楚并同意甲方及甲方用户在注册使用巴别鸟免费服务前必须同时无条件接受本服务条款所有条款项的约束，并对违反国家法律规定及本服务条款所产生的一切后果承担法律责任。 巴别鸟企业公有云版服务（基于SaaS） 开通企业公有云版服务。甲方购买巴别鸟企业公有云版时，可联系相关客服并完成付款，支付成功后甲方所购买的巴别鸟企业公有云版即会及时开通。 企业公有云版服务时限。企业公有云本服务时限是甲方购买巴别鸟企业公有云版服务时选择的“购买时长”为准，单位为“年”。 企业公有云版服务升级。上海画擎信息科技有限公司升级巴别鸟企业公有云版服务时，甲方所使用的公有云版将会自动升级，无需支付其他费用。 企业公有云版服务续费。甲方以公有云的方式所购买的巴别鸟企业公有云版服务时限到期前1个月，上海画擎信息科技有限公司将通知甲方续缴费用，续费价格以上海画擎信息科技有限公司官方公布为准。如甲方在企业公有云版服务时限期满后仍未续费，上海画擎信息科技有限公司即停止对甲方提供已到期部分的企业公有云版服务。 企业公有云版服务终止。甲方在其购买的巴别鸟企业公有云版服务到期后仍未续费，则视为甲方自动放弃巴别鸟企业公有云版服务，甲方已到期企业公有云版服务即被限制或锁定。 巴别鸟订单合同。甲方在购买巴别鸟企业公有云版服务后，可与上海画擎信息有限公司签订[巴别鸟企业版（公有云）软件使用许可协议]。[巴别鸟企业版（公有云）软件使用许可协议]是上海画擎信息有限公司与甲方之间关于巴别鸟服务与费用的书面协定。 巴别鸟企业私有化服务 上海画擎信息科技有限公司仅提供巴别鸟部署及巴别鸟私有化授权服务。部署所需的硬件及环境由甲方准备及维护。 部署企业私有云版本。甲方购买巴别鸟企业私有云版本后，由上海画擎信息科技根据甲方签订合同时所选的项目（详见协议附件 服务订单）进行部署及相关调试。 企业私有云版服务时限。企业私有云版本的账号授权时限为终生授权，客服支持及升级服务按年为单位。购买后第一年免维护费用。 企业私有云版服务升级。上海画擎信息科技有限公司升级巴别鸟企业私有云版服务时，会第一时间通知甲方，由甲方决定是否升级，如甲方同意升级即进行远程升级服务，无需支付其他费用。 企业私有云版维护费。巴别鸟企业私有云版本为终生授权，但如果需要上海画擎信息科技有限公司提供相应的培训、答疑、及系统bug修正、系统升级服务则需支付维护费用。购买企业私有云版本后的第一年免维护费，第二年开始甲方需要按合同约定支付相应的维护费用。如逾期甲方没有支付维护费用，将视为甲方放弃本服务条款的所有服务。 巴别鸟订单合同。甲方在购买巴别鸟企业私有云版服务后，可与上海画擎信息有限公司签订[巴别鸟私有云软件使用许可协议]。[巴别鸟私有云软件使用许可协议]是上海画擎信息有限公司与甲方之间关于巴别鸟服务与费用的书面协定。 甲方权利和义务 甲方必须自行配备连通互联网和使用电信企业公有云版业务所需的设备，自行担负个人上网或第三方（包括但不限于电信或移动通信提供商）收取的通讯费、信息费、流量费等有关费用。如涉及电信企业公有云版服务的，我们建议您与您的电信企业公有云版服务提供商确认相关的费用问题。 甲方不得利用巴别鸟发送或传输任何妨碍社会治安或非法、虚假、骚扰性、侮辱性、恐吓性、伤害性、破坏性、挑衅性、淫秽色情等内容的信息。 甲方须自行负责对其系统内部成员用户进行管理，如：增加（删减）账号、设置用户密码等管理行为。甲方须指派专门的系统管理员对其巴别鸟账号进行维护管理，甲方管理员的行为由甲方负责，管理行为的后果以及责任由甲方承担。 甲方及其甲方用户应维持自身账号及密码的机密安全，甲方及其甲方用户不得将其账号或密码转让或出借第三方使用。上海画擎信息科技有限公司无法对第三方非法或未经甲方授权使用其账号及密码的行为做出甄别，因此上海画擎信息科技有限公司不承担任何责任。在此，甲方同意并承诺做到： 当甲方及甲方用户的账号及密码遭到未获授权的使用，或者发生其他任何安全问题时，甲方立即通知上海画擎信息科技有限公司。 甲方及甲方用户每次使用巴别鸟系统完毕后，点击退出巴别鸟。 甲方已清楚明白，巴别鸟仅可作为甲方内部使用，除非另有协议，甲方不得将其甲方账号进行转让、分销、或者买卖。 上海画擎信息科技有限公司权利和义务 上海画擎信息科技有限公司有义务为甲方提供巴别鸟的管理权限，便于甲方自行为甲方用户进行系统相关设置。 上海画擎信息科技有限公司不得公开、编辑或对外披露甲方及甲方用户存储在巴别鸟的任何数据。但下列情况除外 事先得到甲方书面明确授权； 根据中华人民共和国国家安全机构、公安部门的要求或根据相关的法律程序或维护社会公共利益的要求。 如甲方或甲方用户违反本服务条款的约定或法律规定，上海画擎信息科技有限公司有权中断或终止巴别鸟服务并且剩余服务费用不进行退还。 上海画擎信息科技有限公司有权根据实际情况调整或更新本服务条款内容，上海画擎信息科技有限公司有义务通知甲方并在巴别鸟官方网页或巴别鸟系统作出明显公示。修改后的条款一旦公布即有效代替原有条款，新条款适用于所有巴别鸟免费服务用户以及所有巴别鸟企业公有云版服务用户。 如甲方及甲方用户违反国家法律法规或本服务条款，上海画擎信息科技有限公司有权立即停止向甲方提供服务而不需承担任何责任。 知识产权、保密条款 巴别鸟的所有权和基于巴别鸟的所有知识产权（包括但不限于专利权、商标权、著作权、计算机软件著作权等）归上海画擎信息科技有限公司所有。上海画擎信息科技有限公司对巴别鸟的所有权不包括甲方及甲方用户存放在巴别鸟服务器中的数据。 上海画擎信息科技有限公司、上海画擎信息科技有限公司logo、巴别鸟的logo等，以及其他上海画擎信息科技有限公司标志及产品、服务名称、均为上海画擎信息科技有限公司之商标（以下简称“上海画擎信息科技有限公司标识”）。未经上海画擎信息科技有限公司事先书面同意，甲方不得将上海画擎信息科技有限公司标识以任何方式展示或使用或作其他处理，也不得向他人表明甲方有权展示、使用、或其他有权处理上海画擎信息科技有限公司标识的行为。 甲方有义务保护上海画擎信息科技有限公司的知识产权不受第三方侵犯。甲方及甲方用户不得使用、复制巴别鸟有关的软件、数据，不得允许第三方窃取巴别鸟的任何数据与软件。数据不包括甲方及甲方用户在巴别鸟服务器中存放的数据。 甲方和上海画擎信息科技有限公司任何一方对在合作过程中所获知的对方及上海画擎信息科技有限公司未向社会公开的技术及商业秘密均有保密的义务，未经对方书面许可，任何一方不得将其泄露给第三方，否则应承担违约责任并赔偿损失。 服务风险、免责声明 甲方已经清楚并明白，巴别鸟服务仅依其当前所呈现的状况提供，巴别鸟服务涉及到互联网及移动数据通讯等服务，可能会受到各个环节不稳定因素的影响。因此服务存在因上述不可抗力、洪水、地震、台风、火灾与其他天灾、战争、计算机病毒或黑客攻击、基于计算机系统和网络的各种犯罪行为、政府行为、系统出错或不稳定、用户所在位置、用户关机、GSM网络不稳定、3G网络不稳定、互联网络线路故障、骨干网通信线路故障原因等造成的服务中断或不能满足用户要求并因此给甲方带来损失的风险。甲方需承担上述风险，上海画擎信息科技有限公司不提供对巴别鸟适销性、适用性、可靠性、及时性、安全性、完整性、无病毒及无错误的任何明示或默认保证，不承担因此而对甲方造成的任何直接、间接、附带、衍生或惩罚性的赔偿。 如巴别鸟所发生的故障影响到甲方的正常使用，上海画擎信息科技有限公司承诺在第一时间内与相关单位配合，及时处理进行修复。上海画擎信息科技有限公司保留不经事前通知为维修保养、升级或其他目的暂停巴别鸟任何部分的权利。在此期间发生的服务暂停现象，或由于网络通路的偶然阻塞造成服务应用故障，属正常情况，不可视为上海画擎信息科技有限公司违约。 甲方同意，甲方与甲方用户经由巴别鸟以上传、张贴、发送即时消息、电子邮件或其他方式传送的资讯、资料、文字、软件、音乐、音频、照片、图片、视频、信息、资源链接、用户登记资料或其他资料（以下简称“内容”），均由甲方与甲方用户承担完全的法律责任，上海画擎信息科技有限公司无须承担任何直接、间接、或连带责任。由于上海画擎信息科技有限公司无法控制经由巴别鸟传送的内容，也无法对用户的使用行为进行全面监控，因此不保证甲方内容的合法性、正确性、完整性、真实性或品质。如甲方的内容存在侵犯第三人著作权的可能，上海画擎信息科技有限公司将遵循国家的法律法规进行处理。 甲方已经清楚地了解并知道，甲方用户如需使用巴别鸟必须接受本服务条款。在甲方部分或全部甲方用户不接受或不同意本服务条款而导致无法使用巴别鸟时，甲方仍同意向上海画擎信息科技有限公司支付服务费用。 甲方承诺因甲方、甲方系统管理员、甲方用户对巴别鸟的错误操作而对甲方所造成的任何损失负完全责任。这些错误操作包括但不限于甲方系统管理员误删了甲方用户所造成的数据丢失、甲方用户错误地删除了甲方企业网盘中的共享数据等。 甲方及甲方用户已经清楚地了解到，其通过巴别鸟与商家或个人进行任何形式的通讯或商业往来、或参与促销活动，包含相关商品或服务之付款及交付，以及达成的其他任何相关条款、条件、保证或证明，完全为甲方及甲方成员与商家及其他个人之间的行为。除有关法律有明文规定要求上海画擎信息科技有限公司承担责任以外，甲方因上述任何交易或上述商家或个人而遭受的任何性质的损失或损害，上海画擎信息科技有限公司均不予负责。 违约责任 甲方使用巴别鸟前须清楚了解并同意本服务条款，并对违反国家法律规定及本服务条款所产生的一切后果承担法律责任。 因上海画擎信息科技有限公司过失而造成甲方在使用巴别鸟过程中遭受损失的，甲方有权以书面形式通知上海画擎信息科技有限公司终止其巴别鸟账号。经上海画擎信息科技有限公司查证如甲方之情况属实，上海画擎信息科技有限公司会在10个工作日内按约收取服务起始日至服务终止日期间产生的费用后将甲方余款（如有）退还。 服务变更、中断或终止及服务条款修改 巴别鸟的所有权和运作权、一切解释权归上海画擎信息科技有限公司所有。上海画擎信息科技有限公司有权随时根据国家有关法律、法规的变化、行业的发展及公司经营状况和经营策略的调整等情况修改本条款。 上海画擎信息科技有限公司修改巴别鸟服务或本服务条款时，应根据本条款6.4项执行。甲方有义务对最新的服务条款进行仔细阅读并确认，当发生有关争议时，以最新的服务条款为准。 上海画擎信息科技有限公司保留对巴别鸟中所有应用程序的价格调整权及产品试用期的调整权。 如发生下列任何一种情况，上海画擎信息科技有限公司有权随时中断或终止向甲方提供服务或禁用某些甲方用户账号而无须通知甲方： 甲方违反本服务条款的规定； 按照国家主管部门的要求； 其他上海画擎信息科技有限公司认为是符合整体服务需求的特殊情形。 法律及争议解决 本服务条款要与国家相关法律、法规一致，如发生与相关法律、法规条款有相抵触的内容，抵触部分以法律、法规条款为准。 如双方发生任何争议但又不能友好协商的，任何一方均可向上海画擎信息科技有限公司住所地上海市有管辖权的人民法院提起诉讼。 巴别鸟提供的售后服务 巴别鸟采用一对一专人服务模式，有专门的客户经理负责为客户提供服务。 维护单位名称：上海画擎信息科技有限公司 软件维护期为一年，第二年后客户需缴纳维护费，进入下一轮软件维护期，如客户维护期满后不缴纳服务费，客户可以继续使用系统，但我司不再提供维护服务，直到补齐年服务费用后，服务继续。 维护期内上海画擎负责提供合同范围内软件版本的程序代码及系统配置信息的维护、支持，不包含因业务改变等因素所引起的新增功能开发。如中日友好医院需要新增功能及因业务流程变更带来的客户化开发服务，则由双方协商确定实施方案。 免费服务内容和范围 巴别鸟对所有付费客户提供产品使用周期中的终身免费质保服务，包括： 5 24小时的电话技术支持服务 7 24小时的紧急灾备处理服务 免费在线培训，系统使用指导 BUG第一时间反馈，快速处理 软件更新及升级服务 针对用户数量超过1000人的企业用户，巴别鸟提供了产品使用周期中的终身免费VIP服务，包括： 付费客户的所有免费服务 系统搭建及需求对应解决方案咨询服务 代客户初始化系统及完成配置 免费数据迁移服务（小于10TB的数据） 每年免费上门培训1次（用户数超过10000每年有三次免费上门培训机会） 专属大客户经理责任制服务 针对私有化用户，在用户正常缴纳年服务费的前提下，享受如下免费服务： 付费客户的所有免费服务 免费系统升级及更新服务，纯内网用户（内网无法连接到互联网）每年有1次免费上门升级及更新服务 代客户初始化系统及完成配置 服务器性能优化及排障 每年免费上门培训1次，无限次远程培训 针对基于巴别鸟系统的二次开发及功能定制用户，享受如下免费服务： 付费客户的所有免费服务 二次开发部分的功能质保，Bug修正 接口及功能联调服务 二次开发部分代码及接口的注释及指导服务，方便用户再开发 完工验收后，在我方成本可承受范围内的微调及功能修正（非Bug） 收费服务 在现有系统上的再开发工作，按需求评估开发工时及难度系数，按工时结算。 产品设计服务。根据客户新需求帮助客户进行产品架构、功能及交互的设计，并提供技术咨询。 有偿上门培训及调试服务。免费额度用完或不符合免费上门服务条件的用户可以付费申请。费用为 2000元1人1天 及报销到达用户处所的交通费用（高铁及当地出租车） 提供的服务项目包括如下： 序号 服务项目 服务内容 1 首访服务 由服务人员主动开展首次访问服务 2 回访服务 由服务人员主动开展回访的服务 3 软件常规运行维护服务 所购买软件的程序代码维护，如修补软件缺陷、安装调试软件补丁 4 系统升级技术咨询 当系统升级时提供的技术咨询服务 5 软件升级通知 当该版本软件升级时，及时通知客户 服务方式包括： 热线支持：通过400热线电话向客户提供技术问题解答； E MAIL支持：通过E MAIL解答客户问题； 远程维护：通过远程方式对客户环境下的巴别鸟软件进行调试。客户需提供远程维护所需的环境，否则，由客户承担因此而引起的售后响应时间滞后的责任。 现场服务：如属远程维护所不能解决的问题，我司会承担现场服务。属于应用软件自身问题带来的现场服务，属于免费维护范围。 故障处理流程 当客户使用中出现问题： 立即拨打专职客户经理电话（或微信联系），可以解决的立即解决； 不能立即解决的，立即联系技术人员对接，由技术人员远程协助客户解决； 仍然没有解决，反馈给客户经理，由客户经理安排技术人员上门服务。 其他 如本服务条款中的任何条款无论因何种原因完全或部分无效或不具有执行力，本服务条款的其余条款仍应有效且具有约束力，并且努力使该规定反映之意向具备效力。 本服务条款构成甲方与上海画擎信息科技有限公司之全部协议，规范您对本服务之使用，并取代您先前与上海画擎信息科技有限公司达成的全部协议。但在甲方使用相关服务、或使用第三方提供的内容或软件时，亦应遵从所适用之附加条款及权利。 上海画擎信息科技有限公司保留本服务条款之所有解释权。 甲方（盖章）： 乙方（盖章）： 甲方代表（签字）： 乙方代表（签字）： 日 期： 日 期：" }, { "lang": "en", "slug": "reference-whitepaper-images", "title": "White Paper Image Index", "description": "All embedded images extracted from the BabelBird enterprise network disk white paper are used for illustration, original text comparison and AI visual data indexing.", "category": "Source References", "top_category": "维护", "keywords": [ "white paper", "picture", "screenshot", "With pictures" ], "url": "en/reference-whitepaper-images.html", "source": "content/en/reference-whitepaper-images.md", "summary": "白皮书图片索引 本页汇总《巴别鸟企业网盘白皮书》中的全部嵌入图片。 这些图片从源文档中按原始顺序抽取，保留为可直接访问的静态资源。页面主要用于原文对照、AI 视觉资料索引、后续人工挑选配图和搜索引擎发现。 项 数值 图片数量 129 来源文件 巴别鸟企业网盘白皮书.docx 白皮书图片索引图片 001 来源：巴别鸟企业网盘白皮书 / word/media/image1.png 静态路径： assets/images/whitepaper/whitepaper 001.png 白皮书图片索引图片 001 白皮书图片索引图片 001，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 002 来源：巴别鸟企业网盘白皮书 / word/media/image10.png 静态路径： assets/images/whitepaper/whitepaper 002.png 白皮书图片索引图片 002 白皮书图片索引图片 002，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 003 来源：巴别鸟企业网盘白皮书 / word/media/image100.png 静态路径： assets/images/whitepaper/whitepaper 003.png 白皮书图片索引图片 003 白皮书图片索引图片 003，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 004 来源：巴别鸟企业网盘白皮书 / word/media/image101.png 静态路径： assets/images/whitepaper/whitepaper 004.png", "headings": [ { "level": 1, "title": "白皮书图片索引", "id": "section" }, { "level": 2, "title": "白皮书图片索引图片 001", "id": "001" }, { "level": 2, "title": "白皮书图片索引图片 002", "id": "002" }, { "level": 2, "title": "白皮书图片索引图片 003", "id": "003" }, { "level": 2, "title": "白皮书图片索引图片 004", "id": "004" }, { "level": 2, "title": "白皮书图片索引图片 005", "id": "005" }, { "level": 2, "title": "白皮书图片索引图片 006", "id": "006" }, { "level": 2, "title": "白皮书图片索引图片 007", "id": "007" }, { "level": 2, "title": "白皮书图片索引图片 008", "id": "008" }, { "level": 2, "title": "白皮书图片索引图片 009", "id": "009" }, { "level": 2, "title": "白皮书图片索引图片 010", "id": "010" }, { "level": 2, "title": "白皮书图片索引图片 011", "id": "011" }, { "level": 2, "title": "白皮书图片索引图片 012", "id": "012" }, { "level": 2, "title": "白皮书图片索引图片 013", "id": "013" }, { "level": 2, "title": "白皮书图片索引图片 014", "id": "014" }, { "level": 2, "title": "白皮书图片索引图片 015", "id": "015" }, { "level": 2, "title": "白皮书图片索引图片 016", "id": "016" }, { "level": 2, "title": "白皮书图片索引图片 017", "id": "017" }, { "level": 2, "title": "白皮书图片索引图片 018", "id": "018" }, { "level": 2, "title": "白皮书图片索引图片 019", "id": "019" }, { "level": 2, "title": "白皮书图片索引图片 020", "id": "020" }, { "level": 2, "title": "白皮书图片索引图片 021", "id": "021" }, { "level": 2, "title": "白皮书图片索引图片 022", "id": "022" }, { "level": 2, "title": "白皮书图片索引图片 023", "id": "023" }, { "level": 2, "title": "白皮书图片索引图片 024", "id": "024" }, { "level": 2, "title": "白皮书图片索引图片 025", "id": "025" }, { "level": 2, "title": "白皮书图片索引图片 026", "id": "026" }, { "level": 2, "title": "白皮书图片索引图片 027", "id": "027" }, { "level": 2, "title": "白皮书图片索引图片 028", "id": "028" }, { "level": 2, "title": "白皮书图片索引图片 029", "id": "029" }, { "level": 2, "title": "白皮书图片索引图片 030", "id": "030" }, { "level": 2, "title": "白皮书图片索引图片 031", "id": "031" }, { "level": 2, "title": "白皮书图片索引图片 032", "id": "032" }, { "level": 2, "title": "白皮书图片索引图片 033", "id": "033" }, { "level": 2, "title": "白皮书图片索引图片 034", "id": "034" }, { "level": 2, "title": "白皮书图片索引图片 035", "id": "035" }, { "level": 2, "title": "白皮书图片索引图片 036", "id": "036" }, { "level": 2, "title": "白皮书图片索引图片 037", "id": "037" }, { "level": 2, "title": "白皮书图片索引图片 038", "id": "038" }, { "level": 2, "title": "白皮书图片索引图片 039", "id": "039" }, { "level": 2, "title": "白皮书图片索引图片 040", "id": "040" }, { "level": 2, "title": "白皮书图片索引图片 041", "id": "041" }, { "level": 2, "title": "白皮书图片索引图片 042", "id": "042" }, { "level": 2, "title": "白皮书图片索引图片 043", "id": "043" }, { "level": 2, "title": "白皮书图片索引图片 044", "id": "044" }, { "level": 2, "title": "白皮书图片索引图片 045", "id": "045" }, { "level": 2, "title": "白皮书图片索引图片 046", "id": "046" }, { "level": 2, "title": "白皮书图片索引图片 047", "id": "047" }, { "level": 2, "title": "白皮书图片索引图片 048", "id": "048" }, { "level": 2, "title": "白皮书图片索引图片 049", "id": "049" }, { "level": 2, "title": "白皮书图片索引图片 050", "id": "050" }, { "level": 2, "title": "白皮书图片索引图片 051", "id": "051" }, { "level": 2, "title": "白皮书图片索引图片 052", "id": "052" }, { "level": 2, "title": "白皮书图片索引图片 053", "id": "053" }, { "level": 2, "title": "白皮书图片索引图片 054", "id": "054" }, { "level": 2, "title": "白皮书图片索引图片 055", "id": "055" }, { "level": 2, "title": "白皮书图片索引图片 056", "id": "056" }, { "level": 2, "title": "白皮书图片索引图片 057", "id": "057" }, { "level": 2, "title": "白皮书图片索引图片 058", "id": "058" }, { "level": 2, "title": "白皮书图片索引图片 059", "id": "059" }, { "level": 2, "title": "白皮书图片索引图片 060", "id": "060" }, { "level": 2, "title": "白皮书图片索引图片 061", "id": "061" }, { "level": 2, "title": "白皮书图片索引图片 062", "id": "062" }, { "level": 2, "title": "白皮书图片索引图片 063", "id": "063" }, { "level": 2, "title": "白皮书图片索引图片 064", "id": "064" }, { "level": 2, "title": "白皮书图片索引图片 065", "id": "065" }, { "level": 2, "title": "白皮书图片索引图片 066", "id": "066" }, { "level": 2, "title": "白皮书图片索引图片 067", "id": "067" }, { "level": 2, "title": "白皮书图片索引图片 068", "id": "068" }, { "level": 2, "title": "白皮书图片索引图片 069", "id": "069" }, { "level": 2, "title": "白皮书图片索引图片 070", "id": "070" }, { "level": 2, "title": "白皮书图片索引图片 071", "id": "071" }, { "level": 2, "title": "白皮书图片索引图片 072", "id": "072" }, { "level": 2, "title": "白皮书图片索引图片 073", "id": "073" }, { "level": 2, "title": "白皮书图片索引图片 074", "id": "074" }, { "level": 2, "title": "白皮书图片索引图片 075", "id": "075" }, { "level": 2, "title": "白皮书图片索引图片 076", "id": "076" }, { "level": 2, "title": "白皮书图片索引图片 077", "id": "077" }, { "level": 2, "title": "白皮书图片索引图片 078", "id": "078" }, { "level": 2, "title": "白皮书图片索引图片 079", "id": "079" }, { "level": 2, "title": "白皮书图片索引图片 080", "id": "080" }, { "level": 2, "title": "白皮书图片索引图片 081", "id": "081" }, { "level": 2, "title": "白皮书图片索引图片 082", "id": "082" }, { "level": 2, "title": "白皮书图片索引图片 083", "id": "083" }, { "level": 2, "title": "白皮书图片索引图片 084", "id": "084" }, { "level": 2, "title": "白皮书图片索引图片 085", "id": "085" }, { "level": 2, "title": "白皮书图片索引图片 086", "id": "086" }, { "level": 2, "title": "白皮书图片索引图片 087", "id": "087" }, { "level": 2, "title": "白皮书图片索引图片 088", "id": "088" }, { "level": 2, "title": "白皮书图片索引图片 089", "id": "089" }, { "level": 2, "title": "白皮书图片索引图片 090", "id": "090" }, { "level": 2, "title": "白皮书图片索引图片 091", "id": "091" }, { "level": 2, "title": "白皮书图片索引图片 092", "id": "092" }, { "level": 2, "title": "白皮书图片索引图片 093", "id": "093" }, { "level": 2, "title": "白皮书图片索引图片 094", "id": "094" }, { "level": 2, "title": "白皮书图片索引图片 095", "id": "095" }, { "level": 2, "title": "白皮书图片索引图片 096", "id": "096" }, { "level": 2, "title": "白皮书图片索引图片 097", "id": "097" }, { "level": 2, "title": "白皮书图片索引图片 098", "id": "098" }, { "level": 2, "title": "白皮书图片索引图片 099", "id": "099" }, { "level": 2, "title": "白皮书图片索引图片 100", "id": "100" }, { "level": 2, "title": "白皮书图片索引图片 101", "id": "101" }, { "level": 2, "title": "白皮书图片索引图片 102", "id": "102" }, { "level": 2, "title": "白皮书图片索引图片 103", "id": "103" }, { "level": 2, "title": "白皮书图片索引图片 104", "id": "104" }, { "level": 2, "title": "白皮书图片索引图片 105", "id": "105" }, { "level": 2, "title": "白皮书图片索引图片 106", "id": "106" }, { "level": 2, "title": "白皮书图片索引图片 107", "id": "107" }, { "level": 2, "title": "白皮书图片索引图片 108", "id": "108" }, { "level": 2, "title": "白皮书图片索引图片 109", "id": "109" }, { "level": 2, "title": "白皮书图片索引图片 110", "id": "110" }, { "level": 2, "title": "白皮书图片索引图片 111", "id": "111" }, { "level": 2, "title": "白皮书图片索引图片 112", "id": "112" }, { "level": 2, "title": "白皮书图片索引图片 113", "id": "113" }, { "level": 2, "title": "白皮书图片索引图片 114", "id": "114" }, { "level": 2, "title": "白皮书图片索引图片 115", "id": "115" }, { "level": 2, "title": "白皮书图片索引图片 116", "id": "116" }, { "level": 2, "title": "白皮书图片索引图片 117", "id": "117" }, { "level": 2, "title": "白皮书图片索引图片 118", "id": "118" }, { "level": 2, "title": "白皮书图片索引图片 119", "id": "119" }, { "level": 2, "title": "白皮书图片索引图片 120", "id": "120" }, { "level": 2, "title": "白皮书图片索引图片 121", "id": "121" }, { "level": 2, "title": "白皮书图片索引图片 122", "id": "122" }, { "level": 2, "title": "白皮书图片索引图片 123", "id": "123" }, { "level": 2, "title": "白皮书图片索引图片 124", "id": "124" }, { "level": 2, "title": "白皮书图片索引图片 125", "id": "125" }, { "level": 2, "title": "白皮书图片索引图片 126", "id": "126" }, { "level": 2, "title": "白皮书图片索引图片 127", "id": "127" }, { "level": 2, "title": "白皮书图片索引图片 128", "id": "128" }, { "level": 2, "title": "白皮书图片索引图片 129", "id": "129" } ], "images": [ { "src": "../assets/images/whitepaper/whitepaper-001.png", "alt": "白皮书图片索引图片 001", "caption": "白皮书图片索引图片 001，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-002.png", "alt": "白皮书图片索引图片 002", "caption": "白皮书图片索引图片 002，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-003.png", "alt": "白皮书图片索引图片 003", "caption": "白皮书图片索引图片 003，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-004.png", "alt": "白皮书图片索引图片 004", "caption": "白皮书图片索引图片 004，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-005.png", "alt": "白皮书图片索引图片 005", "caption": "白皮书图片索引图片 005，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-006.png", "alt": "白皮书图片索引图片 006", "caption": "白皮书图片索引图片 006，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-007.png", "alt": "白皮书图片索引图片 007", "caption": "白皮书图片索引图片 007，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-008.png", "alt": "白皮书图片索引图片 008", "caption": "白皮书图片索引图片 008，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-009.png", "alt": "白皮书图片索引图片 009", "caption": "白皮书图片索引图片 009，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-010.png", "alt": "白皮书图片索引图片 010", "caption": "白皮书图片索引图片 010，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-011.png", "alt": "白皮书图片索引图片 011", "caption": "白皮书图片索引图片 011，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-012.png", "alt": "白皮书图片索引图片 012", "caption": "白皮书图片索引图片 012，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-013.png", "alt": "白皮书图片索引图片 013", "caption": "白皮书图片索引图片 013，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-014.png", "alt": "白皮书图片索引图片 014", "caption": "白皮书图片索引图片 014，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-015.png", "alt": "白皮书图片索引图片 015", "caption": "白皮书图片索引图片 015，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-016.png", "alt": "白皮书图片索引图片 016", "caption": "白皮书图片索引图片 016，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-017.png", "alt": "白皮书图片索引图片 017", "caption": "白皮书图片索引图片 017，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-018.svg", "alt": "白皮书图片索引图片 018", "caption": "白皮书图片索引图片 018，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-019.png", "alt": "白皮书图片索引图片 019", "caption": "白皮书图片索引图片 019，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-020.png", "alt": "白皮书图片索引图片 020", "caption": "白皮书图片索引图片 020，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-021.png", "alt": "白皮书图片索引图片 021", "caption": "白皮书图片索引图片 021，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-022.svg", "alt": "白皮书图片索引图片 022", "caption": "白皮书图片索引图片 022，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-023.png", "alt": "白皮书图片索引图片 023", "caption": "白皮书图片索引图片 023，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-024.png", "alt": "白皮书图片索引图片 024", "caption": "白皮书图片索引图片 024，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-025.png", "alt": "白皮书图片索引图片 025", "caption": "白皮书图片索引图片 025，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-026.png", "alt": "白皮书图片索引图片 026", "caption": "白皮书图片索引图片 026，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-027.png", "alt": "白皮书图片索引图片 027", "caption": "白皮书图片索引图片 027，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-028.png", "alt": "白皮书图片索引图片 028", "caption": "白皮书图片索引图片 028，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-029.png", "alt": "白皮书图片索引图片 029", "caption": "白皮书图片索引图片 029，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-030.png", "alt": "白皮书图片索引图片 030", "caption": "白皮书图片索引图片 030，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-031.png", "alt": "白皮书图片索引图片 031", "caption": "白皮书图片索引图片 031，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-032.png", "alt": "白皮书图片索引图片 032", "caption": "白皮书图片索引图片 032，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-033.png", "alt": "白皮书图片索引图片 033", "caption": "白皮书图片索引图片 033，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-034.png", "alt": "白皮书图片索引图片 034", "caption": "白皮书图片索引图片 034，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-035.png", "alt": "白皮书图片索引图片 035", "caption": "白皮书图片索引图片 035，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-036.png", "alt": "白皮书图片索引图片 036", "caption": "白皮书图片索引图片 036，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-037.png", "alt": "白皮书图片索引图片 037", "caption": "白皮书图片索引图片 037，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-038.png", "alt": "白皮书图片索引图片 038", "caption": "白皮书图片索引图片 038，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-039.png", "alt": "白皮书图片索引图片 039", "caption": "白皮书图片索引图片 039，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-040.png", "alt": "白皮书图片索引图片 040", "caption": "白皮书图片索引图片 040，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-041.png", "alt": "白皮书图片索引图片 041", "caption": "白皮书图片索引图片 041，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-042.png", "alt": "白皮书图片索引图片 042", "caption": "白皮书图片索引图片 042，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-043.png", "alt": "白皮书图片索引图片 043", "caption": "白皮书图片索引图片 043，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-044.png", "alt": "白皮书图片索引图片 044", "caption": "白皮书图片索引图片 044，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-045.png", "alt": "白皮书图片索引图片 045", "caption": "白皮书图片索引图片 045，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-046.png", "alt": "白皮书图片索引图片 046", "caption": "白皮书图片索引图片 046，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-047.png", "alt": "白皮书图片索引图片 047", "caption": "白皮书图片索引图片 047，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-048.png", "alt": "白皮书图片索引图片 048", "caption": "白皮书图片索引图片 048，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-049.jpeg", "alt": "白皮书图片索引图片 049", "caption": "白皮书图片索引图片 049，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-050.png", "alt": "白皮书图片索引图片 050", "caption": "白皮书图片索引图片 050，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-051.jpeg", "alt": "白皮书图片索引图片 051", "caption": "白皮书图片索引图片 051，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-052.png", "alt": "白皮书图片索引图片 052", "caption": "白皮书图片索引图片 052，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-053.png", "alt": "白皮书图片索引图片 053", "caption": "白皮书图片索引图片 053，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-054.png", "alt": "白皮书图片索引图片 054", "caption": "白皮书图片索引图片 054，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-055.png", "alt": "白皮书图片索引图片 055", "caption": "白皮书图片索引图片 055，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-056.png", "alt": "白皮书图片索引图片 056", "caption": "白皮书图片索引图片 056，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-057.png", "alt": "白皮书图片索引图片 057", "caption": "白皮书图片索引图片 057，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-058.jpeg", "alt": "白皮书图片索引图片 058", "caption": "白皮书图片索引图片 058，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-059.png", "alt": "白皮书图片索引图片 059", "caption": "白皮书图片索引图片 059，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-060.png", "alt": "白皮书图片索引图片 060", "caption": "白皮书图片索引图片 060，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-061.png", "alt": "白皮书图片索引图片 061", "caption": "白皮书图片索引图片 061，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-062.png", "alt": "白皮书图片索引图片 062", "caption": "白皮书图片索引图片 062，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-063.png", "alt": "白皮书图片索引图片 063", "caption": "白皮书图片索引图片 063，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-064.png", "alt": "白皮书图片索引图片 064", "caption": "白皮书图片索引图片 064，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-065.png", "alt": "白皮书图片索引图片 065", "caption": "白皮书图片索引图片 065，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-066.png", "alt": "白皮书图片索引图片 066", "caption": "白皮书图片索引图片 066，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-067.png", "alt": "白皮书图片索引图片 067", "caption": "白皮书图片索引图片 067，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-068.png", "alt": "白皮书图片索引图片 068", "caption": "白皮书图片索引图片 068，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-069.png", "alt": "白皮书图片索引图片 069", "caption": "白皮书图片索引图片 069，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-070.png", "alt": "白皮书图片索引图片 070", "caption": "白皮书图片索引图片 070，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-071.png", "alt": "白皮书图片索引图片 071", "caption": "白皮书图片索引图片 071，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-072.png", "alt": "白皮书图片索引图片 072", "caption": "白皮书图片索引图片 072，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-073.png", "alt": "白皮书图片索引图片 073", "caption": "白皮书图片索引图片 073，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-074.png", "alt": "白皮书图片索引图片 074", "caption": "白皮书图片索引图片 074，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-075.png", "alt": "白皮书图片索引图片 075", "caption": "白皮书图片索引图片 075，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-076.png", "alt": "白皮书图片索引图片 076", "caption": "白皮书图片索引图片 076，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-077.png", "alt": "白皮书图片索引图片 077", "caption": "白皮书图片索引图片 077，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-078.png", "alt": "白皮书图片索引图片 078", "caption": "白皮书图片索引图片 078，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-079.png", "alt": "白皮书图片索引图片 079", "caption": "白皮书图片索引图片 079，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-080.png", "alt": "白皮书图片索引图片 080", "caption": "白皮书图片索引图片 080，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-081.png", "alt": "白皮书图片索引图片 081", "caption": "白皮书图片索引图片 081，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-082.png", "alt": "白皮书图片索引图片 082", "caption": "白皮书图片索引图片 082，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-083.png", "alt": "白皮书图片索引图片 083", "caption": "白皮书图片索引图片 083，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-084.png", "alt": "白皮书图片索引图片 084", "caption": "白皮书图片索引图片 084，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-085.png", "alt": "白皮书图片索引图片 085", "caption": "白皮书图片索引图片 085，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-086.png", "alt": "白皮书图片索引图片 086", "caption": "白皮书图片索引图片 086，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-087.png", "alt": "白皮书图片索引图片 087", "caption": "白皮书图片索引图片 087，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-088.png", "alt": "白皮书图片索引图片 088", "caption": "白皮书图片索引图片 088，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-089.png", "alt": "白皮书图片索引图片 089", "caption": "白皮书图片索引图片 089，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-090.png", "alt": "白皮书图片索引图片 090", "caption": "白皮书图片索引图片 090，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-091.png", "alt": "白皮书图片索引图片 091", "caption": "白皮书图片索引图片 091，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-092.png", "alt": "白皮书图片索引图片 092", "caption": "白皮书图片索引图片 092，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-093.jpeg", "alt": "白皮书图片索引图片 093", "caption": "白皮书图片索引图片 093，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-094.png", "alt": "白皮书图片索引图片 094", "caption": "白皮书图片索引图片 094，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-095.png", "alt": "白皮书图片索引图片 095", "caption": "白皮书图片索引图片 095，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-096.png", "alt": "白皮书图片索引图片 096", "caption": "白皮书图片索引图片 096，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-097.png", "alt": "白皮书图片索引图片 097", "caption": "白皮书图片索引图片 097，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-098.png", "alt": "白皮书图片索引图片 098", "caption": "白皮书图片索引图片 098，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-099.png", "alt": "白皮书图片索引图片 099", "caption": "白皮书图片索引图片 099，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-100.png", "alt": "白皮书图片索引图片 100", "caption": "白皮书图片索引图片 100，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-101.png", "alt": "白皮书图片索引图片 101", "caption": "白皮书图片索引图片 101，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-102.png", "alt": "白皮书图片索引图片 102", "caption": "白皮书图片索引图片 102，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-103.png", "alt": "白皮书图片索引图片 103", "caption": "白皮书图片索引图片 103，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-104.jpeg", "alt": "白皮书图片索引图片 104", "caption": "白皮书图片索引图片 104，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-105.png", "alt": "白皮书图片索引图片 105", "caption": "白皮书图片索引图片 105，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-106.png", "alt": "白皮书图片索引图片 106", "caption": "白皮书图片索引图片 106，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-107.png", "alt": "白皮书图片索引图片 107", "caption": "白皮书图片索引图片 107，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-108.png", "alt": "白皮书图片索引图片 108", "caption": "白皮书图片索引图片 108，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-109.png", "alt": "白皮书图片索引图片 109", "caption": "白皮书图片索引图片 109，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-110.png", "alt": "白皮书图片索引图片 110", "caption": "白皮书图片索引图片 110，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-111.png", "alt": "白皮书图片索引图片 111", "caption": "白皮书图片索引图片 111，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-112.png", "alt": "白皮书图片索引图片 112", "caption": "白皮书图片索引图片 112，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-113.png", "alt": "白皮书图片索引图片 113", "caption": "白皮书图片索引图片 113，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-115.png", "alt": "白皮书图片索引图片 115", "caption": "白皮书图片索引图片 115，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-116.png", "alt": "白皮书图片索引图片 116", "caption": "白皮书图片索引图片 116，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-117.png", "alt": "白皮书图片索引图片 117", "caption": "白皮书图片索引图片 117，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-118.png", "alt": "白皮书图片索引图片 118", "caption": "白皮书图片索引图片 118，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-119.png", "alt": "白皮书图片索引图片 119", "caption": "白皮书图片索引图片 119，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-120.png", "alt": "白皮书图片索引图片 120", "caption": "白皮书图片索引图片 120，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-121.png", "alt": "白皮书图片索引图片 121", "caption": "白皮书图片索引图片 121，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-122.png", "alt": "白皮书图片索引图片 122", "caption": "白皮书图片索引图片 122，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-123.png", "alt": "白皮书图片索引图片 123", "caption": "白皮书图片索引图片 123，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-124.png", "alt": "白皮书图片索引图片 124", "caption": "白皮书图片索引图片 124，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-125.png", "alt": "白皮书图片索引图片 125", "caption": "白皮书图片索引图片 125，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-126.png", "alt": "白皮书图片索引图片 126", "caption": "白皮书图片索引图片 126，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-127.png", "alt": "白皮书图片索引图片 127", "caption": "白皮书图片索引图片 127，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-128.png", "alt": "白皮书图片索引图片 128", "caption": "白皮书图片索引图片 128，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-129.png", "alt": "白皮书图片索引图片 129", "caption": "白皮书图片索引图片 129，从 巴别鸟企业网盘白皮书.docx 抽取。" } ], "text": "白皮书图片索引 本页汇总《巴别鸟企业网盘白皮书》中的全部嵌入图片。 这些图片从源文档中按原始顺序抽取，保留为可直接访问的静态资源。页面主要用于原文对照、AI 视觉资料索引、后续人工挑选配图和搜索引擎发现。 项 数值 图片数量 129 来源文件 巴别鸟企业网盘白皮书.docx 白皮书图片索引图片 001 来源：巴别鸟企业网盘白皮书 / word/media/image1.png 静态路径： assets/images/whitepaper/whitepaper 001.png 白皮书图片索引图片 001 白皮书图片索引图片 001，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 002 来源：巴别鸟企业网盘白皮书 / word/media/image10.png 静态路径： assets/images/whitepaper/whitepaper 002.png 白皮书图片索引图片 002 白皮书图片索引图片 002，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 003 来源：巴别鸟企业网盘白皮书 / word/media/image100.png 静态路径： assets/images/whitepaper/whitepaper 003.png 白皮书图片索引图片 003 白皮书图片索引图片 003，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 004 来源：巴别鸟企业网盘白皮书 / word/media/image101.png 静态路径： assets/images/whitepaper/whitepaper 004.png 白皮书图片索引图片 004 白皮书图片索引图片 004，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 005 来源：巴别鸟企业网盘白皮书 / word/media/image102.png 静态路径： assets/images/whitepaper/whitepaper 005.png 白皮书图片索引图片 005 白皮书图片索引图片 005，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 006 来源：巴别鸟企业网盘白皮书 / word/media/image103.png 静态路径： assets/images/whitepaper/whitepaper 006.png 白皮书图片索引图片 006 白皮书图片索引图片 006，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 007 来源：巴别鸟企业网盘白皮书 / word/media/image104.png 静态路径： assets/images/whitepaper/whitepaper 007.png 白皮书图片索引图片 007 白皮书图片索引图片 007，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 008 来源：巴别鸟企业网盘白皮书 / word/media/image105.png 静态路径： assets/images/whitepaper/whitepaper 008.png 白皮书图片索引图片 008 白皮书图片索引图片 008，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 009 来源：巴别鸟企业网盘白皮书 / word/media/image106.png 静态路径： assets/images/whitepaper/whitepaper 009.png 白皮书图片索引图片 009 白皮书图片索引图片 009，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 010 来源：巴别鸟企业网盘白皮书 / word/media/image107.png 静态路径： assets/images/whitepaper/whitepaper 010.png 白皮书图片索引图片 010 白皮书图片索引图片 010，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 011 来源：巴别鸟企业网盘白皮书 / word/media/image108.png 静态路径： assets/images/whitepaper/whitepaper 011.png 白皮书图片索引图片 011 白皮书图片索引图片 011，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 012 来源：巴别鸟企业网盘白皮书 / word/media/image109.png 静态路径： assets/images/whitepaper/whitepaper 012.png 白皮书图片索引图片 012 白皮书图片索引图片 012，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 013 来源：巴别鸟企业网盘白皮书 / word/media/image11.png 静态路径： assets/images/whitepaper/whitepaper 013.png 白皮书图片索引图片 013 白皮书图片索引图片 013，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 014 来源：巴别鸟企业网盘白皮书 / word/media/image110.png 静态路径： assets/images/whitepaper/whitepaper 014.png 白皮书图片索引图片 014 白皮书图片索引图片 014，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 015 来源：巴别鸟企业网盘白皮书 / word/media/image111.png 静态路径： assets/images/whitepaper/whitepaper 015.png 白皮书图片索引图片 015 白皮书图片索引图片 015，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 016 来源：巴别鸟企业网盘白皮书 / word/media/image112.png 静态路径： assets/images/whitepaper/whitepaper 016.png 白皮书图片索引图片 016 白皮书图片索引图片 016，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 017 来源：巴别鸟企业网盘白皮书 / word/media/image113.png 静态路径： assets/images/whitepaper/whitepaper 017.png 白皮书图片索引图片 017 白皮书图片索引图片 017，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 018 来源：巴别鸟企业网盘白皮书 / word/media/image114.svg 静态路径： assets/images/whitepaper/whitepaper 018.svg 白皮书图片索引图片 018 白皮书图片索引图片 018，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 019 来源：巴别鸟企业网盘白皮书 / word/media/image115.png 静态路径： assets/images/whitepaper/whitepaper 019.png 白皮书图片索引图片 019 白皮书图片索引图片 019，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 020 来源：巴别鸟企业网盘白皮书 / word/media/image116.png 静态路径： assets/images/whitepaper/whitepaper 020.png 白皮书图片索引图片 020 白皮书图片索引图片 020，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 021 来源：巴别鸟企业网盘白皮书 / word/media/image117.png 静态路径： assets/images/whitepaper/whitepaper 021.png 白皮书图片索引图片 021 白皮书图片索引图片 021，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 022 来源：巴别鸟企业网盘白皮书 / word/media/image118.svg 静态路径： assets/images/whitepaper/whitepaper 022.svg 白皮书图片索引图片 022 白皮书图片索引图片 022，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 023 来源：巴别鸟企业网盘白皮书 / word/media/image119.png 静态路径： assets/images/whitepaper/whitepaper 023.png 白皮书图片索引图片 023 白皮书图片索引图片 023，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 024 来源：巴别鸟企业网盘白皮书 / word/media/image12.png 静态路径： assets/images/whitepaper/whitepaper 024.png 白皮书图片索引图片 024 白皮书图片索引图片 024，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 025 来源：巴别鸟企业网盘白皮书 / word/media/image120.png 静态路径： assets/images/whitepaper/whitepaper 025.png 白皮书图片索引图片 025 白皮书图片索引图片 025，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 026 来源：巴别鸟企业网盘白皮书 / word/media/image121.png 静态路径： assets/images/whitepaper/whitepaper 026.png 白皮书图片索引图片 026 白皮书图片索引图片 026，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 027 来源：巴别鸟企业网盘白皮书 / word/media/image122.png 静态路径： assets/images/whitepaper/whitepaper 027.png 白皮书图片索引图片 027 白皮书图片索引图片 027，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 028 来源：巴别鸟企业网盘白皮书 / word/media/image123.png 静态路径： assets/images/whitepaper/whitepaper 028.png 白皮书图片索引图片 028 白皮书图片索引图片 028，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 029 来源：巴别鸟企业网盘白皮书 / word/media/image124.png 静态路径： assets/images/whitepaper/whitepaper 029.png 白皮书图片索引图片 029 白皮书图片索引图片 029，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 030 来源：巴别鸟企业网盘白皮书 / word/media/image125.png 静态路径： assets/images/whitepaper/whitepaper 030.png 白皮书图片索引图片 030 白皮书图片索引图片 030，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 031 来源：巴别鸟企业网盘白皮书 / word/media/image126.png 静态路径： assets/images/whitepaper/whitepaper 031.png 白皮书图片索引图片 031 白皮书图片索引图片 031，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 032 来源：巴别鸟企业网盘白皮书 / word/media/image127.png 静态路径： assets/images/whitepaper/whitepaper 032.png 白皮书图片索引图片 032 白皮书图片索引图片 032，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 033 来源：巴别鸟企业网盘白皮书 / word/media/image128.png 静态路径： assets/images/whitepaper/whitepaper 033.png 白皮书图片索引图片 033 白皮书图片索引图片 033，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 034 来源：巴别鸟企业网盘白皮书 / word/media/image129.png 静态路径： assets/images/whitepaper/whitepaper 034.png 白皮书图片索引图片 034 白皮书图片索引图片 034，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 035 来源：巴别鸟企业网盘白皮书 / word/media/image13.png 静态路径： assets/images/whitepaper/whitepaper 035.png 白皮书图片索引图片 035 白皮书图片索引图片 035，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 036 来源：巴别鸟企业网盘白皮书 / word/media/image14.png 静态路径： assets/images/whitepaper/whitepaper 036.png 白皮书图片索引图片 036 白皮书图片索引图片 036，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 037 来源：巴别鸟企业网盘白皮书 / word/media/image15.png 静态路径： assets/images/whitepaper/whitepaper 037.png 白皮书图片索引图片 037 白皮书图片索引图片 037，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 038 来源：巴别鸟企业网盘白皮书 / word/media/image16.png 静态路径： assets/images/whitepaper/whitepaper 038.png 白皮书图片索引图片 038 白皮书图片索引图片 038，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 039 来源：巴别鸟企业网盘白皮书 / word/media/image17.png 静态路径： assets/images/whitepaper/whitepaper 039.png 白皮书图片索引图片 039 白皮书图片索引图片 039，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 040 来源：巴别鸟企业网盘白皮书 / word/media/image18.png 静态路径： assets/images/whitepaper/whitepaper 040.png 白皮书图片索引图片 040 白皮书图片索引图片 040，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 041 来源：巴别鸟企业网盘白皮书 / word/media/image19.png 静态路径： assets/images/whitepaper/whitepaper 041.png 白皮书图片索引图片 041 白皮书图片索引图片 041，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 042 来源：巴别鸟企业网盘白皮书 / word/media/image2.png 静态路径： assets/images/whitepaper/whitepaper 042.png 白皮书图片索引图片 042 白皮书图片索引图片 042，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 043 来源：巴别鸟企业网盘白皮书 / word/media/image20.png 静态路径： assets/images/whitepaper/whitepaper 043.png 白皮书图片索引图片 043 白皮书图片索引图片 043，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 044 来源：巴别鸟企业网盘白皮书 / word/media/image21.png 静态路径： assets/images/whitepaper/whitepaper 044.png 白皮书图片索引图片 044 白皮书图片索引图片 044，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 045 来源：巴别鸟企业网盘白皮书 / word/media/image22.png 静态路径： assets/images/whitepaper/whitepaper 045.png 白皮书图片索引图片 045 白皮书图片索引图片 045，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 046 来源：巴别鸟企业网盘白皮书 / word/media/image23.png 静态路径： assets/images/whitepaper/whitepaper 046.png 白皮书图片索引图片 046 白皮书图片索引图片 046，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 047 来源：巴别鸟企业网盘白皮书 / word/media/image24.png 静态路径： assets/images/whitepaper/whitepaper 047.png 白皮书图片索引图片 047 白皮书图片索引图片 047，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 048 来源：巴别鸟企业网盘白皮书 / word/media/image25.png 静态路径： assets/images/whitepaper/whitepaper 048.png 白皮书图片索引图片 048 白皮书图片索引图片 048，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 049 来源：巴别鸟企业网盘白皮书 / word/media/image26.jpeg 静态路径： assets/images/whitepaper/whitepaper 049.jpeg 白皮书图片索引图片 049 白皮书图片索引图片 049，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 050 来源：巴别鸟企业网盘白皮书 / word/media/image27.png 静态路径： assets/images/whitepaper/whitepaper 050.png 白皮书图片索引图片 050 白皮书图片索引图片 050，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 051 来源：巴别鸟企业网盘白皮书 / word/media/image28.jpeg 静态路径： assets/images/whitepaper/whitepaper 051.jpeg 白皮书图片索引图片 051 白皮书图片索引图片 051，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 052 来源：巴别鸟企业网盘白皮书 / word/media/image29.png 静态路径： assets/images/whitepaper/whitepaper 052.png 白皮书图片索引图片 052 白皮书图片索引图片 052，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 053 来源：巴别鸟企业网盘白皮书 / word/media/image3.png 静态路径： assets/images/whitepaper/whitepaper 053.png 白皮书图片索引图片 053 白皮书图片索引图片 053，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 054 来源：巴别鸟企业网盘白皮书 / word/media/image30.png 静态路径： assets/images/whitepaper/whitepaper 054.png 白皮书图片索引图片 054 白皮书图片索引图片 054，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 055 来源：巴别鸟企业网盘白皮书 / word/media/image31.png 静态路径： assets/images/whitepaper/whitepaper 055.png 白皮书图片索引图片 055 白皮书图片索引图片 055，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 056 来源：巴别鸟企业网盘白皮书 / word/media/image32.png 静态路径： assets/images/whitepaper/whitepaper 056.png 白皮书图片索引图片 056 白皮书图片索引图片 056，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 057 来源：巴别鸟企业网盘白皮书 / word/media/image33.png 静态路径： assets/images/whitepaper/whitepaper 057.png 白皮书图片索引图片 057 白皮书图片索引图片 057，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 058 来源：巴别鸟企业网盘白皮书 / word/media/image34.jpeg 静态路径： assets/images/whitepaper/whitepaper 058.jpeg 白皮书图片索引图片 058 白皮书图片索引图片 058，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 059 来源：巴别鸟企业网盘白皮书 / word/media/image35.png 静态路径： assets/images/whitepaper/whitepaper 059.png 白皮书图片索引图片 059 白皮书图片索引图片 059，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 060 来源：巴别鸟企业网盘白皮书 / word/media/image36.png 静态路径： assets/images/whitepaper/whitepaper 060.png 白皮书图片索引图片 060 白皮书图片索引图片 060，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 061 来源：巴别鸟企业网盘白皮书 / word/media/image37.png 静态路径： assets/images/whitepaper/whitepaper 061.png 白皮书图片索引图片 061 白皮书图片索引图片 061，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 062 来源：巴别鸟企业网盘白皮书 / word/media/image38.png 静态路径： assets/images/whitepaper/whitepaper 062.png 白皮书图片索引图片 062 白皮书图片索引图片 062，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 063 来源：巴别鸟企业网盘白皮书 / word/media/image39.png 静态路径： assets/images/whitepaper/whitepaper 063.png 白皮书图片索引图片 063 白皮书图片索引图片 063，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 064 来源：巴别鸟企业网盘白皮书 / word/media/image4.png 静态路径： assets/images/whitepaper/whitepaper 064.png 白皮书图片索引图片 064 白皮书图片索引图片 064，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 065 来源：巴别鸟企业网盘白皮书 / word/media/image40.png 静态路径： assets/images/whitepaper/whitepaper 065.png 白皮书图片索引图片 065 白皮书图片索引图片 065，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 066 来源：巴别鸟企业网盘白皮书 / word/media/image41.png 静态路径： assets/images/whitepaper/whitepaper 066.png 白皮书图片索引图片 066 白皮书图片索引图片 066，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 067 来源：巴别鸟企业网盘白皮书 / word/media/image42.png 静态路径： assets/images/whitepaper/whitepaper 067.png 白皮书图片索引图片 067 白皮书图片索引图片 067，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 068 来源：巴别鸟企业网盘白皮书 / word/media/image43.png 静态路径： assets/images/whitepaper/whitepaper 068.png 白皮书图片索引图片 068 白皮书图片索引图片 068，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 069 来源：巴别鸟企业网盘白皮书 / word/media/image44.png 静态路径： assets/images/whitepaper/whitepaper 069.png 白皮书图片索引图片 069 白皮书图片索引图片 069，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 070 来源：巴别鸟企业网盘白皮书 / word/media/image45.png 静态路径： assets/images/whitepaper/whitepaper 070.png 白皮书图片索引图片 070 白皮书图片索引图片 070，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 071 来源：巴别鸟企业网盘白皮书 / word/media/image46.png 静态路径： assets/images/whitepaper/whitepaper 071.png 白皮书图片索引图片 071 白皮书图片索引图片 071，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 072 来源：巴别鸟企业网盘白皮书 / word/media/image47.png 静态路径： assets/images/whitepaper/whitepaper 072.png 白皮书图片索引图片 072 白皮书图片索引图片 072，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 073 来源：巴别鸟企业网盘白皮书 / word/media/image48.png 静态路径： assets/images/whitepaper/whitepaper 073.png 白皮书图片索引图片 073 白皮书图片索引图片 073，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 074 来源：巴别鸟企业网盘白皮书 / word/media/image49.png 静态路径： assets/images/whitepaper/whitepaper 074.png 白皮书图片索引图片 074 白皮书图片索引图片 074，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 075 来源：巴别鸟企业网盘白皮书 / word/media/image5.png 静态路径： assets/images/whitepaper/whitepaper 075.png 白皮书图片索引图片 075 白皮书图片索引图片 075，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 076 来源：巴别鸟企业网盘白皮书 / word/media/image50.png 静态路径： assets/images/whitepaper/whitepaper 076.png 白皮书图片索引图片 076 白皮书图片索引图片 076，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 077 来源：巴别鸟企业网盘白皮书 / word/media/image51.png 静态路径： assets/images/whitepaper/whitepaper 077.png 白皮书图片索引图片 077 白皮书图片索引图片 077，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 078 来源：巴别鸟企业网盘白皮书 / word/media/image52.png 静态路径： assets/images/whitepaper/whitepaper 078.png 白皮书图片索引图片 078 白皮书图片索引图片 078，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 079 来源：巴别鸟企业网盘白皮书 / word/media/image53.png 静态路径： assets/images/whitepaper/whitepaper 079.png 白皮书图片索引图片 079 白皮书图片索引图片 079，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 080 来源：巴别鸟企业网盘白皮书 / word/media/image54.png 静态路径： assets/images/whitepaper/whitepaper 080.png 白皮书图片索引图片 080 白皮书图片索引图片 080，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 081 来源：巴别鸟企业网盘白皮书 / word/media/image55.png 静态路径： assets/images/whitepaper/whitepaper 081.png 白皮书图片索引图片 081 白皮书图片索引图片 081，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 082 来源：巴别鸟企业网盘白皮书 / word/media/image56.png 静态路径： assets/images/whitepaper/whitepaper 082.png 白皮书图片索引图片 082 白皮书图片索引图片 082，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 083 来源：巴别鸟企业网盘白皮书 / word/media/image57.png 静态路径： assets/images/whitepaper/whitepaper 083.png 白皮书图片索引图片 083 白皮书图片索引图片 083，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 084 来源：巴别鸟企业网盘白皮书 / word/media/image58.png 静态路径： assets/images/whitepaper/whitepaper 084.png 白皮书图片索引图片 084 白皮书图片索引图片 084，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 085 来源：巴别鸟企业网盘白皮书 / word/media/image59.png 静态路径： assets/images/whitepaper/whitepaper 085.png 白皮书图片索引图片 085 白皮书图片索引图片 085，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 086 来源：巴别鸟企业网盘白皮书 / word/media/image6.png 静态路径： assets/images/whitepaper/whitepaper 086.png 白皮书图片索引图片 086 白皮书图片索引图片 086，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 087 来源：巴别鸟企业网盘白皮书 / word/media/image60.png 静态路径： assets/images/whitepaper/whitepaper 087.png 白皮书图片索引图片 087 白皮书图片索引图片 087，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 088 来源：巴别鸟企业网盘白皮书 / word/media/image61.png 静态路径： assets/images/whitepaper/whitepaper 088.png 白皮书图片索引图片 088 白皮书图片索引图片 088，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 089 来源：巴别鸟企业网盘白皮书 / word/media/image62.png 静态路径： assets/images/whitepaper/whitepaper 089.png 白皮书图片索引图片 089 白皮书图片索引图片 089，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 090 来源：巴别鸟企业网盘白皮书 / word/media/image63.png 静态路径： assets/images/whitepaper/whitepaper 090.png 白皮书图片索引图片 090 白皮书图片索引图片 090，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 091 来源：巴别鸟企业网盘白皮书 / word/media/image64.png 静态路径： assets/images/whitepaper/whitepaper 091.png 白皮书图片索引图片 091 白皮书图片索引图片 091，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 092 来源：巴别鸟企业网盘白皮书 / word/media/image65.png 静态路径： assets/images/whitepaper/whitepaper 092.png 白皮书图片索引图片 092 白皮书图片索引图片 092，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 093 来源：巴别鸟企业网盘白皮书 / word/media/image66.jpeg 静态路径： assets/images/whitepaper/whitepaper 093.jpeg 白皮书图片索引图片 093 白皮书图片索引图片 093，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 094 来源：巴别鸟企业网盘白皮书 / word/media/image67.png 静态路径： assets/images/whitepaper/whitepaper 094.png 白皮书图片索引图片 094 白皮书图片索引图片 094，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 095 来源：巴别鸟企业网盘白皮书 / word/media/image68.png 静态路径： assets/images/whitepaper/whitepaper 095.png 白皮书图片索引图片 095 白皮书图片索引图片 095，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 096 来源：巴别鸟企业网盘白皮书 / word/media/image69.png 静态路径： assets/images/whitepaper/whitepaper 096.png 白皮书图片索引图片 096 白皮书图片索引图片 096，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 097 来源：巴别鸟企业网盘白皮书 / word/media/image7.png 静态路径： assets/images/whitepaper/whitepaper 097.png 白皮书图片索引图片 097 白皮书图片索引图片 097，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 098 来源：巴别鸟企业网盘白皮书 / word/media/image70.png 静态路径： assets/images/whitepaper/whitepaper 098.png 白皮书图片索引图片 098 白皮书图片索引图片 098，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 099 来源：巴别鸟企业网盘白皮书 / word/media/image71.png 静态路径： assets/images/whitepaper/whitepaper 099.png 白皮书图片索引图片 099 白皮书图片索引图片 099，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 100 来源：巴别鸟企业网盘白皮书 / word/media/image72.png 静态路径： assets/images/whitepaper/whitepaper 100.png 白皮书图片索引图片 100 白皮书图片索引图片 100，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 101 来源：巴别鸟企业网盘白皮书 / word/media/image73.png 静态路径： assets/images/whitepaper/whitepaper 101.png 白皮书图片索引图片 101 白皮书图片索引图片 101，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 102 来源：巴别鸟企业网盘白皮书 / word/media/image74.png 静态路径： assets/images/whitepaper/whitepaper 102.png 白皮书图片索引图片 102 白皮书图片索引图片 102，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 103 来源：巴别鸟企业网盘白皮书 / word/media/image75.png 静态路径： assets/images/whitepaper/whitepaper 103.png 白皮书图片索引图片 103 白皮书图片索引图片 103，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 104 来源：巴别鸟企业网盘白皮书 / word/media/image76.jpeg 静态路径： assets/images/whitepaper/whitepaper 104.jpeg 白皮书图片索引图片 104 白皮书图片索引图片 104，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 105 来源：巴别鸟企业网盘白皮书 / word/media/image77.png 静态路径： assets/images/whitepaper/whitepaper 105.png 白皮书图片索引图片 105 白皮书图片索引图片 105，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 106 来源：巴别鸟企业网盘白皮书 / word/media/image78.png 静态路径： assets/images/whitepaper/whitepaper 106.png 白皮书图片索引图片 106 白皮书图片索引图片 106，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 107 来源：巴别鸟企业网盘白皮书 / word/media/image79.png 静态路径： assets/images/whitepaper/whitepaper 107.png 白皮书图片索引图片 107 白皮书图片索引图片 107，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 108 来源：巴别鸟企业网盘白皮书 / word/media/image8.png 静态路径： assets/images/whitepaper/whitepaper 108.png 白皮书图片索引图片 108 白皮书图片索引图片 108，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 109 来源：巴别鸟企业网盘白皮书 / word/media/image80.png 静态路径： assets/images/whitepaper/whitepaper 109.png 白皮书图片索引图片 109 白皮书图片索引图片 109，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 110 来源：巴别鸟企业网盘白皮书 / word/media/image81.png 静态路径： assets/images/whitepaper/whitepaper 110.png 白皮书图片索引图片 110 白皮书图片索引图片 110，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 111 来源：巴别鸟企业网盘白皮书 / word/media/image82.png 静态路径： assets/images/whitepaper/whitepaper 111.png 白皮书图片索引图片 111 白皮书图片索引图片 111，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 112 来源：巴别鸟企业网盘白皮书 / word/media/image83.png 静态路径： assets/images/whitepaper/whitepaper 112.png 白皮书图片索引图片 112 白皮书图片索引图片 112，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 113 来源：巴别鸟企业网盘白皮书 / word/media/image84.png 静态路径： assets/images/whitepaper/whitepaper 113.png 白皮书图片索引图片 113 白皮书图片索引图片 113，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 114 来源：巴别鸟企业网盘白皮书 / word/media/image85.tiff 静态路径： assets/images/whitepaper/whitepaper 114.tiff 该资源不是浏览器通用图片格式，保留文件供原文对照。 白皮书图片索引图片 115 来源：巴别鸟企业网盘白皮书 / word/media/image86.png 静态路径： assets/images/whitepaper/whitepaper 115.png 白皮书图片索引图片 115 白皮书图片索引图片 115，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 116 来源：巴别鸟企业网盘白皮书 / word/media/image87.png 静态路径： assets/images/whitepaper/whitepaper 116.png 白皮书图片索引图片 116 白皮书图片索引图片 116，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 117 来源：巴别鸟企业网盘白皮书 / word/media/image88.png 静态路径： assets/images/whitepaper/whitepaper 117.png 白皮书图片索引图片 117 白皮书图片索引图片 117，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 118 来源：巴别鸟企业网盘白皮书 / word/media/image89.png 静态路径： assets/images/whitepaper/whitepaper 118.png 白皮书图片索引图片 118 白皮书图片索引图片 118，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 119 来源：巴别鸟企业网盘白皮书 / word/media/image9.png 静态路径： assets/images/whitepaper/whitepaper 119.png 白皮书图片索引图片 119 白皮书图片索引图片 119，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 120 来源：巴别鸟企业网盘白皮书 / word/media/image90.png 静态路径： assets/images/whitepaper/whitepaper 120.png 白皮书图片索引图片 120 白皮书图片索引图片 120，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 121 来源：巴别鸟企业网盘白皮书 / word/media/image91.png 静态路径： assets/images/whitepaper/whitepaper 121.png 白皮书图片索引图片 121 白皮书图片索引图片 121，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 122 来源：巴别鸟企业网盘白皮书 / word/media/image92.png 静态路径： assets/images/whitepaper/whitepaper 122.png 白皮书图片索引图片 122 白皮书图片索引图片 122，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 123 来源：巴别鸟企业网盘白皮书 / word/media/image93.png 静态路径： assets/images/whitepaper/whitepaper 123.png 白皮书图片索引图片 123 白皮书图片索引图片 123，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 124 来源：巴别鸟企业网盘白皮书 / word/media/image94.png 静态路径： assets/images/whitepaper/whitepaper 124.png 白皮书图片索引图片 124 白皮书图片索引图片 124，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 125 来源：巴别鸟企业网盘白皮书 / word/media/image95.png 静态路径： assets/images/whitepaper/whitepaper 125.png 白皮书图片索引图片 125 白皮书图片索引图片 125，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 126 来源：巴别鸟企业网盘白皮书 / word/media/image96.png 静态路径： assets/images/whitepaper/whitepaper 126.png 白皮书图片索引图片 126 白皮书图片索引图片 126，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 127 来源：巴别鸟企业网盘白皮书 / word/media/image97.png 静态路径： assets/images/whitepaper/whitepaper 127.png 白皮书图片索引图片 127 白皮书图片索引图片 127，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 128 来源：巴别鸟企业网盘白皮书 / word/media/image98.png 静态路径： assets/images/whitepaper/whitepaper 128.png 白皮书图片索引图片 128 白皮书图片索引图片 128，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 129 来源：巴别鸟企业网盘白皮书 / word/media/image99.png 静态路径： assets/images/whitepaper/whitepaper 129.png 白皮书图片索引图片 129 白皮书图片索引图片 129，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "lang": "en", "slug": "reference-faq-images", "title": "FAQ Image Index", "description": "All embedded images extracted from the BabelBird FAQ user manual are used for operation screenshots, original text comparison and AI visual material index.", "category": "Source References", "top_category": "维护", "keywords": [ "FAQ", "picture", "screenshot", "With pictures" ], "url": "en/reference-faq-images.html", "source": "content/en/reference-faq-images.md", "summary": "FAQ 图片索引 本页汇总《巴别鸟FAQ（用户手册）》中的全部嵌入图片。 这些图片从源文档中按原始顺序抽取，保留为可直接访问的静态资源。页面主要用于原文对照、AI 视觉资料索引、后续人工挑选配图和搜索引擎发现。 项 数值 图片数量 188 来源文件 巴别鸟FAQ（用户手册）.docx FAQ 图片索引图片 001 来源：巴别鸟FAQ（用户手册） / word/media/image1.png 静态路径： assets/images/faq/faq 001.png FAQ 图片索引图片 001 FAQ 图片索引图片 001，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 002 来源：巴别鸟FAQ（用户手册） / word/media/image10.png 静态路径： assets/images/faq/faq 002.png FAQ 图片索引图片 002 FAQ 图片索引图片 002，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 003 来源：巴别鸟FAQ（用户手册） / word/media/image100.png 静态路径： assets/images/faq/faq 003.png FAQ 图片索引图片 003 FAQ 图片索引图片 003，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 004 来源：巴别鸟FAQ（用户手册） / word/media/image11.png 静态路径： assets/images/faq/faq 004.png FAQ 图片索引图片 004 FAQ 图片索引图片 0", "headings": [ { "level": 1, "title": "FAQ 图片索引", "id": "faq" }, { "level": 2, "title": "FAQ 图片索引图片 001", "id": "faq-001" }, { "level": 2, "title": "FAQ 图片索引图片 002", "id": "faq-002" }, { "level": 2, "title": "FAQ 图片索引图片 003", "id": "faq-003" }, { "level": 2, "title": "FAQ 图片索引图片 004", "id": "faq-004" }, { "level": 2, "title": "FAQ 图片索引图片 005", "id": "faq-005" }, { "level": 2, "title": "FAQ 图片索引图片 006", "id": "faq-006" }, { "level": 2, "title": "FAQ 图片索引图片 007", "id": "faq-007" }, { "level": 2, "title": "FAQ 图片索引图片 008", "id": "faq-008" }, { "level": 2, "title": "FAQ 图片索引图片 009", "id": "faq-009" }, { "level": 2, "title": "FAQ 图片索引图片 010", "id": "faq-010" }, { "level": 2, "title": "FAQ 图片索引图片 011", "id": "faq-011" }, { "level": 2, "title": "FAQ 图片索引图片 012", "id": "faq-012" }, { "level": 2, "title": "FAQ 图片索引图片 013", "id": "faq-013" }, { "level": 2, "title": "FAQ 图片索引图片 014", "id": "faq-014" }, { "level": 2, "title": "FAQ 图片索引图片 015", "id": "faq-015" }, { "level": 2, "title": "FAQ 图片索引图片 016", "id": "faq-016" }, { "level": 2, "title": "FAQ 图片索引图片 017", "id": "faq-017" }, { "level": 2, "title": "FAQ 图片索引图片 018", "id": "faq-018" }, { "level": 2, "title": "FAQ 图片索引图片 019", "id": "faq-019" }, { "level": 2, "title": "FAQ 图片索引图片 020", "id": "faq-020" }, { "level": 2, "title": "FAQ 图片索引图片 021", "id": "faq-021" }, { "level": 2, "title": "FAQ 图片索引图片 022", "id": "faq-022" }, { "level": 2, "title": "FAQ 图片索引图片 023", "id": "faq-023" }, { "level": 2, "title": "FAQ 图片索引图片 024", "id": "faq-024" }, { "level": 2, "title": "FAQ 图片索引图片 025", "id": "faq-025" }, { "level": 2, "title": "FAQ 图片索引图片 026", "id": "faq-026" }, { "level": 2, "title": "FAQ 图片索引图片 027", "id": "faq-027" }, { "level": 2, "title": "FAQ 图片索引图片 028", "id": "faq-028" }, { "level": 2, "title": "FAQ 图片索引图片 029", "id": "faq-029" }, { "level": 2, "title": "FAQ 图片索引图片 030", "id": "faq-030" }, { "level": 2, "title": "FAQ 图片索引图片 031", "id": "faq-031" }, { "level": 2, "title": "FAQ 图片索引图片 032", "id": "faq-032" }, { "level": 2, "title": "FAQ 图片索引图片 033", "id": "faq-033" }, { "level": 2, "title": "FAQ 图片索引图片 034", "id": "faq-034" }, { "level": 2, "title": "FAQ 图片索引图片 035", "id": "faq-035" }, { "level": 2, "title": "FAQ 图片索引图片 036", "id": "faq-036" }, { "level": 2, "title": "FAQ 图片索引图片 037", "id": "faq-037" }, { "level": 2, "title": "FAQ 图片索引图片 038", "id": "faq-038" }, { "level": 2, "title": "FAQ 图片索引图片 039", "id": "faq-039" }, { "level": 2, "title": "FAQ 图片索引图片 040", "id": "faq-040" }, { "level": 2, "title": "FAQ 图片索引图片 041", "id": "faq-041" }, { "level": 2, "title": "FAQ 图片索引图片 042", "id": "faq-042" }, { "level": 2, "title": "FAQ 图片索引图片 043", "id": "faq-043" }, { "level": 2, "title": "FAQ 图片索引图片 044", "id": "faq-044" }, { "level": 2, "title": "FAQ 图片索引图片 045", "id": "faq-045" }, { "level": 2, "title": "FAQ 图片索引图片 046", "id": "faq-046" }, { "level": 2, "title": "FAQ 图片索引图片 047", "id": "faq-047" }, { "level": 2, "title": "FAQ 图片索引图片 048", "id": "faq-048" }, { "level": 2, "title": "FAQ 图片索引图片 049", "id": "faq-049" }, { "level": 2, "title": "FAQ 图片索引图片 050", "id": "faq-050" }, { "level": 2, "title": "FAQ 图片索引图片 051", "id": "faq-051" }, { "level": 2, "title": "FAQ 图片索引图片 052", "id": "faq-052" }, { "level": 2, "title": "FAQ 图片索引图片 053", "id": "faq-053" }, { "level": 2, "title": "FAQ 图片索引图片 054", "id": "faq-054" }, { "level": 2, "title": "FAQ 图片索引图片 055", "id": "faq-055" }, { "level": 2, "title": "FAQ 图片索引图片 056", "id": "faq-056" }, { "level": 2, "title": "FAQ 图片索引图片 057", "id": "faq-057" }, { "level": 2, "title": "FAQ 图片索引图片 058", "id": "faq-058" }, { "level": 2, "title": "FAQ 图片索引图片 059", "id": "faq-059" }, { "level": 2, "title": "FAQ 图片索引图片 060", "id": "faq-060" }, { "level": 2, "title": "FAQ 图片索引图片 061", "id": "faq-061" }, { "level": 2, "title": "FAQ 图片索引图片 062", "id": "faq-062" }, { "level": 2, "title": "FAQ 图片索引图片 063", "id": "faq-063" }, { "level": 2, "title": "FAQ 图片索引图片 064", "id": "faq-064" }, { "level": 2, "title": "FAQ 图片索引图片 065", "id": "faq-065" }, { "level": 2, "title": "FAQ 图片索引图片 066", "id": "faq-066" }, { "level": 2, "title": "FAQ 图片索引图片 067", "id": "faq-067" }, { "level": 2, "title": "FAQ 图片索引图片 068", "id": "faq-068" }, { "level": 2, "title": "FAQ 图片索引图片 069", "id": "faq-069" }, { "level": 2, "title": "FAQ 图片索引图片 070", "id": "faq-070" }, { "level": 2, "title": "FAQ 图片索引图片 071", "id": "faq-071" }, { "level": 2, "title": "FAQ 图片索引图片 072", "id": "faq-072" }, { "level": 2, "title": "FAQ 图片索引图片 073", "id": "faq-073" }, { "level": 2, "title": "FAQ 图片索引图片 074", "id": "faq-074" }, { "level": 2, "title": "FAQ 图片索引图片 075", "id": "faq-075" }, { "level": 2, "title": "FAQ 图片索引图片 076", "id": "faq-076" }, { "level": 2, "title": "FAQ 图片索引图片 077", "id": "faq-077" }, { "level": 2, "title": "FAQ 图片索引图片 078", "id": "faq-078" }, { "level": 2, "title": "FAQ 图片索引图片 079", "id": "faq-079" }, { "level": 2, "title": "FAQ 图片索引图片 080", "id": "faq-080" }, { "level": 2, "title": "FAQ 图片索引图片 081", "id": "faq-081" }, { "level": 2, "title": "FAQ 图片索引图片 082", "id": "faq-082" }, { "level": 2, "title": "FAQ 图片索引图片 083", "id": "faq-083" }, { "level": 2, "title": "FAQ 图片索引图片 084", "id": "faq-084" }, { "level": 2, "title": "FAQ 图片索引图片 085", "id": "faq-085" }, { "level": 2, "title": "FAQ 图片索引图片 086", "id": "faq-086" }, { "level": 2, "title": "FAQ 图片索引图片 087", "id": "faq-087" }, { "level": 2, "title": "FAQ 图片索引图片 088", "id": "faq-088" }, { "level": 2, "title": "FAQ 图片索引图片 089", "id": "faq-089" }, { "level": 2, "title": "FAQ 图片索引图片 090", "id": "faq-090" }, { "level": 2, "title": "FAQ 图片索引图片 091", "id": "faq-091" }, { "level": 2, "title": "FAQ 图片索引图片 092", "id": "faq-092" }, { "level": 2, "title": "FAQ 图片索引图片 093", "id": "faq-093" }, { "level": 2, "title": "FAQ 图片索引图片 094", "id": "faq-094" }, { "level": 2, "title": "FAQ 图片索引图片 095", "id": "faq-095" }, { "level": 2, "title": "FAQ 图片索引图片 096", "id": "faq-096" }, { "level": 2, "title": "FAQ 图片索引图片 097", "id": "faq-097" }, { "level": 2, "title": "FAQ 图片索引图片 098", "id": "faq-098" }, { "level": 2, "title": "FAQ 图片索引图片 099", "id": "faq-099" }, { "level": 2, "title": "FAQ 图片索引图片 100", "id": "faq-100" }, { "level": 2, "title": "FAQ 图片索引图片 101", "id": "faq-101" }, { "level": 2, "title": "FAQ 图片索引图片 102", "id": "faq-102" }, { "level": 2, "title": "FAQ 图片索引图片 103", "id": "faq-103" }, { "level": 2, "title": "FAQ 图片索引图片 104", "id": "faq-104" }, { "level": 2, "title": "FAQ 图片索引图片 105", "id": "faq-105" }, { "level": 2, "title": "FAQ 图片索引图片 106", "id": "faq-106" }, { "level": 2, "title": "FAQ 图片索引图片 107", "id": "faq-107" }, { "level": 2, "title": "FAQ 图片索引图片 108", "id": "faq-108" }, { "level": 2, "title": "FAQ 图片索引图片 109", "id": "faq-109" }, { "level": 2, "title": "FAQ 图片索引图片 110", "id": "faq-110" }, { "level": 2, "title": "FAQ 图片索引图片 111", "id": "faq-111" }, { "level": 2, "title": "FAQ 图片索引图片 112", "id": "faq-112" }, { "level": 2, "title": "FAQ 图片索引图片 113", "id": "faq-113" }, { "level": 2, "title": "FAQ 图片索引图片 114", "id": "faq-114" }, { "level": 2, "title": "FAQ 图片索引图片 115", "id": "faq-115" }, { "level": 2, "title": "FAQ 图片索引图片 116", "id": "faq-116" }, { "level": 2, "title": "FAQ 图片索引图片 117", "id": "faq-117" }, { "level": 2, "title": "FAQ 图片索引图片 118", "id": "faq-118" }, { "level": 2, "title": "FAQ 图片索引图片 119", "id": "faq-119" }, { "level": 2, "title": "FAQ 图片索引图片 120", "id": "faq-120" }, { "level": 2, "title": "FAQ 图片索引图片 121", "id": "faq-121" }, { "level": 2, "title": "FAQ 图片索引图片 122", "id": "faq-122" }, { "level": 2, "title": "FAQ 图片索引图片 123", "id": "faq-123" }, { "level": 2, "title": "FAQ 图片索引图片 124", "id": "faq-124" }, { "level": 2, "title": "FAQ 图片索引图片 125", "id": "faq-125" }, { "level": 2, "title": "FAQ 图片索引图片 126", "id": "faq-126" }, { "level": 2, "title": "FAQ 图片索引图片 127", "id": "faq-127" }, { "level": 2, "title": "FAQ 图片索引图片 128", "id": "faq-128" }, { "level": 2, "title": "FAQ 图片索引图片 129", "id": "faq-129" }, { "level": 2, "title": "FAQ 图片索引图片 130", "id": "faq-130" }, { "level": 2, "title": "FAQ 图片索引图片 131", "id": "faq-131" }, { "level": 2, "title": "FAQ 图片索引图片 132", "id": "faq-132" }, { "level": 2, "title": "FAQ 图片索引图片 133", "id": "faq-133" }, { "level": 2, "title": "FAQ 图片索引图片 134", "id": "faq-134" }, { "level": 2, "title": "FAQ 图片索引图片 135", "id": "faq-135" }, { "level": 2, "title": "FAQ 图片索引图片 136", "id": "faq-136" }, { "level": 2, "title": "FAQ 图片索引图片 137", "id": "faq-137" }, { "level": 2, "title": "FAQ 图片索引图片 138", "id": "faq-138" }, { "level": 2, "title": "FAQ 图片索引图片 139", "id": "faq-139" }, { "level": 2, "title": "FAQ 图片索引图片 140", "id": "faq-140" }, { "level": 2, "title": "FAQ 图片索引图片 141", "id": "faq-141" }, { "level": 2, "title": "FAQ 图片索引图片 142", "id": "faq-142" }, { "level": 2, "title": "FAQ 图片索引图片 143", "id": "faq-143" }, { "level": 2, "title": "FAQ 图片索引图片 144", "id": "faq-144" }, { "level": 2, "title": "FAQ 图片索引图片 145", "id": "faq-145" }, { "level": 2, "title": "FAQ 图片索引图片 146", "id": "faq-146" }, { "level": 2, "title": "FAQ 图片索引图片 147", "id": "faq-147" }, { "level": 2, "title": "FAQ 图片索引图片 148", "id": "faq-148" }, { "level": 2, "title": "FAQ 图片索引图片 149", "id": "faq-149" }, { "level": 2, "title": "FAQ 图片索引图片 150", "id": "faq-150" }, { "level": 2, "title": "FAQ 图片索引图片 151", "id": "faq-151" }, { "level": 2, "title": "FAQ 图片索引图片 152", "id": "faq-152" }, { "level": 2, "title": "FAQ 图片索引图片 153", "id": "faq-153" }, { "level": 2, "title": "FAQ 图片索引图片 154", "id": "faq-154" }, { "level": 2, "title": "FAQ 图片索引图片 155", "id": "faq-155" }, { "level": 2, "title": "FAQ 图片索引图片 156", "id": "faq-156" }, { "level": 2, "title": "FAQ 图片索引图片 157", "id": "faq-157" }, { "level": 2, "title": "FAQ 图片索引图片 158", "id": "faq-158" }, { "level": 2, "title": "FAQ 图片索引图片 159", "id": "faq-159" }, { "level": 2, "title": "FAQ 图片索引图片 160", "id": "faq-160" }, { "level": 2, "title": "FAQ 图片索引图片 161", "id": "faq-161" }, { "level": 2, "title": "FAQ 图片索引图片 162", "id": "faq-162" }, { "level": 2, "title": "FAQ 图片索引图片 163", "id": "faq-163" }, { "level": 2, "title": "FAQ 图片索引图片 164", "id": "faq-164" }, { "level": 2, "title": "FAQ 图片索引图片 165", "id": "faq-165" }, { "level": 2, "title": "FAQ 图片索引图片 166", "id": "faq-166" }, { "level": 2, "title": "FAQ 图片索引图片 167", "id": "faq-167" }, { "level": 2, "title": "FAQ 图片索引图片 168", "id": "faq-168" }, { "level": 2, "title": "FAQ 图片索引图片 169", "id": "faq-169" }, { "level": 2, "title": "FAQ 图片索引图片 170", "id": "faq-170" }, { "level": 2, "title": "FAQ 图片索引图片 171", "id": "faq-171" }, { "level": 2, "title": "FAQ 图片索引图片 172", "id": "faq-172" }, { "level": 2, "title": "FAQ 图片索引图片 173", "id": "faq-173" }, { "level": 2, "title": "FAQ 图片索引图片 174", "id": "faq-174" }, { "level": 2, "title": "FAQ 图片索引图片 175", "id": "faq-175" }, { "level": 2, "title": "FAQ 图片索引图片 176", "id": "faq-176" }, { "level": 2, "title": "FAQ 图片索引图片 177", "id": "faq-177" }, { "level": 2, "title": "FAQ 图片索引图片 178", "id": "faq-178" }, { "level": 2, "title": "FAQ 图片索引图片 179", "id": "faq-179" }, { "level": 2, "title": "FAQ 图片索引图片 180", "id": "faq-180" }, { "level": 2, "title": "FAQ 图片索引图片 181", "id": "faq-181" }, { "level": 2, "title": "FAQ 图片索引图片 182", "id": "faq-182" }, { "level": 2, "title": "FAQ 图片索引图片 183", "id": "faq-183" }, { "level": 2, "title": "FAQ 图片索引图片 184", "id": "faq-184" }, { "level": 2, "title": "FAQ 图片索引图片 185", "id": "faq-185" }, { "level": 2, "title": "FAQ 图片索引图片 186", "id": "faq-186" }, { "level": 2, "title": "FAQ 图片索引图片 187", "id": "faq-187" }, { "level": 2, "title": "FAQ 图片索引图片 188", "id": "faq-188" } ], "images": [ { "src": "../assets/images/faq/faq-001.png", "alt": "FAQ 图片索引图片 001", "caption": "FAQ 图片索引图片 001，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-002.png", "alt": "FAQ 图片索引图片 002", "caption": "FAQ 图片索引图片 002，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-003.png", "alt": "FAQ 图片索引图片 003", "caption": "FAQ 图片索引图片 003，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-004.png", "alt": "FAQ 图片索引图片 004", "caption": "FAQ 图片索引图片 004，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-005.png", "alt": "FAQ 图片索引图片 005", "caption": "FAQ 图片索引图片 005，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-006.png", "alt": "FAQ 图片索引图片 006", "caption": "FAQ 图片索引图片 006，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-007.png", "alt": "FAQ 图片索引图片 007", "caption": "FAQ 图片索引图片 007，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-008.png", "alt": "FAQ 图片索引图片 008", "caption": "FAQ 图片索引图片 008，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-009.png", "alt": "FAQ 图片索引图片 009", "caption": "FAQ 图片索引图片 009，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-010.png", "alt": "FAQ 图片索引图片 010", "caption": "FAQ 图片索引图片 010，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-011.png", "alt": "FAQ 图片索引图片 011", "caption": "FAQ 图片索引图片 011，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-012.png", "alt": "FAQ 图片索引图片 012", "caption": "FAQ 图片索引图片 012，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-013.png", "alt": "FAQ 图片索引图片 013", "caption": "FAQ 图片索引图片 013，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-014.png", "alt": "FAQ 图片索引图片 014", "caption": "FAQ 图片索引图片 014，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-015.png", "alt": "FAQ 图片索引图片 015", "caption": "FAQ 图片索引图片 015，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-016.png", "alt": "FAQ 图片索引图片 016", "caption": "FAQ 图片索引图片 016，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-017.png", "alt": "FAQ 图片索引图片 017", "caption": "FAQ 图片索引图片 017，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-018.png", "alt": "FAQ 图片索引图片 018", "caption": "FAQ 图片索引图片 018，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-019.png", "alt": "FAQ 图片索引图片 019", "caption": "FAQ 图片索引图片 019，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-020.png", "alt": "FAQ 图片索引图片 020", "caption": "FAQ 图片索引图片 020，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-021.png", "alt": "FAQ 图片索引图片 021", "caption": "FAQ 图片索引图片 021，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-022.png", "alt": "FAQ 图片索引图片 022", "caption": "FAQ 图片索引图片 022，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-023.png", "alt": "FAQ 图片索引图片 023", "caption": "FAQ 图片索引图片 023，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-024.png", "alt": "FAQ 图片索引图片 024", "caption": "FAQ 图片索引图片 024，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-025.png", "alt": "FAQ 图片索引图片 025", "caption": "FAQ 图片索引图片 025，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-026.png", "alt": "FAQ 图片索引图片 026", "caption": "FAQ 图片索引图片 026，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-027.png", "alt": "FAQ 图片索引图片 027", "caption": "FAQ 图片索引图片 027，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-028.png", "alt": "FAQ 图片索引图片 028", "caption": "FAQ 图片索引图片 028，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-029.png", "alt": "FAQ 图片索引图片 029", "caption": "FAQ 图片索引图片 029，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-030.png", "alt": "FAQ 图片索引图片 030", "caption": "FAQ 图片索引图片 030，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-031.png", "alt": "FAQ 图片索引图片 031", "caption": "FAQ 图片索引图片 031，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-032.png", "alt": "FAQ 图片索引图片 032", "caption": "FAQ 图片索引图片 032，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-033.png", "alt": "FAQ 图片索引图片 033", "caption": "FAQ 图片索引图片 033，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-034.png", "alt": "FAQ 图片索引图片 034", "caption": "FAQ 图片索引图片 034，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-035.png", "alt": "FAQ 图片索引图片 035", "caption": "FAQ 图片索引图片 035，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-036.png", "alt": "FAQ 图片索引图片 036", "caption": "FAQ 图片索引图片 036，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-037.png", "alt": "FAQ 图片索引图片 037", "caption": "FAQ 图片索引图片 037，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-038.png", "alt": "FAQ 图片索引图片 038", "caption": "FAQ 图片索引图片 038，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-039.png", "alt": "FAQ 图片索引图片 039", "caption": "FAQ 图片索引图片 039，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-040.png", "alt": "FAQ 图片索引图片 040", "caption": "FAQ 图片索引图片 040，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-041.png", "alt": "FAQ 图片索引图片 041", "caption": "FAQ 图片索引图片 041，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-042.png", "alt": "FAQ 图片索引图片 042", "caption": "FAQ 图片索引图片 042，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-043.png", "alt": "FAQ 图片索引图片 043", "caption": "FAQ 图片索引图片 043，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-044.png", "alt": "FAQ 图片索引图片 044", "caption": "FAQ 图片索引图片 044，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-045.png", "alt": "FAQ 图片索引图片 045", "caption": "FAQ 图片索引图片 045，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-046.png", "alt": "FAQ 图片索引图片 046", "caption": "FAQ 图片索引图片 046，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-047.png", "alt": "FAQ 图片索引图片 047", "caption": "FAQ 图片索引图片 047，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-048.png", "alt": "FAQ 图片索引图片 048", "caption": "FAQ 图片索引图片 048，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-049.png", "alt": "FAQ 图片索引图片 049", "caption": "FAQ 图片索引图片 049，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-050.png", "alt": "FAQ 图片索引图片 050", "caption": "FAQ 图片索引图片 050，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-051.png", "alt": "FAQ 图片索引图片 051", "caption": "FAQ 图片索引图片 051，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-052.png", "alt": "FAQ 图片索引图片 052", "caption": "FAQ 图片索引图片 052，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-053.png", "alt": "FAQ 图片索引图片 053", "caption": "FAQ 图片索引图片 053，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-054.png", "alt": "FAQ 图片索引图片 054", "caption": "FAQ 图片索引图片 054，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-055.png", "alt": "FAQ 图片索引图片 055", "caption": "FAQ 图片索引图片 055，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-056.png", "alt": "FAQ 图片索引图片 056", "caption": "FAQ 图片索引图片 056，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-057.png", "alt": "FAQ 图片索引图片 057", "caption": "FAQ 图片索引图片 057，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-058.png", "alt": "FAQ 图片索引图片 058", "caption": "FAQ 图片索引图片 058，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-059.png", "alt": "FAQ 图片索引图片 059", "caption": "FAQ 图片索引图片 059，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-060.png", "alt": "FAQ 图片索引图片 060", "caption": "FAQ 图片索引图片 060，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-061.png", "alt": "FAQ 图片索引图片 061", "caption": "FAQ 图片索引图片 061，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-062.png", "alt": "FAQ 图片索引图片 062", "caption": "FAQ 图片索引图片 062，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-063.png", "alt": "FAQ 图片索引图片 063", "caption": "FAQ 图片索引图片 063，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-064.png", "alt": "FAQ 图片索引图片 064", "caption": "FAQ 图片索引图片 064，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-065.png", "alt": "FAQ 图片索引图片 065", "caption": "FAQ 图片索引图片 065，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-066.png", "alt": "FAQ 图片索引图片 066", "caption": "FAQ 图片索引图片 066，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-067.png", "alt": "FAQ 图片索引图片 067", "caption": "FAQ 图片索引图片 067，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-068.png", "alt": "FAQ 图片索引图片 068", "caption": "FAQ 图片索引图片 068，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-069.png", "alt": "FAQ 图片索引图片 069", "caption": "FAQ 图片索引图片 069，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-070.png", "alt": "FAQ 图片索引图片 070", "caption": "FAQ 图片索引图片 070，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-071.png", "alt": "FAQ 图片索引图片 071", "caption": "FAQ 图片索引图片 071，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-072.png", "alt": "FAQ 图片索引图片 072", "caption": "FAQ 图片索引图片 072，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-073.png", "alt": "FAQ 图片索引图片 073", "caption": "FAQ 图片索引图片 073，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-074.png", "alt": "FAQ 图片索引图片 074", "caption": "FAQ 图片索引图片 074，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-075.png", "alt": "FAQ 图片索引图片 075", "caption": "FAQ 图片索引图片 075，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-076.png", "alt": "FAQ 图片索引图片 076", "caption": "FAQ 图片索引图片 076，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-077.png", "alt": "FAQ 图片索引图片 077", "caption": "FAQ 图片索引图片 077，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-078.png", "alt": "FAQ 图片索引图片 078", "caption": "FAQ 图片索引图片 078，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-079.png", "alt": "FAQ 图片索引图片 079", "caption": "FAQ 图片索引图片 079，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-080.png", "alt": "FAQ 图片索引图片 080", "caption": "FAQ 图片索引图片 080，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-081.png", "alt": "FAQ 图片索引图片 081", "caption": "FAQ 图片索引图片 081，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-082.png", "alt": "FAQ 图片索引图片 082", "caption": "FAQ 图片索引图片 082，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-083.png", "alt": "FAQ 图片索引图片 083", "caption": "FAQ 图片索引图片 083，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-084.png", "alt": "FAQ 图片索引图片 084", "caption": "FAQ 图片索引图片 084，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-085.png", "alt": "FAQ 图片索引图片 085", "caption": "FAQ 图片索引图片 085，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-086.png", "alt": "FAQ 图片索引图片 086", "caption": "FAQ 图片索引图片 086，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-087.png", "alt": "FAQ 图片索引图片 087", "caption": "FAQ 图片索引图片 087，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-088.png", "alt": "FAQ 图片索引图片 088", "caption": "FAQ 图片索引图片 088，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-089.png", "alt": "FAQ 图片索引图片 089", "caption": "FAQ 图片索引图片 089，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-090.png", "alt": "FAQ 图片索引图片 090", "caption": "FAQ 图片索引图片 090，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-091.png", "alt": "FAQ 图片索引图片 091", "caption": "FAQ 图片索引图片 091，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-092.png", "alt": "FAQ 图片索引图片 092", "caption": "FAQ 图片索引图片 092，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-093.png", "alt": "FAQ 图片索引图片 093", "caption": "FAQ 图片索引图片 093，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-094.png", "alt": "FAQ 图片索引图片 094", "caption": "FAQ 图片索引图片 094，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-095.png", "alt": "FAQ 图片索引图片 095", "caption": "FAQ 图片索引图片 095，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-096.png", "alt": "FAQ 图片索引图片 096", "caption": "FAQ 图片索引图片 096，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-097.png", "alt": "FAQ 图片索引图片 097", "caption": "FAQ 图片索引图片 097，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-098.png", "alt": "FAQ 图片索引图片 098", "caption": "FAQ 图片索引图片 098，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-099.png", "alt": "FAQ 图片索引图片 099", "caption": "FAQ 图片索引图片 099，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-100.png", "alt": "FAQ 图片索引图片 100", "caption": "FAQ 图片索引图片 100，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-101.png", "alt": "FAQ 图片索引图片 101", "caption": "FAQ 图片索引图片 101，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-102.jpg", "alt": "FAQ 图片索引图片 102", "caption": "FAQ 图片索引图片 102，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-103.png", "alt": "FAQ 图片索引图片 103", "caption": "FAQ 图片索引图片 103，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-104.jpg", "alt": "FAQ 图片索引图片 104", "caption": "FAQ 图片索引图片 104，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-105.png", "alt": "FAQ 图片索引图片 105", "caption": "FAQ 图片索引图片 105，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-106.png", "alt": "FAQ 图片索引图片 106", "caption": "FAQ 图片索引图片 106，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-107.png", "alt": "FAQ 图片索引图片 107", "caption": "FAQ 图片索引图片 107，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-108.png", "alt": "FAQ 图片索引图片 108", "caption": "FAQ 图片索引图片 108，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-109.png", "alt": "FAQ 图片索引图片 109", "caption": "FAQ 图片索引图片 109，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-110.png", "alt": "FAQ 图片索引图片 110", "caption": "FAQ 图片索引图片 110，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-111.png", "alt": "FAQ 图片索引图片 111", "caption": "FAQ 图片索引图片 111，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-112.png", "alt": "FAQ 图片索引图片 112", "caption": "FAQ 图片索引图片 112，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-113.png", "alt": "FAQ 图片索引图片 113", "caption": "FAQ 图片索引图片 113，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-114.png", "alt": "FAQ 图片索引图片 114", "caption": "FAQ 图片索引图片 114，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-115.png", "alt": "FAQ 图片索引图片 115", "caption": "FAQ 图片索引图片 115，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-116.png", "alt": "FAQ 图片索引图片 116", "caption": "FAQ 图片索引图片 116，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-117.png", "alt": "FAQ 图片索引图片 117", "caption": "FAQ 图片索引图片 117，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-118.png", "alt": "FAQ 图片索引图片 118", "caption": "FAQ 图片索引图片 118，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-119.png", "alt": "FAQ 图片索引图片 119", "caption": "FAQ 图片索引图片 119，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-120.png", "alt": "FAQ 图片索引图片 120", "caption": "FAQ 图片索引图片 120，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-121.png", "alt": "FAQ 图片索引图片 121", "caption": "FAQ 图片索引图片 121，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-122.png", "alt": "FAQ 图片索引图片 122", "caption": "FAQ 图片索引图片 122，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-123.png", "alt": "FAQ 图片索引图片 123", "caption": "FAQ 图片索引图片 123，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-124.png", "alt": "FAQ 图片索引图片 124", "caption": "FAQ 图片索引图片 124，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-125.png", "alt": "FAQ 图片索引图片 125", "caption": "FAQ 图片索引图片 125，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-126.png", "alt": "FAQ 图片索引图片 126", "caption": "FAQ 图片索引图片 126，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-127.png", "alt": "FAQ 图片索引图片 127", "caption": "FAQ 图片索引图片 127，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-128.png", "alt": "FAQ 图片索引图片 128", "caption": "FAQ 图片索引图片 128，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-129.png", "alt": "FAQ 图片索引图片 129", "caption": "FAQ 图片索引图片 129，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-130.png", "alt": "FAQ 图片索引图片 130", "caption": "FAQ 图片索引图片 130，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-131.png", "alt": "FAQ 图片索引图片 131", "caption": "FAQ 图片索引图片 131，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-132.png", "alt": "FAQ 图片索引图片 132", "caption": "FAQ 图片索引图片 132，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-133.png", "alt": "FAQ 图片索引图片 133", "caption": "FAQ 图片索引图片 133，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-134.png", "alt": "FAQ 图片索引图片 134", "caption": "FAQ 图片索引图片 134，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-135.png", "alt": "FAQ 图片索引图片 135", "caption": "FAQ 图片索引图片 135，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-136.png", "alt": "FAQ 图片索引图片 136", "caption": "FAQ 图片索引图片 136，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-137.png", "alt": "FAQ 图片索引图片 137", "caption": "FAQ 图片索引图片 137，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-138.png", "alt": "FAQ 图片索引图片 138", "caption": "FAQ 图片索引图片 138，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-139.png", "alt": "FAQ 图片索引图片 139", "caption": "FAQ 图片索引图片 139，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-140.png", "alt": "FAQ 图片索引图片 140", "caption": "FAQ 图片索引图片 140，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-141.png", "alt": "FAQ 图片索引图片 141", "caption": "FAQ 图片索引图片 141，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-142.png", "alt": "FAQ 图片索引图片 142", "caption": "FAQ 图片索引图片 142，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-143.png", "alt": "FAQ 图片索引图片 143", "caption": "FAQ 图片索引图片 143，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-144.png", "alt": "FAQ 图片索引图片 144", "caption": "FAQ 图片索引图片 144，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-145.png", "alt": "FAQ 图片索引图片 145", "caption": "FAQ 图片索引图片 145，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-146.png", "alt": "FAQ 图片索引图片 146", "caption": "FAQ 图片索引图片 146，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-147.png", "alt": "FAQ 图片索引图片 147", "caption": "FAQ 图片索引图片 147，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-148.png", "alt": "FAQ 图片索引图片 148", "caption": "FAQ 图片索引图片 148，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-149.png", "alt": "FAQ 图片索引图片 149", "caption": "FAQ 图片索引图片 149，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-150.png", "alt": "FAQ 图片索引图片 150", "caption": "FAQ 图片索引图片 150，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-151.png", "alt": "FAQ 图片索引图片 151", "caption": "FAQ 图片索引图片 151，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-152.png", "alt": "FAQ 图片索引图片 152", "caption": "FAQ 图片索引图片 152，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-153.png", "alt": "FAQ 图片索引图片 153", "caption": "FAQ 图片索引图片 153，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-154.png", "alt": "FAQ 图片索引图片 154", "caption": "FAQ 图片索引图片 154，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-155.png", "alt": "FAQ 图片索引图片 155", "caption": "FAQ 图片索引图片 155，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-156.png", "alt": "FAQ 图片索引图片 156", "caption": "FAQ 图片索引图片 156，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-157.png", "alt": "FAQ 图片索引图片 157", "caption": "FAQ 图片索引图片 157，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-158.png", "alt": "FAQ 图片索引图片 158", "caption": "FAQ 图片索引图片 158，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-159.png", "alt": "FAQ 图片索引图片 159", "caption": "FAQ 图片索引图片 159，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-160.png", "alt": "FAQ 图片索引图片 160", "caption": "FAQ 图片索引图片 160，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-161.png", "alt": "FAQ 图片索引图片 161", "caption": "FAQ 图片索引图片 161，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-162.png", "alt": "FAQ 图片索引图片 162", "caption": "FAQ 图片索引图片 162，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-163.png", "alt": "FAQ 图片索引图片 163", "caption": "FAQ 图片索引图片 163，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-164.png", "alt": "FAQ 图片索引图片 164", "caption": "FAQ 图片索引图片 164，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-165.png", "alt": "FAQ 图片索引图片 165", "caption": "FAQ 图片索引图片 165，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-166.png", "alt": "FAQ 图片索引图片 166", "caption": "FAQ 图片索引图片 166，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-167.png", "alt": "FAQ 图片索引图片 167", "caption": "FAQ 图片索引图片 167，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-168.png", "alt": "FAQ 图片索引图片 168", "caption": "FAQ 图片索引图片 168，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-169.png", "alt": "FAQ 图片索引图片 169", "caption": "FAQ 图片索引图片 169，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-170.png", "alt": "FAQ 图片索引图片 170", "caption": "FAQ 图片索引图片 170，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-171.png", "alt": "FAQ 图片索引图片 171", "caption": "FAQ 图片索引图片 171，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-172.png", "alt": "FAQ 图片索引图片 172", "caption": "FAQ 图片索引图片 172，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-173.png", "alt": "FAQ 图片索引图片 173", "caption": "FAQ 图片索引图片 173，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-174.png", "alt": "FAQ 图片索引图片 174", "caption": "FAQ 图片索引图片 174，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-175.png", "alt": "FAQ 图片索引图片 175", "caption": "FAQ 图片索引图片 175，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-176.png", "alt": "FAQ 图片索引图片 176", "caption": "FAQ 图片索引图片 176，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-177.png", "alt": "FAQ 图片索引图片 177", "caption": "FAQ 图片索引图片 177，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-178.png", "alt": "FAQ 图片索引图片 178", "caption": "FAQ 图片索引图片 178，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-179.png", "alt": "FAQ 图片索引图片 179", "caption": "FAQ 图片索引图片 179，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-180.png", "alt": "FAQ 图片索引图片 180", "caption": "FAQ 图片索引图片 180，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-181.png", "alt": "FAQ 图片索引图片 181", "caption": "FAQ 图片索引图片 181，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-182.png", "alt": "FAQ 图片索引图片 182", "caption": "FAQ 图片索引图片 182，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-183.png", "alt": "FAQ 图片索引图片 183", "caption": "FAQ 图片索引图片 183，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-184.png", "alt": "FAQ 图片索引图片 184", "caption": "FAQ 图片索引图片 184，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-185.png", "alt": "FAQ 图片索引图片 185", "caption": "FAQ 图片索引图片 185，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-186.png", "alt": "FAQ 图片索引图片 186", "caption": "FAQ 图片索引图片 186，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-187.png", "alt": "FAQ 图片索引图片 187", "caption": "FAQ 图片索引图片 187，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-188.png", "alt": "FAQ 图片索引图片 188", "caption": "FAQ 图片索引图片 188，从 巴别鸟FAQ（用户手册）.docx 抽取。" } ], "text": "FAQ 图片索引 本页汇总《巴别鸟FAQ（用户手册）》中的全部嵌入图片。 这些图片从源文档中按原始顺序抽取，保留为可直接访问的静态资源。页面主要用于原文对照、AI 视觉资料索引、后续人工挑选配图和搜索引擎发现。 项 数值 图片数量 188 来源文件 巴别鸟FAQ（用户手册）.docx FAQ 图片索引图片 001 来源：巴别鸟FAQ（用户手册） / word/media/image1.png 静态路径： assets/images/faq/faq 001.png FAQ 图片索引图片 001 FAQ 图片索引图片 001，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 002 来源：巴别鸟FAQ（用户手册） / word/media/image10.png 静态路径： assets/images/faq/faq 002.png FAQ 图片索引图片 002 FAQ 图片索引图片 002，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 003 来源：巴别鸟FAQ（用户手册） / word/media/image100.png 静态路径： assets/images/faq/faq 003.png FAQ 图片索引图片 003 FAQ 图片索引图片 003，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 004 来源：巴别鸟FAQ（用户手册） / word/media/image11.png 静态路径： assets/images/faq/faq 004.png FAQ 图片索引图片 004 FAQ 图片索引图片 004，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 005 来源：巴别鸟FAQ（用户手册） / word/media/image110.png 静态路径： assets/images/faq/faq 005.png FAQ 图片索引图片 005 FAQ 图片索引图片 005，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 006 来源：巴别鸟FAQ（用户手册） / word/media/image111.png 静态路径： assets/images/faq/faq 006.png FAQ 图片索引图片 006 FAQ 图片索引图片 006，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 007 来源：巴别鸟FAQ（用户手册） / word/media/image12.png 静态路径： assets/images/faq/faq 007.png FAQ 图片索引图片 007 FAQ 图片索引图片 007，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 008 来源：巴别鸟FAQ（用户手册） / word/media/image120.png 静态路径： assets/images/faq/faq 008.png FAQ 图片索引图片 008 FAQ 图片索引图片 008，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 009 来源：巴别鸟FAQ（用户手册） / word/media/image13.png 静态路径： assets/images/faq/faq 009.png FAQ 图片索引图片 009 FAQ 图片索引图片 009，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 010 来源：巴别鸟FAQ（用户手册） / word/media/image130.png 静态路径： assets/images/faq/faq 010.png FAQ 图片索引图片 010 FAQ 图片索引图片 010，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 011 来源：巴别鸟FAQ（用户手册） / word/media/image14.png 静态路径： assets/images/faq/faq 011.png FAQ 图片索引图片 011 FAQ 图片索引图片 011，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 012 来源：巴别鸟FAQ（用户手册） / word/media/image140.png 静态路径： assets/images/faq/faq 012.png FAQ 图片索引图片 012 FAQ 图片索引图片 012，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 013 来源：巴别鸟FAQ（用户手册） / word/media/image15.png 静态路径： assets/images/faq/faq 013.png FAQ 图片索引图片 013 FAQ 图片索引图片 013，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 014 来源：巴别鸟FAQ（用户手册） / word/media/image150.png 静态路径： assets/images/faq/faq 014.png FAQ 图片索引图片 014 FAQ 图片索引图片 014，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 015 来源：巴别鸟FAQ（用户手册） / word/media/image16.png 静态路径： assets/images/faq/faq 015.png FAQ 图片索引图片 015 FAQ 图片索引图片 015，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 016 来源：巴别鸟FAQ（用户手册） / word/media/image160.png 静态路径： assets/images/faq/faq 016.png FAQ 图片索引图片 016 FAQ 图片索引图片 016，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 017 来源：巴别鸟FAQ（用户手册） / word/media/image17.png 静态路径： assets/images/faq/faq 017.png FAQ 图片索引图片 017 FAQ 图片索引图片 017，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 018 来源：巴别鸟FAQ（用户手册） / word/media/image170.png 静态路径： assets/images/faq/faq 018.png FAQ 图片索引图片 018 FAQ 图片索引图片 018，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 019 来源：巴别鸟FAQ（用户手册） / word/media/image18.png 静态路径： assets/images/faq/faq 019.png FAQ 图片索引图片 019 FAQ 图片索引图片 019，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 020 来源：巴别鸟FAQ（用户手册） / word/media/image180.png 静态路径： assets/images/faq/faq 020.png FAQ 图片索引图片 020 FAQ 图片索引图片 020，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 021 来源：巴别鸟FAQ（用户手册） / word/media/image19.png 静态路径： assets/images/faq/faq 021.png FAQ 图片索引图片 021 FAQ 图片索引图片 021，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 022 来源：巴别鸟FAQ（用户手册） / word/media/image190.png 静态路径： assets/images/faq/faq 022.png FAQ 图片索引图片 022 FAQ 图片索引图片 022，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 023 来源：巴别鸟FAQ（用户手册） / word/media/image2.png 静态路径： assets/images/faq/faq 023.png FAQ 图片索引图片 023 FAQ 图片索引图片 023，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 024 来源：巴别鸟FAQ（用户手册） / word/media/image20.png 静态路径： assets/images/faq/faq 024.png FAQ 图片索引图片 024 FAQ 图片索引图片 024，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 025 来源：巴别鸟FAQ（用户手册） / word/media/image200.png 静态路径： assets/images/faq/faq 025.png FAQ 图片索引图片 025 FAQ 图片索引图片 025，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 026 来源：巴别鸟FAQ（用户手册） / word/media/image21.png 静态路径： assets/images/faq/faq 026.png FAQ 图片索引图片 026 FAQ 图片索引图片 026，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 027 来源：巴别鸟FAQ（用户手册） / word/media/image210.png 静态路径： assets/images/faq/faq 027.png FAQ 图片索引图片 027 FAQ 图片索引图片 027，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 028 来源：巴别鸟FAQ（用户手册） / word/media/image211.png 静态路径： assets/images/faq/faq 028.png FAQ 图片索引图片 028 FAQ 图片索引图片 028，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 029 来源：巴别鸟FAQ（用户手册） / word/media/image22.png 静态路径： assets/images/faq/faq 029.png FAQ 图片索引图片 029 FAQ 图片索引图片 029，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 030 来源：巴别鸟FAQ（用户手册） / word/media/image220.png 静态路径： assets/images/faq/faq 030.png FAQ 图片索引图片 030 FAQ 图片索引图片 030，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 031 来源：巴别鸟FAQ（用户手册） / word/media/image23.png 静态路径： assets/images/faq/faq 031.png FAQ 图片索引图片 031 FAQ 图片索引图片 031，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 032 来源：巴别鸟FAQ（用户手册） / word/media/image230.png 静态路径： assets/images/faq/faq 032.png FAQ 图片索引图片 032 FAQ 图片索引图片 032，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 033 来源：巴别鸟FAQ（用户手册） / word/media/image24.png 静态路径： assets/images/faq/faq 033.png FAQ 图片索引图片 033 FAQ 图片索引图片 033，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 034 来源：巴别鸟FAQ（用户手册） / word/media/image240.png 静态路径： assets/images/faq/faq 034.png FAQ 图片索引图片 034 FAQ 图片索引图片 034，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 035 来源：巴别鸟FAQ（用户手册） / word/media/image25.png 静态路径： assets/images/faq/faq 035.png FAQ 图片索引图片 035 FAQ 图片索引图片 035，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 036 来源：巴别鸟FAQ（用户手册） / word/media/image250.png 静态路径： assets/images/faq/faq 036.png FAQ 图片索引图片 036 FAQ 图片索引图片 036，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 037 来源：巴别鸟FAQ（用户手册） / word/media/image26.png 静态路径： assets/images/faq/faq 037.png FAQ 图片索引图片 037 FAQ 图片索引图片 037，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 038 来源：巴别鸟FAQ（用户手册） / word/media/image260.png 静态路径： assets/images/faq/faq 038.png FAQ 图片索引图片 038 FAQ 图片索引图片 038，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 039 来源：巴别鸟FAQ（用户手册） / word/media/image27.png 静态路径： assets/images/faq/faq 039.png FAQ 图片索引图片 039 FAQ 图片索引图片 039，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 040 来源：巴别鸟FAQ（用户手册） / word/media/image270.png 静态路径： assets/images/faq/faq 040.png FAQ 图片索引图片 040 FAQ 图片索引图片 040，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 041 来源：巴别鸟FAQ（用户手册） / word/media/image28.png 静态路径： assets/images/faq/faq 041.png FAQ 图片索引图片 041 FAQ 图片索引图片 041，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 042 来源：巴别鸟FAQ（用户手册） / word/media/image280.png 静态路径： assets/images/faq/faq 042.png FAQ 图片索引图片 042 FAQ 图片索引图片 042，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 043 来源：巴别鸟FAQ（用户手册） / word/media/image29.png 静态路径： assets/images/faq/faq 043.png FAQ 图片索引图片 043 FAQ 图片索引图片 043，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 044 来源：巴别鸟FAQ（用户手册） / word/media/image290.png 静态路径： assets/images/faq/faq 044.png FAQ 图片索引图片 044 FAQ 图片索引图片 044，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 045 来源：巴别鸟FAQ（用户手册） / word/media/image3.png 静态路径： assets/images/faq/faq 045.png FAQ 图片索引图片 045 FAQ 图片索引图片 045，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 046 来源：巴别鸟FAQ（用户手册） / word/media/image30.png 静态路径： assets/images/faq/faq 046.png FAQ 图片索引图片 046 FAQ 图片索引图片 046，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 047 来源：巴别鸟FAQ（用户手册） / word/media/image300.png 静态路径： assets/images/faq/faq 047.png FAQ 图片索引图片 047 FAQ 图片索引图片 047，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 048 来源：巴别鸟FAQ（用户手册） / word/media/image31.png 静态路径： assets/images/faq/faq 048.png FAQ 图片索引图片 048 FAQ 图片索引图片 048，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 049 来源：巴别鸟FAQ（用户手册） / word/media/image310.png 静态路径： assets/images/faq/faq 049.png FAQ 图片索引图片 049 FAQ 图片索引图片 049，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 050 来源：巴别鸟FAQ（用户手册） / word/media/image311.png 静态路径： assets/images/faq/faq 050.png FAQ 图片索引图片 050 FAQ 图片索引图片 050，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 051 来源：巴别鸟FAQ（用户手册） / word/media/image32.png 静态路径： assets/images/faq/faq 051.png FAQ 图片索引图片 051 FAQ 图片索引图片 051，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 052 来源：巴别鸟FAQ（用户手册） / word/media/image320.png 静态路径： assets/images/faq/faq 052.png FAQ 图片索引图片 052 FAQ 图片索引图片 052，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 053 来源：巴别鸟FAQ（用户手册） / word/media/image33.png 静态路径： assets/images/faq/faq 053.png FAQ 图片索引图片 053 FAQ 图片索引图片 053，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 054 来源：巴别鸟FAQ（用户手册） / word/media/image330.png 静态路径： assets/images/faq/faq 054.png FAQ 图片索引图片 054 FAQ 图片索引图片 054，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 055 来源：巴别鸟FAQ（用户手册） / word/media/image34.png 静态路径： assets/images/faq/faq 055.png FAQ 图片索引图片 055 FAQ 图片索引图片 055，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 056 来源：巴别鸟FAQ（用户手册） / word/media/image340.png 静态路径： assets/images/faq/faq 056.png FAQ 图片索引图片 056 FAQ 图片索引图片 056，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 057 来源：巴别鸟FAQ（用户手册） / word/media/image35.png 静态路径： assets/images/faq/faq 057.png FAQ 图片索引图片 057 FAQ 图片索引图片 057，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 058 来源：巴别鸟FAQ（用户手册） / word/media/image350.png 静态路径： assets/images/faq/faq 058.png FAQ 图片索引图片 058 FAQ 图片索引图片 058，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 059 来源：巴别鸟FAQ（用户手册） / word/media/image36.png 静态路径： assets/images/faq/faq 059.png FAQ 图片索引图片 059 FAQ 图片索引图片 059，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 060 来源：巴别鸟FAQ（用户手册） / word/media/image360.png 静态路径： assets/images/faq/faq 060.png FAQ 图片索引图片 060 FAQ 图片索引图片 060，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 061 来源：巴别鸟FAQ（用户手册） / word/media/image37.png 静态路径： assets/images/faq/faq 061.png FAQ 图片索引图片 061 FAQ 图片索引图片 061，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 062 来源：巴别鸟FAQ（用户手册） / word/media/image370.png 静态路径： assets/images/faq/faq 062.png FAQ 图片索引图片 062 FAQ 图片索引图片 062，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 063 来源：巴别鸟FAQ（用户手册） / word/media/image38.png 静态路径： assets/images/faq/faq 063.png FAQ 图片索引图片 063 FAQ 图片索引图片 063，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 064 来源：巴别鸟FAQ（用户手册） / word/media/image380.png 静态路径： assets/images/faq/faq 064.png FAQ 图片索引图片 064 FAQ 图片索引图片 064，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 065 来源：巴别鸟FAQ（用户手册） / word/media/image39.png 静态路径： assets/images/faq/faq 065.png FAQ 图片索引图片 065 FAQ 图片索引图片 065，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 066 来源：巴别鸟FAQ（用户手册） / word/media/image390.png 静态路径： assets/images/faq/faq 066.png FAQ 图片索引图片 066 FAQ 图片索引图片 066，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 067 来源：巴别鸟FAQ（用户手册） / word/media/image4.png 静态路径： assets/images/faq/faq 067.png FAQ 图片索引图片 067 FAQ 图片索引图片 067，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 068 来源：巴别鸟FAQ（用户手册） / word/media/image40.png 静态路径： assets/images/faq/faq 068.png FAQ 图片索引图片 068 FAQ 图片索引图片 068，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 069 来源：巴别鸟FAQ（用户手册） / word/media/image400.png 静态路径： assets/images/faq/faq 069.png FAQ 图片索引图片 069 FAQ 图片索引图片 069，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 070 来源：巴别鸟FAQ（用户手册） / word/media/image41.png 静态路径： assets/images/faq/faq 070.png FAQ 图片索引图片 070 FAQ 图片索引图片 070，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 071 来源：巴别鸟FAQ（用户手册） / word/media/image410.png 静态路径： assets/images/faq/faq 071.png FAQ 图片索引图片 071 FAQ 图片索引图片 071，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 072 来源：巴别鸟FAQ（用户手册） / word/media/image411.png 静态路径： assets/images/faq/faq 072.png FAQ 图片索引图片 072 FAQ 图片索引图片 072，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 073 来源：巴别鸟FAQ（用户手册） / word/media/image42.png 静态路径： assets/images/faq/faq 073.png FAQ 图片索引图片 073 FAQ 图片索引图片 073，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 074 来源：巴别鸟FAQ（用户手册） / word/media/image420.png 静态路径： assets/images/faq/faq 074.png FAQ 图片索引图片 074 FAQ 图片索引图片 074，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 075 来源：巴别鸟FAQ（用户手册） / word/media/image43.png 静态路径： assets/images/faq/faq 075.png FAQ 图片索引图片 075 FAQ 图片索引图片 075，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 076 来源：巴别鸟FAQ（用户手册） / word/media/image430.png 静态路径： assets/images/faq/faq 076.png FAQ 图片索引图片 076 FAQ 图片索引图片 076，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 077 来源：巴别鸟FAQ（用户手册） / word/media/image44.png 静态路径： assets/images/faq/faq 077.png FAQ 图片索引图片 077 FAQ 图片索引图片 077，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 078 来源：巴别鸟FAQ（用户手册） / word/media/image440.png 静态路径： assets/images/faq/faq 078.png FAQ 图片索引图片 078 FAQ 图片索引图片 078，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 079 来源：巴别鸟FAQ（用户手册） / word/media/image45.png 静态路径： assets/images/faq/faq 079.png FAQ 图片索引图片 079 FAQ 图片索引图片 079，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 080 来源：巴别鸟FAQ（用户手册） / word/media/image450.png 静态路径： assets/images/faq/faq 080.png FAQ 图片索引图片 080 FAQ 图片索引图片 080，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 081 来源：巴别鸟FAQ（用户手册） / word/media/image46.png 静态路径： assets/images/faq/faq 081.png FAQ 图片索引图片 081 FAQ 图片索引图片 081，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 082 来源：巴别鸟FAQ（用户手册） / word/media/image460.png 静态路径： assets/images/faq/faq 082.png FAQ 图片索引图片 082 FAQ 图片索引图片 082，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 083 来源：巴别鸟FAQ（用户手册） / word/media/image47.png 静态路径： assets/images/faq/faq 083.png FAQ 图片索引图片 083 FAQ 图片索引图片 083，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 084 来源：巴别鸟FAQ（用户手册） / word/media/image470.png 静态路径： assets/images/faq/faq 084.png FAQ 图片索引图片 084 FAQ 图片索引图片 084，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 085 来源：巴别鸟FAQ（用户手册） / word/media/image48.png 静态路径： assets/images/faq/faq 085.png FAQ 图片索引图片 085 FAQ 图片索引图片 085，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 086 来源：巴别鸟FAQ（用户手册） / word/media/image480.png 静态路径： assets/images/faq/faq 086.png FAQ 图片索引图片 086 FAQ 图片索引图片 086，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 087 来源：巴别鸟FAQ（用户手册） / word/media/image49.png 静态路径： assets/images/faq/faq 087.png FAQ 图片索引图片 087 FAQ 图片索引图片 087，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 088 来源：巴别鸟FAQ（用户手册） / word/media/image490.png 静态路径： assets/images/faq/faq 088.png FAQ 图片索引图片 088 FAQ 图片索引图片 088，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 089 来源：巴别鸟FAQ（用户手册） / word/media/image5.png 静态路径： assets/images/faq/faq 089.png FAQ 图片索引图片 089 FAQ 图片索引图片 089，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 090 来源：巴别鸟FAQ（用户手册） / word/media/image50.png 静态路径： assets/images/faq/faq 090.png FAQ 图片索引图片 090 FAQ 图片索引图片 090，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 091 来源：巴别鸟FAQ（用户手册） / word/media/image500.png 静态路径： assets/images/faq/faq 091.png FAQ 图片索引图片 091 FAQ 图片索引图片 091，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 092 来源：巴别鸟FAQ（用户手册） / word/media/image51.png 静态路径： assets/images/faq/faq 092.png FAQ 图片索引图片 092 FAQ 图片索引图片 092，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 093 来源：巴别鸟FAQ（用户手册） / word/media/image510.png 静态路径： assets/images/faq/faq 093.png FAQ 图片索引图片 093 FAQ 图片索引图片 093，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 094 来源：巴别鸟FAQ（用户手册） / word/media/image52.png 静态路径： assets/images/faq/faq 094.png FAQ 图片索引图片 094 FAQ 图片索引图片 094，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 095 来源：巴别鸟FAQ（用户手册） / word/media/image520.png 静态路径： assets/images/faq/faq 095.png FAQ 图片索引图片 095 FAQ 图片索引图片 095，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 096 来源：巴别鸟FAQ（用户手册） / word/media/image53.png 静态路径： assets/images/faq/faq 096.png FAQ 图片索引图片 096 FAQ 图片索引图片 096，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 097 来源：巴别鸟FAQ（用户手册） / word/media/image530.png 静态路径： assets/images/faq/faq 097.png FAQ 图片索引图片 097 FAQ 图片索引图片 097，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 098 来源：巴别鸟FAQ（用户手册） / word/media/image54.png 静态路径： assets/images/faq/faq 098.png FAQ 图片索引图片 098 FAQ 图片索引图片 098，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 099 来源：巴别鸟FAQ（用户手册） / word/media/image540.png 静态路径： assets/images/faq/faq 099.png FAQ 图片索引图片 099 FAQ 图片索引图片 099，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 100 来源：巴别鸟FAQ（用户手册） / word/media/image55.png 静态路径： assets/images/faq/faq 100.png FAQ 图片索引图片 100 FAQ 图片索引图片 100，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 101 来源：巴别鸟FAQ（用户手册） / word/media/image550.png 静态路径： assets/images/faq/faq 101.png FAQ 图片索引图片 101 FAQ 图片索引图片 101，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 102 来源：巴别鸟FAQ（用户手册） / word/media/image56.jpg 静态路径： assets/images/faq/faq 102.jpg FAQ 图片索引图片 102 FAQ 图片索引图片 102，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 103 来源：巴别鸟FAQ（用户手册） / word/media/image56.png 静态路径： assets/images/faq/faq 103.png FAQ 图片索引图片 103 FAQ 图片索引图片 103，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 104 来源：巴别鸟FAQ（用户手册） / word/media/image560.jpg 静态路径： assets/images/faq/faq 104.jpg FAQ 图片索引图片 104 FAQ 图片索引图片 104，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 105 来源：巴别鸟FAQ（用户手册） / word/media/image57.png 静态路径： assets/images/faq/faq 105.png FAQ 图片索引图片 105 FAQ 图片索引图片 105，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 106 来源：巴别鸟FAQ（用户手册） / word/media/image570.png 静态路径： assets/images/faq/faq 106.png FAQ 图片索引图片 106 FAQ 图片索引图片 106，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 107 来源：巴别鸟FAQ（用户手册） / word/media/image58.png 静态路径： assets/images/faq/faq 107.png FAQ 图片索引图片 107 FAQ 图片索引图片 107，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 108 来源：巴别鸟FAQ（用户手册） / word/media/image580.png 静态路径： assets/images/faq/faq 108.png FAQ 图片索引图片 108 FAQ 图片索引图片 108，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 109 来源：巴别鸟FAQ（用户手册） / word/media/image59.png 静态路径： assets/images/faq/faq 109.png FAQ 图片索引图片 109 FAQ 图片索引图片 109，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 110 来源：巴别鸟FAQ（用户手册） / word/media/image590.png 静态路径： assets/images/faq/faq 110.png FAQ 图片索引图片 110 FAQ 图片索引图片 110，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 111 来源：巴别鸟FAQ（用户手册） / word/media/image6.png 静态路径： assets/images/faq/faq 111.png FAQ 图片索引图片 111 FAQ 图片索引图片 111，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 112 来源：巴别鸟FAQ（用户手册） / word/media/image60.png 静态路径： assets/images/faq/faq 112.png FAQ 图片索引图片 112 FAQ 图片索引图片 112，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 113 来源：巴别鸟FAQ（用户手册） / word/media/image600.png 静态路径： assets/images/faq/faq 113.png FAQ 图片索引图片 113 FAQ 图片索引图片 113，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 114 来源：巴别鸟FAQ（用户手册） / word/media/image61.png 静态路径： assets/images/faq/faq 114.png FAQ 图片索引图片 114 FAQ 图片索引图片 114，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 115 来源：巴别鸟FAQ（用户手册） / word/media/image610.png 静态路径： assets/images/faq/faq 115.png FAQ 图片索引图片 115 FAQ 图片索引图片 115，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 116 来源：巴别鸟FAQ（用户手册） / word/media/image611.png 静态路径： assets/images/faq/faq 116.png FAQ 图片索引图片 116 FAQ 图片索引图片 116，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 117 来源：巴别鸟FAQ（用户手册） / word/media/image62.png 静态路径： assets/images/faq/faq 117.png FAQ 图片索引图片 117 FAQ 图片索引图片 117，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 118 来源：巴别鸟FAQ（用户手册） / word/media/image620.png 静态路径： assets/images/faq/faq 118.png FAQ 图片索引图片 118 FAQ 图片索引图片 118，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 119 来源：巴别鸟FAQ（用户手册） / word/media/image63.png 静态路径： assets/images/faq/faq 119.png FAQ 图片索引图片 119 FAQ 图片索引图片 119，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 120 来源：巴别鸟FAQ（用户手册） / word/media/image630.png 静态路径： assets/images/faq/faq 120.png FAQ 图片索引图片 120 FAQ 图片索引图片 120，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 121 来源：巴别鸟FAQ（用户手册） / word/media/image64.png 静态路径： assets/images/faq/faq 121.png FAQ 图片索引图片 121 FAQ 图片索引图片 121，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 122 来源：巴别鸟FAQ（用户手册） / word/media/image640.png 静态路径： assets/images/faq/faq 122.png FAQ 图片索引图片 122 FAQ 图片索引图片 122，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 123 来源：巴别鸟FAQ（用户手册） / word/media/image65.png 静态路径： assets/images/faq/faq 123.png FAQ 图片索引图片 123 FAQ 图片索引图片 123，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 124 来源：巴别鸟FAQ（用户手册） / word/media/image650.png 静态路径： assets/images/faq/faq 124.png FAQ 图片索引图片 124 FAQ 图片索引图片 124，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 125 来源：巴别鸟FAQ（用户手册） / word/media/image66.png 静态路径： assets/images/faq/faq 125.png FAQ 图片索引图片 125 FAQ 图片索引图片 125，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 126 来源：巴别鸟FAQ（用户手册） / word/media/image660.png 静态路径： assets/images/faq/faq 126.png FAQ 图片索引图片 126 FAQ 图片索引图片 126，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 127 来源：巴别鸟FAQ（用户手册） / word/media/image67.png 静态路径： assets/images/faq/faq 127.png FAQ 图片索引图片 127 FAQ 图片索引图片 127，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 128 来源：巴别鸟FAQ（用户手册） / word/media/image670.png 静态路径： assets/images/faq/faq 128.png FAQ 图片索引图片 128 FAQ 图片索引图片 128，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 129 来源：巴别鸟FAQ（用户手册） / word/media/image68.png 静态路径： assets/images/faq/faq 129.png FAQ 图片索引图片 129 FAQ 图片索引图片 129，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 130 来源：巴别鸟FAQ（用户手册） / word/media/image680.png 静态路径： assets/images/faq/faq 130.png FAQ 图片索引图片 130 FAQ 图片索引图片 130，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 131 来源：巴别鸟FAQ（用户手册） / word/media/image69.png 静态路径： assets/images/faq/faq 131.png FAQ 图片索引图片 131 FAQ 图片索引图片 131，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 132 来源：巴别鸟FAQ（用户手册） / word/media/image690.png 静态路径： assets/images/faq/faq 132.png FAQ 图片索引图片 132 FAQ 图片索引图片 132，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 133 来源：巴别鸟FAQ（用户手册） / word/media/image7.png 静态路径： assets/images/faq/faq 133.png FAQ 图片索引图片 133 FAQ 图片索引图片 133，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 134 来源：巴别鸟FAQ（用户手册） / word/media/image70.png 静态路径： assets/images/faq/faq 134.png FAQ 图片索引图片 134 FAQ 图片索引图片 134，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 135 来源：巴别鸟FAQ（用户手册） / word/media/image700.png 静态路径： assets/images/faq/faq 135.png FAQ 图片索引图片 135 FAQ 图片索引图片 135，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 136 来源：巴别鸟FAQ（用户手册） / word/media/image71.png 静态路径： assets/images/faq/faq 136.png FAQ 图片索引图片 136 FAQ 图片索引图片 136，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 137 来源：巴别鸟FAQ（用户手册） / word/media/image710.png 静态路径： assets/images/faq/faq 137.png FAQ 图片索引图片 137 FAQ 图片索引图片 137，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 138 来源：巴别鸟FAQ（用户手册） / word/media/image711.png 静态路径： assets/images/faq/faq 138.png FAQ 图片索引图片 138 FAQ 图片索引图片 138，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 139 来源：巴别鸟FAQ（用户手册） / word/media/image72.png 静态路径： assets/images/faq/faq 139.png FAQ 图片索引图片 139 FAQ 图片索引图片 139，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 140 来源：巴别鸟FAQ（用户手册） / word/media/image720.png 静态路径： assets/images/faq/faq 140.png FAQ 图片索引图片 140 FAQ 图片索引图片 140，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 141 来源：巴别鸟FAQ（用户手册） / word/media/image73.png 静态路径： assets/images/faq/faq 141.png FAQ 图片索引图片 141 FAQ 图片索引图片 141，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 142 来源：巴别鸟FAQ（用户手册） / word/media/image730.png 静态路径： assets/images/faq/faq 142.png FAQ 图片索引图片 142 FAQ 图片索引图片 142，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 143 来源：巴别鸟FAQ（用户手册） / word/media/image74.png 静态路径： assets/images/faq/faq 143.png FAQ 图片索引图片 143 FAQ 图片索引图片 143，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 144 来源：巴别鸟FAQ（用户手册） / word/media/image740.png 静态路径： assets/images/faq/faq 144.png FAQ 图片索引图片 144 FAQ 图片索引图片 144，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 145 来源：巴别鸟FAQ（用户手册） / word/media/image75.png 静态路径： assets/images/faq/faq 145.png FAQ 图片索引图片 145 FAQ 图片索引图片 145，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 146 来源：巴别鸟FAQ（用户手册） / word/media/image750.png 静态路径： assets/images/faq/faq 146.png FAQ 图片索引图片 146 FAQ 图片索引图片 146，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 147 来源：巴别鸟FAQ（用户手册） / word/media/image76.png 静态路径： assets/images/faq/faq 147.png FAQ 图片索引图片 147 FAQ 图片索引图片 147，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 148 来源：巴别鸟FAQ（用户手册） / word/media/image760.png 静态路径： assets/images/faq/faq 148.png FAQ 图片索引图片 148 FAQ 图片索引图片 148，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 149 来源：巴别鸟FAQ（用户手册） / word/media/image77.png 静态路径： assets/images/faq/faq 149.png FAQ 图片索引图片 149 FAQ 图片索引图片 149，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 150 来源：巴别鸟FAQ（用户手册） / word/media/image770.png 静态路径： assets/images/faq/faq 150.png FAQ 图片索引图片 150 FAQ 图片索引图片 150，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 151 来源：巴别鸟FAQ（用户手册） / word/media/image78.png 静态路径： assets/images/faq/faq 151.png FAQ 图片索引图片 151 FAQ 图片索引图片 151，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 152 来源：巴别鸟FAQ（用户手册） / word/media/image780.png 静态路径： assets/images/faq/faq 152.png FAQ 图片索引图片 152 FAQ 图片索引图片 152，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 153 来源：巴别鸟FAQ（用户手册） / word/media/image79.png 静态路径： assets/images/faq/faq 153.png FAQ 图片索引图片 153 FAQ 图片索引图片 153，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 154 来源：巴别鸟FAQ（用户手册） / word/media/image790.png 静态路径： assets/images/faq/faq 154.png FAQ 图片索引图片 154 FAQ 图片索引图片 154，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 155 来源：巴别鸟FAQ（用户手册） / word/media/image8.png 静态路径： assets/images/faq/faq 155.png FAQ 图片索引图片 155 FAQ 图片索引图片 155，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 156 来源：巴别鸟FAQ（用户手册） / word/media/image80.png 静态路径： assets/images/faq/faq 156.png FAQ 图片索引图片 156 FAQ 图片索引图片 156，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 157 来源：巴别鸟FAQ（用户手册） / word/media/image800.png 静态路径： assets/images/faq/faq 157.png FAQ 图片索引图片 157 FAQ 图片索引图片 157，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 158 来源：巴别鸟FAQ（用户手册） / word/media/image81.png 静态路径： assets/images/faq/faq 158.png FAQ 图片索引图片 158 FAQ 图片索引图片 158，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 159 来源：巴别鸟FAQ（用户手册） / word/media/image810.png 静态路径： assets/images/faq/faq 159.png FAQ 图片索引图片 159 FAQ 图片索引图片 159，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 160 来源：巴别鸟FAQ（用户手册） / word/media/image811.png 静态路径： assets/images/faq/faq 160.png FAQ 图片索引图片 160 FAQ 图片索引图片 160，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 161 来源：巴别鸟FAQ（用户手册） / word/media/image82.png 静态路径： assets/images/faq/faq 161.png FAQ 图片索引图片 161 FAQ 图片索引图片 161，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 162 来源：巴别鸟FAQ（用户手册） / word/media/image820.png 静态路径： assets/images/faq/faq 162.png FAQ 图片索引图片 162 FAQ 图片索引图片 162，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 163 来源：巴别鸟FAQ（用户手册） / word/media/image83.png 静态路径： assets/images/faq/faq 163.png FAQ 图片索引图片 163 FAQ 图片索引图片 163，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 164 来源：巴别鸟FAQ（用户手册） / word/media/image830.png 静态路径： assets/images/faq/faq 164.png FAQ 图片索引图片 164 FAQ 图片索引图片 164，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 165 来源：巴别鸟FAQ（用户手册） / word/media/image84.png 静态路径： assets/images/faq/faq 165.png FAQ 图片索引图片 165 FAQ 图片索引图片 165，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 166 来源：巴别鸟FAQ（用户手册） / word/media/image840.png 静态路径： assets/images/faq/faq 166.png FAQ 图片索引图片 166 FAQ 图片索引图片 166，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 167 来源：巴别鸟FAQ（用户手册） / word/media/image85.png 静态路径： assets/images/faq/faq 167.png FAQ 图片索引图片 167 FAQ 图片索引图片 167，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 168 来源：巴别鸟FAQ（用户手册） / word/media/image850.png 静态路径： assets/images/faq/faq 168.png FAQ 图片索引图片 168 FAQ 图片索引图片 168，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 169 来源：巴别鸟FAQ（用户手册） / word/media/image86.png 静态路径： assets/images/faq/faq 169.png FAQ 图片索引图片 169 FAQ 图片索引图片 169，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 170 来源：巴别鸟FAQ（用户手册） / word/media/image860.png 静态路径： assets/images/faq/faq 170.png FAQ 图片索引图片 170 FAQ 图片索引图片 170，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 171 来源：巴别鸟FAQ（用户手册） / word/media/image87.png 静态路径： assets/images/faq/faq 171.png FAQ 图片索引图片 171 FAQ 图片索引图片 171，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 172 来源：巴别鸟FAQ（用户手册） / word/media/image870.png 静态路径： assets/images/faq/faq 172.png FAQ 图片索引图片 172 FAQ 图片索引图片 172，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 173 来源：巴别鸟FAQ（用户手册） / word/media/image88.png 静态路径： assets/images/faq/faq 173.png FAQ 图片索引图片 173 FAQ 图片索引图片 173，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 174 来源：巴别鸟FAQ（用户手册） / word/media/image880.png 静态路径： assets/images/faq/faq 174.png FAQ 图片索引图片 174 FAQ 图片索引图片 174，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 175 来源：巴别鸟FAQ（用户手册） / word/media/image89.png 静态路径： assets/images/faq/faq 175.png FAQ 图片索引图片 175 FAQ 图片索引图片 175，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 176 来源：巴别鸟FAQ（用户手册） / word/media/image890.png 静态路径： assets/images/faq/faq 176.png FAQ 图片索引图片 176 FAQ 图片索引图片 176，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 177 来源：巴别鸟FAQ（用户手册） / word/media/image9.png 静态路径： assets/images/faq/faq 177.png FAQ 图片索引图片 177 FAQ 图片索引图片 177，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 178 来源：巴别鸟FAQ（用户手册） / word/media/image90.png 静态路径： assets/images/faq/faq 178.png FAQ 图片索引图片 178 FAQ 图片索引图片 178，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 179 来源：巴别鸟FAQ（用户手册） / word/media/image900.png 静态路径： assets/images/faq/faq 179.png FAQ 图片索引图片 179 FAQ 图片索引图片 179，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 180 来源：巴别鸟FAQ（用户手册） / word/media/image91.png 静态路径： assets/images/faq/faq 180.png FAQ 图片索引图片 180 FAQ 图片索引图片 180，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 181 来源：巴别鸟FAQ（用户手册） / word/media/image910.png 静态路径： assets/images/faq/faq 181.png FAQ 图片索引图片 181 FAQ 图片索引图片 181，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 182 来源：巴别鸟FAQ（用户手册） / word/media/image92.png 静态路径： assets/images/faq/faq 182.png FAQ 图片索引图片 182 FAQ 图片索引图片 182，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 183 来源：巴别鸟FAQ（用户手册） / word/media/image920.png 静态路径： assets/images/faq/faq 183.png FAQ 图片索引图片 183 FAQ 图片索引图片 183，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 184 来源：巴别鸟FAQ（用户手册） / word/media/image93.png 静态路径： assets/images/faq/faq 184.png FAQ 图片索引图片 184 FAQ 图片索引图片 184，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 185 来源：巴别鸟FAQ（用户手册） / word/media/image930.png 静态路径： assets/images/faq/faq 185.png FAQ 图片索引图片 185 FAQ 图片索引图片 185，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 186 来源：巴别鸟FAQ（用户手册） / word/media/image94.png 静态路径： assets/images/faq/faq 186.png FAQ 图片索引图片 186 FAQ 图片索引图片 186，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 187 来源：巴别鸟FAQ（用户手册） / word/media/image940.png 静态路径： assets/images/faq/faq 187.png FAQ 图片索引图片 187 FAQ 图片索引图片 187，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 188 来源：巴别鸟FAQ（用户手册） / word/media/image95.png 静态路径： assets/images/faq/faq 188.png FAQ 图片索引图片 188 FAQ 图片索引图片 188，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "lang": "en", "slug": "maintenance", "title": "Maintenance and release", "description": "Describes how to maintain, build, debug and upload babelwiki static directories locally.", "category": "Maintenance", "top_category": "维护", "keywords": [ "maintain", "local debugging", "release" ], "url": "en/maintenance.html", "source": "content/en/maintenance.md", "summary": "维护与发布 本地维护 文档源文件位于 babelwiki/content/zh 和 babelwiki/content/en 。推荐流程是先更新 DOC 目录中的源文档或产品截图，再运行重建脚本生成 Markdown 和 HTML。 本地构建 本地预览 浏览器打开 http://127.0.0.1:8080/ 即可调试，根目录会直接显示中文“概况”文档页。 上传发布 将 babelwiki 整个目录上传到 www.babel.cc 对应目录，使其可通过 https://www.babel.cc/babelwiki/ 访问。上传后建议检查： index.html zh/overview.html llms.txt llms full.txt ai index.json developer api index.json image index.json sitemap.xml", "headings": [ { "level": 1, "title": "维护与发布", "id": "section" }, { "level": 2, "title": "本地维护", "id": "section-2" }, { "level": 2, "title": "本地构建", "id": "section-3" }, { "level": 2, "title": "本地预览", "id": "section-4" }, { "level": 2, "title": "上传发布", "id": "section-5" } ], "images": [], "text": "维护与发布 本地维护 文档源文件位于 babelwiki/content/zh 和 babelwiki/content/en 。推荐流程是先更新 DOC 目录中的源文档或产品截图，再运行重建脚本生成 Markdown 和 HTML。 本地构建 本地预览 浏览器打开 http://127.0.0.1:8080/ 即可调试，根目录会直接显示中文“概况”文档页。 上传发布 将 babelwiki 整个目录上传到 www.babel.cc 对应目录，使其可通过 https://www.babel.cc/babelwiki/ 访问。上传后建议检查： index.html zh/overview.html llms.txt llms full.txt ai index.json developer api index.json image index.json sitemap.xml" }, { "lang": "en", "slug": "terms", "title": "terms agreement", "description": "Sub-topic entrance to BabelBird’s Terms of Service.", "category": "Terms And Agreements", "top_category": "条款协议", "keywords": [ "Terms", "protocol", "Terms of Service" ], "url": "en/terms.html", "source": "content/en/terms.md", "summary": "Terms Agreement The terms agreement summarizes the BabelBird service form, the rights and obligations of both parties, intellectual property rights, confidentiality, risks, breach of contract, legal disputes and after sales service related content. Terms Agreement Overview: Scope of application of terms of service, service form and reading entrance. Free Service Terms: Free service registration, information authenticity and user responsibilities. [Enterprise Public Cloud Service Terms] (terms public cloud.md): Public cloud service activation, time limit, upgrade, renewal, termination and order contract. Enterprise Privatization Service Terms: Private cloud deployment, authorization time limi", "headings": [ { "level": 1, "title": "Terms Agreement", "id": "terms-agreement" } ], "images": [], "text": "Terms Agreement The terms agreement summarizes the BabelBird service form, the rights and obligations of both parties, intellectual property rights, confidentiality, risks, breach of contract, legal disputes and after sales service related content. Terms Agreement Overview: Scope of application of terms of service, service form and reading entrance. Free Service Terms: Free service registration, information authenticity and user responsibilities. [Enterprise Public Cloud Service Terms] (terms public cloud.md): Public cloud service activation, time limit, upgrade, renewal, termination and order contract. Enterprise Privatization Service Terms: Private cloud deployment, authorization time limit, maintenance fees, upgrades and order contracts. Party A’s rights and obligations: customer account, administrator, usage behavior and security responsibilities. Service Party Rights and Obligations: Service Party management rights, data disclosure boundaries, terms adjustment and service termination rights. Intellectual Property and Confidentiality: Software intellectual property rights, trademarks, data ownership and confidentiality obligations of both parties. Service Risk and Disclaimer: Force majeure, network risk, content liability, user operation risk and third party transaction risk. Liability for breach of contract and service changes: Liability for breach of contract, service changes, interruption, termination and modification of terms. Legal disputes and after sales service: applicable law, dispute resolution, after sales service, maintenance, free services and VIP services." }, { "lang": "en", "slug": "terms-overview", "title": "Terms Agreement Overview", "description": "Scope of service, service form and reading entrance.", "category": "Terms And Agreements", "top_category": "条款协议", "keywords": [ "Terms", "Terms Agreement Overview" ], "url": "en/terms-overview.html", "source": "content/en/terms-overview.md", "summary": "Terms Agreement Overview Service description Shanghai Huaqing Information Technology Co., Ltd. provides services to corporate customers through the following methods: A website with the domain name babe.cc; The Babel privatized system is privately deployed for customers in the customer's computer room or cloud space managed by the customer; Shanghai Huaqing Information Technology Co., Ltd. has released a desktop client program called \"BabelBird\"; Shanghai Huaqing Information Technology Co., Ltd. has released a smart mobile application called \"BabelBird\" (including but not limited to iOS, Android systems). BabelBird's Terms of Service (hereinafter referred to as the \"Terms of Service\") apply ", "headings": [ { "level": 1, "title": "Terms Agreement Overview", "id": "terms-agreement-overview" } ], "images": [], "text": "Terms Agreement Overview Service description Shanghai Huaqing Information Technology Co., Ltd. provides services to corporate customers through the following methods: A website with the domain name babe.cc; The Babel privatized system is privately deployed for customers in the customer's computer room or cloud space managed by the customer; Shanghai Huaqing Information Technology Co., Ltd. has released a desktop client program called \"BabelBird\"; Shanghai Huaqing Information Technology Co., Ltd. has released a smart mobile application called \"BabelBird\" (including but not limited to iOS, Android systems). BabelBird's Terms of Service (hereinafter referred to as the \"Terms of Service\") apply to all applications provided in BabelBird. However, when Party A uses a specific service of BabelBird, if the service has separate service terms, guidelines or rules, it shall become an additional term to these Terms, and Party A shall abide by these Terms together. The normal realization of BabelBird and its functions is predicated on the correct performance of management actions by Party A and the correct completion of system settings. If Party A violates relevant laws, regulations and the provisions of these Terms of Service, it must bear full legal responsibility and bear legal responsibility for the losses caused to Shanghai Huaqing Information Technology Co., Ltd." }, { "lang": "en", "slug": "terms-free-saas", "title": "Free service terms", "description": "Free Service Registration, Information Authenticity and User Responsibility.", "category": "Terms And Agreements", "top_category": "条款协议", "keywords": [ "Terms", "Free service terms" ], "url": "en/terms-free-saas.html", "source": "content/en/terms-free-saas.md", "summary": "Free service terms BabelBird free service (based on SaaS) On the basis of understanding and agreeing to these terms, Party A can apply to register a BabelBird account to use BabelBird's free services. BabelBird's free service includes basic functions of the free version, limited time trial functions, etc. Details are subject to the announcement on the BabelBird website. Party A understands and agrees to provide true and valid corporate information (such as contact person, contact number, email address, etc.) when registering BabelBird. Shanghai Huaqing Information Technology Co., Ltd. has the right to stop users who provide false registration information from using BabelBird’s free services.", "headings": [ { "level": 1, "title": "Free service terms", "id": "free-service-terms" } ], "images": [], "text": "Free service terms BabelBird free service (based on SaaS) On the basis of understanding and agreeing to these terms, Party A can apply to register a BabelBird account to use BabelBird's free services. BabelBird's free service includes basic functions of the free version, limited time trial functions, etc. Details are subject to the announcement on the BabelBird website. Party A understands and agrees to provide true and valid corporate information (such as contact person, contact number, email address, etc.) when registering BabelBird. Shanghai Huaqing Information Technology Co., Ltd. has the right to stop users who provide false registration information from using BabelBird’s free services. Party A understands and agrees that Party A and Party A's users must unconditionally accept all terms of these Terms of Service before registering to use BabelBird's free services, and shall bear legal responsibility for all consequences arising from violations of national laws and these Terms of Service." }, { "lang": "en", "slug": "terms-public-cloud", "title": "Enterprise Public Cloud Service Terms", "description": "Public cloud service activation, time limit, upgrade, renewal, termination and order contract.", "category": "Terms And Agreements", "top_category": "条款协议", "keywords": [ "Terms", "Enterprise Public Cloud Service Terms" ], "url": "en/terms-public-cloud.html", "source": "content/en/terms-public-cloud.md", "summary": "Enterprise Public Cloud Service Terms Babel Enterprise Public Cloud Edition Service (based on SaaS) Activate the enterprise public cloud version service. When Party A purchases the BabelBird Enterprise Public Cloud Edition, he can contact the relevant customer service and complete the payment. After the payment is successful, the BabelBird Enterprise Public Cloud Edition purchased by Party A will be activated in time. Enterprise public cloud version service time limit. The enterprise public cloud service time limit is based on the \"purchase duration\" selected by Party A when purchasing the BabelBird enterprise public cloud service, and the unit is \"years\". Enterprise public cloud version ser", "headings": [ { "level": 1, "title": "Enterprise Public Cloud Service Terms", "id": "enterprise-public-cloud-service-terms" } ], "images": [], "text": "Enterprise Public Cloud Service Terms Babel Enterprise Public Cloud Edition Service (based on SaaS) Activate the enterprise public cloud version service. When Party A purchases the BabelBird Enterprise Public Cloud Edition, he can contact the relevant customer service and complete the payment. After the payment is successful, the BabelBird Enterprise Public Cloud Edition purchased by Party A will be activated in time. Enterprise public cloud version service time limit. The enterprise public cloud service time limit is based on the \"purchase duration\" selected by Party A when purchasing the BabelBird enterprise public cloud service, and the unit is \"years\". Enterprise public cloud version service upgrade. When Shanghai Huaqing Information Technology Co., Ltd. upgrades the BabelBird Enterprise public cloud version service, the public cloud version used by Party A will be automatically upgraded without paying other fees. Enterprise public cloud version service renewal. One month before the expiration of the BabelBird Enterprise Public Cloud Edition service purchased by Party A through the public cloud, Shanghai Huaqing Information Technology Co., Ltd. will notify Party A to renew the fee. The renewal price shall be subject to the official announcement of Shanghai Huaqing Information Technology Co., Ltd. If Party A fails to renew the enterprise public cloud version service after expiration, Shanghai Huaqing Information Technology Co., Ltd. will stop providing Party A with the expired part of the enterprise public cloud version service. The enterprise public cloud version service is terminated. If Party A fails to renew the BabelBird Enterprise Public Cloud Edition service it purchased after it expires, Party A will be deemed to have automatically given up the BabelBird Enterprise Public Cloud Edition service, and Party A's expired Enterprise Public Cloud Edition service will be restricted or locked. Babel Order Contract. After purchasing the BabelBird Enterprise Public Cloud Edition service, Party A can sign the [BabelBird Enterprise Edition (Public Cloud) Software License Agreement] with Shanghai Huaqing Information Co., Ltd. [BabelBird Enterprise Edition (Public Cloud) Software License Agreement] is a written agreement between Shanghai Huaqing Information Co., Ltd. and Party A regarding BabelBird services and fees." }, { "lang": "en", "slug": "terms-private-cloud", "title": "Enterprise Privatization Service Terms", "description": "Private cloud deployment, licensing time limit, maintenance fees, upgrades and order contracts.", "category": "Terms And Agreements", "top_category": "条款协议", "keywords": [ "Terms", "Enterprise Privatization Service Terms" ], "url": "en/terms-private-cloud.html", "source": "content/en/terms-private-cloud.md", "summary": "Enterprise Privatization Service Terms Babel Enterprise Privatization Services Shanghai Huaqing Information Technology Co., Ltd. only provides BabelBird deployment and BabelBird privatization authorization services. The hardware and environment required for deployment shall be prepared and maintained by Party A. Deploy enterprise private cloud version. After Party A purchases the BabelBird enterprise private cloud version, Shanghai Huaqing Information Technology will deploy and debug it based on the project selected by Party A when signing the contract (see the agreement attachment service order for details). Enterprise private cloud version service time limit. The account authorization peri", "headings": [ { "level": 1, "title": "Enterprise Privatization Service Terms", "id": "enterprise-privatization-service-terms" } ], "images": [], "text": "Enterprise Privatization Service Terms Babel Enterprise Privatization Services Shanghai Huaqing Information Technology Co., Ltd. only provides BabelBird deployment and BabelBird privatization authorization services. The hardware and environment required for deployment shall be prepared and maintained by Party A. Deploy enterprise private cloud version. After Party A purchases the BabelBird enterprise private cloud version, Shanghai Huaqing Information Technology will deploy and debug it based on the project selected by Party A when signing the contract (see the agreement attachment service order for details). Enterprise private cloud version service time limit. The account authorization period for the enterprise private cloud version is lifetime authorization, and customer service support and upgrade services are provided on an annual basis. Maintenance fee is free for the first year after purchase. Enterprise private cloud version service upgrade. When Shanghai Huaqing Information Technology Co., Ltd. upgrades the BabelBird Enterprise Private Cloud Edition service, it will notify Party A as soon as possible, and Party A will decide whether to upgrade. If Party A agrees to the upgrade, the service will be upgraded remotely without paying other fees. Enterprise private cloud version maintenance fee. The BabelBird enterprise private cloud version is a lifetime license, but if you need Shanghai Huaqing Information Technology Co., Ltd. to provide corresponding training, Q&A, system bug correction, and system upgrade services, you will need to pay maintenance fees. After purchasing the enterprise private cloud version, maintenance fees are free in the first year. Starting from the second year, Party A needs to pay corresponding maintenance fees as stipulated in the contract. If Party A fails to pay the maintenance fee overdue, it will be deemed that Party A has given up all services under these Terms of Service. Babel Order Contract. After purchasing the BabelBird Enterprise Private Cloud Edition service, Party A can sign the [BabelBird Private Cloud Software License Agreement] with Shanghai Huaqing Information Co., Ltd. [BabelBird Private Cloud Software License Agreement] is a written agreement between Shanghai Huaqing Information Co., Ltd. and Party A regarding BabelBird services and fees." }, { "lang": "en", "slug": "terms-customer-obligations", "title": "Party A’s rights and obligations", "description": "Customer accounts, administrators, usage practices and security responsibilities.", "category": "Terms And Agreements", "top_category": "条款协议", "keywords": [ "Terms", "Party A’s rights and obligations" ], "url": "en/terms-customer-obligations.html", "source": "content/en/terms-customer-obligations.md", "summary": "Party A’s rights and obligations Party A’s rights and obligations Party A must equip itself with the equipment needed to connect to the Internet and use the public cloud version of telecommunications companies, and bear all related costs such as communication fees, information fees, traffic fees, etc. charged by personal Internet access or third parties (including but not limited to telecommunications or mobile communication providers). If it involves telecom enterprise public cloud version services, we recommend that you confirm the relevant cost issues with your telecom enterprise public cloud version service provider. Party A shall not use BabelBird to send or transmit any information tha", "headings": [ { "level": 1, "title": "Party A’s rights and obligations", "id": "party-a-s-rights-and-obligations" } ], "images": [], "text": "Party A’s rights and obligations Party A’s rights and obligations Party A must equip itself with the equipment needed to connect to the Internet and use the public cloud version of telecommunications companies, and bear all related costs such as communication fees, information fees, traffic fees, etc. charged by personal Internet access or third parties (including but not limited to telecommunications or mobile communication providers). If it involves telecom enterprise public cloud version services, we recommend that you confirm the relevant cost issues with your telecom enterprise public cloud version service provider. Party A shall not use BabelBird to send or transmit any information that hinders public order or is illegal, false, harassing, insulting, threatening, harmful, destructive, provocative, obscene and pornographic. Party A must be responsible for the management of member users within its system, such as adding (deleting) accounts, setting user passwords and other management actions. Party A must assign a dedicated system administrator to maintain and manage its BabelBird account. Party A is responsible for the actions of Party A's administrator, and Party A is responsible for the consequences and responsibilities of the management actions. Party A and its users shall maintain the confidentiality and security of their own accounts and passwords. Party A and its users shall not transfer or lend their accounts or passwords to third parties. Shanghai Huaqing Information Technology Co., Ltd. cannot detect the illegal or unauthorized use of its account and password by a third party, so Shanghai Huaqing Information Technology Co., Ltd. does not assume any responsibility. Here, Party A agrees and commits to: When Party A and Party A's users' accounts and passwords are used without authorization, or any other security issues occur, Party A will immediately notify Shanghai Huaqing Information Technology Co., Ltd. Party A and its users must click to exit BabelBird every time they finish using the BabelBird system. Party A has clearly understood that BabelBird can only be used internally by Party A. Unless otherwise agreed, Party A may not transfer, distribute, or buy or sell its Party A account." }, { "lang": "en", "slug": "terms-company-obligations", "title": "Service Party Rights and Obligations", "description": "Service provider management rights, data disclosure boundaries, terms adjustment and service termination rights.", "category": "Terms And Agreements", "top_category": "条款协议", "keywords": [ "Terms", "Service Party Rights and Obligations" ], "url": "en/terms-company-obligations.html", "source": "content/en/terms-company-obligations.md", "summary": "Service Party Rights and Obligations Rights and obligations of Shanghai Huaqing Information Technology Co., Ltd. Shanghai Huaqing Information Technology Co., Ltd. is obliged to provide Party A with the management rights of BabelBird, so that Party A can make system related settings for Party A’s users. Shanghai Huaqing Information Technology Co., Ltd. shall not disclose, edit or disclose any data stored in BabelBird by Party A and Party A’s users. Except for the following circumstances Obtain explicit written authorization from Party A in advance; According to the requirements of the national security agencies and public security departments of the People's Republic of China or in accordance", "headings": [ { "level": 1, "title": "Service Party Rights and Obligations", "id": "service-party-rights-and-obligations" } ], "images": [], "text": "Service Party Rights and Obligations Rights and obligations of Shanghai Huaqing Information Technology Co., Ltd. Shanghai Huaqing Information Technology Co., Ltd. is obliged to provide Party A with the management rights of BabelBird, so that Party A can make system related settings for Party A’s users. Shanghai Huaqing Information Technology Co., Ltd. shall not disclose, edit or disclose any data stored in BabelBird by Party A and Party A’s users. Except for the following circumstances Obtain explicit written authorization from Party A in advance; According to the requirements of the national security agencies and public security departments of the People's Republic of China or in accordance with relevant legal procedures or the requirements to safeguard social and public interests. If Party A or Party A's users violate the terms of this service or legal provisions, Shanghai Huaqing Information Technology Co., Ltd. has the right to interrupt or terminate the BabelBird service and the remaining service fees will not be refunded. Shanghai Huaqing Information Technology Co., Ltd. has the right to adjust or update the content of these Terms of Service based on the actual situation. Shanghai Huaqing Information Technology Co., Ltd. is obliged to notify Party A and make an obvious announcement on the BabelBird official website or BabelBird system. Once the revised terms are announced, they will effectively replace the original terms. The new terms are applicable to all BabelBird free service users and all BabelBird enterprise public cloud version service users. If Party A and Party A's users violate national laws and regulations or these Terms of Service, Shanghai Huaqing Information Technology Co., Ltd. has the right to immediately stop providing services to Party A without assuming any responsibility." }, { "lang": "en", "slug": "terms-ip-confidentiality", "title": "Intellectual Property and Confidentiality", "description": "Software intellectual property rights, trademarks, data ownership and confidentiality obligations of both parties.", "category": "Terms And Agreements", "top_category": "条款协议", "keywords": [ "Terms", "Intellectual Property and Confidentiality" ], "url": "en/terms-ip-confidentiality.html", "source": "content/en/terms-ip-confidentiality.md", "summary": "Intellectual Property and Confidentiality Intellectual property rights, confidentiality clauses The ownership of BabelBird and all intellectual property rights based on BabelBird (including but not limited to patent rights, trademark rights, copyrights, computer software copyrights, etc.) belong to Shanghai Huaqing Information Technology Co., Ltd. Shanghai Huaqing Information Technology Co., Ltd.’s ownership of BabelBird does not include the data stored in the BabelBird server by Party A and Party A’s users. Shanghai Huaqing Information Technology Co., Ltd., Shanghai Huaqing Information Technology Co., Ltd. logo, BabelBird's logo, etc., as well as other Shanghai Huaqing Information Technolog", "headings": [ { "level": 1, "title": "Intellectual Property and Confidentiality", "id": "intellectual-property-and-confidentiality" } ], "images": [], "text": "Intellectual Property and Confidentiality Intellectual property rights, confidentiality clauses The ownership of BabelBird and all intellectual property rights based on BabelBird (including but not limited to patent rights, trademark rights, copyrights, computer software copyrights, etc.) belong to Shanghai Huaqing Information Technology Co., Ltd. Shanghai Huaqing Information Technology Co., Ltd.’s ownership of BabelBird does not include the data stored in the BabelBird server by Party A and Party A’s users. Shanghai Huaqing Information Technology Co., Ltd., Shanghai Huaqing Information Technology Co., Ltd. logo, BabelBird's logo, etc., as well as other Shanghai Huaqing Information Technology Co., Ltd. logos and product and service names are trademarks of Shanghai Huaqing Information Technology Co., Ltd. (hereinafter referred to as the \"Shanghai Huaqing Information Technology Co., Ltd. logo\"). Without the prior written consent of Shanghai Huaqing Information Technology Co., Ltd., Party A shall not display or use the Shanghai Huaqing Information Technology Co., Ltd. logo in any way or otherwise process it, nor may it indicate to others that Party A has the right to display, use, or otherwise process the Shanghai Huaqing Information Technology Co., Ltd. logo. Party A is obliged to protect the intellectual property rights of Shanghai Huaqing Information Technology Co., Ltd. from third parties. Party A and Party A's users shall not use or copy the software and data related to BabelBird, and shall not allow third parties to steal any data and software of BabelBird. The data does not include the data stored by Party A and Party A's users in the Babel server. Either party A and Shanghai Huaqing Information Technology Co., Ltd. are obliged to keep confidential the technical and commercial secrets of the other party and Shanghai Huaqing Information Technology Co., Ltd. that they learn during the cooperation process and that have not been disclosed to the public. Without the written permission of the other party, neither party shall disclose it to a third party, otherwise it shall bear liability for breach of contract and compensate for losses." }, { "lang": "en", "slug": "terms-risk-disclaimer", "title": "Service Risks and Disclaimers", "description": "Force majeure, network risks, content liability, user operation risks and third-party transaction risks.", "category": "Terms And Agreements", "top_category": "条款协议", "keywords": [ "Terms", "Service Risks and Disclaimers" ], "url": "en/terms-risk-disclaimer.html", "source": "content/en/terms-risk-disclaimer.md", "summary": "Service Risks and Disclaimers Service risks, disclaimers Party A has clearly understood that the BabelBird service is only provided based on its current situation. The BabelBird service involves Internet and mobile data communication services, and may be affected by unstable factors in various links. Therefore, the service is subject to the risk of service interruption or failure to meet user requirements due to the above mentioned force majeure, floods, earthquakes, typhoons, fires and other natural disasters, wars, computer viruses or hacker attacks, various crimes based on computer systems and networks, government actions, system errors or instability, user location, user shutdown, GSM ne", "headings": [ { "level": 1, "title": "Service Risks and Disclaimers", "id": "service-risks-and-disclaimers" } ], "images": [], "text": "Service Risks and Disclaimers Service risks, disclaimers Party A has clearly understood that the BabelBird service is only provided based on its current situation. The BabelBird service involves Internet and mobile data communication services, and may be affected by unstable factors in various links. Therefore, the service is subject to the risk of service interruption or failure to meet user requirements due to the above mentioned force majeure, floods, earthquakes, typhoons, fires and other natural disasters, wars, computer viruses or hacker attacks, various crimes based on computer systems and networks, government actions, system errors or instability, user location, user shutdown, GSM network instability, 3G network instability, Internet network line failure, backbone network communication line failure, etc., resulting in losses to Party A. Party A is required to bear the above risks. Shanghai Huaqing Information Technology Co., Ltd. does not provide any express or tacit guarantee of the marketability, applicability, reliability, timeliness, security, completeness, virus free and error free of BabelBird, and is not responsible for any direct, indirect, incidental, derivative or punitive compensation caused to Party A as a result. If the failure of BabelBird affects the normal use of Party A, Shanghai Huaqing Information Technology Co., Ltd. promises to cooperate with relevant units as soon as possible to handle and repair it in a timely manner. Shanghai Huaqing Information Technology Co., Ltd. reserves the right to suspend any part of BabelBird for maintenance, upgrades or other purposes without prior notice. Service suspensions that occur during this period, or service application failures caused by accidental network access congestion, are normal circumstances and cannot be regarded as a breach of contract by Shanghai Huaqing Information Technology Co., Ltd. Party A agrees that Party A and Party A's users shall bear full legal responsibility for the information, materials, text, software, music, audio, photos, pictures, videos, information, resource links, user registration information or other materials (hereinafter referred to as \"content\") uploaded, posted, sent instant messages, emails or other means through BabelBird, and Shanghai Huaqing Information Technology Co., Ltd. shall not assume any direct, indirect, or joint liability. Since Shanghai Huaqing Information Technology Co., Ltd. cannot control the content transmitted through BabelBird, nor can it comprehensively monitor the user's usage behavior, it does not guarantee the legality, accuracy, integrity, authenticity or quality of Party A's content. If Party A's content may infringe the copyright of a third party, Shanghai Huaqing Information Technology Co., Ltd. will handle it in accordance with national laws and regulations. Party A has clearly understood and understood that Party A users must accept these Terms of Service if they want to use BabelBird. When some or all of Party A's users do not accept or agree to these Terms of Service and are unable to use BabelBird, Party A still agrees to pay service fees to Shanghai Huaqing Information Technology Co., Ltd. Party A promises to be fully responsible for any losses caused by Party A, Party A's system administrator, and Party A's users due to incorrect operation of BabelBird. These erroneous operations include but are not limited to data loss caused by Party A's system administrator mistakenly deleting Party A's users, Party A's users mistakenly deleting shared data in Party A's corporate network disk, etc. Party A and Party A's users have clearly understood that any form of communication or business dealings, or participation in promotional activities, with merchants or individuals through BabelBird, including the payment and delivery of related goods or services, as well as any other relevant terms, conditions, guarantees or certifications reached, are entirely between Party A and Party A's members and merchants and other individuals. Unless the relevant laws expressly require Shanghai Huaqing Information Technology Co., Ltd. to assume responsibility, Shanghai Huaqing Information Technology Co., Ltd. will not be responsible for any loss or damage of any nature suffered by Party A due to any of the above transactions or the above mentioned merchants or individuals." }, { "lang": "en", "slug": "terms-liability-change", "title": "Liability for breach of contract and service changes", "description": "Liability for breach of contract, service changes, interruptions, terminations and modifications to terms.", "category": "Terms And Agreements", "top_category": "条款协议", "keywords": [ "Terms", "Liability for breach of contract and service changes" ], "url": "en/terms-liability-change.html", "source": "content/en/terms-liability-change.md", "summary": "Liability for breach of contract and service changes Liability for breach of contract Party A must clearly understand and agree to these Terms of Service before using BabelBird, and shall bear legal responsibility for all consequences arising from violation of national laws and these Terms of Service. If Party A suffers losses while using BabelBird due to the negligence of Shanghai Huaqing Information Technology Co., Ltd., Party A has the right to notify Shanghai Huaqing Information Technology Co., Ltd. in writing to terminate its BabelBird account. After verification by Shanghai Huaqing Information Technology Co., Ltd., if Party A's situation is true, Shanghai Huaqing Information Technology", "headings": [ { "level": 1, "title": "Liability for breach of contract and service changes", "id": "liability-for-breach-of-contract-and-service-changes" } ], "images": [], "text": "Liability for breach of contract and service changes Liability for breach of contract Party A must clearly understand and agree to these Terms of Service before using BabelBird, and shall bear legal responsibility for all consequences arising from violation of national laws and these Terms of Service. If Party A suffers losses while using BabelBird due to the negligence of Shanghai Huaqing Information Technology Co., Ltd., Party A has the right to notify Shanghai Huaqing Information Technology Co., Ltd. in writing to terminate its BabelBird account. After verification by Shanghai Huaqing Information Technology Co., Ltd., if Party A's situation is true, Shanghai Huaqing Information Technology Co., Ltd. will refund Party A's balance (if any) after collecting the fees incurred from the service start date to the service termination date within 10 working days. Service changes, interruptions or terminations and modifications to the terms of service The ownership, operation rights and all interpretation rights of BabelBird belong to Shanghai Huaqing Information Technology Co., Ltd. Shanghai Huaqing Information Technology Co., Ltd. has the right to modify these terms at any time based on changes in relevant national laws and regulations, industry development, and adjustments to the company's operating conditions and business strategies. When Shanghai Huaqing Information Technology Co., Ltd. modifies the BabelBird service or these terms of service, it shall be implemented in accordance with item 6.4 of this article. Party A is obliged to carefully read and confirm the latest terms of service. When a relevant dispute occurs, the latest terms of service shall prevail. Shanghai Huaqing Information Technology Co., Ltd. reserves the right to adjust the prices and product trial periods of all applications in BabelBird. If any of the following circumstances occurs, Shanghai Huaqing Information Technology Co., Ltd. has the right to interrupt or terminate the provision of services to Party A at any time or disable certain Party A user accounts without notifying Party A: Party A violates the provisions of these Terms of Service; In accordance with the requirements of the national competent authorities; Other special circumstances that Shanghai Huaqing Information Technology Co., Ltd. considers to meet the overall service needs." }, { "lang": "en", "slug": "terms-law-support", "title": "Legal disputes and after-sales service", "description": "Legal application, dispute resolution, after-sales service, maintenance, free services and VIP services.", "category": "Terms And Agreements", "top_category": "条款协议", "keywords": [ "Terms", "Legal disputes and after-sales service" ], "url": "en/terms-law-support.html", "source": "content/en/terms-law-support.md", "summary": "Legal disputes and after sales service Legal and dispute resolution These terms of service must be consistent with relevant national laws and regulations. If there is any conflict with relevant laws and regulations, the conflicting parts shall prevail. If any dispute arises between the two parties but they cannot negotiate amicably, either party may file a lawsuit with the People's Court with jurisdiction in Shanghai where Shanghai Huaqing Information Technology Co., Ltd. is domiciled. After sales service provided by BabelBird Babel adopts a one on one dedicated service model, with a dedicated account manager responsible for providing services to customers. Name of maintenance unit: Shanghai", "headings": [ { "level": 1, "title": "Legal disputes and after sales service", "id": "legal-disputes-and-after-sales-service" } ], "images": [], "text": "Legal disputes and after sales service Legal and dispute resolution These terms of service must be consistent with relevant national laws and regulations. If there is any conflict with relevant laws and regulations, the conflicting parts shall prevail. If any dispute arises between the two parties but they cannot negotiate amicably, either party may file a lawsuit with the People's Court with jurisdiction in Shanghai where Shanghai Huaqing Information Technology Co., Ltd. is domiciled. After sales service provided by BabelBird Babel adopts a one on one dedicated service model, with a dedicated account manager responsible for providing services to customers. Name of maintenance unit: Shanghai Huaqing Information Technology Co., Ltd. The software maintenance period is one year. After the second year, customers need to pay the maintenance fee and enter the next round of software maintenance period. If the customer does not pay the service fee after the maintenance period expires, the customer can continue to use the system, but our company will no longer provide maintenance services until the annual service fee is paid. The service will continue. During the maintenance period, Shanghai Huaqing is responsible for providing maintenance and support for the program code and system configuration information of the software version within the scope of the contract, excluding the development of new functions caused by business changes and other factors. If the China Japan Friendship Hospital requires new functions and customized development services due to changes in business processes, the two parties will negotiate and determine the implementation plan. Free service content and scope Babel provides all paying customers with a lifetime free warranty service during the product life cycle, including: 5 24 hours telephone technical support service 24/7 emergency disaster recovery services Free online training, system usage guidance Report bugs as soon as possible and handle them quickly Software updates and upgrade services For enterprise users with more than 1,000 users, Babel provides lifetime free VIP services during the product life cycle, including: All free services for paying customers System construction and demand corresponding solution consulting services Initialize the system and complete the configuration on behalf of the customer Free data migration service (data less than 10TB) Free on site training once a year (if the number of users exceeds 10,000, there will be three free on site training opportunities per year) Exclusive key account manager responsibility system service For privatized users, on the premise that users pay normal annual service fees, they can enjoy the following free services: All free services for paying customers Free system upgrade and update service. Pure intranet users (intranet cannot connect to the Internet) can receive free on site upgrade and update service once a year. Initialize the system and complete the configuration on behalf of the customer Server performance optimization and troubleshooting Free on site training once a year and unlimited remote training For users of secondary development and function customization based on the BabelBird system, enjoy the following free services: All free services for paying customers Functional warranty and bug correction for the secondary development part Interface and function joint debugging services Comments and guidance services for secondary development codes and interfaces to facilitate redevelopment by users After completion acceptance, fine tuning and functional corrections (non bugs) will be made within our cost tolerance Charged services For redevelopment work on the existing system, the development hours and difficulty will be assessed based on needs, and settlement will be based on hours of work. Product design services. Help customers design product architecture, functions and interactions based on their new needs, and provide technical consultation. Paid on site training and debugging services. Users who have exhausted their free quota or do not meet the conditions for free door to door service can apply for a fee. The fee is 2,000 yuan per person for one day and reimbursement of transportation costs to the user's premises (high speed rail and local taxis) Services provided include the following: Serial number Service items Service content 1 First visit service Service staff proactively carry out first visit service 2 Return visit service Service staff proactively carry out return visit service 3 Routine software operation and maintenance services Program code maintenance of purchased software, such as patching software defects and installing and debugging software patches 4 System upgrade technical consulting Technical consulting services provided when the system is upgraded 5 Software upgrade notification When this version of the software is upgraded, customers will be notified in a timely manner Service methods include: Hotline support: Provide customers with answers to technical questions through the 400 hotline; E MAIL support: answer customer questions via E MAIL; Remote maintenance: remotely debug the Babel software in the customer environment. The customer needs to provide the environment required for remote maintenance. Otherwise, the customer will bear the responsibility for the resulting delay in after sales response time. On site service: If the problem cannot be solved by remote maintenance, our company will provide on site service. It is an on site service caused by problems of the application software itself and falls within the scope of free maintenance. Troubleshooting process When problems arise during customer use: Call the dedicated account manager immediately (or contact us via WeChat), and any issues that can be resolved will be resolved immediately; If the problem cannot be solved immediately, contact the technical personnel immediately, and the technical personnel will remotely assist the customer to solve the problem; If the problem is still unresolved, please report it to the account manager, who will arrange for technicians to provide on site service. Others If any provision of these Terms of Service is wholly or partially invalid or unenforceable for any reason, the remaining provisions of these Terms of Service shall remain valid and binding, and efforts shall be made to give effect to the intentions reflected in such provision. These Terms of Service constitute the entire agreement between Party A and Shanghai Huaqing Information Technology Co., Ltd., regulate your use of this service, and replace all previous agreements between you and Shanghai Huaqing Information Technology Co., Ltd. However, when Party A uses relevant services or uses content or software provided by third parties, it shall also comply with the applicable additional terms and rights. Shanghai Huaqing Information Technology Co., Ltd. reserves all rights of interpretation of these Terms of Service. Party A (seal): Party B (seal): Representative of Party A (signature): Representative of Party B (signature): Date: Date:" }, { "lang": "zh", "slug": "overview", "title": "概况", "description": "介绍巴别鸟企业网盘的产品定位、核心能力、适用对象和典型使用场景。", "category": "概况", "top_category": "使用指南", "keywords": [ "巴别鸟", "企业网盘", "文件协作", "权限安全", "v9.4.2" ], "url": "zh/overview.html", "source": "content/zh/overview.md", "summary": "巴别鸟企业网盘概况 巴别鸟企业网盘是面向企业非结构化数据管理、文件协作、安全管控、AI 知识库和私有化部署的产品平台。它把企业文件、部门资料、项目资料、素材库、档案库、在线编辑、权限审计、客户端同步、虚拟映射盘和智巢 AI 组织在同一个文件协作体系中，帮助企业把分散文件变成可管理、可协作、可追溯、可智能检索的数字资产。 巴别鸟首页与产品入口 首页展示了巴别鸟围绕企业网盘、AI 知识库、私有化部署和行业解决方案的整体定位。 产品定位 巴别鸟不是单纯的“上传下载网盘”。它更接近企业文件操作系统，覆盖文件从创建、上传、预览、编辑、同步、分享、评审、归档到审计的完整生命周期。对于私有化部署客户，巴别鸟还可以结合企业组织结构、统一身份认证、对象存储、内网部署、安全策略、第三方系统集成和专属 AI 知识库进行交付。 主要解决的问题 企业文件散落在个人电脑、聊天工具、移动硬盘、邮件附件和不同系统中，难以统一管理。 文件版本反复覆盖，缺少历史版本、变更记录、访问记录和可追溯的协作过程。 部门、项目、外部伙伴之间需要共享资料，但下载、外发、预览、编辑和有效期必须可控。 图片、图纸、合同、扫描件、视频、Office 文档等非结构化资料数量很大，传统目录检索效率不足。 企业希望在自己的文件和知识库上使用 AI，但需要遵守原有权限、安全和私有化要求。 核心能力 能力 说明 文件管理 个人文件、企业文件、部门文件夹、项目文件夹、素材库、档案库、多级目录、文件详情、标签、说明、排序和批量操作 协同编辑 Office 在线编辑、轻文档、Markdown/代码/文本、KM 思维导图、draw.io 流程图、本", "headings": [ { "level": 1, "title": "巴别鸟企业网盘概况", "id": "section" }, { "level": 2, "title": "产品定位", "id": "section-2" }, { "level": 2, "title": "主要解决的问题", "id": "section-3" }, { "level": 2, "title": "核心能力", "id": "section-4" }, { "level": 2, "title": "典型使用对象", "id": "section-5" }, { "level": 2, "title": "版本口径", "id": "section-6" }, { "level": 2, "title": "快速入口", "id": "section-7" } ], "images": [ { "src": "../assets/images/home.webp", "alt": "巴别鸟首页与产品入口", "caption": "首页展示了巴别鸟围绕企业网盘、AI 知识库、私有化部署和行业解决方案的整体定位。" } ], "text": "巴别鸟企业网盘概况 巴别鸟企业网盘是面向企业非结构化数据管理、文件协作、安全管控、AI 知识库和私有化部署的产品平台。它把企业文件、部门资料、项目资料、素材库、档案库、在线编辑、权限审计、客户端同步、虚拟映射盘和智巢 AI 组织在同一个文件协作体系中，帮助企业把分散文件变成可管理、可协作、可追溯、可智能检索的数字资产。 巴别鸟首页与产品入口 首页展示了巴别鸟围绕企业网盘、AI 知识库、私有化部署和行业解决方案的整体定位。 产品定位 巴别鸟不是单纯的“上传下载网盘”。它更接近企业文件操作系统，覆盖文件从创建、上传、预览、编辑、同步、分享、评审、归档到审计的完整生命周期。对于私有化部署客户，巴别鸟还可以结合企业组织结构、统一身份认证、对象存储、内网部署、安全策略、第三方系统集成和专属 AI 知识库进行交付。 主要解决的问题 企业文件散落在个人电脑、聊天工具、移动硬盘、邮件附件和不同系统中，难以统一管理。 文件版本反复覆盖，缺少历史版本、变更记录、访问记录和可追溯的协作过程。 部门、项目、外部伙伴之间需要共享资料，但下载、外发、预览、编辑和有效期必须可控。 图片、图纸、合同、扫描件、视频、Office 文档等非结构化资料数量很大，传统目录检索效率不足。 企业希望在自己的文件和知识库上使用 AI，但需要遵守原有权限、安全和私有化要求。 核心能力 能力 说明 文件管理 个人文件、企业文件、部门文件夹、项目文件夹、素材库、档案库、多级目录、文件详情、标签、说明、排序和批量操作 协同编辑 Office 在线编辑、轻文档、Markdown/代码/文本、KM 思维导图、draw.io 流程图、本地客户端编辑和文件锁定 版本与预览 自动生成历史版本、版本回滚、版本对比、100+ 格式在线预览、转码、批注、手绘和评审 分享与外发 邀请分享、链接分享、快照分享、外部协作、分享权限、有效期、密码、审批和分享日志 权限安全 企业角色、部门角色、项目权限、文件访问控制、自定义文件权限、水印、密级、审计日志、IP 策略、Mac 绑定、加密文件夹和敏感内容识别 客户端能力 Windows、macOS、麒麟客户端，支持上传下载、同步文件夹、虚拟映射盘、本地编辑和传输任务管理 素材与档案 素材库、瀑布流图片管理、图片元数据筛选、档案归档、阅览室、借阅审批和长期保存 自动化任务 自动清理、自动解压缩、自动重命名、自动整理、自动转 PDF、创建签章和批量创建文件夹 智巢 AI AI 搜索、智搜、文搜图、图搜图、OCR、文档助手、表格问答、企业知识库、知识库机器人、AI 自动标签、MCP 接口和私有化 AI 部署 私有化与集成 单机、集群、对象存储、信创环境、企业微信/钉钉/飞书、SSO、API、数据摆渡和定制开发 典型使用对象 角色 关注点 普通成员 上传、查找、预览、编辑、分享、同步和移动端访问文件 部门负责人 部门资料沉淀、成员权限、项目协作、分享控制和文件统计 项目团队 跨部门协作、外部成员参与、版本管理、评审批注和项目讨论 管理员 组织结构、账号、角色、权限、模块开关、水印、安全策略、日志和报表 实施与运维 私有化部署、存储、备份、转码、搜索、AI、第三方系统和升级维护 开发者 认证、文件、分享、企业组织、消息推送和素材库相关 API 版本口径 当前最新版本口径为 v9.4.2.2606171439 。不同客户的可用能力会受到实际部署版本、授权模块和管理员配置影响，使用前应以企业当前环境为准。 快速入口 产品基本概念 功能总览表 文件管理 同步与客户端 虚拟映射盘 素材库 水印功能 加密文件夹 敏感内容识别 在线编辑 权限体系 智巢 AI 自动化任务 私有化部署 开发 API 概览 FAQ 总览" }, { "lang": "zh", "slug": "getting-started", "title": "产品基本概念", "description": "解释账号、设备、个人文件、企业文件、部门、项目、素材库和档案库等基本概念。", "category": "概况", "top_category": "使用指南", "keywords": [ "入门", "账号", "部门", "项目", "企业文件" ], "url": "zh/getting-started.html", "source": "content/zh/getting-started.md", "summary": "产品基本概念 巴别鸟能做什么 巴别鸟主要解决企业文件统一管理、协同协作和数据安全三类问题。用户可以把工作文件同步到云端，在浏览器、客户端、移动端或企业内部入口访问个人文件、部门文件和项目文件；也可以在线编辑 Office 文档，使用本地客户端编辑任意格式文件，并通过版本管理避免误覆盖。 支持的设备 巴别鸟支持浏览器访问，推荐使用符合 HTML5 规范的现代浏览器；也提供 Windows、macOS、麒麟客户端，以及 iOS、Android 移动端。私有化部署可通过企业专属域名访问，企业微信、钉钉、飞书等集成入口需按模块配置。 文件空间 空间 归属 典型用途 个人文件 个人用户 个人资料、草稿、个人项目 企业文件 企业和部门 长期共享、部门资料、企业公共资源 部门文件夹 部门 部门内长期协作、部门权限管控 项目文件夹 项目负责人和项目成员 跨部门、跨组织、带有效期的协作 素材库 企业素材管理员或授权成员 图片、素材、图纸、可复用资产 档案库 档案管理员 归档、借阅、长期保存、合规管理 部门与项目 部门是企业组织结构和长期文件空间的基本单位。项目用于临时或跨部门协作，可以邀请企业内部成员、外部成员或未注册用户加入，并支持项目有效期、项目负责人、项目助理、成员权限和项目讨论组。 典型入门操作 1. 登录企业分配的地址或官网公有云入口。 2. 进入个人文件、企业文件、部门文件或我的项目。 3. 通过拖拽、新建按钮、客户端右键、同步文件夹、映射盘或移动端上传文件。 4. 使用文件右键菜单进行分享、编辑、版本、权限、批注、归档等操作。 5. 管理员从企业控制台维护组织结构、成员、角色、权限", "headings": [ { "level": 1, "title": "产品基本概念", "id": "section" }, { "level": 2, "title": "巴别鸟能做什么", "id": "section-2" }, { "level": 2, "title": "支持的设备", "id": "section-3" }, { "level": 2, "title": "文件空间", "id": "section-4" }, { "level": 2, "title": "部门与项目", "id": "section-5" }, { "level": 2, "title": "典型入门操作", "id": "section-6" }, { "level": 2, "title": "相关问题", "id": "section-7" } ], "images": [], "text": "产品基本概念 巴别鸟能做什么 巴别鸟主要解决企业文件统一管理、协同协作和数据安全三类问题。用户可以把工作文件同步到云端，在浏览器、客户端、移动端或企业内部入口访问个人文件、部门文件和项目文件；也可以在线编辑 Office 文档，使用本地客户端编辑任意格式文件，并通过版本管理避免误覆盖。 支持的设备 巴别鸟支持浏览器访问，推荐使用符合 HTML5 规范的现代浏览器；也提供 Windows、macOS、麒麟客户端，以及 iOS、Android 移动端。私有化部署可通过企业专属域名访问，企业微信、钉钉、飞书等集成入口需按模块配置。 文件空间 空间 归属 典型用途 个人文件 个人用户 个人资料、草稿、个人项目 企业文件 企业和部门 长期共享、部门资料、企业公共资源 部门文件夹 部门 部门内长期协作、部门权限管控 项目文件夹 项目负责人和项目成员 跨部门、跨组织、带有效期的协作 素材库 企业素材管理员或授权成员 图片、素材、图纸、可复用资产 档案库 档案管理员 归档、借阅、长期保存、合规管理 部门与项目 部门是企业组织结构和长期文件空间的基本单位。项目用于临时或跨部门协作，可以邀请企业内部成员、外部成员或未注册用户加入，并支持项目有效期、项目负责人、项目助理、成员权限和项目讨论组。 典型入门操作 1. 登录企业分配的地址或官网公有云入口。 2. 进入个人文件、企业文件、部门文件或我的项目。 3. 通过拖拽、新建按钮、客户端右键、同步文件夹、映射盘或移动端上传文件。 4. 使用文件右键菜单进行分享、编辑、版本、权限、批注、归档等操作。 5. 管理员从企业控制台维护组织结构、成员、角色、权限、水印、日志和系统配置。 相关问题 账号注册、个人空间、企业空间和基础操作相关问题可继续查看 FAQ：入门、账号与文件空间。" }, { "lang": "zh", "slug": "feature-matrix", "title": "功能总览表", "description": "按文件管理、在线协作、权限安全、自动化、智巢 AI、客户端、素材库和私有化集成汇总巴别鸟企业网盘能力。", "category": "产品功能介绍", "top_category": "使用指南", "keywords": [ "功能列表", "自动化任务", "智巢AI", "素材库", "加密文件夹", "敏感内容识别", "瀑布流" ], "url": "zh/feature-matrix.html", "source": "content/zh/feature-matrix.md", "summary": "功能总览表 巴别鸟企业网盘的功能可以按文件生命周期理解：文件进入系统后，会经历上传、新建、预览、编辑、同步、分享、权限控制、版本留存、搜索、归档、审计、自动化处理和 AI 检索等环节。不同企业可用的具体能力取决于部署版本、授权模块和管理员配置。 核心功能清单 模块 子功能 说明 典型入口 文件管理 上传、下载、拖拽上传、文件夹上传、断点续传、秒传、增量传输 面向日常文件收集、资料沉淀和大文件传输 文件列表、客户端、移动端、映射盘 新建能力 文件夹、Office 文档、轻文档、文本/代码文件、思维导图、draw.io 流程图、模板创建 用户可在网盘内直接创建业务文件和标准目录 新建菜单 文件组织 个人文件、企业文件、部门文件夹、项目文件夹、子项目、文件树、星标、最近访问 以组织结构和协作场景组织文件 左侧栏、文件列表、项目栏目 文件详情 标签、说明、文件属性、上传者、历史版本、访问日志、关联文件 让文件可被检索、追踪和复用 文件详情面板 版本管理 自动保存版本、上传新版本、版本回滚、版本对比、版本批注继承 降低误覆盖和协同冲突风险 文件详情、预览器、客户端 预览与批注 Office、PDF、图片、视频、音频、CAD、代码、Markdown、KM、draw.io 等格式预览 无需下载即可查看和讨论文件内容 文件预览器 在线协作 OnlyOffice 在线编辑、轻文档协同、Markdown/代码/文本编辑、KM/Xmind、draw.io 支持多人协作、在线编辑、本地编辑和锁定 在线编辑入口、客户端编辑 分享与外发 邀请分享、链接分享、快照分享、收件箱、仅上传、分享审批、分享密码、有", "headings": [ { "level": 1, "title": "功能总览表", "id": "section" }, { "level": 2, "title": "核心功能清单", "id": "section-2" }, { "level": 2, "title": "重点新增能力", "id": "section-3" }, { "level": 3, "title": "加密文件夹", "id": "section-4" }, { "level": 3, "title": "敏感内容识别", "id": "section-5" }, { "level": 3, "title": "瀑布流展示", "id": "section-6" }, { "level": 2, "title": "智巢 AI 子功能", "id": "ai" }, { "level": 2, "title": "自动化任务清单", "id": "section-7" }, { "level": 2, "title": "使用建议", "id": "section-8" } ], "images": [], "text": "功能总览表 巴别鸟企业网盘的功能可以按文件生命周期理解：文件进入系统后，会经历上传、新建、预览、编辑、同步、分享、权限控制、版本留存、搜索、归档、审计、自动化处理和 AI 检索等环节。不同企业可用的具体能力取决于部署版本、授权模块和管理员配置。 核心功能清单 模块 子功能 说明 典型入口 文件管理 上传、下载、拖拽上传、文件夹上传、断点续传、秒传、增量传输 面向日常文件收集、资料沉淀和大文件传输 文件列表、客户端、移动端、映射盘 新建能力 文件夹、Office 文档、轻文档、文本/代码文件、思维导图、draw.io 流程图、模板创建 用户可在网盘内直接创建业务文件和标准目录 新建菜单 文件组织 个人文件、企业文件、部门文件夹、项目文件夹、子项目、文件树、星标、最近访问 以组织结构和协作场景组织文件 左侧栏、文件列表、项目栏目 文件详情 标签、说明、文件属性、上传者、历史版本、访问日志、关联文件 让文件可被检索、追踪和复用 文件详情面板 版本管理 自动保存版本、上传新版本、版本回滚、版本对比、版本批注继承 降低误覆盖和协同冲突风险 文件详情、预览器、客户端 预览与批注 Office、PDF、图片、视频、音频、CAD、代码、Markdown、KM、draw.io 等格式预览 无需下载即可查看和讨论文件内容 文件预览器 在线协作 OnlyOffice 在线编辑、轻文档协同、Markdown/代码/文本编辑、KM/Xmind、draw.io 支持多人协作、在线编辑、本地编辑和锁定 在线编辑入口、客户端编辑 分享与外发 邀请分享、链接分享、快照分享、收件箱、仅上传、分享审批、分享密码、有效期 控制资料在内部、跨部门和外部伙伴之间流转 分享菜单、项目、收件箱 权限体系 企业角色、部门角色、项目权限、文件访问控制、自定义文件权限、分享权限 控制谁能看、传、改、删、下、评、管 企业控制台、部门管理、文件访问控制 安全增强 水印、密级、IP 策略、Mac 绑定、审计日志、黑白名单、加密文件夹、敏感内容识别 适合合同、财务、人事、研发、图纸和客户资料 企业控制台、文件夹、新建菜单 客户端 Windows、macOS、麒麟客户端、本地编辑、传输列表、右键上传、右键同步、匿名下载 让网盘文件与本地工作流连接 桌面客户端 同步 双向同步、上行同步、下行同步、同步黑名单、同步周期、冲突处理、20 万文件夹同步 面向长期离线编辑、资料分发和本地工作目录 客户端同步管理 映射盘 云端文件按需访问、虚拟盘符、按需缓存、本地应用打开、权限继承 像访问本地磁盘一样访问云端文件 客户端映射盘 素材库 素材分类、子素材库、素材库权限、下载审批、缩略图控制、图片元数据 面向品牌资产、设计图、产品图、营销素材和图库 企业文件下的素材库 瀑布流展示 图片文件夹自动或手动切换为瀑布流，支持缩略图快速浏览 适合大量图片、图纸、海报和素材筛选 文件列表、素材库 档案库 归档、阅览室、借阅审批、本地归档、档案管理员、长期保存 面向合同、项目交付、制度和归档文件 档案库 自动化任务 自动清理、自动重命名、自动整理、自动转 PDF、自动解压缩、创建签章、批量创建文件夹 把重复文件处理规则交给后台执行 文件夹右键菜单、自动化任务栏目 智巢 AI AI 助理、AI 搜索、智搜、文搜图、图搜图、图片 OCR、文档助手、表格问答、深度研究 在权限边界内检索、阅读、问答和分析企业文件 顶部 AI 入口、搜索、智巢 AI 栏目 智巢 AI 管理 企业知识库、知识库机器人、自定义智能体、MCP 接口、私有化模型、GPU 算力 面向客服、售前、培训、知识库和第三方 AI 集成 智巢 AI、后台配置、接口 企业控制台 组织结构、成员、角色、标签、水印、日志、通知、统计、模块开关、企业配置 管理员配置企业网盘的组织、权限和安全策略 企业控制台 私有化部署 单机、集群、对象存储、信创环境、专属域名、SSO、企业微信/钉钉/飞书、数据摆渡 适合内网、安全合规、国产化和系统集成场景 私有化部署项目 开发 API 认证、文件、分享、企业、部门、素材库、关注、日志等接口 用于业务系统集成、门户嵌入、自动化和二次开发 API 文档 重点新增能力 加密文件夹 加密文件夹用于在共享网盘中建立需要密码才能访问的文件夹。用户从新建菜单创建加密文件夹，输入文件夹名和密码后生成带锁标识的文件夹。每次打开文件夹都需要输入密码；即使文件夹内文件被分享给其他人，访问者也需要知道加密文件夹密码才能访问内容。 密码需要由创建者自行妥善保存。该能力采用匿名加密方式，密码遗失后无法找回，运营方和技术人员也无法帮助解密。详见加密文件夹。 敏感内容识别 敏感内容识别用于在企业控制台中配置敏感词或敏感内容识别策略。被检测出敏感内容的文件可被标记，并可按配置限制查看、限制分享或进入人工处理流程。该能力适合合同、证照、个人信息、客户资料、财务资料、研发资料和受监管内容的风险识别。详见敏感内容识别。 瀑布流展示 瀑布流展示适合图片密集场景，可让素材、设计图、产品图、图纸或拍摄图片以缩略图方式快速浏览。图片较多的文件夹可切换或自动适配瀑布流模式，配合素材库、标签、图片元数据、AI 搜图和图搜图提升查找效率。详见素材库。 智巢 AI 子功能 子功能 用途 相关章节 AI 助理 基于企业知识库和可选联网搜索回答问题 智巢 AI AI 搜索 在搜索结果中返回自然语言理解后的答案和引用 AI 搜索与智搜 智搜 问答、深度研究和文章撰写 AI 搜索与智搜 文搜图 用文字描述查找网盘图片 文搜图、图搜图与 OCR 图搜图 上传或选择图片查找相似图片 文搜图、图搜图与 OCR 图片 OCR 提取图片中文字并参与搜索 文搜图、图搜图与 OCR 文档助手 对当前文档做总结、问答、解释和阅读辅助 AI 助理与文档助手 表格问答 对 Excel 数据进行问答、分析和函数辅助 标准版模块 AI 自动打标签 对文件自动匹配标签库中最接近的标签 标准版模块 企业知识库 将企业文档组织为可问答、可检索的知识源 知识库机器人与智能体 知识库机器人 创建可面向内部或外部场景的问答机器人 AI 客服与知识库机器人 MCP 接口 向外部 AI 应用提供知识库访问和文件操作能力 标准版模块 自动化任务清单 任务 作用 说明 自动清理文件夹 按规则清理符合条件的文件 适合临时上传区、收集箱和周期性清理目录 自动解压缩 文件进入目录后自动解压 适合供应商包、素材包和项目交付包 自动重命名 按规则统一文件名 适合合同、图片、项目文件和交付文件标准化 自动格式转化 将文件转为 PDF 或其他目标格式 适合归档、审批、签章和只读流转 自动整理 按规则把文件移动到对应目录 适合收集、分发、归档和分类整理 创建签章 在签章场景中自动创建或应用签章流程 适合合同、审批单和正式交付文件 批量创建文件夹 通过模板或数据批量生成目录 适合项目初始化、客户目录、部门标准目录 使用建议 1. 先按“文件进入、文件协作、文件外发、文件归档、文件检索”梳理业务流程，再决定开启哪些模块。 2. 对高敏感资料，组合使用权限、文件访问控制、水印、加密文件夹、敏感内容识别、日志审计和下载控制。 3. 对图片和素材场景，优先配置素材库、瀑布流、标签、图片元数据、文搜图和图搜图。 4. 对重复性文件处理，优先使用自动化任务，把命名、整理、转 PDF、清理和批量建目录规则沉淀下来。 5. 对 AI 使用场景，先确认知识库范围、权限继承、模型部署方式、数据流向和审计要求。" }, { "lang": "zh", "slug": "file-transfer", "title": "文件传输", "description": "上传、下载、同步盘、映射盘的数据传输机制。", "category": "产品功能介绍", "top_category": "使用指南", "keywords": [ "文件管理", "文件传输", "巴别鸟" ], "url": "zh/file-transfer.html", "source": "content/zh/file-transfer.md", "summary": "文件传输 上传、下载、同步盘、映射盘的数据传输机制。 详细说明 数据传输模块是巴别鸟企业网盘的核心组成部分，负责管理上传、下载、同步盘和映射盘的数据传输。这一模块采用多种技术来确保数据的安全性、可靠性和高效性。 技术特点 文件分块: 数据传输模块采用文件分块技术，将大文件分成小块，以便更有效地传输和存储。这不仅有助于减少网络流量和服务器资源的消耗，还支持断点续传和增量上传下载。 哈希验证（秒传）: 在数据传输过程中，哈希验证用于确保文件的完整性。每个文件块都有相应的哈希值，服务器和客户端会相互验证这些哈希值，以检测是否有数据损坏或篡改。 同时，如果存储系统中已经有相同哈希码的文件，该文件就不用再次上传。实现秒传功能。 SSL传输: 数据传输模块使用SSL（安全套接层）协议来加密数据传输，以确保数据在传输过程中的保密性和安全性。这对于敏感企业数据的传输至关重要。 断点续传: 巴别鸟企业网盘支持断点续传，允许用户在传输中断的情况下从上次中断的地方继续上传或下载文件，而无需重新开始整个过程。这节省了时间和带宽。 增量上传下载: 数据传输模块还支持增量上传和下载，允许用户只传输发生更改的部分的文件分块，而不是整个文件。这在大型文件和频繁同步的情况下非常有用。 优势 数据完整性: 文件分块和哈希验证确保了数据的完整性，降低了数据损坏或篡改的风险。 数据安全: SSL传输提供了数据的端到端加密，确保数据在传输过程中不会被窥探或窃取。 效率: 断点续传和增量上传下载提高了数据传输的效率，节省了时间和带宽。 节约存储空间： 使用文件哈希码技术可以在磁盘上只存储一份相同哈希的文件。无论文件路径、", "headings": [ { "level": 1, "title": "文件传输", "id": "section" }, { "level": 2, "title": "详细说明", "id": "section-2" }, { "level": 3, "title": "技术特点", "id": "section-3" }, { "level": 3, "title": "优势", "id": "section-4" } ], "images": [], "text": "文件传输 上传、下载、同步盘、映射盘的数据传输机制。 详细说明 数据传输模块是巴别鸟企业网盘的核心组成部分，负责管理上传、下载、同步盘和映射盘的数据传输。这一模块采用多种技术来确保数据的安全性、可靠性和高效性。 技术特点 文件分块: 数据传输模块采用文件分块技术，将大文件分成小块，以便更有效地传输和存储。这不仅有助于减少网络流量和服务器资源的消耗，还支持断点续传和增量上传下载。 哈希验证（秒传）: 在数据传输过程中，哈希验证用于确保文件的完整性。每个文件块都有相应的哈希值，服务器和客户端会相互验证这些哈希值，以检测是否有数据损坏或篡改。 同时，如果存储系统中已经有相同哈希码的文件，该文件就不用再次上传。实现秒传功能。 SSL传输: 数据传输模块使用SSL（安全套接层）协议来加密数据传输，以确保数据在传输过程中的保密性和安全性。这对于敏感企业数据的传输至关重要。 断点续传: 巴别鸟企业网盘支持断点续传，允许用户在传输中断的情况下从上次中断的地方继续上传或下载文件，而无需重新开始整个过程。这节省了时间和带宽。 增量上传下载: 数据传输模块还支持增量上传和下载，允许用户只传输发生更改的部分的文件分块，而不是整个文件。这在大型文件和频繁同步的情况下非常有用。 优势 数据完整性: 文件分块和哈希验证确保了数据的完整性，降低了数据损坏或篡改的风险。 数据安全: SSL传输提供了数据的端到端加密，确保数据在传输过程中不会被窥探或窃取。 效率: 断点续传和增量上传下载提高了数据传输的效率，节省了时间和带宽。 节约存储空间： 使用文件哈希码技术可以在磁盘上只存储一份相同哈希的文件。无论文件路径、文件名如何变化，或者在网盘中有多少个文件副本，文件实际存储空间就只占用一个文件的容量。（去重存储） 高速上传： 相同哈希值的文件不需要再次上传，如上传网盘上已存在的文件，检测到同样哈希值就会自动标记为上传成功，无需再次上传。 数据传输模块是巴别鸟企业网盘的关键组成部分，通过采用这些技术特点，它确保了用户可以安全、高效地上传、下载和同步其文件。这一模块的功能是使巴别鸟企业网盘成为一个可信赖的数据管理平台。" }, { "lang": "zh", "slug": "file-create", "title": "新建文件与文件夹", "description": "新建 Office、文本、代码、思维导图、流程图、模板、部门、项目和文件夹。", "category": "产品功能介绍", "top_category": "使用指南", "keywords": [ "文件管理", "新建文件与文件夹", "巴别鸟" ], "url": "zh/file-create.html", "source": "content/zh/file-create.md", "summary": "新建文件与文件夹 新建 Office、文本、代码、思维导图、流程图、模板、部门、项目和文件夹。 详细说明 新建模块主要负责文件、部门、项目、模版、文件夹的创建。在巴别鸟中可以做到无需上传文件就直接新建文件进行工作。 文件的新建 Office文件 巴别鸟支持在线创建空白word文档、Excel文档、PPT文档。 使用客户端新建会默认打开本地office相应组件创建并编辑文档。 在网页上新建会使用在线office创建并编辑文档。 Office文档都可以使用在线编辑（无需安装office）或使用客户端选择本地编辑（使用电脑上安装的office编辑）。 在线编辑支持多人实时协同编辑。 使用客户端调取本地office编辑时文档会自动锁定编辑，防止其他人在编辑时也编辑该文档造成冲突。 文本代码类文件 巴别鸟文本编辑器可在线创建并打开所有的文本类文件，如RTF、TXT、HTML、MD、CSS… 为了客户使用方便，公有云版本仅支持新建TXT和MD（markdown文件），私有云用户如需要其他格式的文本文件创建可以要求开放。 文本编辑器不同于在线office，不支持协同编辑，但可以在线编辑文本类文件。 思维导图及流程图。 巴别鸟自带思维导图模块，可以在线新建及在线编辑思维导图文件。 思维导图文件默认保存为KM格式。也可以导出为KM、TXT、MD、SVG、PNG、Xmind格式。 巴别鸟也可选支持创建流程图，但需要购买相应的模块授权（非标准版默认自带）。 其他第三方模块。 符合WebAPI的互联网应用理论上都可以对接巴别鸟并新建文件。巴别鸟提供第三方应用对接服务。 从模版创建 不少客户需要大量创建", "headings": [ { "level": 1, "title": "新建文件与文件夹", "id": "section" }, { "level": 2, "title": "详细说明", "id": "section-2" } ], "images": [], "text": "新建文件与文件夹 新建 Office、文本、代码、思维导图、流程图、模板、部门、项目和文件夹。 详细说明 新建模块主要负责文件、部门、项目、模版、文件夹的创建。在巴别鸟中可以做到无需上传文件就直接新建文件进行工作。 文件的新建 Office文件 巴别鸟支持在线创建空白word文档、Excel文档、PPT文档。 使用客户端新建会默认打开本地office相应组件创建并编辑文档。 在网页上新建会使用在线office创建并编辑文档。 Office文档都可以使用在线编辑（无需安装office）或使用客户端选择本地编辑（使用电脑上安装的office编辑）。 在线编辑支持多人实时协同编辑。 使用客户端调取本地office编辑时文档会自动锁定编辑，防止其他人在编辑时也编辑该文档造成冲突。 文本代码类文件 巴别鸟文本编辑器可在线创建并打开所有的文本类文件，如RTF、TXT、HTML、MD、CSS… 为了客户使用方便，公有云版本仅支持新建TXT和MD（markdown文件），私有云用户如需要其他格式的文本文件创建可以要求开放。 文本编辑器不同于在线office，不支持协同编辑，但可以在线编辑文本类文件。 思维导图及流程图。 巴别鸟自带思维导图模块，可以在线新建及在线编辑思维导图文件。 思维导图文件默认保存为KM格式。也可以导出为KM、TXT、MD、SVG、PNG、Xmind格式。 巴别鸟也可选支持创建流程图，但需要购买相应的模块授权（非标准版默认自带）。 其他第三方模块。 符合WebAPI的互联网应用理论上都可以对接巴别鸟并新建文件。巴别鸟提供第三方应用对接服务。 从模版创建 不少客户需要大量创建相同结构的文件夹或从某个特定模版（如企业PPT模版）创建文件。巴别鸟支持从模版创建文件夹和文件。 创建模版。 拥有部门文件管理权限的人可以在新建菜单里创建模版。 点击创建模版后会生成一个模版文件夹，模版文件夹类似于普通文件夹，可以拖动文件到文件夹中上传、新建文件夹及部门。 在模版文件夹根目录中上传的文件即成为文件模版，在模版文件夹中创建的文件夹就是文件夹模版。如下图： 图：在模版文件夹中显示 图：在新建模版时显示 从模版创建。 有创建文件及文件夹权限的部门都可以新建时选择模版快速创建和模版一致的文件或文件夹。 新建部门、项目 使用新建功能也可以创建部门和项目。 创建部门。 只有在企业文件根部门下才能创建部门，部门文件属于企业，超级管理员能看到根部门和整个文件树。 拥有子部门管理权限的用户（默认部门经理角色）可以创建子部门。 部门文件夹可以新增部门成员，并完成部门级别的管理。 只有加入部门的成员（部门成员）及上级部门拥有“查看子部门文件”权限的成员才能访问部门文件。 部门成员由在该部门的角色决定基本权限。 可以用文件权限管理的方式针对文件（文件夹）做权限管理 项目。 用户可以在个人文件或企业文件的部门文件夹下创建项目。 项目可以跨部门、跨企业邀请项目组成员，甚至可以邀请企业外的非注册用户。 拥有个人文件的人都可以创建个人项目，要在部门下创建项目用户角色需要有“创建文件夹/项目“权限。 项目文件夹中支持创建子项目。 项目文件夹的上级一定是个部门或者是个项目，这意味着不能在普通文件夹下创建部门。 项目创建者默认为项目管理员，项目是可以转交的，可以把项目管理员转交给其他成员及其他部门。 项目内成员的权限由创建项目时指定。项目相对是一个独立的共享文件夹。 新建普通文件夹 个人文件下创建文件夹。 用户可以在个人文件下可以任意创建文件夹，并自行管理。 企业文件下创建文件夹 企业文件下需要在部门中创建文件夹（所有的文件夹都有归属部门）。 在所在部门中角色具有“创建文件夹/项目“权限的用户可以创建文件夹。 只要角色具有“创建文件夹/项目“权限的用户可以在部门中任意普通文件夹中创建子文件夹。" }, { "lang": "zh", "slug": "files-management", "title": "文件管理", "description": "文件列表、排序、详情、标签、置顶、快捷方式、复制移动、批量操作和文件访问。", "category": "产品功能介绍", "top_category": "使用指南", "keywords": [ "文件管理", "文件管理", "巴别鸟" ], "url": "zh/files-management.html", "source": "content/zh/files-management.md", "summary": "文件管理 文件列表、排序、详情、标签、置顶、快捷方式、复制移动、批量操作和文件访问。 网页版主界面 网页版主界面采用左侧导航、右侧文件列表和顶部功能区，常用文件操作集中在文件列表和右键菜单。 打开文件树 树状视图适合需要按层级管理大量文件夹的场景。 详细说明 简介 文件管理模块是巴别鸟企业网盘的核心功能之一，用于用户管理和操作文件及文件夹，并根据权限推送给用户不同的文件列表。也是用户使用网盘的主要界面。该模块提供了广泛的功能，以满足企业用户对文件的管理和组织需求。 技术特点 A．文件访问与组织 分页载入技术: 文件管理模块使用分页载入技术，由服务器端数据库进行文件的排序查询操作，并把文件列表返回前台进行分页载入。这样一个文件列表可以分页载入几十万行数据，确保用户能够高效载入和浏览大量文件，而不会影响性能和用户体验。 树状展示文件列表: 巴别鸟支持树状展示文件列表，使文件的组织结构更加直观，用户可以轻松导航和管理文件夹。 权限控制: 根据用户的权限不同，文件管理模块会动态显示适当的列表项目，不同用户看到的文件列表内容根据权限不同而不同。以确保只有授权用户可以查看、编辑或删除特定文件和文件夹。 B. 文件排序和快捷操作 多维度排序: 支持多维度排序，用户可以按照文件名称、最近版本、文件大小等不同维度进行排序。 文件名排序: 不同于大多数网盘应用，巴别鸟文件名排序支持多位数字按顺序排序，使文件名包含数字编号的文件能够准确排序。（大部分网盘文件名排序仅首字母排序如：1、2、10、3、4，但在巴别鸟可以正确显示排序为：1、2、3、4、10） 自定义全局排序: 用户在设置里可以自定义适合自", "headings": [ { "level": 1, "title": "文件管理", "id": "section" }, { "level": 2, "title": "详细说明", "id": "section-2" }, { "level": 3, "title": "简介", "id": "section-3" }, { "level": 3, "title": "技术特点", "id": "section-4" } ], "images": [ { "src": "../assets/images/web-main.webp", "alt": "网页版主界面", "caption": "网页版主界面采用左侧导航、右侧文件列表和顶部功能区，常用文件操作集中在文件列表和右键菜单。" }, { "src": "../assets/images/web-tree.webp", "alt": "打开文件树", "caption": "树状视图适合需要按层级管理大量文件夹的场景。" } ], "text": "文件管理 文件列表、排序、详情、标签、置顶、快捷方式、复制移动、批量操作和文件访问。 网页版主界面 网页版主界面采用左侧导航、右侧文件列表和顶部功能区，常用文件操作集中在文件列表和右键菜单。 打开文件树 树状视图适合需要按层级管理大量文件夹的场景。 详细说明 简介 文件管理模块是巴别鸟企业网盘的核心功能之一，用于用户管理和操作文件及文件夹，并根据权限推送给用户不同的文件列表。也是用户使用网盘的主要界面。该模块提供了广泛的功能，以满足企业用户对文件的管理和组织需求。 技术特点 A．文件访问与组织 分页载入技术: 文件管理模块使用分页载入技术，由服务器端数据库进行文件的排序查询操作，并把文件列表返回前台进行分页载入。这样一个文件列表可以分页载入几十万行数据，确保用户能够高效载入和浏览大量文件，而不会影响性能和用户体验。 树状展示文件列表: 巴别鸟支持树状展示文件列表，使文件的组织结构更加直观，用户可以轻松导航和管理文件夹。 权限控制: 根据用户的权限不同，文件管理模块会动态显示适当的列表项目，不同用户看到的文件列表内容根据权限不同而不同。以确保只有授权用户可以查看、编辑或删除特定文件和文件夹。 B. 文件排序和快捷操作 多维度排序: 支持多维度排序，用户可以按照文件名称、最近版本、文件大小等不同维度进行排序。 文件名排序: 不同于大多数网盘应用，巴别鸟文件名排序支持多位数字按顺序排序，使文件名包含数字编号的文件能够准确排序。（大部分网盘文件名排序仅首字母排序如：1、2、10、3、4，但在巴别鸟可以正确显示排序为：1、2、3、4、10） 自定义全局排序: 用户在设置里可以自定义适合自己的全局使用的排序方式，同时系统会记住上一次用户在文件夹选择的排序方式，下一次打开文件夹也按上一次的排序显示。 C. 文件展示和详细管理 列表模式和瀑布流模式可切换: 支持列表模式浏览文件夹，同时可以切换为瀑布流模式预览。 支持瀑布流模式浏览文件夹（文件缩略图），使文件的浏览更加流畅和直观。 图片较多的文件夹会自动适配为瀑布流模式显示。 文件详情页面: 每个文件和文件夹都有详细的详情页面，用户可以管理文件信息，增加文件注释，查看文件访问日志，对文件访问进行统计并生成报表。 文件详情页面也能管理文件的版本。 评论区: 每个文件或文件夹都自带评论区，支持用户评论和@提及其他用户，促进团队协作和反馈。 文件关联: 支持文件关联文件，允许用户在相关文件之间建立连接，以便更方便地访问相关信息。 文件关注提醒: 用户可以提醒有权限查看文件的人关注文件或文件夹，确保重要文件不会被忽视。 D. 高级搜索和筛选 高级搜索 巴别鸟支持高级搜索功能，可以根据关键字、全文内容、时间、文件格式、上传者、搜索范围、搜索类型等维度进行高级搜索。" }, { "lang": "zh", "slug": "file-versioning", "title": "版本管理", "description": "文件版本生成、回退、下载、预览、对比、日志和勒索病毒防护。", "category": "产品功能介绍", "top_category": "使用指南", "keywords": [ "文件管理", "版本管理", "巴别鸟" ], "url": "zh/file-versioning.html", "source": "content/zh/file-versioning.md", "summary": "版本管理 文件版本生成、回退、下载、预览、对比、日志和勒索病毒防护。 详细说明 版本管理概述 版本管理是巴别鸟企业网盘的重要功能之一，它允许用户跟踪和管理文件的不同版本，确保文件的历史记录和更新能够得以保留和查看。巴别鸟的版本管理功能非常强大，支持多种更新方式以及版本的回滚和查看。 技术实现 版本管理使用文件分块和增量保存技术来存储文件版本。这意味着每次文件的更改都会生成一个新的版本，而这些版本仅存储所做更改的数据块，以减小存储需求并提高效率。企业管理员可以在企业控制台中设置文件版本的保存数量和保存时间，以控制版本管理的策略。 版本管理功能使用户能够灵活管理文件版本，从而确保文件的完整性、历史记录和安全性。版本管理是巴别鸟企业网盘的一项核心功能，旨在提供卓越的用户体验和数据安全性。 版本更新方式 巴别鸟允许用户使用多种方式更新文件版本，包括： 手动上传新版本: 用户可以右键点击文件，选择上传新版本，手动上传新文件，并将其保存为文件的新版本。 同名文件检测: 上传时巴别鸟可以检测到文件名相同的文件，用户可以选择将新文件上传为已有文件的新版本。 客户端编辑保存: 如果用户使用客户端编辑文件并保存，巴别鸟将保存所做的更改作为文件的新版本。 在线编辑保存: 如果用户在网页上使用在线编辑功能编辑文件并保存，也将生成新版本。 同步文件夹编辑: 巴别鸟客户端会监控同步文件夹的更新，在同步文件夹中编辑或覆盖文件并保存会生成新版本。 映射盘编辑: 编辑映射盘中的文件并保存，更新的文件也会保存为新的版本。 版本管理功能 巴别鸟版本管理模块具有以下功能： 版本回退: 在文件的版本列表中，用户可以选择", "headings": [ { "level": 1, "title": "版本管理", "id": "section" }, { "level": 2, "title": "详细说明", "id": "section-2" }, { "level": 3, "title": "版本管理概述", "id": "section-3" }, { "level": 3, "title": "技术实现", "id": "section-4" }, { "level": 3, "title": "版本更新方式", "id": "section-5" }, { "level": 3, "title": "版本管理功能", "id": "section-6" }, { "level": 3, "title": "企业控制", "id": "section-7" }, { "level": 3, "title": "搜索模块概述", "id": "section-8" }, { "level": 3, "title": "带权限判断的搜索", "id": "section-9" }, { "level": 3, "title": "技术基础", "id": "section-10" }, { "level": 3, "title": "搜索功能", "id": "section-11" }, { "level": 3, "title": "性能优化", "id": "section-12" }, { "level": 3, "title": "未来发展", "id": "section-13" } ], "images": [], "text": "版本管理 文件版本生成、回退、下载、预览、对比、日志和勒索病毒防护。 详细说明 版本管理概述 版本管理是巴别鸟企业网盘的重要功能之一，它允许用户跟踪和管理文件的不同版本，确保文件的历史记录和更新能够得以保留和查看。巴别鸟的版本管理功能非常强大，支持多种更新方式以及版本的回滚和查看。 技术实现 版本管理使用文件分块和增量保存技术来存储文件版本。这意味着每次文件的更改都会生成一个新的版本，而这些版本仅存储所做更改的数据块，以减小存储需求并提高效率。企业管理员可以在企业控制台中设置文件版本的保存数量和保存时间，以控制版本管理的策略。 版本管理功能使用户能够灵活管理文件版本，从而确保文件的完整性、历史记录和安全性。版本管理是巴别鸟企业网盘的一项核心功能，旨在提供卓越的用户体验和数据安全性。 版本更新方式 巴别鸟允许用户使用多种方式更新文件版本，包括： 手动上传新版本: 用户可以右键点击文件，选择上传新版本，手动上传新文件，并将其保存为文件的新版本。 同名文件检测: 上传时巴别鸟可以检测到文件名相同的文件，用户可以选择将新文件上传为已有文件的新版本。 客户端编辑保存: 如果用户使用客户端编辑文件并保存，巴别鸟将保存所做的更改作为文件的新版本。 在线编辑保存: 如果用户在网页上使用在线编辑功能编辑文件并保存，也将生成新版本。 同步文件夹编辑: 巴别鸟客户端会监控同步文件夹的更新，在同步文件夹中编辑或覆盖文件并保存会生成新版本。 映射盘编辑: 编辑映射盘中的文件并保存，更新的文件也会保存为新的版本。 版本管理功能 巴别鸟版本管理模块具有以下功能： 版本回退: 在文件的版本列表中，用户可以选择将旧版本置为当前版本，实现版本回退的功能。 版本下载: 用户可以选择下载历史版本，以便访问以前的文件版本。 版本预览: 版本管理模块允许用户在点击旧版本文件时进行预览，以查看该版本的内容。 版本对比： 在巴别鸟预览器预览文件时，可以选择文件对比功能，该功能支持选择旧版本和新版本进行对比。 版本日志: 用户可以为每个文件版本添加日志，以记录版本的重要信息和更改历史。 企业控制 巴别鸟企业网盘的版本管理功能允许企业管理员在企业控制台中进行高级设置，以满足企业的特定需求。企业管理员可以根据公司政策和合规要求，设置文件版本的保留数量和保留时间，以满足不同文件类型和部门的需求。 这样的版本管理系统保障了文件的数据一致性、可追溯性，以及用户数据的完整性。同时对勒索病毒这类改变文件可读性的病毒具有强大的防护性，因为勒索病毒更改文件需要更新的文件，而更新的文件将形成新的版本，用户只要回退版本就能拿到被攻击前的文件。 搜索 搜索模块概述 巴别鸟企业网盘的搜索模块是一个关键的功能，它基于强大的Elasticsearch技术和数据库查询技术开发，旨在提供高效、精确和全面的文档搜索功能。搜索模块不仅支持全文搜索，还可以搜索文档的说明、注释和文件名，满足不同用户的搜索需求。 带权限判断的搜索 巴别鸟的搜索模块不仅具备强大的搜索功能，还采用高级权限管理技术，动态判断用户权限，确保用户只能看到其权限范围内的文件。搜索结果是根据用户的权限动态生成的，这意味着用户共享的文件中，只有用户有权限查看的文件才会被搜索到。这是一项关键的技术，特别在企业环境中，权限是随时变化的。 技术基础 Elasticsearch: Elasticsearch是一款开源搜索引擎，它以高效的分布式架构和强大的全文搜索能力而闻名。巴别鸟使用Elasticsearch作为核心搜索引擎，以支持全文搜索和高级查询功能。 数据库查询: 除了Elasticsearch，搜索模块还利用数据库查询技术来搜索文档的元数据和标签信息，以提供更全面的搜索结果。 文档解析: 搜索模块使用文本提取技术，可以从各种类型的文件中提取文本信息。这些提取的文本信息用于搜索引擎的索引和查询。关键字抽取。 分词优化: 巴别鸟进行了大量的分词优化工作，特别针对中文词汇，以提高搜索引擎的分词准确性和性能。中文分词的优化对搜索结果的准确性起到关键作用。 搜索功能 巴别鸟搜索模块包括以下主要功能： 全文搜索: 用户可以执行全文搜索，查找文档中的文字内容，以找到与关键字相关的文件。 文档描述和注释搜索: 搜索模块支持搜索用户添加到巴别鸟的文档的说明和注释，使用户可以更轻松地找到特定信息。 文件名搜索: 用户可以进行精确的文件名搜索，以查找特定文件。 标签搜索: 可进行标签的搜索、查询、分类显示 高级搜索 巴别鸟支持高级搜索功能，可以根据关键字、全文内容、时间、文件格式、上传者、搜索范围、搜索类型等维度进行高级搜索。 性能优化 搜索模块对服务器性能要求较高，因此对于私有化部署的用户，建议将搜索模块部署在独立的虚拟机或服务器上，以减少对其他模块的性能占用。 未来发展 未来版本的巴别鸟将继续改进搜索模块，结合AI技术，例如ChatGPT，实现文档内容的问答式聊天对话搜索，为用户提供更智能的搜索体验。目前基于AI的文档分析及客服系统“智巢AI”已经上线，详情可查阅智巢AI章节。 搜索模块的不断改进将有助于用户更快速、准确地找到所需的文件和信息，引入AI系统后，用户可以用问答的形式获取信息，并能交叉多个文档的内容得出完整的结论，能大幅度提高生产效率和工作效率。" }, { "lang": "zh", "slug": "search-preview", "title": "搜索", "description": "全文搜索、标签、说明、注释、文件名、高级搜索和带权限判断的搜索。", "category": "产品功能介绍", "top_category": "使用指南", "keywords": [ "文件管理", "搜索", "巴别鸟" ], "url": "zh/search-preview.html", "source": "content/zh/search-preview.md", "summary": "搜索 全文搜索、标签、说明、注释、文件名、高级搜索和带权限判断的搜索。 详细说明 巴别鸟也支持全文搜索，可搜索文件内容里的关键字。 也可使用文件名搜索、标签搜索找到对应文件 搜索的结果可以通过筛选的方式再次搜索或筛选 筛选功能: 可以根据文件标签、类型、文件说明关键字、大小、版本、上传者、照片元数据等进行筛选，以快速定位所需文件。 文件标签和分类: 用户可以给文件打标签，以更好地组织和分类文件。 标签可以有企业统一管理，以保证标签符合规范。 左侧栏可以加入标签快捷方式使用。 常见文件管理功能 A. 文件传输和操作 上传和下载文件: 用户可以上传和下载文件，确保数据的灵活传输。 支持文件夹拖动上传，以方便大批量文件的传输。 浏览器支持文件夹打包下载（少于100个文件或小于500MB大小的文件夹） 客户端支持文件夹直接下载（传输列表） 文件和文件夹的新建: 用户可以新建各类文件和文件夹，同时支持从模版新建文件或文件夹，以提高工作效率。 文件复制和移动: 用户可以复制和移动文件或文件夹，以方便组织文件。 支持将文件或文件夹复制到指定目录，以便文件的备份和管理。 文件归档: 用户可以将文件归档到档案库，以便长期保存和检索。 文件置顶: 个人文件支持将文件或文件夹置顶，以便快速访问重要文件。 部门或项目管理员可以置顶部门文件或项目文件，方便部门成员和项目成员快速访问重要文件。 创建文件或文件夹快捷方式: 用户可以创建文件或文件夹的快捷方式，以方便快速访问。 上传新版本: 用户可以上传新版本的文件，系统会自动检测重名文件并提供是上传新版本还是重命名文件的选择。 点击上传新版本按钮可以直接上", "headings": [ { "level": 1, "title": "搜索", "id": "section" }, { "level": 2, "title": "详细说明", "id": "section-2" }, { "level": 3, "title": "常见文件管理功能", "id": "section-3" } ], "images": [], "text": "搜索 全文搜索、标签、说明、注释、文件名、高级搜索和带权限判断的搜索。 详细说明 巴别鸟也支持全文搜索，可搜索文件内容里的关键字。 也可使用文件名搜索、标签搜索找到对应文件 搜索的结果可以通过筛选的方式再次搜索或筛选 筛选功能: 可以根据文件标签、类型、文件说明关键字、大小、版本、上传者、照片元数据等进行筛选，以快速定位所需文件。 文件标签和分类: 用户可以给文件打标签，以更好地组织和分类文件。 标签可以有企业统一管理，以保证标签符合规范。 左侧栏可以加入标签快捷方式使用。 常见文件管理功能 A. 文件传输和操作 上传和下载文件: 用户可以上传和下载文件，确保数据的灵活传输。 支持文件夹拖动上传，以方便大批量文件的传输。 浏览器支持文件夹打包下载（少于100个文件或小于500MB大小的文件夹） 客户端支持文件夹直接下载（传输列表） 文件和文件夹的新建: 用户可以新建各类文件和文件夹，同时支持从模版新建文件或文件夹，以提高工作效率。 文件复制和移动: 用户可以复制和移动文件或文件夹，以方便组织文件。 支持将文件或文件夹复制到指定目录，以便文件的备份和管理。 文件归档: 用户可以将文件归档到档案库，以便长期保存和检索。 文件置顶: 个人文件支持将文件或文件夹置顶，以便快速访问重要文件。 部门或项目管理员可以置顶部门文件或项目文件，方便部门成员和项目成员快速访问重要文件。 创建文件或文件夹快捷方式: 用户可以创建文件或文件夹的快捷方式，以方便快速访问。 上传新版本: 用户可以上传新版本的文件，系统会自动检测重名文件并提供是上传新版本还是重命名文件的选择。 点击上传新版本按钮可以直接上传新版本。 文件打印为加水印PDF: 开启水印的时候，支持将文件打印为加水印的PDF文件，以确保文件的传播安全性和保密性。 锁定文件: 文件使用客户端编辑时会自动锁定防止冲突。 用户也可以在文件列表中手动锁定文件，以防止其他用户的编辑和冲突。 文件预览: 支持大多数文件预览，以快速查看文件内容。要了解更多可查看 预览与转码 章节。 文件列表展示缩略图: 文件管理模块可以在文件列表中展示文件的缩略图，使文件的浏览更加直观。 批量文件上传下载: 巴别鸟提供客户端专用的上传下载模块，支持批量文件的上传和下载，同时提供传输文件列表展示。 查看文件详情及版本管理: 巴别鸟有专门的文件详情界面。在文件详情里可以添加文件说明，查看文件基础信息，图片文件可以查看元数据，同时还可以在详情里查看文件日志及文件访问、使用情况，管理文件的版本。 B. 文件安全和权限控制 文件访问控制： 部门管理员或项目管理员可以设定文件访问控制，精确的控制每一个文件或文件夹针对每一个用户或某个角色的访问权限。 文件访问控制的优先级高于成员的部门角色权限。譬如：一个部门成员角色拥有某文件的编辑权限，但部门管理员使用文件访问控制把该成员对该文件的权限改为“不可见”，该成员将不能访问该文件。 文件分享: 支持分享文件和文件夹，允许用户设置详细的访问权限，以控制文件的访问。 文件快照分享: 针对只想分享当前版本的需求，用户可以创建文件的快照分享，快照分享不会受文件内容更新而改变，保持建立快照时的版本。" }, { "lang": "zh", "slug": "file-sharing", "title": "分享与外发", "description": "邀请分享、链接分享、快照分享、外发、分享日志和企业策略。", "category": "产品功能介绍", "top_category": "使用指南", "keywords": [ "文件管理", "分享与外发", "巴别鸟" ], "url": "zh/file-sharing.html", "source": "content/zh/file-sharing.md", "summary": "分享与外发 邀请分享、链接分享、快照分享、外发、分享日志和企业策略。 详细说明 分享功能 巴别鸟企业网盘提供了多种灵活的分享方式，包括邀请分享和链接分享，以满足用户的不同需求。 邀请分享： 邀请分享是一种将文件或文件夹分享给特定人员的方式。特点如下： 身份验证：被邀请者需要进行身份验证，可以通过巴别鸟账号登录或者接收验证码确认身份。 每个被邀请者可以独立管理权限，可设置权限有效期。这意味者同一个邀请分享，不同的被邀请者可以设定不同的访问权限。 权限控制：分享者可以自定义分享权限，包括查看、编辑、下载等权限。这有助于细化控制分享内容。 审批机制：如果用户没有分享权限，分享操作需要经过审批，确保只有授权的人员可以分享文件。 链接分享： 链接分享允许用户创建一个公开链接，供其他人访问文件或文件夹。特点如下： 允许匿名访问：分享者可以选择是否允许匿名访问。如果关闭匿名访问选项，访问者需要拥有巴别鸟账号才能访问。 快照分享：快照分享模式下，分享的内容是分享时的当前版本，即使文件内容更新，快照分享的内容也不会变化。 密码保护：用户可以设置密码，确保只有知晓密码的人能够访问分享链接。 有效期：链接分享可以设置有效期，确保文件不会永久公开。一旦有效期结束，分享链接将自动失效。 自定义设置： 在企业控制台中，管理员可以自定义分享权限、按部门设定分享行为（支持或禁止分享），按文件设定分享规则（禁止分享高密级文件），以及关闭整个企业的对外分享功能。 分享日志： 所有的分享行为和外界访问行为都有独立的日志，每个分享的访问日志都可以查询。你可以知道什么人什么时候访问了分享的文件或文件夹，分享文件更新版本", "headings": [ { "level": 1, "title": "分享与外发", "id": "section" }, { "level": 2, "title": "详细说明", "id": "section-2" }, { "level": 3, "title": "分享功能", "id": "section-3" }, { "level": 3, "title": "外发功能（发送文件）", "id": "section-4" }, { "level": 3, "title": "用户控制和企业策略", "id": "section-5" }, { "level": 3, "title": "灵活性与便捷性", "id": "section-6" } ], "images": [], "text": "分享与外发 邀请分享、链接分享、快照分享、外发、分享日志和企业策略。 详细说明 分享功能 巴别鸟企业网盘提供了多种灵活的分享方式，包括邀请分享和链接分享，以满足用户的不同需求。 邀请分享： 邀请分享是一种将文件或文件夹分享给特定人员的方式。特点如下： 身份验证：被邀请者需要进行身份验证，可以通过巴别鸟账号登录或者接收验证码确认身份。 每个被邀请者可以独立管理权限，可设置权限有效期。这意味者同一个邀请分享，不同的被邀请者可以设定不同的访问权限。 权限控制：分享者可以自定义分享权限，包括查看、编辑、下载等权限。这有助于细化控制分享内容。 审批机制：如果用户没有分享权限，分享操作需要经过审批，确保只有授权的人员可以分享文件。 链接分享： 链接分享允许用户创建一个公开链接，供其他人访问文件或文件夹。特点如下： 允许匿名访问：分享者可以选择是否允许匿名访问。如果关闭匿名访问选项，访问者需要拥有巴别鸟账号才能访问。 快照分享：快照分享模式下，分享的内容是分享时的当前版本，即使文件内容更新，快照分享的内容也不会变化。 密码保护：用户可以设置密码，确保只有知晓密码的人能够访问分享链接。 有效期：链接分享可以设置有效期，确保文件不会永久公开。一旦有效期结束，分享链接将自动失效。 自定义设置： 在企业控制台中，管理员可以自定义分享权限、按部门设定分享行为（支持或禁止分享），按文件设定分享规则（禁止分享高密级文件），以及关闭整个企业的对外分享功能。 分享日志： 所有的分享行为和外界访问行为都有独立的日志，每个分享的访问日志都可以查询。你可以知道什么人什么时候访问了分享的文件或文件夹，分享文件更新版本会提醒用户。 统一管理分享： 部门管理员可以统一查看和管理整个部门所有被分享的文件，分享的个人文件也可以在“我分享的文件”栏目统一查看管理，确保不会有遗漏的分享在不知情的情况下泄露。 外发功能（发送文件） 外发功能是一种通过邮件或手机号将文件发送给其他用户以供直接下载使用的方式。外发不同于分享，仅用于接收方下载外发的文件，无需配置权限。特点如下： 发送文件：用户可以使用外发功能将文件发送到其他用户的邮箱或手机号，以便他们可以直接下载并使用。 发送文件功能也可以发送文件给内部用户，收到文件会有通知，点击通知就可以下载或转存文件。 无需权限：外发不需要配置权限，只要用户有分享和下载权限即可使用。 邮件或短信发送：外发可以通过电子邮件或短信发送文件链接，确保接收方可方便地获得文件。 快捷下载：接收方可以通过点击链接直接下载文件，简单便捷。 用户控制和企业策略 用户的分享权限可以由企业管理员进行控制，确保文件的分享和外发都受到严格管理。此外，企业管理员还可以通过企业控制台自定义分享规则和权限，以适应不同的企业需求。 安全性 分享和外发功能均受到严格的安全控制，保护企业文件不被未经授权的人员访问。管理员可以根据企业的安全策略，灵活配置分享和外发的权限和规则。 灵活性与便捷性 分享和外发功能提供了企业灵活性和便捷性，满足了不同用户及场景的需求。用户可以根据具体情况选择最适合的分享方式，从而更好地管理和共享文件。" }, { "lang": "zh", "slug": "preview-annotation-review", "title": "预览、批注与评审", "description": "BabelViewer、批注、手绘、语音批注、版本对比和评审协作。", "category": "产品功能介绍", "top_category": "使用指南", "keywords": [ "文件管理", "预览、批注与评审", "巴别鸟" ], "url": "zh/preview-annotation-review.html", "source": "content/zh/preview-annotation-review.md", "summary": "预览、批注与评审 BabelViewer、批注、手绘、语音批注、版本对比和评审协作。 支持的预览格式、转码机制和预览排队等细节见 白皮书：预览及转码。 详细说明 为了让用户能更方便的预览文件，并且可以在预览文件时进行协作讨论提高协作效率，巴别鸟开发了巴别鸟预览器BabelViewer，在巴别鸟上可以预览的大多数文件格式都可以用预览器打开，巴别鸟预览器不仅可以预览文件，还可以通过手绘、文字讨论、语音（仅手机APP支持建立语音批注）等方式在文件内容上和协作者进行交流。同时，巴别鸟预览器还支持版本对比，切换版本查看不同版本批注、批注管理、审批管理等功能。 技术架构 使用canvas开发及多图层技术 预览器基于Html5 Canvas技术开发，使用多图层技术，以在文件预览层上面增加批注和手绘图层，不影响文件内容但可以进行批注讨论和实时手绘。 实时协同模块 预览器的实时协同模块，保证多用户在文件预览时的批注讨论和手绘是实时展示的，这意味着用户可以边批注边讨论文档或设计稿件的问题。 批注点坐标系定位 巴别鸟预览器使用坐标系定位， 保证批注点在不同的分辨率屏幕下，不同浏览器尺寸下的位置一致。 适用的文件类型 巴别鸟预览器能打开绝大多数图片及office文档、PDF文档及矢量图形文件。具体支持的文件类型可参阅 预览转码章节里的 支持在线预览的文件类型 预览器类型 多页文档预览器 支持对多页文档的预览，如word、PPT、PDF等格式。针对多页文档提供适合多页文档的目录、放大、旋转页面等功能。 图片预览器 为更好的预览图片而设计。拥有鹰眼、放大缩小、显示原始比例、旋转等功能。 右键可以复制图片到", "headings": [ { "level": 1, "title": "预览、批注与评审", "id": "section" }, { "level": 2, "title": "详细说明", "id": "section-2" }, { "level": 3, "title": "技术架构", "id": "section-3" }, { "level": 3, "title": "适用的文件类型", "id": "section-4" }, { "level": 3, "title": "预览器类型", "id": "section-5" }, { "level": 3, "title": "批注种类", "id": "section-6" }, { "level": 3, "title": "功能模块", "id": "section-7" } ], "images": [], "text": "预览、批注与评审 BabelViewer、批注、手绘、语音批注、版本对比和评审协作。 支持的预览格式、转码机制和预览排队等细节见 白皮书：预览及转码。 详细说明 为了让用户能更方便的预览文件，并且可以在预览文件时进行协作讨论提高协作效率，巴别鸟开发了巴别鸟预览器BabelViewer，在巴别鸟上可以预览的大多数文件格式都可以用预览器打开，巴别鸟预览器不仅可以预览文件，还可以通过手绘、文字讨论、语音（仅手机APP支持建立语音批注）等方式在文件内容上和协作者进行交流。同时，巴别鸟预览器还支持版本对比，切换版本查看不同版本批注、批注管理、审批管理等功能。 技术架构 使用canvas开发及多图层技术 预览器基于Html5 Canvas技术开发，使用多图层技术，以在文件预览层上面增加批注和手绘图层，不影响文件内容但可以进行批注讨论和实时手绘。 实时协同模块 预览器的实时协同模块，保证多用户在文件预览时的批注讨论和手绘是实时展示的，这意味着用户可以边批注边讨论文档或设计稿件的问题。 批注点坐标系定位 巴别鸟预览器使用坐标系定位， 保证批注点在不同的分辨率屏幕下，不同浏览器尺寸下的位置一致。 适用的文件类型 巴别鸟预览器能打开绝大多数图片及office文档、PDF文档及矢量图形文件。具体支持的文件类型可参阅 预览转码章节里的 支持在线预览的文件类型 预览器类型 多页文档预览器 支持对多页文档的预览，如word、PPT、PDF等格式。针对多页文档提供适合多页文档的目录、放大、旋转页面等功能。 图片预览器 为更好的预览图片而设计。拥有鹰眼、放大缩小、显示原始比例、旋转等功能。 右键可以复制图片到剪贴版，方便在微信、邮箱里直接粘贴图片。 针对PNG等拥有透明度的图片，可以改变图片背景。 图形预览器 为预览CAD、SVG、单页PDF等矢量图形文件设计，支持鹰眼、分图层显示、更改背景、鼠标拖动区域放大、矢量放大。对SVG文件可以切换编码模式。 3D预览器 为预览3D文件设计，可以旋转、鼠标滚轮拉近放远3D文件、炸开图像、支持3D空间的批注。 批注种类 文字讨论区 文字讨论区可以在预览文件的任意区域创建（双击建立文字讨论批注）。 文件的协作者如果有查阅批注权限都可以看到批注，并参与讨论。 批注内容实时显示，一个文字批注讨论区相当于针对批注内容的群聊。 支持插入附件进行讨论，也支持@等聊天功能。 可以设定批注的可见性，如：仅企业成员可见、所有人可见、仅批注者自己可见。 文字标注 文字标注可以在文档内容或照片上添加标注 选定文字批注 针对有文字的文件，如word、PDF，可以选择一段文字进行批注。 特殊符号插入 针对特殊需求的稿件，可以插入修订符号或焊接标记（如CAD图纸） 建立图形批注 也支持使用图形框选批注，支持矩形、椭圆及箭头。 语音批注 巴别鸟移动设备APP可以建立语音批注。在网页和客户端可以查看（收听）语音批注，但不能创建。 手绘批注 支持在稿件或文档上实时绘制，参与者可以实时看到绘制的线条，并且标记手绘者昵称。 功能模块 批注管理模块 可以管理创建的批注和批注状态，查阅其他版本批注，并切换到相应的版本 评审工作区 巴别鸟可以在文件评审时使用批注，并显示评审的相关面板，让评审人员能更准确便捷的传达评审信息。 鹰眼 鹰眼可以在图像放大时显示图像视口所在的区域。 版本对比 巴别鸟预览器支持文件对比功能，也可以对比不同版本的文件。 文件目录 对于拥有目录的文件（word、pdf），巴别鸟也支持预览时显示文件目录。" }, { "lang": "zh", "slug": "file-review", "title": "文件评审", "description": "多文件评审、审批流程、外部评审、报表和签名。", "category": "产品功能介绍", "top_category": "使用指南", "keywords": [ "文件管理", "文件评审", "巴别鸟" ], "url": "zh/file-review.html", "source": "content/zh/file-review.md", "summary": "文件评审 多文件评审、审批流程、外部评审、报表和签名。 详细说明 巴别鸟企业网盘提供了强大的文件评审功能，旨在帮助用户高效管理文件的审批和修订过程。文件评审是一种协同工作流程，允许用户发起文件评审，邀请评审人员查看文件，提供批注和建议，以最终确定文件是否需要修改或批准。 主要特点 多文件评审：支持同时评审多个文件，用户可以一次性发起对多个文件的评审，确保高效的审批过程。 文件锁定：文件在评审过程中会被自动锁定，以防止其他用户进行编辑或上传新版本，确保文件内容在评审期间不会被更改。 文件预览和批注：评审人员可以在预览文件时添加批注，填写评审意见，以提供详细的反馈。这有助于更好地理解文件内容和提供有针对性的建议。 评审流程：用户可以选择不同的评审流程，包括自由定义审批流程、使用预设审批流程，或限用特定审批流程。这允许不同部门根据其需求选择适当的审批流程。 多阶段审批：审批流程支持多个阶段，每个阶段可以设置一个或多个审批者。用户可以定义通过比例，例如，50%的审批者通过即可通过某个阶段。 邀请外部审批者：用户可以邀请外部成员（通过邮件或手机号）参与文件评审，以获得更多不同角度的反馈，譬如：论文答辩时邀请外部专家。 审批报表：每次文件评审后，会生成审批报表，记录每个阶段参与者的评审意见，以便审批结果的跟踪和分析。 评审签名：支持评审结束后在稿件上插入签名，并下载为PDF。 我的评审栏目：用户可以在“我的评审”栏目中查看和管理与自己相关的所有评审文件的各个阶段，包括发起的评审和邀请参与的评审。 技术架构 文件评审功能的实现涉及以下技术和模块： 评审流程定义：后台定义不同的评审流程，包括阶", "headings": [ { "level": 1, "title": "文件评审", "id": "section" }, { "level": 2, "title": "详细说明", "id": "section-2" }, { "level": 3, "title": "主要特点", "id": "section-3" }, { "level": 3, "title": "技术架构", "id": "section-4" }, { "level": 3, "title": "文件评审的优势", "id": "section-5" } ], "images": [], "text": "文件评审 多文件评审、审批流程、外部评审、报表和签名。 详细说明 巴别鸟企业网盘提供了强大的文件评审功能，旨在帮助用户高效管理文件的审批和修订过程。文件评审是一种协同工作流程，允许用户发起文件评审，邀请评审人员查看文件，提供批注和建议，以最终确定文件是否需要修改或批准。 主要特点 多文件评审：支持同时评审多个文件，用户可以一次性发起对多个文件的评审，确保高效的审批过程。 文件锁定：文件在评审过程中会被自动锁定，以防止其他用户进行编辑或上传新版本，确保文件内容在评审期间不会被更改。 文件预览和批注：评审人员可以在预览文件时添加批注，填写评审意见，以提供详细的反馈。这有助于更好地理解文件内容和提供有针对性的建议。 评审流程：用户可以选择不同的评审流程，包括自由定义审批流程、使用预设审批流程，或限用特定审批流程。这允许不同部门根据其需求选择适当的审批流程。 多阶段审批：审批流程支持多个阶段，每个阶段可以设置一个或多个审批者。用户可以定义通过比例，例如，50%的审批者通过即可通过某个阶段。 邀请外部审批者：用户可以邀请外部成员（通过邮件或手机号）参与文件评审，以获得更多不同角度的反馈，譬如：论文答辩时邀请外部专家。 审批报表：每次文件评审后，会生成审批报表，记录每个阶段参与者的评审意见，以便审批结果的跟踪和分析。 评审签名：支持评审结束后在稿件上插入签名，并下载为PDF。 我的评审栏目：用户可以在“我的评审”栏目中查看和管理与自己相关的所有评审文件的各个阶段，包括发起的评审和邀请参与的评审。 技术架构 文件评审功能的实现涉及以下技术和模块： 评审流程定义：后台定义不同的评审流程，包括阶段设置、审批者选择、通过比例设定等。这些流程可供前台用户选择。 部门特定审批流程：不同部门可以选择不同的审批流程，根据需要选择自由定义、预设或限用特定审批流程。 多阶段审批：可实现多阶段审批，每个阶段具有不同的审批要求，包括审批者的选择和通过比例。也可以设定某阶段是否能跳过。 外部审批者邀请：支持邀请外部成员参与文件评审，通过邮件或手机号进行邀请。 审批报表：生成审批报表，记录每个阶段的评审意见，以便审批结果的跟踪和分析。 文件评审的优势 文件评审功能有助于用户高效管理文件的审批和修订过程，确保文件内容的准确性和合规性。用户可以通过文件评审，确保文件经过充分的审查和讨论，以满足其工作需求和合规要求。这个功能的引入增加了文件协作和管理的深度，为用户提供了更强大的文件协作工具。" }, { "lang": "zh", "slug": "archive-library", "title": "档案库", "description": "归档、阅览室、借阅、长期保存和档案库搜索。", "category": "产品功能介绍", "top_category": "使用指南", "keywords": [ "文件管理", "档案库", "巴别鸟" ], "url": "zh/archive-library.html", "source": "content/zh/archive-library.md", "summary": "档案库 归档、阅览室、借阅、长期保存和档案库搜索。 详细说明 巴别鸟企业网盘提供了强大的档案管理模块，用于统一管理和归档企业文件。这一模块旨在帮助企业更好地组织和保留关键文件，同时确保文件的安全性和可访问性。 主要特点 档案管理员：巴别鸟允许超级管理员指定一名或多名企业成员作为档案管理员。档案管理员负责管理归档的文件和档案库。 档案库：归档的文件存储在档案库的根目录中。档案库是企业的资料图书馆，用于长期保留和管理文件。 阅览室：档案管理员可以建立阅览室，将档案库根目录的文件移入阅览室。这样其他企业成员才可以借阅这些文件。 借阅权限：阅览室可以选择不同的借阅方式，包括公开、需要借阅、限定部门公开、限定部门内借阅等。借阅文件时，可以设定权限级别，如仅可阅读、可复制、可下载，并指定借阅时长。 文件归档：归档后的文件不可更改，确保文件的完整性和可信度。这对于长期保留法律和合规性文件非常重要。 档案库搜索：档案库拥有独立的搜索功能，只会搜索档案库内的文件。用户可以快速找到需要的归档文件。 文件隐私：没有借阅权限的非公开文件不会显示预览图，以确保文件隐私性。 技术架构 档案管理模块使用以下关键技术和模块： 档案管理员权限：超级管理员可以指定企业成员为档案管理员，允许他们管理档案库和阅览室。 阅览室设置：档案管理员可以创建阅览室并配置不同的借阅权限和可访问性选项。 归档和保留：文件归档后，需要确保其内容不可更改。这需要技术措施来保护文件完整性。 独立搜索：档案库拥有独立的搜索引擎，用于搜索档案库内的文件，确保用户可以快速找到需要的文件。 档案管理的优势 档案管理模块帮助企业更好地管理文件的归", "headings": [ { "level": 1, "title": "档案库", "id": "section" }, { "level": 2, "title": "详细说明", "id": "section-2" }, { "level": 3, "title": "主要特点", "id": "section-3" }, { "level": 3, "title": "技术架构", "id": "section-4" }, { "level": 3, "title": "档案管理的优势", "id": "section-5" } ], "images": [], "text": "档案库 归档、阅览室、借阅、长期保存和档案库搜索。 详细说明 巴别鸟企业网盘提供了强大的档案管理模块，用于统一管理和归档企业文件。这一模块旨在帮助企业更好地组织和保留关键文件，同时确保文件的安全性和可访问性。 主要特点 档案管理员：巴别鸟允许超级管理员指定一名或多名企业成员作为档案管理员。档案管理员负责管理归档的文件和档案库。 档案库：归档的文件存储在档案库的根目录中。档案库是企业的资料图书馆，用于长期保留和管理文件。 阅览室：档案管理员可以建立阅览室，将档案库根目录的文件移入阅览室。这样其他企业成员才可以借阅这些文件。 借阅权限：阅览室可以选择不同的借阅方式，包括公开、需要借阅、限定部门公开、限定部门内借阅等。借阅文件时，可以设定权限级别，如仅可阅读、可复制、可下载，并指定借阅时长。 文件归档：归档后的文件不可更改，确保文件的完整性和可信度。这对于长期保留法律和合规性文件非常重要。 档案库搜索：档案库拥有独立的搜索功能，只会搜索档案库内的文件。用户可以快速找到需要的归档文件。 文件隐私：没有借阅权限的非公开文件不会显示预览图，以确保文件隐私性。 技术架构 档案管理模块使用以下关键技术和模块： 档案管理员权限：超级管理员可以指定企业成员为档案管理员，允许他们管理档案库和阅览室。 阅览室设置：档案管理员可以创建阅览室并配置不同的借阅权限和可访问性选项。 归档和保留：文件归档后，需要确保其内容不可更改。这需要技术措施来保护文件完整性。 独立搜索：档案库拥有独立的搜索引擎，用于搜索档案库内的文件，确保用户可以快速找到需要的文件。 档案管理的优势 档案管理模块帮助企业更好地管理文件的归档和保留。通过档案库、阅览室、和不同的借阅权限，企业可以确保文件长期保留、有序管理，并能够满足合规性和法律要求。这一模块还可以作为知识库使用，帮助企业保存重要信息和知识。" }, { "lang": "zh", "slug": "logs-reports", "title": "日志与报表", "description": "文件日志、访问统计、部门报表、企业日志和统计分析。", "category": "产品功能介绍", "top_category": "使用指南", "keywords": [ "文件管理", "日志与报表", "巴别鸟" ], "url": "zh/logs-reports.html", "source": "content/zh/logs-reports.md", "summary": "日志与报表 文件日志、访问统计、部门报表、企业日志和统计分析。 详细说明 巴别鸟企业网盘的日志与报表系统提供了全面的文件使用情况管理、监控、审计和追责功能。这一模块旨在帮助企业管理者及用户深入了解文件活动、访问情况以及系统使用情况，以支持合规性和安全性需求。 主要特点 文件日志：每个文件和文件夹都有独立的日志，详细记录了文件的生命周期内的各种操作，包括创建、阅读、修改、更名、分享、删除、权限更改等。甚至包括匿名分享操作以及访问者的IP地址。这些日志可以导出为Excel报表，用于审计和监控。 文件访问统计：文件详情页提供了文件批注数量、下载次数、打开次数、访问人数和访问人员的统计。 文件夹列表：可以导出文件夹内文件和子文件的列表为EXCEl文件，以便审计和管理。 文件评审记录报表：文件评审操作也被记录为报表，以支持文件评审的审计。 部门日志与报表：部门管理员可以查看整个部门的使用日志，包括文件详细访问日志、上传文件数量、创建子部门数量或项目数量的统计。此外，部门管理员可以统计及管理整个部门分享的文件以及更改过权限的文件。 企业级管理：企业管理员和安全审计员可以查看整个企业的使用行为，包括各个部门的日志和报表，并且还有访问日志和统计分析两个栏目统一查看及管理整个企业的使用行为。这有助于维护企业的合规性和安全性。 访问日志：访问日志记录了整个企业网盘的使用日志，包括用户在网盘中的每个操作。管理员可以进行详细的查询和导出报表。 统计分析：提供了统计分析图表工具，允许管理员查看不同部门的使用活跃度、文件数量、活跃文件排名、新建文件统计、上传文件数量统计以及流量使用统计等。 技术架构 日志", "headings": [ { "level": 1, "title": "日志与报表", "id": "section" }, { "level": 2, "title": "详细说明", "id": "section-2" }, { "level": 3, "title": "主要特点", "id": "section-3" }, { "level": 3, "title": "技术架构", "id": "section-4" }, { "level": 3, "title": "日志与报表的优势", "id": "section-5" } ], "images": [], "text": "日志与报表 文件日志、访问统计、部门报表、企业日志和统计分析。 详细说明 巴别鸟企业网盘的日志与报表系统提供了全面的文件使用情况管理、监控、审计和追责功能。这一模块旨在帮助企业管理者及用户深入了解文件活动、访问情况以及系统使用情况，以支持合规性和安全性需求。 主要特点 文件日志：每个文件和文件夹都有独立的日志，详细记录了文件的生命周期内的各种操作，包括创建、阅读、修改、更名、分享、删除、权限更改等。甚至包括匿名分享操作以及访问者的IP地址。这些日志可以导出为Excel报表，用于审计和监控。 文件访问统计：文件详情页提供了文件批注数量、下载次数、打开次数、访问人数和访问人员的统计。 文件夹列表：可以导出文件夹内文件和子文件的列表为EXCEl文件，以便审计和管理。 文件评审记录报表：文件评审操作也被记录为报表，以支持文件评审的审计。 部门日志与报表：部门管理员可以查看整个部门的使用日志，包括文件详细访问日志、上传文件数量、创建子部门数量或项目数量的统计。此外，部门管理员可以统计及管理整个部门分享的文件以及更改过权限的文件。 企业级管理：企业管理员和安全审计员可以查看整个企业的使用行为，包括各个部门的日志和报表，并且还有访问日志和统计分析两个栏目统一查看及管理整个企业的使用行为。这有助于维护企业的合规性和安全性。 访问日志：访问日志记录了整个企业网盘的使用日志，包括用户在网盘中的每个操作。管理员可以进行详细的查询和导出报表。 统计分析：提供了统计分析图表工具，允许管理员查看不同部门的使用活跃度、文件数量、活跃文件排名、新建文件统计、上传文件数量统计以及流量使用统计等。 技术架构 日志记录：系统需要记录每个操作的详细日志，包括操作类型、时间戳、执行者、目标文件、IP地址等信息。 报表生成：管理员能够从日志数据中生成报表，通常以Excel格式呈现，以便审计和监控。 数据分析工具：统计分析工具用于分析和可视化数据，帮助管理员更好地了解系统使用情况。 日志接口：巴别鸟支持通过接口导出日志数据，以使用第三方日志管理及分析工具。 日志与报表的优势 日志与报表系统有助于企业实现以下目标： 合规性：帮助企业遵守法规和内部政策，确保文件操作的合规性。 安全审计：提供审计功能，允许企业检查和监视文件访问和操作，以发现潜在的风险。 性能优化：通过统计分析，帮助企业了解系统的性能瓶颈，以采取适当的改进措施。 用户行为监控：允许企业管理者了解员工的行为，包括文件访问和操作，以确保数据的安全性和保密性。 决策支持：通过数据分析，帮助企业管理者做出更明智的决策，包括资源分配和文件管理。 日志与报表系统是巴别鸟企业网盘的重要组成部分，提供了全面的文件使用情况管理和监控功能，以支持企业的合规性和安全性需求。" }, { "lang": "zh", "slug": "activity-notification", "title": "动态与通知", "description": "动态信息流、通知类型、通知设置和协作提醒。", "category": "产品功能介绍", "top_category": "使用指南", "keywords": [ "文件管理", "动态与通知", "巴别鸟" ], "url": "zh/activity-notification.html", "source": "content/zh/activity-notification.md", "summary": "动态与通知 动态信息流、通知类型、通知设置和协作提醒。 详细说明 动态栏目 概述：巴别鸟企业网盘的动态栏目是一个信息流，用于展示与您有关的文件和用户的动态信息。它提供了一个实时的工作情况总览，帮助您跟踪同事的活动，包括文件的变更、批注、评论等。 实时信息流：动态栏目以实时信息流的方式呈现您和您的团队的协作活动，从而帮助您及时了解团队中发生的事情。 便捷互动：通过动态栏目，您可以直接访问与您有关的文件，回复批注，与同事互动，以更便捷的方式完成协作任务。 动态搜索：您可以搜索动态的历史内容，更精准的定位到相关的动态条目。 通知栏目 通知系统：巴别鸟企业网盘的通知系统用于发送各种与您有关的提醒和通知。这些通知可以以多种方式传达给您，包括邮件通知、手机应用程序通知、桌面通知等。 通知类型：通知系统涵盖了多种通知类型，如@提到您、文件更新通知、审批请求、文件授权请求等。这有助于您保持对各种工作流程的掌握。 个性化设置 信息类型设置：用户可以根据自己的需求在设置中自定义接收哪些动态和通知类型，以确保信息的准确性和有针对性。 应用场景 动态栏目和通知栏目帮助用户了解工作中的重要动态和通知，提高了协作效率，使用户能够更快速地回应同事的协作请求，回复评论以及跟踪文件的变化。 巴别鸟企业网盘的动态与通知栏目是关键的协作工具，它们提供了实时的协作情况总览和各种通知，使用户能够更有效地与团队协作，并保持对工作流程的了解。这些功能有助于提高协作效率，确保重要信息不被忽略。", "headings": [ { "level": 1, "title": "动态与通知", "id": "section" }, { "level": 2, "title": "详细说明", "id": "section-2" }, { "level": 3, "title": "动态栏目", "id": "section-3" }, { "level": 3, "title": "通知栏目", "id": "section-4" }, { "level": 3, "title": "个性化设置", "id": "section-5" }, { "level": 3, "title": "应用场景", "id": "section-6" } ], "images": [], "text": "动态与通知 动态信息流、通知类型、通知设置和协作提醒。 详细说明 动态栏目 概述：巴别鸟企业网盘的动态栏目是一个信息流，用于展示与您有关的文件和用户的动态信息。它提供了一个实时的工作情况总览，帮助您跟踪同事的活动，包括文件的变更、批注、评论等。 实时信息流：动态栏目以实时信息流的方式呈现您和您的团队的协作活动，从而帮助您及时了解团队中发生的事情。 便捷互动：通过动态栏目，您可以直接访问与您有关的文件，回复批注，与同事互动，以更便捷的方式完成协作任务。 动态搜索：您可以搜索动态的历史内容，更精准的定位到相关的动态条目。 通知栏目 通知系统：巴别鸟企业网盘的通知系统用于发送各种与您有关的提醒和通知。这些通知可以以多种方式传达给您，包括邮件通知、手机应用程序通知、桌面通知等。 通知类型：通知系统涵盖了多种通知类型，如@提到您、文件更新通知、审批请求、文件授权请求等。这有助于您保持对各种工作流程的掌握。 个性化设置 信息类型设置：用户可以根据自己的需求在设置中自定义接收哪些动态和通知类型，以确保信息的准确性和有针对性。 应用场景 动态栏目和通知栏目帮助用户了解工作中的重要动态和通知，提高了协作效率，使用户能够更快速地回应同事的协作请求，回复评论以及跟踪文件的变化。 巴别鸟企业网盘的动态与通知栏目是关键的协作工具，它们提供了实时的协作情况总览和各种通知，使用户能够更有效地与团队协作，并保持对工作流程的了解。这些功能有助于提高协作效率，确保重要信息不被忽略。" }, { "lang": "zh", "slug": "discussion-workbench", "title": "讨论组与工作台", "description": "部门/项目讨论组与个性化工作台。", "category": "产品功能介绍", "top_category": "使用指南", "keywords": [ "文件管理", "讨论组与工作台", "巴别鸟" ], "url": "zh/discussion-workbench.html", "source": "content/zh/discussion-workbench.md", "summary": "讨论组与工作台 部门/项目讨论组与个性化工作台。 详细说明 概述 讨论组功能：巴别鸟企业网盘为每个部门和项目创建了讨论组，作为部门或项目内部成员的群聊空间。讨论组允许成员在其中发布文本和图片，进行讨论，并分享附件。 成员互动：讨论组提供了一个方便的平台，使成员能够互相沟通、协作和讨论项目相关事项，从而增强团队合作和信息分享。 主要功能 信息发布：讨论组成员可以发布文本消息和图片，以实现实时的讨论和交流。 附件分享：成员可以轻松分享附件，如文档、表格和其他文件，以便共享和讨论。 可见性：讨论组中发布的信息对所属部门或项目的所有成员可见，从而确保信息共享。 应用场景 讨论组适用于部门内部和项目团队之间的信息交流和讨论。它们促进了实时协作，有助于解决问题、分享见解和跟踪进度。 总结 讨论组为部门和项目成员提供了一个便捷的协作平台，用于共享信息、讨论事务和协同工作。这些讨论组有助于加强内部沟通，提高团队的效率和生产力。 工作台 概述 工作台功能：巴别鸟的工作台是一个个性化的界面，允许用户将常用的文件夹、工作内容以及各种信息以卡片的形式集中在一个界面上展示。每个卡片直接呈现内容，可进行操作，用户可以根据需要自由调整卡片的位置和排序。 个性化：工作台提供了多个备选卡片，用户可以自由选择需要添加到工作台上的卡片，根据自己的需求进行定制。这使得用户能够在一个页面上获取与其工作相关的信息和功能。 主要功能 卡片展示：每个卡片代表不同类型的信息或工作内容，例如最近访问的文件、上传的文件、关注的文件、分享的文件、批注过的文件、标签云图等。 自定义图表：用户可以自定义图表或卡片，以便将特定项目、文件夹", "headings": [ { "level": 1, "title": "讨论组与工作台", "id": "section" }, { "level": 2, "title": "详细说明", "id": "section-2" }, { "level": 3, "title": "概述", "id": "section-3" }, { "level": 3, "title": "主要功能", "id": "section-4" }, { "level": 3, "title": "应用场景", "id": "section-5" }, { "level": 3, "title": "总结", "id": "section-6" }, { "level": 2, "title": "工作台", "id": "section-7" }, { "level": 3, "title": "概述", "id": "section-8" }, { "level": 3, "title": "主要功能", "id": "section-9" }, { "level": 3, "title": "应用场景", "id": "section-10" } ], "images": [], "text": "讨论组与工作台 部门/项目讨论组与个性化工作台。 详细说明 概述 讨论组功能：巴别鸟企业网盘为每个部门和项目创建了讨论组，作为部门或项目内部成员的群聊空间。讨论组允许成员在其中发布文本和图片，进行讨论，并分享附件。 成员互动：讨论组提供了一个方便的平台，使成员能够互相沟通、协作和讨论项目相关事项，从而增强团队合作和信息分享。 主要功能 信息发布：讨论组成员可以发布文本消息和图片，以实现实时的讨论和交流。 附件分享：成员可以轻松分享附件，如文档、表格和其他文件，以便共享和讨论。 可见性：讨论组中发布的信息对所属部门或项目的所有成员可见，从而确保信息共享。 应用场景 讨论组适用于部门内部和项目团队之间的信息交流和讨论。它们促进了实时协作，有助于解决问题、分享见解和跟踪进度。 总结 讨论组为部门和项目成员提供了一个便捷的协作平台，用于共享信息、讨论事务和协同工作。这些讨论组有助于加强内部沟通，提高团队的效率和生产力。 工作台 概述 工作台功能：巴别鸟的工作台是一个个性化的界面，允许用户将常用的文件夹、工作内容以及各种信息以卡片的形式集中在一个界面上展示。每个卡片直接呈现内容，可进行操作，用户可以根据需要自由调整卡片的位置和排序。 个性化：工作台提供了多个备选卡片，用户可以自由选择需要添加到工作台上的卡片，根据自己的需求进行定制。这使得用户能够在一个页面上获取与其工作相关的信息和功能。 主要功能 卡片展示：每个卡片代表不同类型的信息或工作内容，例如最近访问的文件、上传的文件、关注的文件、分享的文件、批注过的文件、标签云图等。 自定义图表：用户可以自定义图表或卡片，以便将特定项目、文件夹或其他信息添加到工作台上，以满足其独特的需求。 卡片排序：用户可以通过拖放方式对卡片进行排序，以便将最重要或最频繁使用的信息放在前面。 应用场景 工作台适用于用户需要集中管理和访问与其工作相关的信息和资源的情况。用户可以将常用的文件和项目放在工作台上，以提高工作效率。" }, { "lang": "zh", "slug": "admin-console", "title": "企业控制台", "description": "企业配置、组织结构、权限、成员、标签、水印、日志、IP策略和模块管理。", "category": "产品功能介绍", "top_category": "使用指南", "keywords": [ "文件管理", "企业控制台", "巴别鸟" ], "url": "zh/admin-console.html", "source": "content/zh/admin-console.md", "summary": "企业控制台 企业配置、组织结构、权限、成员、标签、水印、日志、IP策略和模块管理。 详细说明 巴别鸟企业控制台集中了管理员对整个企业进行管理的功能。企业管理员可以在企业控制台中配置企业网盘的各个选项、开启或关闭需要的功能模块、设定组织结构、自定义角色和权限，管理成员、设置水印、设定部门安全策略、iP访问策略、绑定账户和mac地址、监控网盘使用情况…. 主要栏目 企业配置：综合管理企业网盘的配置项，譬如空间分配、是否允许个人文件、允许的文件上传大小、历史版本有效期或历史版本数量、各种管理员分配、更改logo及登录背景、禁止或开启对外分享、是否接受邮件通知。各种企业配置选项里面都可以在企业配置栏目找到。 组织结构：统一管理和维护企业的组织结构及部门。能树状查看部门和管理部门。查看部门成员、分配部门空间、创建子部门、设定部门安全策略… 权限管理：创建角色和更改角色权限，同时可管理自定义文件权限。 成员管理：可以查找和筛选整个企业的成员账户，新增成员、批量导入成员、分配成员部门及角色、详细查看及管理每一个成员的信息及使用情况、成员离职一件交接、成员账户的增删改查、成员空间和流量的分配及限制。 标签管理：统一管理企业所使用的标签，添加标签和给标签分类，便于用户选择标签。 文件配置：添加文件审批可选流程，管理已经添加的审批流程。同时拥有文件黑名单功能，可以阻止特定类型的文件上传。 企业通知：创建企业通知，管理历史企业通知列表、发送企业通知。 分组管理：建立分组及管理分组。前台分享文件时可以选择分享给什么分组。 水印设置：管理文档的水印类型，水印参数调整，水印显示范围设定。 访问日志：管理及", "headings": [ { "level": 1, "title": "企业控制台", "id": "section" }, { "level": 2, "title": "详细说明", "id": "section-2" }, { "level": 3, "title": "主要栏目", "id": "section-3" } ], "images": [], "text": "企业控制台 企业配置、组织结构、权限、成员、标签、水印、日志、IP策略和模块管理。 详细说明 巴别鸟企业控制台集中了管理员对整个企业进行管理的功能。企业管理员可以在企业控制台中配置企业网盘的各个选项、开启或关闭需要的功能模块、设定组织结构、自定义角色和权限，管理成员、设置水印、设定部门安全策略、iP访问策略、绑定账户和mac地址、监控网盘使用情况…. 主要栏目 企业配置：综合管理企业网盘的配置项，譬如空间分配、是否允许个人文件、允许的文件上传大小、历史版本有效期或历史版本数量、各种管理员分配、更改logo及登录背景、禁止或开启对外分享、是否接受邮件通知。各种企业配置选项里面都可以在企业配置栏目找到。 组织结构：统一管理和维护企业的组织结构及部门。能树状查看部门和管理部门。查看部门成员、分配部门空间、创建子部门、设定部门安全策略… 权限管理：创建角色和更改角色权限，同时可管理自定义文件权限。 成员管理：可以查找和筛选整个企业的成员账户，新增成员、批量导入成员、分配成员部门及角色、详细查看及管理每一个成员的信息及使用情况、成员离职一件交接、成员账户的增删改查、成员空间和流量的分配及限制。 标签管理：统一管理企业所使用的标签，添加标签和给标签分类，便于用户选择标签。 文件配置：添加文件审批可选流程，管理已经添加的审批流程。同时拥有文件黑名单功能，可以阻止特定类型的文件上传。 企业通知：创建企业通知，管理历史企业通知列表、发送企业通知。 分组管理：建立分组及管理分组。前台分享文件时可以选择分享给什么分组。 水印设置：管理文档的水印类型，水印参数调整，水印显示范围设定。 访问日志：管理及查询整个企业网盘的所有访问记录。可导出日志报表。 IP策略列表：可通过IP策略管理企业文件的上传下载行为。譬如：某个IP段禁止下载文件，回到某个IP段即可下载文件。 Mac地址绑定：可以把用户账号和特定设备mac地址绑定，让账号只能在绑定mac地址的设备上使用。也可以创建mac地址池。 统计分析：统计分析网盘的使用情况。包括系统活跃度、文件数量统计、活跃文件、一段时间内的新建文件数、每个月上传数、流量使用情况。 工作台推送：设定工作台的默认显示卡片。 系统配置（仅私有部署版本）：配置邮件服务器，绑定第三方SSO认证，设定第三方认证登录方式。 第三方账号同步（仅私有部署版本）：设置第三方账号同步时间，查询第三方账号同步记录。 可选模块（仅私有部署版本）：选择企业需要展现的功能模块，关闭某些功能模块。 监控预警：设定异常行为的预警，遇到异常行为通知管理员（譬如：用户大量删除文件） 传送文件配置：数据摆渡系统的配置，允许多套巴别鸟间进行数据摆渡。配置数据的接收端口及发送端口。" }, { "lang": "zh", "slug": "material-library", "title": "素材库", "description": "介绍企业素材库、素材分类、子素材库、瀑布流展示、权限控制、搜索筛选和 AI 搜图协同。", "category": "产品功能介绍", "top_category": "使用指南", "keywords": [ "素材库", "瀑布流", "图片素材", "AI搜图", "素材库API" ], "url": "zh/material-library.html", "source": "content/zh/material-library.md", "summary": "素材库 素材库是巴别鸟面向图片、品牌资产、设计素材、图纸、营销资料和可复用数字资产的集中管理能力。它与普通企业文件夹一样继承上传、预览、标签、搜索、分享、版本、日志和权限能力，同时增加面向素材管理的分类、子素材库、瀑布流展示和素材访问控制。 素材库界面 素材库适合将图片、设计稿、产品图、品牌资产、图纸和营销素材按分类统一管理。 瀑布流素材展示 瀑布流视图适合大量图片素材的快速浏览、挑选和预览。 适用场景 场景 典型内容 管理目标 品牌素材库 Logo、VI、字体、标准图、活动图 保证企业内外使用同一套最新版品牌资产 设计素材库 图片、PSD、AI、CAD、3D、渲染图 按项目、品类、客户或产品线沉淀可复用素材 营销资料库 海报、视频、产品图、宣传册 快速检索、预览、下载和分享给销售或渠道 工程图纸库 设计图、扫描件、过程图、交付图 结合权限、版本、归档和审计控制流转 AI 图片知识库 图片、PDF 中的图片、带标签素材 与 AI 搜图、图搜图、OCR 和自动标签配合使用 结构模型 素材库可以按企业业务划分为多个素材分类。 每个素材分类下可以建立子素材库，用于按品牌、项目、产品线、客户、年度、地区或业务部门继续细分。 素材文件仍然是巴别鸟文件对象，具备版本、日志、预览、下载、分享、移动、复制、标签、说明、批注和权限控制。 API 中提供素材库相关接口，可用于自动创建分类、创建子素材库或控制用户是否有素材库访问权。 管理入口 能力 说明 设置用户素材库权限 通过管理端或 API 控制用户是否有权访问素材库 创建素材分类 建立企业级素材分类，如品牌、营销、设计、工程、产品图 创建子素", "headings": [ { "level": 1, "title": "素材库", "id": "section" }, { "level": 2, "title": "适用场景", "id": "section-2" }, { "level": 2, "title": "结构模型", "id": "section-3" }, { "level": 2, "title": "管理入口", "id": "section-4" }, { "level": 2, "title": "权限与安全", "id": "section-5" }, { "level": 2, "title": "与 AI 搜图的关系", "id": "ai" }, { "level": 2, "title": "相关 API", "id": "api" } ], "images": [ { "src": "../assets/images/web-assets.webp", "alt": "素材库界面", "caption": "素材库适合将图片、设计稿、产品图、品牌资产、图纸和营销素材按分类统一管理。" }, { "src": "../assets/images/waterfall.webp", "alt": "瀑布流素材展示", "caption": "瀑布流视图适合大量图片素材的快速浏览、挑选和预览。" } ], "text": "素材库 素材库是巴别鸟面向图片、品牌资产、设计素材、图纸、营销资料和可复用数字资产的集中管理能力。它与普通企业文件夹一样继承上传、预览、标签、搜索、分享、版本、日志和权限能力，同时增加面向素材管理的分类、子素材库、瀑布流展示和素材访问控制。 素材库界面 素材库适合将图片、设计稿、产品图、品牌资产、图纸和营销素材按分类统一管理。 瀑布流素材展示 瀑布流视图适合大量图片素材的快速浏览、挑选和预览。 适用场景 场景 典型内容 管理目标 品牌素材库 Logo、VI、字体、标准图、活动图 保证企业内外使用同一套最新版品牌资产 设计素材库 图片、PSD、AI、CAD、3D、渲染图 按项目、品类、客户或产品线沉淀可复用素材 营销资料库 海报、视频、产品图、宣传册 快速检索、预览、下载和分享给销售或渠道 工程图纸库 设计图、扫描件、过程图、交付图 结合权限、版本、归档和审计控制流转 AI 图片知识库 图片、PDF 中的图片、带标签素材 与 AI 搜图、图搜图、OCR 和自动标签配合使用 结构模型 素材库可以按企业业务划分为多个素材分类。 每个素材分类下可以建立子素材库，用于按品牌、项目、产品线、客户、年度、地区或业务部门继续细分。 素材文件仍然是巴别鸟文件对象，具备版本、日志、预览、下载、分享、移动、复制、标签、说明、批注和权限控制。 API 中提供素材库相关接口，可用于自动创建分类、创建子素材库或控制用户是否有素材库访问权。 管理入口 能力 说明 设置用户素材库权限 通过管理端或 API 控制用户是否有权访问素材库 创建素材分类 建立企业级素材分类，如品牌、营销、设计、工程、产品图 创建子素材库 在分类下继续建立业务库，便于授权、运营和检索 文件上传与整理 支持网页端、客户端、同步、拖拽、右键上传和批量整理 瀑布流浏览 对图片素材提供更适合视觉筛选的列表方式 元数据与筛选 结合标签、说明、文件名、图片元数据、高级搜索和 AI 搜图筛选 权限与安全 素材库不应被理解为公开图库。它仍然受企业账号、部门、项目、文件访问控制、分享权限、安全策略和审计日志约束： 管理员可以控制哪些用户有权访问素材库。 素材库中的文件可继续设置文件夹权限、成员权限、有效期权限和分享权限。 对外分享素材时，可结合密码、有效期、下载权限、预览权限、水印和分享日志。 对敏感图片、设计稿、图纸或客户素材，可结合水印、下载控制、密级、访问日志和安全审计。 AI 搜图、图搜图、OCR 或自动标签应只在用户有权限访问的素材范围内返回结果。 与 AI 搜图的关系 素材库与智巢 AI 的文搜图、图搜图、图片 OCR、PDF 图片搜索和 AI 自动标签天然关联。对于图片数量大、人工命名不规范、目录层级很深的企业，素材库提供“存放和授权”的基础，AI 搜图提供“理解和查找”的能力。 相关 API 设置用户是否有权访问素材库 创建素材库分类 创建子素材库" }, { "lang": "zh", "slug": "watermark-security", "title": "水印功能", "description": "介绍文字水印、注册账户水印、图片水印、真水印、预览水印、下载水印和企业控制台设置。", "category": "产品功能介绍", "top_category": "使用指南", "keywords": [ "水印", "真水印", "预览水印", "下载水印", "安全" ], "url": "zh/watermark-security.html", "source": "content/zh/watermark-security.md", "summary": "水印功能 水印功能用于降低文件预览、下载、打印、分享和外发过程中的泄密风险。巴别鸟的水印能力分为界面/预览水印、输出文件水印和嵌入文件的真水印，并与权限控制、分享策略、审计日志、密级和企业控制台配置一起工作。 网页版文件预览与操作入口 水印通常与预览、下载、打印、分享和企业控制台策略共同生效，实际显示效果取决于部署配置和管理员设置。 水印类型 类型 说明 典型用途 文字水印 管理员设置固定文字，如企业名、项目名、保密级别 企业统一保密提示 注册账户水印 根据当前访问者账号信息显示水印 追溯截图、拍照或外泄来源 图片水印 使用企业 Logo 或指定图片叠加 品牌识别、版权保护 混合水印 私有云版本可按配置组合多种水印 高安全等级文件或外发资料 真水印 嵌入文件内容或输出文件中的水印 需要随文件传播保留标记的场景 生效范围 水印的使用范围可由管理员在企业控制台配置，常见策略包括： 对所有文件启用水印。 仅对所有对外分享文件启用水印。 允许文件分享者在分享时选择是否启用水印。 对特定企业、部门、安全策略、密级或文件流转场景启用。 结合“仅预览、禁止下载、允许下载带水印 PDF”等权限策略使用。 预览、下载与打印 白皮书资料中明确提到，预览文件可以内嵌水印，并可另存为带水印的 PDF 文件。开启水印时，预览转码服务器会对预览图片进行预处理，在图片中嵌入水印；图片类文件也可以另存为带水印 PDF。对于 Office、PDF、图片、CAD、3D、视频截图等不同格式，最终效果取决于预览/转码模块、文件格式和部署配置。 与权限体系的关系 水印不是权限的替代品，而是权限、审计和泄密追溯的一部分：", "headings": [ { "level": 1, "title": "水印功能", "id": "section" }, { "level": 2, "title": "水印类型", "id": "section-2" }, { "level": 2, "title": "生效范围", "id": "section-3" }, { "level": 2, "title": "预览、下载与打印", "id": "section-4" }, { "level": 2, "title": "与权限体系的关系", "id": "section-5" }, { "level": 2, "title": "管理员配置", "id": "section-6" }, { "level": 2, "title": "水印设置说明", "id": "section-7" }, { "level": 2, "title": "相关章节", "id": "section-8" }, { "level": 2, "title": "白皮书摘录", "id": "section-9" }, { "level": 3, "title": "主要栏目", "id": "section-10" } ], "images": [ { "src": "../assets/images/web-main.webp", "alt": "网页版文件预览与操作入口", "caption": "水印通常与预览、下载、打印、分享和企业控制台策略共同生效，实际显示效果取决于部署配置和管理员设置。" } ], "text": "水印功能 水印功能用于降低文件预览、下载、打印、分享和外发过程中的泄密风险。巴别鸟的水印能力分为界面/预览水印、输出文件水印和嵌入文件的真水印，并与权限控制、分享策略、审计日志、密级和企业控制台配置一起工作。 网页版文件预览与操作入口 水印通常与预览、下载、打印、分享和企业控制台策略共同生效，实际显示效果取决于部署配置和管理员设置。 水印类型 类型 说明 典型用途 文字水印 管理员设置固定文字，如企业名、项目名、保密级别 企业统一保密提示 注册账户水印 根据当前访问者账号信息显示水印 追溯截图、拍照或外泄来源 图片水印 使用企业 Logo 或指定图片叠加 品牌识别、版权保护 混合水印 私有云版本可按配置组合多种水印 高安全等级文件或外发资料 真水印 嵌入文件内容或输出文件中的水印 需要随文件传播保留标记的场景 生效范围 水印的使用范围可由管理员在企业控制台配置，常见策略包括： 对所有文件启用水印。 仅对所有对外分享文件启用水印。 允许文件分享者在分享时选择是否启用水印。 对特定企业、部门、安全策略、密级或文件流转场景启用。 结合“仅预览、禁止下载、允许下载带水印 PDF”等权限策略使用。 预览、下载与打印 白皮书资料中明确提到，预览文件可以内嵌水印，并可另存为带水印的 PDF 文件。开启水印时，预览转码服务器会对预览图片进行预处理，在图片中嵌入水印；图片类文件也可以另存为带水印 PDF。对于 Office、PDF、图片、CAD、3D、视频截图等不同格式，最终效果取决于预览/转码模块、文件格式和部署配置。 与权限体系的关系 水印不是权限的替代品，而是权限、审计和泄密追溯的一部分： 访问控制决定谁能看、编辑、下载、分享或打印。 水印用于在已授权访问时增加视觉提示和追溯标识。 分享权限决定外部访问者能否预览、下载、编辑或继续分享。 审计日志记录文件访问、分享、下载、权限调整等行为。 密级、IP 策略、Mac 绑定、二次验证和部门安全策略可进一步收紧访问边界。 管理员配置 管理员可在企业控制台维护水印类型、参数和显示范围。功能列表中列出的相关能力包括“水印类型选择及水印设置”和“嵌入文件的真水印”。私有化部署场景中，还可以结合企业 Logo、登录背景、模块开关、安全策略和定制转码服务进行配置。 水印设置说明 巴别鸟水印由管理员在企业控制台设置，可使用文字水印、注册账户水印、图片水印中的一种，私有云版本支持三种水印叠加；设置完成后，范围内文件按照管理员配置显示水印。 相关章节 权限体系 安全与审计 预览、批注与评审 分享与外发 白皮书摘录 巴别鸟企业控制台集中了管理员对整个企业进行管理的功能。企业管理员可以在企业控制台中配置企业网盘的各个选项、开启或关闭需要的功能模块、设定组织结构、自定义角色和权限，管理成员、设置水印、设定部门安全策略、iP访问策略、绑定账户和mac地址、监控网盘使用情况…. 主要栏目 企业配置：综合管理企业网盘的配置项，譬如空间分配、是否允许个人文件、允许的文件上传大小、历史版本有效期或历史版本数量、各种管理员分配、更改logo及登录背景、禁止或开启对外分享、是否接受邮件通知。各种企业配置选项里面都可以在企业配置栏目找到。 组织结构：统一管理和维护企业的组织结构及部门。能树状查看部门和管理部门。查看部门成员、分配部门空间、创建子部门、设定部门安全策略… 权限管理：创建角色和更改角色权限，同时可管理自定义文件权限。 成员管理：可以查找和筛选整个企业的成员账户，新增成员、批量导入成员、分配成员部门及角色、详细查看及管理每一个成员的信息及使用情况、成员离职一件交接、成员账户的增删改查、成员空间和流量的分配及限制。 标签管理：统一管理企业所使用的标签，添加标签和给标签分类，便于用户选择标签。 文件配置：添加文件审批可选流程，管理已经添加的审批流程。同时拥有文件黑名单功能，可以阻止特定类型的文件上传。 企业通知：创建企业通知，管理历史企业通知列表、发送企业通知。 分组管理：建立分组及管理分组。前台分享文件时可以选择分享给什么分组。 水印设置：管理文档的水印类型，水印参数调整，水印显示范围设定。 访问日志：管理及查询整个企业网盘的所有访问记录。可导出日志报表。 IP策略列表：可通过IP策略管理企业文件的上传下载行为。譬如：某个IP段禁止下载文件，回到某个IP段即可下载文件。 Mac地址绑定：可以把用户账号和特定设备mac地址绑定，让账号只能在绑定mac地址的设备上使用。也可以创建mac地址池。 统计分析：统计分析网盘的使用情况。包括系统活跃度、文件数量统计、活跃文件、一段时间内的新建文件数、每个月上传数、流量使用情况。 工作台推送：设定工作台的默认显示卡片。 系统配置（仅私有部署版本）：配置邮件服务器，绑定第三方SSO认证，设定第三方认证登录方式。 第三方账号同步（仅私有部署版本）：设置第三方账号同步时间，查询第三方账号同步记录。 可选模块（仅私有部署版本）：选择企业需要展现的功能模块，关闭某些功能模块。 监控预警：设定异常行为的预警，遇到异常行为通知管理员（譬如：用户大量删除文件） 传送文件配置：数据摆渡系统的配置，允许多套巴别鸟间进行数据摆渡。配置数据的接收端口及发送端口。" }, { "lang": "zh", "slug": "sync-client", "title": "同步与客户端", "description": "介绍任意文件夹同步、同步类型、冲突处理、客户端传输、锁定和 20 万文件夹同步能力。", "category": "产品功能介绍", "top_category": "使用指南", "keywords": [ "同步", "客户端", "冲突处理", "文件锁定" ], "url": "zh/sync-client.html", "source": "content/zh/sync-client.md", "summary": "同步与客户端 同步功能用于在本地电脑与巴别鸟云端文件夹之间建立持续同步关系。它不是简单“整盘复制”，而是由权限、同步方向、自动同步周期、文件锁定、冲突处理、黑名单和客户端任务管理共同组成的企业同步能力。 客户端创建同步 客户端可从本地文件夹创建同步任务，并选择云端目标位置。 客户端同步管理 同步管理用于查看同步状态、错误、冲突和多个同步任务。 核心能力 能力 说明 支持平台 云端到本地 云端任意文件夹可同步到本地任意位置，前提是用户拥有下载权限 Windows 客户端、Mac 客户端 本地到云端 本地任意文件夹可同步到云端任意位置，前提是用户拥有上传权限 Windows 客户端、Mac 客户端 双向同步 本地与云端互相同步，适合长期维护同一批工作文件 Windows 客户端、Mac 客户端 上行同步 本地变化上传到云端，适合采集、备份、集中归档 Windows 客户端、Mac 客户端 下行同步 云端变化下载到本地，适合资料分发、离线使用、标准素材下发 Windows 客户端、Mac 客户端 自动同步时间 可设定自动同步时间或同步周期 Windows 客户端、Mac 客户端 同步黑名单 指定某些文件类型或临时文件不参与同步 Windows 客户端、Mac 客户端 编辑锁定 同步文件夹中的文件编辑时自动锁定，降低多人冲突 Windows 客户端、Mac 客户端 权限前提 从云端同步到本地需要拥有目标文件夹或文件的下载权限。 从本地同步到云端需要拥有云端目标目录的上传权限。 如果文件夹权限、分享权限、项目权限或有效期权限变化，同步行为也应跟随变化。 管理员关闭个人空间、限制下载、限制", "headings": [ { "level": 1, "title": "同步与客户端", "id": "section" }, { "level": 2, "title": "核心能力", "id": "section-2" }, { "level": 2, "title": "权限前提", "id": "section-3" }, { "level": 2, "title": "冲突与版本", "id": "section-4" }, { "level": 2, "title": "与映射盘的区别", "id": "section-5" }, { "level": 2, "title": "适用建议", "id": "section-6" }, { "level": 3, "title": "概述", "id": "section-7" }, { "level": 3, "title": "使用方式", "id": "section-8" }, { "level": 3, "title": "总结", "id": "section-9" } ], "images": [ { "src": "../assets/images/client-sync-create.webp", "alt": "客户端创建同步", "caption": "客户端可从本地文件夹创建同步任务，并选择云端目标位置。" }, { "src": "../assets/images/client-sync-manage.webp", "alt": "客户端同步管理", "caption": "同步管理用于查看同步状态、错误、冲突和多个同步任务。" } ], "text": "同步与客户端 同步功能用于在本地电脑与巴别鸟云端文件夹之间建立持续同步关系。它不是简单“整盘复制”，而是由权限、同步方向、自动同步周期、文件锁定、冲突处理、黑名单和客户端任务管理共同组成的企业同步能力。 客户端创建同步 客户端可从本地文件夹创建同步任务，并选择云端目标位置。 客户端同步管理 同步管理用于查看同步状态、错误、冲突和多个同步任务。 核心能力 能力 说明 支持平台 云端到本地 云端任意文件夹可同步到本地任意位置，前提是用户拥有下载权限 Windows 客户端、Mac 客户端 本地到云端 本地任意文件夹可同步到云端任意位置，前提是用户拥有上传权限 Windows 客户端、Mac 客户端 双向同步 本地与云端互相同步，适合长期维护同一批工作文件 Windows 客户端、Mac 客户端 上行同步 本地变化上传到云端，适合采集、备份、集中归档 Windows 客户端、Mac 客户端 下行同步 云端变化下载到本地，适合资料分发、离线使用、标准素材下发 Windows 客户端、Mac 客户端 自动同步时间 可设定自动同步时间或同步周期 Windows 客户端、Mac 客户端 同步黑名单 指定某些文件类型或临时文件不参与同步 Windows 客户端、Mac 客户端 编辑锁定 同步文件夹中的文件编辑时自动锁定，降低多人冲突 Windows 客户端、Mac 客户端 权限前提 从云端同步到本地需要拥有目标文件夹或文件的下载权限。 从本地同步到云端需要拥有云端目标目录的上传权限。 如果文件夹权限、分享权限、项目权限或有效期权限变化，同步行为也应跟随变化。 管理员关闭个人空间、限制下载、限制上传或调整模块授权时，同步入口和能力可能随配置变化。 Linux/信创客户端由于系统文件管理界面限制，不支持同步文件夹和映射盘能力；网页端、移动端也不承担本地文件夹同步。 冲突与版本 同步文件夹中的文件被编辑或覆盖后，客户端会监控本地变化并上传为云端新版本。若本地文件与云端文件同时发生变化，可能产生版本冲突。同步文件夹出现惊叹号角标通常表示本地与云端存在版本冲突，系统一般会在再次扫描更新后尝试处理；如长时间未恢复，应手动确认当前需要保留的版本，再通过下载覆盖或作为新版本上传处理。 与映射盘的区别 维度 同步文件夹 虚拟映射盘 本地存储 会把同步范围内文件保存到本地 默认不完整占用本地空间，按需缓存 离线能力 已同步文件可在离线时使用 更依赖网络连接 适用场景 固定工作资料、本地批量处理、离线办公、数据采集 像访问本地磁盘一样浏览云端资料 风险点 同步范围大时占用磁盘，需要处理冲突 网络或权限变化会直接影响访问体验 适用建议 需要长期离线编辑或本地批量处理的目录，优先使用同步。 只需随时浏览大量云端资料、不想占用本地磁盘，优先使用映射盘。 对设计、工程、视频、素材等大文件场景，应合理设置同步范围和黑名单。 对保密资料，应结合下载权限、水印、审计、密级和部门安全策略。 概述 文件同步是巴别鸟企业网盘最受欢迎的功能之一。它允许用户将本地任意文件夹同步到云端或者把云端任意文件夹同步到本地，实现云端和本地文件的实时同步。这个部分包含了以下关键功能： 同步管理：巴别鸟支持创建多个同步，并可在同步管理列表里统一管理。 多人协作：巴别鸟同步是为多人协作而设计的。它自动锁定文件，防止多人同时编辑造成冲突，还有冲突处理机制和版本管理。 和权限一致：巴别鸟同步会判断用户的权限。没有下载权限的用户也不会因同步而下载文件，保证权限的一致性和闭环，这意味着，用户可以通过权限来设定哪些文件夹可以同步。 多种同步类型：巴别鸟支持多种同步类型，用户可以根据具体需求选择合适的同步方式： 双向同步：云端和本地文件夹保持内容一致，任何一侧的修改都将同步到另一侧。 单向向上同步：本地更新会同步到云端，但云端更新不影响本地。 单向向下同步：云端更新会同步到本地，但本地更新不影响云端。 强大技术优势：巴别鸟企业网盘同步功能拥有多项技术优势，确保性能和稳定性： 支持大规模文件夹：巴别鸟支持高达20万个文件的文件夹同步。 文件编辑锁定：编辑同步文件时，文件会自动锁定，以防止多人编辑引发冲突。 冲突处理机制：针对同一文件的编辑冲突，巴别鸟提供了冲突处理机制，确保文件版本的完整性。 版本管理：文件同步功能和版本管理配合，能保证本地的文件夹也不会因为误操作等原因被覆盖从而丢失内容，即使出现文件冲突，冲突的两个版本文件也都会得到保存。 异步情况下的错误处理：文件同步功能还包括对异步情况下的错误处理和修复。 使用方式 开启同步：本地文件夹右键菜单选择巴别鸟——同步该文件夹。 选择同步方式：用户可以在同步时选择合适的同步方式，包括单向同步、双向同步等。 权限配置：通过权限配置，用户可以实现更多的自定义同步方式，根据需要限制文件删除或其他操作。 多人协作：多人协作下，文件编辑时会自动锁定，以避免多人同时编辑造成冲突。冲突处理机制确保文件版本的一致性。 版本管理：文件同步功能支持版本管理，用户可以查看以前的文件版本并进行恢复。 总结 巴别鸟企业网盘的文件同步功能是一项出色的工具，可以实现云端和本地文件的实时同步。多种同步方式、权限配置、多人协作、版本管理等技术优势确保了高性能、稳定性和安全性。" }, { "lang": "zh", "slug": "mapped-drive", "title": "虚拟映射盘", "description": "介绍像本地磁盘一样访问云端文件的映射盘能力，以及与 WebDAV/SMB 的差异。", "category": "产品功能介绍", "top_category": "使用指南", "keywords": [ "映射盘", "云桥", "WebDAV", "SMB" ], "url": "zh/mapped-drive.html", "source": "content/zh/mapped-drive.md", "summary": "虚拟映射盘 虚拟映射盘让用户在 Windows 资源管理器或 macOS Finder 中像访问本地磁盘一样访问巴别鸟云端文件。它适合目录层级深、文件数量多、用户已经习惯本地文件管理器和专业软件打开文件的场景。 客户端主界面 客户端承载上传下载、同步、映射盘和本地编辑等桌面端能力。 核心能力 能力 说明 支持平台 资源管理器/Finder 访问 在系统文件管理器中访问网盘目录 Windows 客户端、Mac 客户端 虚拟盘符/虚拟路径 可通过盘符或虚拟路径进入云端文件 Windows 客户端、Mac 客户端 缓存管理 文件按需下载与缓存，减少完整占用本地磁盘 Windows 客户端、Mac 客户端 编辑自动锁定 在映射盘中打开编辑文件时自动锁定，减少多人编辑冲突 Windows 客户端、Mac 客户端 文件引用与关联资源 点击文件可打开文件引用和关联资源 Windows 客户端、Mac 客户端 第三方程序访问 本地应用可像访问本地路径一样访问映射盘文件 Windows 客户端、Mac 客户端 工作方式 虚拟映射盘使用类似 OneDrive、iCloud 的本地虚拟盘技术，在操作系统中呈现云端目录。文件图标、目录结构和基本操作在系统文件管理器中可见，用户可以打开、复制、粘贴、删除或用第三方软件访问文件。与完整同步不同，映射盘通常不把全部云端文件预先保存到本地，而是在需要时下载或缓存。 权限与网络 用户能看到和操作的文件范围仍由巴别鸟权限体系决定。 映射盘访问依赖网络连接；网络不可用或权限失效时，未缓存文件无法正常打开。 文件编辑、上传新版本、删除、移动、分享等行为仍应受文件夹权限", "headings": [ { "level": 1, "title": "虚拟映射盘", "id": "section" }, { "level": 2, "title": "核心能力", "id": "section-2" }, { "level": 2, "title": "工作方式", "id": "section-3" }, { "level": 2, "title": "权限与网络", "id": "section-4" }, { "level": 2, "title": "与 WebDAV/SMB 的区别", "id": "webdav-smb" }, { "level": 2, "title": "适用建议", "id": "section-5" }, { "level": 2, "title": "白皮书详细说明", "id": "section-6" }, { "level": 3, "title": "概述", "id": "section-7" }, { "level": 3, "title": "主要特点", "id": "section-8" }, { "level": 3, "title": "技术优势（对比WebDAV和SMB）", "id": "webdav-smb-2" }, { "level": 3, "title": "应用场景", "id": "section-9" } ], "images": [ { "src": "../assets/images/client-main.webp", "alt": "客户端主界面", "caption": "客户端承载上传下载、同步、映射盘和本地编辑等桌面端能力。" } ], "text": "虚拟映射盘 虚拟映射盘让用户在 Windows 资源管理器或 macOS Finder 中像访问本地磁盘一样访问巴别鸟云端文件。它适合目录层级深、文件数量多、用户已经习惯本地文件管理器和专业软件打开文件的场景。 客户端主界面 客户端承载上传下载、同步、映射盘和本地编辑等桌面端能力。 核心能力 能力 说明 支持平台 资源管理器/Finder 访问 在系统文件管理器中访问网盘目录 Windows 客户端、Mac 客户端 虚拟盘符/虚拟路径 可通过盘符或虚拟路径进入云端文件 Windows 客户端、Mac 客户端 缓存管理 文件按需下载与缓存，减少完整占用本地磁盘 Windows 客户端、Mac 客户端 编辑自动锁定 在映射盘中打开编辑文件时自动锁定，减少多人编辑冲突 Windows 客户端、Mac 客户端 文件引用与关联资源 点击文件可打开文件引用和关联资源 Windows 客户端、Mac 客户端 第三方程序访问 本地应用可像访问本地路径一样访问映射盘文件 Windows 客户端、Mac 客户端 工作方式 虚拟映射盘使用类似 OneDrive、iCloud 的本地虚拟盘技术，在操作系统中呈现云端目录。文件图标、目录结构和基本操作在系统文件管理器中可见，用户可以打开、复制、粘贴、删除或用第三方软件访问文件。与完整同步不同，映射盘通常不把全部云端文件预先保存到本地，而是在需要时下载或缓存。 权限与网络 用户能看到和操作的文件范围仍由巴别鸟权限体系决定。 映射盘访问依赖网络连接；网络不可用或权限失效时，未缓存文件无法正常打开。 文件编辑、上传新版本、删除、移动、分享等行为仍应受文件夹权限、项目权限和安全策略控制。 Linux/信创客户端不支持同步文件夹和映射盘功能，适合通过网页端、客户端常规文件列表或其他已部署入口访问。 与 WebDAV/SMB 的区别 维度 虚拟映射盘 WebDAV/SMB 权限一致性 与巴别鸟账号、部门、项目、分享和文件访问控制保持一致 往往需要单独网关或协议权限映射 产品集成 可结合版本、锁定、日志、关联资源、客户端编辑 更偏通用文件协议 体验目标 面向巴别鸟云端文件的本地化访问体验 面向网络文件系统访问 适用边界 依赖客户端和企业配置 依赖协议服务和网络环境 适用建议 大量浏览云端资料但不希望占用本地磁盘时，优先使用映射盘。 需要离线处理固定目录时，优先使用同步文件夹。 使用 CAD、设计、视频、工程和办公类专业软件时，可通过映射盘保持本地打开习惯。 对敏感目录，应结合文件访问权限、下载控制、水印和日志审计。 白皮书详细说明 概述 虚拟映射盘：巴别鸟企业网盘引入了虚拟映射盘功能，提供了一种无缝连接云端文件的方式，在windows资源管理器或着mac的访达中都可以类似于访问本地磁盘一样访问映射盘，从而实现轻松访问云端文件的体验。 技术实现：巴别鸟虚拟映射盘使用了类似OneDrive、iCloud的技术方案，它在操作系统中创建了一个虚拟磁盘，将云端文件映射到用户的本地计算机上，使得这些文件在用户的文件浏览器中可见。 主要特点 本地访问云端文件：虚拟映射盘允许用户通过本地文件资源管理器或Finder等工具访问其巴别鸟企业网盘中的文件和文件夹。 无本地存储占用：与传统的文件同步方式不同，虚拟映射盘并不将云端文件实际存储在用户的本地磁盘上，因此不会占用本地存储空间。文件只在需要时进行缓存或下载。 在线访问：虚拟映射盘需要网络连接才能访问云端文件。文件图标实际上只是云端文件的链接，因此需要在线才能查看和操作这些文件，权限也和云端一致。 透明操作：用户可以像操作本地文件一样操作虚拟映射盘中的文件，包括打开、复制、粘贴、删除等操作。 自动同步：文件的更改会自动同步到云端，从而保持云端文件与虚拟映射盘中的文件的一致性。 关联文件：在巴别鸟映射盘中打开有关联文件的文件，会自动加载关联文件，实现和本地文件夹打开文件一样的效果。譬如：打开含有大量参照文件的DWG（AutoCAD文件）、或者有关联其他文件的Excel图表。 技术优势（对比WebDAV和SMB） 权限一致性：不同于WebDAV或SMB挂载（必须使用兼容WebDAV或SMB的权限规则），巴别鸟映射盘是直接调用操作系统底层文件系统实现的，可以实现和巴别鸟一致的权限控制。（譬如：只能预览但不能下载或另存为。）在WebDAV和SMB中，仅查看权限实际为只读，只要是可见的文件，用户都可以通过只读模式打开并获得文件，失去了对文件的管控。 更高的性能：巴别鸟映射盘直接对应巴别鸟服务器相关接口，没有转发和中间处理环节，可以直接获取服务器提供的文件列表以虚拟方式打开文件夹，所以能提供更高的性能，打开文件列表和查阅文件不会卡顿。使用WebDAV只能打开一个文件夹临时载入一个列表，文件夹文件数量超过一定数量（和设备性能及网速有关，一般数量是超过300个）就会发生严重的卡顿和访问缓慢。使用对象存储系统的超大文件夹WebDAV并不能很好支持。 更安全：巴别鸟映射盘能根据权限判断每个人可以查看的文件夹和文件夹中的文件，不同权限的人查看同一个文件夹看到的内容可以不同，SMB和WebDAV目前做不到。同时巴别鸟的文件分块加密存储于对象存储，但如果是分块加密存储的文件，使用WebDAV就需要分文件解密后才能获得文件列表，这意味着，支持WebDAV的产品要么数据存储没有加密，要么WebDAV性能极差文件数量超过一定范围即不可用。 可控性：不同于使用第三方软件挂载的WebDAV及SMB，巴别鸟映射盘为自主研发驱动器，对驱动器的操作、菜单及运行方式、功能实现都具有可控性，并且能对产品质量及使用体验一致性负责。未来也能有更多的功能扩展。 主流企业级解决方案：无论是微软的OneDrive、Google的Google Drive或是苹果的iCloud、BOX的BOX Drive还是国内主流互联网企业网盘厂商，都使用了类似巴别鸟映射盘的解决方案，而不是简单接入WebDAV（接入WebDAV只要做协议兼容并开放接入即可，实现简单，为什么主流企业级厂商还都花费大量精力自研映射盘呢？）。WebDAV主要应用场景还是不需要进行复杂权限判断也不需要存储加密并开放所有文件的个人或小团队使用。SMB的主要使用场景也是个人及小团队的开放文件共享（明文存储）。 应用场景 虚拟映射盘适用于需要频繁访问云端文件、但不想改变本地磁盘的使用习惯也不想占用本地存储空间的用户。这个功能使得用户可以像访问本地文件一样访问云端文件，并且在其他应用程序里如同打开本地文件夹一样访问网盘，不改变使用习惯，便于文件的管理和使用。" }, { "lang": "zh", "slug": "encrypted-folder", "title": "加密文件夹", "description": "介绍巴别鸟加密文件夹的使用场景、创建方式、访问方式、密码安全和分享限制。", "category": "产品功能介绍", "top_category": "使用指南", "keywords": [ "加密文件夹", "文件保险箱", "密码访问", "安全" ], "url": "zh/encrypted-folder.html", "source": "content/zh/encrypted-folder.md", "summary": "加密文件夹 加密文件夹用于在共享网盘中建立需要密码才能访问的特殊文件夹。它适合团队共享空间中需要额外保护的资料，例如未发布文件、私密资料、合同、人事资料、财务资料、研发资料或临时不想公开的项目文件。 新建加密文件夹入口 在新建菜单中选择“加密文件夹”，即可创建需要密码才能访问的文件夹。 功能定位 加密文件夹不是替代巴别鸟原有权限体系，而是在权限之外增加一层“知道密码才能进入”的访问保护。用户即使在部门、项目或分享中拥有文件夹入口，也需要输入密码才能查看文件夹内容。 适用场景包括： 共享部门空间里有部分文件只希望掌握密码的人访问。 项目资料尚未发布，需要先临时封存，发布后再迁移或调整访问策略。 私密资料需要作为“文件保险箱”管理，降低误点、误分享和普通权限配置失误的风险。 对外分享加密文件夹内文件时，仍希望接收者必须输入加密文件夹密码。 创建方式 1. 在目标目录点击“新建”。 2. 选择“加密文件夹”。 3. 输入文件夹名称和密码。 4. 保存后，文件列表中会生成带锁标识的加密文件夹。 设置加密文件夹密码 创建时需要输入文件夹名称和密码，密码应由创建者自行妥善保存。 访问方式 打开加密文件夹时，系统会要求输入密码。密码正确后，用户可以像普通文件夹一样在其中上传、下载、创建、预览、编辑、分享或使用其他文件功能；具体可执行操作仍受用户原有权限、文件访问控制、分享权限和管理员配置影响。 带锁标识的加密文件夹 创建成功后，加密文件夹会显示锁标识；进入时需要输入密码。 密码安全 加密文件夹采用匿名加密方式，密码遗失后无法找回。即使是网盘运营方或技术人员，也不能帮助用户解密或恢复密码。密码", "headings": [ { "level": 1, "title": "加密文件夹", "id": "section" }, { "level": 2, "title": "功能定位", "id": "section-2" }, { "level": 2, "title": "创建方式", "id": "section-3" }, { "level": 2, "title": "访问方式", "id": "section-4" }, { "level": 2, "title": "密码安全", "id": "section-5" }, { "level": 2, "title": "与分享的关系", "id": "section-6" }, { "level": 2, "title": "与其他安全功能的组合", "id": "section-7" } ], "images": [ { "src": "../assets/images/encrypted-folder-create.png", "alt": "新建加密文件夹入口", "caption": "在新建菜单中选择“加密文件夹”，即可创建需要密码才能访问的文件夹。" }, { "src": "../assets/images/encrypted-folder-password.png", "alt": "设置加密文件夹密码", "caption": "创建时需要输入文件夹名称和密码，密码应由创建者自行妥善保存。" }, { "src": "../assets/images/encrypted-folder-locked.png", "alt": "带锁标识的加密文件夹", "caption": "创建成功后，加密文件夹会显示锁标识；进入时需要输入密码。" } ], "text": "加密文件夹 加密文件夹用于在共享网盘中建立需要密码才能访问的特殊文件夹。它适合团队共享空间中需要额外保护的资料，例如未发布文件、私密资料、合同、人事资料、财务资料、研发资料或临时不想公开的项目文件。 新建加密文件夹入口 在新建菜单中选择“加密文件夹”，即可创建需要密码才能访问的文件夹。 功能定位 加密文件夹不是替代巴别鸟原有权限体系，而是在权限之外增加一层“知道密码才能进入”的访问保护。用户即使在部门、项目或分享中拥有文件夹入口，也需要输入密码才能查看文件夹内容。 适用场景包括： 共享部门空间里有部分文件只希望掌握密码的人访问。 项目资料尚未发布，需要先临时封存，发布后再迁移或调整访问策略。 私密资料需要作为“文件保险箱”管理，降低误点、误分享和普通权限配置失误的风险。 对外分享加密文件夹内文件时，仍希望接收者必须输入加密文件夹密码。 创建方式 1. 在目标目录点击“新建”。 2. 选择“加密文件夹”。 3. 输入文件夹名称和密码。 4. 保存后，文件列表中会生成带锁标识的加密文件夹。 设置加密文件夹密码 创建时需要输入文件夹名称和密码，密码应由创建者自行妥善保存。 访问方式 打开加密文件夹时，系统会要求输入密码。密码正确后，用户可以像普通文件夹一样在其中上传、下载、创建、预览、编辑、分享或使用其他文件功能；具体可执行操作仍受用户原有权限、文件访问控制、分享权限和管理员配置影响。 带锁标识的加密文件夹 创建成功后，加密文件夹会显示锁标识；进入时需要输入密码。 密码安全 加密文件夹采用匿名加密方式，密码遗失后无法找回。即使是网盘运营方或技术人员，也不能帮助用户解密或恢复密码。密码丢失后，该文件夹无法正常打开，通常只能删除并重新建立。 使用时应注意： 不要把加密文件夹密码写入同一文件夹内。 不要在公开聊天群或无权限控制的文档中传播密码。 对长期使用的高敏资料，应结合部门权限、文件访问控制、水印、审计日志和密级策略。 离职、项目结束或资料公开后，应及时清理密码知情范围，并按企业制度迁移、归档或删除资料。 与分享的关系 加密文件夹内的文件即使被分享给其他人，访问者仍需要输入加密文件夹密码才能访问。分享权限只控制接收者在分享范围内能否查看、下载、编辑、批注或继续分享；加密文件夹密码控制是否能进入该加密空间。 与其他安全功能的组合 功能 作用 文件访问控制 指定成员、角色或项目成员对文件/文件夹的权限 水印 在预览、下载或输出文件时增加追溯标识 敏感内容识别 识别和标记可能包含敏感内容的文件 审计日志 记录访问、下载、分享、权限调整等行为 IP 策略与 Mac 绑定 限制账号在特定网络或设备中使用 密级与安全策略 对部门或文件设置更高的保密要求" }, { "lang": "zh", "slug": "sensitive-content-recognition", "title": "敏感内容识别", "description": "介绍巴别鸟敏感内容识别的配置入口、识别策略、处置方式、适用场景和权限关系。", "category": "产品功能介绍", "top_category": "使用指南", "keywords": [ "敏感内容识别", "敏感词", "风险识别", "安全审计", "管理工具" ], "url": "zh/sensitive-content-recognition.html", "source": "content/zh/sensitive-content-recognition.md", "summary": "敏感内容识别 敏感内容识别用于发现企业网盘中可能包含敏感内容的文件，并根据配置进行标记、限制查看、限制分享或辅助管理员处理。该能力在 v9.4.2.2606171439 版本口径中正式推出，公开更新日志中也记录了企业控制台“管理工具”增加敏感内容识别入口。 敏感内容识别设置界面 管理员可在企业控制台管理工具中配置敏感内容识别，并查看命中的敏感内容文件列表。 功能定位 企业网盘中常见的高风险文件包括合同、证照、个人信息、客户资料、财务数据、报价文件、研发资料、源代码、涉密项目材料和受监管行业资料。敏感内容识别的目标不是替代人工判断，而是先把可能有风险的文件筛出来，减少完全依赖人工巡检的压力。 管理入口 公开资料显示，企业控制台中的“文件设置”已调整为“管理工具”，并在其中增加“敏感内容识别”Tab。管理员可在该入口开启或关闭识别功能，维护自定义敏感词，并查询含敏感内容的文件列表。 常见配置包括： 开启或关闭敏感内容识别。 维护自定义敏感词，多个敏感词可用分隔符区分。 上传敏感词文件，便于批量维护敏感词库。 设置命中文件的处理策略。 查询和定位含敏感内容文件列表。 识别与处置 能力 说明 文件标记 命中敏感内容的文件会被标记，便于管理员识别和追踪 禁止查看 可配置为禁止查看命中文件，降低敏感内容继续扩散的风险 禁止分享 可配置为禁止分享命中文件，避免敏感内容被外发 命中列表 管理员可查看含敏感内容文件列表，并定位到对应文件 自定义敏感词 企业可按行业、部门、项目或制度维护敏感词 实际处置策略应以企业部署版本、授权模块和管理员配置为准。涉及误报、业务例外或合规确认时，建议由管理员、安", "headings": [ { "level": 1, "title": "敏感内容识别", "id": "section" }, { "level": 2, "title": "功能定位", "id": "section-2" }, { "level": 2, "title": "管理入口", "id": "section-3" }, { "level": 2, "title": "识别与处置", "id": "section-4" }, { "level": 2, "title": "适用场景", "id": "section-5" }, { "level": 2, "title": "与权限体系的关系", "id": "section-6" }, { "level": 2, "title": "版本说明", "id": "section-7" } ], "images": [ { "src": "../assets/images/sensitive-content-recognition.jpg", "alt": "敏感内容识别设置界面", "caption": "管理员可在企业控制台管理工具中配置敏感内容识别，并查看命中的敏感内容文件列表。" } ], "text": "敏感内容识别 敏感内容识别用于发现企业网盘中可能包含敏感内容的文件，并根据配置进行标记、限制查看、限制分享或辅助管理员处理。该能力在 v9.4.2.2606171439 版本口径中正式推出，公开更新日志中也记录了企业控制台“管理工具”增加敏感内容识别入口。 敏感内容识别设置界面 管理员可在企业控制台管理工具中配置敏感内容识别，并查看命中的敏感内容文件列表。 功能定位 企业网盘中常见的高风险文件包括合同、证照、个人信息、客户资料、财务数据、报价文件、研发资料、源代码、涉密项目材料和受监管行业资料。敏感内容识别的目标不是替代人工判断，而是先把可能有风险的文件筛出来，减少完全依赖人工巡检的压力。 管理入口 公开资料显示，企业控制台中的“文件设置”已调整为“管理工具”，并在其中增加“敏感内容识别”Tab。管理员可在该入口开启或关闭识别功能，维护自定义敏感词，并查询含敏感内容的文件列表。 常见配置包括： 开启或关闭敏感内容识别。 维护自定义敏感词，多个敏感词可用分隔符区分。 上传敏感词文件，便于批量维护敏感词库。 设置命中文件的处理策略。 查询和定位含敏感内容文件列表。 识别与处置 能力 说明 文件标记 命中敏感内容的文件会被标记，便于管理员识别和追踪 禁止查看 可配置为禁止查看命中文件，降低敏感内容继续扩散的风险 禁止分享 可配置为禁止分享命中文件，避免敏感内容被外发 命中列表 管理员可查看含敏感内容文件列表，并定位到对应文件 自定义敏感词 企业可按行业、部门、项目或制度维护敏感词 实际处置策略应以企业部署版本、授权模块和管理员配置为准。涉及误报、业务例外或合规确认时，建议由管理员、安全保密员或业务负责人复核。 适用场景 合同、报价、招投标、商务谈判资料。 身份证、手机号、邮箱、地址、银行卡等个人信息。 财务报表、薪酬数据、发票、付款信息。 客户名单、渠道资料、销售线索和合作协议。 研发文档、图纸、代码、内部制度和未发布内容。 需要符合行业合规、审计或保密制度的资料库。 与权限体系的关系 敏感内容识别负责发现风险，权限体系负责控制访问。建议组合使用： 使用部门角色和项目权限限定基础访问范围。 使用文件访问控制对高风险文件做额外授权。 使用水印和日志保留访问追踪。 使用分享审批、禁止对外分享或禁止下载控制外发。 对极敏资料使用加密文件夹或密级策略再增加保护。 版本说明 v9.4.2.2606171439 的最新口径包含“推出敏感内容识别功能”。如果企业仍处于更早部署版本，可能只看到企业控制台入口、内部测试能力或未开放模块；是否可用以实际部署和授权为准。" }, { "lang": "zh", "slug": "online-editing", "title": "在线编辑", "description": "独立介绍 Office 在线编辑、轻文档、Markdown/代码文本、KM 思维导图、draw.io 流程图和权限体系。", "category": "在线协作", "top_category": "使用指南", "keywords": [ "在线编辑", "OnlyOffice", "轻文档", "Markdown", "KM", "draw.io", "权限" ], "url": "zh/online-editing.html", "source": "content/zh/online-editing.md", "summary": "在线编辑 在线编辑覆盖 Office 文档在线协同编辑、轻文档在线编辑、Markdown/代码/文本编辑、KM 思维导图、draw.io 流程图，以及客户端编辑和权限控制。 网页版文件列表 在线编辑通常从文件列表或右键菜单进入，并受文件权限、分享权限、锁定状态和企业模块配置共同控制。 能力总览 类型 默认能力 说明 Office 在线编辑 OnlyOffice 默认使用 OnlyOffice，支持 Word、Excel、PPT、WPS 等文档在线编辑和多人协作 其他在线 Office 可接入 私有化部署可按需求对接 Office 365、WPS Online、永中 Office 等支持 Web/API 的在线 Office 轻文档 可作为独立轻量文档形态 适合快速记录、在线协作、知识沉淀和不需要传统 Office 排版的场景；参考资料： Markdown / 代码 / 文本 自带文本编辑器 可编辑 TXT、MD、RTF，以及 CSS、JS、JSP 等文本/代码类文件 思维导图 KM 格式 默认保存为 .KM ，可导出 KM、TXT、MD、SVG、PNG、Xmind 流程图 draw.io 支持 draw.io 流程图在线编辑；是否默认开启取决于模块授权和部署配置 客户端编辑 本地应用 调用本地软件编辑云端文件，保存后自动上传为新版本 权限体系 在线编辑不是单独绕过权限的入口。用户能否编辑取决于以下权限和状态： 用户是否拥有该文件或文件夹的在线编辑、编辑、上传新版本或相应自定义文件权限。 文件是否处于客户端编辑锁定、在线编辑锁定、审批锁定、定稿或归档状态。 分享场景中，分享者是否", "headings": [ { "level": 1, "title": "在线编辑", "id": "section" }, { "level": 2, "title": "能力总览", "id": "section-2" }, { "level": 2, "title": "权限体系", "id": "section-3" }, { "level": 2, "title": "Office 在线编辑", "id": "office" }, { "level": 3, "title": "在线编辑模块概述", "id": "section-4" }, { "level": 3, "title": "技术基础", "id": "section-5" }, { "level": 3, "title": "主要功能", "id": "section-6" }, { "level": 3, "title": "用户体验", "id": "section-7" }, { "level": 3, "title": "企业协作", "id": "section-8" }, { "level": 3, "title": "开放API", "id": "api" }, { "level": 3, "title": "其他在线编辑器", "id": "section-9" }, { "level": 2, "title": "客户端编辑", "id": "section-10" }, { "level": 3, "title": "客户端编辑概述", "id": "section-11" }, { "level": 3, "title": "技术实现", "id": "section-12" }, { "level": 3, "title": "主要功能", "id": "section-13" }, { "level": 3, "title": "用户体验", "id": "section-14" }, { "level": 3, "title": "技术挑战", "id": "section-15" }, { "level": 2, "title": "轻文档在线编辑", "id": "section-16" }, { "level": 2, "title": "Markdown、代码和文本在线编辑", "id": "markdown" }, { "level": 2, "title": "思维导图在线编辑", "id": "section-17" }, { "level": 2, "title": "流程图在线编辑", "id": "section-18" } ], "images": [ { "src": "../assets/images/web-main.webp", "alt": "网页版文件列表", "caption": "在线编辑通常从文件列表或右键菜单进入，并受文件权限、分享权限、锁定状态和企业模块配置共同控制。" } ], "text": "在线编辑 在线编辑覆盖 Office 文档在线协同编辑、轻文档在线编辑、Markdown/代码/文本编辑、KM 思维导图、draw.io 流程图，以及客户端编辑和权限控制。 网页版文件列表 在线编辑通常从文件列表或右键菜单进入，并受文件权限、分享权限、锁定状态和企业模块配置共同控制。 能力总览 类型 默认能力 说明 Office 在线编辑 OnlyOffice 默认使用 OnlyOffice，支持 Word、Excel、PPT、WPS 等文档在线编辑和多人协作 其他在线 Office 可接入 私有化部署可按需求对接 Office 365、WPS Online、永中 Office 等支持 Web/API 的在线 Office 轻文档 可作为独立轻量文档形态 适合快速记录、在线协作、知识沉淀和不需要传统 Office 排版的场景；参考资料： Markdown / 代码 / 文本 自带文本编辑器 可编辑 TXT、MD、RTF，以及 CSS、JS、JSP 等文本/代码类文件 思维导图 KM 格式 默认保存为 .KM ，可导出 KM、TXT、MD、SVG、PNG、Xmind 流程图 draw.io 支持 draw.io 流程图在线编辑；是否默认开启取决于模块授权和部署配置 客户端编辑 本地应用 调用本地软件编辑云端文件，保存后自动上传为新版本 权限体系 在线编辑不是单独绕过权限的入口。用户能否编辑取决于以下权限和状态： 用户是否拥有该文件或文件夹的在线编辑、编辑、上传新版本或相应自定义文件权限。 文件是否处于客户端编辑锁定、在线编辑锁定、审批锁定、定稿或归档状态。 分享场景中，分享者是否授予在线编辑、批注、下载、查看等权限。 企业是否启用“仅在线编辑”等权限组合，用于允许协作编辑但限制源文件下载。 私有化部署是否启用了对应在线 Office、轻文档、思维导图、流程图或第三方编辑器模块。 Office 在线编辑 在线编辑模块概述 巴别鸟企业网盘是OnlyOffice多年的官方合作伙伴，巴别鸟企业网盘的在线编辑模块基于OnlyOffice技术研发并优化了中文字体的载入和显示问题。巴别鸟在线编辑器支持多种文档格式，包括Microsoft Office（Word、Excel、PPT）和WPS Office。 巴别鸟和OnlyOffice的合作详情可以参见OnlyOffice官方网站： https://www.onlyoffice.com 技术基础 在线编辑模块的技术基础包括： OnlyOffice编辑器: OnlyOffice是一个强大的在线办公套件，支持多种文档格式的在线编辑。巴别鸟将其集成到网盘系统中，以提供优质的在线编辑体验。 中文字体优化: 为了克服OnlyOffice中对中文字体载入效率的不足，巴别鸟进行了优化，通过采用字库本地化技术，大幅提高中文字体的载入和显示速度，从而提升用户体验。 文档锁定: 巴别鸟同时支持客户端编辑和在线编辑，这意味着为防止文件版本冲突文件在线编辑时要锁定不能客户端编辑，文件客户端编辑时要锁定不能在线编辑。 主要功能 巴别鸟的在线编辑模块包括以下主要功能： 多格式支持: 用户可以在线编辑和查看Microsoft Office（Word、Excel、PPT）和WPS Office格式的文档。 协同编辑: 在线编辑模块支持多用户同时协同编辑文档，用户可以实时查看其他用户的更改，并共同编辑文档。这种协同编辑功能对于团队协作非常有用。 兼容性: 巴别鸟的在线编辑模块兼容微软Office，能很好的在网页上还原office的版式和字体。确保文档排版和格式在不同编辑器中打开的良好兼容性。 开放API: 巴别鸟开放在线编辑器的API，允许其他企业软件调用该API，将在线编辑功能集成到其他应用中。 用户体验 在线编辑模块的目标是提供用户友好且流畅的在线编辑体验。用户可以直接在网盘中打开需要编辑的文档，编辑完后即时保存，而无需离开网盘界面。这种无缝集成提高了用户的效率，使编辑文档更加便捷。 同时巴别鸟权限配置支持“仅在线编辑”，这意味着可以让一些用户仅能在线编辑文档但不能下载获取文档。 企业协作 巴别鸟在线编辑模块不仅适用于个人用户，还为企业提供了一个协同办公的平台。团队成员可以一起编辑文档，共享想法，并通过实时协作提高工作效率。 开放API 巴别鸟在线编辑器API允许企业将在线编辑功能集成到其自有软件或第三方软件中，使企业能充分使用在线编辑的能力。 其他在线编辑器 巴别鸟标准版还集成了其他在线编辑器，用于在线编辑及创建如MD文件，TXT文件甚至思维导图（如脑图）同时，巴别鸟也可以通过接入第三方API的形式集成其他支持HTML5的在线编辑系统，譬如可以对接微软office365或金山的web office（WPS）。 自带文本编辑器在线编辑。 巴别鸟自带的文本编辑器可以编辑及预览如：TXT、MD、RTF等文本文件，同时也能编辑CSS、JS、JSP…等代码文件，便于用户快速创建文档记录。 自带脑图（思维导图）编辑器。 巴别鸟自带思维导图模块，可以在线新建及在线编辑思维导图文件。 思维导图文件默认保存为KM格式。也可以导出为KM、TXT、MD、SVG、PNG、Xmind格式。 巴别鸟也可选支持创建流程图，但需要购买相应的模块授权（非标准版默认自带）。 客户端编辑 客户端编辑概述 巴别鸟企业网盘提供了强大的客户端编辑功能，用户可以轻松调用本地编辑软件对云端文档进行编辑，编辑保存后文件会自动上传到云端。这个功能不仅提高了用户的便捷性，还有助于避免文件版本的冲突，从而提高工作效率。 在客户端文件列表要编辑的文件上点击右键，选择编辑即可打开客户端编辑。 客户端编辑的实现原理决定了只要本地有编辑程序，所有类型的文件都可以进行客户端编辑。 技术实现 客户端编辑功能的实现技术包括： 客户端集成: 巴别鸟的Win客户端和Mac客户端均支持本地编辑软件的调用，这使得用户可以直接在本地软件中打开并编辑云端文件。 缓存管理: 客户端编辑使用缓存技术，把需要编辑的文件从云端缓存到本地并调用本地应用打开。系统监测到正在编辑的文件更新就把更新文件作为新版本上传。良好的缓存管理技术能在保证效率的前提下节约用户本地的磁盘空间。用户也可以在巴别鸟右键菜单手动清除文件的缓存。 文件状态检测: 在进行客户端编辑之前，系统会检测文件的状态，包括文件是否已被其他用户锁定。这有助于防止多人同时编辑同一文件，避免版本冲突。 自动锁定和解锁: 当用户开始编辑文件时，系统会自动锁定文件，以确保其他用户无法同时编辑相同文件。编辑完成后，文件将自动解锁，同时生成一个新的版本，并将修改后的文件上传到云端。 版本冲突处理: 尽管存在锁定机制，但在某些情况下，如网络问题或长时间未编辑时可能出现文件版本冲突。巴别鸟提供了冲突处理界面，允许用户对比选择是使用云端版本还是本地版本作为当前版本。无论用户的选择如何，系统都会确保没有选择的版本也会上传至云端作为历史版本，以防止数据丢失。 主要功能 客户端编辑功能的主要功能包括： 本地编辑: 用户可以通过点击本地编辑按钮，将文件缓存到本地，并使用本地默认应用程序进行编辑。 只要本地有相应的应用程序，理论上巴别鸟支持所有文件的本地编辑。 自动锁定: 文件在编辑时会自动锁定，以防止其他用户同时编辑，从而避免版本冲突。 自动解锁: 编辑完成关闭应用后，文件将自动解锁，并生成一个新的版本，将修改后的文件上传到云端。 版本控制: 所有编辑和上传的文件都将生成新的版本，以便用户可以随时查看和还原以前的版本。 用户体验 客户端编辑功能提供了出色的用户体验。用户可以在本地编辑器中进行编辑，而不必下载文件编辑后再上传。同时不支持在线编辑或在线预览的文件格式也可以通过客户端编辑打开编辑或预览。这提高了编辑效率和工作流程的顺畅性。 技术挑战 客户端编辑功能的技术挑战在于检测文件的状态，自动锁定和解锁，以及文件版本的冲突处理。系统需要准确判断文件是否正在被其他用户编辑，同时在冲突发生时提供用户友好的解决方案。这些挑战需要综合考虑用户体验和数据完整性。巴别鸟客户端编辑是业内少有的能很好处理这些问题的功能模块。 轻文档在线编辑 轻文档面向快速编写、多人协作、知识沉淀和轻量发布场景。与传统 Office 相比，轻文档更适合以结构化段落、列表、表格、链接和嵌入内容组织信息；与 Markdown 相比，轻文档更强调可视化编辑和非技术人员的低门槛协作。实际部署中，轻文档的入口、模板、权限和发布方式应与企业文档规范、项目协作方式和知识库沉淀流程一起设计。 Markdown、代码和文本在线编辑 巴别鸟自带文本编辑器可用于 TXT、MD、RTF 等文本文档，也可编辑 CSS、JS、JSP 等代码类文件。适用场景包括项目说明、轻量技术文档、配置片段、脚本说明、日志片段和团队知识维护。 思维导图在线编辑 思维导图默认保存为 .KM 格式，并支持导出为 KM、TXT、MD、SVG、PNG、Xmind。它适合需求梳理、会议纪要、知识结构、项目拆解和培训材料。与项目文件夹配合时，思维导图也会参与版本管理、权限控制、分享和同步。 流程图在线编辑 流程图采用 draw.io 体系，适合业务流程、系统架构、审批流、数据流和实施流程图。该能力可作为可选模块接入，是否可用取决于授权与部署配置。" }, { "lang": "zh", "slug": "permissions", "title": "权限体系", "description": "系统介绍部门角色、项目权限、文件访问控制、分享权限、自定义文件权限和在线编辑权限。", "category": "权限安全", "top_category": "使用指南", "keywords": [ "权限", "ACL", "文件访问控制", "项目权限", "分享权限" ], "url": "zh/permissions.html", "source": "content/zh/permissions.md", "summary": "权限体系 巴别鸟的权限体系贯穿文件列表、搜索、预览、编辑、同步、映射盘、分享、AI 回答和自动化任务。权限不是单一开关，而是由企业角色、部门角色、项目成员权限、文件访问控制、自定义文件权限、分享权限和企业安全策略共同决定。 权限判断层次 层次 控制对象 示例 企业角色 企业级管理行为 超级管理员、安全保密员、安全审计员、档案管理员 部门角色 部门文件夹和部门成员 查看、上传、下载、编辑、删除、部门文件管理、子部门管理 项目权限 项目文件夹 项目负责人、项目助理、项目成员、成员有效期 文件访问控制 单个文件或文件夹 对某成员或角色设置不可见、可查看、可编辑、有效期权限 自定义文件权限 分享、项目、访问控制 由管理员定义权限名称和组合 分享权限 外部或内部接收者 查看、下载、编辑、批注、有效期、密码、匿名访问 安全策略 企业或部门 IP 策略、Mac 绑定、水印、密级、对外分享策略 白皮书详细说明 巴别鸟企业网盘的权限管理是其核心功能之一，它贯穿整个系统，确保用户能够安全、合规地访问和管理文件。巴别鸟权限体系包括角色权限和文件权限两个主要方面。 角色权限 定义角色：巴别鸟允许在企业内定义不同的角色，每个角色可以包括一组特定的权限，用于控制用户在部门文件夹的访问和操作。这些角色可以根据部门管理需求进行创建，例如“部门管理员”、“部门成员”等。 部门角色权限：每个部门成员可以根据其在不同部门的角色分配不同的访问权限。这意味着用户可以在不同部门享有不同级别的权限。 灵活管理：巴别鸟的角色权限支持多个部门角色，并且可以在不同部门内同时使用相同的角色。角色的权限内容更改后，使用相同角色的成员", "headings": [ { "level": 1, "title": "权限体系", "id": "section" }, { "level": 2, "title": "权限判断层次", "id": "section-2" }, { "level": 2, "title": "白皮书详细说明", "id": "section-3" }, { "level": 3, "title": "角色权限", "id": "section-4" }, { "level": 3, "title": "文件权限", "id": "section-5" }, { "level": 3, "title": "总结", "id": "section-6" }, { "level": 2, "title": "与在线编辑的关系", "id": "section-7" } ], "images": [], "text": "权限体系 巴别鸟的权限体系贯穿文件列表、搜索、预览、编辑、同步、映射盘、分享、AI 回答和自动化任务。权限不是单一开关，而是由企业角色、部门角色、项目成员权限、文件访问控制、自定义文件权限、分享权限和企业安全策略共同决定。 权限判断层次 层次 控制对象 示例 企业角色 企业级管理行为 超级管理员、安全保密员、安全审计员、档案管理员 部门角色 部门文件夹和部门成员 查看、上传、下载、编辑、删除、部门文件管理、子部门管理 项目权限 项目文件夹 项目负责人、项目助理、项目成员、成员有效期 文件访问控制 单个文件或文件夹 对某成员或角色设置不可见、可查看、可编辑、有效期权限 自定义文件权限 分享、项目、访问控制 由管理员定义权限名称和组合 分享权限 外部或内部接收者 查看、下载、编辑、批注、有效期、密码、匿名访问 安全策略 企业或部门 IP 策略、Mac 绑定、水印、密级、对外分享策略 白皮书详细说明 巴别鸟企业网盘的权限管理是其核心功能之一，它贯穿整个系统，确保用户能够安全、合规地访问和管理文件。巴别鸟权限体系包括角色权限和文件权限两个主要方面。 角色权限 定义角色：巴别鸟允许在企业内定义不同的角色，每个角色可以包括一组特定的权限，用于控制用户在部门文件夹的访问和操作。这些角色可以根据部门管理需求进行创建，例如“部门管理员”、“部门成员”等。 部门角色权限：每个部门成员可以根据其在不同部门的角色分配不同的访问权限。这意味着用户可以在不同部门享有不同级别的权限。 灵活管理：巴别鸟的角色权限支持多个部门角色，并且可以在不同部门内同时使用相同的角色。角色的权限内容更改后，使用相同角色的成员的权限也会相应更改。 权限组合：巴别鸟角色权限支持30多种可选权限进行组合，以实现精细化的用户权限控制。这些权限涵盖了各种访问和操作行为，如预览、上传、下载、编辑等。 角色可选权限列表： 文件权限 自定义权限：文件权限也可以在后台自定义，用户可以选择特定权限类型和名称。这些自定义文件权限将用于文件分享、项目管理和文件权限控制。 文件访问控制：文件访问控制允许部门成员在文件和文件夹上设置具体的访问权限，以覆盖部门角色权限。这意味着可以更精确的控制部门里某个文件或文件夹的访问行为，文件访问控制仅适用于部门成员和项目成员。 高优先级：文件访问控制的权限具有较高的优先级，如果设置了文件访问控制，将覆盖成员的部门角色权限或项目权限。用户可以根据需要设置文件的访问权限。 部门文件和文件夹控制：用户可以为部门文件和文件夹启用文件访问控制，以控制特定文件或文件夹的访问权限。 有效期：文件访问控制可以设定有效期，到有效期后，文件访问控制的约束失效。譬如：给某个没有文件编辑权限的部门成员该文件的编辑权限，有效期3天，3天后文件访问控制赋予的权限就会失效，部门成员对文件的权限就变成成员角色的权限。 总结 巴别鸟企业网盘的权限管理是一个全面的系统，可以满足企业不同部门和项目的特定需求。角色权限和文件权限相互配合，确保用户可以精确控制文件的访问和操作。这一功能有助于提高安全性、合规性和工作效率。 与在线编辑的关系 在线编辑、仅在线编辑、客户端下载、客户端编辑、上传新版本和预览权限可以组合使用。典型安全策略是允许外部人员在线协同或预览，但不允许下载源文件；也可以让项目成员只在有效期内访问某项目文件。" }, { "lang": "zh", "slug": "security", "title": "安全与审计", "description": "介绍安全架构、SSO、加密、日志审计、水印、备份、部门安全策略和风险控制。", "category": "权限安全", "top_category": "使用指南", "keywords": [ "安全", "SSO", "审计", "水印", "加密" ], "url": "zh/security.html", "source": "content/zh/security.md", "summary": "安全与审计 安全性 用户身份验证: 使用强大的用户身份验证机制，包括单一登录（SSO）、OAuth认证和多因素认证（MFA）。 授权: 使用Spring Security等授权框架来定义和强制访问控制策略，确保用户只能访问其授权的资源。 数据加密: 实施数据传输和存储的加密，以保护用户数据的安全性。 业务逻辑 文件管理: 开发了业务逻辑来处理文件上传、下载、版本控制、共享和协作功能。 用户管理: 实施用户管理、权限管理和用户组织结构。 搜索功能: 开发了高效的搜索引擎，支持文件和元数据的快速检索。 在线编辑：负责文件的在线编辑、协同编辑。 文件转码：负责文件的批量排队转码，生成预览文件。 对象存储：文件的分块及落盘，存储系统管理。 Web服务 RESTful API: 使用RESTful API，以支持前端和其他客户端的数据交互和协作。 缓存管理 缓存策略: 使用缓存来提高性能，包括页面缓存、数据缓存和会话缓存。 异步任务处理 消息队列: 使用消息队列系统RabbitMQ来处理异步任务，如文件转码、文件预览生成等。 通过采用Struts2和Spring框架，结合以上设计考虑，可以构建一个强大、高性能、安全可靠的企业网盘后端系统，满足用户的需求并支持未来的扩展和功能添加。 云基础设施选择（公有云 SAAS版本巴别鸟） 公有云基础设施选择可以直接影响到企业网盘产品的性能、可靠性和安全性。巴别鸟公有云版本经过多方对比，选择了阿里云的ECS、OSS服务以及CDN分发业务。目前（2023年）公有云SAAS模式运行的巴别鸟系统已经0服务器故障在线运作了超过10年。 云服务提供商选择 业务服", "headings": [ { "level": 1, "title": "安全与审计", "id": "section" }, { "level": 2, "title": "预览及转码", "id": "section-2" }, { "level": 3, "title": "性能优化", "id": "section-3" }, { "level": 2, "title": "安全性", "id": "section-4" }, { "level": 3, "title": "安全的架构", "id": "section-5" }, { "level": 3, "title": "用户身份验证和授权（SSO）", "id": "sso" }, { "level": 3, "title": "用户体验", "id": "section-6" }, { "level": 3, "title": "概述", "id": "section-7" }, { "level": 3, "title": "概述", "id": "section-8" }, { "level": 3, "title": "概述", "id": "section-9" } ], "images": [], "text": "安全与审计 安全性 用户身份验证: 使用强大的用户身份验证机制，包括单一登录（SSO）、OAuth认证和多因素认证（MFA）。 授权: 使用Spring Security等授权框架来定义和强制访问控制策略，确保用户只能访问其授权的资源。 数据加密: 实施数据传输和存储的加密，以保护用户数据的安全性。 业务逻辑 文件管理: 开发了业务逻辑来处理文件上传、下载、版本控制、共享和协作功能。 用户管理: 实施用户管理、权限管理和用户组织结构。 搜索功能: 开发了高效的搜索引擎，支持文件和元数据的快速检索。 在线编辑：负责文件的在线编辑、协同编辑。 文件转码：负责文件的批量排队转码，生成预览文件。 对象存储：文件的分块及落盘，存储系统管理。 Web服务 RESTful API: 使用RESTful API，以支持前端和其他客户端的数据交互和协作。 缓存管理 缓存策略: 使用缓存来提高性能，包括页面缓存、数据缓存和会话缓存。 异步任务处理 消息队列: 使用消息队列系统RabbitMQ来处理异步任务，如文件转码、文件预览生成等。 通过采用Struts2和Spring框架，结合以上设计考虑，可以构建一个强大、高性能、安全可靠的企业网盘后端系统，满足用户的需求并支持未来的扩展和功能添加。 云基础设施选择（公有云 SAAS版本巴别鸟） 公有云基础设施选择可以直接影响到企业网盘产品的性能、可靠性和安全性。巴别鸟公有云版本经过多方对比，选择了阿里云的ECS、OSS服务以及CDN分发业务。目前（2023年）公有云SAAS模式运行的巴别鸟系统已经0服务器故障在线运作了超过10年。 云服务提供商选择 业务服务器SAAS版本巴别鸟使用了阿里云的ECS（云服务器）集群 阿里云的ECS是一种弹性计算服务，为你提供了虚拟机实例，使你能够在云中运行应用程序。这些是选择ECS的一些关键优势： 灵活性: ECS允许你根据需要创建、启动和停止虚拟机实例。这意味着你可以根据流量需求来扩展或缩减计算资源。 可扩展性: 阿里云提供了多种不同规格的ECS实例，以满足不同工作负载的需求。你可以根据应用程序的性能要求进行选择。 可靠性: 阿里云的ECS实例通常具有高可用性，提供了多个数据中心和可用区，以确保业务连续性。 安全性: 阿里云提供了各种安全性功能，包括网络隔离、防火墙和安全组，以帮助你保护你的虚拟机实例免受恶意攻击。 对象存储SAAS版本巴别鸟使用了阿里云的OSS（对象存储服务） 阿里云的OSS是一种高度可扩展、安全可靠的云存储服务，适用于存储和管理大量的文件和数据。以下是选择OSS的一些优势： 可扩展的存储: OSS提供了可扩展的存储容量，可以根据你的需要进行动态扩展。这对于企业网盘产品中的文件存储非常重要。 数据备份和恢复: 阿里云的OSS具有数据备份和版本控制功能，可以帮助你保护数据免受丢失或损坏。 安全性: 数据存储在OSS中通常会受到加密和访问控制的保护，以确保数据的安全性。 CDN整合: 与CDN服务集成，可以提高文件的分发速度和用户体验。 为确保全球各地的访问通畅，巴别鸟也使用了CDN分发 CDN（内容分发网络）服务是将内容缓存到全球分布的边缘节点，以降低加载时间并提高用户体验。阿里云的CDN服务可以为企业网盘产品带来以下好处： 快速分发: 加速文件的分发，确保用户能够快速访问和下载文件，不受地理位置的限制。 负载均衡: CDN可以帮助分担服务器的负载，降低服务器的压力，提高网站的性能。 安全性: CDN服务通常具有DDoS攻击防护功能，可保护网站免受恶意攻击。 全球覆盖: 阿里云的CDN服务具有全球性覆盖，可确保你的内容快速传递给全球用户。 数据中心地理位置 目前巴别鸟使用了阿里云的两个数据中心： 杭州数据中心 及 威海数据中心 一南一北的配置能保证服务的可持续性及灾备需求。 数据库设计 数据库类型 巴别鸟企业网盘采用了多种类型的数据库，同时也可根据客户需求支持信创的数据库产品或是Oracle等大型数据库。 巴别鸟默认的产品数据库为： 核心数据库为关系型数据库 mysql 辅助数据库有：Redis 数据库，MongoDB 数据库 数据库架构 数据架构在企业网盘系统中扮演着至关重要的角色，确保了数据的高可用性、性能和一致性。下面是巴别鸟的数据库架构： A. 主从数据库架构 主库（Master） 主库负责处理写入操作，包括用户上传文件、修改文件信息等。 主库提供高可用性、数据一致性和事务处理。 从库（Slave） 从库主要用于读取操作，包括文件的查询、搜索等。 从库可以提供负载均衡，分担主库的读取负载。 数据同步：采用数据复制机制确保从库与主库的数据保持同步。 故障转移：从库可以在主库故障时接管写入操作，确保系统的连续性。 B. 关系型数据库（MySQL） 数据库设计 数据库设计以支持文件和用户管理，包括文件元数据、用户信息、权限等表的定义。 数据表之间的关系清晰，使用外键来维护数据一致性。 数据冗余 主从架构中的从库用于数据冗余，以防止主库故障时的数据丢失。 数据同步机制确保从库的数据与主库保持一致。 C. NoSQL数据库（MongoDB） 文件元数据存储 MongoDB可用于存储文件的元数据，如文件名、大小、版本信息等。 具有弹性模式的MongoDB适用于不断变化的数据模式。 D. 缓存数据库（Redis） 缓存读取数据 Redis用于缓存频繁读取的数据，以减轻数据库的负载。 缓存的数据可以包括用户会话信息、热门文件、访问日志等。 E. 数据备份和恢复 备份策略 定期备份主库和从库的数据，以确保数据的安全性。 巴别鸟备份数据存储在不同地理位置的可靠存储中。 灾难恢复 我们制定详实的恢复计划，包括从备份中还原数据的步骤和时间表。 巴别鸟运维团队会定期测试灾难恢复过程以确保其有效性。 F. 数据一致性和事务管理 事务支持 使用数据库事务来确保一系列操作的一致性，如文件上传、共享和权限更改。 事务应该被正确地管理，以避免数据损坏和不一致性。 并发控制 使用数据库锁和隔离级别来管理并发访问，以避免数据竞争和冲突。 G. 监控和性能优化 性能监控 实施数据库性能监控，包括查询响应时间、负载和资源利用率。 根据监控结果进行性能调整，以确保数据库的稳定性和性能。 查询优化 优化复杂查询以提高查询性能，包括索引优化和查询计划分析。 这些数据架构的元素将有助于确保你的企业网盘系统能够具备高可用性、性能卓越和数据的安全性。通过合理的数据库设计和维护，你可以提供稳定可靠的服务，满足用户需求并确保数据的完整性。 数据备份和恢复策略（公有云） A. 数据备份 定期备份计划：巴别鸟有定期的备份计划，以确保数据的连续备份（每日凌晨数据备份）。 完整备份和增量备份：巴别鸟采用完整备份和增量备份的组合策略。完整备份将数据库的全部数据备份，而增量备份仅备份自上次备份以来发生更改的数据，以减少备份时间和存储空间的消耗。 多备份位置：公有云版本巴别鸟有杭州机房及威海机房两个地理位置，以应对自然灾害或硬件故障。云存储和远程数据中心是常见的备份存储选择。 自动化备份：巴别鸟的数据库备份采用全自动备份机制，无需人工干预，以提高可靠性。 备份测试：我们会定期测试备份以确保其完整性和可用性。通过还原备份数据到测试环境中并验证数据的一致性来进行测试。 B. 灾难恢复 恢复计划：我们建立了详细的恢复计划，明确每个步骤和责任。确保团队成员了解如何执行恢复过程。 备份恢复测试：我们会定期测试备份恢复过程，以确保在紧急情况下能够迅速有效地还原数据。测试应包括各种故障场景的模拟。 备份监控：监控备份任务的运行情况，出现问题会自动提醒及报错，确保备份系统正常运行。 灾难恢复团队：我们有专门的灾难恢复团队，7 24小时待命，负责在紧急情况下采取行动，确保业务的持续运行。 通信计划：我们建立了有效的通信计划，及自动告警信息送达监控，以通知相关利益相关者有关灾难事件和恢复过程的信息。 文档和培训：确保恢复计划和过程的详细文档，并为团队成员提供培训，使其了解恢复策略和步骤。 以上策略和努力立足于确保数据库数据的安全性和可用性，并最大程度地减少数据丢失和系统停机的风险。 预览及转码 文件预览功能能让用户无需安装应用程序就能直接在网盘上直接打开文件进行预览，为了能在网页端及客户端上预览文件及保证文件在只读状态下的安全性（不被人获取内容或源文件），文件预览和转码是企业网盘系统的核心功能之一。这章将介绍巴别鸟如何实现文件的在线预览和转码，以提供更便捷的用户体验。 支持在线预览的文件类型 文本、代码及office文件： Pdf，md，js，xml，htm，html，css，scss，jsp，c，cpp，java，php，m，h，hpp，mm， mail ，msg ，epub，doc，docx，ppt，pptx，xls，xlsx，txt，rtf，wps，wpt，dps，dpt，et，ett Xmind，km 可选支持：（可选项需要增加服务器及相应模块费用） key，numbers，pages 音视频： mp3，mp4， wav，asf，ape 可选支持：（可选项需要增加服务器及相应模块费用） flv，f4v，mp4，m4v，webm，3gp，3gpp，wmv，avi，rm，rmvb，mkv，asf，mov，mpeg，swf，mpg，mts，m2ts，ogv 3D图形： dae、3ds、abc、fbx、mtl、obj、ply、stl、x3d 可选支持1：（可选项需要增加服务器及相应模块费用） x3d， ply，3ds，abc，m3d 可选支持2: revit、soildworks、3DMax 图片格式： bmp，jpg，jpeg，gif，png，bmp，psd，tif，tiff，raw，cr2，arw，dng，nef，pef，dcm，ico dicom（医疗图像） 矢量图片： ai，svg，eps，indd，indt，idml CAD dwg，dwt，dxf，dcm 压缩文件： 可选支持： rar, zip 在线预览工具（巴别鸟预览器） 巴别鸟企业网盘使用了自主研发的BabelViewer在线预览工具进行在线预览，支持不同文件转码后统一预览。允许用户查看文件内容，而无需下载到本地。 BabelViewer是针对企业网盘用户需求开发的强大的H5在线预览工具，有如下特性： 支持多个库，以便于多种方式渲染预览文件。 支持多图层技术，可以在预览文件上进行多人绘制。 支持在线批注，并可以在批注区内多人讨论。 可展开批注列表统一管理当前版本及历史版本的批注。 支持多种文件的版本对比。 矢量化的渲染，矢量文件可以高倍率放大不失真。 可以在预览状态下快速切换预览多个文件。 使用webGL技术支持3D文件的在线渲染，也支持3D文件的在线批注。 文件转码功能 转码工具： 巴别鸟转码服务集成了多个转码工具，以将文件从一种格式转换为另一种支持巴别鸟预览器打开的格式。私有部署系统需要一台专用的服务器（或虚拟机）来来处理文件的转码。 例如，将高分辨率图片转换为Web友好的JPEG格式。 自动转码： 巴别鸟实现了自动转码功能，用户上传的文件会自动转换为适当的格式并抽取文件列表缩略图，以节省存储空间和提高性能。针对大量文件同时上传的转码处理，巴别鸟有一套独特的调度机制，力求在有限的资源占用下让用户打开预览更及时。 服务器空闲时用户文件上传即刻自动转码，生成预览文件。 服务器繁忙时，如果用户同时上传的文件超过一定数量，这些文件将不会进行转码，当用户点击文件准备预览时，优先加入到转码进程，实时生成预览文件。 因为用户一次性上传大量文件后要马上预览的概率很低，这样的设定可以防止用户同时大量上传文件时因服务器繁忙造成真正需要转码的文件打不开的情况。 转码队列和异步处理： 将转码任务加入队列，并使用异步处理方式来执行转码操作，以避免阻塞其他系统功能。 缓存和性能优化 预览和转码缓存： 实施缓存机制，以存储已转码的文件和预览数据，以减少重复转码和提高响应速度。 负载均衡： 同时转码队列配置了负载均衡策略，以确保多个预览和转码请求能够平衡地分配到不同的处理节点。 性能优化 性能监控： 实时性能监控，包括转码速度、缓存命中率和响应时间，出错自动清空队列重试处理。严重错误短信通知运维人员。 资源调整： 根据监控结果和负载情况，动态调整预览和转码资源，以确保高性能和可用性。 集成测试 性能测试： 进行性能测试，模拟大量并发预览和转码请求，以评估系统在高负载下的表现。 office家族文件 巴别鸟支持微软office家族及WPS的文件的在线预览，为确保office文件特别是word文件的显示准确性，巴别鸟提供了2种office文件的预览方式： 使用运行于Windows服务器的office转码模块把文件转码后进行预览（默认）。 需要部署一台window服务器生成预览文件。 可以相当准确的与微软office或WPS打开无差别的预览word类文件和ppt类文件。 支持使用巴别鸟预览器(BabelViewer)对文件进行批注讨论、圈画及版本对比。 可使用“智巢AI”文档助理功能。 Excel文件因没有版式和字体问题，都使用在线office的预览功能进行预览。 所有的预览文件都可以内嵌水印，并可另存为带水印的PDF文件。 使用运行于Linux服务器的在线office的预览功能提供office及wps文件的在线预览。 针对只能使用Linux，并且对word文件预览版式准确度没有较高要求的用户。 因系统字体差异，在线office解析等原因，在Linux系统中的在线office并不能1：1完美显示word文件的版式，在譬如：项目符号编号、段落高度、分页、插入图形位置等方面会有少许差异。 Excel文件因没有版式和字体问题，都使用在线office的预览功能进行预览。 使用在线office预览功能打开的word类和ppt类文件将不再支持巴别鸟预览器的批注功能。 不支持使用“智巢AI”的文档助理功能。 所有的预览文件都可以内嵌水印，并可另存为带水印的PDF文件。 考虑到浏览器的性能及服务器的效率，在线预览office文件会有一定的文件尺寸大小限制，超过这个限制的文件就无法在线预览。私有云用户可以自定义这些限制，但不建议调过大。 Word（文档）类文档最大可预览文件大小为 200MB。 PPT（幻灯片）类文档最大可预览大小为 200MB。 Excel（表格）类文档最大可预览大小为 50MB。 图片及图形文件 巴别鸟支持绝大多数图片文件的在线预览，包括psd、gif家族、jpg家族、bmp家族、png、raw家族（部分）、arw、tif、TIFF、dicom、ico等文件，同时也支持医学图形常用的dicom格式。并且得益于巴别鸟强大的图片处理技术，巴别鸟可以以1：1的方式在线预览超高分辨率的大图（可选组件），并且在图片上批注讨论，并且巴别鸟支持读取照片的元数据。 PSD、RAW、BMP等图片格式需要服务器自动转码后才能预览。 通常情况下（没有开启大图显示模块）超过4K分辨率的大图片将会被服务器处理成便于网页展示的尺寸及格式。开启大图显示模块后，服务器将把大图切割成若干小块，分块载入1：1显示，这将耗费较大服务器资源。 PNG等透明背景的图在巴别鸟中也能显示出透明度，并且可以更改背景。 巴别鸟系统会读取图片元数据信息，供搜索、查询、排序。这些信息包括：分辨率、尺寸、拍摄设备、拍摄时间、拍摄地点。 所有可预览图片格式都会生成缩略图，供文件列表展示快速查找及瀑布流模式展示。 所有图片格式都支持在巴别鸟预览器(BabelViewer)中批注讨论、圈画及版本对比。 如开启水印功能，服务器将会对预览的图片进行预处理，在图片中嵌入水印。 所有图片类文件都可以另存为带水印的PDF文件。 巴别鸟也能很好的支持矢量图形的在线预览，包括但不限于ai、dwg、dcm、dxf 、dwt 、pdf、eps、svg、idml、indd…等矢量图形格式。更重要的是，巴别鸟能以矢量渲染的方式打开这些格式的文档，这意味着这类图形可以在巴别鸟中放大几十倍也不会模糊或失真。 AI、eps、indd等文件需要服务器自动转码后才能预览。 以矢量的方式显示，支持更改背景颜色。 放大后图形不会失真或模糊。 其他特性和图片一致，同样支持嵌入水印、另存为带水印PDF、在巴别鸟预览器(BabelViewer)中批注讨论、圈画及版本对比、生成文件列表预览图。 3D及CAD文件 得益于巴别鸟预览器(BabelViewer)对3D格式的支持，我们默认支持dae、3ds、abc、fbx、mtl、obj、ply、stl、x3d等3D图形的在线预览，并且支持在3D空间中的批注讨论。 目前，巴别鸟预览器仅支持单个文件3D图形，如果文件有外挂皮肤等外挂文件将只能载入模型本体。 3D文件目前还不支持生成预览图，但如果有这方面需求支持定制开发。 3D文件可以在巴别鸟预览器中旋转、放大、缩小、拆分，并可以建立批注讨论点，系统会记住建立批注时的视口，点击批注会自动旋转到建立批注时的视角。 如需对revit、soildworks、3DMax等专业格式进行支持，私有化部署用户可以选择接入第三方3D在线显示及转码插件，（如：Autodesk viewer）这会产生相关费用。 目前不支持在移动设备预览3D文件。仅支持在网页及客户端预览3D文件。 巴别鸟支持对CAD文件的预览。如: dwg，dwt，dxf 格式，目前在公有云上，巴别鸟向专业版及企业版用户提供强大的CAD预览服务，私有化用户想要预览CAD文件需要购买相应的CAD转码服务私有化授权。 巴别鸟CAD预览支持CAD版本R12 2021。 CAD文件可生成预览缩略图，用于文件列表及瀑布流模式。 兼容天正全专业T20V7版本。 支持在浏览器、客户端、移动端预览及批注CAD文件。 支持百兆以上图纸浏览。 图层打开/隐藏/多选/全选。 布局切换、视图平移、缩放、更改背景颜色、鹰眼鸟瞰视图。 音视频转码 不使用转码服务器的情况下 巴别鸟无须转码服务就可以直接在线播放支持HTML5标准的视频文件。 支持的格式如下： 视频文件格式 MP4：MPEG 4 Part 14，支持H.264编码。几乎所有的浏览器都支持该格式。 WebM：谷歌开发的格式，使用VP8或VP9编码，可以在大多数现代浏览器中播放 Ogg：开放媒体格式，使用Vorbis编码，可以在大多数现代浏览器中播放。 音频文件格式 MP3：MPEG 1或MPEG 2 Audio Layer III，可以在几乎所有的浏览器中播放。 AAC：Advanced Audio Coding，可以在大多数现代浏览器中播放。 Ogg：开放媒体格式，使用Vorbis编码，可以在大多数现代浏览器中播放。 WAV：Waveform Audio File Format，可以在几乎所有的浏览器中播放，但文件较大，不适合在网络上播放。 兼容性 视频兼容性 音频兼容性 使用转码服务器的情况下 如果需要使用巴别鸟管理查询大量视频素材，就需要搭建专用的视频转码服务器，并购买相应的视频转码模块授权。（目前此服务仅支持私有化部署用户） 巴别鸟视频转码模块采用FFmpeg解决方案，FFmpeg 支持 MPEG、 DivX、MPEG4、AC3、DV、FLV 等40多种编码，AVI、MPEG、OGG、Matroska、ASF 等90多种解码，FFmpeg 支持的编解码器种类共有 280 多种， 涵盖了几乎所有常见音视频编码格式， 能解码几乎所有的音视频。 视频转码服务器所需硬件配置 视频转码是一个相当耗费运算资源的服务，需要一台专门的物理机来执行转码操作。同时服务器性能要求和需要转码的视频类型，时长和码率都有关系。 按每天转换累计时长50小时的HDR 4K视频（使用CUDA）为1080P H.264 AC3 MP4为基准，所需的服务器硬件配置如下： 服务器类型 配置要求 操作系统 服务器用途 备注 视频转码服务器 至强Intel E5 2630v3CPU 2 64G内存 2TB SSD硬盘 + Nvidia Tesla M4 4G显卡 Linux 视频转码服务器 使用GPU（CUDA） 根据视频码率不同所需转码时间也不同，在通常情况下，一个100秒的2K视频转码成1080P MP4耗时为8秒（使用上文硬件配置），如果同时转码的视频多，服务器则会做多线程排队处理。 使用转码服务器后，视频文件转码完成后即可播放，并且可以在文件列表查看缩略图。 安全性 安全的架构 安全是业务的关键！巴别鸟从产品设计到架构搭建及服务器管理都优先考虑安全性，并且包含了许多重要的安全功能。您可以控制每个文件及每位成员的访问行为、添加文件水印、查看访问日志、重要文件归入档案库、给文件及部门设立加密等级及安全策略….这一系列举措可以最大限度保护重要数字资产。同时，巴别鸟使用了安全等级最高的EV SSL认证，银行级的加密传输，多机房分布式备份，确保你的数据安全无忧。这些举措使巴别鸟获得了QUALYS安全性A+认证，同时我们也拥有ISO27001信息安全质量体系认证。 巴别鸟从上线开始就实现了从上传、下载、到落盘的全链路的加密传输和存储，配合权限管理及文件管理的细节处理，以及各种使用场景所遇到的风险分析及相应的功能应对策略，使巴别鸟成为了市面上最安全的企业网盘之一。 图：巴别鸟数据传输链路 防火墙、堡垒机、VPN、SSL….在传输和服务器部署架构上我们有越来越多的手段保证系统的数据安全性。但是根据我们多年从事企业安全服务的经验来看，80%数据泄露事件往往来源于内部人员泄露及管理混乱。即使系统做到了物理隔离，也没办法杜绝数据泄露风险。巴别鸟从产品设计之初就考虑到了这一点，从管理、人员和设备的角度提供了多种安全设计及功能。在易用性和安全性的矛盾之处也提供了多种可选设置及方案。从产品结构和使用逻辑上尽可能保证数据安全性。大幅消除因内部人员疏忽或破坏产生的数据泄露风险。 用户身份验证和授权（SSO） 自有用户体系 巴别鸟自由用户体系身份验证种类 账号类型 验证方式 备注 邮箱 密码、验证码 公有云需绑定手机号验证 手机号（全球） 密码、验证码 私有云需对接短信发送平台 工号（user ID） 密码 仅私有云支持，忘记密码只能管理员重置，首次登录会要求用户强制重置密码 微信 扫码、APP跳转（移动端） 仅公有云支持，需绑定手机号验证 巴别鸟支持多种身份验证类型混用。 可强制要求多因素认证（MFA）以提高安全性 混合身份验证: 在使用单点登录时（SSO）支持同时使用自有用户体系和SSO。用户可以选择使用自有凭据登录或通过SSO登录（如使用企业微信扫码登录及采用账户密码登录）。 单点登录（Single Sign On，SSO）集成 单点登录（Single Sign On，SSO）集成是企业网盘产品中的一个关键功能，它允许用户在一次身份验证后访问多个不同的应用程序和服务，提高了用户体验和安全性。 巴别鸟支持OAuth2.0、CAS等方式集成单点登录，并已实际应用于和多种系统的对接中。 支持的SSO标准和协议 巴别鸟企业网盘支持多种SSO标准和协议，包括但不限于以下内容： ADFS集成： 巴别鸟支持与Active Directory Federation Services（ADFS）的集成，这使得基于Windows身份验证的SSO成为可能。这种集成允许企业内部用户使用他们的Windows凭据进行登录。 AD域控制器集成： 巴别鸟还支持与企业的本地Active Directory（AD）域控制器的集成。这使得企业内部用户可以使用他们的本地域凭据进行登录。 企业微信集成： 巴别鸟支持对接企业微信，这使得企业可以直接用企业微信账号进行扫码认证登录。并且可以同步导入微信的组织结构及用户，使用企业微信发送通知，并在工作台中访问巴别鸟。 钉钉集成： 巴别鸟支持对接钉钉，这使得企业可以直接用钉钉账号进行扫码认证登录。并且可以同步导入钉钉的组织结构及用户，使用钉钉发送通知，并在钉钉工作台中访问巴别鸟。 飞书集成： 巴别鸟支持对接飞书，这使得企业可以直接用飞书账号进行扫码认证登录。并且可以同步导入飞书的组织结构及用户，使用飞书发送通知，并在飞书工作台中访问巴别鸟。 集成文档： AD域控、企业微信、钉钉、飞书、致远OA的集成已内嵌于巴别鸟私有化版本中，用户购买相应模块后只需要根据相应文档进行配置即可使用。相关配置文档可咨询巴别鸟客服人员。 第三方SSO集成： 如果你的组织使用第三方SSO供应商（如Okta、OneLogin、Auth0、千帆、泛微等），我们也支持与这些供应商的产品集成。这意味着外部用户可以通过这些供应商的产品进行SSO登录。但这需要二次开发并需要支付一定费用。 第三方自有用户体系集成 我们理解许多组织可能同时拥有自有用户体系，因此我们的SSO集成支持混合身份验证： 混合身份验证: 我们的系统允许用户选择使用自有凭据进行登录，或者使用SSO进行登录。这提供了最大的灵活性，以适应不同用户的需求。 用户映射和同步: 我们确保自有用户体系中的用户帐户与SSO中的用户帐户同步。这意味着用户的属性和权限在整个系统中保持一致。 安全性和授权 我们非常注重安全性和授权策略的实施，以确保只有授权用户能够访问资源： 身份验证策略: 我们支持灵活的身份验证策略，包括多因素认证（MFA）等高级选项。这有助于确保用户的身份得到妥善验证。 授权和访问控制: 我们允许管理员配置和管理用户的访问权限，包括文件和资源的授权。这确保了只有经过授权的用户能够访问敏感数据。从其他平台导入的用户仅会拥有所在部门的初始权限（默认为部门成员），管理员可以通过自定义“部门成员”角色权限的方式统一更改导入用户的初始权限范围。 用户体验 我们关注用户体验，努力提供无缝的登录体验： 登录页面: 我们的登录页面清晰直观，提供用户选择不同的登录方式的选项。用户可以选择使用SSO登录或使用自有凭据登录。同时，我们也支持使用用户单点登录系统自己的登录页面（如ADFS系统认证页面） 单点注销: 如果对接的单点登录系统（SSO）支持单点注销功能，我们也可支持单点注销，这意味着用户可以在任何一个连接的应用程序中注销，系统会自动注销其他应用程序的会话。 访问控制列表（ACL）设计 概述 在巴别鸟企业网盘中，权限管理是确保文件和资源的安全性和可访问性的核心组成部分。ACL（Access Control List）被用于定义用户和角色对于不同部门中的资源的访问权限。本章将详细介绍我们的ACL设计，包括角色管理、用户分配、角色权限和变更管理。 角色管理 角色定义: 我们允许管理员自定义角色，每个角色代表一组权限的集合，有32种权限可选组合成角色。 每个角色应有一个明确的名称和描述，以便管理员和用户了解其功能。 权限分配: 每个角色都被分配特定的权限，这些权限决定了角色在部门中的操作能力。 权限应该精心选择，以确保用户拥有必要的权限但又不会过度授权。 用户管理 用户角色分配: 每个用户都可以被分配一个或多个角色，这些角色决定了用户在不同部门中的权限。 允许一个用户在不同部门拥有不同的角色，以适应多样化的需求。 用户与部门的关联: 用户应与其所属部门建立关联，以便根据部门角色自动分配相应的权限。 用户仅能访问其所在的部门，并有角色决定在部门中的访问权限。 能否访问子部门，也由角色权限决定（角色有访问子部门权限）。 角色权限管理 角色权限定义: 每个角色有明确的权限定义，包括可读、可写、可删除、可共享等操作。 角色可以根据需要新增或删减。 权限继承: 我们的系统支持权限的继承，当用户分配到一个角色时，他们会自动继承该角色的权限。 这减少了手动分配权限的工作量，同时确保一致性。 变更管理 角色权限变更: 当管理员更改角色的权限时，所有拥有该角色的用户在部门中的权限也会相应更改。 我们将详细记录这些变更，以便进行审计和故障排除。 权限审计: 安全管理员可定期审计角色和用户的权限，以确保授权的准确性和安全性。 不再需要的权限应及时取消。 安全性 访问控制: 巴别鸟企业网盘的ACL系统将严格控制用户和角色对资源的访问。 只有经过授权的用户并拥有在该部门的角色才能访问部门文件。 部门间相互隔离，可以设定不同的密级（部门安全策略）来保护部门的文件。 审计和监控: 所有的权限变更角色变更都会留下日志记录。方便管理查询。 实施监控和审计机制，以监视权限变更和访问活动，及时检测和响应潜在的风险。 最佳实践 最小特权原则: 遵循最小特权原则，即给予用户和角色所需的最低权限，以降低潜在的安全风险。 部门文件可通过文件访问控制来精确增加某个成员（或某种角色）的权限，并设定权限有效期。 定期审查: 定期审查角色和权限配置，以确保系统的安全性和性能。 未来扩展 多租户支持: 公有云系统支持多租户控制。 私有云考虑将ACL系统扩展到多租户环境，以支持多个客户或组织的需求。 数据加密 数据传输加密（SSL/TLS） 加密协议 在巴别鸟企业网盘中，我们高度重视数据传输的安全性。为了确保数据在传输过程中得到保护，我们采用了安全套接字层（Secure Socket Layer，SSL）协议来实现传输加密。 HTTPS: 我们使用HTTPS协议，它是HTTP的安全版本，以加密所有数据传输。 HTTPS通过TLS/SSL协议提供端到端的数据加密，防止第三方恶意用户截取或窃听传输的数据。 证书管理 SHA 256证书: 我们的SSL证书采用SHA 256哈希算法，这是一种强大的哈希算法，提供了高级的安全性和完整性保护。 SHA 256证书对于验证服务器的身份以及保护数据传输非常关键。 证书更新: 巴别鸟企业网盘将定期更新SSL证书，以确保证书的有效性和安全性。 我们会监视证书的到期日期，提前进行续签。 数据加密 数据传输加密: 所有在巴别鸟企业网盘和用户终端之间的数据传输都会经过TLS/SSL加密。 这包括用户登录、文件上传和下载、以及任何敏感数据的传输。 数据完整性保护: TLS/SSL不仅提供了数据加密，还能够验证传输过程中数据的完整性，以防止数据被篡改或损坏。 安全性 严格的加密策略: 我们遵循严格的加密策略，确保所有数据传输都经过安全通道，无法被非授权方访问。 保护用户隐私: 数据传输加密有助于保护用户的隐私和敏感信息，包括个人身份信息和机密文件。 最佳实践 安全升级: 我们将继续关注新的安全标准和最佳实践，确保数据传输加密的安全性得到不断提升。 安全审计: 我们会定期进行安全审计和漏洞扫描，以确保我们的加密机制不受到潜在威胁的影响。 图：巴别鸟获得了Qualys SSL扫描的A+安全验证 数据存储加密 概述 在巴别鸟企业网盘中，我们采用了高级的分块加密技术，以确保文件的安全性和完整性。我们使用分块加密技术来将文件分成小块，每个小块都经过哈希加密，然后存储在对象存储系统中。这一技术确保即使在服务器控制权或硬盘被攻破的情况下，攻击者也无法获取到完整的文件内容。 分块加密 文件分块: 上传到巴别鸟企业网盘的文件会被分成若干小块（chunks）。 每个小块的大小可以根据系统需求进行配置，以平衡性能和安全性。 哈希加密: 每个小块都会经过哈希加密，使用强大的哈希算法确保数据的完整性。 哈希值将与存储的小块一起存储，以便后续验证。 存储安全 对象存储: 加密后的小块将存储在巴别鸟企业网盘的对象存储系统中，确保高可用性和数据冗余。 无法还原的加密: 我们使用不可逆的哈希加密算法来确保存储的小块无法还原为原始文件内容，以确保文件存储的安全性。 安全传输: 小块数据在传输到对象存储系统时也会经过加密，以防止中间人攻击。 文件下载 临时下载链接: 当用户需要下载文件时，鉴权通过系统会动态地拼合分块，形成一个临时下载链接。 这个链接是唯一的，只有很短的有效期用于下载。再次下载需要从新生成下载链接。这个设定可以防止通过获取下载链接暴露文件。 下载解密: 在用户请求下载时，巴别鸟企业网盘会将分块数据在服务器端解密，然后合并为完整的文件。 这确保了文件在存储过程中即使硬盘被非法读取内容也不会暴露文件给任何未授权的访问者。 安全性 数据隔离: 分块加密技术将数据分成小块，每个小块都经过独立的哈希加密，以防止整个文件被暴露。 无法还原性: 使用不可逆的哈希算法确保了数据的无法还原性，即使攻击者获取了一部分小块数据，但因数据缺失也无法还原原始文件。 防止数据泄漏 安全审计日志 概述 在巴别鸟企业网盘中，我们强调数据访问和操作的可追溯性和安全性。为了实现这一目标，我们建立了一个强大的访问日志系统，用于记录整个系统的历史访问日志。这些日志包括文件的上传和下载、权限的变更、用户讨论批注、文件的增删改查、审批以及部门变更等操作。本章将详细介绍我们的安全审计日志系统和角色管理。 访问日志功能 全面的日志记录: 我们的日志系统记录了整个巴别鸟企业网盘的各种访问行为，确保每个操作都可以被追溯和审计。 记录的操作包括但不限于文件管理、权限控制、用户操作和部门管理。 关于巴别鸟日志的更多信息，可查阅：日志及报表 章节。 默认保存时间: 默认情况下，我们保存完整访问日志的时间段为90天。 这确保了足够的历史数据可供审计和检查。 可扩展的保存时间: 根据需要，管理员可以根据特定合规性要求扩展访问日志的保存时间（仅私有化系统支持）。 第三方日志管理系统 集成支持: 巴别鸟可对接第三方日志管理系统，以便将访问日志数据导入到外部日志平台进行进一步分析和长期存储。 安全管理员角色 安全保密员: 安全保密员具有高级的权限，可以在前台查看和管理所有部门的文件。 在企业管理后台，安全保密员具备以下权限： 制定公司安全策略（独有权限）。 管理组织结构。 成员管理。 权限管理。 安全审计员: 安全审计员可以在前台查看和管理所有部门的文件。 在企业管理后台，安全审计员具备以下权限： 查看企业安全策略。 查看组织结构。 查看成员权限。 查看权限管理。 查看文件访问日志。 安全性 数据隔离: 安全审计日志数据被严格隔离，只有授权的管理员可以访问和管理它们。 保密性: 安全保密员和安全审计员的角色都经过精心设计，一个负责安全策略，一个负责安全审计，互相监督，以确保数据的保密性和合规性。 扩展 自动化告警: 支持自动化告警机制，可添加监控项目，以在发现异常活动时及时通知超级管理员。 巴别鸟企业网盘的安全审计日志系统，包括功能、角色管理和安全性措施确保了数据访问和操作的可追溯性，并支持与第三方日志管理系统的集成，以进一步提高安全性和合规性。 安全性审查和测试 渗透测试 测试委托: 巴别鸟企业网盘会定期自己进行渗透测试或委托第三方机构，如绿盟科技，进行渗透测试，以评估系统的安全性。 渗透测试的目标是使用前沿的攻击技术，成熟的黑客攻击手段，以及标准的软件测试技术，测试指定系统的安全性，发现潜在的安全漏洞和风险。 测试阶段: 渗透测试包括以下流程： 信息收集：测试人员进行必要的信息收集，如IP地址、DNS记录、软件版本信息、IP段以及公开信息等。 渗透测试：测试人员根据信息收集阶段的结果，尝试入侵网络和系统。成功的情况下，可能获得普通权限。 缺陷利用：测试人员尝试提升权限，以获取对系统的完全控制权。在必要时，他们可能会回到信息收集阶段重新开始。 成果收集：测试人员对之前阶段发现的问题，如弱点和漏洞进行分类整理，并集中展示。 威胁分析：测试人员对发现的问题进行威胁分类和分析其潜在影响。 输出报告：测试人员根据测试和分析的结果，编写直观的渗透测试服务报告。 渗透测试的主要目标： 发现系统中的安全漏洞和潜在风险。 评估系统的安全性，包括身份验证、访问控制、数据保护等方面。 提供改进建议，以加强系统的安全性。 测试的结果将有助于我们采取适当的措施来修复发现的问题，提高系统的整体安全性。 最佳实践 巴别鸟企业网盘将定期进行渗透测试，以保持系统的安全性。 使用自动化工具和手动测试相结合，以提高渗透测试的全面性和准确性。 测试完成后根据报告及时整改，以确保系统的安全性。 未来扩展 我们将继续改进渗透测试流程，以适应不断演进的安全威胁。 考虑引入高级分析工具，以更深入地评估系统的安全性。 安全漏洞扫描 为了维护巴别鸟企业网盘的安全性，我们定期进行安全漏洞扫描。这项措施旨在自动化地检测系统中的潜在安全漏洞，以及可能导致安全威胁的问题。我们依托专业的扫描工具（例如：Qualys、Rapid7 InsightVM、OpenVAS）来确保系统持续保持在一个高度安全的状态。 扫描过程 安全漏洞扫描包括以下关键阶段： 定期扫描: 我们定期（通常是按计划的时间间隔）对系统进行安全漏洞扫描。 扫描工具自动化地执行一系列测试来发现潜在的漏洞。 扫描目标: 安全漏洞扫描的目标包括系统中的应用程序、操作系统、网络设备等各个方面。 扫描确保系统的整体安全性。 扫描结果: 扫描工具将识别并报告系统中发现的漏洞。 报告会包括漏洞的类型、严重程度以及可能的修复建议。 修复措施: 基于扫描结果，我们采取必要的修复措施来解决发现的漏洞和问题，以确保系统的安全性。 巴别鸟安全相关功能" }, { "lang": "zh", "slug": "ai-overview", "title": "智巢 AI 概览", "description": "完整介绍智巢 AI 的定位、模块、能力边界、权限控制、训练资料和适用场景。", "category": "智巢 AI", "top_category": "使用指南", "keywords": [ "智巢AI", "AI知识库", "AI搜索", "AI搜图", "智能体", "文档助理", "AI客服", "MCP" ], "url": "zh/ai-overview.html", "source": "content/zh/ai-overview.md", "summary": "智巢 AI 概览 智巢 AI 是巴别鸟企业网盘围绕企业文件、知识库、搜索、客服和数据分析建设的 AI 能力集合。它不是孤立的聊天工具，而是与巴别鸟的文件存储、权限体系、搜索引擎、素材库、项目协作、在线预览和私有化部署能力结合在一起，让 AI 能够在企业已有资料上工作。 智巢AI栏目 智巢 AI 栏目聚合 AI 搜索、搜图、智能体、企业 AI 助理和知识库等入口。 模块总览 模块 主要能力 典型场景 AI 搜索 学习企业文档，以自然语言检索并回答问题，支持追问、来源引用、多模态和权限判断 企业知识查询、制度查询、项目资料检索、技术资料问答 AI 搜图 通过文字描述或上传图片查找网盘内图片，搜索范围按权限过滤 素材库、品牌资产、设计图库、图片档案 智能数据助理 分析 Excel/表格数据，可跨多个 Excel 文件查询、分析、生成图表，支持第三方 URL 数据源 销售报表、项目台账、供应链数据、运营统计 自定义智能体与知识库机器人 自定义人设、提示词、回复逻辑、学习文件夹、行业模板、多 Agent 和网站嵌入 企业知识库、在线客服、行业助理、内部专家系统 企业 AI 助理 以对话形式集成多数智巢应用，回答企业文档知识点，多维度查找网盘文件 日常办公助理、文件查找、跨资料问答 AI 客服 学习产品说明、FAQ、客服文档，生成可对外服务的智能客服 官网客服、产品支持、售前问答、售后知识库 标准版模块 16 个标准模块的入口、用途和功能边界 管理员选型、实施范围确认、员工培训 AI 部署与定制 私有化部署、专属智能体、行业应用和按企业流程开发 AI 应用 私有云、专属模型服务、行业方案 ", "headings": [ { "level": 1, "title": "智巢 AI 概览", "id": "ai" }, { "level": 2, "title": "模块总览", "id": "section" }, { "level": 2, "title": "标准版模块清单", "id": "section-2" }, { "level": 2, "title": "核心能力", "id": "section-3" }, { "level": 2, "title": "与企业网盘的关系", "id": "section-4" }, { "level": 2, "title": "权限感知", "id": "section-5" }, { "level": 3, "title": "智巢AI的三个主要模块", "id": "ai-2" }, { "level": 3, "title": "技术解决方案", "id": "section-6" }, { "level": 3, "title": "优势", "id": "section-7" }, { "level": 2, "title": "权限与使用边界", "id": "section-8" }, { "level": 2, "title": "相关资料", "id": "section-9" } ], "images": [ { "src": "../assets/images/ai-column.webp", "alt": "智巢AI栏目", "caption": "智巢 AI 栏目聚合 AI 搜索、搜图、智能体、企业 AI 助理和知识库等入口。" } ], "text": "智巢 AI 概览 智巢 AI 是巴别鸟企业网盘围绕企业文件、知识库、搜索、客服和数据分析建设的 AI 能力集合。它不是孤立的聊天工具，而是与巴别鸟的文件存储、权限体系、搜索引擎、素材库、项目协作、在线预览和私有化部署能力结合在一起，让 AI 能够在企业已有资料上工作。 智巢AI栏目 智巢 AI 栏目聚合 AI 搜索、搜图、智能体、企业 AI 助理和知识库等入口。 模块总览 模块 主要能力 典型场景 AI 搜索 学习企业文档，以自然语言检索并回答问题，支持追问、来源引用、多模态和权限判断 企业知识查询、制度查询、项目资料检索、技术资料问答 AI 搜图 通过文字描述或上传图片查找网盘内图片，搜索范围按权限过滤 素材库、品牌资产、设计图库、图片档案 智能数据助理 分析 Excel/表格数据，可跨多个 Excel 文件查询、分析、生成图表，支持第三方 URL 数据源 销售报表、项目台账、供应链数据、运营统计 自定义智能体与知识库机器人 自定义人设、提示词、回复逻辑、学习文件夹、行业模板、多 Agent 和网站嵌入 企业知识库、在线客服、行业助理、内部专家系统 企业 AI 助理 以对话形式集成多数智巢应用，回答企业文档知识点，多维度查找网盘文件 日常办公助理、文件查找、跨资料问答 AI 客服 学习产品说明、FAQ、客服文档，生成可对外服务的智能客服 官网客服、产品支持、售前问答、售后知识库 标准版模块 16 个标准模块的入口、用途和功能边界 管理员选型、实施范围确认、员工培训 AI 部署与定制 私有化部署、专属智能体、行业应用和按企业流程开发 AI 应用 私有云、专属模型服务、行业方案 标准版模块清单 以下模块构成智巢 AI 标准版的主要功能范围。实际入口和可用性可能受版本、授权和部署配置影响。 编号 模块 入口 功能 1 智巢 AI 助理 顶部右侧 AI 助理入口 基于企业知识库进行 AI 对话，并可结合联网搜索回答问题 2 AI 搜索 搜索栏 搜索结果中包含 AI 搜索内容，用自然语言查找企业资料 3 智搜 智巢 AI 栏目 提供问题解答、深度研究和文章撰写能力 4 文搜图 智巢 AI 栏目 通过文字描述查找网盘中的图片 5 图搜图 智巢 AI 栏目、图片缩略图入口 通过上传或选择图片匹配网盘中的相似图片 6 图片 OCR 搜索、智巢 AI 栏目 识别图片中的文字，并让图片内容参与搜索 7 文档助手 文件预览界面 基于当前文档进行总结、问答和阅读辅助 8 AI 自动打标签 文件列表 为所选文档匹配标签库中最接近的标签 9 表格问答 Excel 文件预览界面、智巢 AI 栏目 基于 Excel 进行问答、表格生成和函数运算 10 深度思考 AI 助理、表格问答、文档助手 对复杂问题切换为更深入的推理模式 11 联网搜索 AI 助理 搜索互联网内容并结合外部知识回答 12 深度研究 智巢 AI 栏目中的智搜 通过多轮搜索和综合整理形成研究型回答 13 企业知识库 后台服务器端 企业文档自动入库，形成可问答、可检索的知识库 14 知识库机器人 智巢 AI 栏目“创建智体” 创建可自定义的智能体或知识库机器人 15 PDF 图片搜索 搜索栏 搜索带图片 PDF 文档中的图片内容 16 MCP 接口 接口 向 OpenClaw 及其他 AI 应用提供知识库访问和网盘文件操作能力 核心能力 企业专属 AI 助理与 AI 客服，服务对象可以是内部员工，也可以通过嵌入代码服务外部客户。 AI 搜索和基于对话的复合查询，用户可以像问同事一样追问资料、找文件、查制度、查项目。 AI 自动打标签与文件分类，用于降低人工整理素材、资料和归档文件的成本。 可自定义的 AI 知识库和智能体，可指定学习文件夹，也可以为不同知识域配置不同助理。 AI 搜图、图搜图、文搜图、OCR 和多模态理解，用于图片、素材和扫描件场景。 AI 文档阅读助理，用于总结单文档、提取重点、回答文档问题。 支持 Excel 的智能数据助理，用于多表交叉分析、查询和图表生成。 支持按需开发和私有化部署，适配行业知识、企业流程和部署安全要求。 与企业网盘的关系 智巢 AI 的价值来自“AI + 企业文件系统”的组合。传统通用聊天工具通常不知道企业内部文件在哪里、谁有权限看、哪个版本是最新、哪些文件属于同一项目；智巢 AI 则可以围绕巴别鸟中的文件、项目、部门、素材库和权限体系工作。对于企业来说，这意味着 AI 不只是回答通用知识，而是可以围绕企业自己的资料和业务语境提供帮助。 权限感知 智巢 AI 的搜索、问答、智能体和知识库需要和巴别鸟权限体系联动。一个用户能够从 AI 获得什么答案，应受到以下因素限制： 用户在企业、部门、项目和文件夹中的角色。 单文件或单文件夹的访问控制、分享权限和有效期。 管理员为智能体、知识库或 AI 助理指定的学习范围。 企业对外分享、下载、预览、水印、密级和审计策略。 私有化部署中对模型、索引、向量库和第三方 API 的配置策略。 智巢AI是巴别鸟企业网盘的AI平台，包括智巢AI客服、智巢AI知识库和智巢AI文档助理三个主要模块。这些模块结合了大模型API和自定义训练，能够满足企业的智能客服、文件内容分析和问题回答需求。 智巢AI的三个主要模块 智巢AI客服：该模块充当企业的AI客服，巴别鸟企业网盘自己也用了该模块回答用户在巴别鸟网盘使用中遇到的问题。我们也向企业客户开放这个服务，企业可以将产品说明书、FAQ、客服文档等资料提供给智巢AI进行学习，并微调以满足企业客服需求。企业还可以将智巢AI的代码块嵌入其网站，快速建立对外智能客服系统。智巢AI客服能显著降低客服成本，节约时间和资源。 智巢AI文档助理：这一模块用于回答关于单个文档的问题。通过分析文档内容，智巢AI能够回答关于文档内容的各种问题，从总结到揭示关键发现。用户可以向AI提问，而不必亲自阅读冗长的文档，从而提高工作效率。 智巢AI知识库：这一模块允许企业为自己定制专属AI助手。智巢AI团队会根据企业的资料帮助准备训练集、调参，从而建立专属的AI模型，可以根据巴别鸟上不同权限的人提供权限范围内的答案。可以以问答的形式作为企业知识库助手。 技术解决方案 智能回答问题：智巢AI借助大模型和自定义训练，以保证准确性。它还利用小模型来辅助大模型的工作，减少瞎说话、不懂装懂或泄密等问题。此外，智巢AI遵循巴别鸟的权限管理机制，确保用户只能获取其权限范围内的答案。 自动学习：智巢AI可通过学习用户提供的文件来积累知识，为用户提供更准确的答案。所有参与训练的文档都是由用户指定并同意的，以确保数据隐私和合规性。 优势 客服成本降低：智巢AI客服可以显著减少企业的客服成本，无需大规模培训人员，AI可以随时提供答案。 快速问题回答：智巢AI能够即时回答用户的问题，提高了工作效率。 文件内容分析：智巢AI文档助理可以快速分析文档内容，帮助用户快速获取信息，而无需阅读整个文档。 自定义AI助手：企业可以根据自己的需求为智巢AI知识库定制专属AI助手，以满足特定的知识管理和问题回答需求。 权限管理：智巢AI能够根据用户权限提供不同范围内的答案，以确保数据安全和合规性。 权限与使用边界 智巢 AI 的回答、搜索和文件引用应遵循巴别鸟现有权限体系。用户只能获得其账号、部门、项目、分享和文件访问控制范围内的内容。 参与学习、训练、索引或问答的资料应由企业或管理员指定；不应默认把所有文件都作为公开知识源。 对外客服、网站嵌入、第三方数据源、私有化模型和 GPU 算力属于可选部署或定制能力，应以实际授权、实施方案和企业配置为准。 当 AI 回答涉及合同、财务、医疗、法律、工程安全等高风险内容时，应把 AI 输出作为辅助信息，由专业人员复核。 相关资料 权限体系 安全与审计 FAQ：部署、AI 与技术问题 公开介绍：" }, { "lang": "zh", "slug": "ai-standard-modules", "title": "标准版模块", "description": "标准版模块汇总智巢 AI 的 16 个入口、功能和使用场景。", "category": "智巢 AI", "top_category": "使用指南", "keywords": [ "智巢AI", "标准版模块", "MCP", "知识库机器人" ], "url": "zh/ai-standard-modules.html", "source": "content/zh/ai-standard-modules.md", "summary": "标准版模块 标准版模块汇总智巢 AI 的 16 个入口、功能和使用场景。 标准版模块 标准版模块 的界面示意。 标准版模块清单 以下模块构成智巢 AI 标准版的主要功能范围。实际入口和可用性可能受版本、授权和部署配置影响。 编号 模块 入口 功能 1 智巢 AI 助理 顶部右侧 AI 助理入口 基于企业知识库进行 AI 对话，并可结合联网搜索回答问题 2 AI 搜索 搜索栏 搜索结果中包含 AI 搜索内容，用自然语言查找企业资料 3 智搜 智巢 AI 栏目 提供问题解答、深度研究和文章撰写能力 4 文搜图 智巢 AI 栏目 通过文字描述查找网盘中的图片 5 图搜图 智巢 AI 栏目、图片缩略图入口 通过上传或选择图片匹配网盘中的相似图片 6 图片 OCR 搜索、智巢 AI 栏目 识别图片中的文字，并让图片内容参与搜索 7 文档助手 文件预览界面 基于当前文档进行总结、问答和阅读辅助 8 AI 自动打标签 文件列表 为所选文档匹配标签库中最接近的标签 9 表格问答 Excel 文件预览界面、智巢 AI 栏目 基于 Excel 进行问答、表格生成和函数运算 10 深度思考 AI 助理、表格问答、文档助手 对复杂问题切换为更深入的推理模式 11 联网搜索 AI 助理 搜索互联网内容并结合外部知识回答 12 深度研究 智巢 AI 栏目中的智搜 通过多轮搜索和综合整理形成研究型回答 13 企业知识库 后台服务器端 企业文档自动入库，形成可问答、可检索的知识库 14 知识库机器人 智巢 AI 栏目“创建智体” 创建可自定义的智能体或知识库机器人 15 PDF 图片搜索 搜索栏 搜索带图片 ", "headings": [ { "level": 1, "title": "标准版模块", "id": "section" }, { "level": 2, "title": "标准版模块清单", "id": "section-2" }, { "level": 2, "title": "模块关系", "id": "section-3" }, { "level": 2, "title": "实施建议", "id": "section-4" }, { "level": 2, "title": "权限与使用边界", "id": "section-5" }, { "level": 2, "title": "相关资料", "id": "section-6" } ], "images": [ { "src": "../assets/images/ai-column.webp", "alt": "标准版模块", "caption": "标准版模块 的界面示意。" } ], "text": "标准版模块 标准版模块汇总智巢 AI 的 16 个入口、功能和使用场景。 标准版模块 标准版模块 的界面示意。 标准版模块清单 以下模块构成智巢 AI 标准版的主要功能范围。实际入口和可用性可能受版本、授权和部署配置影响。 编号 模块 入口 功能 1 智巢 AI 助理 顶部右侧 AI 助理入口 基于企业知识库进行 AI 对话，并可结合联网搜索回答问题 2 AI 搜索 搜索栏 搜索结果中包含 AI 搜索内容，用自然语言查找企业资料 3 智搜 智巢 AI 栏目 提供问题解答、深度研究和文章撰写能力 4 文搜图 智巢 AI 栏目 通过文字描述查找网盘中的图片 5 图搜图 智巢 AI 栏目、图片缩略图入口 通过上传或选择图片匹配网盘中的相似图片 6 图片 OCR 搜索、智巢 AI 栏目 识别图片中的文字，并让图片内容参与搜索 7 文档助手 文件预览界面 基于当前文档进行总结、问答和阅读辅助 8 AI 自动打标签 文件列表 为所选文档匹配标签库中最接近的标签 9 表格问答 Excel 文件预览界面、智巢 AI 栏目 基于 Excel 进行问答、表格生成和函数运算 10 深度思考 AI 助理、表格问答、文档助手 对复杂问题切换为更深入的推理模式 11 联网搜索 AI 助理 搜索互联网内容并结合外部知识回答 12 深度研究 智巢 AI 栏目中的智搜 通过多轮搜索和综合整理形成研究型回答 13 企业知识库 后台服务器端 企业文档自动入库，形成可问答、可检索的知识库 14 知识库机器人 智巢 AI 栏目“创建智体” 创建可自定义的智能体或知识库机器人 15 PDF 图片搜索 搜索栏 搜索带图片 PDF 文档中的图片内容 16 MCP 接口 接口 向 OpenClaw 及其他 AI 应用提供知识库访问和网盘文件操作能力 模块关系 这 16 个模块可以分为四组：第一组是面向普通用户的对话、搜索、文档阅读和表格问答；第二组是面向图片、PDF 图片和 OCR 的多模态检索；第三组是面向管理员和实施团队的企业知识库、知识库机器人和智能体配置；第四组是面向开发和集成的 MCP 接口、第三方数据源和按需开发能力。 实施建议 先确认企业最需要解决的是“找文件”“读文档”“做客服”“分析表格”还是“对外知识库”。 对内部员工优先开放 AI 助理、AI 搜索、文档助手和表格问答。 对素材或品牌团队重点启用文搜图、图搜图、图片 OCR 和 PDF 图片搜索。 对客服、售前、培训和制度问答场景重点配置知识库机器人和自定义智能体。 对需要外部 AI 应用访问知识库或执行文件操作的场景，再规划 MCP 接口权限和审计策略。 权限与使用边界 智巢 AI 的回答、搜索和文件引用应遵循巴别鸟现有权限体系。用户只能获得其账号、部门、项目、分享和文件访问控制范围内的内容。 参与学习、训练、索引或问答的资料应由企业或管理员指定；不应默认把所有文件都作为公开知识源。 对外客服、网站嵌入、第三方数据源、私有化模型和 GPU 算力属于可选部署或定制能力，应以实际授权、实施方案和企业配置为准。 当 AI 回答涉及合同、财务、医疗、法律、工程安全等高风险内容时，应把 AI 输出作为辅助信息，由专业人员复核。 相关资料 权限体系 安全与审计 FAQ：部署、AI 与技术问题 公开介绍：" }, { "lang": "zh", "slug": "ai-search", "title": "AI 搜索", "description": "AI 搜索用于用自然语言检索权限范围内的企业文件、资料和知识。", "category": "智巢 AI", "top_category": "使用指南", "keywords": [ "智巢AI", "AI搜索", "权限搜索", "RAG" ], "url": "zh/ai-search.html", "source": "content/zh/ai-search.md", "summary": "AI 搜索 AI 搜索用于用自然语言检索权限范围内的企业文件、资料和知识。 AI 搜索 AI 搜索 的界面示意。 功能说明 AI 搜索面向企业资料问答和知识检索。用户可以输入自然语言问题，由系统在权限范围内检索相关文件，并结合大模型生成答案。它适合回答“某个制度怎么规定”“某项目的设计资料在哪里”“某客户合同里有哪些关键条款”“某类文件中有哪些相似内容”等问题。 主要能力 学习企业指定范围内的文档、知识资料和文件内容。 根据用户权限判断可检索范围，避免越权回答。 支持追问，用户可以围绕上一次回答继续深入。 回答给出信息来源，便于用户回到对应文件核对。 支持识别图片中的文字，并可与 OCR、多模态能力结合。 搜索结果中可包含 AI 生成内容，也可回到原始文件核验来源。 可与全文搜索、标签、说明、注释、文件名搜索等能力形成互补。 适用场景 企业制度、流程、合同、项目资料、产品说明和客服资料问答。 研发、工程、设计、法务、行政、人事等部门的资料检索。 多文件、多项目、多版本资料的快速定位。 让新员工通过提问理解企业资料，而不是逐个目录翻找。 权限与使用边界 智巢 AI 的回答、搜索和文件引用应遵循巴别鸟现有权限体系。用户只能获得其账号、部门、项目、分享和文件访问控制范围内的内容。 参与学习、训练、索引或问答的资料应由企业或管理员指定；不应默认把所有文件都作为公开知识源。 对外客服、网站嵌入、第三方数据源、私有化模型和 GPU 算力属于可选部署或定制能力，应以实际授权、实施方案和企业配置为准。 当 AI 回答涉及合同、财务、医疗、法律、工程安全等高风险内容时，应把 AI 输出作为辅助信", "headings": [ { "level": 1, "title": "AI 搜索", "id": "ai" }, { "level": 2, "title": "功能说明", "id": "section" }, { "level": 2, "title": "主要能力", "id": "section-2" }, { "level": 2, "title": "适用场景", "id": "section-3" }, { "level": 2, "title": "权限与使用边界", "id": "section-4" }, { "level": 2, "title": "相关资料", "id": "section-5" } ], "images": [ { "src": "../assets/images/ai-search.webp", "alt": "AI 搜索", "caption": "AI 搜索 的界面示意。" } ], "text": "AI 搜索 AI 搜索用于用自然语言检索权限范围内的企业文件、资料和知识。 AI 搜索 AI 搜索 的界面示意。 功能说明 AI 搜索面向企业资料问答和知识检索。用户可以输入自然语言问题，由系统在权限范围内检索相关文件，并结合大模型生成答案。它适合回答“某个制度怎么规定”“某项目的设计资料在哪里”“某客户合同里有哪些关键条款”“某类文件中有哪些相似内容”等问题。 主要能力 学习企业指定范围内的文档、知识资料和文件内容。 根据用户权限判断可检索范围，避免越权回答。 支持追问，用户可以围绕上一次回答继续深入。 回答给出信息来源，便于用户回到对应文件核对。 支持识别图片中的文字，并可与 OCR、多模态能力结合。 搜索结果中可包含 AI 生成内容，也可回到原始文件核验来源。 可与全文搜索、标签、说明、注释、文件名搜索等能力形成互补。 适用场景 企业制度、流程、合同、项目资料、产品说明和客服资料问答。 研发、工程、设计、法务、行政、人事等部门的资料检索。 多文件、多项目、多版本资料的快速定位。 让新员工通过提问理解企业资料，而不是逐个目录翻找。 权限与使用边界 智巢 AI 的回答、搜索和文件引用应遵循巴别鸟现有权限体系。用户只能获得其账号、部门、项目、分享和文件访问控制范围内的内容。 参与学习、训练、索引或问答的资料应由企业或管理员指定；不应默认把所有文件都作为公开知识源。 对外客服、网站嵌入、第三方数据源、私有化模型和 GPU 算力属于可选部署或定制能力，应以实际授权、实施方案和企业配置为准。 当 AI 回答涉及合同、财务、医疗、法律、工程安全等高风险内容时，应把 AI 输出作为辅助信息，由专业人员复核。 相关资料 权限体系 安全与审计 FAQ：部署、AI 与技术问题 公开介绍：" }, { "lang": "zh", "slug": "ai-image-search", "title": "AI 搜图", "description": "AI 搜图用于通过文字描述或上传图片查找网盘中的图片和视觉资产。", "category": "智巢 AI", "top_category": "使用指南", "keywords": [ "智巢AI", "AI搜图", "图搜图", "文搜图", "OCR" ], "url": "zh/ai-image-search.html", "source": "content/zh/ai-image-search.md", "summary": "AI 搜图 AI 搜图用于通过文字描述或上传图片查找网盘中的图片和视觉资产。 AI 搜图 AI 搜图 的界面示意。 功能说明 AI 搜图面向企业图片、素材、设计稿、产品图、活动图和扫描资料检索。它既可以通过文字描述查找图片，也可以上传一张图片搜索相似图片，适合素材库和视觉资产数量很大的企业。 主要能力 文搜图：输入“蓝色包装盒”“会议现场照片”“某产品白底图”等描述查找图片。 图搜图：上传参考图，查找相似或相关图片。 按权限过滤搜索范围，用户只能搜索自己可访问的图片。 可结合 OCR 识别图片中的文字，让扫描件、海报、截图也能参与检索。 PDF 图片搜索可让带图片的 PDF 文档参与图片内容检索。 适合素材库、品牌资产库、设计档案、营销图库和项目图纸资料。 与素材库的关系 AI 搜图可以和巴别鸟素材库、瀑布流展示、标签、说明、预览和分享结合。对于品牌、营销、设计、工程和档案团队，AI 搜图可以减少手工打标签和逐级目录查找的工作量。 权限与使用边界 智巢 AI 的回答、搜索和文件引用应遵循巴别鸟现有权限体系。用户只能获得其账号、部门、项目、分享和文件访问控制范围内的内容。 参与学习、训练、索引或问答的资料应由企业或管理员指定；不应默认把所有文件都作为公开知识源。 对外客服、网站嵌入、第三方数据源、私有化模型和 GPU 算力属于可选部署或定制能力，应以实际授权、实施方案和企业配置为准。 当 AI 回答涉及合同、财务、医疗、法律、工程安全等高风险内容时，应把 AI 输出作为辅助信息，由专业人员复核。 相关资料 权限体系 安全与审计 FAQ：部署、AI 与技术问题 公开介绍：", "headings": [ { "level": 1, "title": "AI 搜图", "id": "ai" }, { "level": 2, "title": "功能说明", "id": "section" }, { "level": 2, "title": "主要能力", "id": "section-2" }, { "level": 2, "title": "与素材库的关系", "id": "section-3" }, { "level": 2, "title": "权限与使用边界", "id": "section-4" }, { "level": 2, "title": "相关资料", "id": "section-5" } ], "images": [ { "src": "../assets/images/ai-image-search.webp", "alt": "AI 搜图", "caption": "AI 搜图 的界面示意。" } ], "text": "AI 搜图 AI 搜图用于通过文字描述或上传图片查找网盘中的图片和视觉资产。 AI 搜图 AI 搜图 的界面示意。 功能说明 AI 搜图面向企业图片、素材、设计稿、产品图、活动图和扫描资料检索。它既可以通过文字描述查找图片，也可以上传一张图片搜索相似图片，适合素材库和视觉资产数量很大的企业。 主要能力 文搜图：输入“蓝色包装盒”“会议现场照片”“某产品白底图”等描述查找图片。 图搜图：上传参考图，查找相似或相关图片。 按权限过滤搜索范围，用户只能搜索自己可访问的图片。 可结合 OCR 识别图片中的文字，让扫描件、海报、截图也能参与检索。 PDF 图片搜索可让带图片的 PDF 文档参与图片内容检索。 适合素材库、品牌资产库、设计档案、营销图库和项目图纸资料。 与素材库的关系 AI 搜图可以和巴别鸟素材库、瀑布流展示、标签、说明、预览和分享结合。对于品牌、营销、设计、工程和档案团队，AI 搜图可以减少手工打标签和逐级目录查找的工作量。 权限与使用边界 智巢 AI 的回答、搜索和文件引用应遵循巴别鸟现有权限体系。用户只能获得其账号、部门、项目、分享和文件访问控制范围内的内容。 参与学习、训练、索引或问答的资料应由企业或管理员指定；不应默认把所有文件都作为公开知识源。 对外客服、网站嵌入、第三方数据源、私有化模型和 GPU 算力属于可选部署或定制能力，应以实际授权、实施方案和企业配置为准。 当 AI 回答涉及合同、财务、医疗、法律、工程安全等高风险内容时，应把 AI 输出作为辅助信息，由专业人员复核。 相关资料 权限体系 安全与审计 FAQ：部署、AI 与技术问题 公开介绍：" }, { "lang": "zh", "slug": "ai-data-assistant", "title": "智能数据助理", "description": "智能数据助理用于 Excel 和第三方数据源的查询、分析、交叉统计和图表生成。", "category": "智巢 AI", "top_category": "使用指南", "keywords": [ "智巢AI", "智能数据助理", "Excel", "数据分析", "图表" ], "url": "zh/ai-data-assistant.html", "source": "content/zh/ai-data-assistant.md", "summary": "智能数据助理 智能数据助理用于 Excel 和第三方数据源的查询、分析、交叉统计和图表生成。 智能数据助理 智能数据助理 的界面示意。 功能说明 智能数据助理面向企业表格、台账、报表和业务数据查询。它可以围绕多个 Excel 文件进行交叉分析，也可以按实施方案接入以 URL 形式访问的第三方数据源。适合不想手工写公式、筛选条件或统计脚本的业务用户。 主要能力 支持多个 Excel 文件的交叉分析和综合查询。 支持以 URL 形式访问第三方数据源，具体范围取决于企业配置。 AI 可根据问题自动编程进行数据查询、清洗、统计和分析。 可根据查询结果生成图表，辅助制作报表或经营分析。 支持在 Excel 文件预览界面或智巢 AI 栏目中使用表格问答。 可结合深度思考模式处理更复杂的统计、函数和分析任务。 支持多语言交互，适合跨地区或跨语言团队使用。 适用场景 销售订单、库存、项目台账、供应商清单、客户清单和财务明细的汇总分析。 多个部门维护的 Excel 文件之间进行交叉比对。 用自然语言提出问题，例如“按区域统计本月销售额”“找出逾期项目”“比较两张表中缺失的客户”。 注意事项 智能数据助理处理的数据范围应由企业确认。对财务、人事、客户隐私等敏感数据，应结合权限、审计和脱敏策略使用。 权限与使用边界 智巢 AI 的回答、搜索和文件引用应遵循巴别鸟现有权限体系。用户只能获得其账号、部门、项目、分享和文件访问控制范围内的内容。 参与学习、训练、索引或问答的资料应由企业或管理员指定；不应默认把所有文件都作为公开知识源。 对外客服、网站嵌入、第三方数据源、私有化模型和 GPU 算力属于可选部", "headings": [ { "level": 1, "title": "智能数据助理", "id": "section" }, { "level": 2, "title": "功能说明", "id": "section-2" }, { "level": 2, "title": "主要能力", "id": "section-3" }, { "level": 2, "title": "适用场景", "id": "section-4" }, { "level": 2, "title": "注意事项", "id": "section-5" }, { "level": 2, "title": "权限与使用边界", "id": "section-6" }, { "level": 2, "title": "相关资料", "id": "section-7" } ], "images": [ { "src": "../assets/images/ai-assistant.webp", "alt": "智能数据助理", "caption": "智能数据助理 的界面示意。" } ], "text": "智能数据助理 智能数据助理用于 Excel 和第三方数据源的查询、分析、交叉统计和图表生成。 智能数据助理 智能数据助理 的界面示意。 功能说明 智能数据助理面向企业表格、台账、报表和业务数据查询。它可以围绕多个 Excel 文件进行交叉分析，也可以按实施方案接入以 URL 形式访问的第三方数据源。适合不想手工写公式、筛选条件或统计脚本的业务用户。 主要能力 支持多个 Excel 文件的交叉分析和综合查询。 支持以 URL 形式访问第三方数据源，具体范围取决于企业配置。 AI 可根据问题自动编程进行数据查询、清洗、统计和分析。 可根据查询结果生成图表，辅助制作报表或经营分析。 支持在 Excel 文件预览界面或智巢 AI 栏目中使用表格问答。 可结合深度思考模式处理更复杂的统计、函数和分析任务。 支持多语言交互，适合跨地区或跨语言团队使用。 适用场景 销售订单、库存、项目台账、供应商清单、客户清单和财务明细的汇总分析。 多个部门维护的 Excel 文件之间进行交叉比对。 用自然语言提出问题，例如“按区域统计本月销售额”“找出逾期项目”“比较两张表中缺失的客户”。 注意事项 智能数据助理处理的数据范围应由企业确认。对财务、人事、客户隐私等敏感数据，应结合权限、审计和脱敏策略使用。 权限与使用边界 智巢 AI 的回答、搜索和文件引用应遵循巴别鸟现有权限体系。用户只能获得其账号、部门、项目、分享和文件访问控制范围内的内容。 参与学习、训练、索引或问答的资料应由企业或管理员指定；不应默认把所有文件都作为公开知识源。 对外客服、网站嵌入、第三方数据源、私有化模型和 GPU 算力属于可选部署或定制能力，应以实际授权、实施方案和企业配置为准。 当 AI 回答涉及合同、财务、医疗、法律、工程安全等高风险内容时，应把 AI 输出作为辅助信息，由专业人员复核。 相关资料 权限体系 安全与审计 FAQ：部署、AI 与技术问题 公开介绍：" }, { "lang": "zh", "slug": "ai-assistant-agent", "title": "自定义智能体与知识库机器人", "description": "自定义智能体用于构建企业专属知识库、AI 客服、行业助理和多 Agent 工作流。", "category": "智巢 AI", "top_category": "使用指南", "keywords": [ "智巢AI", "自定义智能体", "知识库机器人", "AI客服", "多Agent" ], "url": "zh/ai-assistant-agent.html", "source": "content/zh/ai-assistant-agent.md", "summary": "自定义智能体与知识库机器人 自定义智能体用于构建企业专属知识库、AI 客服、行业助理和多 Agent 工作流。 自定义智能体与知识库机器人 自定义智能体与知识库机器人 的界面示意。 功能说明 自定义智能体是智巢 AI 中面向企业知识库和业务助理的核心模块。管理员或实施团队可以为不同业务场景配置不同智能体，例如客服、知识库、分析师、作家、项目助理、售前顾问或行业专家。 自定义知识库机器人 知识库机器人可以面向企业资料问答、在线客服和专属知识助理场景。 主要能力 自定义智能体的人设、回复逻辑和提示词。 指定智能体学习的目标文件夹或资料范围。 支持以 URL 形式访问第三方数据源，具体取决于实施配置。 提供客服、知识库、分析师、写作等多种行业预设模板。 支持多 Agent，让不同智能体按业务分工服务不同问题。 可生成嵌入代码，在第三方网站或企业门户中使用。 可作为企业知识库机器人，为不同知识域配置不同助理。 知识库建设方式 企业可以把产品说明书、FAQ、客服文档、制度文件、培训材料、项目资料等交给指定智能体学习。与传统人工整理知识库相比，智巢 AI 更强调直接利用企业已有文件，减少重复撰写知识库条目的成本。 使用建议 按业务域拆分智能体，例如“客服机器人”“售前知识库”“内部制度助理”“项目资料助理”。 每个智能体指定清晰的学习范围和使用对象，避免一个智能体承载过多无关知识。 对外客服类智能体应设置回答边界、免责声明、人工转接和敏感问题处理规则。 权限与使用边界 智巢 AI 的回答、搜索和文件引用应遵循巴别鸟现有权限体系。用户只能获得其账号、部门、项目、分享和文件访问控制范围内的内容", "headings": [ { "level": 1, "title": "自定义智能体与知识库机器人", "id": "section" }, { "level": 2, "title": "功能说明", "id": "section-2" }, { "level": 2, "title": "主要能力", "id": "section-3" }, { "level": 2, "title": "知识库建设方式", "id": "section-4" }, { "level": 2, "title": "使用建议", "id": "section-5" }, { "level": 2, "title": "权限与使用边界", "id": "section-6" }, { "level": 2, "title": "相关资料", "id": "section-7" } ], "images": [ { "src": "../assets/images/ai-agent.webp", "alt": "自定义智能体与知识库机器人", "caption": "自定义智能体与知识库机器人 的界面示意。" }, { "src": "../assets/images/ai-bot.webp", "alt": "自定义知识库机器人", "caption": "知识库机器人可以面向企业资料问答、在线客服和专属知识助理场景。" } ], "text": "自定义智能体与知识库机器人 自定义智能体用于构建企业专属知识库、AI 客服、行业助理和多 Agent 工作流。 自定义智能体与知识库机器人 自定义智能体与知识库机器人 的界面示意。 功能说明 自定义智能体是智巢 AI 中面向企业知识库和业务助理的核心模块。管理员或实施团队可以为不同业务场景配置不同智能体，例如客服、知识库、分析师、作家、项目助理、售前顾问或行业专家。 自定义知识库机器人 知识库机器人可以面向企业资料问答、在线客服和专属知识助理场景。 主要能力 自定义智能体的人设、回复逻辑和提示词。 指定智能体学习的目标文件夹或资料范围。 支持以 URL 形式访问第三方数据源，具体取决于实施配置。 提供客服、知识库、分析师、写作等多种行业预设模板。 支持多 Agent，让不同智能体按业务分工服务不同问题。 可生成嵌入代码，在第三方网站或企业门户中使用。 可作为企业知识库机器人，为不同知识域配置不同助理。 知识库建设方式 企业可以把产品说明书、FAQ、客服文档、制度文件、培训材料、项目资料等交给指定智能体学习。与传统人工整理知识库相比，智巢 AI 更强调直接利用企业已有文件，减少重复撰写知识库条目的成本。 使用建议 按业务域拆分智能体，例如“客服机器人”“售前知识库”“内部制度助理”“项目资料助理”。 每个智能体指定清晰的学习范围和使用对象，避免一个智能体承载过多无关知识。 对外客服类智能体应设置回答边界、免责声明、人工转接和敏感问题处理规则。 权限与使用边界 智巢 AI 的回答、搜索和文件引用应遵循巴别鸟现有权限体系。用户只能获得其账号、部门、项目、分享和文件访问控制范围内的内容。 参与学习、训练、索引或问答的资料应由企业或管理员指定；不应默认把所有文件都作为公开知识源。 对外客服、网站嵌入、第三方数据源、私有化模型和 GPU 算力属于可选部署或定制能力，应以实际授权、实施方案和企业配置为准。 当 AI 回答涉及合同、财务、医疗、法律、工程安全等高风险内容时，应把 AI 输出作为辅助信息，由专业人员复核。 相关资料 权限体系 安全与审计 FAQ：部署、AI 与技术问题 公开介绍：" }, { "lang": "zh", "slug": "ai-assistant", "title": "企业 AI 助理", "description": "企业 AI 助理以对话形式集成智巢应用，帮助用户查文件、问知识、读文档和完成办公任务。", "category": "智巢 AI", "top_category": "使用指南", "keywords": [ "智巢AI", "企业AI助理", "文档助理", "多模态" ], "url": "zh/ai-assistant.html", "source": "content/zh/ai-assistant.md", "summary": "企业 AI 助理 企业 AI 助理以对话形式集成智巢应用，帮助用户查文件、问知识、读文档和完成办公任务。 企业 AI 助理 企业 AI 助理 的界面示意。 功能说明 企业 AI 助理是面向普通员工的统一对话入口。用户不需要先判断应该使用搜索、搜图、文档助理还是知识库机器人，可以直接用对话方式提出问题，由 AI 在企业资料和已启用模块中完成检索、阅读、分析或进一步引导。 主要能力 以对话形式集成多数智巢应用。 回答企业所有授权范围内文档中涉及的知识点。 通过多轮对话多维度查找网盘文件。 可结合联网搜索回答外部知识问题。 可切换深度思考模式处理复杂问题。 支持多模态输入和输出能力，具体能力取决于部署模型和模块配置。 可作为员工日常工作中的资料助理、文件助理和知识问答入口。 与文档助理的关系 文档助理更关注“单个文档”的阅读和问答；企业 AI 助理更关注“企业资料范围内”的综合查询和任务入口。两者可以互补：用户先通过企业 AI 助理找到文件，再进入文档助理深入阅读。 权限与使用边界 智巢 AI 的回答、搜索和文件引用应遵循巴别鸟现有权限体系。用户只能获得其账号、部门、项目、分享和文件访问控制范围内的内容。 参与学习、训练、索引或问答的资料应由企业或管理员指定；不应默认把所有文件都作为公开知识源。 对外客服、网站嵌入、第三方数据源、私有化模型和 GPU 算力属于可选部署或定制能力，应以实际授权、实施方案和企业配置为准。 当 AI 回答涉及合同、财务、医疗、法律、工程安全等高风险内容时，应把 AI 输出作为辅助信息，由专业人员复核。 相关资料 权限体系 安全与审计 FAQ：部署、AI 与", "headings": [ { "level": 1, "title": "企业 AI 助理", "id": "ai" }, { "level": 2, "title": "功能说明", "id": "section" }, { "level": 2, "title": "主要能力", "id": "section-2" }, { "level": 2, "title": "与文档助理的关系", "id": "section-3" }, { "level": 2, "title": "权限与使用边界", "id": "section-4" }, { "level": 2, "title": "相关资料", "id": "section-5" } ], "images": [ { "src": "../assets/images/ai-assistant.webp", "alt": "企业 AI 助理", "caption": "企业 AI 助理 的界面示意。" } ], "text": "企业 AI 助理 企业 AI 助理以对话形式集成智巢应用，帮助用户查文件、问知识、读文档和完成办公任务。 企业 AI 助理 企业 AI 助理 的界面示意。 功能说明 企业 AI 助理是面向普通员工的统一对话入口。用户不需要先判断应该使用搜索、搜图、文档助理还是知识库机器人，可以直接用对话方式提出问题，由 AI 在企业资料和已启用模块中完成检索、阅读、分析或进一步引导。 主要能力 以对话形式集成多数智巢应用。 回答企业所有授权范围内文档中涉及的知识点。 通过多轮对话多维度查找网盘文件。 可结合联网搜索回答外部知识问题。 可切换深度思考模式处理复杂问题。 支持多模态输入和输出能力，具体能力取决于部署模型和模块配置。 可作为员工日常工作中的资料助理、文件助理和知识问答入口。 与文档助理的关系 文档助理更关注“单个文档”的阅读和问答；企业 AI 助理更关注“企业资料范围内”的综合查询和任务入口。两者可以互补：用户先通过企业 AI 助理找到文件，再进入文档助理深入阅读。 权限与使用边界 智巢 AI 的回答、搜索和文件引用应遵循巴别鸟现有权限体系。用户只能获得其账号、部门、项目、分享和文件访问控制范围内的内容。 参与学习、训练、索引或问答的资料应由企业或管理员指定；不应默认把所有文件都作为公开知识源。 对外客服、网站嵌入、第三方数据源、私有化模型和 GPU 算力属于可选部署或定制能力，应以实际授权、实施方案和企业配置为准。 当 AI 回答涉及合同、财务、医疗、法律、工程安全等高风险内容时，应把 AI 输出作为辅助信息，由专业人员复核。 相关资料 权限体系 安全与审计 FAQ：部署、AI 与技术问题 公开介绍：" }, { "lang": "zh", "slug": "ai-customer-service", "title": "AI 客服", "description": "AI 客服用于学习产品说明、FAQ、客服文档并为客户或员工提供自动问答服务。", "category": "智巢 AI", "top_category": "使用指南", "keywords": [ "智巢AI", "AI客服", "客服机器人", "网站嵌入" ], "url": "zh/ai-customer-service.html", "source": "content/zh/ai-customer-service.md", "summary": "AI 客服 AI 客服用于学习产品说明、FAQ、客服文档并为客户或员工提供自动问答服务。 AI 客服 AI 客服 的界面示意。 功能说明 AI 客服是智巢 AI 面向对外服务和内部支持的模块。企业可以提供产品说明书、FAQ、客服文档、售后流程、政策说明等资料，让 AI 学习并形成可对话的客服能力。 主要能力 基于企业指定资料回答客户或员工问题。 可通过嵌入代码接入企业网站、帮助中心或业务入口。 可作为售前问答、售后支持、产品说明、内部 IT 支持或知识库入口。 支持通过微调、提示词、问答范围和人工复核流程提高回答稳定性。 可降低重复问答的人力成本，把复杂问题转给人工客服或业务人员。 资料准备 建议企业准备结构清晰、版本明确、可公开或可授权使用的资料，包括产品说明、常见问题、服务条款、操作手册、故障处理、价格口径、交付说明等。对外客服尤其要确认哪些内容可以公开回答，哪些问题必须转人工。 权限与使用边界 智巢 AI 的回答、搜索和文件引用应遵循巴别鸟现有权限体系。用户只能获得其账号、部门、项目、分享和文件访问控制范围内的内容。 参与学习、训练、索引或问答的资料应由企业或管理员指定；不应默认把所有文件都作为公开知识源。 对外客服、网站嵌入、第三方数据源、私有化模型和 GPU 算力属于可选部署或定制能力，应以实际授权、实施方案和企业配置为准。 当 AI 回答涉及合同、财务、医疗、法律、工程安全等高风险内容时，应把 AI 输出作为辅助信息，由专业人员复核。 相关资料 权限体系 安全与审计 FAQ：部署、AI 与技术问题 公开介绍：", "headings": [ { "level": 1, "title": "AI 客服", "id": "ai" }, { "level": 2, "title": "功能说明", "id": "section" }, { "level": 2, "title": "主要能力", "id": "section-2" }, { "level": 2, "title": "资料准备", "id": "section-3" }, { "level": 2, "title": "权限与使用边界", "id": "section-4" }, { "level": 2, "title": "相关资料", "id": "section-5" } ], "images": [ { "src": "../assets/images/ai-bot.webp", "alt": "AI 客服", "caption": "AI 客服 的界面示意。" } ], "text": "AI 客服 AI 客服用于学习产品说明、FAQ、客服文档并为客户或员工提供自动问答服务。 AI 客服 AI 客服 的界面示意。 功能说明 AI 客服是智巢 AI 面向对外服务和内部支持的模块。企业可以提供产品说明书、FAQ、客服文档、售后流程、政策说明等资料，让 AI 学习并形成可对话的客服能力。 主要能力 基于企业指定资料回答客户或员工问题。 可通过嵌入代码接入企业网站、帮助中心或业务入口。 可作为售前问答、售后支持、产品说明、内部 IT 支持或知识库入口。 支持通过微调、提示词、问答范围和人工复核流程提高回答稳定性。 可降低重复问答的人力成本，把复杂问题转给人工客服或业务人员。 资料准备 建议企业准备结构清晰、版本明确、可公开或可授权使用的资料，包括产品说明、常见问题、服务条款、操作手册、故障处理、价格口径、交付说明等。对外客服尤其要确认哪些内容可以公开回答，哪些问题必须转人工。 权限与使用边界 智巢 AI 的回答、搜索和文件引用应遵循巴别鸟现有权限体系。用户只能获得其账号、部门、项目、分享和文件访问控制范围内的内容。 参与学习、训练、索引或问答的资料应由企业或管理员指定；不应默认把所有文件都作为公开知识源。 对外客服、网站嵌入、第三方数据源、私有化模型和 GPU 算力属于可选部署或定制能力，应以实际授权、实施方案和企业配置为准。 当 AI 回答涉及合同、财务、医疗、法律、工程安全等高风险内容时，应把 AI 输出作为辅助信息，由专业人员复核。 相关资料 权限体系 安全与审计 FAQ：部署、AI 与技术问题 公开介绍：" }, { "lang": "zh", "slug": "ai-deployment-customization", "title": "AI 部署与定制", "description": "介绍智巢 AI 私有化部署、GPU 算力、专属智能体、行业应用和按需开发。", "category": "智巢 AI", "top_category": "使用指南", "keywords": [ "智巢AI", "私有化", "GPU", "定制开发", "智能体" ], "url": "zh/ai-deployment-customization.html", "source": "content/zh/ai-deployment-customization.md", "summary": "AI 部署与定制 介绍智巢 AI 私有化部署、GPU 算力、专属智能体、行业应用和按需开发。 AI 部署与定制 AI 部署与定制 的界面示意。 私有化部署方式 智巢 AI 私有化可以按数据安全、预算、算力、模型调用和联网搜索要求分为三类。实际项目应以正式实施评估为准。 方式 说明 适用场景 全部私有化 在自建服务器上部署 DeepSeek、千问等约 32B 级模型，模型推理和知识库能力尽量在客户环境内运行 对数据出域限制严格、预算和 GPU 算力充足的客户 向量本地化 在自建服务器部署向量模型和知识库入库运算，问答推理使用公网大模型 API 希望知识库入库过程本地可控，同时接受外部模型推理的客户 向量仅本地存储 自建服务器保存完成向量化后的知识库，模型推理和向量运算使用公网大模型 API 希望降低本地 GPU 成本，并接受外部模型服务的客户 参考服务器配置 部署方式 服务器用途 参考配置 算卡配置 全部私有化 算力服务器 CPU 2 8368Q、256G 内存、960G SSD 2、8TB HDD 2 5880 ADA 48G 4 向量本地化 向量服务器 CPU 2 4310、128G 内存、480G SSD、4TB HDD 2 3090 24G 2 向量仅本地存储 向量服务器 CPU 2 4310、128G 内存、480G SSD、4TB HDD 2 无 外部模型和联网搜索 部分部署方式会使用公网大模型 API、联网搜索 API 或 TokenPlan。可选模型和服务可包括 Minmax、智谱 GLM、DeepSeek 以及腾讯云联网搜索 API 等。费用会随模型、调用量、联", "headings": [ { "level": 1, "title": "AI 部署与定制", "id": "ai" }, { "level": 2, "title": "私有化部署方式", "id": "section" }, { "level": 2, "title": "参考服务器配置", "id": "section-2" }, { "level": 2, "title": "外部模型和联网搜索", "id": "section-3" }, { "level": 2, "title": "部署形态", "id": "section-4" }, { "level": 2, "title": "按需开发", "id": "section-5" }, { "level": 2, "title": "典型交付内容", "id": "section-6" }, { "level": 2, "title": "私有化注意事项", "id": "section-7" }, { "level": 2, "title": "权限与使用边界", "id": "section-8" }, { "level": 2, "title": "相关资料", "id": "section-9" } ], "images": [ { "src": "../assets/images/ai-column.webp", "alt": "AI 部署与定制", "caption": "AI 部署与定制 的界面示意。" } ], "text": "AI 部署与定制 介绍智巢 AI 私有化部署、GPU 算力、专属智能体、行业应用和按需开发。 AI 部署与定制 AI 部署与定制 的界面示意。 私有化部署方式 智巢 AI 私有化可以按数据安全、预算、算力、模型调用和联网搜索要求分为三类。实际项目应以正式实施评估为准。 方式 说明 适用场景 全部私有化 在自建服务器上部署 DeepSeek、千问等约 32B 级模型，模型推理和知识库能力尽量在客户环境内运行 对数据出域限制严格、预算和 GPU 算力充足的客户 向量本地化 在自建服务器部署向量模型和知识库入库运算，问答推理使用公网大模型 API 希望知识库入库过程本地可控，同时接受外部模型推理的客户 向量仅本地存储 自建服务器保存完成向量化后的知识库，模型推理和向量运算使用公网大模型 API 希望降低本地 GPU 成本，并接受外部模型服务的客户 参考服务器配置 部署方式 服务器用途 参考配置 算卡配置 全部私有化 算力服务器 CPU 2 8368Q、256G 内存、960G SSD 2、8TB HDD 2 5880 ADA 48G 4 向量本地化 向量服务器 CPU 2 4310、128G 内存、480G SSD、4TB HDD 2 3090 24G 2 向量仅本地存储 向量服务器 CPU 2 4310、128G 内存、480G SSD、4TB HDD 2 无 外部模型和联网搜索 部分部署方式会使用公网大模型 API、联网搜索 API 或 TokenPlan。可选模型和服务可包括 Minmax、智谱 GLM、DeepSeek 以及腾讯云联网搜索 API 等。费用会随模型、调用量、联网搜索次数和企业使用强度变化，正式费用以商务报价和实施方案为准。 部署形态 智巢 AI 可作为巴别鸟企业网盘的可选模块使用，也可在私有化项目中按企业要求部署。私有化部署通常需要额外 GPU 算力、模型服务、向量检索或知识库索引服务，并需要结合企业的数据安全、网络访问和第三方模型策略设计。 按需开发 巴别鸟可围绕企业行业场景和业务流程开发专属 AI 应用，例如专属智能体、业务数据查询、特定行业问答、文档处理流程、AI 标签和分类规则、第三方系统接入等。 典型交付内容 资料范围确认、知识库设计和智能体角色设计。 模型、向量库、OCR、多模态、第三方数据源等能力配置。 权限联动、审计日志、访问范围和安全策略设计。 智能体嵌入、企业门户集成或第三方网站接入。 测试问答集、效果调优、上线培训和后续维护。 私有化注意事项 私有化智巢 AI 是否完全内网运行、是否调用外部模型、是否使用第三方 API、是否支持离线模型，应在实施方案中明确。涉及敏感数据的客户应优先确认数据流向、日志留存、模型训练边界和权限审计。 权限与使用边界 智巢 AI 的回答、搜索和文件引用应遵循巴别鸟现有权限体系。用户只能获得其账号、部门、项目、分享和文件访问控制范围内的内容。 参与学习、训练、索引或问答的资料应由企业或管理员指定；不应默认把所有文件都作为公开知识源。 对外客服、网站嵌入、第三方数据源、私有化模型和 GPU 算力属于可选部署或定制能力，应以实际授权、实施方案和企业配置为准。 当 AI 回答涉及合同、财务、医疗、法律、工程安全等高风险内容时，应把 AI 输出作为辅助信息，由专业人员复核。 相关资料 权限体系 安全与审计 FAQ：部署、AI 与技术问题 公开介绍：" }, { "lang": "zh", "slug": "automation-overview", "title": "自动化任务", "description": "自动化任务总览、权限驱动、多任务串联和执行权重。", "category": "产品功能介绍", "top_category": "使用指南", "keywords": [ "自动化", "自动化任务", "工作流" ], "url": "zh/automation-overview.html", "source": "content/zh/automation-overview.md", "summary": "自动化任务 自动化任务总览、权限驱动、多任务串联和执行权重。 自动化任务 自动化任务可从文件夹任务入口或自动化任务列表进入配置。 面对日益增长的数字资产，传统的人工文件管理模式已难以满足高效流转的需求。巴别鸟推出的 “自动化任务”引擎，旨在将繁琐、重复的文件处理动作交由系统后台自动执行。通过建立“自组织、自规范”的智能流转体系，大幅降低人工干预成本，让团队将精力聚焦于核心业务创造。 自动化任务包含在标准版中，用户无需另行购买。 核心运作机制： 灵活的权限驱动： 依托平台极细颗粒度的权限管理体系，凡具备目标网盘或文件夹相应权限的用户，均可按需自主配置、开启或关闭特定的自动化任务。 多任务流串联 (Workflow)： 自动化任务并非孤立运行，支持多规则自由组合形成工作流。例如：文件上传后，系统可先触发“自动重命名”规范文件名称，随后立即触发“自动整理”将其归档至相关目录，实现多步骤一气呵成。 持续扩展的能力矩阵： 自动化引擎具备高度的扩展性。除了现有的基础功能外，平台将持续接入更多的自动化处理节点，以满足日益复杂的业务场景。 当前已支持的核心任务（包括但不限于）： 自动重命名： 按预设规则（如关键字替换、大小写转换）统一标准化命名。 自动整理与清理： 依据触发条件自动分类归档文件，或按策略定期清理空间。 自动转 PDF 与签章： 自动为源文件生成 PDF 副本，或在云端加盖企业签章。 批量创建文件夹： 通过导入数据模板（如 Excel）一键生成标准业务目录树。 多任务协同与执行流转权重 在复杂的业务场景中，一个文件夹往往会叠加配置多项自动化任务。为保障数据处理的逻辑严密性与安全性", "headings": [ { "level": 1, "title": "自动化任务", "id": "section" }, { "level": 3, "title": "多任务协同与执行流转权重", "id": "section-2" } ], "images": [ { "src": "../assets/images/automation-list.webp", "alt": "自动化任务", "caption": "自动化任务可从文件夹任务入口或自动化任务列表进入配置。" } ], "text": "自动化任务 自动化任务总览、权限驱动、多任务串联和执行权重。 自动化任务 自动化任务可从文件夹任务入口或自动化任务列表进入配置。 面对日益增长的数字资产，传统的人工文件管理模式已难以满足高效流转的需求。巴别鸟推出的 “自动化任务”引擎，旨在将繁琐、重复的文件处理动作交由系统后台自动执行。通过建立“自组织、自规范”的智能流转体系，大幅降低人工干预成本，让团队将精力聚焦于核心业务创造。 自动化任务包含在标准版中，用户无需另行购买。 核心运作机制： 灵活的权限驱动： 依托平台极细颗粒度的权限管理体系，凡具备目标网盘或文件夹相应权限的用户，均可按需自主配置、开启或关闭特定的自动化任务。 多任务流串联 (Workflow)： 自动化任务并非孤立运行，支持多规则自由组合形成工作流。例如：文件上传后，系统可先触发“自动重命名”规范文件名称，随后立即触发“自动整理”将其归档至相关目录，实现多步骤一气呵成。 持续扩展的能力矩阵： 自动化引擎具备高度的扩展性。除了现有的基础功能外，平台将持续接入更多的自动化处理节点，以满足日益复杂的业务场景。 当前已支持的核心任务（包括但不限于）： 自动重命名： 按预设规则（如关键字替换、大小写转换）统一标准化命名。 自动整理与清理： 依据触发条件自动分类归档文件，或按策略定期清理空间。 自动转 PDF 与签章： 自动为源文件生成 PDF 副本，或在云端加盖企业签章。 批量创建文件夹： 通过导入数据模板（如 Excel）一键生成标准业务目录树。 多任务协同与执行流转权重 在复杂的业务场景中，一个文件夹往往会叠加配置多项自动化任务。为保障数据处理的逻辑严密性与安全性，系统底层预设了严格的自动化处理先后顺序 。 具体执行权重（数值越高越优先执行）规范如下： 自动清理文件夹（权重 10）： 系统最高优先级。如有符合条件的清理任务将率先执行，以避免对即将被废弃的无效数据投入后续算力 。 自动解压缩（权重 9）： 优先将打包资产释放，以便进入后续流转 。 自动更名（权重 8）： 在文件进入分类归档前，优先完成命名的标准化统一 。 自动格式转化类（权重 7）： 优先完成如转存 PDF、图片或音视频格式的转换任务 。 自动整理 / 排序（权重 6）： 作为流转的末端节点执行 。这意味着文件在被移动和分类前，均已完成了清洗、重命名与格式转换等核心前置标准化操作。" }, { "lang": "zh", "slug": "automation-clean", "title": "自动清理文件", "description": "按规则清理临时文件、过程文件和短期流转素材。", "category": "产品功能介绍", "top_category": "使用指南", "keywords": [ "自动化", "自动清理文件", "工作流" ], "url": "zh/automation-clean.html", "source": "content/zh/automation-clean.md", "summary": "自动清理文件 按规则清理临时文件、过程文件和短期流转素材。 自动清理文件 自动化任务可从文件夹任务入口或自动化任务列表进入配置。 功能概述 在日常的跨部门协作或项目周期管理中，企业网盘内往往会不可避免地产生大量的临时数据、过程文件或短期流转素材。 “自动清理文件” 功能旨在为企业提供自动化的存储空间优化与目录瘦身方案。通过该功能，系统能够按照用户设定的特定规则，自动删除指定文件夹中的冗余文件，长效保持项目目录的整洁度并释放高价值的存储资源。 核心运作与配置规则 本模块通过严密的逻辑规则引擎执行文件的清理动作，确保数据处理的精准与高效： 目标目录锁定： 任务配置需明确指定应用该规则的目标文件夹。用户可选择将规则仅应用于新进入该文件夹的文件，或同时溯源应用于目录内已存在的历史文件。 多维规则触发： 支持基于特定规则对文件进行精准筛选与剔除。常见的判定规则可涵盖文件类型（如特定后缀的临时文件）、生命周期（如文件进入目录超过指定天数）等维度，实现高度定制化的清理策略。 工作流协同： 作为完整自动化流转的末端环节，自动清理可与其他任务无缝衔接。例如，在“自动转 PDF”任务完成后，系统可随即触发“自动清理”规则，将原始草稿文件进行统一清理，仅保留标准化定稿。 权限与数据安全控制 鉴于清理任务涉及文件删除这一敏感操作，该功能深度依托巴别鸟的极细颗粒度权限管理体系： 配置权限： 仅拥有该文件夹相应高级权限（如管理、删除权限）的协作成员，方可新建或修改自动清理任务，从源头杜绝越权操作造成的数据流失。 无感且安全的执行： 后台静默执行清理任务，减少对用户前端操作的干扰，同时严格遵循企业既定的数据", "headings": [ { "level": 1, "title": "自动清理文件", "id": "section" }, { "level": 3, "title": "功能概述", "id": "section-2" }, { "level": 3, "title": "核心运作与配置规则", "id": "section-3" }, { "level": 3, "title": "权限与数据安全控制", "id": "section-4" }, { "level": 3, "title": "典型业务应用场景", "id": "section-5" } ], "images": [ { "src": "../assets/images/automation-create.webp", "alt": "自动清理文件", "caption": "自动化任务可从文件夹任务入口或自动化任务列表进入配置。" } ], "text": "自动清理文件 按规则清理临时文件、过程文件和短期流转素材。 自动清理文件 自动化任务可从文件夹任务入口或自动化任务列表进入配置。 功能概述 在日常的跨部门协作或项目周期管理中，企业网盘内往往会不可避免地产生大量的临时数据、过程文件或短期流转素材。 “自动清理文件” 功能旨在为企业提供自动化的存储空间优化与目录瘦身方案。通过该功能，系统能够按照用户设定的特定规则，自动删除指定文件夹中的冗余文件，长效保持项目目录的整洁度并释放高价值的存储资源。 核心运作与配置规则 本模块通过严密的逻辑规则引擎执行文件的清理动作，确保数据处理的精准与高效： 目标目录锁定： 任务配置需明确指定应用该规则的目标文件夹。用户可选择将规则仅应用于新进入该文件夹的文件，或同时溯源应用于目录内已存在的历史文件。 多维规则触发： 支持基于特定规则对文件进行精准筛选与剔除。常见的判定规则可涵盖文件类型（如特定后缀的临时文件）、生命周期（如文件进入目录超过指定天数）等维度，实现高度定制化的清理策略。 工作流协同： 作为完整自动化流转的末端环节，自动清理可与其他任务无缝衔接。例如，在“自动转 PDF”任务完成后，系统可随即触发“自动清理”规则，将原始草稿文件进行统一清理，仅保留标准化定稿。 权限与数据安全控制 鉴于清理任务涉及文件删除这一敏感操作，该功能深度依托巴别鸟的极细颗粒度权限管理体系： 配置权限： 仅拥有该文件夹相应高级权限（如管理、删除权限）的协作成员，方可新建或修改自动清理任务，从源头杜绝越权操作造成的数据流失。 无感且安全的执行： 后台静默执行清理任务，减少对用户前端操作的干扰，同时严格遵循企业既定的数据合规与回收站保留策略，确保数据资产的绝对安全。 典型业务应用场景 设计与研发类项目： 在建筑设计或科研管理中，工作软件常会自动生成大量的备份或缓存文件（如 .bak 或临时渲染文件）。通过配置自动清理任务，可设定定期自动识别并删除特定后缀的无用文件，保持核心图纸与文献目录的纯净。 公共资料交换区： 针对企业内部设置的“临时中转站”或“临时分享区”，可配置按时间维度（如“保留 7 天后自动清理”）的自动清理任务，实现公共空间的自组织与自净化，降低运维管理成本。" }, { "lang": "zh", "slug": "automation-rename", "title": "自动重命名", "description": "按变量、元数据、编号和文本规则自动标准化文件名。", "category": "产品功能介绍", "top_category": "使用指南", "keywords": [ "自动化", "自动重命名", "工作流" ], "url": "zh/automation-rename.html", "source": "content/zh/automation-rename.md", "summary": "自动重命名 按变量、元数据、编号和文本规则自动标准化文件名。 自动重命名 自动化任务可从文件夹任务入口或自动化任务列表进入配置。 功能概述 在多方协作、多频次资料收集的业务场景中，由于操作人员习惯差异，文件命名往往缺乏统一规范，给后续的检索、归档与审计带来极大困扰。 “自动重命名” 功能允许系统对上传至指定文件夹的文件，按照高度定制化的预设规则进行自动化的名称重构 。该机制有效杜绝了因人为因素导致的命名混乱，确保企业数据资产入库即达标。 适用范围与权限控制 权限驱动： 该功能的启用严格依托于用户的操作权限。只要用户对目标文件夹（涵盖个人、部门、项目或素材库等各类文件夹）拥有“上传”及“重命名”权限，即可为其配置自动重命名任务 。 溯源处理： 规则不仅作用于新上传的文件，用户还可选择将其溯源应用于目标目录及其所有子文件夹中已存在的历史文件 。为保障系统性能与执行稳定性，批量溯源重命名的单次处理上限为 5000 个文件 。 核心规则引擎与配置维度 巴别鸟提供了一个高度灵活的可视化规则拼接引擎。用户可添加多个命名规则，并通过拖拽的方式对规则进行自由排序 。配置界面全程提供实时变化的“示例文件名”，帮助用户直观预览重命名规则的叠加结果 。 规则引擎支持以下多维度的命名元素： 标准属性变量： 支持提取并插入系统级变量，包括文件上传者、文件负责人、上级文件夹名称以及上传时间 。 多媒体元数据 (Metadata)： 针对图像等特定格式文件，系统可深度解析并提取其底层元数据作为命名依据，如拍摄日期、相机制造商/型号、镜头型号、尺寸以及 DPI/DPCM 等参数 。 自定义文本与连续编号： 用", "headings": [ { "level": 1, "title": "自动重命名", "id": "section" }, { "level": 3, "title": "功能概述", "id": "section-2" }, { "level": 3, "title": "适用范围与权限控制", "id": "section-3" }, { "level": 3, "title": "核心规则引擎与配置维度", "id": "section-4" }, { "level": 3, "title": "原始名称的精细化修剪与防冲突机制", "id": "section-5" }, { "level": 3, "title": "全局格式化输出控制", "id": "section-6" } ], "images": [ { "src": "../assets/images/automation-create.webp", "alt": "自动重命名", "caption": "自动化任务可从文件夹任务入口或自动化任务列表进入配置。" } ], "text": "自动重命名 按变量、元数据、编号和文本规则自动标准化文件名。 自动重命名 自动化任务可从文件夹任务入口或自动化任务列表进入配置。 功能概述 在多方协作、多频次资料收集的业务场景中，由于操作人员习惯差异，文件命名往往缺乏统一规范，给后续的检索、归档与审计带来极大困扰。 “自动重命名” 功能允许系统对上传至指定文件夹的文件，按照高度定制化的预设规则进行自动化的名称重构 。该机制有效杜绝了因人为因素导致的命名混乱，确保企业数据资产入库即达标。 适用范围与权限控制 权限驱动： 该功能的启用严格依托于用户的操作权限。只要用户对目标文件夹（涵盖个人、部门、项目或素材库等各类文件夹）拥有“上传”及“重命名”权限，即可为其配置自动重命名任务 。 溯源处理： 规则不仅作用于新上传的文件，用户还可选择将其溯源应用于目标目录及其所有子文件夹中已存在的历史文件 。为保障系统性能与执行稳定性，批量溯源重命名的单次处理上限为 5000 个文件 。 核心规则引擎与配置维度 巴别鸟提供了一个高度灵活的可视化规则拼接引擎。用户可添加多个命名规则，并通过拖拽的方式对规则进行自由排序 。配置界面全程提供实时变化的“示例文件名”，帮助用户直观预览重命名规则的叠加结果 。 规则引擎支持以下多维度的命名元素： 标准属性变量： 支持提取并插入系统级变量，包括文件上传者、文件负责人、上级文件夹名称以及上传时间 。 多媒体元数据 (Metadata)： 针对图像等特定格式文件，系统可深度解析并提取其底层元数据作为命名依据，如拍摄日期、相机制造商/型号、镜头型号、尺寸以及 DPI/DPCM 等参数 。 自定义文本与连续编号： 用户可自由插入自定义文本内容 。在编号机制上，与传统的单次批量重命名不同，自动重命名具备状态记忆（延续性）。系统会自动读取目标列表中最后一个符合规则的编号，确保跨批次、跨时段上传的文件能够实现序号的无缝延续 。用户可精确设定编号的起始值、增量值及具体位数 。 原始名称的精细化修剪与防冲突机制 除了添加新前/后缀，系统同样支持对文件原有的名称进行深度结构化清洗： 名称修剪与替换： 可对原始文件名执行“替换特定内容”、“删除指定内容”操作 。此外，还提供一键“删除字符”功能，精准剔除文件名中的冗余空格、数字、引号、破折号及下划线 。 强制防冲突保护： 若用户在规则中选择完全删除“原始文件名”（即上传时不保留原名），为避免同名文件相互覆盖的风险，系统会强制要求并在规则链中自动追加一项“编号”规则 。 日期逻辑互斥： 在调用日期类变量时，用户可勾选“替换在文件名中检测到的日期” 。为防止逻辑冲突，在单一重命名任务中，该替换指令仅允许被某一时间变量（如“上传时间”或“拍摄时间”）勾选一次 。 全局格式化输出控制 在完成规则变量的拼接后，系统支持在输出端进行统一的格式化规范： 大小写标准化： 支持一键将拼装后的文件名转换为首字母大写、首字母小写、全部大写或全部小写，满足不同企业的视觉规范 。 字词分隔统一： 支持在各个命名规则模块之间统一插入标准化的分隔符（如空格、下划线或破折号），进一步提升文件名的机读与人读体验 。" }, { "lang": "zh", "slug": "automation-pdf", "title": "自动转 PDF", "description": "自动生成标准 PDF 副本，支持文档、图片、工程图纸等格式。", "category": "产品功能介绍", "top_category": "使用指南", "keywords": [ "自动化", "自动转 PDF", "工作流" ], "url": "zh/automation-pdf.html", "source": "content/zh/automation-pdf.md", "summary": "自动转 PDF 自动生成标准 PDF 副本，支持文档、图片、工程图纸等格式。 自动转 PDF 自动化任务可从文件夹任务入口或自动化任务列表进入配置。 功能概述 在跨企业协作、外部资料分发以及项目定稿归档等业务环节中，PDF 格式因其跨设备显示的一致性与防篡改特性，成为了标准的文档交换媒介。巴别鸟的“自动转 PDF”功能，旨在建立一个自动化的文件格式标准化通道。配置该任务后，当文件被添加到选定的目标目录，系统将在后台静默触发转换引擎，将其自动转换为标准的 PDF 文件 。该能力大幅消除了人工逐一导出 PDF 的低效劳动，确保了数据对外输出与对内归档的规范性。 执行逻辑与边界条件 为保障平台底层计算资源的高效运转以及企业数据流转的安全可控，自动转换任务设定了以下执行逻辑与边界限制： 作用域与溯源处理： 该任务可向下覆盖，支持勾选应用于目标目录及其所有子文件夹中的文件 。此外，规则同样支持向历史数据溯源，可应用于目录内的现有文件，但为保障执行稳定性，单次溯源处理的文件数量被严格限制在 5000 个以内 。 系统性能保护机制： 为避免超大源文件在转换过程中长时间占用算力并导致任务队列阻塞，系统内置了文件体积阈值，即超过 30MB 的大体积文件将不会触发自动转换机制 。 存储空间自动释放： 针对“仅需保留定稿 PDF”的特定业务场景，用户可在任务配置界面勾选“转换成功后删除原文件”选项 。开启该策略后，系统将在确认 PDF 副本生成无误的前提下自动清理原始文件，从而大幅度优化网盘存储空间的利用率 。 广泛的格式兼容矩阵 巴别鸟自动转换引擎具备强大的多格式解析能力，支持将 32 种不同行业", "headings": [ { "level": 1, "title": "自动转 PDF", "id": "pdf" }, { "level": 3, "title": "功能概述", "id": "section" }, { "level": 3, "title": "执行逻辑与边界条件", "id": "section-2" }, { "level": 3, "title": "广泛的格式兼容矩阵", "id": "section-3" } ], "images": [ { "src": "../assets/images/automation-create.webp", "alt": "自动转 PDF", "caption": "自动化任务可从文件夹任务入口或自动化任务列表进入配置。" } ], "text": "自动转 PDF 自动生成标准 PDF 副本，支持文档、图片、工程图纸等格式。 自动转 PDF 自动化任务可从文件夹任务入口或自动化任务列表进入配置。 功能概述 在跨企业协作、外部资料分发以及项目定稿归档等业务环节中，PDF 格式因其跨设备显示的一致性与防篡改特性，成为了标准的文档交换媒介。巴别鸟的“自动转 PDF”功能，旨在建立一个自动化的文件格式标准化通道。配置该任务后，当文件被添加到选定的目标目录，系统将在后台静默触发转换引擎，将其自动转换为标准的 PDF 文件 。该能力大幅消除了人工逐一导出 PDF 的低效劳动，确保了数据对外输出与对内归档的规范性。 执行逻辑与边界条件 为保障平台底层计算资源的高效运转以及企业数据流转的安全可控，自动转换任务设定了以下执行逻辑与边界限制： 作用域与溯源处理： 该任务可向下覆盖，支持勾选应用于目标目录及其所有子文件夹中的文件 。此外，规则同样支持向历史数据溯源，可应用于目录内的现有文件，但为保障执行稳定性，单次溯源处理的文件数量被严格限制在 5000 个以内 。 系统性能保护机制： 为避免超大源文件在转换过程中长时间占用算力并导致任务队列阻塞，系统内置了文件体积阈值，即超过 30MB 的大体积文件将不会触发自动转换机制 。 存储空间自动释放： 针对“仅需保留定稿 PDF”的特定业务场景，用户可在任务配置界面勾选“转换成功后删除原文件”选项 。开启该策略后，系统将在确认 PDF 副本生成无误的前提下自动清理原始文件，从而大幅度优化网盘存储空间的利用率 。 广泛的格式兼容矩阵 巴别鸟自动转换引擎具备强大的多格式解析能力，支持将 32 种不同行业的主流业务文件自动化转储为 PDF 。用户可选择针对“所有支持的文件”执行转换，也可通过下拉菜单按类别精准勾选所需转换的扩展名 。具体支持的格式矩阵如下： 文档排版类： 全面兼容主流办公与出版软件产生的源文件，包括 doc、docx、ppt、pptx、wps、epub、dpt、indd、rtf、docm 以及 pptm 。 图片与影像类： 支持主流位图、数字底片及医疗影像格式的渲染转换，涵盖 jpg、bmp、jpeg、jpg2、png、psd、tif、tiff、raw、cr2、dcm 以及 heic 。 图形与工程图纸类： 深度适配设计与建筑工程领域的矢量及 CAD 图纸转换，支持的格式包含 ai、svg、eps、dwg、dwt 以及 dxf 。" }, { "lang": "zh", "slug": "automation-organize", "title": "自动整理文件", "description": "按时间、关键字、格式等规则自动分类和移动文件。", "category": "产品功能介绍", "top_category": "使用指南", "keywords": [ "自动化", "自动整理文件", "工作流" ], "url": "zh/automation-organize.html", "source": "content/zh/automation-organize.md", "summary": "自动整理文件 按时间、关键字、格式等规则自动分类和移动文件。 自动整理文件 自动化任务可从文件夹任务入口或自动化任务列表进入配置。 功能概述 随着平台内协作数据的沉淀，如何保持底层“任意文件夹同步”架构与权限管控目录的整洁，成为了企业数字资产管理的关键。 “自动整理文件” 功能允许系统按预置的时间周期或内容特征，将文件自动分类并路由至相应的目标目录。该功能确保了海量文件在流转过程中的高度结构化，避免了人工归档的滞后性与错漏。 灵活的触发机制与作用域 用户可通过文件夹右键菜单中的“任务”选项 ，或左侧的自动化任务列表面板进入配置 。配置涵盖以下触发与作用规则： 事件驱动（默认）： 当文件被上传或者移动到指定的触发文件夹时，系统即刻响应并开始整理动作 。 周期驱动： 适用于集中式的数据归档场景，系统可按固定的周期（例如设定为每天 23:00）统一执行文件整理 。 历史溯源： 规则既可应用于新增文件及所有子文件夹，也可勾选“应用于现有文件”对历史存量数据进行批量溯源整理。为保障系统平稳，溯源处理单次不得超过 5000 个文件 。 核心智能整理规则引擎 系统提供三种高度自定义的分类规则，满足不同维度的数据归档需求： 1. 基于时间维度的结构化归档（按月 / 按年分类） 系统可按文件添加到网盘的对应年份或月份自动创建对应的子文件夹（例如“2025”、“2025 10”）并将相关文件移入 。 执行按年或按月分类时相同 ，系统具备按需建档的智能性，如果特定周期内（如某个月）没有产生文件，则系统不会冗余创建该月的空文件夹 。 2. 基于内容的智能路由（按关键字分类） 根据文件名中包含的特定关键", "headings": [ { "level": 1, "title": "自动整理文件", "id": "section" }, { "level": 3, "title": "功能概述", "id": "section-2" }, { "level": 3, "title": "灵活的触发机制与作用域", "id": "section-3" }, { "level": 3, "title": "核心智能整理规则引擎", "id": "section-4" } ], "images": [ { "src": "../assets/images/automation-create.webp", "alt": "自动整理文件", "caption": "自动化任务可从文件夹任务入口或自动化任务列表进入配置。" } ], "text": "自动整理文件 按时间、关键字、格式等规则自动分类和移动文件。 自动整理文件 自动化任务可从文件夹任务入口或自动化任务列表进入配置。 功能概述 随着平台内协作数据的沉淀，如何保持底层“任意文件夹同步”架构与权限管控目录的整洁，成为了企业数字资产管理的关键。 “自动整理文件” 功能允许系统按预置的时间周期或内容特征，将文件自动分类并路由至相应的目标目录。该功能确保了海量文件在流转过程中的高度结构化，避免了人工归档的滞后性与错漏。 灵活的触发机制与作用域 用户可通过文件夹右键菜单中的“任务”选项 ，或左侧的自动化任务列表面板进入配置 。配置涵盖以下触发与作用规则： 事件驱动（默认）： 当文件被上传或者移动到指定的触发文件夹时，系统即刻响应并开始整理动作 。 周期驱动： 适用于集中式的数据归档场景，系统可按固定的周期（例如设定为每天 23:00）统一执行文件整理 。 历史溯源： 规则既可应用于新增文件及所有子文件夹，也可勾选“应用于现有文件”对历史存量数据进行批量溯源整理。为保障系统平稳，溯源处理单次不得超过 5000 个文件 。 核心智能整理规则引擎 系统提供三种高度自定义的分类规则，满足不同维度的数据归档需求： 1. 基于时间维度的结构化归档（按月 / 按年分类） 系统可按文件添加到网盘的对应年份或月份自动创建对应的子文件夹（例如“2025”、“2025 10”）并将相关文件移入 。 执行按年或按月分类时相同 ，系统具备按需建档的智能性，如果特定周期内（如某个月）没有产生文件，则系统不会冗余创建该月的空文件夹 。 2. 基于内容的智能路由（按关键字分类） 根据文件名中包含的特定关键字，系统将文件自动分发并移动至预设的目标文件夹 。 格式识别： 文件扩展名（如“jpg”）同样可作为关键字配置，实现特定类型素材的定向归集 。 多线并行路由： 用户可通过“添加关键字分类”按钮持续增加多条路由规则 。既支持将包含不同关键字的文件分别分发到不同的目录 ，也支持将多条关键字任务统一指向同一个目标文件夹 。 防重名与优先级控制： 关键字匹配严格按任务设定的先后顺序处理。例如，当文件名为“123ABC定稿.jpg”，若关键字列表第一项规则为“123”，第二项为“定稿”，则该文件将优先匹配“123”的规则并执行移动 。系统内置防重复检测，每个关键字仅允许输入一次，重复输入会触发“请重新输入”的错误拦截 。 同名冲突化解： 在执行文件移动与整理的过程中，如在目标文件夹内遇到重名文件，系统会自动在文件名后附加编号，以确保数据不被意外覆盖 。" }, { "lang": "zh", "slug": "automation-esign", "title": "电子签章", "description": "云端签署、签名/图章资产、PDF 输出和响应式签章界面。", "category": "产品功能介绍", "top_category": "使用指南", "keywords": [ "自动化", "电子签章", "工作流" ], "url": "zh/automation-esign.html", "source": "content/zh/automation-esign.md", "summary": "电子签章 云端签署、签名/图章资产、PDF 输出和响应式签章界面。 电子签章 自动化任务可从文件夹任务入口或自动化任务列表进入配置。 业务场景与功能概述 在企业的合同审批、图纸会签及业务合规流转等关键环节中，具备防篡改属性的数字化签署是打通线上协作闭环的核心节点。传统的跨系统签署往往伴随繁琐的文件下载与格式转换。巴别鸟推出的 “创建签章” 功能，允许用户直接在云端网盘的工作流中对文件进行盖章与签署 。该引擎支持多种主流文件类型直接加载印签，并支持将签署完毕的文件一键导出为标准的 PDF 格式，从源头保障数字资产的安全、合规与不可篡改性 。 签章资产库与个性化配置 系统为用户提供了一个高度集成的数字印签管理控制台，确保电子签章资产的统一沉淀与快速调用： 多元签名采集： 在“签名设置”模块中，用户既可以调用终端进行在线“添加手写签名”，也支持直接“上传签名图片文件”（如含透明通道的 PNG 素材），以满足不同层级的签署合规要求 。 企业图章管理： 在“图章设置”模块，企业用户可按需上传业务专用的电子公章或合规图章图片 。 默认优先级状态： 针对拥有多个印签资产的用户，系统支持一键将其中的特定签名或图章“设置为当前使用”（默认印签） 。在后续的文档预览与流转界面中，系统将优先调用该默认印签，极大提升高频审批场景下的签署效率 。 智能自适应交互与沉浸式引导体系 为兼顾不同硬件终端的显示极限并降低用户的学习门槛，签章配置中心采用了多断点的智能响应式（Responsive）界面架构，并深度嵌入了多语言操作指引： 宽屏工作站模式（窗口宽度 ≥ 1120px）： 当用户在桌面级宽屏设备上操作时", "headings": [ { "level": 1, "title": "电子签章", "id": "section" }, { "level": 3, "title": "业务场景与功能概述", "id": "section-2" }, { "level": 3, "title": "签章资产库与个性化配置", "id": "section-3" }, { "level": 3, "title": "智能自适应交互与沉浸式引导体系", "id": "section-4" } ], "images": [ { "src": "../assets/images/automation-create.webp", "alt": "电子签章", "caption": "自动化任务可从文件夹任务入口或自动化任务列表进入配置。" } ], "text": "电子签章 云端签署、签名/图章资产、PDF 输出和响应式签章界面。 电子签章 自动化任务可从文件夹任务入口或自动化任务列表进入配置。 业务场景与功能概述 在企业的合同审批、图纸会签及业务合规流转等关键环节中，具备防篡改属性的数字化签署是打通线上协作闭环的核心节点。传统的跨系统签署往往伴随繁琐的文件下载与格式转换。巴别鸟推出的 “创建签章” 功能，允许用户直接在云端网盘的工作流中对文件进行盖章与签署 。该引擎支持多种主流文件类型直接加载印签，并支持将签署完毕的文件一键导出为标准的 PDF 格式，从源头保障数字资产的安全、合规与不可篡改性 。 签章资产库与个性化配置 系统为用户提供了一个高度集成的数字印签管理控制台，确保电子签章资产的统一沉淀与快速调用： 多元签名采集： 在“签名设置”模块中，用户既可以调用终端进行在线“添加手写签名”，也支持直接“上传签名图片文件”（如含透明通道的 PNG 素材），以满足不同层级的签署合规要求 。 企业图章管理： 在“图章设置”模块，企业用户可按需上传业务专用的电子公章或合规图章图片 。 默认优先级状态： 针对拥有多个印签资产的用户，系统支持一键将其中的特定签名或图章“设置为当前使用”（默认印签） 。在后续的文档预览与流转界面中，系统将优先调用该默认印签，极大提升高频审批场景下的签署效率 。 智能自适应交互与沉浸式引导体系 为兼顾不同硬件终端的显示极限并降低用户的学习门槛，签章配置中心采用了多断点的智能响应式（Responsive）界面架构，并深度嵌入了多语言操作指引： 宽屏工作站模式（窗口宽度 ≥ 1120px）： 当用户在桌面级宽屏设备上操作时，系统不仅在左侧保留标准的签章配置面板，还会在右侧自动展开独立的视频教学区。该区域会自动加载并无感循环播放签章使用教程（播放完毕停顿 3 秒后重播），为用户提供“边学边配”的沉浸式体验 。 紧凑聚焦模式（窗口宽度 ＜ 1100px）： 当处于较窄的屏幕或移动端窗口时，系统会智能折叠右侧的视频播放区，以最大化保障核心签署设置区的视觉焦点 。同时，系统在界面底部提供“如何使用签章？”入口，用户点击后可唤起全屏教程播放 。 国际化双语支持： 考虑到跨国企业的协作需求，系统内置了本地化的教学视频库。除中文语言环境播放专属中文教程外，其他所有多语言版本均默认匹配并播放标准英文教程，保障全球业务团队的无障碍落地 。" }, { "lang": "zh", "slug": "automation-batch-folders", "title": "批量创建文件夹", "description": "通过 Excel、CSV、TXT 批量生成目录树和项目文件夹。", "category": "产品功能介绍", "top_category": "使用指南", "keywords": [ "自动化", "批量创建文件夹", "工作流" ], "url": "zh/automation-batch-folders.html", "source": "content/zh/automation-batch-folders.md", "summary": "批量创建文件夹 通过 Excel、CSV、TXT 批量生成目录树和项目文件夹。 批量创建文件夹 自动化任务可从文件夹任务入口或自动化任务列表进入配置。 功能概述与业务价值 在多项目并发或企业部门架构调整的业务场景中，由人工逐一建立复杂的标准目录树不仅耗费大量操作时间，且极易因人为疏漏导致目录层级错乱或命名不规范。巴别鸟提供的 “批量创建文件夹” 功能，允许用户通过外部结构化数据（如 Excel、CSV、TXT 文本）直接驱动云端目录的生成 。该功能可将标准化的业务目录模板瞬间转化为可落地的网盘文件夹阵列，极大提升了大型项目启动阶段的初始化建档效率。 标准目录阵列的大规模生成 该模块具备强大的数据解析能力与人工容错干预机制： 高并发支持： 系统支持通过导入 xls、xlsx、csv 或 txt 格式的文件，按换行符规则快速读取目录清单，单次批处理任务的上限高达 5000 行，满足绝大多数企业级数据结构的生成需求 。 可视化预审与动态干预： 在正式执行批量创建前，系统会完成数据解析并在界面中直观渲染出即将生成的文件夹列表与层级关系 。在此预览环节中，用户可直接通过鼠标右键或悬浮菜单，对特定的预设目录执行“创建子文件夹”、“重命名”或“删除”等即时修改动作 。这一“先审后建”的机制，确保了最终落地的目录树与业务需求绝对对齐。 项目级文件夹与权限的“一键部署” 当目标路径设定为部门文件夹或个人文件夹的根目录时，系统支持创建更为高阶的 “项目文件夹” 。该模式深度结合了巴别鸟的底层权限管理体系，实现了目录构建与成员权限配置的同步落地： 专属标准模板： 批量生成项目文件夹需下载并使用系统专", "headings": [ { "level": 1, "title": "批量创建文件夹", "id": "section" }, { "level": 3, "title": "功能概述与业务价值", "id": "section-2" }, { "level": 3, "title": "标准目录阵列的大规模生成", "id": "section-3" }, { "level": 3, "title": "项目级文件夹与权限的“一键部署”", "id": "section-4" }, { "level": 3, "title": "实时状态监控与智能容错机制", "id": "section-5" } ], "images": [ { "src": "../assets/images/automation-create.webp", "alt": "批量创建文件夹", "caption": "自动化任务可从文件夹任务入口或自动化任务列表进入配置。" } ], "text": "批量创建文件夹 通过 Excel、CSV、TXT 批量生成目录树和项目文件夹。 批量创建文件夹 自动化任务可从文件夹任务入口或自动化任务列表进入配置。 功能概述与业务价值 在多项目并发或企业部门架构调整的业务场景中，由人工逐一建立复杂的标准目录树不仅耗费大量操作时间，且极易因人为疏漏导致目录层级错乱或命名不规范。巴别鸟提供的 “批量创建文件夹” 功能，允许用户通过外部结构化数据（如 Excel、CSV、TXT 文本）直接驱动云端目录的生成 。该功能可将标准化的业务目录模板瞬间转化为可落地的网盘文件夹阵列，极大提升了大型项目启动阶段的初始化建档效率。 标准目录阵列的大规模生成 该模块具备强大的数据解析能力与人工容错干预机制： 高并发支持： 系统支持通过导入 xls、xlsx、csv 或 txt 格式的文件，按换行符规则快速读取目录清单，单次批处理任务的上限高达 5000 行，满足绝大多数企业级数据结构的生成需求 。 可视化预审与动态干预： 在正式执行批量创建前，系统会完成数据解析并在界面中直观渲染出即将生成的文件夹列表与层级关系 。在此预览环节中，用户可直接通过鼠标右键或悬浮菜单，对特定的预设目录执行“创建子文件夹”、“重命名”或“删除”等即时修改动作 。这一“先审后建”的机制，确保了最终落地的目录树与业务需求绝对对齐。 项目级文件夹与权限的“一键部署” 当目标路径设定为部门文件夹或个人文件夹的根目录时，系统支持创建更为高阶的 “项目文件夹” 。该模式深度结合了巴别鸟的底层权限管理体系，实现了目录构建与成员权限配置的同步落地： 专属标准模板： 批量生成项目文件夹需下载并使用系统专属模板导入数据 。若上传的非标文件不符合解析格式，系统将严格拦截并提示重新上传 。 项目角色与权限预设： 模板不仅规范了“项目文件夹名字”，还支持直接关联账号系统预设“项目负责人”与“项目成员” 。 负责人指派： 填写的负责人 ID（支持手机号、邮箱或特定的工号格式）必须为已注册的企业成员；若该字段留空或填写的身份无法校验，系统将遵循安全保底原则，默认将当前创建任务的操作者设为项目负责人 。 成员自动化邀请与赋权： 用户可在模板中通过逗号分隔批量录入多位项目成员 。项目目录生成后，系统将自动向这些成员发送邀请通知，并为其赋予基础的“上传及下载”默认权限 ，彻底免除了建档后繁琐的逐一授权操作。 实时状态监控与智能容错机制 在执行大规模创建任务时，系统后台会以队列形式稳健处理，并在前端提供全方位的进程监控与异常修复闭环： 全局进度追踪： 创建过程中，列表节点会实时更新其执行状态（从代表正在执行的转圈动画，平滑过渡至代表成功的确认勾选状态） 。任务全局状态亦会从“创建中”明确流转至“完成” 。 精准异常归因与重试： 全部任务执行完毕后，系统顶部会输出清晰的结果汇总（如“共创建了 XXX 个文件夹，失败 X 个”） 。用户可一键查阅“创建失败文件列表” 。系统会将失败原因精确归类为“包含文件名不允许字符”或“已有同名文件夹”等系统级冲突 。针对这些异常条目，用户不仅可以查明原因，还能直接在界面上点击绿色的“重试”按钮触发二次创建 ，大幅降低了批量运维的阻力。" }, { "lang": "zh", "slug": "doc-control-project", "title": "文控项目", "description": "介绍工程设计行业的文控项目、TRANSMITTAL、发送单、接收方和自动化文控流程。", "category": "产品功能介绍", "top_category": "使用指南", "keywords": [ "文控", "DCC", "TRANSMITTAL", "工程设计" ], "url": "zh/doc-control-project.html", "source": "content/zh/doc-control-project.md", "summary": "文控项目 文控项目是巴别鸟的一个行业应用独立模块（需要另行购买）。巴别鸟文控项目解决了工程设计行业中的文控标准的流程管理（DCC）及自动化问题。提高了大量文控人员的工作效率的同时也降低了人为失误的可能。 使用范围 需要严格管理每一次文件发送的行业或企业。每次发送给客户的文件都由特定人员发送（文控人员）每次发送都有发送单据可查，能明确的管理发送内容。通过发送单号可以查询到每次发送文件给接收方的具体信息和文件。同时对接收方是否收件，对发送过去的内容是否驳回都可管理查询。并且发送单可以作为凭据。 需要解决的问题 目前很多企业的文控流程基本是靠手动，文件存储于EDMS系统或文控人员电脑本地。依靠文件夹分类来管理文档，每次发送文件手动建立一个文件夹，按文件名规范命名文件夹，文件通过邮件发送后把发送的文件放入文件夹并附上本次发送的TRANSMITTAL（文件发送单）。 每次发送都会产生一个文件夹及相应的TRANSMITTAL。这些工作人工操作相当繁琐，除了整理文件，每次还需要手动填写文件发送单，手动按规则编写发送单编号，日后还要手动核对，效率极低。 巴别鸟解决方案 可新建新的文控项目类型。这意味着不同的项目可以设定不同的TRANSMITTAL（发送单）规则生成不同的发送单和发送单号。不同项目也可以管理不同的收件人（收件企业） 可设定每个项目的文件接收方，统一管理文件接收方。 文控项目中的文档支持发送功能，发送功能支持多选。选择文件或文件夹发送后，收件人可以通过邮箱收到所发送文件的下载link和TRANSMITTAL（发送单）。并且通过下载link下载到的文件是发送时的版本。 每次发送的文件", "headings": [ { "level": 1, "title": "文控项目", "id": "section" }, { "level": 3, "title": "使用范围", "id": "section-2" }, { "level": 3, "title": "需要解决的问题", "id": "section-3" }, { "level": 3, "title": "巴别鸟解决方案", "id": "section-4" }, { "level": 3, "title": "基本介绍", "id": "section-5" } ], "images": [], "text": "文控项目 文控项目是巴别鸟的一个行业应用独立模块（需要另行购买）。巴别鸟文控项目解决了工程设计行业中的文控标准的流程管理（DCC）及自动化问题。提高了大量文控人员的工作效率的同时也降低了人为失误的可能。 使用范围 需要严格管理每一次文件发送的行业或企业。每次发送给客户的文件都由特定人员发送（文控人员）每次发送都有发送单据可查，能明确的管理发送内容。通过发送单号可以查询到每次发送文件给接收方的具体信息和文件。同时对接收方是否收件，对发送过去的内容是否驳回都可管理查询。并且发送单可以作为凭据。 需要解决的问题 目前很多企业的文控流程基本是靠手动，文件存储于EDMS系统或文控人员电脑本地。依靠文件夹分类来管理文档，每次发送文件手动建立一个文件夹，按文件名规范命名文件夹，文件通过邮件发送后把发送的文件放入文件夹并附上本次发送的TRANSMITTAL（文件发送单）。 每次发送都会产生一个文件夹及相应的TRANSMITTAL。这些工作人工操作相当繁琐，除了整理文件，每次还需要手动填写文件发送单，手动按规则编写发送单编号，日后还要手动核对，效率极低。 巴别鸟解决方案 可新建新的文控项目类型。这意味着不同的项目可以设定不同的TRANSMITTAL（发送单）规则生成不同的发送单和发送单号。不同项目也可以管理不同的收件人（收件企业） 可设定每个项目的文件接收方，统一管理文件接收方。 文控项目中的文档支持发送功能，发送功能支持多选。选择文件或文件夹发送后，收件人可以通过邮箱收到所发送文件的下载link和TRANSMITTAL（发送单）。并且通过下载link下载到的文件是发送时的版本。 每次发送的文件都是文件当前版本，文件升版会形成新的版本号，并在发送单显示。 文件发送后根据预先设定的规则自动生成本次发送的TRANSMITTAL（发送单）和TRANSMITTAL NO.（发送单号） 可以管理及查询所由TRANSMITTAL（发送单），并可导出发送单为PDF。 巴别鸟文控项目使用指引： 基本介绍 巴别鸟文控管理系统是在巴别鸟企业私有云版的基础上增加文控管理模块，以实现文控工作的自动化。 文控管理的方式是以建立“文控项目”的方式来实现。文控项目是针对文控需求特别定制的特殊项目，以项目为单位进行管理。 建立文控项目 登录系统后，在要创建文控项目的部门中点击“新建”——“新建项目” 项目只能建立于根目录（企业文件）或部门根目录下 例：在HQSM文控这个部门下建立一个文控项目 点击新建项目，出现项目类型选择界面 选择“创建文控管理项目” 这时候出现项目初始化选择界面 按照项目的要求填写初始化信息 每项的介绍如下： 项目负责人 管理、转交项目、修改项目权限及基础信息。不可为空。可删除TRANSMITTAL 项目秘书 不可转交项目，其他同项目负责人，可多人，可为空。可删除TRANSMITTAL 文控人员 可以发送文件给接收人。其他权限可配置，可多人，可为空。选择人员后点击右侧权限选择下拉框可以批量修改成员权限（如图）。 其他成员 没有发送文件选项，其他同普通项目普通成员，权限可配置，可为空。 版本号规则 如图，如果前缀填写为HQSM，文件的第一个版本就为 HQSM A ，第二个版本为 HQSM B以此类推 基本信息 基本信息的填写内容将显示于TRANSMITTA头部。 如图：画红圈处就是填写的基本信息。 接收方信息 接收方信息决定了发件时的可选项和所发文件的TRANSMITTA号 收件方名字是指收件方在系统中的称呼，一般填写收件方的企业简称，如 MCC 邮箱支持添加多个，添加多个后，一次发送就可以向多个邮箱地址发送文件及TRANSMITTA ATTN可以任意输入，同时也会显示在TRANSMITTA上 运单号规则其实就是TRANSMITTA号的自动生成规则，不同的收件方可以生成不同的运单号。所以需要在每个收件方处设定不同的运单号规则。 规则自定义界面示意如下： 3栏分别为TRANSMITTAL号的3个组成部分，如果所需的TRANSMITTA号需要更多的编码来组成也可以点击+号来增加更多栏 例： 第一栏选择输入文字，弹出文字输入框，输入 “HQSM ” 第二栏选择编码规则为1 2 3数字顺序 第三栏选择 文字输入、输入“ 2020” 点加号新增一栏，选择a b c字母顺序 第一次发送生成的TRANSMITTAL号即为： HQSM 1 2020a 第二次发送生成的TRANSMITTAL号为：HQSM 2 2020b 选择字母作为编号超过26个后，z号的下一个版本自动变为a1 如果该项目有多个接收方，也可以点击来增加。（项目建立后也可以在项目管理界面中去增删接收方。 这些填写完成后，点击“新增项目”就完成了项目的新建 你可以在创建项目路径的文件列表中看到新建的文控项目，点击即可进入 文控管理项目不同于普通项目，项目首页顶部栏增加了文控管理的按钮 其中“发送单列表”可以查询该项目发出的所有TRANSMITTA，管理项目可以对项目进行管理。 上传文件 点击新建的文控项目，进入项目页面。 直接拖拽想要上传的文件到项目中即可上传文件，当然，你也可以和使用普通文件夹一样使用同步功能进行上传下载。 发送文件 选中要发送的文件（支持多选），然后点击右键，选择“发送文件”会出现文件发送界面 每次最多发送的文件为2000个（包含文件夹）。如项目需要全部文件发送，建议以压缩包形式进行发送。 收件人可以下拉选择项目初始化时填写的收件人及ATTN 抄送可以填写其他任意邮箱地址，也可以留空不填写 选择的提交文件类型也会在生成的TRANSMITTA中显示 文件列表罗列了本次要发送的文件。 系统要发送TRANSMITTAL的文件名构成为 文件编号+描述，如一个文件文件名为 1000+图纸.pdf，发送时显示在TRANSMITTAL的文件编号为“1000”，描述为“图纸”。如果发送的文件的文件名中没有+分割，文件编号就显示文件名，如果发送的文件名为“+图纸.jpg“就不显示文件编号，显示描述为“图纸”。描述可中途更改。 附言将会在收件人接受到的邮件中显示并不会显示在TRANSMITTAL中 填写完成后点击“发送文件”系统会自动生成TRANSMITTAL并作为link附在邮件中发送给客户。 生成TRANSMITTAL 发送成功后系统会弹出提示 点击查看，就能查看本次发送自动生成的TRANSMITTAL 点击导出为PDF就可以把该TRANSMITTAL保存为PDF文件 你也可以在传送单列表（TRANSMITTAL list）中去查看该项目中发送的所有TRANSMITTAL 收件人在邮箱中收到的TRANSMITTAL和该TRANSMITTAL一致。 查看TRANSMITTAL 在项目首页点击发送单列表（TRANSMITTAL list） 打开列表就可以看到及查询本项目的所有发送单。 点击传送单号可查看详情并下载TRANSMITTAL的PDF文件 为接受就是接受方并没有打开已发送的邮件，如对方打开邮件并访问了TRANSMITTAL，接收状态会变为已接收。 查看发送记录 在任意文件上右键点击，可查看该文件的发送记录及其对应的TRANSMITTAL" }, { "lang": "zh", "slug": "developer-api-overview", "title": "开发 API 概览", "description": "介绍企业开发账号、认证方式、API 目录、调用规范和开发者索引。", "category": "API概览", "top_category": "API文档", "keywords": [ "API", "开发者", "OAuth", "JWT", "文件接口" ], "url": "zh/developer-api-overview.html", "source": "content/zh/developer-api-overview.md", "summary": "开发 API 概览 巴别鸟开发 API 用于把企业网盘的认证、文件、分享、组织、消息和登录能力接入第三方业务系统。左侧栏按接口作用分组，组内直接列出可调用端点。 调用总览 企业管理员在私有云企业管理后台创建开发者账号，获得 client id 、 client secret 和 JWT 相关密钥。 OAuth 回调方式使用 /api/authorize.do 获取授权码，再用 /api/token.do 获取 access token 。 JWT 免登录方式使用 /api/authorizeByJWT.do 或 /account/tokenLogin.do ，私有化部署需开启对应配置。 文件访问 API 请求需要在 HTTP Header 中携带 Authorization: Bearer 。 POST、PUT、DELETE 请求通常使用 Content Type: application/json 。 API 分组 分组 主要用途 典型入口 认证 API 开发者账号、OAuth 回调、JWT 免登录、Token 获取和刷新 获取 token 文件 API 文件列表、文件信息、上传下载、版本、移动复制、回收站、素材库分类 获取文件列表 分享 API 分享链接、分享权限、参与人、关注提醒 获取文件的分享 url 企业 API 企业信息、部门、成员、企业日志 获取当前企业信息 消息与登录 API 公告、部门讨论、JWT token 登录、通用状态码 JWT token 登录 单接口页面 每个 API 条目均有独立页面，便于开发者按接口查阅路径、方法、参数和返回信息。 GET 认证接", "headings": [ { "level": 1, "title": "开发 API 概览", "id": "api" }, { "level": 2, "title": "调用总览", "id": "section" }, { "level": 2, "title": "API 分组", "id": "api-2" }, { "level": 2, "title": "单接口页面", "id": "section-2" } ], "images": [], "text": "开发 API 概览 巴别鸟开发 API 用于把企业网盘的认证、文件、分享、组织、消息和登录能力接入第三方业务系统。左侧栏按接口作用分组，组内直接列出可调用端点。 调用总览 企业管理员在私有云企业管理后台创建开发者账号，获得 client id 、 client secret 和 JWT 相关密钥。 OAuth 回调方式使用 /api/authorize.do 获取授权码，再用 /api/token.do 获取 access token 。 JWT 免登录方式使用 /api/authorizeByJWT.do 或 /account/tokenLogin.do ，私有化部署需开启对应配置。 文件访问 API 请求需要在 HTTP Header 中携带 Authorization: Bearer 。 POST、PUT、DELETE 请求通常使用 Content Type: application/json 。 API 分组 分组 主要用途 典型入口 认证 API 开发者账号、OAuth 回调、JWT 免登录、Token 获取和刷新 获取 token 文件 API 文件列表、文件信息、上传下载、版本、移动复制、回收站、素材库分类 获取文件列表 分享 API 分享链接、分享权限、参与人、关注提醒 获取文件的分享 url 企业 API 企业信息、部门、成员、企业日志 获取当前企业信息 消息与登录 API 公告、部门讨论、JWT token 登录、通用状态码 JWT token 登录 单接口页面 每个 API 条目均有独立页面，便于开发者按接口查阅路径、方法、参数和返回信息。 GET 认证接口一（登录回调方式）： /api/authorize.do GET 认证接口二（免登录 JWT token 方式）： /api/authorizeByJWT.do POST 获取 token： /api/token.do POST 刷新 token： /api/refreshToken.do GET 获取文件列表： /nd/api/file/list dir GET 获取文件信息： /nd/api/file/fileinfo POST 创建文件夹： /nd/api/file/create folder GET 预上传文件： /api/file/preUploadFile.do GET 获取下载文件地址： /api/file/getFileDownloadUrl.do GET 获取下载多文件地址： /api/file/downloadMultiFiles.do GET 获取下载文件缩略图地址： /api/file/downloadThumbnail.do POST 修改文件信息： /nd/api/file/update file POST 修改文件名： /nd/api/file/rename POST 删除文件(到回收站）： /nd/api/file/remove file POST 删除文件（从回收站）： /nd/api/file/remove from trash POST 清空回收站： /nd/api/file/empty trash POST 恢复文件（从回收站）： /nd/api/file/restore file GET 获取文件的所有版本信息： /nd/api/file/versions POST 设置文件当前版本： /nd/api/file/version POST 移动文件： /nd/api/file/move POST 拷贝文件： /nd/api/file/copy POST 拷贝文件进度： /nd/api/file/copy progress GET 文件日志： /nd/api/file/file logs POST 设置用户是否有权访问素材库： /nd/api/file/set user access material library POST 创建素材库分类： /nd/api/file/create material class POST 创建子素材库： /nd/api/file/create material folder GET 获取文件的分享 url： /nd/api/share/shareurl GET 获取分享的权限列表： /nd/api/share/share roles GET 获取用户对于单个文件有权设置的分享角色： /nd/api/share/share role forfile POST 创建链接分享： /nd/api/share/open link share POST 关闭链接分享： /nd/api/share/close link share POST 设置链接分享密码： /nd/api/share/set share password POST 邀请人员参与分享： /nd/api/share/invite share GET 获取所有分享参与人： /nd/api/share/share participants POST 设置分享参与人的权限角色： /nd/api/share/set participant role POST 删除分享参与人： /nd/api/file/remove share participant POST 提醒关注： /nd/api/file/focus file POST 移除某人的关注： /nd/api/file/unfocus file GET 获取关注文件的用户列表： /nd/api/file/user focusfile GET 获取可以关注文件的用户列表，并且标记已关注文件的用户： /nd/api/file/user can focusfile GET 获取当前企业信息： /nd/api/enterprise/current GET 获取企业所有部门信息： /nd/api/enterprise/departments POST 创建企业部门： /nd/api/enterprise/create department GET 获取部门角色列表： /nd/api/enterprise/dep role POST 添加部门人员： /nd/api/enterprise/add dep mem POST 删除部门人员： /nd/api/enterprise/remove dep mem GET 获取自己所在部门信息： /nd/api/enterprise/mydeparments GET 获取部门人员： /nd/api/enterprise/departmentmembers POST 添加企业成员： /nd/api/enterprise/add ent mem POST 更新成员信息： /api/updateUserInfo.do GET 获取企业成员信息： /api/getEnterpriseMember.do POST 获取企业所有成员： /nd/api/enterprise/enterprise members POST 获取企业日志： /nd/api/enterprise/enterprise logs POST 发布公告： /nd/api/enterprise/broadcast GET 获取发布的公告： /nd/api/enterprise/broadcast POST 发送部门讨论： /nd/api/file/send dep discussion POST 获取部门讨论： /nd/api/file/dep discussion GET 获取企业日志： /nd/api/enterprise/enterprise logs GET JWT token 登录： /account/tokenLogin.do" }, { "lang": "zh", "slug": "developer-api-auth", "title": "认证与 Token", "description": "认证与 Token 的接口路径、方法、参数和返回字段。", "category": "认证 API", "top_category": "API文档", "keywords": [ "API", "认证与 Token", "开发者" ], "url": "zh/developer-api-auth.html", "source": "content/zh/developer-api-auth.md", "summary": "认证与 Token PDF 第 1 页 企业开发 API V6.6 上海画擎信息科技有限公司 姜大军 PDF 第 2 页 目录 一、 获取企业开发账号 ..............................................................................................................................................................................4 二、 认证 API ............................................................................................................................................................................................. 6 认证接口一（登录回调方式） ................................................................................................................................................................6 认证接口二（免登录方式 – JWT token 方式，在私有云部署中，需要开启 jwt token 的登录方式） .............", "headings": [ { "level": 1, "title": "认证与 Token", "id": "token" }, { "level": 3, "title": "PDF 第 1 页", "id": "pdf-1" }, { "level": 3, "title": "PDF 第 2 页", "id": "pdf-2" }, { "level": 3, "title": "PDF 第 3 页", "id": "pdf-3" }, { "level": 3, "title": "PDF 第 4 页", "id": "pdf-4" }, { "level": 2, "title": "一、 获取企业开发账号", "id": "section" }, { "level": 3, "title": "PDF 第 5 页", "id": "pdf-5" }, { "level": 3, "title": "PDF 第 6 页", "id": "pdf-6" }, { "level": 2, "title": "二、 认证 API", "id": "api" }, { "level": 3, "title": "认证接口一（登录回调方式）", "id": "section-2" }, { "level": 3, "title": "PDF 第 7 页", "id": "pdf-7" }, { "level": 3, "title": "PDF 第 8 页", "id": "pdf-8" }, { "level": 3, "title": "获取 token", "id": "token-2" }, { "level": 3, "title": "刷新 token", "id": "token-3" }, { "level": 2, "title": "三、 文件访问 API", "id": "api-2" }, { "level": 3, "title": "PDF 第 9 页", "id": "pdf-9" }, { "level": 3, "title": "获取文件列表", "id": "section-3" }, { "level": 3, "title": "获取文件信息", "id": "section-5" }, { "level": 3, "title": "PDF 第 10 页", "id": "pdf-10" }, { "level": 3, "title": "创建文件夹", "id": "section-7" }, { "level": 3, "title": "预上传文件", "id": "section-9" }, { "level": 3, "title": "PDF 第 11 页", "id": "pdf-11" }, { "level": 3, "title": "上传文件", "id": "section-12" }, { "level": 3, "title": "PDF 第 12 页", "id": "pdf-12" }, { "level": 3, "title": "获取下载文件地址", "id": "section-14" }, { "level": 3, "title": "获取下载多文件地址", "id": "section-16" }, { "level": 3, "title": "PDF 第 13 页", "id": "pdf-13" }, { "level": 3, "title": "获取下载文件缩略图地址", "id": "section-18" }, { "level": 3, "title": "修改文件信息", "id": "section-20" }, { "level": 3, "title": "修改文件信息", "id": "section-21" }, { "level": 3, "title": "修改文件名", "id": "section-23" }, { "level": 3, "title": "修改文件信息", "id": "section-24" }, { "level": 3, "title": "PDF 第 14 页", "id": "pdf-14" }, { "level": 3, "title": "删除文件(到回收站）", "id": "section-26" }, { "level": 3, "title": "删除文件（从回收站）", "id": "section-28" }, { "level": 3, "title": "清空回收站", "id": "section-30" }, { "level": 3, "title": "恢复文件（从回收站）", "id": "section-32" }, { "level": 3, "title": "PDF 第 15 页", "id": "pdf-15" }, { "level": 3, "title": "获取文件的所有版本信息", "id": "section-34" }, { "level": 3, "title": "设置文件当前版本", "id": "section-36" }, { "level": 3, "title": "移动文件", "id": "section-38" }, { "level": 3, "title": "拷贝文件", "id": "section-40" }, { "level": 3, "title": "PDF 第 16 页", "id": "pdf-16" }, { "level": 3, "title": "拷贝文件进度", "id": "section-42" }, { "level": 3, "title": "文件日志", "id": "section-44" }, { "level": 3, "title": "设置用户是否有权访问素材库", "id": "section-46" }, { "level": 3, "title": "PDF 第 17 页", "id": "pdf-17" }, { "level": 3, "title": "创建素材库分类", "id": "section-48" }, { "level": 3, "title": "创建子素材库", "id": "section-50" }, { "level": 2, "title": "共享文件相关 API", "id": "api-3" }, { "level": 3, "title": "PDF 第 18 页", "id": "pdf-18" }, { "level": 3, "title": "获取文件的分享 url", "id": "url-12" }, { "level": 3, "title": "获取分享的权限列表", "id": "section-53" }, { "level": 3, "title": "获取用户对于单个文件有权设置的分享角色", "id": "section-55" }, { "level": 3, "title": "创建链接分享", "id": "section-57" }, { "level": 3, "title": "PDF 第 19 页", "id": "pdf-19" }, { "level": 3, "title": "关闭链接分享", "id": "section-59" }, { "level": 3, "title": "设置链接分享密码", "id": "section-61" }, { "level": 3, "title": "邀请人员参与分享", "id": "section-63" }, { "level": 3, "title": "PDF 第 20 页", "id": "pdf-20" }, { "level": 3, "title": "获取所有分享参与人", "id": "section-65" }, { "level": 3, "title": "设置分享参与人的权限角色", "id": "section-67" }, { "level": 3, "title": "删除分享参与人", "id": "section-69" }, { "level": 3, "title": "PDF 第 21 页", "id": "pdf-21" }, { "level": 3, "title": "提醒关注", "id": "section-71" }, { "level": 3, "title": "移除某人的关注", "id": "section-73" }, { "level": 3, "title": "获取关注文件的用户列表", "id": "section-75" }, { "level": 3, "title": "获取可以关注文件的用户列表，并且标记已关注文件的用户", "id": "section-77" }, { "level": 3, "title": "PDF 第 22 页", "id": "pdf-22" }, { "level": 2, "title": "企业部门相关 API", "id": "api-4" }, { "level": 3, "title": "获取当前企业信息", "id": "section-79" }, { "level": 3, "title": "获取企业所有部门信息", "id": "section-81" }, { "level": 3, "title": "创建企业部门", "id": "section-83" }, { "level": 3, "title": "PDF 第 23 页", "id": "pdf-23" }, { "level": 3, "title": "获取部门角色列表", "id": "section-85" }, { "level": 3, "title": "添加部门人员", "id": "section-87" }, { "level": 3, "title": "PDF 第 24 页", "id": "pdf-24" }, { "level": 3, "title": "删除部门人员", "id": "section-89" }, { "level": 3, "title": "获取自己所在部门信息", "id": "section-91" }, { "level": 3, "title": "获取部门人员", "id": "section-93" }, { "level": 3, "title": "PDF 第 25 页", "id": "pdf-25" }, { "level": 3, "title": "添加企业成员", "id": "section-95" }, { "level": 3, "title": "更新成员信息", "id": "section-96" }, { "level": 3, "title": "PDF 第 26 页", "id": "pdf-26" }, { "level": 3, "title": "获取企业成员信息", "id": "section-97" }, { "level": 3, "title": "获取企业所有成员", "id": "section-99" }, { "level": 3, "title": "获取企业日志", "id": "section-101" }, { "level": 3, "title": "PDF 第 27 页", "id": "pdf-27" }, { "level": 2, "title": "消息推送 API", "id": "api-5" }, { "level": 3, "title": "发布公告", "id": "section-103" }, { "level": 3, "title": "获取发布的公告", "id": "section-105" }, { "level": 3, "title": "发送部门讨论", "id": "section-107" }, { "level": 3, "title": "PDF 第 28 页", "id": "pdf-28" }, { "level": 3, "title": "获取部门讨论", "id": "section-109" }, { "level": 3, "title": "获取企业日志", "id": "section-111" }, { "level": 3, "title": "PDF 第 29 页", "id": "pdf-29" }, { "level": 2, "title": "四、 JWT token 登录", "id": "jwt-token" }, { "level": 3, "title": "PDF 第 30 页", "id": "pdf-30" }, { "level": 2, "title": "五、 附录 通用 API 调用返回状态码", "id": "api-6" }, { "level": 2, "title": "状态码 result code", "id": "result-code" } ], "images": [], "text": "认证与 Token PDF 第 1 页 企业开发 API V6.6 上海画擎信息科技有限公司 姜大军 PDF 第 2 页 目录 一、 获取企业开发账号 ..............................................................................................................................................................................4 二、 认证 API ............................................................................................................................................................................................. 6 认证接口一（登录回调方式） ................................................................................................................................................................6 认证接口二（免登录方式 – JWT token 方式，在私有云部署中，需要开启 jwt token 的登录方式） ....................................... 6 获取 token .................................................................................................................................................................................................8 刷新 token .................................................................................................................................................................................................8 三、 文件访问 API ..................................................................................................................................................................................... 8 获取文件列表 ............................................................................................................................................................................................9 获取文件信息 ............................................................................................................................................................................................9 创建文件夹 ..............................................................................................................................................................................................10 预上传文件 ..............................................................................................................................................................................................10 上传文件 ..................................................................................................................................................................................................11 获取下载文件地址 ..................................................................................................................................................................................12 获取下载多文件地址 ..............................................................................................................................................................................12 获取下载文件缩略图地址 ......................................................................................................................................................................13 修改文件信息 ..........................................................................................................................................................................................13 修改文件名 ..............................................................................................................................................................................................13 删除文件(到回收站） .............................................................................................................................................................................14 删除文件（从回收站） ..........................................................................................................................................................................14 清空回收站 ..............................................................................................................................................................................................14 恢复文件（从回收站） ..........................................................................................................................................................................14 获取文件的所有版本信息 ......................................................................................................................................................................15 设置文件当前版本 ..................................................................................................................................................................................15 移动文件 ..................................................................................................................................................................................................15 拷贝文件 ..................................................................................................................................................................................................15 拷贝文件进度 ..........................................................................................................................................................................................16 文件日志 ..................................................................................................................................................................................................16 创建素材库分类 ......................................................................................................................................................................................17 创建子素材库 ..........................................................................................................................................................................................17 共享文件相关 API ................................................................................................................................................................................. 17 获取文件的分享 url ................................................................................................................................................................................ 18 获取分享的权限列表 ..............................................................................................................................................................................18 获取用户对于单个文件有权设置的分享角色 ......................................................................................................................................18 创建链接分享 ..........................................................................................................................................................................................18 关闭链接分享 ..........................................................................................................................................................................................19 设置链接分享密码 ..................................................................................................................................................................................19 邀请人员参与分享 ..................................................................................................................................................................................19 获取所有分享参与人 ..............................................................................................................................................................................20 设置分享参与人的权限角色 ..................................................................................................................................................................20 删除分享参与人 ......................................................................................................................................................................................20 提醒关注 ..................................................................................................................................................................................................21 移除某人的关注 ......................................................................................................................................................................................21 获取关注文件的用户列表 ......................................................................................................................................................................21 获取可以关注文件的用户列表，并且标记已关注文件的用户 ..........................................................................................................21 企业部门相关 API ................................................................................................................................................................................. 22 获取当前企业信息 ..................................................................................................................................................................................22 获取企业所有部门信息 ..........................................................................................................................................................................22 创建企业部门 ..........................................................................................................................................................................................22 获取部门角色列表 ..................................................................................................................................................................................23 添加部门人员 ..........................................................................................................................................................................................23 删除部门人员 ..........................................................................................................................................................................................24 获取自己所在部门信息 ..........................................................................................................................................................................24 获取部门人员 ..........................................................................................................................................................................................24 添加企业成员 ..........................................................................................................................................................................................25 更新成员信息 ..........................................................................................................................................................................................25 获取企业成员信息 ..................................................................................................................................................................................26 获取企业所有成员 ..................................................................................................................................................................................26 获取企业日志 ..........................................................................................................................................................................................26 消息推送 API ......................................................................................................................................................................................... 27 发布公告 ..................................................................................................................................................................................................27 获取发布的公告 ......................................................................................................................................................................................27 发送部门讨论 ..........................................................................................................................................................................................27 获取部门讨论 ..........................................................................................................................................................................................28 获取企业日志 ..........................................................................................................................................................................................28 四、 JWT token 登录 .................................................................................................................................................................................29 五、 附录 通用 API 调用返回状态码 ............................................................................................................................................... 30 PDF 第 3 页 状态码 result code ................................................................................................................................................................................. 30 PDF 第 4 页 一、 获取企业开发账号 登录巴别鸟私有云企业管理后台，在首页中设置开发者账号： 打开后填写回调函数地址：http://xxx.xxx.xxx.xxx/public/babelAuthResult.do 填写后点击确定后自动产生开发者 id (client id)和开发者密钥(client secret)： 注：jwtToken 为相应的生成 jwtToken 时的加密密钥。 PDF 第 5 页 PDF 第 6 页 二、 认证 API 认证接口一（登录回调方式） /api/authorize.do HTTP 请求方式 GET URL 参数 参数名 Comment(说明) response type 必须为 code（必填） string client id 开发者的 id（必填） string redirect uri 回调函数地址，需要和注册时保持一致（必填） string data 任意数据，回调时传回 string 例如： /api/authorize.do?response type=code&client id=xxxxx&redirect uri=http://xxx.xxx.xxx&data=xxx 通过浏览器访问 返回结果 如果用户未登录，则会跳转到登录页，登录后如果未授权，则会 302 跳转到授权页，如果用户已经授权，则会 302 跳转到 redirect uri 并且带上授权码和 data，类似于 http://xxx.xxx.xxx?code=xxx&data=xxx code 有效期 5 分钟。 认证接口二（免登录方式 – JWT token 方式，在私有云部署中，需要开启 jwt token 的登录方 式） /api/authorizeByJWT.do HTTP 请求方式 GET URL 参数 参数名 Comment(说明) response type 必须为 code（必填） string client id 开发者的 id（必填） string jwt token Jwt token，（必填） string 是对{client id: xxxxxxx} 加密 形成的字符串 email email(可选), 传入用户的邮箱，以该用户进行登录，不填以企业管理员进行登录，string phone phone(可选), 传入用户的手机号，以该用户进行登录，不填以企业管理员进行登录， string babelId babelId(可选), 传入用户的工号，以该用户进行登录，不填以企业管理员进行登录， string PDF 第 7 页 例如： /api/authorizeByJWT.do?response type=code&client id=xxxxx&jwt token=xxx 说明：使用这个 api，如果不填 email, phone, babelId 系统将自动以管理员身份登录，否则会以 email, phone, babelId 对应的用户去 登录，不会显示登录界面去登录。注（email, phone, babelId）只需其中一个就可。 返回结果 { \"success\": true \"code\": \"xxxxxxxxxxxxxxxxxxxxxxxxx\", } jwt token 为 自己写程序生成 样例代码如下: import java.util.Date; import java.util.HashMap; import java.util.Map; import javax.crypto.SecretKey; import javax.crypto.spec.SecretKeySpec; import io.jsonwebtoken.Claims; import io.jsonwebtoken.JwtBuilder; import io.jsonwebtoken.Jwts; import io.jsonwebtoken.SignatureAlgorithm; import net.sf.json.JSONObject; / 生成标准 jwt 使用的 token / public class JWT App { static String skey = \"babeldfdfer95840834 t8e 9 9 5934 5943 5886256\"; // 密钥 在巴别鸟后台 开发者账号处 填入的 jwtToken 字段。 public static void main( String[] args ) { HashMap clientInfo = new HashMap (); clientInfo.put(\"client id\", \"7459492016147273\"); // 为开发者账户中的 client id try { String token = createTokenJWT(clientInfo); System.out.println(\" login token:\" + token); String token1 = \"eyJhbGciOiJIUzI1NiJ9.eyJkdXJhdGlvbiI6NjAsInBheWxvYWQiOnsiY2xpZW50X2lkIjoiNzQ1OTQ5MjAxNjE0NzI3MyJ9LCJ0aW1lIjoxNjkxNDg4MzY4NTk0fQ.pRFCwXd2snMr IgFWOFwYbvyAeeNhoFINGk Wmv7d24g\"; JSONObject parsed = parseTokenJWT(token1); System.out.println(\" parsed:\" + parsed); System.out.println(\" 将此 token 作为参数放在 url 中即可， 如:\"); } catch (Exception e) { System.out.println(e.getMessage()); } } public static String createTokenJWT(Map config) throws Exception { HashMap data = new HashMap (); data.put(\"time\", new Date().getTime()); data.put(\"duration\", 60); data.put(\"payload\", config); SignatureAlgorithm signatureAlgorithm = SignatureAlgorithm.HS256; SecretKey key = generalKey(); JwtBuilder builder = Jwts.builder() .setClaims(data) .signWith(signatureAlgorithm, key); System.out.println( \" builder :\" + builder); return builder.compact(); } public static JSONObject parseTokenJWT(String jwt) throws Exception { SecretKey key = generalKey(); Claims claims = Jwts.parser() .setSigningKey(key) .parseClaimsJws(jwt) .getBody(); System.out.println(\" claims:\" + claims.toString()); Long time = (Long)claims.get(\"time\"); long duration = (Integer)claims.get(\"duration\"); Long now = new Date().getTime(); if (now time 1000 duration) return null; // 超过 10 分钟的 token 无效 JSONObject obj = JSONObject.fromObject(claims.get(\"payload\")); return obj; } public static SecretKey generalKey(){ String stringKey = skey; byte[] encodedKey = stringKey.getBytes(); SecretKey key = new SecretKeySpec(encodedKey, 0, encodedKey.length, \"HmacSHA256\"); return key; } } PDF 第 8 页 获取 token /api/token.do HTTP 方法： POST HTTP Header 该接口使用 Basic Auth 的方式校验 client 的信息。具体做法是在 header 中添加类似于\"Authorization: Basic xxxxxxxxx\"。其中 \"xxxxxxxxx\"是通过开发者 id (client id)和开发者秘钥(client secret)算出来的，具体算法为 Base64Encode(client id + \":\" + client secret) Base64Encode 自行选择工具进行 Base64 编码 URL 参数 参数名 Comment(说明) grant type（必填） 必须为 authorization code string code（必填） 授权码，即回调地址接收到的授权码，授权码的有效期为 5 分钟，用过一次，无论成功 还是失败，授权码都会失效 string 例如： /api/token.do?grant type=authorization code&code=xxx&redirect uri=http://xxx.xxx.xxx 返回结果 access token 接口访问标识 refresh token 用来刷新 access token，有效时间为 30 天 expires in access token 的有效时间，单位为 s 刷新 token /api/refreshToken.do HTTP 方法： POST HTTP Header 该接口使用 Basic Auth 的方式校验 client 的信息。具体做法是在 header 中添加类似于\"Authorization: Basic xxxxxxxxx\"。其中 \"xxxxxxxxx\"是通过 client id 和 client secret 算出来的，具体算法为 Base64Encode(client id + \":\" + client secret) URL 参数 参数名 Comment(说明) grant type（必填） 必须为 refresh token string refresh token（必填） 即接口 2 中获取到的 refresh token string 例如： /api/refreshToken.do?grant type=refresh token&refresh token=xxx 返回结果 access token 接口访问标识, refresh token 用来刷新 access token，有效时间为 30 天 expires in access token 的有效时间 为 3600，单位为 s 三、 文件访问 API 所有的接口在访问时需要在 HTTP header 中带上 access token。对于含有请求参数的接口，通常是一些 POST、 PUT 或者 DELETE 接口，还需要设置 Content Type 来指定参数的格式。如果需要访问不同版本的 API，就需要 在请求路径上指定具体版本，如果需要返回不同格式的 response body，那么还需要设置 Accept。所有的参数都应 该采用 utf 8 的编码。 PDF 第 9 页 Headers： Authorization：存放 access token，格式为：\"Bearer \" + access token。 Content Type：指明请求参数的格式。如果是 POST、PUT 或者 DELETE 请求，需要指定\"application/json\"，我 们目前不支持其他请求参数的格式，比如 xml。如果是其他类型比如 GET 请求，可以不在 header 中设置 Content Type。 Accept：用于指定响应结果的格式以及 api 的版本信息。目前只支持返回 json 格式的 response，所以一般情况下 指定\"application/json\"。 若接口访问成功，我们会返回 json 格式的 response，并且 HTTP 的 status code 为 200。所有请求成功的 response 的 json 都会带有\"success: true”。response 的 header 里的 X Babel Version 表示此次请求访问的 api 的版本号。 获取文件列表 /nd/api/file/list dir HTTP 方法： GET URL 参数 参数名 Comment(说明) parent id 父文件夹 id（必填） string 当 parent 为 1 时返回企业文件夹内容，2 返回个人文件夹内容，3 返回我的 项目，4 返回我加入的分享，其它 fileId 返回正常的文件夹中的内容。 page size 页的大小 number page 页号 number type 类型：分为 1 file，2 folder，0 all 三种类型 string 返回字段说明 属性名 类型 说明 files 数组 文件信息 {fileId, name, …} total int 总数量 page int 页容量 success boolean 获取成功标记 code int 返回错误码 0 表示成功 获取文件信息 /nd/api/file/fileinfo HTTP 方法： GET URL 参数 参数名 Comment(说明) id 文件 id（必填） string 返回字段说明 fileInfo 信息 属性名 类型 说明 file Object 文件信息 { id, name, …} PDF 第 10 页 success boolean 获取成功标记 code int 返回错误码 0 表示成功 创建文件夹 /nd/api/file/create folder HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) parent id 目标文件夹 id（必填） string name 文件名（必填） string 返回字段说明 属性名 类型 说明 file Object 文件信息 { id, name, …} success boolean 获取成功标记 code int 返回错误码 0 表示成功 预上传文件 用于返回第二步上传文件时所需要的参数(url、upload token) /api/file/preUploadFile.do HTTP 方法： GET URL 参数 参数名 Comment(说明) parent id 目标文件夹 id（必填）(在根目录下上传可忽略此项) string name 文件名（必填） string file id 上传新版本时需要指定上传那个文件的新版本(上传新文件可忽略此项) string 正确的返回结果如下 {\"upload token\":\"92808ecfc2ac4e0ebc0b912edac3be4a\",\"url\":\"http://testdocument.babel.cc/api/file/uploadPdf.do\",\"su ccess\":true,\"code\":0} 返回字段说明 属性名 类型 说明 url string 该 url 仅能使用 1 次，且有效期为 1 小时 调用此 url 上传文件，成功后会返回 fileId， fileName、version 等 upload token string 上传文件时作为 post 的参数 PDF 第 11 页 上传文件 注意，本 api 的 url 是预上传接口返回的, 这里没有具体的 url，只是参数说明 https://xxx.xxx.xxx:xxx/api/file/uploadXXX.do（具体的 url 是由上一节 /api/file/preUploadFile.do 中返回的 url） POST POST 请求体参数 参数名 Comment(说明) file 文件二进制数据(上传数据) upload token /api/file/preUploadFile.do 请求中的返回值 返回信息如下 {\"fileId\":\"7728538212615908\",\"version\":0,\"fileName\":\"mesos.pdf\",\"fileSize\":848854,\"success\":true,\"code\":0} 上传相关代码 示例 加入 ‘com.squareup.okhttp3:okhttp:3.3.1’ 包 private void uploadFile(final String fileName, String parentId, final DaoCallback callback){ preUploadFile(fileName, parentId, new DaoCallback () { @Override public void onSuccess(JSONObject data) { int code = data.optInt(\"code\", 1); final String url = data.optString(\"url\", null); final String uploadToken = data.optString(\"upload token\"); if (code == 0) { // File file = new File(filePath); RequestBody fileContent = RequestBody.create(MultipartBody.FORM, file); RequestBody requestBody = new MultipartBody.Builder() .setType(MultipartBody.FORM) .addFormDataPart(\"file\", fileName, fileContent) .addFormDataPart(\"upload token\", uploadToken) .build(); Request request = new Request.Builder() .url(url) .post(requestBody) .build(); // 上传需要较长的时间，因此需要设置较长的 timeout OkHttpClient okHttpClient = new OkHttpClient(); okHttpClient.newCall(request) .enqueue(new okhttp3.Callback() { @Override public void onFailure(okhttp3.Call call, IOException e) { callback.onFailure( 1, null); } @Override public void onResponse(okhttp3.Call call, okhttp3.Response response) throws IOException { int httpCode = response.code(); if (httpCode == 200) { try { JSONObject result = new JSONObject(response.body().string()); response.body().close(); boolean success = result.getBoolean(\"success\"); if (success) { callback.onSuccess(null); } else { int code = result.getInt(\"code\"); String msg = result.optString(\"msg\"); callback.onFailure(code, msg); } } catch (JSONException e) { callback.onFailure( 2, null); } } else { callback.onFailure(httpCode, null); } } }); } } @Override public void onFailure( int errorCode, String msg){ Log.e(\"FileTransfer\", \"filePreUpload 失败 errorCode=\" + errorCode); } }); } PDF 第 12 页 private void preUploadFile(String fileName, String parentId, final DaoCallback callback) { String preUploadUrl = \"http://private.babel.cc:80/api/file/preUploadFile.do?name=1234.jpg&parent id=0\"; // 传入相应的参数 name, parent id String authorization = \"Bearer d48d0a0e253c4a2985d8c5653f717d71\"; //根据说明 生成 Request request = new Request.Builder().url(preUploadUrl) .addHeader(\"Authorization\", authorization) .build(); OkHttpClient okHttpClient = new OkHttpClient(); okHttpClient.newCall(request).enqueue(new okhttp3.Callback() { @Override public void onFailure(okhttp3.Call call, IOException e) { Log.d(\"\", \"\"); } @Override public void onResponse(okhttp3.Call call, okhttp3.Response response) throws IOException { Log.d(\"\",\"\"); int httpCode = response.code(); if (httpCode == 200) { JSONObject result = null; try { result = new JSONObject(response.body().string()); } catch (JSONException e) { e.printStackTrace(); } try { boolean success = result.getBoolean(\"success\"); if (success) { String url = result.getString(\"url\"); callback.onSuccess(result); } else { int code = result.getInt(\"code\"); String msg = result.optString(\"msg\"); callback.onFailure(code, msg); } } catch (JSONException e) { callback.onFailure( 2, null); } } else { callback.onFailure(httpCode, null); } } }); } 获取下载文件地址 /api/file/getFileDownloadUrl.do HTTP 方法： GET URL 参数 参数名 Comment(说明) fileId 需要下载的文件 id（必填） string version 文件的版本号（可选） number 返回信息如下 {\"code\":0,\"success\":true,\"type\":\"文件类型\",\"url\":\"文件下载地址\"} 获取下载多文件地址 /api/file/downloadMultiFiles.do HTTP 方法： GET URL 参数 参数名 Comment(说明) fileIdArr 由需要下载的文件 id 组成的字符串，由符号“!“(半角)分割，比如下载 id 为 133 与 233 的两 个文件，则 fileIdArr 的值为“133!233” string 类型 PDF 第 13 页 返回信息如下 {\"code\":0,\"success\":true,\"type\":\"文件类型\",\"url\":\"文件下载地址\"} 返回值 url 为多个文件打包后的下载地址。 获取下载文件缩略图地址 /api/file/downloadThumbnail.do HTTP 方法： GET URL 参数 参数名 Comment(说明) fileId 需要下载的文件 id（必填） string version 文件的版本号（可选） number size 需要显示的缩略图尺寸，取宽高中的最大值 返回信息如下 {\"code\":0,\"success\":true, \"url\":\"文件下载地址\"} 返回值 url 为多个文件打包后的下载地址。 修改文件信息 /nd /api/file/update file HTTP 方法： POST 修改文件信息 POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填） string name 新文件名 （可选） string description 文件说明 （可选） string 返回信息如下 {\"code\":0,\"success\":true} 修改文件名 /nd /api/file/rename HTTP 方法： POST 修改文件信息 POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填） string name 新文件名 string 返回信息如下 {\"code\":0,\"success\":true} PDF 第 14 页 删除文件(到回收站） /nd /api/file/remove file HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file ids[] 目标文件 id 数组（必填） string[] 返回信息如下 {\"code\":0,\"success\":true} 删除文件（从回收站） /nd /api/file/remove from trash HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file ids[] 目标文件 id 数组（必填） string[] 返回信息如下 {\"code\":0,\"success\":true} 清空回收站 /nd /api/file/empty trash HTTP 方法： POST POST 请求体参数 参数名 说明 返回信息如下 {\"code\":0,\"success\":true} 恢复文件（从回收站） /nd /api/file/restore file HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file ids[] 目标文件 id 数组 string[] restoreAll 不填写 file ids, restoreAll 为 true，时恢复回收站中所有文件，boolean 返回信息如下 PDF 第 15 页 {\"code\":0,\"success\":true} 获取文件的所有版本信息 /nd /api/file/versions HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 目标文件 id（必填） string 返回信息如下 {\"code\":0,\"versions\":[],\"success\":true} 设置文件当前版本 /nd /api/file/version HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file id 目标文件 id （必填） string version 版本号（必填） number 返回信息如下 {\"code\":0,\"success\":true} 移动文件 /nd /api/file/move HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file ids 需要移动的目标文件 id 数组（必填） string target id 需要移动到的目标文件夹 id（必填） string 返回信息如下 {\"code\":0,\"success\":true} 拷贝文件 /nd /api/file/copy HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) PDF 第 16 页 file ids 需要拷贝的目标文件 id 数组（必填） string target id 需要拷贝到的目标文件夹 id（必填） string 返回信息如下 { \"code\": 0, \"copyKey\": \"81427630 054a 11ef 8355 db93b4b1d006\",\"fileNum\": 10, \"success\": true} 拷贝文件进度 /nd /api/file/copy progress HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) copyKey 查看拷贝进度 copyKey 由 copy 接口返回（必填） string 返回信息如下 { \"code\": 0, \"completed\": 10,\"total\": 10, \"result\": {}, \"success\": true} 文件日志 /nd /api/file/file logs HTTP 方法： GET GET 请求体参数 参数名 Comment(说明) file id 目标文件 id 数组（必填） string startIndex 获取日志的起始顺序 第几条日志开始返回（选填） int 默认 0， pageSize 每页返回的个数（选填） int type 日志类型(选填) int 默认 0, 查看所有记录， 1 仅查看访问记录，2 仅查看上传下载，3 仅查看匿名用 户，4 仅查看分享及邀请，5 仅查看删除记录 userName 某个用户名 (选填) string, 返回某个用户的日志 lang 语言(选填) 默认 cn, string 返回日志的语言 cn(中文) en(英文) 返回信息如下 {\"code\":0,\"success\":true, \"logs\":[], \"total\":50} 设置用户是否有权访问素材库 /nd /api/file/ set user access material library HTTP 方法： POST GET 请求体参数 参数名 Comment(说明) userId 用户的 id 数组数型 [usrId1, userId2]（必填） string can 是否可访问 数值类型 （必填） int 默认 0， 0： 不可访问， 1:可以访问 返回信息如下 {\"code\":0,\"success\":true} PDF 第 17 页 创建素材库分类 /nd /api/file/create material class HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) destDirFileId 目标文件夹 的 fileId（必填） string name 创建分类库的名称（必填） string accessType 分类可见性 (选填) 默认为公开 0. 0: // 公开 1: // 需要申请 2: // 部门公开 3: // 部门申请 4: // 保密 managerIds 负责人的 id 数组类型 [usrId1,userId2] departmentIds 分类可见性 限定部门 的部门 id (选填) 数组类型 [departmentId1,departmentId2] 返回信息如下 {\"code\":0, \"success\":true, \"materialClass\": {}} 创建子素材库 /nd /api/file/create material folder HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) destDirFileId 目标文件夹 的 fileId（必填） string name 创建分类库的名称（必填） string accessType 分类可见性 (选填) 默认为公开 0. 0: // 公开 1: // 需要申请 2: // 部门公开 3: // 部门申请 4: // 保密 managerId 负责人的 id (选填) string departmentIds 分类可见性 限定部门 的部门 id (选填) 数组类型 [departmentId1,departmentId2] assistantIds 素材库助理人员的 id （选填） 数组类型 [usrId1,userId2] 返回信息如下 {\"code\":0, \"success\":true, \"materialFolder\": {}} 共享文件相关 API PDF 第 18 页 获取文件的分享 url /nd/api/share/shareurl HTTP 方法： GET 获取文件的分享链接（先打开分享后，再获取该链接） URL 参数 参数名 Comment(说明) file id 文件 id string is https 返回的 share url 协议是否为 https 0 为 http, 1 为 https， 默认 0 number 返回字段说明 {\"code\":0,\"url\":\"https://private.babel.cc/share.do?s=http://private.babel.cc/share.do?s=MjY2OTYzNTk3OTU2NzEzOTtXZWQgSnVsIDAxIDIwMj AgMTg6MzM6NTAgR01UKzA4MDAgKEhvbmcgS29uZyBTdGFuZGFyZCBUaW1lKQ%3D%3D\",\"success\":true} 获取分享的权限列表 /nd/api/share/share roles HTTP 方法： GET URL 参数 参数名 Comment(说明) 返回字段说明 {\"code\":0,\"roles\":[],\"success\":true} 获取用户对于单个文件有权设置的分享角色 /nd/api/share/share role forfile HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 文件 id string 返回字段说明 {\"code\":0,\"roles\":[],\"success\":true} 创建链接分享 /nd/api/share/open link share HTTP 方法： POST 打开分享，获取新的分享链接，之前的链接失效。 PDF 第 19 页 POST 请求体参数 参数名 Comment(说明) file id 预分享的文件 id（必填） string link role id 分享的角色 string is https 返回的 share url 协议是否为 https number anonymousVisit 是否允许匿名访问，1 为允许，0 为不允许（可选，默认为 1） number 返回字段说明 {\"code\":0,\"share url\":\"http://private.babel.cc/share.do?s=http://private.babel.cc/share.do?s=MjY2OTYzNTk3OTU2NzEzOTtXZWQgSnV sIDAxIDIwMjAgMTg6MzM6NTAgR01UKzA4MDAgKEhvbmcgS29uZyBTdGFuZGFyZCBUaW1lKQ%3D%3D\",\"password\":\"\",\"success\":tru e} 关闭链接分享 /nd/api/share/close link share HTTP 方法： POST 关闭我打开的分享链接 POST 请求体参数 参数名 Comment(说明) file id 分享的文件 id（必填） string 返回字段说明 {\"code\":0,\"success\":true} 设置链接分享密码 /nd/api/share/set share password HTTP 方法： POST 文件链接分享已打开，设置链接分享的密码。 POST 请求体参数 参数名 Comment(说明) file id 预分享的文件 id（必填） string password 链接分享的密码 string is https 返回的 share url 协议是否为 https number 返回字段说明 {\"code\":0,\"success\":true, \"share url\": \"http://private.babel.cc/share.do?s=xxxxxxxxxxx\"} 邀请人员参与分享 /nd/api/share/invite share HTTP 方法： POST PDF 第 20 页 可以根据用户的邮箱或者手机来邀请某些人来访问文件 POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填） string share role 分享的权限的 id（以上所有人共享此权限）（必填） string emails[] 邮箱数组 string[] phones[] 手机号的数组 string[] 返回字段说明 {\"code\":0,\"success\":true} 获取所有分享参与人 /nd/api/share/share participants HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 文件 id（必填） string 返回字段说明 {\"code\":0,\"users\":[],\"success\":true} 设置分享参与人的权限角色 /nd/api/share/set participant role HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填） string babelshare id int（必填） 用户 id string role id int（必填） 角色 id string 返回字段说明 {\"code\":0,\"success\":true} 删除分享参与人 /nd/api/file/remove share participant HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) PDF 第 21 页 file id 文件 id（必填） string babelshare ids[] int （必填） 用户 id string 返回字段说明 {\"code\":0,\"success\":true} 提醒关注 /nd/api/file/focus file HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填） string user ids[] 提醒的用户的 id，此 id 应该在文件参与人中选取，否则提醒不会起作用（必填）string[] 返回字段说明 {\"code\":0,\"success\":true} 移除某人的关注 /nd/api/file/unfocus file HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填）string user ids[] 提醒的用户的 id，此 id 应该在文件参与人中选取，否则提醒不会起作用（必填） string[] 返回字段说明 {\"code\":0,\"success\":true} 获取关注文件的用户列表 /nd/api/file/user focusfile HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 文件 id（必填） string 返回字段说明 {\"code\":0,\"users\":[],\"success\":true} 获取可以关注文件的用户列表，并且标记已关注文件的用户 /nd/api/file/user can focusfile PDF 第 22 页 HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 文件 id（必填） string 返回字段说明 企业部门相关 API 获取当前企业信息 /nd/api/enterprise/current HTTP 方法： GET URL 参数 参数名 Comment(说明) 无 返回字段说明 {\"code\":0,\"enterprise\":{},\"success\":true} 获取企业所有部门信息 /nd/api/enterprise/departments HTTP 方法： GET URL 参数 参数名 Comment(说明) 无 返回字段说明 属性名 类型 说明 departments []数组 返回所有的部门信息 tree {}json 数据 返回部门的父子结构信息 code int sucess boolean 创建企业部门 /nd/api/enterprise/create department HTTP 方法： POST PDF 第 23 页 POST 请求体参数 参数名 Comment(说明) parent dep 父部门 id， 0 表示跟部门（必填）string name 部门名称（必填）string description 部门描述 string 返回字段说明 属性名 类型 说明 department {} json 数据结构 code int sucess boolean 获取部门角色列表 /nd/api/enterprise/dep role HTTP 方法： GET URL 参数 参数名 Comment(说明) 返回字段说明 属性名 类型 说明 roles []数组 { id, filePermission,enterpriseId,filePermission,managerPermission, default,nameEn,name} code int sucess boolean 添加部门人员 /nd/api/enterprise/add dep mem HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) department id 部门 id（必填）string user ids[] 用户列表 string[] role id 用户在部门中的角色 string PDF 第 24 页 返回字段说明 属性名 类型 说明 删除部门人员 /nd/api/enterprise/remove dep mem HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) department id 部门 id（必填）string user ids[] 人员的 id（必填）string[] 返回字段说明 属性名 类型 说明 获取自己所在部门信息 /nd/api/enterprise/mydeparments HTTP 方法： GET URL 参数 参数名 Comment(说明) 无 返回字段说明 属性名 类型 说明 departments []数组 返回我所在的部门信息 code int sucess boolean 获取部门人员 /nd/api/enterprise/departmentmembers PDF 第 25 页 HTTP 方法： GET URL 参数 参数名 Comment(说明) department id 部门 id（必填）string 返回字段说明 属性名 类型 说明 users 数组 ： {id, name, avatrUrl,} 添加企业成员 /nd/api/enterprise/add ent mem HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) email Email 邮箱 string password 密码 string enterprise role 企业成员角色, 可选 number department ids[] 该用户的部门， 可选 string[] department roles[] 在部门中的角色， 可选 string[] sex 性别 0 未设置 1 男 2 女 number name 用户名 string phone 手机号， 可选 string babelId 工号，可选 string spacelimit 个人空间限制，单位 GB, 0 表示不限制 number can ownfile 用户能否拥有个人文件， 1 使用企业总体设置, 0 没有个人文件, 1 有个人文件 number remarks 用户描述， 可选 string join time 用户加入企业时间，Unix time, 单位秒 number password is md5 传入密码是否需要 md5 加密, 0 非 md5 密码， 1 md5 加密过的密码 number 更新成员信息 /api/updateUserInfo.do HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) email 邮箱地址（搜索关键字，必须）string password 密码（修改密码，可选）string frozen 1 – 表示冻结， 0 – 表示解冻 （冻结该账号，可选）number password is md5 传入密码是否需要 md5 加密, 0 非 md5 密码， 1 md5 加密过的密码 number phone 手机号 (可选) string PDF 第 26 页 获取企业成员信息 /api/getEnterpriseMember.do HTTP 方法： GET URL 参数 参数名 Comment(说明) email 邮箱地址（搜索关键字）string phone 手机号（搜索关键字）string babelId 工号（搜索关键字）string email/phone/babelId 可选择其一 返回字段说明 {\"code\":0,\"success\":true,\"user\":{}} 获取企业所有成员 /nd/api/enterprise/enterprise members HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) lang 语言类型，cn 中文 ，en 英文 , 可选 options { departmentId: // 部门 id，不填写就是企业所有人员 roleId: // 角色 id， 不填写就是不限角色 \"userType\": 0, // 0 企业内人员， 1 外部人员 \"keyName\": \"\", // 搜索关键字： 人名，手机号，邮箱， 不填写就是所有人员 \"startIndex\": 0， \"pageSize\": 20, status: // 0 所有账号， 1 停用的账号 } 可选 返回字段说明 {\"code\":0,\"success\":true,\"members\":{},\"total\":xx} 获取企业日志 /nd/api/enterprise/enterprise logs HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) department id 部门 id，不填写就是所有部门的日志 string 可选 keyword 日志的相关搜索关键字 string 可选 PDF 第 27 页 startTime 日志起始时间 number 可选 endTime 日志截止时间 number 可选 startIndex int 可选 pageSize int 可选 返回字段说明 {\"code\":0,\"success\":true,\"logs\":{},\"total\":xx} 消息推送 API 发布公告 /nd/api/enterprise/broadcast HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) title 公告内容字符串（必填） string content 内容（必填）string target users[] UserId 数组，如果为空则表示全部人员接收，string[] target deps[] 目标部门，该部门及子部门所有成员都会收到通知，string[] target users 与 target deps 至少要填 1 个 返回字段说明 {\"code\":0,\"success\":true} 获取发布的公告 /nd/api/enterprise/broadcast HTTP 方法： GET URL 参数 参数名 Comment(说明) start index number pagesize number 返回字段说明 {\"code\":0,\"broadcasts\":[],\"total\":19,\"success\":true} 发送部门讨论 /nd/api/file/send dep discussion HTTP 方法： POST PDF 第 28 页 POST 请求体参数 参数名 Comment(说明) dep id 部门 id（必填） string message 信息字符（必填） string json 字符串, 格式{Type: “Text”, Body:”你好” } 返回字段说明 {\"code\":0,\"messageId\":99,\"success\":true} 获取部门讨论 /nd/api/file/dep discussion HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) dep id 部门 id（必填）string pagesize 页的大小 string start id 消息 id,只会获取此消息之前的消息，为空则获取最新消息 string 返回字段说明 {\"msgArr\":[],\"gotMoreMessages\":1,\"code\":0,\"success\":true} 获取企业日志 /nd/api/enterprise/enterprise logs HTTP 方法： GET URL 参数 参数名 Comment(说明) department id 部门 id（）string pagesize 页的大小 number，默认值 1000 start index 消息起始位置, number keyword 日志关键词 string startTime 起始日期: 秒 number endTime 截止日期 秒 number 返回字段说明 {\"logs\":[],\"total\":0,\"code\":0,\"success\":true} total 返回所有符合条件的(与分页 pageSize 无关) PDF 第 29 页 四、 JWT token 登录 在私有云部署中，可以开启 jwt token 的登录方式，在这种情况下，允许通过下面的 url 直接以某用户的身份免登录进入网盘系 统： /account/tokenLogin.do 参数： 参数名称 可选性 说明 可选值 默认值 userToken 必填 含有登录用户的加密信息（构造方 无 法详见下面的说明） fileId 可选 要访问的文件（夹）的 id，如果不 无 填写则打开用户根目录 closeTitleBar 可选 是否关闭标题栏 1 关闭 0 不关闭 0 disableEntMark 可选 是否隐藏左上角企业标识 1 隐藏 0 不隐藏 0 disableUserMark 可选 是否隐藏右上角用户设置入口 1 隐藏 0 不隐藏 0 defaultLang 可选 设置界面使用的语言 cn 中文 en 英文 zh HK 繁体 cn defaultClrTheme 可选 设置界面颜色主题 normal 标准模式，dark 暗色模式 normal 比如下面是以英文及暗色模式并隐藏右上角用户标志进入用户根目录界面 /account/tokenLogin.do userToken=xxxxxxxxxxxxxxxx defaultClrTheme=dark defaultLang=en disableUserMark=1 userToken 的构建 userToken 是含有登录用户信息的加密字符串，加密信息是通过标准的双方传输可信数据的安全机制 JWT 创建的口令字， JWT 加密的用户信息 JSONObject 内容如下： { payload: { email: “xxx@xxx.com”/“135XXXXXXX”/“XXXX”} time: now } 说明：其中 email, 可以是邮箱，手机号，工号； 代码如下： public static void main( String[] args ) { HashMap user = new HashMap (); user.put(\"email\", \"yuanchaozhao@qq.com\"); try { //token login String userToken = createTokenJWT(user); System.out.println(\" login token:\" + userToken); JSONObject parsed = parseTokenJWT(userToken); System.out.println(\" parsed:\" + parsed); System.out.println(\" 将此 token 作为参数放在 url 中即可， 如:\"); System.out.println(\"/account/tokenLogin.do?userToken=\" + userToken); } catch (Exception e) { System.out.println(e.getMessage()); } } 其它代码 参考 jwtToken 的生成代码，在认证接口二处有提供。 备注： JWT 即 JSON Web Tokens 的简写， 是满足工业标准 RFC7519 的一种通信加密解密机制，请参考： https://jwt.io/ PDF 第 30 页 五、 附录 通用 API 调用返回状态码 状态码 result code 码值 说明 0 成功 1 未知错误 2 参数错误 7 空间不足 12 禁止的用户操作 13 无效的 token 结束 the end" }, { "lang": "zh", "slug": "developer-api-files", "title": "文件 API", "description": "文件 API 的接口路径、方法、参数和返回字段。", "category": "文件 API", "top_category": "API文档", "keywords": [ "API", "文件 API", "开发者" ], "url": "zh/developer-api-files.html", "source": "content/zh/developer-api-files.md", "summary": "文件 API PDF 第 1 页 企业开发 API V6.6 上海画擎信息科技有限公司 姜大军 PDF 第 2 页 目录 一、 获取企业开发账号 ..............................................................................................................................................................................4 二、 认证 API ............................................................................................................................................................................................. 6 认证接口一（登录回调方式） ................................................................................................................................................................6 认证接口二（免登录方式 – JWT token 方式，在私有云部署中，需要开启 jwt token 的登录方式） ................", "headings": [ { "level": 1, "title": "文件 API", "id": "api" }, { "level": 3, "title": "PDF 第 1 页", "id": "pdf-1" }, { "level": 3, "title": "PDF 第 2 页", "id": "pdf-2" }, { "level": 3, "title": "PDF 第 3 页", "id": "pdf-3" }, { "level": 3, "title": "PDF 第 4 页", "id": "pdf-4" }, { "level": 2, "title": "一、 获取企业开发账号", "id": "section" }, { "level": 3, "title": "PDF 第 5 页", "id": "pdf-5" }, { "level": 3, "title": "PDF 第 6 页", "id": "pdf-6" }, { "level": 2, "title": "二、 认证 API", "id": "api-2" }, { "level": 3, "title": "认证接口一（登录回调方式）", "id": "section-2" }, { "level": 3, "title": "PDF 第 7 页", "id": "pdf-7" }, { "level": 3, "title": "PDF 第 8 页", "id": "pdf-8" }, { "level": 3, "title": "获取 token", "id": "token" }, { "level": 3, "title": "刷新 token", "id": "token-2" }, { "level": 2, "title": "三、 文件访问 API", "id": "api-3" }, { "level": 3, "title": "PDF 第 9 页", "id": "pdf-9" }, { "level": 3, "title": "获取文件列表", "id": "section-3" }, { "level": 3, "title": "获取文件信息", "id": "section-5" }, { "level": 3, "title": "PDF 第 10 页", "id": "pdf-10" }, { "level": 3, "title": "创建文件夹", "id": "section-7" }, { "level": 3, "title": "预上传文件", "id": "section-9" }, { "level": 3, "title": "PDF 第 11 页", "id": "pdf-11" }, { "level": 3, "title": "上传文件", "id": "section-12" }, { "level": 3, "title": "PDF 第 12 页", "id": "pdf-12" }, { "level": 3, "title": "获取下载文件地址", "id": "section-14" }, { "level": 3, "title": "获取下载多文件地址", "id": "section-16" }, { "level": 3, "title": "PDF 第 13 页", "id": "pdf-13" }, { "level": 3, "title": "获取下载文件缩略图地址", "id": "section-18" }, { "level": 3, "title": "修改文件信息", "id": "section-20" }, { "level": 3, "title": "修改文件信息", "id": "section-21" }, { "level": 3, "title": "修改文件名", "id": "section-23" }, { "level": 3, "title": "修改文件信息", "id": "section-24" }, { "level": 3, "title": "PDF 第 14 页", "id": "pdf-14" }, { "level": 3, "title": "删除文件(到回收站）", "id": "section-26" }, { "level": 3, "title": "删除文件（从回收站）", "id": "section-28" }, { "level": 3, "title": "清空回收站", "id": "section-30" }, { "level": 3, "title": "恢复文件（从回收站）", "id": "section-32" }, { "level": 3, "title": "PDF 第 15 页", "id": "pdf-15" }, { "level": 3, "title": "获取文件的所有版本信息", "id": "section-34" }, { "level": 3, "title": "设置文件当前版本", "id": "section-36" }, { "level": 3, "title": "移动文件", "id": "section-38" }, { "level": 3, "title": "拷贝文件", "id": "section-40" }, { "level": 3, "title": "PDF 第 16 页", "id": "pdf-16" }, { "level": 3, "title": "拷贝文件进度", "id": "section-42" }, { "level": 3, "title": "文件日志", "id": "section-44" }, { "level": 3, "title": "设置用户是否有权访问素材库", "id": "section-46" }, { "level": 3, "title": "PDF 第 17 页", "id": "pdf-17" }, { "level": 3, "title": "创建素材库分类", "id": "section-48" }, { "level": 3, "title": "创建子素材库", "id": "section-50" }, { "level": 2, "title": "共享文件相关 API", "id": "api-4" }, { "level": 3, "title": "PDF 第 18 页", "id": "pdf-18" }, { "level": 3, "title": "获取文件的分享 url", "id": "url-12" }, { "level": 3, "title": "获取分享的权限列表", "id": "section-53" }, { "level": 3, "title": "获取用户对于单个文件有权设置的分享角色", "id": "section-55" }, { "level": 3, "title": "创建链接分享", "id": "section-57" }, { "level": 3, "title": "PDF 第 19 页", "id": "pdf-19" }, { "level": 3, "title": "关闭链接分享", "id": "section-59" }, { "level": 3, "title": "设置链接分享密码", "id": "section-61" }, { "level": 3, "title": "邀请人员参与分享", "id": "section-63" }, { "level": 3, "title": "PDF 第 20 页", "id": "pdf-20" }, { "level": 3, "title": "获取所有分享参与人", "id": "section-65" }, { "level": 3, "title": "设置分享参与人的权限角色", "id": "section-67" }, { "level": 3, "title": "删除分享参与人", "id": "section-69" }, { "level": 3, "title": "PDF 第 21 页", "id": "pdf-21" }, { "level": 3, "title": "提醒关注", "id": "section-71" }, { "level": 3, "title": "移除某人的关注", "id": "section-73" }, { "level": 3, "title": "获取关注文件的用户列表", "id": "section-75" }, { "level": 3, "title": "获取可以关注文件的用户列表，并且标记已关注文件的用户", "id": "section-77" }, { "level": 3, "title": "PDF 第 22 页", "id": "pdf-22" }, { "level": 2, "title": "企业部门相关 API", "id": "api-5" }, { "level": 3, "title": "获取当前企业信息", "id": "section-79" }, { "level": 3, "title": "获取企业所有部门信息", "id": "section-81" }, { "level": 3, "title": "创建企业部门", "id": "section-83" }, { "level": 3, "title": "PDF 第 23 页", "id": "pdf-23" }, { "level": 3, "title": "获取部门角色列表", "id": "section-85" }, { "level": 3, "title": "添加部门人员", "id": "section-87" }, { "level": 3, "title": "PDF 第 24 页", "id": "pdf-24" }, { "level": 3, "title": "删除部门人员", "id": "section-89" }, { "level": 3, "title": "获取自己所在部门信息", "id": "section-91" }, { "level": 3, "title": "获取部门人员", "id": "section-93" }, { "level": 3, "title": "PDF 第 25 页", "id": "pdf-25" }, { "level": 3, "title": "添加企业成员", "id": "section-95" }, { "level": 3, "title": "更新成员信息", "id": "section-96" }, { "level": 3, "title": "PDF 第 26 页", "id": "pdf-26" }, { "level": 3, "title": "获取企业成员信息", "id": "section-97" }, { "level": 3, "title": "获取企业所有成员", "id": "section-99" }, { "level": 3, "title": "获取企业日志", "id": "section-101" }, { "level": 3, "title": "PDF 第 27 页", "id": "pdf-27" }, { "level": 2, "title": "消息推送 API", "id": "api-6" }, { "level": 3, "title": "发布公告", "id": "section-103" }, { "level": 3, "title": "获取发布的公告", "id": "section-105" }, { "level": 3, "title": "发送部门讨论", "id": "section-107" }, { "level": 3, "title": "PDF 第 28 页", "id": "pdf-28" }, { "level": 3, "title": "获取部门讨论", "id": "section-109" }, { "level": 3, "title": "获取企业日志", "id": "section-111" }, { "level": 3, "title": "PDF 第 29 页", "id": "pdf-29" }, { "level": 2, "title": "四、 JWT token 登录", "id": "jwt-token" }, { "level": 3, "title": "PDF 第 30 页", "id": "pdf-30" }, { "level": 2, "title": "五、 附录 通用 API 调用返回状态码", "id": "api-7" }, { "level": 2, "title": "状态码 result code", "id": "result-code" } ], "images": [], "text": "文件 API PDF 第 1 页 企业开发 API V6.6 上海画擎信息科技有限公司 姜大军 PDF 第 2 页 目录 一、 获取企业开发账号 ..............................................................................................................................................................................4 二、 认证 API ............................................................................................................................................................................................. 6 认证接口一（登录回调方式） ................................................................................................................................................................6 认证接口二（免登录方式 – JWT token 方式，在私有云部署中，需要开启 jwt token 的登录方式） ....................................... 6 获取 token .................................................................................................................................................................................................8 刷新 token .................................................................................................................................................................................................8 三、 文件访问 API ..................................................................................................................................................................................... 8 获取文件列表 ............................................................................................................................................................................................9 获取文件信息 ............................................................................................................................................................................................9 创建文件夹 ..............................................................................................................................................................................................10 预上传文件 ..............................................................................................................................................................................................10 上传文件 ..................................................................................................................................................................................................11 获取下载文件地址 ..................................................................................................................................................................................12 获取下载多文件地址 ..............................................................................................................................................................................12 获取下载文件缩略图地址 ......................................................................................................................................................................13 修改文件信息 ..........................................................................................................................................................................................13 修改文件名 ..............................................................................................................................................................................................13 删除文件(到回收站） .............................................................................................................................................................................14 删除文件（从回收站） ..........................................................................................................................................................................14 清空回收站 ..............................................................................................................................................................................................14 恢复文件（从回收站） ..........................................................................................................................................................................14 获取文件的所有版本信息 ......................................................................................................................................................................15 设置文件当前版本 ..................................................................................................................................................................................15 移动文件 ..................................................................................................................................................................................................15 拷贝文件 ..................................................................................................................................................................................................15 拷贝文件进度 ..........................................................................................................................................................................................16 文件日志 ..................................................................................................................................................................................................16 创建素材库分类 ......................................................................................................................................................................................17 创建子素材库 ..........................................................................................................................................................................................17 共享文件相关 API ................................................................................................................................................................................. 17 获取文件的分享 url ................................................................................................................................................................................ 18 获取分享的权限列表 ..............................................................................................................................................................................18 获取用户对于单个文件有权设置的分享角色 ......................................................................................................................................18 创建链接分享 ..........................................................................................................................................................................................18 关闭链接分享 ..........................................................................................................................................................................................19 设置链接分享密码 ..................................................................................................................................................................................19 邀请人员参与分享 ..................................................................................................................................................................................19 获取所有分享参与人 ..............................................................................................................................................................................20 设置分享参与人的权限角色 ..................................................................................................................................................................20 删除分享参与人 ......................................................................................................................................................................................20 提醒关注 ..................................................................................................................................................................................................21 移除某人的关注 ......................................................................................................................................................................................21 获取关注文件的用户列表 ......................................................................................................................................................................21 获取可以关注文件的用户列表，并且标记已关注文件的用户 ..........................................................................................................21 企业部门相关 API ................................................................................................................................................................................. 22 获取当前企业信息 ..................................................................................................................................................................................22 获取企业所有部门信息 ..........................................................................................................................................................................22 创建企业部门 ..........................................................................................................................................................................................22 获取部门角色列表 ..................................................................................................................................................................................23 添加部门人员 ..........................................................................................................................................................................................23 删除部门人员 ..........................................................................................................................................................................................24 获取自己所在部门信息 ..........................................................................................................................................................................24 获取部门人员 ..........................................................................................................................................................................................24 添加企业成员 ..........................................................................................................................................................................................25 更新成员信息 ..........................................................................................................................................................................................25 获取企业成员信息 ..................................................................................................................................................................................26 获取企业所有成员 ..................................................................................................................................................................................26 获取企业日志 ..........................................................................................................................................................................................26 消息推送 API ......................................................................................................................................................................................... 27 发布公告 ..................................................................................................................................................................................................27 获取发布的公告 ......................................................................................................................................................................................27 发送部门讨论 ..........................................................................................................................................................................................27 获取部门讨论 ..........................................................................................................................................................................................28 获取企业日志 ..........................................................................................................................................................................................28 四、 JWT token 登录 .................................................................................................................................................................................29 五、 附录 通用 API 调用返回状态码 ............................................................................................................................................... 30 PDF 第 3 页 状态码 result code ................................................................................................................................................................................. 30 PDF 第 4 页 一、 获取企业开发账号 登录巴别鸟私有云企业管理后台，在首页中设置开发者账号： 打开后填写回调函数地址：http://xxx.xxx.xxx.xxx/public/babelAuthResult.do 填写后点击确定后自动产生开发者 id (client id)和开发者密钥(client secret)： 注：jwtToken 为相应的生成 jwtToken 时的加密密钥。 PDF 第 5 页 PDF 第 6 页 二、 认证 API 认证接口一（登录回调方式） /api/authorize.do HTTP 请求方式 GET URL 参数 参数名 Comment(说明) response type 必须为 code（必填） string client id 开发者的 id（必填） string redirect uri 回调函数地址，需要和注册时保持一致（必填） string data 任意数据，回调时传回 string 例如： /api/authorize.do?response type=code&client id=xxxxx&redirect uri=http://xxx.xxx.xxx&data=xxx 通过浏览器访问 返回结果 如果用户未登录，则会跳转到登录页，登录后如果未授权，则会 302 跳转到授权页，如果用户已经授权，则会 302 跳转到 redirect uri 并且带上授权码和 data，类似于 http://xxx.xxx.xxx?code=xxx&data=xxx code 有效期 5 分钟。 认证接口二（免登录方式 – JWT token 方式，在私有云部署中，需要开启 jwt token 的登录方 式） /api/authorizeByJWT.do HTTP 请求方式 GET URL 参数 参数名 Comment(说明) response type 必须为 code（必填） string client id 开发者的 id（必填） string jwt token Jwt token，（必填） string 是对{client id: xxxxxxx} 加密 形成的字符串 email email(可选), 传入用户的邮箱，以该用户进行登录，不填以企业管理员进行登录，string phone phone(可选), 传入用户的手机号，以该用户进行登录，不填以企业管理员进行登录， string babelId babelId(可选), 传入用户的工号，以该用户进行登录，不填以企业管理员进行登录， string PDF 第 7 页 例如： /api/authorizeByJWT.do?response type=code&client id=xxxxx&jwt token=xxx 说明：使用这个 api，如果不填 email, phone, babelId 系统将自动以管理员身份登录，否则会以 email, phone, babelId 对应的用户去 登录，不会显示登录界面去登录。注（email, phone, babelId）只需其中一个就可。 返回结果 { \"success\": true \"code\": \"xxxxxxxxxxxxxxxxxxxxxxxxx\", } jwt token 为 自己写程序生成 样例代码如下: import java.util.Date; import java.util.HashMap; import java.util.Map; import javax.crypto.SecretKey; import javax.crypto.spec.SecretKeySpec; import io.jsonwebtoken.Claims; import io.jsonwebtoken.JwtBuilder; import io.jsonwebtoken.Jwts; import io.jsonwebtoken.SignatureAlgorithm; import net.sf.json.JSONObject; / 生成标准 jwt 使用的 token / public class JWT App { static String skey = \"babeldfdfer95840834 t8e 9 9 5934 5943 5886256\"; // 密钥 在巴别鸟后台 开发者账号处 填入的 jwtToken 字段。 public static void main( String[] args ) { HashMap clientInfo = new HashMap (); clientInfo.put(\"client id\", \"7459492016147273\"); // 为开发者账户中的 client id try { String token = createTokenJWT(clientInfo); System.out.println(\" login token:\" + token); String token1 = \"eyJhbGciOiJIUzI1NiJ9.eyJkdXJhdGlvbiI6NjAsInBheWxvYWQiOnsiY2xpZW50X2lkIjoiNzQ1OTQ5MjAxNjE0NzI3MyJ9LCJ0aW1lIjoxNjkxNDg4MzY4NTk0fQ.pRFCwXd2snMr IgFWOFwYbvyAeeNhoFINGk Wmv7d24g\"; JSONObject parsed = parseTokenJWT(token1); System.out.println(\" parsed:\" + parsed); System.out.println(\" 将此 token 作为参数放在 url 中即可， 如:\"); } catch (Exception e) { System.out.println(e.getMessage()); } } public static String createTokenJWT(Map config) throws Exception { HashMap data = new HashMap (); data.put(\"time\", new Date().getTime()); data.put(\"duration\", 60); data.put(\"payload\", config); SignatureAlgorithm signatureAlgorithm = SignatureAlgorithm.HS256; SecretKey key = generalKey(); JwtBuilder builder = Jwts.builder() .setClaims(data) .signWith(signatureAlgorithm, key); System.out.println( \" builder :\" + builder); return builder.compact(); } public static JSONObject parseTokenJWT(String jwt) throws Exception { SecretKey key = generalKey(); Claims claims = Jwts.parser() .setSigningKey(key) .parseClaimsJws(jwt) .getBody(); System.out.println(\" claims:\" + claims.toString()); Long time = (Long)claims.get(\"time\"); long duration = (Integer)claims.get(\"duration\"); Long now = new Date().getTime(); if (now time 1000 duration) return null; // 超过 10 分钟的 token 无效 JSONObject obj = JSONObject.fromObject(claims.get(\"payload\")); return obj; } public static SecretKey generalKey(){ String stringKey = skey; byte[] encodedKey = stringKey.getBytes(); SecretKey key = new SecretKeySpec(encodedKey, 0, encodedKey.length, \"HmacSHA256\"); return key; } } PDF 第 8 页 获取 token /api/token.do HTTP 方法： POST HTTP Header 该接口使用 Basic Auth 的方式校验 client 的信息。具体做法是在 header 中添加类似于\"Authorization: Basic xxxxxxxxx\"。其中 \"xxxxxxxxx\"是通过开发者 id (client id)和开发者秘钥(client secret)算出来的，具体算法为 Base64Encode(client id + \":\" + client secret) Base64Encode 自行选择工具进行 Base64 编码 URL 参数 参数名 Comment(说明) grant type（必填） 必须为 authorization code string code（必填） 授权码，即回调地址接收到的授权码，授权码的有效期为 5 分钟，用过一次，无论成功 还是失败，授权码都会失效 string 例如： /api/token.do?grant type=authorization code&code=xxx&redirect uri=http://xxx.xxx.xxx 返回结果 access token 接口访问标识 refresh token 用来刷新 access token，有效时间为 30 天 expires in access token 的有效时间，单位为 s 刷新 token /api/refreshToken.do HTTP 方法： POST HTTP Header 该接口使用 Basic Auth 的方式校验 client 的信息。具体做法是在 header 中添加类似于\"Authorization: Basic xxxxxxxxx\"。其中 \"xxxxxxxxx\"是通过 client id 和 client secret 算出来的，具体算法为 Base64Encode(client id + \":\" + client secret) URL 参数 参数名 Comment(说明) grant type（必填） 必须为 refresh token string refresh token（必填） 即接口 2 中获取到的 refresh token string 例如： /api/refreshToken.do?grant type=refresh token&refresh token=xxx 返回结果 access token 接口访问标识, refresh token 用来刷新 access token，有效时间为 30 天 expires in access token 的有效时间 为 3600，单位为 s 三、 文件访问 API 所有的接口在访问时需要在 HTTP header 中带上 access token。对于含有请求参数的接口，通常是一些 POST、 PUT 或者 DELETE 接口，还需要设置 Content Type 来指定参数的格式。如果需要访问不同版本的 API，就需要 在请求路径上指定具体版本，如果需要返回不同格式的 response body，那么还需要设置 Accept。所有的参数都应 该采用 utf 8 的编码。 PDF 第 9 页 Headers： Authorization：存放 access token，格式为：\"Bearer \" + access token。 Content Type：指明请求参数的格式。如果是 POST、PUT 或者 DELETE 请求，需要指定\"application/json\"，我 们目前不支持其他请求参数的格式，比如 xml。如果是其他类型比如 GET 请求，可以不在 header 中设置 Content Type。 Accept：用于指定响应结果的格式以及 api 的版本信息。目前只支持返回 json 格式的 response，所以一般情况下 指定\"application/json\"。 若接口访问成功，我们会返回 json 格式的 response，并且 HTTP 的 status code 为 200。所有请求成功的 response 的 json 都会带有\"success: true”。response 的 header 里的 X Babel Version 表示此次请求访问的 api 的版本号。 获取文件列表 /nd/api/file/list dir HTTP 方法： GET URL 参数 参数名 Comment(说明) parent id 父文件夹 id（必填） string 当 parent 为 1 时返回企业文件夹内容，2 返回个人文件夹内容，3 返回我的 项目，4 返回我加入的分享，其它 fileId 返回正常的文件夹中的内容。 page size 页的大小 number page 页号 number type 类型：分为 1 file，2 folder，0 all 三种类型 string 返回字段说明 属性名 类型 说明 files 数组 文件信息 {fileId, name, …} total int 总数量 page int 页容量 success boolean 获取成功标记 code int 返回错误码 0 表示成功 获取文件信息 /nd/api/file/fileinfo HTTP 方法： GET URL 参数 参数名 Comment(说明) id 文件 id（必填） string 返回字段说明 fileInfo 信息 属性名 类型 说明 file Object 文件信息 { id, name, …} PDF 第 10 页 success boolean 获取成功标记 code int 返回错误码 0 表示成功 创建文件夹 /nd/api/file/create folder HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) parent id 目标文件夹 id（必填） string name 文件名（必填） string 返回字段说明 属性名 类型 说明 file Object 文件信息 { id, name, …} success boolean 获取成功标记 code int 返回错误码 0 表示成功 预上传文件 用于返回第二步上传文件时所需要的参数(url、upload token) /api/file/preUploadFile.do HTTP 方法： GET URL 参数 参数名 Comment(说明) parent id 目标文件夹 id（必填）(在根目录下上传可忽略此项) string name 文件名（必填） string file id 上传新版本时需要指定上传那个文件的新版本(上传新文件可忽略此项) string 正确的返回结果如下 {\"upload token\":\"92808ecfc2ac4e0ebc0b912edac3be4a\",\"url\":\"http://testdocument.babel.cc/api/file/uploadPdf.do\",\"su ccess\":true,\"code\":0} 返回字段说明 属性名 类型 说明 url string 该 url 仅能使用 1 次，且有效期为 1 小时 调用此 url 上传文件，成功后会返回 fileId， fileName、version 等 upload token string 上传文件时作为 post 的参数 PDF 第 11 页 上传文件 注意，本 api 的 url 是预上传接口返回的, 这里没有具体的 url，只是参数说明 https://xxx.xxx.xxx:xxx/api/file/uploadXXX.do（具体的 url 是由上一节 /api/file/preUploadFile.do 中返回的 url） POST POST 请求体参数 参数名 Comment(说明) file 文件二进制数据(上传数据) upload token /api/file/preUploadFile.do 请求中的返回值 返回信息如下 {\"fileId\":\"7728538212615908\",\"version\":0,\"fileName\":\"mesos.pdf\",\"fileSize\":848854,\"success\":true,\"code\":0} 上传相关代码 示例 加入 ‘com.squareup.okhttp3:okhttp:3.3.1’ 包 private void uploadFile(final String fileName, String parentId, final DaoCallback callback){ preUploadFile(fileName, parentId, new DaoCallback () { @Override public void onSuccess(JSONObject data) { int code = data.optInt(\"code\", 1); final String url = data.optString(\"url\", null); final String uploadToken = data.optString(\"upload token\"); if (code == 0) { // File file = new File(filePath); RequestBody fileContent = RequestBody.create(MultipartBody.FORM, file); RequestBody requestBody = new MultipartBody.Builder() .setType(MultipartBody.FORM) .addFormDataPart(\"file\", fileName, fileContent) .addFormDataPart(\"upload token\", uploadToken) .build(); Request request = new Request.Builder() .url(url) .post(requestBody) .build(); // 上传需要较长的时间，因此需要设置较长的 timeout OkHttpClient okHttpClient = new OkHttpClient(); okHttpClient.newCall(request) .enqueue(new okhttp3.Callback() { @Override public void onFailure(okhttp3.Call call, IOException e) { callback.onFailure( 1, null); } @Override public void onResponse(okhttp3.Call call, okhttp3.Response response) throws IOException { int httpCode = response.code(); if (httpCode == 200) { try { JSONObject result = new JSONObject(response.body().string()); response.body().close(); boolean success = result.getBoolean(\"success\"); if (success) { callback.onSuccess(null); } else { int code = result.getInt(\"code\"); String msg = result.optString(\"msg\"); callback.onFailure(code, msg); } } catch (JSONException e) { callback.onFailure( 2, null); } } else { callback.onFailure(httpCode, null); } } }); } } @Override public void onFailure( int errorCode, String msg){ Log.e(\"FileTransfer\", \"filePreUpload 失败 errorCode=\" + errorCode); } }); } PDF 第 12 页 private void preUploadFile(String fileName, String parentId, final DaoCallback callback) { String preUploadUrl = \"http://private.babel.cc:80/api/file/preUploadFile.do?name=1234.jpg&parent id=0\"; // 传入相应的参数 name, parent id String authorization = \"Bearer d48d0a0e253c4a2985d8c5653f717d71\"; //根据说明 生成 Request request = new Request.Builder().url(preUploadUrl) .addHeader(\"Authorization\", authorization) .build(); OkHttpClient okHttpClient = new OkHttpClient(); okHttpClient.newCall(request).enqueue(new okhttp3.Callback() { @Override public void onFailure(okhttp3.Call call, IOException e) { Log.d(\"\", \"\"); } @Override public void onResponse(okhttp3.Call call, okhttp3.Response response) throws IOException { Log.d(\"\",\"\"); int httpCode = response.code(); if (httpCode == 200) { JSONObject result = null; try { result = new JSONObject(response.body().string()); } catch (JSONException e) { e.printStackTrace(); } try { boolean success = result.getBoolean(\"success\"); if (success) { String url = result.getString(\"url\"); callback.onSuccess(result); } else { int code = result.getInt(\"code\"); String msg = result.optString(\"msg\"); callback.onFailure(code, msg); } } catch (JSONException e) { callback.onFailure( 2, null); } } else { callback.onFailure(httpCode, null); } } }); } 获取下载文件地址 /api/file/getFileDownloadUrl.do HTTP 方法： GET URL 参数 参数名 Comment(说明) fileId 需要下载的文件 id（必填） string version 文件的版本号（可选） number 返回信息如下 {\"code\":0,\"success\":true,\"type\":\"文件类型\",\"url\":\"文件下载地址\"} 获取下载多文件地址 /api/file/downloadMultiFiles.do HTTP 方法： GET URL 参数 参数名 Comment(说明) fileIdArr 由需要下载的文件 id 组成的字符串，由符号“!“(半角)分割，比如下载 id 为 133 与 233 的两 个文件，则 fileIdArr 的值为“133!233” string 类型 PDF 第 13 页 返回信息如下 {\"code\":0,\"success\":true,\"type\":\"文件类型\",\"url\":\"文件下载地址\"} 返回值 url 为多个文件打包后的下载地址。 获取下载文件缩略图地址 /api/file/downloadThumbnail.do HTTP 方法： GET URL 参数 参数名 Comment(说明) fileId 需要下载的文件 id（必填） string version 文件的版本号（可选） number size 需要显示的缩略图尺寸，取宽高中的最大值 返回信息如下 {\"code\":0,\"success\":true, \"url\":\"文件下载地址\"} 返回值 url 为多个文件打包后的下载地址。 修改文件信息 /nd /api/file/update file HTTP 方法： POST 修改文件信息 POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填） string name 新文件名 （可选） string description 文件说明 （可选） string 返回信息如下 {\"code\":0,\"success\":true} 修改文件名 /nd /api/file/rename HTTP 方法： POST 修改文件信息 POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填） string name 新文件名 string 返回信息如下 {\"code\":0,\"success\":true} PDF 第 14 页 删除文件(到回收站） /nd /api/file/remove file HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file ids[] 目标文件 id 数组（必填） string[] 返回信息如下 {\"code\":0,\"success\":true} 删除文件（从回收站） /nd /api/file/remove from trash HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file ids[] 目标文件 id 数组（必填） string[] 返回信息如下 {\"code\":0,\"success\":true} 清空回收站 /nd /api/file/empty trash HTTP 方法： POST POST 请求体参数 参数名 说明 返回信息如下 {\"code\":0,\"success\":true} 恢复文件（从回收站） /nd /api/file/restore file HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file ids[] 目标文件 id 数组 string[] restoreAll 不填写 file ids, restoreAll 为 true，时恢复回收站中所有文件，boolean 返回信息如下 PDF 第 15 页 {\"code\":0,\"success\":true} 获取文件的所有版本信息 /nd /api/file/versions HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 目标文件 id（必填） string 返回信息如下 {\"code\":0,\"versions\":[],\"success\":true} 设置文件当前版本 /nd /api/file/version HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file id 目标文件 id （必填） string version 版本号（必填） number 返回信息如下 {\"code\":0,\"success\":true} 移动文件 /nd /api/file/move HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file ids 需要移动的目标文件 id 数组（必填） string target id 需要移动到的目标文件夹 id（必填） string 返回信息如下 {\"code\":0,\"success\":true} 拷贝文件 /nd /api/file/copy HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) PDF 第 16 页 file ids 需要拷贝的目标文件 id 数组（必填） string target id 需要拷贝到的目标文件夹 id（必填） string 返回信息如下 { \"code\": 0, \"copyKey\": \"81427630 054a 11ef 8355 db93b4b1d006\",\"fileNum\": 10, \"success\": true} 拷贝文件进度 /nd /api/file/copy progress HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) copyKey 查看拷贝进度 copyKey 由 copy 接口返回（必填） string 返回信息如下 { \"code\": 0, \"completed\": 10,\"total\": 10, \"result\": {}, \"success\": true} 文件日志 /nd /api/file/file logs HTTP 方法： GET GET 请求体参数 参数名 Comment(说明) file id 目标文件 id 数组（必填） string startIndex 获取日志的起始顺序 第几条日志开始返回（选填） int 默认 0， pageSize 每页返回的个数（选填） int type 日志类型(选填) int 默认 0, 查看所有记录， 1 仅查看访问记录，2 仅查看上传下载，3 仅查看匿名用 户，4 仅查看分享及邀请，5 仅查看删除记录 userName 某个用户名 (选填) string, 返回某个用户的日志 lang 语言(选填) 默认 cn, string 返回日志的语言 cn(中文) en(英文) 返回信息如下 {\"code\":0,\"success\":true, \"logs\":[], \"total\":50} 设置用户是否有权访问素材库 /nd /api/file/ set user access material library HTTP 方法： POST GET 请求体参数 参数名 Comment(说明) userId 用户的 id 数组数型 [usrId1, userId2]（必填） string can 是否可访问 数值类型 （必填） int 默认 0， 0： 不可访问， 1:可以访问 返回信息如下 {\"code\":0,\"success\":true} PDF 第 17 页 创建素材库分类 /nd /api/file/create material class HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) destDirFileId 目标文件夹 的 fileId（必填） string name 创建分类库的名称（必填） string accessType 分类可见性 (选填) 默认为公开 0. 0: // 公开 1: // 需要申请 2: // 部门公开 3: // 部门申请 4: // 保密 managerIds 负责人的 id 数组类型 [usrId1,userId2] departmentIds 分类可见性 限定部门 的部门 id (选填) 数组类型 [departmentId1,departmentId2] 返回信息如下 {\"code\":0, \"success\":true, \"materialClass\": {}} 创建子素材库 /nd /api/file/create material folder HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) destDirFileId 目标文件夹 的 fileId（必填） string name 创建分类库的名称（必填） string accessType 分类可见性 (选填) 默认为公开 0. 0: // 公开 1: // 需要申请 2: // 部门公开 3: // 部门申请 4: // 保密 managerId 负责人的 id (选填) string departmentIds 分类可见性 限定部门 的部门 id (选填) 数组类型 [departmentId1,departmentId2] assistantIds 素材库助理人员的 id （选填） 数组类型 [usrId1,userId2] 返回信息如下 {\"code\":0, \"success\":true, \"materialFolder\": {}} 共享文件相关 API PDF 第 18 页 获取文件的分享 url /nd/api/share/shareurl HTTP 方法： GET 获取文件的分享链接（先打开分享后，再获取该链接） URL 参数 参数名 Comment(说明) file id 文件 id string is https 返回的 share url 协议是否为 https 0 为 http, 1 为 https， 默认 0 number 返回字段说明 {\"code\":0,\"url\":\"https://private.babel.cc/share.do?s=http://private.babel.cc/share.do?s=MjY2OTYzNTk3OTU2NzEzOTtXZWQgSnVsIDAxIDIwMj AgMTg6MzM6NTAgR01UKzA4MDAgKEhvbmcgS29uZyBTdGFuZGFyZCBUaW1lKQ%3D%3D\",\"success\":true} 获取分享的权限列表 /nd/api/share/share roles HTTP 方法： GET URL 参数 参数名 Comment(说明) 返回字段说明 {\"code\":0,\"roles\":[],\"success\":true} 获取用户对于单个文件有权设置的分享角色 /nd/api/share/share role forfile HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 文件 id string 返回字段说明 {\"code\":0,\"roles\":[],\"success\":true} 创建链接分享 /nd/api/share/open link share HTTP 方法： POST 打开分享，获取新的分享链接，之前的链接失效。 PDF 第 19 页 POST 请求体参数 参数名 Comment(说明) file id 预分享的文件 id（必填） string link role id 分享的角色 string is https 返回的 share url 协议是否为 https number anonymousVisit 是否允许匿名访问，1 为允许，0 为不允许（可选，默认为 1） number 返回字段说明 {\"code\":0,\"share url\":\"http://private.babel.cc/share.do?s=http://private.babel.cc/share.do?s=MjY2OTYzNTk3OTU2NzEzOTtXZWQgSnV sIDAxIDIwMjAgMTg6MzM6NTAgR01UKzA4MDAgKEhvbmcgS29uZyBTdGFuZGFyZCBUaW1lKQ%3D%3D\",\"password\":\"\",\"success\":tru e} 关闭链接分享 /nd/api/share/close link share HTTP 方法： POST 关闭我打开的分享链接 POST 请求体参数 参数名 Comment(说明) file id 分享的文件 id（必填） string 返回字段说明 {\"code\":0,\"success\":true} 设置链接分享密码 /nd/api/share/set share password HTTP 方法： POST 文件链接分享已打开，设置链接分享的密码。 POST 请求体参数 参数名 Comment(说明) file id 预分享的文件 id（必填） string password 链接分享的密码 string is https 返回的 share url 协议是否为 https number 返回字段说明 {\"code\":0,\"success\":true, \"share url\": \"http://private.babel.cc/share.do?s=xxxxxxxxxxx\"} 邀请人员参与分享 /nd/api/share/invite share HTTP 方法： POST PDF 第 20 页 可以根据用户的邮箱或者手机来邀请某些人来访问文件 POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填） string share role 分享的权限的 id（以上所有人共享此权限）（必填） string emails[] 邮箱数组 string[] phones[] 手机号的数组 string[] 返回字段说明 {\"code\":0,\"success\":true} 获取所有分享参与人 /nd/api/share/share participants HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 文件 id（必填） string 返回字段说明 {\"code\":0,\"users\":[],\"success\":true} 设置分享参与人的权限角色 /nd/api/share/set participant role HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填） string babelshare id int（必填） 用户 id string role id int（必填） 角色 id string 返回字段说明 {\"code\":0,\"success\":true} 删除分享参与人 /nd/api/file/remove share participant HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) PDF 第 21 页 file id 文件 id（必填） string babelshare ids[] int （必填） 用户 id string 返回字段说明 {\"code\":0,\"success\":true} 提醒关注 /nd/api/file/focus file HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填） string user ids[] 提醒的用户的 id，此 id 应该在文件参与人中选取，否则提醒不会起作用（必填）string[] 返回字段说明 {\"code\":0,\"success\":true} 移除某人的关注 /nd/api/file/unfocus file HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填）string user ids[] 提醒的用户的 id，此 id 应该在文件参与人中选取，否则提醒不会起作用（必填） string[] 返回字段说明 {\"code\":0,\"success\":true} 获取关注文件的用户列表 /nd/api/file/user focusfile HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 文件 id（必填） string 返回字段说明 {\"code\":0,\"users\":[],\"success\":true} 获取可以关注文件的用户列表，并且标记已关注文件的用户 /nd/api/file/user can focusfile PDF 第 22 页 HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 文件 id（必填） string 返回字段说明 企业部门相关 API 获取当前企业信息 /nd/api/enterprise/current HTTP 方法： GET URL 参数 参数名 Comment(说明) 无 返回字段说明 {\"code\":0,\"enterprise\":{},\"success\":true} 获取企业所有部门信息 /nd/api/enterprise/departments HTTP 方法： GET URL 参数 参数名 Comment(说明) 无 返回字段说明 属性名 类型 说明 departments []数组 返回所有的部门信息 tree {}json 数据 返回部门的父子结构信息 code int sucess boolean 创建企业部门 /nd/api/enterprise/create department HTTP 方法： POST PDF 第 23 页 POST 请求体参数 参数名 Comment(说明) parent dep 父部门 id， 0 表示跟部门（必填）string name 部门名称（必填）string description 部门描述 string 返回字段说明 属性名 类型 说明 department {} json 数据结构 code int sucess boolean 获取部门角色列表 /nd/api/enterprise/dep role HTTP 方法： GET URL 参数 参数名 Comment(说明) 返回字段说明 属性名 类型 说明 roles []数组 { id, filePermission,enterpriseId,filePermission,managerPermission, default,nameEn,name} code int sucess boolean 添加部门人员 /nd/api/enterprise/add dep mem HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) department id 部门 id（必填）string user ids[] 用户列表 string[] role id 用户在部门中的角色 string PDF 第 24 页 返回字段说明 属性名 类型 说明 删除部门人员 /nd/api/enterprise/remove dep mem HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) department id 部门 id（必填）string user ids[] 人员的 id（必填）string[] 返回字段说明 属性名 类型 说明 获取自己所在部门信息 /nd/api/enterprise/mydeparments HTTP 方法： GET URL 参数 参数名 Comment(说明) 无 返回字段说明 属性名 类型 说明 departments []数组 返回我所在的部门信息 code int sucess boolean 获取部门人员 /nd/api/enterprise/departmentmembers PDF 第 25 页 HTTP 方法： GET URL 参数 参数名 Comment(说明) department id 部门 id（必填）string 返回字段说明 属性名 类型 说明 users 数组 ： {id, name, avatrUrl,} 添加企业成员 /nd/api/enterprise/add ent mem HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) email Email 邮箱 string password 密码 string enterprise role 企业成员角色, 可选 number department ids[] 该用户的部门， 可选 string[] department roles[] 在部门中的角色， 可选 string[] sex 性别 0 未设置 1 男 2 女 number name 用户名 string phone 手机号， 可选 string babelId 工号，可选 string spacelimit 个人空间限制，单位 GB, 0 表示不限制 number can ownfile 用户能否拥有个人文件， 1 使用企业总体设置, 0 没有个人文件, 1 有个人文件 number remarks 用户描述， 可选 string join time 用户加入企业时间，Unix time, 单位秒 number password is md5 传入密码是否需要 md5 加密, 0 非 md5 密码， 1 md5 加密过的密码 number 更新成员信息 /api/updateUserInfo.do HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) email 邮箱地址（搜索关键字，必须）string password 密码（修改密码，可选）string frozen 1 – 表示冻结， 0 – 表示解冻 （冻结该账号，可选）number password is md5 传入密码是否需要 md5 加密, 0 非 md5 密码， 1 md5 加密过的密码 number phone 手机号 (可选) string PDF 第 26 页 获取企业成员信息 /api/getEnterpriseMember.do HTTP 方法： GET URL 参数 参数名 Comment(说明) email 邮箱地址（搜索关键字）string phone 手机号（搜索关键字）string babelId 工号（搜索关键字）string email/phone/babelId 可选择其一 返回字段说明 {\"code\":0,\"success\":true,\"user\":{}} 获取企业所有成员 /nd/api/enterprise/enterprise members HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) lang 语言类型，cn 中文 ，en 英文 , 可选 options { departmentId: // 部门 id，不填写就是企业所有人员 roleId: // 角色 id， 不填写就是不限角色 \"userType\": 0, // 0 企业内人员， 1 外部人员 \"keyName\": \"\", // 搜索关键字： 人名，手机号，邮箱， 不填写就是所有人员 \"startIndex\": 0， \"pageSize\": 20, status: // 0 所有账号， 1 停用的账号 } 可选 返回字段说明 {\"code\":0,\"success\":true,\"members\":{},\"total\":xx} 获取企业日志 /nd/api/enterprise/enterprise logs HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) department id 部门 id，不填写就是所有部门的日志 string 可选 keyword 日志的相关搜索关键字 string 可选 PDF 第 27 页 startTime 日志起始时间 number 可选 endTime 日志截止时间 number 可选 startIndex int 可选 pageSize int 可选 返回字段说明 {\"code\":0,\"success\":true,\"logs\":{},\"total\":xx} 消息推送 API 发布公告 /nd/api/enterprise/broadcast HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) title 公告内容字符串（必填） string content 内容（必填）string target users[] UserId 数组，如果为空则表示全部人员接收，string[] target deps[] 目标部门，该部门及子部门所有成员都会收到通知，string[] target users 与 target deps 至少要填 1 个 返回字段说明 {\"code\":0,\"success\":true} 获取发布的公告 /nd/api/enterprise/broadcast HTTP 方法： GET URL 参数 参数名 Comment(说明) start index number pagesize number 返回字段说明 {\"code\":0,\"broadcasts\":[],\"total\":19,\"success\":true} 发送部门讨论 /nd/api/file/send dep discussion HTTP 方法： POST PDF 第 28 页 POST 请求体参数 参数名 Comment(说明) dep id 部门 id（必填） string message 信息字符（必填） string json 字符串, 格式{Type: “Text”, Body:”你好” } 返回字段说明 {\"code\":0,\"messageId\":99,\"success\":true} 获取部门讨论 /nd/api/file/dep discussion HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) dep id 部门 id（必填）string pagesize 页的大小 string start id 消息 id,只会获取此消息之前的消息，为空则获取最新消息 string 返回字段说明 {\"msgArr\":[],\"gotMoreMessages\":1,\"code\":0,\"success\":true} 获取企业日志 /nd/api/enterprise/enterprise logs HTTP 方法： GET URL 参数 参数名 Comment(说明) department id 部门 id（）string pagesize 页的大小 number，默认值 1000 start index 消息起始位置, number keyword 日志关键词 string startTime 起始日期: 秒 number endTime 截止日期 秒 number 返回字段说明 {\"logs\":[],\"total\":0,\"code\":0,\"success\":true} total 返回所有符合条件的(与分页 pageSize 无关) PDF 第 29 页 四、 JWT token 登录 在私有云部署中，可以开启 jwt token 的登录方式，在这种情况下，允许通过下面的 url 直接以某用户的身份免登录进入网盘系 统： /account/tokenLogin.do 参数： 参数名称 可选性 说明 可选值 默认值 userToken 必填 含有登录用户的加密信息（构造方 无 法详见下面的说明） fileId 可选 要访问的文件（夹）的 id，如果不 无 填写则打开用户根目录 closeTitleBar 可选 是否关闭标题栏 1 关闭 0 不关闭 0 disableEntMark 可选 是否隐藏左上角企业标识 1 隐藏 0 不隐藏 0 disableUserMark 可选 是否隐藏右上角用户设置入口 1 隐藏 0 不隐藏 0 defaultLang 可选 设置界面使用的语言 cn 中文 en 英文 zh HK 繁体 cn defaultClrTheme 可选 设置界面颜色主题 normal 标准模式，dark 暗色模式 normal 比如下面是以英文及暗色模式并隐藏右上角用户标志进入用户根目录界面 /account/tokenLogin.do userToken=xxxxxxxxxxxxxxxx defaultClrTheme=dark defaultLang=en disableUserMark=1 userToken 的构建 userToken 是含有登录用户信息的加密字符串，加密信息是通过标准的双方传输可信数据的安全机制 JWT 创建的口令字， JWT 加密的用户信息 JSONObject 内容如下： { payload: { email: “xxx@xxx.com”/“135XXXXXXX”/“XXXX”} time: now } 说明：其中 email, 可以是邮箱，手机号，工号； 代码如下： public static void main( String[] args ) { HashMap user = new HashMap (); user.put(\"email\", \"yuanchaozhao@qq.com\"); try { //token login String userToken = createTokenJWT(user); System.out.println(\" login token:\" + userToken); JSONObject parsed = parseTokenJWT(userToken); System.out.println(\" parsed:\" + parsed); System.out.println(\" 将此 token 作为参数放在 url 中即可， 如:\"); System.out.println(\"/account/tokenLogin.do?userToken=\" + userToken); } catch (Exception e) { System.out.println(e.getMessage()); } } 其它代码 参考 jwtToken 的生成代码，在认证接口二处有提供。 备注： JWT 即 JSON Web Tokens 的简写， 是满足工业标准 RFC7519 的一种通信加密解密机制，请参考： https://jwt.io/ PDF 第 30 页 五、 附录 通用 API 调用返回状态码 状态码 result code 码值 说明 0 成功 1 未知错误 2 参数错误 7 空间不足 12 禁止的用户操作 13 无效的 token 结束 the end" }, { "lang": "zh", "slug": "developer-api-sharing", "title": "分享 API", "description": "分享 API 的接口路径、方法、参数和返回字段。", "category": "分享 API", "top_category": "API文档", "keywords": [ "API", "分享 API", "开发者" ], "url": "zh/developer-api-sharing.html", "source": "content/zh/developer-api-sharing.md", "summary": "分享 API PDF 第 1 页 企业开发 API V6.6 上海画擎信息科技有限公司 姜大军 PDF 第 2 页 目录 一、 获取企业开发账号 ..............................................................................................................................................................................4 二、 认证 API ............................................................................................................................................................................................. 6 认证接口一（登录回调方式） ................................................................................................................................................................6 认证接口二（免登录方式 – JWT token 方式，在私有云部署中，需要开启 jwt token 的登录方式） ................", "headings": [ { "level": 1, "title": "分享 API", "id": "api" }, { "level": 3, "title": "PDF 第 1 页", "id": "pdf-1" }, { "level": 3, "title": "PDF 第 2 页", "id": "pdf-2" }, { "level": 3, "title": "PDF 第 3 页", "id": "pdf-3" }, { "level": 3, "title": "PDF 第 4 页", "id": "pdf-4" }, { "level": 2, "title": "一、 获取企业开发账号", "id": "section" }, { "level": 3, "title": "PDF 第 5 页", "id": "pdf-5" }, { "level": 3, "title": "PDF 第 6 页", "id": "pdf-6" }, { "level": 2, "title": "二、 认证 API", "id": "api-2" }, { "level": 3, "title": "认证接口一（登录回调方式）", "id": "section-2" }, { "level": 3, "title": "PDF 第 7 页", "id": "pdf-7" }, { "level": 3, "title": "PDF 第 8 页", "id": "pdf-8" }, { "level": 3, "title": "获取 token", "id": "token" }, { "level": 3, "title": "刷新 token", "id": "token-2" }, { "level": 2, "title": "三、 文件访问 API", "id": "api-3" }, { "level": 3, "title": "PDF 第 9 页", "id": "pdf-9" }, { "level": 3, "title": "获取文件列表", "id": "section-3" }, { "level": 3, "title": "获取文件信息", "id": "section-5" }, { "level": 3, "title": "PDF 第 10 页", "id": "pdf-10" }, { "level": 3, "title": "创建文件夹", "id": "section-7" }, { "level": 3, "title": "预上传文件", "id": "section-9" }, { "level": 3, "title": "PDF 第 11 页", "id": "pdf-11" }, { "level": 3, "title": "上传文件", "id": "section-12" }, { "level": 3, "title": "PDF 第 12 页", "id": "pdf-12" }, { "level": 3, "title": "获取下载文件地址", "id": "section-14" }, { "level": 3, "title": "获取下载多文件地址", "id": "section-16" }, { "level": 3, "title": "PDF 第 13 页", "id": "pdf-13" }, { "level": 3, "title": "获取下载文件缩略图地址", "id": "section-18" }, { "level": 3, "title": "修改文件信息", "id": "section-20" }, { "level": 3, "title": "修改文件信息", "id": "section-21" }, { "level": 3, "title": "修改文件名", "id": "section-23" }, { "level": 3, "title": "修改文件信息", "id": "section-24" }, { "level": 3, "title": "PDF 第 14 页", "id": "pdf-14" }, { "level": 3, "title": "删除文件(到回收站）", "id": "section-26" }, { "level": 3, "title": "删除文件（从回收站）", "id": "section-28" }, { "level": 3, "title": "清空回收站", "id": "section-30" }, { "level": 3, "title": "恢复文件（从回收站）", "id": "section-32" }, { "level": 3, "title": "PDF 第 15 页", "id": "pdf-15" }, { "level": 3, "title": "获取文件的所有版本信息", "id": "section-34" }, { "level": 3, "title": "设置文件当前版本", "id": "section-36" }, { "level": 3, "title": "移动文件", "id": "section-38" }, { "level": 3, "title": "拷贝文件", "id": "section-40" }, { "level": 3, "title": "PDF 第 16 页", "id": "pdf-16" }, { "level": 3, "title": "拷贝文件进度", "id": "section-42" }, { "level": 3, "title": "文件日志", "id": "section-44" }, { "level": 3, "title": "设置用户是否有权访问素材库", "id": "section-46" }, { "level": 3, "title": "PDF 第 17 页", "id": "pdf-17" }, { "level": 3, "title": "创建素材库分类", "id": "section-48" }, { "level": 3, "title": "创建子素材库", "id": "section-50" }, { "level": 2, "title": "共享文件相关 API", "id": "api-4" }, { "level": 3, "title": "PDF 第 18 页", "id": "pdf-18" }, { "level": 3, "title": "获取文件的分享 url", "id": "url-12" }, { "level": 3, "title": "获取分享的权限列表", "id": "section-53" }, { "level": 3, "title": "获取用户对于单个文件有权设置的分享角色", "id": "section-55" }, { "level": 3, "title": "创建链接分享", "id": "section-57" }, { "level": 3, "title": "PDF 第 19 页", "id": "pdf-19" }, { "level": 3, "title": "关闭链接分享", "id": "section-59" }, { "level": 3, "title": "设置链接分享密码", "id": "section-61" }, { "level": 3, "title": "邀请人员参与分享", "id": "section-63" }, { "level": 3, "title": "PDF 第 20 页", "id": "pdf-20" }, { "level": 3, "title": "获取所有分享参与人", "id": "section-65" }, { "level": 3, "title": "设置分享参与人的权限角色", "id": "section-67" }, { "level": 3, "title": "删除分享参与人", "id": "section-69" }, { "level": 3, "title": "PDF 第 21 页", "id": "pdf-21" }, { "level": 3, "title": "提醒关注", "id": "section-71" }, { "level": 3, "title": "移除某人的关注", "id": "section-73" }, { "level": 3, "title": "获取关注文件的用户列表", "id": "section-75" }, { "level": 3, "title": "获取可以关注文件的用户列表，并且标记已关注文件的用户", "id": "section-77" }, { "level": 3, "title": "PDF 第 22 页", "id": "pdf-22" }, { "level": 2, "title": "企业部门相关 API", "id": "api-5" }, { "level": 3, "title": "获取当前企业信息", "id": "section-79" }, { "level": 3, "title": "获取企业所有部门信息", "id": "section-81" }, { "level": 3, "title": "创建企业部门", "id": "section-83" }, { "level": 3, "title": "PDF 第 23 页", "id": "pdf-23" }, { "level": 3, "title": "获取部门角色列表", "id": "section-85" }, { "level": 3, "title": "添加部门人员", "id": "section-87" }, { "level": 3, "title": "PDF 第 24 页", "id": "pdf-24" }, { "level": 3, "title": "删除部门人员", "id": "section-89" }, { "level": 3, "title": "获取自己所在部门信息", "id": "section-91" }, { "level": 3, "title": "获取部门人员", "id": "section-93" }, { "level": 3, "title": "PDF 第 25 页", "id": "pdf-25" }, { "level": 3, "title": "添加企业成员", "id": "section-95" }, { "level": 3, "title": "更新成员信息", "id": "section-96" }, { "level": 3, "title": "PDF 第 26 页", "id": "pdf-26" }, { "level": 3, "title": "获取企业成员信息", "id": "section-97" }, { "level": 3, "title": "获取企业所有成员", "id": "section-99" }, { "level": 3, "title": "获取企业日志", "id": "section-101" }, { "level": 3, "title": "PDF 第 27 页", "id": "pdf-27" }, { "level": 2, "title": "消息推送 API", "id": "api-6" }, { "level": 3, "title": "发布公告", "id": "section-103" }, { "level": 3, "title": "获取发布的公告", "id": "section-105" }, { "level": 3, "title": "发送部门讨论", "id": "section-107" }, { "level": 3, "title": "PDF 第 28 页", "id": "pdf-28" }, { "level": 3, "title": "获取部门讨论", "id": "section-109" }, { "level": 3, "title": "获取企业日志", "id": "section-111" }, { "level": 3, "title": "PDF 第 29 页", "id": "pdf-29" }, { "level": 2, "title": "四、 JWT token 登录", "id": "jwt-token" }, { "level": 3, "title": "PDF 第 30 页", "id": "pdf-30" }, { "level": 2, "title": "五、 附录 通用 API 调用返回状态码", "id": "api-7" }, { "level": 2, "title": "状态码 result code", "id": "result-code" } ], "images": [], "text": "分享 API PDF 第 1 页 企业开发 API V6.6 上海画擎信息科技有限公司 姜大军 PDF 第 2 页 目录 一、 获取企业开发账号 ..............................................................................................................................................................................4 二、 认证 API ............................................................................................................................................................................................. 6 认证接口一（登录回调方式） ................................................................................................................................................................6 认证接口二（免登录方式 – JWT token 方式，在私有云部署中，需要开启 jwt token 的登录方式） ....................................... 6 获取 token .................................................................................................................................................................................................8 刷新 token .................................................................................................................................................................................................8 三、 文件访问 API ..................................................................................................................................................................................... 8 获取文件列表 ............................................................................................................................................................................................9 获取文件信息 ............................................................................................................................................................................................9 创建文件夹 ..............................................................................................................................................................................................10 预上传文件 ..............................................................................................................................................................................................10 上传文件 ..................................................................................................................................................................................................11 获取下载文件地址 ..................................................................................................................................................................................12 获取下载多文件地址 ..............................................................................................................................................................................12 获取下载文件缩略图地址 ......................................................................................................................................................................13 修改文件信息 ..........................................................................................................................................................................................13 修改文件名 ..............................................................................................................................................................................................13 删除文件(到回收站） .............................................................................................................................................................................14 删除文件（从回收站） ..........................................................................................................................................................................14 清空回收站 ..............................................................................................................................................................................................14 恢复文件（从回收站） ..........................................................................................................................................................................14 获取文件的所有版本信息 ......................................................................................................................................................................15 设置文件当前版本 ..................................................................................................................................................................................15 移动文件 ..................................................................................................................................................................................................15 拷贝文件 ..................................................................................................................................................................................................15 拷贝文件进度 ..........................................................................................................................................................................................16 文件日志 ..................................................................................................................................................................................................16 创建素材库分类 ......................................................................................................................................................................................17 创建子素材库 ..........................................................................................................................................................................................17 共享文件相关 API ................................................................................................................................................................................. 17 获取文件的分享 url ................................................................................................................................................................................ 18 获取分享的权限列表 ..............................................................................................................................................................................18 获取用户对于单个文件有权设置的分享角色 ......................................................................................................................................18 创建链接分享 ..........................................................................................................................................................................................18 关闭链接分享 ..........................................................................................................................................................................................19 设置链接分享密码 ..................................................................................................................................................................................19 邀请人员参与分享 ..................................................................................................................................................................................19 获取所有分享参与人 ..............................................................................................................................................................................20 设置分享参与人的权限角色 ..................................................................................................................................................................20 删除分享参与人 ......................................................................................................................................................................................20 提醒关注 ..................................................................................................................................................................................................21 移除某人的关注 ......................................................................................................................................................................................21 获取关注文件的用户列表 ......................................................................................................................................................................21 获取可以关注文件的用户列表，并且标记已关注文件的用户 ..........................................................................................................21 企业部门相关 API ................................................................................................................................................................................. 22 获取当前企业信息 ..................................................................................................................................................................................22 获取企业所有部门信息 ..........................................................................................................................................................................22 创建企业部门 ..........................................................................................................................................................................................22 获取部门角色列表 ..................................................................................................................................................................................23 添加部门人员 ..........................................................................................................................................................................................23 删除部门人员 ..........................................................................................................................................................................................24 获取自己所在部门信息 ..........................................................................................................................................................................24 获取部门人员 ..........................................................................................................................................................................................24 添加企业成员 ..........................................................................................................................................................................................25 更新成员信息 ..........................................................................................................................................................................................25 获取企业成员信息 ..................................................................................................................................................................................26 获取企业所有成员 ..................................................................................................................................................................................26 获取企业日志 ..........................................................................................................................................................................................26 消息推送 API ......................................................................................................................................................................................... 27 发布公告 ..................................................................................................................................................................................................27 获取发布的公告 ......................................................................................................................................................................................27 发送部门讨论 ..........................................................................................................................................................................................27 获取部门讨论 ..........................................................................................................................................................................................28 获取企业日志 ..........................................................................................................................................................................................28 四、 JWT token 登录 .................................................................................................................................................................................29 五、 附录 通用 API 调用返回状态码 ............................................................................................................................................... 30 PDF 第 3 页 状态码 result code ................................................................................................................................................................................. 30 PDF 第 4 页 一、 获取企业开发账号 登录巴别鸟私有云企业管理后台，在首页中设置开发者账号： 打开后填写回调函数地址：http://xxx.xxx.xxx.xxx/public/babelAuthResult.do 填写后点击确定后自动产生开发者 id (client id)和开发者密钥(client secret)： 注：jwtToken 为相应的生成 jwtToken 时的加密密钥。 PDF 第 5 页 PDF 第 6 页 二、 认证 API 认证接口一（登录回调方式） /api/authorize.do HTTP 请求方式 GET URL 参数 参数名 Comment(说明) response type 必须为 code（必填） string client id 开发者的 id（必填） string redirect uri 回调函数地址，需要和注册时保持一致（必填） string data 任意数据，回调时传回 string 例如： /api/authorize.do?response type=code&client id=xxxxx&redirect uri=http://xxx.xxx.xxx&data=xxx 通过浏览器访问 返回结果 如果用户未登录，则会跳转到登录页，登录后如果未授权，则会 302 跳转到授权页，如果用户已经授权，则会 302 跳转到 redirect uri 并且带上授权码和 data，类似于 http://xxx.xxx.xxx?code=xxx&data=xxx code 有效期 5 分钟。 认证接口二（免登录方式 – JWT token 方式，在私有云部署中，需要开启 jwt token 的登录方 式） /api/authorizeByJWT.do HTTP 请求方式 GET URL 参数 参数名 Comment(说明) response type 必须为 code（必填） string client id 开发者的 id（必填） string jwt token Jwt token，（必填） string 是对{client id: xxxxxxx} 加密 形成的字符串 email email(可选), 传入用户的邮箱，以该用户进行登录，不填以企业管理员进行登录，string phone phone(可选), 传入用户的手机号，以该用户进行登录，不填以企业管理员进行登录， string babelId babelId(可选), 传入用户的工号，以该用户进行登录，不填以企业管理员进行登录， string PDF 第 7 页 例如： /api/authorizeByJWT.do?response type=code&client id=xxxxx&jwt token=xxx 说明：使用这个 api，如果不填 email, phone, babelId 系统将自动以管理员身份登录，否则会以 email, phone, babelId 对应的用户去 登录，不会显示登录界面去登录。注（email, phone, babelId）只需其中一个就可。 返回结果 { \"success\": true \"code\": \"xxxxxxxxxxxxxxxxxxxxxxxxx\", } jwt token 为 自己写程序生成 样例代码如下: import java.util.Date; import java.util.HashMap; import java.util.Map; import javax.crypto.SecretKey; import javax.crypto.spec.SecretKeySpec; import io.jsonwebtoken.Claims; import io.jsonwebtoken.JwtBuilder; import io.jsonwebtoken.Jwts; import io.jsonwebtoken.SignatureAlgorithm; import net.sf.json.JSONObject; / 生成标准 jwt 使用的 token / public class JWT App { static String skey = \"babeldfdfer95840834 t8e 9 9 5934 5943 5886256\"; // 密钥 在巴别鸟后台 开发者账号处 填入的 jwtToken 字段。 public static void main( String[] args ) { HashMap clientInfo = new HashMap (); clientInfo.put(\"client id\", \"7459492016147273\"); // 为开发者账户中的 client id try { String token = createTokenJWT(clientInfo); System.out.println(\" login token:\" + token); String token1 = \"eyJhbGciOiJIUzI1NiJ9.eyJkdXJhdGlvbiI6NjAsInBheWxvYWQiOnsiY2xpZW50X2lkIjoiNzQ1OTQ5MjAxNjE0NzI3MyJ9LCJ0aW1lIjoxNjkxNDg4MzY4NTk0fQ.pRFCwXd2snMr IgFWOFwYbvyAeeNhoFINGk Wmv7d24g\"; JSONObject parsed = parseTokenJWT(token1); System.out.println(\" parsed:\" + parsed); System.out.println(\" 将此 token 作为参数放在 url 中即可， 如:\"); } catch (Exception e) { System.out.println(e.getMessage()); } } public static String createTokenJWT(Map config) throws Exception { HashMap data = new HashMap (); data.put(\"time\", new Date().getTime()); data.put(\"duration\", 60); data.put(\"payload\", config); SignatureAlgorithm signatureAlgorithm = SignatureAlgorithm.HS256; SecretKey key = generalKey(); JwtBuilder builder = Jwts.builder() .setClaims(data) .signWith(signatureAlgorithm, key); System.out.println( \" builder :\" + builder); return builder.compact(); } public static JSONObject parseTokenJWT(String jwt) throws Exception { SecretKey key = generalKey(); Claims claims = Jwts.parser() .setSigningKey(key) .parseClaimsJws(jwt) .getBody(); System.out.println(\" claims:\" + claims.toString()); Long time = (Long)claims.get(\"time\"); long duration = (Integer)claims.get(\"duration\"); Long now = new Date().getTime(); if (now time 1000 duration) return null; // 超过 10 分钟的 token 无效 JSONObject obj = JSONObject.fromObject(claims.get(\"payload\")); return obj; } public static SecretKey generalKey(){ String stringKey = skey; byte[] encodedKey = stringKey.getBytes(); SecretKey key = new SecretKeySpec(encodedKey, 0, encodedKey.length, \"HmacSHA256\"); return key; } } PDF 第 8 页 获取 token /api/token.do HTTP 方法： POST HTTP Header 该接口使用 Basic Auth 的方式校验 client 的信息。具体做法是在 header 中添加类似于\"Authorization: Basic xxxxxxxxx\"。其中 \"xxxxxxxxx\"是通过开发者 id (client id)和开发者秘钥(client secret)算出来的，具体算法为 Base64Encode(client id + \":\" + client secret) Base64Encode 自行选择工具进行 Base64 编码 URL 参数 参数名 Comment(说明) grant type（必填） 必须为 authorization code string code（必填） 授权码，即回调地址接收到的授权码，授权码的有效期为 5 分钟，用过一次，无论成功 还是失败，授权码都会失效 string 例如： /api/token.do?grant type=authorization code&code=xxx&redirect uri=http://xxx.xxx.xxx 返回结果 access token 接口访问标识 refresh token 用来刷新 access token，有效时间为 30 天 expires in access token 的有效时间，单位为 s 刷新 token /api/refreshToken.do HTTP 方法： POST HTTP Header 该接口使用 Basic Auth 的方式校验 client 的信息。具体做法是在 header 中添加类似于\"Authorization: Basic xxxxxxxxx\"。其中 \"xxxxxxxxx\"是通过 client id 和 client secret 算出来的，具体算法为 Base64Encode(client id + \":\" + client secret) URL 参数 参数名 Comment(说明) grant type（必填） 必须为 refresh token string refresh token（必填） 即接口 2 中获取到的 refresh token string 例如： /api/refreshToken.do?grant type=refresh token&refresh token=xxx 返回结果 access token 接口访问标识, refresh token 用来刷新 access token，有效时间为 30 天 expires in access token 的有效时间 为 3600，单位为 s 三、 文件访问 API 所有的接口在访问时需要在 HTTP header 中带上 access token。对于含有请求参数的接口，通常是一些 POST、 PUT 或者 DELETE 接口，还需要设置 Content Type 来指定参数的格式。如果需要访问不同版本的 API，就需要 在请求路径上指定具体版本，如果需要返回不同格式的 response body，那么还需要设置 Accept。所有的参数都应 该采用 utf 8 的编码。 PDF 第 9 页 Headers： Authorization：存放 access token，格式为：\"Bearer \" + access token。 Content Type：指明请求参数的格式。如果是 POST、PUT 或者 DELETE 请求，需要指定\"application/json\"，我 们目前不支持其他请求参数的格式，比如 xml。如果是其他类型比如 GET 请求，可以不在 header 中设置 Content Type。 Accept：用于指定响应结果的格式以及 api 的版本信息。目前只支持返回 json 格式的 response，所以一般情况下 指定\"application/json\"。 若接口访问成功，我们会返回 json 格式的 response，并且 HTTP 的 status code 为 200。所有请求成功的 response 的 json 都会带有\"success: true”。response 的 header 里的 X Babel Version 表示此次请求访问的 api 的版本号。 获取文件列表 /nd/api/file/list dir HTTP 方法： GET URL 参数 参数名 Comment(说明) parent id 父文件夹 id（必填） string 当 parent 为 1 时返回企业文件夹内容，2 返回个人文件夹内容，3 返回我的 项目，4 返回我加入的分享，其它 fileId 返回正常的文件夹中的内容。 page size 页的大小 number page 页号 number type 类型：分为 1 file，2 folder，0 all 三种类型 string 返回字段说明 属性名 类型 说明 files 数组 文件信息 {fileId, name, …} total int 总数量 page int 页容量 success boolean 获取成功标记 code int 返回错误码 0 表示成功 获取文件信息 /nd/api/file/fileinfo HTTP 方法： GET URL 参数 参数名 Comment(说明) id 文件 id（必填） string 返回字段说明 fileInfo 信息 属性名 类型 说明 file Object 文件信息 { id, name, …} PDF 第 10 页 success boolean 获取成功标记 code int 返回错误码 0 表示成功 创建文件夹 /nd/api/file/create folder HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) parent id 目标文件夹 id（必填） string name 文件名（必填） string 返回字段说明 属性名 类型 说明 file Object 文件信息 { id, name, …} success boolean 获取成功标记 code int 返回错误码 0 表示成功 预上传文件 用于返回第二步上传文件时所需要的参数(url、upload token) /api/file/preUploadFile.do HTTP 方法： GET URL 参数 参数名 Comment(说明) parent id 目标文件夹 id（必填）(在根目录下上传可忽略此项) string name 文件名（必填） string file id 上传新版本时需要指定上传那个文件的新版本(上传新文件可忽略此项) string 正确的返回结果如下 {\"upload token\":\"92808ecfc2ac4e0ebc0b912edac3be4a\",\"url\":\"http://testdocument.babel.cc/api/file/uploadPdf.do\",\"su ccess\":true,\"code\":0} 返回字段说明 属性名 类型 说明 url string 该 url 仅能使用 1 次，且有效期为 1 小时 调用此 url 上传文件，成功后会返回 fileId， fileName、version 等 upload token string 上传文件时作为 post 的参数 PDF 第 11 页 上传文件 注意，本 api 的 url 是预上传接口返回的, 这里没有具体的 url，只是参数说明 https://xxx.xxx.xxx:xxx/api/file/uploadXXX.do（具体的 url 是由上一节 /api/file/preUploadFile.do 中返回的 url） POST POST 请求体参数 参数名 Comment(说明) file 文件二进制数据(上传数据) upload token /api/file/preUploadFile.do 请求中的返回值 返回信息如下 {\"fileId\":\"7728538212615908\",\"version\":0,\"fileName\":\"mesos.pdf\",\"fileSize\":848854,\"success\":true,\"code\":0} 上传相关代码 示例 加入 ‘com.squareup.okhttp3:okhttp:3.3.1’ 包 private void uploadFile(final String fileName, String parentId, final DaoCallback callback){ preUploadFile(fileName, parentId, new DaoCallback () { @Override public void onSuccess(JSONObject data) { int code = data.optInt(\"code\", 1); final String url = data.optString(\"url\", null); final String uploadToken = data.optString(\"upload token\"); if (code == 0) { // File file = new File(filePath); RequestBody fileContent = RequestBody.create(MultipartBody.FORM, file); RequestBody requestBody = new MultipartBody.Builder() .setType(MultipartBody.FORM) .addFormDataPart(\"file\", fileName, fileContent) .addFormDataPart(\"upload token\", uploadToken) .build(); Request request = new Request.Builder() .url(url) .post(requestBody) .build(); // 上传需要较长的时间，因此需要设置较长的 timeout OkHttpClient okHttpClient = new OkHttpClient(); okHttpClient.newCall(request) .enqueue(new okhttp3.Callback() { @Override public void onFailure(okhttp3.Call call, IOException e) { callback.onFailure( 1, null); } @Override public void onResponse(okhttp3.Call call, okhttp3.Response response) throws IOException { int httpCode = response.code(); if (httpCode == 200) { try { JSONObject result = new JSONObject(response.body().string()); response.body().close(); boolean success = result.getBoolean(\"success\"); if (success) { callback.onSuccess(null); } else { int code = result.getInt(\"code\"); String msg = result.optString(\"msg\"); callback.onFailure(code, msg); } } catch (JSONException e) { callback.onFailure( 2, null); } } else { callback.onFailure(httpCode, null); } } }); } } @Override public void onFailure( int errorCode, String msg){ Log.e(\"FileTransfer\", \"filePreUpload 失败 errorCode=\" + errorCode); } }); } PDF 第 12 页 private void preUploadFile(String fileName, String parentId, final DaoCallback callback) { String preUploadUrl = \"http://private.babel.cc:80/api/file/preUploadFile.do?name=1234.jpg&parent id=0\"; // 传入相应的参数 name, parent id String authorization = \"Bearer d48d0a0e253c4a2985d8c5653f717d71\"; //根据说明 生成 Request request = new Request.Builder().url(preUploadUrl) .addHeader(\"Authorization\", authorization) .build(); OkHttpClient okHttpClient = new OkHttpClient(); okHttpClient.newCall(request).enqueue(new okhttp3.Callback() { @Override public void onFailure(okhttp3.Call call, IOException e) { Log.d(\"\", \"\"); } @Override public void onResponse(okhttp3.Call call, okhttp3.Response response) throws IOException { Log.d(\"\",\"\"); int httpCode = response.code(); if (httpCode == 200) { JSONObject result = null; try { result = new JSONObject(response.body().string()); } catch (JSONException e) { e.printStackTrace(); } try { boolean success = result.getBoolean(\"success\"); if (success) { String url = result.getString(\"url\"); callback.onSuccess(result); } else { int code = result.getInt(\"code\"); String msg = result.optString(\"msg\"); callback.onFailure(code, msg); } } catch (JSONException e) { callback.onFailure( 2, null); } } else { callback.onFailure(httpCode, null); } } }); } 获取下载文件地址 /api/file/getFileDownloadUrl.do HTTP 方法： GET URL 参数 参数名 Comment(说明) fileId 需要下载的文件 id（必填） string version 文件的版本号（可选） number 返回信息如下 {\"code\":0,\"success\":true,\"type\":\"文件类型\",\"url\":\"文件下载地址\"} 获取下载多文件地址 /api/file/downloadMultiFiles.do HTTP 方法： GET URL 参数 参数名 Comment(说明) fileIdArr 由需要下载的文件 id 组成的字符串，由符号“!“(半角)分割，比如下载 id 为 133 与 233 的两 个文件，则 fileIdArr 的值为“133!233” string 类型 PDF 第 13 页 返回信息如下 {\"code\":0,\"success\":true,\"type\":\"文件类型\",\"url\":\"文件下载地址\"} 返回值 url 为多个文件打包后的下载地址。 获取下载文件缩略图地址 /api/file/downloadThumbnail.do HTTP 方法： GET URL 参数 参数名 Comment(说明) fileId 需要下载的文件 id（必填） string version 文件的版本号（可选） number size 需要显示的缩略图尺寸，取宽高中的最大值 返回信息如下 {\"code\":0,\"success\":true, \"url\":\"文件下载地址\"} 返回值 url 为多个文件打包后的下载地址。 修改文件信息 /nd /api/file/update file HTTP 方法： POST 修改文件信息 POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填） string name 新文件名 （可选） string description 文件说明 （可选） string 返回信息如下 {\"code\":0,\"success\":true} 修改文件名 /nd /api/file/rename HTTP 方法： POST 修改文件信息 POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填） string name 新文件名 string 返回信息如下 {\"code\":0,\"success\":true} PDF 第 14 页 删除文件(到回收站） /nd /api/file/remove file HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file ids[] 目标文件 id 数组（必填） string[] 返回信息如下 {\"code\":0,\"success\":true} 删除文件（从回收站） /nd /api/file/remove from trash HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file ids[] 目标文件 id 数组（必填） string[] 返回信息如下 {\"code\":0,\"success\":true} 清空回收站 /nd /api/file/empty trash HTTP 方法： POST POST 请求体参数 参数名 说明 返回信息如下 {\"code\":0,\"success\":true} 恢复文件（从回收站） /nd /api/file/restore file HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file ids[] 目标文件 id 数组 string[] restoreAll 不填写 file ids, restoreAll 为 true，时恢复回收站中所有文件，boolean 返回信息如下 PDF 第 15 页 {\"code\":0,\"success\":true} 获取文件的所有版本信息 /nd /api/file/versions HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 目标文件 id（必填） string 返回信息如下 {\"code\":0,\"versions\":[],\"success\":true} 设置文件当前版本 /nd /api/file/version HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file id 目标文件 id （必填） string version 版本号（必填） number 返回信息如下 {\"code\":0,\"success\":true} 移动文件 /nd /api/file/move HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file ids 需要移动的目标文件 id 数组（必填） string target id 需要移动到的目标文件夹 id（必填） string 返回信息如下 {\"code\":0,\"success\":true} 拷贝文件 /nd /api/file/copy HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) PDF 第 16 页 file ids 需要拷贝的目标文件 id 数组（必填） string target id 需要拷贝到的目标文件夹 id（必填） string 返回信息如下 { \"code\": 0, \"copyKey\": \"81427630 054a 11ef 8355 db93b4b1d006\",\"fileNum\": 10, \"success\": true} 拷贝文件进度 /nd /api/file/copy progress HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) copyKey 查看拷贝进度 copyKey 由 copy 接口返回（必填） string 返回信息如下 { \"code\": 0, \"completed\": 10,\"total\": 10, \"result\": {}, \"success\": true} 文件日志 /nd /api/file/file logs HTTP 方法： GET GET 请求体参数 参数名 Comment(说明) file id 目标文件 id 数组（必填） string startIndex 获取日志的起始顺序 第几条日志开始返回（选填） int 默认 0， pageSize 每页返回的个数（选填） int type 日志类型(选填) int 默认 0, 查看所有记录， 1 仅查看访问记录，2 仅查看上传下载，3 仅查看匿名用 户，4 仅查看分享及邀请，5 仅查看删除记录 userName 某个用户名 (选填) string, 返回某个用户的日志 lang 语言(选填) 默认 cn, string 返回日志的语言 cn(中文) en(英文) 返回信息如下 {\"code\":0,\"success\":true, \"logs\":[], \"total\":50} 设置用户是否有权访问素材库 /nd /api/file/ set user access material library HTTP 方法： POST GET 请求体参数 参数名 Comment(说明) userId 用户的 id 数组数型 [usrId1, userId2]（必填） string can 是否可访问 数值类型 （必填） int 默认 0， 0： 不可访问， 1:可以访问 返回信息如下 {\"code\":0,\"success\":true} PDF 第 17 页 创建素材库分类 /nd /api/file/create material class HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) destDirFileId 目标文件夹 的 fileId（必填） string name 创建分类库的名称（必填） string accessType 分类可见性 (选填) 默认为公开 0. 0: // 公开 1: // 需要申请 2: // 部门公开 3: // 部门申请 4: // 保密 managerIds 负责人的 id 数组类型 [usrId1,userId2] departmentIds 分类可见性 限定部门 的部门 id (选填) 数组类型 [departmentId1,departmentId2] 返回信息如下 {\"code\":0, \"success\":true, \"materialClass\": {}} 创建子素材库 /nd /api/file/create material folder HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) destDirFileId 目标文件夹 的 fileId（必填） string name 创建分类库的名称（必填） string accessType 分类可见性 (选填) 默认为公开 0. 0: // 公开 1: // 需要申请 2: // 部门公开 3: // 部门申请 4: // 保密 managerId 负责人的 id (选填) string departmentIds 分类可见性 限定部门 的部门 id (选填) 数组类型 [departmentId1,departmentId2] assistantIds 素材库助理人员的 id （选填） 数组类型 [usrId1,userId2] 返回信息如下 {\"code\":0, \"success\":true, \"materialFolder\": {}} 共享文件相关 API PDF 第 18 页 获取文件的分享 url /nd/api/share/shareurl HTTP 方法： GET 获取文件的分享链接（先打开分享后，再获取该链接） URL 参数 参数名 Comment(说明) file id 文件 id string is https 返回的 share url 协议是否为 https 0 为 http, 1 为 https， 默认 0 number 返回字段说明 {\"code\":0,\"url\":\"https://private.babel.cc/share.do?s=http://private.babel.cc/share.do?s=MjY2OTYzNTk3OTU2NzEzOTtXZWQgSnVsIDAxIDIwMj AgMTg6MzM6NTAgR01UKzA4MDAgKEhvbmcgS29uZyBTdGFuZGFyZCBUaW1lKQ%3D%3D\",\"success\":true} 获取分享的权限列表 /nd/api/share/share roles HTTP 方法： GET URL 参数 参数名 Comment(说明) 返回字段说明 {\"code\":0,\"roles\":[],\"success\":true} 获取用户对于单个文件有权设置的分享角色 /nd/api/share/share role forfile HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 文件 id string 返回字段说明 {\"code\":0,\"roles\":[],\"success\":true} 创建链接分享 /nd/api/share/open link share HTTP 方法： POST 打开分享，获取新的分享链接，之前的链接失效。 PDF 第 19 页 POST 请求体参数 参数名 Comment(说明) file id 预分享的文件 id（必填） string link role id 分享的角色 string is https 返回的 share url 协议是否为 https number anonymousVisit 是否允许匿名访问，1 为允许，0 为不允许（可选，默认为 1） number 返回字段说明 {\"code\":0,\"share url\":\"http://private.babel.cc/share.do?s=http://private.babel.cc/share.do?s=MjY2OTYzNTk3OTU2NzEzOTtXZWQgSnV sIDAxIDIwMjAgMTg6MzM6NTAgR01UKzA4MDAgKEhvbmcgS29uZyBTdGFuZGFyZCBUaW1lKQ%3D%3D\",\"password\":\"\",\"success\":tru e} 关闭链接分享 /nd/api/share/close link share HTTP 方法： POST 关闭我打开的分享链接 POST 请求体参数 参数名 Comment(说明) file id 分享的文件 id（必填） string 返回字段说明 {\"code\":0,\"success\":true} 设置链接分享密码 /nd/api/share/set share password HTTP 方法： POST 文件链接分享已打开，设置链接分享的密码。 POST 请求体参数 参数名 Comment(说明) file id 预分享的文件 id（必填） string password 链接分享的密码 string is https 返回的 share url 协议是否为 https number 返回字段说明 {\"code\":0,\"success\":true, \"share url\": \"http://private.babel.cc/share.do?s=xxxxxxxxxxx\"} 邀请人员参与分享 /nd/api/share/invite share HTTP 方法： POST PDF 第 20 页 可以根据用户的邮箱或者手机来邀请某些人来访问文件 POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填） string share role 分享的权限的 id（以上所有人共享此权限）（必填） string emails[] 邮箱数组 string[] phones[] 手机号的数组 string[] 返回字段说明 {\"code\":0,\"success\":true} 获取所有分享参与人 /nd/api/share/share participants HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 文件 id（必填） string 返回字段说明 {\"code\":0,\"users\":[],\"success\":true} 设置分享参与人的权限角色 /nd/api/share/set participant role HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填） string babelshare id int（必填） 用户 id string role id int（必填） 角色 id string 返回字段说明 {\"code\":0,\"success\":true} 删除分享参与人 /nd/api/file/remove share participant HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) PDF 第 21 页 file id 文件 id（必填） string babelshare ids[] int （必填） 用户 id string 返回字段说明 {\"code\":0,\"success\":true} 提醒关注 /nd/api/file/focus file HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填） string user ids[] 提醒的用户的 id，此 id 应该在文件参与人中选取，否则提醒不会起作用（必填）string[] 返回字段说明 {\"code\":0,\"success\":true} 移除某人的关注 /nd/api/file/unfocus file HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填）string user ids[] 提醒的用户的 id，此 id 应该在文件参与人中选取，否则提醒不会起作用（必填） string[] 返回字段说明 {\"code\":0,\"success\":true} 获取关注文件的用户列表 /nd/api/file/user focusfile HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 文件 id（必填） string 返回字段说明 {\"code\":0,\"users\":[],\"success\":true} 获取可以关注文件的用户列表，并且标记已关注文件的用户 /nd/api/file/user can focusfile PDF 第 22 页 HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 文件 id（必填） string 返回字段说明 企业部门相关 API 获取当前企业信息 /nd/api/enterprise/current HTTP 方法： GET URL 参数 参数名 Comment(说明) 无 返回字段说明 {\"code\":0,\"enterprise\":{},\"success\":true} 获取企业所有部门信息 /nd/api/enterprise/departments HTTP 方法： GET URL 参数 参数名 Comment(说明) 无 返回字段说明 属性名 类型 说明 departments []数组 返回所有的部门信息 tree {}json 数据 返回部门的父子结构信息 code int sucess boolean 创建企业部门 /nd/api/enterprise/create department HTTP 方法： POST PDF 第 23 页 POST 请求体参数 参数名 Comment(说明) parent dep 父部门 id， 0 表示跟部门（必填）string name 部门名称（必填）string description 部门描述 string 返回字段说明 属性名 类型 说明 department {} json 数据结构 code int sucess boolean 获取部门角色列表 /nd/api/enterprise/dep role HTTP 方法： GET URL 参数 参数名 Comment(说明) 返回字段说明 属性名 类型 说明 roles []数组 { id, filePermission,enterpriseId,filePermission,managerPermission, default,nameEn,name} code int sucess boolean 添加部门人员 /nd/api/enterprise/add dep mem HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) department id 部门 id（必填）string user ids[] 用户列表 string[] role id 用户在部门中的角色 string PDF 第 24 页 返回字段说明 属性名 类型 说明 删除部门人员 /nd/api/enterprise/remove dep mem HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) department id 部门 id（必填）string user ids[] 人员的 id（必填）string[] 返回字段说明 属性名 类型 说明 获取自己所在部门信息 /nd/api/enterprise/mydeparments HTTP 方法： GET URL 参数 参数名 Comment(说明) 无 返回字段说明 属性名 类型 说明 departments []数组 返回我所在的部门信息 code int sucess boolean 获取部门人员 /nd/api/enterprise/departmentmembers PDF 第 25 页 HTTP 方法： GET URL 参数 参数名 Comment(说明) department id 部门 id（必填）string 返回字段说明 属性名 类型 说明 users 数组 ： {id, name, avatrUrl,} 添加企业成员 /nd/api/enterprise/add ent mem HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) email Email 邮箱 string password 密码 string enterprise role 企业成员角色, 可选 number department ids[] 该用户的部门， 可选 string[] department roles[] 在部门中的角色， 可选 string[] sex 性别 0 未设置 1 男 2 女 number name 用户名 string phone 手机号， 可选 string babelId 工号，可选 string spacelimit 个人空间限制，单位 GB, 0 表示不限制 number can ownfile 用户能否拥有个人文件， 1 使用企业总体设置, 0 没有个人文件, 1 有个人文件 number remarks 用户描述， 可选 string join time 用户加入企业时间，Unix time, 单位秒 number password is md5 传入密码是否需要 md5 加密, 0 非 md5 密码， 1 md5 加密过的密码 number 更新成员信息 /api/updateUserInfo.do HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) email 邮箱地址（搜索关键字，必须）string password 密码（修改密码，可选）string frozen 1 – 表示冻结， 0 – 表示解冻 （冻结该账号，可选）number password is md5 传入密码是否需要 md5 加密, 0 非 md5 密码， 1 md5 加密过的密码 number phone 手机号 (可选) string PDF 第 26 页 获取企业成员信息 /api/getEnterpriseMember.do HTTP 方法： GET URL 参数 参数名 Comment(说明) email 邮箱地址（搜索关键字）string phone 手机号（搜索关键字）string babelId 工号（搜索关键字）string email/phone/babelId 可选择其一 返回字段说明 {\"code\":0,\"success\":true,\"user\":{}} 获取企业所有成员 /nd/api/enterprise/enterprise members HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) lang 语言类型，cn 中文 ，en 英文 , 可选 options { departmentId: // 部门 id，不填写就是企业所有人员 roleId: // 角色 id， 不填写就是不限角色 \"userType\": 0, // 0 企业内人员， 1 外部人员 \"keyName\": \"\", // 搜索关键字： 人名，手机号，邮箱， 不填写就是所有人员 \"startIndex\": 0， \"pageSize\": 20, status: // 0 所有账号， 1 停用的账号 } 可选 返回字段说明 {\"code\":0,\"success\":true,\"members\":{},\"total\":xx} 获取企业日志 /nd/api/enterprise/enterprise logs HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) department id 部门 id，不填写就是所有部门的日志 string 可选 keyword 日志的相关搜索关键字 string 可选 PDF 第 27 页 startTime 日志起始时间 number 可选 endTime 日志截止时间 number 可选 startIndex int 可选 pageSize int 可选 返回字段说明 {\"code\":0,\"success\":true,\"logs\":{},\"total\":xx} 消息推送 API 发布公告 /nd/api/enterprise/broadcast HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) title 公告内容字符串（必填） string content 内容（必填）string target users[] UserId 数组，如果为空则表示全部人员接收，string[] target deps[] 目标部门，该部门及子部门所有成员都会收到通知，string[] target users 与 target deps 至少要填 1 个 返回字段说明 {\"code\":0,\"success\":true} 获取发布的公告 /nd/api/enterprise/broadcast HTTP 方法： GET URL 参数 参数名 Comment(说明) start index number pagesize number 返回字段说明 {\"code\":0,\"broadcasts\":[],\"total\":19,\"success\":true} 发送部门讨论 /nd/api/file/send dep discussion HTTP 方法： POST PDF 第 28 页 POST 请求体参数 参数名 Comment(说明) dep id 部门 id（必填） string message 信息字符（必填） string json 字符串, 格式{Type: “Text”, Body:”你好” } 返回字段说明 {\"code\":0,\"messageId\":99,\"success\":true} 获取部门讨论 /nd/api/file/dep discussion HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) dep id 部门 id（必填）string pagesize 页的大小 string start id 消息 id,只会获取此消息之前的消息，为空则获取最新消息 string 返回字段说明 {\"msgArr\":[],\"gotMoreMessages\":1,\"code\":0,\"success\":true} 获取企业日志 /nd/api/enterprise/enterprise logs HTTP 方法： GET URL 参数 参数名 Comment(说明) department id 部门 id（）string pagesize 页的大小 number，默认值 1000 start index 消息起始位置, number keyword 日志关键词 string startTime 起始日期: 秒 number endTime 截止日期 秒 number 返回字段说明 {\"logs\":[],\"total\":0,\"code\":0,\"success\":true} total 返回所有符合条件的(与分页 pageSize 无关) PDF 第 29 页 四、 JWT token 登录 在私有云部署中，可以开启 jwt token 的登录方式，在这种情况下，允许通过下面的 url 直接以某用户的身份免登录进入网盘系 统： /account/tokenLogin.do 参数： 参数名称 可选性 说明 可选值 默认值 userToken 必填 含有登录用户的加密信息（构造方 无 法详见下面的说明） fileId 可选 要访问的文件（夹）的 id，如果不 无 填写则打开用户根目录 closeTitleBar 可选 是否关闭标题栏 1 关闭 0 不关闭 0 disableEntMark 可选 是否隐藏左上角企业标识 1 隐藏 0 不隐藏 0 disableUserMark 可选 是否隐藏右上角用户设置入口 1 隐藏 0 不隐藏 0 defaultLang 可选 设置界面使用的语言 cn 中文 en 英文 zh HK 繁体 cn defaultClrTheme 可选 设置界面颜色主题 normal 标准模式，dark 暗色模式 normal 比如下面是以英文及暗色模式并隐藏右上角用户标志进入用户根目录界面 /account/tokenLogin.do userToken=xxxxxxxxxxxxxxxx defaultClrTheme=dark defaultLang=en disableUserMark=1 userToken 的构建 userToken 是含有登录用户信息的加密字符串，加密信息是通过标准的双方传输可信数据的安全机制 JWT 创建的口令字， JWT 加密的用户信息 JSONObject 内容如下： { payload: { email: “xxx@xxx.com”/“135XXXXXXX”/“XXXX”} time: now } 说明：其中 email, 可以是邮箱，手机号，工号； 代码如下： public static void main( String[] args ) { HashMap user = new HashMap (); user.put(\"email\", \"yuanchaozhao@qq.com\"); try { //token login String userToken = createTokenJWT(user); System.out.println(\" login token:\" + userToken); JSONObject parsed = parseTokenJWT(userToken); System.out.println(\" parsed:\" + parsed); System.out.println(\" 将此 token 作为参数放在 url 中即可， 如:\"); System.out.println(\"/account/tokenLogin.do?userToken=\" + userToken); } catch (Exception e) { System.out.println(e.getMessage()); } } 其它代码 参考 jwtToken 的生成代码，在认证接口二处有提供。 备注： JWT 即 JSON Web Tokens 的简写， 是满足工业标准 RFC7519 的一种通信加密解密机制，请参考： https://jwt.io/ PDF 第 30 页 五、 附录 通用 API 调用返回状态码 状态码 result code 码值 说明 0 成功 1 未知错误 2 参数错误 7 空间不足 12 禁止的用户操作 13 无效的 token 结束 the end" }, { "lang": "zh", "slug": "developer-api-enterprise", "title": "企业 API", "description": "企业 API 的接口路径、方法、参数和返回字段。", "category": "企业 API", "top_category": "API文档", "keywords": [ "API", "企业 API", "开发者" ], "url": "zh/developer-api-enterprise.html", "source": "content/zh/developer-api-enterprise.md", "summary": "企业 API PDF 第 1 页 企业开发 API V6.6 上海画擎信息科技有限公司 姜大军 PDF 第 2 页 目录 一、 获取企业开发账号 ..............................................................................................................................................................................4 二、 认证 API ............................................................................................................................................................................................. 6 认证接口一（登录回调方式） ................................................................................................................................................................6 认证接口二（免登录方式 – JWT token 方式，在私有云部署中，需要开启 jwt token 的登录方式） ................", "headings": [ { "level": 1, "title": "企业 API", "id": "api" }, { "level": 3, "title": "PDF 第 1 页", "id": "pdf-1" }, { "level": 3, "title": "PDF 第 2 页", "id": "pdf-2" }, { "level": 3, "title": "PDF 第 3 页", "id": "pdf-3" }, { "level": 3, "title": "PDF 第 4 页", "id": "pdf-4" }, { "level": 2, "title": "一、 获取企业开发账号", "id": "section" }, { "level": 3, "title": "PDF 第 5 页", "id": "pdf-5" }, { "level": 3, "title": "PDF 第 6 页", "id": "pdf-6" }, { "level": 2, "title": "二、 认证 API", "id": "api-2" }, { "level": 3, "title": "认证接口一（登录回调方式）", "id": "section-2" }, { "level": 3, "title": "PDF 第 7 页", "id": "pdf-7" }, { "level": 3, "title": "PDF 第 8 页", "id": "pdf-8" }, { "level": 3, "title": "获取 token", "id": "token" }, { "level": 3, "title": "刷新 token", "id": "token-2" }, { "level": 2, "title": "三、 文件访问 API", "id": "api-3" }, { "level": 3, "title": "PDF 第 9 页", "id": "pdf-9" }, { "level": 3, "title": "获取文件列表", "id": "section-3" }, { "level": 3, "title": "获取文件信息", "id": "section-5" }, { "level": 3, "title": "PDF 第 10 页", "id": "pdf-10" }, { "level": 3, "title": "创建文件夹", "id": "section-7" }, { "level": 3, "title": "预上传文件", "id": "section-9" }, { "level": 3, "title": "PDF 第 11 页", "id": "pdf-11" }, { "level": 3, "title": "上传文件", "id": "section-12" }, { "level": 3, "title": "PDF 第 12 页", "id": "pdf-12" }, { "level": 3, "title": "获取下载文件地址", "id": "section-14" }, { "level": 3, "title": "获取下载多文件地址", "id": "section-16" }, { "level": 3, "title": "PDF 第 13 页", "id": "pdf-13" }, { "level": 3, "title": "获取下载文件缩略图地址", "id": "section-18" }, { "level": 3, "title": "修改文件信息", "id": "section-20" }, { "level": 3, "title": "修改文件信息", "id": "section-21" }, { "level": 3, "title": "修改文件名", "id": "section-23" }, { "level": 3, "title": "修改文件信息", "id": "section-24" }, { "level": 3, "title": "PDF 第 14 页", "id": "pdf-14" }, { "level": 3, "title": "删除文件(到回收站）", "id": "section-26" }, { "level": 3, "title": "删除文件（从回收站）", "id": "section-28" }, { "level": 3, "title": "清空回收站", "id": "section-30" }, { "level": 3, "title": "恢复文件（从回收站）", "id": "section-32" }, { "level": 3, "title": "PDF 第 15 页", "id": "pdf-15" }, { "level": 3, "title": "获取文件的所有版本信息", "id": "section-34" }, { "level": 3, "title": "设置文件当前版本", "id": "section-36" }, { "level": 3, "title": "移动文件", "id": "section-38" }, { "level": 3, "title": "拷贝文件", "id": "section-40" }, { "level": 3, "title": "PDF 第 16 页", "id": "pdf-16" }, { "level": 3, "title": "拷贝文件进度", "id": "section-42" }, { "level": 3, "title": "文件日志", "id": "section-44" }, { "level": 3, "title": "设置用户是否有权访问素材库", "id": "section-46" }, { "level": 3, "title": "PDF 第 17 页", "id": "pdf-17" }, { "level": 3, "title": "创建素材库分类", "id": "section-48" }, { "level": 3, "title": "创建子素材库", "id": "section-50" }, { "level": 2, "title": "共享文件相关 API", "id": "api-4" }, { "level": 3, "title": "PDF 第 18 页", "id": "pdf-18" }, { "level": 3, "title": "获取文件的分享 url", "id": "url-12" }, { "level": 3, "title": "获取分享的权限列表", "id": "section-53" }, { "level": 3, "title": "获取用户对于单个文件有权设置的分享角色", "id": "section-55" }, { "level": 3, "title": "创建链接分享", "id": "section-57" }, { "level": 3, "title": "PDF 第 19 页", "id": "pdf-19" }, { "level": 3, "title": "关闭链接分享", "id": "section-59" }, { "level": 3, "title": "设置链接分享密码", "id": "section-61" }, { "level": 3, "title": "邀请人员参与分享", "id": "section-63" }, { "level": 3, "title": "PDF 第 20 页", "id": "pdf-20" }, { "level": 3, "title": "获取所有分享参与人", "id": "section-65" }, { "level": 3, "title": "设置分享参与人的权限角色", "id": "section-67" }, { "level": 3, "title": "删除分享参与人", "id": "section-69" }, { "level": 3, "title": "PDF 第 21 页", "id": "pdf-21" }, { "level": 3, "title": "提醒关注", "id": "section-71" }, { "level": 3, "title": "移除某人的关注", "id": "section-73" }, { "level": 3, "title": "获取关注文件的用户列表", "id": "section-75" }, { "level": 3, "title": "获取可以关注文件的用户列表，并且标记已关注文件的用户", "id": "section-77" }, { "level": 3, "title": "PDF 第 22 页", "id": "pdf-22" }, { "level": 2, "title": "企业部门相关 API", "id": "api-5" }, { "level": 3, "title": "获取当前企业信息", "id": "section-79" }, { "level": 3, "title": "获取企业所有部门信息", "id": "section-81" }, { "level": 3, "title": "创建企业部门", "id": "section-83" }, { "level": 3, "title": "PDF 第 23 页", "id": "pdf-23" }, { "level": 3, "title": "获取部门角色列表", "id": "section-85" }, { "level": 3, "title": "添加部门人员", "id": "section-87" }, { "level": 3, "title": "PDF 第 24 页", "id": "pdf-24" }, { "level": 3, "title": "删除部门人员", "id": "section-89" }, { "level": 3, "title": "获取自己所在部门信息", "id": "section-91" }, { "level": 3, "title": "获取部门人员", "id": "section-93" }, { "level": 3, "title": "PDF 第 25 页", "id": "pdf-25" }, { "level": 3, "title": "添加企业成员", "id": "section-95" }, { "level": 3, "title": "更新成员信息", "id": "section-96" }, { "level": 3, "title": "PDF 第 26 页", "id": "pdf-26" }, { "level": 3, "title": "获取企业成员信息", "id": "section-97" }, { "level": 3, "title": "获取企业所有成员", "id": "section-99" }, { "level": 3, "title": "获取企业日志", "id": "section-101" }, { "level": 3, "title": "PDF 第 27 页", "id": "pdf-27" }, { "level": 2, "title": "消息推送 API", "id": "api-6" }, { "level": 3, "title": "发布公告", "id": "section-103" }, { "level": 3, "title": "获取发布的公告", "id": "section-105" }, { "level": 3, "title": "发送部门讨论", "id": "section-107" }, { "level": 3, "title": "PDF 第 28 页", "id": "pdf-28" }, { "level": 3, "title": "获取部门讨论", "id": "section-109" }, { "level": 3, "title": "获取企业日志", "id": "section-111" }, { "level": 3, "title": "PDF 第 29 页", "id": "pdf-29" }, { "level": 2, "title": "四、 JWT token 登录", "id": "jwt-token" }, { "level": 3, "title": "PDF 第 30 页", "id": "pdf-30" }, { "level": 2, "title": "五、 附录 通用 API 调用返回状态码", "id": "api-7" }, { "level": 2, "title": "状态码 result code", "id": "result-code" } ], "images": [], "text": "企业 API PDF 第 1 页 企业开发 API V6.6 上海画擎信息科技有限公司 姜大军 PDF 第 2 页 目录 一、 获取企业开发账号 ..............................................................................................................................................................................4 二、 认证 API ............................................................................................................................................................................................. 6 认证接口一（登录回调方式） ................................................................................................................................................................6 认证接口二（免登录方式 – JWT token 方式，在私有云部署中，需要开启 jwt token 的登录方式） ....................................... 6 获取 token .................................................................................................................................................................................................8 刷新 token .................................................................................................................................................................................................8 三、 文件访问 API ..................................................................................................................................................................................... 8 获取文件列表 ............................................................................................................................................................................................9 获取文件信息 ............................................................................................................................................................................................9 创建文件夹 ..............................................................................................................................................................................................10 预上传文件 ..............................................................................................................................................................................................10 上传文件 ..................................................................................................................................................................................................11 获取下载文件地址 ..................................................................................................................................................................................12 获取下载多文件地址 ..............................................................................................................................................................................12 获取下载文件缩略图地址 ......................................................................................................................................................................13 修改文件信息 ..........................................................................................................................................................................................13 修改文件名 ..............................................................................................................................................................................................13 删除文件(到回收站） .............................................................................................................................................................................14 删除文件（从回收站） ..........................................................................................................................................................................14 清空回收站 ..............................................................................................................................................................................................14 恢复文件（从回收站） ..........................................................................................................................................................................14 获取文件的所有版本信息 ......................................................................................................................................................................15 设置文件当前版本 ..................................................................................................................................................................................15 移动文件 ..................................................................................................................................................................................................15 拷贝文件 ..................................................................................................................................................................................................15 拷贝文件进度 ..........................................................................................................................................................................................16 文件日志 ..................................................................................................................................................................................................16 创建素材库分类 ......................................................................................................................................................................................17 创建子素材库 ..........................................................................................................................................................................................17 共享文件相关 API ................................................................................................................................................................................. 17 获取文件的分享 url ................................................................................................................................................................................ 18 获取分享的权限列表 ..............................................................................................................................................................................18 获取用户对于单个文件有权设置的分享角色 ......................................................................................................................................18 创建链接分享 ..........................................................................................................................................................................................18 关闭链接分享 ..........................................................................................................................................................................................19 设置链接分享密码 ..................................................................................................................................................................................19 邀请人员参与分享 ..................................................................................................................................................................................19 获取所有分享参与人 ..............................................................................................................................................................................20 设置分享参与人的权限角色 ..................................................................................................................................................................20 删除分享参与人 ......................................................................................................................................................................................20 提醒关注 ..................................................................................................................................................................................................21 移除某人的关注 ......................................................................................................................................................................................21 获取关注文件的用户列表 ......................................................................................................................................................................21 获取可以关注文件的用户列表，并且标记已关注文件的用户 ..........................................................................................................21 企业部门相关 API ................................................................................................................................................................................. 22 获取当前企业信息 ..................................................................................................................................................................................22 获取企业所有部门信息 ..........................................................................................................................................................................22 创建企业部门 ..........................................................................................................................................................................................22 获取部门角色列表 ..................................................................................................................................................................................23 添加部门人员 ..........................................................................................................................................................................................23 删除部门人员 ..........................................................................................................................................................................................24 获取自己所在部门信息 ..........................................................................................................................................................................24 获取部门人员 ..........................................................................................................................................................................................24 添加企业成员 ..........................................................................................................................................................................................25 更新成员信息 ..........................................................................................................................................................................................25 获取企业成员信息 ..................................................................................................................................................................................26 获取企业所有成员 ..................................................................................................................................................................................26 获取企业日志 ..........................................................................................................................................................................................26 消息推送 API ......................................................................................................................................................................................... 27 发布公告 ..................................................................................................................................................................................................27 获取发布的公告 ......................................................................................................................................................................................27 发送部门讨论 ..........................................................................................................................................................................................27 获取部门讨论 ..........................................................................................................................................................................................28 获取企业日志 ..........................................................................................................................................................................................28 四、 JWT token 登录 .................................................................................................................................................................................29 五、 附录 通用 API 调用返回状态码 ............................................................................................................................................... 30 PDF 第 3 页 状态码 result code ................................................................................................................................................................................. 30 PDF 第 4 页 一、 获取企业开发账号 登录巴别鸟私有云企业管理后台，在首页中设置开发者账号： 打开后填写回调函数地址：http://xxx.xxx.xxx.xxx/public/babelAuthResult.do 填写后点击确定后自动产生开发者 id (client id)和开发者密钥(client secret)： 注：jwtToken 为相应的生成 jwtToken 时的加密密钥。 PDF 第 5 页 PDF 第 6 页 二、 认证 API 认证接口一（登录回调方式） /api/authorize.do HTTP 请求方式 GET URL 参数 参数名 Comment(说明) response type 必须为 code（必填） string client id 开发者的 id（必填） string redirect uri 回调函数地址，需要和注册时保持一致（必填） string data 任意数据，回调时传回 string 例如： /api/authorize.do?response type=code&client id=xxxxx&redirect uri=http://xxx.xxx.xxx&data=xxx 通过浏览器访问 返回结果 如果用户未登录，则会跳转到登录页，登录后如果未授权，则会 302 跳转到授权页，如果用户已经授权，则会 302 跳转到 redirect uri 并且带上授权码和 data，类似于 http://xxx.xxx.xxx?code=xxx&data=xxx code 有效期 5 分钟。 认证接口二（免登录方式 – JWT token 方式，在私有云部署中，需要开启 jwt token 的登录方 式） /api/authorizeByJWT.do HTTP 请求方式 GET URL 参数 参数名 Comment(说明) response type 必须为 code（必填） string client id 开发者的 id（必填） string jwt token Jwt token，（必填） string 是对{client id: xxxxxxx} 加密 形成的字符串 email email(可选), 传入用户的邮箱，以该用户进行登录，不填以企业管理员进行登录，string phone phone(可选), 传入用户的手机号，以该用户进行登录，不填以企业管理员进行登录， string babelId babelId(可选), 传入用户的工号，以该用户进行登录，不填以企业管理员进行登录， string PDF 第 7 页 例如： /api/authorizeByJWT.do?response type=code&client id=xxxxx&jwt token=xxx 说明：使用这个 api，如果不填 email, phone, babelId 系统将自动以管理员身份登录，否则会以 email, phone, babelId 对应的用户去 登录，不会显示登录界面去登录。注（email, phone, babelId）只需其中一个就可。 返回结果 { \"success\": true \"code\": \"xxxxxxxxxxxxxxxxxxxxxxxxx\", } jwt token 为 自己写程序生成 样例代码如下: import java.util.Date; import java.util.HashMap; import java.util.Map; import javax.crypto.SecretKey; import javax.crypto.spec.SecretKeySpec; import io.jsonwebtoken.Claims; import io.jsonwebtoken.JwtBuilder; import io.jsonwebtoken.Jwts; import io.jsonwebtoken.SignatureAlgorithm; import net.sf.json.JSONObject; / 生成标准 jwt 使用的 token / public class JWT App { static String skey = \"babeldfdfer95840834 t8e 9 9 5934 5943 5886256\"; // 密钥 在巴别鸟后台 开发者账号处 填入的 jwtToken 字段。 public static void main( String[] args ) { HashMap clientInfo = new HashMap (); clientInfo.put(\"client id\", \"7459492016147273\"); // 为开发者账户中的 client id try { String token = createTokenJWT(clientInfo); System.out.println(\" login token:\" + token); String token1 = \"eyJhbGciOiJIUzI1NiJ9.eyJkdXJhdGlvbiI6NjAsInBheWxvYWQiOnsiY2xpZW50X2lkIjoiNzQ1OTQ5MjAxNjE0NzI3MyJ9LCJ0aW1lIjoxNjkxNDg4MzY4NTk0fQ.pRFCwXd2snMr IgFWOFwYbvyAeeNhoFINGk Wmv7d24g\"; JSONObject parsed = parseTokenJWT(token1); System.out.println(\" parsed:\" + parsed); System.out.println(\" 将此 token 作为参数放在 url 中即可， 如:\"); } catch (Exception e) { System.out.println(e.getMessage()); } } public static String createTokenJWT(Map config) throws Exception { HashMap data = new HashMap (); data.put(\"time\", new Date().getTime()); data.put(\"duration\", 60); data.put(\"payload\", config); SignatureAlgorithm signatureAlgorithm = SignatureAlgorithm.HS256; SecretKey key = generalKey(); JwtBuilder builder = Jwts.builder() .setClaims(data) .signWith(signatureAlgorithm, key); System.out.println( \" builder :\" + builder); return builder.compact(); } public static JSONObject parseTokenJWT(String jwt) throws Exception { SecretKey key = generalKey(); Claims claims = Jwts.parser() .setSigningKey(key) .parseClaimsJws(jwt) .getBody(); System.out.println(\" claims:\" + claims.toString()); Long time = (Long)claims.get(\"time\"); long duration = (Integer)claims.get(\"duration\"); Long now = new Date().getTime(); if (now time 1000 duration) return null; // 超过 10 分钟的 token 无效 JSONObject obj = JSONObject.fromObject(claims.get(\"payload\")); return obj; } public static SecretKey generalKey(){ String stringKey = skey; byte[] encodedKey = stringKey.getBytes(); SecretKey key = new SecretKeySpec(encodedKey, 0, encodedKey.length, \"HmacSHA256\"); return key; } } PDF 第 8 页 获取 token /api/token.do HTTP 方法： POST HTTP Header 该接口使用 Basic Auth 的方式校验 client 的信息。具体做法是在 header 中添加类似于\"Authorization: Basic xxxxxxxxx\"。其中 \"xxxxxxxxx\"是通过开发者 id (client id)和开发者秘钥(client secret)算出来的，具体算法为 Base64Encode(client id + \":\" + client secret) Base64Encode 自行选择工具进行 Base64 编码 URL 参数 参数名 Comment(说明) grant type（必填） 必须为 authorization code string code（必填） 授权码，即回调地址接收到的授权码，授权码的有效期为 5 分钟，用过一次，无论成功 还是失败，授权码都会失效 string 例如： /api/token.do?grant type=authorization code&code=xxx&redirect uri=http://xxx.xxx.xxx 返回结果 access token 接口访问标识 refresh token 用来刷新 access token，有效时间为 30 天 expires in access token 的有效时间，单位为 s 刷新 token /api/refreshToken.do HTTP 方法： POST HTTP Header 该接口使用 Basic Auth 的方式校验 client 的信息。具体做法是在 header 中添加类似于\"Authorization: Basic xxxxxxxxx\"。其中 \"xxxxxxxxx\"是通过 client id 和 client secret 算出来的，具体算法为 Base64Encode(client id + \":\" + client secret) URL 参数 参数名 Comment(说明) grant type（必填） 必须为 refresh token string refresh token（必填） 即接口 2 中获取到的 refresh token string 例如： /api/refreshToken.do?grant type=refresh token&refresh token=xxx 返回结果 access token 接口访问标识, refresh token 用来刷新 access token，有效时间为 30 天 expires in access token 的有效时间 为 3600，单位为 s 三、 文件访问 API 所有的接口在访问时需要在 HTTP header 中带上 access token。对于含有请求参数的接口，通常是一些 POST、 PUT 或者 DELETE 接口，还需要设置 Content Type 来指定参数的格式。如果需要访问不同版本的 API，就需要 在请求路径上指定具体版本，如果需要返回不同格式的 response body，那么还需要设置 Accept。所有的参数都应 该采用 utf 8 的编码。 PDF 第 9 页 Headers： Authorization：存放 access token，格式为：\"Bearer \" + access token。 Content Type：指明请求参数的格式。如果是 POST、PUT 或者 DELETE 请求，需要指定\"application/json\"，我 们目前不支持其他请求参数的格式，比如 xml。如果是其他类型比如 GET 请求，可以不在 header 中设置 Content Type。 Accept：用于指定响应结果的格式以及 api 的版本信息。目前只支持返回 json 格式的 response，所以一般情况下 指定\"application/json\"。 若接口访问成功，我们会返回 json 格式的 response，并且 HTTP 的 status code 为 200。所有请求成功的 response 的 json 都会带有\"success: true”。response 的 header 里的 X Babel Version 表示此次请求访问的 api 的版本号。 获取文件列表 /nd/api/file/list dir HTTP 方法： GET URL 参数 参数名 Comment(说明) parent id 父文件夹 id（必填） string 当 parent 为 1 时返回企业文件夹内容，2 返回个人文件夹内容，3 返回我的 项目，4 返回我加入的分享，其它 fileId 返回正常的文件夹中的内容。 page size 页的大小 number page 页号 number type 类型：分为 1 file，2 folder，0 all 三种类型 string 返回字段说明 属性名 类型 说明 files 数组 文件信息 {fileId, name, …} total int 总数量 page int 页容量 success boolean 获取成功标记 code int 返回错误码 0 表示成功 获取文件信息 /nd/api/file/fileinfo HTTP 方法： GET URL 参数 参数名 Comment(说明) id 文件 id（必填） string 返回字段说明 fileInfo 信息 属性名 类型 说明 file Object 文件信息 { id, name, …} PDF 第 10 页 success boolean 获取成功标记 code int 返回错误码 0 表示成功 创建文件夹 /nd/api/file/create folder HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) parent id 目标文件夹 id（必填） string name 文件名（必填） string 返回字段说明 属性名 类型 说明 file Object 文件信息 { id, name, …} success boolean 获取成功标记 code int 返回错误码 0 表示成功 预上传文件 用于返回第二步上传文件时所需要的参数(url、upload token) /api/file/preUploadFile.do HTTP 方法： GET URL 参数 参数名 Comment(说明) parent id 目标文件夹 id（必填）(在根目录下上传可忽略此项) string name 文件名（必填） string file id 上传新版本时需要指定上传那个文件的新版本(上传新文件可忽略此项) string 正确的返回结果如下 {\"upload token\":\"92808ecfc2ac4e0ebc0b912edac3be4a\",\"url\":\"http://testdocument.babel.cc/api/file/uploadPdf.do\",\"su ccess\":true,\"code\":0} 返回字段说明 属性名 类型 说明 url string 该 url 仅能使用 1 次，且有效期为 1 小时 调用此 url 上传文件，成功后会返回 fileId， fileName、version 等 upload token string 上传文件时作为 post 的参数 PDF 第 11 页 上传文件 注意，本 api 的 url 是预上传接口返回的, 这里没有具体的 url，只是参数说明 https://xxx.xxx.xxx:xxx/api/file/uploadXXX.do（具体的 url 是由上一节 /api/file/preUploadFile.do 中返回的 url） POST POST 请求体参数 参数名 Comment(说明) file 文件二进制数据(上传数据) upload token /api/file/preUploadFile.do 请求中的返回值 返回信息如下 {\"fileId\":\"7728538212615908\",\"version\":0,\"fileName\":\"mesos.pdf\",\"fileSize\":848854,\"success\":true,\"code\":0} 上传相关代码 示例 加入 ‘com.squareup.okhttp3:okhttp:3.3.1’ 包 private void uploadFile(final String fileName, String parentId, final DaoCallback callback){ preUploadFile(fileName, parentId, new DaoCallback () { @Override public void onSuccess(JSONObject data) { int code = data.optInt(\"code\", 1); final String url = data.optString(\"url\", null); final String uploadToken = data.optString(\"upload token\"); if (code == 0) { // File file = new File(filePath); RequestBody fileContent = RequestBody.create(MultipartBody.FORM, file); RequestBody requestBody = new MultipartBody.Builder() .setType(MultipartBody.FORM) .addFormDataPart(\"file\", fileName, fileContent) .addFormDataPart(\"upload token\", uploadToken) .build(); Request request = new Request.Builder() .url(url) .post(requestBody) .build(); // 上传需要较长的时间，因此需要设置较长的 timeout OkHttpClient okHttpClient = new OkHttpClient(); okHttpClient.newCall(request) .enqueue(new okhttp3.Callback() { @Override public void onFailure(okhttp3.Call call, IOException e) { callback.onFailure( 1, null); } @Override public void onResponse(okhttp3.Call call, okhttp3.Response response) throws IOException { int httpCode = response.code(); if (httpCode == 200) { try { JSONObject result = new JSONObject(response.body().string()); response.body().close(); boolean success = result.getBoolean(\"success\"); if (success) { callback.onSuccess(null); } else { int code = result.getInt(\"code\"); String msg = result.optString(\"msg\"); callback.onFailure(code, msg); } } catch (JSONException e) { callback.onFailure( 2, null); } } else { callback.onFailure(httpCode, null); } } }); } } @Override public void onFailure( int errorCode, String msg){ Log.e(\"FileTransfer\", \"filePreUpload 失败 errorCode=\" + errorCode); } }); } PDF 第 12 页 private void preUploadFile(String fileName, String parentId, final DaoCallback callback) { String preUploadUrl = \"http://private.babel.cc:80/api/file/preUploadFile.do?name=1234.jpg&parent id=0\"; // 传入相应的参数 name, parent id String authorization = \"Bearer d48d0a0e253c4a2985d8c5653f717d71\"; //根据说明 生成 Request request = new Request.Builder().url(preUploadUrl) .addHeader(\"Authorization\", authorization) .build(); OkHttpClient okHttpClient = new OkHttpClient(); okHttpClient.newCall(request).enqueue(new okhttp3.Callback() { @Override public void onFailure(okhttp3.Call call, IOException e) { Log.d(\"\", \"\"); } @Override public void onResponse(okhttp3.Call call, okhttp3.Response response) throws IOException { Log.d(\"\",\"\"); int httpCode = response.code(); if (httpCode == 200) { JSONObject result = null; try { result = new JSONObject(response.body().string()); } catch (JSONException e) { e.printStackTrace(); } try { boolean success = result.getBoolean(\"success\"); if (success) { String url = result.getString(\"url\"); callback.onSuccess(result); } else { int code = result.getInt(\"code\"); String msg = result.optString(\"msg\"); callback.onFailure(code, msg); } } catch (JSONException e) { callback.onFailure( 2, null); } } else { callback.onFailure(httpCode, null); } } }); } 获取下载文件地址 /api/file/getFileDownloadUrl.do HTTP 方法： GET URL 参数 参数名 Comment(说明) fileId 需要下载的文件 id（必填） string version 文件的版本号（可选） number 返回信息如下 {\"code\":0,\"success\":true,\"type\":\"文件类型\",\"url\":\"文件下载地址\"} 获取下载多文件地址 /api/file/downloadMultiFiles.do HTTP 方法： GET URL 参数 参数名 Comment(说明) fileIdArr 由需要下载的文件 id 组成的字符串，由符号“!“(半角)分割，比如下载 id 为 133 与 233 的两 个文件，则 fileIdArr 的值为“133!233” string 类型 PDF 第 13 页 返回信息如下 {\"code\":0,\"success\":true,\"type\":\"文件类型\",\"url\":\"文件下载地址\"} 返回值 url 为多个文件打包后的下载地址。 获取下载文件缩略图地址 /api/file/downloadThumbnail.do HTTP 方法： GET URL 参数 参数名 Comment(说明) fileId 需要下载的文件 id（必填） string version 文件的版本号（可选） number size 需要显示的缩略图尺寸，取宽高中的最大值 返回信息如下 {\"code\":0,\"success\":true, \"url\":\"文件下载地址\"} 返回值 url 为多个文件打包后的下载地址。 修改文件信息 /nd /api/file/update file HTTP 方法： POST 修改文件信息 POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填） string name 新文件名 （可选） string description 文件说明 （可选） string 返回信息如下 {\"code\":0,\"success\":true} 修改文件名 /nd /api/file/rename HTTP 方法： POST 修改文件信息 POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填） string name 新文件名 string 返回信息如下 {\"code\":0,\"success\":true} PDF 第 14 页 删除文件(到回收站） /nd /api/file/remove file HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file ids[] 目标文件 id 数组（必填） string[] 返回信息如下 {\"code\":0,\"success\":true} 删除文件（从回收站） /nd /api/file/remove from trash HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file ids[] 目标文件 id 数组（必填） string[] 返回信息如下 {\"code\":0,\"success\":true} 清空回收站 /nd /api/file/empty trash HTTP 方法： POST POST 请求体参数 参数名 说明 返回信息如下 {\"code\":0,\"success\":true} 恢复文件（从回收站） /nd /api/file/restore file HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file ids[] 目标文件 id 数组 string[] restoreAll 不填写 file ids, restoreAll 为 true，时恢复回收站中所有文件，boolean 返回信息如下 PDF 第 15 页 {\"code\":0,\"success\":true} 获取文件的所有版本信息 /nd /api/file/versions HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 目标文件 id（必填） string 返回信息如下 {\"code\":0,\"versions\":[],\"success\":true} 设置文件当前版本 /nd /api/file/version HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file id 目标文件 id （必填） string version 版本号（必填） number 返回信息如下 {\"code\":0,\"success\":true} 移动文件 /nd /api/file/move HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file ids 需要移动的目标文件 id 数组（必填） string target id 需要移动到的目标文件夹 id（必填） string 返回信息如下 {\"code\":0,\"success\":true} 拷贝文件 /nd /api/file/copy HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) PDF 第 16 页 file ids 需要拷贝的目标文件 id 数组（必填） string target id 需要拷贝到的目标文件夹 id（必填） string 返回信息如下 { \"code\": 0, \"copyKey\": \"81427630 054a 11ef 8355 db93b4b1d006\",\"fileNum\": 10, \"success\": true} 拷贝文件进度 /nd /api/file/copy progress HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) copyKey 查看拷贝进度 copyKey 由 copy 接口返回（必填） string 返回信息如下 { \"code\": 0, \"completed\": 10,\"total\": 10, \"result\": {}, \"success\": true} 文件日志 /nd /api/file/file logs HTTP 方法： GET GET 请求体参数 参数名 Comment(说明) file id 目标文件 id 数组（必填） string startIndex 获取日志的起始顺序 第几条日志开始返回（选填） int 默认 0， pageSize 每页返回的个数（选填） int type 日志类型(选填) int 默认 0, 查看所有记录， 1 仅查看访问记录，2 仅查看上传下载，3 仅查看匿名用 户，4 仅查看分享及邀请，5 仅查看删除记录 userName 某个用户名 (选填) string, 返回某个用户的日志 lang 语言(选填) 默认 cn, string 返回日志的语言 cn(中文) en(英文) 返回信息如下 {\"code\":0,\"success\":true, \"logs\":[], \"total\":50} 设置用户是否有权访问素材库 /nd /api/file/ set user access material library HTTP 方法： POST GET 请求体参数 参数名 Comment(说明) userId 用户的 id 数组数型 [usrId1, userId2]（必填） string can 是否可访问 数值类型 （必填） int 默认 0， 0： 不可访问， 1:可以访问 返回信息如下 {\"code\":0,\"success\":true} PDF 第 17 页 创建素材库分类 /nd /api/file/create material class HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) destDirFileId 目标文件夹 的 fileId（必填） string name 创建分类库的名称（必填） string accessType 分类可见性 (选填) 默认为公开 0. 0: // 公开 1: // 需要申请 2: // 部门公开 3: // 部门申请 4: // 保密 managerIds 负责人的 id 数组类型 [usrId1,userId2] departmentIds 分类可见性 限定部门 的部门 id (选填) 数组类型 [departmentId1,departmentId2] 返回信息如下 {\"code\":0, \"success\":true, \"materialClass\": {}} 创建子素材库 /nd /api/file/create material folder HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) destDirFileId 目标文件夹 的 fileId（必填） string name 创建分类库的名称（必填） string accessType 分类可见性 (选填) 默认为公开 0. 0: // 公开 1: // 需要申请 2: // 部门公开 3: // 部门申请 4: // 保密 managerId 负责人的 id (选填) string departmentIds 分类可见性 限定部门 的部门 id (选填) 数组类型 [departmentId1,departmentId2] assistantIds 素材库助理人员的 id （选填） 数组类型 [usrId1,userId2] 返回信息如下 {\"code\":0, \"success\":true, \"materialFolder\": {}} 共享文件相关 API PDF 第 18 页 获取文件的分享 url /nd/api/share/shareurl HTTP 方法： GET 获取文件的分享链接（先打开分享后，再获取该链接） URL 参数 参数名 Comment(说明) file id 文件 id string is https 返回的 share url 协议是否为 https 0 为 http, 1 为 https， 默认 0 number 返回字段说明 {\"code\":0,\"url\":\"https://private.babel.cc/share.do?s=http://private.babel.cc/share.do?s=MjY2OTYzNTk3OTU2NzEzOTtXZWQgSnVsIDAxIDIwMj AgMTg6MzM6NTAgR01UKzA4MDAgKEhvbmcgS29uZyBTdGFuZGFyZCBUaW1lKQ%3D%3D\",\"success\":true} 获取分享的权限列表 /nd/api/share/share roles HTTP 方法： GET URL 参数 参数名 Comment(说明) 返回字段说明 {\"code\":0,\"roles\":[],\"success\":true} 获取用户对于单个文件有权设置的分享角色 /nd/api/share/share role forfile HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 文件 id string 返回字段说明 {\"code\":0,\"roles\":[],\"success\":true} 创建链接分享 /nd/api/share/open link share HTTP 方法： POST 打开分享，获取新的分享链接，之前的链接失效。 PDF 第 19 页 POST 请求体参数 参数名 Comment(说明) file id 预分享的文件 id（必填） string link role id 分享的角色 string is https 返回的 share url 协议是否为 https number anonymousVisit 是否允许匿名访问，1 为允许，0 为不允许（可选，默认为 1） number 返回字段说明 {\"code\":0,\"share url\":\"http://private.babel.cc/share.do?s=http://private.babel.cc/share.do?s=MjY2OTYzNTk3OTU2NzEzOTtXZWQgSnV sIDAxIDIwMjAgMTg6MzM6NTAgR01UKzA4MDAgKEhvbmcgS29uZyBTdGFuZGFyZCBUaW1lKQ%3D%3D\",\"password\":\"\",\"success\":tru e} 关闭链接分享 /nd/api/share/close link share HTTP 方法： POST 关闭我打开的分享链接 POST 请求体参数 参数名 Comment(说明) file id 分享的文件 id（必填） string 返回字段说明 {\"code\":0,\"success\":true} 设置链接分享密码 /nd/api/share/set share password HTTP 方法： POST 文件链接分享已打开，设置链接分享的密码。 POST 请求体参数 参数名 Comment(说明) file id 预分享的文件 id（必填） string password 链接分享的密码 string is https 返回的 share url 协议是否为 https number 返回字段说明 {\"code\":0,\"success\":true, \"share url\": \"http://private.babel.cc/share.do?s=xxxxxxxxxxx\"} 邀请人员参与分享 /nd/api/share/invite share HTTP 方法： POST PDF 第 20 页 可以根据用户的邮箱或者手机来邀请某些人来访问文件 POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填） string share role 分享的权限的 id（以上所有人共享此权限）（必填） string emails[] 邮箱数组 string[] phones[] 手机号的数组 string[] 返回字段说明 {\"code\":0,\"success\":true} 获取所有分享参与人 /nd/api/share/share participants HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 文件 id（必填） string 返回字段说明 {\"code\":0,\"users\":[],\"success\":true} 设置分享参与人的权限角色 /nd/api/share/set participant role HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填） string babelshare id int（必填） 用户 id string role id int（必填） 角色 id string 返回字段说明 {\"code\":0,\"success\":true} 删除分享参与人 /nd/api/file/remove share participant HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) PDF 第 21 页 file id 文件 id（必填） string babelshare ids[] int （必填） 用户 id string 返回字段说明 {\"code\":0,\"success\":true} 提醒关注 /nd/api/file/focus file HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填） string user ids[] 提醒的用户的 id，此 id 应该在文件参与人中选取，否则提醒不会起作用（必填）string[] 返回字段说明 {\"code\":0,\"success\":true} 移除某人的关注 /nd/api/file/unfocus file HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填）string user ids[] 提醒的用户的 id，此 id 应该在文件参与人中选取，否则提醒不会起作用（必填） string[] 返回字段说明 {\"code\":0,\"success\":true} 获取关注文件的用户列表 /nd/api/file/user focusfile HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 文件 id（必填） string 返回字段说明 {\"code\":0,\"users\":[],\"success\":true} 获取可以关注文件的用户列表，并且标记已关注文件的用户 /nd/api/file/user can focusfile PDF 第 22 页 HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 文件 id（必填） string 返回字段说明 企业部门相关 API 获取当前企业信息 /nd/api/enterprise/current HTTP 方法： GET URL 参数 参数名 Comment(说明) 无 返回字段说明 {\"code\":0,\"enterprise\":{},\"success\":true} 获取企业所有部门信息 /nd/api/enterprise/departments HTTP 方法： GET URL 参数 参数名 Comment(说明) 无 返回字段说明 属性名 类型 说明 departments []数组 返回所有的部门信息 tree {}json 数据 返回部门的父子结构信息 code int sucess boolean 创建企业部门 /nd/api/enterprise/create department HTTP 方法： POST PDF 第 23 页 POST 请求体参数 参数名 Comment(说明) parent dep 父部门 id， 0 表示跟部门（必填）string name 部门名称（必填）string description 部门描述 string 返回字段说明 属性名 类型 说明 department {} json 数据结构 code int sucess boolean 获取部门角色列表 /nd/api/enterprise/dep role HTTP 方法： GET URL 参数 参数名 Comment(说明) 返回字段说明 属性名 类型 说明 roles []数组 { id, filePermission,enterpriseId,filePermission,managerPermission, default,nameEn,name} code int sucess boolean 添加部门人员 /nd/api/enterprise/add dep mem HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) department id 部门 id（必填）string user ids[] 用户列表 string[] role id 用户在部门中的角色 string PDF 第 24 页 返回字段说明 属性名 类型 说明 删除部门人员 /nd/api/enterprise/remove dep mem HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) department id 部门 id（必填）string user ids[] 人员的 id（必填）string[] 返回字段说明 属性名 类型 说明 获取自己所在部门信息 /nd/api/enterprise/mydeparments HTTP 方法： GET URL 参数 参数名 Comment(说明) 无 返回字段说明 属性名 类型 说明 departments []数组 返回我所在的部门信息 code int sucess boolean 获取部门人员 /nd/api/enterprise/departmentmembers PDF 第 25 页 HTTP 方法： GET URL 参数 参数名 Comment(说明) department id 部门 id（必填）string 返回字段说明 属性名 类型 说明 users 数组 ： {id, name, avatrUrl,} 添加企业成员 /nd/api/enterprise/add ent mem HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) email Email 邮箱 string password 密码 string enterprise role 企业成员角色, 可选 number department ids[] 该用户的部门， 可选 string[] department roles[] 在部门中的角色， 可选 string[] sex 性别 0 未设置 1 男 2 女 number name 用户名 string phone 手机号， 可选 string babelId 工号，可选 string spacelimit 个人空间限制，单位 GB, 0 表示不限制 number can ownfile 用户能否拥有个人文件， 1 使用企业总体设置, 0 没有个人文件, 1 有个人文件 number remarks 用户描述， 可选 string join time 用户加入企业时间，Unix time, 单位秒 number password is md5 传入密码是否需要 md5 加密, 0 非 md5 密码， 1 md5 加密过的密码 number 更新成员信息 /api/updateUserInfo.do HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) email 邮箱地址（搜索关键字，必须）string password 密码（修改密码，可选）string frozen 1 – 表示冻结， 0 – 表示解冻 （冻结该账号，可选）number password is md5 传入密码是否需要 md5 加密, 0 非 md5 密码， 1 md5 加密过的密码 number phone 手机号 (可选) string PDF 第 26 页 获取企业成员信息 /api/getEnterpriseMember.do HTTP 方法： GET URL 参数 参数名 Comment(说明) email 邮箱地址（搜索关键字）string phone 手机号（搜索关键字）string babelId 工号（搜索关键字）string email/phone/babelId 可选择其一 返回字段说明 {\"code\":0,\"success\":true,\"user\":{}} 获取企业所有成员 /nd/api/enterprise/enterprise members HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) lang 语言类型，cn 中文 ，en 英文 , 可选 options { departmentId: // 部门 id，不填写就是企业所有人员 roleId: // 角色 id， 不填写就是不限角色 \"userType\": 0, // 0 企业内人员， 1 外部人员 \"keyName\": \"\", // 搜索关键字： 人名，手机号，邮箱， 不填写就是所有人员 \"startIndex\": 0， \"pageSize\": 20, status: // 0 所有账号， 1 停用的账号 } 可选 返回字段说明 {\"code\":0,\"success\":true,\"members\":{},\"total\":xx} 获取企业日志 /nd/api/enterprise/enterprise logs HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) department id 部门 id，不填写就是所有部门的日志 string 可选 keyword 日志的相关搜索关键字 string 可选 PDF 第 27 页 startTime 日志起始时间 number 可选 endTime 日志截止时间 number 可选 startIndex int 可选 pageSize int 可选 返回字段说明 {\"code\":0,\"success\":true,\"logs\":{},\"total\":xx} 消息推送 API 发布公告 /nd/api/enterprise/broadcast HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) title 公告内容字符串（必填） string content 内容（必填）string target users[] UserId 数组，如果为空则表示全部人员接收，string[] target deps[] 目标部门，该部门及子部门所有成员都会收到通知，string[] target users 与 target deps 至少要填 1 个 返回字段说明 {\"code\":0,\"success\":true} 获取发布的公告 /nd/api/enterprise/broadcast HTTP 方法： GET URL 参数 参数名 Comment(说明) start index number pagesize number 返回字段说明 {\"code\":0,\"broadcasts\":[],\"total\":19,\"success\":true} 发送部门讨论 /nd/api/file/send dep discussion HTTP 方法： POST PDF 第 28 页 POST 请求体参数 参数名 Comment(说明) dep id 部门 id（必填） string message 信息字符（必填） string json 字符串, 格式{Type: “Text”, Body:”你好” } 返回字段说明 {\"code\":0,\"messageId\":99,\"success\":true} 获取部门讨论 /nd/api/file/dep discussion HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) dep id 部门 id（必填）string pagesize 页的大小 string start id 消息 id,只会获取此消息之前的消息，为空则获取最新消息 string 返回字段说明 {\"msgArr\":[],\"gotMoreMessages\":1,\"code\":0,\"success\":true} 获取企业日志 /nd/api/enterprise/enterprise logs HTTP 方法： GET URL 参数 参数名 Comment(说明) department id 部门 id（）string pagesize 页的大小 number，默认值 1000 start index 消息起始位置, number keyword 日志关键词 string startTime 起始日期: 秒 number endTime 截止日期 秒 number 返回字段说明 {\"logs\":[],\"total\":0,\"code\":0,\"success\":true} total 返回所有符合条件的(与分页 pageSize 无关) PDF 第 29 页 四、 JWT token 登录 在私有云部署中，可以开启 jwt token 的登录方式，在这种情况下，允许通过下面的 url 直接以某用户的身份免登录进入网盘系 统： /account/tokenLogin.do 参数： 参数名称 可选性 说明 可选值 默认值 userToken 必填 含有登录用户的加密信息（构造方 无 法详见下面的说明） fileId 可选 要访问的文件（夹）的 id，如果不 无 填写则打开用户根目录 closeTitleBar 可选 是否关闭标题栏 1 关闭 0 不关闭 0 disableEntMark 可选 是否隐藏左上角企业标识 1 隐藏 0 不隐藏 0 disableUserMark 可选 是否隐藏右上角用户设置入口 1 隐藏 0 不隐藏 0 defaultLang 可选 设置界面使用的语言 cn 中文 en 英文 zh HK 繁体 cn defaultClrTheme 可选 设置界面颜色主题 normal 标准模式，dark 暗色模式 normal 比如下面是以英文及暗色模式并隐藏右上角用户标志进入用户根目录界面 /account/tokenLogin.do userToken=xxxxxxxxxxxxxxxx defaultClrTheme=dark defaultLang=en disableUserMark=1 userToken 的构建 userToken 是含有登录用户信息的加密字符串，加密信息是通过标准的双方传输可信数据的安全机制 JWT 创建的口令字， JWT 加密的用户信息 JSONObject 内容如下： { payload: { email: “xxx@xxx.com”/“135XXXXXXX”/“XXXX”} time: now } 说明：其中 email, 可以是邮箱，手机号，工号； 代码如下： public static void main( String[] args ) { HashMap user = new HashMap (); user.put(\"email\", \"yuanchaozhao@qq.com\"); try { //token login String userToken = createTokenJWT(user); System.out.println(\" login token:\" + userToken); JSONObject parsed = parseTokenJWT(userToken); System.out.println(\" parsed:\" + parsed); System.out.println(\" 将此 token 作为参数放在 url 中即可， 如:\"); System.out.println(\"/account/tokenLogin.do?userToken=\" + userToken); } catch (Exception e) { System.out.println(e.getMessage()); } } 其它代码 参考 jwtToken 的生成代码，在认证接口二处有提供。 备注： JWT 即 JSON Web Tokens 的简写， 是满足工业标准 RFC7519 的一种通信加密解密机制，请参考： https://jwt.io/ PDF 第 30 页 五、 附录 通用 API 调用返回状态码 状态码 result code 码值 说明 0 成功 1 未知错误 2 参数错误 7 空间不足 12 禁止的用户操作 13 无效的 token 结束 the end" }, { "lang": "zh", "slug": "developer-api-jwt-status", "title": "消息与登录 API", "description": "消息与登录 API 的接口路径、方法、参数和返回字段。", "category": "消息与登录 API", "top_category": "API文档", "keywords": [ "API", "消息与登录 API", "开发者" ], "url": "zh/developer-api-jwt-status.html", "source": "content/zh/developer-api-jwt-status.md", "summary": "消息与登录 API PDF 第 1 页 企业开发 API V6.6 上海画擎信息科技有限公司 姜大军 PDF 第 2 页 目录 一、 获取企业开发账号 ..............................................................................................................................................................................4 二、 认证 API ............................................................................................................................................................................................. 6 认证接口一（登录回调方式） ................................................................................................................................................................6 认证接口二（免登录方式 – JWT token 方式，在私有云部署中，需要开启 jwt token 的登录方式） .............", "headings": [ { "level": 1, "title": "消息与登录 API", "id": "api" }, { "level": 3, "title": "PDF 第 1 页", "id": "pdf-1" }, { "level": 3, "title": "PDF 第 2 页", "id": "pdf-2" }, { "level": 3, "title": "PDF 第 3 页", "id": "pdf-3" }, { "level": 3, "title": "PDF 第 4 页", "id": "pdf-4" }, { "level": 2, "title": "一、 获取企业开发账号", "id": "section" }, { "level": 3, "title": "PDF 第 5 页", "id": "pdf-5" }, { "level": 3, "title": "PDF 第 6 页", "id": "pdf-6" }, { "level": 2, "title": "二、 认证 API", "id": "api-2" }, { "level": 3, "title": "认证接口一（登录回调方式）", "id": "section-2" }, { "level": 3, "title": "PDF 第 7 页", "id": "pdf-7" }, { "level": 3, "title": "PDF 第 8 页", "id": "pdf-8" }, { "level": 3, "title": "获取 token", "id": "token" }, { "level": 3, "title": "刷新 token", "id": "token-2" }, { "level": 2, "title": "三、 文件访问 API", "id": "api-3" }, { "level": 3, "title": "PDF 第 9 页", "id": "pdf-9" }, { "level": 3, "title": "获取文件列表", "id": "section-3" }, { "level": 3, "title": "获取文件信息", "id": "section-5" }, { "level": 3, "title": "PDF 第 10 页", "id": "pdf-10" }, { "level": 3, "title": "创建文件夹", "id": "section-7" }, { "level": 3, "title": "预上传文件", "id": "section-9" }, { "level": 3, "title": "PDF 第 11 页", "id": "pdf-11" }, { "level": 3, "title": "上传文件", "id": "section-12" }, { "level": 3, "title": "PDF 第 12 页", "id": "pdf-12" }, { "level": 3, "title": "获取下载文件地址", "id": "section-14" }, { "level": 3, "title": "获取下载多文件地址", "id": "section-16" }, { "level": 3, "title": "PDF 第 13 页", "id": "pdf-13" }, { "level": 3, "title": "获取下载文件缩略图地址", "id": "section-18" }, { "level": 3, "title": "修改文件信息", "id": "section-20" }, { "level": 3, "title": "修改文件信息", "id": "section-21" }, { "level": 3, "title": "修改文件名", "id": "section-23" }, { "level": 3, "title": "修改文件信息", "id": "section-24" }, { "level": 3, "title": "PDF 第 14 页", "id": "pdf-14" }, { "level": 3, "title": "删除文件(到回收站）", "id": "section-26" }, { "level": 3, "title": "删除文件（从回收站）", "id": "section-28" }, { "level": 3, "title": "清空回收站", "id": "section-30" }, { "level": 3, "title": "恢复文件（从回收站）", "id": "section-32" }, { "level": 3, "title": "PDF 第 15 页", "id": "pdf-15" }, { "level": 3, "title": "获取文件的所有版本信息", "id": "section-34" }, { "level": 3, "title": "设置文件当前版本", "id": "section-36" }, { "level": 3, "title": "移动文件", "id": "section-38" }, { "level": 3, "title": "拷贝文件", "id": "section-40" }, { "level": 3, "title": "PDF 第 16 页", "id": "pdf-16" }, { "level": 3, "title": "拷贝文件进度", "id": "section-42" }, { "level": 3, "title": "文件日志", "id": "section-44" }, { "level": 3, "title": "设置用户是否有权访问素材库", "id": "section-46" }, { "level": 3, "title": "PDF 第 17 页", "id": "pdf-17" }, { "level": 3, "title": "创建素材库分类", "id": "section-48" }, { "level": 3, "title": "创建子素材库", "id": "section-50" }, { "level": 2, "title": "共享文件相关 API", "id": "api-4" }, { "level": 3, "title": "PDF 第 18 页", "id": "pdf-18" }, { "level": 3, "title": "获取文件的分享 url", "id": "url-12" }, { "level": 3, "title": "获取分享的权限列表", "id": "section-53" }, { "level": 3, "title": "获取用户对于单个文件有权设置的分享角色", "id": "section-55" }, { "level": 3, "title": "创建链接分享", "id": "section-57" }, { "level": 3, "title": "PDF 第 19 页", "id": "pdf-19" }, { "level": 3, "title": "关闭链接分享", "id": "section-59" }, { "level": 3, "title": "设置链接分享密码", "id": "section-61" }, { "level": 3, "title": "邀请人员参与分享", "id": "section-63" }, { "level": 3, "title": "PDF 第 20 页", "id": "pdf-20" }, { "level": 3, "title": "获取所有分享参与人", "id": "section-65" }, { "level": 3, "title": "设置分享参与人的权限角色", "id": "section-67" }, { "level": 3, "title": "删除分享参与人", "id": "section-69" }, { "level": 3, "title": "PDF 第 21 页", "id": "pdf-21" }, { "level": 3, "title": "提醒关注", "id": "section-71" }, { "level": 3, "title": "移除某人的关注", "id": "section-73" }, { "level": 3, "title": "获取关注文件的用户列表", "id": "section-75" }, { "level": 3, "title": "获取可以关注文件的用户列表，并且标记已关注文件的用户", "id": "section-77" }, { "level": 3, "title": "PDF 第 22 页", "id": "pdf-22" }, { "level": 2, "title": "企业部门相关 API", "id": "api-5" }, { "level": 3, "title": "获取当前企业信息", "id": "section-79" }, { "level": 3, "title": "获取企业所有部门信息", "id": "section-81" }, { "level": 3, "title": "创建企业部门", "id": "section-83" }, { "level": 3, "title": "PDF 第 23 页", "id": "pdf-23" }, { "level": 3, "title": "获取部门角色列表", "id": "section-85" }, { "level": 3, "title": "添加部门人员", "id": "section-87" }, { "level": 3, "title": "PDF 第 24 页", "id": "pdf-24" }, { "level": 3, "title": "删除部门人员", "id": "section-89" }, { "level": 3, "title": "获取自己所在部门信息", "id": "section-91" }, { "level": 3, "title": "获取部门人员", "id": "section-93" }, { "level": 3, "title": "PDF 第 25 页", "id": "pdf-25" }, { "level": 3, "title": "添加企业成员", "id": "section-95" }, { "level": 3, "title": "更新成员信息", "id": "section-96" }, { "level": 3, "title": "PDF 第 26 页", "id": "pdf-26" }, { "level": 3, "title": "获取企业成员信息", "id": "section-97" }, { "level": 3, "title": "获取企业所有成员", "id": "section-99" }, { "level": 3, "title": "获取企业日志", "id": "section-101" }, { "level": 3, "title": "PDF 第 27 页", "id": "pdf-27" }, { "level": 2, "title": "消息推送 API", "id": "api-6" }, { "level": 3, "title": "发布公告", "id": "section-103" }, { "level": 3, "title": "获取发布的公告", "id": "section-105" }, { "level": 3, "title": "发送部门讨论", "id": "section-107" }, { "level": 3, "title": "PDF 第 28 页", "id": "pdf-28" }, { "level": 3, "title": "获取部门讨论", "id": "section-109" }, { "level": 3, "title": "获取企业日志", "id": "section-111" }, { "level": 3, "title": "PDF 第 29 页", "id": "pdf-29" }, { "level": 2, "title": "四、 JWT token 登录", "id": "jwt-token" }, { "level": 3, "title": "PDF 第 30 页", "id": "pdf-30" }, { "level": 2, "title": "五、 附录 通用 API 调用返回状态码", "id": "api-7" }, { "level": 2, "title": "状态码 result code", "id": "result-code" } ], "images": [], "text": "消息与登录 API PDF 第 1 页 企业开发 API V6.6 上海画擎信息科技有限公司 姜大军 PDF 第 2 页 目录 一、 获取企业开发账号 ..............................................................................................................................................................................4 二、 认证 API ............................................................................................................................................................................................. 6 认证接口一（登录回调方式） ................................................................................................................................................................6 认证接口二（免登录方式 – JWT token 方式，在私有云部署中，需要开启 jwt token 的登录方式） ....................................... 6 获取 token .................................................................................................................................................................................................8 刷新 token .................................................................................................................................................................................................8 三、 文件访问 API ..................................................................................................................................................................................... 8 获取文件列表 ............................................................................................................................................................................................9 获取文件信息 ............................................................................................................................................................................................9 创建文件夹 ..............................................................................................................................................................................................10 预上传文件 ..............................................................................................................................................................................................10 上传文件 ..................................................................................................................................................................................................11 获取下载文件地址 ..................................................................................................................................................................................12 获取下载多文件地址 ..............................................................................................................................................................................12 获取下载文件缩略图地址 ......................................................................................................................................................................13 修改文件信息 ..........................................................................................................................................................................................13 修改文件名 ..............................................................................................................................................................................................13 删除文件(到回收站） .............................................................................................................................................................................14 删除文件（从回收站） ..........................................................................................................................................................................14 清空回收站 ..............................................................................................................................................................................................14 恢复文件（从回收站） ..........................................................................................................................................................................14 获取文件的所有版本信息 ......................................................................................................................................................................15 设置文件当前版本 ..................................................................................................................................................................................15 移动文件 ..................................................................................................................................................................................................15 拷贝文件 ..................................................................................................................................................................................................15 拷贝文件进度 ..........................................................................................................................................................................................16 文件日志 ..................................................................................................................................................................................................16 创建素材库分类 ......................................................................................................................................................................................17 创建子素材库 ..........................................................................................................................................................................................17 共享文件相关 API ................................................................................................................................................................................. 17 获取文件的分享 url ................................................................................................................................................................................ 18 获取分享的权限列表 ..............................................................................................................................................................................18 获取用户对于单个文件有权设置的分享角色 ......................................................................................................................................18 创建链接分享 ..........................................................................................................................................................................................18 关闭链接分享 ..........................................................................................................................................................................................19 设置链接分享密码 ..................................................................................................................................................................................19 邀请人员参与分享 ..................................................................................................................................................................................19 获取所有分享参与人 ..............................................................................................................................................................................20 设置分享参与人的权限角色 ..................................................................................................................................................................20 删除分享参与人 ......................................................................................................................................................................................20 提醒关注 ..................................................................................................................................................................................................21 移除某人的关注 ......................................................................................................................................................................................21 获取关注文件的用户列表 ......................................................................................................................................................................21 获取可以关注文件的用户列表，并且标记已关注文件的用户 ..........................................................................................................21 企业部门相关 API ................................................................................................................................................................................. 22 获取当前企业信息 ..................................................................................................................................................................................22 获取企业所有部门信息 ..........................................................................................................................................................................22 创建企业部门 ..........................................................................................................................................................................................22 获取部门角色列表 ..................................................................................................................................................................................23 添加部门人员 ..........................................................................................................................................................................................23 删除部门人员 ..........................................................................................................................................................................................24 获取自己所在部门信息 ..........................................................................................................................................................................24 获取部门人员 ..........................................................................................................................................................................................24 添加企业成员 ..........................................................................................................................................................................................25 更新成员信息 ..........................................................................................................................................................................................25 获取企业成员信息 ..................................................................................................................................................................................26 获取企业所有成员 ..................................................................................................................................................................................26 获取企业日志 ..........................................................................................................................................................................................26 消息推送 API ......................................................................................................................................................................................... 27 发布公告 ..................................................................................................................................................................................................27 获取发布的公告 ......................................................................................................................................................................................27 发送部门讨论 ..........................................................................................................................................................................................27 获取部门讨论 ..........................................................................................................................................................................................28 获取企业日志 ..........................................................................................................................................................................................28 四、 JWT token 登录 .................................................................................................................................................................................29 五、 附录 通用 API 调用返回状态码 ............................................................................................................................................... 30 PDF 第 3 页 状态码 result code ................................................................................................................................................................................. 30 PDF 第 4 页 一、 获取企业开发账号 登录巴别鸟私有云企业管理后台，在首页中设置开发者账号： 打开后填写回调函数地址：http://xxx.xxx.xxx.xxx/public/babelAuthResult.do 填写后点击确定后自动产生开发者 id (client id)和开发者密钥(client secret)： 注：jwtToken 为相应的生成 jwtToken 时的加密密钥。 PDF 第 5 页 PDF 第 6 页 二、 认证 API 认证接口一（登录回调方式） /api/authorize.do HTTP 请求方式 GET URL 参数 参数名 Comment(说明) response type 必须为 code（必填） string client id 开发者的 id（必填） string redirect uri 回调函数地址，需要和注册时保持一致（必填） string data 任意数据，回调时传回 string 例如： /api/authorize.do?response type=code&client id=xxxxx&redirect uri=http://xxx.xxx.xxx&data=xxx 通过浏览器访问 返回结果 如果用户未登录，则会跳转到登录页，登录后如果未授权，则会 302 跳转到授权页，如果用户已经授权，则会 302 跳转到 redirect uri 并且带上授权码和 data，类似于 http://xxx.xxx.xxx?code=xxx&data=xxx code 有效期 5 分钟。 认证接口二（免登录方式 – JWT token 方式，在私有云部署中，需要开启 jwt token 的登录方 式） /api/authorizeByJWT.do HTTP 请求方式 GET URL 参数 参数名 Comment(说明) response type 必须为 code（必填） string client id 开发者的 id（必填） string jwt token Jwt token，（必填） string 是对{client id: xxxxxxx} 加密 形成的字符串 email email(可选), 传入用户的邮箱，以该用户进行登录，不填以企业管理员进行登录，string phone phone(可选), 传入用户的手机号，以该用户进行登录，不填以企业管理员进行登录， string babelId babelId(可选), 传入用户的工号，以该用户进行登录，不填以企业管理员进行登录， string PDF 第 7 页 例如： /api/authorizeByJWT.do?response type=code&client id=xxxxx&jwt token=xxx 说明：使用这个 api，如果不填 email, phone, babelId 系统将自动以管理员身份登录，否则会以 email, phone, babelId 对应的用户去 登录，不会显示登录界面去登录。注（email, phone, babelId）只需其中一个就可。 返回结果 { \"success\": true \"code\": \"xxxxxxxxxxxxxxxxxxxxxxxxx\", } jwt token 为 自己写程序生成 样例代码如下: import java.util.Date; import java.util.HashMap; import java.util.Map; import javax.crypto.SecretKey; import javax.crypto.spec.SecretKeySpec; import io.jsonwebtoken.Claims; import io.jsonwebtoken.JwtBuilder; import io.jsonwebtoken.Jwts; import io.jsonwebtoken.SignatureAlgorithm; import net.sf.json.JSONObject; / 生成标准 jwt 使用的 token / public class JWT App { static String skey = \"babeldfdfer95840834 t8e 9 9 5934 5943 5886256\"; // 密钥 在巴别鸟后台 开发者账号处 填入的 jwtToken 字段。 public static void main( String[] args ) { HashMap clientInfo = new HashMap (); clientInfo.put(\"client id\", \"7459492016147273\"); // 为开发者账户中的 client id try { String token = createTokenJWT(clientInfo); System.out.println(\" login token:\" + token); String token1 = \"eyJhbGciOiJIUzI1NiJ9.eyJkdXJhdGlvbiI6NjAsInBheWxvYWQiOnsiY2xpZW50X2lkIjoiNzQ1OTQ5MjAxNjE0NzI3MyJ9LCJ0aW1lIjoxNjkxNDg4MzY4NTk0fQ.pRFCwXd2snMr IgFWOFwYbvyAeeNhoFINGk Wmv7d24g\"; JSONObject parsed = parseTokenJWT(token1); System.out.println(\" parsed:\" + parsed); System.out.println(\" 将此 token 作为参数放在 url 中即可， 如:\"); } catch (Exception e) { System.out.println(e.getMessage()); } } public static String createTokenJWT(Map config) throws Exception { HashMap data = new HashMap (); data.put(\"time\", new Date().getTime()); data.put(\"duration\", 60); data.put(\"payload\", config); SignatureAlgorithm signatureAlgorithm = SignatureAlgorithm.HS256; SecretKey key = generalKey(); JwtBuilder builder = Jwts.builder() .setClaims(data) .signWith(signatureAlgorithm, key); System.out.println( \" builder :\" + builder); return builder.compact(); } public static JSONObject parseTokenJWT(String jwt) throws Exception { SecretKey key = generalKey(); Claims claims = Jwts.parser() .setSigningKey(key) .parseClaimsJws(jwt) .getBody(); System.out.println(\" claims:\" + claims.toString()); Long time = (Long)claims.get(\"time\"); long duration = (Integer)claims.get(\"duration\"); Long now = new Date().getTime(); if (now time 1000 duration) return null; // 超过 10 分钟的 token 无效 JSONObject obj = JSONObject.fromObject(claims.get(\"payload\")); return obj; } public static SecretKey generalKey(){ String stringKey = skey; byte[] encodedKey = stringKey.getBytes(); SecretKey key = new SecretKeySpec(encodedKey, 0, encodedKey.length, \"HmacSHA256\"); return key; } } PDF 第 8 页 获取 token /api/token.do HTTP 方法： POST HTTP Header 该接口使用 Basic Auth 的方式校验 client 的信息。具体做法是在 header 中添加类似于\"Authorization: Basic xxxxxxxxx\"。其中 \"xxxxxxxxx\"是通过开发者 id (client id)和开发者秘钥(client secret)算出来的，具体算法为 Base64Encode(client id + \":\" + client secret) Base64Encode 自行选择工具进行 Base64 编码 URL 参数 参数名 Comment(说明) grant type（必填） 必须为 authorization code string code（必填） 授权码，即回调地址接收到的授权码，授权码的有效期为 5 分钟，用过一次，无论成功 还是失败，授权码都会失效 string 例如： /api/token.do?grant type=authorization code&code=xxx&redirect uri=http://xxx.xxx.xxx 返回结果 access token 接口访问标识 refresh token 用来刷新 access token，有效时间为 30 天 expires in access token 的有效时间，单位为 s 刷新 token /api/refreshToken.do HTTP 方法： POST HTTP Header 该接口使用 Basic Auth 的方式校验 client 的信息。具体做法是在 header 中添加类似于\"Authorization: Basic xxxxxxxxx\"。其中 \"xxxxxxxxx\"是通过 client id 和 client secret 算出来的，具体算法为 Base64Encode(client id + \":\" + client secret) URL 参数 参数名 Comment(说明) grant type（必填） 必须为 refresh token string refresh token（必填） 即接口 2 中获取到的 refresh token string 例如： /api/refreshToken.do?grant type=refresh token&refresh token=xxx 返回结果 access token 接口访问标识, refresh token 用来刷新 access token，有效时间为 30 天 expires in access token 的有效时间 为 3600，单位为 s 三、 文件访问 API 所有的接口在访问时需要在 HTTP header 中带上 access token。对于含有请求参数的接口，通常是一些 POST、 PUT 或者 DELETE 接口，还需要设置 Content Type 来指定参数的格式。如果需要访问不同版本的 API，就需要 在请求路径上指定具体版本，如果需要返回不同格式的 response body，那么还需要设置 Accept。所有的参数都应 该采用 utf 8 的编码。 PDF 第 9 页 Headers： Authorization：存放 access token，格式为：\"Bearer \" + access token。 Content Type：指明请求参数的格式。如果是 POST、PUT 或者 DELETE 请求，需要指定\"application/json\"，我 们目前不支持其他请求参数的格式，比如 xml。如果是其他类型比如 GET 请求，可以不在 header 中设置 Content Type。 Accept：用于指定响应结果的格式以及 api 的版本信息。目前只支持返回 json 格式的 response，所以一般情况下 指定\"application/json\"。 若接口访问成功，我们会返回 json 格式的 response，并且 HTTP 的 status code 为 200。所有请求成功的 response 的 json 都会带有\"success: true”。response 的 header 里的 X Babel Version 表示此次请求访问的 api 的版本号。 获取文件列表 /nd/api/file/list dir HTTP 方法： GET URL 参数 参数名 Comment(说明) parent id 父文件夹 id（必填） string 当 parent 为 1 时返回企业文件夹内容，2 返回个人文件夹内容，3 返回我的 项目，4 返回我加入的分享，其它 fileId 返回正常的文件夹中的内容。 page size 页的大小 number page 页号 number type 类型：分为 1 file，2 folder，0 all 三种类型 string 返回字段说明 属性名 类型 说明 files 数组 文件信息 {fileId, name, …} total int 总数量 page int 页容量 success boolean 获取成功标记 code int 返回错误码 0 表示成功 获取文件信息 /nd/api/file/fileinfo HTTP 方法： GET URL 参数 参数名 Comment(说明) id 文件 id（必填） string 返回字段说明 fileInfo 信息 属性名 类型 说明 file Object 文件信息 { id, name, …} PDF 第 10 页 success boolean 获取成功标记 code int 返回错误码 0 表示成功 创建文件夹 /nd/api/file/create folder HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) parent id 目标文件夹 id（必填） string name 文件名（必填） string 返回字段说明 属性名 类型 说明 file Object 文件信息 { id, name, …} success boolean 获取成功标记 code int 返回错误码 0 表示成功 预上传文件 用于返回第二步上传文件时所需要的参数(url、upload token) /api/file/preUploadFile.do HTTP 方法： GET URL 参数 参数名 Comment(说明) parent id 目标文件夹 id（必填）(在根目录下上传可忽略此项) string name 文件名（必填） string file id 上传新版本时需要指定上传那个文件的新版本(上传新文件可忽略此项) string 正确的返回结果如下 {\"upload token\":\"92808ecfc2ac4e0ebc0b912edac3be4a\",\"url\":\"http://testdocument.babel.cc/api/file/uploadPdf.do\",\"su ccess\":true,\"code\":0} 返回字段说明 属性名 类型 说明 url string 该 url 仅能使用 1 次，且有效期为 1 小时 调用此 url 上传文件，成功后会返回 fileId， fileName、version 等 upload token string 上传文件时作为 post 的参数 PDF 第 11 页 上传文件 注意，本 api 的 url 是预上传接口返回的, 这里没有具体的 url，只是参数说明 https://xxx.xxx.xxx:xxx/api/file/uploadXXX.do（具体的 url 是由上一节 /api/file/preUploadFile.do 中返回的 url） POST POST 请求体参数 参数名 Comment(说明) file 文件二进制数据(上传数据) upload token /api/file/preUploadFile.do 请求中的返回值 返回信息如下 {\"fileId\":\"7728538212615908\",\"version\":0,\"fileName\":\"mesos.pdf\",\"fileSize\":848854,\"success\":true,\"code\":0} 上传相关代码 示例 加入 ‘com.squareup.okhttp3:okhttp:3.3.1’ 包 private void uploadFile(final String fileName, String parentId, final DaoCallback callback){ preUploadFile(fileName, parentId, new DaoCallback () { @Override public void onSuccess(JSONObject data) { int code = data.optInt(\"code\", 1); final String url = data.optString(\"url\", null); final String uploadToken = data.optString(\"upload token\"); if (code == 0) { // File file = new File(filePath); RequestBody fileContent = RequestBody.create(MultipartBody.FORM, file); RequestBody requestBody = new MultipartBody.Builder() .setType(MultipartBody.FORM) .addFormDataPart(\"file\", fileName, fileContent) .addFormDataPart(\"upload token\", uploadToken) .build(); Request request = new Request.Builder() .url(url) .post(requestBody) .build(); // 上传需要较长的时间，因此需要设置较长的 timeout OkHttpClient okHttpClient = new OkHttpClient(); okHttpClient.newCall(request) .enqueue(new okhttp3.Callback() { @Override public void onFailure(okhttp3.Call call, IOException e) { callback.onFailure( 1, null); } @Override public void onResponse(okhttp3.Call call, okhttp3.Response response) throws IOException { int httpCode = response.code(); if (httpCode == 200) { try { JSONObject result = new JSONObject(response.body().string()); response.body().close(); boolean success = result.getBoolean(\"success\"); if (success) { callback.onSuccess(null); } else { int code = result.getInt(\"code\"); String msg = result.optString(\"msg\"); callback.onFailure(code, msg); } } catch (JSONException e) { callback.onFailure( 2, null); } } else { callback.onFailure(httpCode, null); } } }); } } @Override public void onFailure( int errorCode, String msg){ Log.e(\"FileTransfer\", \"filePreUpload 失败 errorCode=\" + errorCode); } }); } PDF 第 12 页 private void preUploadFile(String fileName, String parentId, final DaoCallback callback) { String preUploadUrl = \"http://private.babel.cc:80/api/file/preUploadFile.do?name=1234.jpg&parent id=0\"; // 传入相应的参数 name, parent id String authorization = \"Bearer d48d0a0e253c4a2985d8c5653f717d71\"; //根据说明 生成 Request request = new Request.Builder().url(preUploadUrl) .addHeader(\"Authorization\", authorization) .build(); OkHttpClient okHttpClient = new OkHttpClient(); okHttpClient.newCall(request).enqueue(new okhttp3.Callback() { @Override public void onFailure(okhttp3.Call call, IOException e) { Log.d(\"\", \"\"); } @Override public void onResponse(okhttp3.Call call, okhttp3.Response response) throws IOException { Log.d(\"\",\"\"); int httpCode = response.code(); if (httpCode == 200) { JSONObject result = null; try { result = new JSONObject(response.body().string()); } catch (JSONException e) { e.printStackTrace(); } try { boolean success = result.getBoolean(\"success\"); if (success) { String url = result.getString(\"url\"); callback.onSuccess(result); } else { int code = result.getInt(\"code\"); String msg = result.optString(\"msg\"); callback.onFailure(code, msg); } } catch (JSONException e) { callback.onFailure( 2, null); } } else { callback.onFailure(httpCode, null); } } }); } 获取下载文件地址 /api/file/getFileDownloadUrl.do HTTP 方法： GET URL 参数 参数名 Comment(说明) fileId 需要下载的文件 id（必填） string version 文件的版本号（可选） number 返回信息如下 {\"code\":0,\"success\":true,\"type\":\"文件类型\",\"url\":\"文件下载地址\"} 获取下载多文件地址 /api/file/downloadMultiFiles.do HTTP 方法： GET URL 参数 参数名 Comment(说明) fileIdArr 由需要下载的文件 id 组成的字符串，由符号“!“(半角)分割，比如下载 id 为 133 与 233 的两 个文件，则 fileIdArr 的值为“133!233” string 类型 PDF 第 13 页 返回信息如下 {\"code\":0,\"success\":true,\"type\":\"文件类型\",\"url\":\"文件下载地址\"} 返回值 url 为多个文件打包后的下载地址。 获取下载文件缩略图地址 /api/file/downloadThumbnail.do HTTP 方法： GET URL 参数 参数名 Comment(说明) fileId 需要下载的文件 id（必填） string version 文件的版本号（可选） number size 需要显示的缩略图尺寸，取宽高中的最大值 返回信息如下 {\"code\":0,\"success\":true, \"url\":\"文件下载地址\"} 返回值 url 为多个文件打包后的下载地址。 修改文件信息 /nd /api/file/update file HTTP 方法： POST 修改文件信息 POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填） string name 新文件名 （可选） string description 文件说明 （可选） string 返回信息如下 {\"code\":0,\"success\":true} 修改文件名 /nd /api/file/rename HTTP 方法： POST 修改文件信息 POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填） string name 新文件名 string 返回信息如下 {\"code\":0,\"success\":true} PDF 第 14 页 删除文件(到回收站） /nd /api/file/remove file HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file ids[] 目标文件 id 数组（必填） string[] 返回信息如下 {\"code\":0,\"success\":true} 删除文件（从回收站） /nd /api/file/remove from trash HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file ids[] 目标文件 id 数组（必填） string[] 返回信息如下 {\"code\":0,\"success\":true} 清空回收站 /nd /api/file/empty trash HTTP 方法： POST POST 请求体参数 参数名 说明 返回信息如下 {\"code\":0,\"success\":true} 恢复文件（从回收站） /nd /api/file/restore file HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file ids[] 目标文件 id 数组 string[] restoreAll 不填写 file ids, restoreAll 为 true，时恢复回收站中所有文件，boolean 返回信息如下 PDF 第 15 页 {\"code\":0,\"success\":true} 获取文件的所有版本信息 /nd /api/file/versions HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 目标文件 id（必填） string 返回信息如下 {\"code\":0,\"versions\":[],\"success\":true} 设置文件当前版本 /nd /api/file/version HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file id 目标文件 id （必填） string version 版本号（必填） number 返回信息如下 {\"code\":0,\"success\":true} 移动文件 /nd /api/file/move HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file ids 需要移动的目标文件 id 数组（必填） string target id 需要移动到的目标文件夹 id（必填） string 返回信息如下 {\"code\":0,\"success\":true} 拷贝文件 /nd /api/file/copy HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) PDF 第 16 页 file ids 需要拷贝的目标文件 id 数组（必填） string target id 需要拷贝到的目标文件夹 id（必填） string 返回信息如下 { \"code\": 0, \"copyKey\": \"81427630 054a 11ef 8355 db93b4b1d006\",\"fileNum\": 10, \"success\": true} 拷贝文件进度 /nd /api/file/copy progress HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) copyKey 查看拷贝进度 copyKey 由 copy 接口返回（必填） string 返回信息如下 { \"code\": 0, \"completed\": 10,\"total\": 10, \"result\": {}, \"success\": true} 文件日志 /nd /api/file/file logs HTTP 方法： GET GET 请求体参数 参数名 Comment(说明) file id 目标文件 id 数组（必填） string startIndex 获取日志的起始顺序 第几条日志开始返回（选填） int 默认 0， pageSize 每页返回的个数（选填） int type 日志类型(选填) int 默认 0, 查看所有记录， 1 仅查看访问记录，2 仅查看上传下载，3 仅查看匿名用 户，4 仅查看分享及邀请，5 仅查看删除记录 userName 某个用户名 (选填) string, 返回某个用户的日志 lang 语言(选填) 默认 cn, string 返回日志的语言 cn(中文) en(英文) 返回信息如下 {\"code\":0,\"success\":true, \"logs\":[], \"total\":50} 设置用户是否有权访问素材库 /nd /api/file/ set user access material library HTTP 方法： POST GET 请求体参数 参数名 Comment(说明) userId 用户的 id 数组数型 [usrId1, userId2]（必填） string can 是否可访问 数值类型 （必填） int 默认 0， 0： 不可访问， 1:可以访问 返回信息如下 {\"code\":0,\"success\":true} PDF 第 17 页 创建素材库分类 /nd /api/file/create material class HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) destDirFileId 目标文件夹 的 fileId（必填） string name 创建分类库的名称（必填） string accessType 分类可见性 (选填) 默认为公开 0. 0: // 公开 1: // 需要申请 2: // 部门公开 3: // 部门申请 4: // 保密 managerIds 负责人的 id 数组类型 [usrId1,userId2] departmentIds 分类可见性 限定部门 的部门 id (选填) 数组类型 [departmentId1,departmentId2] 返回信息如下 {\"code\":0, \"success\":true, \"materialClass\": {}} 创建子素材库 /nd /api/file/create material folder HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) destDirFileId 目标文件夹 的 fileId（必填） string name 创建分类库的名称（必填） string accessType 分类可见性 (选填) 默认为公开 0. 0: // 公开 1: // 需要申请 2: // 部门公开 3: // 部门申请 4: // 保密 managerId 负责人的 id (选填) string departmentIds 分类可见性 限定部门 的部门 id (选填) 数组类型 [departmentId1,departmentId2] assistantIds 素材库助理人员的 id （选填） 数组类型 [usrId1,userId2] 返回信息如下 {\"code\":0, \"success\":true, \"materialFolder\": {}} 共享文件相关 API PDF 第 18 页 获取文件的分享 url /nd/api/share/shareurl HTTP 方法： GET 获取文件的分享链接（先打开分享后，再获取该链接） URL 参数 参数名 Comment(说明) file id 文件 id string is https 返回的 share url 协议是否为 https 0 为 http, 1 为 https， 默认 0 number 返回字段说明 {\"code\":0,\"url\":\"https://private.babel.cc/share.do?s=http://private.babel.cc/share.do?s=MjY2OTYzNTk3OTU2NzEzOTtXZWQgSnVsIDAxIDIwMj AgMTg6MzM6NTAgR01UKzA4MDAgKEhvbmcgS29uZyBTdGFuZGFyZCBUaW1lKQ%3D%3D\",\"success\":true} 获取分享的权限列表 /nd/api/share/share roles HTTP 方法： GET URL 参数 参数名 Comment(说明) 返回字段说明 {\"code\":0,\"roles\":[],\"success\":true} 获取用户对于单个文件有权设置的分享角色 /nd/api/share/share role forfile HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 文件 id string 返回字段说明 {\"code\":0,\"roles\":[],\"success\":true} 创建链接分享 /nd/api/share/open link share HTTP 方法： POST 打开分享，获取新的分享链接，之前的链接失效。 PDF 第 19 页 POST 请求体参数 参数名 Comment(说明) file id 预分享的文件 id（必填） string link role id 分享的角色 string is https 返回的 share url 协议是否为 https number anonymousVisit 是否允许匿名访问，1 为允许，0 为不允许（可选，默认为 1） number 返回字段说明 {\"code\":0,\"share url\":\"http://private.babel.cc/share.do?s=http://private.babel.cc/share.do?s=MjY2OTYzNTk3OTU2NzEzOTtXZWQgSnV sIDAxIDIwMjAgMTg6MzM6NTAgR01UKzA4MDAgKEhvbmcgS29uZyBTdGFuZGFyZCBUaW1lKQ%3D%3D\",\"password\":\"\",\"success\":tru e} 关闭链接分享 /nd/api/share/close link share HTTP 方法： POST 关闭我打开的分享链接 POST 请求体参数 参数名 Comment(说明) file id 分享的文件 id（必填） string 返回字段说明 {\"code\":0,\"success\":true} 设置链接分享密码 /nd/api/share/set share password HTTP 方法： POST 文件链接分享已打开，设置链接分享的密码。 POST 请求体参数 参数名 Comment(说明) file id 预分享的文件 id（必填） string password 链接分享的密码 string is https 返回的 share url 协议是否为 https number 返回字段说明 {\"code\":0,\"success\":true, \"share url\": \"http://private.babel.cc/share.do?s=xxxxxxxxxxx\"} 邀请人员参与分享 /nd/api/share/invite share HTTP 方法： POST PDF 第 20 页 可以根据用户的邮箱或者手机来邀请某些人来访问文件 POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填） string share role 分享的权限的 id（以上所有人共享此权限）（必填） string emails[] 邮箱数组 string[] phones[] 手机号的数组 string[] 返回字段说明 {\"code\":0,\"success\":true} 获取所有分享参与人 /nd/api/share/share participants HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 文件 id（必填） string 返回字段说明 {\"code\":0,\"users\":[],\"success\":true} 设置分享参与人的权限角色 /nd/api/share/set participant role HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填） string babelshare id int（必填） 用户 id string role id int（必填） 角色 id string 返回字段说明 {\"code\":0,\"success\":true} 删除分享参与人 /nd/api/file/remove share participant HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) PDF 第 21 页 file id 文件 id（必填） string babelshare ids[] int （必填） 用户 id string 返回字段说明 {\"code\":0,\"success\":true} 提醒关注 /nd/api/file/focus file HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填） string user ids[] 提醒的用户的 id，此 id 应该在文件参与人中选取，否则提醒不会起作用（必填）string[] 返回字段说明 {\"code\":0,\"success\":true} 移除某人的关注 /nd/api/file/unfocus file HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填）string user ids[] 提醒的用户的 id，此 id 应该在文件参与人中选取，否则提醒不会起作用（必填） string[] 返回字段说明 {\"code\":0,\"success\":true} 获取关注文件的用户列表 /nd/api/file/user focusfile HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 文件 id（必填） string 返回字段说明 {\"code\":0,\"users\":[],\"success\":true} 获取可以关注文件的用户列表，并且标记已关注文件的用户 /nd/api/file/user can focusfile PDF 第 22 页 HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 文件 id（必填） string 返回字段说明 企业部门相关 API 获取当前企业信息 /nd/api/enterprise/current HTTP 方法： GET URL 参数 参数名 Comment(说明) 无 返回字段说明 {\"code\":0,\"enterprise\":{},\"success\":true} 获取企业所有部门信息 /nd/api/enterprise/departments HTTP 方法： GET URL 参数 参数名 Comment(说明) 无 返回字段说明 属性名 类型 说明 departments []数组 返回所有的部门信息 tree {}json 数据 返回部门的父子结构信息 code int sucess boolean 创建企业部门 /nd/api/enterprise/create department HTTP 方法： POST PDF 第 23 页 POST 请求体参数 参数名 Comment(说明) parent dep 父部门 id， 0 表示跟部门（必填）string name 部门名称（必填）string description 部门描述 string 返回字段说明 属性名 类型 说明 department {} json 数据结构 code int sucess boolean 获取部门角色列表 /nd/api/enterprise/dep role HTTP 方法： GET URL 参数 参数名 Comment(说明) 返回字段说明 属性名 类型 说明 roles []数组 { id, filePermission,enterpriseId,filePermission,managerPermission, default,nameEn,name} code int sucess boolean 添加部门人员 /nd/api/enterprise/add dep mem HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) department id 部门 id（必填）string user ids[] 用户列表 string[] role id 用户在部门中的角色 string PDF 第 24 页 返回字段说明 属性名 类型 说明 删除部门人员 /nd/api/enterprise/remove dep mem HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) department id 部门 id（必填）string user ids[] 人员的 id（必填）string[] 返回字段说明 属性名 类型 说明 获取自己所在部门信息 /nd/api/enterprise/mydeparments HTTP 方法： GET URL 参数 参数名 Comment(说明) 无 返回字段说明 属性名 类型 说明 departments []数组 返回我所在的部门信息 code int sucess boolean 获取部门人员 /nd/api/enterprise/departmentmembers PDF 第 25 页 HTTP 方法： GET URL 参数 参数名 Comment(说明) department id 部门 id（必填）string 返回字段说明 属性名 类型 说明 users 数组 ： {id, name, avatrUrl,} 添加企业成员 /nd/api/enterprise/add ent mem HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) email Email 邮箱 string password 密码 string enterprise role 企业成员角色, 可选 number department ids[] 该用户的部门， 可选 string[] department roles[] 在部门中的角色， 可选 string[] sex 性别 0 未设置 1 男 2 女 number name 用户名 string phone 手机号， 可选 string babelId 工号，可选 string spacelimit 个人空间限制，单位 GB, 0 表示不限制 number can ownfile 用户能否拥有个人文件， 1 使用企业总体设置, 0 没有个人文件, 1 有个人文件 number remarks 用户描述， 可选 string join time 用户加入企业时间，Unix time, 单位秒 number password is md5 传入密码是否需要 md5 加密, 0 非 md5 密码， 1 md5 加密过的密码 number 更新成员信息 /api/updateUserInfo.do HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) email 邮箱地址（搜索关键字，必须）string password 密码（修改密码，可选）string frozen 1 – 表示冻结， 0 – 表示解冻 （冻结该账号，可选）number password is md5 传入密码是否需要 md5 加密, 0 非 md5 密码， 1 md5 加密过的密码 number phone 手机号 (可选) string PDF 第 26 页 获取企业成员信息 /api/getEnterpriseMember.do HTTP 方法： GET URL 参数 参数名 Comment(说明) email 邮箱地址（搜索关键字）string phone 手机号（搜索关键字）string babelId 工号（搜索关键字）string email/phone/babelId 可选择其一 返回字段说明 {\"code\":0,\"success\":true,\"user\":{}} 获取企业所有成员 /nd/api/enterprise/enterprise members HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) lang 语言类型，cn 中文 ，en 英文 , 可选 options { departmentId: // 部门 id，不填写就是企业所有人员 roleId: // 角色 id， 不填写就是不限角色 \"userType\": 0, // 0 企业内人员， 1 外部人员 \"keyName\": \"\", // 搜索关键字： 人名，手机号，邮箱， 不填写就是所有人员 \"startIndex\": 0， \"pageSize\": 20, status: // 0 所有账号， 1 停用的账号 } 可选 返回字段说明 {\"code\":0,\"success\":true,\"members\":{},\"total\":xx} 获取企业日志 /nd/api/enterprise/enterprise logs HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) department id 部门 id，不填写就是所有部门的日志 string 可选 keyword 日志的相关搜索关键字 string 可选 PDF 第 27 页 startTime 日志起始时间 number 可选 endTime 日志截止时间 number 可选 startIndex int 可选 pageSize int 可选 返回字段说明 {\"code\":0,\"success\":true,\"logs\":{},\"total\":xx} 消息推送 API 发布公告 /nd/api/enterprise/broadcast HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) title 公告内容字符串（必填） string content 内容（必填）string target users[] UserId 数组，如果为空则表示全部人员接收，string[] target deps[] 目标部门，该部门及子部门所有成员都会收到通知，string[] target users 与 target deps 至少要填 1 个 返回字段说明 {\"code\":0,\"success\":true} 获取发布的公告 /nd/api/enterprise/broadcast HTTP 方法： GET URL 参数 参数名 Comment(说明) start index number pagesize number 返回字段说明 {\"code\":0,\"broadcasts\":[],\"total\":19,\"success\":true} 发送部门讨论 /nd/api/file/send dep discussion HTTP 方法： POST PDF 第 28 页 POST 请求体参数 参数名 Comment(说明) dep id 部门 id（必填） string message 信息字符（必填） string json 字符串, 格式{Type: “Text”, Body:”你好” } 返回字段说明 {\"code\":0,\"messageId\":99,\"success\":true} 获取部门讨论 /nd/api/file/dep discussion HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) dep id 部门 id（必填）string pagesize 页的大小 string start id 消息 id,只会获取此消息之前的消息，为空则获取最新消息 string 返回字段说明 {\"msgArr\":[],\"gotMoreMessages\":1,\"code\":0,\"success\":true} 获取企业日志 /nd/api/enterprise/enterprise logs HTTP 方法： GET URL 参数 参数名 Comment(说明) department id 部门 id（）string pagesize 页的大小 number，默认值 1000 start index 消息起始位置, number keyword 日志关键词 string startTime 起始日期: 秒 number endTime 截止日期 秒 number 返回字段说明 {\"logs\":[],\"total\":0,\"code\":0,\"success\":true} total 返回所有符合条件的(与分页 pageSize 无关) PDF 第 29 页 四、 JWT token 登录 在私有云部署中，可以开启 jwt token 的登录方式，在这种情况下，允许通过下面的 url 直接以某用户的身份免登录进入网盘系 统： /account/tokenLogin.do 参数： 参数名称 可选性 说明 可选值 默认值 userToken 必填 含有登录用户的加密信息（构造方 无 法详见下面的说明） fileId 可选 要访问的文件（夹）的 id，如果不 无 填写则打开用户根目录 closeTitleBar 可选 是否关闭标题栏 1 关闭 0 不关闭 0 disableEntMark 可选 是否隐藏左上角企业标识 1 隐藏 0 不隐藏 0 disableUserMark 可选 是否隐藏右上角用户设置入口 1 隐藏 0 不隐藏 0 defaultLang 可选 设置界面使用的语言 cn 中文 en 英文 zh HK 繁体 cn defaultClrTheme 可选 设置界面颜色主题 normal 标准模式，dark 暗色模式 normal 比如下面是以英文及暗色模式并隐藏右上角用户标志进入用户根目录界面 /account/tokenLogin.do userToken=xxxxxxxxxxxxxxxx defaultClrTheme=dark defaultLang=en disableUserMark=1 userToken 的构建 userToken 是含有登录用户信息的加密字符串，加密信息是通过标准的双方传输可信数据的安全机制 JWT 创建的口令字， JWT 加密的用户信息 JSONObject 内容如下： { payload: { email: “xxx@xxx.com”/“135XXXXXXX”/“XXXX”} time: now } 说明：其中 email, 可以是邮箱，手机号，工号； 代码如下： public static void main( String[] args ) { HashMap user = new HashMap (); user.put(\"email\", \"yuanchaozhao@qq.com\"); try { //token login String userToken = createTokenJWT(user); System.out.println(\" login token:\" + userToken); JSONObject parsed = parseTokenJWT(userToken); System.out.println(\" parsed:\" + parsed); System.out.println(\" 将此 token 作为参数放在 url 中即可， 如:\"); System.out.println(\"/account/tokenLogin.do?userToken=\" + userToken); } catch (Exception e) { System.out.println(e.getMessage()); } } 其它代码 参考 jwtToken 的生成代码，在认证接口二处有提供。 备注： JWT 即 JSON Web Tokens 的简写， 是满足工业标准 RFC7519 的一种通信加密解密机制，请参考： https://jwt.io/ PDF 第 30 页 五、 附录 通用 API 调用返回状态码 状态码 result code 码值 说明 0 成功 1 未知错误 2 参数错误 7 空间不足 12 禁止的用户操作 13 无效的 token 结束 the end" }, { "lang": "zh", "slug": "api-get-api-authorize-do", "title": "认证接口一（登录回调方式）", "description": "GET /api/authorize.do：认证接口一（登录回调方式） 接口说明，包含路径、方法、参数和返回信息。", "category": "认证 API", "top_category": "API文档", "keywords": [ "API", "认证接口一（登录回调方式）", "/api/authorize.do" ], "url": "zh/api-get-api-authorize-do.html", "source": "content/zh/api-get-api-authorize-do.md", "summary": "认证接口一（登录回调方式） 属性 值 HTTP 方法 GET 接口路径 /api/authorize.do 所属分类 认证 API 接口说明 接口路径： /api/authorize.do HTTP 方法： GET HTTP 请求方式 GET URL 参数 参数名 Comment(说明) response type 必须为 code（必填） string client id 开发者的 id（必填） string redirect uri 回调函数地址，需要和注册时保持一致（必填） string data 任意数据，回调时传回 string 例如： /api/authorize.do?response type=code&client id=xxxxx&redirect uri=http://xxx.xxx.xxx&data=xxx 通过浏览器访问 返回结果 如果用户未登录，则会跳转到登录页，登录后如果未授权，则会 302 跳转到授权页，如果用户已经授权，则会 302 跳转到 redirect uri 并且带上授权码和 data，类似于 http://xxx.xxx.xxx?code=xxx&data=xxx code 有效期 5 分钟。 认证接口二（免登录方式 – JWT token 方式，在私有云部署中，需要开启 jwt token 的登录方 式） 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类", "headings": [ { "level": 1, "title": "认证接口一（登录回调方式）", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-3" } ], "images": [], "text": "认证接口一（登录回调方式） 属性 值 HTTP 方法 GET 接口路径 /api/authorize.do 所属分类 认证 API 接口说明 接口路径： /api/authorize.do HTTP 方法： GET HTTP 请求方式 GET URL 参数 参数名 Comment(说明) response type 必须为 code（必填） string client id 开发者的 id（必填） string redirect uri 回调函数地址，需要和注册时保持一致（必填） string data 任意数据，回调时传回 string 例如： /api/authorize.do?response type=code&client id=xxxxx&redirect uri=http://xxx.xxx.xxx&data=xxx 通过浏览器访问 返回结果 如果用户未登录，则会跳转到登录页，登录后如果未授权，则会 302 跳转到授权页，如果用户已经授权，则会 302 跳转到 redirect uri 并且带上授权码和 data，类似于 http://xxx.xxx.xxx?code=xxx&data=xxx code 有效期 5 分钟。 认证接口二（免登录方式 – JWT token 方式，在私有云部署中，需要开启 jwt token 的登录方 式） 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：认证 API。" }, { "lang": "zh", "slug": "api-get-api-authorizebyjwt-do", "title": "认证接口二（免登录 JWT token 方式）", "description": "GET /api/authorizeByJWT.do：认证接口二（免登录 JWT token 方式） 接口说明，包含路径、方法、参数和返回信息。", "category": "认证 API", "top_category": "API文档", "keywords": [ "API", "认证接口二（免登录 JWT token 方式）", "/api/authorizeByJWT.do" ], "url": "zh/api-get-api-authorizebyjwt-do.html", "source": "content/zh/api-get-api-authorizebyjwt-do.md", "summary": "认证接口二（免登录 JWT token 方式） 属性 值 HTTP 方法 GET 接口路径 /api/authorizeByJWT.do 所属分类 认证 API 接口说明 接口路径： /api/authorizeByJWT.do HTTP 方法： GET 所属小节：认证接口一（登录回调方式） HTTP 请求方式 GET URL 参数 参数名 Comment(说明) response type 必须为 code（必填） string client id 开发者的 id（必填） string jwt token Jwt token，（必填） string 是对{client id: xxxxxxx} 加密 形成的字符串 email email(可选), 传入用户的邮箱，以该用户进行登录，不填以企业管理员进行登录，string phone phone(可选), 传入用户的手机号，以该用户进行登录，不填以企业管理员进行登录， string babelId babelId(可选), 传入用户的工号，以该用户进行登录，不填以企业管理员进行登录， string 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：认证 API。", "headings": [ { "level": 1, "title": "认证接口二（免登录 JWT token 方式）", "id": "jwt-token" }, { "level": 2, "title": "接口说明", "id": "section" }, { "level": 2, "title": "调用说明", "id": "section-2" } ], "images": [], "text": "认证接口二（免登录 JWT token 方式） 属性 值 HTTP 方法 GET 接口路径 /api/authorizeByJWT.do 所属分类 认证 API 接口说明 接口路径： /api/authorizeByJWT.do HTTP 方法： GET 所属小节：认证接口一（登录回调方式） HTTP 请求方式 GET URL 参数 参数名 Comment(说明) response type 必须为 code（必填） string client id 开发者的 id（必填） string jwt token Jwt token，（必填） string 是对{client id: xxxxxxx} 加密 形成的字符串 email email(可选), 传入用户的邮箱，以该用户进行登录，不填以企业管理员进行登录，string phone phone(可选), 传入用户的手机号，以该用户进行登录，不填以企业管理员进行登录， string babelId babelId(可选), 传入用户的工号，以该用户进行登录，不填以企业管理员进行登录， string 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：认证 API。" }, { "lang": "zh", "slug": "api-post-api-token-do", "title": "获取 token", "description": "POST /api/token.do：获取 token 接口说明，包含路径、方法、参数和返回信息。", "category": "认证 API", "top_category": "API文档", "keywords": [ "API", "获取 token", "/api/token.do" ], "url": "zh/api-post-api-token-do.html", "source": "content/zh/api-post-api-token-do.md", "summary": "获取 token 属性 值 HTTP 方法 POST 接口路径 /api/token.do 所属分类 认证 API 接口说明 接口路径： /api/token.do HTTP 方法： POST HTTP 方法： POST HTTP Header 该接口使用 Basic Auth 的方式校验 client 的信息。具体做法是在 header 中添加类似于\"Authorization: Basic xxxxxxxxx\"。其中 \"xxxxxxxxx\"是通过开发者 id (client id)和开发者秘钥(client secret)算出来的，具体算法为 Base64Encode(client id + \":\" + client secret) Base64Encode 自行选择工具进行 Base64 编码 URL 参数 参数名 Comment(说明) grant type（必填） 必须为 authorization code string code（必填） 授权码，即回调地址接收到的授权码，授权码的有效期为 5 分钟，用过一次，无论成功 还是失败，授权码都会失效 string 例如： /api/token.do?grant type=authorization code&code=xxx&redirect uri=http://xxx.xxx.xxx 返回结果 access token 接口访问标识 refresh token 用来刷新 access token，有效时间为 30 天 expires in access token 的有效时间，单位为 s 调用说明 调用前需完成 获取", "headings": [ { "level": 1, "title": "获取 token", "id": "token" }, { "level": 2, "title": "接口说明", "id": "section" }, { "level": 2, "title": "调用说明", "id": "section-2" } ], "images": [], "text": "获取 token 属性 值 HTTP 方法 POST 接口路径 /api/token.do 所属分类 认证 API 接口说明 接口路径： /api/token.do HTTP 方法： POST HTTP 方法： POST HTTP Header 该接口使用 Basic Auth 的方式校验 client 的信息。具体做法是在 header 中添加类似于\"Authorization: Basic xxxxxxxxx\"。其中 \"xxxxxxxxx\"是通过开发者 id (client id)和开发者秘钥(client secret)算出来的，具体算法为 Base64Encode(client id + \":\" + client secret) Base64Encode 自行选择工具进行 Base64 编码 URL 参数 参数名 Comment(说明) grant type（必填） 必须为 authorization code string code（必填） 授权码，即回调地址接收到的授权码，授权码的有效期为 5 分钟，用过一次，无论成功 还是失败，授权码都会失效 string 例如： /api/token.do?grant type=authorization code&code=xxx&redirect uri=http://xxx.xxx.xxx 返回结果 access token 接口访问标识 refresh token 用来刷新 access token，有效时间为 30 天 expires in access token 的有效时间，单位为 s 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：认证 API。" }, { "lang": "zh", "slug": "api-post-api-refreshtoken-do", "title": "刷新 token", "description": "POST /api/refreshToken.do：刷新 token 接口说明，包含路径、方法、参数和返回信息。", "category": "认证 API", "top_category": "API文档", "keywords": [ "API", "刷新 token", "/api/refreshToken.do" ], "url": "zh/api-post-api-refreshtoken-do.html", "source": "content/zh/api-post-api-refreshtoken-do.md", "summary": "刷新 token 属性 值 HTTP 方法 POST 接口路径 /api/refreshToken.do 所属分类 认证 API 接口说明 接口路径： /api/refreshToken.do HTTP 方法： POST HTTP 方法： POST HTTP Header 该接口使用 Basic Auth 的方式校验 client 的信息。具体做法是在 header 中添加类似于\"Authorization: Basic xxxxxxxxx\"。其中 \"xxxxxxxxx\"是通过 client id 和 client secret 算出来的，具体算法为 Base64Encode(client id + \":\" + client secret) URL 参数 参数名 Comment(说明) grant type（必填） 必须为 refresh token string refresh token（必填） 即接口 2 中获取到的 refresh token string 例如： /api/refreshToken.do?grant type=refresh token&refresh token=xxx 返回结果 access token 接口访问标识, refresh token 用来刷新 access token，有效时间为 30 天 expires in access token 的有效时间 为 3600，单位为 s 三、 文件访问 API 所有的接口在访问时需要在 HTTP header 中带上 access token。对于含有请求参数的接口，通常是一些 POST、 PUT", "headings": [ { "level": 1, "title": "刷新 token", "id": "token" }, { "level": 2, "title": "接口说明", "id": "section" }, { "level": 2, "title": "三、 文件访问 API", "id": "api" }, { "level": 2, "title": "调用说明", "id": "section-2" } ], "images": [], "text": "刷新 token 属性 值 HTTP 方法 POST 接口路径 /api/refreshToken.do 所属分类 认证 API 接口说明 接口路径： /api/refreshToken.do HTTP 方法： POST HTTP 方法： POST HTTP Header 该接口使用 Basic Auth 的方式校验 client 的信息。具体做法是在 header 中添加类似于\"Authorization: Basic xxxxxxxxx\"。其中 \"xxxxxxxxx\"是通过 client id 和 client secret 算出来的，具体算法为 Base64Encode(client id + \":\" + client secret) URL 参数 参数名 Comment(说明) grant type（必填） 必须为 refresh token string refresh token（必填） 即接口 2 中获取到的 refresh token string 例如： /api/refreshToken.do?grant type=refresh token&refresh token=xxx 返回结果 access token 接口访问标识, refresh token 用来刷新 access token，有效时间为 30 天 expires in access token 的有效时间 为 3600，单位为 s 三、 文件访问 API 所有的接口在访问时需要在 HTTP header 中带上 access token。对于含有请求参数的接口，通常是一些 POST、 PUT 或者 DELETE 接口，还需要设置 Content Type 来指定参数的格式。如果需要访问不同版本的 API，就需要 在请求路径上指定具体版本，如果需要返回不同格式的 response body，那么还需要设置 Accept。所有的参数都应 该采用 utf 8 的编码。 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：认证 API。" }, { "lang": "zh", "slug": "api-get-nd-api-file-list-dir", "title": "获取文件列表", "description": "GET /nd/api/file/list_dir：获取文件列表 接口说明，包含路径、方法、参数和返回信息。", "category": "文件 API", "top_category": "API文档", "keywords": [ "API", "获取文件列表", "/nd/api/file/list_dir" ], "url": "zh/api-get-nd-api-file-list-dir.html", "source": "content/zh/api-get-nd-api-file-list-dir.md", "summary": "获取文件列表 属性 值 HTTP 方法 GET 接口路径 /nd/api/file/list dir 所属分类 文件 API 接口说明 接口路径： /nd/api/file/list dir HTTP 方法： GET HTTP 方法： GET URL 参数 参数名 Comment(说明) parent id 父文件夹 id（必填） string 当 parent 为 1 时返回企业文件夹内容，2 返回个人文件夹内容，3 返回我的 项目，4 返回我加入的分享，其它 fileId 返回正常的文件夹中的内容。 page size 页的大小 number page 页号 number type 类型：分为 1 file，2 folder，0 all 三种类型 string 返回字段说明 属性名 类型 说明 files 数组 文件信息 {fileId, name, …} total int 总数量 page int 页容量 success boolean 获取成功标记 code int 返回错误码 0 表示成功 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。", "headings": [ { "level": 1, "title": "获取文件列表", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-4" } ], "images": [], "text": "获取文件列表 属性 值 HTTP 方法 GET 接口路径 /nd/api/file/list dir 所属分类 文件 API 接口说明 接口路径： /nd/api/file/list dir HTTP 方法： GET HTTP 方法： GET URL 参数 参数名 Comment(说明) parent id 父文件夹 id（必填） string 当 parent 为 1 时返回企业文件夹内容，2 返回个人文件夹内容，3 返回我的 项目，4 返回我加入的分享，其它 fileId 返回正常的文件夹中的内容。 page size 页的大小 number page 页号 number type 类型：分为 1 file，2 folder，0 all 三种类型 string 返回字段说明 属性名 类型 说明 files 数组 文件信息 {fileId, name, …} total int 总数量 page int 页容量 success boolean 获取成功标记 code int 返回错误码 0 表示成功 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。" }, { "lang": "zh", "slug": "api-get-nd-api-file-fileinfo", "title": "获取文件信息", "description": "GET /nd/api/file/fileinfo：获取文件信息 接口说明，包含路径、方法、参数和返回信息。", "category": "文件 API", "top_category": "API文档", "keywords": [ "API", "获取文件信息", "/nd/api/file/fileinfo" ], "url": "zh/api-get-nd-api-file-fileinfo.html", "source": "content/zh/api-get-nd-api-file-fileinfo.md", "summary": "获取文件信息 属性 值 HTTP 方法 GET 接口路径 /nd/api/file/fileinfo 所属分类 文件 API 接口说明 接口路径： /nd/api/file/fileinfo HTTP 方法： GET HTTP 方法： GET URL 参数 参数名 Comment(说明) id 文件 id（必填） string 返回字段说明 fileInfo 信息 属性名 类型 说明 file Object 文件信息 { id, name, …} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。", "headings": [ { "level": 1, "title": "获取文件信息", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-4" } ], "images": [], "text": "获取文件信息 属性 值 HTTP 方法 GET 接口路径 /nd/api/file/fileinfo 所属分类 文件 API 接口说明 接口路径： /nd/api/file/fileinfo HTTP 方法： GET HTTP 方法： GET URL 参数 参数名 Comment(说明) id 文件 id（必填） string 返回字段说明 fileInfo 信息 属性名 类型 说明 file Object 文件信息 { id, name, …} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。" }, { "lang": "zh", "slug": "api-post-nd-api-file-create-folder", "title": "创建文件夹", "description": "POST /nd/api/file/create_folder：创建文件夹 接口说明，包含路径、方法、参数和返回信息。", "category": "文件 API", "top_category": "API文档", "keywords": [ "API", "创建文件夹", "/nd/api/file/create_folder" ], "url": "zh/api-post-nd-api-file-create-folder.html", "source": "content/zh/api-post-nd-api-file-create-folder.md", "summary": "创建文件夹 属性 值 HTTP 方法 POST 接口路径 /nd/api/file/create folder 所属分类 文件 API 接口说明 接口路径： /nd/api/file/create folder HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) parent id 目标文件夹 id（必填） string name 文件名（必填） string 返回字段说明 属性名 类型 说明 file Object 文件信息 { id, name, …} success boolean 获取成功标记 code int 返回错误码 0 表示成功 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。", "headings": [ { "level": 1, "title": "创建文件夹", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-4" } ], "images": [], "text": "创建文件夹 属性 值 HTTP 方法 POST 接口路径 /nd/api/file/create folder 所属分类 文件 API 接口说明 接口路径： /nd/api/file/create folder HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) parent id 目标文件夹 id（必填） string name 文件名（必填） string 返回字段说明 属性名 类型 说明 file Object 文件信息 { id, name, …} success boolean 获取成功标记 code int 返回错误码 0 表示成功 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。" }, { "lang": "zh", "slug": "api-get-api-file-preuploadfile-do", "title": "预上传文件", "description": "GET /api/file/preUploadFile.do：预上传文件 接口说明，包含路径、方法、参数和返回信息。", "category": "文件 API", "top_category": "API文档", "keywords": [ "API", "预上传文件", "/api/file/preUploadFile.do" ], "url": "zh/api-get-api-file-preuploadfile-do.html", "source": "content/zh/api-get-api-file-preuploadfile-do.md", "summary": "预上传文件 属性 值 HTTP 方法 GET 接口路径 /api/file/preUploadFile.do 所属分类 文件 API 接口说明 接口路径： /api/file/preUploadFile.do HTTP 方法： GET HTTP 方法： GET URL 参数 参数名 Comment(说明) parent id 目标文件夹 id（必填）(在根目录下上传可忽略此项) string name 文件名（必填） string file id 上传新版本时需要指定上传那个文件的新版本(上传新文件可忽略此项) string 正确的返回结果如下 {\"upload token\":\"92808ecfc2ac4e0ebc0b912edac3be4a\",\"url\":\"http://testdocument.babel.cc/api/file/uploadPdf.do\",\"su ccess\":true,\"code\":0} 返回字段说明 属性名 类型 说明 url string 该 url 仅能使用 1 次，且有效期为 1 小时 调用此 url 上传文件，成功后会返回 fileId， fileName、version 等 upload token string 上传文件时作为 post 的参数 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。", "headings": [ { "level": 1, "title": "预上传文件", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-5" } ], "images": [], "text": "预上传文件 属性 值 HTTP 方法 GET 接口路径 /api/file/preUploadFile.do 所属分类 文件 API 接口说明 接口路径： /api/file/preUploadFile.do HTTP 方法： GET HTTP 方法： GET URL 参数 参数名 Comment(说明) parent id 目标文件夹 id（必填）(在根目录下上传可忽略此项) string name 文件名（必填） string file id 上传新版本时需要指定上传那个文件的新版本(上传新文件可忽略此项) string 正确的返回结果如下 {\"upload token\":\"92808ecfc2ac4e0ebc0b912edac3be4a\",\"url\":\"http://testdocument.babel.cc/api/file/uploadPdf.do\",\"su ccess\":true,\"code\":0} 返回字段说明 属性名 类型 说明 url string 该 url 仅能使用 1 次，且有效期为 1 小时 调用此 url 上传文件，成功后会返回 fileId， fileName、version 等 upload token string 上传文件时作为 post 的参数 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。" }, { "lang": "zh", "slug": "api-get-api-file-getfiledownloadurl-do", "title": "获取下载文件地址", "description": "GET /api/file/getFileDownloadUrl.do：获取下载文件地址 接口说明，包含路径、方法、参数和返回信息。", "category": "文件 API", "top_category": "API文档", "keywords": [ "API", "获取下载文件地址", "/api/file/getFileDownloadUrl.do" ], "url": "zh/api-get-api-file-getfiledownloadurl-do.html", "source": "content/zh/api-get-api-file-getfiledownloadurl-do.md", "summary": "获取下载文件地址 属性 值 HTTP 方法 GET 接口路径 /api/file/getFileDownloadUrl.do 所属分类 文件 API 接口说明 接口路径： /api/file/getFileDownloadUrl.do HTTP 方法： GET HTTP 方法： GET URL 参数 参数名 Comment(说明) fileId 需要下载的文件 id（必填） string version 文件的版本号（可选） number 返回信息如下 {\"code\":0,\"success\":true,\"type\":\"文件类型\",\"url\":\"文件下载地址\"} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。", "headings": [ { "level": 1, "title": "获取下载文件地址", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-4" } ], "images": [], "text": "获取下载文件地址 属性 值 HTTP 方法 GET 接口路径 /api/file/getFileDownloadUrl.do 所属分类 文件 API 接口说明 接口路径： /api/file/getFileDownloadUrl.do HTTP 方法： GET HTTP 方法： GET URL 参数 参数名 Comment(说明) fileId 需要下载的文件 id（必填） string version 文件的版本号（可选） number 返回信息如下 {\"code\":0,\"success\":true,\"type\":\"文件类型\",\"url\":\"文件下载地址\"} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。" }, { "lang": "zh", "slug": "api-get-api-file-downloadmultifiles-do", "title": "获取下载多文件地址", "description": "GET /api/file/downloadMultiFiles.do：获取下载多文件地址 接口说明，包含路径、方法、参数和返回信息。", "category": "文件 API", "top_category": "API文档", "keywords": [ "API", "获取下载多文件地址", "/api/file/downloadMultiFiles.do" ], "url": "zh/api-get-api-file-downloadmultifiles-do.html", "source": "content/zh/api-get-api-file-downloadmultifiles-do.md", "summary": "获取下载多文件地址 属性 值 HTTP 方法 GET 接口路径 /api/file/downloadMultiFiles.do 所属分类 文件 API 接口说明 接口路径： /api/file/downloadMultiFiles.do HTTP 方法： GET HTTP 方法： GET URL 参数 参数名 Comment(说明) fileIdArr 由需要下载的文件 id 组成的字符串，由符号“!“(半角)分割，比如下载 id 为 133 与 233 的两 个文件，则 fileIdArr 的值为“133!233” string 类型 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。", "headings": [ { "level": 1, "title": "获取下载多文件地址", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-3" } ], "images": [], "text": "获取下载多文件地址 属性 值 HTTP 方法 GET 接口路径 /api/file/downloadMultiFiles.do 所属分类 文件 API 接口说明 接口路径： /api/file/downloadMultiFiles.do HTTP 方法： GET HTTP 方法： GET URL 参数 参数名 Comment(说明) fileIdArr 由需要下载的文件 id 组成的字符串，由符号“!“(半角)分割，比如下载 id 为 133 与 233 的两 个文件，则 fileIdArr 的值为“133!233” string 类型 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。" }, { "lang": "zh", "slug": "api-get-api-file-downloadthumbnail-do", "title": "获取下载文件缩略图地址", "description": "GET /api/file/downloadThumbnail.do：获取下载文件缩略图地址 接口说明，包含路径、方法、参数和返回信息。", "category": "文件 API", "top_category": "API文档", "keywords": [ "API", "获取下载文件缩略图地址", "/api/file/downloadThumbnail.do" ], "url": "zh/api-get-api-file-downloadthumbnail-do.html", "source": "content/zh/api-get-api-file-downloadthumbnail-do.md", "summary": "获取下载文件缩略图地址 属性 值 HTTP 方法 GET 接口路径 /api/file/downloadThumbnail.do 所属分类 文件 API 接口说明 接口路径： /api/file/downloadThumbnail.do HTTP 方法： GET HTTP 方法： GET URL 参数 参数名 Comment(说明) fileId 需要下载的文件 id（必填） string version 文件的版本号（可选） number size 需要显示的缩略图尺寸，取宽高中的最大值 返回信息如下 {\"code\":0,\"success\":true, \"url\":\"文件下载地址\"} 返回值 url 为多个文件打包后的下载地址。 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。", "headings": [ { "level": 1, "title": "获取下载文件缩略图地址", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-4" } ], "images": [], "text": "获取下载文件缩略图地址 属性 值 HTTP 方法 GET 接口路径 /api/file/downloadThumbnail.do 所属分类 文件 API 接口说明 接口路径： /api/file/downloadThumbnail.do HTTP 方法： GET HTTP 方法： GET URL 参数 参数名 Comment(说明) fileId 需要下载的文件 id（必填） string version 文件的版本号（可选） number size 需要显示的缩略图尺寸，取宽高中的最大值 返回信息如下 {\"code\":0,\"success\":true, \"url\":\"文件下载地址\"} 返回值 url 为多个文件打包后的下载地址。 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。" }, { "lang": "zh", "slug": "api-post-nd-api-file-update-file", "title": "修改文件信息", "description": "POST /nd/api/file/update_file：修改文件信息 接口说明，包含路径、方法、参数和返回信息。", "category": "文件 API", "top_category": "API文档", "keywords": [ "API", "修改文件信息", "/nd/api/file/update_file" ], "url": "zh/api-post-nd-api-file-update-file.html", "source": "content/zh/api-post-nd-api-file-update-file.md", "summary": "修改文件信息 属性 值 HTTP 方法 POST 接口路径 /nd/api/file/update file 所属分类 文件 API 接口说明 接口路径： /nd/api/file/update file HTTP 方法： POST HTTP 方法： POST 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。", "headings": [ { "level": 1, "title": "修改文件信息", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-3" } ], "images": [], "text": "修改文件信息 属性 值 HTTP 方法 POST 接口路径 /nd/api/file/update file 所属分类 文件 API 接口说明 接口路径： /nd/api/file/update file HTTP 方法： POST HTTP 方法： POST 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。" }, { "lang": "zh", "slug": "api-post-nd-api-file-rename", "title": "修改文件名", "description": "POST /nd/api/file/rename：修改文件名 接口说明，包含路径、方法、参数和返回信息。", "category": "文件 API", "top_category": "API文档", "keywords": [ "API", "修改文件名", "/nd/api/file/rename" ], "url": "zh/api-post-nd-api-file-rename.html", "source": "content/zh/api-post-nd-api-file-rename.md", "summary": "修改文件名 属性 值 HTTP 方法 POST 接口路径 /nd/api/file/rename 所属分类 文件 API 接口说明 接口路径： /nd/api/file/rename HTTP 方法： POST HTTP 方法： POST 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。", "headings": [ { "level": 1, "title": "修改文件名", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-3" } ], "images": [], "text": "修改文件名 属性 值 HTTP 方法 POST 接口路径 /nd/api/file/rename 所属分类 文件 API 接口说明 接口路径： /nd/api/file/rename HTTP 方法： POST HTTP 方法： POST 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。" }, { "lang": "zh", "slug": "api-post-nd-api-file-remove-file", "title": "删除文件(到回收站）", "description": "POST /nd/api/file/remove_file：删除文件(到回收站） 接口说明，包含路径、方法、参数和返回信息。", "category": "文件 API", "top_category": "API文档", "keywords": [ "API", "删除文件(到回收站）", "/nd/api/file/remove_file" ], "url": "zh/api-post-nd-api-file-remove-file.html", "source": "content/zh/api-post-nd-api-file-remove-file.md", "summary": "删除文件(到回收站） 属性 值 HTTP 方法 POST 接口路径 /nd/api/file/remove file 所属分类 文件 API 接口说明 接口路径： /nd/api/file/remove file HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file ids[] 目标文件 id 数组（必填） string[] 返回信息如下 {\"code\":0,\"success\":true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。", "headings": [ { "level": 1, "title": "删除文件(到回收站）", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-4" } ], "images": [], "text": "删除文件(到回收站） 属性 值 HTTP 方法 POST 接口路径 /nd/api/file/remove file 所属分类 文件 API 接口说明 接口路径： /nd/api/file/remove file HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file ids[] 目标文件 id 数组（必填） string[] 返回信息如下 {\"code\":0,\"success\":true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。" }, { "lang": "zh", "slug": "api-post-nd-api-file-remove-from-trash", "title": "删除文件（从回收站）", "description": "POST /nd/api/file/remove_from_trash：删除文件（从回收站） 接口说明，包含路径、方法、参数和返回信息。", "category": "文件 API", "top_category": "API文档", "keywords": [ "API", "删除文件（从回收站）", "/nd/api/file/remove_from_trash" ], "url": "zh/api-post-nd-api-file-remove-from-trash.html", "source": "content/zh/api-post-nd-api-file-remove-from-trash.md", "summary": "删除文件（从回收站） 属性 值 HTTP 方法 POST 接口路径 /nd/api/file/remove from trash 所属分类 文件 API 接口说明 接口路径： /nd/api/file/remove from trash HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file ids[] 目标文件 id 数组（必填） string[] 返回信息如下 {\"code\":0,\"success\":true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。", "headings": [ { "level": 1, "title": "删除文件（从回收站）", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-4" } ], "images": [], "text": "删除文件（从回收站） 属性 值 HTTP 方法 POST 接口路径 /nd/api/file/remove from trash 所属分类 文件 API 接口说明 接口路径： /nd/api/file/remove from trash HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file ids[] 目标文件 id 数组（必填） string[] 返回信息如下 {\"code\":0,\"success\":true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。" }, { "lang": "zh", "slug": "api-post-nd-api-file-empty-trash", "title": "清空回收站", "description": "POST /nd/api/file/empty_trash：清空回收站 接口说明，包含路径、方法、参数和返回信息。", "category": "文件 API", "top_category": "API文档", "keywords": [ "API", "清空回收站", "/nd/api/file/empty_trash" ], "url": "zh/api-post-nd-api-file-empty-trash.html", "source": "content/zh/api-post-nd-api-file-empty-trash.md", "summary": "清空回收站 属性 值 HTTP 方法 POST 接口路径 /nd/api/file/empty trash 所属分类 文件 API 接口说明 接口路径： /nd/api/file/empty trash HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 说明 返回信息如下 {\"code\":0,\"success\":true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。", "headings": [ { "level": 1, "title": "清空回收站", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-4" } ], "images": [], "text": "清空回收站 属性 值 HTTP 方法 POST 接口路径 /nd/api/file/empty trash 所属分类 文件 API 接口说明 接口路径： /nd/api/file/empty trash HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 说明 返回信息如下 {\"code\":0,\"success\":true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。" }, { "lang": "zh", "slug": "api-post-nd-api-file-restore-file", "title": "恢复文件（从回收站）", "description": "POST /nd/api/file/restore_file：恢复文件（从回收站） 接口说明，包含路径、方法、参数和返回信息。", "category": "文件 API", "top_category": "API文档", "keywords": [ "API", "恢复文件（从回收站）", "/nd/api/file/restore_file" ], "url": "zh/api-post-nd-api-file-restore-file.html", "source": "content/zh/api-post-nd-api-file-restore-file.md", "summary": "恢复文件（从回收站） 属性 值 HTTP 方法 POST 接口路径 /nd/api/file/restore file 所属分类 文件 API 接口说明 接口路径： /nd/api/file/restore file HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file ids[] 目标文件 id 数组 string[] restoreAll 不填写 file ids, restoreAll 为 true，时恢复回收站中所有文件，boolean 返回信息如下 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。", "headings": [ { "level": 1, "title": "恢复文件（从回收站）", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-4" } ], "images": [], "text": "恢复文件（从回收站） 属性 值 HTTP 方法 POST 接口路径 /nd/api/file/restore file 所属分类 文件 API 接口说明 接口路径： /nd/api/file/restore file HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file ids[] 目标文件 id 数组 string[] restoreAll 不填写 file ids, restoreAll 为 true，时恢复回收站中所有文件，boolean 返回信息如下 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。" }, { "lang": "zh", "slug": "api-get-nd-api-file-versions", "title": "获取文件的所有版本信息", "description": "GET /nd/api/file/versions：获取文件的所有版本信息 接口说明，包含路径、方法、参数和返回信息。", "category": "文件 API", "top_category": "API文档", "keywords": [ "API", "获取文件的所有版本信息", "/nd/api/file/versions" ], "url": "zh/api-get-nd-api-file-versions.html", "source": "content/zh/api-get-nd-api-file-versions.md", "summary": "获取文件的所有版本信息 属性 值 HTTP 方法 GET 接口路径 /nd/api/file/versions 所属分类 文件 API 接口说明 接口路径： /nd/api/file/versions HTTP 方法： GET HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 目标文件 id（必填） string 返回信息如下 {\"code\":0,\"versions\":[],\"success\":true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。", "headings": [ { "level": 1, "title": "获取文件的所有版本信息", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-4" } ], "images": [], "text": "获取文件的所有版本信息 属性 值 HTTP 方法 GET 接口路径 /nd/api/file/versions 所属分类 文件 API 接口说明 接口路径： /nd/api/file/versions HTTP 方法： GET HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 目标文件 id（必填） string 返回信息如下 {\"code\":0,\"versions\":[],\"success\":true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。" }, { "lang": "zh", "slug": "api-post-nd-api-file-version", "title": "设置文件当前版本", "description": "POST /nd/api/file/version：设置文件当前版本 接口说明，包含路径、方法、参数和返回信息。", "category": "文件 API", "top_category": "API文档", "keywords": [ "API", "设置文件当前版本", "/nd/api/file/version" ], "url": "zh/api-post-nd-api-file-version.html", "source": "content/zh/api-post-nd-api-file-version.md", "summary": "设置文件当前版本 属性 值 HTTP 方法 POST 接口路径 /nd/api/file/version 所属分类 文件 API 接口说明 接口路径： /nd/api/file/version HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file id 目标文件 id （必填） string version 版本号（必填） number 返回信息如下 {\"code\":0,\"success\":true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。", "headings": [ { "level": 1, "title": "设置文件当前版本", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-4" } ], "images": [], "text": "设置文件当前版本 属性 值 HTTP 方法 POST 接口路径 /nd/api/file/version 所属分类 文件 API 接口说明 接口路径： /nd/api/file/version HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file id 目标文件 id （必填） string version 版本号（必填） number 返回信息如下 {\"code\":0,\"success\":true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。" }, { "lang": "zh", "slug": "api-post-nd-api-file-move", "title": "移动文件", "description": "POST /nd/api/file/move：移动文件 接口说明，包含路径、方法、参数和返回信息。", "category": "文件 API", "top_category": "API文档", "keywords": [ "API", "移动文件", "/nd/api/file/move" ], "url": "zh/api-post-nd-api-file-move.html", "source": "content/zh/api-post-nd-api-file-move.md", "summary": "移动文件 属性 值 HTTP 方法 POST 接口路径 /nd/api/file/move 所属分类 文件 API 接口说明 接口路径： /nd/api/file/move HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file ids 需要移动的目标文件 id 数组（必填） string target id 需要移动到的目标文件夹 id（必填） string 返回信息如下 {\"code\":0,\"success\":true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。", "headings": [ { "level": 1, "title": "移动文件", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-4" } ], "images": [], "text": "移动文件 属性 值 HTTP 方法 POST 接口路径 /nd/api/file/move 所属分类 文件 API 接口说明 接口路径： /nd/api/file/move HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file ids 需要移动的目标文件 id 数组（必填） string target id 需要移动到的目标文件夹 id（必填） string 返回信息如下 {\"code\":0,\"success\":true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。" }, { "lang": "zh", "slug": "api-post-nd-api-file-copy", "title": "拷贝文件", "description": "POST /nd/api/file/copy：拷贝文件 接口说明，包含路径、方法、参数和返回信息。", "category": "文件 API", "top_category": "API文档", "keywords": [ "API", "拷贝文件", "/nd/api/file/copy" ], "url": "zh/api-post-nd-api-file-copy.html", "source": "content/zh/api-post-nd-api-file-copy.md", "summary": "拷贝文件 属性 值 HTTP 方法 POST 接口路径 /nd/api/file/copy 所属分类 文件 API 接口说明 接口路径： /nd/api/file/copy HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。", "headings": [ { "level": 1, "title": "拷贝文件", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-3" } ], "images": [], "text": "拷贝文件 属性 值 HTTP 方法 POST 接口路径 /nd/api/file/copy 所属分类 文件 API 接口说明 接口路径： /nd/api/file/copy HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。" }, { "lang": "zh", "slug": "api-post-nd-api-file-copy-progress", "title": "拷贝文件进度", "description": "POST /nd/api/file/copy_progress：拷贝文件进度 接口说明，包含路径、方法、参数和返回信息。", "category": "文件 API", "top_category": "API文档", "keywords": [ "API", "拷贝文件进度", "/nd/api/file/copy_progress" ], "url": "zh/api-post-nd-api-file-copy-progress.html", "source": "content/zh/api-post-nd-api-file-copy-progress.md", "summary": "拷贝文件进度 属性 值 HTTP 方法 POST 接口路径 /nd/api/file/copy progress 所属分类 文件 API 接口说明 接口路径： /nd/api/file/copy progress HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) copyKey 查看拷贝进度 copyKey 由 copy 接口返回（必填） string 返回信息如下 { \"code\": 0, \"completed\": 10,\"total\": 10, \"result\": {}, \"success\": true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。", "headings": [ { "level": 1, "title": "拷贝文件进度", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-4" } ], "images": [], "text": "拷贝文件进度 属性 值 HTTP 方法 POST 接口路径 /nd/api/file/copy progress 所属分类 文件 API 接口说明 接口路径： /nd/api/file/copy progress HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) copyKey 查看拷贝进度 copyKey 由 copy 接口返回（必填） string 返回信息如下 { \"code\": 0, \"completed\": 10,\"total\": 10, \"result\": {}, \"success\": true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。" }, { "lang": "zh", "slug": "api-get-nd-api-file-file-logs", "title": "文件日志", "description": "GET /nd/api/file/file_logs：文件日志 接口说明，包含路径、方法、参数和返回信息。", "category": "文件 API", "top_category": "API文档", "keywords": [ "API", "文件日志", "/nd/api/file/file_logs" ], "url": "zh/api-get-nd-api-file-file-logs.html", "source": "content/zh/api-get-nd-api-file-file-logs.md", "summary": "文件日志 属性 值 HTTP 方法 GET 接口路径 /nd/api/file/file logs 所属分类 文件 API 接口说明 接口路径： /nd/api/file/file logs HTTP 方法： GET HTTP 方法： GET GET 请求体参数 参数名 Comment(说明) file id 目标文件 id 数组（必填） string startIndex 获取日志的起始顺序 第几条日志开始返回（选填） int 默认 0， pageSize 每页返回的个数（选填） int type 日志类型(选填) int 默认 0, 查看所有记录， 1 仅查看访问记录，2 仅查看上传下载，3 仅查看匿名用 户，4 仅查看分享及邀请，5 仅查看删除记录 userName 某个用户名 (选填) string, 返回某个用户的日志 lang 语言(选填) 默认 cn, string 返回日志的语言 cn(中文) en(英文) 返回信息如下 {\"code\":0,\"success\":true, \"logs\":[], \"total\":50} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。", "headings": [ { "level": 1, "title": "文件日志", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-4" } ], "images": [], "text": "文件日志 属性 值 HTTP 方法 GET 接口路径 /nd/api/file/file logs 所属分类 文件 API 接口说明 接口路径： /nd/api/file/file logs HTTP 方法： GET HTTP 方法： GET GET 请求体参数 参数名 Comment(说明) file id 目标文件 id 数组（必填） string startIndex 获取日志的起始顺序 第几条日志开始返回（选填） int 默认 0， pageSize 每页返回的个数（选填） int type 日志类型(选填) int 默认 0, 查看所有记录， 1 仅查看访问记录，2 仅查看上传下载，3 仅查看匿名用 户，4 仅查看分享及邀请，5 仅查看删除记录 userName 某个用户名 (选填) string, 返回某个用户的日志 lang 语言(选填) 默认 cn, string 返回日志的语言 cn(中文) en(英文) 返回信息如下 {\"code\":0,\"success\":true, \"logs\":[], \"total\":50} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。" }, { "lang": "zh", "slug": "api-post-nd-api-file-set-user-access-material-library", "title": "设置用户是否有权访问素材库", "description": "POST /nd/api/file/set_user_access_material_library：设置用户是否有权访问素材库 接口说明，包含路径、方法、参数和返回信息。", "category": "文件 API", "top_category": "API文档", "keywords": [ "API", "设置用户是否有权访问素材库", "/nd/api/file/set_user_access_material_library" ], "url": "zh/api-post-nd-api-file-set-user-access-material-library.html", "source": "content/zh/api-post-nd-api-file-set-user-access-material-library.md", "summary": "设置用户是否有权访问素材库 属性 值 HTTP 方法 POST 接口路径 /nd/api/file/set user access material library 所属分类 文件 API 接口说明 接口路径： /nd/api/file/set user access material library HTTP 方法： POST HTTP 方法： POST GET 请求体参数 参数名 Comment(说明) userId 用户的 id 数组数型 [usrId1, userId2]（必填） string can 是否可访问 数值类型 （必填） int 默认 0， 0： 不可访问， 1:可以访问 返回信息如下 {\"code\":0,\"success\":true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。", "headings": [ { "level": 1, "title": "设置用户是否有权访问素材库", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-4" } ], "images": [], "text": "设置用户是否有权访问素材库 属性 值 HTTP 方法 POST 接口路径 /nd/api/file/set user access material library 所属分类 文件 API 接口说明 接口路径： /nd/api/file/set user access material library HTTP 方法： POST HTTP 方法： POST GET 请求体参数 参数名 Comment(说明) userId 用户的 id 数组数型 [usrId1, userId2]（必填） string can 是否可访问 数值类型 （必填） int 默认 0， 0： 不可访问， 1:可以访问 返回信息如下 {\"code\":0,\"success\":true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。" }, { "lang": "zh", "slug": "api-post-nd-api-file-create-material-class", "title": "创建素材库分类", "description": "POST /nd/api/file/create_material_class：创建素材库分类 接口说明，包含路径、方法、参数和返回信息。", "category": "文件 API", "top_category": "API文档", "keywords": [ "API", "创建素材库分类", "/nd/api/file/create_material_class" ], "url": "zh/api-post-nd-api-file-create-material-class.html", "source": "content/zh/api-post-nd-api-file-create-material-class.md", "summary": "创建素材库分类 属性 值 HTTP 方法 POST 接口路径 /nd/api/file/create material class 所属分类 文件 API 接口说明 接口路径： /nd/api/file/create material class HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) destDirFileId 目标文件夹 的 fileId（必填） string name 创建分类库的名称（必填） string accessType 分类可见性 (选填) 默认为公开 0. 0: // 公开 1: // 需要申请 2: // 部门公开 3: // 部门申请 4: // 保密 managerIds 负责人的 id 数组类型 [usrId1,userId2] departmentIds 分类可见性 限定部门 的部门 id (选填) 数组类型 [departmentId1,departmentId2] 返回信息如下 {\"code\":0, \"success\":true, \"materialClass\": {}} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。", "headings": [ { "level": 1, "title": "创建素材库分类", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-4" } ], "images": [], "text": "创建素材库分类 属性 值 HTTP 方法 POST 接口路径 /nd/api/file/create material class 所属分类 文件 API 接口说明 接口路径： /nd/api/file/create material class HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) destDirFileId 目标文件夹 的 fileId（必填） string name 创建分类库的名称（必填） string accessType 分类可见性 (选填) 默认为公开 0. 0: // 公开 1: // 需要申请 2: // 部门公开 3: // 部门申请 4: // 保密 managerIds 负责人的 id 数组类型 [usrId1,userId2] departmentIds 分类可见性 限定部门 的部门 id (选填) 数组类型 [departmentId1,departmentId2] 返回信息如下 {\"code\":0, \"success\":true, \"materialClass\": {}} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。" }, { "lang": "zh", "slug": "api-post-nd-api-file-create-material-folder", "title": "创建子素材库", "description": "POST /nd/api/file/create_material_folder：创建子素材库 接口说明，包含路径、方法、参数和返回信息。", "category": "文件 API", "top_category": "API文档", "keywords": [ "API", "创建子素材库", "/nd/api/file/create_material_folder" ], "url": "zh/api-post-nd-api-file-create-material-folder.html", "source": "content/zh/api-post-nd-api-file-create-material-folder.md", "summary": "创建子素材库 属性 值 HTTP 方法 POST 接口路径 /nd/api/file/create material folder 所属分类 文件 API 接口说明 接口路径： /nd/api/file/create material folder HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) destDirFileId 目标文件夹 的 fileId（必填） string name 创建分类库的名称（必填） string accessType 分类可见性 (选填) 默认为公开 0. 0: // 公开 1: // 需要申请 2: // 部门公开 3: // 部门申请 4: // 保密 managerId 负责人的 id (选填) string departmentIds 分类可见性 限定部门 的部门 id (选填) 数组类型 [departmentId1,departmentId2] assistantIds 素材库助理人员的 id （选填） 数组类型 [usrId1,userId2] 返回信息如下 {\"code\":0, \"success\":true, \"materialFolder\": {}} 共享文件相关 API 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。", "headings": [ { "level": 1, "title": "创建子素材库", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "共享文件相关 API", "id": "api" }, { "level": 2, "title": "调用说明", "id": "section-4" } ], "images": [], "text": "创建子素材库 属性 值 HTTP 方法 POST 接口路径 /nd/api/file/create material folder 所属分类 文件 API 接口说明 接口路径： /nd/api/file/create material folder HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) destDirFileId 目标文件夹 的 fileId（必填） string name 创建分类库的名称（必填） string accessType 分类可见性 (选填) 默认为公开 0. 0: // 公开 1: // 需要申请 2: // 部门公开 3: // 部门申请 4: // 保密 managerId 负责人的 id (选填) string departmentIds 分类可见性 限定部门 的部门 id (选填) 数组类型 [departmentId1,departmentId2] assistantIds 素材库助理人员的 id （选填） 数组类型 [usrId1,userId2] 返回信息如下 {\"code\":0, \"success\":true, \"materialFolder\": {}} 共享文件相关 API 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：文件 API。" }, { "lang": "zh", "slug": "api-get-nd-api-share-shareurl", "title": "获取文件的分享 url", "description": "GET /nd/api/share/shareurl：获取文件的分享 url 接口说明，包含路径、方法、参数和返回信息。", "category": "分享 API", "top_category": "API文档", "keywords": [ "API", "获取文件的分享 url", "/nd/api/share/shareurl" ], "url": "zh/api-get-nd-api-share-shareurl.html", "source": "content/zh/api-get-nd-api-share-shareurl.md", "summary": "获取文件的分享 url 属性 值 HTTP 方法 GET 接口路径 /nd/api/share/shareurl 所属分类 分享 API 接口说明 接口路径： /nd/api/share/shareurl HTTP 方法： GET HTTP 方法： GET 获取文件的分享链接（先打开分享后，再获取该链接） URL 参数 参数名 Comment(说明) file id 文件 id string is https 返回的 share url 协议是否为 https 0 为 http, 1 为 https， 默认 0 number 返回字段说明 {\"code\":0,\"url\":\"https://private.babel.cc/share.do?s=http://private.babel.cc/share.do?s=MjY2OTYzNTk3OTU2NzEzOTtXZWQgSnVsIDAxIDIwMj AgMTg6MzM6NTAgR01UKzA4MDAgKEhvbmcgS29uZyBTdGFuZGFyZCBUaW1lKQ%3D%3D\",\"success\":true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：分享 API。", "headings": [ { "level": 1, "title": "获取文件的分享 url", "id": "url" }, { "level": 2, "title": "接口说明", "id": "section" }, { "level": 2, "title": "调用说明", "id": "section-3" } ], "images": [], "text": "获取文件的分享 url 属性 值 HTTP 方法 GET 接口路径 /nd/api/share/shareurl 所属分类 分享 API 接口说明 接口路径： /nd/api/share/shareurl HTTP 方法： GET HTTP 方法： GET 获取文件的分享链接（先打开分享后，再获取该链接） URL 参数 参数名 Comment(说明) file id 文件 id string is https 返回的 share url 协议是否为 https 0 为 http, 1 为 https， 默认 0 number 返回字段说明 {\"code\":0,\"url\":\"https://private.babel.cc/share.do?s=http://private.babel.cc/share.do?s=MjY2OTYzNTk3OTU2NzEzOTtXZWQgSnVsIDAxIDIwMj AgMTg6MzM6NTAgR01UKzA4MDAgKEhvbmcgS29uZyBTdGFuZGFyZCBUaW1lKQ%3D%3D\",\"success\":true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：分享 API。" }, { "lang": "zh", "slug": "api-get-nd-api-share-share-roles", "title": "获取分享的权限列表", "description": "GET /nd/api/share/share_roles：获取分享的权限列表 接口说明，包含路径、方法、参数和返回信息。", "category": "分享 API", "top_category": "API文档", "keywords": [ "API", "获取分享的权限列表", "/nd/api/share/share_roles" ], "url": "zh/api-get-nd-api-share-share-roles.html", "source": "content/zh/api-get-nd-api-share-share-roles.md", "summary": "获取分享的权限列表 属性 值 HTTP 方法 GET 接口路径 /nd/api/share/share roles 所属分类 分享 API 接口说明 接口路径： /nd/api/share/share roles HTTP 方法： GET HTTP 方法： GET URL 参数 参数名 Comment(说明) 返回字段说明 {\"code\":0,\"roles\":[],\"success\":true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：分享 API。", "headings": [ { "level": 1, "title": "获取分享的权限列表", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-4" } ], "images": [], "text": "获取分享的权限列表 属性 值 HTTP 方法 GET 接口路径 /nd/api/share/share roles 所属分类 分享 API 接口说明 接口路径： /nd/api/share/share roles HTTP 方法： GET HTTP 方法： GET URL 参数 参数名 Comment(说明) 返回字段说明 {\"code\":0,\"roles\":[],\"success\":true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：分享 API。" }, { "lang": "zh", "slug": "api-get-nd-api-share-share-role-forfile", "title": "获取用户对于单个文件有权设置的分享角色", "description": "GET /nd/api/share/share_role_forfile：获取用户对于单个文件有权设置的分享角色 接口说明，包含路径、方法、参数和返回信息。", "category": "分享 API", "top_category": "API文档", "keywords": [ "API", "获取用户对于单个文件有权设置的分享角色", "/nd/api/share/share_role_forfile" ], "url": "zh/api-get-nd-api-share-share-role-forfile.html", "source": "content/zh/api-get-nd-api-share-share-role-forfile.md", "summary": "获取用户对于单个文件有权设置的分享角色 属性 值 HTTP 方法 GET 接口路径 /nd/api/share/share role forfile 所属分类 分享 API 接口说明 接口路径： /nd/api/share/share role forfile HTTP 方法： GET HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 文件 id string 返回字段说明 {\"code\":0,\"roles\":[],\"success\":true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：分享 API。", "headings": [ { "level": 1, "title": "获取用户对于单个文件有权设置的分享角色", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-4" } ], "images": [], "text": "获取用户对于单个文件有权设置的分享角色 属性 值 HTTP 方法 GET 接口路径 /nd/api/share/share role forfile 所属分类 分享 API 接口说明 接口路径： /nd/api/share/share role forfile HTTP 方法： GET HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 文件 id string 返回字段说明 {\"code\":0,\"roles\":[],\"success\":true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：分享 API。" }, { "lang": "zh", "slug": "api-post-nd-api-share-open-link-share", "title": "创建链接分享", "description": "POST /nd/api/share/open_link_share：创建链接分享 接口说明，包含路径、方法、参数和返回信息。", "category": "分享 API", "top_category": "API文档", "keywords": [ "API", "创建链接分享", "/nd/api/share/open_link_share" ], "url": "zh/api-post-nd-api-share-open-link-share.html", "source": "content/zh/api-post-nd-api-share-open-link-share.md", "summary": "创建链接分享 属性 值 HTTP 方法 POST 接口路径 /nd/api/share/open link share 所属分类 分享 API 接口说明 接口路径： /nd/api/share/open link share HTTP 方法： POST HTTP 方法： POST 打开分享，获取新的分享链接，之前的链接失效。 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：分享 API。", "headings": [ { "level": 1, "title": "创建链接分享", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-3" } ], "images": [], "text": "创建链接分享 属性 值 HTTP 方法 POST 接口路径 /nd/api/share/open link share 所属分类 分享 API 接口说明 接口路径： /nd/api/share/open link share HTTP 方法： POST HTTP 方法： POST 打开分享，获取新的分享链接，之前的链接失效。 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：分享 API。" }, { "lang": "zh", "slug": "api-post-nd-api-share-close-link-share", "title": "关闭链接分享", "description": "POST /nd/api/share/close_link_share：关闭链接分享 接口说明，包含路径、方法、参数和返回信息。", "category": "分享 API", "top_category": "API文档", "keywords": [ "API", "关闭链接分享", "/nd/api/share/close_link_share" ], "url": "zh/api-post-nd-api-share-close-link-share.html", "source": "content/zh/api-post-nd-api-share-close-link-share.md", "summary": "关闭链接分享 属性 值 HTTP 方法 POST 接口路径 /nd/api/share/close link share 所属分类 分享 API 接口说明 接口路径： /nd/api/share/close link share HTTP 方法： POST HTTP 方法： POST 关闭我打开的分享链接 POST 请求体参数 参数名 Comment(说明) file id 分享的文件 id（必填） string 返回字段说明 {\"code\":0,\"success\":true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：分享 API。", "headings": [ { "level": 1, "title": "关闭链接分享", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-4" } ], "images": [], "text": "关闭链接分享 属性 值 HTTP 方法 POST 接口路径 /nd/api/share/close link share 所属分类 分享 API 接口说明 接口路径： /nd/api/share/close link share HTTP 方法： POST HTTP 方法： POST 关闭我打开的分享链接 POST 请求体参数 参数名 Comment(说明) file id 分享的文件 id（必填） string 返回字段说明 {\"code\":0,\"success\":true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：分享 API。" }, { "lang": "zh", "slug": "api-post-nd-api-share-set-share-password", "title": "设置链接分享密码", "description": "POST /nd/api/share/set_share_password：设置链接分享密码 接口说明，包含路径、方法、参数和返回信息。", "category": "分享 API", "top_category": "API文档", "keywords": [ "API", "设置链接分享密码", "/nd/api/share/set_share_password" ], "url": "zh/api-post-nd-api-share-set-share-password.html", "source": "content/zh/api-post-nd-api-share-set-share-password.md", "summary": "设置链接分享密码 属性 值 HTTP 方法 POST 接口路径 /nd/api/share/set share password 所属分类 分享 API 接口说明 接口路径： /nd/api/share/set share password HTTP 方法： POST HTTP 方法： POST 文件链接分享已打开，设置链接分享的密码。 POST 请求体参数 参数名 Comment(说明) file id 预分享的文件 id（必填） string password 链接分享的密码 string is https 返回的 share url 协议是否为 https number 返回字段说明 {\"code\":0,\"success\":true, \"share url\": \"http://private.babel.cc/share.do?s=xxxxxxxxxxx\"} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：分享 API。", "headings": [ { "level": 1, "title": "设置链接分享密码", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-4" } ], "images": [], "text": "设置链接分享密码 属性 值 HTTP 方法 POST 接口路径 /nd/api/share/set share password 所属分类 分享 API 接口说明 接口路径： /nd/api/share/set share password HTTP 方法： POST HTTP 方法： POST 文件链接分享已打开，设置链接分享的密码。 POST 请求体参数 参数名 Comment(说明) file id 预分享的文件 id（必填） string password 链接分享的密码 string is https 返回的 share url 协议是否为 https number 返回字段说明 {\"code\":0,\"success\":true, \"share url\": \"http://private.babel.cc/share.do?s=xxxxxxxxxxx\"} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：分享 API。" }, { "lang": "zh", "slug": "api-post-nd-api-share-invite-share", "title": "邀请人员参与分享", "description": "POST /nd/api/share/invite_share：邀请人员参与分享 接口说明，包含路径、方法、参数和返回信息。", "category": "分享 API", "top_category": "API文档", "keywords": [ "API", "邀请人员参与分享", "/nd/api/share/invite_share" ], "url": "zh/api-post-nd-api-share-invite-share.html", "source": "content/zh/api-post-nd-api-share-invite-share.md", "summary": "邀请人员参与分享 属性 值 HTTP 方法 POST 接口路径 /nd/api/share/invite share 所属分类 分享 API 接口说明 接口路径： /nd/api/share/invite share HTTP 方法： POST HTTP 方法： POST 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：分享 API。", "headings": [ { "level": 1, "title": "邀请人员参与分享", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-3" } ], "images": [], "text": "邀请人员参与分享 属性 值 HTTP 方法 POST 接口路径 /nd/api/share/invite share 所属分类 分享 API 接口说明 接口路径： /nd/api/share/invite share HTTP 方法： POST HTTP 方法： POST 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：分享 API。" }, { "lang": "zh", "slug": "api-get-nd-api-share-share-participants", "title": "获取所有分享参与人", "description": "GET /nd/api/share/share_participants：获取所有分享参与人 接口说明，包含路径、方法、参数和返回信息。", "category": "分享 API", "top_category": "API文档", "keywords": [ "API", "获取所有分享参与人", "/nd/api/share/share_participants" ], "url": "zh/api-get-nd-api-share-share-participants.html", "source": "content/zh/api-get-nd-api-share-share-participants.md", "summary": "获取所有分享参与人 属性 值 HTTP 方法 GET 接口路径 /nd/api/share/share participants 所属分类 分享 API 接口说明 接口路径： /nd/api/share/share participants HTTP 方法： GET HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 文件 id（必填） string 返回字段说明 {\"code\":0,\"users\":[],\"success\":true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：分享 API。", "headings": [ { "level": 1, "title": "获取所有分享参与人", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-4" } ], "images": [], "text": "获取所有分享参与人 属性 值 HTTP 方法 GET 接口路径 /nd/api/share/share participants 所属分类 分享 API 接口说明 接口路径： /nd/api/share/share participants HTTP 方法： GET HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 文件 id（必填） string 返回字段说明 {\"code\":0,\"users\":[],\"success\":true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：分享 API。" }, { "lang": "zh", "slug": "api-post-nd-api-share-set-participant-role", "title": "设置分享参与人的权限角色", "description": "POST /nd/api/share/set_participant_role：设置分享参与人的权限角色 接口说明，包含路径、方法、参数和返回信息。", "category": "分享 API", "top_category": "API文档", "keywords": [ "API", "设置分享参与人的权限角色", "/nd/api/share/set_participant_role" ], "url": "zh/api-post-nd-api-share-set-participant-role.html", "source": "content/zh/api-post-nd-api-share-set-participant-role.md", "summary": "设置分享参与人的权限角色 属性 值 HTTP 方法 POST 接口路径 /nd/api/share/set participant role 所属分类 分享 API 接口说明 接口路径： /nd/api/share/set participant role HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填） string babelshare id int（必填） 用户 id string role id int（必填） 角色 id string 返回字段说明 {\"code\":0,\"success\":true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：分享 API。", "headings": [ { "level": 1, "title": "设置分享参与人的权限角色", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-4" } ], "images": [], "text": "设置分享参与人的权限角色 属性 值 HTTP 方法 POST 接口路径 /nd/api/share/set participant role 所属分类 分享 API 接口说明 接口路径： /nd/api/share/set participant role HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填） string babelshare id int（必填） 用户 id string role id int（必填） 角色 id string 返回字段说明 {\"code\":0,\"success\":true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：分享 API。" }, { "lang": "zh", "slug": "api-post-nd-api-file-remove-share-participant", "title": "删除分享参与人", "description": "POST /nd/api/file/remove_share_participant：删除分享参与人 接口说明，包含路径、方法、参数和返回信息。", "category": "分享 API", "top_category": "API文档", "keywords": [ "API", "删除分享参与人", "/nd/api/file/remove_share_participant" ], "url": "zh/api-post-nd-api-file-remove-share-participant.html", "source": "content/zh/api-post-nd-api-file-remove-share-participant.md", "summary": "删除分享参与人 属性 值 HTTP 方法 POST 接口路径 /nd/api/file/remove share participant 所属分类 分享 API 接口说明 接口路径： /nd/api/file/remove share participant HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：分享 API。", "headings": [ { "level": 1, "title": "删除分享参与人", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-3" } ], "images": [], "text": "删除分享参与人 属性 值 HTTP 方法 POST 接口路径 /nd/api/file/remove share participant 所属分类 分享 API 接口说明 接口路径： /nd/api/file/remove share participant HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：分享 API。" }, { "lang": "zh", "slug": "api-post-nd-api-file-focus-file", "title": "提醒关注", "description": "POST /nd/api/file/focus_file：提醒关注 接口说明，包含路径、方法、参数和返回信息。", "category": "分享 API", "top_category": "API文档", "keywords": [ "API", "提醒关注", "/nd/api/file/focus_file" ], "url": "zh/api-post-nd-api-file-focus-file.html", "source": "content/zh/api-post-nd-api-file-focus-file.md", "summary": "提醒关注 属性 值 HTTP 方法 POST 接口路径 /nd/api/file/focus file 所属分类 分享 API 接口说明 接口路径： /nd/api/file/focus file HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填） string user ids[] 提醒的用户的 id，此 id 应该在文件参与人中选取，否则提醒不会起作用（必填）string[] 返回字段说明 {\"code\":0,\"success\":true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：分享 API。", "headings": [ { "level": 1, "title": "提醒关注", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-4" } ], "images": [], "text": "提醒关注 属性 值 HTTP 方法 POST 接口路径 /nd/api/file/focus file 所属分类 分享 API 接口说明 接口路径： /nd/api/file/focus file HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填） string user ids[] 提醒的用户的 id，此 id 应该在文件参与人中选取，否则提醒不会起作用（必填）string[] 返回字段说明 {\"code\":0,\"success\":true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：分享 API。" }, { "lang": "zh", "slug": "api-post-nd-api-file-unfocus-file", "title": "移除某人的关注", "description": "POST /nd/api/file/unfocus_file：移除某人的关注 接口说明，包含路径、方法、参数和返回信息。", "category": "分享 API", "top_category": "API文档", "keywords": [ "API", "移除某人的关注", "/nd/api/file/unfocus_file" ], "url": "zh/api-post-nd-api-file-unfocus-file.html", "source": "content/zh/api-post-nd-api-file-unfocus-file.md", "summary": "移除某人的关注 属性 值 HTTP 方法 POST 接口路径 /nd/api/file/unfocus file 所属分类 分享 API 接口说明 接口路径： /nd/api/file/unfocus file HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填）string user ids[] 提醒的用户的 id，此 id 应该在文件参与人中选取，否则提醒不会起作用（必填） string[] 返回字段说明 {\"code\":0,\"success\":true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：分享 API。", "headings": [ { "level": 1, "title": "移除某人的关注", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-4" } ], "images": [], "text": "移除某人的关注 属性 值 HTTP 方法 POST 接口路径 /nd/api/file/unfocus file 所属分类 分享 API 接口说明 接口路径： /nd/api/file/unfocus file HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填）string user ids[] 提醒的用户的 id，此 id 应该在文件参与人中选取，否则提醒不会起作用（必填） string[] 返回字段说明 {\"code\":0,\"success\":true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：分享 API。" }, { "lang": "zh", "slug": "api-get-nd-api-file-user-focusfile", "title": "获取关注文件的用户列表", "description": "GET /nd/api/file/user_focusfile：获取关注文件的用户列表 接口说明，包含路径、方法、参数和返回信息。", "category": "分享 API", "top_category": "API文档", "keywords": [ "API", "获取关注文件的用户列表", "/nd/api/file/user_focusfile" ], "url": "zh/api-get-nd-api-file-user-focusfile.html", "source": "content/zh/api-get-nd-api-file-user-focusfile.md", "summary": "获取关注文件的用户列表 属性 值 HTTP 方法 GET 接口路径 /nd/api/file/user focusfile 所属分类 分享 API 接口说明 接口路径： /nd/api/file/user focusfile HTTP 方法： GET HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 文件 id（必填） string 返回字段说明 {\"code\":0,\"users\":[],\"success\":true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：分享 API。", "headings": [ { "level": 1, "title": "获取关注文件的用户列表", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-4" } ], "images": [], "text": "获取关注文件的用户列表 属性 值 HTTP 方法 GET 接口路径 /nd/api/file/user focusfile 所属分类 分享 API 接口说明 接口路径： /nd/api/file/user focusfile HTTP 方法： GET HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 文件 id（必填） string 返回字段说明 {\"code\":0,\"users\":[],\"success\":true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：分享 API。" }, { "lang": "zh", "slug": "api-get-nd-api-file-user-can-focusfile", "title": "获取可以关注文件的用户列表，并且标记已关注文件的用户", "description": "GET /nd/api/file/user_can_focusfile：获取可以关注文件的用户列表，并且标记已关注文件的用户 接口说明，包含路径、方法、参数和返回信息。", "category": "分享 API", "top_category": "API文档", "keywords": [ "API", "获取可以关注文件的用户列表，并且标记已关注文件的用户", "/nd/api/file/user_can_focusfile" ], "url": "zh/api-get-nd-api-file-user-can-focusfile.html", "source": "content/zh/api-get-nd-api-file-user-can-focusfile.md", "summary": "获取可以关注文件的用户列表，并且标记已关注文件的用户 属性 值 HTTP 方法 GET 接口路径 /nd/api/file/user can focusfile 所属分类 分享 API 接口说明 接口路径： /nd/api/file/user can focusfile HTTP 方法： GET 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：分享 API。", "headings": [ { "level": 1, "title": "获取可以关注文件的用户列表，并且标记已关注文件的用户", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-3" } ], "images": [], "text": "获取可以关注文件的用户列表，并且标记已关注文件的用户 属性 值 HTTP 方法 GET 接口路径 /nd/api/file/user can focusfile 所属分类 分享 API 接口说明 接口路径： /nd/api/file/user can focusfile HTTP 方法： GET 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：分享 API。" }, { "lang": "zh", "slug": "api-get-nd-api-enterprise-current", "title": "获取当前企业信息", "description": "GET /nd/api/enterprise/current：获取当前企业信息 接口说明，包含路径、方法、参数和返回信息。", "category": "企业 API", "top_category": "API文档", "keywords": [ "API", "获取当前企业信息", "/nd/api/enterprise/current" ], "url": "zh/api-get-nd-api-enterprise-current.html", "source": "content/zh/api-get-nd-api-enterprise-current.md", "summary": "获取当前企业信息 属性 值 HTTP 方法 GET 接口路径 /nd/api/enterprise/current 所属分类 企业 API 接口说明 接口路径： /nd/api/enterprise/current HTTP 方法： GET HTTP 方法： GET URL 参数 参数名 Comment(说明) 无 返回字段说明 {\"code\":0,\"enterprise\":{},\"success\":true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：企业 API。", "headings": [ { "level": 1, "title": "获取当前企业信息", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-4" } ], "images": [], "text": "获取当前企业信息 属性 值 HTTP 方法 GET 接口路径 /nd/api/enterprise/current 所属分类 企业 API 接口说明 接口路径： /nd/api/enterprise/current HTTP 方法： GET HTTP 方法： GET URL 参数 参数名 Comment(说明) 无 返回字段说明 {\"code\":0,\"enterprise\":{},\"success\":true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：企业 API。" }, { "lang": "zh", "slug": "api-get-nd-api-enterprise-departments", "title": "获取企业所有部门信息", "description": "GET /nd/api/enterprise/departments：获取企业所有部门信息 接口说明，包含路径、方法、参数和返回信息。", "category": "企业 API", "top_category": "API文档", "keywords": [ "API", "获取企业所有部门信息", "/nd/api/enterprise/departments" ], "url": "zh/api-get-nd-api-enterprise-departments.html", "source": "content/zh/api-get-nd-api-enterprise-departments.md", "summary": "获取企业所有部门信息 属性 值 HTTP 方法 GET 接口路径 /nd/api/enterprise/departments 所属分类 企业 API 接口说明 接口路径： /nd/api/enterprise/departments HTTP 方法： GET HTTP 方法： GET URL 参数 参数名 Comment(说明) 无 返回字段说明 属性名 类型 说明 departments []数组 返回所有的部门信息 tree {}json 数据 返回部门的父子结构信息 code int sucess boolean 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：企业 API。", "headings": [ { "level": 1, "title": "获取企业所有部门信息", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-4" } ], "images": [], "text": "获取企业所有部门信息 属性 值 HTTP 方法 GET 接口路径 /nd/api/enterprise/departments 所属分类 企业 API 接口说明 接口路径： /nd/api/enterprise/departments HTTP 方法： GET HTTP 方法： GET URL 参数 参数名 Comment(说明) 无 返回字段说明 属性名 类型 说明 departments []数组 返回所有的部门信息 tree {}json 数据 返回部门的父子结构信息 code int sucess boolean 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：企业 API。" }, { "lang": "zh", "slug": "api-post-nd-api-enterprise-create-department", "title": "创建企业部门", "description": "POST /nd/api/enterprise/create_department：创建企业部门 接口说明，包含路径、方法、参数和返回信息。", "category": "企业 API", "top_category": "API文档", "keywords": [ "API", "创建企业部门", "/nd/api/enterprise/create_department" ], "url": "zh/api-post-nd-api-enterprise-create-department.html", "source": "content/zh/api-post-nd-api-enterprise-create-department.md", "summary": "创建企业部门 属性 值 HTTP 方法 POST 接口路径 /nd/api/enterprise/create department 所属分类 企业 API 接口说明 接口路径： /nd/api/enterprise/create department HTTP 方法： POST HTTP 方法： POST 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：企业 API。", "headings": [ { "level": 1, "title": "创建企业部门", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-3" } ], "images": [], "text": "创建企业部门 属性 值 HTTP 方法 POST 接口路径 /nd/api/enterprise/create department 所属分类 企业 API 接口说明 接口路径： /nd/api/enterprise/create department HTTP 方法： POST HTTP 方法： POST 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：企业 API。" }, { "lang": "zh", "slug": "api-get-nd-api-enterprise-dep-role", "title": "获取部门角色列表", "description": "GET /nd/api/enterprise/dep_role：获取部门角色列表 接口说明，包含路径、方法、参数和返回信息。", "category": "企业 API", "top_category": "API文档", "keywords": [ "API", "获取部门角色列表", "/nd/api/enterprise/dep_role" ], "url": "zh/api-get-nd-api-enterprise-dep-role.html", "source": "content/zh/api-get-nd-api-enterprise-dep-role.md", "summary": "获取部门角色列表 属性 值 HTTP 方法 GET 接口路径 /nd/api/enterprise/dep role 所属分类 企业 API 接口说明 接口路径： /nd/api/enterprise/dep role HTTP 方法： GET HTTP 方法： GET URL 参数 参数名 Comment(说明) 返回字段说明 属性名 类型 说明 roles []数组 { id, filePermission,enterpriseId,filePermission,managerPermission, default,nameEn,name} code int sucess boolean 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：企业 API。", "headings": [ { "level": 1, "title": "获取部门角色列表", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-4" } ], "images": [], "text": "获取部门角色列表 属性 值 HTTP 方法 GET 接口路径 /nd/api/enterprise/dep role 所属分类 企业 API 接口说明 接口路径： /nd/api/enterprise/dep role HTTP 方法： GET HTTP 方法： GET URL 参数 参数名 Comment(说明) 返回字段说明 属性名 类型 说明 roles []数组 { id, filePermission,enterpriseId,filePermission,managerPermission, default,nameEn,name} code int sucess boolean 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：企业 API。" }, { "lang": "zh", "slug": "api-post-nd-api-enterprise-add-dep-mem", "title": "添加部门人员", "description": "POST /nd/api/enterprise/add_dep_mem：添加部门人员 接口说明，包含路径、方法、参数和返回信息。", "category": "企业 API", "top_category": "API文档", "keywords": [ "API", "添加部门人员", "/nd/api/enterprise/add_dep_mem" ], "url": "zh/api-post-nd-api-enterprise-add-dep-mem.html", "source": "content/zh/api-post-nd-api-enterprise-add-dep-mem.md", "summary": "添加部门人员 属性 值 HTTP 方法 POST 接口路径 /nd/api/enterprise/add dep mem 所属分类 企业 API 接口说明 接口路径： /nd/api/enterprise/add dep mem HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) department id 部门 id（必填）string user ids[] 用户列表 string[] role id 用户在部门中的角色 string 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：企业 API。", "headings": [ { "level": 1, "title": "添加部门人员", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-3" } ], "images": [], "text": "添加部门人员 属性 值 HTTP 方法 POST 接口路径 /nd/api/enterprise/add dep mem 所属分类 企业 API 接口说明 接口路径： /nd/api/enterprise/add dep mem HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) department id 部门 id（必填）string user ids[] 用户列表 string[] role id 用户在部门中的角色 string 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：企业 API。" }, { "lang": "zh", "slug": "api-post-nd-api-enterprise-remove-dep-mem", "title": "删除部门人员", "description": "POST /nd/api/enterprise/remove_dep_mem：删除部门人员 接口说明，包含路径、方法、参数和返回信息。", "category": "企业 API", "top_category": "API文档", "keywords": [ "API", "删除部门人员", "/nd/api/enterprise/remove_dep_mem" ], "url": "zh/api-post-nd-api-enterprise-remove-dep-mem.html", "source": "content/zh/api-post-nd-api-enterprise-remove-dep-mem.md", "summary": "删除部门人员 属性 值 HTTP 方法 POST 接口路径 /nd/api/enterprise/remove dep mem 所属分类 企业 API 接口说明 接口路径： /nd/api/enterprise/remove dep mem HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) department id 部门 id（必填）string user ids[] 人员的 id（必填）string[] 返回字段说明 属性名 类型 说明 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：企业 API。", "headings": [ { "level": 1, "title": "删除部门人员", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-4" } ], "images": [], "text": "删除部门人员 属性 值 HTTP 方法 POST 接口路径 /nd/api/enterprise/remove dep mem 所属分类 企业 API 接口说明 接口路径： /nd/api/enterprise/remove dep mem HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) department id 部门 id（必填）string user ids[] 人员的 id（必填）string[] 返回字段说明 属性名 类型 说明 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：企业 API。" }, { "lang": "zh", "slug": "api-get-nd-api-enterprise-mydeparments", "title": "获取自己所在部门信息", "description": "GET /nd/api/enterprise/mydeparments：获取自己所在部门信息 接口说明，包含路径、方法、参数和返回信息。", "category": "企业 API", "top_category": "API文档", "keywords": [ "API", "获取自己所在部门信息", "/nd/api/enterprise/mydeparments" ], "url": "zh/api-get-nd-api-enterprise-mydeparments.html", "source": "content/zh/api-get-nd-api-enterprise-mydeparments.md", "summary": "获取自己所在部门信息 属性 值 HTTP 方法 GET 接口路径 /nd/api/enterprise/mydeparments 所属分类 企业 API 接口说明 接口路径： /nd/api/enterprise/mydeparments HTTP 方法： GET HTTP 方法： GET URL 参数 参数名 Comment(说明) 无 返回字段说明 属性名 类型 说明 departments []数组 返回我所在的部门信息 code int sucess boolean 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：企业 API。", "headings": [ { "level": 1, "title": "获取自己所在部门信息", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-4" } ], "images": [], "text": "获取自己所在部门信息 属性 值 HTTP 方法 GET 接口路径 /nd/api/enterprise/mydeparments 所属分类 企业 API 接口说明 接口路径： /nd/api/enterprise/mydeparments HTTP 方法： GET HTTP 方法： GET URL 参数 参数名 Comment(说明) 无 返回字段说明 属性名 类型 说明 departments []数组 返回我所在的部门信息 code int sucess boolean 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：企业 API。" }, { "lang": "zh", "slug": "api-get-nd-api-enterprise-departmentmembers", "title": "获取部门人员", "description": "GET /nd/api/enterprise/departmentmembers：获取部门人员 接口说明，包含路径、方法、参数和返回信息。", "category": "企业 API", "top_category": "API文档", "keywords": [ "API", "获取部门人员", "/nd/api/enterprise/departmentmembers" ], "url": "zh/api-get-nd-api-enterprise-departmentmembers.html", "source": "content/zh/api-get-nd-api-enterprise-departmentmembers.md", "summary": "获取部门人员 属性 值 HTTP 方法 GET 接口路径 /nd/api/enterprise/departmentmembers 所属分类 企业 API 接口说明 接口路径： /nd/api/enterprise/departmentmembers HTTP 方法： GET 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：企业 API。", "headings": [ { "level": 1, "title": "获取部门人员", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-3" } ], "images": [], "text": "获取部门人员 属性 值 HTTP 方法 GET 接口路径 /nd/api/enterprise/departmentmembers 所属分类 企业 API 接口说明 接口路径： /nd/api/enterprise/departmentmembers HTTP 方法： GET 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：企业 API。" }, { "lang": "zh", "slug": "api-post-nd-api-enterprise-add-ent-mem", "title": "添加企业成员", "description": "POST /nd/api/enterprise/add_ent_mem：添加企业成员 接口说明，包含路径、方法、参数和返回信息。", "category": "企业 API", "top_category": "API文档", "keywords": [ "API", "添加企业成员", "/nd/api/enterprise/add_ent_mem" ], "url": "zh/api-post-nd-api-enterprise-add-ent-mem.html", "source": "content/zh/api-post-nd-api-enterprise-add-ent-mem.md", "summary": "添加企业成员 属性 值 HTTP 方法 POST 接口路径 /nd/api/enterprise/add ent mem 所属分类 企业 API 接口说明 接口路径： /nd/api/enterprise/add ent mem HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) email Email 邮箱 string password 密码 string enterprise role 企业成员角色, 可选 number department ids[] 该用户的部门， 可选 string[] department roles[] 在部门中的角色， 可选 string[] sex 性别 0 未设置 1 男 2 女 number name 用户名 string phone 手机号， 可选 string babelId 工号，可选 string spacelimit 个人空间限制，单位 GB, 0 表示不限制 number can ownfile 用户能否拥有个人文件， 1 使用企业总体设置, 0 没有个人文件, 1 有个人文件 number remarks 用户描述， 可选 string join time 用户加入企业时间，Unix time, 单位秒 number password is md5 传入密码是否需要 md5 加密, 0 非 md5 密码， 1 md5 加密过的密码 number 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: ", "headings": [ { "level": 1, "title": "添加企业成员", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-3" } ], "images": [], "text": "添加企业成员 属性 值 HTTP 方法 POST 接口路径 /nd/api/enterprise/add ent mem 所属分类 企业 API 接口说明 接口路径： /nd/api/enterprise/add ent mem HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) email Email 邮箱 string password 密码 string enterprise role 企业成员角色, 可选 number department ids[] 该用户的部门， 可选 string[] department roles[] 在部门中的角色， 可选 string[] sex 性别 0 未设置 1 男 2 女 number name 用户名 string phone 手机号， 可选 string babelId 工号，可选 string spacelimit 个人空间限制，单位 GB, 0 表示不限制 number can ownfile 用户能否拥有个人文件， 1 使用企业总体设置, 0 没有个人文件, 1 有个人文件 number remarks 用户描述， 可选 string join time 用户加入企业时间，Unix time, 单位秒 number password is md5 传入密码是否需要 md5 加密, 0 非 md5 密码， 1 md5 加密过的密码 number 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：企业 API。" }, { "lang": "zh", "slug": "api-post-api-updateuserinfo-do", "title": "更新成员信息", "description": "POST /api/updateUserInfo.do：更新成员信息 接口说明，包含路径、方法、参数和返回信息。", "category": "企业 API", "top_category": "API文档", "keywords": [ "API", "更新成员信息", "/api/updateUserInfo.do" ], "url": "zh/api-post-api-updateuserinfo-do.html", "source": "content/zh/api-post-api-updateuserinfo-do.md", "summary": "更新成员信息 属性 值 HTTP 方法 POST 接口路径 /api/updateUserInfo.do 所属分类 企业 API 接口说明 接口路径： /api/updateUserInfo.do HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) email 邮箱地址（搜索关键字，必须）string password 密码（修改密码，可选）string frozen 1 – 表示冻结， 0 – 表示解冻 （冻结该账号，可选）number password is md5 传入密码是否需要 md5 加密, 0 非 md5 密码， 1 md5 加密过的密码 number phone 手机号 (可选) string 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：企业 API。", "headings": [ { "level": 1, "title": "更新成员信息", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-3" } ], "images": [], "text": "更新成员信息 属性 值 HTTP 方法 POST 接口路径 /api/updateUserInfo.do 所属分类 企业 API 接口说明 接口路径： /api/updateUserInfo.do HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) email 邮箱地址（搜索关键字，必须）string password 密码（修改密码，可选）string frozen 1 – 表示冻结， 0 – 表示解冻 （冻结该账号，可选）number password is md5 传入密码是否需要 md5 加密, 0 非 md5 密码， 1 md5 加密过的密码 number phone 手机号 (可选) string 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：企业 API。" }, { "lang": "zh", "slug": "api-get-api-getenterprisemember-do", "title": "获取企业成员信息", "description": "GET /api/getEnterpriseMember.do：获取企业成员信息 接口说明，包含路径、方法、参数和返回信息。", "category": "企业 API", "top_category": "API文档", "keywords": [ "API", "获取企业成员信息", "/api/getEnterpriseMember.do" ], "url": "zh/api-get-api-getenterprisemember-do.html", "source": "content/zh/api-get-api-getenterprisemember-do.md", "summary": "获取企业成员信息 属性 值 HTTP 方法 GET 接口路径 /api/getEnterpriseMember.do 所属分类 企业 API 接口说明 接口路径： /api/getEnterpriseMember.do HTTP 方法： GET HTTP 方法： GET URL 参数 参数名 Comment(说明) email 邮箱地址（搜索关键字）string phone 手机号（搜索关键字）string babelId 工号（搜索关键字）string email/phone/babelId 可选择其一 返回字段说明 {\"code\":0,\"success\":true,\"user\":{}} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：企业 API。", "headings": [ { "level": 1, "title": "获取企业成员信息", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-4" } ], "images": [], "text": "获取企业成员信息 属性 值 HTTP 方法 GET 接口路径 /api/getEnterpriseMember.do 所属分类 企业 API 接口说明 接口路径： /api/getEnterpriseMember.do HTTP 方法： GET HTTP 方法： GET URL 参数 参数名 Comment(说明) email 邮箱地址（搜索关键字）string phone 手机号（搜索关键字）string babelId 工号（搜索关键字）string email/phone/babelId 可选择其一 返回字段说明 {\"code\":0,\"success\":true,\"user\":{}} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：企业 API。" }, { "lang": "zh", "slug": "api-post-nd-api-enterprise-enterprise-members", "title": "获取企业所有成员", "description": "POST /nd/api/enterprise/enterprise_members：获取企业所有成员 接口说明，包含路径、方法、参数和返回信息。", "category": "企业 API", "top_category": "API文档", "keywords": [ "API", "获取企业所有成员", "/nd/api/enterprise/enterprise_members" ], "url": "zh/api-post-nd-api-enterprise-enterprise-members.html", "source": "content/zh/api-post-nd-api-enterprise-enterprise-members.md", "summary": "获取企业所有成员 属性 值 HTTP 方法 POST 接口路径 /nd/api/enterprise/enterprise members 所属分类 企业 API 接口说明 接口路径： /nd/api/enterprise/enterprise members HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) lang 语言类型，cn 中文 ，en 英文 , 可选 options { departmentId: // 部门 id，不填写就是企业所有人员 roleId: // 角色 id， 不填写就是不限角色 \"userType\": 0, // 0 企业内人员， 1 外部人员 \"keyName\": \"\", // 搜索关键字： 人名，手机号，邮箱， 不填写就是所有人员 \"startIndex\": 0， \"pageSize\": 20, status: // 0 所有账号， 1 停用的账号 } 可选 返回字段说明 {\"code\":0,\"success\":true,\"members\":{},\"total\":xx} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：企业 API。", "headings": [ { "level": 1, "title": "获取企业所有成员", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-4" } ], "images": [], "text": "获取企业所有成员 属性 值 HTTP 方法 POST 接口路径 /nd/api/enterprise/enterprise members 所属分类 企业 API 接口说明 接口路径： /nd/api/enterprise/enterprise members HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) lang 语言类型，cn 中文 ，en 英文 , 可选 options { departmentId: // 部门 id，不填写就是企业所有人员 roleId: // 角色 id， 不填写就是不限角色 \"userType\": 0, // 0 企业内人员， 1 外部人员 \"keyName\": \"\", // 搜索关键字： 人名，手机号，邮箱， 不填写就是所有人员 \"startIndex\": 0， \"pageSize\": 20, status: // 0 所有账号， 1 停用的账号 } 可选 返回字段说明 {\"code\":0,\"success\":true,\"members\":{},\"total\":xx} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：企业 API。" }, { "lang": "zh", "slug": "api-post-nd-api-enterprise-enterprise-logs", "title": "获取企业日志", "description": "POST /nd/api/enterprise/enterprise_logs：获取企业日志 接口说明，包含路径、方法、参数和返回信息。", "category": "企业 API", "top_category": "API文档", "keywords": [ "API", "获取企业日志", "/nd/api/enterprise/enterprise_logs" ], "url": "zh/api-post-nd-api-enterprise-enterprise-logs.html", "source": "content/zh/api-post-nd-api-enterprise-enterprise-logs.md", "summary": "获取企业日志 属性 值 HTTP 方法 POST 接口路径 /nd/api/enterprise/enterprise logs 所属分类 企业 API 接口说明 接口路径： /nd/api/enterprise/enterprise logs HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) department id 部门 id，不填写就是所有部门的日志 string 可选 keyword 日志的相关搜索关键字 string 可选 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：企业 API。", "headings": [ { "level": 1, "title": "获取企业日志", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-3" } ], "images": [], "text": "获取企业日志 属性 值 HTTP 方法 POST 接口路径 /nd/api/enterprise/enterprise logs 所属分类 企业 API 接口说明 接口路径： /nd/api/enterprise/enterprise logs HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) department id 部门 id，不填写就是所有部门的日志 string 可选 keyword 日志的相关搜索关键字 string 可选 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：企业 API。" }, { "lang": "zh", "slug": "api-post-nd-api-enterprise-broadcast", "title": "发布公告", "description": "POST /nd/api/enterprise/broadcast：发布公告 接口说明，包含路径、方法、参数和返回信息。", "category": "企业 API", "top_category": "API文档", "keywords": [ "API", "发布公告", "/nd/api/enterprise/broadcast" ], "url": "zh/api-post-nd-api-enterprise-broadcast.html", "source": "content/zh/api-post-nd-api-enterprise-broadcast.md", "summary": "发布公告 属性 值 HTTP 方法 POST 接口路径 /nd/api/enterprise/broadcast 所属分类 企业 API 接口说明 接口路径： /nd/api/enterprise/broadcast HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) title 公告内容字符串（必填） string content 内容（必填）string target users[] UserId 数组，如果为空则表示全部人员接收，string[] target deps[] 目标部门，该部门及子部门所有成员都会收到通知，string[] target users 与 target deps 至少要填 1 个 返回字段说明 {\"code\":0,\"success\":true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：企业 API。", "headings": [ { "level": 1, "title": "发布公告", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-4" } ], "images": [], "text": "发布公告 属性 值 HTTP 方法 POST 接口路径 /nd/api/enterprise/broadcast 所属分类 企业 API 接口说明 接口路径： /nd/api/enterprise/broadcast HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) title 公告内容字符串（必填） string content 内容（必填）string target users[] UserId 数组，如果为空则表示全部人员接收，string[] target deps[] 目标部门，该部门及子部门所有成员都会收到通知，string[] target users 与 target deps 至少要填 1 个 返回字段说明 {\"code\":0,\"success\":true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：企业 API。" }, { "lang": "zh", "slug": "api-get-nd-api-enterprise-broadcast", "title": "获取发布的公告", "description": "GET /nd/api/enterprise/broadcast：获取发布的公告 接口说明，包含路径、方法、参数和返回信息。", "category": "企业 API", "top_category": "API文档", "keywords": [ "API", "获取发布的公告", "/nd/api/enterprise/broadcast" ], "url": "zh/api-get-nd-api-enterprise-broadcast.html", "source": "content/zh/api-get-nd-api-enterprise-broadcast.md", "summary": "获取发布的公告 属性 值 HTTP 方法 GET 接口路径 /nd/api/enterprise/broadcast 所属分类 企业 API 接口说明 接口路径： /nd/api/enterprise/broadcast HTTP 方法： GET HTTP 方法： GET URL 参数 参数名 Comment(说明) start index number pagesize number 返回字段说明 {\"code\":0,\"broadcasts\":[],\"total\":19,\"success\":true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：企业 API。", "headings": [ { "level": 1, "title": "获取发布的公告", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-4" } ], "images": [], "text": "获取发布的公告 属性 值 HTTP 方法 GET 接口路径 /nd/api/enterprise/broadcast 所属分类 企业 API 接口说明 接口路径： /nd/api/enterprise/broadcast HTTP 方法： GET HTTP 方法： GET URL 参数 参数名 Comment(说明) start index number pagesize number 返回字段说明 {\"code\":0,\"broadcasts\":[],\"total\":19,\"success\":true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：企业 API。" }, { "lang": "zh", "slug": "api-post-nd-api-file-send-dep-discussion", "title": "发送部门讨论", "description": "POST /nd/api/file/send_dep_discussion：发送部门讨论 接口说明，包含路径、方法、参数和返回信息。", "category": "消息与登录 API", "top_category": "API文档", "keywords": [ "API", "发送部门讨论", "/nd/api/file/send_dep_discussion" ], "url": "zh/api-post-nd-api-file-send-dep-discussion.html", "source": "content/zh/api-post-nd-api-file-send-dep-discussion.md", "summary": "发送部门讨论 属性 值 HTTP 方法 POST 接口路径 /nd/api/file/send dep discussion 所属分类 消息与登录 API 接口说明 接口路径： /nd/api/file/send dep discussion HTTP 方法： POST HTTP 方法： POST 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：消息与登录 API。", "headings": [ { "level": 1, "title": "发送部门讨论", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-3" } ], "images": [], "text": "发送部门讨论 属性 值 HTTP 方法 POST 接口路径 /nd/api/file/send dep discussion 所属分类 消息与登录 API 接口说明 接口路径： /nd/api/file/send dep discussion HTTP 方法： POST HTTP 方法： POST 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：消息与登录 API。" }, { "lang": "zh", "slug": "api-post-nd-api-file-dep-discussion", "title": "获取部门讨论", "description": "POST /nd/api/file/dep_discussion：获取部门讨论 接口说明，包含路径、方法、参数和返回信息。", "category": "消息与登录 API", "top_category": "API文档", "keywords": [ "API", "获取部门讨论", "/nd/api/file/dep_discussion" ], "url": "zh/api-post-nd-api-file-dep-discussion.html", "source": "content/zh/api-post-nd-api-file-dep-discussion.md", "summary": "获取部门讨论 属性 值 HTTP 方法 POST 接口路径 /nd/api/file/dep discussion 所属分类 消息与登录 API 接口说明 接口路径： /nd/api/file/dep discussion HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) dep id 部门 id（必填）string pagesize 页的大小 string start id 消息 id,只会获取此消息之前的消息，为空则获取最新消息 string 返回字段说明 {\"msgArr\":[],\"gotMoreMessages\":1,\"code\":0,\"success\":true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：消息与登录 API。", "headings": [ { "level": 1, "title": "获取部门讨论", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-4" } ], "images": [], "text": "获取部门讨论 属性 值 HTTP 方法 POST 接口路径 /nd/api/file/dep discussion 所属分类 消息与登录 API 接口说明 接口路径： /nd/api/file/dep discussion HTTP 方法： POST HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) dep id 部门 id（必填）string pagesize 页的大小 string start id 消息 id,只会获取此消息之前的消息，为空则获取最新消息 string 返回字段说明 {\"msgArr\":[],\"gotMoreMessages\":1,\"code\":0,\"success\":true} 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：消息与登录 API。" }, { "lang": "zh", "slug": "api-get-nd-api-enterprise-enterprise-logs", "title": "获取企业日志", "description": "GET /nd/api/enterprise/enterprise_logs：获取企业日志 接口说明，包含路径、方法、参数和返回信息。", "category": "企业 API", "top_category": "API文档", "keywords": [ "API", "获取企业日志", "/nd/api/enterprise/enterprise_logs" ], "url": "zh/api-get-nd-api-enterprise-enterprise-logs.html", "source": "content/zh/api-get-nd-api-enterprise-enterprise-logs.md", "summary": "获取企业日志 属性 值 HTTP 方法 GET 接口路径 /nd/api/enterprise/enterprise logs 所属分类 企业 API 接口说明 接口路径： /nd/api/enterprise/enterprise logs HTTP 方法： GET HTTP 方法： GET URL 参数 参数名 Comment(说明) department id 部门 id（）string pagesize 页的大小 number，默认值 1000 start index 消息起始位置, number keyword 日志关键词 string startTime 起始日期: 秒 number endTime 截止日期 秒 number 返回字段说明 {\"logs\":[],\"total\":0,\"code\":0,\"success\":true} total 返回所有符合条件的(与分页 pageSize 无关) 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：企业 API。", "headings": [ { "level": 1, "title": "获取企业日志", "id": "section" }, { "level": 2, "title": "接口说明", "id": "section-2" }, { "level": 2, "title": "调用说明", "id": "section-4" } ], "images": [], "text": "获取企业日志 属性 值 HTTP 方法 GET 接口路径 /nd/api/enterprise/enterprise logs 所属分类 企业 API 接口说明 接口路径： /nd/api/enterprise/enterprise logs HTTP 方法： GET HTTP 方法： GET URL 参数 参数名 Comment(说明) department id 部门 id（）string pagesize 页的大小 number，默认值 1000 start index 消息起始位置, number keyword 日志关键词 string startTime 起始日期: 秒 number endTime 截止日期 秒 number 返回字段说明 {\"logs\":[],\"total\":0,\"code\":0,\"success\":true} total 返回所有符合条件的(与分页 pageSize 无关) 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：企业 API。" }, { "lang": "zh", "slug": "api-get-account-tokenlogin-do", "title": "JWT token 登录", "description": "GET /account/tokenLogin.do：JWT token 登录 接口说明，包含路径、方法、参数和返回信息。", "category": "消息与登录 API", "top_category": "API文档", "keywords": [ "API", "JWT token 登录", "/account/tokenLogin.do" ], "url": "zh/api-get-account-tokenlogin-do.html", "source": "content/zh/api-get-account-tokenlogin-do.md", "summary": "JWT token 登录 属性 值 HTTP 方法 GET 接口路径 /account/tokenLogin.do 所属分类 消息与登录 API 接口说明 接口路径： /account/tokenLogin.do HTTP 方法： GET 所属小节：PDF 第 29 页 userToken=xxxxxxxxxxxxxxxx defaultClrTheme=dark defaultLang=en disableUserMark=1 userToken 的构建 userToken 是含有登录用户信息的加密字符串，加密信息是通过标准的双方传输可信数据的安全机制 JWT 创建的口令字， JWT 加密的用户信息 JSONObject 内容如下： { payload: { email: “xxx@xxx.com”/“135XXXXXXX”/“XXXX”} time: now } 说明：其中 email, 可以是邮箱，手机号，工号； 代码如下： public static void main( String[] args ) { HashMap user = new HashMap (); user.put(\"email\", \"yuanchaozhao@qq.com\"); try { //token login String userToken = createTokenJWT(user); System.out.println(\" login token:\" + userToken); JSONObject parsed = parseTokenJWT(userToken); System", "headings": [ { "level": 1, "title": "JWT token 登录", "id": "jwt-token" }, { "level": 2, "title": "接口说明", "id": "section" }, { "level": 2, "title": "调用说明", "id": "section-2" } ], "images": [], "text": "JWT token 登录 属性 值 HTTP 方法 GET 接口路径 /account/tokenLogin.do 所属分类 消息与登录 API 接口说明 接口路径： /account/tokenLogin.do HTTP 方法： GET 所属小节：PDF 第 29 页 userToken=xxxxxxxxxxxxxxxx defaultClrTheme=dark defaultLang=en disableUserMark=1 userToken 的构建 userToken 是含有登录用户信息的加密字符串，加密信息是通过标准的双方传输可信数据的安全机制 JWT 创建的口令字， JWT 加密的用户信息 JSONObject 内容如下： { payload: { email: “xxx@xxx.com”/“135XXXXXXX”/“XXXX”} time: now } 说明：其中 email, 可以是邮箱，手机号，工号； 代码如下： public static void main( String[] args ) { HashMap user = new HashMap (); user.put(\"email\", \"yuanchaozhao@qq.com\"); try { //token login String userToken = createTokenJWT(user); System.out.println(\" login token:\" + userToken); JSONObject parsed = parseTokenJWT(userToken); System.out.println(\" parsed:\" + parsed); System.out.println(\" 将此 token 作为参数放在 url 中即可， 如:\"); System.out.println(\"/account/tokenLogin.do?userToken=\" + userToken); } catch (Exception e) { System.out.println(e.getMessage()); } } 其它代码 参考 jwtToken 的生成代码，在认证接口二处有提供。 备注： JWT 即 JSON Web Tokens 的简写， 是满足工业标准 RFC7519 的一种通信加密解密机制，请参考： https://jwt.io/ 调用说明 调用前需完成 获取 token 或相应免登录认证，并在请求 Header 中携带 Authorization: Bearer 。 参数和返回字段如因部署版本存在差异，应以实际私有云 API 文档和联调结果为准。 所属分类：消息与登录 API。" }, { "lang": "zh", "slug": "reference-api-pdf-full", "title": "API 完整接口资料", "description": "Babel 开发 API 完整接口资料。", "category": "源资料参考", "top_category": "API文档", "keywords": [ "API", "PDF", "原文" ], "url": "zh/reference-api-pdf-full.html", "source": "content/zh/reference-api-pdf-full.md", "summary": "API 完整接口资料 PDF 第 1 页 企业开发 API V6.6 上海画擎信息科技有限公司 姜大军 PDF 第 2 页 目录 一、 获取企业开发账号 ..............................................................................................................................................................................4 二、 认证 API ............................................................................................................................................................................................. 6 认证接口一（登录回调方式） ................................................................................................................................................................6 认证接口二（免登录方式 – JWT token 方式，在私有云部署中，需要开启 jwt token 的登录方式） ............", "headings": [ { "level": 1, "title": "API 完整接口资料", "id": "api" }, { "level": 3, "title": "PDF 第 1 页", "id": "pdf-1" }, { "level": 3, "title": "PDF 第 2 页", "id": "pdf-2" }, { "level": 3, "title": "PDF 第 3 页", "id": "pdf-3" }, { "level": 3, "title": "PDF 第 4 页", "id": "pdf-4" }, { "level": 2, "title": "一、 获取企业开发账号", "id": "section" }, { "level": 3, "title": "PDF 第 5 页", "id": "pdf-5" }, { "level": 3, "title": "PDF 第 6 页", "id": "pdf-6" }, { "level": 2, "title": "二、 认证 API", "id": "api-2" }, { "level": 3, "title": "认证接口一（登录回调方式）", "id": "section-2" }, { "level": 3, "title": "PDF 第 7 页", "id": "pdf-7" }, { "level": 3, "title": "PDF 第 8 页", "id": "pdf-8" }, { "level": 3, "title": "获取 token", "id": "token" }, { "level": 3, "title": "刷新 token", "id": "token-2" }, { "level": 2, "title": "三、 文件访问 API", "id": "api-3" }, { "level": 3, "title": "PDF 第 9 页", "id": "pdf-9" }, { "level": 3, "title": "获取文件列表", "id": "section-3" }, { "level": 3, "title": "获取文件信息", "id": "section-5" }, { "level": 3, "title": "PDF 第 10 页", "id": "pdf-10" }, { "level": 3, "title": "创建文件夹", "id": "section-7" }, { "level": 3, "title": "预上传文件", "id": "section-9" }, { "level": 3, "title": "PDF 第 11 页", "id": "pdf-11" }, { "level": 3, "title": "上传文件", "id": "section-12" }, { "level": 3, "title": "PDF 第 12 页", "id": "pdf-12" }, { "level": 3, "title": "获取下载文件地址", "id": "section-14" }, { "level": 3, "title": "获取下载多文件地址", "id": "section-16" }, { "level": 3, "title": "PDF 第 13 页", "id": "pdf-13" }, { "level": 3, "title": "获取下载文件缩略图地址", "id": "section-18" }, { "level": 3, "title": "修改文件信息", "id": "section-20" }, { "level": 3, "title": "修改文件信息", "id": "section-21" }, { "level": 3, "title": "修改文件名", "id": "section-23" }, { "level": 3, "title": "修改文件信息", "id": "section-24" }, { "level": 3, "title": "PDF 第 14 页", "id": "pdf-14" }, { "level": 3, "title": "删除文件(到回收站）", "id": "section-26" }, { "level": 3, "title": "删除文件（从回收站）", "id": "section-28" }, { "level": 3, "title": "清空回收站", "id": "section-30" }, { "level": 3, "title": "恢复文件（从回收站）", "id": "section-32" }, { "level": 3, "title": "PDF 第 15 页", "id": "pdf-15" }, { "level": 3, "title": "获取文件的所有版本信息", "id": "section-34" }, { "level": 3, "title": "设置文件当前版本", "id": "section-36" }, { "level": 3, "title": "移动文件", "id": "section-38" }, { "level": 3, "title": "拷贝文件", "id": "section-40" }, { "level": 3, "title": "PDF 第 16 页", "id": "pdf-16" }, { "level": 3, "title": "拷贝文件进度", "id": "section-42" }, { "level": 3, "title": "文件日志", "id": "section-44" }, { "level": 3, "title": "设置用户是否有权访问素材库", "id": "section-46" }, { "level": 3, "title": "PDF 第 17 页", "id": "pdf-17" }, { "level": 3, "title": "创建素材库分类", "id": "section-48" }, { "level": 3, "title": "创建子素材库", "id": "section-50" }, { "level": 2, "title": "共享文件相关 API", "id": "api-4" }, { "level": 3, "title": "PDF 第 18 页", "id": "pdf-18" }, { "level": 3, "title": "获取文件的分享 url", "id": "url-12" }, { "level": 3, "title": "获取分享的权限列表", "id": "section-53" }, { "level": 3, "title": "获取用户对于单个文件有权设置的分享角色", "id": "section-55" }, { "level": 3, "title": "创建链接分享", "id": "section-57" }, { "level": 3, "title": "PDF 第 19 页", "id": "pdf-19" }, { "level": 3, "title": "关闭链接分享", "id": "section-59" }, { "level": 3, "title": "设置链接分享密码", "id": "section-61" }, { "level": 3, "title": "邀请人员参与分享", "id": "section-63" }, { "level": 3, "title": "PDF 第 20 页", "id": "pdf-20" }, { "level": 3, "title": "获取所有分享参与人", "id": "section-65" }, { "level": 3, "title": "设置分享参与人的权限角色", "id": "section-67" }, { "level": 3, "title": "删除分享参与人", "id": "section-69" }, { "level": 3, "title": "PDF 第 21 页", "id": "pdf-21" }, { "level": 3, "title": "提醒关注", "id": "section-71" }, { "level": 3, "title": "移除某人的关注", "id": "section-73" }, { "level": 3, "title": "获取关注文件的用户列表", "id": "section-75" }, { "level": 3, "title": "获取可以关注文件的用户列表，并且标记已关注文件的用户", "id": "section-77" }, { "level": 3, "title": "PDF 第 22 页", "id": "pdf-22" }, { "level": 2, "title": "企业部门相关 API", "id": "api-5" }, { "level": 3, "title": "获取当前企业信息", "id": "section-79" }, { "level": 3, "title": "获取企业所有部门信息", "id": "section-81" }, { "level": 3, "title": "创建企业部门", "id": "section-83" }, { "level": 3, "title": "PDF 第 23 页", "id": "pdf-23" }, { "level": 3, "title": "获取部门角色列表", "id": "section-85" }, { "level": 3, "title": "添加部门人员", "id": "section-87" }, { "level": 3, "title": "PDF 第 24 页", "id": "pdf-24" }, { "level": 3, "title": "删除部门人员", "id": "section-89" }, { "level": 3, "title": "获取自己所在部门信息", "id": "section-91" }, { "level": 3, "title": "获取部门人员", "id": "section-93" }, { "level": 3, "title": "PDF 第 25 页", "id": "pdf-25" }, { "level": 3, "title": "添加企业成员", "id": "section-95" }, { "level": 3, "title": "更新成员信息", "id": "section-96" }, { "level": 3, "title": "PDF 第 26 页", "id": "pdf-26" }, { "level": 3, "title": "获取企业成员信息", "id": "section-97" }, { "level": 3, "title": "获取企业所有成员", "id": "section-99" }, { "level": 3, "title": "获取企业日志", "id": "section-101" }, { "level": 3, "title": "PDF 第 27 页", "id": "pdf-27" }, { "level": 2, "title": "消息推送 API", "id": "api-6" }, { "level": 3, "title": "发布公告", "id": "section-103" }, { "level": 3, "title": "获取发布的公告", "id": "section-105" }, { "level": 3, "title": "发送部门讨论", "id": "section-107" }, { "level": 3, "title": "PDF 第 28 页", "id": "pdf-28" }, { "level": 3, "title": "获取部门讨论", "id": "section-109" }, { "level": 3, "title": "获取企业日志", "id": "section-111" }, { "level": 3, "title": "PDF 第 29 页", "id": "pdf-29" }, { "level": 2, "title": "四、 JWT token 登录", "id": "jwt-token" }, { "level": 3, "title": "PDF 第 30 页", "id": "pdf-30" }, { "level": 2, "title": "五、 附录 通用 API 调用返回状态码", "id": "api-7" }, { "level": 2, "title": "状态码 result code", "id": "result-code" } ], "images": [], "text": "API 完整接口资料 PDF 第 1 页 企业开发 API V6.6 上海画擎信息科技有限公司 姜大军 PDF 第 2 页 目录 一、 获取企业开发账号 ..............................................................................................................................................................................4 二、 认证 API ............................................................................................................................................................................................. 6 认证接口一（登录回调方式） ................................................................................................................................................................6 认证接口二（免登录方式 – JWT token 方式，在私有云部署中，需要开启 jwt token 的登录方式） ....................................... 6 获取 token .................................................................................................................................................................................................8 刷新 token .................................................................................................................................................................................................8 三、 文件访问 API ..................................................................................................................................................................................... 8 获取文件列表 ............................................................................................................................................................................................9 获取文件信息 ............................................................................................................................................................................................9 创建文件夹 ..............................................................................................................................................................................................10 预上传文件 ..............................................................................................................................................................................................10 上传文件 ..................................................................................................................................................................................................11 获取下载文件地址 ..................................................................................................................................................................................12 获取下载多文件地址 ..............................................................................................................................................................................12 获取下载文件缩略图地址 ......................................................................................................................................................................13 修改文件信息 ..........................................................................................................................................................................................13 修改文件名 ..............................................................................................................................................................................................13 删除文件(到回收站） .............................................................................................................................................................................14 删除文件（从回收站） ..........................................................................................................................................................................14 清空回收站 ..............................................................................................................................................................................................14 恢复文件（从回收站） ..........................................................................................................................................................................14 获取文件的所有版本信息 ......................................................................................................................................................................15 设置文件当前版本 ..................................................................................................................................................................................15 移动文件 ..................................................................................................................................................................................................15 拷贝文件 ..................................................................................................................................................................................................15 拷贝文件进度 ..........................................................................................................................................................................................16 文件日志 ..................................................................................................................................................................................................16 创建素材库分类 ......................................................................................................................................................................................17 创建子素材库 ..........................................................................................................................................................................................17 共享文件相关 API ................................................................................................................................................................................. 17 获取文件的分享 url ................................................................................................................................................................................ 18 获取分享的权限列表 ..............................................................................................................................................................................18 获取用户对于单个文件有权设置的分享角色 ......................................................................................................................................18 创建链接分享 ..........................................................................................................................................................................................18 关闭链接分享 ..........................................................................................................................................................................................19 设置链接分享密码 ..................................................................................................................................................................................19 邀请人员参与分享 ..................................................................................................................................................................................19 获取所有分享参与人 ..............................................................................................................................................................................20 设置分享参与人的权限角色 ..................................................................................................................................................................20 删除分享参与人 ......................................................................................................................................................................................20 提醒关注 ..................................................................................................................................................................................................21 移除某人的关注 ......................................................................................................................................................................................21 获取关注文件的用户列表 ......................................................................................................................................................................21 获取可以关注文件的用户列表，并且标记已关注文件的用户 ..........................................................................................................21 企业部门相关 API ................................................................................................................................................................................. 22 获取当前企业信息 ..................................................................................................................................................................................22 获取企业所有部门信息 ..........................................................................................................................................................................22 创建企业部门 ..........................................................................................................................................................................................22 获取部门角色列表 ..................................................................................................................................................................................23 添加部门人员 ..........................................................................................................................................................................................23 删除部门人员 ..........................................................................................................................................................................................24 获取自己所在部门信息 ..........................................................................................................................................................................24 获取部门人员 ..........................................................................................................................................................................................24 添加企业成员 ..........................................................................................................................................................................................25 更新成员信息 ..........................................................................................................................................................................................25 获取企业成员信息 ..................................................................................................................................................................................26 获取企业所有成员 ..................................................................................................................................................................................26 获取企业日志 ..........................................................................................................................................................................................26 消息推送 API ......................................................................................................................................................................................... 27 发布公告 ..................................................................................................................................................................................................27 获取发布的公告 ......................................................................................................................................................................................27 发送部门讨论 ..........................................................................................................................................................................................27 获取部门讨论 ..........................................................................................................................................................................................28 获取企业日志 ..........................................................................................................................................................................................28 四、 JWT token 登录 .................................................................................................................................................................................29 五、 附录 通用 API 调用返回状态码 ............................................................................................................................................... 30 PDF 第 3 页 状态码 result code ................................................................................................................................................................................. 30 PDF 第 4 页 一、 获取企业开发账号 登录巴别鸟私有云企业管理后台，在首页中设置开发者账号： 打开后填写回调函数地址：http://xxx.xxx.xxx.xxx/public/babelAuthResult.do 填写后点击确定后自动产生开发者 id (client id)和开发者密钥(client secret)： 注：jwtToken 为相应的生成 jwtToken 时的加密密钥。 PDF 第 5 页 PDF 第 6 页 二、 认证 API 认证接口一（登录回调方式） /api/authorize.do HTTP 请求方式 GET URL 参数 参数名 Comment(说明) response type 必须为 code（必填） string client id 开发者的 id（必填） string redirect uri 回调函数地址，需要和注册时保持一致（必填） string data 任意数据，回调时传回 string 例如： /api/authorize.do?response type=code&client id=xxxxx&redirect uri=http://xxx.xxx.xxx&data=xxx 通过浏览器访问 返回结果 如果用户未登录，则会跳转到登录页，登录后如果未授权，则会 302 跳转到授权页，如果用户已经授权，则会 302 跳转到 redirect uri 并且带上授权码和 data，类似于 http://xxx.xxx.xxx?code=xxx&data=xxx code 有效期 5 分钟。 认证接口二（免登录方式 – JWT token 方式，在私有云部署中，需要开启 jwt token 的登录方 式） /api/authorizeByJWT.do HTTP 请求方式 GET URL 参数 参数名 Comment(说明) response type 必须为 code（必填） string client id 开发者的 id（必填） string jwt token Jwt token，（必填） string 是对{client id: xxxxxxx} 加密 形成的字符串 email email(可选), 传入用户的邮箱，以该用户进行登录，不填以企业管理员进行登录，string phone phone(可选), 传入用户的手机号，以该用户进行登录，不填以企业管理员进行登录， string babelId babelId(可选), 传入用户的工号，以该用户进行登录，不填以企业管理员进行登录， string PDF 第 7 页 例如： /api/authorizeByJWT.do?response type=code&client id=xxxxx&jwt token=xxx 说明：使用这个 api，如果不填 email, phone, babelId 系统将自动以管理员身份登录，否则会以 email, phone, babelId 对应的用户去 登录，不会显示登录界面去登录。注（email, phone, babelId）只需其中一个就可。 返回结果 { \"success\": true \"code\": \"xxxxxxxxxxxxxxxxxxxxxxxxx\", } jwt token 为 自己写程序生成 样例代码如下: import java.util.Date; import java.util.HashMap; import java.util.Map; import javax.crypto.SecretKey; import javax.crypto.spec.SecretKeySpec; import io.jsonwebtoken.Claims; import io.jsonwebtoken.JwtBuilder; import io.jsonwebtoken.Jwts; import io.jsonwebtoken.SignatureAlgorithm; import net.sf.json.JSONObject; / 生成标准 jwt 使用的 token / public class JWT App { static String skey = \"babeldfdfer95840834 t8e 9 9 5934 5943 5886256\"; // 密钥 在巴别鸟后台 开发者账号处 填入的 jwtToken 字段。 public static void main( String[] args ) { HashMap clientInfo = new HashMap (); clientInfo.put(\"client id\", \"7459492016147273\"); // 为开发者账户中的 client id try { String token = createTokenJWT(clientInfo); System.out.println(\" login token:\" + token); String token1 = \"eyJhbGciOiJIUzI1NiJ9.eyJkdXJhdGlvbiI6NjAsInBheWxvYWQiOnsiY2xpZW50X2lkIjoiNzQ1OTQ5MjAxNjE0NzI3MyJ9LCJ0aW1lIjoxNjkxNDg4MzY4NTk0fQ.pRFCwXd2snMr IgFWOFwYbvyAeeNhoFINGk Wmv7d24g\"; JSONObject parsed = parseTokenJWT(token1); System.out.println(\" parsed:\" + parsed); System.out.println(\" 将此 token 作为参数放在 url 中即可， 如:\"); } catch (Exception e) { System.out.println(e.getMessage()); } } public static String createTokenJWT(Map config) throws Exception { HashMap data = new HashMap (); data.put(\"time\", new Date().getTime()); data.put(\"duration\", 60); data.put(\"payload\", config); SignatureAlgorithm signatureAlgorithm = SignatureAlgorithm.HS256; SecretKey key = generalKey(); JwtBuilder builder = Jwts.builder() .setClaims(data) .signWith(signatureAlgorithm, key); System.out.println( \" builder :\" + builder); return builder.compact(); } public static JSONObject parseTokenJWT(String jwt) throws Exception { SecretKey key = generalKey(); Claims claims = Jwts.parser() .setSigningKey(key) .parseClaimsJws(jwt) .getBody(); System.out.println(\" claims:\" + claims.toString()); Long time = (Long)claims.get(\"time\"); long duration = (Integer)claims.get(\"duration\"); Long now = new Date().getTime(); if (now time 1000 duration) return null; // 超过 10 分钟的 token 无效 JSONObject obj = JSONObject.fromObject(claims.get(\"payload\")); return obj; } public static SecretKey generalKey(){ String stringKey = skey; byte[] encodedKey = stringKey.getBytes(); SecretKey key = new SecretKeySpec(encodedKey, 0, encodedKey.length, \"HmacSHA256\"); return key; } } PDF 第 8 页 获取 token /api/token.do HTTP 方法： POST HTTP Header 该接口使用 Basic Auth 的方式校验 client 的信息。具体做法是在 header 中添加类似于\"Authorization: Basic xxxxxxxxx\"。其中 \"xxxxxxxxx\"是通过开发者 id (client id)和开发者秘钥(client secret)算出来的，具体算法为 Base64Encode(client id + \":\" + client secret) Base64Encode 自行选择工具进行 Base64 编码 URL 参数 参数名 Comment(说明) grant type（必填） 必须为 authorization code string code（必填） 授权码，即回调地址接收到的授权码，授权码的有效期为 5 分钟，用过一次，无论成功 还是失败，授权码都会失效 string 例如： /api/token.do?grant type=authorization code&code=xxx&redirect uri=http://xxx.xxx.xxx 返回结果 access token 接口访问标识 refresh token 用来刷新 access token，有效时间为 30 天 expires in access token 的有效时间，单位为 s 刷新 token /api/refreshToken.do HTTP 方法： POST HTTP Header 该接口使用 Basic Auth 的方式校验 client 的信息。具体做法是在 header 中添加类似于\"Authorization: Basic xxxxxxxxx\"。其中 \"xxxxxxxxx\"是通过 client id 和 client secret 算出来的，具体算法为 Base64Encode(client id + \":\" + client secret) URL 参数 参数名 Comment(说明) grant type（必填） 必须为 refresh token string refresh token（必填） 即接口 2 中获取到的 refresh token string 例如： /api/refreshToken.do?grant type=refresh token&refresh token=xxx 返回结果 access token 接口访问标识, refresh token 用来刷新 access token，有效时间为 30 天 expires in access token 的有效时间 为 3600，单位为 s 三、 文件访问 API 所有的接口在访问时需要在 HTTP header 中带上 access token。对于含有请求参数的接口，通常是一些 POST、 PUT 或者 DELETE 接口，还需要设置 Content Type 来指定参数的格式。如果需要访问不同版本的 API，就需要 在请求路径上指定具体版本，如果需要返回不同格式的 response body，那么还需要设置 Accept。所有的参数都应 该采用 utf 8 的编码。 PDF 第 9 页 Headers： Authorization：存放 access token，格式为：\"Bearer \" + access token。 Content Type：指明请求参数的格式。如果是 POST、PUT 或者 DELETE 请求，需要指定\"application/json\"，我 们目前不支持其他请求参数的格式，比如 xml。如果是其他类型比如 GET 请求，可以不在 header 中设置 Content Type。 Accept：用于指定响应结果的格式以及 api 的版本信息。目前只支持返回 json 格式的 response，所以一般情况下 指定\"application/json\"。 若接口访问成功，我们会返回 json 格式的 response，并且 HTTP 的 status code 为 200。所有请求成功的 response 的 json 都会带有\"success: true”。response 的 header 里的 X Babel Version 表示此次请求访问的 api 的版本号。 获取文件列表 /nd/api/file/list dir HTTP 方法： GET URL 参数 参数名 Comment(说明) parent id 父文件夹 id（必填） string 当 parent 为 1 时返回企业文件夹内容，2 返回个人文件夹内容，3 返回我的 项目，4 返回我加入的分享，其它 fileId 返回正常的文件夹中的内容。 page size 页的大小 number page 页号 number type 类型：分为 1 file，2 folder，0 all 三种类型 string 返回字段说明 属性名 类型 说明 files 数组 文件信息 {fileId, name, …} total int 总数量 page int 页容量 success boolean 获取成功标记 code int 返回错误码 0 表示成功 获取文件信息 /nd/api/file/fileinfo HTTP 方法： GET URL 参数 参数名 Comment(说明) id 文件 id（必填） string 返回字段说明 fileInfo 信息 属性名 类型 说明 file Object 文件信息 { id, name, …} PDF 第 10 页 success boolean 获取成功标记 code int 返回错误码 0 表示成功 创建文件夹 /nd/api/file/create folder HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) parent id 目标文件夹 id（必填） string name 文件名（必填） string 返回字段说明 属性名 类型 说明 file Object 文件信息 { id, name, …} success boolean 获取成功标记 code int 返回错误码 0 表示成功 预上传文件 用于返回第二步上传文件时所需要的参数(url、upload token) /api/file/preUploadFile.do HTTP 方法： GET URL 参数 参数名 Comment(说明) parent id 目标文件夹 id（必填）(在根目录下上传可忽略此项) string name 文件名（必填） string file id 上传新版本时需要指定上传那个文件的新版本(上传新文件可忽略此项) string 正确的返回结果如下 {\"upload token\":\"92808ecfc2ac4e0ebc0b912edac3be4a\",\"url\":\"http://testdocument.babel.cc/api/file/uploadPdf.do\",\"su ccess\":true,\"code\":0} 返回字段说明 属性名 类型 说明 url string 该 url 仅能使用 1 次，且有效期为 1 小时 调用此 url 上传文件，成功后会返回 fileId， fileName、version 等 upload token string 上传文件时作为 post 的参数 PDF 第 11 页 上传文件 注意，本 api 的 url 是预上传接口返回的, 这里没有具体的 url，只是参数说明 https://xxx.xxx.xxx:xxx/api/file/uploadXXX.do（具体的 url 是由上一节 /api/file/preUploadFile.do 中返回的 url） POST POST 请求体参数 参数名 Comment(说明) file 文件二进制数据(上传数据) upload token /api/file/preUploadFile.do 请求中的返回值 返回信息如下 {\"fileId\":\"7728538212615908\",\"version\":0,\"fileName\":\"mesos.pdf\",\"fileSize\":848854,\"success\":true,\"code\":0} 上传相关代码 示例 加入 ‘com.squareup.okhttp3:okhttp:3.3.1’ 包 private void uploadFile(final String fileName, String parentId, final DaoCallback callback){ preUploadFile(fileName, parentId, new DaoCallback () { @Override public void onSuccess(JSONObject data) { int code = data.optInt(\"code\", 1); final String url = data.optString(\"url\", null); final String uploadToken = data.optString(\"upload token\"); if (code == 0) { // File file = new File(filePath); RequestBody fileContent = RequestBody.create(MultipartBody.FORM, file); RequestBody requestBody = new MultipartBody.Builder() .setType(MultipartBody.FORM) .addFormDataPart(\"file\", fileName, fileContent) .addFormDataPart(\"upload token\", uploadToken) .build(); Request request = new Request.Builder() .url(url) .post(requestBody) .build(); // 上传需要较长的时间，因此需要设置较长的 timeout OkHttpClient okHttpClient = new OkHttpClient(); okHttpClient.newCall(request) .enqueue(new okhttp3.Callback() { @Override public void onFailure(okhttp3.Call call, IOException e) { callback.onFailure( 1, null); } @Override public void onResponse(okhttp3.Call call, okhttp3.Response response) throws IOException { int httpCode = response.code(); if (httpCode == 200) { try { JSONObject result = new JSONObject(response.body().string()); response.body().close(); boolean success = result.getBoolean(\"success\"); if (success) { callback.onSuccess(null); } else { int code = result.getInt(\"code\"); String msg = result.optString(\"msg\"); callback.onFailure(code, msg); } } catch (JSONException e) { callback.onFailure( 2, null); } } else { callback.onFailure(httpCode, null); } } }); } } @Override public void onFailure( int errorCode, String msg){ Log.e(\"FileTransfer\", \"filePreUpload 失败 errorCode=\" + errorCode); } }); } PDF 第 12 页 private void preUploadFile(String fileName, String parentId, final DaoCallback callback) { String preUploadUrl = \"http://private.babel.cc:80/api/file/preUploadFile.do?name=1234.jpg&parent id=0\"; // 传入相应的参数 name, parent id String authorization = \"Bearer d48d0a0e253c4a2985d8c5653f717d71\"; //根据说明 生成 Request request = new Request.Builder().url(preUploadUrl) .addHeader(\"Authorization\", authorization) .build(); OkHttpClient okHttpClient = new OkHttpClient(); okHttpClient.newCall(request).enqueue(new okhttp3.Callback() { @Override public void onFailure(okhttp3.Call call, IOException e) { Log.d(\"\", \"\"); } @Override public void onResponse(okhttp3.Call call, okhttp3.Response response) throws IOException { Log.d(\"\",\"\"); int httpCode = response.code(); if (httpCode == 200) { JSONObject result = null; try { result = new JSONObject(response.body().string()); } catch (JSONException e) { e.printStackTrace(); } try { boolean success = result.getBoolean(\"success\"); if (success) { String url = result.getString(\"url\"); callback.onSuccess(result); } else { int code = result.getInt(\"code\"); String msg = result.optString(\"msg\"); callback.onFailure(code, msg); } } catch (JSONException e) { callback.onFailure( 2, null); } } else { callback.onFailure(httpCode, null); } } }); } 获取下载文件地址 /api/file/getFileDownloadUrl.do HTTP 方法： GET URL 参数 参数名 Comment(说明) fileId 需要下载的文件 id（必填） string version 文件的版本号（可选） number 返回信息如下 {\"code\":0,\"success\":true,\"type\":\"文件类型\",\"url\":\"文件下载地址\"} 获取下载多文件地址 /api/file/downloadMultiFiles.do HTTP 方法： GET URL 参数 参数名 Comment(说明) fileIdArr 由需要下载的文件 id 组成的字符串，由符号“!“(半角)分割，比如下载 id 为 133 与 233 的两 个文件，则 fileIdArr 的值为“133!233” string 类型 PDF 第 13 页 返回信息如下 {\"code\":0,\"success\":true,\"type\":\"文件类型\",\"url\":\"文件下载地址\"} 返回值 url 为多个文件打包后的下载地址。 获取下载文件缩略图地址 /api/file/downloadThumbnail.do HTTP 方法： GET URL 参数 参数名 Comment(说明) fileId 需要下载的文件 id（必填） string version 文件的版本号（可选） number size 需要显示的缩略图尺寸，取宽高中的最大值 返回信息如下 {\"code\":0,\"success\":true, \"url\":\"文件下载地址\"} 返回值 url 为多个文件打包后的下载地址。 修改文件信息 /nd /api/file/update file HTTP 方法： POST 修改文件信息 POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填） string name 新文件名 （可选） string description 文件说明 （可选） string 返回信息如下 {\"code\":0,\"success\":true} 修改文件名 /nd /api/file/rename HTTP 方法： POST 修改文件信息 POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填） string name 新文件名 string 返回信息如下 {\"code\":0,\"success\":true} PDF 第 14 页 删除文件(到回收站） /nd /api/file/remove file HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file ids[] 目标文件 id 数组（必填） string[] 返回信息如下 {\"code\":0,\"success\":true} 删除文件（从回收站） /nd /api/file/remove from trash HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file ids[] 目标文件 id 数组（必填） string[] 返回信息如下 {\"code\":0,\"success\":true} 清空回收站 /nd /api/file/empty trash HTTP 方法： POST POST 请求体参数 参数名 说明 返回信息如下 {\"code\":0,\"success\":true} 恢复文件（从回收站） /nd /api/file/restore file HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file ids[] 目标文件 id 数组 string[] restoreAll 不填写 file ids, restoreAll 为 true，时恢复回收站中所有文件，boolean 返回信息如下 PDF 第 15 页 {\"code\":0,\"success\":true} 获取文件的所有版本信息 /nd /api/file/versions HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 目标文件 id（必填） string 返回信息如下 {\"code\":0,\"versions\":[],\"success\":true} 设置文件当前版本 /nd /api/file/version HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file id 目标文件 id （必填） string version 版本号（必填） number 返回信息如下 {\"code\":0,\"success\":true} 移动文件 /nd /api/file/move HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file ids 需要移动的目标文件 id 数组（必填） string target id 需要移动到的目标文件夹 id（必填） string 返回信息如下 {\"code\":0,\"success\":true} 拷贝文件 /nd /api/file/copy HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) PDF 第 16 页 file ids 需要拷贝的目标文件 id 数组（必填） string target id 需要拷贝到的目标文件夹 id（必填） string 返回信息如下 { \"code\": 0, \"copyKey\": \"81427630 054a 11ef 8355 db93b4b1d006\",\"fileNum\": 10, \"success\": true} 拷贝文件进度 /nd /api/file/copy progress HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) copyKey 查看拷贝进度 copyKey 由 copy 接口返回（必填） string 返回信息如下 { \"code\": 0, \"completed\": 10,\"total\": 10, \"result\": {}, \"success\": true} 文件日志 /nd /api/file/file logs HTTP 方法： GET GET 请求体参数 参数名 Comment(说明) file id 目标文件 id 数组（必填） string startIndex 获取日志的起始顺序 第几条日志开始返回（选填） int 默认 0， pageSize 每页返回的个数（选填） int type 日志类型(选填) int 默认 0, 查看所有记录， 1 仅查看访问记录，2 仅查看上传下载，3 仅查看匿名用 户，4 仅查看分享及邀请，5 仅查看删除记录 userName 某个用户名 (选填) string, 返回某个用户的日志 lang 语言(选填) 默认 cn, string 返回日志的语言 cn(中文) en(英文) 返回信息如下 {\"code\":0,\"success\":true, \"logs\":[], \"total\":50} 设置用户是否有权访问素材库 /nd /api/file/ set user access material library HTTP 方法： POST GET 请求体参数 参数名 Comment(说明) userId 用户的 id 数组数型 [usrId1, userId2]（必填） string can 是否可访问 数值类型 （必填） int 默认 0， 0： 不可访问， 1:可以访问 返回信息如下 {\"code\":0,\"success\":true} PDF 第 17 页 创建素材库分类 /nd /api/file/create material class HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) destDirFileId 目标文件夹 的 fileId（必填） string name 创建分类库的名称（必填） string accessType 分类可见性 (选填) 默认为公开 0. 0: // 公开 1: // 需要申请 2: // 部门公开 3: // 部门申请 4: // 保密 managerIds 负责人的 id 数组类型 [usrId1,userId2] departmentIds 分类可见性 限定部门 的部门 id (选填) 数组类型 [departmentId1,departmentId2] 返回信息如下 {\"code\":0, \"success\":true, \"materialClass\": {}} 创建子素材库 /nd /api/file/create material folder HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) destDirFileId 目标文件夹 的 fileId（必填） string name 创建分类库的名称（必填） string accessType 分类可见性 (选填) 默认为公开 0. 0: // 公开 1: // 需要申请 2: // 部门公开 3: // 部门申请 4: // 保密 managerId 负责人的 id (选填) string departmentIds 分类可见性 限定部门 的部门 id (选填) 数组类型 [departmentId1,departmentId2] assistantIds 素材库助理人员的 id （选填） 数组类型 [usrId1,userId2] 返回信息如下 {\"code\":0, \"success\":true, \"materialFolder\": {}} 共享文件相关 API PDF 第 18 页 获取文件的分享 url /nd/api/share/shareurl HTTP 方法： GET 获取文件的分享链接（先打开分享后，再获取该链接） URL 参数 参数名 Comment(说明) file id 文件 id string is https 返回的 share url 协议是否为 https 0 为 http, 1 为 https， 默认 0 number 返回字段说明 {\"code\":0,\"url\":\"https://private.babel.cc/share.do?s=http://private.babel.cc/share.do?s=MjY2OTYzNTk3OTU2NzEzOTtXZWQgSnVsIDAxIDIwMj AgMTg6MzM6NTAgR01UKzA4MDAgKEhvbmcgS29uZyBTdGFuZGFyZCBUaW1lKQ%3D%3D\",\"success\":true} 获取分享的权限列表 /nd/api/share/share roles HTTP 方法： GET URL 参数 参数名 Comment(说明) 返回字段说明 {\"code\":0,\"roles\":[],\"success\":true} 获取用户对于单个文件有权设置的分享角色 /nd/api/share/share role forfile HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 文件 id string 返回字段说明 {\"code\":0,\"roles\":[],\"success\":true} 创建链接分享 /nd/api/share/open link share HTTP 方法： POST 打开分享，获取新的分享链接，之前的链接失效。 PDF 第 19 页 POST 请求体参数 参数名 Comment(说明) file id 预分享的文件 id（必填） string link role id 分享的角色 string is https 返回的 share url 协议是否为 https number anonymousVisit 是否允许匿名访问，1 为允许，0 为不允许（可选，默认为 1） number 返回字段说明 {\"code\":0,\"share url\":\"http://private.babel.cc/share.do?s=http://private.babel.cc/share.do?s=MjY2OTYzNTk3OTU2NzEzOTtXZWQgSnV sIDAxIDIwMjAgMTg6MzM6NTAgR01UKzA4MDAgKEhvbmcgS29uZyBTdGFuZGFyZCBUaW1lKQ%3D%3D\",\"password\":\"\",\"success\":tru e} 关闭链接分享 /nd/api/share/close link share HTTP 方法： POST 关闭我打开的分享链接 POST 请求体参数 参数名 Comment(说明) file id 分享的文件 id（必填） string 返回字段说明 {\"code\":0,\"success\":true} 设置链接分享密码 /nd/api/share/set share password HTTP 方法： POST 文件链接分享已打开，设置链接分享的密码。 POST 请求体参数 参数名 Comment(说明) file id 预分享的文件 id（必填） string password 链接分享的密码 string is https 返回的 share url 协议是否为 https number 返回字段说明 {\"code\":0,\"success\":true, \"share url\": \"http://private.babel.cc/share.do?s=xxxxxxxxxxx\"} 邀请人员参与分享 /nd/api/share/invite share HTTP 方法： POST PDF 第 20 页 可以根据用户的邮箱或者手机来邀请某些人来访问文件 POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填） string share role 分享的权限的 id（以上所有人共享此权限）（必填） string emails[] 邮箱数组 string[] phones[] 手机号的数组 string[] 返回字段说明 {\"code\":0,\"success\":true} 获取所有分享参与人 /nd/api/share/share participants HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 文件 id（必填） string 返回字段说明 {\"code\":0,\"users\":[],\"success\":true} 设置分享参与人的权限角色 /nd/api/share/set participant role HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填） string babelshare id int（必填） 用户 id string role id int（必填） 角色 id string 返回字段说明 {\"code\":0,\"success\":true} 删除分享参与人 /nd/api/file/remove share participant HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) PDF 第 21 页 file id 文件 id（必填） string babelshare ids[] int （必填） 用户 id string 返回字段说明 {\"code\":0,\"success\":true} 提醒关注 /nd/api/file/focus file HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填） string user ids[] 提醒的用户的 id，此 id 应该在文件参与人中选取，否则提醒不会起作用（必填）string[] 返回字段说明 {\"code\":0,\"success\":true} 移除某人的关注 /nd/api/file/unfocus file HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) file id 文件 id（必填）string user ids[] 提醒的用户的 id，此 id 应该在文件参与人中选取，否则提醒不会起作用（必填） string[] 返回字段说明 {\"code\":0,\"success\":true} 获取关注文件的用户列表 /nd/api/file/user focusfile HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 文件 id（必填） string 返回字段说明 {\"code\":0,\"users\":[],\"success\":true} 获取可以关注文件的用户列表，并且标记已关注文件的用户 /nd/api/file/user can focusfile PDF 第 22 页 HTTP 方法： GET URL 参数 参数名 Comment(说明) file id 文件 id（必填） string 返回字段说明 企业部门相关 API 获取当前企业信息 /nd/api/enterprise/current HTTP 方法： GET URL 参数 参数名 Comment(说明) 无 返回字段说明 {\"code\":0,\"enterprise\":{},\"success\":true} 获取企业所有部门信息 /nd/api/enterprise/departments HTTP 方法： GET URL 参数 参数名 Comment(说明) 无 返回字段说明 属性名 类型 说明 departments []数组 返回所有的部门信息 tree {}json 数据 返回部门的父子结构信息 code int sucess boolean 创建企业部门 /nd/api/enterprise/create department HTTP 方法： POST PDF 第 23 页 POST 请求体参数 参数名 Comment(说明) parent dep 父部门 id， 0 表示跟部门（必填）string name 部门名称（必填）string description 部门描述 string 返回字段说明 属性名 类型 说明 department {} json 数据结构 code int sucess boolean 获取部门角色列表 /nd/api/enterprise/dep role HTTP 方法： GET URL 参数 参数名 Comment(说明) 返回字段说明 属性名 类型 说明 roles []数组 { id, filePermission,enterpriseId,filePermission,managerPermission, default,nameEn,name} code int sucess boolean 添加部门人员 /nd/api/enterprise/add dep mem HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) department id 部门 id（必填）string user ids[] 用户列表 string[] role id 用户在部门中的角色 string PDF 第 24 页 返回字段说明 属性名 类型 说明 删除部门人员 /nd/api/enterprise/remove dep mem HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) department id 部门 id（必填）string user ids[] 人员的 id（必填）string[] 返回字段说明 属性名 类型 说明 获取自己所在部门信息 /nd/api/enterprise/mydeparments HTTP 方法： GET URL 参数 参数名 Comment(说明) 无 返回字段说明 属性名 类型 说明 departments []数组 返回我所在的部门信息 code int sucess boolean 获取部门人员 /nd/api/enterprise/departmentmembers PDF 第 25 页 HTTP 方法： GET URL 参数 参数名 Comment(说明) department id 部门 id（必填）string 返回字段说明 属性名 类型 说明 users 数组 ： {id, name, avatrUrl,} 添加企业成员 /nd/api/enterprise/add ent mem HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) email Email 邮箱 string password 密码 string enterprise role 企业成员角色, 可选 number department ids[] 该用户的部门， 可选 string[] department roles[] 在部门中的角色， 可选 string[] sex 性别 0 未设置 1 男 2 女 number name 用户名 string phone 手机号， 可选 string babelId 工号，可选 string spacelimit 个人空间限制，单位 GB, 0 表示不限制 number can ownfile 用户能否拥有个人文件， 1 使用企业总体设置, 0 没有个人文件, 1 有个人文件 number remarks 用户描述， 可选 string join time 用户加入企业时间，Unix time, 单位秒 number password is md5 传入密码是否需要 md5 加密, 0 非 md5 密码， 1 md5 加密过的密码 number 更新成员信息 /api/updateUserInfo.do HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) email 邮箱地址（搜索关键字，必须）string password 密码（修改密码，可选）string frozen 1 – 表示冻结， 0 – 表示解冻 （冻结该账号，可选）number password is md5 传入密码是否需要 md5 加密, 0 非 md5 密码， 1 md5 加密过的密码 number phone 手机号 (可选) string PDF 第 26 页 获取企业成员信息 /api/getEnterpriseMember.do HTTP 方法： GET URL 参数 参数名 Comment(说明) email 邮箱地址（搜索关键字）string phone 手机号（搜索关键字）string babelId 工号（搜索关键字）string email/phone/babelId 可选择其一 返回字段说明 {\"code\":0,\"success\":true,\"user\":{}} 获取企业所有成员 /nd/api/enterprise/enterprise members HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) lang 语言类型，cn 中文 ，en 英文 , 可选 options { departmentId: // 部门 id，不填写就是企业所有人员 roleId: // 角色 id， 不填写就是不限角色 \"userType\": 0, // 0 企业内人员， 1 外部人员 \"keyName\": \"\", // 搜索关键字： 人名，手机号，邮箱， 不填写就是所有人员 \"startIndex\": 0， \"pageSize\": 20, status: // 0 所有账号， 1 停用的账号 } 可选 返回字段说明 {\"code\":0,\"success\":true,\"members\":{},\"total\":xx} 获取企业日志 /nd/api/enterprise/enterprise logs HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) department id 部门 id，不填写就是所有部门的日志 string 可选 keyword 日志的相关搜索关键字 string 可选 PDF 第 27 页 startTime 日志起始时间 number 可选 endTime 日志截止时间 number 可选 startIndex int 可选 pageSize int 可选 返回字段说明 {\"code\":0,\"success\":true,\"logs\":{},\"total\":xx} 消息推送 API 发布公告 /nd/api/enterprise/broadcast HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) title 公告内容字符串（必填） string content 内容（必填）string target users[] UserId 数组，如果为空则表示全部人员接收，string[] target deps[] 目标部门，该部门及子部门所有成员都会收到通知，string[] target users 与 target deps 至少要填 1 个 返回字段说明 {\"code\":0,\"success\":true} 获取发布的公告 /nd/api/enterprise/broadcast HTTP 方法： GET URL 参数 参数名 Comment(说明) start index number pagesize number 返回字段说明 {\"code\":0,\"broadcasts\":[],\"total\":19,\"success\":true} 发送部门讨论 /nd/api/file/send dep discussion HTTP 方法： POST PDF 第 28 页 POST 请求体参数 参数名 Comment(说明) dep id 部门 id（必填） string message 信息字符（必填） string json 字符串, 格式{Type: “Text”, Body:”你好” } 返回字段说明 {\"code\":0,\"messageId\":99,\"success\":true} 获取部门讨论 /nd/api/file/dep discussion HTTP 方法： POST POST 请求体参数 参数名 Comment(说明) dep id 部门 id（必填）string pagesize 页的大小 string start id 消息 id,只会获取此消息之前的消息，为空则获取最新消息 string 返回字段说明 {\"msgArr\":[],\"gotMoreMessages\":1,\"code\":0,\"success\":true} 获取企业日志 /nd/api/enterprise/enterprise logs HTTP 方法： GET URL 参数 参数名 Comment(说明) department id 部门 id（）string pagesize 页的大小 number，默认值 1000 start index 消息起始位置, number keyword 日志关键词 string startTime 起始日期: 秒 number endTime 截止日期 秒 number 返回字段说明 {\"logs\":[],\"total\":0,\"code\":0,\"success\":true} total 返回所有符合条件的(与分页 pageSize 无关) PDF 第 29 页 四、 JWT token 登录 在私有云部署中，可以开启 jwt token 的登录方式，在这种情况下，允许通过下面的 url 直接以某用户的身份免登录进入网盘系 统： /account/tokenLogin.do 参数： 参数名称 可选性 说明 可选值 默认值 userToken 必填 含有登录用户的加密信息（构造方 无 法详见下面的说明） fileId 可选 要访问的文件（夹）的 id，如果不 无 填写则打开用户根目录 closeTitleBar 可选 是否关闭标题栏 1 关闭 0 不关闭 0 disableEntMark 可选 是否隐藏左上角企业标识 1 隐藏 0 不隐藏 0 disableUserMark 可选 是否隐藏右上角用户设置入口 1 隐藏 0 不隐藏 0 defaultLang 可选 设置界面使用的语言 cn 中文 en 英文 zh HK 繁体 cn defaultClrTheme 可选 设置界面颜色主题 normal 标准模式，dark 暗色模式 normal 比如下面是以英文及暗色模式并隐藏右上角用户标志进入用户根目录界面 /account/tokenLogin.do userToken=xxxxxxxxxxxxxxxx defaultClrTheme=dark defaultLang=en disableUserMark=1 userToken 的构建 userToken 是含有登录用户信息的加密字符串，加密信息是通过标准的双方传输可信数据的安全机制 JWT 创建的口令字， JWT 加密的用户信息 JSONObject 内容如下： { payload: { email: “xxx@xxx.com”/“135XXXXXXX”/“XXXX”} time: now } 说明：其中 email, 可以是邮箱，手机号，工号； 代码如下： public static void main( String[] args ) { HashMap user = new HashMap (); user.put(\"email\", \"yuanchaozhao@qq.com\"); try { //token login String userToken = createTokenJWT(user); System.out.println(\" login token:\" + userToken); JSONObject parsed = parseTokenJWT(userToken); System.out.println(\" parsed:\" + parsed); System.out.println(\" 将此 token 作为参数放在 url 中即可， 如:\"); System.out.println(\"/account/tokenLogin.do?userToken=\" + userToken); } catch (Exception e) { System.out.println(e.getMessage()); } } 其它代码 参考 jwtToken 的生成代码，在认证接口二处有提供。 备注： JWT 即 JSON Web Tokens 的简写， 是满足工业标准 RFC7519 的一种通信加密解密机制，请参考： https://jwt.io/ PDF 第 30 页 五、 附录 通用 API 调用返回状态码 状态码 result code 码值 说明 0 成功 1 未知错误 2 参数错误 7 空间不足 12 禁止的用户操作 13 无效的 token 结束 the end" }, { "lang": "zh", "slug": "private-package-overview", "title": "私有套餐概览", "description": "介绍巴别鸟私有化套餐的适用场景、组成、模块和报价口径。", "category": "私有套餐", "top_category": "私有套餐", "keywords": [ "私有套餐", "私有化", "授权", "模块" ], "url": "zh/private-package-overview.html", "source": "content/zh/private-package-overview.md", "summary": "私有套餐概览 巴别鸟私有化套餐面向需要把企业网盘、权限、安全、AI、在线编辑和业务系统集成部署在自有服务器、私有云或受控云环境中的客户。套餐内容通常由基础私有化授权、部署实施、标准功能模块、可选增值模块、第三方服务接入、维护服务和定制开发服务组成。 适用场景 企业要求文件数据存储在自有机房、政企云、专属云或隔离网络中。 需要接入企业微信、钉钉、飞书、OA、ERP、PDM、AD/SSO 或统一身份认证系统。 需要对象存储、数据摆渡、部门安全策略、审计、水印、IP 策略、Mac 绑定等更强管控。 需要在线 Office、CAD 预览、AI 知识库、文控项目、自动化任务或电子签章等模块化能力。 需要白牌 OEM、流程定制、API 对接或围绕企业业务进行二次开发。 套餐组成 组成 说明 私有化授权 巴别鸟企业私有云版本的产品授权，部署在客户准备或客户管理的服务器环境中 标准功能 企业网盘、部门/项目文件、权限、分享、版本、预览、同步、映射盘、日志、控制台等 部署实施 由巴别鸟团队远程或现场部署、签发证书、调试服务并协助初始化 可选模块 智巢 AI、文控项目、在线 Office、数据摆渡、第三方平台接入、短信、签章、CAD/OCR 等 存储方案 本地磁盘、NFS、S3、MinIO 对象存储或第三方对象存储 维护服务 培训、答疑、故障处理、版本升级、配置支持和运维配合 定制开发 API 对接、流程定制、界面重塑、业务系统集成和白牌服务 价格与报价口径 实际报价会受到用户数量、授权模块、部署方式、存储规模、是否需要现场服务、是否需要定制开发和维护服务周期影响，应以正式商务报价和合同为准。", "headings": [ { "level": 1, "title": "私有套餐概览", "id": "section" }, { "level": 2, "title": "适用场景", "id": "section-2" }, { "level": 2, "title": "套餐组成", "id": "section-3" }, { "level": 2, "title": "价格与报价口径", "id": "section-4" } ], "images": [], "text": "私有套餐概览 巴别鸟私有化套餐面向需要把企业网盘、权限、安全、AI、在线编辑和业务系统集成部署在自有服务器、私有云或受控云环境中的客户。套餐内容通常由基础私有化授权、部署实施、标准功能模块、可选增值模块、第三方服务接入、维护服务和定制开发服务组成。 适用场景 企业要求文件数据存储在自有机房、政企云、专属云或隔离网络中。 需要接入企业微信、钉钉、飞书、OA、ERP、PDM、AD/SSO 或统一身份认证系统。 需要对象存储、数据摆渡、部门安全策略、审计、水印、IP 策略、Mac 绑定等更强管控。 需要在线 Office、CAD 预览、AI 知识库、文控项目、自动化任务或电子签章等模块化能力。 需要白牌 OEM、流程定制、API 对接或围绕企业业务进行二次开发。 套餐组成 组成 说明 私有化授权 巴别鸟企业私有云版本的产品授权，部署在客户准备或客户管理的服务器环境中 标准功能 企业网盘、部门/项目文件、权限、分享、版本、预览、同步、映射盘、日志、控制台等 部署实施 由巴别鸟团队远程或现场部署、签发证书、调试服务并协助初始化 可选模块 智巢 AI、文控项目、在线 Office、数据摆渡、第三方平台接入、短信、签章、CAD/OCR 等 存储方案 本地磁盘、NFS、S3、MinIO 对象存储或第三方对象存储 维护服务 培训、答疑、故障处理、版本升级、配置支持和运维配合 定制开发 API 对接、流程定制、界面重塑、业务系统集成和白牌服务 价格与报价口径 实际报价会受到用户数量、授权模块、部署方式、存储规模、是否需要现场服务、是否需要定制开发和维护服务周期影响，应以正式商务报价和合同为准。" }, { "lang": "zh", "slug": "private-package-standard", "title": "标准私有化套餐", "description": "说明标准私有化套餐包含的基础产品能力和默认交付范围。", "category": "私有套餐", "top_category": "私有套餐", "keywords": [ "标准私有化", "企业网盘", "私有部署" ], "url": "zh/private-package-standard.html", "source": "content/zh/private-package-standard.md", "summary": "标准私有化套餐 标准私有化套餐继承公有云巴别鸟的核心能力，并在客户自有环境中运行。它适合需要统一管理企业文件、保护数据安全、接入内部系统并保持长期可维护的组织。 标准能力 企业文件、个人文件、部门文件夹、项目文件夹和素材库。 文件上传、下载、分块传输、断点续传、增量上传下载和去重存储。 文件预览、BabelViewer、批注、评论、版本管理、版本回退和版本对比。 部门角色、项目权限、文件访问控制、自定义文件权限、分享权限和日志审计。 Windows、macOS、麒麟客户端，包含同步、传输管理和虚拟映射盘能力。 企业控制台，管理组织结构、成员、角色、标签、水印、访问日志、统计分析等。 私有化交付说明 私有化部署 巴别鸟公有云网盘系统需要同时为包含免费用户在内的60万用户提供持续不间断服务、要挡住公网上的各种攻击、要不断提高系统效率以降低高昂的公有云服务器成本。多达10年的公有云不间断服务经验使巴别鸟系统久经考验。巴别鸟私有云系统是在巴别鸟公有云系统基础上发展起来的，继承了公有云巴别鸟的所有功能及特性，并与公有云巴别鸟保持同步更新，提供给您其他私有网盘无法比拟的高稳定性及高可用性。 部署方案 针对不同企业不同的IT系统建设需求，巴别鸟私有化系统支持多种灵活的部署方式及部署要求。无论是单服务器、多服务器、集群、超融合系统、分布式系统、第三方云平台甚至Docker方式的部署我们都支持。我们的部署团队可以根据你的需求和你共同制定部署方案。同时因为私有云只服务于单一企业的特性，我们可提供远超公有云系统的可选自定义设置，从界面操作到流程到权限都可以根据你的需求调整。 服务器建议配置及性能需求", "headings": [ { "level": 1, "title": "标准私有化套餐", "id": "section" }, { "level": 2, "title": "标准能力", "id": "section-2" }, { "level": 2, "title": "私有化交付说明", "id": "section-3" }, { "level": 2, "title": "私有化部署", "id": "section-4" } ], "images": [], "text": "标准私有化套餐 标准私有化套餐继承公有云巴别鸟的核心能力，并在客户自有环境中运行。它适合需要统一管理企业文件、保护数据安全、接入内部系统并保持长期可维护的组织。 标准能力 企业文件、个人文件、部门文件夹、项目文件夹和素材库。 文件上传、下载、分块传输、断点续传、增量上传下载和去重存储。 文件预览、BabelViewer、批注、评论、版本管理、版本回退和版本对比。 部门角色、项目权限、文件访问控制、自定义文件权限、分享权限和日志审计。 Windows、macOS、麒麟客户端，包含同步、传输管理和虚拟映射盘能力。 企业控制台，管理组织结构、成员、角色、标签、水印、访问日志、统计分析等。 私有化交付说明 私有化部署 巴别鸟公有云网盘系统需要同时为包含免费用户在内的60万用户提供持续不间断服务、要挡住公网上的各种攻击、要不断提高系统效率以降低高昂的公有云服务器成本。多达10年的公有云不间断服务经验使巴别鸟系统久经考验。巴别鸟私有云系统是在巴别鸟公有云系统基础上发展起来的，继承了公有云巴别鸟的所有功能及特性，并与公有云巴别鸟保持同步更新，提供给您其他私有网盘无法比拟的高稳定性及高可用性。 部署方案 针对不同企业不同的IT系统建设需求，巴别鸟私有化系统支持多种灵活的部署方式及部署要求。无论是单服务器、多服务器、集群、超融合系统、分布式系统、第三方云平台甚至Docker方式的部署我们都支持。我们的部署团队可以根据你的需求和你共同制定部署方案。同时因为私有云只服务于单一企业的特性，我们可提供远超公有云系统的可选自定义设置，从界面操作到流程到权限都可以根据你的需求调整。 服务器建议配置及性能需求 服务器类型及作用： 巴别鸟网盘所需硬件系统由业务服务器及存储服务器两部份构成，其中业务服务器可以分为4种类型，这4种类型的服务可以根据需求部署在一台物理机或虚拟机中，也可以分散部署在四台甚至更多的服务器中。所以，部署巴别鸟系统最小单位是两台物理服务器或两台虚拟机（一台业务一台存储） 服务名 用途 操作系统 主业务服务器 web服务、负载均衡、主业务功能实现 Linux 数据库服务器 数据库服务 Linux 搜索服务器 提供文件全文搜索、高级搜索功能 Linux 转码服务器 为需要转码预览的文件进行转码及增加水印 windows 2012、Linux 存储服务器 提供文件存储 Linux 极端情况下，如果使用服务器挂载的硬盘作为存储空间，巴别鸟也支持把全部服务及存储都部署在一台物理机或虚拟机中（一体机模式），但考虑到性能及灾备或是日后的升级扩容问题，不推荐这样的部署方式。 我们推荐的最佳部署方式是4台服务器（虚拟机）的小集群部署。主业务服务及数据库服务放在在一台服务器，搜索服务器和转码服务器独立，然后外加一台存储服务器。 如果存储的空间需求小于10TB，也可以不需要存储服务器。可以直接挂载硬盘或NFS磁盘进行存储。 巴别鸟也支持接入第三方存储，理论上，只要第三方存储系统支持NFS或S3协议都可以接入到巴别鸟作为存储服务。绝大多数存储系统都支持这两种协议。 各个服务器之间要保证互访的畅通。如内网有较高安全要求可以参阅 9.1.2需要开放的端口 最低性能配置： 巴别鸟的最低性能配置可以支持100左右用户正常使用，管理10TB以下的数据。 cpu 内存 系统盘 存储盘 网络 操作系统 8核CPU （参考基准E5 2609） 32G ECC 内存 500G 10TB以下 千兆 Linux 推荐性能配置实例： 巴别鸟的推荐性能配置可以支持1000 2000用户正常使用，管理最高可达1PB的文档。 巴别鸟支持多种部署方式，该实例是标准部署方式。使用虚拟机部署业务服务器对接独立的单台或多台对象存储服务器。业务服务器和存储服务器分开管理。 业务服务器： 建议业务服务器使用虚拟机进行部署 编号 服务器类型 配置要求 操作系统 服务器用途 1 虚拟机 8核CPU 64G内存 500G SSD系统盘 CentOS8或openeuler22 主业务服务器/数据库 2 虚拟机 8核CPU 32G内存 500G SSD系统盘 CentOS8或openeuler22 搜索服务器 3 虚拟机 8核CPU 16G内存 200G SSD系统盘 windows 2012 R2 转码服务器 8核cpu的性能应该接近志强4410 巴别鸟企业网盘采用Docker部署，理论上只要是Linux操作系统即可进行部署，推荐使用CentOS或open Euler。 如果没有现成的虚拟机资源，需要采购新的业务服务器，业务服务器硬件配置需求如下： 编号 服务器类型 配置要求 操作系统 服务器用途 1 业务服务器 至强银牌4210 2 20核CPU 64G内存 2TB SSD硬盘 Linux 主业务服务器 业务服务器最好购买VM，使用虚拟化进行管理。 存储服务器（对象存储）： 巴别鸟支持在通用服务器上搭建对象存储系统，如预计存储空间用量小于100TB，推荐使用单台服务器搭建对象存储系统。单台对象存储可以用磁盘进行数据校验冗余，并且可以以每次增加一台存储服务器的方式进行横向扩容。（扩容操作可以做到不停服） 对象存储服务器建议使用独立的物理机，建议配置如下： 服务器类型 配置要求 操作系统 服务器用途 备注 存储服务器 至强银牌4210 2 20核CPU 64G内存 480G SSD硬盘 +存储所需容量硬盘 硬盘如果考虑性价比，建议使用 8T 10（2U） 或 8T 24（4U）。如果考虑存储密度及未来扩容投入可使用12T硬盘。 Linux 对象存储服务器 未来扩展建议增加相同磁盘容量的服务器。 如所需存储空间大于300TB，需要多台服务器搭建分布式对象那个存储系统。 巴别鸟也支持为客户搭建分布式对象存储系统。要了解分布式对象存储可查阅“自建对象存储”章节。 需要开放的端口 为了服务器系统的安全，我们需要只开放特定的端口，下面是需要开放的端口： 对外开放的端口（外网访问需要使用的端口）： 端口号 端口用途 协议 开放的主机 80 网盘主业务 web外部访问端口，不加密 http 主业务服务器 443 网盘主业务 web外部访问端口，加密 https 主业务服务器 3060 网盘主业务node 外部访问端口，不加密 TCP 主业务服务器 3080 网盘主业务node 外部访问端口，加密 TCP 主业务服务器 服务器间需要开放的端口（服务器内部通讯需要开放的端口）： 一般实际部署时，只会限制外网端口（对外），服务器间内部端口不会限制。但一些跨网络跨机房部署的用户也会需要限定内部端口。 主机 端口号 端口用途 协议 目标网段 业务服务器 6379 redis访问端口，供windows转码与搜索服务器使用 TCP 转码服务器与搜索服务器 业务服务器 8080 供windows转码服务器，访问网盘业务服务器使用 TCP 转码服务器与搜索服务器 业务服务器 3306 数据库端口，供搜索服务器访问数据库使用 TCP 转码服务器与搜索服务器 业务服务器 9000 docker 集群部署，内部可视化界面端口 TCP 转码服务器与搜索服务器 业务服务器 111 portmap 端口 TCP+UDP 转码服务器与搜索服务器 业务服务器 2049 TCP+UDP TCP+UDP 转码服务器与搜索服务器 业务服务器 35000 mountd 端口 TCP+UDP 转码服务器与搜索服务器 业务服务器 2376 docker REST API端口，进行TLS加密 TCP 本机 业务服务器 2377 TCP端口 用来 docker 集群管理相关通信 TCP+UDP 本机 业务服务器 7946 TCP与UDP端口，用来docker swarm 各节点间的通信 TCP+UDP 本机 业务服务器 4789 docker overlay 网络默认端口 TCP+UDP 本机 搜索服务器 9200 elastic 端口，供主业务服务器调用使用 TCP 业务服务器 搜索服务器 5601 kibana端口，内部可视化elastic界面访问端口 TCP 业务服务器 搜索服务器 9998 tika端口，提取文档文本服务器端口 TCP 业务服务器 搜索服务器 9000 docker 集群部署，内部可视化界面端口 TCP 转码服务器与搜索服务器 搜索服务器 2376 docker REST API端口，进行TLS加密 TCP 本机 搜索服务器 2377 TCP端口 用来 docker 集群管理相关通信 TCP 本机 搜索服务器 7946 TCP与UDP端口，用来docker swarm 各节点间的通信 TCP+UDP 本机 搜索服务器 4789 docker overlay 网络默认端口 TCP+UDP 本机 转码服务器 转码服务器 可以访问业务服务器 可以访问业务服务器 可以访问业务服务器 部署时需要开放的端口： 端口号 端口用途 开放的服务器 目标IP地址 22 ssh端口号，ssh 访问使用 所有服务器 部署用跳板机 443 获取授权 所有服务器 47.96.234.200 443 获取安装源 所有服务器 120.27.245.68 443 Docker安装源 所有服务器 13.35.121.100 POC部署 POC部署适用于用户在选型前在生产环境进行POC测试而进行的部署方式。 POC部署需求：" }, { "lang": "zh", "slug": "private-package-modules", "title": "可选模块与增值能力", "description": "列出智巢 AI、在线编辑、数据摆渡、文控、第三方接入、CAD/OCR/签章等可选模块。", "category": "私有套餐", "top_category": "私有套餐", "keywords": [ "可选模块", "智巢AI", "数据摆渡", "文控项目" ], "url": "zh/private-package-modules.html", "source": "content/zh/private-package-modules.md", "summary": "可选模块与增值能力 私有化版本可按企业需求启用或接入不同模块。实际是否包含在合同中，应以报价单、授权清单和实施方案为准。 常见可选模块 模块 说明 智巢 AI AI 搜索、AI 搜图、文档助理、知识库机器人、自定义智能体和 AI 客服 在线 Office 默认 OnlyOffice，也可按需接入 Office 365、WPS Online、永中 Office 轻文档/文本/脑图/流程图 轻文档、Markdown/代码文本、KM 思维导图、draw.io 流程图 数据摆渡 密区与非密区之间安全、可审计、可审批的文件传送 文控项目 工程设计行业 DCC、TRANSMITTAL、发送单、接收方和发送记录管理 自动化任务 自动清理、自动重命名、自动转 PDF、自动整理、签章、批量建文件夹 第三方平台 企业微信、钉钉、飞书、OA、ERP、PDM、ADFS、SSO 第三方能力 高级 CAD 预览、CAD 在线编辑、OCR、图像识别、电子签章、DLP 第三方服务接入条件 接入第三方服务 作为一个围绕企业文件的办公平台，私有化的巴别鸟企业网盘通过接入第三方API的方式，可以轻松集成各种第三方服务到巴别鸟中，以满足不同的需求这些服务包括但不限于：电子签名、高级CAD预览、office、文字识别、图像识别....等第三方服务来解决您遇到的需求问题。 接入第三方服务的条件 理论上支持BS架构的第三方应用或者服务模块都可以接入。 第三方服务必须提供开放的API，以便巴别鸟企业网盘可以与之集成 如果是互联网服务，需要服务器能访问外网。 需要企业自行或委托我们购买接入的第三方服务的授权 推荐的可接入服务 ", "headings": [ { "level": 1, "title": "可选模块与增值能力", "id": "section" }, { "level": 2, "title": "常见可选模块", "id": "section-2" }, { "level": 2, "title": "第三方服务接入条件", "id": "section-3" } ], "images": [], "text": "可选模块与增值能力 私有化版本可按企业需求启用或接入不同模块。实际是否包含在合同中，应以报价单、授权清单和实施方案为准。 常见可选模块 模块 说明 智巢 AI AI 搜索、AI 搜图、文档助理、知识库机器人、自定义智能体和 AI 客服 在线 Office 默认 OnlyOffice，也可按需接入 Office 365、WPS Online、永中 Office 轻文档/文本/脑图/流程图 轻文档、Markdown/代码文本、KM 思维导图、draw.io 流程图 数据摆渡 密区与非密区之间安全、可审计、可审批的文件传送 文控项目 工程设计行业 DCC、TRANSMITTAL、发送单、接收方和发送记录管理 自动化任务 自动清理、自动重命名、自动转 PDF、自动整理、签章、批量建文件夹 第三方平台 企业微信、钉钉、飞书、OA、ERP、PDM、ADFS、SSO 第三方能力 高级 CAD 预览、CAD 在线编辑、OCR、图像识别、电子签章、DLP 第三方服务接入条件 接入第三方服务 作为一个围绕企业文件的办公平台，私有化的巴别鸟企业网盘通过接入第三方API的方式，可以轻松集成各种第三方服务到巴别鸟中，以满足不同的需求这些服务包括但不限于：电子签名、高级CAD预览、office、文字识别、图像识别....等第三方服务来解决您遇到的需求问题。 接入第三方服务的条件 理论上支持BS架构的第三方应用或者服务模块都可以接入。 第三方服务必须提供开放的API，以便巴别鸟企业网盘可以与之集成 如果是互联网服务，需要服务器能访问外网。 需要企业自行或委托我们购买接入的第三方服务的授权 推荐的可接入服务 文件防泄密系统： ipguard 在线office编辑：onlyoffice（自带）、office365、WPS Online、永中office 高级CAD预览：浩辰云图、梦想CAD CAD在线编辑：梦想CAD 在线签章：上上签 文字识别图像识别：百度千帆（智能云） AI相关：智巢AI（自有）、ChatGPT、智谱AI" }, { "lang": "zh", "slug": "private-package-service", "title": "服务与维护", "description": "说明私有化部署、维护、培训、升级和售后服务范围。", "category": "私有套餐", "top_category": "私有套餐", "keywords": [ "维护服务", "售后", "私有化" ], "url": "zh/private-package-service.html", "source": "content/zh/private-package-service.md", "summary": "服务与维护 私有化系统不仅包含软件授权，也包含部署实施、初始化、培训、维护、升级和故障响应服务。服务范围应结合合同、服务订单和维护期约定确认。 私有云服务条款摘录 巴别鸟企业私有化服务 上海画擎信息科技有限公司仅提供巴别鸟部署及巴别鸟私有化授权服务。部署所需的硬件及环境由甲方准备及维护。 部署企业私有云版本。甲方购买巴别鸟企业私有云版本后，由上海画擎信息科技根据甲方签订合同时所选的项目（详见协议附件 服务订单）进行部署及相关调试。 企业私有云版服务时限。企业私有云版本的账号授权时限为终生授权，客服支持及升级服务按年为单位。购买后第一年免维护费用。 企业私有云版服务升级。上海画擎信息科技有限公司升级巴别鸟企业私有云版服务时，会第一时间通知甲方，由甲方决定是否升级，如甲方同意升级即进行远程升级服务，无需支付其他费用。 企业私有云版维护费。巴别鸟企业私有云版本为终生授权，但如果需要上海画擎信息科技有限公司提供相应的培训、答疑、及系统bug修正、系统升级服务则需支付维护费用。购买企业私有云版本后的第一年免维护费，第二年开始甲方需要按合同约定支付相应的维护费用。如逾期甲方没有支付维护费用，将视为甲方放弃本服务条款的所有服务。 巴别鸟订单合同。甲方在购买巴别鸟企业私有云版服务后，可与上海画擎信息有限公司签订[巴别鸟私有云软件使用许可协议]。[巴别鸟私有云软件使用许可协议]是上海画擎信息有限公司与甲方之间关于巴别鸟服务与费用的书面协定。 售后与维护 巴别鸟提供的售后服务 巴别鸟采用一对一专人服务模式，有专门的客户经理负责为客户提供服务。 维护单位名称：上海画擎信息科技有限公司 软件维护期为一", "headings": [ { "level": 1, "title": "服务与维护", "id": "section" }, { "level": 2, "title": "私有云服务条款摘录", "id": "section-2" }, { "level": 2, "title": "售后与维护", "id": "section-3" } ], "images": [], "text": "服务与维护 私有化系统不仅包含软件授权，也包含部署实施、初始化、培训、维护、升级和故障响应服务。服务范围应结合合同、服务订单和维护期约定确认。 私有云服务条款摘录 巴别鸟企业私有化服务 上海画擎信息科技有限公司仅提供巴别鸟部署及巴别鸟私有化授权服务。部署所需的硬件及环境由甲方准备及维护。 部署企业私有云版本。甲方购买巴别鸟企业私有云版本后，由上海画擎信息科技根据甲方签订合同时所选的项目（详见协议附件 服务订单）进行部署及相关调试。 企业私有云版服务时限。企业私有云版本的账号授权时限为终生授权，客服支持及升级服务按年为单位。购买后第一年免维护费用。 企业私有云版服务升级。上海画擎信息科技有限公司升级巴别鸟企业私有云版服务时，会第一时间通知甲方，由甲方决定是否升级，如甲方同意升级即进行远程升级服务，无需支付其他费用。 企业私有云版维护费。巴别鸟企业私有云版本为终生授权，但如果需要上海画擎信息科技有限公司提供相应的培训、答疑、及系统bug修正、系统升级服务则需支付维护费用。购买企业私有云版本后的第一年免维护费，第二年开始甲方需要按合同约定支付相应的维护费用。如逾期甲方没有支付维护费用，将视为甲方放弃本服务条款的所有服务。 巴别鸟订单合同。甲方在购买巴别鸟企业私有云版服务后，可与上海画擎信息有限公司签订[巴别鸟私有云软件使用许可协议]。[巴别鸟私有云软件使用许可协议]是上海画擎信息有限公司与甲方之间关于巴别鸟服务与费用的书面协定。 售后与维护 巴别鸟提供的售后服务 巴别鸟采用一对一专人服务模式，有专门的客户经理负责为客户提供服务。 维护单位名称：上海画擎信息科技有限公司 软件维护期为一年，第二年后客户需缴纳维护费，进入下一轮软件维护期，如客户维护期满后不缴纳服务费，客户可以继续使用系统，但我司不再提供维护服务，直到补齐年服务费用后，服务继续。 维护期内上海画擎负责提供合同范围内软件版本的程序代码及系统配置信息的维护、支持，不包含因业务改变等因素所引起的新增功能开发。如中日友好医院需要新增功能及因业务流程变更带来的客户化开发服务，则由双方协商确定实施方案。 免费服务内容和范围 巴别鸟对所有付费客户提供产品使用周期中的终身免费质保服务，包括： 5 24小时的电话技术支持服务 7 24小时的紧急灾备处理服务 免费在线培训，系统使用指导 BUG第一时间反馈，快速处理 软件更新及升级服务 针对用户数量超过1000人的企业用户，巴别鸟提供了产品使用周期中的终身免费VIP服务，包括： 付费客户的所有免费服务 系统搭建及需求对应解决方案咨询服务 代客户初始化系统及完成配置 免费数据迁移服务（小于10TB的数据） 每年免费上门培训1次（用户数超过10000每年有三次免费上门培训机会） 专属大客户经理责任制服务 针对私有化用户，在用户正常缴纳年服务费的前提下，享受如下免费服务： 付费客户的所有免费服务 免费系统升级及更新服务，纯内网用户（内网无法连接到互联网）每年有1次免费上门升级及更新服务 代客户初始化系统及完成配置 服务器性能优化及排障 每年免费上门培训1次，无限次远程培训 针对基于巴别鸟系统的二次开发及功能定制用户，享受如下免费服务： 付费客户的所有免费服务 二次开发部分的功能质保，Bug修正 接口及功能联调服务 二次开发部分代码及接口的注释及指导服务，方便用户再开发 完工验收后，在我方成本可承受范围内的微调及功能修正（非Bug） 收费服务 在现有系统上的再开发工作，按需求评估开发工时及难度系数，按工时结算。 产品设计服务。根据客户新需求帮助客户进行产品架构、功能及交互的设计，并提供技术咨询。 有偿上门培训及调试服务。免费额度用完或不符合免费上门服务条件的用户可以付费申请。费用为 2000元1人1天 及报销到达用户处所的交通费用（高铁及当地出租车） 提供的服务项目包括如下： 序号 服务项目 服务内容 1 首访服务 由服务人员主动开展首次访问服务 2 回访服务 由服务人员主动开展回访的服务 3 软件常规运行维护服务 所购买软件的程序代码维护，如修补软件缺陷、安装调试软件补丁 4 系统升级技术咨询 当系统升级时提供的技术咨询服务 5 软件升级通知 当该版本软件升级时，及时通知客户 服务方式包括： 热线支持：通过400热线电话向客户提供技术问题解答； E MAIL支持：通过E MAIL解答客户问题； 远程维护：通过远程方式对客户环境下的巴别鸟软件进行调试。客户需提供远程维护所需的环境，否则，由客户承担因此而引起的售后响应时间滞后的责任。 现场服务：如属远程维护所不能解决的问题，我司会承担现场服务。属于应用软件自身问题带来的现场服务，属于免费维护范围。 故障处理流程 当客户使用中出现问题： 立即拨打专职客户经理电话（或微信联系），可以解决的立即解决； 不能立即解决的，立即联系技术人员对接，由技术人员远程协助客户解决； 仍然没有解决，反馈给客户经理，由客户经理安排技术人员上门服务。 其他 如本服务条款中的任何条款无论因何种原因完全或部分无效或不具有执行力，本服务条款的其余条款仍应有效且具有约束力，并且努力使该规定反映之意向具备效力。 本服务条款构成甲方与上海画擎信息科技有限公司之全部协议，规范您对本服务之使用，并取代您先前与上海画擎信息科技有限公司达成的全部协议。但在甲方使用相关服务、或使用第三方提供的内容或软件时，亦应遵从所适用之附加条款及权利。 上海画擎信息科技有限公司保留本服务条款之所有解释权。 甲方（盖章）： 乙方（盖章）： 甲方代表（签字）： 乙方代表（签字）： 日 期： 日 期：" }, { "lang": "zh", "slug": "deployment-overview", "title": "私有化部署", "description": "介绍私有化部署方案、服务器角色、性能配置、对象存储、POC、实施流程和信创支持。", "category": "部署实施", "top_category": "部署指南", "keywords": [ "私有化部署", "对象存储", "POC", "信创" ], "url": "zh/deployment-overview.html", "source": "content/zh/deployment-overview.md", "summary": "私有化部署 私有化部署 巴别鸟公有云网盘系统需要同时为包含免费用户在内的60万用户提供持续不间断服务、要挡住公网上的各种攻击、要不断提高系统效率以降低高昂的公有云服务器成本。多达10年的公有云不间断服务经验使巴别鸟系统久经考验。巴别鸟私有云系统是在巴别鸟公有云系统基础上发展起来的，继承了公有云巴别鸟的所有功能及特性，并与公有云巴别鸟保持同步更新，提供给您其他私有网盘无法比拟的高稳定性及高可用性。 部署方案 针对不同企业不同的IT系统建设需求，巴别鸟私有化系统支持多种灵活的部署方式及部署要求。无论是单服务器、多服务器、集群、超融合系统、分布式系统、第三方云平台甚至Docker方式的部署我们都支持。我们的部署团队可以根据你的需求和你共同制定部署方案。同时因为私有云只服务于单一企业的特性，我们可提供远超公有云系统的可选自定义设置，从界面操作到流程到权限都可以根据你的需求调整。 服务器建议配置及性能需求 服务器类型及作用： 巴别鸟网盘所需硬件系统由业务服务器及存储服务器两部份构成，其中业务服务器可以分为4种类型，这4种类型的服务可以根据需求部署在一台物理机或虚拟机中，也可以分散部署在四台甚至更多的服务器中。所以，部署巴别鸟系统最小单位是两台物理服务器或两台虚拟机（一台业务一台存储） 服务名 用途 操作系统 主业务服务器 web服务、负载均衡、主业务功能实现 Linux 数据库服务器 数据库服务 Linux 搜索服务器 提供文件全文搜索、高级搜索功能 Linux 转码服务器 为需要转码预览的文件进行转码及增加水印 windows 2012、Linux 存储服务器 提供文件存储 Linux", "headings": [ { "level": 1, "title": "私有化部署", "id": "section" }, { "level": 2, "title": "私有化部署", "id": "section-2" } ], "images": [], "text": "私有化部署 私有化部署 巴别鸟公有云网盘系统需要同时为包含免费用户在内的60万用户提供持续不间断服务、要挡住公网上的各种攻击、要不断提高系统效率以降低高昂的公有云服务器成本。多达10年的公有云不间断服务经验使巴别鸟系统久经考验。巴别鸟私有云系统是在巴别鸟公有云系统基础上发展起来的，继承了公有云巴别鸟的所有功能及特性，并与公有云巴别鸟保持同步更新，提供给您其他私有网盘无法比拟的高稳定性及高可用性。 部署方案 针对不同企业不同的IT系统建设需求，巴别鸟私有化系统支持多种灵活的部署方式及部署要求。无论是单服务器、多服务器、集群、超融合系统、分布式系统、第三方云平台甚至Docker方式的部署我们都支持。我们的部署团队可以根据你的需求和你共同制定部署方案。同时因为私有云只服务于单一企业的特性，我们可提供远超公有云系统的可选自定义设置，从界面操作到流程到权限都可以根据你的需求调整。 服务器建议配置及性能需求 服务器类型及作用： 巴别鸟网盘所需硬件系统由业务服务器及存储服务器两部份构成，其中业务服务器可以分为4种类型，这4种类型的服务可以根据需求部署在一台物理机或虚拟机中，也可以分散部署在四台甚至更多的服务器中。所以，部署巴别鸟系统最小单位是两台物理服务器或两台虚拟机（一台业务一台存储） 服务名 用途 操作系统 主业务服务器 web服务、负载均衡、主业务功能实现 Linux 数据库服务器 数据库服务 Linux 搜索服务器 提供文件全文搜索、高级搜索功能 Linux 转码服务器 为需要转码预览的文件进行转码及增加水印 windows 2012、Linux 存储服务器 提供文件存储 Linux 极端情况下，如果使用服务器挂载的硬盘作为存储空间，巴别鸟也支持把全部服务及存储都部署在一台物理机或虚拟机中（一体机模式），但考虑到性能及灾备或是日后的升级扩容问题，不推荐这样的部署方式。 我们推荐的最佳部署方式是4台服务器（虚拟机）的小集群部署。主业务服务及数据库服务放在在一台服务器，搜索服务器和转码服务器独立，然后外加一台存储服务器。 如果存储的空间需求小于10TB，也可以不需要存储服务器。可以直接挂载硬盘或NFS磁盘进行存储。 巴别鸟也支持接入第三方存储，理论上，只要第三方存储系统支持NFS或S3协议都可以接入到巴别鸟作为存储服务。绝大多数存储系统都支持这两种协议。 各个服务器之间要保证互访的畅通。如内网有较高安全要求可以参阅 9.1.2需要开放的端口 最低性能配置： 巴别鸟的最低性能配置可以支持100左右用户正常使用，管理10TB以下的数据。 cpu 内存 系统盘 存储盘 网络 操作系统 8核CPU （参考基准E5 2609） 32G ECC 内存 500G 10TB以下 千兆 Linux 推荐性能配置实例： 巴别鸟的推荐性能配置可以支持1000 2000用户正常使用，管理最高可达1PB的文档。 巴别鸟支持多种部署方式，该实例是标准部署方式。使用虚拟机部署业务服务器对接独立的单台或多台对象存储服务器。业务服务器和存储服务器分开管理。 业务服务器： 建议业务服务器使用虚拟机进行部署 编号 服务器类型 配置要求 操作系统 服务器用途 1 虚拟机 8核CPU 64G内存 500G SSD系统盘 CentOS8或openeuler22 主业务服务器/数据库 2 虚拟机 8核CPU 32G内存 500G SSD系统盘 CentOS8或openeuler22 搜索服务器 3 虚拟机 8核CPU 16G内存 200G SSD系统盘 windows 2012 R2 转码服务器 8核cpu的性能应该接近志强4410 巴别鸟企业网盘采用Docker部署，理论上只要是Linux操作系统即可进行部署，推荐使用CentOS或open Euler。 如果没有现成的虚拟机资源，需要采购新的业务服务器，业务服务器硬件配置需求如下： 编号 服务器类型 配置要求 操作系统 服务器用途 1 业务服务器 至强银牌4210 2 20核CPU 64G内存 2TB SSD硬盘 Linux 主业务服务器 业务服务器最好购买VM，使用虚拟化进行管理。 存储服务器（对象存储）： 巴别鸟支持在通用服务器上搭建对象存储系统，如预计存储空间用量小于100TB，推荐使用单台服务器搭建对象存储系统。单台对象存储可以用磁盘进行数据校验冗余，并且可以以每次增加一台存储服务器的方式进行横向扩容。（扩容操作可以做到不停服） 对象存储服务器建议使用独立的物理机，建议配置如下： 服务器类型 配置要求 操作系统 服务器用途 备注 存储服务器 至强银牌4210 2 20核CPU 64G内存 480G SSD硬盘 +存储所需容量硬盘 硬盘如果考虑性价比，建议使用 8T 10（2U） 或 8T 24（4U）。如果考虑存储密度及未来扩容投入可使用12T硬盘。 Linux 对象存储服务器 未来扩展建议增加相同磁盘容量的服务器。 如所需存储空间大于300TB，需要多台服务器搭建分布式对象那个存储系统。 巴别鸟也支持为客户搭建分布式对象存储系统。要了解分布式对象存储可查阅“自建对象存储”章节。 需要开放的端口 为了服务器系统的安全，我们需要只开放特定的端口，下面是需要开放的端口： 对外开放的端口（外网访问需要使用的端口）： 端口号 端口用途 协议 开放的主机 80 网盘主业务 web外部访问端口，不加密 http 主业务服务器 443 网盘主业务 web外部访问端口，加密 https 主业务服务器 3060 网盘主业务node 外部访问端口，不加密 TCP 主业务服务器 3080 网盘主业务node 外部访问端口，加密 TCP 主业务服务器 服务器间需要开放的端口（服务器内部通讯需要开放的端口）： 一般实际部署时，只会限制外网端口（对外），服务器间内部端口不会限制。但一些跨网络跨机房部署的用户也会需要限定内部端口。 主机 端口号 端口用途 协议 目标网段 业务服务器 6379 redis访问端口，供windows转码与搜索服务器使用 TCP 转码服务器与搜索服务器 业务服务器 8080 供windows转码服务器，访问网盘业务服务器使用 TCP 转码服务器与搜索服务器 业务服务器 3306 数据库端口，供搜索服务器访问数据库使用 TCP 转码服务器与搜索服务器 业务服务器 9000 docker 集群部署，内部可视化界面端口 TCP 转码服务器与搜索服务器 业务服务器 111 portmap 端口 TCP+UDP 转码服务器与搜索服务器 业务服务器 2049 TCP+UDP TCP+UDP 转码服务器与搜索服务器 业务服务器 35000 mountd 端口 TCP+UDP 转码服务器与搜索服务器 业务服务器 2376 docker REST API端口，进行TLS加密 TCP 本机 业务服务器 2377 TCP端口 用来 docker 集群管理相关通信 TCP+UDP 本机 业务服务器 7946 TCP与UDP端口，用来docker swarm 各节点间的通信 TCP+UDP 本机 业务服务器 4789 docker overlay 网络默认端口 TCP+UDP 本机 搜索服务器 9200 elastic 端口，供主业务服务器调用使用 TCP 业务服务器 搜索服务器 5601 kibana端口，内部可视化elastic界面访问端口 TCP 业务服务器 搜索服务器 9998 tika端口，提取文档文本服务器端口 TCP 业务服务器 搜索服务器 9000 docker 集群部署，内部可视化界面端口 TCP 转码服务器与搜索服务器 搜索服务器 2376 docker REST API端口，进行TLS加密 TCP 本机 搜索服务器 2377 TCP端口 用来 docker 集群管理相关通信 TCP 本机 搜索服务器 7946 TCP与UDP端口，用来docker swarm 各节点间的通信 TCP+UDP 本机 搜索服务器 4789 docker overlay 网络默认端口 TCP+UDP 本机 转码服务器 转码服务器 可以访问业务服务器 可以访问业务服务器 可以访问业务服务器 部署时需要开放的端口： 端口号 端口用途 开放的服务器 目标IP地址 22 ssh端口号，ssh 访问使用 所有服务器 部署用跳板机 443 获取授权 所有服务器 47.96.234.200 443 获取安装源 所有服务器 120.27.245.68 443 Docker安装源 所有服务器 13.35.121.100 POC部署 POC部署适用于用户在选型前在生产环境进行POC测试而进行的部署方式。 POC部署需求： 基础POC部署，可测试软件功能，并发量，API接口，安全性，并进行生产环境试用。建议使用标准部署作为POC测试。 如需要进行对象存储、不同密区数据摆渡、高可用的POC，择需要增加相应的服务器和网段。 环境准备 推荐使用虚拟机进行部署： 巴别鸟私有化企业网盘采用Docker部署，理论上只要是Linux操作系统即可进行部署。推荐使用CentOS或open Euler。按要求准备好虚拟机后，联系我们预约时间后即可开始POC部署。 编号 服务器类型 配置要求 操作系统 服务器用途 备注 1 虚拟机 8核CPU 32G内存 500G系统盘 +500G存储盘 CentOS8或openeuler22及以上 主业务服务器 2 虚拟机 8核CPU 16G内存 500G系统盘 CentOS8或openeuler22及以上 搜索服务器 3 虚拟机 8核CPU 8G内存 200G系统盘 windows 2012 R2 转码服务器 CAD、office转码 win服务器是为了更好的office文件预览效果。巴别鸟也支持纯Linux环境部署 POC部署其他要求如下： 编号 项目 要求 备注 1 远程接入 可以远程接入服务器进行部署 可使用堡垒机或者跳板机或向日葵、VPN，能远程接入服务器部署即可。 2 外网连接 服务器需要能连接外网，拉取安装包，获取授权 需要连接的外网地址： software.babel.cc docker.babel.cc POC部署的使用授权时长为30天，授权账户数为100个。 初始化 部署完成后，巴别鸟团队会帮助用户进行系统初始化，根据用户需求初始化系统。包括不限于： 初始化管理员账号。（需要准备一个邮箱地址作为超级管理员账号） 初始化通知发件邮箱。（需要用户准备一个可提供密码和smtp服务器地址的邮箱作为系统默认发件箱） 初始化部门结构。（对接AD或导入部门） 初始化基础配置。logo、企业名、各类配置项。 培训 巴别鸟是一个专业的企业级应用，需要一定的培训工作帮助客户落地。POC后建议联系我方销售人员进行使用培训。 培训分为3类： 管理员培训（培训管理员的配置，使用，需求功能实现。耗时 1 2小时） 部门经理培训。（培训部门经理权限分配、成员增减等日常管理方式。耗时 1小时） 使用者培训。（使用成员的培训。耗时 1小时） 开启POC试用 培训完成后即可开始正式POC试用，使用中遇到的问题可以在相关群直接询问，巴别鸟团队会在2个小时内响应并解答。POC系统有效期为30天，如果需要延期，可联系我们销售人员。 巴别鸟常用部署方式介绍 巴别鸟可以按需支持多种部署方式，这里介绍下巴别鸟常用的部署方式。 在阿里云、腾讯云、华为云等公有平台部署： 巴别鸟支持在公有云服务商如：阿里云、腾讯云、百度云、华为云、天翼云的虚拟机（ECS）及对象存储（OSS、OBS...）上进行部署，在互联网上为用户提供服务。 和纯私有化部署的差别对比如下表： 优缺点/ 部署方式 图片服务 视频服务 公网访问 稳定性 硬件费用 采用阿里云存储和阿里云服务器 可以使用阿里云提供的图片服务 可以采用阿里云的视频转码服务，但是需要额外付费(价格贵) 可以在公网上访问，用户访问的快慢取决于用户自己的带宽和购买的阿里云的带宽。 系统很稳定，部署简单，便于管理。 需要支付阿里云的存储和服务器费用，可按月或按年付费等。服务器的维护即可由用户自己负责，也可以委托我们进行维护并负责升级。 存储和服务器均搭建在自己的内网 使用自建的图片处理服务(需要客户提供高性能的服务器) 使用自建的转码服务(需要客户提供高性能的服务器)，如果用户没有这方面的需求，可以忽略。 如果没有外网的出口，则用户不能在外网访问。但是在内网访问很快。 稳定，针对存储系统等的模块做了定制开发。数据的安全性由用户自己负责。 需要提供独立的主机和存储系统。服务器即可由用户选配购买，也可以由我们选配购买。服务器维护由用户负责，我们可以提供相应的软件升级服务。 公有云部署（1000+用户）要求： 编号 服务器类型 配置要求 操作系统 服务器用途 1 ECS 16核CPU 32G内存 500G SSD系统盘 CentOS8或openeuler22 主业务服务器 2 ECS 8核CPU 16G内存 500G SSD系统盘 CentOS8或openeuler22 数据库服务器 3 ECS 8核CPU 16G内存 500G SSD系统盘 CentOS8或openeuler22 搜索服务器 4 存储 对象存储系统。如阿里云OSS、华为云OBS 对象存储系统。如阿里云OSS、华为云OBS 对象存储系统。如阿里云OSS、华为云OBS 在公有云平台部署的主要优势是不需要专人维护、无需购买硬件就能做到顶级的灾备、在互联网上访问速度快、同时服务器和数据在自己手上管理。 在公有云平台部署的缺点主要为：数据没有本地化、每年需要支付服务器租用费用及相应的带宽存储成本。 自购服务器（2台物理机）进行部署： 如果想在自己机房部署纯私有的巴别鸟，并且没有富余的虚拟机资源，需要采购硬件部署，要求如下： 物理机服务器品牌建议：建议使用2台 DELL T440 服务器来完成系统搭建。并购买DELL3年金牌服务。 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：建议使用2台 DELL T440 服务器来完成系统搭建。并购买DELL3年金牌服务。 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：建议使用2台 DELL T440 服务器来完成系统搭建。并购买DELL3年金牌服务。 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：建议使用2台 DELL T440 服务器来完成系统搭建。并购买DELL3年金牌服务。 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：建议使用2台 DELL T440 服务器来完成系统搭建。并购买DELL3年金牌服务。 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：建议使用2台 DELL T440 服务器来完成系统搭建。并购买DELL3年金牌服务。 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 两台服务器方案 业务+存储 两台服务器方案 业务+存储 两台服务器方案 业务+存储 两台服务器方案 业务+存储 两台服务器方案 业务+存储 两台服务器方案 业务+存储 编号 服务器类型 配置要求 操作系统 服务器用途 备注 1 服务器 志强银牌4410 2 16核CPU、 64G内存、 2TB SSD硬盘 open Euler、Ubuntu、CentOS 主业务服务器 建议安装VM 2 存储 4410 2 16核CPU 、64G内存、 500G SSD硬盘+所需的硬盘空间（不需要raid或raid0） open Euler、Ubuntu、CentOS 存储服务器 硬盘容量按对存储空间需求进行配置 以上配置可支持1000+用户，150TB左右的存储空间 巴别鸟存储服务器使用对象存储系统，支持分布式部署（多台存储服务器）最低要求为一台物理服务器。支持使用硬盘组进行校验，支持2+1、3+1、4+1...等多种校验类型。详见 自建对象存储 章节 如需扩容存储空间，增加单台存储服务器即可。 也可增加一台存储服务器作为备份服务器，实时同步备份，主存储服务器出问题切换到备份服务器即可正常使用。 单服务器（1台物理机）部署： 一些没有机房但需要私有化部署巴别鸟，并且存储空间需求不大（10TB以下）的客户，可以选用单台服务器部署巴别鸟。只需购买一台符合要求的塔式服务器放置在公司也能满足使用巴别鸟的需求。 物理机服务器品牌建议：如果没有机房，建议使用塔式服务器进行部署。服务器存储硬盘建议raid1或者raid5+1 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：如果没有机房，建议使用塔式服务器进行部署。服务器存储硬盘建议raid1或者raid5+1 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：如果没有机房，建议使用塔式服务器进行部署。服务器存储硬盘建议raid1或者raid5+1 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：如果没有机房，建议使用塔式服务器进行部署。服务器存储硬盘建议raid1或者raid5+1 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：如果没有机房，建议使用塔式服务器进行部署。服务器存储硬盘建议raid1或者raid5+1 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：如果没有机房，建议使用塔式服务器进行部署。服务器存储硬盘建议raid1或者raid5+1 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 一台服务器（一体机方案） 一台服务器（一体机方案） 一台服务器（一体机方案） 一台服务器（一体机方案） 一台服务器（一体机方案） 一台服务器（一体机方案） 编号 服务器类型 配置要求 操作系统 服务器用途 备注 1 服务器 志强银牌4410 2 16核CPU 64G内存 2TB SSD硬盘 +需要存储容量的硬盘 2（未来也可增加硬盘） openEuler、Ubuntu、CentOS 8.5 及以上 一体机 建议安装VM，2个CPU授权。 单服务器部署整套巴别鸟系统不支持对象存储，采用只读硬盘或NFS的方式进行存储。建议使用raid1来提升系统可靠性。 可增加一台备份服务器用来进行数据同步备份。如主服务器出问题可以用备份服务器进行数据重建。 在现有虚拟机（超融合）系统上进行部署： 这是目前最常用的部署方式，在企业现有的服务器和硬件条件下进行部署，无需采购新的设备。 在客户现有的VM或超融合平台分配的虚拟机中完成部署，适合已经有一定IT建设及管理的用户。 采用小集群的方式部署，由虚拟机平台负责服务器的统一管理。 支持绝大多数虚拟化系统。 推荐采用4台虚拟机挂载存储空间的方式进行部署。 编号 服务器类型 配置要求 操作系统 服务器用途 1 虚拟机 8核CPU 32G内存 500G SSD系统盘 CentOS8或openeuler22 主业务服务器 2 虚拟机 8核CPU 16G内存 500G SSD系统盘 CentOS8或openeuler22 数据库服务器 3 虚拟机 8核CPU 16G内存 500G SSD系统盘 CentOS8或openeuler22 搜索服务器 4 虚拟机 8核CPU 16G内存 200G SSD系统盘 windows 2012 R2 转码服务器 5 存储 支持NFS或S3接口的存储系统或虚拟机挂载磁盘作为存储盘 支持NFS或S3接口的存储系统或虚拟机挂载磁盘作为存储盘 支持NFS或S3接口的存储系统或虚拟机挂载磁盘作为存储盘 如有系统冗余需求，可以准备6台虚拟机，就能很好的完成数据库备份及系统冗余。 编号 服务器类型 配置要求 操作系统 服务器用途 1 虚拟机 8核CPU 32G内存 500G SSD系统盘 CentOS8或openeuler22 主业务服务器 2 虚拟机 8核CPU 32G内存 500G SSD系统盘 CentOS8或openeuler22 从业务服务器 3 虚拟机 8核CPU 16G内存 500G SSD系统盘 CentOS8或openeuler22 主数据库服务器 4 虚拟机 8核CPU 16G内存 500G SSD系统盘 CentOS8或openeuler22 从数据库服务器 5 虚拟机 8核CPU 16G内存 500G SSD系统盘 CentOS8或openeuler22 数据库服务器 6 虚拟机 8核CPU 16G内存 200G SSD系统盘 windows 2012 R2 转码服务器 7 存储 分布式对象存储 分布式对象存储 分布式对象存储 支持虚拟机挂载磁盘的形式把挂载盘作为存储空间。 也可以对接san存储或者对象存储系统等第三方存储系统。 巴别鸟也为客户提供自建对象存储服务。 自建对象存储服务器配合虚拟机部署： 巴别鸟支持为客户在通用服务器上搭建对象存储，因为对象存储软件定义存储的优势（高可用、横向扩展容易），推荐没有对象存储的用户可以新购一台服务器部署巴别鸟对象存储系统配合在虚拟机（超融合）运行的巴别鸟业务系统一起使用。 业务服务器需求同上一节“在现有虚拟机（超融合）系统上进行部署”的要求。 关于巴别鸟对象存储的详细介绍可查看“自建对象存储服务器”章节。 我们大多数客户最终都选择对象存储服务器作为存储。 最低支持单服务器搭建对象存储系统（150TB以下空间需求）。 服务器类型 配置要求 操作系统 服务器用途 备注 存储服务器 至强银牌4210 2 20核CPU 64G内存 480G SSD硬盘 +存储所需容量硬盘 硬盘如果考虑性价比，建议使用 8T 10（2U） 或 8T 24（4U）。如果考虑存储密度及未来扩容投入可使用12T硬盘。 Linux 对象存储服务器 未来扩展建议增加相同磁盘容量的服务器。 单服务器对象存储网络拓扑图： 我们也支持搭建多台服务器组成的分布式对象存储系统。 分布式存储系统最小需求为2+1，就是需要准备三台存储服务器，性能要求和单台对象存储的要求一致。 物理分布式存储目前推荐最小单位是3台存储服务器。2+1纠错码意味着每扩充2台存储节点就需要增加1台服务器作为纠错服务器。以此，4+1意味着增加4台存储服务器就需要增加一台纠错服务器。所以4+1的磁盘利用率高于2+1。使用4+1方案首次建设就需要5台存储服务器。每次扩容增加的最小单位和首次建设需要的最小服务器单位一致。 多服务器分布对象存储网络拓扑图： 可以新增一台或一套存储服务器用来实时备份。主存储服务器出问题快速切换到备份服务器即可正常使用。 分布式高可用高冗余部署： 金融机构、医院、能源、超大型企业因为有业务不中断的硬性指标，需要系统能做到高可用、高冗余，不会因为服务器的单点故障而中断服务，并且能做到热切换及热修复，极端情况下，连交换机等网络设备都需要实现主备分离，这就需要使用分布式高可用高冗余部署。 巴别鸟支持多种高可用高冗余方案，可以部署在传统的分布式系统中实现高可用高冗余。 我们也可以为客户搭建适合巴别鸟的分布式系统。（硬件需要客户按要求自行采购） 巴别鸟分布式部署能确保任何一个单点故障都不会影响系统的正常使用。 推荐的分布式容易部署方案，业务服务器采用主备双活，存储系统采用分布式存储。 有密区及非密区管控需求的，详见 “数据摆渡章节” 巴别鸟高可用系统网络拓扑 异地灾备部署 对于对数据保全有着较高要求的用户，巴别鸟也支持异地灾备方案。就是把重要的数据库及文件存储内容备份到异地的备份系统中。如果本地机房出现问题，只要备份数据在，可以在任何地方重建系统并恢复正常使用。 巴别鸟可以为客户搭建异地灾备服务器，但不支持冷热数据分离等高级备份方式，如果数据量极大（1PB以上）考虑到性价比，建议使用专业的备份系统（如：NBU、云祺）。 巴别鸟有支持NBU标准的备份API可以调用。 异地灾备部署对网络环境要求较高，不同位置的机房间最好有专线或稳定的VPN连接。 使用备份系统只能在出问题后通过备份还原及重建数据，不支持直接切换到备份数据。一般情况下数据重建周期会比较久。 使用备份系统进行异地灾备示意图： 如果不需要冷热数据分类保存，巴别鸟也可以采用对象存储自带的异地灾备功能为客户完成异地灾备部署。 使用对象存储进行异地灾备，当主系统出问题可以快速切换到灾备服务器中。 自建对象存储服务器 巴别鸟对象存储是在开源MinIO系统上发展起来的对象存储系统。它继承了MinIO高性能、可扩展、数据安全的优势，同时更适配巴别鸟企业网盘的应用场景。 巴别鸟对象存储系统作为先进的对象存储系统，在速度、安全性、稳定性、高可用、横向扩展方面都有着传统存储系统无可比拟的优势。 巴别鸟对象存储系统优势 性能 MinIO号称是世界上速度最快的对象存储服务器，没有之一。在 32 个 NVMe 驱动器节点和 100Gbe 网络上发布的 GET/PUT 结果超过 325 GiB/秒和 165 GiB/秒，和亚马逊S3相比有明显优势，远远超越传统HDFS。 高可用性：MinIO通过数据的多副本、故障转移和自动恢复，保证高度可靠性和可用性，从而确保数据不丢失和业务不中断。 低冗余且磁盘损坏高容忍：标准且最高的数据冗余系数为2(即存储一个1 M的数据对象，实际占用磁盘空间为2M)。但在任意n/2块disk损坏的情况下依然可以读出数据(n为一个纠删码集合(Erasure Coding Set)中的disk数量)。并且这种损坏恢复是基于单个对象的,而不是基于整个存储卷的。 安全性： MinIO 通过最高级别的加密以及广泛的优化提供更多功能，几乎消除了通常与存储加密操作相关的开销。 数据分块存储与各个硬盘，获取硬盘或服务器读写权限也无法还原数据。 极高的可扩展性：MinIO支持分布式部署，并且可以水平扩展。在需要更多的存储空间或更高的性能时，可以通过添加新的节点轻松地扩展MinIO。 最低支持单机部署对象存储系统，而不是传统的需要三台独立服务器。 对象存储系统及纠删码 关于纠删码 巴别鸟对象存储系统(MinIO)使用纠删码erasure code 和校验和checksum来保护数据免受硬件故障和无声数据损坏。最高冗余状态下即便丢失一半数量(N/2)的硬盘,您仍然可以恢复数据。 纠删码是一种恢复丢失和损坏数据的数学算法，MinIO采用Reed Solomon code将对象拆分成N/2数据和N/2奇偶校验块。这就意味着如果是12块盘，一个对象会被分成6个数据块、6个奇偶校验块，可以丢失任意6块盘(不管其是存放的数据块还是奇偶校验块) , 仍可以从剩下的盘中的数据进行恢复，我们称数据存储为D、纠删码（奇偶校验）为P。 默认情况下会以N/2个数据和N/2奇偶校验块的方式来进行驱动器分片（支持自定义以支持更高的空间利用率） 纠删码不同于传统的多副本技术，它的磁盘利用率更高，数据恢复效率更高。（但是不少存储厂商把纠删码宣传为多副本，把P数说成是副本数，这是不准确的，会引起很多误解） 巴别鸟语境下的多副本是指增加备份服务器全量同步存储的数据。 纠删码特点及与raid技术区别 纠删码可以保护数据免受多个驱动器故障的影响 RAID6允许两个驱动器故障而MinIO纠删码允许丢失一半的驱动器 RAID属于卷级别的纠删码而MinIO纠删码是基于对象实现的纠删码（不用停机） 有效空间计算（空间利用率） 假设需要100TB的存储空间，需要购买多少个多大的硬盘取决于选择的冗余标准。譬如：采用3+1的冗余方式，100TB可用空间就需要购买12块12TB的硬盘，4块硬盘一组组成3组，9个数据盘3个校验盘，可用空间就是9 12一共108TB可用。如果采用2+1的冗余方式，就需要15块10TB的硬盘，10个数据盘，5个校验盘。 3+1方案中12块硬盘只能坏任意3块不影响系统使用及数据还原，但如果使用2+1方案，虽然需要购买更多硬盘，但15块硬盘里能坏任意5块也不影响系统使用。 更换坏掉的硬盘后系统能自动修复数据。 空间利用率可以参考下表。如果空间需求量大（超过150TB）并且在持续增长，考虑到存储密度和性价比，建议一台服务器一次性配16块硬盘。 不同数量的磁盘及空间利用率可以点击下方链接进行计算 https://min.io/product/erasure code calculator?ref=docs 硬件准备 所需硬件配置。 巴别鸟支持单台服务器搭建对象存储系统（单节点），以硬盘组作为冗余对象。最高可以损坏一半的硬盘也不影响系统的正常使用。 巴别鸟对象存储系统需要客户按要求事先准备好硬件服务器以供部署，最低配置需要2块志强CPU、64GB内存及400G固态硬盘（系统盘）然后增加相应存储容量所需的机械硬盘。 如要计算所需存储空间和购买的硬盘数，可点击下方链接进行计算。 https://min.io/product/erasure code calculator?ref=docs 建议硬件配置如下： 服务器类型 配置要求 操作系统 服务器用途 备注 存储服务器 至强银牌4210 2 20核CPU 64G内存 480G SSD硬盘 +存储所需容量硬盘 硬盘如果考虑性价比，建议使用 8T 12（2U） 或 8T 24（4U）。如果考虑存储密度及未来扩容投入可使用12T硬盘。 Linux 对象存储服务器 未来扩展建议增加相同磁盘容量的服务器。 巴别鸟对象存储使用软件定义存储技术，所以硬盘无需raid，考虑到一些服务器需要raid才能支持多磁盘，这种情况下每块硬盘都做成raid0直通模式即可。 单服务器模式每次扩容需要增加一台配置一致的服务器。扩容时可以不间断服务。 单服务器部署也支持增加一台配置一致的服务器搭建主备模式实时同步，如果一台服务器硬件损坏，可以快速切换到备用服务器。 磁盘有效空间容量和选择的冗余方式有关。譬如：使用8块10T硬盘来组建对象存储系统，采用3+1的冗余方案，相当于4块硬盘一个分组，分为2组，有效可用空间为60TB，同时8块硬盘损坏任意两块也不影响数据及系统使用，替换坏的硬盘即可自动重建。如果采用7+1的冗余方案，有效可用空间就为70TB，8块硬盘里任意损坏1块不影响数据及系统使用。 多服务器部署（分布式）。 巴别鸟对象存储系统支持多服务器部署，如使用服务器为冗余单位，最少要求3台服务器，即2+1模式，但考虑到空间利用率，推荐采用3+1方案（即4台服务器） 每个节点（服务器）的配置要求和上文单服务器部署一致。 建议节点配置一致（相同的操作系统、相同数量的磁盘和相同的网络连接） 每个节点提供的驱动器数量必须相同 节点间的时间差异不能大于15分钟（建议使用NTP确保时间的一致性） 空间利用率计算同单服务器。 私有化要求及服务流程 为了确保使用巴别鸟系统的体验和质量，巴别鸟所有的私有化部署工作都是由巴别鸟团队远程或现场进行部署及签发证书，暂不支持代理团队部署或客户自行部署。同时系统的维护工作也由巴别鸟运维团队进行定期远程维护。客户只需按要求准备好硬件及接入资源，其他事情就交给巴别鸟团队来完成。 私有化部署前期需要准备的： 计算大体使用人数、并发量、存储空间及空间增长率交由巴别鸟客户经理评估所需配置。 客户评估现有服务器剩余资源（如有），根据实际情况选择部署方式。 巴别鸟出具私有化部署方案。 客户根据方案准备相应的服务器及接入资源，分配服务器、安装操作系统。 保证服务器能够在外网远程桌面（也可以使用向日葵）和ssh访问，开启相应端口（我们的部署技术人员会提出具体端口要求） 用户最好能提供一个域名，没有域名的话需要一个固定的ip地址，用ip地址访问的方案需要保证在使用时期ip地址不会发生变动 如需接入邮箱找回密码或手机号发送验证码，需要准备相应的邮箱接入或短信网关。 编号 项目 要求 备注 1 域名 需要一个独立的主域名或二级域名 可以在公司原有域名的基础上设定一个二级域名。如yun.company.com 2 邮箱 需要一个可发送通知邮件的邮箱 支持smtp的邮箱地址即可 邮件推送相关 MailUser=xxxx@mail.com MailPassword=password MailHost=邮件服务器地址 MailPort=端口号 3 远程访问 可远程访问服务器进行配置 支持远程访问及控制服务器 4 SSl证书 https需要申请SSL证书 像数字证书颁发机构CA申请。推荐申请 OV 通配符 5 短信接口 如需要手机邀请，手机注册。则需开通短信接口服务（可选） 阿里云、腾讯云等云服务商也提供短信服务接口，申请即可开通 实施阶段 准备工作完成后通知我们，我们会给用户一个具体的实施时间安排，实施时间段内请保持外网访问的畅通 实施一般需要2 3个工作日，第一天远程部署安装巴别鸟，第二天测试和验收，第三天修正遇到的问题 实施完成后我们会通知用户，然后开始初始化阶段 初始化服务 巴别鸟为所有私有云客户提供了初始化服务，服务内容包括： 维护人员培训（远程或是现场） 帮助用户进行数据迁移、用户导入、权限分配等工作（远程或是现场） 使用人员培训 （远程或是现场） 接入第三方服务 作为一个围绕企业文件的办公平台，私有化的巴别鸟企业网盘通过接入第三方API的方式，可以轻松集成各种第三方服务到巴别鸟中，以满足不同的需求这些服务包括但不限于：电子签名、高级CAD预览、office、文字识别、图像识别....等第三方服务来解决您遇到的需求问题。 接入第三方服务的条件 理论上支持BS架构的第三方应用或者服务模块都可以接入。 第三方服务必须提供开放的API，以便巴别鸟企业网盘可以与之集成 如果是互联网服务，需要服务器能访问外网。 需要企业自行或委托我们购买接入的第三方服务的授权 推荐的可接入服务 文件防泄密系统： ipguard 在线office编辑：onlyoffice（自带）、office365、WPS Online、永中office 高级CAD预览：浩辰云图、梦想CAD CAD在线编辑：梦想CAD 在线签章：上上签 文字识别图像识别：百度千帆（智能云） AI相关：智巢AI（自有）、ChatGPT、智谱AI 开放API（统一存储平台） 巴别鸟私有化版本提供了开放API，使用巴别鸟API，您可以在您的系统中使用巴别鸟的几乎所有能力。并在云中构建自定义应用程序和集成，而无需构建和维护自己的内容管理服务。 统一存储平台 非结构化数据统一管理: 巴别鸟企业网盘的开放API的核心价值在于它可以作为一个统一的存储平台，用于整合和管理企业各个平台的非结构化数据。这包括但不限于OA（办公自动化）、CRM（客户关系管理）、ERP（企业资源规划）等应用，这样企业的所有非结构化数据都能在一个平台统一管理，提高安全性并节约存储资源。 企业级对象存储: 巴别鸟企业网盘还可以开放自带的对象存储接口，作为企业的统一存储管理平台。这意味着企业可以将不同来源的数据，包括文档、媒体、报表等，存储在巴别鸟企业网盘，并通过API访问和管理这些数据。 文档和支持 详细文档: 巴别鸟企业网盘提供详细的API文档，包括示例代码和用例，以帮助开发人员快速集成API。 附件2: 巴别鸟API文档 https://www.babel.cc/p/api integration.do 开发支持: 我们提供开发支持服务，技术人员会参与联调，一对一解决在API集成过程中可能遇到的问题和挑战。 单点登录SSO 巴别鸟私有化系统支持对接SSO单点登录平台或企业微信、钉钉、飞书、OA、ADFS、ERP等第三方平台以是实现单点登录。 更多关于单点登录的内容可以参见上文安全性章节的 ：单点登录（Single Sign On，SSO）集成 数据摆渡 巴别鸟可以使用“部门安全策略”的方式隔离某个部门数据，实现涉密部门的安全性和外发审批等功能，但是面对网络隔离的密区和非密区之间的文件传输，就需要用到数据摆渡的方式，确保密区和非密区之间可以安全可控的交换文件，这里就需要部署巴别鸟数据摆渡功能。在巴别鸟中，该功能模块命名为“传送文件“便于普通用户理解。 实现方式 在密区（研发区）和非密区（办公区）各部署一套巴别鸟，在两套巴别鸟之间传送文件: 需要安装巴别鸟数据摆渡模块 两套服务器间需要配置传输端口 传输使用SSL加密 支持多套巴别鸟之间互传文件 超级管理员可设定特定的文件接收者及审核人 可设定从非密区向密区传送文件无需审批 所有的传输都有记录及日志 多套巴别鸟在多个网络进行文件传送: 单套巴别鸟简化的文件传送方式 ： 有些客户的核心需求是非密区往密区便捷快速传输文件，仅想在密区部署一套巴别鸟，并没有在非密区使用网盘的需求，这时候就可以使用简化的数据摆渡方式。 出于安全考虑，该方式仅支持非密区向密区传送文件，并不支持密区向非密区传送文件。 除了在密区部署完整的巴别鸟系统，也需要在非密区部署一个文件传输服务。 非密区向密区传输文件无需审批。 使用步骤 部署完成数据摆渡模块的巴别鸟会在企业控制台增加一个“传送文件配置”模块，如果在企业控制台能看到该模块入口，说明已部署成功数据摆渡模块。 在企业控制台“传送文件配置”中新建接受端口和发送端口。已确定数据摆渡的接受端和发送端。 如果其中一套巴别鸟只配置了接口端口没有配置发送端口，那么就只能接收文件但不能发送文件。如：密区只能接收文件但不能发送文件。 新建了接收端会自动生成一个token，发送端要填入该token以实现加密传输。 一个巴别鸟可以建立多个接收端，每个接收端可以选择不同的成员。如：研发部和技术部的接收端分开。 通过审核后，接收人员能在自己的巴别鸟账号“传送文件”栏目找到摆渡过来的文件。 使用者在巴别鸟企业网盘中直接右键“传送文件”选择传送的接收端进行文件传送（发件）。并在“传送文件”栏目下查看发送过来并通过审核的文件。 为保证安全，传送文件以文件为单位（在多层文件夹中夹带重要文件，骗过审核），并不支持选择文件夹传送，但支持多选文件进行传送。 具有审批权限的管理员或部门经理可以在“传送文件”栏目下对接收和发送的文件进行审核，审核通过后文件才能传输。 定制化开发 巴别鸟私有化版本可以为客户提供专业的定制化开发（二次开发）服务。在巴别鸟现有产品的基础上针对客户具体需求推出更适合客户的产品。 巴别鸟定制开发优势 从产品思维出发帮助您设计产品 不同行业有不同的工作流程及使用习惯，同时需求和最终的产品间往往也隔着很深的鸿沟。只有需求没有好的产品设计往往会使项目迟迟无法落地。为了更好的适用于您的使用场景，我们职业产品经理带队的Babel care团队会为您的企业定制属于你的解决方案及二次开发支持。 精细化估时管理 我们拥有曾服务于北大方正的精细化估时管理体系，能精确的进行开发估时管理，提高项目成功率及落地效率。项目估时清晰有据可查，有效降低企业成本并提高效率。 透明的项目跟进及验收 在项目的每一个阶段，我们都有专职项目经理和产品经理跟进。确保项目进度及验收标准。并且我们可以开放我们的Jira（项目管理工具）给客户，让客户随时了解到项目的进度及耗时。 保持更新和维护 定制开发最普遍的问题是未来的更新和维护问题。传统的定制开发因为和标准产品有较大区别，所以往往会使用新的分支，开发团队也没有精力去维护新的分支，这就造成了定制开发产品会失去持续的维护及功能更新，越来越不好用或者孤立，最终被弃用。巴别鸟注意到并解决了这个问题，我们会在标准产品的基础上使用模块化的方式开发新的定制需求，或者把定制需求结合进标准产品以配置项的方式进行管理。这样，就是定制开发产品也能享受标准产品的更新及维护服务，做到可持续发展。 支持白牌服务（OEM） 出于商业目的或品牌建设需求，一些企业需要使用自己的产品名称及logo，巴别鸟可提供符合企业要求的白牌（OEM）版本。 透明、专业、负责 负责，是客户给我们最多的和最高的评价。在项目维护期内，我们会站在企业角度考虑，及时对应修正bug并完成功能调整。为企业提供长期可持续的维护服务。 巴别鸟定制开发范围 基于API的系统对接：如与OA、CRM、PDM等系统的对接整合。 API的定制开发：针对巴别鸟企业网盘某项功能开放API。 使用巴别鸟API接口的独立功能模块或子系统的定制开发。 围绕巴别鸟企业网盘现有功能的功能扩充，流程定制，数据交换。 基于巴别鸟源码的界面重塑及功能定制化开发。 巴别鸟定制开发流程 和客户确定需求及技术实现方案。出具：《需求分析说明书》 产品经理和客户深度讨论，设计原型和交互。出具《二次开发方案》、《产品原型》、《详细模块及估时表》 商务及合同环节，客户支付预付款项。 设计出图，开发启动。 内部测试及联调。 试上线及用户测试。 用户培训。 用户验收及交付 客户支付尾款。 信创支持 巴别鸟多年来一直积极响应国产化号召，巴别鸟的产品也能运行在大多数信创环境下。特别是针对服务器端，无论是CPU、操作系统还是数据库，巴别鸟都有相应的信创解决方案。 CPU及服务器架构支持。 巴别鸟支持X86和arm指令集的国产CPU，如X86的龙芯、飞腾、麒麟、海光…同时也支持arm架构的国产CPU，如：鲲鹏架构、飞腾arm架构。 操作系统。 巴别鸟使用docker部署，支持一切支持docker的Linux操作系统。如open Euler、银河麒麟、统信UOS 数据库。 巴别鸟推荐使用AliSQL数据库或其他兼容MySQL的数据库如：open Causs （高斯）。 巴别鸟也可以为定制接入其他国产数据库。如：达梦、人大金仓、南大通用….. 客户端。 巴别鸟客户端可以运行在Linux系统上，支持麒麟、统信等国产化系统。 由于Linux系统文件管理界面并没有统一，Linux版本的巴别鸟不支持同步文件夹及映射盘功能。 分类 分类 标准部署系统（非信创） 巴别鸟信创方案（x86) 巴别鸟信创方案（arm） 信创版本不支持的功能 业务服务器 操作系统 Centos、openEuler、Ubuntu openEuler 、麒麟 鲲鹏、麒麟、统信 无 业务服务器 巴别鸟版本 标准版 巴别鸟信创版（X86） 巴别鸟信创版（arm） 无 业务服务器 数据库 MySQL 高斯、TiDB、aliSql 高斯arm 无 业务服务器 组件/中间件 tomcat tomcat、TongWeb7 tomcat 无 业务服务器 组件/中间件 pomleo pomleo（信创） pomleo（信创） 无 业务服务器 组件/中间件 Elastic Search Elastic Search（ 信创） Elastic Search（arm） 无 业务服务器 组件/中间件 Redis Babel readis Babel readis 无 存储服务器 存储系统 minio minio minio arm 无 客户端 客户端 巴别鸟win/mac客户端 巴别鸟linux/麒麟/Ubuntu客户端 需要二开移植 linux版本客户端不支持映射盘、同步文件夹功能" }, { "lang": "zh", "slug": "architecture", "title": "系统架构", "description": "介绍前端、客户端、后端、数据库、对象存储、备份和服务拆分架构。", "category": "架构与存储", "top_category": "部署指南", "keywords": [ "架构", "Docker", "SOA", "对象存储" ], "url": "zh/architecture.html", "source": "content/zh/architecture.md", "summary": "系统架构 系统架构 架构概述 前端架构 前端架构包括以下关键组件和技术： 主架构选择了backbone.js，它提供了组件化开发、状态管理和路由控制等功能。又在其基础上引入了Gulp、Babel、browserify、Scss、jQuery、underscore、ES6等用以构建可维护和高性能的前端应用程序。 使用了WebSocket协议和后台进行消息的即时通讯。 设计了风格统一、用户友好、直观的界面，包括搜索、文件夹管理、文件预览等功能。 网站支持全平台预览，使用了CSS媒体查询和移动优化技术创建响应式布局，以确保网盘产品在不同设备上具备一致的外观和功能。 考虑多语言支持，目前系统支持中、英文两种语言，可在界面随时切换，也能通过浏览器语言进行切换。 采用了代码分割、懒加载、资源压缩和CDN加速等前端性能优化技术，以提高页面加载速度和响应时间。 实施前端安全性最佳实践，包括XSS（跨站脚本攻击）和CSRF（跨站请求伪造）防护。确保数据传输加密和安全存储。 跨平台和多语言： 巴别鸟系统前端部分包含了：巴别鸟iOS版（iPhone、iPad）、巴别鸟安卓版、巴别鸟web版、巴别鸟微信版（H5），巴别鸟mac客户端，巴别鸟windows客户端、巴别鸟Linux（麒麟）客户端。 原生iOS客户端使用Object C和Swift开发。 原生安卓客户端、鸿蒙使用Java开发（Android studio）。 windows、mac、麒麟 客户端使用Electron及C++进行开发，包含 客户端界面、同步端、传输管理、映射盘四个组件。 后端架构 服务器拓扑结构 巴别鸟的后端架构主要负责业务逻", "headings": [ { "level": 1, "title": "系统架构", "id": "section" }, { "level": 2, "title": "系统架构", "id": "section-2" } ], "images": [], "text": "系统架构 系统架构 架构概述 前端架构 前端架构包括以下关键组件和技术： 主架构选择了backbone.js，它提供了组件化开发、状态管理和路由控制等功能。又在其基础上引入了Gulp、Babel、browserify、Scss、jQuery、underscore、ES6等用以构建可维护和高性能的前端应用程序。 使用了WebSocket协议和后台进行消息的即时通讯。 设计了风格统一、用户友好、直观的界面，包括搜索、文件夹管理、文件预览等功能。 网站支持全平台预览，使用了CSS媒体查询和移动优化技术创建响应式布局，以确保网盘产品在不同设备上具备一致的外观和功能。 考虑多语言支持，目前系统支持中、英文两种语言，可在界面随时切换，也能通过浏览器语言进行切换。 采用了代码分割、懒加载、资源压缩和CDN加速等前端性能优化技术，以提高页面加载速度和响应时间。 实施前端安全性最佳实践，包括XSS（跨站脚本攻击）和CSRF（跨站请求伪造）防护。确保数据传输加密和安全存储。 跨平台和多语言： 巴别鸟系统前端部分包含了：巴别鸟iOS版（iPhone、iPad）、巴别鸟安卓版、巴别鸟web版、巴别鸟微信版（H5），巴别鸟mac客户端，巴别鸟windows客户端、巴别鸟Linux（麒麟）客户端。 原生iOS客户端使用Object C和Swift开发。 原生安卓客户端、鸿蒙使用Java开发（Android studio）。 windows、mac、麒麟 客户端使用Electron及C++进行开发，包含 客户端界面、同步端、传输管理、映射盘四个组件。 后端架构 服务器拓扑结构 巴别鸟的后端架构主要负责业务逻辑、数据处理和与前端的交互。它满足了以下关键目标： 模块化设计: 后端采用了模块化的设计，以便将不同功能和业务逻辑划分为独立的模块。这有助于代码的可维护性和可扩展性。 性能: 巴别鸟后端具有良好的性能，能够处理大规模的文件上传、下载、搜索和协作请求。采用了适当的负载均衡及缓存策略和优化技术以提高响应时间。 安全性: 巴别鸟后端重点强化安全性，包括用户身份验证、授权、数据加密和防御性编程，以保护用户数据免受攻击。 可扩展性: 巴别鸟后端架构具备可扩展性，以适应未来的业务需求和新功能的添加。采用了SOA服务架构和模块化组件设计，以支持功能的灵活扩展。 数据管理: 巴别鸟后端有效地管理了用户数据、文件数据和元数据。这包括数据库设计、备份策略和数据清理。 框架选择 巴别鸟采用了松散的、面向服务的架构模式。不同的服务，其设计、开发、部署都是独立的，这样就确保了系统的稳定性和可扩展性。最终，我们会采用docker把这些服务容器化，进行统一的管理和部署。 对于逻辑简单、高频访问的服务，我们选择Nodejs及相应的开发框架。 对于逻辑复杂、低消耗的服务，我们会选择Struts2+Spring框架。 对于逻辑复杂、且高消耗(比如MD5计算、文件分块、加密)的服务，我们会选用Rust语言进行开发。 数据层 数据库: 巴别鸟选择了MySQL作为数据库管理系统，也支持使用其他数据库（可按需支持 高斯、PostgreSQL、Oracle） 同时，巴别采用ORM（对象关系映射）: 使用ORM框架（Hibernate）将数据库表映射到Java对象，以简化数据访问和持久化。 安全性 用户身份验证: 使用强大的用户身份验证机制，包括单一登录（SSO）、OAuth认证和多因素认证（MFA）。 授权: 使用Spring Security等授权框架来定义和强制访问控制策略，确保用户只能访问其授权的资源。 数据加密: 实施数据传输和存储的加密，以保护用户数据的安全性。 业务逻辑 文件管理: 开发了业务逻辑来处理文件上传、下载、版本控制、共享和协作功能。 用户管理: 实施用户管理、权限管理和用户组织结构。 搜索功能: 开发了高效的搜索引擎，支持文件和元数据的快速检索。 在线编辑：负责文件的在线编辑、协同编辑。 文件转码：负责文件的批量排队转码，生成预览文件。 对象存储：文件的分块及落盘，存储系统管理。 Web服务 RESTful API: 使用RESTful API，以支持前端和其他客户端的数据交互和协作。 缓存管理 缓存策略: 使用缓存来提高性能，包括页面缓存、数据缓存和会话缓存。 异步任务处理 消息队列: 使用消息队列系统RabbitMQ来处理异步任务，如文件转码、文件预览生成等。 通过采用Struts2和Spring框架，结合以上设计考虑，可以构建一个强大、高性能、安全可靠的企业网盘后端系统，满足用户的需求并支持未来的扩展和功能添加。 云基础设施选择（公有云 SAAS版本巴别鸟） 公有云基础设施选择可以直接影响到企业网盘产品的性能、可靠性和安全性。巴别鸟公有云版本经过多方对比，选择了阿里云的ECS、OSS服务以及CDN分发业务。目前（2023年）公有云SAAS模式运行的巴别鸟系统已经0服务器故障在线运作了超过10年。 云服务提供商选择 业务服务器SAAS版本巴别鸟使用了阿里云的ECS（云服务器）集群 阿里云的ECS是一种弹性计算服务，为你提供了虚拟机实例，使你能够在云中运行应用程序。这些是选择ECS的一些关键优势： 灵活性: ECS允许你根据需要创建、启动和停止虚拟机实例。这意味着你可以根据流量需求来扩展或缩减计算资源。 可扩展性: 阿里云提供了多种不同规格的ECS实例，以满足不同工作负载的需求。你可以根据应用程序的性能要求进行选择。 可靠性: 阿里云的ECS实例通常具有高可用性，提供了多个数据中心和可用区，以确保业务连续性。 安全性: 阿里云提供了各种安全性功能，包括网络隔离、防火墙和安全组，以帮助你保护你的虚拟机实例免受恶意攻击。 对象存储SAAS版本巴别鸟使用了阿里云的OSS（对象存储服务） 阿里云的OSS是一种高度可扩展、安全可靠的云存储服务，适用于存储和管理大量的文件和数据。以下是选择OSS的一些优势： 可扩展的存储: OSS提供了可扩展的存储容量，可以根据你的需要进行动态扩展。这对于企业网盘产品中的文件存储非常重要。 数据备份和恢复: 阿里云的OSS具有数据备份和版本控制功能，可以帮助你保护数据免受丢失或损坏。 安全性: 数据存储在OSS中通常会受到加密和访问控制的保护，以确保数据的安全性。 CDN整合: 与CDN服务集成，可以提高文件的分发速度和用户体验。 为确保全球各地的访问通畅，巴别鸟也使用了CDN分发 CDN（内容分发网络）服务是将内容缓存到全球分布的边缘节点，以降低加载时间并提高用户体验。阿里云的CDN服务可以为企业网盘产品带来以下好处： 快速分发: 加速文件的分发，确保用户能够快速访问和下载文件，不受地理位置的限制。 负载均衡: CDN可以帮助分担服务器的负载，降低服务器的压力，提高网站的性能。 安全性: CDN服务通常具有DDoS攻击防护功能，可保护网站免受恶意攻击。 全球覆盖: 阿里云的CDN服务具有全球性覆盖，可确保你的内容快速传递给全球用户。 数据中心地理位置 目前巴别鸟使用了阿里云的两个数据中心： 杭州数据中心 及 威海数据中心 一南一北的配置能保证服务的可持续性及灾备需求。 数据库设计 数据库类型 巴别鸟企业网盘采用了多种类型的数据库，同时也可根据客户需求支持信创的数据库产品或是Oracle等大型数据库。 巴别鸟默认的产品数据库为： 核心数据库为关系型数据库 mysql 辅助数据库有：Redis 数据库，MongoDB 数据库 数据库架构 数据架构在企业网盘系统中扮演着至关重要的角色，确保了数据的高可用性、性能和一致性。下面是巴别鸟的数据库架构： A. 主从数据库架构 主库（Master） 主库负责处理写入操作，包括用户上传文件、修改文件信息等。 主库提供高可用性、数据一致性和事务处理。 从库（Slave） 从库主要用于读取操作，包括文件的查询、搜索等。 从库可以提供负载均衡，分担主库的读取负载。 数据同步：采用数据复制机制确保从库与主库的数据保持同步。 故障转移：从库可以在主库故障时接管写入操作，确保系统的连续性。 B. 关系型数据库（MySQL） 数据库设计 数据库设计以支持文件和用户管理，包括文件元数据、用户信息、权限等表的定义。 数据表之间的关系清晰，使用外键来维护数据一致性。 数据冗余 主从架构中的从库用于数据冗余，以防止主库故障时的数据丢失。 数据同步机制确保从库的数据与主库保持一致。 C. NoSQL数据库（MongoDB） 文件元数据存储 MongoDB可用于存储文件的元数据，如文件名、大小、版本信息等。 具有弹性模式的MongoDB适用于不断变化的数据模式。 D. 缓存数据库（Redis） 缓存读取数据 Redis用于缓存频繁读取的数据，以减轻数据库的负载。 缓存的数据可以包括用户会话信息、热门文件、访问日志等。 E. 数据备份和恢复 备份策略 定期备份主库和从库的数据，以确保数据的安全性。 巴别鸟备份数据存储在不同地理位置的可靠存储中。 灾难恢复 我们制定详实的恢复计划，包括从备份中还原数据的步骤和时间表。 巴别鸟运维团队会定期测试灾难恢复过程以确保其有效性。 F. 数据一致性和事务管理 事务支持 使用数据库事务来确保一系列操作的一致性，如文件上传、共享和权限更改。 事务应该被正确地管理，以避免数据损坏和不一致性。 并发控制 使用数据库锁和隔离级别来管理并发访问，以避免数据竞争和冲突。 G. 监控和性能优化 性能监控 实施数据库性能监控，包括查询响应时间、负载和资源利用率。 根据监控结果进行性能调整，以确保数据库的稳定性和性能。 查询优化 优化复杂查询以提高查询性能，包括索引优化和查询计划分析。 这些数据架构的元素将有助于确保你的企业网盘系统能够具备高可用性、性能卓越和数据的安全性。通过合理的数据库设计和维护，你可以提供稳定可靠的服务，满足用户需求并确保数据的完整性。 数据备份和恢复策略（公有云） A. 数据备份 定期备份计划：巴别鸟有定期的备份计划，以确保数据的连续备份（每日凌晨数据备份）。 完整备份和增量备份：巴别鸟采用完整备份和增量备份的组合策略。完整备份将数据库的全部数据备份，而增量备份仅备份自上次备份以来发生更改的数据，以减少备份时间和存储空间的消耗。 多备份位置：公有云版本巴别鸟有杭州机房及威海机房两个地理位置，以应对自然灾害或硬件故障。云存储和远程数据中心是常见的备份存储选择。 自动化备份：巴别鸟的数据库备份采用全自动备份机制，无需人工干预，以提高可靠性。 备份测试：我们会定期测试备份以确保其完整性和可用性。通过还原备份数据到测试环境中并验证数据的一致性来进行测试。 B. 灾难恢复 恢复计划：我们建立了详细的恢复计划，明确每个步骤和责任。确保团队成员了解如何执行恢复过程。 备份恢复测试：我们会定期测试备份恢复过程，以确保在紧急情况下能够迅速有效地还原数据。测试应包括各种故障场景的模拟。 备份监控：监控备份任务的运行情况，出现问题会自动提醒及报错，确保备份系统正常运行。 灾难恢复团队：我们有专门的灾难恢复团队，7 24小时待命，负责在紧急情况下采取行动，确保业务的持续运行。 通信计划：我们建立了有效的通信计划，及自动告警信息送达监控，以通知相关利益相关者有关灾难事件和恢复过程的信息。 文档和培训：确保恢复计划和过程的详细文档，并为团队成员提供培训，使其了解恢复策略和步骤。 以上策略和努力立足于确保数据库数据的安全性和可用性，并最大程度地减少数据丢失和系统停机的风险。" }, { "lang": "zh", "slug": "performance-scalability", "title": "性能优化与可扩展性", "description": "介绍负载均衡、缓存、异步任务、文件分块、去重、集群、容器化和 SOA 服务架构。", "category": "架构与存储", "top_category": "部署指南", "keywords": [ "性能", "可扩展性", "负载均衡", "缓存" ], "url": "zh/performance-scalability.html", "source": "content/zh/performance-scalability.md", "summary": "性能优化与可扩展性 性能优化 性能监控： 实时性能监控，包括转码速度、缓存命中率和响应时间，出错自动清空队列重试处理。严重错误短信通知运维人员。 资源调整： 根据监控结果和负载情况，动态调整预览和转码资源，以确保高性能和可用性。 集成测试 性能测试： 进行性能测试，模拟大量并发预览和转码请求，以评估系统在高负载下的表现。 office家族文件 巴别鸟支持微软office家族及WPS的文件的在线预览，为确保office文件特别是word文件的显示准确性，巴别鸟提供了2种office文件的预览方式： 使用运行于Windows服务器的office转码模块把文件转码后进行预览（默认）。 需要部署一台window服务器生成预览文件。 可以相当准确的与微软office或WPS打开无差别的预览word类文件和ppt类文件。 支持使用巴别鸟预览器(BabelViewer)对文件进行批注讨论、圈画及版本对比。 可使用“智巢AI”文档助理功能。 Excel文件因没有版式和字体问题，都使用在线office的预览功能进行预览。 所有的预览文件都可以内嵌水印，并可另存为带水印的PDF文件。 使用运行于Linux服务器的在线office的预览功能提供office及wps文件的在线预览。 针对只能使用Linux，并且对word文件预览版式准确度没有较高要求的用户。 因系统字体差异，在线office解析等原因，在Linux系统中的在线office并不能1：1完美显示word文件的版式，在譬如：项目符号编号、段落高度、分页、插入图形位置等方面会有少许差异。 Excel文件因没有版式和字体问题，都使用在线offi", "headings": [ { "level": 1, "title": "性能优化与可扩展性", "id": "section" }, { "level": 3, "title": "性能优化", "id": "section-2" }, { "level": 2, "title": "安全性", "id": "section-3" }, { "level": 3, "title": "安全的架构", "id": "section-4" }, { "level": 3, "title": "用户身份验证和授权（SSO）", "id": "sso" }, { "level": 3, "title": "用户体验", "id": "section-5" }, { "level": 3, "title": "概述", "id": "section-6" }, { "level": 3, "title": "概述", "id": "section-7" }, { "level": 3, "title": "概述", "id": "section-8" }, { "level": 2, "title": "主要功能模块", "id": "section-9" }, { "level": 3, "title": "技术特点", "id": "section-10" }, { "level": 3, "title": "优势", "id": "section-11" }, { "level": 3, "title": "简介", "id": "section-12" }, { "level": 3, "title": "技术特点", "id": "section-13" }, { "level": 3, "title": "常见文件管理功能", "id": "section-14" }, { "level": 3, "title": "版本管理概述", "id": "section-15" }, { "level": 3, "title": "技术实现", "id": "section-16" }, { "level": 3, "title": "版本更新方式", "id": "section-17" }, { "level": 3, "title": "版本管理功能", "id": "section-18" }, { "level": 3, "title": "企业控制", "id": "section-19" }, { "level": 3, "title": "搜索模块概述", "id": "section-20" }, { "level": 3, "title": "带权限判断的搜索", "id": "section-21" }, { "level": 3, "title": "技术基础", "id": "section-22" }, { "level": 3, "title": "搜索功能", "id": "section-23" }, { "level": 3, "title": "性能优化", "id": "section-24" }, { "level": 3, "title": "未来发展", "id": "section-25" }, { "level": 3, "title": "在线编辑模块概述", "id": "section-26" }, { "level": 3, "title": "技术基础", "id": "section-27" }, { "level": 3, "title": "主要功能", "id": "section-28" }, { "level": 3, "title": "用户体验", "id": "section-29" }, { "level": 3, "title": "企业协作", "id": "section-30" }, { "level": 3, "title": "开放API", "id": "api" }, { "level": 3, "title": "其他在线编辑器", "id": "section-31" }, { "level": 3, "title": "客户端编辑概述", "id": "section-32" }, { "level": 3, "title": "技术实现", "id": "section-33" }, { "level": 3, "title": "主要功能", "id": "section-34" }, { "level": 3, "title": "用户体验", "id": "section-35" }, { "level": 3, "title": "技术挑战", "id": "section-36" }, { "level": 3, "title": "分享功能", "id": "section-37" }, { "level": 3, "title": "外发功能（发送文件）", "id": "section-38" }, { "level": 3, "title": "用户控制和企业策略", "id": "section-39" }, { "level": 3, "title": "灵活性与便捷性", "id": "section-40" }, { "level": 3, "title": "技术架构", "id": "section-41" }, { "level": 3, "title": "适用的文件类型", "id": "section-42" }, { "level": 3, "title": "预览器类型", "id": "section-43" }, { "level": 3, "title": "批注种类", "id": "section-44" }, { "level": 3, "title": "功能模块", "id": "section-45" }, { "level": 3, "title": "主要特点", "id": "section-46" }, { "level": 3, "title": "技术架构", "id": "section-47" }, { "level": 3, "title": "文件评审的优势", "id": "section-48" }, { "level": 3, "title": "角色权限", "id": "section-49" }, { "level": 3, "title": "文件权限", "id": "section-50" }, { "level": 3, "title": "总结", "id": "section-51" }, { "level": 3, "title": "概述", "id": "section-52" }, { "level": 3, "title": "使用方式", "id": "section-53" }, { "level": 3, "title": "总结", "id": "section-54" }, { "level": 3, "title": "概述", "id": "section-55" }, { "level": 3, "title": "主要特点", "id": "section-56" }, { "level": 3, "title": "技术优势（对比WebDAV和SMB）", "id": "webdav-smb" }, { "level": 3, "title": "应用场景", "id": "section-57" }, { "level": 3, "title": "主要特点", "id": "section-58" }, { "level": 3, "title": "技术架构", "id": "section-59" }, { "level": 3, "title": "档案管理的优势", "id": "section-60" }, { "level": 3, "title": "主要特点", "id": "section-61" }, { "level": 3, "title": "技术架构", "id": "section-62" }, { "level": 3, "title": "日志与报表的优势", "id": "section-63" }, { "level": 3, "title": "动态栏目", "id": "section-64" }, { "level": 3, "title": "通知栏目", "id": "section-65" }, { "level": 3, "title": "个性化设置", "id": "section-66" }, { "level": 3, "title": "应用场景", "id": "section-67" }, { "level": 3, "title": "概述", "id": "section-68" }, { "level": 3, "title": "主要功能", "id": "section-69" }, { "level": 3, "title": "应用场景", "id": "section-70" }, { "level": 3, "title": "总结", "id": "section-71" }, { "level": 3, "title": "概述", "id": "section-72" }, { "level": 3, "title": "主要功能", "id": "section-73" }, { "level": 3, "title": "应用场景", "id": "section-74" }, { "level": 3, "title": "主要栏目", "id": "section-75" }, { "level": 3, "title": "智巢AI的三个主要模块", "id": "ai" }, { "level": 3, "title": "技术解决方案", "id": "section-76" }, { "level": 3, "title": "优势", "id": "section-77" }, { "level": 3, "title": "多任务协同与执行流转权重", "id": "section-78" }, { "level": 3, "title": "功能概述", "id": "section-79" }, { "level": 3, "title": "核心运作与配置规则", "id": "section-80" }, { "level": 3, "title": "权限与数据安全控制", "id": "section-81" }, { "level": 3, "title": "典型业务应用场景", "id": "section-82" }, { "level": 3, "title": "功能概述", "id": "section-83" }, { "level": 3, "title": "适用范围与权限控制", "id": "section-84" }, { "level": 3, "title": "核心规则引擎与配置维度", "id": "section-85" }, { "level": 3, "title": "原始名称的精细化修剪与防冲突机制", "id": "section-86" }, { "level": 3, "title": "全局格式化输出控制", "id": "section-87" }, { "level": 3, "title": "功能概述", "id": "section-88" }, { "level": 3, "title": "执行逻辑与边界条件", "id": "section-89" }, { "level": 3, "title": "广泛的格式兼容矩阵", "id": "section-90" }, { "level": 3, "title": "功能概述", "id": "section-91" }, { "level": 3, "title": "灵活的触发机制与作用域", "id": "section-92" }, { "level": 3, "title": "核心智能整理规则引擎", "id": "section-93" }, { "level": 3, "title": "业务场景与功能概述", "id": "section-94" }, { "level": 3, "title": "签章资产库与个性化配置", "id": "section-95" }, { "level": 3, "title": "智能自适应交互与沉浸式引导体系", "id": "section-96" }, { "level": 3, "title": "功能概述与业务价值", "id": "section-97" }, { "level": 3, "title": "标准目录阵列的大规模生成", "id": "section-98" }, { "level": 3, "title": "项目级文件夹与权限的“一键部署”", "id": "section-99" }, { "level": 3, "title": "实时状态监控与智能容错机制", "id": "section-100" }, { "level": 3, "title": "使用范围", "id": "section-101" }, { "level": 3, "title": "需要解决的问题", "id": "section-102" }, { "level": 3, "title": "巴别鸟解决方案", "id": "section-103" }, { "level": 3, "title": "基本介绍", "id": "section-104" }, { "level": 2, "title": "用户界面", "id": "section-105" }, { "level": 2, "title": "性能优化", "id": "section-106" }, { "level": 3, "title": "优势", "id": "section-107" }, { "level": 3, "title": "优势", "id": "section-108" }, { "level": 3, "title": "优势", "id": "section-109" }, { "level": 3, "title": "优势", "id": "section-110" }, { "level": 2, "title": "可扩展性", "id": "section-111" } ], "images": [], "text": "性能优化与可扩展性 性能优化 性能监控： 实时性能监控，包括转码速度、缓存命中率和响应时间，出错自动清空队列重试处理。严重错误短信通知运维人员。 资源调整： 根据监控结果和负载情况，动态调整预览和转码资源，以确保高性能和可用性。 集成测试 性能测试： 进行性能测试，模拟大量并发预览和转码请求，以评估系统在高负载下的表现。 office家族文件 巴别鸟支持微软office家族及WPS的文件的在线预览，为确保office文件特别是word文件的显示准确性，巴别鸟提供了2种office文件的预览方式： 使用运行于Windows服务器的office转码模块把文件转码后进行预览（默认）。 需要部署一台window服务器生成预览文件。 可以相当准确的与微软office或WPS打开无差别的预览word类文件和ppt类文件。 支持使用巴别鸟预览器(BabelViewer)对文件进行批注讨论、圈画及版本对比。 可使用“智巢AI”文档助理功能。 Excel文件因没有版式和字体问题，都使用在线office的预览功能进行预览。 所有的预览文件都可以内嵌水印，并可另存为带水印的PDF文件。 使用运行于Linux服务器的在线office的预览功能提供office及wps文件的在线预览。 针对只能使用Linux，并且对word文件预览版式准确度没有较高要求的用户。 因系统字体差异，在线office解析等原因，在Linux系统中的在线office并不能1：1完美显示word文件的版式，在譬如：项目符号编号、段落高度、分页、插入图形位置等方面会有少许差异。 Excel文件因没有版式和字体问题，都使用在线office的预览功能进行预览。 使用在线office预览功能打开的word类和ppt类文件将不再支持巴别鸟预览器的批注功能。 不支持使用“智巢AI”的文档助理功能。 所有的预览文件都可以内嵌水印，并可另存为带水印的PDF文件。 考虑到浏览器的性能及服务器的效率，在线预览office文件会有一定的文件尺寸大小限制，超过这个限制的文件就无法在线预览。私有云用户可以自定义这些限制，但不建议调过大。 Word（文档）类文档最大可预览文件大小为 200MB。 PPT（幻灯片）类文档最大可预览大小为 200MB。 Excel（表格）类文档最大可预览大小为 50MB。 图片及图形文件 巴别鸟支持绝大多数图片文件的在线预览，包括psd、gif家族、jpg家族、bmp家族、png、raw家族（部分）、arw、tif、TIFF、dicom、ico等文件，同时也支持医学图形常用的dicom格式。并且得益于巴别鸟强大的图片处理技术，巴别鸟可以以1：1的方式在线预览超高分辨率的大图（可选组件），并且在图片上批注讨论，并且巴别鸟支持读取照片的元数据。 PSD、RAW、BMP等图片格式需要服务器自动转码后才能预览。 通常情况下（没有开启大图显示模块）超过4K分辨率的大图片将会被服务器处理成便于网页展示的尺寸及格式。开启大图显示模块后，服务器将把大图切割成若干小块，分块载入1：1显示，这将耗费较大服务器资源。 PNG等透明背景的图在巴别鸟中也能显示出透明度，并且可以更改背景。 巴别鸟系统会读取图片元数据信息，供搜索、查询、排序。这些信息包括：分辨率、尺寸、拍摄设备、拍摄时间、拍摄地点。 所有可预览图片格式都会生成缩略图，供文件列表展示快速查找及瀑布流模式展示。 所有图片格式都支持在巴别鸟预览器(BabelViewer)中批注讨论、圈画及版本对比。 如开启水印功能，服务器将会对预览的图片进行预处理，在图片中嵌入水印。 所有图片类文件都可以另存为带水印的PDF文件。 巴别鸟也能很好的支持矢量图形的在线预览，包括但不限于ai、dwg、dcm、dxf 、dwt 、pdf、eps、svg、idml、indd…等矢量图形格式。更重要的是，巴别鸟能以矢量渲染的方式打开这些格式的文档，这意味着这类图形可以在巴别鸟中放大几十倍也不会模糊或失真。 AI、eps、indd等文件需要服务器自动转码后才能预览。 以矢量的方式显示，支持更改背景颜色。 放大后图形不会失真或模糊。 其他特性和图片一致，同样支持嵌入水印、另存为带水印PDF、在巴别鸟预览器(BabelViewer)中批注讨论、圈画及版本对比、生成文件列表预览图。 3D及CAD文件 得益于巴别鸟预览器(BabelViewer)对3D格式的支持，我们默认支持dae、3ds、abc、fbx、mtl、obj、ply、stl、x3d等3D图形的在线预览，并且支持在3D空间中的批注讨论。 目前，巴别鸟预览器仅支持单个文件3D图形，如果文件有外挂皮肤等外挂文件将只能载入模型本体。 3D文件目前还不支持生成预览图，但如果有这方面需求支持定制开发。 3D文件可以在巴别鸟预览器中旋转、放大、缩小、拆分，并可以建立批注讨论点，系统会记住建立批注时的视口，点击批注会自动旋转到建立批注时的视角。 如需对revit、soildworks、3DMax等专业格式进行支持，私有化部署用户可以选择接入第三方3D在线显示及转码插件，（如：Autodesk viewer）这会产生相关费用。 目前不支持在移动设备预览3D文件。仅支持在网页及客户端预览3D文件。 巴别鸟支持对CAD文件的预览。如: dwg，dwt，dxf 格式，目前在公有云上，巴别鸟向专业版及企业版用户提供强大的CAD预览服务，私有化用户想要预览CAD文件需要购买相应的CAD转码服务私有化授权。 巴别鸟CAD预览支持CAD版本R12 2021。 CAD文件可生成预览缩略图，用于文件列表及瀑布流模式。 兼容天正全专业T20V7版本。 支持在浏览器、客户端、移动端预览及批注CAD文件。 支持百兆以上图纸浏览。 图层打开/隐藏/多选/全选。 布局切换、视图平移、缩放、更改背景颜色、鹰眼鸟瞰视图。 音视频转码 不使用转码服务器的情况下 巴别鸟无须转码服务就可以直接在线播放支持HTML5标准的视频文件。 支持的格式如下： 视频文件格式 MP4：MPEG 4 Part 14，支持H.264编码。几乎所有的浏览器都支持该格式。 WebM：谷歌开发的格式，使用VP8或VP9编码，可以在大多数现代浏览器中播放 Ogg：开放媒体格式，使用Vorbis编码，可以在大多数现代浏览器中播放。 音频文件格式 MP3：MPEG 1或MPEG 2 Audio Layer III，可以在几乎所有的浏览器中播放。 AAC：Advanced Audio Coding，可以在大多数现代浏览器中播放。 Ogg：开放媒体格式，使用Vorbis编码，可以在大多数现代浏览器中播放。 WAV：Waveform Audio File Format，可以在几乎所有的浏览器中播放，但文件较大，不适合在网络上播放。 兼容性 视频兼容性 音频兼容性 使用转码服务器的情况下 如果需要使用巴别鸟管理查询大量视频素材，就需要搭建专用的视频转码服务器，并购买相应的视频转码模块授权。（目前此服务仅支持私有化部署用户） 巴别鸟视频转码模块采用FFmpeg解决方案，FFmpeg 支持 MPEG、 DivX、MPEG4、AC3、DV、FLV 等40多种编码，AVI、MPEG、OGG、Matroska、ASF 等90多种解码，FFmpeg 支持的编解码器种类共有 280 多种， 涵盖了几乎所有常见音视频编码格式， 能解码几乎所有的音视频。 视频转码服务器所需硬件配置 视频转码是一个相当耗费运算资源的服务，需要一台专门的物理机来执行转码操作。同时服务器性能要求和需要转码的视频类型，时长和码率都有关系。 按每天转换累计时长50小时的HDR 4K视频（使用CUDA）为1080P H.264 AC3 MP4为基准，所需的服务器硬件配置如下： 服务器类型 配置要求 操作系统 服务器用途 备注 视频转码服务器 至强Intel E5 2630v3CPU 2 64G内存 2TB SSD硬盘 + Nvidia Tesla M4 4G显卡 Linux 视频转码服务器 使用GPU（CUDA） 根据视频码率不同所需转码时间也不同，在通常情况下，一个100秒的2K视频转码成1080P MP4耗时为8秒（使用上文硬件配置），如果同时转码的视频多，服务器则会做多线程排队处理。 使用转码服务器后，视频文件转码完成后即可播放，并且可以在文件列表查看缩略图。 安全性 安全的架构 安全是业务的关键！巴别鸟从产品设计到架构搭建及服务器管理都优先考虑安全性，并且包含了许多重要的安全功能。您可以控制每个文件及每位成员的访问行为、添加文件水印、查看访问日志、重要文件归入档案库、给文件及部门设立加密等级及安全策略….这一系列举措可以最大限度保护重要数字资产。同时，巴别鸟使用了安全等级最高的EV SSL认证，银行级的加密传输，多机房分布式备份，确保你的数据安全无忧。这些举措使巴别鸟获得了QUALYS安全性A+认证，同时我们也拥有ISO27001信息安全质量体系认证。 巴别鸟从上线开始就实现了从上传、下载、到落盘的全链路的加密传输和存储，配合权限管理及文件管理的细节处理，以及各种使用场景所遇到的风险分析及相应的功能应对策略，使巴别鸟成为了市面上最安全的企业网盘之一。 图：巴别鸟数据传输链路 防火墙、堡垒机、VPN、SSL….在传输和服务器部署架构上我们有越来越多的手段保证系统的数据安全性。但是根据我们多年从事企业安全服务的经验来看，80%数据泄露事件往往来源于内部人员泄露及管理混乱。即使系统做到了物理隔离，也没办法杜绝数据泄露风险。巴别鸟从产品设计之初就考虑到了这一点，从管理、人员和设备的角度提供了多种安全设计及功能。在易用性和安全性的矛盾之处也提供了多种可选设置及方案。从产品结构和使用逻辑上尽可能保证数据安全性。大幅消除因内部人员疏忽或破坏产生的数据泄露风险。 用户身份验证和授权（SSO） 自有用户体系 巴别鸟自由用户体系身份验证种类 账号类型 验证方式 备注 邮箱 密码、验证码 公有云需绑定手机号验证 手机号（全球） 密码、验证码 私有云需对接短信发送平台 工号（user ID） 密码 仅私有云支持，忘记密码只能管理员重置，首次登录会要求用户强制重置密码 微信 扫码、APP跳转（移动端） 仅公有云支持，需绑定手机号验证 巴别鸟支持多种身份验证类型混用。 可强制要求多因素认证（MFA）以提高安全性 混合身份验证: 在使用单点登录时（SSO）支持同时使用自有用户体系和SSO。用户可以选择使用自有凭据登录或通过SSO登录（如使用企业微信扫码登录及采用账户密码登录）。 单点登录（Single Sign On，SSO）集成 单点登录（Single Sign On，SSO）集成是企业网盘产品中的一个关键功能，它允许用户在一次身份验证后访问多个不同的应用程序和服务，提高了用户体验和安全性。 巴别鸟支持OAuth2.0、CAS等方式集成单点登录，并已实际应用于和多种系统的对接中。 支持的SSO标准和协议 巴别鸟企业网盘支持多种SSO标准和协议，包括但不限于以下内容： ADFS集成： 巴别鸟支持与Active Directory Federation Services（ADFS）的集成，这使得基于Windows身份验证的SSO成为可能。这种集成允许企业内部用户使用他们的Windows凭据进行登录。 AD域控制器集成： 巴别鸟还支持与企业的本地Active Directory（AD）域控制器的集成。这使得企业内部用户可以使用他们的本地域凭据进行登录。 企业微信集成： 巴别鸟支持对接企业微信，这使得企业可以直接用企业微信账号进行扫码认证登录。并且可以同步导入微信的组织结构及用户，使用企业微信发送通知，并在工作台中访问巴别鸟。 钉钉集成： 巴别鸟支持对接钉钉，这使得企业可以直接用钉钉账号进行扫码认证登录。并且可以同步导入钉钉的组织结构及用户，使用钉钉发送通知，并在钉钉工作台中访问巴别鸟。 飞书集成： 巴别鸟支持对接飞书，这使得企业可以直接用飞书账号进行扫码认证登录。并且可以同步导入飞书的组织结构及用户，使用飞书发送通知，并在飞书工作台中访问巴别鸟。 集成文档： AD域控、企业微信、钉钉、飞书、致远OA的集成已内嵌于巴别鸟私有化版本中，用户购买相应模块后只需要根据相应文档进行配置即可使用。相关配置文档可咨询巴别鸟客服人员。 第三方SSO集成： 如果你的组织使用第三方SSO供应商（如Okta、OneLogin、Auth0、千帆、泛微等），我们也支持与这些供应商的产品集成。这意味着外部用户可以通过这些供应商的产品进行SSO登录。但这需要二次开发并需要支付一定费用。 第三方自有用户体系集成 我们理解许多组织可能同时拥有自有用户体系，因此我们的SSO集成支持混合身份验证： 混合身份验证: 我们的系统允许用户选择使用自有凭据进行登录，或者使用SSO进行登录。这提供了最大的灵活性，以适应不同用户的需求。 用户映射和同步: 我们确保自有用户体系中的用户帐户与SSO中的用户帐户同步。这意味着用户的属性和权限在整个系统中保持一致。 安全性和授权 我们非常注重安全性和授权策略的实施，以确保只有授权用户能够访问资源： 身份验证策略: 我们支持灵活的身份验证策略，包括多因素认证（MFA）等高级选项。这有助于确保用户的身份得到妥善验证。 授权和访问控制: 我们允许管理员配置和管理用户的访问权限，包括文件和资源的授权。这确保了只有经过授权的用户能够访问敏感数据。从其他平台导入的用户仅会拥有所在部门的初始权限（默认为部门成员），管理员可以通过自定义“部门成员”角色权限的方式统一更改导入用户的初始权限范围。 用户体验 我们关注用户体验，努力提供无缝的登录体验： 登录页面: 我们的登录页面清晰直观，提供用户选择不同的登录方式的选项。用户可以选择使用SSO登录或使用自有凭据登录。同时，我们也支持使用用户单点登录系统自己的登录页面（如ADFS系统认证页面） 单点注销: 如果对接的单点登录系统（SSO）支持单点注销功能，我们也可支持单点注销，这意味着用户可以在任何一个连接的应用程序中注销，系统会自动注销其他应用程序的会话。 访问控制列表（ACL）设计 概述 在巴别鸟企业网盘中，权限管理是确保文件和资源的安全性和可访问性的核心组成部分。ACL（Access Control List）被用于定义用户和角色对于不同部门中的资源的访问权限。本章将详细介绍我们的ACL设计，包括角色管理、用户分配、角色权限和变更管理。 角色管理 角色定义: 我们允许管理员自定义角色，每个角色代表一组权限的集合，有32种权限可选组合成角色。 每个角色应有一个明确的名称和描述，以便管理员和用户了解其功能。 权限分配: 每个角色都被分配特定的权限，这些权限决定了角色在部门中的操作能力。 权限应该精心选择，以确保用户拥有必要的权限但又不会过度授权。 用户管理 用户角色分配: 每个用户都可以被分配一个或多个角色，这些角色决定了用户在不同部门中的权限。 允许一个用户在不同部门拥有不同的角色，以适应多样化的需求。 用户与部门的关联: 用户应与其所属部门建立关联，以便根据部门角色自动分配相应的权限。 用户仅能访问其所在的部门，并有角色决定在部门中的访问权限。 能否访问子部门，也由角色权限决定（角色有访问子部门权限）。 角色权限管理 角色权限定义: 每个角色有明确的权限定义，包括可读、可写、可删除、可共享等操作。 角色可以根据需要新增或删减。 权限继承: 我们的系统支持权限的继承，当用户分配到一个角色时，他们会自动继承该角色的权限。 这减少了手动分配权限的工作量，同时确保一致性。 变更管理 角色权限变更: 当管理员更改角色的权限时，所有拥有该角色的用户在部门中的权限也会相应更改。 我们将详细记录这些变更，以便进行审计和故障排除。 权限审计: 安全管理员可定期审计角色和用户的权限，以确保授权的准确性和安全性。 不再需要的权限应及时取消。 安全性 访问控制: 巴别鸟企业网盘的ACL系统将严格控制用户和角色对资源的访问。 只有经过授权的用户并拥有在该部门的角色才能访问部门文件。 部门间相互隔离，可以设定不同的密级（部门安全策略）来保护部门的文件。 审计和监控: 所有的权限变更角色变更都会留下日志记录。方便管理查询。 实施监控和审计机制，以监视权限变更和访问活动，及时检测和响应潜在的风险。 最佳实践 最小特权原则: 遵循最小特权原则，即给予用户和角色所需的最低权限，以降低潜在的安全风险。 部门文件可通过文件访问控制来精确增加某个成员（或某种角色）的权限，并设定权限有效期。 定期审查: 定期审查角色和权限配置，以确保系统的安全性和性能。 未来扩展 多租户支持: 公有云系统支持多租户控制。 私有云考虑将ACL系统扩展到多租户环境，以支持多个客户或组织的需求。 数据加密 数据传输加密（SSL/TLS） 加密协议 在巴别鸟企业网盘中，我们高度重视数据传输的安全性。为了确保数据在传输过程中得到保护，我们采用了安全套接字层（Secure Socket Layer，SSL）协议来实现传输加密。 HTTPS: 我们使用HTTPS协议，它是HTTP的安全版本，以加密所有数据传输。 HTTPS通过TLS/SSL协议提供端到端的数据加密，防止第三方恶意用户截取或窃听传输的数据。 证书管理 SHA 256证书: 我们的SSL证书采用SHA 256哈希算法，这是一种强大的哈希算法，提供了高级的安全性和完整性保护。 SHA 256证书对于验证服务器的身份以及保护数据传输非常关键。 证书更新: 巴别鸟企业网盘将定期更新SSL证书，以确保证书的有效性和安全性。 我们会监视证书的到期日期，提前进行续签。 数据加密 数据传输加密: 所有在巴别鸟企业网盘和用户终端之间的数据传输都会经过TLS/SSL加密。 这包括用户登录、文件上传和下载、以及任何敏感数据的传输。 数据完整性保护: TLS/SSL不仅提供了数据加密，还能够验证传输过程中数据的完整性，以防止数据被篡改或损坏。 安全性 严格的加密策略: 我们遵循严格的加密策略，确保所有数据传输都经过安全通道，无法被非授权方访问。 保护用户隐私: 数据传输加密有助于保护用户的隐私和敏感信息，包括个人身份信息和机密文件。 最佳实践 安全升级: 我们将继续关注新的安全标准和最佳实践，确保数据传输加密的安全性得到不断提升。 安全审计: 我们会定期进行安全审计和漏洞扫描，以确保我们的加密机制不受到潜在威胁的影响。 图：巴别鸟获得了Qualys SSL扫描的A+安全验证 数据存储加密 概述 在巴别鸟企业网盘中，我们采用了高级的分块加密技术，以确保文件的安全性和完整性。我们使用分块加密技术来将文件分成小块，每个小块都经过哈希加密，然后存储在对象存储系统中。这一技术确保即使在服务器控制权或硬盘被攻破的情况下，攻击者也无法获取到完整的文件内容。 分块加密 文件分块: 上传到巴别鸟企业网盘的文件会被分成若干小块（chunks）。 每个小块的大小可以根据系统需求进行配置，以平衡性能和安全性。 哈希加密: 每个小块都会经过哈希加密，使用强大的哈希算法确保数据的完整性。 哈希值将与存储的小块一起存储，以便后续验证。 存储安全 对象存储: 加密后的小块将存储在巴别鸟企业网盘的对象存储系统中，确保高可用性和数据冗余。 无法还原的加密: 我们使用不可逆的哈希加密算法来确保存储的小块无法还原为原始文件内容，以确保文件存储的安全性。 安全传输: 小块数据在传输到对象存储系统时也会经过加密，以防止中间人攻击。 文件下载 临时下载链接: 当用户需要下载文件时，鉴权通过系统会动态地拼合分块，形成一个临时下载链接。 这个链接是唯一的，只有很短的有效期用于下载。再次下载需要从新生成下载链接。这个设定可以防止通过获取下载链接暴露文件。 下载解密: 在用户请求下载时，巴别鸟企业网盘会将分块数据在服务器端解密，然后合并为完整的文件。 这确保了文件在存储过程中即使硬盘被非法读取内容也不会暴露文件给任何未授权的访问者。 安全性 数据隔离: 分块加密技术将数据分成小块，每个小块都经过独立的哈希加密，以防止整个文件被暴露。 无法还原性: 使用不可逆的哈希算法确保了数据的无法还原性，即使攻击者获取了一部分小块数据，但因数据缺失也无法还原原始文件。 防止数据泄漏 安全审计日志 概述 在巴别鸟企业网盘中，我们强调数据访问和操作的可追溯性和安全性。为了实现这一目标，我们建立了一个强大的访问日志系统，用于记录整个系统的历史访问日志。这些日志包括文件的上传和下载、权限的变更、用户讨论批注、文件的增删改查、审批以及部门变更等操作。本章将详细介绍我们的安全审计日志系统和角色管理。 访问日志功能 全面的日志记录: 我们的日志系统记录了整个巴别鸟企业网盘的各种访问行为，确保每个操作都可以被追溯和审计。 记录的操作包括但不限于文件管理、权限控制、用户操作和部门管理。 关于巴别鸟日志的更多信息，可查阅：日志及报表 章节。 默认保存时间: 默认情况下，我们保存完整访问日志的时间段为90天。 这确保了足够的历史数据可供审计和检查。 可扩展的保存时间: 根据需要，管理员可以根据特定合规性要求扩展访问日志的保存时间（仅私有化系统支持）。 第三方日志管理系统 集成支持: 巴别鸟可对接第三方日志管理系统，以便将访问日志数据导入到外部日志平台进行进一步分析和长期存储。 安全管理员角色 安全保密员: 安全保密员具有高级的权限，可以在前台查看和管理所有部门的文件。 在企业管理后台，安全保密员具备以下权限： 制定公司安全策略（独有权限）。 管理组织结构。 成员管理。 权限管理。 安全审计员: 安全审计员可以在前台查看和管理所有部门的文件。 在企业管理后台，安全审计员具备以下权限： 查看企业安全策略。 查看组织结构。 查看成员权限。 查看权限管理。 查看文件访问日志。 安全性 数据隔离: 安全审计日志数据被严格隔离，只有授权的管理员可以访问和管理它们。 保密性: 安全保密员和安全审计员的角色都经过精心设计，一个负责安全策略，一个负责安全审计，互相监督，以确保数据的保密性和合规性。 扩展 自动化告警: 支持自动化告警机制，可添加监控项目，以在发现异常活动时及时通知超级管理员。 巴别鸟企业网盘的安全审计日志系统，包括功能、角色管理和安全性措施确保了数据访问和操作的可追溯性，并支持与第三方日志管理系统的集成，以进一步提高安全性和合规性。 安全性审查和测试 渗透测试 测试委托: 巴别鸟企业网盘会定期自己进行渗透测试或委托第三方机构，如绿盟科技，进行渗透测试，以评估系统的安全性。 渗透测试的目标是使用前沿的攻击技术，成熟的黑客攻击手段，以及标准的软件测试技术，测试指定系统的安全性，发现潜在的安全漏洞和风险。 测试阶段: 渗透测试包括以下流程： 信息收集：测试人员进行必要的信息收集，如IP地址、DNS记录、软件版本信息、IP段以及公开信息等。 渗透测试：测试人员根据信息收集阶段的结果，尝试入侵网络和系统。成功的情况下，可能获得普通权限。 缺陷利用：测试人员尝试提升权限，以获取对系统的完全控制权。在必要时，他们可能会回到信息收集阶段重新开始。 成果收集：测试人员对之前阶段发现的问题，如弱点和漏洞进行分类整理，并集中展示。 威胁分析：测试人员对发现的问题进行威胁分类和分析其潜在影响。 输出报告：测试人员根据测试和分析的结果，编写直观的渗透测试服务报告。 渗透测试的主要目标： 发现系统中的安全漏洞和潜在风险。 评估系统的安全性，包括身份验证、访问控制、数据保护等方面。 提供改进建议，以加强系统的安全性。 测试的结果将有助于我们采取适当的措施来修复发现的问题，提高系统的整体安全性。 最佳实践 巴别鸟企业网盘将定期进行渗透测试，以保持系统的安全性。 使用自动化工具和手动测试相结合，以提高渗透测试的全面性和准确性。 测试完成后根据报告及时整改，以确保系统的安全性。 未来扩展 我们将继续改进渗透测试流程，以适应不断演进的安全威胁。 考虑引入高级分析工具，以更深入地评估系统的安全性。 安全漏洞扫描 为了维护巴别鸟企业网盘的安全性，我们定期进行安全漏洞扫描。这项措施旨在自动化地检测系统中的潜在安全漏洞，以及可能导致安全威胁的问题。我们依托专业的扫描工具（例如：Qualys、Rapid7 InsightVM、OpenVAS）来确保系统持续保持在一个高度安全的状态。 扫描过程 安全漏洞扫描包括以下关键阶段： 定期扫描: 我们定期（通常是按计划的时间间隔）对系统进行安全漏洞扫描。 扫描工具自动化地执行一系列测试来发现潜在的漏洞。 扫描目标: 安全漏洞扫描的目标包括系统中的应用程序、操作系统、网络设备等各个方面。 扫描确保系统的整体安全性。 扫描结果: 扫描工具将识别并报告系统中发现的漏洞。 报告会包括漏洞的类型、严重程度以及可能的修复建议。 修复措施: 基于扫描结果，我们采取必要的修复措施来解决发现的漏洞和问题，以确保系统的安全性。 巴别鸟安全相关功能 主要功能模块 数据传输模块 数据传输模块是巴别鸟企业网盘的核心组成部分，负责管理上传、下载、同步盘和映射盘的数据传输。这一模块采用多种技术来确保数据的安全性、可靠性和高效性。 技术特点 文件分块: 数据传输模块采用文件分块技术，将大文件分成小块，以便更有效地传输和存储。这不仅有助于减少网络流量和服务器资源的消耗，还支持断点续传和增量上传下载。 哈希验证（秒传）: 在数据传输过程中，哈希验证用于确保文件的完整性。每个文件块都有相应的哈希值，服务器和客户端会相互验证这些哈希值，以检测是否有数据损坏或篡改。 同时，如果存储系统中已经有相同哈希码的文件，该文件就不用再次上传。实现秒传功能。 SSL传输: 数据传输模块使用SSL（安全套接层）协议来加密数据传输，以确保数据在传输过程中的保密性和安全性。这对于敏感企业数据的传输至关重要。 断点续传: 巴别鸟企业网盘支持断点续传，允许用户在传输中断的情况下从上次中断的地方继续上传或下载文件，而无需重新开始整个过程。这节省了时间和带宽。 增量上传下载: 数据传输模块还支持增量上传和下载，允许用户只传输发生更改的部分的文件分块，而不是整个文件。这在大型文件和频繁同步的情况下非常有用。 优势 数据完整性: 文件分块和哈希验证确保了数据的完整性，降低了数据损坏或篡改的风险。 数据安全: SSL传输提供了数据的端到端加密，确保数据在传输过程中不会被窥探或窃取。 效率: 断点续传和增量上传下载提高了数据传输的效率，节省了时间和带宽。 节约存储空间： 使用文件哈希码技术可以在磁盘上只存储一份相同哈希的文件。无论文件路径、文件名如何变化，或者在网盘中有多少个文件副本，文件实际存储空间就只占用一个文件的容量。（去重存储） 高速上传： 相同哈希值的文件不需要再次上传，如上传网盘上已存在的文件，检测到同样哈希值就会自动标记为上传成功，无需再次上传。 数据传输模块是巴别鸟企业网盘的关键组成部分，通过采用这些技术特点，它确保了用户可以安全、高效地上传、下载和同步其文件。这一模块的功能是使巴别鸟企业网盘成为一个可信赖的数据管理平台。 新建模块 新建模块主要负责文件、部门、项目、模版、文件夹的创建。在巴别鸟中可以做到无需上传文件就直接新建文件进行工作。 文件的新建 Office文件 巴别鸟支持在线创建空白word文档、Excel文档、PPT文档。 使用客户端新建会默认打开本地office相应组件创建并编辑文档。 在网页上新建会使用在线office创建并编辑文档。 Office文档都可以使用在线编辑（无需安装office）或使用客户端选择本地编辑（使用电脑上安装的office编辑）。 在线编辑支持多人实时协同编辑。 使用客户端调取本地office编辑时文档会自动锁定编辑，防止其他人在编辑时也编辑该文档造成冲突。 文本代码类文件 巴别鸟文本编辑器可在线创建并打开所有的文本类文件，如RTF、TXT、HTML、MD、CSS… 为了客户使用方便，公有云版本仅支持新建TXT和MD（markdown文件），私有云用户如需要其他格式的文本文件创建可以要求开放。 文本编辑器不同于在线office，不支持协同编辑，但可以在线编辑文本类文件。 思维导图及流程图。 巴别鸟自带思维导图模块，可以在线新建及在线编辑思维导图文件。 思维导图文件默认保存为KM格式。也可以导出为KM、TXT、MD、SVG、PNG、Xmind格式。 巴别鸟也可选支持创建流程图，但需要购买相应的模块授权（非标准版默认自带）。 其他第三方模块。 符合WebAPI的互联网应用理论上都可以对接巴别鸟并新建文件。巴别鸟提供第三方应用对接服务。 从模版创建 不少客户需要大量创建相同结构的文件夹或从某个特定模版（如企业PPT模版）创建文件。巴别鸟支持从模版创建文件夹和文件。 创建模版。 拥有部门文件管理权限的人可以在新建菜单里创建模版。 点击创建模版后会生成一个模版文件夹，模版文件夹类似于普通文件夹，可以拖动文件到文件夹中上传、新建文件夹及部门。 在模版文件夹根目录中上传的文件即成为文件模版，在模版文件夹中创建的文件夹就是文件夹模版。如下图： 图：在模版文件夹中显示 图：在新建模版时显示 从模版创建。 有创建文件及文件夹权限的部门都可以新建时选择模版快速创建和模版一致的文件或文件夹。 新建部门、项目 使用新建功能也可以创建部门和项目。 创建部门。 只有在企业文件根部门下才能创建部门，部门文件属于企业，超级管理员能看到根部门和整个文件树。 拥有子部门管理权限的用户（默认部门经理角色）可以创建子部门。 部门文件夹可以新增部门成员，并完成部门级别的管理。 只有加入部门的成员（部门成员）及上级部门拥有“查看子部门文件”权限的成员才能访问部门文件。 部门成员由在该部门的角色决定基本权限。 可以用文件权限管理的方式针对文件（文件夹）做权限管理 项目。 用户可以在个人文件或企业文件的部门文件夹下创建项目。 项目可以跨部门、跨企业邀请项目组成员，甚至可以邀请企业外的非注册用户。 拥有个人文件的人都可以创建个人项目，要在部门下创建项目用户角色需要有“创建文件夹/项目“权限。 项目文件夹中支持创建子项目。 项目文件夹的上级一定是个部门或者是个项目，这意味着不能在普通文件夹下创建部门。 项目创建者默认为项目管理员，项目是可以转交的，可以把项目管理员转交给其他成员及其他部门。 项目内成员的权限由创建项目时指定。项目相对是一个独立的共享文件夹。 新建普通文件夹 个人文件下创建文件夹。 用户可以在个人文件下可以任意创建文件夹，并自行管理。 企业文件下创建文件夹 企业文件下需要在部门中创建文件夹（所有的文件夹都有归属部门）。 在所在部门中角色具有“创建文件夹/项目“权限的用户可以创建文件夹。 只要角色具有“创建文件夹/项目“权限的用户可以在部门中任意普通文件夹中创建子文件夹。 文件管理 简介 文件管理模块是巴别鸟企业网盘的核心功能之一，用于用户管理和操作文件及文件夹，并根据权限推送给用户不同的文件列表。也是用户使用网盘的主要界面。该模块提供了广泛的功能，以满足企业用户对文件的管理和组织需求。 技术特点 A．文件访问与组织 分页载入技术: 文件管理模块使用分页载入技术，由服务器端数据库进行文件的排序查询操作，并把文件列表返回前台进行分页载入。这样一个文件列表可以分页载入几十万行数据，确保用户能够高效载入和浏览大量文件，而不会影响性能和用户体验。 树状展示文件列表: 巴别鸟支持树状展示文件列表，使文件的组织结构更加直观，用户可以轻松导航和管理文件夹。 权限控制: 根据用户的权限不同，文件管理模块会动态显示适当的列表项目，不同用户看到的文件列表内容根据权限不同而不同。以确保只有授权用户可以查看、编辑或删除特定文件和文件夹。 B. 文件排序和快捷操作 多维度排序: 支持多维度排序，用户可以按照文件名称、最近版本、文件大小等不同维度进行排序。 文件名排序: 不同于大多数网盘应用，巴别鸟文件名排序支持多位数字按顺序排序，使文件名包含数字编号的文件能够准确排序。（大部分网盘文件名排序仅首字母排序如：1、2、10、3、4，但在巴别鸟可以正确显示排序为：1、2、3、4、10） 自定义全局排序: 用户在设置里可以自定义适合自己的全局使用的排序方式，同时系统会记住上一次用户在文件夹选择的排序方式，下一次打开文件夹也按上一次的排序显示。 C. 文件展示和详细管理 列表模式和瀑布流模式可切换: 支持列表模式浏览文件夹，同时可以切换为瀑布流模式预览。 支持瀑布流模式浏览文件夹（文件缩略图），使文件的浏览更加流畅和直观。 图片较多的文件夹会自动适配为瀑布流模式显示。 文件详情页面: 每个文件和文件夹都有详细的详情页面，用户可以管理文件信息，增加文件注释，查看文件访问日志，对文件访问进行统计并生成报表。 文件详情页面也能管理文件的版本。 评论区: 每个文件或文件夹都自带评论区，支持用户评论和@提及其他用户，促进团队协作和反馈。 文件关联: 支持文件关联文件，允许用户在相关文件之间建立连接，以便更方便地访问相关信息。 文件关注提醒: 用户可以提醒有权限查看文件的人关注文件或文件夹，确保重要文件不会被忽视。 D. 高级搜索和筛选 高级搜索 巴别鸟支持高级搜索功能，可以根据关键字、全文内容、时间、文件格式、上传者、搜索范围、搜索类型等维度进行高级搜索。 搜索 巴别鸟也支持全文搜索，可搜索文件内容里的关键字。 也可使用文件名搜索、标签搜索找到对应文件 搜索的结果可以通过筛选的方式再次搜索或筛选 筛选功能: 可以根据文件标签、类型、文件说明关键字、大小、版本、上传者、照片元数据等进行筛选，以快速定位所需文件。 文件标签和分类: 用户可以给文件打标签，以更好地组织和分类文件。 标签可以有企业统一管理，以保证标签符合规范。 左侧栏可以加入标签快捷方式使用。 常见文件管理功能 A. 文件传输和操作 上传和下载文件: 用户可以上传和下载文件，确保数据的灵活传输。 支持文件夹拖动上传，以方便大批量文件的传输。 浏览器支持文件夹打包下载（少于100个文件或小于500MB大小的文件夹） 客户端支持文件夹直接下载（传输列表） 文件和文件夹的新建: 用户可以新建各类文件和文件夹，同时支持从模版新建文件或文件夹，以提高工作效率。 文件复制和移动: 用户可以复制和移动文件或文件夹，以方便组织文件。 支持将文件或文件夹复制到指定目录，以便文件的备份和管理。 文件归档: 用户可以将文件归档到档案库，以便长期保存和检索。 文件置顶: 个人文件支持将文件或文件夹置顶，以便快速访问重要文件。 部门或项目管理员可以置顶部门文件或项目文件，方便部门成员和项目成员快速访问重要文件。 创建文件或文件夹快捷方式: 用户可以创建文件或文件夹的快捷方式，以方便快速访问。 上传新版本: 用户可以上传新版本的文件，系统会自动检测重名文件并提供是上传新版本还是重命名文件的选择。 点击上传新版本按钮可以直接上传新版本。 文件打印为加水印PDF: 开启水印的时候，支持将文件打印为加水印的PDF文件，以确保文件的传播安全性和保密性。 锁定文件: 文件使用客户端编辑时会自动锁定防止冲突。 用户也可以在文件列表中手动锁定文件，以防止其他用户的编辑和冲突。 文件预览: 支持大多数文件预览，以快速查看文件内容。要了解更多可查看 预览与转码 章节。 文件列表展示缩略图: 文件管理模块可以在文件列表中展示文件的缩略图，使文件的浏览更加直观。 批量文件上传下载: 巴别鸟提供客户端专用的上传下载模块，支持批量文件的上传和下载，同时提供传输文件列表展示。 查看文件详情及版本管理: 巴别鸟有专门的文件详情界面。在文件详情里可以添加文件说明，查看文件基础信息，图片文件可以查看元数据，同时还可以在详情里查看文件日志及文件访问、使用情况，管理文件的版本。 B. 文件安全和权限控制 文件访问控制： 部门管理员或项目管理员可以设定文件访问控制，精确的控制每一个文件或文件夹针对每一个用户或某个角色的访问权限。 文件访问控制的优先级高于成员的部门角色权限。譬如：一个部门成员角色拥有某文件的编辑权限，但部门管理员使用文件访问控制把该成员对该文件的权限改为“不可见”，该成员将不能访问该文件。 文件分享: 支持分享文件和文件夹，允许用户设置详细的访问权限，以控制文件的访问。 文件快照分享: 针对只想分享当前版本的需求，用户可以创建文件的快照分享，快照分享不会受文件内容更新而改变，保持建立快照时的版本。 版本管理 版本管理概述 版本管理是巴别鸟企业网盘的重要功能之一，它允许用户跟踪和管理文件的不同版本，确保文件的历史记录和更新能够得以保留和查看。巴别鸟的版本管理功能非常强大，支持多种更新方式以及版本的回滚和查看。 技术实现 版本管理使用文件分块和增量保存技术来存储文件版本。这意味着每次文件的更改都会生成一个新的版本，而这些版本仅存储所做更改的数据块，以减小存储需求并提高效率。企业管理员可以在企业控制台中设置文件版本的保存数量和保存时间，以控制版本管理的策略。 版本管理功能使用户能够灵活管理文件版本，从而确保文件的完整性、历史记录和安全性。版本管理是巴别鸟企业网盘的一项核心功能，旨在提供卓越的用户体验和数据安全性。 版本更新方式 巴别鸟允许用户使用多种方式更新文件版本，包括： 手动上传新版本: 用户可以右键点击文件，选择上传新版本，手动上传新文件，并将其保存为文件的新版本。 同名文件检测: 上传时巴别鸟可以检测到文件名相同的文件，用户可以选择将新文件上传为已有文件的新版本。 客户端编辑保存: 如果用户使用客户端编辑文件并保存，巴别鸟将保存所做的更改作为文件的新版本。 在线编辑保存: 如果用户在网页上使用在线编辑功能编辑文件并保存，也将生成新版本。 同步文件夹编辑: 巴别鸟客户端会监控同步文件夹的更新，在同步文件夹中编辑或覆盖文件并保存会生成新版本。 映射盘编辑: 编辑映射盘中的文件并保存，更新的文件也会保存为新的版本。 版本管理功能 巴别鸟版本管理模块具有以下功能： 版本回退: 在文件的版本列表中，用户可以选择将旧版本置为当前版本，实现版本回退的功能。 版本下载: 用户可以选择下载历史版本，以便访问以前的文件版本。 版本预览: 版本管理模块允许用户在点击旧版本文件时进行预览，以查看该版本的内容。 版本对比： 在巴别鸟预览器预览文件时，可以选择文件对比功能，该功能支持选择旧版本和新版本进行对比。 版本日志: 用户可以为每个文件版本添加日志，以记录版本的重要信息和更改历史。 企业控制 巴别鸟企业网盘的版本管理功能允许企业管理员在企业控制台中进行高级设置，以满足企业的特定需求。企业管理员可以根据公司政策和合规要求，设置文件版本的保留数量和保留时间，以满足不同文件类型和部门的需求。 这样的版本管理系统保障了文件的数据一致性、可追溯性，以及用户数据的完整性。同时对勒索病毒这类改变文件可读性的病毒具有强大的防护性，因为勒索病毒更改文件需要更新的文件，而更新的文件将形成新的版本，用户只要回退版本就能拿到被攻击前的文件。 搜索 搜索模块概述 巴别鸟企业网盘的搜索模块是一个关键的功能，它基于强大的Elasticsearch技术和数据库查询技术开发，旨在提供高效、精确和全面的文档搜索功能。搜索模块不仅支持全文搜索，还可以搜索文档的说明、注释和文件名，满足不同用户的搜索需求。 带权限判断的搜索 巴别鸟的搜索模块不仅具备强大的搜索功能，还采用高级权限管理技术，动态判断用户权限，确保用户只能看到其权限范围内的文件。搜索结果是根据用户的权限动态生成的，这意味着用户共享的文件中，只有用户有权限查看的文件才会被搜索到。这是一项关键的技术，特别在企业环境中，权限是随时变化的。 技术基础 Elasticsearch: Elasticsearch是一款开源搜索引擎，它以高效的分布式架构和强大的全文搜索能力而闻名。巴别鸟使用Elasticsearch作为核心搜索引擎，以支持全文搜索和高级查询功能。 数据库查询: 除了Elasticsearch，搜索模块还利用数据库查询技术来搜索文档的元数据和标签信息，以提供更全面的搜索结果。 文档解析: 搜索模块使用文本提取技术，可以从各种类型的文件中提取文本信息。这些提取的文本信息用于搜索引擎的索引和查询。关键字抽取。 分词优化: 巴别鸟进行了大量的分词优化工作，特别针对中文词汇，以提高搜索引擎的分词准确性和性能。中文分词的优化对搜索结果的准确性起到关键作用。 搜索功能 巴别鸟搜索模块包括以下主要功能： 全文搜索: 用户可以执行全文搜索，查找文档中的文字内容，以找到与关键字相关的文件。 文档描述和注释搜索: 搜索模块支持搜索用户添加到巴别鸟的文档的说明和注释，使用户可以更轻松地找到特定信息。 文件名搜索: 用户可以进行精确的文件名搜索，以查找特定文件。 标签搜索: 可进行标签的搜索、查询、分类显示 高级搜索 巴别鸟支持高级搜索功能，可以根据关键字、全文内容、时间、文件格式、上传者、搜索范围、搜索类型等维度进行高级搜索。 性能优化 搜索模块对服务器性能要求较高，因此对于私有化部署的用户，建议将搜索模块部署在独立的虚拟机或服务器上，以减少对其他模块的性能占用。 未来发展 未来版本的巴别鸟将继续改进搜索模块，结合AI技术，例如ChatGPT，实现文档内容的问答式聊天对话搜索，为用户提供更智能的搜索体验。目前基于AI的文档分析及客服系统“智巢AI”已经上线，详情可查阅智巢AI章节。 搜索模块的不断改进将有助于用户更快速、准确地找到所需的文件和信息，引入AI系统后，用户可以用问答的形式获取信息，并能交叉多个文档的内容得出完整的结论，能大幅度提高生产效率和工作效率。 office在线编辑 在线编辑模块概述 巴别鸟企业网盘是OnlyOffice多年的官方合作伙伴，巴别鸟企业网盘的在线编辑模块基于OnlyOffice技术研发并优化了中文字体的载入和显示问题。巴别鸟在线编辑器支持多种文档格式，包括Microsoft Office（Word、Excel、PPT）和WPS Office。 巴别鸟和OnlyOffice的合作详情可以参见OnlyOffice官方网站： https://www.onlyoffice.com 技术基础 在线编辑模块的技术基础包括： OnlyOffice编辑器: OnlyOffice是一个强大的在线办公套件，支持多种文档格式的在线编辑。巴别鸟将其集成到网盘系统中，以提供优质的在线编辑体验。 中文字体优化: 为了克服OnlyOffice中对中文字体载入效率的不足，巴别鸟进行了优化，通过采用字库本地化技术，大幅提高中文字体的载入和显示速度，从而提升用户体验。 文档锁定: 巴别鸟同时支持客户端编辑和在线编辑，这意味着为防止文件版本冲突文件在线编辑时要锁定不能客户端编辑，文件客户端编辑时要锁定不能在线编辑。 主要功能 巴别鸟的在线编辑模块包括以下主要功能： 多格式支持: 用户可以在线编辑和查看Microsoft Office（Word、Excel、PPT）和WPS Office格式的文档。 协同编辑: 在线编辑模块支持多用户同时协同编辑文档，用户可以实时查看其他用户的更改，并共同编辑文档。这种协同编辑功能对于团队协作非常有用。 兼容性: 巴别鸟的在线编辑模块兼容微软Office，能很好的在网页上还原office的版式和字体。确保文档排版和格式在不同编辑器中打开的良好兼容性。 开放API: 巴别鸟开放在线编辑器的API，允许其他企业软件调用该API，将在线编辑功能集成到其他应用中。 用户体验 在线编辑模块的目标是提供用户友好且流畅的在线编辑体验。用户可以直接在网盘中打开需要编辑的文档，编辑完后即时保存，而无需离开网盘界面。这种无缝集成提高了用户的效率，使编辑文档更加便捷。 同时巴别鸟权限配置支持“仅在线编辑”，这意味着可以让一些用户仅能在线编辑文档但不能下载获取文档。 企业协作 巴别鸟在线编辑模块不仅适用于个人用户，还为企业提供了一个协同办公的平台。团队成员可以一起编辑文档，共享想法，并通过实时协作提高工作效率。 开放API 巴别鸟在线编辑器API允许企业将在线编辑功能集成到其自有软件或第三方软件中，使企业能充分使用在线编辑的能力。 其他在线编辑器 巴别鸟标准版还集成了其他在线编辑器，用于在线编辑及创建如MD文件，TXT文件甚至思维导图（如脑图）同时，巴别鸟也可以通过接入第三方API的形式集成其他支持HTML5的在线编辑系统，譬如可以对接微软office365或金山的web office（WPS）。 自带文本编辑器在线编辑。 巴别鸟自带的文本编辑器可以编辑及预览如：TXT、MD、RTF等文本文件，同时也能编辑CSS、JS、JSP…等代码文件，便于用户快速创建文档记录。 自带脑图（思维导图）编辑器。 巴别鸟自带思维导图模块，可以在线新建及在线编辑思维导图文件。 思维导图文件默认保存为KM格式。也可以导出为KM、TXT、MD、SVG、PNG、Xmind格式。 巴别鸟也可选支持创建流程图，但需要购买相应的模块授权（非标准版默认自带）。 客户端编辑 客户端编辑概述 巴别鸟企业网盘提供了强大的客户端编辑功能，用户可以轻松调用本地编辑软件对云端文档进行编辑，编辑保存后文件会自动上传到云端。这个功能不仅提高了用户的便捷性，还有助于避免文件版本的冲突，从而提高工作效率。 在客户端文件列表要编辑的文件上点击右键，选择编辑即可打开客户端编辑。 客户端编辑的实现原理决定了只要本地有编辑程序，所有类型的文件都可以进行客户端编辑。 技术实现 客户端编辑功能的实现技术包括： 客户端集成: 巴别鸟的Win客户端和Mac客户端均支持本地编辑软件的调用，这使得用户可以直接在本地软件中打开并编辑云端文件。 缓存管理: 客户端编辑使用缓存技术，把需要编辑的文件从云端缓存到本地并调用本地应用打开。系统监测到正在编辑的文件更新就把更新文件作为新版本上传。良好的缓存管理技术能在保证效率的前提下节约用户本地的磁盘空间。用户也可以在巴别鸟右键菜单手动清除文件的缓存。 文件状态检测: 在进行客户端编辑之前，系统会检测文件的状态，包括文件是否已被其他用户锁定。这有助于防止多人同时编辑同一文件，避免版本冲突。 自动锁定和解锁: 当用户开始编辑文件时，系统会自动锁定文件，以确保其他用户无法同时编辑相同文件。编辑完成后，文件将自动解锁，同时生成一个新的版本，并将修改后的文件上传到云端。 版本冲突处理: 尽管存在锁定机制，但在某些情况下，如网络问题或长时间未编辑时可能出现文件版本冲突。巴别鸟提供了冲突处理界面，允许用户对比选择是使用云端版本还是本地版本作为当前版本。无论用户的选择如何，系统都会确保没有选择的版本也会上传至云端作为历史版本，以防止数据丢失。 主要功能 客户端编辑功能的主要功能包括： 本地编辑: 用户可以通过点击本地编辑按钮，将文件缓存到本地，并使用本地默认应用程序进行编辑。 只要本地有相应的应用程序，理论上巴别鸟支持所有文件的本地编辑。 自动锁定: 文件在编辑时会自动锁定，以防止其他用户同时编辑，从而避免版本冲突。 自动解锁: 编辑完成关闭应用后，文件将自动解锁，并生成一个新的版本，将修改后的文件上传到云端。 版本控制: 所有编辑和上传的文件都将生成新的版本，以便用户可以随时查看和还原以前的版本。 用户体验 客户端编辑功能提供了出色的用户体验。用户可以在本地编辑器中进行编辑，而不必下载文件编辑后再上传。同时不支持在线编辑或在线预览的文件格式也可以通过客户端编辑打开编辑或预览。这提高了编辑效率和工作流程的顺畅性。 技术挑战 客户端编辑功能的技术挑战在于检测文件的状态，自动锁定和解锁，以及文件版本的冲突处理。系统需要准确判断文件是否正在被其他用户编辑，同时在冲突发生时提供用户友好的解决方案。这些挑战需要综合考虑用户体验和数据完整性。巴别鸟客户端编辑是业内少有的能很好处理这些问题的功能模块。 分享及外发 分享功能 巴别鸟企业网盘提供了多种灵活的分享方式，包括邀请分享和链接分享，以满足用户的不同需求。 邀请分享： 邀请分享是一种将文件或文件夹分享给特定人员的方式。特点如下： 身份验证：被邀请者需要进行身份验证，可以通过巴别鸟账号登录或者接收验证码确认身份。 每个被邀请者可以独立管理权限，可设置权限有效期。这意味者同一个邀请分享，不同的被邀请者可以设定不同的访问权限。 权限控制：分享者可以自定义分享权限，包括查看、编辑、下载等权限。这有助于细化控制分享内容。 审批机制：如果用户没有分享权限，分享操作需要经过审批，确保只有授权的人员可以分享文件。 链接分享： 链接分享允许用户创建一个公开链接，供其他人访问文件或文件夹。特点如下： 允许匿名访问：分享者可以选择是否允许匿名访问。如果关闭匿名访问选项，访问者需要拥有巴别鸟账号才能访问。 快照分享：快照分享模式下，分享的内容是分享时的当前版本，即使文件内容更新，快照分享的内容也不会变化。 密码保护：用户可以设置密码，确保只有知晓密码的人能够访问分享链接。 有效期：链接分享可以设置有效期，确保文件不会永久公开。一旦有效期结束，分享链接将自动失效。 自定义设置： 在企业控制台中，管理员可以自定义分享权限、按部门设定分享行为（支持或禁止分享），按文件设定分享规则（禁止分享高密级文件），以及关闭整个企业的对外分享功能。 分享日志： 所有的分享行为和外界访问行为都有独立的日志，每个分享的访问日志都可以查询。你可以知道什么人什么时候访问了分享的文件或文件夹，分享文件更新版本会提醒用户。 统一管理分享： 部门管理员可以统一查看和管理整个部门所有被分享的文件，分享的个人文件也可以在“我分享的文件”栏目统一查看管理，确保不会有遗漏的分享在不知情的情况下泄露。 外发功能（发送文件） 外发功能是一种通过邮件或手机号将文件发送给其他用户以供直接下载使用的方式。外发不同于分享，仅用于接收方下载外发的文件，无需配置权限。特点如下： 发送文件：用户可以使用外发功能将文件发送到其他用户的邮箱或手机号，以便他们可以直接下载并使用。 发送文件功能也可以发送文件给内部用户，收到文件会有通知，点击通知就可以下载或转存文件。 无需权限：外发不需要配置权限，只要用户有分享和下载权限即可使用。 邮件或短信发送：外发可以通过电子邮件或短信发送文件链接，确保接收方可方便地获得文件。 快捷下载：接收方可以通过点击链接直接下载文件，简单便捷。 用户控制和企业策略 用户的分享权限可以由企业管理员进行控制，确保文件的分享和外发都受到严格管理。此外，企业管理员还可以通过企业控制台自定义分享规则和权限，以适应不同的企业需求。 安全性 分享和外发功能均受到严格的安全控制，保护企业文件不被未经授权的人员访问。管理员可以根据企业的安全策略，灵活配置分享和外发的权限和规则。 灵活性与便捷性 分享和外发功能提供了企业灵活性和便捷性，满足了不同用户及场景的需求。用户可以根据具体情况选择最适合的分享方式，从而更好地管理和共享文件。 预览器及批注、讨论 为了让用户能更方便的预览文件，并且可以在预览文件时进行协作讨论提高协作效率，巴别鸟开发了巴别鸟预览器BabelViewer，在巴别鸟上可以预览的大多数文件格式都可以用预览器打开，巴别鸟预览器不仅可以预览文件，还可以通过手绘、文字讨论、语音（仅手机APP支持建立语音批注）等方式在文件内容上和协作者进行交流。同时，巴别鸟预览器还支持版本对比，切换版本查看不同版本批注、批注管理、审批管理等功能。 技术架构 使用canvas开发及多图层技术 预览器基于Html5 Canvas技术开发，使用多图层技术，以在文件预览层上面增加批注和手绘图层，不影响文件内容但可以进行批注讨论和实时手绘。 实时协同模块 预览器的实时协同模块，保证多用户在文件预览时的批注讨论和手绘是实时展示的，这意味着用户可以边批注边讨论文档或设计稿件的问题。 批注点坐标系定位 巴别鸟预览器使用坐标系定位， 保证批注点在不同的分辨率屏幕下，不同浏览器尺寸下的位置一致。 适用的文件类型 巴别鸟预览器能打开绝大多数图片及office文档、PDF文档及矢量图形文件。具体支持的文件类型可参阅 预览转码章节里的 支持在线预览的文件类型 预览器类型 多页文档预览器 支持对多页文档的预览，如word、PPT、PDF等格式。针对多页文档提供适合多页文档的目录、放大、旋转页面等功能。 图片预览器 为更好的预览图片而设计。拥有鹰眼、放大缩小、显示原始比例、旋转等功能。 右键可以复制图片到剪贴版，方便在微信、邮箱里直接粘贴图片。 针对PNG等拥有透明度的图片，可以改变图片背景。 图形预览器 为预览CAD、SVG、单页PDF等矢量图形文件设计，支持鹰眼、分图层显示、更改背景、鼠标拖动区域放大、矢量放大。对SVG文件可以切换编码模式。 3D预览器 为预览3D文件设计，可以旋转、鼠标滚轮拉近放远3D文件、炸开图像、支持3D空间的批注。 批注种类 文字讨论区 文字讨论区可以在预览文件的任意区域创建（双击建立文字讨论批注）。 文件的协作者如果有查阅批注权限都可以看到批注，并参与讨论。 批注内容实时显示，一个文字批注讨论区相当于针对批注内容的群聊。 支持插入附件进行讨论，也支持@等聊天功能。 可以设定批注的可见性，如：仅企业成员可见、所有人可见、仅批注者自己可见。 文字标注 文字标注可以在文档内容或照片上添加标注 选定文字批注 针对有文字的文件，如word、PDF，可以选择一段文字进行批注。 特殊符号插入 针对特殊需求的稿件，可以插入修订符号或焊接标记（如CAD图纸） 建立图形批注 也支持使用图形框选批注，支持矩形、椭圆及箭头。 语音批注 巴别鸟移动设备APP可以建立语音批注。在网页和客户端可以查看（收听）语音批注，但不能创建。 手绘批注 支持在稿件或文档上实时绘制，参与者可以实时看到绘制的线条，并且标记手绘者昵称。 功能模块 批注管理模块 可以管理创建的批注和批注状态，查阅其他版本批注，并切换到相应的版本 评审工作区 巴别鸟可以在文件评审时使用批注，并显示评审的相关面板，让评审人员能更准确便捷的传达评审信息。 鹰眼 鹰眼可以在图像放大时显示图像视口所在的区域。 版本对比 巴别鸟预览器支持文件对比功能，也可以对比不同版本的文件。 文件目录 对于拥有目录的文件（word、pdf），巴别鸟也支持预览时显示文件目录。 文件评审 巴别鸟企业网盘提供了强大的文件评审功能，旨在帮助用户高效管理文件的审批和修订过程。文件评审是一种协同工作流程，允许用户发起文件评审，邀请评审人员查看文件，提供批注和建议，以最终确定文件是否需要修改或批准。 主要特点 多文件评审：支持同时评审多个文件，用户可以一次性发起对多个文件的评审，确保高效的审批过程。 文件锁定：文件在评审过程中会被自动锁定，以防止其他用户进行编辑或上传新版本，确保文件内容在评审期间不会被更改。 文件预览和批注：评审人员可以在预览文件时添加批注，填写评审意见，以提供详细的反馈。这有助于更好地理解文件内容和提供有针对性的建议。 评审流程：用户可以选择不同的评审流程，包括自由定义审批流程、使用预设审批流程，或限用特定审批流程。这允许不同部门根据其需求选择适当的审批流程。 多阶段审批：审批流程支持多个阶段，每个阶段可以设置一个或多个审批者。用户可以定义通过比例，例如，50%的审批者通过即可通过某个阶段。 邀请外部审批者：用户可以邀请外部成员（通过邮件或手机号）参与文件评审，以获得更多不同角度的反馈，譬如：论文答辩时邀请外部专家。 审批报表：每次文件评审后，会生成审批报表，记录每个阶段参与者的评审意见，以便审批结果的跟踪和分析。 评审签名：支持评审结束后在稿件上插入签名，并下载为PDF。 我的评审栏目：用户可以在“我的评审”栏目中查看和管理与自己相关的所有评审文件的各个阶段，包括发起的评审和邀请参与的评审。 技术架构 文件评审功能的实现涉及以下技术和模块： 评审流程定义：后台定义不同的评审流程，包括阶段设置、审批者选择、通过比例设定等。这些流程可供前台用户选择。 部门特定审批流程：不同部门可以选择不同的审批流程，根据需要选择自由定义、预设或限用特定审批流程。 多阶段审批：可实现多阶段审批，每个阶段具有不同的审批要求，包括审批者的选择和通过比例。也可以设定某阶段是否能跳过。 外部审批者邀请：支持邀请外部成员参与文件评审，通过邮件或手机号进行邀请。 审批报表：生成审批报表，记录每个阶段的评审意见，以便审批结果的跟踪和分析。 文件评审的优势 文件评审功能有助于用户高效管理文件的审批和修订过程，确保文件内容的准确性和合规性。用户可以通过文件评审，确保文件经过充分的审查和讨论，以满足其工作需求和合规要求。这个功能的引入增加了文件协作和管理的深度，为用户提供了更强大的文件协作工具。 权限管理 巴别鸟企业网盘的权限管理是其核心功能之一，它贯穿整个系统，确保用户能够安全、合规地访问和管理文件。巴别鸟权限体系包括角色权限和文件权限两个主要方面。 角色权限 定义角色：巴别鸟允许在企业内定义不同的角色，每个角色可以包括一组特定的权限，用于控制用户在部门文件夹的访问和操作。这些角色可以根据部门管理需求进行创建，例如“部门管理员”、“部门成员”等。 部门角色权限：每个部门成员可以根据其在不同部门的角色分配不同的访问权限。这意味着用户可以在不同部门享有不同级别的权限。 灵活管理：巴别鸟的角色权限支持多个部门角色，并且可以在不同部门内同时使用相同的角色。角色的权限内容更改后，使用相同角色的成员的权限也会相应更改。 权限组合：巴别鸟角色权限支持30多种可选权限进行组合，以实现精细化的用户权限控制。这些权限涵盖了各种访问和操作行为，如预览、上传、下载、编辑等。 角色可选权限列表： 文件权限 自定义权限：文件权限也可以在后台自定义，用户可以选择特定权限类型和名称。这些自定义文件权限将用于文件分享、项目管理和文件权限控制。 文件访问控制：文件访问控制允许部门成员在文件和文件夹上设置具体的访问权限，以覆盖部门角色权限。这意味着可以更精确的控制部门里某个文件或文件夹的访问行为，文件访问控制仅适用于部门成员和项目成员。 高优先级：文件访问控制的权限具有较高的优先级，如果设置了文件访问控制，将覆盖成员的部门角色权限或项目权限。用户可以根据需要设置文件的访问权限。 部门文件和文件夹控制：用户可以为部门文件和文件夹启用文件访问控制，以控制特定文件或文件夹的访问权限。 有效期：文件访问控制可以设定有效期，到有效期后，文件访问控制的约束失效。譬如：给某个没有文件编辑权限的部门成员该文件的编辑权限，有效期3天，3天后文件访问控制赋予的权限就会失效，部门成员对文件的权限就变成成员角色的权限。 总结 巴别鸟企业网盘的权限管理是一个全面的系统，可以满足企业不同部门和项目的特定需求。角色权限和文件权限相互配合，确保用户可以精确控制文件的访问和操作。这一功能有助于提高安全性、合规性和工作效率。 同步 概述 文件同步是巴别鸟企业网盘最受欢迎的功能之一。它允许用户将本地任意文件夹同步到云端或者把云端任意文件夹同步到本地，实现云端和本地文件的实时同步。这个部分包含了以下关键功能： 同步管理：巴别鸟支持创建多个同步，并可在同步管理列表里统一管理。 多人协作：巴别鸟同步是为多人协作而设计的。它自动锁定文件，防止多人同时编辑造成冲突，还有冲突处理机制和版本管理。 和权限一致：巴别鸟同步会判断用户的权限。没有下载权限的用户也不会因同步而下载文件，保证权限的一致性和闭环，这意味着，用户可以通过权限来设定哪些文件夹可以同步。 多种同步类型：巴别鸟支持多种同步类型，用户可以根据具体需求选择合适的同步方式： 双向同步：云端和本地文件夹保持内容一致，任何一侧的修改都将同步到另一侧。 单向向上同步：本地更新会同步到云端，但云端更新不影响本地。 单向向下同步：云端更新会同步到本地，但本地更新不影响云端。 强大技术优势：巴别鸟企业网盘同步功能拥有多项技术优势，确保性能和稳定性： 支持大规模文件夹：巴别鸟支持高达20万个文件的文件夹同步。 文件编辑锁定：编辑同步文件时，文件会自动锁定，以防止多人编辑引发冲突。 冲突处理机制：针对同一文件的编辑冲突，巴别鸟提供了冲突处理机制，确保文件版本的完整性。 版本管理：文件同步功能和版本管理配合，能保证本地的文件夹也不会因为误操作等原因被覆盖从而丢失内容，即使出现文件冲突，冲突的两个版本文件也都会得到保存。 异步情况下的错误处理：文件同步功能还包括对异步情况下的错误处理和修复。 使用方式 开启同步：本地文件夹右键菜单选择巴别鸟——同步该文件夹。 选择同步方式：用户可以在同步时选择合适的同步方式，包括单向同步、双向同步等。 权限配置：通过权限配置，用户可以实现更多的自定义同步方式，根据需要限制文件删除或其他操作。 多人协作：多人协作下，文件编辑时会自动锁定，以避免多人同时编辑造成冲突。冲突处理机制确保文件版本的一致性。 版本管理：文件同步功能支持版本管理，用户可以查看以前的文件版本并进行恢复。 总结 巴别鸟企业网盘的文件同步功能是一项出色的工具，可以实现云端和本地文件的实时同步。多种同步方式、权限配置、多人协作、版本管理等技术优势确保了高性能、稳定性和安全性。 虚拟映射盘 概述 虚拟映射盘：巴别鸟企业网盘引入了虚拟映射盘功能，提供了一种无缝连接云端文件的方式，在windows资源管理器或着mac的访达中都可以类似于访问本地磁盘一样访问映射盘，从而实现轻松访问云端文件的体验。 技术实现：巴别鸟虚拟映射盘使用了类似OneDrive、iCloud的技术方案，它在操作系统中创建了一个虚拟磁盘，将云端文件映射到用户的本地计算机上，使得这些文件在用户的文件浏览器中可见。 主要特点 本地访问云端文件：虚拟映射盘允许用户通过本地文件资源管理器或Finder等工具访问其巴别鸟企业网盘中的文件和文件夹。 无本地存储占用：与传统的文件同步方式不同，虚拟映射盘并不将云端文件实际存储在用户的本地磁盘上，因此不会占用本地存储空间。文件只在需要时进行缓存或下载。 在线访问：虚拟映射盘需要网络连接才能访问云端文件。文件图标实际上只是云端文件的链接，因此需要在线才能查看和操作这些文件，权限也和云端一致。 透明操作：用户可以像操作本地文件一样操作虚拟映射盘中的文件，包括打开、复制、粘贴、删除等操作。 自动同步：文件的更改会自动同步到云端，从而保持云端文件与虚拟映射盘中的文件的一致性。 关联文件：在巴别鸟映射盘中打开有关联文件的文件，会自动加载关联文件，实现和本地文件夹打开文件一样的效果。譬如：打开含有大量参照文件的DWG（AutoCAD文件）、或者有关联其他文件的Excel图表。 技术优势（对比WebDAV和SMB） 权限一致性：不同于WebDAV或SMB挂载（必须使用兼容WebDAV或SMB的权限规则），巴别鸟映射盘是直接调用操作系统底层文件系统实现的，可以实现和巴别鸟一致的权限控制。（譬如：只能预览但不能下载或另存为。）在WebDAV和SMB中，仅查看权限实际为只读，只要是可见的文件，用户都可以通过只读模式打开并获得文件，失去了对文件的管控。 更高的性能：巴别鸟映射盘直接对应巴别鸟服务器相关接口，没有转发和中间处理环节，可以直接获取服务器提供的文件列表以虚拟方式打开文件夹，所以能提供更高的性能，打开文件列表和查阅文件不会卡顿。使用WebDAV只能打开一个文件夹临时载入一个列表，文件夹文件数量超过一定数量（和设备性能及网速有关，一般数量是超过300个）就会发生严重的卡顿和访问缓慢。使用对象存储系统的超大文件夹WebDAV并不能很好支持。 更安全：巴别鸟映射盘能根据权限判断每个人可以查看的文件夹和文件夹中的文件，不同权限的人查看同一个文件夹看到的内容可以不同，SMB和WebDAV目前做不到。同时巴别鸟的文件分块加密存储于对象存储，但如果是分块加密存储的文件，使用WebDAV就需要分文件解密后才能获得文件列表，这意味着，支持WebDAV的产品要么数据存储没有加密，要么WebDAV性能极差文件数量超过一定范围即不可用。 可控性：不同于使用第三方软件挂载的WebDAV及SMB，巴别鸟映射盘为自主研发驱动器，对驱动器的操作、菜单及运行方式、功能实现都具有可控性，并且能对产品质量及使用体验一致性负责。未来也能有更多的功能扩展。 主流企业级解决方案：无论是微软的OneDrive、Google的Google Drive或是苹果的iCloud、BOX的BOX Drive还是国内主流互联网企业网盘厂商，都使用了类似巴别鸟映射盘的解决方案，而不是简单接入WebDAV（接入WebDAV只要做协议兼容并开放接入即可，实现简单，为什么主流企业级厂商还都花费大量精力自研映射盘呢？）。WebDAV主要应用场景还是不需要进行复杂权限判断也不需要存储加密并开放所有文件的个人或小团队使用。SMB的主要使用场景也是个人及小团队的开放文件共享（明文存储）。 应用场景 虚拟映射盘适用于需要频繁访问云端文件、但不想改变本地磁盘的使用习惯也不想占用本地存储空间的用户。这个功能使得用户可以像访问本地文件一样访问云端文件，并且在其他应用程序里如同打开本地文件夹一样访问网盘，不改变使用习惯，便于文件的管理和使用。 档案管理 巴别鸟企业网盘提供了强大的档案管理模块，用于统一管理和归档企业文件。这一模块旨在帮助企业更好地组织和保留关键文件，同时确保文件的安全性和可访问性。 主要特点 档案管理员：巴别鸟允许超级管理员指定一名或多名企业成员作为档案管理员。档案管理员负责管理归档的文件和档案库。 档案库：归档的文件存储在档案库的根目录中。档案库是企业的资料图书馆，用于长期保留和管理文件。 阅览室：档案管理员可以建立阅览室，将档案库根目录的文件移入阅览室。这样其他企业成员才可以借阅这些文件。 借阅权限：阅览室可以选择不同的借阅方式，包括公开、需要借阅、限定部门公开、限定部门内借阅等。借阅文件时，可以设定权限级别，如仅可阅读、可复制、可下载，并指定借阅时长。 文件归档：归档后的文件不可更改，确保文件的完整性和可信度。这对于长期保留法律和合规性文件非常重要。 档案库搜索：档案库拥有独立的搜索功能，只会搜索档案库内的文件。用户可以快速找到需要的归档文件。 文件隐私：没有借阅权限的非公开文件不会显示预览图，以确保文件隐私性。 技术架构 档案管理模块使用以下关键技术和模块： 档案管理员权限：超级管理员可以指定企业成员为档案管理员，允许他们管理档案库和阅览室。 阅览室设置：档案管理员可以创建阅览室并配置不同的借阅权限和可访问性选项。 归档和保留：文件归档后，需要确保其内容不可更改。这需要技术措施来保护文件完整性。 独立搜索：档案库拥有独立的搜索引擎，用于搜索档案库内的文件，确保用户可以快速找到需要的文件。 档案管理的优势 档案管理模块帮助企业更好地管理文件的归档和保留。通过档案库、阅览室、和不同的借阅权限，企业可以确保文件长期保留、有序管理，并能够满足合规性和法律要求。这一模块还可以作为知识库使用，帮助企业保存重要信息和知识。 日志及报表 巴别鸟企业网盘的日志与报表系统提供了全面的文件使用情况管理、监控、审计和追责功能。这一模块旨在帮助企业管理者及用户深入了解文件活动、访问情况以及系统使用情况，以支持合规性和安全性需求。 主要特点 文件日志：每个文件和文件夹都有独立的日志，详细记录了文件的生命周期内的各种操作，包括创建、阅读、修改、更名、分享、删除、权限更改等。甚至包括匿名分享操作以及访问者的IP地址。这些日志可以导出为Excel报表，用于审计和监控。 文件访问统计：文件详情页提供了文件批注数量、下载次数、打开次数、访问人数和访问人员的统计。 文件夹列表：可以导出文件夹内文件和子文件的列表为EXCEl文件，以便审计和管理。 文件评审记录报表：文件评审操作也被记录为报表，以支持文件评审的审计。 部门日志与报表：部门管理员可以查看整个部门的使用日志，包括文件详细访问日志、上传文件数量、创建子部门数量或项目数量的统计。此外，部门管理员可以统计及管理整个部门分享的文件以及更改过权限的文件。 企业级管理：企业管理员和安全审计员可以查看整个企业的使用行为，包括各个部门的日志和报表，并且还有访问日志和统计分析两个栏目统一查看及管理整个企业的使用行为。这有助于维护企业的合规性和安全性。 访问日志：访问日志记录了整个企业网盘的使用日志，包括用户在网盘中的每个操作。管理员可以进行详细的查询和导出报表。 统计分析：提供了统计分析图表工具，允许管理员查看不同部门的使用活跃度、文件数量、活跃文件排名、新建文件统计、上传文件数量统计以及流量使用统计等。 技术架构 日志记录：系统需要记录每个操作的详细日志，包括操作类型、时间戳、执行者、目标文件、IP地址等信息。 报表生成：管理员能够从日志数据中生成报表，通常以Excel格式呈现，以便审计和监控。 数据分析工具：统计分析工具用于分析和可视化数据，帮助管理员更好地了解系统使用情况。 日志接口：巴别鸟支持通过接口导出日志数据，以使用第三方日志管理及分析工具。 日志与报表的优势 日志与报表系统有助于企业实现以下目标： 合规性：帮助企业遵守法规和内部政策，确保文件操作的合规性。 安全审计：提供审计功能，允许企业检查和监视文件访问和操作，以发现潜在的风险。 性能优化：通过统计分析，帮助企业了解系统的性能瓶颈，以采取适当的改进措施。 用户行为监控：允许企业管理者了解员工的行为，包括文件访问和操作，以确保数据的安全性和保密性。 决策支持：通过数据分析，帮助企业管理者做出更明智的决策，包括资源分配和文件管理。 日志与报表系统是巴别鸟企业网盘的重要组成部分，提供了全面的文件使用情况管理和监控功能，以支持企业的合规性和安全性需求。 动态及通知 动态栏目 概述：巴别鸟企业网盘的动态栏目是一个信息流，用于展示与您有关的文件和用户的动态信息。它提供了一个实时的工作情况总览，帮助您跟踪同事的活动，包括文件的变更、批注、评论等。 实时信息流：动态栏目以实时信息流的方式呈现您和您的团队的协作活动，从而帮助您及时了解团队中发生的事情。 便捷互动：通过动态栏目，您可以直接访问与您有关的文件，回复批注，与同事互动，以更便捷的方式完成协作任务。 动态搜索：您可以搜索动态的历史内容，更精准的定位到相关的动态条目。 通知栏目 通知系统：巴别鸟企业网盘的通知系统用于发送各种与您有关的提醒和通知。这些通知可以以多种方式传达给您，包括邮件通知、手机应用程序通知、桌面通知等。 通知类型：通知系统涵盖了多种通知类型，如@提到您、文件更新通知、审批请求、文件授权请求等。这有助于您保持对各种工作流程的掌握。 个性化设置 信息类型设置：用户可以根据自己的需求在设置中自定义接收哪些动态和通知类型，以确保信息的准确性和有针对性。 应用场景 动态栏目和通知栏目帮助用户了解工作中的重要动态和通知，提高了协作效率，使用户能够更快速地回应同事的协作请求，回复评论以及跟踪文件的变化。 巴别鸟企业网盘的动态与通知栏目是关键的协作工具，它们提供了实时的协作情况总览和各种通知，使用户能够更有效地与团队协作，并保持对工作流程的了解。这些功能有助于提高协作效率，确保重要信息不被忽略。 讨论组 概述 讨论组功能：巴别鸟企业网盘为每个部门和项目创建了讨论组，作为部门或项目内部成员的群聊空间。讨论组允许成员在其中发布文本和图片，进行讨论，并分享附件。 成员互动：讨论组提供了一个方便的平台，使成员能够互相沟通、协作和讨论项目相关事项，从而增强团队合作和信息分享。 主要功能 信息发布：讨论组成员可以发布文本消息和图片，以实现实时的讨论和交流。 附件分享：成员可以轻松分享附件，如文档、表格和其他文件，以便共享和讨论。 可见性：讨论组中发布的信息对所属部门或项目的所有成员可见，从而确保信息共享。 应用场景 讨论组适用于部门内部和项目团队之间的信息交流和讨论。它们促进了实时协作，有助于解决问题、分享见解和跟踪进度。 总结 讨论组为部门和项目成员提供了一个便捷的协作平台，用于共享信息、讨论事务和协同工作。这些讨论组有助于加强内部沟通，提高团队的效率和生产力。 工作台 概述 工作台功能：巴别鸟的工作台是一个个性化的界面，允许用户将常用的文件夹、工作内容以及各种信息以卡片的形式集中在一个界面上展示。每个卡片直接呈现内容，可进行操作，用户可以根据需要自由调整卡片的位置和排序。 个性化：工作台提供了多个备选卡片，用户可以自由选择需要添加到工作台上的卡片，根据自己的需求进行定制。这使得用户能够在一个页面上获取与其工作相关的信息和功能。 主要功能 卡片展示：每个卡片代表不同类型的信息或工作内容，例如最近访问的文件、上传的文件、关注的文件、分享的文件、批注过的文件、标签云图等。 自定义图表：用户可以自定义图表或卡片，以便将特定项目、文件夹或其他信息添加到工作台上，以满足其独特的需求。 卡片排序：用户可以通过拖放方式对卡片进行排序，以便将最重要或最频繁使用的信息放在前面。 应用场景 工作台适用于用户需要集中管理和访问与其工作相关的信息和资源的情况。用户可以将常用的文件和项目放在工作台上，以提高工作效率。 企业管理后台（企业控制台） 巴别鸟企业控制台集中了管理员对整个企业进行管理的功能。企业管理员可以在企业控制台中配置企业网盘的各个选项、开启或关闭需要的功能模块、设定组织结构、自定义角色和权限，管理成员、设置水印、设定部门安全策略、iP访问策略、绑定账户和mac地址、监控网盘使用情况…. 主要栏目 企业配置：综合管理企业网盘的配置项，譬如空间分配、是否允许个人文件、允许的文件上传大小、历史版本有效期或历史版本数量、各种管理员分配、更改logo及登录背景、禁止或开启对外分享、是否接受邮件通知。各种企业配置选项里面都可以在企业配置栏目找到。 组织结构：统一管理和维护企业的组织结构及部门。能树状查看部门和管理部门。查看部门成员、分配部门空间、创建子部门、设定部门安全策略… 权限管理：创建角色和更改角色权限，同时可管理自定义文件权限。 成员管理：可以查找和筛选整个企业的成员账户，新增成员、批量导入成员、分配成员部门及角色、详细查看及管理每一个成员的信息及使用情况、成员离职一件交接、成员账户的增删改查、成员空间和流量的分配及限制。 标签管理：统一管理企业所使用的标签，添加标签和给标签分类，便于用户选择标签。 文件配置：添加文件审批可选流程，管理已经添加的审批流程。同时拥有文件黑名单功能，可以阻止特定类型的文件上传。 企业通知：创建企业通知，管理历史企业通知列表、发送企业通知。 分组管理：建立分组及管理分组。前台分享文件时可以选择分享给什么分组。 水印设置：管理文档的水印类型，水印参数调整，水印显示范围设定。 访问日志：管理及查询整个企业网盘的所有访问记录。可导出日志报表。 IP策略列表：可通过IP策略管理企业文件的上传下载行为。譬如：某个IP段禁止下载文件，回到某个IP段即可下载文件。 Mac地址绑定：可以把用户账号和特定设备mac地址绑定，让账号只能在绑定mac地址的设备上使用。也可以创建mac地址池。 统计分析：统计分析网盘的使用情况。包括系统活跃度、文件数量统计、活跃文件、一段时间内的新建文件数、每个月上传数、流量使用情况。 工作台推送：设定工作台的默认显示卡片。 系统配置（仅私有部署版本）：配置邮件服务器，绑定第三方SSO认证，设定第三方认证登录方式。 第三方账号同步（仅私有部署版本）：设置第三方账号同步时间，查询第三方账号同步记录。 可选模块（仅私有部署版本）：选择企业需要展现的功能模块，关闭某些功能模块。 监控预警：设定异常行为的预警，遇到异常行为通知管理员（譬如：用户大量删除文件） 传送文件配置：数据摆渡系统的配置，允许多套巴别鸟间进行数据摆渡。配置数据的接收端口及发送端口。 API 巴别鸟API模块负责巴别鸟开放API，私有云用户可以在企业控制台免费申请及开通开发者账号，获取开发者id、密钥几Token、并设定回调URL 回调URL设置规则：http://客户域名 /public/babelAuthResult.do 譬如：http://testqiyeban.babel.cc/public/babelAuthResult.do 设置路径：企业控制台——企业配置——开发者账号 访问以下链接获取最新API文档： https://www.babel.cc/p/api integration.do 第三方登录（SSO） 巴别鸟支持集成第三方登录（SSO）平台，以实现单点登录及统一登录。并且巴别鸟支持多个第三方登录平台集成。譬如：既可以企业微信扫码登录也可以OA账密登录、钉钉扫码登录。 SSO集成分为两个模块。第三方授权登录及第三方组织结构同步。其中第三方授权登录允许多个源进行授权登录。但第三方组织结构同步为了防止造成用户账户冲突，仅允许同步一个源。譬如：同步了OA系统的组织结构，但是支持OA和企业微信的SSO登录（OA和企业微信的的组织结构需要用一致的userID） 更多关于巴别鸟第三方登录的信息，可以查阅用户身份验证和授权（SSO）章节 数据摆渡 巴别鸟数据摆渡支持部署在密区的巴别鸟与部署在非密区的巴别鸟以安全并且带审批的方式互传数据。以实现在企业监管下的密区和非密区的数据交换。 关于巴别鸟数据摆渡的详细信息，可以查阅 巴别鸟数据摆渡 章节。 智巢AI 智巢AI是巴别鸟企业网盘的AI平台，包括智巢AI客服、智巢AI知识库和智巢AI文档助理三个主要模块。这些模块结合了大模型API和自定义训练，能够满足企业的智能客服、文件内容分析和问题回答需求。 智巢AI的三个主要模块 智巢AI客服：该模块充当企业的AI客服，巴别鸟企业网盘自己也用了该模块回答用户在巴别鸟网盘使用中遇到的问题。我们也向企业客户开放这个服务，企业可以将产品说明书、FAQ、客服文档等资料提供给智巢AI进行学习，并微调以满足企业客服需求。企业还可以将智巢AI的代码块嵌入其网站，快速建立对外智能客服系统。智巢AI客服能显著降低客服成本，节约时间和资源。 智巢AI文档助理：这一模块用于回答关于单个文档的问题。通过分析文档内容，智巢AI能够回答关于文档内容的各种问题，从总结到揭示关键发现。用户可以向AI提问，而不必亲自阅读冗长的文档，从而提高工作效率。 智巢AI知识库：这一模块允许企业为自己定制专属AI助手。智巢AI团队会根据企业的资料帮助准备训练集、调参，从而建立专属的AI模型，可以根据巴别鸟上不同权限的人提供权限范围内的答案。可以以问答的形式作为企业知识库助手。 技术解决方案 智能回答问题：智巢AI借助大模型和自定义训练，以保证准确性。它还利用小模型来辅助大模型的工作，减少瞎说话、不懂装懂或泄密等问题。此外，智巢AI遵循巴别鸟的权限管理机制，确保用户只能获取其权限范围内的答案。 自动学习：智巢AI可通过学习用户提供的文件来积累知识，为用户提供更准确的答案。所有参与训练的文档都是由用户指定并同意的，以确保数据隐私和合规性。 优势 客服成本降低：智巢AI客服可以显著减少企业的客服成本，无需大规模培训人员，AI可以随时提供答案。 快速问题回答：智巢AI能够即时回答用户的问题，提高了工作效率。 文件内容分析：智巢AI文档助理可以快速分析文档内容，帮助用户快速获取信息，而无需阅读整个文档。 自定义AI助手：企业可以根据自己的需求为智巢AI知识库定制专属AI助手，以满足特定的知识管理和问题回答需求。 权限管理：智巢AI能够根据用户权限提供不同范围内的答案，以确保数据安全和合规性。 自动化任务 面对日益增长的数字资产，传统的人工文件管理模式已难以满足高效流转的需求。巴别鸟推出的 “自动化任务”引擎，旨在将繁琐、重复的文件处理动作交由系统后台自动执行。通过建立“自组织、自规范”的智能流转体系，大幅降低人工干预成本，让团队将精力聚焦于核心业务创造。 自动化任务包含在标准版中，用户无需另行购买。 核心运作机制： 灵活的权限驱动： 依托平台极细颗粒度的权限管理体系，凡具备目标网盘或文件夹相应权限的用户，均可按需自主配置、开启或关闭特定的自动化任务。 多任务流串联 (Workflow)： 自动化任务并非孤立运行，支持多规则自由组合形成工作流。例如：文件上传后，系统可先触发“自动重命名”规范文件名称，随后立即触发“自动整理”将其归档至相关目录，实现多步骤一气呵成。 持续扩展的能力矩阵： 自动化引擎具备高度的扩展性。除了现有的基础功能外，平台将持续接入更多的自动化处理节点，以满足日益复杂的业务场景。 当前已支持的核心任务（包括但不限于）： 自动重命名： 按预设规则（如关键字替换、大小写转换）统一标准化命名。 自动整理与清理： 依据触发条件自动分类归档文件，或按策略定期清理空间。 自动转 PDF 与签章： 自动为源文件生成 PDF 副本，或在云端加盖企业签章。 批量创建文件夹： 通过导入数据模板（如 Excel）一键生成标准业务目录树。 多任务协同与执行流转权重 在复杂的业务场景中，一个文件夹往往会叠加配置多项自动化任务。为保障数据处理的逻辑严密性与安全性，系统底层预设了严格的自动化处理先后顺序 。 具体执行权重（数值越高越优先执行）规范如下： 自动清理文件夹（权重 10）： 系统最高优先级。如有符合条件的清理任务将率先执行，以避免对即将被废弃的无效数据投入后续算力 。 自动解压缩（权重 9）： 优先将打包资产释放，以便进入后续流转 。 自动更名（权重 8）： 在文件进入分类归档前，优先完成命名的标准化统一 。 自动格式转化类（权重 7）： 优先完成如转存 PDF、图片或音视频格式的转换任务 。 自动整理 / 排序（权重 6）： 作为流转的末端节点执行 。这意味着文件在被移动和分类前，均已完成了清洗、重命名与格式转换等核心前置标准化操作。 自动清理文件 (Auto Clean) 功能概述 在日常的跨部门协作或项目周期管理中，企业网盘内往往会不可避免地产生大量的临时数据、过程文件或短期流转素材。 “自动清理文件” 功能旨在为企业提供自动化的存储空间优化与目录瘦身方案。通过该功能，系统能够按照用户设定的特定规则，自动删除指定文件夹中的冗余文件，长效保持项目目录的整洁度并释放高价值的存储资源。 核心运作与配置规则 本模块通过严密的逻辑规则引擎执行文件的清理动作，确保数据处理的精准与高效： 目标目录锁定： 任务配置需明确指定应用该规则的目标文件夹。用户可选择将规则仅应用于新进入该文件夹的文件，或同时溯源应用于目录内已存在的历史文件。 多维规则触发： 支持基于特定规则对文件进行精准筛选与剔除。常见的判定规则可涵盖文件类型（如特定后缀的临时文件）、生命周期（如文件进入目录超过指定天数）等维度，实现高度定制化的清理策略。 工作流协同： 作为完整自动化流转的末端环节，自动清理可与其他任务无缝衔接。例如，在“自动转 PDF”任务完成后，系统可随即触发“自动清理”规则，将原始草稿文件进行统一清理，仅保留标准化定稿。 权限与数据安全控制 鉴于清理任务涉及文件删除这一敏感操作，该功能深度依托巴别鸟的极细颗粒度权限管理体系： 配置权限： 仅拥有该文件夹相应高级权限（如管理、删除权限）的协作成员，方可新建或修改自动清理任务，从源头杜绝越权操作造成的数据流失。 无感且安全的执行： 后台静默执行清理任务，减少对用户前端操作的干扰，同时严格遵循企业既定的数据合规与回收站保留策略，确保数据资产的绝对安全。 典型业务应用场景 设计与研发类项目： 在建筑设计或科研管理中，工作软件常会自动生成大量的备份或缓存文件（如 .bak 或临时渲染文件）。通过配置自动清理任务，可设定定期自动识别并删除特定后缀的无用文件，保持核心图纸与文献目录的纯净。 公共资料交换区： 针对企业内部设置的“临时中转站”或“临时分享区”，可配置按时间维度（如“保留 7 天后自动清理”）的自动清理任务，实现公共空间的自组织与自净化，降低运维管理成本。 自动重命名 (Auto Rename) 功能概述 在多方协作、多频次资料收集的业务场景中，由于操作人员习惯差异，文件命名往往缺乏统一规范，给后续的检索、归档与审计带来极大困扰。 “自动重命名” 功能允许系统对上传至指定文件夹的文件，按照高度定制化的预设规则进行自动化的名称重构 。该机制有效杜绝了因人为因素导致的命名混乱，确保企业数据资产入库即达标。 适用范围与权限控制 权限驱动： 该功能的启用严格依托于用户的操作权限。只要用户对目标文件夹（涵盖个人、部门、项目或素材库等各类文件夹）拥有“上传”及“重命名”权限，即可为其配置自动重命名任务 。 溯源处理： 规则不仅作用于新上传的文件，用户还可选择将其溯源应用于目标目录及其所有子文件夹中已存在的历史文件 。为保障系统性能与执行稳定性，批量溯源重命名的单次处理上限为 5000 个文件 。 核心规则引擎与配置维度 巴别鸟提供了一个高度灵活的可视化规则拼接引擎。用户可添加多个命名规则，并通过拖拽的方式对规则进行自由排序 。配置界面全程提供实时变化的“示例文件名”，帮助用户直观预览重命名规则的叠加结果 。 规则引擎支持以下多维度的命名元素： 标准属性变量： 支持提取并插入系统级变量，包括文件上传者、文件负责人、上级文件夹名称以及上传时间 。 多媒体元数据 (Metadata)： 针对图像等特定格式文件，系统可深度解析并提取其底层元数据作为命名依据，如拍摄日期、相机制造商/型号、镜头型号、尺寸以及 DPI/DPCM 等参数 。 自定义文本与连续编号： 用户可自由插入自定义文本内容 。在编号机制上，与传统的单次批量重命名不同，自动重命名具备状态记忆（延续性）。系统会自动读取目标列表中最后一个符合规则的编号，确保跨批次、跨时段上传的文件能够实现序号的无缝延续 。用户可精确设定编号的起始值、增量值及具体位数 。 原始名称的精细化修剪与防冲突机制 除了添加新前/后缀，系统同样支持对文件原有的名称进行深度结构化清洗： 名称修剪与替换： 可对原始文件名执行“替换特定内容”、“删除指定内容”操作 。此外，还提供一键“删除字符”功能，精准剔除文件名中的冗余空格、数字、引号、破折号及下划线 。 强制防冲突保护： 若用户在规则中选择完全删除“原始文件名”（即上传时不保留原名），为避免同名文件相互覆盖的风险，系统会强制要求并在规则链中自动追加一项“编号”规则 。 日期逻辑互斥： 在调用日期类变量时，用户可勾选“替换在文件名中检测到的日期” 。为防止逻辑冲突，在单一重命名任务中，该替换指令仅允许被某一时间变量（如“上传时间”或“拍摄时间”）勾选一次 。 全局格式化输出控制 在完成规则变量的拼接后，系统支持在输出端进行统一的格式化规范： 大小写标准化： 支持一键将拼装后的文件名转换为首字母大写、首字母小写、全部大写或全部小写，满足不同企业的视觉规范 。 字词分隔统一： 支持在各个命名规则模块之间统一插入标准化的分隔符（如空格、下划线或破折号），进一步提升文件名的机读与人读体验 。 自动转 PDF (Auto to PDF) 功能概述 在跨企业协作、外部资料分发以及项目定稿归档等业务环节中，PDF 格式因其跨设备显示的一致性与防篡改特性，成为了标准的文档交换媒介。巴别鸟的“自动转 PDF”功能，旨在建立一个自动化的文件格式标准化通道。配置该任务后，当文件被添加到选定的目标目录，系统将在后台静默触发转换引擎，将其自动转换为标准的 PDF 文件 。该能力大幅消除了人工逐一导出 PDF 的低效劳动，确保了数据对外输出与对内归档的规范性。 执行逻辑与边界条件 为保障平台底层计算资源的高效运转以及企业数据流转的安全可控，自动转换任务设定了以下执行逻辑与边界限制： 作用域与溯源处理： 该任务可向下覆盖，支持勾选应用于目标目录及其所有子文件夹中的文件 。此外，规则同样支持向历史数据溯源，可应用于目录内的现有文件，但为保障执行稳定性，单次溯源处理的文件数量被严格限制在 5000 个以内 。 系统性能保护机制： 为避免超大源文件在转换过程中长时间占用算力并导致任务队列阻塞，系统内置了文件体积阈值，即超过 30MB 的大体积文件将不会触发自动转换机制 。 存储空间自动释放： 针对“仅需保留定稿 PDF”的特定业务场景，用户可在任务配置界面勾选“转换成功后删除原文件”选项 。开启该策略后，系统将在确认 PDF 副本生成无误的前提下自动清理原始文件，从而大幅度优化网盘存储空间的利用率 。 广泛的格式兼容矩阵 巴别鸟自动转换引擎具备强大的多格式解析能力，支持将 32 种不同行业的主流业务文件自动化转储为 PDF 。用户可选择针对“所有支持的文件”执行转换，也可通过下拉菜单按类别精准勾选所需转换的扩展名 。具体支持的格式矩阵如下： 文档排版类： 全面兼容主流办公与出版软件产生的源文件，包括 doc、docx、ppt、pptx、wps、epub、dpt、indd、rtf、docm 以及 pptm 。 图片与影像类： 支持主流位图、数字底片及医疗影像格式的渲染转换，涵盖 jpg、bmp、jpeg、jpg2、png、psd、tif、tiff、raw、cr2、dcm 以及 heic 。 图形与工程图纸类： 深度适配设计与建筑工程领域的矢量及 CAD 图纸转换，支持的格式包含 ai、svg、eps、dwg、dwt 以及 dxf 。 自动整理文件 (Auto Organize) 功能概述 随着平台内协作数据的沉淀，如何保持底层“任意文件夹同步”架构与权限管控目录的整洁，成为了企业数字资产管理的关键。 “自动整理文件” 功能允许系统按预置的时间周期或内容特征，将文件自动分类并路由至相应的目标目录。该功能确保了海量文件在流转过程中的高度结构化，避免了人工归档的滞后性与错漏。 灵活的触发机制与作用域 用户可通过文件夹右键菜单中的“任务”选项 ，或左侧的自动化任务列表面板进入配置 。配置涵盖以下触发与作用规则： 事件驱动（默认）： 当文件被上传或者移动到指定的触发文件夹时，系统即刻响应并开始整理动作 。 周期驱动： 适用于集中式的数据归档场景，系统可按固定的周期（例如设定为每天 23:00）统一执行文件整理 。 历史溯源： 规则既可应用于新增文件及所有子文件夹，也可勾选“应用于现有文件”对历史存量数据进行批量溯源整理。为保障系统平稳，溯源处理单次不得超过 5000 个文件 。 核心智能整理规则引擎 系统提供三种高度自定义的分类规则，满足不同维度的数据归档需求： 1. 基于时间维度的结构化归档（按月 / 按年分类） 系统可按文件添加到网盘的对应年份或月份自动创建对应的子文件夹（例如“2025”、“2025 10”）并将相关文件移入 。 执行按年或按月分类时相同 ，系统具备按需建档的智能性，如果特定周期内（如某个月）没有产生文件，则系统不会冗余创建该月的空文件夹 。 2. 基于内容的智能路由（按关键字分类） 根据文件名中包含的特定关键字，系统将文件自动分发并移动至预设的目标文件夹 。 格式识别： 文件扩展名（如“jpg”）同样可作为关键字配置，实现特定类型素材的定向归集 。 多线并行路由： 用户可通过“添加关键字分类”按钮持续增加多条路由规则 。既支持将包含不同关键字的文件分别分发到不同的目录 ，也支持将多条关键字任务统一指向同一个目标文件夹 。 防重名与优先级控制： 关键字匹配严格按任务设定的先后顺序处理。例如，当文件名为“123ABC定稿.jpg”，若关键字列表第一项规则为“123”，第二项为“定稿”，则该文件将优先匹配“123”的规则并执行移动 。系统内置防重复检测，每个关键字仅允许输入一次，重复输入会触发“请重新输入”的错误拦截 。 同名冲突化解： 在执行文件移动与整理的过程中，如在目标文件夹内遇到重名文件，系统会自动在文件名后附加编号，以确保数据不被意外覆盖 。 创建签章 (E Sign) 业务场景与功能概述 在企业的合同审批、图纸会签及业务合规流转等关键环节中，具备防篡改属性的数字化签署是打通线上协作闭环的核心节点。传统的跨系统签署往往伴随繁琐的文件下载与格式转换。巴别鸟推出的 “创建签章” 功能，允许用户直接在云端网盘的工作流中对文件进行盖章与签署 。该引擎支持多种主流文件类型直接加载印签，并支持将签署完毕的文件一键导出为标准的 PDF 格式，从源头保障数字资产的安全、合规与不可篡改性 。 签章资产库与个性化配置 系统为用户提供了一个高度集成的数字印签管理控制台，确保电子签章资产的统一沉淀与快速调用： 多元签名采集： 在“签名设置”模块中，用户既可以调用终端进行在线“添加手写签名”，也支持直接“上传签名图片文件”（如含透明通道的 PNG 素材），以满足不同层级的签署合规要求 。 企业图章管理： 在“图章设置”模块，企业用户可按需上传业务专用的电子公章或合规图章图片 。 默认优先级状态： 针对拥有多个印签资产的用户，系统支持一键将其中的特定签名或图章“设置为当前使用”（默认印签） 。在后续的文档预览与流转界面中，系统将优先调用该默认印签，极大提升高频审批场景下的签署效率 。 智能自适应交互与沉浸式引导体系 为兼顾不同硬件终端的显示极限并降低用户的学习门槛，签章配置中心采用了多断点的智能响应式（Responsive）界面架构，并深度嵌入了多语言操作指引： 宽屏工作站模式（窗口宽度 ≥ 1120px）： 当用户在桌面级宽屏设备上操作时，系统不仅在左侧保留标准的签章配置面板，还会在右侧自动展开独立的视频教学区。该区域会自动加载并无感循环播放签章使用教程（播放完毕停顿 3 秒后重播），为用户提供“边学边配”的沉浸式体验 。 紧凑聚焦模式（窗口宽度 ＜ 1100px）： 当处于较窄的屏幕或移动端窗口时，系统会智能折叠右侧的视频播放区，以最大化保障核心签署设置区的视觉焦点 。同时，系统在界面底部提供“如何使用签章？”入口，用户点击后可唤起全屏教程播放 。 国际化双语支持： 考虑到跨国企业的协作需求，系统内置了本地化的教学视频库。除中文语言环境播放专属中文教程外，其他所有多语言版本均默认匹配并播放标准英文教程，保障全球业务团队的无障碍落地 。 批量创建文件夹 (Batch Create Folders) 功能概述与业务价值 在多项目并发或企业部门架构调整的业务场景中，由人工逐一建立复杂的标准目录树不仅耗费大量操作时间，且极易因人为疏漏导致目录层级错乱或命名不规范。巴别鸟提供的 “批量创建文件夹” 功能，允许用户通过外部结构化数据（如 Excel、CSV、TXT 文本）直接驱动云端目录的生成 。该功能可将标准化的业务目录模板瞬间转化为可落地的网盘文件夹阵列，极大提升了大型项目启动阶段的初始化建档效率。 标准目录阵列的大规模生成 该模块具备强大的数据解析能力与人工容错干预机制： 高并发支持： 系统支持通过导入 xls、xlsx、csv 或 txt 格式的文件，按换行符规则快速读取目录清单，单次批处理任务的上限高达 5000 行，满足绝大多数企业级数据结构的生成需求 。 可视化预审与动态干预： 在正式执行批量创建前，系统会完成数据解析并在界面中直观渲染出即将生成的文件夹列表与层级关系 。在此预览环节中，用户可直接通过鼠标右键或悬浮菜单，对特定的预设目录执行“创建子文件夹”、“重命名”或“删除”等即时修改动作 。这一“先审后建”的机制，确保了最终落地的目录树与业务需求绝对对齐。 项目级文件夹与权限的“一键部署” 当目标路径设定为部门文件夹或个人文件夹的根目录时，系统支持创建更为高阶的 “项目文件夹” 。该模式深度结合了巴别鸟的底层权限管理体系，实现了目录构建与成员权限配置的同步落地： 专属标准模板： 批量生成项目文件夹需下载并使用系统专属模板导入数据 。若上传的非标文件不符合解析格式，系统将严格拦截并提示重新上传 。 项目角色与权限预设： 模板不仅规范了“项目文件夹名字”，还支持直接关联账号系统预设“项目负责人”与“项目成员” 。 负责人指派： 填写的负责人 ID（支持手机号、邮箱或特定的工号格式）必须为已注册的企业成员；若该字段留空或填写的身份无法校验，系统将遵循安全保底原则，默认将当前创建任务的操作者设为项目负责人 。 成员自动化邀请与赋权： 用户可在模板中通过逗号分隔批量录入多位项目成员 。项目目录生成后，系统将自动向这些成员发送邀请通知，并为其赋予基础的“上传及下载”默认权限 ，彻底免除了建档后繁琐的逐一授权操作。 实时状态监控与智能容错机制 在执行大规模创建任务时，系统后台会以队列形式稳健处理，并在前端提供全方位的进程监控与异常修复闭环： 全局进度追踪： 创建过程中，列表节点会实时更新其执行状态（从代表正在执行的转圈动画，平滑过渡至代表成功的确认勾选状态） 。任务全局状态亦会从“创建中”明确流转至“完成” 。 精准异常归因与重试： 全部任务执行完毕后，系统顶部会输出清晰的结果汇总（如“共创建了 XXX 个文件夹，失败 X 个”） 。用户可一键查阅“创建失败文件列表” 。系统会将失败原因精确归类为“包含文件名不允许字符”或“已有同名文件夹”等系统级冲突 。针对这些异常条目，用户不仅可以查明原因，还能直接在界面上点击绿色的“重试”按钮触发二次创建 ，大幅降低了批量运维的阻力。 文控项目 文控项目是巴别鸟的一个行业应用独立模块（需要另行购买）。巴别鸟文控项目解决了工程设计行业中的文控标准的流程管理（DCC）及自动化问题。提高了大量文控人员的工作效率的同时也降低了人为失误的可能。 使用范围 需要严格管理每一次文件发送的行业或企业。每次发送给客户的文件都由特定人员发送（文控人员）每次发送都有发送单据可查，能明确的管理发送内容。通过发送单号可以查询到每次发送文件给接收方的具体信息和文件。同时对接收方是否收件，对发送过去的内容是否驳回都可管理查询。并且发送单可以作为凭据。 需要解决的问题 目前很多企业的文控流程基本是靠手动，文件存储于EDMS系统或文控人员电脑本地。依靠文件夹分类来管理文档，每次发送文件手动建立一个文件夹，按文件名规范命名文件夹，文件通过邮件发送后把发送的文件放入文件夹并附上本次发送的TRANSMITTAL（文件发送单）。 每次发送都会产生一个文件夹及相应的TRANSMITTAL。这些工作人工操作相当繁琐，除了整理文件，每次还需要手动填写文件发送单，手动按规则编写发送单编号，日后还要手动核对，效率极低。 巴别鸟解决方案 可新建新的文控项目类型。这意味着不同的项目可以设定不同的TRANSMITTAL（发送单）规则生成不同的发送单和发送单号。不同项目也可以管理不同的收件人（收件企业） 可设定每个项目的文件接收方，统一管理文件接收方。 文控项目中的文档支持发送功能，发送功能支持多选。选择文件或文件夹发送后，收件人可以通过邮箱收到所发送文件的下载link和TRANSMITTAL（发送单）。并且通过下载link下载到的文件是发送时的版本。 每次发送的文件都是文件当前版本，文件升版会形成新的版本号，并在发送单显示。 文件发送后根据预先设定的规则自动生成本次发送的TRANSMITTAL（发送单）和TRANSMITTAL NO.（发送单号） 可以管理及查询所由TRANSMITTAL（发送单），并可导出发送单为PDF。 巴别鸟文控项目使用指引： 基本介绍 巴别鸟文控管理系统是在巴别鸟企业私有云版的基础上增加文控管理模块，以实现文控工作的自动化。 文控管理的方式是以建立“文控项目”的方式来实现。文控项目是针对文控需求特别定制的特殊项目，以项目为单位进行管理。 建立文控项目 登录系统后，在要创建文控项目的部门中点击“新建”——“新建项目” 项目只能建立于根目录（企业文件）或部门根目录下 例：在HQSM文控这个部门下建立一个文控项目 点击新建项目，出现项目类型选择界面 选择“创建文控管理项目” 这时候出现项目初始化选择界面 按照项目的要求填写初始化信息 每项的介绍如下： 项目负责人 管理、转交项目、修改项目权限及基础信息。不可为空。可删除TRANSMITTAL 项目秘书 不可转交项目，其他同项目负责人，可多人，可为空。可删除TRANSMITTAL 文控人员 可以发送文件给接收人。其他权限可配置，可多人，可为空。选择人员后点击右侧权限选择下拉框可以批量修改成员权限（如图）。 其他成员 没有发送文件选项，其他同普通项目普通成员，权限可配置，可为空。 版本号规则 如图，如果前缀填写为HQSM，文件的第一个版本就为 HQSM A ，第二个版本为 HQSM B以此类推 基本信息 基本信息的填写内容将显示于TRANSMITTA头部。 如图：画红圈处就是填写的基本信息。 接收方信息 接收方信息决定了发件时的可选项和所发文件的TRANSMITTA号 收件方名字是指收件方在系统中的称呼，一般填写收件方的企业简称，如 MCC 邮箱支持添加多个，添加多个后，一次发送就可以向多个邮箱地址发送文件及TRANSMITTA ATTN可以任意输入，同时也会显示在TRANSMITTA上 运单号规则其实就是TRANSMITTA号的自动生成规则，不同的收件方可以生成不同的运单号。所以需要在每个收件方处设定不同的运单号规则。 规则自定义界面示意如下： 3栏分别为TRANSMITTAL号的3个组成部分，如果所需的TRANSMITTA号需要更多的编码来组成也可以点击+号来增加更多栏 例： 第一栏选择输入文字，弹出文字输入框，输入 “HQSM ” 第二栏选择编码规则为1 2 3数字顺序 第三栏选择 文字输入、输入“ 2020” 点加号新增一栏，选择a b c字母顺序 第一次发送生成的TRANSMITTAL号即为： HQSM 1 2020a 第二次发送生成的TRANSMITTAL号为：HQSM 2 2020b 选择字母作为编号超过26个后，z号的下一个版本自动变为a1 如果该项目有多个接收方，也可以点击来增加。（项目建立后也可以在项目管理界面中去增删接收方。 这些填写完成后，点击“新增项目”就完成了项目的新建 你可以在创建项目路径的文件列表中看到新建的文控项目，点击即可进入 文控管理项目不同于普通项目，项目首页顶部栏增加了文控管理的按钮 其中“发送单列表”可以查询该项目发出的所有TRANSMITTA，管理项目可以对项目进行管理。 上传文件 点击新建的文控项目，进入项目页面。 直接拖拽想要上传的文件到项目中即可上传文件，当然，你也可以和使用普通文件夹一样使用同步功能进行上传下载。 发送文件 选中要发送的文件（支持多选），然后点击右键，选择“发送文件”会出现文件发送界面 每次最多发送的文件为2000个（包含文件夹）。如项目需要全部文件发送，建议以压缩包形式进行发送。 收件人可以下拉选择项目初始化时填写的收件人及ATTN 抄送可以填写其他任意邮箱地址，也可以留空不填写 选择的提交文件类型也会在生成的TRANSMITTA中显示 文件列表罗列了本次要发送的文件。 系统要发送TRANSMITTAL的文件名构成为 文件编号+描述，如一个文件文件名为 1000+图纸.pdf，发送时显示在TRANSMITTAL的文件编号为“1000”，描述为“图纸”。如果发送的文件的文件名中没有+分割，文件编号就显示文件名，如果发送的文件名为“+图纸.jpg“就不显示文件编号，显示描述为“图纸”。描述可中途更改。 附言将会在收件人接受到的邮件中显示并不会显示在TRANSMITTAL中 填写完成后点击“发送文件”系统会自动生成TRANSMITTAL并作为link附在邮件中发送给客户。 生成TRANSMITTAL 发送成功后系统会弹出提示 点击查看，就能查看本次发送自动生成的TRANSMITTAL 点击导出为PDF就可以把该TRANSMITTAL保存为PDF文件 你也可以在传送单列表（TRANSMITTAL list）中去查看该项目中发送的所有TRANSMITTAL 收件人在邮箱中收到的TRANSMITTAL和该TRANSMITTAL一致。 查看TRANSMITTAL 在项目首页点击发送单列表（TRANSMITTAL list） 打开列表就可以看到及查询本项目的所有发送单。 点击传送单号可查看详情并下载TRANSMITTAL的PDF文件 为接受就是接受方并没有打开已发送的邮件，如对方打开邮件并访问了TRANSMITTAL，接收状态会变为已接收。 查看发送记录 在任意文件上右键点击，可查看该文件的发送记录及其对应的TRANSMITTAL 用户界面 用户界面设计 巴别鸟界面设计理念 企业网盘集成的功能比较多，如何合理分配功能入口，让用户实际使用时更加方便？是一个界面设计和交互时需要重点考虑的问题，目前有两种互有冲突的设计理念。 界面设计理念 优缺点 隐藏非常用功能，保证界面简洁，降低学习难度，易上手，初次使用体验友好。（代表：微云、腾讯文档等2C产品） 前缓后陡的学习曲线，用户初次试用时体验好，但实际长期使用时不方便 功能入口显性化，界面复杂，但需要的功能可以快速找到。界面较重，学习成本稍高，初次使用体验不友好。（代表：office、CAD等专业软件） 前陡后缓的学习曲线，用户初次使用体验复杂，但实际长期使用方便。不利于营销。 考虑到企业网盘是一个面向企业长期使用的专业产品，前期陡峭的学习曲线虽然不利于营销（用户简单试用时弃用率增高）但是对应选择巴别鸟的用户长期使用是友好的，熟悉后能更好用更有条理，而作为一个生产力工具，日常使用的便捷度和降低出错概率更加重要。所以巴别鸟企业网盘选择了第二种设计理念： 作为一个专业面向企业场景的产品，为用户长期日常使用时的便捷性，可以适当增加上手复杂度。 界面设计原则 用户友好性: 在保证功能使用优先的前提下，强调用户友好性，确保用户能够轻松使用企业网盘。 一致性: 维持一致的界面设计，以提供一致的用户体验。 简洁性: 采用简洁的设计，减少冗余和复杂性，使用户能够迅速理解界面。 可用性: 确保功能模块容易被用户找到并有相应指引，3步内直接可以使用。 用户界面元素 网页版（web） 采用左菜单、右文件列表、顶部功能分区的布局。方便用户注意力集中在文件列表上。 左侧菜单可以收起，显示更多文件列表内容，提供沉浸式体验。 为了更好的树状管理文件，也可以打开树状视图类似windows资源管理器一样管理文件。 如果文件夹图片文件数量多，可自动打开瀑布流预览模式，便于用户查看。 左侧菜单（快捷方式）用户可以自定义，便于用户日常按使用习惯自定义快捷入口。 文件/文件夹的所有功能操作集中在右键，容易找到，常用功能显示在文件列表上，同时文件列表栏也有相应按钮，防止因鼠标右键失效影响用户操作。 客户端（windows、mac、麒麟） 客户端使用Electron及C++进行跨平台开发，很好的保证了风格一致性和操作一致性。并且针对各平台也有各自的优化。客户端还包括同步模块、上传下载列表及虚拟映射盘（云桥）模块。 主操作界面延续网页版风格和布局，但针对本地软件的使用习惯及客户端独有模块进行了布局上的改进，把顶部功能分区集中在左侧栏，让顶部显示更简洁。 左侧栏增加了传输和同步两个客户端独有功能按钮及入口。 文件传输模块，管理同步进程和上传下载任务。 在windows和MacOS系统文件右键菜单上集成了同步和上传、发送文件的快捷方式，便于用户快速建立同步和上传文件（夹）。 在windows和MacOS上集成了虚拟映射盘，让用户可以像访问本地硬盘一样访问云端文件。 响应式设计 响应式设计原则 多设备兼容性: 巴别鸟企业网盘的用户界面被设计为在各种设备上获得最佳体验，包括桌面、移动设备和平板电脑，以保证用户随时随地用各种设备都能有良好的体验。 图：巴别鸟从诞生起就是跨平台的 自适应布局 用户界面元素会自动根据屏幕尺寸和方向进行调整，以确保内容的可见性和可用性。 触摸友好性: 优化移动设备上的触摸交互，包括手势控制、滑动和缩放。 图像和媒体优化: 使用了预载入、图像转码生成缩略图和媒体压缩技术，以减少页面加载时间和带宽使用。 移动端支持 网页版本移动设备优化 移动界面设计: 巴别鸟网页版本有针对移动设备打开设计的H5页面，及宣传网站移动版及分享链接移动版下载界面，支持常见触摸手势，如滑动、缩放和点击。 图：移动设备访问巴别鸟H5页面 移动APP: 为了获得更好的使用体验，巴别鸟开发了移动端专用的APP，支持安卓和iOS系统。 为保证良好的性能，巴别鸟APP都以原生应用的方式进行开发。 APP的交互、界面、功能模块都全部重新设计，以适合在移动设备上访问。 图：移动端界面 平板电脑优化 巴别鸟iOS APP针对iPad重新设计制作了界面，以更适应在大屏幕上工作。 性能优化 负载均衡策略 鉴权认证与服务分离 分离鉴权认证: 为了提高系统的性能和安全性，巴别鸟企业网盘采用了鉴权认证与核心服务分离的策略。这意味着用户的鉴权认证请求会被路由到专门的认证服务器上，而上传、下载以及查询浏览等核心服务请求会被路由到相应的核心服务服务器上。 请求路由: 我们使用负载均衡器来根据请求类型将请求路由到不同的服务器。这确保了鉴权认证服务器不会成为核心服务的性能瓶颈，并允许我们根据需求独立扩展认证和核心服务。 相同类型请求的多台服务器部署 多服务器支持: 巴别鸟企业网盘允许相同类型的请求在多台服务器上部署，以提高性能和可用性。这种多服务器支持策略确保了即使一台服务器出现故障，其他服务器仍然可以处理请求。 请求平均分配: 我们使用负载均衡算法将相同类型的请求均匀分配到多台服务器上，以避免服务器过载和提供更快的响应时间。 负载均衡器 负载均衡器配置: 我们使用专业的负载均衡器来实现请求的分发和路由。负载均衡器根据预定的规则将请求发送到适当的服务器。 监控和自动故障转移: 负载均衡器配备了监控功能，能够检测服务器的健康状态。如果某台服务器出现故障，负载均衡器会自动将请求路由到其他可用的服务器，以确保系统的连续性。 优势 性能提升: 负载均衡策略提高了系统的性能，允许请求在多台服务器上并行处理，减少了单一服务器的负载。 高可用性: 多台服务器的部署和自动故障转移确保了系统的高可用性，即使出现故障，仍然可以提供服务。 扩展性: 负载均衡策略允许根据需求添加更多的服务器，以满足不断增长的用户和请求。 缓存管理 文件缓冲区管理 文件缓冲区设置: 为了优化性能并减轻CPU资源负担，巴别鸟企业网盘实施了文件缓冲区管理。解密后的文件将暂时存储在缓冲区中，以减少重复解密操作。 LRU策略: 我们采用最近最少使用（LRU）策略来管理文件缓冲区。这意味着最不常使用的文件缓存将被淘汰，从而保持缓冲区的高效利用。 文件鉴权缓冲管理 文件鉴权缓冲: 鉴权检测对于文件访问的权限是复杂而耗时的。针对文件所在部门、项目、分享以及保密级别等多个因素，需要进行综合性的鉴权检测。为了提高性能，我们实施了文件鉴权缓冲，将鉴权结果缓存起来。 过期淘汰机制: 文件鉴权缓冲采用过期淘汰机制。每个缓存条目都有一个预定的过期时间，一旦超过该时间，缓存将被自动淘汰。这确保了缓存数据的新鲜性，并降低了内存使用。 优势 性能优化: 缓存管理减少了解密操作和鉴权检测的重复执行，从而提高了系统的响应速度和性能。 资源节约: 通过使用LRU策略和过期淘汰机制，我们有效地管理了内存资源，避免了内存泄漏和过度占用的问题。 复杂鉴权的快速响应: 文件鉴权缓冲确保了复杂的鉴权检测结果的快速响应，减少了对鉴权服务的压力。 数据压缩和传输优化 文件分块技术 文件分块存储: 为了优化文件的传输和存储，巴别鸟企业网盘采用了文件分块技术。大文件会被分成小块，并分别存储在服务器上。这有助于提高文件的传输效率和断点续传的支持。 并行块请求: 文件分块存储允许前端在文件下载时并行发起多个块的请求。一旦所有块都被下载，前端将它们组装成完整的文件，从而显著提高了下载速度。 基于哈希码的文件存储去重技术 文件去重: 巴别鸟企业网盘采用基于哈希码的文件存储去重技术。当用户上传文件时，系统会计算文件的哈希码并与已有文件的哈希码进行比较。如果发现相同的哈希码，系统将只保留一份文件的副本，从而节省存储空间。 节省存储空间: 文件去重技术有效减少了存储冗余，特别是在企业中频繁共享和传输的文件，从而降低了存储成本。 优势 传输效率: 文件分块技术和并行块请求加速了文件的传输速度，特别是对于大文件和高带宽连接。 存储节省: 基于哈希码的文件存储去重技术降低了存储需求，降低了维护成本。 用户体验: 快速的文件传输和节省存储空间改善了用户体验，提供更高效的文件管理和共享。 异步任务处理 后台异步处理 任务耗时处理: 为了处理那些前台发出的可能比较耗时，甚至可能导致HTTP请求超时的任务，巴别鸟企业网盘采用了后台异步处理的策略。这些任务不会阻塞主要的HTTP请求响应，而是在后台异步执行。 提高响应速度: 后台异步处理确保了前台请求的响应速度不受到耗时任务的影响，提高了用户体验。 配置化管理异步任务 任务队列: 为了防止服务器资源紧张，我们对异步任务进行了配置化管理。可以将异步任务配置为一个或多个处理队列，这些队列可以独立执行任务。任务队列可以根据任务的类型和优先级进行配置和管理。 消息队列: 另一种管理异步任务的方式是使用消息队列。巴别鸟企业网盘可以配置为使用消息队列来存储和调度异步任务。这种机制可以确保任务的有序执行和可控制性。 消息处理机制: 异步任务通过消息处理机制进行控制和执行。任务被加入队列或消息队列后，由专门的处理器进行处理和执行。 优势 响应性: 后台异步处理提高了系统的响应速度，避免了长时间的等待。 资源控制: 配置化管理异步任务允许对服务器资源进行有效的控制，防止资源耗尽。 可扩展性: 消息队列和消息处理机制提供了系统的可扩展性，可以轻松添加新的异步任务类型。 可扩展性 水平扩展 集群部署: 巴别鸟企业网盘业务服务器采用集群部署模型，这允许我们轻松扩展系统的容量和性能。集群中的多台服务器协同工作，以分担负载并提供高可用性。这种模型允许我们根据需求添加新节点，以满足不断增长的用户和数据需求。私有云部署客户在用户增长时也可以通过增加虚拟机或物理服务器的方式来扩充性能以满足高并发需求。关于巴别鸟集群部署可扩展性的更多信息，可以查看 分布式部署 章节。 对象存储系统: 巴别鸟的存储系统采用对象存储技术，这种技术非常适合大规模的数据存储和水平扩展。对象存储系统具有高度的可伸缩性，可以容纳大量的数据，并在需要时增加存储节点自动扩展存储容量。关于巴别鸟对象存储扩展性的更多信息，可以查看 自建对象存储 章节。 负载均衡: 我们实施了负载均衡策略，确保用户请求被均匀分配到集群中的各个节点，以避免单点故障和提供更快的响应时间。 自动伸缩（公有云）: 得益于阿里云ECS弹性计算服务，我们的系统配置了自动伸缩机制，根据负载情况自动增加或减少服务器节点。这种自动伸缩保证了系统的稳定性和性能。 垂直扩展 硬件升级: 除了水平扩展，针对私有云用户我们还可以进行垂直扩展，即升级服务器硬件以增加单个服务器的性能和容量。这在需要更多计算能力或内存的情况下是一种有效的解决方案。 数据库优化: 我们还可以优化数据库系统，通过调整配置、使用更高性能的硬件或升级数据库管理系统来提高性能。这些改进可以提供更好的查询性能和数据处理能力。 缓存: 我们使用缓存技术来加速数据访问，减轻数据库和存储系统的负载。缓存支持内存缓存、CDN缓存等多种方式，根据需要选择最适合的缓存策略。 容器化和SOA服务架构 Docker容器化 Docker部署: 我们采用Docker容器化技术来部署巴别鸟企业网盘的各个组件和模块。这种方式允许我们将每个主要模块打包为独立的Docker容器，提供了更高的灵活性和可扩展性。 容器编排: 我们使用容器编排工具来管理和协调各个容器，确保它们能够协同工作，实现高可用性和弹性。 容器镜像管理: 巴别鸟企业网盘使用容器镜像仓库来存储和管理Docker镜像，以便随时部署新的容器实例。 SOA服务架构 服务拆分: 我们将巴别鸟企业网盘的主要功能模块拆分为独立的服务，每个服务负责执行特定的任务或功能。这种拆分提高了系统的可维护性和可扩展性。 API通信: 服务之间通过API进行通信，使用兼容RESTful API协议。这种松耦合的通信方式使得服务可以独立开发、测试和部署。 独立部署: 每个服务可以独立部署和扩展，这意味着我们可以根据需求对特定服务进行水平扩展，而不影响其他服务的运行。 容器化和SOA服务架构的优势 高可用性: 容器化和SOA服务架构提供高可用性，允许我们在出现故障时快速恢复服务。 灵活性: 容器化允许我们轻松部署、升级和维护每个容器，而SOA服务架构提供了灵活的模块化开发和部署选项。 资源利用率: 我们可以根据需要分配资源，避免资源浪费，实现更高的资源利用率。 快速交付: 容器化和SOA服务架构使得新功能和改进可以更快地交付给用户。私有云用户也可以享有媲美公有云系统的快速更新及升级服务。 容器化和SOA服务架构的挑战 复杂性: 管理多个容器和服务可能会引入一定的复杂性，需要适当的管理工具和策略。 监控和日志: 我们使用监控和日志工具来确保容器和服务的正常运行，并及时识别和解决问题，并配备自动重启机制，如果服务有问题则自动重启有问题的模块以保证整体服务的畅通。" }, { "lang": "zh", "slug": "integrations", "title": "集成与开放能力", "description": "介绍企业微信、钉钉、飞书、SSO、OA/ERP/PDM、第三方服务和数据摆渡。", "category": "集成与扩展", "top_category": "部署指南", "keywords": [ "集成", "SSO", "企业微信", "钉钉", "飞书", "数据摆渡" ], "url": "zh/integrations.html", "source": "content/zh/integrations.md", "summary": "集成与开放能力 巴别鸟私有化版本可接入企业微信、钉钉、飞书、OA、ERP、PDM、ADFS、在线 Office、CAD 预览、OCR、AI 模型和其他第三方业务系统。 SSO 与组织同步 巴别鸟支持集成第三方登录（SSO）平台，以实现单点登录及统一登录。并且巴别鸟支持多个第三方登录平台集成。譬如：既可以企业微信扫码登录也可以OA账密登录、钉钉扫码登录。 SSO集成分为两个模块。第三方授权登录及第三方组织结构同步。其中第三方授权登录允许多个源进行授权登录。但第三方组织结构同步为了防止造成用户账户冲突，仅允许同步一个源。譬如：同步了OA系统的组织结构，但是支持OA和企业微信的SSO登录（OA和企业微信的的组织结构需要用一致的userID） 更多关于巴别鸟第三方登录的信息，可以查阅用户身份验证和授权（SSO）章节 数据摆渡 巴别鸟数据摆渡支持部署在密区的巴别鸟与部署在非密区的巴别鸟以安全并且带审批的方式互传数据。以实现在企业监管下的密区和非密区的数据交换。 关于巴别鸟数据摆渡的详细信息，可以查阅 巴别鸟数据摆渡 章节。 企业微信、钉钉、飞书接入指南 完整接入指南见 参考：企业微信、钉钉及飞书接入指南。", "headings": [ { "level": 1, "title": "集成与开放能力", "id": "section" }, { "level": 2, "title": "SSO 与组织同步", "id": "sso" }, { "level": 2, "title": "数据摆渡", "id": "section-2" }, { "level": 2, "title": "企业微信、钉钉、飞书接入指南", "id": "section-3" } ], "images": [], "text": "集成与开放能力 巴别鸟私有化版本可接入企业微信、钉钉、飞书、OA、ERP、PDM、ADFS、在线 Office、CAD 预览、OCR、AI 模型和其他第三方业务系统。 SSO 与组织同步 巴别鸟支持集成第三方登录（SSO）平台，以实现单点登录及统一登录。并且巴别鸟支持多个第三方登录平台集成。譬如：既可以企业微信扫码登录也可以OA账密登录、钉钉扫码登录。 SSO集成分为两个模块。第三方授权登录及第三方组织结构同步。其中第三方授权登录允许多个源进行授权登录。但第三方组织结构同步为了防止造成用户账户冲突，仅允许同步一个源。譬如：同步了OA系统的组织结构，但是支持OA和企业微信的SSO登录（OA和企业微信的的组织结构需要用一致的userID） 更多关于巴别鸟第三方登录的信息，可以查阅用户身份验证和授权（SSO）章节 数据摆渡 巴别鸟数据摆渡支持部署在密区的巴别鸟与部署在非密区的巴别鸟以安全并且带审批的方式互传数据。以实现在企业监管下的密区和非密区的数据交换。 关于巴别鸟数据摆渡的详细信息，可以查阅 巴别鸟数据摆渡 章节。 企业微信、钉钉、飞书接入指南 完整接入指南见 参考：企业微信、钉钉及飞书接入指南。" }, { "lang": "zh", "slug": "deployment-requirements", "title": "服务器配置与性能需求", "description": "业务服务器、数据库、搜索、转码、存储服务器的配置建议与性能边界。", "category": "部署实施", "top_category": "部署指南", "keywords": [ "部署", "服务器配置与性能需求", "私有化" ], "url": "zh/deployment-requirements.html", "source": "content/zh/deployment-requirements.md", "summary": "服务器配置与性能需求 服务器建议配置及性能需求 服务器类型及作用： 巴别鸟网盘所需硬件系统由业务服务器及存储服务器两部份构成，其中业务服务器可以分为4种类型，这4种类型的服务可以根据需求部署在一台物理机或虚拟机中，也可以分散部署在四台甚至更多的服务器中。所以，部署巴别鸟系统最小单位是两台物理服务器或两台虚拟机（一台业务一台存储） 服务名 用途 操作系统 主业务服务器 web服务、负载均衡、主业务功能实现 Linux 数据库服务器 数据库服务 Linux 搜索服务器 提供文件全文搜索、高级搜索功能 Linux 转码服务器 为需要转码预览的文件进行转码及增加水印 windows 2012、Linux 存储服务器 提供文件存储 Linux 极端情况下，如果使用服务器挂载的硬盘作为存储空间，巴别鸟也支持把全部服务及存储都部署在一台物理机或虚拟机中（一体机模式），但考虑到性能及灾备或是日后的升级扩容问题，不推荐这样的部署方式。 我们推荐的最佳部署方式是4台服务器（虚拟机）的小集群部署。主业务服务及数据库服务放在在一台服务器，搜索服务器和转码服务器独立，然后外加一台存储服务器。 如果存储的空间需求小于10TB，也可以不需要存储服务器。可以直接挂载硬盘或NFS磁盘进行存储。 巴别鸟也支持接入第三方存储，理论上，只要第三方存储系统支持NFS或S3协议都可以接入到巴别鸟作为存储服务。绝大多数存储系统都支持这两种协议。 各个服务器之间要保证互访的畅通。如内网有较高安全要求可以参阅 9.1.2需要开放的端口 最低性能配置： 巴别鸟的最低性能配置可以支持100左右用户正常使用，管理10TB以下的数据。", "headings": [ { "level": 1, "title": "服务器配置与性能需求", "id": "section" } ], "images": [], "text": "服务器配置与性能需求 服务器建议配置及性能需求 服务器类型及作用： 巴别鸟网盘所需硬件系统由业务服务器及存储服务器两部份构成，其中业务服务器可以分为4种类型，这4种类型的服务可以根据需求部署在一台物理机或虚拟机中，也可以分散部署在四台甚至更多的服务器中。所以，部署巴别鸟系统最小单位是两台物理服务器或两台虚拟机（一台业务一台存储） 服务名 用途 操作系统 主业务服务器 web服务、负载均衡、主业务功能实现 Linux 数据库服务器 数据库服务 Linux 搜索服务器 提供文件全文搜索、高级搜索功能 Linux 转码服务器 为需要转码预览的文件进行转码及增加水印 windows 2012、Linux 存储服务器 提供文件存储 Linux 极端情况下，如果使用服务器挂载的硬盘作为存储空间，巴别鸟也支持把全部服务及存储都部署在一台物理机或虚拟机中（一体机模式），但考虑到性能及灾备或是日后的升级扩容问题，不推荐这样的部署方式。 我们推荐的最佳部署方式是4台服务器（虚拟机）的小集群部署。主业务服务及数据库服务放在在一台服务器，搜索服务器和转码服务器独立，然后外加一台存储服务器。 如果存储的空间需求小于10TB，也可以不需要存储服务器。可以直接挂载硬盘或NFS磁盘进行存储。 巴别鸟也支持接入第三方存储，理论上，只要第三方存储系统支持NFS或S3协议都可以接入到巴别鸟作为存储服务。绝大多数存储系统都支持这两种协议。 各个服务器之间要保证互访的畅通。如内网有较高安全要求可以参阅 9.1.2需要开放的端口 最低性能配置： 巴别鸟的最低性能配置可以支持100左右用户正常使用，管理10TB以下的数据。 cpu 内存 系统盘 存储盘 网络 操作系统 8核CPU （参考基准E5 2609） 32G ECC 内存 500G 10TB以下 千兆 Linux 推荐性能配置实例： 巴别鸟的推荐性能配置可以支持1000 2000用户正常使用，管理最高可达1PB的文档。 巴别鸟支持多种部署方式，该实例是标准部署方式。使用虚拟机部署业务服务器对接独立的单台或多台对象存储服务器。业务服务器和存储服务器分开管理。 业务服务器： 建议业务服务器使用虚拟机进行部署 编号 服务器类型 配置要求 操作系统 服务器用途 1 虚拟机 8核CPU 64G内存 500G SSD系统盘 CentOS8或openeuler22 主业务服务器/数据库 2 虚拟机 8核CPU 32G内存 500G SSD系统盘 CentOS8或openeuler22 搜索服务器 3 虚拟机 8核CPU 16G内存 200G SSD系统盘 windows 2012 R2 转码服务器 8核cpu的性能应该接近志强4410 巴别鸟企业网盘采用Docker部署，理论上只要是Linux操作系统即可进行部署，推荐使用CentOS或open Euler。 如果没有现成的虚拟机资源，需要采购新的业务服务器，业务服务器硬件配置需求如下： 编号 服务器类型 配置要求 操作系统 服务器用途 1 业务服务器 至强银牌4210 2 20核CPU 64G内存 2TB SSD硬盘 Linux 主业务服务器 业务服务器最好购买VM，使用虚拟化进行管理。 存储服务器（对象存储）： 巴别鸟支持在通用服务器上搭建对象存储系统，如预计存储空间用量小于100TB，推荐使用单台服务器搭建对象存储系统。单台对象存储可以用磁盘进行数据校验冗余，并且可以以每次增加一台存储服务器的方式进行横向扩容。（扩容操作可以做到不停服） 对象存储服务器建议使用独立的物理机，建议配置如下： 服务器类型 配置要求 操作系统 服务器用途 备注 存储服务器 至强银牌4210 2 20核CPU 64G内存 480G SSD硬盘 +存储所需容量硬盘 硬盘如果考虑性价比，建议使用 8T 10（2U） 或 8T 24（4U）。如果考虑存储密度及未来扩容投入可使用12T硬盘。 Linux 对象存储服务器 未来扩展建议增加相同磁盘容量的服务器。 如所需存储空间大于300TB，需要多台服务器搭建分布式对象那个存储系统。 巴别鸟也支持为客户搭建分布式对象存储系统。要了解分布式对象存储可查阅“自建对象存储”章节。" }, { "lang": "zh", "slug": "deployment-ports", "title": "端口与网络要求", "description": "外网访问、服务器内部通信和部署阶段需要开放的端口说明。", "category": "部署指南", "top_category": "部署指南", "keywords": [ "部署", "端口与网络要求", "私有化" ], "url": "zh/deployment-ports.html", "source": "content/zh/deployment-ports.md", "summary": "端口与网络要求 需要开放的端口 为了服务器系统的安全，我们需要只开放特定的端口，下面是需要开放的端口： 对外开放的端口（外网访问需要使用的端口）： 端口号 端口用途 协议 开放的主机 80 网盘主业务 web外部访问端口，不加密 http 主业务服务器 443 网盘主业务 web外部访问端口，加密 https 主业务服务器 3060 网盘主业务node 外部访问端口，不加密 TCP 主业务服务器 3080 网盘主业务node 外部访问端口，加密 TCP 主业务服务器 服务器间需要开放的端口（服务器内部通讯需要开放的端口）： 一般实际部署时，只会限制外网端口（对外），服务器间内部端口不会限制。但一些跨网络跨机房部署的用户也会需要限定内部端口。 主机 端口号 端口用途 协议 目标网段 业务服务器 6379 redis访问端口，供windows转码与搜索服务器使用 TCP 转码服务器与搜索服务器 业务服务器 8080 供windows转码服务器，访问网盘业务服务器使用 TCP 转码服务器与搜索服务器 业务服务器 3306 数据库端口，供搜索服务器访问数据库使用 TCP 转码服务器与搜索服务器 业务服务器 9000 docker 集群部署，内部可视化界面端口 TCP 转码服务器与搜索服务器 业务服务器 111 portmap 端口 TCP+UDP 转码服务器与搜索服务器 业务服务器 2049 TCP+UDP TCP+UDP 转码服务器与搜索服务器 业务服务器 35000 mountd 端口 TCP+UDP 转码服务器与搜索服务器 业务服务器 2376 docker REST API端口", "headings": [ { "level": 1, "title": "端口与网络要求", "id": "section" } ], "images": [], "text": "端口与网络要求 需要开放的端口 为了服务器系统的安全，我们需要只开放特定的端口，下面是需要开放的端口： 对外开放的端口（外网访问需要使用的端口）： 端口号 端口用途 协议 开放的主机 80 网盘主业务 web外部访问端口，不加密 http 主业务服务器 443 网盘主业务 web外部访问端口，加密 https 主业务服务器 3060 网盘主业务node 外部访问端口，不加密 TCP 主业务服务器 3080 网盘主业务node 外部访问端口，加密 TCP 主业务服务器 服务器间需要开放的端口（服务器内部通讯需要开放的端口）： 一般实际部署时，只会限制外网端口（对外），服务器间内部端口不会限制。但一些跨网络跨机房部署的用户也会需要限定内部端口。 主机 端口号 端口用途 协议 目标网段 业务服务器 6379 redis访问端口，供windows转码与搜索服务器使用 TCP 转码服务器与搜索服务器 业务服务器 8080 供windows转码服务器，访问网盘业务服务器使用 TCP 转码服务器与搜索服务器 业务服务器 3306 数据库端口，供搜索服务器访问数据库使用 TCP 转码服务器与搜索服务器 业务服务器 9000 docker 集群部署，内部可视化界面端口 TCP 转码服务器与搜索服务器 业务服务器 111 portmap 端口 TCP+UDP 转码服务器与搜索服务器 业务服务器 2049 TCP+UDP TCP+UDP 转码服务器与搜索服务器 业务服务器 35000 mountd 端口 TCP+UDP 转码服务器与搜索服务器 业务服务器 2376 docker REST API端口，进行TLS加密 TCP 本机 业务服务器 2377 TCP端口 用来 docker 集群管理相关通信 TCP+UDP 本机 业务服务器 7946 TCP与UDP端口，用来docker swarm 各节点间的通信 TCP+UDP 本机 业务服务器 4789 docker overlay 网络默认端口 TCP+UDP 本机 搜索服务器 9200 elastic 端口，供主业务服务器调用使用 TCP 业务服务器 搜索服务器 5601 kibana端口，内部可视化elastic界面访问端口 TCP 业务服务器 搜索服务器 9998 tika端口，提取文档文本服务器端口 TCP 业务服务器 搜索服务器 9000 docker 集群部署，内部可视化界面端口 TCP 转码服务器与搜索服务器 搜索服务器 2376 docker REST API端口，进行TLS加密 TCP 本机 搜索服务器 2377 TCP端口 用来 docker 集群管理相关通信 TCP 本机 搜索服务器 7946 TCP与UDP端口，用来docker swarm 各节点间的通信 TCP+UDP 本机 搜索服务器 4789 docker overlay 网络默认端口 TCP+UDP 本机 转码服务器 转码服务器 可以访问业务服务器 可以访问业务服务器 可以访问业务服务器 部署时需要开放的端口： 端口号 端口用途 开放的服务器 目标IP地址 22 ssh端口号，ssh 访问使用 所有服务器 部署用跳板机 443 获取授权 所有服务器 47.96.234.200 443 获取安装源 所有服务器 120.27.245.68 443 Docker安装源 所有服务器 13.35.121.100" }, { "lang": "zh", "slug": "deployment-poc", "title": "POC 部署", "description": "POC 环境、初始化、培训、试用和验证建议。", "category": "部署实施", "top_category": "部署指南", "keywords": [ "部署", "POC 部署", "私有化" ], "url": "zh/deployment-poc.html", "source": "content/zh/deployment-poc.md", "summary": "POC 部署 POC部署 POC部署适用于用户在选型前在生产环境进行POC测试而进行的部署方式。 POC部署需求： 基础POC部署，可测试软件功能，并发量，API接口，安全性，并进行生产环境试用。建议使用标准部署作为POC测试。 如需要进行对象存储、不同密区数据摆渡、高可用的POC，择需要增加相应的服务器和网段。 环境准备 推荐使用虚拟机进行部署： 巴别鸟私有化企业网盘采用Docker部署，理论上只要是Linux操作系统即可进行部署。推荐使用CentOS或open Euler。按要求准备好虚拟机后，联系我们预约时间后即可开始POC部署。 编号 服务器类型 配置要求 操作系统 服务器用途 备注 1 虚拟机 8核CPU 32G内存 500G系统盘 +500G存储盘 CentOS8或openeuler22及以上 主业务服务器 2 虚拟机 8核CPU 16G内存 500G系统盘 CentOS8或openeuler22及以上 搜索服务器 3 虚拟机 8核CPU 8G内存 200G系统盘 windows 2012 R2 转码服务器 CAD、office转码 win服务器是为了更好的office文件预览效果。巴别鸟也支持纯Linux环境部署 POC部署其他要求如下： 编号 项目 要求 备注 1 远程接入 可以远程接入服务器进行部署 可使用堡垒机或者跳板机或向日葵、VPN，能远程接入服务器部署即可。 2 外网连接 服务器需要能连接外网，拉取安装包，获取授权 需要连接的外网地址： software.babel.cc docker.babel.cc POC部署的使用授权时长为30天，授权账户数为1", "headings": [ { "level": 1, "title": "POC 部署", "id": "poc" } ], "images": [], "text": "POC 部署 POC部署 POC部署适用于用户在选型前在生产环境进行POC测试而进行的部署方式。 POC部署需求： 基础POC部署，可测试软件功能，并发量，API接口，安全性，并进行生产环境试用。建议使用标准部署作为POC测试。 如需要进行对象存储、不同密区数据摆渡、高可用的POC，择需要增加相应的服务器和网段。 环境准备 推荐使用虚拟机进行部署： 巴别鸟私有化企业网盘采用Docker部署，理论上只要是Linux操作系统即可进行部署。推荐使用CentOS或open Euler。按要求准备好虚拟机后，联系我们预约时间后即可开始POC部署。 编号 服务器类型 配置要求 操作系统 服务器用途 备注 1 虚拟机 8核CPU 32G内存 500G系统盘 +500G存储盘 CentOS8或openeuler22及以上 主业务服务器 2 虚拟机 8核CPU 16G内存 500G系统盘 CentOS8或openeuler22及以上 搜索服务器 3 虚拟机 8核CPU 8G内存 200G系统盘 windows 2012 R2 转码服务器 CAD、office转码 win服务器是为了更好的office文件预览效果。巴别鸟也支持纯Linux环境部署 POC部署其他要求如下： 编号 项目 要求 备注 1 远程接入 可以远程接入服务器进行部署 可使用堡垒机或者跳板机或向日葵、VPN，能远程接入服务器部署即可。 2 外网连接 服务器需要能连接外网，拉取安装包，获取授权 需要连接的外网地址： software.babel.cc docker.babel.cc POC部署的使用授权时长为30天，授权账户数为100个。 初始化 部署完成后，巴别鸟团队会帮助用户进行系统初始化，根据用户需求初始化系统。包括不限于： 初始化管理员账号。（需要准备一个邮箱地址作为超级管理员账号） 初始化通知发件邮箱。（需要用户准备一个可提供密码和smtp服务器地址的邮箱作为系统默认发件箱） 初始化部门结构。（对接AD或导入部门） 初始化基础配置。logo、企业名、各类配置项。 培训 巴别鸟是一个专业的企业级应用，需要一定的培训工作帮助客户落地。POC后建议联系我方销售人员进行使用培训。 培训分为3类： 管理员培训（培训管理员的配置，使用，需求功能实现。耗时 1 2小时） 部门经理培训。（培训部门经理权限分配、成员增减等日常管理方式。耗时 1小时） 使用者培训。（使用成员的培训。耗时 1小时） 开启POC试用 培训完成后即可开始正式POC试用，使用中遇到的问题可以在相关群直接询问，巴别鸟团队会在2个小时内响应并解答。POC系统有效期为30天，如果需要延期，可联系我们销售人员。" }, { "lang": "zh", "slug": "deployment-modes", "title": "常用部署方式", "description": "公有云平台、自购服务器、单服务器、虚拟化、对象存储、分布式和灾备部署方式。", "category": "部署指南", "top_category": "部署指南", "keywords": [ "部署", "常用部署方式", "私有化" ], "url": "zh/deployment-modes.html", "source": "content/zh/deployment-modes.md", "summary": "常用部署方式 巴别鸟常用部署方式介绍 巴别鸟可以按需支持多种部署方式，这里介绍下巴别鸟常用的部署方式。 在阿里云、腾讯云、华为云等公有平台部署： 巴别鸟支持在公有云服务商如：阿里云、腾讯云、百度云、华为云、天翼云的虚拟机（ECS）及对象存储（OSS、OBS...）上进行部署，在互联网上为用户提供服务。 和纯私有化部署的差别对比如下表： 优缺点/ 部署方式 图片服务 视频服务 公网访问 稳定性 硬件费用 采用阿里云存储和阿里云服务器 可以使用阿里云提供的图片服务 可以采用阿里云的视频转码服务，但是需要额外付费(价格贵) 可以在公网上访问，用户访问的快慢取决于用户自己的带宽和购买的阿里云的带宽。 系统很稳定，部署简单，便于管理。 需要支付阿里云的存储和服务器费用，可按月或按年付费等。服务器的维护即可由用户自己负责，也可以委托我们进行维护并负责升级。 存储和服务器均搭建在自己的内网 使用自建的图片处理服务(需要客户提供高性能的服务器) 使用自建的转码服务(需要客户提供高性能的服务器)，如果用户没有这方面的需求，可以忽略。 如果没有外网的出口，则用户不能在外网访问。但是在内网访问很快。 稳定，针对存储系统等的模块做了定制开发。数据的安全性由用户自己负责。 需要提供独立的主机和存储系统。服务器即可由用户选配购买，也可以由我们选配购买。服务器维护由用户负责，我们可以提供相应的软件升级服务。 公有云部署（1000+用户）要求： 编号 服务器类型 配置要求 操作系统 服务器用途 1 ECS 16核CPU 32G内存 500G SSD系统盘 CentOS8或openeuler22 主业务服务器 ", "headings": [ { "level": 1, "title": "常用部署方式", "id": "section" } ], "images": [], "text": "常用部署方式 巴别鸟常用部署方式介绍 巴别鸟可以按需支持多种部署方式，这里介绍下巴别鸟常用的部署方式。 在阿里云、腾讯云、华为云等公有平台部署： 巴别鸟支持在公有云服务商如：阿里云、腾讯云、百度云、华为云、天翼云的虚拟机（ECS）及对象存储（OSS、OBS...）上进行部署，在互联网上为用户提供服务。 和纯私有化部署的差别对比如下表： 优缺点/ 部署方式 图片服务 视频服务 公网访问 稳定性 硬件费用 采用阿里云存储和阿里云服务器 可以使用阿里云提供的图片服务 可以采用阿里云的视频转码服务，但是需要额外付费(价格贵) 可以在公网上访问，用户访问的快慢取决于用户自己的带宽和购买的阿里云的带宽。 系统很稳定，部署简单，便于管理。 需要支付阿里云的存储和服务器费用，可按月或按年付费等。服务器的维护即可由用户自己负责，也可以委托我们进行维护并负责升级。 存储和服务器均搭建在自己的内网 使用自建的图片处理服务(需要客户提供高性能的服务器) 使用自建的转码服务(需要客户提供高性能的服务器)，如果用户没有这方面的需求，可以忽略。 如果没有外网的出口，则用户不能在外网访问。但是在内网访问很快。 稳定，针对存储系统等的模块做了定制开发。数据的安全性由用户自己负责。 需要提供独立的主机和存储系统。服务器即可由用户选配购买，也可以由我们选配购买。服务器维护由用户负责，我们可以提供相应的软件升级服务。 公有云部署（1000+用户）要求： 编号 服务器类型 配置要求 操作系统 服务器用途 1 ECS 16核CPU 32G内存 500G SSD系统盘 CentOS8或openeuler22 主业务服务器 2 ECS 8核CPU 16G内存 500G SSD系统盘 CentOS8或openeuler22 数据库服务器 3 ECS 8核CPU 16G内存 500G SSD系统盘 CentOS8或openeuler22 搜索服务器 4 存储 对象存储系统。如阿里云OSS、华为云OBS 对象存储系统。如阿里云OSS、华为云OBS 对象存储系统。如阿里云OSS、华为云OBS 在公有云平台部署的主要优势是不需要专人维护、无需购买硬件就能做到顶级的灾备、在互联网上访问速度快、同时服务器和数据在自己手上管理。 在公有云平台部署的缺点主要为：数据没有本地化、每年需要支付服务器租用费用及相应的带宽存储成本。 自购服务器（2台物理机）进行部署： 如果想在自己机房部署纯私有的巴别鸟，并且没有富余的虚拟机资源，需要采购硬件部署，要求如下： 物理机服务器品牌建议：建议使用2台 DELL T440 服务器来完成系统搭建。并购买DELL3年金牌服务。 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：建议使用2台 DELL T440 服务器来完成系统搭建。并购买DELL3年金牌服务。 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：建议使用2台 DELL T440 服务器来完成系统搭建。并购买DELL3年金牌服务。 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：建议使用2台 DELL T440 服务器来完成系统搭建。并购买DELL3年金牌服务。 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：建议使用2台 DELL T440 服务器来完成系统搭建。并购买DELL3年金牌服务。 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：建议使用2台 DELL T440 服务器来完成系统搭建。并购买DELL3年金牌服务。 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 两台服务器方案 业务+存储 两台服务器方案 业务+存储 两台服务器方案 业务+存储 两台服务器方案 业务+存储 两台服务器方案 业务+存储 两台服务器方案 业务+存储 编号 服务器类型 配置要求 操作系统 服务器用途 备注 1 服务器 志强银牌4410 2 16核CPU、 64G内存、 2TB SSD硬盘 open Euler、Ubuntu、CentOS 主业务服务器 建议安装VM 2 存储 4410 2 16核CPU 、64G内存、 500G SSD硬盘+所需的硬盘空间（不需要raid或raid0） open Euler、Ubuntu、CentOS 存储服务器 硬盘容量按对存储空间需求进行配置 以上配置可支持1000+用户，150TB左右的存储空间 巴别鸟存储服务器使用对象存储系统，支持分布式部署（多台存储服务器）最低要求为一台物理服务器。支持使用硬盘组进行校验，支持2+1、3+1、4+1...等多种校验类型。详见 自建对象存储 章节 如需扩容存储空间，增加单台存储服务器即可。 也可增加一台存储服务器作为备份服务器，实时同步备份，主存储服务器出问题切换到备份服务器即可正常使用。 单服务器（1台物理机）部署： 一些没有机房但需要私有化部署巴别鸟，并且存储空间需求不大（10TB以下）的客户，可以选用单台服务器部署巴别鸟。只需购买一台符合要求的塔式服务器放置在公司也能满足使用巴别鸟的需求。 物理机服务器品牌建议：如果没有机房，建议使用塔式服务器进行部署。服务器存储硬盘建议raid1或者raid5+1 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：如果没有机房，建议使用塔式服务器进行部署。服务器存储硬盘建议raid1或者raid5+1 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：如果没有机房，建议使用塔式服务器进行部署。服务器存储硬盘建议raid1或者raid5+1 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：如果没有机房，建议使用塔式服务器进行部署。服务器存储硬盘建议raid1或者raid5+1 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：如果没有机房，建议使用塔式服务器进行部署。服务器存储硬盘建议raid1或者raid5+1 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：如果没有机房，建议使用塔式服务器进行部署。服务器存储硬盘建议raid1或者raid5+1 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 一台服务器（一体机方案） 一台服务器（一体机方案） 一台服务器（一体机方案） 一台服务器（一体机方案） 一台服务器（一体机方案） 一台服务器（一体机方案） 编号 服务器类型 配置要求 操作系统 服务器用途 备注 1 服务器 志强银牌4410 2 16核CPU 64G内存 2TB SSD硬盘 +需要存储容量的硬盘 2（未来也可增加硬盘） openEuler、Ubuntu、CentOS 8.5 及以上 一体机 建议安装VM，2个CPU授权。 单服务器部署整套巴别鸟系统不支持对象存储，采用只读硬盘或NFS的方式进行存储。建议使用raid1来提升系统可靠性。 可增加一台备份服务器用来进行数据同步备份。如主服务器出问题可以用备份服务器进行数据重建。 在现有虚拟机（超融合）系统上进行部署： 这是目前最常用的部署方式，在企业现有的服务器和硬件条件下进行部署，无需采购新的设备。 在客户现有的VM或超融合平台分配的虚拟机中完成部署，适合已经有一定IT建设及管理的用户。 采用小集群的方式部署，由虚拟机平台负责服务器的统一管理。 支持绝大多数虚拟化系统。 推荐采用4台虚拟机挂载存储空间的方式进行部署。 编号 服务器类型 配置要求 操作系统 服务器用途 1 虚拟机 8核CPU 32G内存 500G SSD系统盘 CentOS8或openeuler22 主业务服务器 2 虚拟机 8核CPU 16G内存 500G SSD系统盘 CentOS8或openeuler22 数据库服务器 3 虚拟机 8核CPU 16G内存 500G SSD系统盘 CentOS8或openeuler22 搜索服务器 4 虚拟机 8核CPU 16G内存 200G SSD系统盘 windows 2012 R2 转码服务器 5 存储 支持NFS或S3接口的存储系统或虚拟机挂载磁盘作为存储盘 支持NFS或S3接口的存储系统或虚拟机挂载磁盘作为存储盘 支持NFS或S3接口的存储系统或虚拟机挂载磁盘作为存储盘 如有系统冗余需求，可以准备6台虚拟机，就能很好的完成数据库备份及系统冗余。 编号 服务器类型 配置要求 操作系统 服务器用途 1 虚拟机 8核CPU 32G内存 500G SSD系统盘 CentOS8或openeuler22 主业务服务器 2 虚拟机 8核CPU 32G内存 500G SSD系统盘 CentOS8或openeuler22 从业务服务器 3 虚拟机 8核CPU 16G内存 500G SSD系统盘 CentOS8或openeuler22 主数据库服务器 4 虚拟机 8核CPU 16G内存 500G SSD系统盘 CentOS8或openeuler22 从数据库服务器 5 虚拟机 8核CPU 16G内存 500G SSD系统盘 CentOS8或openeuler22 数据库服务器 6 虚拟机 8核CPU 16G内存 200G SSD系统盘 windows 2012 R2 转码服务器 7 存储 分布式对象存储 分布式对象存储 分布式对象存储 支持虚拟机挂载磁盘的形式把挂载盘作为存储空间。 也可以对接san存储或者对象存储系统等第三方存储系统。 巴别鸟也为客户提供自建对象存储服务。 自建对象存储服务器配合虚拟机部署： 巴别鸟支持为客户在通用服务器上搭建对象存储，因为对象存储软件定义存储的优势（高可用、横向扩展容易），推荐没有对象存储的用户可以新购一台服务器部署巴别鸟对象存储系统配合在虚拟机（超融合）运行的巴别鸟业务系统一起使用。 业务服务器需求同上一节“在现有虚拟机（超融合）系统上进行部署”的要求。 关于巴别鸟对象存储的详细介绍可查看“自建对象存储服务器”章节。 我们大多数客户最终都选择对象存储服务器作为存储。 最低支持单服务器搭建对象存储系统（150TB以下空间需求）。 服务器类型 配置要求 操作系统 服务器用途 备注 存储服务器 至强银牌4210 2 20核CPU 64G内存 480G SSD硬盘 +存储所需容量硬盘 硬盘如果考虑性价比，建议使用 8T 10（2U） 或 8T 24（4U）。如果考虑存储密度及未来扩容投入可使用12T硬盘。 Linux 对象存储服务器 未来扩展建议增加相同磁盘容量的服务器。 单服务器对象存储网络拓扑图： 我们也支持搭建多台服务器组成的分布式对象存储系统。 分布式存储系统最小需求为2+1，就是需要准备三台存储服务器，性能要求和单台对象存储的要求一致。 物理分布式存储目前推荐最小单位是3台存储服务器。2+1纠错码意味着每扩充2台存储节点就需要增加1台服务器作为纠错服务器。以此，4+1意味着增加4台存储服务器就需要增加一台纠错服务器。所以4+1的磁盘利用率高于2+1。使用4+1方案首次建设就需要5台存储服务器。每次扩容增加的最小单位和首次建设需要的最小服务器单位一致。 多服务器分布对象存储网络拓扑图： 可以新增一台或一套存储服务器用来实时备份。主存储服务器出问题快速切换到备份服务器即可正常使用。 分布式高可用高冗余部署： 金融机构、医院、能源、超大型企业因为有业务不中断的硬性指标，需要系统能做到高可用、高冗余，不会因为服务器的单点故障而中断服务，并且能做到热切换及热修复，极端情况下，连交换机等网络设备都需要实现主备分离，这就需要使用分布式高可用高冗余部署。 巴别鸟支持多种高可用高冗余方案，可以部署在传统的分布式系统中实现高可用高冗余。 我们也可以为客户搭建适合巴别鸟的分布式系统。（硬件需要客户按要求自行采购） 巴别鸟分布式部署能确保任何一个单点故障都不会影响系统的正常使用。 推荐的分布式容易部署方案，业务服务器采用主备双活，存储系统采用分布式存储。 有密区及非密区管控需求的，详见 “数据摆渡章节” 巴别鸟高可用系统网络拓扑 异地灾备部署 对于对数据保全有着较高要求的用户，巴别鸟也支持异地灾备方案。就是把重要的数据库及文件存储内容备份到异地的备份系统中。如果本地机房出现问题，只要备份数据在，可以在任何地方重建系统并恢复正常使用。 巴别鸟可以为客户搭建异地灾备服务器，但不支持冷热数据分离等高级备份方式，如果数据量极大（1PB以上）考虑到性价比，建议使用专业的备份系统（如：NBU、云祺）。 巴别鸟有支持NBU标准的备份API可以调用。 异地灾备部署对网络环境要求较高，不同位置的机房间最好有专线或稳定的VPN连接。 使用备份系统只能在出问题后通过备份还原及重建数据，不支持直接切换到备份数据。一般情况下数据重建周期会比较久。 使用备份系统进行异地灾备示意图： 如果不需要冷热数据分类保存，巴别鸟也可以采用对象存储自带的异地灾备功能为客户完成异地灾备部署。 使用对象存储进行异地灾备，当主系统出问题可以快速切换到灾备服务器中。" }, { "lang": "zh", "slug": "deployment-object-storage", "title": "对象存储与纠删码", "description": "MinIO 对象存储、纠删码、空间利用率、硬件准备和扩容说明。", "category": "架构与存储", "top_category": "部署指南", "keywords": [ "部署", "对象存储与纠删码", "私有化" ], "url": "zh/deployment-object-storage.html", "source": "content/zh/deployment-object-storage.md", "summary": "对象存储与纠删码 自建对象存储服务器 巴别鸟对象存储是在开源MinIO系统上发展起来的对象存储系统。它继承了MinIO高性能、可扩展、数据安全的优势，同时更适配巴别鸟企业网盘的应用场景。 巴别鸟对象存储系统作为先进的对象存储系统，在速度、安全性、稳定性、高可用、横向扩展方面都有着传统存储系统无可比拟的优势。 巴别鸟对象存储系统优势 性能 MinIO号称是世界上速度最快的对象存储服务器，没有之一。在 32 个 NVMe 驱动器节点和 100Gbe 网络上发布的 GET/PUT 结果超过 325 GiB/秒和 165 GiB/秒，和亚马逊S3相比有明显优势，远远超越传统HDFS。 高可用性：MinIO通过数据的多副本、故障转移和自动恢复，保证高度可靠性和可用性，从而确保数据不丢失和业务不中断。 低冗余且磁盘损坏高容忍：标准且最高的数据冗余系数为2(即存储一个1 M的数据对象，实际占用磁盘空间为2M)。但在任意n/2块disk损坏的情况下依然可以读出数据(n为一个纠删码集合(Erasure Coding Set)中的disk数量)。并且这种损坏恢复是基于单个对象的,而不是基于整个存储卷的。 安全性： MinIO 通过最高级别的加密以及广泛的优化提供更多功能，几乎消除了通常与存储加密操作相关的开销。 数据分块存储与各个硬盘，获取硬盘或服务器读写权限也无法还原数据。 极高的可扩展性：MinIO支持分布式部署，并且可以水平扩展。在需要更多的存储空间或更高的性能时，可以通过添加新的节点轻松地扩展MinIO。 最低支持单机部署对象存储系统，而不是传统的需要三台独立服务器。 对象存储系统及纠删码", "headings": [ { "level": 1, "title": "对象存储与纠删码", "id": "section" } ], "images": [], "text": "对象存储与纠删码 自建对象存储服务器 巴别鸟对象存储是在开源MinIO系统上发展起来的对象存储系统。它继承了MinIO高性能、可扩展、数据安全的优势，同时更适配巴别鸟企业网盘的应用场景。 巴别鸟对象存储系统作为先进的对象存储系统，在速度、安全性、稳定性、高可用、横向扩展方面都有着传统存储系统无可比拟的优势。 巴别鸟对象存储系统优势 性能 MinIO号称是世界上速度最快的对象存储服务器，没有之一。在 32 个 NVMe 驱动器节点和 100Gbe 网络上发布的 GET/PUT 结果超过 325 GiB/秒和 165 GiB/秒，和亚马逊S3相比有明显优势，远远超越传统HDFS。 高可用性：MinIO通过数据的多副本、故障转移和自动恢复，保证高度可靠性和可用性，从而确保数据不丢失和业务不中断。 低冗余且磁盘损坏高容忍：标准且最高的数据冗余系数为2(即存储一个1 M的数据对象，实际占用磁盘空间为2M)。但在任意n/2块disk损坏的情况下依然可以读出数据(n为一个纠删码集合(Erasure Coding Set)中的disk数量)。并且这种损坏恢复是基于单个对象的,而不是基于整个存储卷的。 安全性： MinIO 通过最高级别的加密以及广泛的优化提供更多功能，几乎消除了通常与存储加密操作相关的开销。 数据分块存储与各个硬盘，获取硬盘或服务器读写权限也无法还原数据。 极高的可扩展性：MinIO支持分布式部署，并且可以水平扩展。在需要更多的存储空间或更高的性能时，可以通过添加新的节点轻松地扩展MinIO。 最低支持单机部署对象存储系统，而不是传统的需要三台独立服务器。 对象存储系统及纠删码 关于纠删码 巴别鸟对象存储系统(MinIO)使用纠删码erasure code 和校验和checksum来保护数据免受硬件故障和无声数据损坏。最高冗余状态下即便丢失一半数量(N/2)的硬盘,您仍然可以恢复数据。 纠删码是一种恢复丢失和损坏数据的数学算法，MinIO采用Reed Solomon code将对象拆分成N/2数据和N/2奇偶校验块。这就意味着如果是12块盘，一个对象会被分成6个数据块、6个奇偶校验块，可以丢失任意6块盘(不管其是存放的数据块还是奇偶校验块) , 仍可以从剩下的盘中的数据进行恢复，我们称数据存储为D、纠删码（奇偶校验）为P。 默认情况下会以N/2个数据和N/2奇偶校验块的方式来进行驱动器分片（支持自定义以支持更高的空间利用率） 纠删码不同于传统的多副本技术，它的磁盘利用率更高，数据恢复效率更高。（但是不少存储厂商把纠删码宣传为多副本，把P数说成是副本数，这是不准确的，会引起很多误解） 巴别鸟语境下的多副本是指增加备份服务器全量同步存储的数据。 纠删码特点及与raid技术区别 纠删码可以保护数据免受多个驱动器故障的影响 RAID6允许两个驱动器故障而MinIO纠删码允许丢失一半的驱动器 RAID属于卷级别的纠删码而MinIO纠删码是基于对象实现的纠删码（不用停机） 有效空间计算（空间利用率） 假设需要100TB的存储空间，需要购买多少个多大的硬盘取决于选择的冗余标准。譬如：采用3+1的冗余方式，100TB可用空间就需要购买12块12TB的硬盘，4块硬盘一组组成3组，9个数据盘3个校验盘，可用空间就是9 12一共108TB可用。如果采用2+1的冗余方式，就需要15块10TB的硬盘，10个数据盘，5个校验盘。 3+1方案中12块硬盘只能坏任意3块不影响系统使用及数据还原，但如果使用2+1方案，虽然需要购买更多硬盘，但15块硬盘里能坏任意5块也不影响系统使用。 更换坏掉的硬盘后系统能自动修复数据。 空间利用率可以参考下表。如果空间需求量大（超过150TB）并且在持续增长，考虑到存储密度和性价比，建议一台服务器一次性配16块硬盘。 不同数量的磁盘及空间利用率可以点击下方链接进行计算 https://min.io/product/erasure code calculator?ref=docs 硬件准备 所需硬件配置。 巴别鸟支持单台服务器搭建对象存储系统（单节点），以硬盘组作为冗余对象。最高可以损坏一半的硬盘也不影响系统的正常使用。 巴别鸟对象存储系统需要客户按要求事先准备好硬件服务器以供部署，最低配置需要2块志强CPU、64GB内存及400G固态硬盘（系统盘）然后增加相应存储容量所需的机械硬盘。 如要计算所需存储空间和购买的硬盘数，可点击下方链接进行计算。 https://min.io/product/erasure code calculator?ref=docs 建议硬件配置如下： 服务器类型 配置要求 操作系统 服务器用途 备注 存储服务器 至强银牌4210 2 20核CPU 64G内存 480G SSD硬盘 +存储所需容量硬盘 硬盘如果考虑性价比，建议使用 8T 12（2U） 或 8T 24（4U）。如果考虑存储密度及未来扩容投入可使用12T硬盘。 Linux 对象存储服务器 未来扩展建议增加相同磁盘容量的服务器。 巴别鸟对象存储使用软件定义存储技术，所以硬盘无需raid，考虑到一些服务器需要raid才能支持多磁盘，这种情况下每块硬盘都做成raid0直通模式即可。 单服务器模式每次扩容需要增加一台配置一致的服务器。扩容时可以不间断服务。 单服务器部署也支持增加一台配置一致的服务器搭建主备模式实时同步，如果一台服务器硬件损坏，可以快速切换到备用服务器。 磁盘有效空间容量和选择的冗余方式有关。譬如：使用8块10T硬盘来组建对象存储系统，采用3+1的冗余方案，相当于4块硬盘一个分组，分为2组，有效可用空间为60TB，同时8块硬盘损坏任意两块也不影响数据及系统使用，替换坏的硬盘即可自动重建。如果采用7+1的冗余方案，有效可用空间就为70TB，8块硬盘里任意损坏1块不影响数据及系统使用。 多服务器部署（分布式）。 巴别鸟对象存储系统支持多服务器部署，如使用服务器为冗余单位，最少要求3台服务器，即2+1模式，但考虑到空间利用率，推荐采用3+1方案（即4台服务器） 每个节点（服务器）的配置要求和上文单服务器部署一致。 建议节点配置一致（相同的操作系统、相同数量的磁盘和相同的网络连接） 每个节点提供的驱动器数量必须相同 节点间的时间差异不能大于15分钟（建议使用NTP确保时间的一致性） 空间利用率计算同单服务器。" }, { "lang": "zh", "slug": "deployment-service-flow", "title": "实施流程与初始化服务", "description": "部署前准备、实施阶段、初始化、培训和数据迁移。", "category": "部署实施", "top_category": "部署指南", "keywords": [ "部署", "实施流程与初始化服务", "私有化" ], "url": "zh/deployment-service-flow.html", "source": "content/zh/deployment-service-flow.md", "summary": "实施流程与初始化服务 私有化要求及服务流程 为了确保使用巴别鸟系统的体验和质量，巴别鸟所有的私有化部署工作都是由巴别鸟团队远程或现场进行部署及签发证书，暂不支持代理团队部署或客户自行部署。同时系统的维护工作也由巴别鸟运维团队进行定期远程维护。客户只需按要求准备好硬件及接入资源，其他事情就交给巴别鸟团队来完成。 私有化部署前期需要准备的： 计算大体使用人数、并发量、存储空间及空间增长率交由巴别鸟客户经理评估所需配置。 客户评估现有服务器剩余资源（如有），根据实际情况选择部署方式。 巴别鸟出具私有化部署方案。 客户根据方案准备相应的服务器及接入资源，分配服务器、安装操作系统。 保证服务器能够在外网远程桌面（也可以使用向日葵）和ssh访问，开启相应端口（我们的部署技术人员会提出具体端口要求） 用户最好能提供一个域名，没有域名的话需要一个固定的ip地址，用ip地址访问的方案需要保证在使用时期ip地址不会发生变动 如需接入邮箱找回密码或手机号发送验证码，需要准备相应的邮箱接入或短信网关。 编号 项目 要求 备注 1 域名 需要一个独立的主域名或二级域名 可以在公司原有域名的基础上设定一个二级域名。如yun.company.com 2 邮箱 需要一个可发送通知邮件的邮箱 支持smtp的邮箱地址即可 邮件推送相关 MailUser=xxxx@mail.com MailPassword=password MailHost=邮件服务器地址 MailPort=端口号 3 远程访问 可远程访问服务器进行配置 支持远程访问及控制服务器 4 SSl证书 https需要申请SSL证书 像数字证书颁发机构C", "headings": [ { "level": 1, "title": "实施流程与初始化服务", "id": "section" } ], "images": [], "text": "实施流程与初始化服务 私有化要求及服务流程 为了确保使用巴别鸟系统的体验和质量，巴别鸟所有的私有化部署工作都是由巴别鸟团队远程或现场进行部署及签发证书，暂不支持代理团队部署或客户自行部署。同时系统的维护工作也由巴别鸟运维团队进行定期远程维护。客户只需按要求准备好硬件及接入资源，其他事情就交给巴别鸟团队来完成。 私有化部署前期需要准备的： 计算大体使用人数、并发量、存储空间及空间增长率交由巴别鸟客户经理评估所需配置。 客户评估现有服务器剩余资源（如有），根据实际情况选择部署方式。 巴别鸟出具私有化部署方案。 客户根据方案准备相应的服务器及接入资源，分配服务器、安装操作系统。 保证服务器能够在外网远程桌面（也可以使用向日葵）和ssh访问，开启相应端口（我们的部署技术人员会提出具体端口要求） 用户最好能提供一个域名，没有域名的话需要一个固定的ip地址，用ip地址访问的方案需要保证在使用时期ip地址不会发生变动 如需接入邮箱找回密码或手机号发送验证码，需要准备相应的邮箱接入或短信网关。 编号 项目 要求 备注 1 域名 需要一个独立的主域名或二级域名 可以在公司原有域名的基础上设定一个二级域名。如yun.company.com 2 邮箱 需要一个可发送通知邮件的邮箱 支持smtp的邮箱地址即可 邮件推送相关 MailUser=xxxx@mail.com MailPassword=password MailHost=邮件服务器地址 MailPort=端口号 3 远程访问 可远程访问服务器进行配置 支持远程访问及控制服务器 4 SSl证书 https需要申请SSL证书 像数字证书颁发机构CA申请。推荐申请 OV 通配符 5 短信接口 如需要手机邀请，手机注册。则需开通短信接口服务（可选） 阿里云、腾讯云等云服务商也提供短信服务接口，申请即可开通 实施阶段 准备工作完成后通知我们，我们会给用户一个具体的实施时间安排，实施时间段内请保持外网访问的畅通 实施一般需要2 3个工作日，第一天远程部署安装巴别鸟，第二天测试和验收，第三天修正遇到的问题 实施完成后我们会通知用户，然后开始初始化阶段 初始化服务 巴别鸟为所有私有云客户提供了初始化服务，服务内容包括： 维护人员培训（远程或是现场） 帮助用户进行数据迁移、用户导入、权限分配等工作（远程或是现场） 使用人员培训 （远程或是现场）" }, { "lang": "zh", "slug": "deployment-third-party", "title": "第三方服务接入", "description": "在线 Office、CAD、签章、OCR、DLP、AI 等第三方服务接入条件。", "category": "集成与扩展", "top_category": "部署指南", "keywords": [ "部署", "第三方服务接入", "私有化" ], "url": "zh/deployment-third-party.html", "source": "content/zh/deployment-third-party.md", "summary": "第三方服务接入 接入第三方服务 作为一个围绕企业文件的办公平台，私有化的巴别鸟企业网盘通过接入第三方API的方式，可以轻松集成各种第三方服务到巴别鸟中，以满足不同的需求这些服务包括但不限于：电子签名、高级CAD预览、office、文字识别、图像识别....等第三方服务来解决您遇到的需求问题。 接入第三方服务的条件 理论上支持BS架构的第三方应用或者服务模块都可以接入。 第三方服务必须提供开放的API，以便巴别鸟企业网盘可以与之集成 如果是互联网服务，需要服务器能访问外网。 需要企业自行或委托我们购买接入的第三方服务的授权 推荐的可接入服务 文件防泄密系统： ipguard 在线office编辑：onlyoffice（自带）、office365、WPS Online、永中office 高级CAD预览：浩辰云图、梦想CAD CAD在线编辑：梦想CAD 在线签章：上上签 文字识别图像识别：百度千帆（智能云） AI相关：智巢AI（自有）、ChatGPT、智谱AI", "headings": [ { "level": 1, "title": "第三方服务接入", "id": "section" } ], "images": [], "text": "第三方服务接入 接入第三方服务 作为一个围绕企业文件的办公平台，私有化的巴别鸟企业网盘通过接入第三方API的方式，可以轻松集成各种第三方服务到巴别鸟中，以满足不同的需求这些服务包括但不限于：电子签名、高级CAD预览、office、文字识别、图像识别....等第三方服务来解决您遇到的需求问题。 接入第三方服务的条件 理论上支持BS架构的第三方应用或者服务模块都可以接入。 第三方服务必须提供开放的API，以便巴别鸟企业网盘可以与之集成 如果是互联网服务，需要服务器能访问外网。 需要企业自行或委托我们购买接入的第三方服务的授权 推荐的可接入服务 文件防泄密系统： ipguard 在线office编辑：onlyoffice（自带）、office365、WPS Online、永中office 高级CAD预览：浩辰云图、梦想CAD CAD在线编辑：梦想CAD 在线签章：上上签 文字识别图像识别：百度千帆（智能云） AI相关：智巢AI（自有）、ChatGPT、智谱AI" }, { "lang": "zh", "slug": "deployment-data-ferry", "title": "数据摆渡部署", "description": "密区与非密区之间的传送文件、审批、端口、token 和审计流程。", "category": "集成与扩展", "top_category": "部署指南", "keywords": [ "部署", "数据摆渡部署", "私有化" ], "url": "zh/deployment-data-ferry.html", "source": "content/zh/deployment-data-ferry.md", "summary": "数据摆渡部署 数据摆渡 巴别鸟数据摆渡支持部署在密区的巴别鸟与部署在非密区的巴别鸟以安全并且带审批的方式互传数据。以实现在企业监管下的密区和非密区的数据交换。 关于巴别鸟数据摆渡的详细信息，可以查阅 巴别鸟数据摆渡 章节。 智巢AI 智巢AI是巴别鸟企业网盘的AI平台，包括智巢AI客服、智巢AI知识库和智巢AI文档助理三个主要模块。这些模块结合了大模型API和自定义训练，能够满足企业的智能客服、文件内容分析和问题回答需求。 智巢AI的三个主要模块 智巢AI客服：该模块充当企业的AI客服，巴别鸟企业网盘自己也用了该模块回答用户在巴别鸟网盘使用中遇到的问题。我们也向企业客户开放这个服务，企业可以将产品说明书、FAQ、客服文档等资料提供给智巢AI进行学习，并微调以满足企业客服需求。企业还可以将智巢AI的代码块嵌入其网站，快速建立对外智能客服系统。智巢AI客服能显著降低客服成本，节约时间和资源。 智巢AI文档助理：这一模块用于回答关于单个文档的问题。通过分析文档内容，智巢AI能够回答关于文档内容的各种问题，从总结到揭示关键发现。用户可以向AI提问，而不必亲自阅读冗长的文档，从而提高工作效率。 智巢AI知识库：这一模块允许企业为自己定制专属AI助手。智巢AI团队会根据企业的资料帮助准备训练集、调参，从而建立专属的AI模型，可以根据巴别鸟上不同权限的人提供权限范围内的答案。可以以问答的形式作为企业知识库助手。 技术解决方案 智能回答问题：智巢AI借助大模型和自定义训练，以保证准确性。它还利用小模型来辅助大模型的工作，减少瞎说话、不懂装懂或泄密等问题。此外，智巢AI遵循巴别鸟的权限管理机制，", "headings": [ { "level": 1, "title": "数据摆渡部署", "id": "section" }, { "level": 3, "title": "智巢AI的三个主要模块", "id": "ai" }, { "level": 3, "title": "技术解决方案", "id": "section-2" }, { "level": 3, "title": "优势", "id": "section-3" }, { "level": 3, "title": "多任务协同与执行流转权重", "id": "section-4" }, { "level": 3, "title": "功能概述", "id": "section-5" }, { "level": 3, "title": "核心运作与配置规则", "id": "section-6" }, { "level": 3, "title": "权限与数据安全控制", "id": "section-7" }, { "level": 3, "title": "典型业务应用场景", "id": "section-8" }, { "level": 3, "title": "功能概述", "id": "section-9" }, { "level": 3, "title": "适用范围与权限控制", "id": "section-10" }, { "level": 3, "title": "核心规则引擎与配置维度", "id": "section-11" }, { "level": 3, "title": "原始名称的精细化修剪与防冲突机制", "id": "section-12" }, { "level": 3, "title": "全局格式化输出控制", "id": "section-13" }, { "level": 3, "title": "功能概述", "id": "section-14" }, { "level": 3, "title": "执行逻辑与边界条件", "id": "section-15" }, { "level": 3, "title": "广泛的格式兼容矩阵", "id": "section-16" }, { "level": 3, "title": "功能概述", "id": "section-17" }, { "level": 3, "title": "灵活的触发机制与作用域", "id": "section-18" }, { "level": 3, "title": "核心智能整理规则引擎", "id": "section-19" }, { "level": 3, "title": "业务场景与功能概述", "id": "section-20" }, { "level": 3, "title": "签章资产库与个性化配置", "id": "section-21" }, { "level": 3, "title": "智能自适应交互与沉浸式引导体系", "id": "section-22" }, { "level": 3, "title": "功能概述与业务价值", "id": "section-23" }, { "level": 3, "title": "标准目录阵列的大规模生成", "id": "section-24" }, { "level": 3, "title": "项目级文件夹与权限的“一键部署”", "id": "section-25" }, { "level": 3, "title": "实时状态监控与智能容错机制", "id": "section-26" }, { "level": 3, "title": "使用范围", "id": "section-27" }, { "level": 3, "title": "需要解决的问题", "id": "section-28" }, { "level": 3, "title": "巴别鸟解决方案", "id": "section-29" }, { "level": 3, "title": "基本介绍", "id": "section-30" }, { "level": 2, "title": "用户界面", "id": "section-31" }, { "level": 2, "title": "性能优化", "id": "section-32" }, { "level": 3, "title": "优势", "id": "section-33" }, { "level": 3, "title": "优势", "id": "section-34" }, { "level": 3, "title": "优势", "id": "section-35" }, { "level": 3, "title": "优势", "id": "section-36" }, { "level": 2, "title": "可扩展性", "id": "section-37" }, { "level": 2, "title": "私有化部署", "id": "section-38" } ], "images": [], "text": "数据摆渡部署 数据摆渡 巴别鸟数据摆渡支持部署在密区的巴别鸟与部署在非密区的巴别鸟以安全并且带审批的方式互传数据。以实现在企业监管下的密区和非密区的数据交换。 关于巴别鸟数据摆渡的详细信息，可以查阅 巴别鸟数据摆渡 章节。 智巢AI 智巢AI是巴别鸟企业网盘的AI平台，包括智巢AI客服、智巢AI知识库和智巢AI文档助理三个主要模块。这些模块结合了大模型API和自定义训练，能够满足企业的智能客服、文件内容分析和问题回答需求。 智巢AI的三个主要模块 智巢AI客服：该模块充当企业的AI客服，巴别鸟企业网盘自己也用了该模块回答用户在巴别鸟网盘使用中遇到的问题。我们也向企业客户开放这个服务，企业可以将产品说明书、FAQ、客服文档等资料提供给智巢AI进行学习，并微调以满足企业客服需求。企业还可以将智巢AI的代码块嵌入其网站，快速建立对外智能客服系统。智巢AI客服能显著降低客服成本，节约时间和资源。 智巢AI文档助理：这一模块用于回答关于单个文档的问题。通过分析文档内容，智巢AI能够回答关于文档内容的各种问题，从总结到揭示关键发现。用户可以向AI提问，而不必亲自阅读冗长的文档，从而提高工作效率。 智巢AI知识库：这一模块允许企业为自己定制专属AI助手。智巢AI团队会根据企业的资料帮助准备训练集、调参，从而建立专属的AI模型，可以根据巴别鸟上不同权限的人提供权限范围内的答案。可以以问答的形式作为企业知识库助手。 技术解决方案 智能回答问题：智巢AI借助大模型和自定义训练，以保证准确性。它还利用小模型来辅助大模型的工作，减少瞎说话、不懂装懂或泄密等问题。此外，智巢AI遵循巴别鸟的权限管理机制，确保用户只能获取其权限范围内的答案。 自动学习：智巢AI可通过学习用户提供的文件来积累知识，为用户提供更准确的答案。所有参与训练的文档都是由用户指定并同意的，以确保数据隐私和合规性。 优势 客服成本降低：智巢AI客服可以显著减少企业的客服成本，无需大规模培训人员，AI可以随时提供答案。 快速问题回答：智巢AI能够即时回答用户的问题，提高了工作效率。 文件内容分析：智巢AI文档助理可以快速分析文档内容，帮助用户快速获取信息，而无需阅读整个文档。 自定义AI助手：企业可以根据自己的需求为智巢AI知识库定制专属AI助手，以满足特定的知识管理和问题回答需求。 权限管理：智巢AI能够根据用户权限提供不同范围内的答案，以确保数据安全和合规性。 自动化任务 面对日益增长的数字资产，传统的人工文件管理模式已难以满足高效流转的需求。巴别鸟推出的 “自动化任务”引擎，旨在将繁琐、重复的文件处理动作交由系统后台自动执行。通过建立“自组织、自规范”的智能流转体系，大幅降低人工干预成本，让团队将精力聚焦于核心业务创造。 自动化任务包含在标准版中，用户无需另行购买。 核心运作机制： 灵活的权限驱动： 依托平台极细颗粒度的权限管理体系，凡具备目标网盘或文件夹相应权限的用户，均可按需自主配置、开启或关闭特定的自动化任务。 多任务流串联 (Workflow)： 自动化任务并非孤立运行，支持多规则自由组合形成工作流。例如：文件上传后，系统可先触发“自动重命名”规范文件名称，随后立即触发“自动整理”将其归档至相关目录，实现多步骤一气呵成。 持续扩展的能力矩阵： 自动化引擎具备高度的扩展性。除了现有的基础功能外，平台将持续接入更多的自动化处理节点，以满足日益复杂的业务场景。 当前已支持的核心任务（包括但不限于）： 自动重命名： 按预设规则（如关键字替换、大小写转换）统一标准化命名。 自动整理与清理： 依据触发条件自动分类归档文件，或按策略定期清理空间。 自动转 PDF 与签章： 自动为源文件生成 PDF 副本，或在云端加盖企业签章。 批量创建文件夹： 通过导入数据模板（如 Excel）一键生成标准业务目录树。 多任务协同与执行流转权重 在复杂的业务场景中，一个文件夹往往会叠加配置多项自动化任务。为保障数据处理的逻辑严密性与安全性，系统底层预设了严格的自动化处理先后顺序 。 具体执行权重（数值越高越优先执行）规范如下： 自动清理文件夹（权重 10）： 系统最高优先级。如有符合条件的清理任务将率先执行，以避免对即将被废弃的无效数据投入后续算力 。 自动解压缩（权重 9）： 优先将打包资产释放，以便进入后续流转 。 自动更名（权重 8）： 在文件进入分类归档前，优先完成命名的标准化统一 。 自动格式转化类（权重 7）： 优先完成如转存 PDF、图片或音视频格式的转换任务 。 自动整理 / 排序（权重 6）： 作为流转的末端节点执行 。这意味着文件在被移动和分类前，均已完成了清洗、重命名与格式转换等核心前置标准化操作。 自动清理文件 (Auto Clean) 功能概述 在日常的跨部门协作或项目周期管理中，企业网盘内往往会不可避免地产生大量的临时数据、过程文件或短期流转素材。 “自动清理文件” 功能旨在为企业提供自动化的存储空间优化与目录瘦身方案。通过该功能，系统能够按照用户设定的特定规则，自动删除指定文件夹中的冗余文件，长效保持项目目录的整洁度并释放高价值的存储资源。 核心运作与配置规则 本模块通过严密的逻辑规则引擎执行文件的清理动作，确保数据处理的精准与高效： 目标目录锁定： 任务配置需明确指定应用该规则的目标文件夹。用户可选择将规则仅应用于新进入该文件夹的文件，或同时溯源应用于目录内已存在的历史文件。 多维规则触发： 支持基于特定规则对文件进行精准筛选与剔除。常见的判定规则可涵盖文件类型（如特定后缀的临时文件）、生命周期（如文件进入目录超过指定天数）等维度，实现高度定制化的清理策略。 工作流协同： 作为完整自动化流转的末端环节，自动清理可与其他任务无缝衔接。例如，在“自动转 PDF”任务完成后，系统可随即触发“自动清理”规则，将原始草稿文件进行统一清理，仅保留标准化定稿。 权限与数据安全控制 鉴于清理任务涉及文件删除这一敏感操作，该功能深度依托巴别鸟的极细颗粒度权限管理体系： 配置权限： 仅拥有该文件夹相应高级权限（如管理、删除权限）的协作成员，方可新建或修改自动清理任务，从源头杜绝越权操作造成的数据流失。 无感且安全的执行： 后台静默执行清理任务，减少对用户前端操作的干扰，同时严格遵循企业既定的数据合规与回收站保留策略，确保数据资产的绝对安全。 典型业务应用场景 设计与研发类项目： 在建筑设计或科研管理中，工作软件常会自动生成大量的备份或缓存文件（如 .bak 或临时渲染文件）。通过配置自动清理任务，可设定定期自动识别并删除特定后缀的无用文件，保持核心图纸与文献目录的纯净。 公共资料交换区： 针对企业内部设置的“临时中转站”或“临时分享区”，可配置按时间维度（如“保留 7 天后自动清理”）的自动清理任务，实现公共空间的自组织与自净化，降低运维管理成本。 自动重命名 (Auto Rename) 功能概述 在多方协作、多频次资料收集的业务场景中，由于操作人员习惯差异，文件命名往往缺乏统一规范，给后续的检索、归档与审计带来极大困扰。 “自动重命名” 功能允许系统对上传至指定文件夹的文件，按照高度定制化的预设规则进行自动化的名称重构 。该机制有效杜绝了因人为因素导致的命名混乱，确保企业数据资产入库即达标。 适用范围与权限控制 权限驱动： 该功能的启用严格依托于用户的操作权限。只要用户对目标文件夹（涵盖个人、部门、项目或素材库等各类文件夹）拥有“上传”及“重命名”权限，即可为其配置自动重命名任务 。 溯源处理： 规则不仅作用于新上传的文件，用户还可选择将其溯源应用于目标目录及其所有子文件夹中已存在的历史文件 。为保障系统性能与执行稳定性，批量溯源重命名的单次处理上限为 5000 个文件 。 核心规则引擎与配置维度 巴别鸟提供了一个高度灵活的可视化规则拼接引擎。用户可添加多个命名规则，并通过拖拽的方式对规则进行自由排序 。配置界面全程提供实时变化的“示例文件名”，帮助用户直观预览重命名规则的叠加结果 。 规则引擎支持以下多维度的命名元素： 标准属性变量： 支持提取并插入系统级变量，包括文件上传者、文件负责人、上级文件夹名称以及上传时间 。 多媒体元数据 (Metadata)： 针对图像等特定格式文件，系统可深度解析并提取其底层元数据作为命名依据，如拍摄日期、相机制造商/型号、镜头型号、尺寸以及 DPI/DPCM 等参数 。 自定义文本与连续编号： 用户可自由插入自定义文本内容 。在编号机制上，与传统的单次批量重命名不同，自动重命名具备状态记忆（延续性）。系统会自动读取目标列表中最后一个符合规则的编号，确保跨批次、跨时段上传的文件能够实现序号的无缝延续 。用户可精确设定编号的起始值、增量值及具体位数 。 原始名称的精细化修剪与防冲突机制 除了添加新前/后缀，系统同样支持对文件原有的名称进行深度结构化清洗： 名称修剪与替换： 可对原始文件名执行“替换特定内容”、“删除指定内容”操作 。此外，还提供一键“删除字符”功能，精准剔除文件名中的冗余空格、数字、引号、破折号及下划线 。 强制防冲突保护： 若用户在规则中选择完全删除“原始文件名”（即上传时不保留原名），为避免同名文件相互覆盖的风险，系统会强制要求并在规则链中自动追加一项“编号”规则 。 日期逻辑互斥： 在调用日期类变量时，用户可勾选“替换在文件名中检测到的日期” 。为防止逻辑冲突，在单一重命名任务中，该替换指令仅允许被某一时间变量（如“上传时间”或“拍摄时间”）勾选一次 。 全局格式化输出控制 在完成规则变量的拼接后，系统支持在输出端进行统一的格式化规范： 大小写标准化： 支持一键将拼装后的文件名转换为首字母大写、首字母小写、全部大写或全部小写，满足不同企业的视觉规范 。 字词分隔统一： 支持在各个命名规则模块之间统一插入标准化的分隔符（如空格、下划线或破折号），进一步提升文件名的机读与人读体验 。 自动转 PDF (Auto to PDF) 功能概述 在跨企业协作、外部资料分发以及项目定稿归档等业务环节中，PDF 格式因其跨设备显示的一致性与防篡改特性，成为了标准的文档交换媒介。巴别鸟的“自动转 PDF”功能，旨在建立一个自动化的文件格式标准化通道。配置该任务后，当文件被添加到选定的目标目录，系统将在后台静默触发转换引擎，将其自动转换为标准的 PDF 文件 。该能力大幅消除了人工逐一导出 PDF 的低效劳动，确保了数据对外输出与对内归档的规范性。 执行逻辑与边界条件 为保障平台底层计算资源的高效运转以及企业数据流转的安全可控，自动转换任务设定了以下执行逻辑与边界限制： 作用域与溯源处理： 该任务可向下覆盖，支持勾选应用于目标目录及其所有子文件夹中的文件 。此外，规则同样支持向历史数据溯源，可应用于目录内的现有文件，但为保障执行稳定性，单次溯源处理的文件数量被严格限制在 5000 个以内 。 系统性能保护机制： 为避免超大源文件在转换过程中长时间占用算力并导致任务队列阻塞，系统内置了文件体积阈值，即超过 30MB 的大体积文件将不会触发自动转换机制 。 存储空间自动释放： 针对“仅需保留定稿 PDF”的特定业务场景，用户可在任务配置界面勾选“转换成功后删除原文件”选项 。开启该策略后，系统将在确认 PDF 副本生成无误的前提下自动清理原始文件，从而大幅度优化网盘存储空间的利用率 。 广泛的格式兼容矩阵 巴别鸟自动转换引擎具备强大的多格式解析能力，支持将 32 种不同行业的主流业务文件自动化转储为 PDF 。用户可选择针对“所有支持的文件”执行转换，也可通过下拉菜单按类别精准勾选所需转换的扩展名 。具体支持的格式矩阵如下： 文档排版类： 全面兼容主流办公与出版软件产生的源文件，包括 doc、docx、ppt、pptx、wps、epub、dpt、indd、rtf、docm 以及 pptm 。 图片与影像类： 支持主流位图、数字底片及医疗影像格式的渲染转换，涵盖 jpg、bmp、jpeg、jpg2、png、psd、tif、tiff、raw、cr2、dcm 以及 heic 。 图形与工程图纸类： 深度适配设计与建筑工程领域的矢量及 CAD 图纸转换，支持的格式包含 ai、svg、eps、dwg、dwt 以及 dxf 。 自动整理文件 (Auto Organize) 功能概述 随着平台内协作数据的沉淀，如何保持底层“任意文件夹同步”架构与权限管控目录的整洁，成为了企业数字资产管理的关键。 “自动整理文件” 功能允许系统按预置的时间周期或内容特征，将文件自动分类并路由至相应的目标目录。该功能确保了海量文件在流转过程中的高度结构化，避免了人工归档的滞后性与错漏。 灵活的触发机制与作用域 用户可通过文件夹右键菜单中的“任务”选项 ，或左侧的自动化任务列表面板进入配置 。配置涵盖以下触发与作用规则： 事件驱动（默认）： 当文件被上传或者移动到指定的触发文件夹时，系统即刻响应并开始整理动作 。 周期驱动： 适用于集中式的数据归档场景，系统可按固定的周期（例如设定为每天 23:00）统一执行文件整理 。 历史溯源： 规则既可应用于新增文件及所有子文件夹，也可勾选“应用于现有文件”对历史存量数据进行批量溯源整理。为保障系统平稳，溯源处理单次不得超过 5000 个文件 。 核心智能整理规则引擎 系统提供三种高度自定义的分类规则，满足不同维度的数据归档需求： 1. 基于时间维度的结构化归档（按月 / 按年分类） 系统可按文件添加到网盘的对应年份或月份自动创建对应的子文件夹（例如“2025”、“2025 10”）并将相关文件移入 。 执行按年或按月分类时相同 ，系统具备按需建档的智能性，如果特定周期内（如某个月）没有产生文件，则系统不会冗余创建该月的空文件夹 。 2. 基于内容的智能路由（按关键字分类） 根据文件名中包含的特定关键字，系统将文件自动分发并移动至预设的目标文件夹 。 格式识别： 文件扩展名（如“jpg”）同样可作为关键字配置，实现特定类型素材的定向归集 。 多线并行路由： 用户可通过“添加关键字分类”按钮持续增加多条路由规则 。既支持将包含不同关键字的文件分别分发到不同的目录 ，也支持将多条关键字任务统一指向同一个目标文件夹 。 防重名与优先级控制： 关键字匹配严格按任务设定的先后顺序处理。例如，当文件名为“123ABC定稿.jpg”，若关键字列表第一项规则为“123”，第二项为“定稿”，则该文件将优先匹配“123”的规则并执行移动 。系统内置防重复检测，每个关键字仅允许输入一次，重复输入会触发“请重新输入”的错误拦截 。 同名冲突化解： 在执行文件移动与整理的过程中，如在目标文件夹内遇到重名文件，系统会自动在文件名后附加编号，以确保数据不被意外覆盖 。 创建签章 (E Sign) 业务场景与功能概述 在企业的合同审批、图纸会签及业务合规流转等关键环节中，具备防篡改属性的数字化签署是打通线上协作闭环的核心节点。传统的跨系统签署往往伴随繁琐的文件下载与格式转换。巴别鸟推出的 “创建签章” 功能，允许用户直接在云端网盘的工作流中对文件进行盖章与签署 。该引擎支持多种主流文件类型直接加载印签，并支持将签署完毕的文件一键导出为标准的 PDF 格式，从源头保障数字资产的安全、合规与不可篡改性 。 签章资产库与个性化配置 系统为用户提供了一个高度集成的数字印签管理控制台，确保电子签章资产的统一沉淀与快速调用： 多元签名采集： 在“签名设置”模块中，用户既可以调用终端进行在线“添加手写签名”，也支持直接“上传签名图片文件”（如含透明通道的 PNG 素材），以满足不同层级的签署合规要求 。 企业图章管理： 在“图章设置”模块，企业用户可按需上传业务专用的电子公章或合规图章图片 。 默认优先级状态： 针对拥有多个印签资产的用户，系统支持一键将其中的特定签名或图章“设置为当前使用”（默认印签） 。在后续的文档预览与流转界面中，系统将优先调用该默认印签，极大提升高频审批场景下的签署效率 。 智能自适应交互与沉浸式引导体系 为兼顾不同硬件终端的显示极限并降低用户的学习门槛，签章配置中心采用了多断点的智能响应式（Responsive）界面架构，并深度嵌入了多语言操作指引： 宽屏工作站模式（窗口宽度 ≥ 1120px）： 当用户在桌面级宽屏设备上操作时，系统不仅在左侧保留标准的签章配置面板，还会在右侧自动展开独立的视频教学区。该区域会自动加载并无感循环播放签章使用教程（播放完毕停顿 3 秒后重播），为用户提供“边学边配”的沉浸式体验 。 紧凑聚焦模式（窗口宽度 ＜ 1100px）： 当处于较窄的屏幕或移动端窗口时，系统会智能折叠右侧的视频播放区，以最大化保障核心签署设置区的视觉焦点 。同时，系统在界面底部提供“如何使用签章？”入口，用户点击后可唤起全屏教程播放 。 国际化双语支持： 考虑到跨国企业的协作需求，系统内置了本地化的教学视频库。除中文语言环境播放专属中文教程外，其他所有多语言版本均默认匹配并播放标准英文教程，保障全球业务团队的无障碍落地 。 批量创建文件夹 (Batch Create Folders) 功能概述与业务价值 在多项目并发或企业部门架构调整的业务场景中，由人工逐一建立复杂的标准目录树不仅耗费大量操作时间，且极易因人为疏漏导致目录层级错乱或命名不规范。巴别鸟提供的 “批量创建文件夹” 功能，允许用户通过外部结构化数据（如 Excel、CSV、TXT 文本）直接驱动云端目录的生成 。该功能可将标准化的业务目录模板瞬间转化为可落地的网盘文件夹阵列，极大提升了大型项目启动阶段的初始化建档效率。 标准目录阵列的大规模生成 该模块具备强大的数据解析能力与人工容错干预机制： 高并发支持： 系统支持通过导入 xls、xlsx、csv 或 txt 格式的文件，按换行符规则快速读取目录清单，单次批处理任务的上限高达 5000 行，满足绝大多数企业级数据结构的生成需求 。 可视化预审与动态干预： 在正式执行批量创建前，系统会完成数据解析并在界面中直观渲染出即将生成的文件夹列表与层级关系 。在此预览环节中，用户可直接通过鼠标右键或悬浮菜单，对特定的预设目录执行“创建子文件夹”、“重命名”或“删除”等即时修改动作 。这一“先审后建”的机制，确保了最终落地的目录树与业务需求绝对对齐。 项目级文件夹与权限的“一键部署” 当目标路径设定为部门文件夹或个人文件夹的根目录时，系统支持创建更为高阶的 “项目文件夹” 。该模式深度结合了巴别鸟的底层权限管理体系，实现了目录构建与成员权限配置的同步落地： 专属标准模板： 批量生成项目文件夹需下载并使用系统专属模板导入数据 。若上传的非标文件不符合解析格式，系统将严格拦截并提示重新上传 。 项目角色与权限预设： 模板不仅规范了“项目文件夹名字”，还支持直接关联账号系统预设“项目负责人”与“项目成员” 。 负责人指派： 填写的负责人 ID（支持手机号、邮箱或特定的工号格式）必须为已注册的企业成员；若该字段留空或填写的身份无法校验，系统将遵循安全保底原则，默认将当前创建任务的操作者设为项目负责人 。 成员自动化邀请与赋权： 用户可在模板中通过逗号分隔批量录入多位项目成员 。项目目录生成后，系统将自动向这些成员发送邀请通知，并为其赋予基础的“上传及下载”默认权限 ，彻底免除了建档后繁琐的逐一授权操作。 实时状态监控与智能容错机制 在执行大规模创建任务时，系统后台会以队列形式稳健处理，并在前端提供全方位的进程监控与异常修复闭环： 全局进度追踪： 创建过程中，列表节点会实时更新其执行状态（从代表正在执行的转圈动画，平滑过渡至代表成功的确认勾选状态） 。任务全局状态亦会从“创建中”明确流转至“完成” 。 精准异常归因与重试： 全部任务执行完毕后，系统顶部会输出清晰的结果汇总（如“共创建了 XXX 个文件夹，失败 X 个”） 。用户可一键查阅“创建失败文件列表” 。系统会将失败原因精确归类为“包含文件名不允许字符”或“已有同名文件夹”等系统级冲突 。针对这些异常条目，用户不仅可以查明原因，还能直接在界面上点击绿色的“重试”按钮触发二次创建 ，大幅降低了批量运维的阻力。 文控项目 文控项目是巴别鸟的一个行业应用独立模块（需要另行购买）。巴别鸟文控项目解决了工程设计行业中的文控标准的流程管理（DCC）及自动化问题。提高了大量文控人员的工作效率的同时也降低了人为失误的可能。 使用范围 需要严格管理每一次文件发送的行业或企业。每次发送给客户的文件都由特定人员发送（文控人员）每次发送都有发送单据可查，能明确的管理发送内容。通过发送单号可以查询到每次发送文件给接收方的具体信息和文件。同时对接收方是否收件，对发送过去的内容是否驳回都可管理查询。并且发送单可以作为凭据。 需要解决的问题 目前很多企业的文控流程基本是靠手动，文件存储于EDMS系统或文控人员电脑本地。依靠文件夹分类来管理文档，每次发送文件手动建立一个文件夹，按文件名规范命名文件夹，文件通过邮件发送后把发送的文件放入文件夹并附上本次发送的TRANSMITTAL（文件发送单）。 每次发送都会产生一个文件夹及相应的TRANSMITTAL。这些工作人工操作相当繁琐，除了整理文件，每次还需要手动填写文件发送单，手动按规则编写发送单编号，日后还要手动核对，效率极低。 巴别鸟解决方案 可新建新的文控项目类型。这意味着不同的项目可以设定不同的TRANSMITTAL（发送单）规则生成不同的发送单和发送单号。不同项目也可以管理不同的收件人（收件企业） 可设定每个项目的文件接收方，统一管理文件接收方。 文控项目中的文档支持发送功能，发送功能支持多选。选择文件或文件夹发送后，收件人可以通过邮箱收到所发送文件的下载link和TRANSMITTAL（发送单）。并且通过下载link下载到的文件是发送时的版本。 每次发送的文件都是文件当前版本，文件升版会形成新的版本号，并在发送单显示。 文件发送后根据预先设定的规则自动生成本次发送的TRANSMITTAL（发送单）和TRANSMITTAL NO.（发送单号） 可以管理及查询所由TRANSMITTAL（发送单），并可导出发送单为PDF。 巴别鸟文控项目使用指引： 基本介绍 巴别鸟文控管理系统是在巴别鸟企业私有云版的基础上增加文控管理模块，以实现文控工作的自动化。 文控管理的方式是以建立“文控项目”的方式来实现。文控项目是针对文控需求特别定制的特殊项目，以项目为单位进行管理。 建立文控项目 登录系统后，在要创建文控项目的部门中点击“新建”——“新建项目” 项目只能建立于根目录（企业文件）或部门根目录下 例：在HQSM文控这个部门下建立一个文控项目 点击新建项目，出现项目类型选择界面 选择“创建文控管理项目” 这时候出现项目初始化选择界面 按照项目的要求填写初始化信息 每项的介绍如下： 项目负责人 管理、转交项目、修改项目权限及基础信息。不可为空。可删除TRANSMITTAL 项目秘书 不可转交项目，其他同项目负责人，可多人，可为空。可删除TRANSMITTAL 文控人员 可以发送文件给接收人。其他权限可配置，可多人，可为空。选择人员后点击右侧权限选择下拉框可以批量修改成员权限（如图）。 其他成员 没有发送文件选项，其他同普通项目普通成员，权限可配置，可为空。 版本号规则 如图，如果前缀填写为HQSM，文件的第一个版本就为 HQSM A ，第二个版本为 HQSM B以此类推 基本信息 基本信息的填写内容将显示于TRANSMITTA头部。 如图：画红圈处就是填写的基本信息。 接收方信息 接收方信息决定了发件时的可选项和所发文件的TRANSMITTA号 收件方名字是指收件方在系统中的称呼，一般填写收件方的企业简称，如 MCC 邮箱支持添加多个，添加多个后，一次发送就可以向多个邮箱地址发送文件及TRANSMITTA ATTN可以任意输入，同时也会显示在TRANSMITTA上 运单号规则其实就是TRANSMITTA号的自动生成规则，不同的收件方可以生成不同的运单号。所以需要在每个收件方处设定不同的运单号规则。 规则自定义界面示意如下： 3栏分别为TRANSMITTAL号的3个组成部分，如果所需的TRANSMITTA号需要更多的编码来组成也可以点击+号来增加更多栏 例： 第一栏选择输入文字，弹出文字输入框，输入 “HQSM ” 第二栏选择编码规则为1 2 3数字顺序 第三栏选择 文字输入、输入“ 2020” 点加号新增一栏，选择a b c字母顺序 第一次发送生成的TRANSMITTAL号即为： HQSM 1 2020a 第二次发送生成的TRANSMITTAL号为：HQSM 2 2020b 选择字母作为编号超过26个后，z号的下一个版本自动变为a1 如果该项目有多个接收方，也可以点击来增加。（项目建立后也可以在项目管理界面中去增删接收方。 这些填写完成后，点击“新增项目”就完成了项目的新建 你可以在创建项目路径的文件列表中看到新建的文控项目，点击即可进入 文控管理项目不同于普通项目，项目首页顶部栏增加了文控管理的按钮 其中“发送单列表”可以查询该项目发出的所有TRANSMITTA，管理项目可以对项目进行管理。 上传文件 点击新建的文控项目，进入项目页面。 直接拖拽想要上传的文件到项目中即可上传文件，当然，你也可以和使用普通文件夹一样使用同步功能进行上传下载。 发送文件 选中要发送的文件（支持多选），然后点击右键，选择“发送文件”会出现文件发送界面 每次最多发送的文件为2000个（包含文件夹）。如项目需要全部文件发送，建议以压缩包形式进行发送。 收件人可以下拉选择项目初始化时填写的收件人及ATTN 抄送可以填写其他任意邮箱地址，也可以留空不填写 选择的提交文件类型也会在生成的TRANSMITTA中显示 文件列表罗列了本次要发送的文件。 系统要发送TRANSMITTAL的文件名构成为 文件编号+描述，如一个文件文件名为 1000+图纸.pdf，发送时显示在TRANSMITTAL的文件编号为“1000”，描述为“图纸”。如果发送的文件的文件名中没有+分割，文件编号就显示文件名，如果发送的文件名为“+图纸.jpg“就不显示文件编号，显示描述为“图纸”。描述可中途更改。 附言将会在收件人接受到的邮件中显示并不会显示在TRANSMITTAL中 填写完成后点击“发送文件”系统会自动生成TRANSMITTAL并作为link附在邮件中发送给客户。 生成TRANSMITTAL 发送成功后系统会弹出提示 点击查看，就能查看本次发送自动生成的TRANSMITTAL 点击导出为PDF就可以把该TRANSMITTAL保存为PDF文件 你也可以在传送单列表（TRANSMITTAL list）中去查看该项目中发送的所有TRANSMITTAL 收件人在邮箱中收到的TRANSMITTAL和该TRANSMITTAL一致。 查看TRANSMITTAL 在项目首页点击发送单列表（TRANSMITTAL list） 打开列表就可以看到及查询本项目的所有发送单。 点击传送单号可查看详情并下载TRANSMITTAL的PDF文件 为接受就是接受方并没有打开已发送的邮件，如对方打开邮件并访问了TRANSMITTAL，接收状态会变为已接收。 查看发送记录 在任意文件上右键点击，可查看该文件的发送记录及其对应的TRANSMITTAL 用户界面 用户界面设计 巴别鸟界面设计理念 企业网盘集成的功能比较多，如何合理分配功能入口，让用户实际使用时更加方便？是一个界面设计和交互时需要重点考虑的问题，目前有两种互有冲突的设计理念。 界面设计理念 优缺点 隐藏非常用功能，保证界面简洁，降低学习难度，易上手，初次使用体验友好。（代表：微云、腾讯文档等2C产品） 前缓后陡的学习曲线，用户初次试用时体验好，但实际长期使用时不方便 功能入口显性化，界面复杂，但需要的功能可以快速找到。界面较重，学习成本稍高，初次使用体验不友好。（代表：office、CAD等专业软件） 前陡后缓的学习曲线，用户初次使用体验复杂，但实际长期使用方便。不利于营销。 考虑到企业网盘是一个面向企业长期使用的专业产品，前期陡峭的学习曲线虽然不利于营销（用户简单试用时弃用率增高）但是对应选择巴别鸟的用户长期使用是友好的，熟悉后能更好用更有条理，而作为一个生产力工具，日常使用的便捷度和降低出错概率更加重要。所以巴别鸟企业网盘选择了第二种设计理念： 作为一个专业面向企业场景的产品，为用户长期日常使用时的便捷性，可以适当增加上手复杂度。 界面设计原则 用户友好性: 在保证功能使用优先的前提下，强调用户友好性，确保用户能够轻松使用企业网盘。 一致性: 维持一致的界面设计，以提供一致的用户体验。 简洁性: 采用简洁的设计，减少冗余和复杂性，使用户能够迅速理解界面。 可用性: 确保功能模块容易被用户找到并有相应指引，3步内直接可以使用。 用户界面元素 网页版（web） 采用左菜单、右文件列表、顶部功能分区的布局。方便用户注意力集中在文件列表上。 左侧菜单可以收起，显示更多文件列表内容，提供沉浸式体验。 为了更好的树状管理文件，也可以打开树状视图类似windows资源管理器一样管理文件。 如果文件夹图片文件数量多，可自动打开瀑布流预览模式，便于用户查看。 左侧菜单（快捷方式）用户可以自定义，便于用户日常按使用习惯自定义快捷入口。 文件/文件夹的所有功能操作集中在右键，容易找到，常用功能显示在文件列表上，同时文件列表栏也有相应按钮，防止因鼠标右键失效影响用户操作。 客户端（windows、mac、麒麟） 客户端使用Electron及C++进行跨平台开发，很好的保证了风格一致性和操作一致性。并且针对各平台也有各自的优化。客户端还包括同步模块、上传下载列表及虚拟映射盘（云桥）模块。 主操作界面延续网页版风格和布局，但针对本地软件的使用习惯及客户端独有模块进行了布局上的改进，把顶部功能分区集中在左侧栏，让顶部显示更简洁。 左侧栏增加了传输和同步两个客户端独有功能按钮及入口。 文件传输模块，管理同步进程和上传下载任务。 在windows和MacOS系统文件右键菜单上集成了同步和上传、发送文件的快捷方式，便于用户快速建立同步和上传文件（夹）。 在windows和MacOS上集成了虚拟映射盘，让用户可以像访问本地硬盘一样访问云端文件。 响应式设计 响应式设计原则 多设备兼容性: 巴别鸟企业网盘的用户界面被设计为在各种设备上获得最佳体验，包括桌面、移动设备和平板电脑，以保证用户随时随地用各种设备都能有良好的体验。 图：巴别鸟从诞生起就是跨平台的 自适应布局 用户界面元素会自动根据屏幕尺寸和方向进行调整，以确保内容的可见性和可用性。 触摸友好性: 优化移动设备上的触摸交互，包括手势控制、滑动和缩放。 图像和媒体优化: 使用了预载入、图像转码生成缩略图和媒体压缩技术，以减少页面加载时间和带宽使用。 移动端支持 网页版本移动设备优化 移动界面设计: 巴别鸟网页版本有针对移动设备打开设计的H5页面，及宣传网站移动版及分享链接移动版下载界面，支持常见触摸手势，如滑动、缩放和点击。 图：移动设备访问巴别鸟H5页面 移动APP: 为了获得更好的使用体验，巴别鸟开发了移动端专用的APP，支持安卓和iOS系统。 为保证良好的性能，巴别鸟APP都以原生应用的方式进行开发。 APP的交互、界面、功能模块都全部重新设计，以适合在移动设备上访问。 图：移动端界面 平板电脑优化 巴别鸟iOS APP针对iPad重新设计制作了界面，以更适应在大屏幕上工作。 性能优化 负载均衡策略 鉴权认证与服务分离 分离鉴权认证: 为了提高系统的性能和安全性，巴别鸟企业网盘采用了鉴权认证与核心服务分离的策略。这意味着用户的鉴权认证请求会被路由到专门的认证服务器上，而上传、下载以及查询浏览等核心服务请求会被路由到相应的核心服务服务器上。 请求路由: 我们使用负载均衡器来根据请求类型将请求路由到不同的服务器。这确保了鉴权认证服务器不会成为核心服务的性能瓶颈，并允许我们根据需求独立扩展认证和核心服务。 相同类型请求的多台服务器部署 多服务器支持: 巴别鸟企业网盘允许相同类型的请求在多台服务器上部署，以提高性能和可用性。这种多服务器支持策略确保了即使一台服务器出现故障，其他服务器仍然可以处理请求。 请求平均分配: 我们使用负载均衡算法将相同类型的请求均匀分配到多台服务器上，以避免服务器过载和提供更快的响应时间。 负载均衡器 负载均衡器配置: 我们使用专业的负载均衡器来实现请求的分发和路由。负载均衡器根据预定的规则将请求发送到适当的服务器。 监控和自动故障转移: 负载均衡器配备了监控功能，能够检测服务器的健康状态。如果某台服务器出现故障，负载均衡器会自动将请求路由到其他可用的服务器，以确保系统的连续性。 优势 性能提升: 负载均衡策略提高了系统的性能，允许请求在多台服务器上并行处理，减少了单一服务器的负载。 高可用性: 多台服务器的部署和自动故障转移确保了系统的高可用性，即使出现故障，仍然可以提供服务。 扩展性: 负载均衡策略允许根据需求添加更多的服务器，以满足不断增长的用户和请求。 缓存管理 文件缓冲区管理 文件缓冲区设置: 为了优化性能并减轻CPU资源负担，巴别鸟企业网盘实施了文件缓冲区管理。解密后的文件将暂时存储在缓冲区中，以减少重复解密操作。 LRU策略: 我们采用最近最少使用（LRU）策略来管理文件缓冲区。这意味着最不常使用的文件缓存将被淘汰，从而保持缓冲区的高效利用。 文件鉴权缓冲管理 文件鉴权缓冲: 鉴权检测对于文件访问的权限是复杂而耗时的。针对文件所在部门、项目、分享以及保密级别等多个因素，需要进行综合性的鉴权检测。为了提高性能，我们实施了文件鉴权缓冲，将鉴权结果缓存起来。 过期淘汰机制: 文件鉴权缓冲采用过期淘汰机制。每个缓存条目都有一个预定的过期时间，一旦超过该时间，缓存将被自动淘汰。这确保了缓存数据的新鲜性，并降低了内存使用。 优势 性能优化: 缓存管理减少了解密操作和鉴权检测的重复执行，从而提高了系统的响应速度和性能。 资源节约: 通过使用LRU策略和过期淘汰机制，我们有效地管理了内存资源，避免了内存泄漏和过度占用的问题。 复杂鉴权的快速响应: 文件鉴权缓冲确保了复杂的鉴权检测结果的快速响应，减少了对鉴权服务的压力。 数据压缩和传输优化 文件分块技术 文件分块存储: 为了优化文件的传输和存储，巴别鸟企业网盘采用了文件分块技术。大文件会被分成小块，并分别存储在服务器上。这有助于提高文件的传输效率和断点续传的支持。 并行块请求: 文件分块存储允许前端在文件下载时并行发起多个块的请求。一旦所有块都被下载，前端将它们组装成完整的文件，从而显著提高了下载速度。 基于哈希码的文件存储去重技术 文件去重: 巴别鸟企业网盘采用基于哈希码的文件存储去重技术。当用户上传文件时，系统会计算文件的哈希码并与已有文件的哈希码进行比较。如果发现相同的哈希码，系统将只保留一份文件的副本，从而节省存储空间。 节省存储空间: 文件去重技术有效减少了存储冗余，特别是在企业中频繁共享和传输的文件，从而降低了存储成本。 优势 传输效率: 文件分块技术和并行块请求加速了文件的传输速度，特别是对于大文件和高带宽连接。 存储节省: 基于哈希码的文件存储去重技术降低了存储需求，降低了维护成本。 用户体验: 快速的文件传输和节省存储空间改善了用户体验，提供更高效的文件管理和共享。 异步任务处理 后台异步处理 任务耗时处理: 为了处理那些前台发出的可能比较耗时，甚至可能导致HTTP请求超时的任务，巴别鸟企业网盘采用了后台异步处理的策略。这些任务不会阻塞主要的HTTP请求响应，而是在后台异步执行。 提高响应速度: 后台异步处理确保了前台请求的响应速度不受到耗时任务的影响，提高了用户体验。 配置化管理异步任务 任务队列: 为了防止服务器资源紧张，我们对异步任务进行了配置化管理。可以将异步任务配置为一个或多个处理队列，这些队列可以独立执行任务。任务队列可以根据任务的类型和优先级进行配置和管理。 消息队列: 另一种管理异步任务的方式是使用消息队列。巴别鸟企业网盘可以配置为使用消息队列来存储和调度异步任务。这种机制可以确保任务的有序执行和可控制性。 消息处理机制: 异步任务通过消息处理机制进行控制和执行。任务被加入队列或消息队列后，由专门的处理器进行处理和执行。 优势 响应性: 后台异步处理提高了系统的响应速度，避免了长时间的等待。 资源控制: 配置化管理异步任务允许对服务器资源进行有效的控制，防止资源耗尽。 可扩展性: 消息队列和消息处理机制提供了系统的可扩展性，可以轻松添加新的异步任务类型。 可扩展性 水平扩展 集群部署: 巴别鸟企业网盘业务服务器采用集群部署模型，这允许我们轻松扩展系统的容量和性能。集群中的多台服务器协同工作，以分担负载并提供高可用性。这种模型允许我们根据需求添加新节点，以满足不断增长的用户和数据需求。私有云部署客户在用户增长时也可以通过增加虚拟机或物理服务器的方式来扩充性能以满足高并发需求。关于巴别鸟集群部署可扩展性的更多信息，可以查看 分布式部署 章节。 对象存储系统: 巴别鸟的存储系统采用对象存储技术，这种技术非常适合大规模的数据存储和水平扩展。对象存储系统具有高度的可伸缩性，可以容纳大量的数据，并在需要时增加存储节点自动扩展存储容量。关于巴别鸟对象存储扩展性的更多信息，可以查看 自建对象存储 章节。 负载均衡: 我们实施了负载均衡策略，确保用户请求被均匀分配到集群中的各个节点，以避免单点故障和提供更快的响应时间。 自动伸缩（公有云）: 得益于阿里云ECS弹性计算服务，我们的系统配置了自动伸缩机制，根据负载情况自动增加或减少服务器节点。这种自动伸缩保证了系统的稳定性和性能。 垂直扩展 硬件升级: 除了水平扩展，针对私有云用户我们还可以进行垂直扩展，即升级服务器硬件以增加单个服务器的性能和容量。这在需要更多计算能力或内存的情况下是一种有效的解决方案。 数据库优化: 我们还可以优化数据库系统，通过调整配置、使用更高性能的硬件或升级数据库管理系统来提高性能。这些改进可以提供更好的查询性能和数据处理能力。 缓存: 我们使用缓存技术来加速数据访问，减轻数据库和存储系统的负载。缓存支持内存缓存、CDN缓存等多种方式，根据需要选择最适合的缓存策略。 容器化和SOA服务架构 Docker容器化 Docker部署: 我们采用Docker容器化技术来部署巴别鸟企业网盘的各个组件和模块。这种方式允许我们将每个主要模块打包为独立的Docker容器，提供了更高的灵活性和可扩展性。 容器编排: 我们使用容器编排工具来管理和协调各个容器，确保它们能够协同工作，实现高可用性和弹性。 容器镜像管理: 巴别鸟企业网盘使用容器镜像仓库来存储和管理Docker镜像，以便随时部署新的容器实例。 SOA服务架构 服务拆分: 我们将巴别鸟企业网盘的主要功能模块拆分为独立的服务，每个服务负责执行特定的任务或功能。这种拆分提高了系统的可维护性和可扩展性。 API通信: 服务之间通过API进行通信，使用兼容RESTful API协议。这种松耦合的通信方式使得服务可以独立开发、测试和部署。 独立部署: 每个服务可以独立部署和扩展，这意味着我们可以根据需求对特定服务进行水平扩展，而不影响其他服务的运行。 容器化和SOA服务架构的优势 高可用性: 容器化和SOA服务架构提供高可用性，允许我们在出现故障时快速恢复服务。 灵活性: 容器化允许我们轻松部署、升级和维护每个容器，而SOA服务架构提供了灵活的模块化开发和部署选项。 资源利用率: 我们可以根据需要分配资源，避免资源浪费，实现更高的资源利用率。 快速交付: 容器化和SOA服务架构使得新功能和改进可以更快地交付给用户。私有云用户也可以享有媲美公有云系统的快速更新及升级服务。 容器化和SOA服务架构的挑战 复杂性: 管理多个容器和服务可能会引入一定的复杂性，需要适当的管理工具和策略。 监控和日志: 我们使用监控和日志工具来确保容器和服务的正常运行，并及时识别和解决问题，并配备自动重启机制，如果服务有问题则自动重启有问题的模块以保证整体服务的畅通。 私有化部署 巴别鸟公有云网盘系统需要同时为包含免费用户在内的60万用户提供持续不间断服务、要挡住公网上的各种攻击、要不断提高系统效率以降低高昂的公有云服务器成本。多达10年的公有云不间断服务经验使巴别鸟系统久经考验。巴别鸟私有云系统是在巴别鸟公有云系统基础上发展起来的，继承了公有云巴别鸟的所有功能及特性，并与公有云巴别鸟保持同步更新，提供给您其他私有网盘无法比拟的高稳定性及高可用性。 部署方案 针对不同企业不同的IT系统建设需求，巴别鸟私有化系统支持多种灵活的部署方式及部署要求。无论是单服务器、多服务器、集群、超融合系统、分布式系统、第三方云平台甚至Docker方式的部署我们都支持。我们的部署团队可以根据你的需求和你共同制定部署方案。同时因为私有云只服务于单一企业的特性，我们可提供远超公有云系统的可选自定义设置，从界面操作到流程到权限都可以根据你的需求调整。 服务器建议配置及性能需求 服务器类型及作用： 巴别鸟网盘所需硬件系统由业务服务器及存储服务器两部份构成，其中业务服务器可以分为4种类型，这4种类型的服务可以根据需求部署在一台物理机或虚拟机中，也可以分散部署在四台甚至更多的服务器中。所以，部署巴别鸟系统最小单位是两台物理服务器或两台虚拟机（一台业务一台存储） 服务名 用途 操作系统 主业务服务器 web服务、负载均衡、主业务功能实现 Linux 数据库服务器 数据库服务 Linux 搜索服务器 提供文件全文搜索、高级搜索功能 Linux 转码服务器 为需要转码预览的文件进行转码及增加水印 windows 2012、Linux 存储服务器 提供文件存储 Linux 极端情况下，如果使用服务器挂载的硬盘作为存储空间，巴别鸟也支持把全部服务及存储都部署在一台物理机或虚拟机中（一体机模式），但考虑到性能及灾备或是日后的升级扩容问题，不推荐这样的部署方式。 我们推荐的最佳部署方式是4台服务器（虚拟机）的小集群部署。主业务服务及数据库服务放在在一台服务器，搜索服务器和转码服务器独立，然后外加一台存储服务器。 如果存储的空间需求小于10TB，也可以不需要存储服务器。可以直接挂载硬盘或NFS磁盘进行存储。 巴别鸟也支持接入第三方存储，理论上，只要第三方存储系统支持NFS或S3协议都可以接入到巴别鸟作为存储服务。绝大多数存储系统都支持这两种协议。 各个服务器之间要保证互访的畅通。如内网有较高安全要求可以参阅 9.1.2需要开放的端口 最低性能配置： 巴别鸟的最低性能配置可以支持100左右用户正常使用，管理10TB以下的数据。 cpu 内存 系统盘 存储盘 网络 操作系统 8核CPU （参考基准E5 2609） 32G ECC 内存 500G 10TB以下 千兆 Linux 推荐性能配置实例： 巴别鸟的推荐性能配置可以支持1000 2000用户正常使用，管理最高可达1PB的文档。 巴别鸟支持多种部署方式，该实例是标准部署方式。使用虚拟机部署业务服务器对接独立的单台或多台对象存储服务器。业务服务器和存储服务器分开管理。 业务服务器： 建议业务服务器使用虚拟机进行部署 编号 服务器类型 配置要求 操作系统 服务器用途 1 虚拟机 8核CPU 64G内存 500G SSD系统盘 CentOS8或openeuler22 主业务服务器/数据库 2 虚拟机 8核CPU 32G内存 500G SSD系统盘 CentOS8或openeuler22 搜索服务器 3 虚拟机 8核CPU 16G内存 200G SSD系统盘 windows 2012 R2 转码服务器 8核cpu的性能应该接近志强4410 巴别鸟企业网盘采用Docker部署，理论上只要是Linux操作系统即可进行部署，推荐使用CentOS或open Euler。 如果没有现成的虚拟机资源，需要采购新的业务服务器，业务服务器硬件配置需求如下： 编号 服务器类型 配置要求 操作系统 服务器用途 1 业务服务器 至强银牌4210 2 20核CPU 64G内存 2TB SSD硬盘 Linux 主业务服务器 业务服务器最好购买VM，使用虚拟化进行管理。 存储服务器（对象存储）： 巴别鸟支持在通用服务器上搭建对象存储系统，如预计存储空间用量小于100TB，推荐使用单台服务器搭建对象存储系统。单台对象存储可以用磁盘进行数据校验冗余，并且可以以每次增加一台存储服务器的方式进行横向扩容。（扩容操作可以做到不停服） 对象存储服务器建议使用独立的物理机，建议配置如下： 服务器类型 配置要求 操作系统 服务器用途 备注 存储服务器 至强银牌4210 2 20核CPU 64G内存 480G SSD硬盘 +存储所需容量硬盘 硬盘如果考虑性价比，建议使用 8T 10（2U） 或 8T 24（4U）。如果考虑存储密度及未来扩容投入可使用12T硬盘。 Linux 对象存储服务器 未来扩展建议增加相同磁盘容量的服务器。 如所需存储空间大于300TB，需要多台服务器搭建分布式对象那个存储系统。 巴别鸟也支持为客户搭建分布式对象存储系统。要了解分布式对象存储可查阅“自建对象存储”章节。 需要开放的端口 为了服务器系统的安全，我们需要只开放特定的端口，下面是需要开放的端口： 对外开放的端口（外网访问需要使用的端口）： 端口号 端口用途 协议 开放的主机 80 网盘主业务 web外部访问端口，不加密 http 主业务服务器 443 网盘主业务 web外部访问端口，加密 https 主业务服务器 3060 网盘主业务node 外部访问端口，不加密 TCP 主业务服务器 3080 网盘主业务node 外部访问端口，加密 TCP 主业务服务器 服务器间需要开放的端口（服务器内部通讯需要开放的端口）： 一般实际部署时，只会限制外网端口（对外），服务器间内部端口不会限制。但一些跨网络跨机房部署的用户也会需要限定内部端口。 主机 端口号 端口用途 协议 目标网段 业务服务器 6379 redis访问端口，供windows转码与搜索服务器使用 TCP 转码服务器与搜索服务器 业务服务器 8080 供windows转码服务器，访问网盘业务服务器使用 TCP 转码服务器与搜索服务器 业务服务器 3306 数据库端口，供搜索服务器访问数据库使用 TCP 转码服务器与搜索服务器 业务服务器 9000 docker 集群部署，内部可视化界面端口 TCP 转码服务器与搜索服务器 业务服务器 111 portmap 端口 TCP+UDP 转码服务器与搜索服务器 业务服务器 2049 TCP+UDP TCP+UDP 转码服务器与搜索服务器 业务服务器 35000 mountd 端口 TCP+UDP 转码服务器与搜索服务器 业务服务器 2376 docker REST API端口，进行TLS加密 TCP 本机 业务服务器 2377 TCP端口 用来 docker 集群管理相关通信 TCP+UDP 本机 业务服务器 7946 TCP与UDP端口，用来docker swarm 各节点间的通信 TCP+UDP 本机 业务服务器 4789 docker overlay 网络默认端口 TCP+UDP 本机 搜索服务器 9200 elastic 端口，供主业务服务器调用使用 TCP 业务服务器 搜索服务器 5601 kibana端口，内部可视化elastic界面访问端口 TCP 业务服务器 搜索服务器 9998 tika端口，提取文档文本服务器端口 TCP 业务服务器 搜索服务器 9000 docker 集群部署，内部可视化界面端口 TCP 转码服务器与搜索服务器 搜索服务器 2376 docker REST API端口，进行TLS加密 TCP 本机 搜索服务器 2377 TCP端口 用来 docker 集群管理相关通信 TCP 本机 搜索服务器 7946 TCP与UDP端口，用来docker swarm 各节点间的通信 TCP+UDP 本机 搜索服务器 4789 docker overlay 网络默认端口 TCP+UDP 本机 转码服务器 转码服务器 可以访问业务服务器 可以访问业务服务器 可以访问业务服务器 部署时需要开放的端口： 端口号 端口用途 开放的服务器 目标IP地址 22 ssh端口号，ssh 访问使用 所有服务器 部署用跳板机 443 获取授权 所有服务器 47.96.234.200 443 获取安装源 所有服务器 120.27.245.68 443 Docker安装源 所有服务器 13.35.121.100 POC部署 POC部署适用于用户在选型前在生产环境进行POC测试而进行的部署方式。 POC部署需求： 基础POC部署，可测试软件功能，并发量，API接口，安全性，并进行生产环境试用。建议使用标准部署作为POC测试。 如需要进行对象存储、不同密区数据摆渡、高可用的POC，择需要增加相应的服务器和网段。 环境准备 推荐使用虚拟机进行部署： 巴别鸟私有化企业网盘采用Docker部署，理论上只要是Linux操作系统即可进行部署。推荐使用CentOS或open Euler。按要求准备好虚拟机后，联系我们预约时间后即可开始POC部署。 编号 服务器类型 配置要求 操作系统 服务器用途 备注 1 虚拟机 8核CPU 32G内存 500G系统盘 +500G存储盘 CentOS8或openeuler22及以上 主业务服务器 2 虚拟机 8核CPU 16G内存 500G系统盘 CentOS8或openeuler22及以上 搜索服务器 3 虚拟机 8核CPU 8G内存 200G系统盘 windows 2012 R2 转码服务器 CAD、office转码 win服务器是为了更好的office文件预览效果。巴别鸟也支持纯Linux环境部署 POC部署其他要求如下： 编号 项目 要求 备注 1 远程接入 可以远程接入服务器进行部署 可使用堡垒机或者跳板机或向日葵、VPN，能远程接入服务器部署即可。 2 外网连接 服务器需要能连接外网，拉取安装包，获取授权 需要连接的外网地址： software.babel.cc docker.babel.cc POC部署的使用授权时长为30天，授权账户数为100个。 初始化 部署完成后，巴别鸟团队会帮助用户进行系统初始化，根据用户需求初始化系统。包括不限于： 初始化管理员账号。（需要准备一个邮箱地址作为超级管理员账号） 初始化通知发件邮箱。（需要用户准备一个可提供密码和smtp服务器地址的邮箱作为系统默认发件箱） 初始化部门结构。（对接AD或导入部门） 初始化基础配置。logo、企业名、各类配置项。 培训 巴别鸟是一个专业的企业级应用，需要一定的培训工作帮助客户落地。POC后建议联系我方销售人员进行使用培训。 培训分为3类： 管理员培训（培训管理员的配置，使用，需求功能实现。耗时 1 2小时） 部门经理培训。（培训部门经理权限分配、成员增减等日常管理方式。耗时 1小时） 使用者培训。（使用成员的培训。耗时 1小时） 开启POC试用 培训完成后即可开始正式POC试用，使用中遇到的问题可以在相关群直接询问，巴别鸟团队会在2个小时内响应并解答。POC系统有效期为30天，如果需要延期，可联系我们销售人员。 巴别鸟常用部署方式介绍 巴别鸟可以按需支持多种部署方式，这里介绍下巴别鸟常用的部署方式。 在阿里云、腾讯云、华为云等公有平台部署： 巴别鸟支持在公有云服务商如：阿里云、腾讯云、百度云、华为云、天翼云的虚拟机（ECS）及对象存储（OSS、OBS...）上进行部署，在互联网上为用户提供服务。 和纯私有化部署的差别对比如下表： 优缺点/ 部署方式 图片服务 视频服务 公网访问 稳定性 硬件费用 采用阿里云存储和阿里云服务器 可以使用阿里云提供的图片服务 可以采用阿里云的视频转码服务，但是需要额外付费(价格贵) 可以在公网上访问，用户访问的快慢取决于用户自己的带宽和购买的阿里云的带宽。 系统很稳定，部署简单，便于管理。 需要支付阿里云的存储和服务器费用，可按月或按年付费等。服务器的维护即可由用户自己负责，也可以委托我们进行维护并负责升级。 存储和服务器均搭建在自己的内网 使用自建的图片处理服务(需要客户提供高性能的服务器) 使用自建的转码服务(需要客户提供高性能的服务器)，如果用户没有这方面的需求，可以忽略。 如果没有外网的出口，则用户不能在外网访问。但是在内网访问很快。 稳定，针对存储系统等的模块做了定制开发。数据的安全性由用户自己负责。 需要提供独立的主机和存储系统。服务器即可由用户选配购买，也可以由我们选配购买。服务器维护由用户负责，我们可以提供相应的软件升级服务。 公有云部署（1000+用户）要求： 编号 服务器类型 配置要求 操作系统 服务器用途 1 ECS 16核CPU 32G内存 500G SSD系统盘 CentOS8或openeuler22 主业务服务器 2 ECS 8核CPU 16G内存 500G SSD系统盘 CentOS8或openeuler22 数据库服务器 3 ECS 8核CPU 16G内存 500G SSD系统盘 CentOS8或openeuler22 搜索服务器 4 存储 对象存储系统。如阿里云OSS、华为云OBS 对象存储系统。如阿里云OSS、华为云OBS 对象存储系统。如阿里云OSS、华为云OBS 在公有云平台部署的主要优势是不需要专人维护、无需购买硬件就能做到顶级的灾备、在互联网上访问速度快、同时服务器和数据在自己手上管理。 在公有云平台部署的缺点主要为：数据没有本地化、每年需要支付服务器租用费用及相应的带宽存储成本。 自购服务器（2台物理机）进行部署： 如果想在自己机房部署纯私有的巴别鸟，并且没有富余的虚拟机资源，需要采购硬件部署，要求如下： 物理机服务器品牌建议：建议使用2台 DELL T440 服务器来完成系统搭建。并购买DELL3年金牌服务。 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：建议使用2台 DELL T440 服务器来完成系统搭建。并购买DELL3年金牌服务。 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：建议使用2台 DELL T440 服务器来完成系统搭建。并购买DELL3年金牌服务。 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：建议使用2台 DELL T440 服务器来完成系统搭建。并购买DELL3年金牌服务。 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：建议使用2台 DELL T440 服务器来完成系统搭建。并购买DELL3年金牌服务。 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：建议使用2台 DELL T440 服务器来完成系统搭建。并购买DELL3年金牌服务。 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 两台服务器方案 业务+存储 两台服务器方案 业务+存储 两台服务器方案 业务+存储 两台服务器方案 业务+存储 两台服务器方案 业务+存储 两台服务器方案 业务+存储 编号 服务器类型 配置要求 操作系统 服务器用途 备注 1 服务器 志强银牌4410 2 16核CPU、 64G内存、 2TB SSD硬盘 open Euler、Ubuntu、CentOS 主业务服务器 建议安装VM 2 存储 4410 2 16核CPU 、64G内存、 500G SSD硬盘+所需的硬盘空间（不需要raid或raid0） open Euler、Ubuntu、CentOS 存储服务器 硬盘容量按对存储空间需求进行配置 以上配置可支持1000+用户，150TB左右的存储空间 巴别鸟存储服务器使用对象存储系统，支持分布式部署（多台存储服务器）最低要求为一台物理服务器。支持使用硬盘组进行校验，支持2+1、3+1、4+1...等多种校验类型。详见 自建对象存储 章节 如需扩容存储空间，增加单台存储服务器即可。 也可增加一台存储服务器作为备份服务器，实时同步备份，主存储服务器出问题切换到备份服务器即可正常使用。 单服务器（1台物理机）部署： 一些没有机房但需要私有化部署巴别鸟，并且存储空间需求不大（10TB以下）的客户，可以选用单台服务器部署巴别鸟。只需购买一台符合要求的塔式服务器放置在公司也能满足使用巴别鸟的需求。 物理机服务器品牌建议：如果没有机房，建议使用塔式服务器进行部署。服务器存储硬盘建议raid1或者raid5+1 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：如果没有机房，建议使用塔式服务器进行部署。服务器存储硬盘建议raid1或者raid5+1 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：如果没有机房，建议使用塔式服务器进行部署。服务器存储硬盘建议raid1或者raid5+1 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：如果没有机房，建议使用塔式服务器进行部署。服务器存储硬盘建议raid1或者raid5+1 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：如果没有机房，建议使用塔式服务器进行部署。服务器存储硬盘建议raid1或者raid5+1 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：如果没有机房，建议使用塔式服务器进行部署。服务器存储硬盘建议raid1或者raid5+1 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 一台服务器（一体机方案） 一台服务器（一体机方案） 一台服务器（一体机方案） 一台服务器（一体机方案） 一台服务器（一体机方案） 一台服务器（一体机方案） 编号 服务器类型 配置要求 操作系统 服务器用途 备注 1 服务器 志强银牌4410 2 16核CPU 64G内存 2TB SSD硬盘 +需要存储容量的硬盘 2（未来也可增加硬盘） openEuler、Ubuntu、CentOS 8.5 及以上 一体机 建议安装VM，2个CPU授权。 单服务器部署整套巴别鸟系统不支持对象存储，采用只读硬盘或NFS的方式进行存储。建议使用raid1来提升系统可靠性。 可增加一台备份服务器用来进行数据同步备份。如主服务器出问题可以用备份服务器进行数据重建。 在现有虚拟机（超融合）系统上进行部署： 这是目前最常用的部署方式，在企业现有的服务器和硬件条件下进行部署，无需采购新的设备。 在客户现有的VM或超融合平台分配的虚拟机中完成部署，适合已经有一定IT建设及管理的用户。 采用小集群的方式部署，由虚拟机平台负责服务器的统一管理。 支持绝大多数虚拟化系统。 推荐采用4台虚拟机挂载存储空间的方式进行部署。 编号 服务器类型 配置要求 操作系统 服务器用途 1 虚拟机 8核CPU 32G内存 500G SSD系统盘 CentOS8或openeuler22 主业务服务器 2 虚拟机 8核CPU 16G内存 500G SSD系统盘 CentOS8或openeuler22 数据库服务器 3 虚拟机 8核CPU 16G内存 500G SSD系统盘 CentOS8或openeuler22 搜索服务器 4 虚拟机 8核CPU 16G内存 200G SSD系统盘 windows 2012 R2 转码服务器 5 存储 支持NFS或S3接口的存储系统或虚拟机挂载磁盘作为存储盘 支持NFS或S3接口的存储系统或虚拟机挂载磁盘作为存储盘 支持NFS或S3接口的存储系统或虚拟机挂载磁盘作为存储盘 如有系统冗余需求，可以准备6台虚拟机，就能很好的完成数据库备份及系统冗余。 编号 服务器类型 配置要求 操作系统 服务器用途 1 虚拟机 8核CPU 32G内存 500G SSD系统盘 CentOS8或openeuler22 主业务服务器 2 虚拟机 8核CPU 32G内存 500G SSD系统盘 CentOS8或openeuler22 从业务服务器 3 虚拟机 8核CPU 16G内存 500G SSD系统盘 CentOS8或openeuler22 主数据库服务器 4 虚拟机 8核CPU 16G内存 500G SSD系统盘 CentOS8或openeuler22 从数据库服务器 5 虚拟机 8核CPU 16G内存 500G SSD系统盘 CentOS8或openeuler22 数据库服务器 6 虚拟机 8核CPU 16G内存 200G SSD系统盘 windows 2012 R2 转码服务器 7 存储 分布式对象存储 分布式对象存储 分布式对象存储 支持虚拟机挂载磁盘的形式把挂载盘作为存储空间。 也可以对接san存储或者对象存储系统等第三方存储系统。 巴别鸟也为客户提供自建对象存储服务。 自建对象存储服务器配合虚拟机部署： 巴别鸟支持为客户在通用服务器上搭建对象存储，因为对象存储软件定义存储的优势（高可用、横向扩展容易），推荐没有对象存储的用户可以新购一台服务器部署巴别鸟对象存储系统配合在虚拟机（超融合）运行的巴别鸟业务系统一起使用。 业务服务器需求同上一节“在现有虚拟机（超融合）系统上进行部署”的要求。 关于巴别鸟对象存储的详细介绍可查看“自建对象存储服务器”章节。 我们大多数客户最终都选择对象存储服务器作为存储。 最低支持单服务器搭建对象存储系统（150TB以下空间需求）。 服务器类型 配置要求 操作系统 服务器用途 备注 存储服务器 至强银牌4210 2 20核CPU 64G内存 480G SSD硬盘 +存储所需容量硬盘 硬盘如果考虑性价比，建议使用 8T 10（2U） 或 8T 24（4U）。如果考虑存储密度及未来扩容投入可使用12T硬盘。 Linux 对象存储服务器 未来扩展建议增加相同磁盘容量的服务器。 单服务器对象存储网络拓扑图： 我们也支持搭建多台服务器组成的分布式对象存储系统。 分布式存储系统最小需求为2+1，就是需要准备三台存储服务器，性能要求和单台对象存储的要求一致。 物理分布式存储目前推荐最小单位是3台存储服务器。2+1纠错码意味着每扩充2台存储节点就需要增加1台服务器作为纠错服务器。以此，4+1意味着增加4台存储服务器就需要增加一台纠错服务器。所以4+1的磁盘利用率高于2+1。使用4+1方案首次建设就需要5台存储服务器。每次扩容增加的最小单位和首次建设需要的最小服务器单位一致。 多服务器分布对象存储网络拓扑图： 可以新增一台或一套存储服务器用来实时备份。主存储服务器出问题快速切换到备份服务器即可正常使用。 分布式高可用高冗余部署： 金融机构、医院、能源、超大型企业因为有业务不中断的硬性指标，需要系统能做到高可用、高冗余，不会因为服务器的单点故障而中断服务，并且能做到热切换及热修复，极端情况下，连交换机等网络设备都需要实现主备分离，这就需要使用分布式高可用高冗余部署。 巴别鸟支持多种高可用高冗余方案，可以部署在传统的分布式系统中实现高可用高冗余。 我们也可以为客户搭建适合巴别鸟的分布式系统。（硬件需要客户按要求自行采购） 巴别鸟分布式部署能确保任何一个单点故障都不会影响系统的正常使用。 推荐的分布式容易部署方案，业务服务器采用主备双活，存储系统采用分布式存储。 有密区及非密区管控需求的，详见 “数据摆渡章节” 巴别鸟高可用系统网络拓扑 异地灾备部署 对于对数据保全有着较高要求的用户，巴别鸟也支持异地灾备方案。就是把重要的数据库及文件存储内容备份到异地的备份系统中。如果本地机房出现问题，只要备份数据在，可以在任何地方重建系统并恢复正常使用。 巴别鸟可以为客户搭建异地灾备服务器，但不支持冷热数据分离等高级备份方式，如果数据量极大（1PB以上）考虑到性价比，建议使用专业的备份系统（如：NBU、云祺）。 巴别鸟有支持NBU标准的备份API可以调用。 异地灾备部署对网络环境要求较高，不同位置的机房间最好有专线或稳定的VPN连接。 使用备份系统只能在出问题后通过备份还原及重建数据，不支持直接切换到备份数据。一般情况下数据重建周期会比较久。 使用备份系统进行异地灾备示意图： 如果不需要冷热数据分类保存，巴别鸟也可以采用对象存储自带的异地灾备功能为客户完成异地灾备部署。 使用对象存储进行异地灾备，当主系统出问题可以快速切换到灾备服务器中。 自建对象存储服务器 巴别鸟对象存储是在开源MinIO系统上发展起来的对象存储系统。它继承了MinIO高性能、可扩展、数据安全的优势，同时更适配巴别鸟企业网盘的应用场景。 巴别鸟对象存储系统作为先进的对象存储系统，在速度、安全性、稳定性、高可用、横向扩展方面都有着传统存储系统无可比拟的优势。 巴别鸟对象存储系统优势 性能 MinIO号称是世界上速度最快的对象存储服务器，没有之一。在 32 个 NVMe 驱动器节点和 100Gbe 网络上发布的 GET/PUT 结果超过 325 GiB/秒和 165 GiB/秒，和亚马逊S3相比有明显优势，远远超越传统HDFS。 高可用性：MinIO通过数据的多副本、故障转移和自动恢复，保证高度可靠性和可用性，从而确保数据不丢失和业务不中断。 低冗余且磁盘损坏高容忍：标准且最高的数据冗余系数为2(即存储一个1 M的数据对象，实际占用磁盘空间为2M)。但在任意n/2块disk损坏的情况下依然可以读出数据(n为一个纠删码集合(Erasure Coding Set)中的disk数量)。并且这种损坏恢复是基于单个对象的,而不是基于整个存储卷的。 安全性： MinIO 通过最高级别的加密以及广泛的优化提供更多功能，几乎消除了通常与存储加密操作相关的开销。 数据分块存储与各个硬盘，获取硬盘或服务器读写权限也无法还原数据。 极高的可扩展性：MinIO支持分布式部署，并且可以水平扩展。在需要更多的存储空间或更高的性能时，可以通过添加新的节点轻松地扩展MinIO。 最低支持单机部署对象存储系统，而不是传统的需要三台独立服务器。 对象存储系统及纠删码 关于纠删码 巴别鸟对象存储系统(MinIO)使用纠删码erasure code 和校验和checksum来保护数据免受硬件故障和无声数据损坏。最高冗余状态下即便丢失一半数量(N/2)的硬盘,您仍然可以恢复数据。 纠删码是一种恢复丢失和损坏数据的数学算法，MinIO采用Reed Solomon code将对象拆分成N/2数据和N/2奇偶校验块。这就意味着如果是12块盘，一个对象会被分成6个数据块、6个奇偶校验块，可以丢失任意6块盘(不管其是存放的数据块还是奇偶校验块) , 仍可以从剩下的盘中的数据进行恢复，我们称数据存储为D、纠删码（奇偶校验）为P。 默认情况下会以N/2个数据和N/2奇偶校验块的方式来进行驱动器分片（支持自定义以支持更高的空间利用率） 纠删码不同于传统的多副本技术，它的磁盘利用率更高，数据恢复效率更高。（但是不少存储厂商把纠删码宣传为多副本，把P数说成是副本数，这是不准确的，会引起很多误解） 巴别鸟语境下的多副本是指增加备份服务器全量同步存储的数据。 纠删码特点及与raid技术区别 纠删码可以保护数据免受多个驱动器故障的影响 RAID6允许两个驱动器故障而MinIO纠删码允许丢失一半的驱动器 RAID属于卷级别的纠删码而MinIO纠删码是基于对象实现的纠删码（不用停机） 有效空间计算（空间利用率） 假设需要100TB的存储空间，需要购买多少个多大的硬盘取决于选择的冗余标准。譬如：采用3+1的冗余方式，100TB可用空间就需要购买12块12TB的硬盘，4块硬盘一组组成3组，9个数据盘3个校验盘，可用空间就是9 12一共108TB可用。如果采用2+1的冗余方式，就需要15块10TB的硬盘，10个数据盘，5个校验盘。 3+1方案中12块硬盘只能坏任意3块不影响系统使用及数据还原，但如果使用2+1方案，虽然需要购买更多硬盘，但15块硬盘里能坏任意5块也不影响系统使用。 更换坏掉的硬盘后系统能自动修复数据。 空间利用率可以参考下表。如果空间需求量大（超过150TB）并且在持续增长，考虑到存储密度和性价比，建议一台服务器一次性配16块硬盘。 不同数量的磁盘及空间利用率可以点击下方链接进行计算 https://min.io/product/erasure code calculator?ref=docs 硬件准备 所需硬件配置。 巴别鸟支持单台服务器搭建对象存储系统（单节点），以硬盘组作为冗余对象。最高可以损坏一半的硬盘也不影响系统的正常使用。 巴别鸟对象存储系统需要客户按要求事先准备好硬件服务器以供部署，最低配置需要2块志强CPU、64GB内存及400G固态硬盘（系统盘）然后增加相应存储容量所需的机械硬盘。 如要计算所需存储空间和购买的硬盘数，可点击下方链接进行计算。 https://min.io/product/erasure code calculator?ref=docs 建议硬件配置如下： 服务器类型 配置要求 操作系统 服务器用途 备注 存储服务器 至强银牌4210 2 20核CPU 64G内存 480G SSD硬盘 +存储所需容量硬盘 硬盘如果考虑性价比，建议使用 8T 12（2U） 或 8T 24（4U）。如果考虑存储密度及未来扩容投入可使用12T硬盘。 Linux 对象存储服务器 未来扩展建议增加相同磁盘容量的服务器。 巴别鸟对象存储使用软件定义存储技术，所以硬盘无需raid，考虑到一些服务器需要raid才能支持多磁盘，这种情况下每块硬盘都做成raid0直通模式即可。 单服务器模式每次扩容需要增加一台配置一致的服务器。扩容时可以不间断服务。 单服务器部署也支持增加一台配置一致的服务器搭建主备模式实时同步，如果一台服务器硬件损坏，可以快速切换到备用服务器。 磁盘有效空间容量和选择的冗余方式有关。譬如：使用8块10T硬盘来组建对象存储系统，采用3+1的冗余方案，相当于4块硬盘一个分组，分为2组，有效可用空间为60TB，同时8块硬盘损坏任意两块也不影响数据及系统使用，替换坏的硬盘即可自动重建。如果采用7+1的冗余方案，有效可用空间就为70TB，8块硬盘里任意损坏1块不影响数据及系统使用。 多服务器部署（分布式）。 巴别鸟对象存储系统支持多服务器部署，如使用服务器为冗余单位，最少要求3台服务器，即2+1模式，但考虑到空间利用率，推荐采用3+1方案（即4台服务器） 每个节点（服务器）的配置要求和上文单服务器部署一致。 建议节点配置一致（相同的操作系统、相同数量的磁盘和相同的网络连接） 每个节点提供的驱动器数量必须相同 节点间的时间差异不能大于15分钟（建议使用NTP确保时间的一致性） 空间利用率计算同单服务器。 私有化要求及服务流程 为了确保使用巴别鸟系统的体验和质量，巴别鸟所有的私有化部署工作都是由巴别鸟团队远程或现场进行部署及签发证书，暂不支持代理团队部署或客户自行部署。同时系统的维护工作也由巴别鸟运维团队进行定期远程维护。客户只需按要求准备好硬件及接入资源，其他事情就交给巴别鸟团队来完成。 私有化部署前期需要准备的： 计算大体使用人数、并发量、存储空间及空间增长率交由巴别鸟客户经理评估所需配置。 客户评估现有服务器剩余资源（如有），根据实际情况选择部署方式。 巴别鸟出具私有化部署方案。 客户根据方案准备相应的服务器及接入资源，分配服务器、安装操作系统。 保证服务器能够在外网远程桌面（也可以使用向日葵）和ssh访问，开启相应端口（我们的部署技术人员会提出具体端口要求） 用户最好能提供一个域名，没有域名的话需要一个固定的ip地址，用ip地址访问的方案需要保证在使用时期ip地址不会发生变动 如需接入邮箱找回密码或手机号发送验证码，需要准备相应的邮箱接入或短信网关。 编号 项目 要求 备注 1 域名 需要一个独立的主域名或二级域名 可以在公司原有域名的基础上设定一个二级域名。如yun.company.com 2 邮箱 需要一个可发送通知邮件的邮箱 支持smtp的邮箱地址即可 邮件推送相关 MailUser=xxxx@mail.com MailPassword=password MailHost=邮件服务器地址 MailPort=端口号 3 远程访问 可远程访问服务器进行配置 支持远程访问及控制服务器 4 SSl证书 https需要申请SSL证书 像数字证书颁发机构CA申请。推荐申请 OV 通配符 5 短信接口 如需要手机邀请，手机注册。则需开通短信接口服务（可选） 阿里云、腾讯云等云服务商也提供短信服务接口，申请即可开通 实施阶段 准备工作完成后通知我们，我们会给用户一个具体的实施时间安排，实施时间段内请保持外网访问的畅通 实施一般需要2 3个工作日，第一天远程部署安装巴别鸟，第二天测试和验收，第三天修正遇到的问题 实施完成后我们会通知用户，然后开始初始化阶段 初始化服务 巴别鸟为所有私有云客户提供了初始化服务，服务内容包括： 维护人员培训（远程或是现场） 帮助用户进行数据迁移、用户导入、权限分配等工作（远程或是现场） 使用人员培训 （远程或是现场） 接入第三方服务 作为一个围绕企业文件的办公平台，私有化的巴别鸟企业网盘通过接入第三方API的方式，可以轻松集成各种第三方服务到巴别鸟中，以满足不同的需求这些服务包括但不限于：电子签名、高级CAD预览、office、文字识别、图像识别....等第三方服务来解决您遇到的需求问题。 接入第三方服务的条件 理论上支持BS架构的第三方应用或者服务模块都可以接入。 第三方服务必须提供开放的API，以便巴别鸟企业网盘可以与之集成 如果是互联网服务，需要服务器能访问外网。 需要企业自行或委托我们购买接入的第三方服务的授权 推荐的可接入服务 文件防泄密系统： ipguard 在线office编辑：onlyoffice（自带）、office365、WPS Online、永中office 高级CAD预览：浩辰云图、梦想CAD CAD在线编辑：梦想CAD 在线签章：上上签 文字识别图像识别：百度千帆（智能云） AI相关：智巢AI（自有）、ChatGPT、智谱AI 开放API（统一存储平台） 巴别鸟私有化版本提供了开放API，使用巴别鸟API，您可以在您的系统中使用巴别鸟的几乎所有能力。并在云中构建自定义应用程序和集成，而无需构建和维护自己的内容管理服务。 统一存储平台 非结构化数据统一管理: 巴别鸟企业网盘的开放API的核心价值在于它可以作为一个统一的存储平台，用于整合和管理企业各个平台的非结构化数据。这包括但不限于OA（办公自动化）、CRM（客户关系管理）、ERP（企业资源规划）等应用，这样企业的所有非结构化数据都能在一个平台统一管理，提高安全性并节约存储资源。 企业级对象存储: 巴别鸟企业网盘还可以开放自带的对象存储接口，作为企业的统一存储管理平台。这意味着企业可以将不同来源的数据，包括文档、媒体、报表等，存储在巴别鸟企业网盘，并通过API访问和管理这些数据。 文档和支持 详细文档: 巴别鸟企业网盘提供详细的API文档，包括示例代码和用例，以帮助开发人员快速集成API。 附件2: 巴别鸟API文档 https://www.babel.cc/p/api integration.do 开发支持: 我们提供开发支持服务，技术人员会参与联调，一对一解决在API集成过程中可能遇到的问题和挑战。 单点登录SSO 巴别鸟私有化系统支持对接SSO单点登录平台或企业微信、钉钉、飞书、OA、ADFS、ERP等第三方平台以是实现单点登录。 更多关于单点登录的内容可以参见上文安全性章节的 ：单点登录（Single Sign On，SSO）集成 数据摆渡 巴别鸟可以使用“部门安全策略”的方式隔离某个部门数据，实现涉密部门的安全性和外发审批等功能，但是面对网络隔离的密区和非密区之间的文件传输，就需要用到数据摆渡的方式，确保密区和非密区之间可以安全可控的交换文件，这里就需要部署巴别鸟数据摆渡功能。在巴别鸟中，该功能模块命名为“传送文件“便于普通用户理解。 实现方式 在密区（研发区）和非密区（办公区）各部署一套巴别鸟，在两套巴别鸟之间传送文件: 需要安装巴别鸟数据摆渡模块 两套服务器间需要配置传输端口 传输使用SSL加密 支持多套巴别鸟之间互传文件 超级管理员可设定特定的文件接收者及审核人 可设定从非密区向密区传送文件无需审批 所有的传输都有记录及日志 多套巴别鸟在多个网络进行文件传送: 单套巴别鸟简化的文件传送方式 ： 有些客户的核心需求是非密区往密区便捷快速传输文件，仅想在密区部署一套巴别鸟，并没有在非密区使用网盘的需求，这时候就可以使用简化的数据摆渡方式。 出于安全考虑，该方式仅支持非密区向密区传送文件，并不支持密区向非密区传送文件。 除了在密区部署完整的巴别鸟系统，也需要在非密区部署一个文件传输服务。 非密区向密区传输文件无需审批。 使用步骤 部署完成数据摆渡模块的巴别鸟会在企业控制台增加一个“传送文件配置”模块，如果在企业控制台能看到该模块入口，说明已部署成功数据摆渡模块。 在企业控制台“传送文件配置”中新建接受端口和发送端口。已确定数据摆渡的接受端和发送端。 如果其中一套巴别鸟只配置了接口端口没有配置发送端口，那么就只能接收文件但不能发送文件。如：密区只能接收文件但不能发送文件。 新建了接收端会自动生成一个token，发送端要填入该token以实现加密传输。 一个巴别鸟可以建立多个接收端，每个接收端可以选择不同的成员。如：研发部和技术部的接收端分开。 通过审核后，接收人员能在自己的巴别鸟账号“传送文件”栏目找到摆渡过来的文件。 使用者在巴别鸟企业网盘中直接右键“传送文件”选择传送的接收端进行文件传送（发件）。并在“传送文件”栏目下查看发送过来并通过审核的文件。 为保证安全，传送文件以文件为单位（在多层文件夹中夹带重要文件，骗过审核），并不支持选择文件夹传送，但支持多选文件进行传送。 具有审批权限的管理员或部门经理可以在“传送文件”栏目下对接收和发送的文件进行审核，审核通过后文件才能传输。" }, { "lang": "zh", "slug": "deployment-custom-development", "title": "定制开发与白牌服务", "description": "二次开发、API 对接、流程定制、界面重塑、白牌 OEM 和项目管理方式。", "category": "集成与扩展", "top_category": "部署指南", "keywords": [ "部署", "定制开发与白牌服务", "私有化" ], "url": "zh/deployment-custom-development.html", "source": "content/zh/deployment-custom-development.md", "summary": "定制开发与白牌服务 定制化开发 巴别鸟私有化版本可以为客户提供专业的定制化开发（二次开发）服务。在巴别鸟现有产品的基础上针对客户具体需求推出更适合客户的产品。 巴别鸟定制开发优势 从产品思维出发帮助您设计产品 不同行业有不同的工作流程及使用习惯，同时需求和最终的产品间往往也隔着很深的鸿沟。只有需求没有好的产品设计往往会使项目迟迟无法落地。为了更好的适用于您的使用场景，我们职业产品经理带队的Babel care团队会为您的企业定制属于你的解决方案及二次开发支持。 精细化估时管理 我们拥有曾服务于北大方正的精细化估时管理体系，能精确的进行开发估时管理，提高项目成功率及落地效率。项目估时清晰有据可查，有效降低企业成本并提高效率。 透明的项目跟进及验收 在项目的每一个阶段，我们都有专职项目经理和产品经理跟进。确保项目进度及验收标准。并且我们可以开放我们的Jira（项目管理工具）给客户，让客户随时了解到项目的进度及耗时。 保持更新和维护 定制开发最普遍的问题是未来的更新和维护问题。传统的定制开发因为和标准产品有较大区别，所以往往会使用新的分支，开发团队也没有精力去维护新的分支，这就造成了定制开发产品会失去持续的维护及功能更新，越来越不好用或者孤立，最终被弃用。巴别鸟注意到并解决了这个问题，我们会在标准产品的基础上使用模块化的方式开发新的定制需求，或者把定制需求结合进标准产品以配置项的方式进行管理。这样，就是定制开发产品也能享受标准产品的更新及维护服务，做到可持续发展。 支持白牌服务（OEM） 出于商业目的或品牌建设需求，一些企业需要使用自己的产品名称及logo，巴别鸟可提供符合企业要求的", "headings": [ { "level": 1, "title": "定制开发与白牌服务", "id": "section" } ], "images": [], "text": "定制开发与白牌服务 定制化开发 巴别鸟私有化版本可以为客户提供专业的定制化开发（二次开发）服务。在巴别鸟现有产品的基础上针对客户具体需求推出更适合客户的产品。 巴别鸟定制开发优势 从产品思维出发帮助您设计产品 不同行业有不同的工作流程及使用习惯，同时需求和最终的产品间往往也隔着很深的鸿沟。只有需求没有好的产品设计往往会使项目迟迟无法落地。为了更好的适用于您的使用场景，我们职业产品经理带队的Babel care团队会为您的企业定制属于你的解决方案及二次开发支持。 精细化估时管理 我们拥有曾服务于北大方正的精细化估时管理体系，能精确的进行开发估时管理，提高项目成功率及落地效率。项目估时清晰有据可查，有效降低企业成本并提高效率。 透明的项目跟进及验收 在项目的每一个阶段，我们都有专职项目经理和产品经理跟进。确保项目进度及验收标准。并且我们可以开放我们的Jira（项目管理工具）给客户，让客户随时了解到项目的进度及耗时。 保持更新和维护 定制开发最普遍的问题是未来的更新和维护问题。传统的定制开发因为和标准产品有较大区别，所以往往会使用新的分支，开发团队也没有精力去维护新的分支，这就造成了定制开发产品会失去持续的维护及功能更新，越来越不好用或者孤立，最终被弃用。巴别鸟注意到并解决了这个问题，我们会在标准产品的基础上使用模块化的方式开发新的定制需求，或者把定制需求结合进标准产品以配置项的方式进行管理。这样，就是定制开发产品也能享受标准产品的更新及维护服务，做到可持续发展。 支持白牌服务（OEM） 出于商业目的或品牌建设需求，一些企业需要使用自己的产品名称及logo，巴别鸟可提供符合企业要求的白牌（OEM）版本。 透明、专业、负责 负责，是客户给我们最多的和最高的评价。在项目维护期内，我们会站在企业角度考虑，及时对应修正bug并完成功能调整。为企业提供长期可持续的维护服务。 巴别鸟定制开发范围 基于API的系统对接：如与OA、CRM、PDM等系统的对接整合。 API的定制开发：针对巴别鸟企业网盘某项功能开放API。 使用巴别鸟API接口的独立功能模块或子系统的定制开发。 围绕巴别鸟企业网盘现有功能的功能扩充，流程定制，数据交换。 基于巴别鸟源码的界面重塑及功能定制化开发。 巴别鸟定制开发流程 和客户确定需求及技术实现方案。出具：《需求分析说明书》 产品经理和客户深度讨论，设计原型和交互。出具《二次开发方案》、《产品原型》、《详细模块及估时表》 商务及合同环节，客户支付预付款项。 设计出图，开发启动。 内部测试及联调。 试上线及用户测试。 用户培训。 用户验收及交付 客户支付尾款。" }, { "lang": "zh", "slug": "deployment-xinchuang", "title": "信创支持", "description": "国产 CPU、操作系统、数据库和客户端环境支持。", "category": "集成与扩展", "top_category": "部署指南", "keywords": [ "部署", "信创支持", "私有化" ], "url": "zh/deployment-xinchuang.html", "source": "content/zh/deployment-xinchuang.md", "summary": "信创支持 信创支持 巴别鸟多年来一直积极响应国产化号召，巴别鸟的产品也能运行在大多数信创环境下。特别是针对服务器端，无论是CPU、操作系统还是数据库，巴别鸟都有相应的信创解决方案。 CPU及服务器架构支持。 巴别鸟支持X86和arm指令集的国产CPU，如X86的龙芯、飞腾、麒麟、海光…同时也支持arm架构的国产CPU，如：鲲鹏架构、飞腾arm架构。 操作系统。 巴别鸟使用docker部署，支持一切支持docker的Linux操作系统。如open Euler、银河麒麟、统信UOS 数据库。 巴别鸟推荐使用AliSQL数据库或其他兼容MySQL的数据库如：open Causs （高斯）。 巴别鸟也可以为定制接入其他国产数据库。如：达梦、人大金仓、南大通用….. 客户端。 巴别鸟客户端可以运行在Linux系统上，支持麒麟、统信等国产化系统。 由于Linux系统文件管理界面并没有统一，Linux版本的巴别鸟不支持同步文件夹及映射盘功能。 分类 分类 标准部署系统（非信创） 巴别鸟信创方案（x86) 巴别鸟信创方案（arm） 信创版本不支持的功能 业务服务器 操作系统 Centos、openEuler、Ubuntu openEuler 、麒麟 鲲鹏、麒麟、统信 无 业务服务器 巴别鸟版本 标准版 巴别鸟信创版（X86） 巴别鸟信创版（arm） 无 业务服务器 数据库 MySQL 高斯、TiDB、aliSql 高斯arm 无 业务服务器 组件/中间件 tomcat tomcat、TongWeb7 tomcat 无 业务服务器 组件/中间件 pomleo pomleo（信创） pomleo（", "headings": [ { "level": 1, "title": "信创支持", "id": "section" } ], "images": [], "text": "信创支持 信创支持 巴别鸟多年来一直积极响应国产化号召，巴别鸟的产品也能运行在大多数信创环境下。特别是针对服务器端，无论是CPU、操作系统还是数据库，巴别鸟都有相应的信创解决方案。 CPU及服务器架构支持。 巴别鸟支持X86和arm指令集的国产CPU，如X86的龙芯、飞腾、麒麟、海光…同时也支持arm架构的国产CPU，如：鲲鹏架构、飞腾arm架构。 操作系统。 巴别鸟使用docker部署，支持一切支持docker的Linux操作系统。如open Euler、银河麒麟、统信UOS 数据库。 巴别鸟推荐使用AliSQL数据库或其他兼容MySQL的数据库如：open Causs （高斯）。 巴别鸟也可以为定制接入其他国产数据库。如：达梦、人大金仓、南大通用….. 客户端。 巴别鸟客户端可以运行在Linux系统上，支持麒麟、统信等国产化系统。 由于Linux系统文件管理界面并没有统一，Linux版本的巴别鸟不支持同步文件夹及映射盘功能。 分类 分类 标准部署系统（非信创） 巴别鸟信创方案（x86) 巴别鸟信创方案（arm） 信创版本不支持的功能 业务服务器 操作系统 Centos、openEuler、Ubuntu openEuler 、麒麟 鲲鹏、麒麟、统信 无 业务服务器 巴别鸟版本 标准版 巴别鸟信创版（X86） 巴别鸟信创版（arm） 无 业务服务器 数据库 MySQL 高斯、TiDB、aliSql 高斯arm 无 业务服务器 组件/中间件 tomcat tomcat、TongWeb7 tomcat 无 业务服务器 组件/中间件 pomleo pomleo（信创） pomleo（信创） 无 业务服务器 组件/中间件 Elastic Search Elastic Search（ 信创） Elastic Search（arm） 无 业务服务器 组件/中间件 Redis Babel readis Babel readis 无 存储服务器 存储系统 minio minio minio arm 无 客户端 客户端 巴别鸟win/mac客户端 巴别鸟linux/麒麟/Ubuntu客户端 需要二开移植 linux版本客户端不支持映射盘、同步文件夹功能" }, { "lang": "zh", "slug": "changelog", "title": "更新日志", "description": "按版本整理巴别鸟企业网盘公开更新记录，并标注当前最新版本 v9.4.2.2606171439。", "category": "版本记录", "top_category": "更新日志", "keywords": [ "更新日志", "版本", "v9.4.2", "敏感内容识别", "自动化任务" ], "url": "zh/changelog.html", "source": "content/zh/changelog.md", "summary": "更新日志 当前最新版本口径为 v9.4.2.2606171439 。公开更新日志页面仍可能显示较早版本，本页把公开记录和当前已确认的最新版本信息合并整理，便于用户快速了解功能演进。 公开更新日志来源： 当前版本 v9.4.2.2606171439 类型 更新内容 映射盘 优化映射盘访问体验，提高云端文件按需访问的稳定性 安全 推出敏感内容识别功能，可用于识别、标记和限制敏感内容文件 多语言 支持香港繁体和俄语，便于跨地区或国际化团队使用 自动化任务 自动化任务优化，增加批量创建文件夹功能 近期版本 v9.4.1 2026 02 14 模块 更新内容 自动化任务 增加“创建签章”和“批量创建文件夹”两类任务 电子签章 签章界面调整，增加签章教程视频播放 敏感内容识别 企业控制台“管理工具”增加敏感内容识别功能 对外分享 部门文件和个人文件可分别设置不允许对外分享、无需审批或需要审批，并可指定审核人员 企业控制 增加禁止用户自行修改个人信息的配置项 在线编辑 OnlyOffice 版本号大于 9.2 时显示在线编辑 PDF 按钮 文件访问 任意文件支持右键获取访问链接 优化修复 修复若干问题并优化界面细节 v9.4.0 2026 01 04 模块 更新内容 自动化任务入口 文件夹、部门、项目、素材库、分类等右键菜单增加自动化任务 自动化任务类型 支持自动清理文件夹、自动重命名、自动整理、自动转 PDF 自动化任务管理 左侧栏增加“自动化任务”，可查看、编辑、取消已有任务，也可新建任务 权限控制 部门、项目、素材库、分类等对象需要具备文件访问控制权限才可设置自动化任务 选择文件体验 ", "headings": [ { "level": 1, "title": "更新日志", "id": "section" }, { "level": 2, "title": "当前版本", "id": "section-2" }, { "level": 3, "title": "v9.4.2.2606171439", "id": "v9-4-2-2606171439" }, { "level": 2, "title": "近期版本", "id": "section-3" }, { "level": 3, "title": "v9.4.1 2026 02 14", "id": "v9-4-1-2026-02-14" }, { "level": 3, "title": "v9.4.0 2026 01 04", "id": "v9-4-0-2026-01-04" }, { "level": 3, "title": "v9.3.6 2025 11 11", "id": "v9-3-6-2025-11-11" }, { "level": 3, "title": "v9.3.2 2025 07 19", "id": "v9-3-2-2025-07-19" }, { "level": 3, "title": "v9.3.1 2025 06 27", "id": "v9-3-1-2025-06-27" }, { "level": 3, "title": "v9.3.0 2025 03 至 2025 05", "id": "v9-3-0-2025-03-2025-05" }, { "level": 2, "title": "重要历史版本", "id": "section-4" }, { "level": 3, "title": "v9.2.x", "id": "v9-2-x" }, { "level": 3, "title": "v9.1.x", "id": "v9-1-x" }, { "level": 3, "title": "v9.0.x", "id": "v9-0-x" }, { "level": 3, "title": "v8.x 至 v7.9.5", "id": "v8-x-v7-9-5" }, { "level": 2, "title": "功能演进索引", "id": "section-5" } ], "images": [], "text": "更新日志 当前最新版本口径为 v9.4.2.2606171439 。公开更新日志页面仍可能显示较早版本，本页把公开记录和当前已确认的最新版本信息合并整理，便于用户快速了解功能演进。 公开更新日志来源： 当前版本 v9.4.2.2606171439 类型 更新内容 映射盘 优化映射盘访问体验，提高云端文件按需访问的稳定性 安全 推出敏感内容识别功能，可用于识别、标记和限制敏感内容文件 多语言 支持香港繁体和俄语，便于跨地区或国际化团队使用 自动化任务 自动化任务优化，增加批量创建文件夹功能 近期版本 v9.4.1 2026 02 14 模块 更新内容 自动化任务 增加“创建签章”和“批量创建文件夹”两类任务 电子签章 签章界面调整，增加签章教程视频播放 敏感内容识别 企业控制台“管理工具”增加敏感内容识别功能 对外分享 部门文件和个人文件可分别设置不允许对外分享、无需审批或需要审批，并可指定审核人员 企业控制 增加禁止用户自行修改个人信息的配置项 在线编辑 OnlyOffice 版本号大于 9.2 时显示在线编辑 PDF 按钮 文件访问 任意文件支持右键获取访问链接 优化修复 修复若干问题并优化界面细节 v9.4.0 2026 01 04 模块 更新内容 自动化任务入口 文件夹、部门、项目、素材库、分类等右键菜单增加自动化任务 自动化任务类型 支持自动清理文件夹、自动重命名、自动整理、自动转 PDF 自动化任务管理 左侧栏增加“自动化任务”，可查看、编辑、取消已有任务，也可新建任务 权限控制 部门、项目、素材库、分类等对象需要具备文件访问控制权限才可设置自动化任务 选择文件体验 添加相关文件界面增加搜索框、清除搜索按钮、列表和平铺模式 优化修复 修复若干问题并优化界面细节 v9.3.6 2025 11 11 模块 更新内容 电子签章 个人设置处增加图章设置，前台支持对 PDF、Office、图片等文件添加签章并保存为签署 PDF 文件访问控制 增加“所有下级子部门/文件夹继承该权限”设置项 多语言 新增俄文显示支持 企业文件入口 个人设置可配置点击企业文件后是否直接进入所在部门 轻文档 支持粘贴 Markdown 格式，支持 Markdown 文件导入 文件列表 平铺模式显示文件夹内文件数量 文件锁 增加自动解锁配置项，可控制超过 2 小时的锁是否自动解锁 批量选择 修复筛选后全选可能选中非筛选范围文件的问题 v9.3.2 2025 07 19 模块 更新内容 智能推荐 个人文件、企业文件、素材库频道推荐文件最多显示 6 个，可在个人设置中开启或关闭 文件筛选 文件列表右上角增加最近访问、星标文件筛选项 预览 支持预览 .sh 、 .py 、 .bash 、 .sql 文件 分类 支持批量设置分类 优化修复 修复若干问题并优化界面 v9.3.1 2025 06 27 模块 更新内容 链接文件 支持创建链接文件，链接文件可打开对应页面并支持缩略图和预览 轻文档 支持创建轻文档并在线编辑 文件夹展示 个人文件和企业文件普通文件夹支持“显示子文件夹内容” v9.3.0 2025 03 至 2025 05 模块 更新内容 智巢 AI 新增 AI 搜索、AI 搜图、单文档 AI 问答、右侧栏智巢对话、深度思考和联网搜索 Excel 数据助理 新增表格数据问答、深度思考模式、表格辅助能力 图片 OCR 支持识别图片中的文字，并参与检索 AI 搜索模式 AI 搜索支持快速搜索和深度研究 AI 自动打标签 可根据标签库预设标签自动匹配当前文件，支持批量打标 图片检索 优化 AI 搜图和搜相似体验 界面 调整右键菜单样式和相关界面 重要历史版本 v9.2.x 版本 重点更新 v9.2.1 2025 01 13 搜索结果列表显示标签；提醒关注发送铃铛通知；修复若干问题 v9.2.0 2024 12 15 增加素材库栏目；支持素材分类、子素材库、访问审批、下载审批、缩略图控制、上传黑白名单和素材库访问权限 v9.1.x 版本 重点更新 v9.1.8 2024 10 19 档案库搜索改进、缩略图和高级搜索提速、搜索时严格检测权限配置、draw.io 显示优化 v9.1.7 2024 09 14 私有云定期改密、MP4 缩略图、短链接分享、文件夹打开日志、draw.io 创建、无下载权限不显示缩略图 v9.1.6 2024 08 07 标签列表优化、客户端传输列表优化、项目通知调整、系统标题栏企业简称、同步入口、XSS 与越权修复 v9.1.5 2024 06 17 部门和项目上传黑白名单、在线编辑限制、对外分享限制、Mac 双向绑定、个人私有文件限制 v9.1.3 2024 04 22 文件夹本地归档、分享管理入口、标签集合筛选、音视频播放、上传提速 v9.1.2 2024 03 23 多终端登录数限制、下载提速、键盘快捷键、智巢阅读助手、文件夹上传、批量重命名 v9.1.1 2024 02 07 分享审核、企业内人员访问链接、回收站优化、文件上传白名单、审批阶段移动、批量设置安全级别、标签筛选增强 v9.1.0 2024 01 26 网页预览 CAD、客户端支持匿名用户下载文件夹 v9.0.x 版本 重点更新 v9.0.4 2023 12 多级回收站、深浅主题设置、XSS 修复、文件访问控制分页、客户端匿名下载 v9.0.3 2023 10 21 删除部门模板文件夹、企业空间统计刷新、访问控制分享按钮、数字文件名排序、客户端分享链接访问 v9.0.2 2023 09 29 官网增加智巢 AI 申请内测入口、PDF 搜索修复、访问控制弹框增加分享按钮 v9.0.0 2023 09 排序支持文件夹与文件混排；个人设置增加全局默认排序相关开关 v8.x 至 v7.9.5 版本 重点更新 v8.7.1 2023 07 07 控制台查看账号参与的项目、分享、登录历史和访问控制文件；其他设备登录提示 v8.7 2023 05 07 访问控制人员权限详情、仅查看文件名分享权限、仅使用自定义权限、标签样式自定义 v8.6.6 企业控制台日志新增移动/复制搜索，高级搜索增强，图片元数据，复制/剪切粘贴，运维管理员权限 v8.6.5 2023 01 16 私有云发送文件、监控预警、快捷菜单自定义、默认不接收通知、项目保存路径、专业版回收站 30 天 v8.6.4 2022 11 14 到期项目显示、清空账号权限、OnlyOffice 预览配置、匿名在线编辑、档案库入口、维护中机制 v8.6.3 2022 09 30 本地归档、授权数超限登录控制、项目转交限制 v8.6.2 2022 08 26 上传列表界面、项目转交选项、病毒文件处理、个人用户空间上限 v8.6.1 2022 07 15 授权人数显示、超授权限制、删除含子部门的部门、上传权限与在线编辑关系调整 v8.6.0 2022 06 11 个人文件夹转项目、Session 配置、禁止匿名分享、审批人可添加自己、流量统计导出 v8.5.x 2022 部门模板、IP 策略登录项、脑图另存、企业邮箱修改、分享未注册用户开关、创建思维导图、企业结构隐藏、快照分享等 v8.2 2021 05 21 归档提速、OnlyOffice 只读预览、管理分享权限、项目助理、开放式投件箱、回收站一键恢复 v8.1 2021 04 04 回收站恢复所有文件、海外登录优化、客户端编辑和在线编辑图标区分 v8.0 2021 01 OnlyOffice 只读预览和在线编辑、密码错误限制、项目外部用户、流量限速、上传黑名单、视频倍速播放 v7.9.5 分组按部门添加、项目频道一致性、仅上传分享隐藏文件、批量设置访问控制、带水印 PDF 下载、XSS 修复 功能演进索引 主题 代表版本 相关章节 自动化任务 v9.4.0、v9.4.1、v9.4.2 自动化任务 敏感内容识别 v9.4.1、v9.4.2 敏感内容识别 素材库 v9.2.0、v9.4.0 素材库 智巢 AI v9.3.0 起 智巢 AI 在线编辑与轻文档 v8.0、v9.3.1、v9.3.6 在线编辑 权限安全 v8.7、v9.1.1、v9.1.5、v9.4.1 权限体系、安全与审计 客户端、同步与映射盘 v9.1.6、v9.4.2 同步与客户端、虚拟映射盘" }, { "lang": "zh", "slug": "faq-index", "title": "FAQ 总览", "description": "巴别鸟常见问题的分类入口和全部问题索引。", "category": "常见问题", "top_category": "常见问题", "keywords": [ "FAQ", "用户手册", "问题" ], "url": "zh/faq-index.html", "source": "content/zh/faq-index.md", "summary": "FAQ 总览 本页汇总巴别鸟企业网盘常见问题。可以按场景进入对应章节，也可以在“全部问题索引”中直接定位问题编号。 按场景查找 场景 适合查的问题 入口 初次使用 注册、登录、上传、新建、企业文件、个人文件、部门文件夹、项目文件夹 入门、账号与文件空间 权限配置 角色、部门权限、文件访问控制、上传权限、仅上传权限、密级、审批流程 权限、部门与项目 分享协作 邀请分享、链接分享、头像、通知、锁定、版本、动态、讨论组、工作台 分享、协作与通知 客户端与本地访问 同步、映射盘、删除同步、冲突、权限、客户端拖拽、映射盘丢失 同步、客户端与映射盘 部门和项目管理 部门成员、部门文件、临时项目、收集文件、外部用户、企业微信/钉钉 部门管理、项目和收集文件 文件查看与检索 PPT、视频、误删、离职文件、在线编辑、标签、高级搜索、树形目录 预览、在线编辑、搜索和标签 档案与评审 档案库、批注、回复、批注权限、角标、上传大小、CAD、预览卡住 档案、批注、评审和角标 部署与排障 专业版、私有化、对象存储、智巢 AI、预览格式、验证码、上传速度、邀请成员 部署、AI、限制和排障 常见排障路径 无法登录或提示用户不存在 1. 确认登录入口是公有云、企业二级域名还是私有云专属域名。 2. 确认账号是管理员分配的邮箱或手机号。 3. 私有云用户应通过私有云入口或企业专属地址登录。 4. 仍无法登录时，让管理员在企业控制台检查账号状态、部门归属和初始密码通知。 无法上传或新建文件夹 1. 确认当前位置不是企业文件根目录，企业文件需要进入具体部门后上传。 2. 确认所在部门角色是否具备上传、新建文件夹或创建", "headings": [ { "level": 1, "title": "FAQ 总览", "id": "faq" }, { "level": 2, "title": "按场景查找", "id": "section" }, { "level": 2, "title": "常见排障路径", "id": "section-2" }, { "level": 3, "title": "无法登录或提示用户不存在", "id": "section-3" }, { "level": 3, "title": "无法上传或新建文件夹", "id": "section-4" }, { "level": 3, "title": "同步或映射盘异常", "id": "section-5" }, { "level": 3, "title": "分享链接打不开或权限不对", "id": "section-6" }, { "level": 3, "title": "在线编辑或预览异常", "id": "section-7" }, { "level": 2, "title": "全部问题索引", "id": "section-8" }, { "level": 3, "title": "入门、账号与文件空间", "id": "section-9" }, { "level": 3, "title": "权限、部门与在线编辑", "id": "section-10" }, { "level": 3, "title": "分享、通知、版本与工作台", "id": "section-11" }, { "level": 3, "title": "同步、客户端与映射盘", "id": "section-12" }, { "level": 3, "title": "部门管理、项目和文件收集", "id": "section-13" }, { "level": 3, "title": "预览、在线编辑、搜索和标签", "id": "section-14" }, { "level": 3, "title": "档案、批注、评审和角标", "id": "section-15" }, { "level": 3, "title": "部署、AI、限制和排障", "id": "ai" } ], "images": [], "text": "FAQ 总览 本页汇总巴别鸟企业网盘常见问题。可以按场景进入对应章节，也可以在“全部问题索引”中直接定位问题编号。 按场景查找 场景 适合查的问题 入口 初次使用 注册、登录、上传、新建、企业文件、个人文件、部门文件夹、项目文件夹 入门、账号与文件空间 权限配置 角色、部门权限、文件访问控制、上传权限、仅上传权限、密级、审批流程 权限、部门与项目 分享协作 邀请分享、链接分享、头像、通知、锁定、版本、动态、讨论组、工作台 分享、协作与通知 客户端与本地访问 同步、映射盘、删除同步、冲突、权限、客户端拖拽、映射盘丢失 同步、客户端与映射盘 部门和项目管理 部门成员、部门文件、临时项目、收集文件、外部用户、企业微信/钉钉 部门管理、项目和收集文件 文件查看与检索 PPT、视频、误删、离职文件、在线编辑、标签、高级搜索、树形目录 预览、在线编辑、搜索和标签 档案与评审 档案库、批注、回复、批注权限、角标、上传大小、CAD、预览卡住 档案、批注、评审和角标 部署与排障 专业版、私有化、对象存储、智巢 AI、预览格式、验证码、上传速度、邀请成员 部署、AI、限制和排障 常见排障路径 无法登录或提示用户不存在 1. 确认登录入口是公有云、企业二级域名还是私有云专属域名。 2. 确认账号是管理员分配的邮箱或手机号。 3. 私有云用户应通过私有云入口或企业专属地址登录。 4. 仍无法登录时，让管理员在企业控制台检查账号状态、部门归属和初始密码通知。 无法上传或新建文件夹 1. 确认当前位置不是企业文件根目录，企业文件需要进入具体部门后上传。 2. 确认所在部门角色是否具备上传、新建文件夹或创建项目权限。 3. 检查目标目录是否有文件访问控制、黑名单、白名单、空间限制或仅上传权限。 4. 客户端、同步和映射盘上传也会遵循同一权限体系。 同步或映射盘异常 1. 确认客户端已登录正确企业，映射盘或同步任务仍在运行。 2. 检查本地路径、云端路径、同步方向、同步黑名单和文件权限。 3. 若出现冲突或部分失败，先确认本地与云端最新版本，再按需要覆盖、恢复或上传新版本。 4. 映射盘更依赖网络和权限实时状态，同步文件夹更适合离线编辑和长期本地工作目录。 分享链接打不开或权限不对 1. 检查分享是否过期、被关闭、被管理员限制或需要企业内成员访问。 2. 检查分享权限是否允许预览、下载、编辑、批注或上传。 3. 对部门文件或个人文件，如果企业开启对外分享审批，需要等待审核通过。 4. 对加密文件夹内文件，即使拿到分享也需要输入加密文件夹密码。 在线编辑或预览异常 1. 确认文件格式是否受支持，Office 在线编辑还取决于 OnlyOffice 或在线 Office 模块。 2. 大文件、复杂 PPT、CAD、视频转码可能需要等待预览生成。 3. 如果文件被锁定，先确认是否有人正在编辑，必要时由管理员解锁。 4. 预览长期卡住时，检查转码服务、文件格式、文件大小和浏览器兼容性。 全部问题索引 入门、账号与文件空间 1. 巴别鸟能做什么？ 2. 巴别鸟可以在什么设备上使用？ 3. 在哪里注册巴别鸟账号？ 4. 如何登录我的巴别鸟？ 5. 登录时提示“用户不存在”，是怎么回事？ 6. 如何上传文件？ 7. 为什么我不能在企业文件中上传文件或创建文件夹？ 8. 如何新建文件夹？ 9. 如何进入企业控制台？ 10. 什么是角色？ 11. 蓝色的文件夹和黄色的文件夹有什么区别？ 12. 我个人的文件存在哪里？ 13. 什么是部门文件夹？ 14. 什么是项目文件夹？ 15. 如何建立项目？ 16. 部门和项目有什么区别？ 17. 为什么我不能在部门里上传文件？ 18. 文件如何排序？ 权限、部门与在线编辑 19. 如何使用在线编辑？ 20. 如何多人协同在线编辑？ 21. 为什么多人编辑的文档下载下来后还是编辑前的版本（老版本）？ 22. 文件访问控制如何使用？如何控制某个文件的访问权限？ 23. 如何自定义分享可选权限？ 24. 部门成员的权限如何控制？ 25. 部门文件如何让其他部门的成员看到？ 26. 部门经理如何管理部门？ 27. 如何知道部门文件中有哪些被分享了？ 28. 文件密级（安全级别）是什么？ 29. 如何查看部门的访问日志？ 30. 如何查看部门成员的使用情况？ 31. 审批流程是做什么的？ 32. 上传权限和仅上传权限有什么区别？ 33. 为什么我看不到别人上传的文件？ 分享、通知、版本与工作台 34. 我如何分享一个文件给其他人？ 35. 我如何查看其他人分享给我的文件？ 36. 邀请分享和链接分享有什么区别？ 37. 如何修改我的默认头像？ 38. 我想在同事更新文件后就收到提示通知，怎么操作？ 39. 有的文件或文件夹图标后面有个「控」的角标，是什么意思？ 40. 为什么我新上传的文件搜索不到？ 41. 为什么文件夹在文件列表中不显示大小？ 42. 为什么我上传的文件夹不能覆盖同名文件夹，而文件可以？ 43. 为什么我的文件会提示被锁定？ 44. 如何解锁被锁定的文件？ 45. 如何回滚文件版本？ 46. 动态是什么？ 47. 可以搜索动态么？ 48. 讨论组是什么？ 49. 工作台是什么？如何使用工作台？ 50. 我不想被太多的动态信息骚扰，该怎么办？ 同步、客户端与映射盘 51. 映射盘是什么？和同步有什么区别？ 52. 为什么我无法同步新增加的文件或者没有同步最新的文件版本？ 53. 为什么我同步时提示有几个文件同步不成功？ 54. 和同步有关的权限有哪些？ 55. 同步文件时我本地删除了某个文件，云端还会有么？ 56. 同步时，我云端删除了某个文件，本地还会有么？ 57. 我们部门几个人可以同时同步某一个文件夹么？ 58. 我映射盘上删除一个文件，云端还会有么？ 59. 为什么我映射盘上的文件无法拖入到微信发送？ 60. 为什么我找不到我的映射盘了？ 61. 为什么我同步的文件夹里有一些文件能同步，而有一些不能？ 62. 为什么部门里有的文件我可以编辑，有的不可以？ 63. 我是超级管理员，为什么我看不到一些部门的动态？ 64. 我是超级管理员，为什么我清空回收站后文件又会出现在回收站？ 部门管理、项目和文件收集 65. 部门经理如何添加新成员？ 66. 部门经理怎么改变部门成员的权限？ 67. 部门经理如何查看部门有哪些文件被分享了？ 68. 部门里面有个文件/文件夹不想给一些人看到，怎么操作？ 69. 我想让我们部门的人只能在部门的电脑上使用巴别鸟，怎么操作？ 70. 巴别鸟是否支持一个用户在多个部门？ 71. 临时建立一个项目组，需要从公司各个部门抽调人员并共享文件，怎么操作？ 72. 为什么我不能在部门里创建项目？ 73. 部门里有个文件想给其他部门的人一起看，但不想一个个邀请，该怎么操作？ 74. 我想收集各个部门的一些材料，怎么操作？ 75. 我想发个文件给全公司所有人，让他们都能查看，但不能下载，怎么操作？ 76. 如何使用巴别鸟快速收集用户的文件？ 77. 我发给客户的分享里的内容不对，该怎么办？ 78. 我不想让客户下载我分享的文件，但是能看，怎么操作？ 79. 我想把巴别鸟上的文件在微信里发给联系人，怎么操作？ 80. 我使用企业微信/钉钉可以直接访问巴别鸟的文件么？ 预览、在线编辑、搜索和标签 81. 为什么我预览PPT不能播放动画？ 82. 为什么有的视频文件巴别鸟不能播放？ 83. 文件不小心误删了，怎么办？ 84. 同事离职了，他的文件怎么办？ 85. 部门文件太多了，我新上传了一个文件，想让某同事看下，怎么操作简单？ 86. 为什么下载文件夹点击下载半天没反应？ 87. 客户端的编辑和在线编辑有什么区别？ 88. 为什么我在线编辑器打开很慢？ 89. 我想让几个同事一起填个表格，该怎么操作？ 90. 如何才能树状的查看文件夹？ 91. 能不能按条件筛选出我想找的文件？ 92. 什么是标签？ 93. 如何使用巴别鸟标签？ 94. 巴别鸟如何搜索标签？ 95. 巴别鸟支持高级搜索么？ 96. 我想发送电脑上的文件给同事，有没有好的办法？ 档案、批注、评审和角标 97. 如何管理企业档案库？ 98. 什么类型的文件可以批注？ 99. 如何创建批注？ 100. 如何删除批注？ 101. 如何回复批注？ 102. 我上传了文档的新版本，批注不见了？ 103. 我如何查看老版本的批注？ 104. 文件版本删除了，批注会删除么？ 105. 我回复的批注错误了,能不能撤销？ 106. 为什么我不能创建批注？ 107. 为什么我给了用户链接分享的批注权限，但他们却不能批注？ 108. 为什么我在APP上不能创建一些类型的批注？ 109. 为什么我在电脑上不能创建一些类型的批注？ 110. 在动态里直接回复的批注不能显示怎么办？ 111. 文件上会显示各种角标，他们分别有什么含义？ 112. 最大能上传的单个文件是多大？ 113. CAD文件在客户端预览不了，怎么办？ 114. 预览文件时，卡在生成预览文件界面，怎么办？ 部署、AI、限制和排障 115. 专业版到期了怎么续费？ 116. 巴别鸟上传文件类型有限制吗？ 117. 在线编辑有人数限制吗？ 118. 分享文件给其他人，还没到截至日期，但链接打不开了。 119. 下载速度忽然变慢了，是怎么回事？ 120. 进入一个文件夹，右下角提示文件不存在。 121. 怎么查看共享文件的实时在线编辑人员？ 122. 部门角色有上传文件的权限，在部门里的某个文件夹下不能上传文件，为什么？ 123. 团队里的文件删除后，在谁的回收站里？ 124. 团队删除后，会保存在回收站里吗？ 125. 巴别鸟支持私有化部署么？ 126. 如何私有化部署巴别鸟系统？ 127. 巴别鸟支持对象存储么？ 128. 私有化部署巴别鸟系统需要什么硬件？ 129. 巴别鸟支持对接企业微信么？ 130. 什么是智巢AI？ 131. 我也想要智巢AI助理，怎么操作？ 132. 智巢AI收费吗？如何收费？ 133. 智巢AI可以私有化么？ 134. 巴别鸟支持预览的文件格式有哪些？ 135. 如何使用客户端匿名下载？ 136. 在巴别鸟上传了文件，过了一会儿文件自动删除了，怎么回事呢？ 137. 巴别鸟在手机浏览器上可以上传文件吗？ 138. 匿名用户可以上传文件吗？ 139. 为什么不能在个人文件栏目上传文件？ 140. 可以在前台创建部门吗？ 141. 批量上传文件有数量或大小限制吗？ 142. 注册登录的时候，收不到验证码（邮箱，手机）？ 143. 私有和公有有什么区别？ 144. 什么权限的人可以归档文件？ 145. 电子签名是设置的哪个位置，是否可以手写？ 146. 怎么可以聊天？ 147. 文件水印可以批量添加么？ 148. 上传速度很慢，怎么回事？ 149. 为什么邀请不了成员？" }, { "lang": "zh", "slug": "faq-basic", "title": "FAQ：入门、账号与文件空间", "description": "覆盖 入门、账号与文件空间 相关常见问题。", "category": "常见问题", "top_category": "常见问题", "keywords": [ "FAQ", "FAQ：入门、账号与文件空间" ], "url": "zh/faq-basic.html", "source": "content/zh/faq-basic.md", "summary": "FAQ：入门、账号与文件空间 以下问题覆盖用户在使用巴别鸟企业网盘时常见的操作、权限、协作和排障场景。 1. 巴别鸟能做什么？ 巴别鸟是一个企业网盘，主要解决企业文件统一管理、协同协作、数据安全三大问题。巴别鸟可以自动同步您的工作文件到云端，在任何可以访问互联网的地方都可以使用巴别鸟来访问您的个人文件或您所在部门的文件。在巴别鸟客户端，你可以使用鼠标右键点击文件上的编辑按钮，使用本地应用去编辑云端文件，也可以在线编辑office文档（需购买在线office模块）。同时，您和同事在巴别鸟里也会有统一的部门空间，整个部门的人可以按不同权限访问部门的文件。大家在部门中可以共同批注讨论文件、协同编辑Office文档（需购买在线office模块）。每个文件的编辑操作都会保存下来形成新的版本，保证你的工作内容不会因为不当的操作或设备故障而丢失。 2. 巴别鸟可以在什么设备上使用？ 巴别鸟支持使用浏览器（支持Html5规范，推荐使用Chrome浏览器）、iOS设备（苹果手机和iPad）、安卓设备进行访问。也可以安装Windows客户端、Mac客户端。同时支持接入钉钉及企业微信（需要另购相关模块）。 3. 在哪里注册巴别鸟账号？ 公有云用户官网（网址：https://www.babel.cc）注册企业公有云版本或者个人版即可使用。企业公有云版只需要一个手机号注册就可以了，企业的其他成员是管理员在企业控制台添加的。 注册地址：https://www.babel.cc/p/signin entry.do 同时也可以下载客户端，在客户端使用巴别鸟，下方为下载地址： https://www.babel", "headings": [ { "level": 1, "title": "FAQ：入门、账号与文件空间", "id": "faq" }, { "level": 2, "title": "1. 巴别鸟能做什么？", "id": "1" }, { "level": 2, "title": "2. 巴别鸟可以在什么设备上使用？", "id": "2" }, { "level": 2, "title": "3. 在哪里注册巴别鸟账号？", "id": "3" }, { "level": 2, "title": "4. 如何登录我的巴别鸟？", "id": "4" }, { "level": 2, "title": "5. 登录时提示“用户不存在”，是怎么回事？", "id": "5" }, { "level": 2, "title": "6. 如何上传文件？", "id": "6" }, { "level": 2, "title": "7. 为什么我不能在企业文件中上传文件或创建文件夹？", "id": "7" }, { "level": 2, "title": "8. 如何新建文件夹？", "id": "8" }, { "level": 2, "title": "9. 如何进入企业控制台？", "id": "9" }, { "level": 2, "title": "10. 什么是角色？", "id": "10" }, { "level": 2, "title": "11. 蓝色的文件夹和黄色的文件夹有什么区别？", "id": "11" }, { "level": 2, "title": "12. 我个人的文件存在哪里？", "id": "12" }, { "level": 2, "title": "13. 什么是部门文件夹？", "id": "13" }, { "level": 2, "title": "14. 什么是项目文件夹？", "id": "14" }, { "level": 2, "title": "15. 如何建立项目？", "id": "15" }, { "level": 2, "title": "16. 部门和项目有什么区别？", "id": "16" }, { "level": 2, "title": "17. 为什么我不能在部门里上传文件？", "id": "17" }, { "level": 2, "title": "18. 文件如何排序？", "id": "18" } ], "images": [], "text": "FAQ：入门、账号与文件空间 以下问题覆盖用户在使用巴别鸟企业网盘时常见的操作、权限、协作和排障场景。 1. 巴别鸟能做什么？ 巴别鸟是一个企业网盘，主要解决企业文件统一管理、协同协作、数据安全三大问题。巴别鸟可以自动同步您的工作文件到云端，在任何可以访问互联网的地方都可以使用巴别鸟来访问您的个人文件或您所在部门的文件。在巴别鸟客户端，你可以使用鼠标右键点击文件上的编辑按钮，使用本地应用去编辑云端文件，也可以在线编辑office文档（需购买在线office模块）。同时，您和同事在巴别鸟里也会有统一的部门空间，整个部门的人可以按不同权限访问部门的文件。大家在部门中可以共同批注讨论文件、协同编辑Office文档（需购买在线office模块）。每个文件的编辑操作都会保存下来形成新的版本，保证你的工作内容不会因为不当的操作或设备故障而丢失。 2. 巴别鸟可以在什么设备上使用？ 巴别鸟支持使用浏览器（支持Html5规范，推荐使用Chrome浏览器）、iOS设备（苹果手机和iPad）、安卓设备进行访问。也可以安装Windows客户端、Mac客户端。同时支持接入钉钉及企业微信（需要另购相关模块）。 3. 在哪里注册巴别鸟账号？ 公有云用户官网（网址：https://www.babel.cc）注册企业公有云版本或者个人版即可使用。企业公有云版只需要一个手机号注册就可以了，企业的其他成员是管理员在企业控制台添加的。 注册地址：https://www.babel.cc/p/signin entry.do 同时也可以下载客户端，在客户端使用巴别鸟，下方为下载地址： https://www.babel.cc/p/download.do 私有云用户可以询问IT管理员获取所在企业的登录地址。 你可以在我们的网站上下载相应的客户端，点击私有云入口按钮，输入自己企业的域名，跳转到登录界面登录。 私有云账号是我们的部署人员部署私有化巴别鸟系统时创建的，企业的其他成员也是管理员在企业控制台添加的。 下载地址：https://www.babel.cc/p/download.do 4. 如何登录我的巴别鸟？ 公有云企业版巴别鸟的登录账号和密码由管理员分配，在官网首页点击登录即可。你可能已经在邮箱或手机中收到相应的账号密码，在巴别鸟公有云登录界面输入即可登录到你所在的企业。 登录入口： https://www.babel.cc/account/signin.do 巴别鸟会为公有云上的企业分配一个专属二级域名，你也可以通过这个域名进行登录，域名通常的格式如下： https://xxx.babel.cc 如果您所在的企业购买了私有化巴别鸟，你可以在浏览器中输入你们企业的专属云盘地址进行登录。如果不知道云盘地址（企业域名），请联系企业IT人员。 如果使用客户端或APP，请点击“私有云入口”按钮输入域名后再登录。私有云入口按钮一般在登录框下方。 点击私有化入口后，会出现一个域名输入框，要求输入私有化域名（直接输入域名头即可，不需要加http或https）默认选择https协议。这个时候输入你们企业的云盘域名，点击确定即可进入私有云的登录界面 巴别鸟企业账号由管理员分配，管理员分配后会自动发送邮件或短信，用收取到邮件的邮箱及附在邮件中的初始密码或手机号及短信中的初始密码进行登录。 如果你所在的企业使用了域控单点登录，输入用户名及密码登录，一般情况下，用户名为你的域控邮箱，密码是你的域控密码。 设置好登录私有云的域名地址登录后，系统会记住私有云的地址，下次点击直接登录即可，不需要再次输入。 5. 登录时提示“用户不存在”，是怎么回事？ 检查你输入的账号，确保账号输入正确。 检查你的账号是不是管理员分配的登录账号，巴别鸟登录账号通常是一个邮箱或手机号。 如果你是私有云客户，最有可能的问题是，你在公有云登录入口输入了登录账号及密码。如果你是私有云用户，需要使用私有云的登录入口。如何登录私有云账户，请参考FAQ问题4：如何登录我的巴别鸟？ 6. 如何上传文件？ 巴别鸟支持多种上传文件的方式，但巴别鸟会判断你在上传目标目录有没有上传权限，如果没有上传权限，根据上传途径不同会给出提示或不予响应。常用的上传方式如下： 浏览器及客户端拖拽上传：在巴别鸟上打开目标文件夹，直接拖拽要上传的文件或文件夹至目标文件夹进行上传。（有些浏览器不支持文件夹拖拽上传，如果需要在浏览器拖拽上传，建议使用Chrome浏览器） 点击左上角“新建”按钮进行上传：在巴别鸟上打开要上传的目录，点击“新建”按钮选择“上传文件”选择文件进行上传。 安装客户端后在本地右键点击要上传的文件或文件夹，选择巴别鸟 上传该文件 使用客户端同步功能进行上传：文件夹同步后，直接往文件夹内拖入要上传的文件，该文件会自动同步上传至巴别鸟的对应文件夹 使用映射盘进行上传：在映射盘中打开目标文件夹，拖拽文件至映射盘中，只要你的账户拥有该文件夹的上传权限，在映射盘中的文件会自动上传 在手机APP上打开巴别鸟目标文件夹，点击右上角+号选择上传文件进行上传 在手机微信上打开文件，选择右上角“更多”按钮，选择“用其他应用打开”选择“巴别鸟”进行上传 7. 为什么我不能在企业文件中上传文件或创建文件夹？ 巴别鸟企业文件是以部门为单位管理的，所以企业文件栏目的根目录是用来显示你所属的部门的。在根目录是无法上传和新建文件的。要上传文件到企业中，需要点开你所在的部门，在部门中上传。 如果在部门中也无法上传文件（没有看到上传按钮）或拖拽上传无效，请联系管理员确认你在该部门中是否有上传权限。 8. 如何新建文件夹？ 在部门中拥有新建文件夹权限的成员可以在部门文件夹中新建文件夹 在个人文件中可以任意创建文件夹（有些企业设置不允许用户上传个人私有文件，如果开启这个设置，在个人空间也不能新建文件夹） 在要新建文件夹目录的空白处点击鼠标右键，会弹出新建菜单。在其中选择新建文件夹 也可以点击左上角“新建”按钮，进行文件夹新建。 9. 如何进入企业控制台？ 管理员点击左上角头像，选择企业控制台即可进入 10. 什么是角色？ 角色是成员在部门中的权限集合，设定角色后，根据部门的管理需要，可以给不同成员赋予不同角色。该成员在赋予角色的部门中，对部门文件夹的访问就按角色拥有的权限进行。巴别鸟允许一个企业成员在不同的部门拥有不同的角色也就是不同的访问权限。 多个部门成员可以使用同一个角色，只要设定好角色，根据需要分配给成员即可。但这也意味着，角色的权限内容更改后，使用同一个角色的成员的权限也都会随之更改。 管理员可以在企业控制台——权限管理——部门权限列表中自定义或修改角色权限。 11. 蓝色的文件夹和黄色的文件夹有什么区别？ 带有“企“字的蓝色文件夹是企业文件夹，整个企业的人（身份是受限成员的除外）都可以访问其中的内容。企业文件夹有两种：企业发布文件夹和共同发布文件夹。只有企业管理员、安全保密员和档案管理员可以往企业发布文件夹里上传文件。企业所有成员都可以往共同发布文件夹里上传文件。一般会放一些企业公告或者常用软件等企业共用资源到企业文件夹中。 其他蓝色的是部门文件夹，蓝色文件夹内的文件属于部门及企业，一般用户在“企业文件”栏目会看到一个以自己所在部门命名的蓝色文件夹。这个文件夹只能由父部门管理员或企业超级管理员、运维管理员、安全保密员建立。在该文件夹下放入的文件通常整个部门的人都能看见。部门文件夹可以理解为整个部门的共享文件夹。 黄色的文件夹是普通文件夹，在部门中（部门文件夹下）有新建文件夹权限的角色都可以创建，部门文件夹下创建的黄色文件夹，一般情况下整个部门的人也都可以访问及上传文件。在“个人文件”下创建的黄色文件夹属于个人的文件夹，如果不分享的话仅有自己可见。 深蓝色的文件夹是项目文件夹，项目文件夹在个人文件中就是个人项目，在部门中就是企业项目。项目文件夹由项目负责人和项目助理分配项目成员权限。项目文件夹可以设定有效期，超过有效期后仅有项目负责人和项目助理可见。在部门文件夹下的项目，部门经理（拥有部门文件管理权限的角色）也可以进行管理并查看和下载里面的所有文件。 12. 我个人的文件存在哪里？ 如果你所在的企业开启了“允许用户上传个人私有文件”（一般为默认开启），你就可以在巴别鸟左侧栏“个人文件”栏目中上传你的个人文件。个人文件只要你不打开分享就仅有你自己可见。 员工离职时，管理员可以转移成员的文件给指定的企业成员，这个转移包含了个人文件。 13. 什么是部门文件夹？ 巴别鸟文档体系中，文件/文件夹体系有两种归属：个人文件和企业文件。 企业文件以部门为单位组织，根据组织结构，每个部门都会有一个属于部门的部门文件夹。部门文件夹有以下特性： 同一部门的成员，只要权限允许，都能访问自己部门的部门文件夹，使用其中的文件。 部门文件归属于企业，部门管理员（拥有部门文件管理权限的人，一般是部门经理）对部门内所有文件都拥有管辖权。 部门经理可以在部门中添加或减少成员，也可改变成员的权限。 父部门的成员可以根据角色权限设定是否能查看子部门。 部门成员删除部门的文件后，在自己、部门经理及企业管理员的回收站可以看到并恢复。 对部门内的所有文件/文件夹，部门经理都可以打开文件访问控制，精确控制部门成员及角色对该文件/文件夹的操作权限。 部门经理（拥有部门文件管理权限的人）不需要登录企业后台，可以在前台直接管理部门。 只有本部门成员及超级管理员、安全保密员能访问该部门的文件。 如果在部门里有文件分享权限，可以邀请其他部门的成员或者外部用户来访问部门的文件。 如果在部门里没有文件分享权限，链接分享及邀请分享需要部门管理员同意。 非部门成员无法查看该部门的动态、加入部门讨论。 部门文件夹有独立的日志及管理，部门经理可以查看。 14. 什么是项目文件夹？ 很多时候，我们需要和多个部门合作，跨部门共享文件，这个时候就需要创建项目文件夹。 你可以在“个人文件”根栏目上创建个人项目，也可以在你所在的部门下创建项目（拥有创建文件夹/项目权限的角色才可以创建部门项目）。个人项目的归属是创建者，部门项目的归属是部门，对于部门项目下的内容，部门经理都可以查看及管理，不管该项目是不是由这个部门经理创建的或该部门经理是否属于该项目。个人项目和部门项目均可邀请整个企业的内部成员或外部人员或未注册巴别鸟的手机或邮箱加入。 项目文件夹有如下特性： 项目有有效期，到期后项目成员就看不到项目了。项目负责人可以中途更改项目的有效期。同时项目可以分别设定项目成员的有效期，项目成员权限有效期到期后，项目成员将无法访问该项目，但该成员在项目中上传的文件会保留。 项目负责人和项目本身都可以转交，个人项目也可以通过转交的方式转交到部门或其他个人，部门项目负责人也可以转交给其他部门或其他成员。如果项目转交给了其他部门，项目归属和项目管理权也会随之转交。 项目内的人员权限不受部门角色影响（除有部门文件管理权限的角色），项目负责人可以任意更改项目成员在项目中的权限并设定项目成员访问项目的截止时间。但在部门项目中，拥有“部门文件管理”权限的角色（一般是部门经理）可以不受项目权限的约束来访问项目。 项目创建者及项目负责人可以邀请企业内部的任何成员加入项目。也支持邀请外部成员加入项目。 项目有独立的项目讨论组，可以在讨论组进行群聊。 部门项目只能创建于部门根目录（为了便于管理）下，不能创建于部门的其他文件夹下。 个人项目只能创建于“个人文件”根目录下，不能创建于其他个人文件夹下。 项目中支持创建子项目。子项目可设定独立的项目管理权限及项目负责人。父项目成员均可查阅子项目的内容，权限跟随父项目。 在讨论组中点击人员头像，可以查看该人员在项目中上传的文件列表。 项目创建后，会显示在项目成员的“我的项目”根目录下。项目成员均可在我的项目栏目访问项目。 在我的项目栏目中也可以查看你加入或管理的项目。 15. 如何建立项目？ 在能创建项目的位置（个人项目创建在“个人文件”根目录下，部门项目创建在部门文件夹根目录下）空白处点击左上角新建按钮，选择新建项目按钮，按引导进行项目创建及添加项目成员。成员被添加后会收到加入项目通知，并且在“我的项目”栏目中就可以访问到该项目。 你可以在“个人文件”根栏目上创建个人项目，也可以在你所在的部门下创建项目（拥有创建文件夹/项目权限的角色才可以创建部门项目）。个人项目的归属是创建者，部门项目的归属是部门，对于部门项目下的内容，部门经理都可以查看及管理，不管该项目是不是由这个部门经理创建的或该部门经理是否属于该项目。个人项目和部门项目均可邀请整个企业的内部成员或外部人员或未注册巴别鸟的手机或邮箱加入。 16. 部门和项目有什么区别？ 在巴别鸟中，部门是企业文件的基本组成单位，企业文件由根部门及根部门下的子部门的树状方式组织。如果从第三方应用导入组织机构，组织机构在巴别鸟中也是以部门的形式存在。 所以，部门文件夹适用于企业中需要长期共享文件的相对固定的组织（就是通常所说的部门）使用。 部门在巴别鸟中有以下特性： 平级部门间互相独立，每个部门都可以独立管理，或是由上级部门管理。 每个部门都有一个对应的部门文件夹，部门成员通过角色权限对应部门文件夹的访问权限。 管理部门的成员角色需要有“部门文件管理”“管理部门人员”权限。 如果要管理下级部门，需要角色权限有“子部门管理”权限。 父部门成员要查看子部门文件需要角色有“查看子部门文件”权限。 由管理员统一分配各部门的存储空间上限。 由安全保密员设定企业或部门的整体安全策略。 部门成员在部门中的访问权限由部门成员在该部门的角色权限决定。 部门中的文件也可以通过文件访问控制来控制成员的访问权限，文件访问控制权限的优先级高于成员在部门的角色权限。 部门成员在企业文件根栏目仅能看到自己加入的部门。譬如：如果该成员同时加入了父部门和子部门，在企业文件根栏目会显示两个部门。如果只加入了一个部门，在企业文件根栏目仅会显示一个部门。 超级管理员在企业文件根栏目会显示企业根部门（以企业名称命名），里面包含了企业所有部门。 删除部门会丢失该部门的所有部门文件。 部门中可以建立子部门、项目、也可以建立或上传普通文件夹。 项目只能创建于部门文件夹下，不能创建于部门里的普通文件夹下。 在巴别鸟中，项目适用于跨部门协作，或者临时组建的项目小组共享文件。项目可以加入其他部门成员，也可以加入外部成员，更加灵活。 巴别鸟项目文件夹有以下特性： 分为个人项目及企业项目，个人项目可创建于个人文件根目录，由创建者管理。企业项目只能创建于部门文件夹下。不同部门可以创建不同的项目。 只要拥有个人私有文件的人都可以创建个人项目（是否允许用户上传个人私有文件可以在企业控制台开启或关闭） 企业项目需要部门成员创建于所在部门的根目录，成员角色需要有“创建文件夹/项目“权限。 项目由项目负责人进行管理（默认为项目创建者），项目负责人可以转交给其他人。 项目可以邀请其他部门成员或外部成员加入 项目的访问权限等同于分享权限。可以在企业控制台——权限管理——文件权限列表中自定义可选的项目访问权限。 所有用户主界面左侧栏有一个“我的项目”栏目，里面有该用户建立及加入的所有项目列表。 项目所在部门拥有“部门文件管理”权限的角色成员都能访问及管理该项目。 外部成员可以通过邮箱或手机号验证的方式（邀请其加入项目所使用的邮箱或手机号）加入项目。 项目内的文件也可以通过“文件访问控制”来精细化控制权限。 项目可以使用转交的方式从个人转交到部门、从部门转交到其他部门。 项目可以设有效期，有效期到期后，除了项目负责人，项目所在部门的管理员、其他项目成员将无法访问项目。 项目下还可以创建多个子项目，子项目可以转为父项目，没有子项目的项目也可以转为其他项目的子项目。 综上，部门和项目的主要区别在于： 部门相对固定，功能强大，仅有部门成员通过角色和访问控制权限访问部门文件，管理更精细。适合长期的组织结构管理。 项目属于某部门或个人，比较灵活，可以跨部门邀请成员甚至邀请外部成员，由项目负责人管理。项目成员权限和文件分享权限一致，使用比较简单。适合以项目为单位管理的项目组使用。 部门成员和项目成员如果不做“文件访问控制”的话，默认都可以访问部门中或项目中的所有文件。 17. 为什么我不能在部门里上传文件？ 你的部门角色没有文件上传权限，你可以联系该部门的部门经理更改你的角色。 你没有该部门下面某个文件夹的文件上传权限，该文件夹做了权限控制。 18. 文件如何排序？ 巴别鸟文件列表中的文件都可以按用户需求进行排序，而且系统会记住该文件夹下上一次用户的排序选择，在下一次打开时使用相同的排序。 文件排序的方式是：点击文件列表顶部最右方的“排序”图标，选择需要的排序方式。 默认的排序方式为“最近版本”，即最新更新的文件在前。还可以选择按名称或按大小排序。 用户也可以自定义全局默认的排序方式，操作方式为：点击头像——设置——账户信息——全局默认排序，在下拉框选择需要的排序方式即可。 置顶文件不受排序影响，永远在最前面。默认的是先排部门，接下来是收件箱，普通文件夹，最后是文件。 有一个文件夹和文件混排的开关按钮，打开此开关的话，排序时，按指定的排序方式，文件和文件夹混在一起排序。" }, { "lang": "zh", "slug": "faq-permissions", "title": "FAQ：权限、部门与项目", "description": "覆盖 权限、部门与项目 相关常见问题。", "category": "常见问题", "top_category": "常见问题", "keywords": [ "FAQ", "FAQ：权限、部门与项目" ], "url": "zh/faq-permissions.html", "source": "content/zh/faq-permissions.md", "summary": "FAQ：权限、部门与项目 以下问题覆盖用户在使用巴别鸟企业网盘时常见的操作、权限、协作和排障场景。 19. 如何使用在线编辑？ 巴别鸟支持office类文档的多人在线编辑，无论是word、excel、ppt还是wps文档都可以在巴别鸟上在线编辑。 使用方法很简单，新建或上传一个office文件，在文件上点击右键，选择在线编辑即可开启在线编辑。 如果不能在线编辑，可能是以下几种情况： 没有在线编辑按钮。请检查你是否有该文件的编辑权限。或者你所使用的巴别鸟账号是否开通了在线编辑授权。 点了在线编辑但没有反应。如果使用浏览器访问巴别鸟，请检查在线编辑窗口是否被浏览器屏蔽，有的浏览器会屏蔽新窗口。通常这类浏览器在地址栏最右端会有新窗口被屏蔽的提示，点击打开即可。 提示文件被锁定。这种情况往往是有用户在用客户端编辑该文档 20. 如何多人协同在线编辑？ 巴别鸟支持office类文档的多人在线编辑，无论是word、excel、ppt还是wps文档都可以在巴别鸟上在线编辑。 新建或上传需要多人编辑的office文档，分享给需要协作的成员（如果是部门文件或项目文件，同时协作者也在相应的部门或项目中，则无需分享，他们就能看到文档），注意要给对方编辑权限。 这时候大家都使用在线编辑就可以进行协同编辑了。 21. 为什么多人编辑的文档下载下来后还是编辑前的版本（老版本）？ 为保证在线编辑文档的完整性，巴别鸟在线编辑有一个系统设定：需要等所有编辑者退出10秒后才保存协同编辑的文档为最新版本。如果在协同编辑的中途退出，而此时还有其他协作者在编辑，那么下载文档的版本就是此次在线编辑前的版本。 所以，如果要", "headings": [ { "level": 1, "title": "FAQ：权限、部门与项目", "id": "faq" }, { "level": 2, "title": "19. 如何使用在线编辑？", "id": "19" }, { "level": 2, "title": "20. 如何多人协同在线编辑？", "id": "20" }, { "level": 2, "title": "21. 为什么多人编辑的文档下载下来后还是编辑前的版本（老版本）？", "id": "21" }, { "level": 2, "title": "22. 文件访问控制如何使用？如何控制某个文件的访问权限？", "id": "22" }, { "level": 2, "title": "23. 如何自定义分享可选权限？", "id": "23" }, { "level": 2, "title": "24. 部门成员的权限如何控制？", "id": "24" }, { "level": 2, "title": "25. 部门文件如何让其他部门的成员看到？", "id": "25" }, { "level": 2, "title": "26. 部门经理如何管理部门？", "id": "26" }, { "level": 2, "title": "27. 如何知道部门文件中有哪些被分享了？", "id": "27" }, { "level": 2, "title": "28. 文件密级（安全级别）是什么？", "id": "28" }, { "level": 2, "title": "29. 如何查看部门的访问日志？", "id": "29" }, { "level": 2, "title": "30. 如何查看部门成员的使用情况？", "id": "30" }, { "level": 2, "title": "31. 审批流程是做什么的？", "id": "31" }, { "level": 2, "title": "32. 上传权限和仅上传权限有什么区别？", "id": "32" }, { "level": 2, "title": "33. 为什么我看不到别人上传的文件？", "id": "33" } ], "images": [], "text": "FAQ：权限、部门与项目 以下问题覆盖用户在使用巴别鸟企业网盘时常见的操作、权限、协作和排障场景。 19. 如何使用在线编辑？ 巴别鸟支持office类文档的多人在线编辑，无论是word、excel、ppt还是wps文档都可以在巴别鸟上在线编辑。 使用方法很简单，新建或上传一个office文件，在文件上点击右键，选择在线编辑即可开启在线编辑。 如果不能在线编辑，可能是以下几种情况： 没有在线编辑按钮。请检查你是否有该文件的编辑权限。或者你所使用的巴别鸟账号是否开通了在线编辑授权。 点了在线编辑但没有反应。如果使用浏览器访问巴别鸟，请检查在线编辑窗口是否被浏览器屏蔽，有的浏览器会屏蔽新窗口。通常这类浏览器在地址栏最右端会有新窗口被屏蔽的提示，点击打开即可。 提示文件被锁定。这种情况往往是有用户在用客户端编辑该文档 20. 如何多人协同在线编辑？ 巴别鸟支持office类文档的多人在线编辑，无论是word、excel、ppt还是wps文档都可以在巴别鸟上在线编辑。 新建或上传需要多人编辑的office文档，分享给需要协作的成员（如果是部门文件或项目文件，同时协作者也在相应的部门或项目中，则无需分享，他们就能看到文档），注意要给对方编辑权限。 这时候大家都使用在线编辑就可以进行协同编辑了。 21. 为什么多人编辑的文档下载下来后还是编辑前的版本（老版本）？ 为保证在线编辑文档的完整性，巴别鸟在线编辑有一个系统设定：需要等所有编辑者退出10秒后才保存协同编辑的文档为最新版本。如果在协同编辑的中途退出，而此时还有其他协作者在编辑，那么下载文档的版本就是此次在线编辑前的版本。 所以，如果要下载最新的版本，需要确保所有协作者都退出并关闭在线编辑界面。（在线编辑界面右上角会显示此刻在编辑的成员ID） 如果在编辑过程中想保存最新的版本，也可以直接在在线编辑界面点击文件——下载为——选择想下载的格式下载。这种方式下载的就是当前最新版本。（需要下载者有该文件的下载权限） 巴别鸟的在线编辑权限和下载权限是可以分开的，以实现部分用户需要能在线编辑但不允许下载的特殊需求。 22. 文件访问控制如何使用？如何控制某个文件的访问权限？ 巴别鸟的项目文件/文件夹和部门文件/文件夹可以开启文件访问控制，以限定特定的项目成员或部门成员对该文件/文件夹的访问行为。 文件访问控制仅针对部门内成员。如需要其他部门的人员访问该文件，请使用分享功能。 文件访问控制的优先级高于成员的部门角色权限或项目成员权限。譬如：某成员对部门某个文件拥有编辑权限，但如果通过该文件的文件访问控制把该成员对这个文件的权限设置为只读，那么这个成员对这个文件就只有只读权限。 文件访问控制对文件夹也有效，如果设定了某个文件夹的文件访问控制，被设定访问控制的成员对该文件夹的所有文件包括子文件夹也都会跟随文件访问控制设置的权限。 在项目文件（文件夹）和部门文件（文件夹）上点击右键，选择“文件访问控制”即可开启该文件的文件访问控制。文件访问控制界面里有可以访问该文件的成员列表，给特定成员选择想要控制的权限即可。你也可以设置访问控制的有效期，超过有效期访问控制失效。 同时，部门文件也可以通过文件访问控制设定某个角色对特定文件（文件夹）的访问权限，在部门文件（文件夹）上右键点击“文件访问控制”在文件访问控制界面顶部选择“角色权限设置”栏目，即可设定针对某个角色的文件访问控制。 23. 如何自定义分享可选权限？ 巴别鸟有两套权限体系可以互相配合使用，一个是决定部门内使用权限的“角色权限”、一个是用于分享、项目、文件权限控制的“文件权限” 无论是“角色权限”还是“文件权限”都可以在后台自定义，可选择具体的权限类型及权限名称。 在企业控制台——权限管理中统一管理和自定义。在权限管理栏目选择”部门权限列表“就可以管理角色权限，选择”文件权限列表“则可以管理文件权限。 在文件权限列表里自定义的权限就对应着文件分享时的可选权限。（同时，项目成员权限和文件权限控制的权限也通用） 譬如：在文件权限列表中点击“自定义权限”按钮，新建一个权限，命名为“实习生”然后勾选想赋予实习生的具体权限（如：预览、上传、下载），点击确定后，文件权限列表会新增一个叫“实习生”的权限。同时在文件分享、项目增加成员、文件权限控制时，下拉权限选择框里也会有“实习生”这个权限可以选择。 24. 部门成员的权限如何控制？ 在成员管理里更换该成员的角色，就可以改变该成员的权限。 如果要控制特定文件（文件夹）的访问权限，在文件（文件夹）上点击右键选择“文件访问控制”然后找到想控制权限的成员，下拉选择给他的权限即可。 25. 部门文件如何让其他部门的成员看到？ 使用分享功能邀请其他部门成员访问该文件（文件夹）。在想给其他部门成员查看的文件（文件夹）上点击右键，选择分享——在邀请共享人处选择想分享的成员（或输入成员账号或邮箱），下拉选择给他访问该文件（文件夹）的权限——点击发送。发送成功后，被邀请者能收到邀请通知，同时在被邀请者巴别鸟左侧栏“我加入的分享”栏目中也可以看到该文件（文件夹）。 26. 部门经理如何管理部门？ 在企业文件栏目找到该部门文件夹，右键点击选择“部门管理”即可打开部门管理界面。（只有角色权限有“部门文件管理“权限的人才能看到“部门管理”选项） 27. 如何知道部门文件中有哪些被分享了？ 部门经理（角色权限有“部门文件管理“权限的人）右键点击部门文件夹选择“部门管理”，在部门管理中找到“部门分享文件统计”点击“打开分享文件列表”就可以查看部门所有被分享的文件列表。 也可以点击路径上的蓝色按钮通过快速菜单打开： 28. 文件密级（安全级别）是什么？ 巴别鸟的部门文件可以设置文件密级（安全级别），系统根据文件的安全级别限定文件的使用范围、分享方式和权限。适合对安全要求比较高的文件进行设置。 巴别鸟的文件安全级别分为公开文件、内部文件、限制文件、保密文件四档。默认的文件都是公开文件。在文件上右键——更多选项——安全级别中可以更改文件的安全级别。 不同安全级别文件的处理方式如下： 保密文件，默认除了创建者、项目负责人、文件负责人和部门经理外部门内其他人不可见，分享该文件必须获得安全保密员授权 限制文件，一般人员只读，分享该文件必须获得上级主管授权 内部文件，分享该文件给部门外人员，必须获得上级主管授权 以上三种文件，不支持链接分享仅支持邀请分享 保密文件，限制文件，一般人员不能移动/复制/上传新版本/下载/重命名/查看版本，上级主管和有部门文件管理权限的人员才可以 29. 如何查看部门的访问日志？ 部门管理员（具有“部门文件管理”权限的角色）可以查看整个部门的文件访问日志，有如下两种查看方式。 打开部门文件夹，在部门文件夹顶部路径栏（面包屑）部门名字前有一个蓝色的小图标，点击该图标选择文件访问统计，在弹出窗口顶部选择“访问日志”。 在企业文件根目录找到部门文件夹，右键，选择部门管理，找到部门文件使用管理——文件访问统计,点击“打开文件访问日志” 访问日志右上角有“导出报表”按钮，可以把日志导出为excel文件。 30. 如何查看部门成员的使用情况？ 部门管理员（具有“部门文件管理”权限的角色）可以查看整个部门成员使用网盘的情况，有如下两种查看方式。 打开部门文件夹，在部门文件夹顶部路径栏（面包屑）部门名字前有一个蓝色的小图标,点击该图标选择文件访问统计。 在企业文件根目录找到部门文件夹，右键，选择部门管理，找到部门文件使用管理——成员使用情况,点击“打开使用情况” 31. 审批流程是做什么的？ 巴别鸟支持文件的审批，审批的最终目的是让文件定稿。文件审批的流程可以在企业控制台——文件配置——审批管理里添加配置，成为预制审批流程。有部门文件管理权限的部门角色也可以在部门管理栏目中设置部门成员发起审批时使用的审批流程，有4种设置方式：可自由定义审批流程（部门成员开启审批时可自定义审批的流程的审批人）、可选全部预制审批流程（部门成员开启审批时可选择在管理后台中预设所有的审批流程）、限用特定审批流程（在管理后台预设流程中选择几个作为部门使用的审批流程）、与父部门限制相同（使用上一级部门所使用的审批流程设置）。巴别鸟文件审批有如下特性： 部门成员都可以发起审批，在要审批的文件上右键——更多选项——开启审批即可。 定稿的审批文件可以导出审批报表。在左侧栏“我的审批”栏目可以管理审批。 通过审批的文件状态会变为“定稿”，定稿文件可以更新版本成为“待启动”状态，可以再次开启审批。 选中多个文件右键选择开启审批即可以多文件同时审批。 允许邀请外部成员来审批文件，在填写审批人时输入外部成员的邮箱或手机号即可。 32. 上传权限和仅上传权限有什么区别？ 上传除了上传新文件外还意味着你可以上传一个新版本覆盖原来的文件。巴别鸟的“覆盖”并不会破坏旧文件，而是在旧文件中增加一个新版本作为当前版本。所以上传权限包含了上传新版本权限。 在巴别鸟的权限体系中，上传文件包含了给别人文件上传新版本的含义。譬如一个由别人建立的分享，给了你上传权限就意味着除了上传文件外你也可以给别人的文件上传新版本（编辑）。 仅上传权限的含义是，仅上传自己的文件，这意味着，你可以上传新文件，给自己的文件上传新版本，但对别人上传的文件是没有上传新版本的权限的（你无法编辑别人的文件）。 33. 为什么我看不到别人上传的文件？ 你的部门角色没有查看别人上传文件的权限，你可以联系部门经理更改你的角色。" }, { "lang": "zh", "slug": "faq-sharing", "title": "FAQ：分享、协作与通知", "description": "覆盖 分享、协作与通知 相关常见问题。", "category": "常见问题", "top_category": "常见问题", "keywords": [ "FAQ", "FAQ：分享、协作与通知" ], "url": "zh/faq-sharing.html", "source": "content/zh/faq-sharing.md", "summary": "FAQ：分享、协作与通知 以下问题覆盖用户在使用巴别鸟企业网盘时常见的操作、权限、协作和排障场景。 34. 我如何分享一个文件给其他人？ 只要具有分享权限的文件，都可以进行分享。在需要分享的文件上点击鼠标右键，选择“分享”，即可进行分享，也可以鼠标经文件/文件夹的时候点击分享的快捷方式进行分享。 没有分享权限的文件会弹出授权窗口，你可以按窗口指引进行操作提交分享申请，有文件管理权限的成员或管理员或文件创建者或文件负责人批准后，该分享会自动发送给被邀请人或打开申请的文件的链接分享。 35. 我如何查看其他人分享给我的文件？ 在巴别鸟左侧栏有“我加入的分享”栏目，你在登录状态下加入其他人的分享在该栏目中都可以统一显示。同理，点击“我的分享”栏目也可以查看所有你开启分享的文件。 36. 邀请分享和链接分享有什么区别？ 巴别鸟的分享有两种形式，邀请分享及链接分享。它们的区别在于： 邀请分享必须确定分享对象，你需要拥有分享目标的邮箱或手机号才能进行分享 对于未注册巴别鸟而收到邀请分享的人需要进行身份验证才能访问邀请他的文件/文件夹。身份验证是使用收到邀请的邮箱或手机号（私有部署需要开通短信接口）收取验证码后验证才可以访问 邀请发起者可以自由设定被邀请者访问的权限及有效期，并查看访问日志 邀请发起者可以关闭某一个被邀请者查看分享内容的权限以中断分享 链接分享不需要身份验证，但可以设定分享密码 收到链接分享的任何人都可以打开该分享并查看文件（支持匿名） 链接分享设置不允许匿名访问时，匿名用户不能访问该链接 链接分享需要复制分享link发送给想要分享的人 如果关闭链接分享，所有拥有该链接的人也", "headings": [ { "level": 1, "title": "FAQ：分享、协作与通知", "id": "faq" }, { "level": 2, "title": "34. 我如何分享一个文件给其他人？", "id": "34" }, { "level": 2, "title": "35. 我如何查看其他人分享给我的文件？", "id": "35" }, { "level": 2, "title": "36. 邀请分享和链接分享有什么区别？", "id": "36" }, { "level": 2, "title": "37. 如何修改我的默认头像？", "id": "37" }, { "level": 2, "title": "38. 我想在同事更新文件后就收到提示通知，怎么操作？", "id": "38" }, { "level": 2, "title": "39. 有的文件或文件夹图标后面有个「控」的角标，是什么意思？", "id": "39" }, { "level": 2, "title": "40. 为什么我新上传的文件搜索不到？", "id": "40" }, { "level": 2, "title": "41. 为什么文件夹在文件列表中不显示大小？", "id": "41" }, { "level": 2, "title": "42. 为什么我上传的文件夹不能覆盖同名文件夹，而文件可以？", "id": "42" }, { "level": 2, "title": "43. 为什么我的文件会提示被锁定？", "id": "43" }, { "level": 2, "title": "44. 如何解锁被锁定的文件？", "id": "44" }, { "level": 2, "title": "45. 如何回滚文件版本？", "id": "45" }, { "level": 2, "title": "46. 动态是什么？", "id": "46" }, { "level": 2, "title": "47. 可以搜索动态么？", "id": "47" }, { "level": 2, "title": "48. 讨论组是什么？", "id": "48" }, { "level": 2, "title": "49. 工作台是什么？如何使用工作台？", "id": "49" }, { "level": 2, "title": "50. 我不想被太多的动态信息骚扰，该怎么办？", "id": "50" } ], "images": [], "text": "FAQ：分享、协作与通知 以下问题覆盖用户在使用巴别鸟企业网盘时常见的操作、权限、协作和排障场景。 34. 我如何分享一个文件给其他人？ 只要具有分享权限的文件，都可以进行分享。在需要分享的文件上点击鼠标右键，选择“分享”，即可进行分享，也可以鼠标经文件/文件夹的时候点击分享的快捷方式进行分享。 没有分享权限的文件会弹出授权窗口，你可以按窗口指引进行操作提交分享申请，有文件管理权限的成员或管理员或文件创建者或文件负责人批准后，该分享会自动发送给被邀请人或打开申请的文件的链接分享。 35. 我如何查看其他人分享给我的文件？ 在巴别鸟左侧栏有“我加入的分享”栏目，你在登录状态下加入其他人的分享在该栏目中都可以统一显示。同理，点击“我的分享”栏目也可以查看所有你开启分享的文件。 36. 邀请分享和链接分享有什么区别？ 巴别鸟的分享有两种形式，邀请分享及链接分享。它们的区别在于： 邀请分享必须确定分享对象，你需要拥有分享目标的邮箱或手机号才能进行分享 对于未注册巴别鸟而收到邀请分享的人需要进行身份验证才能访问邀请他的文件/文件夹。身份验证是使用收到邀请的邮箱或手机号（私有部署需要开通短信接口）收取验证码后验证才可以访问 邀请发起者可以自由设定被邀请者访问的权限及有效期，并查看访问日志 邀请发起者可以关闭某一个被邀请者查看分享内容的权限以中断分享 链接分享不需要身份验证，但可以设定分享密码 收到链接分享的任何人都可以打开该分享并查看文件（支持匿名） 链接分享设置不允许匿名访问时，匿名用户不能访问该链接 链接分享需要复制分享link发送给想要分享的人 如果关闭链接分享，所有拥有该链接的人也都不能访问 如果改变链接分享的权限，所有拥有该链接的人的权限也会同时改变 37. 如何修改我的默认头像？ 要修改默认头像可以点击右上角头像图标，在下拉菜单中点击设置。 在设置里点击修改头像按钮，就可以上传自己想修改的头像了。 在手机APP上，可以点击底部栏“我的”，点击顶部头像，点击“头像”栏目进行修改。 38. 我想在同事更新文件后就收到提示通知，怎么操作？ 巴别鸟可以在文件更新时发送更新通知给相关成员，为了防止通知信息过多造成骚扰，只有用户关注的文件才会向用户发送更新通知。 在你需要更新后就让你知道的文件下方点击提醒关注，选择你自己作为关注方。 在提醒关注列表里选择自己，确定生效。 以后只要同事更新这个文件或文件夹，你就能收到铃铛通知。 39. 有的文件或文件夹图标后面有个「控」的角标，是什么意思？ 说明该文件做过“文件访问控制”，对文件的操作权限可能和角色的默认权限有差别。 40. 为什么我新上传的文件搜索不到？ 巴别鸟支持全文搜索，但是需要时间和服务器资源对搜索目标进行索引。为了节约服务器效能，巴别鸟搜索引擎会每隔30分钟进行一次文件索引。所以新上传的文件要在搜索引擎中搜索出来最长需要等待30分钟。 一些文件里的文字是以图形或图片的形式嵌入到文档中的（如PDF扫描件）这类文件内容目前还无法搜索到。 41. 为什么文件夹在文件列表中不显示大小？ 文件夹的结构不可控，可能文件夹层级比较复杂，文件数量众多。要统计海量文件夹的大小会大大浪费服务器的资源并造成加载文件列表缓慢。所以文件夹在列表中不显示大小（其实windows系统资源管理器出于同样的考虑也不显示文件夹大小的）。要查询文件夹大小右键点击“查看详情”，在详情页面可以统计该文件夹大小。 42. 为什么我上传的文件夹不能覆盖同名文件夹，而文件可以？ 巴别鸟上传同名文件会提示是生成原文件的新版本还是更名上传。在同步端或者映射盘里对文件进行修改后，该文件会作为新版本自动上传。但是巴别鸟不支持上传同名文件夹进行覆盖或是生成目标文件夹内文件的新版本。所以用巴别鸟上传同名文件夹会自动给文件夹名增加后缀以作为区分。这是为了增加服务器效率而做的设置，因为文件夹理论上可以有无限多的层级，如果上传一个结构相当复杂的文件夹有可能造成系统卡死。目前主流企业网盘均不支持文件夹上传覆盖。 43. 为什么我的文件会提示被锁定？ 使用巴别鸟客户端编辑文档时，文档会自动锁定，防止其他协作用户同时编辑造成版本冲突。如果你的文件上有加锁标志，意味着该文件有人正在编辑并锁定了。使用在线office编辑模块不会锁定文件。锁定的文件在编辑者完成编辑后30分钟内没有内容更新会自动解锁。也可以手动解锁。 44. 如何解锁被锁定的文件？ 使用巴别鸟客户端编辑文档时，文档会自动锁定，防止其他协作用户同时编辑造成版本冲突。如果你的文件上有加锁标志，意味着该文件有人正在编辑并锁定了。只有文件编辑者及拥有文件管理权限的人（如：部门经理）可以手动解锁已锁定的文件，有解锁权限的人右键点击锁定的文件，选择“解锁文件”即可。 45. 如何回滚文件版本？ 巴别鸟支持文件的历史版本管理及回滚，文件图标右下角有版本标记的文件意味着有多个版本，右键点击文件，菜单中打开“查看版本”就可以查看文件的版本信息。点击版本信息内的文件图标或缩略图可以预览文件的该版本。点击“设为当前版本”按钮，就可以把历史版本回滚为当前版本。回滚操作后，所有要访问该文件的人打开的都是该文件的当前版本。 46. 动态是什么？ 动态是巴别鸟中一个用于展示和使用者相关的文件及部门更新内容的流式列表。使用动态可以直观的了解整个企业中和你相关的成员、文件、部门、项目都发生了什么。 动态信息包括文件的上传、下载、更新、删除等信息；文件的批注、讨论内容；其他成员@你的信息。 动态内的批注和讨论信息可以直接在动态列表中回复。 动态信息通常保存三个月。 47. 可以搜索动态么？ 动态栏目顶部右侧的搜索框为动态搜索框，可以搜索动态的内容。 48. 讨论组是什么？ 讨论组相当于以部门及项目为单位组织的群聊，每个项目或部门、团队（专业版）都拥有自己的讨论组，可以在讨论组输入文字进行群聊。 每创建一个部门或项目都会自动创建一个讨论组。 加入项目或部门的成员自动加入该项目或部门的讨论组。 可以在讨论组栏目中查看所有你加入的讨论组。 讨论组支持发送文件。 49. 工作台是什么？如何使用工作台？ 工作台是巴别鸟中的一个栏目，里面以卡片形式组织展示用户感兴趣的栏目和文件列表，工作台的展示内容可以自定义，合理利用工作台可以作为从更多维度查看文件和管理工作的入口。 工作台可以自定义，每个用户都可以根据自己的需要自定义专属的工作台。 工作台的卡片可以拖动排序，鼠标在卡片顶部长按拖动，就可以按需要排序卡片。 如果觉得卡片的内容展示不够，可以点击卡片右上方更多图标（三个点），选择“更多”选项，就会在新窗口打开卡片的更多内容。 卡片可以删除，点击卡片右上方更多图标（三个点），选择“移除卡片”选项，即可移除卡片。卡片移除并不影响卡片所展现的数据。 点击添加卡片按钮可以根据需要添加更多卡片。 有17种卡片图表类型可选，也可以自定义某个文件夹作为卡片在工作台中访问。 50. 我不想被太多的动态信息骚扰，该怎么办？ 开启客户端时，动态信息会以弹窗形式出现在右下角，如果需要关闭不想收到的动态信息，可以点击头像—设置—通知设置，在动态通知设置里进行设定，选择你想接收的动态通知类型。" }, { "lang": "zh", "slug": "faq-sync", "title": "FAQ：同步、客户端与映射盘", "description": "覆盖 同步、客户端与映射盘 相关常见问题。", "category": "常见问题", "top_category": "常见问题", "keywords": [ "FAQ", "FAQ：同步、客户端与映射盘" ], "url": "zh/faq-sync.html", "source": "content/zh/faq-sync.md", "summary": "FAQ：同步、客户端与映射盘 以下问题覆盖用户在使用巴别鸟企业网盘时常见的操作、权限、协作和排障场景。 51. 映射盘是什么？和同步有什么区别？ 安装巴别鸟客户端后，在资源管理器中会有一个巴别鸟映射盘，点击后可以访问你权限范围内能访问的所有文件。映射盘内的文件内容其实不在你的电脑上，是通过网络映射到你电脑上的。使用这些文件还是需要下载。映射盘的好处是不占用你电脑本地的存储空间，只有你用到的文件需要下载缓存。同时缺点就是，映射盘需要接入网络才能使用，由于里面的文件都在云端，你看到的文件图标只是云端文件的快捷方式，所以不支持拖动映射盘文件到本地磁盘目录。 安装客户端后，如果你选择一个本地磁盘中的文件夹，右键点击，选择巴别鸟，再选择同步到巴别鸟。这个时候你就建立了一个同步文件夹。同步文件夹中的内容都会自动同步到云端，如果云端的内容有更新（其他人同步了这个文件夹到他的电脑，并上传了文件），你这个文件夹内的内容也会更新。同步的好处是，文件同步后都下载到了本地，可以直接进行各种操作，没有网络也可以使用及访问同步文件夹，如果接入网络也会自动同步更新的内容。同步的缺点是，同步需要占用本地硬盘空间，同时由于文件需要下载更新，所以同步的实时性不如映射盘。 52. 为什么我无法同步新增加的文件或者没有同步最新的文件版本？ 你同步的应该是部门内的文件，有几种可能： 你在同步的文件夹里没有文件上传权限 你要同步的文件在一个你在本地新建的文件夹里，而你没有新建文件夹权限 你要同步的文件被设置成了不需要同步的文件类型 你要同步的文件类型在文件黑名单里，不允许上传 你要同步的文件大小超过了单个文件可上传的最大", "headings": [ { "level": 1, "title": "FAQ：同步、客户端与映射盘", "id": "faq" }, { "level": 2, "title": "51. 映射盘是什么？和同步有什么区别？", "id": "51" }, { "level": 2, "title": "52. 为什么我无法同步新增加的文件或者没有同步最新的文件版本？", "id": "52" }, { "level": 2, "title": "53. 为什么我同步时提示有几个文件同步不成功？", "id": "53" }, { "level": 2, "title": "54. 和同步有关的权限有哪些？", "id": "54" }, { "level": 2, "title": "55. 同步文件时我本地删除了某个文件，云端还会有么？", "id": "55" }, { "level": 2, "title": "56. 同步时，我云端删除了某个文件，本地还会有么？", "id": "56" }, { "level": 2, "title": "57. 我们部门几个人可以同时同步某一个文件夹么？", "id": "57" }, { "level": 2, "title": "58. 我映射盘上删除一个文件，云端还会有么？", "id": "58" }, { "level": 2, "title": "59. 为什么我映射盘上的文件无法拖入到微信发送？", "id": "59" }, { "level": 2, "title": "60. 为什么我找不到我的映射盘了？", "id": "60" }, { "level": 2, "title": "61. 为什么我同步的文件夹里有一些文件能同步，而有一些不能？", "id": "61" }, { "level": 2, "title": "62. 为什么部门里有的文件我可以编辑，有的不可以？", "id": "62" }, { "level": 2, "title": "63. 我是超级管理员，为什么我看不到一些部门的动态？", "id": "63" }, { "level": 2, "title": "64. 我是超级管理员，为什么我清空回收站后文件又会出现在回收站？", "id": "64" } ], "images": [], "text": "FAQ：同步、客户端与映射盘 以下问题覆盖用户在使用巴别鸟企业网盘时常见的操作、权限、协作和排障场景。 51. 映射盘是什么？和同步有什么区别？ 安装巴别鸟客户端后，在资源管理器中会有一个巴别鸟映射盘，点击后可以访问你权限范围内能访问的所有文件。映射盘内的文件内容其实不在你的电脑上，是通过网络映射到你电脑上的。使用这些文件还是需要下载。映射盘的好处是不占用你电脑本地的存储空间，只有你用到的文件需要下载缓存。同时缺点就是，映射盘需要接入网络才能使用，由于里面的文件都在云端，你看到的文件图标只是云端文件的快捷方式，所以不支持拖动映射盘文件到本地磁盘目录。 安装客户端后，如果你选择一个本地磁盘中的文件夹，右键点击，选择巴别鸟，再选择同步到巴别鸟。这个时候你就建立了一个同步文件夹。同步文件夹中的内容都会自动同步到云端，如果云端的内容有更新（其他人同步了这个文件夹到他的电脑，并上传了文件），你这个文件夹内的内容也会更新。同步的好处是，文件同步后都下载到了本地，可以直接进行各种操作，没有网络也可以使用及访问同步文件夹，如果接入网络也会自动同步更新的内容。同步的缺点是，同步需要占用本地硬盘空间，同时由于文件需要下载更新，所以同步的实时性不如映射盘。 52. 为什么我无法同步新增加的文件或者没有同步最新的文件版本？ 你同步的应该是部门内的文件，有几种可能： 你在同步的文件夹里没有文件上传权限 你要同步的文件在一个你在本地新建的文件夹里，而你没有新建文件夹权限 你要同步的文件被设置成了不需要同步的文件类型 你要同步的文件类型在文件黑名单里，不允许上传 你要同步的文件大小超过了单个文件可上传的最大限制 你要同步的文件总大小超过了部门空间限制 你要同步的文件是巴别鸟禁止同步的文件类型，如以tmp，swp，lock为后缀的文件。 如果确定都不是以上原因引起的，可以逐条尝试以下解决方法： 重命名没有更新的的文件，同步成功后再改回原来名字。 把没有同步的文件移动出同步文件夹，等同步状态显示已同步再移入。 在同步管理找到同步的项目，右键点击，重置同步。 重启客户端 如都不能解决请联系我们客服人员 53. 为什么我同步时提示有几个文件同步不成功？ 同步很多文件时，偶尔会有一些文件提示“无法成功同步”，一般不能成功同步的文件为以下几类： 该文件的文件名有特殊字符或不规范。巴别鸟为了同时兼容MAC、Linux、Windows的文件系统，文件名规则需要这些系统都兼容。这就导致文件名中包含特殊字符、中文顿号等字符的文件无法进行同步。解决方法：修改需要同步文件的文件名。 该文件损坏或者哈希校验无法通过。巴别鸟有秒传模块，文件上传时会分析文件的哈希码，因为损坏，格式等原因，一些文件的哈希码无法读取，造成同步失败。解决方法：重新编辑或导出文件或将文件打成zip包上传。 文件过大。巴别鸟能稳定支持最大8G的单个文件的上传，超过这个大小的文件上传时无法保证100%的成功率。解决方法：改小文件或多次重试同步。 文件被某些应用程序占用了。一些时候，某些应用程序会限制文件被读取或者被复制，这样会导致同步失败。解决方案：重启操作系统再同步，或者找到开启该文件的应用程序并关闭。 文件在写入过程中。文件在写入过程中也可能导致同步失败。解决方法：等文件保存完成后再进行同步或上传。 文件在其他网络驱动器上。同步不在本地的文件，很容易引起网络出错造成同步失败或同步无响应。解决方法：copy文件或文件夹到本地磁盘再进行同步。 使用VPN翻墙或网络问题。VPN翻墙容易导致电脑本机时钟异常，时钟异常会导致同步失败或出现未知问题。解决方法：时钟和服务器时间不符时，请调整电脑上的时间和时区，使用服务器所在时区的时间。如不是时钟问题，有可能是VPN造成的网络异常，关闭VPN后断开网络连接再开启尝试（关闭网卡或wifi再开启）。 54. 和同步有关的权限有哪些？ 如果你在一个部门，想同步部门文件中的某一个文件夹，和同步相关的权限有： 上传文件（同步上传本地文件） 下载自己的文件 下载别人的文件 移动自己的文件 移动别人的文件 删除自己的文件 删除别人的文件 创建文件夹 只有角色拥有以上权限的人才能进行完全的同步。缺少某个权限就缺少同步时的某个操作。 同时，如果同步的文件夹被设置过“文件访问控制“，以文件访问控制中的设置为准。 55. 同步文件时我本地删除了某个文件，云端还会有么？ 如果你在云端同步文件夹中有完整的编辑权限（上传下载删除），你在本地删除了某个文件或移动了某个文件到同步文件夹外，云端同步文件夹里的对应文件也会被删除。 但是这个删除的文件会在巴别鸟的回收站里，可以在回收站找到并进行恢复操作。 56. 同步时，我云端删除了某个文件，本地还会有么？ 如果你在云端同步文件夹中有完整的编辑权限（上传下载删除），你在云端删除了某个文件或移动了某个文件到同步文件夹外，本地同步文件夹里的对应文件也会被删除。 但是这个删除的文件会在巴别鸟的回收站里，可以进行恢复操作。 57. 我们部门几个人可以同时同步某一个文件夹么？ 可以，巴别鸟支持多人同步同一个云端文件夹。同时，如果同步同一个文件夹的多个用户拥有同样的权限，那么在几个用户的本地同步文件夹中的文件将会一致。 58. 我映射盘上删除一个文件，云端还会有么？ 如果你有删除文件的权限，你在映射盘中删除了一个文件，云端会实时删除。但回收站里会有。 如果你没有删除文件的权限，系统会提示你没有删除权限。 59. 为什么我映射盘上的文件无法拖入到微信发送？ windows映射盘中，由于资源管理器限制，只有缓存完成的文件可以拖动。 Mac映射盘中，没有缓存的文件也可以拖入到微信，自动缓存并发送。但是由于微信的窗口捕获没有做对网络文件拖拽的支持，如果文件超过10MB的微信文件发送限制，大概率会出现不可预知问题（窗口死锁）。这个在Mac微信不做支持的前提下很难解决，也是微信的一个Bug。苹果iCloud就干脆不支持拖动没有缓存的文件到微信来回避这个问题。 60. 为什么我找不到我的映射盘了？ 映射盘因为需要获取操作系统的底层权限容易被操作系统限制从而访问不了。目前的版本已经很好的解决了这个问题，但是在个别杀毒软件或操作系统下还是会出现找不到映射盘，映射盘内文件图标显示错误等问题。 解决方法：把巴别鸟客户端放入防火墙或杀毒软件白名单，卸载并用操作系统管理员权限重装巴别鸟客户端，按提示操作并在杀毒软件或防火墙阻止时给予放行。 61. 为什么我同步的文件夹里有一些文件能同步，而有一些不能？ 同步文件夹一些文件不能同步一般有以下几种可能： 你没有这些文件的下载权限，无法将这些文件同步到本地（下载自己的文件、下载别人的文件两个权限） 你没有同步文件夹或同步文件夹中某些文件夹的上传权限，无法将编辑内容及新增文件同步到云端 你在部门中没有“创建文件夹”权限，你要同步的本地文件夹中有新创建的文件夹 你同步的文件大小超过了单个文件上传大小限制（单个文件大小限制请咨询管理员或巴别鸟客服） 有些文件类型被设置成了不需要同步的文件类型 有些文件类型在文件黑名单里，不允许上传 如果确定都不是以上原因引起的，可以逐条尝试以下解决方法： 重命名没有更新的的文件，同步成功后再改回原来名字。 把没有同步的文件移动出同步文件夹，等同步状态显示已同步再移入。 在同步管理找到同步的项目，右键点击，重置同步。 重启客户端 如都不能解决请联系我们客服人员 62. 为什么部门里有的文件我可以编辑，有的不可以？ 你没有编辑该文件的权限，有可能是你在部门的角色没有“编辑别人的文件”的权限，而这个文件的创建者不是你。或者该文件做了文件权限控制禁止编辑。文件在锁定状态下也无法编辑。如果开启了“文件负责人”模式，非负责人无法编辑文件。 63. 我是超级管理员，为什么我看不到一些部门的动态？ 超级管理员因为管理所需可以看到整个公司的部门文件夹，但是超级管理员看不到他没有加入的部门的动态。为了防止大量信息骚扰，巴别鸟设定为只推送成员所在部门、项目、分享中的动态。如果超级管理员想看到某个部门的动态，可以把自己加入该部门中。 64. 我是超级管理员，为什么我清空回收站后文件又会出现在回收站？ 巴别鸟的回收站是多级回收站，为了方便管理，统一在前台“回收站”中管理。多级回收站的设定是，部门成员删除的部门文件，在部门经理和超级管理员的回收站里也可以看到。部门经理删除的部门文件，在超级管理员的回收站里同样存在。这个机制可以最大限度的避免“删库跑路”的恶性事件。但因为超级管理员在部门中也有相应的角色，甚至可能同时是某部门的项目经理，这就会造成一个现象：超级管理员清空了回收站（作为部门成员或部门经理），文件消失了，但再次刷新，回收站里依然会有这些文件（作为超级管理员看到的）。所以超级管理员要彻底删除一个部门文件需要操作两次。这个设定的确有点体验不佳，我们也注意到这个问题，会在以后的迭代中修正。" }, { "lang": "zh", "slug": "faq-projects", "title": "FAQ：部门管理、项目和收集文件", "description": "覆盖 部门管理、项目和收集文件 相关常见问题。", "category": "常见问题", "top_category": "常见问题", "keywords": [ "FAQ", "FAQ：部门管理、项目和收集文件" ], "url": "zh/faq-projects.html", "source": "content/zh/faq-projects.md", "summary": "FAQ：部门管理、项目和收集文件 以下问题覆盖用户在使用巴别鸟企业网盘时常见的操作、权限、协作和排障场景。 65. 部门经理如何添加新成员？ 部门经理新增成员有两种方式： 部门经理可以从现有的企业成员中选择一部分成员加入其管理的部门。操作方式如下： 在你管理的部门文件夹上右键点击，选择部门管理界面中的“管理部门成员”。 在部门成员管理界面选择“从内部成员添加”按钮 在弹出窗口选择需要加入部门的成员，注意选择加入成员的部门角色。点击确定后，所选成员就自动加入了这个部门。加入部门的成员也会收到一个邮件通知。 如果部门经理拥有“增加企业成员”权限，部门管理可以在部门成员管理界面中新增企业成员。该操作会新增一名企业成员（占用企业成员授权数）到该部门，具体操作如下： 在你管理的部门文件夹上右键点击，选择部门管理界面中的“管理部门成员” 在部门成员管理界面选择“新增成员”按钮，然后填入计划增加的新成员邮箱、手机号等信息。点击确定后，系统会向该成员的邮箱中发送一封邀请邮件或发送一条手机短信，按邮件或短信的引导登录修改密码后就能使用。 66. 部门经理怎么改变部门成员的权限？ 部门经理可以改变任意部门成员的角色（权限集合），角色由超级管理员统一设定，各部门的部门经理都可以从企业控制台的预设角色里为自己的部门成员选择相应的角色，部门经理无法新建角色。如需要新建特别的角色权限，需要联系超级管理员，由超级管理员在企业控制台中新增角色。 部门经理可以通过角色权限查询来了解各个预设角色的具体权限，从而决定分配什么角色给部门成员。通常，部门成员使用默认的“部门成员”角色就能满足大部分需求。 改变部门成员的", "headings": [ { "level": 1, "title": "FAQ：部门管理、项目和收集文件", "id": "faq" }, { "level": 2, "title": "65. 部门经理如何添加新成员？", "id": "65" }, { "level": 2, "title": "66. 部门经理怎么改变部门成员的权限？", "id": "66" }, { "level": 2, "title": "67. 部门经理如何查看部门有哪些文件被分享了？", "id": "67" }, { "level": 2, "title": "68. 部门里面有个文件/文件夹不想给一些人看到，怎么操作？", "id": "68" }, { "level": 2, "title": "69. 我想让我们部门的人只能在部门的电脑上使用巴别鸟，怎么操作？", "id": "69" }, { "level": 2, "title": "70. 巴别鸟是否支持一个用户在多个部门？", "id": "70" }, { "level": 2, "title": "71. 临时建立一个项目组，需要从公司各个部门抽调人员并共享文件，怎么操作？", "id": "71" }, { "level": 2, "title": "72. 为什么我不能在部门里创建项目？", "id": "72" }, { "level": 2, "title": "73. 部门里有个文件想给其他部门的人一起看，但不想一个个邀请，该怎么操作？", "id": "73" }, { "level": 2, "title": "74. 我想收集各个部门的一些材料，怎么操作？", "id": "74" }, { "level": 2, "title": "75. 我想发个文件给全公司所有人，让他们都能查看，但不能下载，怎么操作？", "id": "75" }, { "level": 2, "title": "76. 如何使用巴别鸟快速收集用户的文件？", "id": "76" }, { "level": 2, "title": "77. 我发给客户的分享里的内容不对，该怎么办？", "id": "77" }, { "level": 2, "title": "78. 我不想让客户下载我分享的文件，但是能看，怎么操作？", "id": "78" }, { "level": 2, "title": "79. 我想把巴别鸟上的文件在微信里发给联系人，怎么操作？", "id": "79" }, { "level": 2, "title": "80. 我使用企业微信/钉钉可以直接访问巴别鸟的文件么？", "id": "80" } ], "images": [], "text": "FAQ：部门管理、项目和收集文件 以下问题覆盖用户在使用巴别鸟企业网盘时常见的操作、权限、协作和排障场景。 65. 部门经理如何添加新成员？ 部门经理新增成员有两种方式： 部门经理可以从现有的企业成员中选择一部分成员加入其管理的部门。操作方式如下： 在你管理的部门文件夹上右键点击，选择部门管理界面中的“管理部门成员”。 在部门成员管理界面选择“从内部成员添加”按钮 在弹出窗口选择需要加入部门的成员，注意选择加入成员的部门角色。点击确定后，所选成员就自动加入了这个部门。加入部门的成员也会收到一个邮件通知。 如果部门经理拥有“增加企业成员”权限，部门管理可以在部门成员管理界面中新增企业成员。该操作会新增一名企业成员（占用企业成员授权数）到该部门，具体操作如下： 在你管理的部门文件夹上右键点击，选择部门管理界面中的“管理部门成员” 在部门成员管理界面选择“新增成员”按钮，然后填入计划增加的新成员邮箱、手机号等信息。点击确定后，系统会向该成员的邮箱中发送一封邀请邮件或发送一条手机短信，按邮件或短信的引导登录修改密码后就能使用。 66. 部门经理怎么改变部门成员的权限？ 部门经理可以改变任意部门成员的角色（权限集合），角色由超级管理员统一设定，各部门的部门经理都可以从企业控制台的预设角色里为自己的部门成员选择相应的角色，部门经理无法新建角色。如需要新建特别的角色权限，需要联系超级管理员，由超级管理员在企业控制台中新增角色。 部门经理可以通过角色权限查询来了解各个预设角色的具体权限，从而决定分配什么角色给部门成员。通常，部门成员使用默认的“部门成员”角色就能满足大部分需求。 改变部门成员的部门角色操作分两步： 查看角色的权限。 在你管理的部门文件夹上右键点击，选择部门管理界面中的“管理部门成员” 在部门成员管理界面中，点击“角色”右边的问号图标 此时会展开整个企业的角色权限列表。在列表中可以查看各个角色所具有的权限。 更改部门成员的角色 在角色处点击要更改角色的部门成员的倒三角，在下拉列表中选择需要的角色就可以更改该成员在部门中的角色了。 67. 部门经理如何查看部门有哪些文件被分享了？ 在你有管理权限的部门文件夹上右键点击，菜单中点击部门管理，在弹出界面中点击打开分享文件列表，就可以看到整个部门的分享文件了，包括子部门。 68. 部门里面有个文件/文件夹不想给一些人看到，怎么操作？ 拥有部门文件管理权限的角色（一般是部门经理）可以使用“文件访问控制”的功能设定部门中某一个文件/文件夹的访问权限来重新制定该文件的访问权限。 右键点击需要设定权限控制的部门文件夹，选择“文件访问控制”栏目 在文件访问控制弹窗内可以按成员或者角色的维度来控制特定人或人群对该文件/文件夹的访问权限。选择“不设置”的意思是不改变成员的访问权限。如把某部门成员对该文件/文件夹的访问权限设为“不可见”，该部门成员的部门文件夹中就看不到这个文件/文件夹。点击“角色权限设置”可以更改某一个角色的部门成员对文件的访问控制。 69. 我想让我们部门的人只能在部门的电脑上使用巴别鸟，怎么操作？ 这个需求需要使用“mac地址绑定”功能。只有超级管理员可以设定mac地址绑定。 超级管理可在企业控制台—mac地址绑定栏目里设定特定用户的账号访问设备的mac地址，绑定mac地址后，开启mac地址绑定开关，该账号使用巴别鸟客户端时仅能在该mac地址所在的电脑上，而网页和app的使用不受限制；再开启仅客户端访问开关，绑定mac地址的账户就不能使用网页和手机进行登录，只能在该mac地址所在的电脑上使用客户端访问巴别鸟。（因iOS系统和浏览器的限制，我们无法在网页和iPhone上获取到设备的mac地址，所以mac地址绑定的设备仅限于Windows和Mac设备的客户端使用） 70. 巴别鸟是否支持一个用户在多个部门？ 支持，管理员可以在企业管理后台成员管理栏目中点击成员昵称把成员加入到多个部门，并且在不同部门设定不同的角色。 部门经理也可以在自己部门的部门成员管理界面中选择企业内的其他成员加入本部门。 71. 临时建立一个项目组，需要从公司各个部门抽调人员并共享文件，怎么操作？ 推荐使用巴别鸟的“项目文件夹”来完成。 你可以在“个人文件”根栏目上创建个人项目，也可以在你所在的部门下创建项目（拥有创建文件夹/项目权限的角色才可以创建部门项目）。个人项目的归属是创建者，部门项目的归属是部门，对于部门项目下的内容，部门经理都可以查看及管理，不管该项目是不是由这个部门经理创建的或该部门经理是否属于该项目。个人项目和部门项目均可邀请整个企业的内部成员或外部人员或未注册巴别鸟的手机或邮箱加入。 项目文件夹有如下特性： 项目有有效期，到期后项目成员就看不到项目了。项目负责人可以中途更改项目的有效期。同时项目可以分别设定项目成员的有效期，项目成员权限有效期到期后，项目成员将无法访问该项目，但该成员在项目中上传的文件会保留。 项目负责人和项目本身都可以转交，个人项目也可以通过转交的方式转交到部门或其他个人，部门项目负责人也可以转交给其他部门或其他成员。如果项目转交给了其他部门，项目归属和项目管理权也会随之转交。 项目内的人员权限不受部门角色影响（除有部门文件管理权限的角色），项目负责人可以任意更改项目成员在项目中的权限并设定项目成员访问项目的截止时间。但在部门项目中，拥有“部门文件管理”权限的角色（一般是部门经理）可以不受项目权限的约束来访问项目。 项目创建者及项目负责人可以邀请企业内部的任何成员加入项目。也支持邀请外部成员加入项目。 项目有独立的项目讨论组，可以在讨论组进行群聊。 部门项目只能创建于部门根目录（为了便于管理）下，不能创建于部门的其他文件夹下。 个人项目只能创建于“个人文件”根目录下，不能创建于其他个人文件夹下。 项目中支持创建子项目。子项目可设定独立的项目管理权限及项目负责人。父项目成员均可查阅子项目的内容，权限跟随父项目。 在讨论组中点击人员头像，可以查看该人员在项目中上传的文件列表。 项目创建后，会显示在项目成员的“我的项目”根目录下。项目成员均可在我的项目栏目访问项目。 在我的项目栏目中也可以查看你加入或管理的项目。 如何建立项目： 在能创建项目的位置（个人项目创建在“个人文件”根目录下，部门项目创建在部门文件夹根目录下）空白处点击左上角新建按钮，选择新建项目按钮，按引导进行项目创建及添加项目成员。成员被添加后会收到加入项目通知，并且在“我的项目”栏目中就可以访问到该项目。 72. 为什么我不能在部门里创建项目？ 你试图在一个普通文件夹中创建项目（黄色文件夹）没有在部门根目录创建项目。 你没有在部门中创建项目的权限。如果你需要管理一个项目，可以联系部门经理，由部门经理创建项目并把你设定为项目负责人。你也可以在“个人文件”下创建一个个人项目。 73. 部门里有个文件想给其他部门的人一起看，但不想一个个邀请，该怎么操作？ 右键点击要分享的文件/文件夹——选择分享，在邀请分享中点击“从企业成员列表或者分组中添加”按钮。 点击企业成员栏目，找到你想分享的部门，在想分享的部门名字前单击把部门加入列表后点击“发送”即可。 如果需要邀请不同部门里的某些成员，可以把这些成员加入一个分组（在个人头像倒三角处点击设置，找到分组管理栏目，新建个人私有分组供个人使用；超级管理员可以创建企业公共分组，整个企业内部人员都可使用），邀请的时候邀请该分组即可。 74. 我想收集各个部门的一些材料，怎么操作？ 建议使用巴别鸟的收件箱功能。 进入你需要保存这些材料的目录，点击左上角“新建”按钮， 选择“收件箱 组织内收集”打开收件箱创建界面。 填写相应信息并选择需要提交材料的同事（投件人）后点击“创建”就可以创建一个收件箱文件夹。同时系统会向你选择的投件人发送投件通知。投件人点击通知后可以进入投件箱按要求上传文件。 组织内收集收件箱有如下特性： 投件人必须登录后才能上传文件 截止日期前，投件人可以上传及编辑自己的文件，上传新的版本，截止日期到期后，投件人即无法上传文件和修改已提交的文件 投件人看不到自己上传的文件外的其他文件（收件人上传的文件除外） 还有一种收件箱是开放式收件箱，开放式收件箱会产生一个链接，您可以将链接发放出去，凡知道此链接的人不需要注册就可以上传文件。 75. 我想发个文件给全公司所有人，让他们都能查看，但不能下载，怎么操作？ 在这个文件上点击右键，选择分享，在邀请分享中点击“从企业成员列表或者分组中添加”按钮。 点击企业成员栏目，找到组织结构的根部门（一般是你的公司名），单击公司名使之加入列表，把右侧权限列表中的权限设为“可以查看”，然后点击底部发送按钮即可。 76. 如何使用巴别鸟快速收集用户的文件？ 针对快速收集文件，巴别鸟推出了收件箱功能。 在需要放置收集文件的目录下点击新建——收件箱。 如果你需要收集外界用户（非注册用户）的文件，就选择开放式收集。点击下一步进行相关设置（设置有效期，上传需要填写的表单内容）后会形成一个收集链接和二维码。你可以发送这个链接和二维码给相应的用户（发群里或者公开渠道），他们点击后填写一个表单后即可上传文件。 如果要在企业内收集就选择组织内收集，指定名单的成员会收到通知，点击进入即可上传文件。 收件箱的目标对象仅可看到收件人和自己上传的文件，看不到其他投件人上传的文件。收件人可以看到所有人上传的文件。 77. 我发给客户的分享里的内容不对，该怎么办？ 你只要直接修改你分享的文件或文件夹的内容，或者上传新的版本即可。只通过链接分享地址查看你文件的客户仅能看到文件的最新版本。你只要修改文件，所有查看你分享的用户预览文件时看到的都是文件的最新版本。但如果你给了分享接收者“下载文件”权限，并且对方下载了源文件，那么对方已下载的内容是无法更改的。 78. 我不想让客户下载我分享的文件，但是能看，怎么操作？ 邀请或链接分享时选择“可以查看”（邀请）或“知道此链接的任何人都可以查看”（链接分享）权限，这样收到邀请或链接的用户都只能查看文件并不能下载。 79. 我想把巴别鸟上的文件在微信里发给联系人，怎么操作？ 使用巴别鸟APP可以直接把文件发送给微信中的联系人。 在巴别鸟APP中找到你要发送的文件，点击文件右侧底部的箭头按钮，弹出下拉菜单， 点击分享，打开分享界面。 分享界面中可以选择分享方式 其中： 选择复制链接可以把分享链接复制到剪贴板，你可以在企业微信或钉钉聊天窗口粘贴分享link 选择微信好友直接在微信好友列表中选择发送分享link的对象 选择微信朋友圈直接发送这个分享link到朋友圈 选择二维码可以给身边的朋友扫码获取这个link 选择源文件，可以直接发送源文件（并非link，而是文件本身的源文件，相当于下载文件）给第三方应用中的联系人。如选择企业微信，系统会自动下载文件后发送给你选定的企业微信联系人。发送的源文件不受权限控制，相当于你直接发文件给其他人。 如果你在电脑上想发送文件给微信上的人，可以右键点击要分享的文件，选择“分享”——链接分享，打开开放式链接分享按钮。 然后点击二维码标志，用手机微信扫码获得分享link。 扫码后，会在微信上打开这个分享link， 点击右上角“…”更多按钮， 选择“发送给朋友”即可。 80. 我使用企业微信/钉钉可以直接访问巴别鸟的文件么？ 需要企业选购巴别鸟的企业微信或钉钉集成服务。 开通企业微信或钉钉集成服务后，企业成员可以在工作台中看到巴别鸟的图标。 点击该图标就可以访问巴别鸟，可以查看到用户权限范围内可以看到的全部文件，但由于企业微信及钉钉对网盘系统的限制，仅能使用预览、下载、分享等有限的操作。" }, { "lang": "zh", "slug": "faq-preview-search", "title": "FAQ：预览、在线编辑、搜索和标签", "description": "覆盖 预览、在线编辑、搜索和标签 相关常见问题。", "category": "常见问题", "top_category": "常见问题", "keywords": [ "FAQ", "FAQ：预览、在线编辑、搜索和标签" ], "url": "zh/faq-preview-search.html", "source": "content/zh/faq-preview-search.md", "summary": "FAQ：预览、在线编辑、搜索和标签 以下问题覆盖用户在使用巴别鸟企业网盘时常见的操作、权限、协作和排障场景。 81. 为什么我预览PPT不能播放动画？ 巴别鸟的PPT是以页面的形式展现的，不支持PPT的内置动画和link。 想要播放PPT动画，可使用“在线编辑”功能打开PPT并进行播放（需购买在线编辑模块），或者安装客户端后点击文件的编辑按钮。 82. 为什么有的视频文件巴别鸟不能播放？ 巴别鸟仅支持Html5规则的视频和音频文件的播放，一般是H264视频编码和AAC音频编码的Mp4文件。如果视频编码不符合要求就不能在H5下播放。但可以使用格式工厂等转码软件转码后播放。 具体的可播放文件类型及浏览器对应规则如下： 83. 文件不小心误删了，怎么办？ 你可以在回收站中恢复误删的文件，回收站的保存期限默认为60天，也可以由超级管理员在企业控制台设定，设置范围可从1天到999天。 如果回收站里没有该文件，说明这个文件已经被彻底删除。 84. 同事离职了，他的文件怎么办？ 巴别鸟支持一键交接，超级管理员可以使用一键交接功能处理离职同事的文件交接工作。 在部门成员列表（部门文件夹右键，部门管理中）或企业控制台成员列表中找到该离职同事。 点击姓名打开成员管理界面 在转移文件归属栏目，点击“转移至”按钮 在列表中选择一个交接者，点击确定后完成转移。 文件转移后，离职同事对相应文件/文件夹的权限，分享关系都会转移给交接人。此操作不可逆。 85. 部门文件太多了，我新上传了一个文件，想让某同事看下，怎么操作简单？ 可以使用提醒关注或@功能。 在文件上点击右键，选择“提醒关注”按钮，选择你想提醒关", "headings": [ { "level": 1, "title": "FAQ：预览、在线编辑、搜索和标签", "id": "faq" }, { "level": 2, "title": "81. 为什么我预览PPT不能播放动画？", "id": "81-ppt" }, { "level": 2, "title": "82. 为什么有的视频文件巴别鸟不能播放？", "id": "82" }, { "level": 2, "title": "83. 文件不小心误删了，怎么办？", "id": "83" }, { "level": 2, "title": "84. 同事离职了，他的文件怎么办？", "id": "84" }, { "level": 2, "title": "85. 部门文件太多了，我新上传了一个文件，想让某同事看下，怎么操作简单？", "id": "85" }, { "level": 2, "title": "86. 为什么下载文件夹点击下载半天没反应？", "id": "86" }, { "level": 2, "title": "87. 客户端的编辑和在线编辑有什么区别？", "id": "87" }, { "level": 2, "title": "88. 为什么我在线编辑器打开很慢？", "id": "88" }, { "level": 2, "title": "89. 我想让几个同事一起填个表格，该怎么操作？", "id": "89" }, { "level": 2, "title": "90. 如何才能树状的查看文件夹？", "id": "90" }, { "level": 2, "title": "91. 能不能按条件筛选出我想找的文件？", "id": "91" }, { "level": 2, "title": "92. 什么是标签？", "id": "92" }, { "level": 2, "title": "93. 如何使用巴别鸟标签？", "id": "93" }, { "level": 2, "title": "94. 巴别鸟如何搜索标签？", "id": "94" }, { "level": 2, "title": "95. 巴别鸟支持高级搜索么？", "id": "95" }, { "level": 2, "title": "96. 我想发送电脑上的文件给同事，有没有好的办法？", "id": "96" } ], "images": [], "text": "FAQ：预览、在线编辑、搜索和标签 以下问题覆盖用户在使用巴别鸟企业网盘时常见的操作、权限、协作和排障场景。 81. 为什么我预览PPT不能播放动画？ 巴别鸟的PPT是以页面的形式展现的，不支持PPT的内置动画和link。 想要播放PPT动画，可使用“在线编辑”功能打开PPT并进行播放（需购买在线编辑模块），或者安装客户端后点击文件的编辑按钮。 82. 为什么有的视频文件巴别鸟不能播放？ 巴别鸟仅支持Html5规则的视频和音频文件的播放，一般是H264视频编码和AAC音频编码的Mp4文件。如果视频编码不符合要求就不能在H5下播放。但可以使用格式工厂等转码软件转码后播放。 具体的可播放文件类型及浏览器对应规则如下： 83. 文件不小心误删了，怎么办？ 你可以在回收站中恢复误删的文件，回收站的保存期限默认为60天，也可以由超级管理员在企业控制台设定，设置范围可从1天到999天。 如果回收站里没有该文件，说明这个文件已经被彻底删除。 84. 同事离职了，他的文件怎么办？ 巴别鸟支持一键交接，超级管理员可以使用一键交接功能处理离职同事的文件交接工作。 在部门成员列表（部门文件夹右键，部门管理中）或企业控制台成员列表中找到该离职同事。 点击姓名打开成员管理界面 在转移文件归属栏目，点击“转移至”按钮 在列表中选择一个交接者，点击确定后完成转移。 文件转移后，离职同事对相应文件/文件夹的权限，分享关系都会转移给交接人。此操作不可逆。 85. 部门文件太多了，我新上传了一个文件，想让某同事看下，怎么操作简单？ 可以使用提醒关注或@功能。 在文件上点击右键，选择“提醒关注”按钮，选择你想提醒关注的同事即可。 该同事将会收到一个提醒关注通知，同时在该成员左侧栏“我的关注”列表中将会有这个文件。 你也可以打开文件评论，在评论里@这个同事，他也能收到@通知。 提醒关注和@仅能选择对该文件至少有查看权限的人，如果该同事不在列表里，说明这个同事没有这个文件的访问权限，这种情况下你可以使用邀请分享的形式让这个同事可以阅读该文件。 86. 为什么下载文件夹点击下载半天没反应？ 使用浏览器下载巴别鸟上的文件夹时需要在服务器上把文件夹打包成一个ZIP压缩包再进行下载。打包需要时间，所以点击文件夹下载时需要等待一段时间才能开始下载。并且，为了节约服务器资源，巴别鸟严格限制了文件夹下载的条件：文件夹中的文件数量大于100或文件夹容量大于500MB的文件夹不支持浏览器下载。 如需要下载文件夹，推荐使用巴别鸟客户端，客户端无需打包，可直接下载大文件夹，并且没有文件夹大小限制。 87. 客户端的编辑和在线编辑有什么区别？ 客户端编辑的原理是把网络上的文件缓存到电脑本地，并调用本地的应用程序打开编辑，编辑完成保存时自动上传并在云端建立新的文件版本。这就意味着： 为了防止版本冲突，客户端不支持几个用户同时编辑同一个文件。所以客户端编辑的文件会自动锁定防止他人同时编辑。只有等一个编辑者完成并解锁，其他编辑者才可以继续编辑。 客户端能否编辑一个文件是由安装客户端的电脑决定的，如果安装客户端的电脑有各种应用程序编辑文件，理论上使用客户端编辑可以编辑所有类型的文件。 客户端编辑文件因为是使用本地程序调用本地电脑的运算资源，所以速度更快，体验更好。 在线编辑的原理是直接调用在线编辑服务器，在云端打开文件进行编辑。这意味着： 目前在线编辑能支持office文件（word、excel、ppt）、wps文件、txt文件、markdown文件、km文件，而txt文件、markdown文件、km文件是不支持多人同时在线编辑的。 因为是在云端实时编辑，所以可以多人同时编辑同一个文件，但是有可能多人同时编辑造成版面混乱。 因为在云端编辑，所以很多资源需要缓存到服务器，和网络速度及连通率都有关系，所以速度及体验是不如客户端编辑的。 在线编辑不需要本地安装应用程序，只要支持Html5规范的浏览器都可以使用。 88. 为什么我在线编辑器打开很慢？ 第一次打开office文档进行在线编辑速度会很慢（因为要加载缓存文件），但第二次在同一浏览器打开就会快很多了。 巴别鸟使用了Onlyoffice的office在线编辑模块。在线编辑打开慢主要原因是：不同于本地编辑，在线编辑需要把文件传输到云端的编辑服务器并把在线编辑器缓存到浏览器里才能进行编辑。这个缓存的速度和文件大小及使用的字体关联很大。而我们常用的中文字体都不小（一个中文字体包平均大小一般有30MB以上，一个英文字体包一般只有20KB左右），支持的中文字体越多，缓存越慢。这也是目前中文office在线编辑器共同面临的窘境。我们已经优化了巴别鸟上的Onlyoffice中文字库，但打开文档的速度还是比客户端编辑慢。 89. 我想让几个同事一起填个表格，该怎么操作？ 你可以使用在线编辑功能和同事一起填写表格。 上传需要编辑的表格，提醒同事关注表格或者@同事。详见FAQ问题：部门文件太多了，我新上传了一个文件，想让某同事看下，怎么操作简单？ 然后在要编辑的Excel文件上点击右键选择“在线编辑”，这个时候会打开Excel在线编辑器，在其中编辑表格即可。其他同事如果也在线编辑该表格，在Excel编辑器右上角会有成员提示，你也可以实时看到对方编辑的内容。 90. 如何才能树状的查看文件夹？ 想要树状查看文件夹很简单，点击文件夹列表右上角区域“文件夹目录”按钮即可。 点击该按钮后，会在文件列表左边打开树状目录。 91. 能不能按条件筛选出我想找的文件？ 在你要筛选的文件夹下，点击文件列表右上角工具栏第一个按钮“筛选”按钮。 就可以按标签、文件类型、文件大小、文件更新时间、上传用户的维度组合筛选出当前文件夹下面的筛选结果。 同时，使用搜索功能得出的搜索结果也可以使用筛选功能精确定位。 92. 什么是标签？ 巴别鸟支持给任意文件及文件夹打标签（tag），并且巴别鸟的标签是共享标签，这意味着，当你给文件添加标签后，所有能访问该文件的人都能看到并使用该标签查询到这个文件。这在很多场景下很实用，譬如你可以用标签给素材分类。 93. 如何使用巴别鸟标签？ 文档列表文件名下方有添加标签按钮，点击即可添加标签。如果文件名下方没有添加标签按钮很可能是开启了简洁文件列表，可以在文件列表顶部右方的设置按钮选择标准列表。或者文件上右键“查看详情”，在文件详情里添加标签。 巴别鸟还支持仅允许企业控制台创建标签，在企业控制台——标签管理中打开“只允许企业控制台创建和管理标签”，这样可以由管理员统一创建和管理标签，普通成员添加标签时仅可以从标签库中选择标签。这个设置可以防止不同人添加标签时产生大量同义词标签。 94. 巴别鸟如何搜索标签？ 点击搜索框最右边的搜索选项按钮，选择“仅标签”，这时候搜索的就是标签匹配的文档。 在左侧栏有标签查找功能，点击左侧栏“标签设置”，在标签管理界面里可以选择在左侧栏显示的标签，设定完成后，在左侧栏点击标签，就会在文件列表上显示拥有该标签的文档。 95. 巴别鸟支持高级搜索么？ 巴别鸟支持高级搜索。点击搜索框右边“高级搜索”按钮就可以打开高级搜索窗口。 高级搜索支持如下搜索方式： 多关键字复合搜索。 限定文件更新时间范围的搜索。 照片按拍摄时间搜索。 搜索特定类型、格式的文件。 搜索特定用户上传的文件。 支持手动选择特定文件夹进行搜索。 支持搜索类型选择。如：全文搜索+标签搜索、仅搜索文件说明。 96. 我想发送电脑上的文件给同事，有没有好的办法？ 如果你安装了巴别鸟客户端，要发送电脑上的本地文件/文件夹给同事，操作会相当简单。 右键点击你想要发送的文件/文件夹，在弹出菜单中找到 “巴别鸟”—“快速发送给” 这个时候会弹出快速发送文件选择框，选择需要发给的同事，点击发送即可。 该同事会接收到一条巴别鸟通知，在通知中可下载你发送的文件。 快速发送仅支持小于50个文件并且大小小于50MB的文件夹，如果发送文件的话，支持的最大文件为50MB。" }, { "lang": "zh", "slug": "faq-archive-annotation", "title": "FAQ：档案、批注、评审和角标", "description": "覆盖 档案、批注、评审和角标 相关常见问题。", "category": "常见问题", "top_category": "常见问题", "keywords": [ "FAQ", "FAQ：档案、批注、评审和角标" ], "url": "zh/faq-archive-annotation.html", "source": "content/zh/faq-archive-annotation.md", "summary": "FAQ：档案、批注、评审和角标 以下问题覆盖用户在使用巴别鸟企业网盘时常见的操作、权限、协作和排障场景。 97. 如何管理企业档案库？ 巴别鸟内置一个档案管理模块，所有的归档文件在档案库统一保存。超级管理员和档案管理员可以对归档文件进行建档（阅览室）分类。归档操作不可逆，文档归档后可重命名、可删除、可借阅。借阅有在线阅读和下载、复制三种权限。档案库使用的规则和特性为： 只有“档案管理员”和“超级管理员”能管理企业档案库，其他人员不能管理档案库。 档案管理员的身份需要超级管理员在企业管理后台“档案管理员”下面添加。 档案管理员、超级管理员可以新建阅览室 归档文件要由档案管理员或超级管理员移动至阅览室，其他成员才能借阅 有“部门文件管理”权限的人可以归档所在部门的文件 档案库有独立的“动态”模块，在里面可以查询用户自己的借阅历史 档案管理的“动态”模块里有所有档案借阅记录 档案管理员和超级管理员不需要借阅即可查看所有归档文件 阅览室的开放级别有四种：公开、限定部门内公开、需要借阅、限定部门内可借阅。公开的阅览室内的文件所有人可见，用户可直接对阅览室内文件进行查看、下载等操作；限定部门内公开的阅览室仅指定的部门内成员可见，用户可直接对阅览室内文件进行查看、下载等操作；需要借阅的阅览室内文件所有人可见，用户需要借阅后，才能对阅览室内文件进行查看、下载等操作；限定部门内可借阅的阅览室仅指定的部门内成员可见，用户需要借阅后，才能对阅览室内文件进行查看、下载等操作。 98. 什么类型的文件可以批注？ 除视频和音频文件还有office文件、MD、TXT外的只要能在巴别鸟中打开预览的文件都能进行", "headings": [ { "level": 1, "title": "FAQ：档案、批注、评审和角标", "id": "faq" }, { "level": 2, "title": "97. 如何管理企业档案库？", "id": "97" }, { "level": 2, "title": "98. 什么类型的文件可以批注？", "id": "98" }, { "level": 2, "title": "99. 如何创建批注？", "id": "99" }, { "level": 2, "title": "100. 如何删除批注？", "id": "100" }, { "level": 2, "title": "101. 如何回复批注？", "id": "101" }, { "level": 2, "title": "102. 我上传了文档的新版本，批注不见了？", "id": "102" }, { "level": 2, "title": "103. 我如何查看老版本的批注？", "id": "103" }, { "level": 2, "title": "104. 文件版本删除了，批注会删除么？", "id": "104" }, { "level": 2, "title": "105. 我回复的批注错误了,能不能撤销？", "id": "105" }, { "level": 2, "title": "106. 为什么我不能创建批注？", "id": "106" }, { "level": 2, "title": "107. 为什么我给了用户链接分享的批注权限，但他们却不能批注？", "id": "107" }, { "level": 2, "title": "108. 为什么我在APP上不能创建一些类型的批注？", "id": "108-app" }, { "level": 2, "title": "109. 为什么我在电脑上不能创建一些类型的批注？", "id": "109" }, { "level": 2, "title": "110. 在动态里直接回复的批注不能显示怎么办？", "id": "110" }, { "level": 2, "title": "111. 文件上会显示各种角标，他们分别有什么含义？", "id": "111" }, { "level": 2, "title": "112. 最大能上传的单个文件是多大？", "id": "112" }, { "level": 2, "title": "113. CAD文件在客户端预览不了，怎么办？", "id": "113-cad" }, { "level": 2, "title": "114. 预览文件时，卡在生成预览文件界面，怎么办？", "id": "114" } ], "images": [], "text": "FAQ：档案、批注、评审和角标 以下问题覆盖用户在使用巴别鸟企业网盘时常见的操作、权限、协作和排障场景。 97. 如何管理企业档案库？ 巴别鸟内置一个档案管理模块，所有的归档文件在档案库统一保存。超级管理员和档案管理员可以对归档文件进行建档（阅览室）分类。归档操作不可逆，文档归档后可重命名、可删除、可借阅。借阅有在线阅读和下载、复制三种权限。档案库使用的规则和特性为： 只有“档案管理员”和“超级管理员”能管理企业档案库，其他人员不能管理档案库。 档案管理员的身份需要超级管理员在企业管理后台“档案管理员”下面添加。 档案管理员、超级管理员可以新建阅览室 归档文件要由档案管理员或超级管理员移动至阅览室，其他成员才能借阅 有“部门文件管理”权限的人可以归档所在部门的文件 档案库有独立的“动态”模块，在里面可以查询用户自己的借阅历史 档案管理的“动态”模块里有所有档案借阅记录 档案管理员和超级管理员不需要借阅即可查看所有归档文件 阅览室的开放级别有四种：公开、限定部门内公开、需要借阅、限定部门内可借阅。公开的阅览室内的文件所有人可见，用户可直接对阅览室内文件进行查看、下载等操作；限定部门内公开的阅览室仅指定的部门内成员可见，用户可直接对阅览室内文件进行查看、下载等操作；需要借阅的阅览室内文件所有人可见，用户需要借阅后，才能对阅览室内文件进行查看、下载等操作；限定部门内可借阅的阅览室仅指定的部门内成员可见，用户需要借阅后，才能对阅览室内文件进行查看、下载等操作。 98. 什么类型的文件可以批注？ 除视频和音频文件还有office文件、MD、TXT外的只要能在巴别鸟中打开预览的文件都能进行批注，包括图片、GIF动画、PDF、3D模型、CAD文件。巴别鸟批注只能在文件预览状态下进行，文件编辑时在编辑界面不能进行批注。 私有化系统因为以下模块和设置可能导致一些文件类型不能使用“巴别鸟”批注，但可以使用查看器内部的批注。（这类批注不会在巴别鸟中进行通知和动态显示）。这类情况为： 在office在线编辑过程中建立的批注。 Excel选择了表格模式查看模块。按电子表格预览的形式查看Excel。 选择了CAD高级显示模块，使用Autodesk的CAD查看器。 99. 如何创建批注？ 仅有登录或身份验证通过的用户可以创建批注，目前不支持匿名用户创建批注。 网页版本和客户端：在预览模式下，在想批注的地方双击鼠标左键即可创建批注。或使用左侧批注菜单选择相应的按钮创建批注。 手机APP：在预览模式下，轻触（单击）要创建批注的地方，选择“批注”，即可创建批注。（手机APP仅可创建批注点批注） 手机H5或企业微信或钉钉：在预览模式下，在要创建的地方长按屏幕，选择菜单中“建立批注”选项。 目前支持的批注类型有批注点批注、手绘笔、焊接标记、图形批注、标注和文字批注。 批注点批注：巴别鸟的主要批注类型，双击预览中要创建批注的区域即可建立。每个批注点相当于一个讨论区，手机APP及H5页面也都可以建立及浏览回复。 手绘笔：可以在预览文件上手绘圈画，其他协作者可以实时看到手绘的内容，仅支持在网页及客户端创建，在手机APP上仅可以浏览。 焊接标记：可以在预览文件上插入国际焊接标记并编辑，仅支持在网页及客户端创建，在手机APP上仅可以浏览。 图形批注：使用图形框选区域并建立批注点，批注点和标准的批注点一样可以讨论，仅支持在网页及客户端创建，在手机APP上仅可以浏览及回复。 标注：在预览文件上建立一个文本标注或说明，不可回复及讨论，标注是一个直接显示的文本说明，在手机APP和H5上都可以创建。 文字批注：可以选择一段文本，并建立一个批注区，支持讨论。同时也可以复制选择的文本，仅支持在网页及客户端创建，在手机APP上仅可以浏览及回复。 100. 如何删除批注？ 拥有可删除批注权限的人才可以删除批注。 对于部门文件上的批注：拥有部门文件管理权限的人（部门经理）、超级管理员、批注创建者（角色里打开了删除自己批注权限）可以删除批注。 对于个人文件上的批注：文件所有者、批注创建者可以删除批注。 删除方法如下： 批注点批注： Web或客户端在批注列表中删除批注 Web或客户端打开批注，选择删除按钮进行删除 APP端长按批注点，出现删除按钮后点击删除 手绘笔： Web或客户端在预览模式下右上角手绘列表中删除。 点击显示手绘笔迹列表—鼠标移动到列表中想要删除的项目—出现删除按钮时点击删除。 焊接标记： Web或客户端在标记上点击右键，出现删除按钮，点击删除。 标注： Web或客户端在标注上点击右键，出现删除按钮，点击删除 APP端长按标注，出现删除按钮后点击删除 文字批注： Web或客户端打开文字批注选择删除按钮进行删除 101. 如何回复批注？ 有人在文档中建立批注后，如果你能访问该文档，并且具有查看批注权限。你将会收到文档被批注的动态，同时在文件列表中，有新批注的文档图标前也会有红点提示，你可以有两种方法回复批注： 进入文档查看批注并回复。点击动态消息上的文件名可以进入文档，点击批注两个字可以进入文档并打开这条批注。打开批注后直接回复即可。 如果你清楚对方批注的内容所指想马上回答，可直接点击动态中批注下面的“回复”按钮，直接回复这条批注。不用打开文档。 102. 我上传了文档的新版本，批注不见了？ 巴别鸟的批注是跟随文档版本的，这意味着，当有人上传了文档的新版本，在预览新版本内容时，旧版本的批注就看不到了。但只要这个旧版本还存在，通过“版本管理”栏目查看旧版本时，你依然可以看到旧版本的批注。或者打开批注列表，在批注列表中统一查看所有版本的批注记录。并且点击批注列表的批注时会自动跳转到旧版本。 103. 我如何查看老版本的批注？ 在预览区域点击左上角的批注列表，你可以在列表中查看旧版本的批注。 批注列表展开后，你可以看到历史版本的所有批注。 点击历史版本的批注会自动打开这个批注所在的版本及批注位置进行显示。批注打开后旧版本的批注也可以进行回复，并且动态里也同样会有回复通知。 在文件版本管理中切换到旧版本，也能查看到旧版本的批注。 104. 文件版本删除了，批注会删除么？ 会。因为批注是跟着文件版本走的，批注信息也是该文件版本信息的一部分，文件的版本删除了，该版本的相关批注也会同时被删除。 105. 我回复的批注错误了,能不能撤销？ 回复的批注是可以撤销的，但只能批注回复者本人在回复批注后的两分钟内撤销。目前仅支持在客户端和Web版本中撤销批注回复，在手机APP上不支持批注回复的撤销。 撤销方式：在批注对话框中你的回复上鼠标右键点击，弹出撤销按钮，点击撤销。（撤销操作因要进行权限判定，系统响应会比较慢。如遇到提示“撤销失败”，关闭这个批注，再次打开即可完成撤销）。 106. 为什么我不能创建批注？ 不能创建批注有以下几种可能： 该文件关闭了“可批注”的授权（仅针对部门文件），也有可能对一部分人关闭了可批注授权。 这个文件邀请或者链接分享给你时没有给你批注或查看批注授权。 你是通过分享链接打开的文档，同时你没有登录，巴别鸟不支持匿名批注。 107. 为什么我给了用户链接分享的批注权限，但他们却不能批注？ 巴别鸟不支持匿名批注，用户需要登录巴别鸟才能进行批注。并且由于私有云没有公共账号体系，所以外部成员无法注册成为一个企业的用户，这就意味着没有该企业账户的成员是没有办法在链接分享的文档中进行批注的。如果需要企业外部成员对文档进行批注，可以使用邀请分享功能，输入该外部成员邮箱或手机号（需要购买手机短信模块）进行邀请。对方收到邀请后可以用邀请他的邮箱或手机号进行身份验证，身份验证通过后就可以对文档进行批注。 108. 为什么我在APP上不能创建一些类型的批注？ 巴别鸟针对不同设备的使用习惯和特性会对不同终端的版本进行优化并精简操作。譬如：在手机客户端（APP），操作应该便捷简单符合触摸，所以手机端可以使用单击建立批注的方式快速建立批注点，并且支持语音批注（手机都有麦克风）、或者可在批注中插入手绘。在PC的使用环境下，因为鼠标操作方便及演示需求，又提供了其他类型的批注，但PC上没有语音批注（工作PC上大多数没有麦克风）。 同时，为了传达的信息不丢失，不管什么类型的批注，在手机APP和PC端或Web端都可以查看。APP上可以查看PC上建立的所有批注类型，同时在PC上也可以播放在手机APP上创建的语音批注。 109. 为什么我在电脑上不能创建一些类型的批注？ 电脑端及Web端目前不能创建语音批注，主要原因是大多数工作PC上并没有麦克风，在PC上也 没有使用语音的习惯。但是在电脑端及Web端都可以查阅及收听在APP上创建的语音批注。 110. 在动态里直接回复的批注不能显示怎么办？ 刷新动态页面或切换到文件再切换回动态即可显示。 111. 文件上会显示各种角标，他们分别有什么含义？ 巴别鸟会根据文件状态不同而显示不同的角标，下面是各种角标的含义。（因为各终端的刷新速率和网络状况，角标的显示不一定实时，角标仅做文件状态参考。同时因为界面UI适配原因，不同终端图标颜色也会有所区别） 1.网页和客户端上出现的图标： 文件右下角新版本图标：表示该文件上传过新版本 文件/文件夹右下角分享图标：表示该文件/文件夹已打开分享，该角标会覆盖文件新版本角标 文件/文件夹左下角快捷方式或归档图标：表示这是一个快捷方式文件，源文件/文件夹可以不在该目录下；也可能是归档文件/文件夹。 ”定稿“：该审批文件已经定稿 “驳回”：该审批文件被驳回 “待启动”：定稿或驳回的文件上传了新版本 ”外部文件“：表示该文件/文件夹不是本企业成员创建的 “注”：表示该文件/文件夹有文件说明 “控”：表示该文件/文件夹做了“文件访问控制” “密”：表示该文件/文件夹的安全级别是保密 “限”：表示该文件/文件夹的安全级别是限制 “内”：表示该文件/文件夹的安全级别是内部 文件/文件夹下方有一个红色矩形：表示该文件/文件夹开启了快照分享 文件/文件夹下方有一条黄色的U行区域+“已归档”：表示该文件/文件夹做了本地归档，本地归档的文件不能再上传新版本 五角星：表示是自己关注的文件或文件夹 文件/文件夹图标右上角有一个橙色的圆圈：表示该文件/文件夹继承了上一级的文件访问控制 2.同步文件出现的图标： 文件/文件夹左下角有一个蓝色对号：表示文件/文件夹已同步成功（本地同步文件夹） 文件左下角有一个红色的叹号：表示文件同步失败 文件左下角有一个锁的图标：表示文件被锁定了，可以以只读模式打开（本地同步文件夹） 文件夹上有向上和向下两个半箭头图标：表示这是一个同步的文件夹（客户端） 3.客户端程序状态栏角标： 鸟图标下有一个对号：表示同步已经完成 鸟图标下有两个半圆箭头在不停转动：表示有文件正在同步 鸟图标下有一个叉号：表示出错导致同步中断 4.映射盘角标： 件左下角有一个云朵角标：表示此文件在云端（未下载或缓存） 文件左下角有一个分享角标：表示文件已分享，该角标会覆盖其他角标 文件左下角有一个蓝色对号：表示文件已下载并和云端一致 文件左下角有一个锁的图标：表示文件已被锁定，可以用只读模式开启 文件左下角有一个感叹号：表示本地的文件和云端有冲突 112. 最大能上传的单个文件是多大？ 个人版和专业版支持的单个文件的上传上限是5GB,企业公有云版单个文件的上传上限是10GB,私有云版单个文件的上传上限是可自定义的，在1GB到100GB之间设置，甚至更大都支持。 113. CAD文件在客户端预览不了，怎么办？ 如果在客户端点击CAD（dwg、dwt）文件也无法打开预览，通常会有如下几种情况： 该文件超过了限定大小无法预览。（大于100M） 该文件已损坏，无法生成预览。 制作该文件的CAD版本巴别鸟不兼容，生成预览失败 你可以使用客户端编辑按钮调取你电脑上安装的AutoCad软件进行查看，右键点击文件，选择“编辑”（需要有该文件的下载权限），客户端会自动调用本地可以打开CAD的程序打开该文件。 114. 预览文件时，卡在生成预览文件界面，怎么办？ 关闭该界面，等5 10分钟后重试。 巴别鸟预览服务器有一个转码的排队机制，如果需要转码的文件很多，就需要排队进行转码，点击文件进行预览时，会提高转码优先级，但如果排队的文件过多或是预览请求的用户多，这个转码会持续一段时间，所以等待一会重试就能正常打开预览。 不能预览文件并不会影响文件的编辑及使用，仅仅对在线预览文件功能有影响。文件也可以正常使用。" }, { "lang": "zh", "slug": "faq-technical", "title": "FAQ：部署、AI、限制和排障", "description": "覆盖 部署、AI、限制和排障 相关常见问题。", "category": "常见问题", "top_category": "常见问题", "keywords": [ "FAQ", "FAQ：部署、AI、限制和排障" ], "url": "zh/faq-technical.html", "source": "content/zh/faq-technical.md", "summary": "FAQ：部署、AI、限制和排障 以下问题覆盖用户在使用巴别鸟企业网盘时常见的操作、权限、协作和排障场景。 115. 专业版到期了怎么续费？ 在右上角用户头像处的倒三角处点击“设置”，在账号信息的最下方点击续费按钮，默认续费一年，也可以自己设置时长，2年、3年等都可以。 116. 巴别鸟上传文件类型有限制吗？ 巴别鸟上传文件类型是没有限制的，加入文件黑名单的文件类型才不允许上传。客户端系统设置添加的不需要同步的文件类型也是不上传的，还有一些临时文件，如以tmp;swp;lock等为后缀的文件 （只在同步任务里不上传，网页端或客户端上传是不受此限制的）。 117. 在线编辑有人数限制吗？ 在线编辑可以多人一起编辑，没有人数限制，一般的工作环境都是可以满足的。 118. 分享文件给其他人，还没到截至日期，但链接打不开了。 最大的可能是分享链接关闭又重新打开了，此种情况下，第一个传播出去的分享链接已经失效了。 119. 下载速度忽然变慢了，是怎么回事？ 可能是以下几种情况： 可能是网络问题，网络卡了或是网速忽然变慢了； 使用了VPN或其他翻墙工具占用了网络资源； 或者巴别鸟分配的高速流量用完了，开始使用限速模式； 或者管理员对某用户设置了下载限速等。 120. 进入一个文件夹，右下角提示文件不存在。 导致这种情况的原因有多种，比如服务器硬盘满了，比如内存某时刻满了导致系统不正常了，网络问题也可能导致上述问题（如开启了VPN或翻墙工具），可以稍等一下再试，或者联系巴别鸟客服。 121. 怎么查看共享文件的实时在线编辑人员？ Office文件才可以多人同时在线编辑，打开在线编辑，右上角会显", "headings": [ { "level": 1, "title": "FAQ：部署、AI、限制和排障", "id": "faq-ai" }, { "level": 2, "title": "115. 专业版到期了怎么续费？", "id": "115" }, { "level": 2, "title": "116. 巴别鸟上传文件类型有限制吗？", "id": "116" }, { "level": 2, "title": "117. 在线编辑有人数限制吗？", "id": "117" }, { "level": 2, "title": "118. 分享文件给其他人，还没到截至日期，但链接打不开了。", "id": "118" }, { "level": 2, "title": "119. 下载速度忽然变慢了，是怎么回事？", "id": "119" }, { "level": 2, "title": "120. 进入一个文件夹，右下角提示文件不存在。", "id": "120" }, { "level": 2, "title": "121. 怎么查看共享文件的实时在线编辑人员？", "id": "121" }, { "level": 2, "title": "122. 部门角色有上传文件的权限，在部门里的某个文件夹下不能上传文件，为什么？", "id": "122" }, { "level": 2, "title": "123. 团队里的文件删除后，在谁的回收站里？", "id": "123" }, { "level": 2, "title": "124. 团队删除后，会保存在回收站里吗？", "id": "124" }, { "level": 2, "title": "125. 巴别鸟支持私有化部署么？", "id": "125" }, { "level": 2, "title": "126. 如何私有化部署巴别鸟系统？", "id": "126" }, { "level": 2, "title": "127. 巴别鸟支持对象存储么？", "id": "127" }, { "level": 2, "title": "128. 私有化部署巴别鸟系统需要什么硬件？", "id": "128" }, { "level": 2, "title": "129. 巴别鸟支持对接企业微信么？", "id": "129" }, { "level": 2, "title": "130. 什么是智巢AI？", "id": "130-ai" }, { "level": 2, "title": "131. 我也想要智巢AI助理，怎么操作？", "id": "131-ai" }, { "level": 2, "title": "132. 智巢AI收费吗？如何收费？", "id": "132-ai" }, { "level": 2, "title": "133. 智巢AI可以私有化么？", "id": "133-ai" }, { "level": 2, "title": "134. 巴别鸟支持预览的文件格式有哪些？", "id": "134" }, { "level": 2, "title": "135. 如何使用客户端匿名下载？", "id": "135" }, { "level": 2, "title": "136. 在巴别鸟上传了文件，过了一会儿文件自动删除了，怎么回事呢？", "id": "136" }, { "level": 2, "title": "137. 巴别鸟在手机浏览器上可以上传文件吗？", "id": "137" }, { "level": 2, "title": "138. 匿名用户可以上传文件吗？", "id": "138" }, { "level": 2, "title": "139. 为什么不能在个人文件栏目上传文件？", "id": "139" }, { "level": 2, "title": "140. 可以在前台创建部门吗？", "id": "140" }, { "level": 2, "title": "141. 批量上传文件有数量或大小限制吗？", "id": "141" }, { "level": 2, "title": "142. 注册登录的时候，收不到验证码（邮箱，手机）？", "id": "142" }, { "level": 2, "title": "143. 私有和公有有什么区别？", "id": "143" }, { "level": 2, "title": "144. 什么权限的人可以归档文件？", "id": "144" }, { "level": 2, "title": "145. 电子签名是设置的哪个位置，是否可以手写？", "id": "145" }, { "level": 2, "title": "146. 怎么可以聊天？", "id": "146" }, { "level": 2, "title": "147. 文件水印可以批量添加么？", "id": "147" }, { "level": 2, "title": "148. 上传速度很慢，怎么回事？", "id": "148" }, { "level": 2, "title": "149. 为什么邀请不了成员？", "id": "149" } ], "images": [], "text": "FAQ：部署、AI、限制和排障 以下问题覆盖用户在使用巴别鸟企业网盘时常见的操作、权限、协作和排障场景。 115. 专业版到期了怎么续费？ 在右上角用户头像处的倒三角处点击“设置”，在账号信息的最下方点击续费按钮，默认续费一年，也可以自己设置时长，2年、3年等都可以。 116. 巴别鸟上传文件类型有限制吗？ 巴别鸟上传文件类型是没有限制的，加入文件黑名单的文件类型才不允许上传。客户端系统设置添加的不需要同步的文件类型也是不上传的，还有一些临时文件，如以tmp;swp;lock等为后缀的文件 （只在同步任务里不上传，网页端或客户端上传是不受此限制的）。 117. 在线编辑有人数限制吗？ 在线编辑可以多人一起编辑，没有人数限制，一般的工作环境都是可以满足的。 118. 分享文件给其他人，还没到截至日期，但链接打不开了。 最大的可能是分享链接关闭又重新打开了，此种情况下，第一个传播出去的分享链接已经失效了。 119. 下载速度忽然变慢了，是怎么回事？ 可能是以下几种情况： 可能是网络问题，网络卡了或是网速忽然变慢了； 使用了VPN或其他翻墙工具占用了网络资源； 或者巴别鸟分配的高速流量用完了，开始使用限速模式； 或者管理员对某用户设置了下载限速等。 120. 进入一个文件夹，右下角提示文件不存在。 导致这种情况的原因有多种，比如服务器硬盘满了，比如内存某时刻满了导致系统不正常了，网络问题也可能导致上述问题（如开启了VPN或翻墙工具），可以稍等一下再试，或者联系巴别鸟客服。 121. 怎么查看共享文件的实时在线编辑人员？ Office文件才可以多人同时在线编辑，打开在线编辑，右上角会显示出当前有几人实时在线，点击查看用户，显示当前正在编辑文件的用户。 122. 部门角色有上传文件的权限，在部门里的某个文件夹下不能上传文件，为什么？ 该文件夹做了文件访问控制，设置了某些用户或某些角色或者部门里的所有人不能上传文件。 123. 团队里的文件删除后，在谁的回收站里？ 团里里删除的文件在删除人和团队创建者的回收站里。如果是团队创建者删除文件，那么文件只在团队创建者的回收站里。如果是属于某个企业的用户删除团队里的文件，那么文件也只在团队创建者的回收站里。 124. 团队删除后，会保存在回收站里吗？ 团队删除后就直接删除了，并不会保存到回收站。 125. 巴别鸟支持私有化部署么？ 巴别鸟不仅可以在公有云以SAAS模式使用，同时也支持私有化部署。 巴别鸟私有化版本具有公有云版本的全部功能，同时还有自定义登录背景、自定义第三方平台对接、自定义使用模块等私有云独有功能。 126. 如何私有化部署巴别鸟系统？ 为了保证服务质量及私有化系统的运行稳定性，巴别鸟提供了用户全方位的私有化部署服务。所有的私有化系统都由巴别鸟工程师进行部署，用户只需按要求准备好适合巴别鸟私有化部署的服务器及相关硬件设备即可。我们也会根据用户的需求提供私有化部署的硬件方案，用户可自行采购硬件或使用现有服务器部署巴别鸟。同时，巴别鸟也支持部署在如华为云、阿里云、腾讯云等云服务上。 需要部署私有化巴别鸟系统，请联系我们的客服人员。电话：400 9204020 127. 巴别鸟支持对象存储么？ 考虑到性能及效率、可扩展性、安全性及性价比，巴别鸟推荐私有化用户使用对象存储进行部署。同时，巴别鸟团队也支持在复合要求的服务器上为客户搭建对象存储系统。这会比购买成套的对象存储设备节约不少预算，性价比更高。 128. 私有化部署巴别鸟系统需要什么硬件？ 根据管理的文件数量、使用的用户并发数不同，巴别鸟也有不同的硬件要求，这个需要根据具体需求进行估算。我们有免费的硬件需求评估及硬件搭建方案服务。可联系我们的客服人员了解详情。电话：400 9204020 129. 巴别鸟支持对接企业微信么？ 巴别鸟私有化版本支持对接企业微信、钉钉、飞书、OA、ERP、PDM...等第三方系统，以实现单点登录、用户及组织机构导入、第三方工作台使用巴别鸟、通知送达、手机H5访问....等多种功能。其中企业微信、钉钉、飞书为标准对接模块，私有云用户可以自行在企业控制台中进行配置。 130. 什么是智巢AI？ 智巢AI是巴别鸟团队推出的大模型企业助理模块。不仅能作为巴别鸟的AI客服解答用户在使用巴别鸟中遇到的问题，同时也可以使用企业存储于网盘的文件进行学习，成为你企业的专属AI助理，对于企业的相关资料及问题可以直接以提问的形式和智巢进行对话。并能根据不同权限的人给出权限范围内的回答。 譬如：把你所在企业常用的产品说明书、FAQ、客服文档交给智巢AI学习，经过巴别鸟AI团队微调后，智巢AI就可以成为你企业的专属客服，你的客户可以通过和智巢AI对话的方式获取关于你企业产品的信息，大幅节约客服成本。 131. 我也想要智巢AI助理，怎么操作？ 目前智巢AI要达到好的效果还需要巴别鸟AI团队针对你的需求和你提供的文档做微调及训练智巢AI，以达到好的效果。 所以，如果你也想拥有一个针对你行业及数据的专属AI助理，请联系我们客服人员。 132. 智巢AI收费吗？如何收费？ 是的，因为人工智能模型计算需要耗费大量GPU资源，同时也需要大量人力辅助AI对客户提供的文档进行学习，这些都是成本，所以智巢AI是收费的。 具体费用我们会根据用户的需求情况及实现目标进行估算。 133. 智巢AI可以私有化么？ 智巢AI可以私有化，但需要专用的GPU服务器以提供AI所需的算力。 134. 巴别鸟支持预览的文件格式有哪些？ 巴别鸟支持大多数常用文档的预览，同时支持所有类型文件的存储及客户端编辑。这里“支持的文件格式”特指是在巴比鸟上不借助第三方插件能打开预览的文件格式。 巴别鸟支持所有格式的上传下载及使用客户端打开。以下所列格式为不借助第三方应用可以在巴别鸟上直接预览的格式。 文本文件：txt，md office文件：doc，docx，ppt，pptx，xls，xlsx，wps，wpt，dps，rtf，dpt，et，ett 代码类：js，xml，htm，html，css，scss，jsp，c，cpp，java，php，m，h，hpp，mm 其他常用格式文件：Pdf，mail ，msg ，epub 可选支持：（需增加服务器） key，numbers，pages 音视频类：mp3，mp4， wav，asf，ape 可选支持：（可选项需要增加服务器及相应模块费用，可联系我们客服人员） flv，f4v，mp4，m4v，webm，3gp，3gpp，wmv，avi，rm，rmvb，mkv，asf，mov，mpeg，swf，mpg，mts，m2ts，ogv 3D图形类：Dae，fbx，obj，stl 可选支持：（可选项需要增加服务器及相应模块费用，可联系我们客服人员） x3d， ply，3ds，abc，m3d （可选支持 revit、soildworks、3DMax） 图片格式类：bmp，jpg，jpeg，gif，png，bmp，psd，tif，tiff，raw，cr2，arw，dng，nef，pef，dcm，ico 矢量图片类：ai，svg，eps，indd，indt，idml CAD类：dwg，dwt，dxf 压缩文件类： 可选支持：（可选项需要增加服务器及相应模块费用，可联系我们客服人员） rar, zip 135. 如何使用客户端匿名下载？ 匿名用户下载分享链接中的大文件，提示需要使用客户端下载时如何使用客户端下载？ 下载最新版本客户端，客户端登录界面下方有使用客户端访问分享链接按钮 。 点击此按钮，粘贴分享链接地址即可使用客户端下载文件。 136. 在巴别鸟上传了文件，过了一会儿文件自动删除了，怎么回事呢？ 巴别鸟不会自动删除文件的。这种情况很可能是有其他用户在使用一个比较旧的客户端同步了文件夹，由于某种特定条件触发了删除操作。在比较旧的客户端上有这个bug，在版本5.2上已经修复过，更新客户端即可。 137. 巴别鸟在手机浏览器上可以上传文件吗？ 根据使用场景的不同，手机浏览器是可以预览巴别鸟上的文件的，但不支持上传文件。 可以通过微信打开分享，上传文件。 138. 匿名用户可以上传文件吗？ 巴别鸟支持匿名用户上传文件，链接分享只要设置了允许匿名用户上传，拿到链接的匿名用户就是可以上传文件的。 139. 为什么不能在个人文件栏目上传文件？ 管理员在企业控制台把“默认允许用户上传个人私有文件”的开关按钮给关闭了，整个企业的用户都不能在个人文件栏目上传文件。 140. 可以在前台创建部门吗？ 超级管理员和安全保密员可以在前台任何一个部门下创建部门。运维管理者在自己所在的部门下可以创建部门。默认的部门经理的角色可以在自己部门下创建部门，其他角色中有“子部门管理”权限的部门人员也可以在自己部门下创建部门。 141. 批量上传文件有数量或大小限制吗？ 批量上传文件没有数量和大小的限制。如果是数量特别多，比如达到上万个文件，推荐使用巴别鸟客户端上传。 142. 注册登录的时候，收不到验证码（邮箱，手机）？ 注册时要求使用手机号注册的，需要短信验证码才能完成注册。收不到验证码时，再获取一次验证码，或者检查一下信息模块的拦截信息。如何还是没有验证码，可能是阿里云的短信模块出了问题，可等一段时间再试，或者联系我们的客户人员，我们会及时处理。 登录时可以使用账户密码方式，也可以使用短信验证码方式。如果收不到验证码，处理方式可参考注册时收不到验证码的处理方式。 需要邮箱验证码的情况是有分享或项目邀请了未注册巴别鸟的邮箱，此邮箱会收到一个邀请链接，打开链接，要求进行身份验证，会发送验证码到用户邮箱，此种情况基本上都可以收到验证码的，如果没有收到，可重发一次，或者检查一下垃圾箱。 143. 私有和公有有什么区别？ 巴别鸟私有版本是部署在用户自己的服务器上的，有企业独有的域名，独立的用户体系，有专属的UI界面，可设置登录页面背景图，上传、下载不限流量，可订制各种功能（如需要预览的文件格式），可与第三方平台对接（企业微信、钉钉、飞书、OA、ERP等），单个文件上传上限可自定义，可选择加密保护方式，按需无限定制存储空间，可在企业控制台设置需要使用的模块，支持文字水印、注册账户水印、图片水印的混合显示，支持工号模式登录，支持设置高强度密码。这些都是公有云版没有的。 144. 什么权限的人可以归档文件？ 对于个人私有的文件、文件夹、项目等，文件的创建者可以归档至档案库；对于部门内的文件/文件夹/项目，一般是部门经理权限的用户可以归档，更准确的说是有“部门文件管理”权限的用户可以归档部门内文件。 145. 电子签名是设置的哪个位置，是否可以手写？ 电子签名是在个人设置 签名设置处添加的。在右上角用户头像处点击倒置的三角按钮，打开设置弹框，在签名设置处可添加自己的电子签名。电子签名是通过鼠标画上去的。如果想手写，可以使用写字板等辅助硬件手写电子签名。电子签名的使用是在审批流程中，文件完成审批，定稿后，审批人可以插入自己的电子签名，在预览文件页面，点击鼠标右键，插入签名。插入的电子签名可以调整大小，改变位置，调整方向。 146. 怎么可以聊天？ 巴别鸟的聊天可以在讨论组里进行。团队、项目、部门都有自己的讨论组，团队成员、项目人员、部门里的人员都可以在讨论组频道看到所在团队、项目、部门的讨论组。讨论组里还支持发送文件。对于app，还可以在讨论组里发送语音。 147. 文件水印可以批量添加么？ 巴别鸟的水印是在企业控制台由管理员设置的，可以使用文字水印、注册账户水印、图片水印中的一种，私有云版本支持三种水印的叠加使用。水印可以设置使用范围：所有文件/所有对外分享文件/由文件分享者设定。在企业控制台设置好水印的相关信息后，范围内的所有文件上水印的显示就按设置的来。 148. 上传速度很慢，怎么回事？ 出现上传速度慢时有一下几种可能 网速比较慢； 同时有很多人在大批量上传文件，使得服务器内存占有量很大，cpu比较忙； 使用的翻墙工具或VPN抢占了网络资源。 149. 为什么邀请不了成员？ 团队可以邀请成员，团队邀请成员只能输入手机号，或者从常用联系人中添加。项目邀请成员可输入昵称、邮箱或手机号，匹配出用户时即可确定，注意：需要在项目信息框再一次点击确定按钮，才可邀请成功。项目添加成员时也可以从常用联系人、企业成员、外部人员及分组里选择，支持添加一个部门或一个分组到项目里。 映射盘无法同步？ 云端文件更新了但映射盘没有更新，或者更新了映射盘里的文件但云端没有更新。 有多种原因可能引发以上问题，可以通过以下方式排查： 检查映射盘缓存所在磁盘是否有空余空间。缓存所在目录可以点击客户端右上角“设置”按钮查看。如没有空余空间可在映射盘文件夹上右键“释放空间”按需清除缓存。 7.1.0版本后的客户端，检查不能同步的文件整个路径是否超过260个字符，包含整个路径名及文件夹名字，因为windows操作系统默认不允许路径超过260个字符。如果超过了，改短路径（重命名） 检查是否有在映射盘相应目录上传或下载文件的权限。最简单的方式是通过客户端访问映射盘对应的目录，上传或下载个文件尝试，如果没有权限，客户端会提示。 点击头像，退出当前账户，再次登录后尝试是否能正确同步。 重启计算机后尝试。 如以上方式均不能恢复映射盘同步，可联系巴别鸟客服，我们的工程师可以远程解决。 同步文件夹中一直显示惊叹号？ 同步文件夹中的文件显示惊叹号角标意味着本地文件和云端文件有版本冲突，一般会在同步再次扫描更新后自动解决冲突问题（修改时间最近的版本为当前版本），如果出现超过2小时还是惊叹号，可尝试以下操作： 点击头像，退出当前账户，再次登录后等待同步扫描完成，看是否还出现惊叹号。 在左边栏点击“同步”按钮，在同步任务列表找到相应的同步任务，右键“重置该同步” 手动查看云端的该文件版本和本地的该文件版本，确定你要的当前版本。如果你要的当前版本是云端版本，就在客户端上下载该文件，然后覆盖同步文件夹里的同名文件。如果你要的当前版本是本地版本，就在客户端找到文件所在目录，手动上传本地文件至该目录，选择“作为新版本上传”" }, { "lang": "zh", "slug": "for-ai", "title": "AI 读取指南", "description": "说明 AI、搜索引擎和 RAG 系统如何读取巴别鸟文档中心。", "category": "概况", "top_category": "维护", "keywords": [ "AI", "llms.txt", "RAG", "搜索引擎", "结构化索引" ], "url": "zh/for-ai.html", "source": "content/zh/for-ai.md", "summary": "AI 读取指南 本 wiki 的主要读者之一是 AI 系统，因此除了 HTML 页面，还提供 Markdown、JSON 和纯文本语料。 推荐读取顺序 1. 读取 llms.txt ，了解站点入口、页面清单和机器读取建议。 2. 读取 ai index.json ，获取每个页面的标题、分类、摘要、正文、图片和 Markdown 源文件路径。 3. 读取 llms full.txt ，作为 RAG、向量化或离线知识库的完整语料。 4. 开发者场景读取 developer api index.json ，获取 API 端点清单，再进入对应 API 页面。 5. 需要原文对照时读取 reference 页面，里面包含白皮书、FAQ、功能列表和 PDF 抽取文本。 文件类型说明 文件 用途 index.html 文档首页，直接显示中文概况 zh/ .html 中文完整文档 en/ .html 英文镜像文档 content/zh/ .md 中文 Markdown 源文档 content/en/ .md 英文 Markdown 源文档 llms.txt AI 入口清单 llms full.txt 全量 Markdown 语料 ai index.json 页面级结构化索引 developer api index.json API 端点结构化索引 image index.json 产品截图、白皮书图片和 FAQ 图片结构化索引 search index.json 前端搜索和站内搜索语料 sitemap.xml 搜索引擎抓取入口 语义和权限提醒 文档描述的是产品能力，不代表某个企业部署中所有模块", "headings": [ { "level": 1, "title": "AI 读取指南", "id": "ai" }, { "level": 2, "title": "推荐读取顺序", "id": "section" }, { "level": 2, "title": "文件类型说明", "id": "section-2" }, { "level": 2, "title": "语义和权限提醒", "id": "section-3" } ], "images": [], "text": "AI 读取指南 本 wiki 的主要读者之一是 AI 系统，因此除了 HTML 页面，还提供 Markdown、JSON 和纯文本语料。 推荐读取顺序 1. 读取 llms.txt ，了解站点入口、页面清单和机器读取建议。 2. 读取 ai index.json ，获取每个页面的标题、分类、摘要、正文、图片和 Markdown 源文件路径。 3. 读取 llms full.txt ，作为 RAG、向量化或离线知识库的完整语料。 4. 开发者场景读取 developer api index.json ，获取 API 端点清单，再进入对应 API 页面。 5. 需要原文对照时读取 reference 页面，里面包含白皮书、FAQ、功能列表和 PDF 抽取文本。 文件类型说明 文件 用途 index.html 文档首页，直接显示中文概况 zh/ .html 中文完整文档 en/ .html 英文镜像文档 content/zh/ .md 中文 Markdown 源文档 content/en/ .md 英文 Markdown 源文档 llms.txt AI 入口清单 llms full.txt 全量 Markdown 语料 ai index.json 页面级结构化索引 developer api index.json API 端点结构化索引 image index.json 产品截图、白皮书图片和 FAQ 图片结构化索引 search index.json 前端搜索和站内搜索语料 sitemap.xml 搜索引擎抓取入口 语义和权限提醒 文档描述的是产品能力，不代表某个企业部署中所有模块都已开启。私有化部署、智巢 AI、文控项目、第三方集成、短信、在线 Office、签章等功能可能受版本、授权、部署模块或企业配置影响。AI 回答具体客户问题时，应提示用户以实际部署配置和管理员策略为准。" }, { "lang": "zh", "slug": "reference-whitepaper", "title": "白皮书参考入口", "description": "按白皮书原章节拆分的参考资料入口。", "category": "源资料参考", "top_category": "维护", "keywords": [ "白皮书", "参考资料" ], "url": "zh/reference-whitepaper.html", "source": "content/zh/reference-whitepaper.md", "summary": "白皮书参考入口 以下页面按《巴别鸟企业网盘白皮书》的一级章节拆分，便于全文检索和原文对照。 白皮书：概述 白皮书：系统架构 白皮书：预览及转码 白皮书：安全性 白皮书：主要功能模块 白皮书：用户界面 白皮书：性能优化 白皮书：可扩展性 白皮书：私有化部署 白皮书：附件1:巴别鸟功能列表 白皮书：附件2:巴别鸟开放API（基础API）", "headings": [ { "level": 1, "title": "白皮书参考入口", "id": "section" } ], "images": [], "text": "白皮书参考入口 以下页面按《巴别鸟企业网盘白皮书》的一级章节拆分，便于全文检索和原文对照。 白皮书：概述 白皮书：系统架构 白皮书：预览及转码 白皮书：安全性 白皮书：主要功能模块 白皮书：用户界面 白皮书：性能优化 白皮书：可扩展性 白皮书：私有化部署 白皮书：附件1:巴别鸟功能列表 白皮书：附件2:巴别鸟开放API（基础API）" }, { "lang": "zh", "slug": "reference-whitepaper-01-overview", "title": "白皮书：概述", "description": "《巴别鸟企业网盘白皮书》章节：概述。", "category": "源资料参考", "top_category": "维护", "keywords": [ "白皮书", "概述" ], "url": "zh/reference-whitepaper-01-overview.html", "source": "content/zh/reference-whitepaper-01-overview.md", "summary": "白皮书：概述 巴别鸟简介 巴别鸟是上海画擎信息科技有限公司的注册商标及主要产品，上海画擎成立于2012年，总部位于上海，2016年于北京设立分公司。画擎科技是一个以技术为主导的团队，创始人均来自北大方正，拥有极强的图形图像处理和云计算技术并专注于安全存储及办公协作系统的研发。目前，巴别鸟已经完成了B轮融资，用户数超过80万，文档数据量已突破100PB。 图形图像和云计算领域的孜孜耕耘，高效工作方式的不懈探索，以及对产品用户体验的极致追求，造就了巴别鸟文档管理及协作平台。你可以用巴别鸟解决 企业文件统一管理、协同协作、数据安全 三大问题，大幅提高企业工作效率及数据安全性。 巴别鸟功能列表 详见文末附件1《巴别鸟功能列表》", "headings": [ { "level": 1, "title": "白皮书：概述", "id": "section" } ], "images": [], "text": "白皮书：概述 巴别鸟简介 巴别鸟是上海画擎信息科技有限公司的注册商标及主要产品，上海画擎成立于2012年，总部位于上海，2016年于北京设立分公司。画擎科技是一个以技术为主导的团队，创始人均来自北大方正，拥有极强的图形图像处理和云计算技术并专注于安全存储及办公协作系统的研发。目前，巴别鸟已经完成了B轮融资，用户数超过80万，文档数据量已突破100PB。 图形图像和云计算领域的孜孜耕耘，高效工作方式的不懈探索，以及对产品用户体验的极致追求，造就了巴别鸟文档管理及协作平台。你可以用巴别鸟解决 企业文件统一管理、协同协作、数据安全 三大问题，大幅提高企业工作效率及数据安全性。 巴别鸟功能列表 详见文末附件1《巴别鸟功能列表》" }, { "lang": "zh", "slug": "reference-whitepaper-02-architecture", "title": "白皮书：系统架构", "description": "《巴别鸟企业网盘白皮书》章节：系统架构。", "category": "源资料参考", "top_category": "维护", "keywords": [ "白皮书", "系统架构" ], "url": "zh/reference-whitepaper-02-architecture.html", "source": "content/zh/reference-whitepaper-02-architecture.md", "summary": "白皮书：系统架构 架构概述 前端架构 前端架构包括以下关键组件和技术： 主架构选择了backbone.js，它提供了组件化开发、状态管理和路由控制等功能。又在其基础上引入了Gulp、Babel、browserify、Scss、jQuery、underscore、ES6等用以构建可维护和高性能的前端应用程序。 使用了WebSocket协议和后台进行消息的即时通讯。 设计了风格统一、用户友好、直观的界面，包括搜索、文件夹管理、文件预览等功能。 网站支持全平台预览，使用了CSS媒体查询和移动优化技术创建响应式布局，以确保网盘产品在不同设备上具备一致的外观和功能。 考虑多语言支持，目前系统支持中、英文两种语言，可在界面随时切换，也能通过浏览器语言进行切换。 采用了代码分割、懒加载、资源压缩和CDN加速等前端性能优化技术，以提高页面加载速度和响应时间。 实施前端安全性最佳实践，包括XSS（跨站脚本攻击）和CSRF（跨站请求伪造）防护。确保数据传输加密和安全存储。 跨平台和多语言： 巴别鸟系统前端部分包含了：巴别鸟iOS版（iPhone、iPad）、巴别鸟安卓版、巴别鸟web版、巴别鸟微信版（H5），巴别鸟mac客户端，巴别鸟windows客户端、巴别鸟Linux（麒麟）客户端。 原生iOS客户端使用Object C和Swift开发。 原生安卓客户端、鸿蒙使用Java开发（Android studio）。 windows、mac、麒麟 客户端使用Electron及C++进行开发，包含 客户端界面、同步端、传输管理、映射盘四个组件。 后端架构 服务器拓扑结构 巴别鸟的后端架构主要负责业务逻辑", "headings": [ { "level": 1, "title": "白皮书：系统架构", "id": "section" } ], "images": [], "text": "白皮书：系统架构 架构概述 前端架构 前端架构包括以下关键组件和技术： 主架构选择了backbone.js，它提供了组件化开发、状态管理和路由控制等功能。又在其基础上引入了Gulp、Babel、browserify、Scss、jQuery、underscore、ES6等用以构建可维护和高性能的前端应用程序。 使用了WebSocket协议和后台进行消息的即时通讯。 设计了风格统一、用户友好、直观的界面，包括搜索、文件夹管理、文件预览等功能。 网站支持全平台预览，使用了CSS媒体查询和移动优化技术创建响应式布局，以确保网盘产品在不同设备上具备一致的外观和功能。 考虑多语言支持，目前系统支持中、英文两种语言，可在界面随时切换，也能通过浏览器语言进行切换。 采用了代码分割、懒加载、资源压缩和CDN加速等前端性能优化技术，以提高页面加载速度和响应时间。 实施前端安全性最佳实践，包括XSS（跨站脚本攻击）和CSRF（跨站请求伪造）防护。确保数据传输加密和安全存储。 跨平台和多语言： 巴别鸟系统前端部分包含了：巴别鸟iOS版（iPhone、iPad）、巴别鸟安卓版、巴别鸟web版、巴别鸟微信版（H5），巴别鸟mac客户端，巴别鸟windows客户端、巴别鸟Linux（麒麟）客户端。 原生iOS客户端使用Object C和Swift开发。 原生安卓客户端、鸿蒙使用Java开发（Android studio）。 windows、mac、麒麟 客户端使用Electron及C++进行开发，包含 客户端界面、同步端、传输管理、映射盘四个组件。 后端架构 服务器拓扑结构 巴别鸟的后端架构主要负责业务逻辑、数据处理和与前端的交互。它满足了以下关键目标： 模块化设计: 后端采用了模块化的设计，以便将不同功能和业务逻辑划分为独立的模块。这有助于代码的可维护性和可扩展性。 性能: 巴别鸟后端具有良好的性能，能够处理大规模的文件上传、下载、搜索和协作请求。采用了适当的负载均衡及缓存策略和优化技术以提高响应时间。 安全性: 巴别鸟后端重点强化安全性，包括用户身份验证、授权、数据加密和防御性编程，以保护用户数据免受攻击。 可扩展性: 巴别鸟后端架构具备可扩展性，以适应未来的业务需求和新功能的添加。采用了SOA服务架构和模块化组件设计，以支持功能的灵活扩展。 数据管理: 巴别鸟后端有效地管理了用户数据、文件数据和元数据。这包括数据库设计、备份策略和数据清理。 框架选择 巴别鸟采用了松散的、面向服务的架构模式。不同的服务，其设计、开发、部署都是独立的，这样就确保了系统的稳定性和可扩展性。最终，我们会采用docker把这些服务容器化，进行统一的管理和部署。 对于逻辑简单、高频访问的服务，我们选择Nodejs及相应的开发框架。 对于逻辑复杂、低消耗的服务，我们会选择Struts2+Spring框架。 对于逻辑复杂、且高消耗(比如MD5计算、文件分块、加密)的服务，我们会选用Rust语言进行开发。 数据层 数据库: 巴别鸟选择了MySQL作为数据库管理系统，也支持使用其他数据库（可按需支持 高斯、PostgreSQL、Oracle） 同时，巴别采用ORM（对象关系映射）: 使用ORM框架（Hibernate）将数据库表映射到Java对象，以简化数据访问和持久化。 安全性 用户身份验证: 使用强大的用户身份验证机制，包括单一登录（SSO）、OAuth认证和多因素认证（MFA）。 授权: 使用Spring Security等授权框架来定义和强制访问控制策略，确保用户只能访问其授权的资源。 数据加密: 实施数据传输和存储的加密，以保护用户数据的安全性。 业务逻辑 文件管理: 开发了业务逻辑来处理文件上传、下载、版本控制、共享和协作功能。 用户管理: 实施用户管理、权限管理和用户组织结构。 搜索功能: 开发了高效的搜索引擎，支持文件和元数据的快速检索。 在线编辑：负责文件的在线编辑、协同编辑。 文件转码：负责文件的批量排队转码，生成预览文件。 对象存储：文件的分块及落盘，存储系统管理。 Web服务 RESTful API: 使用RESTful API，以支持前端和其他客户端的数据交互和协作。 缓存管理 缓存策略: 使用缓存来提高性能，包括页面缓存、数据缓存和会话缓存。 异步任务处理 消息队列: 使用消息队列系统RabbitMQ来处理异步任务，如文件转码、文件预览生成等。 通过采用Struts2和Spring框架，结合以上设计考虑，可以构建一个强大、高性能、安全可靠的企业网盘后端系统，满足用户的需求并支持未来的扩展和功能添加。 云基础设施选择（公有云 SAAS版本巴别鸟） 公有云基础设施选择可以直接影响到企业网盘产品的性能、可靠性和安全性。巴别鸟公有云版本经过多方对比，选择了阿里云的ECS、OSS服务以及CDN分发业务。目前（2023年）公有云SAAS模式运行的巴别鸟系统已经0服务器故障在线运作了超过10年。 云服务提供商选择 业务服务器SAAS版本巴别鸟使用了阿里云的ECS（云服务器）集群 阿里云的ECS是一种弹性计算服务，为你提供了虚拟机实例，使你能够在云中运行应用程序。这些是选择ECS的一些关键优势： 灵活性: ECS允许你根据需要创建、启动和停止虚拟机实例。这意味着你可以根据流量需求来扩展或缩减计算资源。 可扩展性: 阿里云提供了多种不同规格的ECS实例，以满足不同工作负载的需求。你可以根据应用程序的性能要求进行选择。 可靠性: 阿里云的ECS实例通常具有高可用性，提供了多个数据中心和可用区，以确保业务连续性。 安全性: 阿里云提供了各种安全性功能，包括网络隔离、防火墙和安全组，以帮助你保护你的虚拟机实例免受恶意攻击。 对象存储SAAS版本巴别鸟使用了阿里云的OSS（对象存储服务） 阿里云的OSS是一种高度可扩展、安全可靠的云存储服务，适用于存储和管理大量的文件和数据。以下是选择OSS的一些优势： 可扩展的存储: OSS提供了可扩展的存储容量，可以根据你的需要进行动态扩展。这对于企业网盘产品中的文件存储非常重要。 数据备份和恢复: 阿里云的OSS具有数据备份和版本控制功能，可以帮助你保护数据免受丢失或损坏。 安全性: 数据存储在OSS中通常会受到加密和访问控制的保护，以确保数据的安全性。 CDN整合: 与CDN服务集成，可以提高文件的分发速度和用户体验。 为确保全球各地的访问通畅，巴别鸟也使用了CDN分发 CDN（内容分发网络）服务是将内容缓存到全球分布的边缘节点，以降低加载时间并提高用户体验。阿里云的CDN服务可以为企业网盘产品带来以下好处： 快速分发: 加速文件的分发，确保用户能够快速访问和下载文件，不受地理位置的限制。 负载均衡: CDN可以帮助分担服务器的负载，降低服务器的压力，提高网站的性能。 安全性: CDN服务通常具有DDoS攻击防护功能，可保护网站免受恶意攻击。 全球覆盖: 阿里云的CDN服务具有全球性覆盖，可确保你的内容快速传递给全球用户。 数据中心地理位置 目前巴别鸟使用了阿里云的两个数据中心： 杭州数据中心 及 威海数据中心 一南一北的配置能保证服务的可持续性及灾备需求。 数据库设计 数据库类型 巴别鸟企业网盘采用了多种类型的数据库，同时也可根据客户需求支持信创的数据库产品或是Oracle等大型数据库。 巴别鸟默认的产品数据库为： 核心数据库为关系型数据库 mysql 辅助数据库有：Redis 数据库，MongoDB 数据库 数据库架构 数据架构在企业网盘系统中扮演着至关重要的角色，确保了数据的高可用性、性能和一致性。下面是巴别鸟的数据库架构： A. 主从数据库架构 主库（Master） 主库负责处理写入操作，包括用户上传文件、修改文件信息等。 主库提供高可用性、数据一致性和事务处理。 从库（Slave） 从库主要用于读取操作，包括文件的查询、搜索等。 从库可以提供负载均衡，分担主库的读取负载。 数据同步：采用数据复制机制确保从库与主库的数据保持同步。 故障转移：从库可以在主库故障时接管写入操作，确保系统的连续性。 B. 关系型数据库（MySQL） 数据库设计 数据库设计以支持文件和用户管理，包括文件元数据、用户信息、权限等表的定义。 数据表之间的关系清晰，使用外键来维护数据一致性。 数据冗余 主从架构中的从库用于数据冗余，以防止主库故障时的数据丢失。 数据同步机制确保从库的数据与主库保持一致。 C. NoSQL数据库（MongoDB） 文件元数据存储 MongoDB可用于存储文件的元数据，如文件名、大小、版本信息等。 具有弹性模式的MongoDB适用于不断变化的数据模式。 D. 缓存数据库（Redis） 缓存读取数据 Redis用于缓存频繁读取的数据，以减轻数据库的负载。 缓存的数据可以包括用户会话信息、热门文件、访问日志等。 E. 数据备份和恢复 备份策略 定期备份主库和从库的数据，以确保数据的安全性。 巴别鸟备份数据存储在不同地理位置的可靠存储中。 灾难恢复 我们制定详实的恢复计划，包括从备份中还原数据的步骤和时间表。 巴别鸟运维团队会定期测试灾难恢复过程以确保其有效性。 F. 数据一致性和事务管理 事务支持 使用数据库事务来确保一系列操作的一致性，如文件上传、共享和权限更改。 事务应该被正确地管理，以避免数据损坏和不一致性。 并发控制 使用数据库锁和隔离级别来管理并发访问，以避免数据竞争和冲突。 G. 监控和性能优化 性能监控 实施数据库性能监控，包括查询响应时间、负载和资源利用率。 根据监控结果进行性能调整，以确保数据库的稳定性和性能。 查询优化 优化复杂查询以提高查询性能，包括索引优化和查询计划分析。 这些数据架构的元素将有助于确保你的企业网盘系统能够具备高可用性、性能卓越和数据的安全性。通过合理的数据库设计和维护，你可以提供稳定可靠的服务，满足用户需求并确保数据的完整性。 数据备份和恢复策略（公有云） A. 数据备份 定期备份计划：巴别鸟有定期的备份计划，以确保数据的连续备份（每日凌晨数据备份）。 完整备份和增量备份：巴别鸟采用完整备份和增量备份的组合策略。完整备份将数据库的全部数据备份，而增量备份仅备份自上次备份以来发生更改的数据，以减少备份时间和存储空间的消耗。 多备份位置：公有云版本巴别鸟有杭州机房及威海机房两个地理位置，以应对自然灾害或硬件故障。云存储和远程数据中心是常见的备份存储选择。 自动化备份：巴别鸟的数据库备份采用全自动备份机制，无需人工干预，以提高可靠性。 备份测试：我们会定期测试备份以确保其完整性和可用性。通过还原备份数据到测试环境中并验证数据的一致性来进行测试。 B. 灾难恢复 恢复计划：我们建立了详细的恢复计划，明确每个步骤和责任。确保团队成员了解如何执行恢复过程。 备份恢复测试：我们会定期测试备份恢复过程，以确保在紧急情况下能够迅速有效地还原数据。测试应包括各种故障场景的模拟。 备份监控：监控备份任务的运行情况，出现问题会自动提醒及报错，确保备份系统正常运行。 灾难恢复团队：我们有专门的灾难恢复团队，7 24小时待命，负责在紧急情况下采取行动，确保业务的持续运行。 通信计划：我们建立了有效的通信计划，及自动告警信息送达监控，以通知相关利益相关者有关灾难事件和恢复过程的信息。 文档和培训：确保恢复计划和过程的详细文档，并为团队成员提供培训，使其了解恢复策略和步骤。 以上策略和努力立足于确保数据库数据的安全性和可用性，并最大程度地减少数据丢失和系统停机的风险。" }, { "lang": "zh", "slug": "reference-whitepaper-03-preview-transcoding", "title": "白皮书：预览及转码", "description": "《巴别鸟企业网盘白皮书》章节：预览及转码。", "category": "源资料参考", "top_category": "维护", "keywords": [ "白皮书", "预览及转码" ], "url": "zh/reference-whitepaper-03-preview-transcoding.html", "source": "content/zh/reference-whitepaper-03-preview-transcoding.md", "summary": "白皮书：预览及转码 文件预览功能能让用户无需安装应用程序就能直接在网盘上直接打开文件进行预览，为了能在网页端及客户端上预览文件及保证文件在只读状态下的安全性（不被人获取内容或源文件），文件预览和转码是企业网盘系统的核心功能之一。这章将介绍巴别鸟如何实现文件的在线预览和转码，以提供更便捷的用户体验。 支持在线预览的文件类型 文本、代码及office文件： Pdf，md，js，xml，htm，html，css，scss，jsp，c，cpp，java，php，m，h，hpp，mm， mail ，msg ，epub，doc，docx，ppt，pptx，xls，xlsx，txt，rtf，wps，wpt，dps，dpt，et，ett Xmind，km 可选支持：（可选项需要增加服务器及相应模块费用） key，numbers，pages 音视频： mp3，mp4， wav，asf，ape 可选支持：（可选项需要增加服务器及相应模块费用） flv，f4v，mp4，m4v，webm，3gp，3gpp，wmv，avi，rm，rmvb，mkv，asf，mov，mpeg，swf，mpg，mts，m2ts，ogv 3D图形： dae、3ds、abc、fbx、mtl、obj、ply、stl、x3d 可选支持1：（可选项需要增加服务器及相应模块费用） x3d， ply，3ds，abc，m3d 可选支持2: revit、soildworks、3DMax 图片格式： bmp，jpg，jpeg，gif，png，bmp，psd，tif，tiff，raw，cr2，arw，dng，nef，pef，dcm，ico dic", "headings": [ { "level": 1, "title": "白皮书：预览及转码", "id": "section" }, { "level": 3, "title": "性能优化", "id": "section-2" } ], "images": [], "text": "白皮书：预览及转码 文件预览功能能让用户无需安装应用程序就能直接在网盘上直接打开文件进行预览，为了能在网页端及客户端上预览文件及保证文件在只读状态下的安全性（不被人获取内容或源文件），文件预览和转码是企业网盘系统的核心功能之一。这章将介绍巴别鸟如何实现文件的在线预览和转码，以提供更便捷的用户体验。 支持在线预览的文件类型 文本、代码及office文件： Pdf，md，js，xml，htm，html，css，scss，jsp，c，cpp，java，php，m，h，hpp，mm， mail ，msg ，epub，doc，docx，ppt，pptx，xls，xlsx，txt，rtf，wps，wpt，dps，dpt，et，ett Xmind，km 可选支持：（可选项需要增加服务器及相应模块费用） key，numbers，pages 音视频： mp3，mp4， wav，asf，ape 可选支持：（可选项需要增加服务器及相应模块费用） flv，f4v，mp4，m4v，webm，3gp，3gpp，wmv，avi，rm，rmvb，mkv，asf，mov，mpeg，swf，mpg，mts，m2ts，ogv 3D图形： dae、3ds、abc、fbx、mtl、obj、ply、stl、x3d 可选支持1：（可选项需要增加服务器及相应模块费用） x3d， ply，3ds，abc，m3d 可选支持2: revit、soildworks、3DMax 图片格式： bmp，jpg，jpeg，gif，png，bmp，psd，tif，tiff，raw，cr2，arw，dng，nef，pef，dcm，ico dicom（医疗图像） 矢量图片： ai，svg，eps，indd，indt，idml CAD dwg，dwt，dxf，dcm 压缩文件： 可选支持： rar, zip 在线预览工具（巴别鸟预览器） 巴别鸟企业网盘使用了自主研发的BabelViewer在线预览工具进行在线预览，支持不同文件转码后统一预览。允许用户查看文件内容，而无需下载到本地。 BabelViewer是针对企业网盘用户需求开发的强大的H5在线预览工具，有如下特性： 支持多个库，以便于多种方式渲染预览文件。 支持多图层技术，可以在预览文件上进行多人绘制。 支持在线批注，并可以在批注区内多人讨论。 可展开批注列表统一管理当前版本及历史版本的批注。 支持多种文件的版本对比。 矢量化的渲染，矢量文件可以高倍率放大不失真。 可以在预览状态下快速切换预览多个文件。 使用webGL技术支持3D文件的在线渲染，也支持3D文件的在线批注。 文件转码功能 转码工具： 巴别鸟转码服务集成了多个转码工具，以将文件从一种格式转换为另一种支持巴别鸟预览器打开的格式。私有部署系统需要一台专用的服务器（或虚拟机）来来处理文件的转码。 例如，将高分辨率图片转换为Web友好的JPEG格式。 自动转码： 巴别鸟实现了自动转码功能，用户上传的文件会自动转换为适当的格式并抽取文件列表缩略图，以节省存储空间和提高性能。针对大量文件同时上传的转码处理，巴别鸟有一套独特的调度机制，力求在有限的资源占用下让用户打开预览更及时。 服务器空闲时用户文件上传即刻自动转码，生成预览文件。 服务器繁忙时，如果用户同时上传的文件超过一定数量，这些文件将不会进行转码，当用户点击文件准备预览时，优先加入到转码进程，实时生成预览文件。 因为用户一次性上传大量文件后要马上预览的概率很低，这样的设定可以防止用户同时大量上传文件时因服务器繁忙造成真正需要转码的文件打不开的情况。 转码队列和异步处理： 将转码任务加入队列，并使用异步处理方式来执行转码操作，以避免阻塞其他系统功能。 缓存和性能优化 预览和转码缓存： 实施缓存机制，以存储已转码的文件和预览数据，以减少重复转码和提高响应速度。 负载均衡： 同时转码队列配置了负载均衡策略，以确保多个预览和转码请求能够平衡地分配到不同的处理节点。 性能优化 性能监控： 实时性能监控，包括转码速度、缓存命中率和响应时间，出错自动清空队列重试处理。严重错误短信通知运维人员。 资源调整： 根据监控结果和负载情况，动态调整预览和转码资源，以确保高性能和可用性。 集成测试 性能测试： 进行性能测试，模拟大量并发预览和转码请求，以评估系统在高负载下的表现。 office家族文件 巴别鸟支持微软office家族及WPS的文件的在线预览，为确保office文件特别是word文件的显示准确性，巴别鸟提供了2种office文件的预览方式： 使用运行于Windows服务器的office转码模块把文件转码后进行预览（默认）。 需要部署一台window服务器生成预览文件。 可以相当准确的与微软office或WPS打开无差别的预览word类文件和ppt类文件。 支持使用巴别鸟预览器(BabelViewer)对文件进行批注讨论、圈画及版本对比。 可使用“智巢AI”文档助理功能。 Excel文件因没有版式和字体问题，都使用在线office的预览功能进行预览。 所有的预览文件都可以内嵌水印，并可另存为带水印的PDF文件。 使用运行于Linux服务器的在线office的预览功能提供office及wps文件的在线预览。 针对只能使用Linux，并且对word文件预览版式准确度没有较高要求的用户。 因系统字体差异，在线office解析等原因，在Linux系统中的在线office并不能1：1完美显示word文件的版式，在譬如：项目符号编号、段落高度、分页、插入图形位置等方面会有少许差异。 Excel文件因没有版式和字体问题，都使用在线office的预览功能进行预览。 使用在线office预览功能打开的word类和ppt类文件将不再支持巴别鸟预览器的批注功能。 不支持使用“智巢AI”的文档助理功能。 所有的预览文件都可以内嵌水印，并可另存为带水印的PDF文件。 考虑到浏览器的性能及服务器的效率，在线预览office文件会有一定的文件尺寸大小限制，超过这个限制的文件就无法在线预览。私有云用户可以自定义这些限制，但不建议调过大。 Word（文档）类文档最大可预览文件大小为 200MB。 PPT（幻灯片）类文档最大可预览大小为 200MB。 Excel（表格）类文档最大可预览大小为 50MB。 图片及图形文件 巴别鸟支持绝大多数图片文件的在线预览，包括psd、gif家族、jpg家族、bmp家族、png、raw家族（部分）、arw、tif、TIFF、dicom、ico等文件，同时也支持医学图形常用的dicom格式。并且得益于巴别鸟强大的图片处理技术，巴别鸟可以以1：1的方式在线预览超高分辨率的大图（可选组件），并且在图片上批注讨论，并且巴别鸟支持读取照片的元数据。 PSD、RAW、BMP等图片格式需要服务器自动转码后才能预览。 通常情况下（没有开启大图显示模块）超过4K分辨率的大图片将会被服务器处理成便于网页展示的尺寸及格式。开启大图显示模块后，服务器将把大图切割成若干小块，分块载入1：1显示，这将耗费较大服务器资源。 PNG等透明背景的图在巴别鸟中也能显示出透明度，并且可以更改背景。 巴别鸟系统会读取图片元数据信息，供搜索、查询、排序。这些信息包括：分辨率、尺寸、拍摄设备、拍摄时间、拍摄地点。 所有可预览图片格式都会生成缩略图，供文件列表展示快速查找及瀑布流模式展示。 所有图片格式都支持在巴别鸟预览器(BabelViewer)中批注讨论、圈画及版本对比。 如开启水印功能，服务器将会对预览的图片进行预处理，在图片中嵌入水印。 所有图片类文件都可以另存为带水印的PDF文件。 巴别鸟也能很好的支持矢量图形的在线预览，包括但不限于ai、dwg、dcm、dxf 、dwt 、pdf、eps、svg、idml、indd…等矢量图形格式。更重要的是，巴别鸟能以矢量渲染的方式打开这些格式的文档，这意味着这类图形可以在巴别鸟中放大几十倍也不会模糊或失真。 AI、eps、indd等文件需要服务器自动转码后才能预览。 以矢量的方式显示，支持更改背景颜色。 放大后图形不会失真或模糊。 其他特性和图片一致，同样支持嵌入水印、另存为带水印PDF、在巴别鸟预览器(BabelViewer)中批注讨论、圈画及版本对比、生成文件列表预览图。 3D及CAD文件 得益于巴别鸟预览器(BabelViewer)对3D格式的支持，我们默认支持dae、3ds、abc、fbx、mtl、obj、ply、stl、x3d等3D图形的在线预览，并且支持在3D空间中的批注讨论。 目前，巴别鸟预览器仅支持单个文件3D图形，如果文件有外挂皮肤等外挂文件将只能载入模型本体。 3D文件目前还不支持生成预览图，但如果有这方面需求支持定制开发。 3D文件可以在巴别鸟预览器中旋转、放大、缩小、拆分，并可以建立批注讨论点，系统会记住建立批注时的视口，点击批注会自动旋转到建立批注时的视角。 如需对revit、soildworks、3DMax等专业格式进行支持，私有化部署用户可以选择接入第三方3D在线显示及转码插件，（如：Autodesk viewer）这会产生相关费用。 目前不支持在移动设备预览3D文件。仅支持在网页及客户端预览3D文件。 巴别鸟支持对CAD文件的预览。如: dwg，dwt，dxf 格式，目前在公有云上，巴别鸟向专业版及企业版用户提供强大的CAD预览服务，私有化用户想要预览CAD文件需要购买相应的CAD转码服务私有化授权。 巴别鸟CAD预览支持CAD版本R12 2021。 CAD文件可生成预览缩略图，用于文件列表及瀑布流模式。 兼容天正全专业T20V7版本。 支持在浏览器、客户端、移动端预览及批注CAD文件。 支持百兆以上图纸浏览。 图层打开/隐藏/多选/全选。 布局切换、视图平移、缩放、更改背景颜色、鹰眼鸟瞰视图。 音视频转码 不使用转码服务器的情况下 巴别鸟无须转码服务就可以直接在线播放支持HTML5标准的视频文件。 支持的格式如下： 视频文件格式 MP4：MPEG 4 Part 14，支持H.264编码。几乎所有的浏览器都支持该格式。 WebM：谷歌开发的格式，使用VP8或VP9编码，可以在大多数现代浏览器中播放 Ogg：开放媒体格式，使用Vorbis编码，可以在大多数现代浏览器中播放。 音频文件格式 MP3：MPEG 1或MPEG 2 Audio Layer III，可以在几乎所有的浏览器中播放。 AAC：Advanced Audio Coding，可以在大多数现代浏览器中播放。 Ogg：开放媒体格式，使用Vorbis编码，可以在大多数现代浏览器中播放。 WAV：Waveform Audio File Format，可以在几乎所有的浏览器中播放，但文件较大，不适合在网络上播放。 兼容性 视频兼容性 音频兼容性 使用转码服务器的情况下 如果需要使用巴别鸟管理查询大量视频素材，就需要搭建专用的视频转码服务器，并购买相应的视频转码模块授权。（目前此服务仅支持私有化部署用户） 巴别鸟视频转码模块采用FFmpeg解决方案，FFmpeg 支持 MPEG、 DivX、MPEG4、AC3、DV、FLV 等40多种编码，AVI、MPEG、OGG、Matroska、ASF 等90多种解码，FFmpeg 支持的编解码器种类共有 280 多种， 涵盖了几乎所有常见音视频编码格式， 能解码几乎所有的音视频。 视频转码服务器所需硬件配置 视频转码是一个相当耗费运算资源的服务，需要一台专门的物理机来执行转码操作。同时服务器性能要求和需要转码的视频类型，时长和码率都有关系。 按每天转换累计时长50小时的HDR 4K视频（使用CUDA）为1080P H.264 AC3 MP4为基准，所需的服务器硬件配置如下： 服务器类型 配置要求 操作系统 服务器用途 备注 视频转码服务器 至强Intel E5 2630v3CPU 2 64G内存 2TB SSD硬盘 + Nvidia Tesla M4 4G显卡 Linux 视频转码服务器 使用GPU（CUDA） 根据视频码率不同所需转码时间也不同，在通常情况下，一个100秒的2K视频转码成1080P MP4耗时为8秒（使用上文硬件配置），如果同时转码的视频多，服务器则会做多线程排队处理。 使用转码服务器后，视频文件转码完成后即可播放，并且可以在文件列表查看缩略图。" }, { "lang": "zh", "slug": "reference-whitepaper-04-security", "title": "白皮书：安全性", "description": "《巴别鸟企业网盘白皮书》章节：安全性。", "category": "源资料参考", "top_category": "维护", "keywords": [ "白皮书", "安全性" ], "url": "zh/reference-whitepaper-04-security.html", "source": "content/zh/reference-whitepaper-04-security.md", "summary": "白皮书：安全性 安全的架构 安全是业务的关键！巴别鸟从产品设计到架构搭建及服务器管理都优先考虑安全性，并且包含了许多重要的安全功能。您可以控制每个文件及每位成员的访问行为、添加文件水印、查看访问日志、重要文件归入档案库、给文件及部门设立加密等级及安全策略….这一系列举措可以最大限度保护重要数字资产。同时，巴别鸟使用了安全等级最高的EV SSL认证，银行级的加密传输，多机房分布式备份，确保你的数据安全无忧。这些举措使巴别鸟获得了QUALYS安全性A+认证，同时我们也拥有ISO27001信息安全质量体系认证。 巴别鸟从上线开始就实现了从上传、下载、到落盘的全链路的加密传输和存储，配合权限管理及文件管理的细节处理，以及各种使用场景所遇到的风险分析及相应的功能应对策略，使巴别鸟成为了市面上最安全的企业网盘之一。 图：巴别鸟数据传输链路 防火墙、堡垒机、VPN、SSL….在传输和服务器部署架构上我们有越来越多的手段保证系统的数据安全性。但是根据我们多年从事企业安全服务的经验来看，80%数据泄露事件往往来源于内部人员泄露及管理混乱。即使系统做到了物理隔离，也没办法杜绝数据泄露风险。巴别鸟从产品设计之初就考虑到了这一点，从管理、人员和设备的角度提供了多种安全设计及功能。在易用性和安全性的矛盾之处也提供了多种可选设置及方案。从产品结构和使用逻辑上尽可能保证数据安全性。大幅消除因内部人员疏忽或破坏产生的数据泄露风险。 用户身份验证和授权（SSO） 自有用户体系 巴别鸟自由用户体系身份验证种类 账号类型 验证方式 备注 邮箱 密码、验证码 公有云需绑定手机号验证 手机号（全球） 密码、验证码 私有", "headings": [ { "level": 1, "title": "白皮书：安全性", "id": "section" }, { "level": 3, "title": "安全的架构", "id": "section-2" }, { "level": 3, "title": "用户身份验证和授权（SSO）", "id": "sso" }, { "level": 3, "title": "用户体验", "id": "section-3" }, { "level": 3, "title": "概述", "id": "section-4" }, { "level": 3, "title": "概述", "id": "section-5" }, { "level": 3, "title": "概述", "id": "section-6" } ], "images": [], "text": "白皮书：安全性 安全的架构 安全是业务的关键！巴别鸟从产品设计到架构搭建及服务器管理都优先考虑安全性，并且包含了许多重要的安全功能。您可以控制每个文件及每位成员的访问行为、添加文件水印、查看访问日志、重要文件归入档案库、给文件及部门设立加密等级及安全策略….这一系列举措可以最大限度保护重要数字资产。同时，巴别鸟使用了安全等级最高的EV SSL认证，银行级的加密传输，多机房分布式备份，确保你的数据安全无忧。这些举措使巴别鸟获得了QUALYS安全性A+认证，同时我们也拥有ISO27001信息安全质量体系认证。 巴别鸟从上线开始就实现了从上传、下载、到落盘的全链路的加密传输和存储，配合权限管理及文件管理的细节处理，以及各种使用场景所遇到的风险分析及相应的功能应对策略，使巴别鸟成为了市面上最安全的企业网盘之一。 图：巴别鸟数据传输链路 防火墙、堡垒机、VPN、SSL….在传输和服务器部署架构上我们有越来越多的手段保证系统的数据安全性。但是根据我们多年从事企业安全服务的经验来看，80%数据泄露事件往往来源于内部人员泄露及管理混乱。即使系统做到了物理隔离，也没办法杜绝数据泄露风险。巴别鸟从产品设计之初就考虑到了这一点，从管理、人员和设备的角度提供了多种安全设计及功能。在易用性和安全性的矛盾之处也提供了多种可选设置及方案。从产品结构和使用逻辑上尽可能保证数据安全性。大幅消除因内部人员疏忽或破坏产生的数据泄露风险。 用户身份验证和授权（SSO） 自有用户体系 巴别鸟自由用户体系身份验证种类 账号类型 验证方式 备注 邮箱 密码、验证码 公有云需绑定手机号验证 手机号（全球） 密码、验证码 私有云需对接短信发送平台 工号（user ID） 密码 仅私有云支持，忘记密码只能管理员重置，首次登录会要求用户强制重置密码 微信 扫码、APP跳转（移动端） 仅公有云支持，需绑定手机号验证 巴别鸟支持多种身份验证类型混用。 可强制要求多因素认证（MFA）以提高安全性 混合身份验证: 在使用单点登录时（SSO）支持同时使用自有用户体系和SSO。用户可以选择使用自有凭据登录或通过SSO登录（如使用企业微信扫码登录及采用账户密码登录）。 单点登录（Single Sign On，SSO）集成 单点登录（Single Sign On，SSO）集成是企业网盘产品中的一个关键功能，它允许用户在一次身份验证后访问多个不同的应用程序和服务，提高了用户体验和安全性。 巴别鸟支持OAuth2.0、CAS等方式集成单点登录，并已实际应用于和多种系统的对接中。 支持的SSO标准和协议 巴别鸟企业网盘支持多种SSO标准和协议，包括但不限于以下内容： ADFS集成： 巴别鸟支持与Active Directory Federation Services（ADFS）的集成，这使得基于Windows身份验证的SSO成为可能。这种集成允许企业内部用户使用他们的Windows凭据进行登录。 AD域控制器集成： 巴别鸟还支持与企业的本地Active Directory（AD）域控制器的集成。这使得企业内部用户可以使用他们的本地域凭据进行登录。 企业微信集成： 巴别鸟支持对接企业微信，这使得企业可以直接用企业微信账号进行扫码认证登录。并且可以同步导入微信的组织结构及用户，使用企业微信发送通知，并在工作台中访问巴别鸟。 钉钉集成： 巴别鸟支持对接钉钉，这使得企业可以直接用钉钉账号进行扫码认证登录。并且可以同步导入钉钉的组织结构及用户，使用钉钉发送通知，并在钉钉工作台中访问巴别鸟。 飞书集成： 巴别鸟支持对接飞书，这使得企业可以直接用飞书账号进行扫码认证登录。并且可以同步导入飞书的组织结构及用户，使用飞书发送通知，并在飞书工作台中访问巴别鸟。 集成文档： AD域控、企业微信、钉钉、飞书、致远OA的集成已内嵌于巴别鸟私有化版本中，用户购买相应模块后只需要根据相应文档进行配置即可使用。相关配置文档可咨询巴别鸟客服人员。 第三方SSO集成： 如果你的组织使用第三方SSO供应商（如Okta、OneLogin、Auth0、千帆、泛微等），我们也支持与这些供应商的产品集成。这意味着外部用户可以通过这些供应商的产品进行SSO登录。但这需要二次开发并需要支付一定费用。 第三方自有用户体系集成 我们理解许多组织可能同时拥有自有用户体系，因此我们的SSO集成支持混合身份验证： 混合身份验证: 我们的系统允许用户选择使用自有凭据进行登录，或者使用SSO进行登录。这提供了最大的灵活性，以适应不同用户的需求。 用户映射和同步: 我们确保自有用户体系中的用户帐户与SSO中的用户帐户同步。这意味着用户的属性和权限在整个系统中保持一致。 安全性和授权 我们非常注重安全性和授权策略的实施，以确保只有授权用户能够访问资源： 身份验证策略: 我们支持灵活的身份验证策略，包括多因素认证（MFA）等高级选项。这有助于确保用户的身份得到妥善验证。 授权和访问控制: 我们允许管理员配置和管理用户的访问权限，包括文件和资源的授权。这确保了只有经过授权的用户能够访问敏感数据。从其他平台导入的用户仅会拥有所在部门的初始权限（默认为部门成员），管理员可以通过自定义“部门成员”角色权限的方式统一更改导入用户的初始权限范围。 用户体验 我们关注用户体验，努力提供无缝的登录体验： 登录页面: 我们的登录页面清晰直观，提供用户选择不同的登录方式的选项。用户可以选择使用SSO登录或使用自有凭据登录。同时，我们也支持使用用户单点登录系统自己的登录页面（如ADFS系统认证页面） 单点注销: 如果对接的单点登录系统（SSO）支持单点注销功能，我们也可支持单点注销，这意味着用户可以在任何一个连接的应用程序中注销，系统会自动注销其他应用程序的会话。 访问控制列表（ACL）设计 概述 在巴别鸟企业网盘中，权限管理是确保文件和资源的安全性和可访问性的核心组成部分。ACL（Access Control List）被用于定义用户和角色对于不同部门中的资源的访问权限。本章将详细介绍我们的ACL设计，包括角色管理、用户分配、角色权限和变更管理。 角色管理 角色定义: 我们允许管理员自定义角色，每个角色代表一组权限的集合，有32种权限可选组合成角色。 每个角色应有一个明确的名称和描述，以便管理员和用户了解其功能。 权限分配: 每个角色都被分配特定的权限，这些权限决定了角色在部门中的操作能力。 权限应该精心选择，以确保用户拥有必要的权限但又不会过度授权。 用户管理 用户角色分配: 每个用户都可以被分配一个或多个角色，这些角色决定了用户在不同部门中的权限。 允许一个用户在不同部门拥有不同的角色，以适应多样化的需求。 用户与部门的关联: 用户应与其所属部门建立关联，以便根据部门角色自动分配相应的权限。 用户仅能访问其所在的部门，并有角色决定在部门中的访问权限。 能否访问子部门，也由角色权限决定（角色有访问子部门权限）。 角色权限管理 角色权限定义: 每个角色有明确的权限定义，包括可读、可写、可删除、可共享等操作。 角色可以根据需要新增或删减。 权限继承: 我们的系统支持权限的继承，当用户分配到一个角色时，他们会自动继承该角色的权限。 这减少了手动分配权限的工作量，同时确保一致性。 变更管理 角色权限变更: 当管理员更改角色的权限时，所有拥有该角色的用户在部门中的权限也会相应更改。 我们将详细记录这些变更，以便进行审计和故障排除。 权限审计: 安全管理员可定期审计角色和用户的权限，以确保授权的准确性和安全性。 不再需要的权限应及时取消。 安全性 访问控制: 巴别鸟企业网盘的ACL系统将严格控制用户和角色对资源的访问。 只有经过授权的用户并拥有在该部门的角色才能访问部门文件。 部门间相互隔离，可以设定不同的密级（部门安全策略）来保护部门的文件。 审计和监控: 所有的权限变更角色变更都会留下日志记录。方便管理查询。 实施监控和审计机制，以监视权限变更和访问活动，及时检测和响应潜在的风险。 最佳实践 最小特权原则: 遵循最小特权原则，即给予用户和角色所需的最低权限，以降低潜在的安全风险。 部门文件可通过文件访问控制来精确增加某个成员（或某种角色）的权限，并设定权限有效期。 定期审查: 定期审查角色和权限配置，以确保系统的安全性和性能。 未来扩展 多租户支持: 公有云系统支持多租户控制。 私有云考虑将ACL系统扩展到多租户环境，以支持多个客户或组织的需求。 数据加密 数据传输加密（SSL/TLS） 加密协议 在巴别鸟企业网盘中，我们高度重视数据传输的安全性。为了确保数据在传输过程中得到保护，我们采用了安全套接字层（Secure Socket Layer，SSL）协议来实现传输加密。 HTTPS: 我们使用HTTPS协议，它是HTTP的安全版本，以加密所有数据传输。 HTTPS通过TLS/SSL协议提供端到端的数据加密，防止第三方恶意用户截取或窃听传输的数据。 证书管理 SHA 256证书: 我们的SSL证书采用SHA 256哈希算法，这是一种强大的哈希算法，提供了高级的安全性和完整性保护。 SHA 256证书对于验证服务器的身份以及保护数据传输非常关键。 证书更新: 巴别鸟企业网盘将定期更新SSL证书，以确保证书的有效性和安全性。 我们会监视证书的到期日期，提前进行续签。 数据加密 数据传输加密: 所有在巴别鸟企业网盘和用户终端之间的数据传输都会经过TLS/SSL加密。 这包括用户登录、文件上传和下载、以及任何敏感数据的传输。 数据完整性保护: TLS/SSL不仅提供了数据加密，还能够验证传输过程中数据的完整性，以防止数据被篡改或损坏。 安全性 严格的加密策略: 我们遵循严格的加密策略，确保所有数据传输都经过安全通道，无法被非授权方访问。 保护用户隐私: 数据传输加密有助于保护用户的隐私和敏感信息，包括个人身份信息和机密文件。 最佳实践 安全升级: 我们将继续关注新的安全标准和最佳实践，确保数据传输加密的安全性得到不断提升。 安全审计: 我们会定期进行安全审计和漏洞扫描，以确保我们的加密机制不受到潜在威胁的影响。 图：巴别鸟获得了Qualys SSL扫描的A+安全验证 数据存储加密 概述 在巴别鸟企业网盘中，我们采用了高级的分块加密技术，以确保文件的安全性和完整性。我们使用分块加密技术来将文件分成小块，每个小块都经过哈希加密，然后存储在对象存储系统中。这一技术确保即使在服务器控制权或硬盘被攻破的情况下，攻击者也无法获取到完整的文件内容。 分块加密 文件分块: 上传到巴别鸟企业网盘的文件会被分成若干小块（chunks）。 每个小块的大小可以根据系统需求进行配置，以平衡性能和安全性。 哈希加密: 每个小块都会经过哈希加密，使用强大的哈希算法确保数据的完整性。 哈希值将与存储的小块一起存储，以便后续验证。 存储安全 对象存储: 加密后的小块将存储在巴别鸟企业网盘的对象存储系统中，确保高可用性和数据冗余。 无法还原的加密: 我们使用不可逆的哈希加密算法来确保存储的小块无法还原为原始文件内容，以确保文件存储的安全性。 安全传输: 小块数据在传输到对象存储系统时也会经过加密，以防止中间人攻击。 文件下载 临时下载链接: 当用户需要下载文件时，鉴权通过系统会动态地拼合分块，形成一个临时下载链接。 这个链接是唯一的，只有很短的有效期用于下载。再次下载需要从新生成下载链接。这个设定可以防止通过获取下载链接暴露文件。 下载解密: 在用户请求下载时，巴别鸟企业网盘会将分块数据在服务器端解密，然后合并为完整的文件。 这确保了文件在存储过程中即使硬盘被非法读取内容也不会暴露文件给任何未授权的访问者。 安全性 数据隔离: 分块加密技术将数据分成小块，每个小块都经过独立的哈希加密，以防止整个文件被暴露。 无法还原性: 使用不可逆的哈希算法确保了数据的无法还原性，即使攻击者获取了一部分小块数据，但因数据缺失也无法还原原始文件。 防止数据泄漏 安全审计日志 概述 在巴别鸟企业网盘中，我们强调数据访问和操作的可追溯性和安全性。为了实现这一目标，我们建立了一个强大的访问日志系统，用于记录整个系统的历史访问日志。这些日志包括文件的上传和下载、权限的变更、用户讨论批注、文件的增删改查、审批以及部门变更等操作。本章将详细介绍我们的安全审计日志系统和角色管理。 访问日志功能 全面的日志记录: 我们的日志系统记录了整个巴别鸟企业网盘的各种访问行为，确保每个操作都可以被追溯和审计。 记录的操作包括但不限于文件管理、权限控制、用户操作和部门管理。 关于巴别鸟日志的更多信息，可查阅：日志及报表 章节。 默认保存时间: 默认情况下，我们保存完整访问日志的时间段为90天。 这确保了足够的历史数据可供审计和检查。 可扩展的保存时间: 根据需要，管理员可以根据特定合规性要求扩展访问日志的保存时间（仅私有化系统支持）。 第三方日志管理系统 集成支持: 巴别鸟可对接第三方日志管理系统，以便将访问日志数据导入到外部日志平台进行进一步分析和长期存储。 安全管理员角色 安全保密员: 安全保密员具有高级的权限，可以在前台查看和管理所有部门的文件。 在企业管理后台，安全保密员具备以下权限： 制定公司安全策略（独有权限）。 管理组织结构。 成员管理。 权限管理。 安全审计员: 安全审计员可以在前台查看和管理所有部门的文件。 在企业管理后台，安全审计员具备以下权限： 查看企业安全策略。 查看组织结构。 查看成员权限。 查看权限管理。 查看文件访问日志。 安全性 数据隔离: 安全审计日志数据被严格隔离，只有授权的管理员可以访问和管理它们。 保密性: 安全保密员和安全审计员的角色都经过精心设计，一个负责安全策略，一个负责安全审计，互相监督，以确保数据的保密性和合规性。 扩展 自动化告警: 支持自动化告警机制，可添加监控项目，以在发现异常活动时及时通知超级管理员。 巴别鸟企业网盘的安全审计日志系统，包括功能、角色管理和安全性措施确保了数据访问和操作的可追溯性，并支持与第三方日志管理系统的集成，以进一步提高安全性和合规性。 安全性审查和测试 渗透测试 测试委托: 巴别鸟企业网盘会定期自己进行渗透测试或委托第三方机构，如绿盟科技，进行渗透测试，以评估系统的安全性。 渗透测试的目标是使用前沿的攻击技术，成熟的黑客攻击手段，以及标准的软件测试技术，测试指定系统的安全性，发现潜在的安全漏洞和风险。 测试阶段: 渗透测试包括以下流程： 信息收集：测试人员进行必要的信息收集，如IP地址、DNS记录、软件版本信息、IP段以及公开信息等。 渗透测试：测试人员根据信息收集阶段的结果，尝试入侵网络和系统。成功的情况下，可能获得普通权限。 缺陷利用：测试人员尝试提升权限，以获取对系统的完全控制权。在必要时，他们可能会回到信息收集阶段重新开始。 成果收集：测试人员对之前阶段发现的问题，如弱点和漏洞进行分类整理，并集中展示。 威胁分析：测试人员对发现的问题进行威胁分类和分析其潜在影响。 输出报告：测试人员根据测试和分析的结果，编写直观的渗透测试服务报告。 渗透测试的主要目标： 发现系统中的安全漏洞和潜在风险。 评估系统的安全性，包括身份验证、访问控制、数据保护等方面。 提供改进建议，以加强系统的安全性。 测试的结果将有助于我们采取适当的措施来修复发现的问题，提高系统的整体安全性。 最佳实践 巴别鸟企业网盘将定期进行渗透测试，以保持系统的安全性。 使用自动化工具和手动测试相结合，以提高渗透测试的全面性和准确性。 测试完成后根据报告及时整改，以确保系统的安全性。 未来扩展 我们将继续改进渗透测试流程，以适应不断演进的安全威胁。 考虑引入高级分析工具，以更深入地评估系统的安全性。 安全漏洞扫描 为了维护巴别鸟企业网盘的安全性，我们定期进行安全漏洞扫描。这项措施旨在自动化地检测系统中的潜在安全漏洞，以及可能导致安全威胁的问题。我们依托专业的扫描工具（例如：Qualys、Rapid7 InsightVM、OpenVAS）来确保系统持续保持在一个高度安全的状态。 扫描过程 安全漏洞扫描包括以下关键阶段： 定期扫描: 我们定期（通常是按计划的时间间隔）对系统进行安全漏洞扫描。 扫描工具自动化地执行一系列测试来发现潜在的漏洞。 扫描目标: 安全漏洞扫描的目标包括系统中的应用程序、操作系统、网络设备等各个方面。 扫描确保系统的整体安全性。 扫描结果: 扫描工具将识别并报告系统中发现的漏洞。 报告会包括漏洞的类型、严重程度以及可能的修复建议。 修复措施: 基于扫描结果，我们采取必要的修复措施来解决发现的漏洞和问题，以确保系统的安全性。 巴别鸟安全相关功能" }, { "lang": "zh", "slug": "reference-whitepaper-05-core-modules", "title": "白皮书：主要功能模块", "description": "《巴别鸟企业网盘白皮书》章节：主要功能模块。", "category": "源资料参考", "top_category": "维护", "keywords": [ "白皮书", "主要功能模块" ], "url": "zh/reference-whitepaper-05-core-modules.html", "source": "content/zh/reference-whitepaper-05-core-modules.md", "summary": "白皮书：主要功能模块 数据传输模块 数据传输模块是巴别鸟企业网盘的核心组成部分，负责管理上传、下载、同步盘和映射盘的数据传输。这一模块采用多种技术来确保数据的安全性、可靠性和高效性。 技术特点 文件分块: 数据传输模块采用文件分块技术，将大文件分成小块，以便更有效地传输和存储。这不仅有助于减少网络流量和服务器资源的消耗，还支持断点续传和增量上传下载。 哈希验证（秒传）: 在数据传输过程中，哈希验证用于确保文件的完整性。每个文件块都有相应的哈希值，服务器和客户端会相互验证这些哈希值，以检测是否有数据损坏或篡改。 同时，如果存储系统中已经有相同哈希码的文件，该文件就不用再次上传。实现秒传功能。 SSL传输: 数据传输模块使用SSL（安全套接层）协议来加密数据传输，以确保数据在传输过程中的保密性和安全性。这对于敏感企业数据的传输至关重要。 断点续传: 巴别鸟企业网盘支持断点续传，允许用户在传输中断的情况下从上次中断的地方继续上传或下载文件，而无需重新开始整个过程。这节省了时间和带宽。 增量上传下载: 数据传输模块还支持增量上传和下载，允许用户只传输发生更改的部分的文件分块，而不是整个文件。这在大型文件和频繁同步的情况下非常有用。 优势 数据完整性: 文件分块和哈希验证确保了数据的完整性，降低了数据损坏或篡改的风险。 数据安全: SSL传输提供了数据的端到端加密，确保数据在传输过程中不会被窥探或窃取。 效率: 断点续传和增量上传下载提高了数据传输的效率，节省了时间和带宽。 节约存储空间： 使用文件哈希码技术可以在磁盘上只存储一份相同哈希的文件。无论文件路径、文件名如何变化，或者在网盘中", "headings": [ { "level": 1, "title": "白皮书：主要功能模块", "id": "section" }, { "level": 3, "title": "技术特点", "id": "section-2" }, { "level": 3, "title": "优势", "id": "section-3" }, { "level": 3, "title": "简介", "id": "section-4" }, { "level": 3, "title": "技术特点", "id": "section-5" }, { "level": 3, "title": "常见文件管理功能", "id": "section-6" }, { "level": 3, "title": "版本管理概述", "id": "section-7" }, { "level": 3, "title": "技术实现", "id": "section-8" }, { "level": 3, "title": "版本更新方式", "id": "section-9" }, { "level": 3, "title": "版本管理功能", "id": "section-10" }, { "level": 3, "title": "企业控制", "id": "section-11" }, { "level": 3, "title": "搜索模块概述", "id": "section-12" }, { "level": 3, "title": "带权限判断的搜索", "id": "section-13" }, { "level": 3, "title": "技术基础", "id": "section-14" }, { "level": 3, "title": "搜索功能", "id": "section-15" }, { "level": 3, "title": "性能优化", "id": "section-16" }, { "level": 3, "title": "未来发展", "id": "section-17" }, { "level": 3, "title": "在线编辑模块概述", "id": "section-18" }, { "level": 3, "title": "技术基础", "id": "section-19" }, { "level": 3, "title": "主要功能", "id": "section-20" }, { "level": 3, "title": "用户体验", "id": "section-21" }, { "level": 3, "title": "企业协作", "id": "section-22" }, { "level": 3, "title": "开放API", "id": "api" }, { "level": 3, "title": "其他在线编辑器", "id": "section-23" }, { "level": 3, "title": "客户端编辑概述", "id": "section-24" }, { "level": 3, "title": "技术实现", "id": "section-25" }, { "level": 3, "title": "主要功能", "id": "section-26" }, { "level": 3, "title": "用户体验", "id": "section-27" }, { "level": 3, "title": "技术挑战", "id": "section-28" }, { "level": 3, "title": "分享功能", "id": "section-29" }, { "level": 3, "title": "外发功能（发送文件）", "id": "section-30" }, { "level": 3, "title": "用户控制和企业策略", "id": "section-31" }, { "level": 3, "title": "灵活性与便捷性", "id": "section-32" }, { "level": 3, "title": "技术架构", "id": "section-33" }, { "level": 3, "title": "适用的文件类型", "id": "section-34" }, { "level": 3, "title": "预览器类型", "id": "section-35" }, { "level": 3, "title": "批注种类", "id": "section-36" }, { "level": 3, "title": "功能模块", "id": "section-37" }, { "level": 3, "title": "主要特点", "id": "section-38" }, { "level": 3, "title": "技术架构", "id": "section-39" }, { "level": 3, "title": "文件评审的优势", "id": "section-40" }, { "level": 3, "title": "角色权限", "id": "section-41" }, { "level": 3, "title": "文件权限", "id": "section-42" }, { "level": 3, "title": "总结", "id": "section-43" }, { "level": 3, "title": "概述", "id": "section-44" }, { "level": 3, "title": "使用方式", "id": "section-45" }, { "level": 3, "title": "总结", "id": "section-46" }, { "level": 3, "title": "概述", "id": "section-47" }, { "level": 3, "title": "主要特点", "id": "section-48" }, { "level": 3, "title": "技术优势（对比WebDAV和SMB）", "id": "webdav-smb" }, { "level": 3, "title": "应用场景", "id": "section-49" }, { "level": 3, "title": "主要特点", "id": "section-50" }, { "level": 3, "title": "技术架构", "id": "section-51" }, { "level": 3, "title": "档案管理的优势", "id": "section-52" }, { "level": 3, "title": "主要特点", "id": "section-53" }, { "level": 3, "title": "技术架构", "id": "section-54" }, { "level": 3, "title": "日志与报表的优势", "id": "section-55" }, { "level": 3, "title": "动态栏目", "id": "section-56" }, { "level": 3, "title": "通知栏目", "id": "section-57" }, { "level": 3, "title": "个性化设置", "id": "section-58" }, { "level": 3, "title": "应用场景", "id": "section-59" }, { "level": 3, "title": "概述", "id": "section-60" }, { "level": 3, "title": "主要功能", "id": "section-61" }, { "level": 3, "title": "应用场景", "id": "section-62" }, { "level": 3, "title": "总结", "id": "section-63" }, { "level": 3, "title": "概述", "id": "section-64" }, { "level": 3, "title": "主要功能", "id": "section-65" }, { "level": 3, "title": "应用场景", "id": "section-66" }, { "level": 3, "title": "主要栏目", "id": "section-67" }, { "level": 3, "title": "智巢AI的三个主要模块", "id": "ai" }, { "level": 3, "title": "技术解决方案", "id": "section-68" }, { "level": 3, "title": "优势", "id": "section-69" }, { "level": 3, "title": "多任务协同与执行流转权重", "id": "section-70" }, { "level": 3, "title": "功能概述", "id": "section-71" }, { "level": 3, "title": "核心运作与配置规则", "id": "section-72" }, { "level": 3, "title": "权限与数据安全控制", "id": "section-73" }, { "level": 3, "title": "典型业务应用场景", "id": "section-74" }, { "level": 3, "title": "功能概述", "id": "section-75" }, { "level": 3, "title": "适用范围与权限控制", "id": "section-76" }, { "level": 3, "title": "核心规则引擎与配置维度", "id": "section-77" }, { "level": 3, "title": "原始名称的精细化修剪与防冲突机制", "id": "section-78" }, { "level": 3, "title": "全局格式化输出控制", "id": "section-79" }, { "level": 3, "title": "功能概述", "id": "section-80" }, { "level": 3, "title": "执行逻辑与边界条件", "id": "section-81" }, { "level": 3, "title": "广泛的格式兼容矩阵", "id": "section-82" }, { "level": 3, "title": "功能概述", "id": "section-83" }, { "level": 3, "title": "灵活的触发机制与作用域", "id": "section-84" }, { "level": 3, "title": "核心智能整理规则引擎", "id": "section-85" }, { "level": 3, "title": "业务场景与功能概述", "id": "section-86" }, { "level": 3, "title": "签章资产库与个性化配置", "id": "section-87" }, { "level": 3, "title": "智能自适应交互与沉浸式引导体系", "id": "section-88" }, { "level": 3, "title": "功能概述与业务价值", "id": "section-89" }, { "level": 3, "title": "标准目录阵列的大规模生成", "id": "section-90" }, { "level": 3, "title": "项目级文件夹与权限的“一键部署”", "id": "section-91" }, { "level": 3, "title": "实时状态监控与智能容错机制", "id": "section-92" }, { "level": 3, "title": "使用范围", "id": "section-93" }, { "level": 3, "title": "需要解决的问题", "id": "section-94" }, { "level": 3, "title": "巴别鸟解决方案", "id": "section-95" }, { "level": 3, "title": "基本介绍", "id": "section-96" } ], "images": [], "text": "白皮书：主要功能模块 数据传输模块 数据传输模块是巴别鸟企业网盘的核心组成部分，负责管理上传、下载、同步盘和映射盘的数据传输。这一模块采用多种技术来确保数据的安全性、可靠性和高效性。 技术特点 文件分块: 数据传输模块采用文件分块技术，将大文件分成小块，以便更有效地传输和存储。这不仅有助于减少网络流量和服务器资源的消耗，还支持断点续传和增量上传下载。 哈希验证（秒传）: 在数据传输过程中，哈希验证用于确保文件的完整性。每个文件块都有相应的哈希值，服务器和客户端会相互验证这些哈希值，以检测是否有数据损坏或篡改。 同时，如果存储系统中已经有相同哈希码的文件，该文件就不用再次上传。实现秒传功能。 SSL传输: 数据传输模块使用SSL（安全套接层）协议来加密数据传输，以确保数据在传输过程中的保密性和安全性。这对于敏感企业数据的传输至关重要。 断点续传: 巴别鸟企业网盘支持断点续传，允许用户在传输中断的情况下从上次中断的地方继续上传或下载文件，而无需重新开始整个过程。这节省了时间和带宽。 增量上传下载: 数据传输模块还支持增量上传和下载，允许用户只传输发生更改的部分的文件分块，而不是整个文件。这在大型文件和频繁同步的情况下非常有用。 优势 数据完整性: 文件分块和哈希验证确保了数据的完整性，降低了数据损坏或篡改的风险。 数据安全: SSL传输提供了数据的端到端加密，确保数据在传输过程中不会被窥探或窃取。 效率: 断点续传和增量上传下载提高了数据传输的效率，节省了时间和带宽。 节约存储空间： 使用文件哈希码技术可以在磁盘上只存储一份相同哈希的文件。无论文件路径、文件名如何变化，或者在网盘中有多少个文件副本，文件实际存储空间就只占用一个文件的容量。（去重存储） 高速上传： 相同哈希值的文件不需要再次上传，如上传网盘上已存在的文件，检测到同样哈希值就会自动标记为上传成功，无需再次上传。 数据传输模块是巴别鸟企业网盘的关键组成部分，通过采用这些技术特点，它确保了用户可以安全、高效地上传、下载和同步其文件。这一模块的功能是使巴别鸟企业网盘成为一个可信赖的数据管理平台。 新建模块 新建模块主要负责文件、部门、项目、模版、文件夹的创建。在巴别鸟中可以做到无需上传文件就直接新建文件进行工作。 文件的新建 Office文件 巴别鸟支持在线创建空白word文档、Excel文档、PPT文档。 使用客户端新建会默认打开本地office相应组件创建并编辑文档。 在网页上新建会使用在线office创建并编辑文档。 Office文档都可以使用在线编辑（无需安装office）或使用客户端选择本地编辑（使用电脑上安装的office编辑）。 在线编辑支持多人实时协同编辑。 使用客户端调取本地office编辑时文档会自动锁定编辑，防止其他人在编辑时也编辑该文档造成冲突。 文本代码类文件 巴别鸟文本编辑器可在线创建并打开所有的文本类文件，如RTF、TXT、HTML、MD、CSS… 为了客户使用方便，公有云版本仅支持新建TXT和MD（markdown文件），私有云用户如需要其他格式的文本文件创建可以要求开放。 文本编辑器不同于在线office，不支持协同编辑，但可以在线编辑文本类文件。 思维导图及流程图。 巴别鸟自带思维导图模块，可以在线新建及在线编辑思维导图文件。 思维导图文件默认保存为KM格式。也可以导出为KM、TXT、MD、SVG、PNG、Xmind格式。 巴别鸟也可选支持创建流程图，但需要购买相应的模块授权（非标准版默认自带）。 其他第三方模块。 符合WebAPI的互联网应用理论上都可以对接巴别鸟并新建文件。巴别鸟提供第三方应用对接服务。 从模版创建 不少客户需要大量创建相同结构的文件夹或从某个特定模版（如企业PPT模版）创建文件。巴别鸟支持从模版创建文件夹和文件。 创建模版。 拥有部门文件管理权限的人可以在新建菜单里创建模版。 点击创建模版后会生成一个模版文件夹，模版文件夹类似于普通文件夹，可以拖动文件到文件夹中上传、新建文件夹及部门。 在模版文件夹根目录中上传的文件即成为文件模版，在模版文件夹中创建的文件夹就是文件夹模版。如下图： 图：在模版文件夹中显示 图：在新建模版时显示 从模版创建。 有创建文件及文件夹权限的部门都可以新建时选择模版快速创建和模版一致的文件或文件夹。 新建部门、项目 使用新建功能也可以创建部门和项目。 创建部门。 只有在企业文件根部门下才能创建部门，部门文件属于企业，超级管理员能看到根部门和整个文件树。 拥有子部门管理权限的用户（默认部门经理角色）可以创建子部门。 部门文件夹可以新增部门成员，并完成部门级别的管理。 只有加入部门的成员（部门成员）及上级部门拥有“查看子部门文件”权限的成员才能访问部门文件。 部门成员由在该部门的角色决定基本权限。 可以用文件权限管理的方式针对文件（文件夹）做权限管理 项目。 用户可以在个人文件或企业文件的部门文件夹下创建项目。 项目可以跨部门、跨企业邀请项目组成员，甚至可以邀请企业外的非注册用户。 拥有个人文件的人都可以创建个人项目，要在部门下创建项目用户角色需要有“创建文件夹/项目“权限。 项目文件夹中支持创建子项目。 项目文件夹的上级一定是个部门或者是个项目，这意味着不能在普通文件夹下创建部门。 项目创建者默认为项目管理员，项目是可以转交的，可以把项目管理员转交给其他成员及其他部门。 项目内成员的权限由创建项目时指定。项目相对是一个独立的共享文件夹。 新建普通文件夹 个人文件下创建文件夹。 用户可以在个人文件下可以任意创建文件夹，并自行管理。 企业文件下创建文件夹 企业文件下需要在部门中创建文件夹（所有的文件夹都有归属部门）。 在所在部门中角色具有“创建文件夹/项目“权限的用户可以创建文件夹。 只要角色具有“创建文件夹/项目“权限的用户可以在部门中任意普通文件夹中创建子文件夹。 文件管理 简介 文件管理模块是巴别鸟企业网盘的核心功能之一，用于用户管理和操作文件及文件夹，并根据权限推送给用户不同的文件列表。也是用户使用网盘的主要界面。该模块提供了广泛的功能，以满足企业用户对文件的管理和组织需求。 技术特点 A．文件访问与组织 分页载入技术: 文件管理模块使用分页载入技术，由服务器端数据库进行文件的排序查询操作，并把文件列表返回前台进行分页载入。这样一个文件列表可以分页载入几十万行数据，确保用户能够高效载入和浏览大量文件，而不会影响性能和用户体验。 树状展示文件列表: 巴别鸟支持树状展示文件列表，使文件的组织结构更加直观，用户可以轻松导航和管理文件夹。 权限控制: 根据用户的权限不同，文件管理模块会动态显示适当的列表项目，不同用户看到的文件列表内容根据权限不同而不同。以确保只有授权用户可以查看、编辑或删除特定文件和文件夹。 B. 文件排序和快捷操作 多维度排序: 支持多维度排序，用户可以按照文件名称、最近版本、文件大小等不同维度进行排序。 文件名排序: 不同于大多数网盘应用，巴别鸟文件名排序支持多位数字按顺序排序，使文件名包含数字编号的文件能够准确排序。（大部分网盘文件名排序仅首字母排序如：1、2、10、3、4，但在巴别鸟可以正确显示排序为：1、2、3、4、10） 自定义全局排序: 用户在设置里可以自定义适合自己的全局使用的排序方式，同时系统会记住上一次用户在文件夹选择的排序方式，下一次打开文件夹也按上一次的排序显示。 C. 文件展示和详细管理 列表模式和瀑布流模式可切换: 支持列表模式浏览文件夹，同时可以切换为瀑布流模式预览。 支持瀑布流模式浏览文件夹（文件缩略图），使文件的浏览更加流畅和直观。 图片较多的文件夹会自动适配为瀑布流模式显示。 文件详情页面: 每个文件和文件夹都有详细的详情页面，用户可以管理文件信息，增加文件注释，查看文件访问日志，对文件访问进行统计并生成报表。 文件详情页面也能管理文件的版本。 评论区: 每个文件或文件夹都自带评论区，支持用户评论和@提及其他用户，促进团队协作和反馈。 文件关联: 支持文件关联文件，允许用户在相关文件之间建立连接，以便更方便地访问相关信息。 文件关注提醒: 用户可以提醒有权限查看文件的人关注文件或文件夹，确保重要文件不会被忽视。 D. 高级搜索和筛选 高级搜索 巴别鸟支持高级搜索功能，可以根据关键字、全文内容、时间、文件格式、上传者、搜索范围、搜索类型等维度进行高级搜索。 搜索 巴别鸟也支持全文搜索，可搜索文件内容里的关键字。 也可使用文件名搜索、标签搜索找到对应文件 搜索的结果可以通过筛选的方式再次搜索或筛选 筛选功能: 可以根据文件标签、类型、文件说明关键字、大小、版本、上传者、照片元数据等进行筛选，以快速定位所需文件。 文件标签和分类: 用户可以给文件打标签，以更好地组织和分类文件。 标签可以有企业统一管理，以保证标签符合规范。 左侧栏可以加入标签快捷方式使用。 常见文件管理功能 A. 文件传输和操作 上传和下载文件: 用户可以上传和下载文件，确保数据的灵活传输。 支持文件夹拖动上传，以方便大批量文件的传输。 浏览器支持文件夹打包下载（少于100个文件或小于500MB大小的文件夹） 客户端支持文件夹直接下载（传输列表） 文件和文件夹的新建: 用户可以新建各类文件和文件夹，同时支持从模版新建文件或文件夹，以提高工作效率。 文件复制和移动: 用户可以复制和移动文件或文件夹，以方便组织文件。 支持将文件或文件夹复制到指定目录，以便文件的备份和管理。 文件归档: 用户可以将文件归档到档案库，以便长期保存和检索。 文件置顶: 个人文件支持将文件或文件夹置顶，以便快速访问重要文件。 部门或项目管理员可以置顶部门文件或项目文件，方便部门成员和项目成员快速访问重要文件。 创建文件或文件夹快捷方式: 用户可以创建文件或文件夹的快捷方式，以方便快速访问。 上传新版本: 用户可以上传新版本的文件，系统会自动检测重名文件并提供是上传新版本还是重命名文件的选择。 点击上传新版本按钮可以直接上传新版本。 文件打印为加水印PDF: 开启水印的时候，支持将文件打印为加水印的PDF文件，以确保文件的传播安全性和保密性。 锁定文件: 文件使用客户端编辑时会自动锁定防止冲突。 用户也可以在文件列表中手动锁定文件，以防止其他用户的编辑和冲突。 文件预览: 支持大多数文件预览，以快速查看文件内容。要了解更多可查看 预览与转码 章节。 文件列表展示缩略图: 文件管理模块可以在文件列表中展示文件的缩略图，使文件的浏览更加直观。 批量文件上传下载: 巴别鸟提供客户端专用的上传下载模块，支持批量文件的上传和下载，同时提供传输文件列表展示。 查看文件详情及版本管理: 巴别鸟有专门的文件详情界面。在文件详情里可以添加文件说明，查看文件基础信息，图片文件可以查看元数据，同时还可以在详情里查看文件日志及文件访问、使用情况，管理文件的版本。 B. 文件安全和权限控制 文件访问控制： 部门管理员或项目管理员可以设定文件访问控制，精确的控制每一个文件或文件夹针对每一个用户或某个角色的访问权限。 文件访问控制的优先级高于成员的部门角色权限。譬如：一个部门成员角色拥有某文件的编辑权限，但部门管理员使用文件访问控制把该成员对该文件的权限改为“不可见”，该成员将不能访问该文件。 文件分享: 支持分享文件和文件夹，允许用户设置详细的访问权限，以控制文件的访问。 文件快照分享: 针对只想分享当前版本的需求，用户可以创建文件的快照分享，快照分享不会受文件内容更新而改变，保持建立快照时的版本。 版本管理 版本管理概述 版本管理是巴别鸟企业网盘的重要功能之一，它允许用户跟踪和管理文件的不同版本，确保文件的历史记录和更新能够得以保留和查看。巴别鸟的版本管理功能非常强大，支持多种更新方式以及版本的回滚和查看。 技术实现 版本管理使用文件分块和增量保存技术来存储文件版本。这意味着每次文件的更改都会生成一个新的版本，而这些版本仅存储所做更改的数据块，以减小存储需求并提高效率。企业管理员可以在企业控制台中设置文件版本的保存数量和保存时间，以控制版本管理的策略。 版本管理功能使用户能够灵活管理文件版本，从而确保文件的完整性、历史记录和安全性。版本管理是巴别鸟企业网盘的一项核心功能，旨在提供卓越的用户体验和数据安全性。 版本更新方式 巴别鸟允许用户使用多种方式更新文件版本，包括： 手动上传新版本: 用户可以右键点击文件，选择上传新版本，手动上传新文件，并将其保存为文件的新版本。 同名文件检测: 上传时巴别鸟可以检测到文件名相同的文件，用户可以选择将新文件上传为已有文件的新版本。 客户端编辑保存: 如果用户使用客户端编辑文件并保存，巴别鸟将保存所做的更改作为文件的新版本。 在线编辑保存: 如果用户在网页上使用在线编辑功能编辑文件并保存，也将生成新版本。 同步文件夹编辑: 巴别鸟客户端会监控同步文件夹的更新，在同步文件夹中编辑或覆盖文件并保存会生成新版本。 映射盘编辑: 编辑映射盘中的文件并保存，更新的文件也会保存为新的版本。 版本管理功能 巴别鸟版本管理模块具有以下功能： 版本回退: 在文件的版本列表中，用户可以选择将旧版本置为当前版本，实现版本回退的功能。 版本下载: 用户可以选择下载历史版本，以便访问以前的文件版本。 版本预览: 版本管理模块允许用户在点击旧版本文件时进行预览，以查看该版本的内容。 版本对比： 在巴别鸟预览器预览文件时，可以选择文件对比功能，该功能支持选择旧版本和新版本进行对比。 版本日志: 用户可以为每个文件版本添加日志，以记录版本的重要信息和更改历史。 企业控制 巴别鸟企业网盘的版本管理功能允许企业管理员在企业控制台中进行高级设置，以满足企业的特定需求。企业管理员可以根据公司政策和合规要求，设置文件版本的保留数量和保留时间，以满足不同文件类型和部门的需求。 这样的版本管理系统保障了文件的数据一致性、可追溯性，以及用户数据的完整性。同时对勒索病毒这类改变文件可读性的病毒具有强大的防护性，因为勒索病毒更改文件需要更新的文件，而更新的文件将形成新的版本，用户只要回退版本就能拿到被攻击前的文件。 搜索 搜索模块概述 巴别鸟企业网盘的搜索模块是一个关键的功能，它基于强大的Elasticsearch技术和数据库查询技术开发，旨在提供高效、精确和全面的文档搜索功能。搜索模块不仅支持全文搜索，还可以搜索文档的说明、注释和文件名，满足不同用户的搜索需求。 带权限判断的搜索 巴别鸟的搜索模块不仅具备强大的搜索功能，还采用高级权限管理技术，动态判断用户权限，确保用户只能看到其权限范围内的文件。搜索结果是根据用户的权限动态生成的，这意味着用户共享的文件中，只有用户有权限查看的文件才会被搜索到。这是一项关键的技术，特别在企业环境中，权限是随时变化的。 技术基础 Elasticsearch: Elasticsearch是一款开源搜索引擎，它以高效的分布式架构和强大的全文搜索能力而闻名。巴别鸟使用Elasticsearch作为核心搜索引擎，以支持全文搜索和高级查询功能。 数据库查询: 除了Elasticsearch，搜索模块还利用数据库查询技术来搜索文档的元数据和标签信息，以提供更全面的搜索结果。 文档解析: 搜索模块使用文本提取技术，可以从各种类型的文件中提取文本信息。这些提取的文本信息用于搜索引擎的索引和查询。关键字抽取。 分词优化: 巴别鸟进行了大量的分词优化工作，特别针对中文词汇，以提高搜索引擎的分词准确性和性能。中文分词的优化对搜索结果的准确性起到关键作用。 搜索功能 巴别鸟搜索模块包括以下主要功能： 全文搜索: 用户可以执行全文搜索，查找文档中的文字内容，以找到与关键字相关的文件。 文档描述和注释搜索: 搜索模块支持搜索用户添加到巴别鸟的文档的说明和注释，使用户可以更轻松地找到特定信息。 文件名搜索: 用户可以进行精确的文件名搜索，以查找特定文件。 标签搜索: 可进行标签的搜索、查询、分类显示 高级搜索 巴别鸟支持高级搜索功能，可以根据关键字、全文内容、时间、文件格式、上传者、搜索范围、搜索类型等维度进行高级搜索。 性能优化 搜索模块对服务器性能要求较高，因此对于私有化部署的用户，建议将搜索模块部署在独立的虚拟机或服务器上，以减少对其他模块的性能占用。 未来发展 未来版本的巴别鸟将继续改进搜索模块，结合AI技术，例如ChatGPT，实现文档内容的问答式聊天对话搜索，为用户提供更智能的搜索体验。目前基于AI的文档分析及客服系统“智巢AI”已经上线，详情可查阅智巢AI章节。 搜索模块的不断改进将有助于用户更快速、准确地找到所需的文件和信息，引入AI系统后，用户可以用问答的形式获取信息，并能交叉多个文档的内容得出完整的结论，能大幅度提高生产效率和工作效率。 office在线编辑 在线编辑模块概述 巴别鸟企业网盘是OnlyOffice多年的官方合作伙伴，巴别鸟企业网盘的在线编辑模块基于OnlyOffice技术研发并优化了中文字体的载入和显示问题。巴别鸟在线编辑器支持多种文档格式，包括Microsoft Office（Word、Excel、PPT）和WPS Office。 巴别鸟和OnlyOffice的合作详情可以参见OnlyOffice官方网站： https://www.onlyoffice.com 技术基础 在线编辑模块的技术基础包括： OnlyOffice编辑器: OnlyOffice是一个强大的在线办公套件，支持多种文档格式的在线编辑。巴别鸟将其集成到网盘系统中，以提供优质的在线编辑体验。 中文字体优化: 为了克服OnlyOffice中对中文字体载入效率的不足，巴别鸟进行了优化，通过采用字库本地化技术，大幅提高中文字体的载入和显示速度，从而提升用户体验。 文档锁定: 巴别鸟同时支持客户端编辑和在线编辑，这意味着为防止文件版本冲突文件在线编辑时要锁定不能客户端编辑，文件客户端编辑时要锁定不能在线编辑。 主要功能 巴别鸟的在线编辑模块包括以下主要功能： 多格式支持: 用户可以在线编辑和查看Microsoft Office（Word、Excel、PPT）和WPS Office格式的文档。 协同编辑: 在线编辑模块支持多用户同时协同编辑文档，用户可以实时查看其他用户的更改，并共同编辑文档。这种协同编辑功能对于团队协作非常有用。 兼容性: 巴别鸟的在线编辑模块兼容微软Office，能很好的在网页上还原office的版式和字体。确保文档排版和格式在不同编辑器中打开的良好兼容性。 开放API: 巴别鸟开放在线编辑器的API，允许其他企业软件调用该API，将在线编辑功能集成到其他应用中。 用户体验 在线编辑模块的目标是提供用户友好且流畅的在线编辑体验。用户可以直接在网盘中打开需要编辑的文档，编辑完后即时保存，而无需离开网盘界面。这种无缝集成提高了用户的效率，使编辑文档更加便捷。 同时巴别鸟权限配置支持“仅在线编辑”，这意味着可以让一些用户仅能在线编辑文档但不能下载获取文档。 企业协作 巴别鸟在线编辑模块不仅适用于个人用户，还为企业提供了一个协同办公的平台。团队成员可以一起编辑文档，共享想法，并通过实时协作提高工作效率。 开放API 巴别鸟在线编辑器API允许企业将在线编辑功能集成到其自有软件或第三方软件中，使企业能充分使用在线编辑的能力。 其他在线编辑器 巴别鸟标准版还集成了其他在线编辑器，用于在线编辑及创建如MD文件，TXT文件甚至思维导图（如脑图）同时，巴别鸟也可以通过接入第三方API的形式集成其他支持HTML5的在线编辑系统，譬如可以对接微软office365或金山的web office（WPS）。 自带文本编辑器在线编辑。 巴别鸟自带的文本编辑器可以编辑及预览如：TXT、MD、RTF等文本文件，同时也能编辑CSS、JS、JSP…等代码文件，便于用户快速创建文档记录。 自带脑图（思维导图）编辑器。 巴别鸟自带思维导图模块，可以在线新建及在线编辑思维导图文件。 思维导图文件默认保存为KM格式。也可以导出为KM、TXT、MD、SVG、PNG、Xmind格式。 巴别鸟也可选支持创建流程图，但需要购买相应的模块授权（非标准版默认自带）。 客户端编辑 客户端编辑概述 巴别鸟企业网盘提供了强大的客户端编辑功能，用户可以轻松调用本地编辑软件对云端文档进行编辑，编辑保存后文件会自动上传到云端。这个功能不仅提高了用户的便捷性，还有助于避免文件版本的冲突，从而提高工作效率。 在客户端文件列表要编辑的文件上点击右键，选择编辑即可打开客户端编辑。 客户端编辑的实现原理决定了只要本地有编辑程序，所有类型的文件都可以进行客户端编辑。 技术实现 客户端编辑功能的实现技术包括： 客户端集成: 巴别鸟的Win客户端和Mac客户端均支持本地编辑软件的调用，这使得用户可以直接在本地软件中打开并编辑云端文件。 缓存管理: 客户端编辑使用缓存技术，把需要编辑的文件从云端缓存到本地并调用本地应用打开。系统监测到正在编辑的文件更新就把更新文件作为新版本上传。良好的缓存管理技术能在保证效率的前提下节约用户本地的磁盘空间。用户也可以在巴别鸟右键菜单手动清除文件的缓存。 文件状态检测: 在进行客户端编辑之前，系统会检测文件的状态，包括文件是否已被其他用户锁定。这有助于防止多人同时编辑同一文件，避免版本冲突。 自动锁定和解锁: 当用户开始编辑文件时，系统会自动锁定文件，以确保其他用户无法同时编辑相同文件。编辑完成后，文件将自动解锁，同时生成一个新的版本，并将修改后的文件上传到云端。 版本冲突处理: 尽管存在锁定机制，但在某些情况下，如网络问题或长时间未编辑时可能出现文件版本冲突。巴别鸟提供了冲突处理界面，允许用户对比选择是使用云端版本还是本地版本作为当前版本。无论用户的选择如何，系统都会确保没有选择的版本也会上传至云端作为历史版本，以防止数据丢失。 主要功能 客户端编辑功能的主要功能包括： 本地编辑: 用户可以通过点击本地编辑按钮，将文件缓存到本地，并使用本地默认应用程序进行编辑。 只要本地有相应的应用程序，理论上巴别鸟支持所有文件的本地编辑。 自动锁定: 文件在编辑时会自动锁定，以防止其他用户同时编辑，从而避免版本冲突。 自动解锁: 编辑完成关闭应用后，文件将自动解锁，并生成一个新的版本，将修改后的文件上传到云端。 版本控制: 所有编辑和上传的文件都将生成新的版本，以便用户可以随时查看和还原以前的版本。 用户体验 客户端编辑功能提供了出色的用户体验。用户可以在本地编辑器中进行编辑，而不必下载文件编辑后再上传。同时不支持在线编辑或在线预览的文件格式也可以通过客户端编辑打开编辑或预览。这提高了编辑效率和工作流程的顺畅性。 技术挑战 客户端编辑功能的技术挑战在于检测文件的状态，自动锁定和解锁，以及文件版本的冲突处理。系统需要准确判断文件是否正在被其他用户编辑，同时在冲突发生时提供用户友好的解决方案。这些挑战需要综合考虑用户体验和数据完整性。巴别鸟客户端编辑是业内少有的能很好处理这些问题的功能模块。 分享及外发 分享功能 巴别鸟企业网盘提供了多种灵活的分享方式，包括邀请分享和链接分享，以满足用户的不同需求。 邀请分享： 邀请分享是一种将文件或文件夹分享给特定人员的方式。特点如下： 身份验证：被邀请者需要进行身份验证，可以通过巴别鸟账号登录或者接收验证码确认身份。 每个被邀请者可以独立管理权限，可设置权限有效期。这意味者同一个邀请分享，不同的被邀请者可以设定不同的访问权限。 权限控制：分享者可以自定义分享权限，包括查看、编辑、下载等权限。这有助于细化控制分享内容。 审批机制：如果用户没有分享权限，分享操作需要经过审批，确保只有授权的人员可以分享文件。 链接分享： 链接分享允许用户创建一个公开链接，供其他人访问文件或文件夹。特点如下： 允许匿名访问：分享者可以选择是否允许匿名访问。如果关闭匿名访问选项，访问者需要拥有巴别鸟账号才能访问。 快照分享：快照分享模式下，分享的内容是分享时的当前版本，即使文件内容更新，快照分享的内容也不会变化。 密码保护：用户可以设置密码，确保只有知晓密码的人能够访问分享链接。 有效期：链接分享可以设置有效期，确保文件不会永久公开。一旦有效期结束，分享链接将自动失效。 自定义设置： 在企业控制台中，管理员可以自定义分享权限、按部门设定分享行为（支持或禁止分享），按文件设定分享规则（禁止分享高密级文件），以及关闭整个企业的对外分享功能。 分享日志： 所有的分享行为和外界访问行为都有独立的日志，每个分享的访问日志都可以查询。你可以知道什么人什么时候访问了分享的文件或文件夹，分享文件更新版本会提醒用户。 统一管理分享： 部门管理员可以统一查看和管理整个部门所有被分享的文件，分享的个人文件也可以在“我分享的文件”栏目统一查看管理，确保不会有遗漏的分享在不知情的情况下泄露。 外发功能（发送文件） 外发功能是一种通过邮件或手机号将文件发送给其他用户以供直接下载使用的方式。外发不同于分享，仅用于接收方下载外发的文件，无需配置权限。特点如下： 发送文件：用户可以使用外发功能将文件发送到其他用户的邮箱或手机号，以便他们可以直接下载并使用。 发送文件功能也可以发送文件给内部用户，收到文件会有通知，点击通知就可以下载或转存文件。 无需权限：外发不需要配置权限，只要用户有分享和下载权限即可使用。 邮件或短信发送：外发可以通过电子邮件或短信发送文件链接，确保接收方可方便地获得文件。 快捷下载：接收方可以通过点击链接直接下载文件，简单便捷。 用户控制和企业策略 用户的分享权限可以由企业管理员进行控制，确保文件的分享和外发都受到严格管理。此外，企业管理员还可以通过企业控制台自定义分享规则和权限，以适应不同的企业需求。 安全性 分享和外发功能均受到严格的安全控制，保护企业文件不被未经授权的人员访问。管理员可以根据企业的安全策略，灵活配置分享和外发的权限和规则。 灵活性与便捷性 分享和外发功能提供了企业灵活性和便捷性，满足了不同用户及场景的需求。用户可以根据具体情况选择最适合的分享方式，从而更好地管理和共享文件。 预览器及批注、讨论 为了让用户能更方便的预览文件，并且可以在预览文件时进行协作讨论提高协作效率，巴别鸟开发了巴别鸟预览器BabelViewer，在巴别鸟上可以预览的大多数文件格式都可以用预览器打开，巴别鸟预览器不仅可以预览文件，还可以通过手绘、文字讨论、语音（仅手机APP支持建立语音批注）等方式在文件内容上和协作者进行交流。同时，巴别鸟预览器还支持版本对比，切换版本查看不同版本批注、批注管理、审批管理等功能。 技术架构 使用canvas开发及多图层技术 预览器基于Html5 Canvas技术开发，使用多图层技术，以在文件预览层上面增加批注和手绘图层，不影响文件内容但可以进行批注讨论和实时手绘。 实时协同模块 预览器的实时协同模块，保证多用户在文件预览时的批注讨论和手绘是实时展示的，这意味着用户可以边批注边讨论文档或设计稿件的问题。 批注点坐标系定位 巴别鸟预览器使用坐标系定位， 保证批注点在不同的分辨率屏幕下，不同浏览器尺寸下的位置一致。 适用的文件类型 巴别鸟预览器能打开绝大多数图片及office文档、PDF文档及矢量图形文件。具体支持的文件类型可参阅 预览转码章节里的 支持在线预览的文件类型 预览器类型 多页文档预览器 支持对多页文档的预览，如word、PPT、PDF等格式。针对多页文档提供适合多页文档的目录、放大、旋转页面等功能。 图片预览器 为更好的预览图片而设计。拥有鹰眼、放大缩小、显示原始比例、旋转等功能。 右键可以复制图片到剪贴版，方便在微信、邮箱里直接粘贴图片。 针对PNG等拥有透明度的图片，可以改变图片背景。 图形预览器 为预览CAD、SVG、单页PDF等矢量图形文件设计，支持鹰眼、分图层显示、更改背景、鼠标拖动区域放大、矢量放大。对SVG文件可以切换编码模式。 3D预览器 为预览3D文件设计，可以旋转、鼠标滚轮拉近放远3D文件、炸开图像、支持3D空间的批注。 批注种类 文字讨论区 文字讨论区可以在预览文件的任意区域创建（双击建立文字讨论批注）。 文件的协作者如果有查阅批注权限都可以看到批注，并参与讨论。 批注内容实时显示，一个文字批注讨论区相当于针对批注内容的群聊。 支持插入附件进行讨论，也支持@等聊天功能。 可以设定批注的可见性，如：仅企业成员可见、所有人可见、仅批注者自己可见。 文字标注 文字标注可以在文档内容或照片上添加标注 选定文字批注 针对有文字的文件，如word、PDF，可以选择一段文字进行批注。 特殊符号插入 针对特殊需求的稿件，可以插入修订符号或焊接标记（如CAD图纸） 建立图形批注 也支持使用图形框选批注，支持矩形、椭圆及箭头。 语音批注 巴别鸟移动设备APP可以建立语音批注。在网页和客户端可以查看（收听）语音批注，但不能创建。 手绘批注 支持在稿件或文档上实时绘制，参与者可以实时看到绘制的线条，并且标记手绘者昵称。 功能模块 批注管理模块 可以管理创建的批注和批注状态，查阅其他版本批注，并切换到相应的版本 评审工作区 巴别鸟可以在文件评审时使用批注，并显示评审的相关面板，让评审人员能更准确便捷的传达评审信息。 鹰眼 鹰眼可以在图像放大时显示图像视口所在的区域。 版本对比 巴别鸟预览器支持文件对比功能，也可以对比不同版本的文件。 文件目录 对于拥有目录的文件（word、pdf），巴别鸟也支持预览时显示文件目录。 文件评审 巴别鸟企业网盘提供了强大的文件评审功能，旨在帮助用户高效管理文件的审批和修订过程。文件评审是一种协同工作流程，允许用户发起文件评审，邀请评审人员查看文件，提供批注和建议，以最终确定文件是否需要修改或批准。 主要特点 多文件评审：支持同时评审多个文件，用户可以一次性发起对多个文件的评审，确保高效的审批过程。 文件锁定：文件在评审过程中会被自动锁定，以防止其他用户进行编辑或上传新版本，确保文件内容在评审期间不会被更改。 文件预览和批注：评审人员可以在预览文件时添加批注，填写评审意见，以提供详细的反馈。这有助于更好地理解文件内容和提供有针对性的建议。 评审流程：用户可以选择不同的评审流程，包括自由定义审批流程、使用预设审批流程，或限用特定审批流程。这允许不同部门根据其需求选择适当的审批流程。 多阶段审批：审批流程支持多个阶段，每个阶段可以设置一个或多个审批者。用户可以定义通过比例，例如，50%的审批者通过即可通过某个阶段。 邀请外部审批者：用户可以邀请外部成员（通过邮件或手机号）参与文件评审，以获得更多不同角度的反馈，譬如：论文答辩时邀请外部专家。 审批报表：每次文件评审后，会生成审批报表，记录每个阶段参与者的评审意见，以便审批结果的跟踪和分析。 评审签名：支持评审结束后在稿件上插入签名，并下载为PDF。 我的评审栏目：用户可以在“我的评审”栏目中查看和管理与自己相关的所有评审文件的各个阶段，包括发起的评审和邀请参与的评审。 技术架构 文件评审功能的实现涉及以下技术和模块： 评审流程定义：后台定义不同的评审流程，包括阶段设置、审批者选择、通过比例设定等。这些流程可供前台用户选择。 部门特定审批流程：不同部门可以选择不同的审批流程，根据需要选择自由定义、预设或限用特定审批流程。 多阶段审批：可实现多阶段审批，每个阶段具有不同的审批要求，包括审批者的选择和通过比例。也可以设定某阶段是否能跳过。 外部审批者邀请：支持邀请外部成员参与文件评审，通过邮件或手机号进行邀请。 审批报表：生成审批报表，记录每个阶段的评审意见，以便审批结果的跟踪和分析。 文件评审的优势 文件评审功能有助于用户高效管理文件的审批和修订过程，确保文件内容的准确性和合规性。用户可以通过文件评审，确保文件经过充分的审查和讨论，以满足其工作需求和合规要求。这个功能的引入增加了文件协作和管理的深度，为用户提供了更强大的文件协作工具。 权限管理 巴别鸟企业网盘的权限管理是其核心功能之一，它贯穿整个系统，确保用户能够安全、合规地访问和管理文件。巴别鸟权限体系包括角色权限和文件权限两个主要方面。 角色权限 定义角色：巴别鸟允许在企业内定义不同的角色，每个角色可以包括一组特定的权限，用于控制用户在部门文件夹的访问和操作。这些角色可以根据部门管理需求进行创建，例如“部门管理员”、“部门成员”等。 部门角色权限：每个部门成员可以根据其在不同部门的角色分配不同的访问权限。这意味着用户可以在不同部门享有不同级别的权限。 灵活管理：巴别鸟的角色权限支持多个部门角色，并且可以在不同部门内同时使用相同的角色。角色的权限内容更改后，使用相同角色的成员的权限也会相应更改。 权限组合：巴别鸟角色权限支持30多种可选权限进行组合，以实现精细化的用户权限控制。这些权限涵盖了各种访问和操作行为，如预览、上传、下载、编辑等。 角色可选权限列表： 文件权限 自定义权限：文件权限也可以在后台自定义，用户可以选择特定权限类型和名称。这些自定义文件权限将用于文件分享、项目管理和文件权限控制。 文件访问控制：文件访问控制允许部门成员在文件和文件夹上设置具体的访问权限，以覆盖部门角色权限。这意味着可以更精确的控制部门里某个文件或文件夹的访问行为，文件访问控制仅适用于部门成员和项目成员。 高优先级：文件访问控制的权限具有较高的优先级，如果设置了文件访问控制，将覆盖成员的部门角色权限或项目权限。用户可以根据需要设置文件的访问权限。 部门文件和文件夹控制：用户可以为部门文件和文件夹启用文件访问控制，以控制特定文件或文件夹的访问权限。 有效期：文件访问控制可以设定有效期，到有效期后，文件访问控制的约束失效。譬如：给某个没有文件编辑权限的部门成员该文件的编辑权限，有效期3天，3天后文件访问控制赋予的权限就会失效，部门成员对文件的权限就变成成员角色的权限。 总结 巴别鸟企业网盘的权限管理是一个全面的系统，可以满足企业不同部门和项目的特定需求。角色权限和文件权限相互配合，确保用户可以精确控制文件的访问和操作。这一功能有助于提高安全性、合规性和工作效率。 同步 概述 文件同步是巴别鸟企业网盘最受欢迎的功能之一。它允许用户将本地任意文件夹同步到云端或者把云端任意文件夹同步到本地，实现云端和本地文件的实时同步。这个部分包含了以下关键功能： 同步管理：巴别鸟支持创建多个同步，并可在同步管理列表里统一管理。 多人协作：巴别鸟同步是为多人协作而设计的。它自动锁定文件，防止多人同时编辑造成冲突，还有冲突处理机制和版本管理。 和权限一致：巴别鸟同步会判断用户的权限。没有下载权限的用户也不会因同步而下载文件，保证权限的一致性和闭环，这意味着，用户可以通过权限来设定哪些文件夹可以同步。 多种同步类型：巴别鸟支持多种同步类型，用户可以根据具体需求选择合适的同步方式： 双向同步：云端和本地文件夹保持内容一致，任何一侧的修改都将同步到另一侧。 单向向上同步：本地更新会同步到云端，但云端更新不影响本地。 单向向下同步：云端更新会同步到本地，但本地更新不影响云端。 强大技术优势：巴别鸟企业网盘同步功能拥有多项技术优势，确保性能和稳定性： 支持大规模文件夹：巴别鸟支持高达20万个文件的文件夹同步。 文件编辑锁定：编辑同步文件时，文件会自动锁定，以防止多人编辑引发冲突。 冲突处理机制：针对同一文件的编辑冲突，巴别鸟提供了冲突处理机制，确保文件版本的完整性。 版本管理：文件同步功能和版本管理配合，能保证本地的文件夹也不会因为误操作等原因被覆盖从而丢失内容，即使出现文件冲突，冲突的两个版本文件也都会得到保存。 异步情况下的错误处理：文件同步功能还包括对异步情况下的错误处理和修复。 使用方式 开启同步：本地文件夹右键菜单选择巴别鸟——同步该文件夹。 选择同步方式：用户可以在同步时选择合适的同步方式，包括单向同步、双向同步等。 权限配置：通过权限配置，用户可以实现更多的自定义同步方式，根据需要限制文件删除或其他操作。 多人协作：多人协作下，文件编辑时会自动锁定，以避免多人同时编辑造成冲突。冲突处理机制确保文件版本的一致性。 版本管理：文件同步功能支持版本管理，用户可以查看以前的文件版本并进行恢复。 总结 巴别鸟企业网盘的文件同步功能是一项出色的工具，可以实现云端和本地文件的实时同步。多种同步方式、权限配置、多人协作、版本管理等技术优势确保了高性能、稳定性和安全性。 虚拟映射盘 概述 虚拟映射盘：巴别鸟企业网盘引入了虚拟映射盘功能，提供了一种无缝连接云端文件的方式，在windows资源管理器或着mac的访达中都可以类似于访问本地磁盘一样访问映射盘，从而实现轻松访问云端文件的体验。 技术实现：巴别鸟虚拟映射盘使用了类似OneDrive、iCloud的技术方案，它在操作系统中创建了一个虚拟磁盘，将云端文件映射到用户的本地计算机上，使得这些文件在用户的文件浏览器中可见。 主要特点 本地访问云端文件：虚拟映射盘允许用户通过本地文件资源管理器或Finder等工具访问其巴别鸟企业网盘中的文件和文件夹。 无本地存储占用：与传统的文件同步方式不同，虚拟映射盘并不将云端文件实际存储在用户的本地磁盘上，因此不会占用本地存储空间。文件只在需要时进行缓存或下载。 在线访问：虚拟映射盘需要网络连接才能访问云端文件。文件图标实际上只是云端文件的链接，因此需要在线才能查看和操作这些文件，权限也和云端一致。 透明操作：用户可以像操作本地文件一样操作虚拟映射盘中的文件，包括打开、复制、粘贴、删除等操作。 自动同步：文件的更改会自动同步到云端，从而保持云端文件与虚拟映射盘中的文件的一致性。 关联文件：在巴别鸟映射盘中打开有关联文件的文件，会自动加载关联文件，实现和本地文件夹打开文件一样的效果。譬如：打开含有大量参照文件的DWG（AutoCAD文件）、或者有关联其他文件的Excel图表。 技术优势（对比WebDAV和SMB） 权限一致性：不同于WebDAV或SMB挂载（必须使用兼容WebDAV或SMB的权限规则），巴别鸟映射盘是直接调用操作系统底层文件系统实现的，可以实现和巴别鸟一致的权限控制。（譬如：只能预览但不能下载或另存为。）在WebDAV和SMB中，仅查看权限实际为只读，只要是可见的文件，用户都可以通过只读模式打开并获得文件，失去了对文件的管控。 更高的性能：巴别鸟映射盘直接对应巴别鸟服务器相关接口，没有转发和中间处理环节，可以直接获取服务器提供的文件列表以虚拟方式打开文件夹，所以能提供更高的性能，打开文件列表和查阅文件不会卡顿。使用WebDAV只能打开一个文件夹临时载入一个列表，文件夹文件数量超过一定数量（和设备性能及网速有关，一般数量是超过300个）就会发生严重的卡顿和访问缓慢。使用对象存储系统的超大文件夹WebDAV并不能很好支持。 更安全：巴别鸟映射盘能根据权限判断每个人可以查看的文件夹和文件夹中的文件，不同权限的人查看同一个文件夹看到的内容可以不同，SMB和WebDAV目前做不到。同时巴别鸟的文件分块加密存储于对象存储，但如果是分块加密存储的文件，使用WebDAV就需要分文件解密后才能获得文件列表，这意味着，支持WebDAV的产品要么数据存储没有加密，要么WebDAV性能极差文件数量超过一定范围即不可用。 可控性：不同于使用第三方软件挂载的WebDAV及SMB，巴别鸟映射盘为自主研发驱动器，对驱动器的操作、菜单及运行方式、功能实现都具有可控性，并且能对产品质量及使用体验一致性负责。未来也能有更多的功能扩展。 主流企业级解决方案：无论是微软的OneDrive、Google的Google Drive或是苹果的iCloud、BOX的BOX Drive还是国内主流互联网企业网盘厂商，都使用了类似巴别鸟映射盘的解决方案，而不是简单接入WebDAV（接入WebDAV只要做协议兼容并开放接入即可，实现简单，为什么主流企业级厂商还都花费大量精力自研映射盘呢？）。WebDAV主要应用场景还是不需要进行复杂权限判断也不需要存储加密并开放所有文件的个人或小团队使用。SMB的主要使用场景也是个人及小团队的开放文件共享（明文存储）。 应用场景 虚拟映射盘适用于需要频繁访问云端文件、但不想改变本地磁盘的使用习惯也不想占用本地存储空间的用户。这个功能使得用户可以像访问本地文件一样访问云端文件，并且在其他应用程序里如同打开本地文件夹一样访问网盘，不改变使用习惯，便于文件的管理和使用。 档案管理 巴别鸟企业网盘提供了强大的档案管理模块，用于统一管理和归档企业文件。这一模块旨在帮助企业更好地组织和保留关键文件，同时确保文件的安全性和可访问性。 主要特点 档案管理员：巴别鸟允许超级管理员指定一名或多名企业成员作为档案管理员。档案管理员负责管理归档的文件和档案库。 档案库：归档的文件存储在档案库的根目录中。档案库是企业的资料图书馆，用于长期保留和管理文件。 阅览室：档案管理员可以建立阅览室，将档案库根目录的文件移入阅览室。这样其他企业成员才可以借阅这些文件。 借阅权限：阅览室可以选择不同的借阅方式，包括公开、需要借阅、限定部门公开、限定部门内借阅等。借阅文件时，可以设定权限级别，如仅可阅读、可复制、可下载，并指定借阅时长。 文件归档：归档后的文件不可更改，确保文件的完整性和可信度。这对于长期保留法律和合规性文件非常重要。 档案库搜索：档案库拥有独立的搜索功能，只会搜索档案库内的文件。用户可以快速找到需要的归档文件。 文件隐私：没有借阅权限的非公开文件不会显示预览图，以确保文件隐私性。 技术架构 档案管理模块使用以下关键技术和模块： 档案管理员权限：超级管理员可以指定企业成员为档案管理员，允许他们管理档案库和阅览室。 阅览室设置：档案管理员可以创建阅览室并配置不同的借阅权限和可访问性选项。 归档和保留：文件归档后，需要确保其内容不可更改。这需要技术措施来保护文件完整性。 独立搜索：档案库拥有独立的搜索引擎，用于搜索档案库内的文件，确保用户可以快速找到需要的文件。 档案管理的优势 档案管理模块帮助企业更好地管理文件的归档和保留。通过档案库、阅览室、和不同的借阅权限，企业可以确保文件长期保留、有序管理，并能够满足合规性和法律要求。这一模块还可以作为知识库使用，帮助企业保存重要信息和知识。 日志及报表 巴别鸟企业网盘的日志与报表系统提供了全面的文件使用情况管理、监控、审计和追责功能。这一模块旨在帮助企业管理者及用户深入了解文件活动、访问情况以及系统使用情况，以支持合规性和安全性需求。 主要特点 文件日志：每个文件和文件夹都有独立的日志，详细记录了文件的生命周期内的各种操作，包括创建、阅读、修改、更名、分享、删除、权限更改等。甚至包括匿名分享操作以及访问者的IP地址。这些日志可以导出为Excel报表，用于审计和监控。 文件访问统计：文件详情页提供了文件批注数量、下载次数、打开次数、访问人数和访问人员的统计。 文件夹列表：可以导出文件夹内文件和子文件的列表为EXCEl文件，以便审计和管理。 文件评审记录报表：文件评审操作也被记录为报表，以支持文件评审的审计。 部门日志与报表：部门管理员可以查看整个部门的使用日志，包括文件详细访问日志、上传文件数量、创建子部门数量或项目数量的统计。此外，部门管理员可以统计及管理整个部门分享的文件以及更改过权限的文件。 企业级管理：企业管理员和安全审计员可以查看整个企业的使用行为，包括各个部门的日志和报表，并且还有访问日志和统计分析两个栏目统一查看及管理整个企业的使用行为。这有助于维护企业的合规性和安全性。 访问日志：访问日志记录了整个企业网盘的使用日志，包括用户在网盘中的每个操作。管理员可以进行详细的查询和导出报表。 统计分析：提供了统计分析图表工具，允许管理员查看不同部门的使用活跃度、文件数量、活跃文件排名、新建文件统计、上传文件数量统计以及流量使用统计等。 技术架构 日志记录：系统需要记录每个操作的详细日志，包括操作类型、时间戳、执行者、目标文件、IP地址等信息。 报表生成：管理员能够从日志数据中生成报表，通常以Excel格式呈现，以便审计和监控。 数据分析工具：统计分析工具用于分析和可视化数据，帮助管理员更好地了解系统使用情况。 日志接口：巴别鸟支持通过接口导出日志数据，以使用第三方日志管理及分析工具。 日志与报表的优势 日志与报表系统有助于企业实现以下目标： 合规性：帮助企业遵守法规和内部政策，确保文件操作的合规性。 安全审计：提供审计功能，允许企业检查和监视文件访问和操作，以发现潜在的风险。 性能优化：通过统计分析，帮助企业了解系统的性能瓶颈，以采取适当的改进措施。 用户行为监控：允许企业管理者了解员工的行为，包括文件访问和操作，以确保数据的安全性和保密性。 决策支持：通过数据分析，帮助企业管理者做出更明智的决策，包括资源分配和文件管理。 日志与报表系统是巴别鸟企业网盘的重要组成部分，提供了全面的文件使用情况管理和监控功能，以支持企业的合规性和安全性需求。 动态及通知 动态栏目 概述：巴别鸟企业网盘的动态栏目是一个信息流，用于展示与您有关的文件和用户的动态信息。它提供了一个实时的工作情况总览，帮助您跟踪同事的活动，包括文件的变更、批注、评论等。 实时信息流：动态栏目以实时信息流的方式呈现您和您的团队的协作活动，从而帮助您及时了解团队中发生的事情。 便捷互动：通过动态栏目，您可以直接访问与您有关的文件，回复批注，与同事互动，以更便捷的方式完成协作任务。 动态搜索：您可以搜索动态的历史内容，更精准的定位到相关的动态条目。 通知栏目 通知系统：巴别鸟企业网盘的通知系统用于发送各种与您有关的提醒和通知。这些通知可以以多种方式传达给您，包括邮件通知、手机应用程序通知、桌面通知等。 通知类型：通知系统涵盖了多种通知类型，如@提到您、文件更新通知、审批请求、文件授权请求等。这有助于您保持对各种工作流程的掌握。 个性化设置 信息类型设置：用户可以根据自己的需求在设置中自定义接收哪些动态和通知类型，以确保信息的准确性和有针对性。 应用场景 动态栏目和通知栏目帮助用户了解工作中的重要动态和通知，提高了协作效率，使用户能够更快速地回应同事的协作请求，回复评论以及跟踪文件的变化。 巴别鸟企业网盘的动态与通知栏目是关键的协作工具，它们提供了实时的协作情况总览和各种通知，使用户能够更有效地与团队协作，并保持对工作流程的了解。这些功能有助于提高协作效率，确保重要信息不被忽略。 讨论组 概述 讨论组功能：巴别鸟企业网盘为每个部门和项目创建了讨论组，作为部门或项目内部成员的群聊空间。讨论组允许成员在其中发布文本和图片，进行讨论，并分享附件。 成员互动：讨论组提供了一个方便的平台，使成员能够互相沟通、协作和讨论项目相关事项，从而增强团队合作和信息分享。 主要功能 信息发布：讨论组成员可以发布文本消息和图片，以实现实时的讨论和交流。 附件分享：成员可以轻松分享附件，如文档、表格和其他文件，以便共享和讨论。 可见性：讨论组中发布的信息对所属部门或项目的所有成员可见，从而确保信息共享。 应用场景 讨论组适用于部门内部和项目团队之间的信息交流和讨论。它们促进了实时协作，有助于解决问题、分享见解和跟踪进度。 总结 讨论组为部门和项目成员提供了一个便捷的协作平台，用于共享信息、讨论事务和协同工作。这些讨论组有助于加强内部沟通，提高团队的效率和生产力。 工作台 概述 工作台功能：巴别鸟的工作台是一个个性化的界面，允许用户将常用的文件夹、工作内容以及各种信息以卡片的形式集中在一个界面上展示。每个卡片直接呈现内容，可进行操作，用户可以根据需要自由调整卡片的位置和排序。 个性化：工作台提供了多个备选卡片，用户可以自由选择需要添加到工作台上的卡片，根据自己的需求进行定制。这使得用户能够在一个页面上获取与其工作相关的信息和功能。 主要功能 卡片展示：每个卡片代表不同类型的信息或工作内容，例如最近访问的文件、上传的文件、关注的文件、分享的文件、批注过的文件、标签云图等。 自定义图表：用户可以自定义图表或卡片，以便将特定项目、文件夹或其他信息添加到工作台上，以满足其独特的需求。 卡片排序：用户可以通过拖放方式对卡片进行排序，以便将最重要或最频繁使用的信息放在前面。 应用场景 工作台适用于用户需要集中管理和访问与其工作相关的信息和资源的情况。用户可以将常用的文件和项目放在工作台上，以提高工作效率。 企业管理后台（企业控制台） 巴别鸟企业控制台集中了管理员对整个企业进行管理的功能。企业管理员可以在企业控制台中配置企业网盘的各个选项、开启或关闭需要的功能模块、设定组织结构、自定义角色和权限，管理成员、设置水印、设定部门安全策略、iP访问策略、绑定账户和mac地址、监控网盘使用情况…. 主要栏目 企业配置：综合管理企业网盘的配置项，譬如空间分配、是否允许个人文件、允许的文件上传大小、历史版本有效期或历史版本数量、各种管理员分配、更改logo及登录背景、禁止或开启对外分享、是否接受邮件通知。各种企业配置选项里面都可以在企业配置栏目找到。 组织结构：统一管理和维护企业的组织结构及部门。能树状查看部门和管理部门。查看部门成员、分配部门空间、创建子部门、设定部门安全策略… 权限管理：创建角色和更改角色权限，同时可管理自定义文件权限。 成员管理：可以查找和筛选整个企业的成员账户，新增成员、批量导入成员、分配成员部门及角色、详细查看及管理每一个成员的信息及使用情况、成员离职一件交接、成员账户的增删改查、成员空间和流量的分配及限制。 标签管理：统一管理企业所使用的标签，添加标签和给标签分类，便于用户选择标签。 文件配置：添加文件审批可选流程，管理已经添加的审批流程。同时拥有文件黑名单功能，可以阻止特定类型的文件上传。 企业通知：创建企业通知，管理历史企业通知列表、发送企业通知。 分组管理：建立分组及管理分组。前台分享文件时可以选择分享给什么分组。 水印设置：管理文档的水印类型，水印参数调整，水印显示范围设定。 访问日志：管理及查询整个企业网盘的所有访问记录。可导出日志报表。 IP策略列表：可通过IP策略管理企业文件的上传下载行为。譬如：某个IP段禁止下载文件，回到某个IP段即可下载文件。 Mac地址绑定：可以把用户账号和特定设备mac地址绑定，让账号只能在绑定mac地址的设备上使用。也可以创建mac地址池。 统计分析：统计分析网盘的使用情况。包括系统活跃度、文件数量统计、活跃文件、一段时间内的新建文件数、每个月上传数、流量使用情况。 工作台推送：设定工作台的默认显示卡片。 系统配置（仅私有部署版本）：配置邮件服务器，绑定第三方SSO认证，设定第三方认证登录方式。 第三方账号同步（仅私有部署版本）：设置第三方账号同步时间，查询第三方账号同步记录。 可选模块（仅私有部署版本）：选择企业需要展现的功能模块，关闭某些功能模块。 监控预警：设定异常行为的预警，遇到异常行为通知管理员（譬如：用户大量删除文件） 传送文件配置：数据摆渡系统的配置，允许多套巴别鸟间进行数据摆渡。配置数据的接收端口及发送端口。 API 巴别鸟API模块负责巴别鸟开放API，私有云用户可以在企业控制台免费申请及开通开发者账号，获取开发者id、密钥几Token、并设定回调URL 回调URL设置规则：http://客户域名 /public/babelAuthResult.do 譬如：http://testqiyeban.babel.cc/public/babelAuthResult.do 设置路径：企业控制台——企业配置——开发者账号 访问以下链接获取最新API文档： https://www.babel.cc/p/api integration.do 第三方登录（SSO） 巴别鸟支持集成第三方登录（SSO）平台，以实现单点登录及统一登录。并且巴别鸟支持多个第三方登录平台集成。譬如：既可以企业微信扫码登录也可以OA账密登录、钉钉扫码登录。 SSO集成分为两个模块。第三方授权登录及第三方组织结构同步。其中第三方授权登录允许多个源进行授权登录。但第三方组织结构同步为了防止造成用户账户冲突，仅允许同步一个源。譬如：同步了OA系统的组织结构，但是支持OA和企业微信的SSO登录（OA和企业微信的的组织结构需要用一致的userID） 更多关于巴别鸟第三方登录的信息，可以查阅用户身份验证和授权（SSO）章节 数据摆渡 巴别鸟数据摆渡支持部署在密区的巴别鸟与部署在非密区的巴别鸟以安全并且带审批的方式互传数据。以实现在企业监管下的密区和非密区的数据交换。 关于巴别鸟数据摆渡的详细信息，可以查阅 巴别鸟数据摆渡 章节。 智巢AI 智巢AI是巴别鸟企业网盘的AI平台，包括智巢AI客服、智巢AI知识库和智巢AI文档助理三个主要模块。这些模块结合了大模型API和自定义训练，能够满足企业的智能客服、文件内容分析和问题回答需求。 智巢AI的三个主要模块 智巢AI客服：该模块充当企业的AI客服，巴别鸟企业网盘自己也用了该模块回答用户在巴别鸟网盘使用中遇到的问题。我们也向企业客户开放这个服务，企业可以将产品说明书、FAQ、客服文档等资料提供给智巢AI进行学习，并微调以满足企业客服需求。企业还可以将智巢AI的代码块嵌入其网站，快速建立对外智能客服系统。智巢AI客服能显著降低客服成本，节约时间和资源。 智巢AI文档助理：这一模块用于回答关于单个文档的问题。通过分析文档内容，智巢AI能够回答关于文档内容的各种问题，从总结到揭示关键发现。用户可以向AI提问，而不必亲自阅读冗长的文档，从而提高工作效率。 智巢AI知识库：这一模块允许企业为自己定制专属AI助手。智巢AI团队会根据企业的资料帮助准备训练集、调参，从而建立专属的AI模型，可以根据巴别鸟上不同权限的人提供权限范围内的答案。可以以问答的形式作为企业知识库助手。 技术解决方案 智能回答问题：智巢AI借助大模型和自定义训练，以保证准确性。它还利用小模型来辅助大模型的工作，减少瞎说话、不懂装懂或泄密等问题。此外，智巢AI遵循巴别鸟的权限管理机制，确保用户只能获取其权限范围内的答案。 自动学习：智巢AI可通过学习用户提供的文件来积累知识，为用户提供更准确的答案。所有参与训练的文档都是由用户指定并同意的，以确保数据隐私和合规性。 优势 客服成本降低：智巢AI客服可以显著减少企业的客服成本，无需大规模培训人员，AI可以随时提供答案。 快速问题回答：智巢AI能够即时回答用户的问题，提高了工作效率。 文件内容分析：智巢AI文档助理可以快速分析文档内容，帮助用户快速获取信息，而无需阅读整个文档。 自定义AI助手：企业可以根据自己的需求为智巢AI知识库定制专属AI助手，以满足特定的知识管理和问题回答需求。 权限管理：智巢AI能够根据用户权限提供不同范围内的答案，以确保数据安全和合规性。 自动化任务 面对日益增长的数字资产，传统的人工文件管理模式已难以满足高效流转的需求。巴别鸟推出的 “自动化任务”引擎，旨在将繁琐、重复的文件处理动作交由系统后台自动执行。通过建立“自组织、自规范”的智能流转体系，大幅降低人工干预成本，让团队将精力聚焦于核心业务创造。 自动化任务包含在标准版中，用户无需另行购买。 核心运作机制： 灵活的权限驱动： 依托平台极细颗粒度的权限管理体系，凡具备目标网盘或文件夹相应权限的用户，均可按需自主配置、开启或关闭特定的自动化任务。 多任务流串联 (Workflow)： 自动化任务并非孤立运行，支持多规则自由组合形成工作流。例如：文件上传后，系统可先触发“自动重命名”规范文件名称，随后立即触发“自动整理”将其归档至相关目录，实现多步骤一气呵成。 持续扩展的能力矩阵： 自动化引擎具备高度的扩展性。除了现有的基础功能外，平台将持续接入更多的自动化处理节点，以满足日益复杂的业务场景。 当前已支持的核心任务（包括但不限于）： 自动重命名： 按预设规则（如关键字替换、大小写转换）统一标准化命名。 自动整理与清理： 依据触发条件自动分类归档文件，或按策略定期清理空间。 自动转 PDF 与签章： 自动为源文件生成 PDF 副本，或在云端加盖企业签章。 批量创建文件夹： 通过导入数据模板（如 Excel）一键生成标准业务目录树。 多任务协同与执行流转权重 在复杂的业务场景中，一个文件夹往往会叠加配置多项自动化任务。为保障数据处理的逻辑严密性与安全性，系统底层预设了严格的自动化处理先后顺序 。 具体执行权重（数值越高越优先执行）规范如下： 自动清理文件夹（权重 10）： 系统最高优先级。如有符合条件的清理任务将率先执行，以避免对即将被废弃的无效数据投入后续算力 。 自动解压缩（权重 9）： 优先将打包资产释放，以便进入后续流转 。 自动更名（权重 8）： 在文件进入分类归档前，优先完成命名的标准化统一 。 自动格式转化类（权重 7）： 优先完成如转存 PDF、图片或音视频格式的转换任务 。 自动整理 / 排序（权重 6）： 作为流转的末端节点执行 。这意味着文件在被移动和分类前，均已完成了清洗、重命名与格式转换等核心前置标准化操作。 自动清理文件 (Auto Clean) 功能概述 在日常的跨部门协作或项目周期管理中，企业网盘内往往会不可避免地产生大量的临时数据、过程文件或短期流转素材。 “自动清理文件” 功能旨在为企业提供自动化的存储空间优化与目录瘦身方案。通过该功能，系统能够按照用户设定的特定规则，自动删除指定文件夹中的冗余文件，长效保持项目目录的整洁度并释放高价值的存储资源。 核心运作与配置规则 本模块通过严密的逻辑规则引擎执行文件的清理动作，确保数据处理的精准与高效： 目标目录锁定： 任务配置需明确指定应用该规则的目标文件夹。用户可选择将规则仅应用于新进入该文件夹的文件，或同时溯源应用于目录内已存在的历史文件。 多维规则触发： 支持基于特定规则对文件进行精准筛选与剔除。常见的判定规则可涵盖文件类型（如特定后缀的临时文件）、生命周期（如文件进入目录超过指定天数）等维度，实现高度定制化的清理策略。 工作流协同： 作为完整自动化流转的末端环节，自动清理可与其他任务无缝衔接。例如，在“自动转 PDF”任务完成后，系统可随即触发“自动清理”规则，将原始草稿文件进行统一清理，仅保留标准化定稿。 权限与数据安全控制 鉴于清理任务涉及文件删除这一敏感操作，该功能深度依托巴别鸟的极细颗粒度权限管理体系： 配置权限： 仅拥有该文件夹相应高级权限（如管理、删除权限）的协作成员，方可新建或修改自动清理任务，从源头杜绝越权操作造成的数据流失。 无感且安全的执行： 后台静默执行清理任务，减少对用户前端操作的干扰，同时严格遵循企业既定的数据合规与回收站保留策略，确保数据资产的绝对安全。 典型业务应用场景 设计与研发类项目： 在建筑设计或科研管理中，工作软件常会自动生成大量的备份或缓存文件（如 .bak 或临时渲染文件）。通过配置自动清理任务，可设定定期自动识别并删除特定后缀的无用文件，保持核心图纸与文献目录的纯净。 公共资料交换区： 针对企业内部设置的“临时中转站”或“临时分享区”，可配置按时间维度（如“保留 7 天后自动清理”）的自动清理任务，实现公共空间的自组织与自净化，降低运维管理成本。 自动重命名 (Auto Rename) 功能概述 在多方协作、多频次资料收集的业务场景中，由于操作人员习惯差异，文件命名往往缺乏统一规范，给后续的检索、归档与审计带来极大困扰。 “自动重命名” 功能允许系统对上传至指定文件夹的文件，按照高度定制化的预设规则进行自动化的名称重构 。该机制有效杜绝了因人为因素导致的命名混乱，确保企业数据资产入库即达标。 适用范围与权限控制 权限驱动： 该功能的启用严格依托于用户的操作权限。只要用户对目标文件夹（涵盖个人、部门、项目或素材库等各类文件夹）拥有“上传”及“重命名”权限，即可为其配置自动重命名任务 。 溯源处理： 规则不仅作用于新上传的文件，用户还可选择将其溯源应用于目标目录及其所有子文件夹中已存在的历史文件 。为保障系统性能与执行稳定性，批量溯源重命名的单次处理上限为 5000 个文件 。 核心规则引擎与配置维度 巴别鸟提供了一个高度灵活的可视化规则拼接引擎。用户可添加多个命名规则，并通过拖拽的方式对规则进行自由排序 。配置界面全程提供实时变化的“示例文件名”，帮助用户直观预览重命名规则的叠加结果 。 规则引擎支持以下多维度的命名元素： 标准属性变量： 支持提取并插入系统级变量，包括文件上传者、文件负责人、上级文件夹名称以及上传时间 。 多媒体元数据 (Metadata)： 针对图像等特定格式文件，系统可深度解析并提取其底层元数据作为命名依据，如拍摄日期、相机制造商/型号、镜头型号、尺寸以及 DPI/DPCM 等参数 。 自定义文本与连续编号： 用户可自由插入自定义文本内容 。在编号机制上，与传统的单次批量重命名不同，自动重命名具备状态记忆（延续性）。系统会自动读取目标列表中最后一个符合规则的编号，确保跨批次、跨时段上传的文件能够实现序号的无缝延续 。用户可精确设定编号的起始值、增量值及具体位数 。 原始名称的精细化修剪与防冲突机制 除了添加新前/后缀，系统同样支持对文件原有的名称进行深度结构化清洗： 名称修剪与替换： 可对原始文件名执行“替换特定内容”、“删除指定内容”操作 。此外，还提供一键“删除字符”功能，精准剔除文件名中的冗余空格、数字、引号、破折号及下划线 。 强制防冲突保护： 若用户在规则中选择完全删除“原始文件名”（即上传时不保留原名），为避免同名文件相互覆盖的风险，系统会强制要求并在规则链中自动追加一项“编号”规则 。 日期逻辑互斥： 在调用日期类变量时，用户可勾选“替换在文件名中检测到的日期” 。为防止逻辑冲突，在单一重命名任务中，该替换指令仅允许被某一时间变量（如“上传时间”或“拍摄时间”）勾选一次 。 全局格式化输出控制 在完成规则变量的拼接后，系统支持在输出端进行统一的格式化规范： 大小写标准化： 支持一键将拼装后的文件名转换为首字母大写、首字母小写、全部大写或全部小写，满足不同企业的视觉规范 。 字词分隔统一： 支持在各个命名规则模块之间统一插入标准化的分隔符（如空格、下划线或破折号），进一步提升文件名的机读与人读体验 。 自动转 PDF (Auto to PDF) 功能概述 在跨企业协作、外部资料分发以及项目定稿归档等业务环节中，PDF 格式因其跨设备显示的一致性与防篡改特性，成为了标准的文档交换媒介。巴别鸟的“自动转 PDF”功能，旨在建立一个自动化的文件格式标准化通道。配置该任务后，当文件被添加到选定的目标目录，系统将在后台静默触发转换引擎，将其自动转换为标准的 PDF 文件 。该能力大幅消除了人工逐一导出 PDF 的低效劳动，确保了数据对外输出与对内归档的规范性。 执行逻辑与边界条件 为保障平台底层计算资源的高效运转以及企业数据流转的安全可控，自动转换任务设定了以下执行逻辑与边界限制： 作用域与溯源处理： 该任务可向下覆盖，支持勾选应用于目标目录及其所有子文件夹中的文件 。此外，规则同样支持向历史数据溯源，可应用于目录内的现有文件，但为保障执行稳定性，单次溯源处理的文件数量被严格限制在 5000 个以内 。 系统性能保护机制： 为避免超大源文件在转换过程中长时间占用算力并导致任务队列阻塞，系统内置了文件体积阈值，即超过 30MB 的大体积文件将不会触发自动转换机制 。 存储空间自动释放： 针对“仅需保留定稿 PDF”的特定业务场景，用户可在任务配置界面勾选“转换成功后删除原文件”选项 。开启该策略后，系统将在确认 PDF 副本生成无误的前提下自动清理原始文件，从而大幅度优化网盘存储空间的利用率 。 广泛的格式兼容矩阵 巴别鸟自动转换引擎具备强大的多格式解析能力，支持将 32 种不同行业的主流业务文件自动化转储为 PDF 。用户可选择针对“所有支持的文件”执行转换，也可通过下拉菜单按类别精准勾选所需转换的扩展名 。具体支持的格式矩阵如下： 文档排版类： 全面兼容主流办公与出版软件产生的源文件，包括 doc、docx、ppt、pptx、wps、epub、dpt、indd、rtf、docm 以及 pptm 。 图片与影像类： 支持主流位图、数字底片及医疗影像格式的渲染转换，涵盖 jpg、bmp、jpeg、jpg2、png、psd、tif、tiff、raw、cr2、dcm 以及 heic 。 图形与工程图纸类： 深度适配设计与建筑工程领域的矢量及 CAD 图纸转换，支持的格式包含 ai、svg、eps、dwg、dwt 以及 dxf 。 自动整理文件 (Auto Organize) 功能概述 随着平台内协作数据的沉淀，如何保持底层“任意文件夹同步”架构与权限管控目录的整洁，成为了企业数字资产管理的关键。 “自动整理文件” 功能允许系统按预置的时间周期或内容特征，将文件自动分类并路由至相应的目标目录。该功能确保了海量文件在流转过程中的高度结构化，避免了人工归档的滞后性与错漏。 灵活的触发机制与作用域 用户可通过文件夹右键菜单中的“任务”选项 ，或左侧的自动化任务列表面板进入配置 。配置涵盖以下触发与作用规则： 事件驱动（默认）： 当文件被上传或者移动到指定的触发文件夹时，系统即刻响应并开始整理动作 。 周期驱动： 适用于集中式的数据归档场景，系统可按固定的周期（例如设定为每天 23:00）统一执行文件整理 。 历史溯源： 规则既可应用于新增文件及所有子文件夹，也可勾选“应用于现有文件”对历史存量数据进行批量溯源整理。为保障系统平稳，溯源处理单次不得超过 5000 个文件 。 核心智能整理规则引擎 系统提供三种高度自定义的分类规则，满足不同维度的数据归档需求： 1. 基于时间维度的结构化归档（按月 / 按年分类） 系统可按文件添加到网盘的对应年份或月份自动创建对应的子文件夹（例如“2025”、“2025 10”）并将相关文件移入 。 执行按年或按月分类时相同 ，系统具备按需建档的智能性，如果特定周期内（如某个月）没有产生文件，则系统不会冗余创建该月的空文件夹 。 2. 基于内容的智能路由（按关键字分类） 根据文件名中包含的特定关键字，系统将文件自动分发并移动至预设的目标文件夹 。 格式识别： 文件扩展名（如“jpg”）同样可作为关键字配置，实现特定类型素材的定向归集 。 多线并行路由： 用户可通过“添加关键字分类”按钮持续增加多条路由规则 。既支持将包含不同关键字的文件分别分发到不同的目录 ，也支持将多条关键字任务统一指向同一个目标文件夹 。 防重名与优先级控制： 关键字匹配严格按任务设定的先后顺序处理。例如，当文件名为“123ABC定稿.jpg”，若关键字列表第一项规则为“123”，第二项为“定稿”，则该文件将优先匹配“123”的规则并执行移动 。系统内置防重复检测，每个关键字仅允许输入一次，重复输入会触发“请重新输入”的错误拦截 。 同名冲突化解： 在执行文件移动与整理的过程中，如在目标文件夹内遇到重名文件，系统会自动在文件名后附加编号，以确保数据不被意外覆盖 。 创建签章 (E Sign) 业务场景与功能概述 在企业的合同审批、图纸会签及业务合规流转等关键环节中，具备防篡改属性的数字化签署是打通线上协作闭环的核心节点。传统的跨系统签署往往伴随繁琐的文件下载与格式转换。巴别鸟推出的 “创建签章” 功能，允许用户直接在云端网盘的工作流中对文件进行盖章与签署 。该引擎支持多种主流文件类型直接加载印签，并支持将签署完毕的文件一键导出为标准的 PDF 格式，从源头保障数字资产的安全、合规与不可篡改性 。 签章资产库与个性化配置 系统为用户提供了一个高度集成的数字印签管理控制台，确保电子签章资产的统一沉淀与快速调用： 多元签名采集： 在“签名设置”模块中，用户既可以调用终端进行在线“添加手写签名”，也支持直接“上传签名图片文件”（如含透明通道的 PNG 素材），以满足不同层级的签署合规要求 。 企业图章管理： 在“图章设置”模块，企业用户可按需上传业务专用的电子公章或合规图章图片 。 默认优先级状态： 针对拥有多个印签资产的用户，系统支持一键将其中的特定签名或图章“设置为当前使用”（默认印签） 。在后续的文档预览与流转界面中，系统将优先调用该默认印签，极大提升高频审批场景下的签署效率 。 智能自适应交互与沉浸式引导体系 为兼顾不同硬件终端的显示极限并降低用户的学习门槛，签章配置中心采用了多断点的智能响应式（Responsive）界面架构，并深度嵌入了多语言操作指引： 宽屏工作站模式（窗口宽度 ≥ 1120px）： 当用户在桌面级宽屏设备上操作时，系统不仅在左侧保留标准的签章配置面板，还会在右侧自动展开独立的视频教学区。该区域会自动加载并无感循环播放签章使用教程（播放完毕停顿 3 秒后重播），为用户提供“边学边配”的沉浸式体验 。 紧凑聚焦模式（窗口宽度 ＜ 1100px）： 当处于较窄的屏幕或移动端窗口时，系统会智能折叠右侧的视频播放区，以最大化保障核心签署设置区的视觉焦点 。同时，系统在界面底部提供“如何使用签章？”入口，用户点击后可唤起全屏教程播放 。 国际化双语支持： 考虑到跨国企业的协作需求，系统内置了本地化的教学视频库。除中文语言环境播放专属中文教程外，其他所有多语言版本均默认匹配并播放标准英文教程，保障全球业务团队的无障碍落地 。 批量创建文件夹 (Batch Create Folders) 功能概述与业务价值 在多项目并发或企业部门架构调整的业务场景中，由人工逐一建立复杂的标准目录树不仅耗费大量操作时间，且极易因人为疏漏导致目录层级错乱或命名不规范。巴别鸟提供的 “批量创建文件夹” 功能，允许用户通过外部结构化数据（如 Excel、CSV、TXT 文本）直接驱动云端目录的生成 。该功能可将标准化的业务目录模板瞬间转化为可落地的网盘文件夹阵列，极大提升了大型项目启动阶段的初始化建档效率。 标准目录阵列的大规模生成 该模块具备强大的数据解析能力与人工容错干预机制： 高并发支持： 系统支持通过导入 xls、xlsx、csv 或 txt 格式的文件，按换行符规则快速读取目录清单，单次批处理任务的上限高达 5000 行，满足绝大多数企业级数据结构的生成需求 。 可视化预审与动态干预： 在正式执行批量创建前，系统会完成数据解析并在界面中直观渲染出即将生成的文件夹列表与层级关系 。在此预览环节中，用户可直接通过鼠标右键或悬浮菜单，对特定的预设目录执行“创建子文件夹”、“重命名”或“删除”等即时修改动作 。这一“先审后建”的机制，确保了最终落地的目录树与业务需求绝对对齐。 项目级文件夹与权限的“一键部署” 当目标路径设定为部门文件夹或个人文件夹的根目录时，系统支持创建更为高阶的 “项目文件夹” 。该模式深度结合了巴别鸟的底层权限管理体系，实现了目录构建与成员权限配置的同步落地： 专属标准模板： 批量生成项目文件夹需下载并使用系统专属模板导入数据 。若上传的非标文件不符合解析格式，系统将严格拦截并提示重新上传 。 项目角色与权限预设： 模板不仅规范了“项目文件夹名字”，还支持直接关联账号系统预设“项目负责人”与“项目成员” 。 负责人指派： 填写的负责人 ID（支持手机号、邮箱或特定的工号格式）必须为已注册的企业成员；若该字段留空或填写的身份无法校验，系统将遵循安全保底原则，默认将当前创建任务的操作者设为项目负责人 。 成员自动化邀请与赋权： 用户可在模板中通过逗号分隔批量录入多位项目成员 。项目目录生成后，系统将自动向这些成员发送邀请通知，并为其赋予基础的“上传及下载”默认权限 ，彻底免除了建档后繁琐的逐一授权操作。 实时状态监控与智能容错机制 在执行大规模创建任务时，系统后台会以队列形式稳健处理，并在前端提供全方位的进程监控与异常修复闭环： 全局进度追踪： 创建过程中，列表节点会实时更新其执行状态（从代表正在执行的转圈动画，平滑过渡至代表成功的确认勾选状态） 。任务全局状态亦会从“创建中”明确流转至“完成” 。 精准异常归因与重试： 全部任务执行完毕后，系统顶部会输出清晰的结果汇总（如“共创建了 XXX 个文件夹，失败 X 个”） 。用户可一键查阅“创建失败文件列表” 。系统会将失败原因精确归类为“包含文件名不允许字符”或“已有同名文件夹”等系统级冲突 。针对这些异常条目，用户不仅可以查明原因，还能直接在界面上点击绿色的“重试”按钮触发二次创建 ，大幅降低了批量运维的阻力。 文控项目 文控项目是巴别鸟的一个行业应用独立模块（需要另行购买）。巴别鸟文控项目解决了工程设计行业中的文控标准的流程管理（DCC）及自动化问题。提高了大量文控人员的工作效率的同时也降低了人为失误的可能。 使用范围 需要严格管理每一次文件发送的行业或企业。每次发送给客户的文件都由特定人员发送（文控人员）每次发送都有发送单据可查，能明确的管理发送内容。通过发送单号可以查询到每次发送文件给接收方的具体信息和文件。同时对接收方是否收件，对发送过去的内容是否驳回都可管理查询。并且发送单可以作为凭据。 需要解决的问题 目前很多企业的文控流程基本是靠手动，文件存储于EDMS系统或文控人员电脑本地。依靠文件夹分类来管理文档，每次发送文件手动建立一个文件夹，按文件名规范命名文件夹，文件通过邮件发送后把发送的文件放入文件夹并附上本次发送的TRANSMITTAL（文件发送单）。 每次发送都会产生一个文件夹及相应的TRANSMITTAL。这些工作人工操作相当繁琐，除了整理文件，每次还需要手动填写文件发送单，手动按规则编写发送单编号，日后还要手动核对，效率极低。 巴别鸟解决方案 可新建新的文控项目类型。这意味着不同的项目可以设定不同的TRANSMITTAL（发送单）规则生成不同的发送单和发送单号。不同项目也可以管理不同的收件人（收件企业） 可设定每个项目的文件接收方，统一管理文件接收方。 文控项目中的文档支持发送功能，发送功能支持多选。选择文件或文件夹发送后，收件人可以通过邮箱收到所发送文件的下载link和TRANSMITTAL（发送单）。并且通过下载link下载到的文件是发送时的版本。 每次发送的文件都是文件当前版本，文件升版会形成新的版本号，并在发送单显示。 文件发送后根据预先设定的规则自动生成本次发送的TRANSMITTAL（发送单）和TRANSMITTAL NO.（发送单号） 可以管理及查询所由TRANSMITTAL（发送单），并可导出发送单为PDF。 巴别鸟文控项目使用指引： 基本介绍 巴别鸟文控管理系统是在巴别鸟企业私有云版的基础上增加文控管理模块，以实现文控工作的自动化。 文控管理的方式是以建立“文控项目”的方式来实现。文控项目是针对文控需求特别定制的特殊项目，以项目为单位进行管理。 建立文控项目 登录系统后，在要创建文控项目的部门中点击“新建”——“新建项目” 项目只能建立于根目录（企业文件）或部门根目录下 例：在HQSM文控这个部门下建立一个文控项目 点击新建项目，出现项目类型选择界面 选择“创建文控管理项目” 这时候出现项目初始化选择界面 按照项目的要求填写初始化信息 每项的介绍如下： 项目负责人 管理、转交项目、修改项目权限及基础信息。不可为空。可删除TRANSMITTAL 项目秘书 不可转交项目，其他同项目负责人，可多人，可为空。可删除TRANSMITTAL 文控人员 可以发送文件给接收人。其他权限可配置，可多人，可为空。选择人员后点击右侧权限选择下拉框可以批量修改成员权限（如图）。 其他成员 没有发送文件选项，其他同普通项目普通成员，权限可配置，可为空。 版本号规则 如图，如果前缀填写为HQSM，文件的第一个版本就为 HQSM A ，第二个版本为 HQSM B以此类推 基本信息 基本信息的填写内容将显示于TRANSMITTA头部。 如图：画红圈处就是填写的基本信息。 接收方信息 接收方信息决定了发件时的可选项和所发文件的TRANSMITTA号 收件方名字是指收件方在系统中的称呼，一般填写收件方的企业简称，如 MCC 邮箱支持添加多个，添加多个后，一次发送就可以向多个邮箱地址发送文件及TRANSMITTA ATTN可以任意输入，同时也会显示在TRANSMITTA上 运单号规则其实就是TRANSMITTA号的自动生成规则，不同的收件方可以生成不同的运单号。所以需要在每个收件方处设定不同的运单号规则。 规则自定义界面示意如下： 3栏分别为TRANSMITTAL号的3个组成部分，如果所需的TRANSMITTA号需要更多的编码来组成也可以点击+号来增加更多栏 例： 第一栏选择输入文字，弹出文字输入框，输入 “HQSM ” 第二栏选择编码规则为1 2 3数字顺序 第三栏选择 文字输入、输入“ 2020” 点加号新增一栏，选择a b c字母顺序 第一次发送生成的TRANSMITTAL号即为： HQSM 1 2020a 第二次发送生成的TRANSMITTAL号为：HQSM 2 2020b 选择字母作为编号超过26个后，z号的下一个版本自动变为a1 如果该项目有多个接收方，也可以点击来增加。（项目建立后也可以在项目管理界面中去增删接收方。 这些填写完成后，点击“新增项目”就完成了项目的新建 你可以在创建项目路径的文件列表中看到新建的文控项目，点击即可进入 文控管理项目不同于普通项目，项目首页顶部栏增加了文控管理的按钮 其中“发送单列表”可以查询该项目发出的所有TRANSMITTA，管理项目可以对项目进行管理。 上传文件 点击新建的文控项目，进入项目页面。 直接拖拽想要上传的文件到项目中即可上传文件，当然，你也可以和使用普通文件夹一样使用同步功能进行上传下载。 发送文件 选中要发送的文件（支持多选），然后点击右键，选择“发送文件”会出现文件发送界面 每次最多发送的文件为2000个（包含文件夹）。如项目需要全部文件发送，建议以压缩包形式进行发送。 收件人可以下拉选择项目初始化时填写的收件人及ATTN 抄送可以填写其他任意邮箱地址，也可以留空不填写 选择的提交文件类型也会在生成的TRANSMITTA中显示 文件列表罗列了本次要发送的文件。 系统要发送TRANSMITTAL的文件名构成为 文件编号+描述，如一个文件文件名为 1000+图纸.pdf，发送时显示在TRANSMITTAL的文件编号为“1000”，描述为“图纸”。如果发送的文件的文件名中没有+分割，文件编号就显示文件名，如果发送的文件名为“+图纸.jpg“就不显示文件编号，显示描述为“图纸”。描述可中途更改。 附言将会在收件人接受到的邮件中显示并不会显示在TRANSMITTAL中 填写完成后点击“发送文件”系统会自动生成TRANSMITTAL并作为link附在邮件中发送给客户。 生成TRANSMITTAL 发送成功后系统会弹出提示 点击查看，就能查看本次发送自动生成的TRANSMITTAL 点击导出为PDF就可以把该TRANSMITTAL保存为PDF文件 你也可以在传送单列表（TRANSMITTAL list）中去查看该项目中发送的所有TRANSMITTAL 收件人在邮箱中收到的TRANSMITTAL和该TRANSMITTAL一致。 查看TRANSMITTAL 在项目首页点击发送单列表（TRANSMITTAL list） 打开列表就可以看到及查询本项目的所有发送单。 点击传送单号可查看详情并下载TRANSMITTAL的PDF文件 为接受就是接受方并没有打开已发送的邮件，如对方打开邮件并访问了TRANSMITTAL，接收状态会变为已接收。 查看发送记录 在任意文件上右键点击，可查看该文件的发送记录及其对应的TRANSMITTAL" }, { "lang": "zh", "slug": "reference-whitepaper-06-user-interface", "title": "白皮书：用户界面", "description": "《巴别鸟企业网盘白皮书》章节：用户界面。", "category": "源资料参考", "top_category": "维护", "keywords": [ "白皮书", "用户界面" ], "url": "zh/reference-whitepaper-06-user-interface.html", "source": "content/zh/reference-whitepaper-06-user-interface.md", "summary": "白皮书：用户界面 用户界面设计 巴别鸟界面设计理念 企业网盘集成的功能比较多，如何合理分配功能入口，让用户实际使用时更加方便？是一个界面设计和交互时需要重点考虑的问题，目前有两种互有冲突的设计理念。 界面设计理念 优缺点 隐藏非常用功能，保证界面简洁，降低学习难度，易上手，初次使用体验友好。（代表：微云、腾讯文档等2C产品） 前缓后陡的学习曲线，用户初次试用时体验好，但实际长期使用时不方便 功能入口显性化，界面复杂，但需要的功能可以快速找到。界面较重，学习成本稍高，初次使用体验不友好。（代表：office、CAD等专业软件） 前陡后缓的学习曲线，用户初次使用体验复杂，但实际长期使用方便。不利于营销。 考虑到企业网盘是一个面向企业长期使用的专业产品，前期陡峭的学习曲线虽然不利于营销（用户简单试用时弃用率增高）但是对应选择巴别鸟的用户长期使用是友好的，熟悉后能更好用更有条理，而作为一个生产力工具，日常使用的便捷度和降低出错概率更加重要。所以巴别鸟企业网盘选择了第二种设计理念： 作为一个专业面向企业场景的产品，为用户长期日常使用时的便捷性，可以适当增加上手复杂度。 界面设计原则 用户友好性: 在保证功能使用优先的前提下，强调用户友好性，确保用户能够轻松使用企业网盘。 一致性: 维持一致的界面设计，以提供一致的用户体验。 简洁性: 采用简洁的设计，减少冗余和复杂性，使用户能够迅速理解界面。 可用性: 确保功能模块容易被用户找到并有相应指引，3步内直接可以使用。 用户界面元素 网页版（web） 采用左菜单、右文件列表、顶部功能分区的布局。方便用户注意力集中在文件列表上。 左侧菜单可以收起", "headings": [ { "level": 1, "title": "白皮书：用户界面", "id": "section" } ], "images": [], "text": "白皮书：用户界面 用户界面设计 巴别鸟界面设计理念 企业网盘集成的功能比较多，如何合理分配功能入口，让用户实际使用时更加方便？是一个界面设计和交互时需要重点考虑的问题，目前有两种互有冲突的设计理念。 界面设计理念 优缺点 隐藏非常用功能，保证界面简洁，降低学习难度，易上手，初次使用体验友好。（代表：微云、腾讯文档等2C产品） 前缓后陡的学习曲线，用户初次试用时体验好，但实际长期使用时不方便 功能入口显性化，界面复杂，但需要的功能可以快速找到。界面较重，学习成本稍高，初次使用体验不友好。（代表：office、CAD等专业软件） 前陡后缓的学习曲线，用户初次使用体验复杂，但实际长期使用方便。不利于营销。 考虑到企业网盘是一个面向企业长期使用的专业产品，前期陡峭的学习曲线虽然不利于营销（用户简单试用时弃用率增高）但是对应选择巴别鸟的用户长期使用是友好的，熟悉后能更好用更有条理，而作为一个生产力工具，日常使用的便捷度和降低出错概率更加重要。所以巴别鸟企业网盘选择了第二种设计理念： 作为一个专业面向企业场景的产品，为用户长期日常使用时的便捷性，可以适当增加上手复杂度。 界面设计原则 用户友好性: 在保证功能使用优先的前提下，强调用户友好性，确保用户能够轻松使用企业网盘。 一致性: 维持一致的界面设计，以提供一致的用户体验。 简洁性: 采用简洁的设计，减少冗余和复杂性，使用户能够迅速理解界面。 可用性: 确保功能模块容易被用户找到并有相应指引，3步内直接可以使用。 用户界面元素 网页版（web） 采用左菜单、右文件列表、顶部功能分区的布局。方便用户注意力集中在文件列表上。 左侧菜单可以收起，显示更多文件列表内容，提供沉浸式体验。 为了更好的树状管理文件，也可以打开树状视图类似windows资源管理器一样管理文件。 如果文件夹图片文件数量多，可自动打开瀑布流预览模式，便于用户查看。 左侧菜单（快捷方式）用户可以自定义，便于用户日常按使用习惯自定义快捷入口。 文件/文件夹的所有功能操作集中在右键，容易找到，常用功能显示在文件列表上，同时文件列表栏也有相应按钮，防止因鼠标右键失效影响用户操作。 客户端（windows、mac、麒麟） 客户端使用Electron及C++进行跨平台开发，很好的保证了风格一致性和操作一致性。并且针对各平台也有各自的优化。客户端还包括同步模块、上传下载列表及虚拟映射盘（云桥）模块。 主操作界面延续网页版风格和布局，但针对本地软件的使用习惯及客户端独有模块进行了布局上的改进，把顶部功能分区集中在左侧栏，让顶部显示更简洁。 左侧栏增加了传输和同步两个客户端独有功能按钮及入口。 文件传输模块，管理同步进程和上传下载任务。 在windows和MacOS系统文件右键菜单上集成了同步和上传、发送文件的快捷方式，便于用户快速建立同步和上传文件（夹）。 在windows和MacOS上集成了虚拟映射盘，让用户可以像访问本地硬盘一样访问云端文件。 响应式设计 响应式设计原则 多设备兼容性: 巴别鸟企业网盘的用户界面被设计为在各种设备上获得最佳体验，包括桌面、移动设备和平板电脑，以保证用户随时随地用各种设备都能有良好的体验。 图：巴别鸟从诞生起就是跨平台的 自适应布局 用户界面元素会自动根据屏幕尺寸和方向进行调整，以确保内容的可见性和可用性。 触摸友好性: 优化移动设备上的触摸交互，包括手势控制、滑动和缩放。 图像和媒体优化: 使用了预载入、图像转码生成缩略图和媒体压缩技术，以减少页面加载时间和带宽使用。 移动端支持 网页版本移动设备优化 移动界面设计: 巴别鸟网页版本有针对移动设备打开设计的H5页面，及宣传网站移动版及分享链接移动版下载界面，支持常见触摸手势，如滑动、缩放和点击。 图：移动设备访问巴别鸟H5页面 移动APP: 为了获得更好的使用体验，巴别鸟开发了移动端专用的APP，支持安卓和iOS系统。 为保证良好的性能，巴别鸟APP都以原生应用的方式进行开发。 APP的交互、界面、功能模块都全部重新设计，以适合在移动设备上访问。 图：移动端界面 平板电脑优化 巴别鸟iOS APP针对iPad重新设计制作了界面，以更适应在大屏幕上工作。" }, { "lang": "zh", "slug": "reference-whitepaper-07-performance", "title": "白皮书：性能优化", "description": "《巴别鸟企业网盘白皮书》章节：性能优化。", "category": "源资料参考", "top_category": "维护", "keywords": [ "白皮书", "性能优化" ], "url": "zh/reference-whitepaper-07-performance.html", "source": "content/zh/reference-whitepaper-07-performance.md", "summary": "白皮书：性能优化 负载均衡策略 鉴权认证与服务分离 分离鉴权认证: 为了提高系统的性能和安全性，巴别鸟企业网盘采用了鉴权认证与核心服务分离的策略。这意味着用户的鉴权认证请求会被路由到专门的认证服务器上，而上传、下载以及查询浏览等核心服务请求会被路由到相应的核心服务服务器上。 请求路由: 我们使用负载均衡器来根据请求类型将请求路由到不同的服务器。这确保了鉴权认证服务器不会成为核心服务的性能瓶颈，并允许我们根据需求独立扩展认证和核心服务。 相同类型请求的多台服务器部署 多服务器支持: 巴别鸟企业网盘允许相同类型的请求在多台服务器上部署，以提高性能和可用性。这种多服务器支持策略确保了即使一台服务器出现故障，其他服务器仍然可以处理请求。 请求平均分配: 我们使用负载均衡算法将相同类型的请求均匀分配到多台服务器上，以避免服务器过载和提供更快的响应时间。 负载均衡器 负载均衡器配置: 我们使用专业的负载均衡器来实现请求的分发和路由。负载均衡器根据预定的规则将请求发送到适当的服务器。 监控和自动故障转移: 负载均衡器配备了监控功能，能够检测服务器的健康状态。如果某台服务器出现故障，负载均衡器会自动将请求路由到其他可用的服务器，以确保系统的连续性。 优势 性能提升: 负载均衡策略提高了系统的性能，允许请求在多台服务器上并行处理，减少了单一服务器的负载。 高可用性: 多台服务器的部署和自动故障转移确保了系统的高可用性，即使出现故障，仍然可以提供服务。 扩展性: 负载均衡策略允许根据需求添加更多的服务器，以满足不断增长的用户和请求。 缓存管理 文件缓冲区管理 文件缓冲区设置: 为了优化性能并减轻C", "headings": [ { "level": 1, "title": "白皮书：性能优化", "id": "section" }, { "level": 3, "title": "优势", "id": "section-2" }, { "level": 3, "title": "优势", "id": "section-3" }, { "level": 3, "title": "优势", "id": "section-4" }, { "level": 3, "title": "优势", "id": "section-5" } ], "images": [], "text": "白皮书：性能优化 负载均衡策略 鉴权认证与服务分离 分离鉴权认证: 为了提高系统的性能和安全性，巴别鸟企业网盘采用了鉴权认证与核心服务分离的策略。这意味着用户的鉴权认证请求会被路由到专门的认证服务器上，而上传、下载以及查询浏览等核心服务请求会被路由到相应的核心服务服务器上。 请求路由: 我们使用负载均衡器来根据请求类型将请求路由到不同的服务器。这确保了鉴权认证服务器不会成为核心服务的性能瓶颈，并允许我们根据需求独立扩展认证和核心服务。 相同类型请求的多台服务器部署 多服务器支持: 巴别鸟企业网盘允许相同类型的请求在多台服务器上部署，以提高性能和可用性。这种多服务器支持策略确保了即使一台服务器出现故障，其他服务器仍然可以处理请求。 请求平均分配: 我们使用负载均衡算法将相同类型的请求均匀分配到多台服务器上，以避免服务器过载和提供更快的响应时间。 负载均衡器 负载均衡器配置: 我们使用专业的负载均衡器来实现请求的分发和路由。负载均衡器根据预定的规则将请求发送到适当的服务器。 监控和自动故障转移: 负载均衡器配备了监控功能，能够检测服务器的健康状态。如果某台服务器出现故障，负载均衡器会自动将请求路由到其他可用的服务器，以确保系统的连续性。 优势 性能提升: 负载均衡策略提高了系统的性能，允许请求在多台服务器上并行处理，减少了单一服务器的负载。 高可用性: 多台服务器的部署和自动故障转移确保了系统的高可用性，即使出现故障，仍然可以提供服务。 扩展性: 负载均衡策略允许根据需求添加更多的服务器，以满足不断增长的用户和请求。 缓存管理 文件缓冲区管理 文件缓冲区设置: 为了优化性能并减轻CPU资源负担，巴别鸟企业网盘实施了文件缓冲区管理。解密后的文件将暂时存储在缓冲区中，以减少重复解密操作。 LRU策略: 我们采用最近最少使用（LRU）策略来管理文件缓冲区。这意味着最不常使用的文件缓存将被淘汰，从而保持缓冲区的高效利用。 文件鉴权缓冲管理 文件鉴权缓冲: 鉴权检测对于文件访问的权限是复杂而耗时的。针对文件所在部门、项目、分享以及保密级别等多个因素，需要进行综合性的鉴权检测。为了提高性能，我们实施了文件鉴权缓冲，将鉴权结果缓存起来。 过期淘汰机制: 文件鉴权缓冲采用过期淘汰机制。每个缓存条目都有一个预定的过期时间，一旦超过该时间，缓存将被自动淘汰。这确保了缓存数据的新鲜性，并降低了内存使用。 优势 性能优化: 缓存管理减少了解密操作和鉴权检测的重复执行，从而提高了系统的响应速度和性能。 资源节约: 通过使用LRU策略和过期淘汰机制，我们有效地管理了内存资源，避免了内存泄漏和过度占用的问题。 复杂鉴权的快速响应: 文件鉴权缓冲确保了复杂的鉴权检测结果的快速响应，减少了对鉴权服务的压力。 数据压缩和传输优化 文件分块技术 文件分块存储: 为了优化文件的传输和存储，巴别鸟企业网盘采用了文件分块技术。大文件会被分成小块，并分别存储在服务器上。这有助于提高文件的传输效率和断点续传的支持。 并行块请求: 文件分块存储允许前端在文件下载时并行发起多个块的请求。一旦所有块都被下载，前端将它们组装成完整的文件，从而显著提高了下载速度。 基于哈希码的文件存储去重技术 文件去重: 巴别鸟企业网盘采用基于哈希码的文件存储去重技术。当用户上传文件时，系统会计算文件的哈希码并与已有文件的哈希码进行比较。如果发现相同的哈希码，系统将只保留一份文件的副本，从而节省存储空间。 节省存储空间: 文件去重技术有效减少了存储冗余，特别是在企业中频繁共享和传输的文件，从而降低了存储成本。 优势 传输效率: 文件分块技术和并行块请求加速了文件的传输速度，特别是对于大文件和高带宽连接。 存储节省: 基于哈希码的文件存储去重技术降低了存储需求，降低了维护成本。 用户体验: 快速的文件传输和节省存储空间改善了用户体验，提供更高效的文件管理和共享。 异步任务处理 后台异步处理 任务耗时处理: 为了处理那些前台发出的可能比较耗时，甚至可能导致HTTP请求超时的任务，巴别鸟企业网盘采用了后台异步处理的策略。这些任务不会阻塞主要的HTTP请求响应，而是在后台异步执行。 提高响应速度: 后台异步处理确保了前台请求的响应速度不受到耗时任务的影响，提高了用户体验。 配置化管理异步任务 任务队列: 为了防止服务器资源紧张，我们对异步任务进行了配置化管理。可以将异步任务配置为一个或多个处理队列，这些队列可以独立执行任务。任务队列可以根据任务的类型和优先级进行配置和管理。 消息队列: 另一种管理异步任务的方式是使用消息队列。巴别鸟企业网盘可以配置为使用消息队列来存储和调度异步任务。这种机制可以确保任务的有序执行和可控制性。 消息处理机制: 异步任务通过消息处理机制进行控制和执行。任务被加入队列或消息队列后，由专门的处理器进行处理和执行。 优势 响应性: 后台异步处理提高了系统的响应速度，避免了长时间的等待。 资源控制: 配置化管理异步任务允许对服务器资源进行有效的控制，防止资源耗尽。 可扩展性: 消息队列和消息处理机制提供了系统的可扩展性，可以轻松添加新的异步任务类型。" }, { "lang": "zh", "slug": "reference-whitepaper-08-scalability", "title": "白皮书：可扩展性", "description": "《巴别鸟企业网盘白皮书》章节：可扩展性。", "category": "源资料参考", "top_category": "维护", "keywords": [ "白皮书", "可扩展性" ], "url": "zh/reference-whitepaper-08-scalability.html", "source": "content/zh/reference-whitepaper-08-scalability.md", "summary": "白皮书：可扩展性 水平扩展 集群部署: 巴别鸟企业网盘业务服务器采用集群部署模型，这允许我们轻松扩展系统的容量和性能。集群中的多台服务器协同工作，以分担负载并提供高可用性。这种模型允许我们根据需求添加新节点，以满足不断增长的用户和数据需求。私有云部署客户在用户增长时也可以通过增加虚拟机或物理服务器的方式来扩充性能以满足高并发需求。关于巴别鸟集群部署可扩展性的更多信息，可以查看 分布式部署 章节。 对象存储系统: 巴别鸟的存储系统采用对象存储技术，这种技术非常适合大规模的数据存储和水平扩展。对象存储系统具有高度的可伸缩性，可以容纳大量的数据，并在需要时增加存储节点自动扩展存储容量。关于巴别鸟对象存储扩展性的更多信息，可以查看 自建对象存储 章节。 负载均衡: 我们实施了负载均衡策略，确保用户请求被均匀分配到集群中的各个节点，以避免单点故障和提供更快的响应时间。 自动伸缩（公有云）: 得益于阿里云ECS弹性计算服务，我们的系统配置了自动伸缩机制，根据负载情况自动增加或减少服务器节点。这种自动伸缩保证了系统的稳定性和性能。 垂直扩展 硬件升级: 除了水平扩展，针对私有云用户我们还可以进行垂直扩展，即升级服务器硬件以增加单个服务器的性能和容量。这在需要更多计算能力或内存的情况下是一种有效的解决方案。 数据库优化: 我们还可以优化数据库系统，通过调整配置、使用更高性能的硬件或升级数据库管理系统来提高性能。这些改进可以提供更好的查询性能和数据处理能力。 缓存: 我们使用缓存技术来加速数据访问，减轻数据库和存储系统的负载。缓存支持内存缓存、CDN缓存等多种方式，根据需要选择最适合的缓存策略。", "headings": [ { "level": 1, "title": "白皮书：可扩展性", "id": "section" } ], "images": [], "text": "白皮书：可扩展性 水平扩展 集群部署: 巴别鸟企业网盘业务服务器采用集群部署模型，这允许我们轻松扩展系统的容量和性能。集群中的多台服务器协同工作，以分担负载并提供高可用性。这种模型允许我们根据需求添加新节点，以满足不断增长的用户和数据需求。私有云部署客户在用户增长时也可以通过增加虚拟机或物理服务器的方式来扩充性能以满足高并发需求。关于巴别鸟集群部署可扩展性的更多信息，可以查看 分布式部署 章节。 对象存储系统: 巴别鸟的存储系统采用对象存储技术，这种技术非常适合大规模的数据存储和水平扩展。对象存储系统具有高度的可伸缩性，可以容纳大量的数据，并在需要时增加存储节点自动扩展存储容量。关于巴别鸟对象存储扩展性的更多信息，可以查看 自建对象存储 章节。 负载均衡: 我们实施了负载均衡策略，确保用户请求被均匀分配到集群中的各个节点，以避免单点故障和提供更快的响应时间。 自动伸缩（公有云）: 得益于阿里云ECS弹性计算服务，我们的系统配置了自动伸缩机制，根据负载情况自动增加或减少服务器节点。这种自动伸缩保证了系统的稳定性和性能。 垂直扩展 硬件升级: 除了水平扩展，针对私有云用户我们还可以进行垂直扩展，即升级服务器硬件以增加单个服务器的性能和容量。这在需要更多计算能力或内存的情况下是一种有效的解决方案。 数据库优化: 我们还可以优化数据库系统，通过调整配置、使用更高性能的硬件或升级数据库管理系统来提高性能。这些改进可以提供更好的查询性能和数据处理能力。 缓存: 我们使用缓存技术来加速数据访问，减轻数据库和存储系统的负载。缓存支持内存缓存、CDN缓存等多种方式，根据需要选择最适合的缓存策略。 容器化和SOA服务架构 Docker容器化 Docker部署: 我们采用Docker容器化技术来部署巴别鸟企业网盘的各个组件和模块。这种方式允许我们将每个主要模块打包为独立的Docker容器，提供了更高的灵活性和可扩展性。 容器编排: 我们使用容器编排工具来管理和协调各个容器，确保它们能够协同工作，实现高可用性和弹性。 容器镜像管理: 巴别鸟企业网盘使用容器镜像仓库来存储和管理Docker镜像，以便随时部署新的容器实例。 SOA服务架构 服务拆分: 我们将巴别鸟企业网盘的主要功能模块拆分为独立的服务，每个服务负责执行特定的任务或功能。这种拆分提高了系统的可维护性和可扩展性。 API通信: 服务之间通过API进行通信，使用兼容RESTful API协议。这种松耦合的通信方式使得服务可以独立开发、测试和部署。 独立部署: 每个服务可以独立部署和扩展，这意味着我们可以根据需求对特定服务进行水平扩展，而不影响其他服务的运行。 容器化和SOA服务架构的优势 高可用性: 容器化和SOA服务架构提供高可用性，允许我们在出现故障时快速恢复服务。 灵活性: 容器化允许我们轻松部署、升级和维护每个容器，而SOA服务架构提供了灵活的模块化开发和部署选项。 资源利用率: 我们可以根据需要分配资源，避免资源浪费，实现更高的资源利用率。 快速交付: 容器化和SOA服务架构使得新功能和改进可以更快地交付给用户。私有云用户也可以享有媲美公有云系统的快速更新及升级服务。 容器化和SOA服务架构的挑战 复杂性: 管理多个容器和服务可能会引入一定的复杂性，需要适当的管理工具和策略。 监控和日志: 我们使用监控和日志工具来确保容器和服务的正常运行，并及时识别和解决问题，并配备自动重启机制，如果服务有问题则自动重启有问题的模块以保证整体服务的畅通。" }, { "lang": "zh", "slug": "reference-whitepaper-09-private-deployment", "title": "白皮书：私有化部署", "description": "《巴别鸟企业网盘白皮书》章节：私有化部署。", "category": "源资料参考", "top_category": "维护", "keywords": [ "白皮书", "私有化部署" ], "url": "zh/reference-whitepaper-09-private-deployment.html", "source": "content/zh/reference-whitepaper-09-private-deployment.md", "summary": "白皮书：私有化部署 巴别鸟公有云网盘系统需要同时为包含免费用户在内的60万用户提供持续不间断服务、要挡住公网上的各种攻击、要不断提高系统效率以降低高昂的公有云服务器成本。多达10年的公有云不间断服务经验使巴别鸟系统久经考验。巴别鸟私有云系统是在巴别鸟公有云系统基础上发展起来的，继承了公有云巴别鸟的所有功能及特性，并与公有云巴别鸟保持同步更新，提供给您其他私有网盘无法比拟的高稳定性及高可用性。 部署方案 针对不同企业不同的IT系统建设需求，巴别鸟私有化系统支持多种灵活的部署方式及部署要求。无论是单服务器、多服务器、集群、超融合系统、分布式系统、第三方云平台甚至Docker方式的部署我们都支持。我们的部署团队可以根据你的需求和你共同制定部署方案。同时因为私有云只服务于单一企业的特性，我们可提供远超公有云系统的可选自定义设置，从界面操作到流程到权限都可以根据你的需求调整。 服务器建议配置及性能需求 服务器类型及作用： 巴别鸟网盘所需硬件系统由业务服务器及存储服务器两部份构成，其中业务服务器可以分为4种类型，这4种类型的服务可以根据需求部署在一台物理机或虚拟机中，也可以分散部署在四台甚至更多的服务器中。所以，部署巴别鸟系统最小单位是两台物理服务器或两台虚拟机（一台业务一台存储） 服务名 用途 操作系统 主业务服务器 web服务、负载均衡、主业务功能实现 Linux 数据库服务器 数据库服务 Linux 搜索服务器 提供文件全文搜索、高级搜索功能 Linux 转码服务器 为需要转码预览的文件进行转码及增加水印 windows 2012、Linux 存储服务器 提供文件存储 Linux 极", "headings": [ { "level": 1, "title": "白皮书：私有化部署", "id": "section" } ], "images": [], "text": "白皮书：私有化部署 巴别鸟公有云网盘系统需要同时为包含免费用户在内的60万用户提供持续不间断服务、要挡住公网上的各种攻击、要不断提高系统效率以降低高昂的公有云服务器成本。多达10年的公有云不间断服务经验使巴别鸟系统久经考验。巴别鸟私有云系统是在巴别鸟公有云系统基础上发展起来的，继承了公有云巴别鸟的所有功能及特性，并与公有云巴别鸟保持同步更新，提供给您其他私有网盘无法比拟的高稳定性及高可用性。 部署方案 针对不同企业不同的IT系统建设需求，巴别鸟私有化系统支持多种灵活的部署方式及部署要求。无论是单服务器、多服务器、集群、超融合系统、分布式系统、第三方云平台甚至Docker方式的部署我们都支持。我们的部署团队可以根据你的需求和你共同制定部署方案。同时因为私有云只服务于单一企业的特性，我们可提供远超公有云系统的可选自定义设置，从界面操作到流程到权限都可以根据你的需求调整。 服务器建议配置及性能需求 服务器类型及作用： 巴别鸟网盘所需硬件系统由业务服务器及存储服务器两部份构成，其中业务服务器可以分为4种类型，这4种类型的服务可以根据需求部署在一台物理机或虚拟机中，也可以分散部署在四台甚至更多的服务器中。所以，部署巴别鸟系统最小单位是两台物理服务器或两台虚拟机（一台业务一台存储） 服务名 用途 操作系统 主业务服务器 web服务、负载均衡、主业务功能实现 Linux 数据库服务器 数据库服务 Linux 搜索服务器 提供文件全文搜索、高级搜索功能 Linux 转码服务器 为需要转码预览的文件进行转码及增加水印 windows 2012、Linux 存储服务器 提供文件存储 Linux 极端情况下，如果使用服务器挂载的硬盘作为存储空间，巴别鸟也支持把全部服务及存储都部署在一台物理机或虚拟机中（一体机模式），但考虑到性能及灾备或是日后的升级扩容问题，不推荐这样的部署方式。 我们推荐的最佳部署方式是4台服务器（虚拟机）的小集群部署。主业务服务及数据库服务放在在一台服务器，搜索服务器和转码服务器独立，然后外加一台存储服务器。 如果存储的空间需求小于10TB，也可以不需要存储服务器。可以直接挂载硬盘或NFS磁盘进行存储。 巴别鸟也支持接入第三方存储，理论上，只要第三方存储系统支持NFS或S3协议都可以接入到巴别鸟作为存储服务。绝大多数存储系统都支持这两种协议。 各个服务器之间要保证互访的畅通。如内网有较高安全要求可以参阅 9.1.2需要开放的端口 最低性能配置： 巴别鸟的最低性能配置可以支持100左右用户正常使用，管理10TB以下的数据。 cpu 内存 系统盘 存储盘 网络 操作系统 8核CPU （参考基准E5 2609） 32G ECC 内存 500G 10TB以下 千兆 Linux 推荐性能配置实例： 巴别鸟的推荐性能配置可以支持1000 2000用户正常使用，管理最高可达1PB的文档。 巴别鸟支持多种部署方式，该实例是标准部署方式。使用虚拟机部署业务服务器对接独立的单台或多台对象存储服务器。业务服务器和存储服务器分开管理。 业务服务器： 建议业务服务器使用虚拟机进行部署 编号 服务器类型 配置要求 操作系统 服务器用途 1 虚拟机 8核CPU 64G内存 500G SSD系统盘 CentOS8或openeuler22 主业务服务器/数据库 2 虚拟机 8核CPU 32G内存 500G SSD系统盘 CentOS8或openeuler22 搜索服务器 3 虚拟机 8核CPU 16G内存 200G SSD系统盘 windows 2012 R2 转码服务器 8核cpu的性能应该接近志强4410 巴别鸟企业网盘采用Docker部署，理论上只要是Linux操作系统即可进行部署，推荐使用CentOS或open Euler。 如果没有现成的虚拟机资源，需要采购新的业务服务器，业务服务器硬件配置需求如下： 编号 服务器类型 配置要求 操作系统 服务器用途 1 业务服务器 至强银牌4210 2 20核CPU 64G内存 2TB SSD硬盘 Linux 主业务服务器 业务服务器最好购买VM，使用虚拟化进行管理。 存储服务器（对象存储）： 巴别鸟支持在通用服务器上搭建对象存储系统，如预计存储空间用量小于100TB，推荐使用单台服务器搭建对象存储系统。单台对象存储可以用磁盘进行数据校验冗余，并且可以以每次增加一台存储服务器的方式进行横向扩容。（扩容操作可以做到不停服） 对象存储服务器建议使用独立的物理机，建议配置如下： 服务器类型 配置要求 操作系统 服务器用途 备注 存储服务器 至强银牌4210 2 20核CPU 64G内存 480G SSD硬盘 +存储所需容量硬盘 硬盘如果考虑性价比，建议使用 8T 10（2U） 或 8T 24（4U）。如果考虑存储密度及未来扩容投入可使用12T硬盘。 Linux 对象存储服务器 未来扩展建议增加相同磁盘容量的服务器。 如所需存储空间大于300TB，需要多台服务器搭建分布式对象那个存储系统。 巴别鸟也支持为客户搭建分布式对象存储系统。要了解分布式对象存储可查阅“自建对象存储”章节。 需要开放的端口 为了服务器系统的安全，我们需要只开放特定的端口，下面是需要开放的端口： 对外开放的端口（外网访问需要使用的端口）： 端口号 端口用途 协议 开放的主机 80 网盘主业务 web外部访问端口，不加密 http 主业务服务器 443 网盘主业务 web外部访问端口，加密 https 主业务服务器 3060 网盘主业务node 外部访问端口，不加密 TCP 主业务服务器 3080 网盘主业务node 外部访问端口，加密 TCP 主业务服务器 服务器间需要开放的端口（服务器内部通讯需要开放的端口）： 一般实际部署时，只会限制外网端口（对外），服务器间内部端口不会限制。但一些跨网络跨机房部署的用户也会需要限定内部端口。 主机 端口号 端口用途 协议 目标网段 业务服务器 6379 redis访问端口，供windows转码与搜索服务器使用 TCP 转码服务器与搜索服务器 业务服务器 8080 供windows转码服务器，访问网盘业务服务器使用 TCP 转码服务器与搜索服务器 业务服务器 3306 数据库端口，供搜索服务器访问数据库使用 TCP 转码服务器与搜索服务器 业务服务器 9000 docker 集群部署，内部可视化界面端口 TCP 转码服务器与搜索服务器 业务服务器 111 portmap 端口 TCP+UDP 转码服务器与搜索服务器 业务服务器 2049 TCP+UDP TCP+UDP 转码服务器与搜索服务器 业务服务器 35000 mountd 端口 TCP+UDP 转码服务器与搜索服务器 业务服务器 2376 docker REST API端口，进行TLS加密 TCP 本机 业务服务器 2377 TCP端口 用来 docker 集群管理相关通信 TCP+UDP 本机 业务服务器 7946 TCP与UDP端口，用来docker swarm 各节点间的通信 TCP+UDP 本机 业务服务器 4789 docker overlay 网络默认端口 TCP+UDP 本机 搜索服务器 9200 elastic 端口，供主业务服务器调用使用 TCP 业务服务器 搜索服务器 5601 kibana端口，内部可视化elastic界面访问端口 TCP 业务服务器 搜索服务器 9998 tika端口，提取文档文本服务器端口 TCP 业务服务器 搜索服务器 9000 docker 集群部署，内部可视化界面端口 TCP 转码服务器与搜索服务器 搜索服务器 2376 docker REST API端口，进行TLS加密 TCP 本机 搜索服务器 2377 TCP端口 用来 docker 集群管理相关通信 TCP 本机 搜索服务器 7946 TCP与UDP端口，用来docker swarm 各节点间的通信 TCP+UDP 本机 搜索服务器 4789 docker overlay 网络默认端口 TCP+UDP 本机 转码服务器 转码服务器 可以访问业务服务器 可以访问业务服务器 可以访问业务服务器 部署时需要开放的端口： 端口号 端口用途 开放的服务器 目标IP地址 22 ssh端口号，ssh 访问使用 所有服务器 部署用跳板机 443 获取授权 所有服务器 47.96.234.200 443 获取安装源 所有服务器 120.27.245.68 443 Docker安装源 所有服务器 13.35.121.100 POC部署 POC部署适用于用户在选型前在生产环境进行POC测试而进行的部署方式。 POC部署需求： 基础POC部署，可测试软件功能，并发量，API接口，安全性，并进行生产环境试用。建议使用标准部署作为POC测试。 如需要进行对象存储、不同密区数据摆渡、高可用的POC，择需要增加相应的服务器和网段。 环境准备 推荐使用虚拟机进行部署： 巴别鸟私有化企业网盘采用Docker部署，理论上只要是Linux操作系统即可进行部署。推荐使用CentOS或open Euler。按要求准备好虚拟机后，联系我们预约时间后即可开始POC部署。 编号 服务器类型 配置要求 操作系统 服务器用途 备注 1 虚拟机 8核CPU 32G内存 500G系统盘 +500G存储盘 CentOS8或openeuler22及以上 主业务服务器 2 虚拟机 8核CPU 16G内存 500G系统盘 CentOS8或openeuler22及以上 搜索服务器 3 虚拟机 8核CPU 8G内存 200G系统盘 windows 2012 R2 转码服务器 CAD、office转码 win服务器是为了更好的office文件预览效果。巴别鸟也支持纯Linux环境部署 POC部署其他要求如下： 编号 项目 要求 备注 1 远程接入 可以远程接入服务器进行部署 可使用堡垒机或者跳板机或向日葵、VPN，能远程接入服务器部署即可。 2 外网连接 服务器需要能连接外网，拉取安装包，获取授权 需要连接的外网地址： software.babel.cc docker.babel.cc POC部署的使用授权时长为30天，授权账户数为100个。 初始化 部署完成后，巴别鸟团队会帮助用户进行系统初始化，根据用户需求初始化系统。包括不限于： 初始化管理员账号。（需要准备一个邮箱地址作为超级管理员账号） 初始化通知发件邮箱。（需要用户准备一个可提供密码和smtp服务器地址的邮箱作为系统默认发件箱） 初始化部门结构。（对接AD或导入部门） 初始化基础配置。logo、企业名、各类配置项。 培训 巴别鸟是一个专业的企业级应用，需要一定的培训工作帮助客户落地。POC后建议联系我方销售人员进行使用培训。 培训分为3类： 管理员培训（培训管理员的配置，使用，需求功能实现。耗时 1 2小时） 部门经理培训。（培训部门经理权限分配、成员增减等日常管理方式。耗时 1小时） 使用者培训。（使用成员的培训。耗时 1小时） 开启POC试用 培训完成后即可开始正式POC试用，使用中遇到的问题可以在相关群直接询问，巴别鸟团队会在2个小时内响应并解答。POC系统有效期为30天，如果需要延期，可联系我们销售人员。 巴别鸟常用部署方式介绍 巴别鸟可以按需支持多种部署方式，这里介绍下巴别鸟常用的部署方式。 在阿里云、腾讯云、华为云等公有平台部署： 巴别鸟支持在公有云服务商如：阿里云、腾讯云、百度云、华为云、天翼云的虚拟机（ECS）及对象存储（OSS、OBS...）上进行部署，在互联网上为用户提供服务。 和纯私有化部署的差别对比如下表： 优缺点/ 部署方式 图片服务 视频服务 公网访问 稳定性 硬件费用 采用阿里云存储和阿里云服务器 可以使用阿里云提供的图片服务 可以采用阿里云的视频转码服务，但是需要额外付费(价格贵) 可以在公网上访问，用户访问的快慢取决于用户自己的带宽和购买的阿里云的带宽。 系统很稳定，部署简单，便于管理。 需要支付阿里云的存储和服务器费用，可按月或按年付费等。服务器的维护即可由用户自己负责，也可以委托我们进行维护并负责升级。 存储和服务器均搭建在自己的内网 使用自建的图片处理服务(需要客户提供高性能的服务器) 使用自建的转码服务(需要客户提供高性能的服务器)，如果用户没有这方面的需求，可以忽略。 如果没有外网的出口，则用户不能在外网访问。但是在内网访问很快。 稳定，针对存储系统等的模块做了定制开发。数据的安全性由用户自己负责。 需要提供独立的主机和存储系统。服务器即可由用户选配购买，也可以由我们选配购买。服务器维护由用户负责，我们可以提供相应的软件升级服务。 公有云部署（1000+用户）要求： 编号 服务器类型 配置要求 操作系统 服务器用途 1 ECS 16核CPU 32G内存 500G SSD系统盘 CentOS8或openeuler22 主业务服务器 2 ECS 8核CPU 16G内存 500G SSD系统盘 CentOS8或openeuler22 数据库服务器 3 ECS 8核CPU 16G内存 500G SSD系统盘 CentOS8或openeuler22 搜索服务器 4 存储 对象存储系统。如阿里云OSS、华为云OBS 对象存储系统。如阿里云OSS、华为云OBS 对象存储系统。如阿里云OSS、华为云OBS 在公有云平台部署的主要优势是不需要专人维护、无需购买硬件就能做到顶级的灾备、在互联网上访问速度快、同时服务器和数据在自己手上管理。 在公有云平台部署的缺点主要为：数据没有本地化、每年需要支付服务器租用费用及相应的带宽存储成本。 自购服务器（2台物理机）进行部署： 如果想在自己机房部署纯私有的巴别鸟，并且没有富余的虚拟机资源，需要采购硬件部署，要求如下： 物理机服务器品牌建议：建议使用2台 DELL T440 服务器来完成系统搭建。并购买DELL3年金牌服务。 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：建议使用2台 DELL T440 服务器来完成系统搭建。并购买DELL3年金牌服务。 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：建议使用2台 DELL T440 服务器来完成系统搭建。并购买DELL3年金牌服务。 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：建议使用2台 DELL T440 服务器来完成系统搭建。并购买DELL3年金牌服务。 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：建议使用2台 DELL T440 服务器来完成系统搭建。并购买DELL3年金牌服务。 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：建议使用2台 DELL T440 服务器来完成系统搭建。并购买DELL3年金牌服务。 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 两台服务器方案 业务+存储 两台服务器方案 业务+存储 两台服务器方案 业务+存储 两台服务器方案 业务+存储 两台服务器方案 业务+存储 两台服务器方案 业务+存储 编号 服务器类型 配置要求 操作系统 服务器用途 备注 1 服务器 志强银牌4410 2 16核CPU、 64G内存、 2TB SSD硬盘 open Euler、Ubuntu、CentOS 主业务服务器 建议安装VM 2 存储 4410 2 16核CPU 、64G内存、 500G SSD硬盘+所需的硬盘空间（不需要raid或raid0） open Euler、Ubuntu、CentOS 存储服务器 硬盘容量按对存储空间需求进行配置 以上配置可支持1000+用户，150TB左右的存储空间 巴别鸟存储服务器使用对象存储系统，支持分布式部署（多台存储服务器）最低要求为一台物理服务器。支持使用硬盘组进行校验，支持2+1、3+1、4+1...等多种校验类型。详见 自建对象存储 章节 如需扩容存储空间，增加单台存储服务器即可。 也可增加一台存储服务器作为备份服务器，实时同步备份，主存储服务器出问题切换到备份服务器即可正常使用。 单服务器（1台物理机）部署： 一些没有机房但需要私有化部署巴别鸟，并且存储空间需求不大（10TB以下）的客户，可以选用单台服务器部署巴别鸟。只需购买一台符合要求的塔式服务器放置在公司也能满足使用巴别鸟的需求。 物理机服务器品牌建议：如果没有机房，建议使用塔式服务器进行部署。服务器存储硬盘建议raid1或者raid5+1 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：如果没有机房，建议使用塔式服务器进行部署。服务器存储硬盘建议raid1或者raid5+1 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：如果没有机房，建议使用塔式服务器进行部署。服务器存储硬盘建议raid1或者raid5+1 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：如果没有机房，建议使用塔式服务器进行部署。服务器存储硬盘建议raid1或者raid5+1 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：如果没有机房，建议使用塔式服务器进行部署。服务器存储硬盘建议raid1或者raid5+1 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 物理机服务器品牌建议：如果没有机房，建议使用塔式服务器进行部署。服务器存储硬盘建议raid1或者raid5+1 服务器的系统盘可选使用 raid 来增强冗余。如使用raid1方案，所需硬盘数量需要增加2倍。（2TB SSD变成 2TB SSD 2） 一台服务器（一体机方案） 一台服务器（一体机方案） 一台服务器（一体机方案） 一台服务器（一体机方案） 一台服务器（一体机方案） 一台服务器（一体机方案） 编号 服务器类型 配置要求 操作系统 服务器用途 备注 1 服务器 志强银牌4410 2 16核CPU 64G内存 2TB SSD硬盘 +需要存储容量的硬盘 2（未来也可增加硬盘） openEuler、Ubuntu、CentOS 8.5 及以上 一体机 建议安装VM，2个CPU授权。 单服务器部署整套巴别鸟系统不支持对象存储，采用只读硬盘或NFS的方式进行存储。建议使用raid1来提升系统可靠性。 可增加一台备份服务器用来进行数据同步备份。如主服务器出问题可以用备份服务器进行数据重建。 在现有虚拟机（超融合）系统上进行部署： 这是目前最常用的部署方式，在企业现有的服务器和硬件条件下进行部署，无需采购新的设备。 在客户现有的VM或超融合平台分配的虚拟机中完成部署，适合已经有一定IT建设及管理的用户。 采用小集群的方式部署，由虚拟机平台负责服务器的统一管理。 支持绝大多数虚拟化系统。 推荐采用4台虚拟机挂载存储空间的方式进行部署。 编号 服务器类型 配置要求 操作系统 服务器用途 1 虚拟机 8核CPU 32G内存 500G SSD系统盘 CentOS8或openeuler22 主业务服务器 2 虚拟机 8核CPU 16G内存 500G SSD系统盘 CentOS8或openeuler22 数据库服务器 3 虚拟机 8核CPU 16G内存 500G SSD系统盘 CentOS8或openeuler22 搜索服务器 4 虚拟机 8核CPU 16G内存 200G SSD系统盘 windows 2012 R2 转码服务器 5 存储 支持NFS或S3接口的存储系统或虚拟机挂载磁盘作为存储盘 支持NFS或S3接口的存储系统或虚拟机挂载磁盘作为存储盘 支持NFS或S3接口的存储系统或虚拟机挂载磁盘作为存储盘 如有系统冗余需求，可以准备6台虚拟机，就能很好的完成数据库备份及系统冗余。 编号 服务器类型 配置要求 操作系统 服务器用途 1 虚拟机 8核CPU 32G内存 500G SSD系统盘 CentOS8或openeuler22 主业务服务器 2 虚拟机 8核CPU 32G内存 500G SSD系统盘 CentOS8或openeuler22 从业务服务器 3 虚拟机 8核CPU 16G内存 500G SSD系统盘 CentOS8或openeuler22 主数据库服务器 4 虚拟机 8核CPU 16G内存 500G SSD系统盘 CentOS8或openeuler22 从数据库服务器 5 虚拟机 8核CPU 16G内存 500G SSD系统盘 CentOS8或openeuler22 数据库服务器 6 虚拟机 8核CPU 16G内存 200G SSD系统盘 windows 2012 R2 转码服务器 7 存储 分布式对象存储 分布式对象存储 分布式对象存储 支持虚拟机挂载磁盘的形式把挂载盘作为存储空间。 也可以对接san存储或者对象存储系统等第三方存储系统。 巴别鸟也为客户提供自建对象存储服务。 自建对象存储服务器配合虚拟机部署： 巴别鸟支持为客户在通用服务器上搭建对象存储，因为对象存储软件定义存储的优势（高可用、横向扩展容易），推荐没有对象存储的用户可以新购一台服务器部署巴别鸟对象存储系统配合在虚拟机（超融合）运行的巴别鸟业务系统一起使用。 业务服务器需求同上一节“在现有虚拟机（超融合）系统上进行部署”的要求。 关于巴别鸟对象存储的详细介绍可查看“自建对象存储服务器”章节。 我们大多数客户最终都选择对象存储服务器作为存储。 最低支持单服务器搭建对象存储系统（150TB以下空间需求）。 服务器类型 配置要求 操作系统 服务器用途 备注 存储服务器 至强银牌4210 2 20核CPU 64G内存 480G SSD硬盘 +存储所需容量硬盘 硬盘如果考虑性价比，建议使用 8T 10（2U） 或 8T 24（4U）。如果考虑存储密度及未来扩容投入可使用12T硬盘。 Linux 对象存储服务器 未来扩展建议增加相同磁盘容量的服务器。 单服务器对象存储网络拓扑图： 我们也支持搭建多台服务器组成的分布式对象存储系统。 分布式存储系统最小需求为2+1，就是需要准备三台存储服务器，性能要求和单台对象存储的要求一致。 物理分布式存储目前推荐最小单位是3台存储服务器。2+1纠错码意味着每扩充2台存储节点就需要增加1台服务器作为纠错服务器。以此，4+1意味着增加4台存储服务器就需要增加一台纠错服务器。所以4+1的磁盘利用率高于2+1。使用4+1方案首次建设就需要5台存储服务器。每次扩容增加的最小单位和首次建设需要的最小服务器单位一致。 多服务器分布对象存储网络拓扑图： 可以新增一台或一套存储服务器用来实时备份。主存储服务器出问题快速切换到备份服务器即可正常使用。 分布式高可用高冗余部署： 金融机构、医院、能源、超大型企业因为有业务不中断的硬性指标，需要系统能做到高可用、高冗余，不会因为服务器的单点故障而中断服务，并且能做到热切换及热修复，极端情况下，连交换机等网络设备都需要实现主备分离，这就需要使用分布式高可用高冗余部署。 巴别鸟支持多种高可用高冗余方案，可以部署在传统的分布式系统中实现高可用高冗余。 我们也可以为客户搭建适合巴别鸟的分布式系统。（硬件需要客户按要求自行采购） 巴别鸟分布式部署能确保任何一个单点故障都不会影响系统的正常使用。 推荐的分布式容易部署方案，业务服务器采用主备双活，存储系统采用分布式存储。 有密区及非密区管控需求的，详见 “数据摆渡章节” 巴别鸟高可用系统网络拓扑 异地灾备部署 对于对数据保全有着较高要求的用户，巴别鸟也支持异地灾备方案。就是把重要的数据库及文件存储内容备份到异地的备份系统中。如果本地机房出现问题，只要备份数据在，可以在任何地方重建系统并恢复正常使用。 巴别鸟可以为客户搭建异地灾备服务器，但不支持冷热数据分离等高级备份方式，如果数据量极大（1PB以上）考虑到性价比，建议使用专业的备份系统（如：NBU、云祺）。 巴别鸟有支持NBU标准的备份API可以调用。 异地灾备部署对网络环境要求较高，不同位置的机房间最好有专线或稳定的VPN连接。 使用备份系统只能在出问题后通过备份还原及重建数据，不支持直接切换到备份数据。一般情况下数据重建周期会比较久。 使用备份系统进行异地灾备示意图： 如果不需要冷热数据分类保存，巴别鸟也可以采用对象存储自带的异地灾备功能为客户完成异地灾备部署。 使用对象存储进行异地灾备，当主系统出问题可以快速切换到灾备服务器中。 自建对象存储服务器 巴别鸟对象存储是在开源MinIO系统上发展起来的对象存储系统。它继承了MinIO高性能、可扩展、数据安全的优势，同时更适配巴别鸟企业网盘的应用场景。 巴别鸟对象存储系统作为先进的对象存储系统，在速度、安全性、稳定性、高可用、横向扩展方面都有着传统存储系统无可比拟的优势。 巴别鸟对象存储系统优势 性能 MinIO号称是世界上速度最快的对象存储服务器，没有之一。在 32 个 NVMe 驱动器节点和 100Gbe 网络上发布的 GET/PUT 结果超过 325 GiB/秒和 165 GiB/秒，和亚马逊S3相比有明显优势，远远超越传统HDFS。 高可用性：MinIO通过数据的多副本、故障转移和自动恢复，保证高度可靠性和可用性，从而确保数据不丢失和业务不中断。 低冗余且磁盘损坏高容忍：标准且最高的数据冗余系数为2(即存储一个1 M的数据对象，实际占用磁盘空间为2M)。但在任意n/2块disk损坏的情况下依然可以读出数据(n为一个纠删码集合(Erasure Coding Set)中的disk数量)。并且这种损坏恢复是基于单个对象的,而不是基于整个存储卷的。 安全性： MinIO 通过最高级别的加密以及广泛的优化提供更多功能，几乎消除了通常与存储加密操作相关的开销。 数据分块存储与各个硬盘，获取硬盘或服务器读写权限也无法还原数据。 极高的可扩展性：MinIO支持分布式部署，并且可以水平扩展。在需要更多的存储空间或更高的性能时，可以通过添加新的节点轻松地扩展MinIO。 最低支持单机部署对象存储系统，而不是传统的需要三台独立服务器。 对象存储系统及纠删码 关于纠删码 巴别鸟对象存储系统(MinIO)使用纠删码erasure code 和校验和checksum来保护数据免受硬件故障和无声数据损坏。最高冗余状态下即便丢失一半数量(N/2)的硬盘,您仍然可以恢复数据。 纠删码是一种恢复丢失和损坏数据的数学算法，MinIO采用Reed Solomon code将对象拆分成N/2数据和N/2奇偶校验块。这就意味着如果是12块盘，一个对象会被分成6个数据块、6个奇偶校验块，可以丢失任意6块盘(不管其是存放的数据块还是奇偶校验块) , 仍可以从剩下的盘中的数据进行恢复，我们称数据存储为D、纠删码（奇偶校验）为P。 默认情况下会以N/2个数据和N/2奇偶校验块的方式来进行驱动器分片（支持自定义以支持更高的空间利用率） 纠删码不同于传统的多副本技术，它的磁盘利用率更高，数据恢复效率更高。（但是不少存储厂商把纠删码宣传为多副本，把P数说成是副本数，这是不准确的，会引起很多误解） 巴别鸟语境下的多副本是指增加备份服务器全量同步存储的数据。 纠删码特点及与raid技术区别 纠删码可以保护数据免受多个驱动器故障的影响 RAID6允许两个驱动器故障而MinIO纠删码允许丢失一半的驱动器 RAID属于卷级别的纠删码而MinIO纠删码是基于对象实现的纠删码（不用停机） 有效空间计算（空间利用率） 假设需要100TB的存储空间，需要购买多少个多大的硬盘取决于选择的冗余标准。譬如：采用3+1的冗余方式，100TB可用空间就需要购买12块12TB的硬盘，4块硬盘一组组成3组，9个数据盘3个校验盘，可用空间就是9 12一共108TB可用。如果采用2+1的冗余方式，就需要15块10TB的硬盘，10个数据盘，5个校验盘。 3+1方案中12块硬盘只能坏任意3块不影响系统使用及数据还原，但如果使用2+1方案，虽然需要购买更多硬盘，但15块硬盘里能坏任意5块也不影响系统使用。 更换坏掉的硬盘后系统能自动修复数据。 空间利用率可以参考下表。如果空间需求量大（超过150TB）并且在持续增长，考虑到存储密度和性价比，建议一台服务器一次性配16块硬盘。 不同数量的磁盘及空间利用率可以点击下方链接进行计算 https://min.io/product/erasure code calculator?ref=docs 硬件准备 所需硬件配置。 巴别鸟支持单台服务器搭建对象存储系统（单节点），以硬盘组作为冗余对象。最高可以损坏一半的硬盘也不影响系统的正常使用。 巴别鸟对象存储系统需要客户按要求事先准备好硬件服务器以供部署，最低配置需要2块志强CPU、64GB内存及400G固态硬盘（系统盘）然后增加相应存储容量所需的机械硬盘。 如要计算所需存储空间和购买的硬盘数，可点击下方链接进行计算。 https://min.io/product/erasure code calculator?ref=docs 建议硬件配置如下： 服务器类型 配置要求 操作系统 服务器用途 备注 存储服务器 至强银牌4210 2 20核CPU 64G内存 480G SSD硬盘 +存储所需容量硬盘 硬盘如果考虑性价比，建议使用 8T 12（2U） 或 8T 24（4U）。如果考虑存储密度及未来扩容投入可使用12T硬盘。 Linux 对象存储服务器 未来扩展建议增加相同磁盘容量的服务器。 巴别鸟对象存储使用软件定义存储技术，所以硬盘无需raid，考虑到一些服务器需要raid才能支持多磁盘，这种情况下每块硬盘都做成raid0直通模式即可。 单服务器模式每次扩容需要增加一台配置一致的服务器。扩容时可以不间断服务。 单服务器部署也支持增加一台配置一致的服务器搭建主备模式实时同步，如果一台服务器硬件损坏，可以快速切换到备用服务器。 磁盘有效空间容量和选择的冗余方式有关。譬如：使用8块10T硬盘来组建对象存储系统，采用3+1的冗余方案，相当于4块硬盘一个分组，分为2组，有效可用空间为60TB，同时8块硬盘损坏任意两块也不影响数据及系统使用，替换坏的硬盘即可自动重建。如果采用7+1的冗余方案，有效可用空间就为70TB，8块硬盘里任意损坏1块不影响数据及系统使用。 多服务器部署（分布式）。 巴别鸟对象存储系统支持多服务器部署，如使用服务器为冗余单位，最少要求3台服务器，即2+1模式，但考虑到空间利用率，推荐采用3+1方案（即4台服务器） 每个节点（服务器）的配置要求和上文单服务器部署一致。 建议节点配置一致（相同的操作系统、相同数量的磁盘和相同的网络连接） 每个节点提供的驱动器数量必须相同 节点间的时间差异不能大于15分钟（建议使用NTP确保时间的一致性） 空间利用率计算同单服务器。 私有化要求及服务流程 为了确保使用巴别鸟系统的体验和质量，巴别鸟所有的私有化部署工作都是由巴别鸟团队远程或现场进行部署及签发证书，暂不支持代理团队部署或客户自行部署。同时系统的维护工作也由巴别鸟运维团队进行定期远程维护。客户只需按要求准备好硬件及接入资源，其他事情就交给巴别鸟团队来完成。 私有化部署前期需要准备的： 计算大体使用人数、并发量、存储空间及空间增长率交由巴别鸟客户经理评估所需配置。 客户评估现有服务器剩余资源（如有），根据实际情况选择部署方式。 巴别鸟出具私有化部署方案。 客户根据方案准备相应的服务器及接入资源，分配服务器、安装操作系统。 保证服务器能够在外网远程桌面（也可以使用向日葵）和ssh访问，开启相应端口（我们的部署技术人员会提出具体端口要求） 用户最好能提供一个域名，没有域名的话需要一个固定的ip地址，用ip地址访问的方案需要保证在使用时期ip地址不会发生变动 如需接入邮箱找回密码或手机号发送验证码，需要准备相应的邮箱接入或短信网关。 编号 项目 要求 备注 1 域名 需要一个独立的主域名或二级域名 可以在公司原有域名的基础上设定一个二级域名。如yun.company.com 2 邮箱 需要一个可发送通知邮件的邮箱 支持smtp的邮箱地址即可 邮件推送相关 MailUser=xxxx@mail.com MailPassword=password MailHost=邮件服务器地址 MailPort=端口号 3 远程访问 可远程访问服务器进行配置 支持远程访问及控制服务器 4 SSl证书 https需要申请SSL证书 像数字证书颁发机构CA申请。推荐申请 OV 通配符 5 短信接口 如需要手机邀请，手机注册。则需开通短信接口服务（可选） 阿里云、腾讯云等云服务商也提供短信服务接口，申请即可开通 实施阶段 准备工作完成后通知我们，我们会给用户一个具体的实施时间安排，实施时间段内请保持外网访问的畅通 实施一般需要2 3个工作日，第一天远程部署安装巴别鸟，第二天测试和验收，第三天修正遇到的问题 实施完成后我们会通知用户，然后开始初始化阶段 初始化服务 巴别鸟为所有私有云客户提供了初始化服务，服务内容包括： 维护人员培训（远程或是现场） 帮助用户进行数据迁移、用户导入、权限分配等工作（远程或是现场） 使用人员培训 （远程或是现场） 接入第三方服务 作为一个围绕企业文件的办公平台，私有化的巴别鸟企业网盘通过接入第三方API的方式，可以轻松集成各种第三方服务到巴别鸟中，以满足不同的需求这些服务包括但不限于：电子签名、高级CAD预览、office、文字识别、图像识别....等第三方服务来解决您遇到的需求问题。 接入第三方服务的条件 理论上支持BS架构的第三方应用或者服务模块都可以接入。 第三方服务必须提供开放的API，以便巴别鸟企业网盘可以与之集成 如果是互联网服务，需要服务器能访问外网。 需要企业自行或委托我们购买接入的第三方服务的授权 推荐的可接入服务 文件防泄密系统： ipguard 在线office编辑：onlyoffice（自带）、office365、WPS Online、永中office 高级CAD预览：浩辰云图、梦想CAD CAD在线编辑：梦想CAD 在线签章：上上签 文字识别图像识别：百度千帆（智能云） AI相关：智巢AI（自有）、ChatGPT、智谱AI 开放API（统一存储平台） 巴别鸟私有化版本提供了开放API，使用巴别鸟API，您可以在您的系统中使用巴别鸟的几乎所有能力。并在云中构建自定义应用程序和集成，而无需构建和维护自己的内容管理服务。 统一存储平台 非结构化数据统一管理: 巴别鸟企业网盘的开放API的核心价值在于它可以作为一个统一的存储平台，用于整合和管理企业各个平台的非结构化数据。这包括但不限于OA（办公自动化）、CRM（客户关系管理）、ERP（企业资源规划）等应用，这样企业的所有非结构化数据都能在一个平台统一管理，提高安全性并节约存储资源。 企业级对象存储: 巴别鸟企业网盘还可以开放自带的对象存储接口，作为企业的统一存储管理平台。这意味着企业可以将不同来源的数据，包括文档、媒体、报表等，存储在巴别鸟企业网盘，并通过API访问和管理这些数据。 文档和支持 详细文档: 巴别鸟企业网盘提供详细的API文档，包括示例代码和用例，以帮助开发人员快速集成API。 附件2: 巴别鸟API文档 https://www.babel.cc/p/api integration.do 开发支持: 我们提供开发支持服务，技术人员会参与联调，一对一解决在API集成过程中可能遇到的问题和挑战。 单点登录SSO 巴别鸟私有化系统支持对接SSO单点登录平台或企业微信、钉钉、飞书、OA、ADFS、ERP等第三方平台以是实现单点登录。 更多关于单点登录的内容可以参见上文安全性章节的 ：单点登录（Single Sign On，SSO）集成 数据摆渡 巴别鸟可以使用“部门安全策略”的方式隔离某个部门数据，实现涉密部门的安全性和外发审批等功能，但是面对网络隔离的密区和非密区之间的文件传输，就需要用到数据摆渡的方式，确保密区和非密区之间可以安全可控的交换文件，这里就需要部署巴别鸟数据摆渡功能。在巴别鸟中，该功能模块命名为“传送文件“便于普通用户理解。 实现方式 在密区（研发区）和非密区（办公区）各部署一套巴别鸟，在两套巴别鸟之间传送文件: 需要安装巴别鸟数据摆渡模块 两套服务器间需要配置传输端口 传输使用SSL加密 支持多套巴别鸟之间互传文件 超级管理员可设定特定的文件接收者及审核人 可设定从非密区向密区传送文件无需审批 所有的传输都有记录及日志 多套巴别鸟在多个网络进行文件传送: 单套巴别鸟简化的文件传送方式 ： 有些客户的核心需求是非密区往密区便捷快速传输文件，仅想在密区部署一套巴别鸟，并没有在非密区使用网盘的需求，这时候就可以使用简化的数据摆渡方式。 出于安全考虑，该方式仅支持非密区向密区传送文件，并不支持密区向非密区传送文件。 除了在密区部署完整的巴别鸟系统，也需要在非密区部署一个文件传输服务。 非密区向密区传输文件无需审批。 使用步骤 部署完成数据摆渡模块的巴别鸟会在企业控制台增加一个“传送文件配置”模块，如果在企业控制台能看到该模块入口，说明已部署成功数据摆渡模块。 在企业控制台“传送文件配置”中新建接受端口和发送端口。已确定数据摆渡的接受端和发送端。 如果其中一套巴别鸟只配置了接口端口没有配置发送端口，那么就只能接收文件但不能发送文件。如：密区只能接收文件但不能发送文件。 新建了接收端会自动生成一个token，发送端要填入该token以实现加密传输。 一个巴别鸟可以建立多个接收端，每个接收端可以选择不同的成员。如：研发部和技术部的接收端分开。 通过审核后，接收人员能在自己的巴别鸟账号“传送文件”栏目找到摆渡过来的文件。 使用者在巴别鸟企业网盘中直接右键“传送文件”选择传送的接收端进行文件传送（发件）。并在“传送文件”栏目下查看发送过来并通过审核的文件。 为保证安全，传送文件以文件为单位（在多层文件夹中夹带重要文件，骗过审核），并不支持选择文件夹传送，但支持多选文件进行传送。 具有审批权限的管理员或部门经理可以在“传送文件”栏目下对接收和发送的文件进行审核，审核通过后文件才能传输。 定制化开发 巴别鸟私有化版本可以为客户提供专业的定制化开发（二次开发）服务。在巴别鸟现有产品的基础上针对客户具体需求推出更适合客户的产品。 巴别鸟定制开发优势 从产品思维出发帮助您设计产品 不同行业有不同的工作流程及使用习惯，同时需求和最终的产品间往往也隔着很深的鸿沟。只有需求没有好的产品设计往往会使项目迟迟无法落地。为了更好的适用于您的使用场景，我们职业产品经理带队的Babel care团队会为您的企业定制属于你的解决方案及二次开发支持。 精细化估时管理 我们拥有曾服务于北大方正的精细化估时管理体系，能精确的进行开发估时管理，提高项目成功率及落地效率。项目估时清晰有据可查，有效降低企业成本并提高效率。 透明的项目跟进及验收 在项目的每一个阶段，我们都有专职项目经理和产品经理跟进。确保项目进度及验收标准。并且我们可以开放我们的Jira（项目管理工具）给客户，让客户随时了解到项目的进度及耗时。 保持更新和维护 定制开发最普遍的问题是未来的更新和维护问题。传统的定制开发因为和标准产品有较大区别，所以往往会使用新的分支，开发团队也没有精力去维护新的分支，这就造成了定制开发产品会失去持续的维护及功能更新，越来越不好用或者孤立，最终被弃用。巴别鸟注意到并解决了这个问题，我们会在标准产品的基础上使用模块化的方式开发新的定制需求，或者把定制需求结合进标准产品以配置项的方式进行管理。这样，就是定制开发产品也能享受标准产品的更新及维护服务，做到可持续发展。 支持白牌服务（OEM） 出于商业目的或品牌建设需求，一些企业需要使用自己的产品名称及logo，巴别鸟可提供符合企业要求的白牌（OEM）版本。 透明、专业、负责 负责，是客户给我们最多的和最高的评价。在项目维护期内，我们会站在企业角度考虑，及时对应修正bug并完成功能调整。为企业提供长期可持续的维护服务。 巴别鸟定制开发范围 基于API的系统对接：如与OA、CRM、PDM等系统的对接整合。 API的定制开发：针对巴别鸟企业网盘某项功能开放API。 使用巴别鸟API接口的独立功能模块或子系统的定制开发。 围绕巴别鸟企业网盘现有功能的功能扩充，流程定制，数据交换。 基于巴别鸟源码的界面重塑及功能定制化开发。 巴别鸟定制开发流程 和客户确定需求及技术实现方案。出具：《需求分析说明书》 产品经理和客户深度讨论，设计原型和交互。出具《二次开发方案》、《产品原型》、《详细模块及估时表》 商务及合同环节，客户支付预付款项。 设计出图，开发启动。 内部测试及联调。 试上线及用户测试。 用户培训。 用户验收及交付 客户支付尾款。 信创支持 巴别鸟多年来一直积极响应国产化号召，巴别鸟的产品也能运行在大多数信创环境下。特别是针对服务器端，无论是CPU、操作系统还是数据库，巴别鸟都有相应的信创解决方案。 CPU及服务器架构支持。 巴别鸟支持X86和arm指令集的国产CPU，如X86的龙芯、飞腾、麒麟、海光…同时也支持arm架构的国产CPU，如：鲲鹏架构、飞腾arm架构。 操作系统。 巴别鸟使用docker部署，支持一切支持docker的Linux操作系统。如open Euler、银河麒麟、统信UOS 数据库。 巴别鸟推荐使用AliSQL数据库或其他兼容MySQL的数据库如：open Causs （高斯）。 巴别鸟也可以为定制接入其他国产数据库。如：达梦、人大金仓、南大通用….. 客户端。 巴别鸟客户端可以运行在Linux系统上，支持麒麟、统信等国产化系统。 由于Linux系统文件管理界面并没有统一，Linux版本的巴别鸟不支持同步文件夹及映射盘功能。 分类 分类 标准部署系统（非信创） 巴别鸟信创方案（x86) 巴别鸟信创方案（arm） 信创版本不支持的功能 业务服务器 操作系统 Centos、openEuler、Ubuntu openEuler 、麒麟 鲲鹏、麒麟、统信 无 业务服务器 巴别鸟版本 标准版 巴别鸟信创版（X86） 巴别鸟信创版（arm） 无 业务服务器 数据库 MySQL 高斯、TiDB、aliSql 高斯arm 无 业务服务器 组件/中间件 tomcat tomcat、TongWeb7 tomcat 无 业务服务器 组件/中间件 pomleo pomleo（信创） pomleo（信创） 无 业务服务器 组件/中间件 Elastic Search Elastic Search（ 信创） Elastic Search（arm） 无 业务服务器 组件/中间件 Redis Babel readis Babel readis 无 存储服务器 存储系统 minio minio minio arm 无 客户端 客户端 巴别鸟win/mac客户端 巴别鸟linux/麒麟/Ubuntu客户端 需要二开移植 linux版本客户端不支持映射盘、同步文件夹功能" }, { "lang": "zh", "slug": "reference-whitepaper-10-feature-list", "title": "白皮书：附件1:巴别鸟功能列表", "description": "《巴别鸟企业网盘白皮书》章节：附件1:巴别鸟功能列表。", "category": "源资料参考", "top_category": "维护", "keywords": [ "白皮书", "附件1:巴别鸟功能列表" ], "url": "zh/reference-whitepaper-10-feature-list.html", "source": "content/zh/reference-whitepaper-10-feature-list.md", "summary": "白皮书：附件1:巴别鸟功能列表 功能大项 功能列表 备注说明 支持平台 （ALL指全平台支持） 数据传输 文件加密上传 SSL加密上传 ALL 数据传输 文件加密下载 SSL加密下载 ALL 数据传输 文件夹上传 ALL 数据传输 文件夹下载 ALL 数据传输 批量下载 网页、win客户端、Mac客户端、麒麟客户端 数据传输 批量打包下载 文件夹打包成zip文件下载，有文件数量限制 浏览器（网页） 数据传输 断点续传 win客户端、Mac客户端、麒麟客户端 数据传输 秒传（哈希验证去重） 同样哈希的文件仅保存一份 ALL 数据传输 增量上传下载 只上传下载文件的更改部分 ALL 数据传输 上传下载列表管理 ALL 数据传输 本地文件右键快速上传文件至网盘 win客户端、Mac客户端 数据传输 本地文件右键快速发送文件至其他用户 win客户端、Mac客户端 数据传输 网闸数据摆渡（多套巴别鸟间） 密区和非密区间的数据传输（带审批） 仅私有化部署支持 新建文件 从模版创建文件结构 支持文件模版和文件夹模版 网页、客户端 新建文件 创建模版 网页、客户端 新建文件 新建office文档（word、excel、ppt） 网页、客户端 新建文件 新建文本文件 网页、客户端 新建文件 新建思维导图 网页、客户端 新建文件 新建markdown 网页、客户端 新建文件 新建收件箱 网页、客户端 新建文件 发送消息 发送消息通知给特定用户 网页、客户端 新建文件 新建子部门 网页、客户端 新建文件 新建项目 网页、客户端 新建文件 自定义新建的类型 自定义需要新建的文件类型 仅私有化部署支持 ", "headings": [ { "level": 1, "title": "白皮书：附件1:巴别鸟功能列表", "id": "1" } ], "images": [], "text": "白皮书：附件1:巴别鸟功能列表 功能大项 功能列表 备注说明 支持平台 （ALL指全平台支持） 数据传输 文件加密上传 SSL加密上传 ALL 数据传输 文件加密下载 SSL加密下载 ALL 数据传输 文件夹上传 ALL 数据传输 文件夹下载 ALL 数据传输 批量下载 网页、win客户端、Mac客户端、麒麟客户端 数据传输 批量打包下载 文件夹打包成zip文件下载，有文件数量限制 浏览器（网页） 数据传输 断点续传 win客户端、Mac客户端、麒麟客户端 数据传输 秒传（哈希验证去重） 同样哈希的文件仅保存一份 ALL 数据传输 增量上传下载 只上传下载文件的更改部分 ALL 数据传输 上传下载列表管理 ALL 数据传输 本地文件右键快速上传文件至网盘 win客户端、Mac客户端 数据传输 本地文件右键快速发送文件至其他用户 win客户端、Mac客户端 数据传输 网闸数据摆渡（多套巴别鸟间） 密区和非密区间的数据传输（带审批） 仅私有化部署支持 新建文件 从模版创建文件结构 支持文件模版和文件夹模版 网页、客户端 新建文件 创建模版 网页、客户端 新建文件 新建office文档（word、excel、ppt） 网页、客户端 新建文件 新建文本文件 网页、客户端 新建文件 新建思维导图 网页、客户端 新建文件 新建markdown 网页、客户端 新建文件 新建收件箱 网页、客户端 新建文件 发送消息 发送消息通知给特定用户 网页、客户端 新建文件 新建子部门 网页、客户端 新建文件 新建项目 网页、客户端 新建文件 自定义新建的类型 自定义需要新建的文件类型 仅私有化部署支持 文件管理 个人文件 每个用户独立的个人空间 ALL 文件管理 个人项目 仅由创建者管理，在个人文件中 ALL 文件管理 个人文件管理 是否开启个人文件、个人空间大小限制、个人文件分享开关 管理后台（企业控制台） 文件管理 企业文件 企业文件列表 ALL 文件管理 企业发布文件夹 ALL 文件管理 共同发布文件夹 ALL 文件管理 部门文件 ALL 文件管理 多级部门管理 部门可分层级管理 ALL 文件管理 收件箱 ALL 文件管理 收件箱管理（我的收件箱） ALL 文件管理 部门项目 部门管理者和创建者管理，属于部门 ALL 文件管理 我的项目 ALL 文件管理 全部项目 ALL 文件管理 我的分享 ALL 文件管理 我加入的分享 ALL 文件管理 多级回收站 部门经理及管理员可恢复被删除文件 ALL 文件管理 关注文件（提醒关注文件） 提醒被关注的文件会在被提醒者我的关注列表中展现。 ALL 文件管理 我的关注 ALL 文件管理 文件列表设置 标准列表及简洁列表切换 网页、客户端 文件管理 文件平铺及列表模式切换 网页、客户端 文件管理 文件详情查看面板 网页、客户端 文件管理 文件夹树状目录模式展示 网页、客户端 文件管理 文件排序 ALL 文件管理 设置全局默认排序 ALL 文件管理 自定义快捷菜单 网页、客户端 文件管理 瀑布流模式 网页、客户端 版本管理 保存时自动生成文件新版本 ALL 版本管理 添加版本说明 ALL 版本管理 版本回滚（设定旧版本为当前版本） ALL 版本管理 删除某个旧版本 ALL 版本管理 预览旧版本 ALL 版本管理 版本对比 网页、客户端 版本管理 文件历史版本保存时长设置 管理后台（企业控制台） 版本管理 文件历史版本保存数量设置 管理后台（企业控制台） 搜索及筛选 添加标签 ALL 搜索及筛选 标签管理 网页、客户端 搜索及筛选 标签样式 网页、客户端 搜索及筛选 左侧栏自定义展示标签 网页、客户端 搜索及筛选 企业标签统一管理 管理后台（企业控制台） 搜索及筛选 共享标签 ALL 搜索及筛选 文件列表筛选 网页、客户端 搜索及筛选 图片文件元数据筛选 网页、客户端 搜索及筛选 文件说明及文件说明查找筛选 网页、客户端 搜索及筛选 全文搜索 ALL 搜索及筛选 文件名搜索 ALL 搜索及筛选 标签搜索 ALL 搜索及筛选 选定文件夹搜索 ALL 搜索及筛选 高级搜索 网页、客户端 搜索及筛选 动态搜索 网页、客户端 搜索及筛选 档案库搜索 网页、客户端 在线编辑 及 客户端编辑 office、wps文档在线编辑 ALL 在线编辑 及 客户端编辑 office、wps文档多人协同在线编辑 ALL 在线编辑 及 客户端编辑 思维导图、txt、markdown文件在线编辑 网页、win客户端、Mac客户端、麒麟客户端 在线编辑 及 客户端编辑 office多人在线编辑显示在线编辑者操作 ALL 在线编辑 及 客户端编辑 在线编辑时锁定文件防止非在线编辑冲突 ALL 在线编辑 及 客户端编辑 客户端调用本地程序编辑（支持所有文件） win客户端、Mac客户端、麒麟客户端 在线编辑 及 客户端编辑 客户端编辑自动锁定防止其他用户编辑冲突 win客户端、Mac客户端、麒麟客户端 在线编辑 及 客户端编辑 客户端编辑退出自动解锁 win客户端、Mac客户端、麒麟客户端 分享及协作 发送文件 网页、客户端 分享及协作 邀请分享（验证加入者身份） ALL 分享及协作 链接分享（支持匿名） ALL 分享及协作 快照分享（仅分享当前版本） 网页、客户端 分享及协作 分享可选权限自定义 管理后台（企业控制台） 分享及协作 分享审批 网页、客户端 分享及协作 关闭某部门分享权限 管理后台（企业控制台） 分享及协作 分享日志及统计 网页、客户端 分享及协作 文件评论 ALL 文件预览 及 批注讨论 支持100+种格式文件的在线预览 详见支持预览格式列表 ALL 文件预览 及 批注讨论 CAD文件在线预览及批注 客户端、iOS、安卓 APP端 文件预览 及 批注讨论 3D文件预览及批注支持 网页、客户端 文件预览 及 批注讨论 H5规格视频文件及音频文件在线播放 ALL 文件预览 及 批注讨论 特殊视频及音频文件支持（可选） 需增加视频转码服务器 文件预览 及 批注讨论 在预览界面建立文字批注讨论区 ALL 文件预览 及 批注讨论 在预览界面建立手绘批注 ALL 文件预览 及 批注讨论 在预览界面建立语音批注 iOS、安卓 APP端 文件预览 及 批注讨论 在预览界面标注 ALL 文件预览 及 批注讨论 在预览界面手绘 ALL 文件预览 及 批注讨论 批注管理 ALL 文件预览 及 批注讨论 版本对比 网页、客户端 文件预览 及 批注讨论 预览时文件内内容搜索 网页、客户端 文件预览 及 批注讨论 旋转预览文件 ALL 文件评审 自定义评审流程 网页、客户端 文件评审 多阶段评审 网页、客户端 文件评审 部门设定可选评审方式 网页、客户端 文件评审 评审时批注、手绘、评审完成插入签名 网页、客户端 文件评审 评审后文件定稿 ALL 文件评审 我的评审栏目 所有评审文件统一查看管理 ALL 文件评审 生成评审报告 网页、客户端 权限管理 自定义角色权限（32项权限自由搭配） 管理后台（企业控制台） 权限管理 自定义文件权限（分享、项目、文件） 管理后台（企业控制台） 权限管理 部门及项目文件文件访问控制权限 网页、客户端 权限管理 权限有效期（到期自动失效） ALL 权限管理 多级管理员 网页、客户端 权限管理 提权申请及批准 ALL 同步文件夹 云端任意文件夹可同步到本地任意位置（需要有下载权限） win客户端、Mac客户端 同步文件夹 本地任意文件夹可同步到云端任意位置（需要有上传权限） win客户端、Mac客户端 同步文件夹 双向同步、上行同步、下行同步可切换 win客户端、Mac客户端 同步文件夹 同步文件夹中文件编辑锁定，防止冲突 win客户端、Mac客户端 同步文件夹 同步任务管理列表 win客户端、Mac客户端 同步文件夹 设定自动同步时间 win客户端、Mac客户端 同步文件夹 同步黑名单（特定类型文件不同步） win客户端、Mac客户端 虚拟映射盘 访达及资源管理器访问映射盘 win客户端、Mac客户端 虚拟映射盘 虚拟盘符、虚拟路径 win客户端、Mac客户端 虚拟映射盘 虚拟盘缓存管理 win客户端、Mac客户端 虚拟映射盘 虚拟盘文件编辑自动锁定 win客户端、Mac客户端 虚拟映射盘 点击文件打开文件引用及关联资源 win客户端、Mac客户端 虚拟映射盘 第三方应用程序可访问虚拟盘 win客户端、Mac客户端 归档及档案库 文件、文件夹、项目右键一键归档 网页、客户端 归档及档案库 档案管理员整理及分类档案 网页、客户端 归档及档案库 创建阅览室、阅览室可见范围指定 网页、客户端 归档及档案库 档案搜索及查询 网页、客户端 归档及档案库 档案借阅及借阅审批 网页、客户端 归档及档案库 档案查看记录及日志 网页、客户端 归档及档案库 阅览室管理 网页、客户端 日志及报表 可查询每个文件独立日志 ALL 日志及报表 部门分享文件统计 网页、客户端 日志及报表 部门文件权限设置统计 网页、客户端 日志及报表 部门密级文件统计 网页、客户端 日志及报表 部门文件访问统计（部门文件日志） 网页、客户端 日志及报表 部门成员使用情况查询 网页、客户端 日志及报表 审批报告 网页、客户端 日志及报表 导出部门、文件夹的文件列表 网页、客户端 日志及报表 查询文件的所有可访问者 网页、客户端 日志及报表 导出用户可访问文件及权限列表 网页、客户端 日志及报表 导出成员报表 网页、客户端 日志及报表 系统活跃度统计分析 网页、客户端 日志及报表 文件统计、活跃文件、新建文件、上传统计 网页、客户端 日志及报表 流量使用情况统计 网页、客户端 日志及报表 全盘访问日志及日志导出 网页、客户端 动态及通知 动态栏目 ALL 动态及通知 动态搜索 ALL 动态及通知 文件状态动态 ALL 动态及通知 @用户动态 ALL 动态及通知 文件批注动态 ALL 动态及通知 批注动态直接回复 ALL 讨论组 每个部门及项目自动生成讨论组 ALL 讨论组 讨论组群聊功能 ALL 讨论组 讨论组上传附件功能 ALL 讨论组 讨论组管理列表 ALL 工作台 工作台卡片管理（添加、删除、排序） 网页、客户端 工作台 工作台图表（共17个可选图表） 网页、客户端 工作台 工作台自定义图表 网页、客户端 个人设置 账户信息修改 ALL 个人设置 个人存储空间查询 ALL 个人设置 自定义默认文件排序 网页、客户端 个人设置 密码更改 ALL 个人设置 自定义接收通知类型 网页、客户端 个人设置 分组管理（个人分组管理） 网页、客户端 个人设置 使用设备管理 网页、客户端 个人设置 远程登出某设备账号 网页、客户端 个人设置 邮件存储（自动转存邮箱内容） 网页、客户端 个人设置 个人访问控制文件统计 网页、客户端 个人设置 设定个人签名 网页、客户端 多级管理员 部门可设定部门管理角色 网页、客户端 多级管理员 超级管理员 网页、客户端 多级管理员 档案管理员 网页、客户端 多级管理员 安全保密员 网页、客户端 多级管理员 安全审计员 网页、客户端 多级管理员 运维管理员 网页、客户端 多级管理员 普通成员及受限用户 网页、客户端 企业管理后台 企业基础信息配置 管理后台（企业控制台） 企业管理后台 企业logo设定及更换 管理后台（企业控制台） 企业管理后台 企业登录背景图更换 管理后台（企业控制台） 企业管理后台 企业空间用量查询 管理后台（企业控制台） 企业管理后台 关闭个人空间按钮 管理后台（企业控制台） 企业管理后台 个人文件分享按钮（关闭即不允许个人文件分享） 管理后台（企业控制台） 企业管理后台 企业用户统计 管理后台（企业控制台） 企业管理后台 邮件通知配置 管理后台（企业控制台） 企业管理后台 组织结构树管理（新增、删除、排序、管理部门） 管理后台（企业控制台） 企业管理后台 企业及部门安全策略管理 管理后台（企业控制台） 企业管理后台 权限管理（自定义可选角色及权限） 管理后台（企业控制台） 企业管理后台 成员管理列表 管理后台（企业控制台） 企业管理后台 成员密码、用户名等基本信息修改 管理后台（企业控制台） 企业管理后台 一键交接（转移文件归属） 管理后台（企业控制台） 企业管理后台 一键清空账户权限 管理后台（企业控制台） 企业管理后台 停用及删除账户 管理后台（企业控制台） 企业管理后台 账户文件下载速率限制 管理后台（企业控制台） 企业管理后台 成员所属部门及权限管理 管理后台（企业控制台） 企业管理后台 成员个人文件空间上限设定 管理后台（企业控制台） 企业管理后台 成员文件使用情况及用量统计 管理后台（企业控制台） 企业管理后台 新增企业账号（成员） 管理后台（企业控制台） 企业管理后台 批量导入成员 管理后台（企业控制台） 企业管理后台 批量编辑成员 管理后台（企业控制台） 企业管理后台 企业标签管理 管理后台（企业控制台） 企业管理后台 企业默认审批流程管理 管理后台（企业控制台） 企业管理后台 文件黑名单（黑名单文件或黑名单文件类型不允许上传） 管理后台（企业控制台） 企业管理后台 企业通知管理列表 管理后台（企业控制台） 企业管理后台 发送企业通知 管理后台（企业控制台） 企业管理后台 企业分组管理 管理后台（企业控制台） 企业管理后台 水印类型选择及水印设置 管理后台（企业控制台） 企业管理后台 访问日志栏目（统一管理整个网盘访问日志） 管理后台（企业控制台） 企业管理后台 IP策略（通过客户登录的IP地址约束上传下载登录行为） 管理后台（企业控制台） 企业管理后台 mac地址绑定（限定仅能在特定设备登录） 管理后台（企业控制台） 企业管理后台 统计分析栏目 管理后台（企业控制台） 企业管理后台 工作台推送（推送工作台特定栏目给用户） 管理后台（企业控制台） 企业管理后台 文件使用行为监控预警 异常使用情况邮件或消息通知管理员 管理后台（企业控制台） 企业管理后台 自定义企业发件邮箱 管理后台（企业控制台） 企业管理后台 自定义使用的网盘功能模块 管理后台（企业控制台） 企业管理后台 配置接入第三系统单点登录 管理后台（企业控制台） 企业管理后台 配置从第三方系统导入组织结构 管理后台（企业控制台） 企业管理后台 账户信息同步管理 管理后台（企业控制台） 企业管理后台 安全登出 管理后台（企业控制台） 智巢AI 巴别鸟AI客服助理 网页、客户端 智巢AI 定制客户专属AI助理 仅私有化部署支持 智巢AI 指定文件进行学习并回答文件中的问题 网页、客户端 智巢AI 智巢AI私有化 仅私有化部署支持 账户及第三方对接 钉钉对接及钉钉内访问支持 网页端、客户端可使用钉钉扫码登录 仅私有化部署支持 账户及第三方对接 企业微信对接及企业微信内访问支持 网页端、客户端可使用企业微信扫码登录 仅私有化部署支持 账户及第三方对接 飞书对接及飞书内访问支持 网页端、客户端可使用飞书扫码登录 仅私有化部署支持 账户及第三方对接 第三方系统通知送达 仅私有化部署支持 账户及第三方对接 第三方系统用户同步 仅私有化部署支持 账户及第三方对接 ADFS、AD域控、OA、ERP、PDM对接支持 仅私有化部署支持 账户及第三方对接 第三方账户手机端登录支持 仅私有化部署支持 账户及第三方对接 对接第三方短信平台 仅私有化部署支持 API 标准web API支持 仅私有化部署支持 API API定制服务 仅私有化部署支持 API 对接第三方API实现更多功能 仅私有化部署支持 数据安全 文件SSL加密传输 ALL 数据安全 文件分块加密存储 ALL 数据安全 文件对象存储 ALL 数据安全 转码文件预览（和源文件分开） ALL 数据安全 企业及部门安全策略 ALL 数据安全 文件密级设定 ALL 数据安全 文件独立访问权限、日志、访问统计 ALL 数据安全 嵌入文件的真水印 ALL 数据安全 预览、在线编辑、下载、打印等权限都可以分开 ALL 数据安全 分享及邀请可授权 ALL 数据安全 多级回收站 ALL 数据安全 部门数据独立 ALL 数据安全 安全审计员独立 ALL 数据安全 所有日志后台管理可查询防篡改 ALL 数据安全 权限有效期、分享有效期、项目有效期，到期自动关闭 ALL 数据安全 文件哈希验证防篡改 ALL 数据安全 支持开启二次验证 ALL 数据安全 多管理员分级 ALL 数据安全 成员、受限成员、外部成员区分 ALL 数据安全 密级文件、企业文件、个人文件、外部文件区分 ALL 数据安全 外部成员管理列表 ALL 数据安全 成员空间使用精细化控制 ALL 数据安全 IP策略及MAC地址绑定限定使用设备及区域 ALL 数据安全 多重备份（公有云异地灾备） ALL 数据安全 服务器集群高可用部署 ALL 数据安全 容灾消灾 ALL 数据安全 分布式数据库 ALL 数据安全 云盾防护 仅公有云 数据安全 多监控平台 仅公有云 数据安全 第三方安全扫描 仅公有云 存储 支持S3标准的所有对象存储 私有化部署支持 存储 支持NFS及挂载磁盘存储 私有化部署支持 存储 支持SAN存储及块存储 私有化部署支持 存储 支持为客户在通用服务器上搭建对象存储 私有化部署支持 存储 支持分布式部署及分布式存储系统 私有化部署支持 存储 支持对接NBU等备份服务器 私有化部署支持 存储 支持使用双对象存储服务器同步备份 私有化部署支持 存储 文件分块加密落盘、文件去重 私有化部署支持 私有化部署 标准部署（单服务器或虚拟机部署） 私有化部署支持 私有化部署 分布式集群部署 私有化部署支持 私有化部署 对象存储部署 私有化部署支持 私有化部署 超融合及公有云平台部署（阿里云、腾讯云、华为云、金山云等...) 私有化部署支持 私有化部署 智巢AI私有化部署 私有化部署支持 私有化部署 高可用、高冗余系统部署 私有化部署支持 私有化部署 根据用户需求提供部署方案指导 私有化部署支持 语言 简体中文版 ALL 语言 英文版 ALL 语言 定制需要的语言 仅私有化部署支持 文控模块 （可选） 文控项目创建 工程行业文控规则下的文控管理项目创建 仅私有化部署支持 文控模块 （可选） 文控项目管理 仅私有化部署支持 文控模块 （可选） 文控人员管理 项目中可添加文控人员（可发送文控邮件） 仅私有化部署支持 文控模块 （可选） 收件人管理 管理文控发送邮件的收件人及对应的发送单号 仅私有化部署支持 文控模块 （可选） 发送单信息录入 发送单基本信息及发送单号规则 仅私有化部署支持 文控模块 （可选） 发送单号自动生成 发送文控邮件时按规则自动生成发送单号 仅私有化部署支持 文控模块 （可选） 发送单自动生成 发送文控邮件时按规则自动生成本次发送的发送单 仅私有化部署支持 文控模块 （可选） 文控发件 文控发送附有文件附件及发送单的邮件到指定邮箱。 仅私有化部署支持 文控模块 （可选） 发送单管理 每次发送的发送单及邮件附件统一查询管理，发送成功失败统计，接收状态统计 仅私有化部署支持" }, { "lang": "zh", "slug": "reference-whitepaper-11-basic-api", "title": "白皮书：附件2:巴别鸟开放API（基础API）", "description": "《巴别鸟企业网盘白皮书》章节：附件2:巴别鸟开放API（基础API）。", "category": "源资料参考", "top_category": "维护", "keywords": [ "白皮书", "附件2:巴别鸟开放API（基础API）" ], "url": "zh/reference-whitepaper-11-basic-api.html", "source": "content/zh/reference-whitepaper-11-basic-api.md", "summary": "白皮书：附件2:巴别鸟开放API（基础API） 访问以下链接获取最新API文档： https://www.babel.cc/p/api integration.do", "headings": [ { "level": 1, "title": "白皮书：附件2:巴别鸟开放API（基础API）", "id": "2-api-api" } ], "images": [], "text": "白皮书：附件2:巴别鸟开放API（基础API） 访问以下链接获取最新API文档： https://www.babel.cc/p/api integration.do" }, { "lang": "zh", "slug": "reference-feature-list", "title": "功能列表", "description": "巴别鸟企业网盘功能列表，包含功能大项、功能列表、说明和支持平台。", "category": "源资料参考", "top_category": "维护", "keywords": [ "功能列表", "支持平台" ], "url": "zh/reference-feature-list.html", "source": "content/zh/reference-feature-list.md", "summary": "功能列表 功能大项 功能列表 备注说明 支持平台 （ALL指全平台支持） 数据传输 文件加密上传 SSL加密上传 ALL 数据传输 文件加密下载 SSL加密下载 ALL 数据传输 文件夹上传 ALL 数据传输 文件夹下载 ALL 数据传输 批量下载 网页、win客户端、Mac客户端、麒麟客户端 数据传输 批量打包下载 文件夹打包成zip文件下载，有文件数量限制 浏览器（网页） 数据传输 断点续传 win客户端、Mac客户端、麒麟客户端 数据传输 秒传（哈希验证去重） 同样哈希的文件仅保存一份 ALL 数据传输 增量上传下载 只上传下载文件的更改部分 ALL 数据传输 上传下载列表管理 ALL 数据传输 本地文件右键快速上传文件至网盘 win客户端、Mac客户端 数据传输 本地文件右键快速发送文件至其他用户 win客户端、Mac客户端 数据传输 网闸数据摆渡（多套巴别鸟间） 密区和非密区间的数据传输（带审批） 仅私有化部署支持 新建文件 从模版创建文件结构 支持文件模版和文件夹模版 网页、客户端 新建文件 创建模版 网页、客户端 新建文件 新建office文档（word、excel、ppt） 网页、客户端 新建文件 新建文本文件 网页、客户端 新建文件 新建思维导图 网页、客户端 新建文件 新建markdown 网页、客户端 新建文件 新建收件箱 网页、客户端 新建文件 发送消息 发送消息通知给特定用户 网页、客户端 新建文件 新建子部门 网页、客户端 新建文件 新建项目 网页、客户端 新建文件 自定义新建的类型 自定义需要新建的文件类型 仅私有化部署支持 文件管理 个人文件 每", "headings": [ { "level": 1, "title": "功能列表", "id": "section" } ], "images": [], "text": "功能列表 功能大项 功能列表 备注说明 支持平台 （ALL指全平台支持） 数据传输 文件加密上传 SSL加密上传 ALL 数据传输 文件加密下载 SSL加密下载 ALL 数据传输 文件夹上传 ALL 数据传输 文件夹下载 ALL 数据传输 批量下载 网页、win客户端、Mac客户端、麒麟客户端 数据传输 批量打包下载 文件夹打包成zip文件下载，有文件数量限制 浏览器（网页） 数据传输 断点续传 win客户端、Mac客户端、麒麟客户端 数据传输 秒传（哈希验证去重） 同样哈希的文件仅保存一份 ALL 数据传输 增量上传下载 只上传下载文件的更改部分 ALL 数据传输 上传下载列表管理 ALL 数据传输 本地文件右键快速上传文件至网盘 win客户端、Mac客户端 数据传输 本地文件右键快速发送文件至其他用户 win客户端、Mac客户端 数据传输 网闸数据摆渡（多套巴别鸟间） 密区和非密区间的数据传输（带审批） 仅私有化部署支持 新建文件 从模版创建文件结构 支持文件模版和文件夹模版 网页、客户端 新建文件 创建模版 网页、客户端 新建文件 新建office文档（word、excel、ppt） 网页、客户端 新建文件 新建文本文件 网页、客户端 新建文件 新建思维导图 网页、客户端 新建文件 新建markdown 网页、客户端 新建文件 新建收件箱 网页、客户端 新建文件 发送消息 发送消息通知给特定用户 网页、客户端 新建文件 新建子部门 网页、客户端 新建文件 新建项目 网页、客户端 新建文件 自定义新建的类型 自定义需要新建的文件类型 仅私有化部署支持 文件管理 个人文件 每个用户独立的个人空间 ALL 文件管理 个人项目 仅由创建者管理，在个人文件中 ALL 文件管理 个人文件管理 是否开启个人文件、个人空间大小限制、个人文件分享开关 管理后台（企业控制台） 文件管理 企业文件 企业文件列表 ALL 文件管理 企业发布文件夹 ALL 文件管理 共同发布文件夹 ALL 文件管理 部门文件 ALL 文件管理 多级部门管理 部门可分层级管理 ALL 文件管理 收件箱 ALL 文件管理 收件箱管理（我的收件箱） ALL 文件管理 部门项目 部门管理者和创建者管理，属于部门 ALL 文件管理 我的项目 ALL 文件管理 全部项目 ALL 文件管理 我的分享 ALL 文件管理 我加入的分享 ALL 文件管理 多级回收站 部门经理及管理员可恢复被删除文件 ALL 文件管理 关注文件（提醒关注文件） 提醒被关注的文件会在被提醒者我的关注列表中展现。 ALL 文件管理 我的关注 ALL 文件管理 文件列表设置 标准列表及简洁列表切换 网页、客户端 文件管理 文件平铺及列表模式切换 网页、客户端 文件管理 文件详情查看面板 网页、客户端 文件管理 文件夹树状目录模式展示 网页、客户端 文件管理 文件排序 ALL 文件管理 设置全局默认排序 ALL 文件管理 自定义快捷菜单 网页、客户端 文件管理 瀑布流模式 网页、客户端 版本管理 保存时自动生成文件新版本 ALL 版本管理 添加版本说明 ALL 版本管理 版本回滚（设定旧版本为当前版本） ALL 版本管理 删除某个旧版本 ALL 版本管理 预览旧版本 ALL 版本管理 版本对比 网页、客户端 版本管理 文件历史版本保存时长设置 管理后台（企业控制台） 版本管理 文件历史版本保存数量设置 管理后台（企业控制台） 搜索及筛选 添加标签 ALL 搜索及筛选 标签管理 网页、客户端 搜索及筛选 标签样式 网页、客户端 搜索及筛选 左侧栏自定义展示标签 网页、客户端 搜索及筛选 企业标签统一管理 管理后台（企业控制台） 搜索及筛选 共享标签 ALL 搜索及筛选 文件列表筛选 网页、客户端 搜索及筛选 图片文件元数据筛选 网页、客户端 搜索及筛选 文件说明及文件说明查找筛选 网页、客户端 搜索及筛选 全文搜索 ALL 搜索及筛选 文件名搜索 ALL 搜索及筛选 标签搜索 ALL 搜索及筛选 选定文件夹搜索 ALL 搜索及筛选 高级搜索 网页、客户端 搜索及筛选 动态搜索 网页、客户端 搜索及筛选 档案库搜索 网页、客户端 在线编辑 及 客户端编辑 office、wps文档在线编辑 ALL 在线编辑 及 客户端编辑 office、wps文档多人协同在线编辑 ALL 在线编辑 及 客户端编辑 思维导图、txt、markdown文件在线编辑 网页、win客户端、Mac客户端、麒麟客户端 在线编辑 及 客户端编辑 office多人在线编辑显示在线编辑者操作 ALL 在线编辑 及 客户端编辑 在线编辑时锁定文件防止非在线编辑冲突 ALL 在线编辑 及 客户端编辑 客户端调用本地程序编辑（支持所有文件） win客户端、Mac客户端、麒麟客户端 在线编辑 及 客户端编辑 客户端编辑自动锁定防止其他用户编辑冲突 win客户端、Mac客户端、麒麟客户端 在线编辑 及 客户端编辑 客户端编辑退出自动解锁 win客户端、Mac客户端、麒麟客户端 分享及协作 发送文件 网页、客户端 分享及协作 邀请分享（验证加入者身份） ALL 分享及协作 链接分享（支持匿名） ALL 分享及协作 快照分享（仅分享当前版本） 网页、客户端 分享及协作 分享可选权限自定义 管理后台（企业控制台） 分享及协作 分享审批 网页、客户端 分享及协作 关闭某部门分享权限 管理后台（企业控制台） 分享及协作 分享日志及统计 网页、客户端 分享及协作 文件评论 ALL 文件预览 及 批注讨论 支持100+种格式文件的在线预览 详见支持预览格式列表 ALL 文件预览 及 批注讨论 CAD文件在线预览及批注 客户端、iOS、安卓 APP端 文件预览 及 批注讨论 3D文件预览及批注支持 网页、客户端 文件预览 及 批注讨论 H5规格视频文件及音频文件在线播放 ALL 文件预览 及 批注讨论 特殊视频及音频文件支持（可选） 需增加视频转码服务器 文件预览 及 批注讨论 在预览界面建立文字批注讨论区 ALL 文件预览 及 批注讨论 在预览界面建立手绘批注 ALL 文件预览 及 批注讨论 在预览界面建立语音批注 iOS、安卓 APP端 文件预览 及 批注讨论 在预览界面标注 ALL 文件预览 及 批注讨论 在预览界面手绘 ALL 文件预览 及 批注讨论 批注管理 ALL 文件预览 及 批注讨论 版本对比 网页、客户端 文件预览 及 批注讨论 预览时文件内内容搜索 网页、客户端 文件预览 及 批注讨论 旋转预览文件 ALL 文件评审 自定义评审流程 网页、客户端 文件评审 多阶段评审 网页、客户端 文件评审 部门设定可选评审方式 网页、客户端 文件评审 评审时批注、手绘、评审完成插入签名 网页、客户端 文件评审 评审后文件定稿 ALL 文件评审 我的评审栏目 所有评审文件统一查看管理 ALL 文件评审 生成评审报告 网页、客户端 权限管理 自定义角色权限（32项权限自由搭配） 管理后台（企业控制台） 权限管理 自定义文件权限（分享、项目、文件） 管理后台（企业控制台） 权限管理 部门及项目文件文件访问控制权限 网页、客户端 权限管理 权限有效期（到期自动失效） ALL 权限管理 多级管理员 网页、客户端 权限管理 提权申请及批准 ALL 同步文件夹 云端任意文件夹可同步到本地任意位置（需要有下载权限） win客户端、Mac客户端 同步文件夹 本地任意文件夹可同步到云端任意位置（需要有上传权限） win客户端、Mac客户端 同步文件夹 双向同步、上行同步、下行同步可切换 win客户端、Mac客户端 同步文件夹 同步文件夹中文件编辑锁定，防止冲突 win客户端、Mac客户端 同步文件夹 同步任务管理列表 win客户端、Mac客户端 同步文件夹 设定自动同步时间 win客户端、Mac客户端 同步文件夹 同步黑名单（特定类型文件不同步） win客户端、Mac客户端 虚拟映射盘 访达及资源管理器访问映射盘 win客户端、Mac客户端 虚拟映射盘 虚拟盘符、虚拟路径 win客户端、Mac客户端 虚拟映射盘 虚拟盘缓存管理 win客户端、Mac客户端 虚拟映射盘 虚拟盘文件编辑自动锁定 win客户端、Mac客户端 虚拟映射盘 点击文件打开文件引用及关联资源 win客户端、Mac客户端 虚拟映射盘 第三方应用程序可访问虚拟盘 win客户端、Mac客户端 归档及档案库 文件、文件夹、项目右键一键归档 网页、客户端 归档及档案库 档案管理员整理及分类档案 网页、客户端 归档及档案库 创建阅览室、阅览室可见范围指定 网页、客户端 归档及档案库 档案搜索及查询 网页、客户端 归档及档案库 档案借阅及借阅审批 网页、客户端 归档及档案库 档案查看记录及日志 网页、客户端 归档及档案库 阅览室管理 网页、客户端 日志及报表 可查询每个文件独立日志 ALL 日志及报表 部门分享文件统计 网页、客户端 日志及报表 部门文件权限设置统计 网页、客户端 日志及报表 部门密级文件统计 网页、客户端 日志及报表 部门文件访问统计（部门文件日志） 网页、客户端 日志及报表 部门成员使用情况查询 网页、客户端 日志及报表 审批报告 网页、客户端 日志及报表 导出部门、文件夹的文件列表 网页、客户端 日志及报表 查询文件的所有可访问者 网页、客户端 日志及报表 导出用户可访问文件及权限列表 网页、客户端 日志及报表 导出成员报表 网页、客户端 日志及报表 系统活跃度统计分析 网页、客户端 日志及报表 文件统计、活跃文件、新建文件、上传统计 网页、客户端 日志及报表 流量使用情况统计 网页、客户端 日志及报表 全盘访问日志及日志导出 网页、客户端 动态及通知 动态栏目 ALL 动态及通知 动态搜索 ALL 动态及通知 文件状态动态 ALL 动态及通知 @用户动态 ALL 动态及通知 文件批注动态 ALL 动态及通知 批注动态直接回复 ALL 讨论组 每个部门及项目自动生成讨论组 ALL 讨论组 讨论组群聊功能 ALL 讨论组 讨论组上传附件功能 ALL 讨论组 讨论组管理列表 ALL 工作台 工作台卡片管理（添加、删除、排序） 网页、客户端 工作台 工作台图表（共17个可选图表） 网页、客户端 工作台 工作台自定义图表 网页、客户端 个人设置 账户信息修改 ALL 个人设置 个人存储空间查询 ALL 个人设置 自定义默认文件排序 网页、客户端 个人设置 密码更改 ALL 个人设置 自定义接收通知类型 网页、客户端 个人设置 分组管理（个人分组管理） 网页、客户端 个人设置 使用设备管理 网页、客户端 个人设置 远程登出某设备账号 网页、客户端 个人设置 邮件存储（自动转存邮箱内容） 网页、客户端 个人设置 个人访问控制文件统计 网页、客户端 个人设置 设定个人签名 网页、客户端 多级管理员 部门可设定部门管理角色 网页、客户端 多级管理员 超级管理员 网页、客户端 多级管理员 档案管理员 网页、客户端 多级管理员 安全保密员 网页、客户端 多级管理员 安全审计员 网页、客户端 多级管理员 运维管理员 网页、客户端 多级管理员 普通成员及受限用户 网页、客户端 企业管理后台 企业基础信息配置 管理后台（企业控制台） 企业管理后台 企业logo设定及更换 管理后台（企业控制台） 企业管理后台 企业登录背景图更换 管理后台（企业控制台） 企业管理后台 企业空间用量查询 管理后台（企业控制台） 企业管理后台 关闭个人空间按钮 管理后台（企业控制台） 企业管理后台 个人文件分享按钮（关闭即不允许个人文件分享） 管理后台（企业控制台） 企业管理后台 企业用户统计 管理后台（企业控制台） 企业管理后台 邮件通知配置 管理后台（企业控制台） 企业管理后台 组织结构树管理（新增、删除、排序、管理部门） 管理后台（企业控制台） 企业管理后台 企业及部门安全策略管理 管理后台（企业控制台） 企业管理后台 权限管理（自定义可选角色及权限） 管理后台（企业控制台） 企业管理后台 成员管理列表 管理后台（企业控制台） 企业管理后台 成员密码、用户名等基本信息修改 管理后台（企业控制台） 企业管理后台 一键交接（转移文件归属） 管理后台（企业控制台） 企业管理后台 一键清空账户权限 管理后台（企业控制台） 企业管理后台 停用及删除账户 管理后台（企业控制台） 企业管理后台 账户文件下载速率限制 管理后台（企业控制台） 企业管理后台 成员所属部门及权限管理 管理后台（企业控制台） 企业管理后台 成员个人文件空间上限设定 管理后台（企业控制台） 企业管理后台 成员文件使用情况及用量统计 管理后台（企业控制台） 企业管理后台 新增企业账号（成员） 管理后台（企业控制台） 企业管理后台 批量导入成员 管理后台（企业控制台） 企业管理后台 批量编辑成员 管理后台（企业控制台） 企业管理后台 企业标签管理 管理后台（企业控制台） 企业管理后台 企业默认审批流程管理 管理后台（企业控制台） 企业管理后台 文件黑名单（黑名单文件或黑名单文件类型不允许上传） 管理后台（企业控制台） 企业管理后台 企业通知管理列表 管理后台（企业控制台） 企业管理后台 发送企业通知 管理后台（企业控制台） 企业管理后台 企业分组管理 管理后台（企业控制台） 企业管理后台 水印类型选择及水印设置 管理后台（企业控制台） 企业管理后台 访问日志栏目（统一管理整个网盘访问日志） 管理后台（企业控制台） 企业管理后台 IP策略（通过客户登录的IP地址约束上传下载登录行为） 管理后台（企业控制台） 企业管理后台 mac地址绑定（限定仅能在特定设备登录） 管理后台（企业控制台） 企业管理后台 统计分析栏目 管理后台（企业控制台） 企业管理后台 工作台推送（推送工作台特定栏目给用户） 管理后台（企业控制台） 企业管理后台 文件使用行为监控预警 异常使用情况邮件或消息通知管理员 管理后台（企业控制台） 企业管理后台 自定义企业发件邮箱 管理后台（企业控制台） 企业管理后台 自定义使用的网盘功能模块 管理后台（企业控制台） 企业管理后台 配置接入第三系统单点登录 管理后台（企业控制台） 企业管理后台 配置从第三方系统导入组织结构 管理后台（企业控制台） 企业管理后台 账户信息同步管理 管理后台（企业控制台） 企业管理后台 安全登出 管理后台（企业控制台） 智巢AI 巴别鸟AI客服助理 网页、客户端 智巢AI 定制客户专属AI助理 仅私有化部署支持 智巢AI 指定文件进行学习并回答文件中的问题 网页、客户端 智巢AI 智巢AI私有化 仅私有化部署支持 账户及第三方对接 钉钉对接及钉钉内访问支持 网页端、客户端可使用钉钉扫码登录 仅私有化部署支持 账户及第三方对接 企业微信对接及企业微信内访问支持 网页端、客户端可使用企业微信扫码登录 仅私有化部署支持 账户及第三方对接 飞书对接及飞书内访问支持 网页端、客户端可使用飞书扫码登录 仅私有化部署支持 账户及第三方对接 第三方系统通知送达 仅私有化部署支持 账户及第三方对接 第三方系统用户同步 仅私有化部署支持 账户及第三方对接 ADFS、AD域控、OA、ERP、PDM对接支持 仅私有化部署支持 账户及第三方对接 第三方账户手机端登录支持 仅私有化部署支持 账户及第三方对接 对接第三方短信平台 仅私有化部署支持 API 标准web API支持 仅私有化部署支持 API API定制服务 仅私有化部署支持 API 对接第三方API实现更多功能 仅私有化部署支持 数据安全 文件SSL加密传输 ALL 数据安全 文件分块加密存储 ALL 数据安全 文件对象存储 ALL 数据安全 转码文件预览（和源文件分开） ALL 数据安全 企业及部门安全策略 ALL 数据安全 文件密级设定 ALL 数据安全 文件独立访问权限、日志、访问统计 ALL 数据安全 嵌入文件的真水印 ALL 数据安全 预览、在线编辑、下载、打印等权限都可以分开 ALL 数据安全 分享及邀请可授权 ALL 数据安全 多级回收站 ALL 数据安全 部门数据独立 ALL 数据安全 安全审计员独立 ALL 数据安全 所有日志后台管理可查询防篡改 ALL 数据安全 权限有效期、分享有效期、项目有效期，到期自动关闭 ALL 数据安全 文件哈希验证防篡改 ALL 数据安全 支持开启二次验证 ALL 数据安全 多管理员分级 ALL 数据安全 成员、受限成员、外部成员区分 ALL 数据安全 密级文件、企业文件、个人文件、外部文件区分 ALL 数据安全 外部成员管理列表 ALL 数据安全 成员空间使用精细化控制 ALL 数据安全 IP策略及MAC地址绑定限定使用设备及区域 ALL 数据安全 多重备份（公有云异地灾备） ALL 数据安全 服务器集群高可用部署 ALL 数据安全 容灾消灾 ALL 数据安全 分布式数据库 ALL 数据安全 云盾防护 仅公有云 数据安全 多监控平台 仅公有云 数据安全 第三方安全扫描 仅公有云 存储 支持S3标准的所有对象存储 私有化部署支持 存储 支持NFS及挂载磁盘存储 私有化部署支持 存储 支持SAN存储及块存储 私有化部署支持 存储 支持为客户在普通服务器上搭建对象存储 私有化部署支持 存储 支持分布式部署及分布式存储系统 私有化部署支持 存储 支持对接NBU等备份服务器 私有化部署支持 存储 支持使用双对象存储服务器同步备份 私有化部署支持 存储 文件分块加密落盘、文件去重 私有化部署支持 私有化部署 标准部署（单服务器或虚拟机部署） 私有化部署支持 私有化部署 分布式集群部署 私有化部署支持 私有化部署 对象存储部署 私有化部署支持 私有化部署 超融合及公有云平台部署（阿里云、腾讯云、华为云、金山云等...) 私有化部署支持 私有化部署 智巢AI私有化部署 私有化部署支持 私有化部署 高可用、高冗余系统部署 私有化部署支持 私有化部署 根据用户需求提供部署方案指导 私有化部署支持 语言 简体中文版 ALL 语言 英文版 ALL 语言 定制需要的语言 仅私有化部署支持 文控模块 （可选） 文控项目创建 工程行业文控规则下的文控管理项目创建 仅私有化部署支持 文控模块 （可选） 文控项目管理 仅私有化部署支持 文控模块 （可选） 文控人员管理 项目中可添加文控人员（可发送文控邮件） 仅私有化部署支持 文控模块 （可选） 收件人管理 管理文控发送邮件的收件人及对应的发送单号 仅私有化部署支持 文控模块 （可选） 发送单信息录入 发送单基本信息及发送单号规则 仅私有化部署支持 文控模块 （可选） 发送单号自动生成 发送文控邮件时按规则自动生成发送单号 仅私有化部署支持 文控模块 （可选） 发送单自动生成 发送文控邮件时按规则自动生成本次发送的发送单 仅私有化部署支持 文控模块 （可选） 文控发件 文控发送附有文件附件及发送单的邮件到指定邮箱。 仅私有化部署支持 文控模块 （可选） 发送单管理 每次发送的发送单及邮件附件统一查询管理，发送成功失败统计，接收状态统计 仅私有化部署支持" }, { "lang": "zh", "slug": "reference-integration-guide", "title": "企业微信、钉钉及飞书接入指南", "description": "企业微信、钉钉和飞书的接入指南参考内容。", "category": "源资料参考", "top_category": "维护", "keywords": [ "企业微信", "钉钉", "飞书", "接入指南" ], "url": "zh/reference-integration-guide.html", "source": "content/zh/reference-integration-guide.md", "summary": "企业微信、钉钉及飞书接入指南 巴别鸟企业微信、钉钉、飞书接入指南 企业微信接入配置说明 1. 获得相关信息 （提供给巴别鸟） 1）企业 CropId 在此获得企业的cropId 2）应用 AngentId， Secret 通过创建内部 添加完自己的应用后，点开 san 获得agentId 与secret 2. 配置工作台主 点击工作台应用主页 https://open.weixin.qq.com/connect/oauth2/authorize?appid=XXXXXXXXXXX&redirect uri=http%3A%2F%2Fprivate.babel.cc%2Faccount%2FentWechatInnerSigninRedirect.do&response type=code&scope=snsapi base&state=STATE wechat redirect 替换其中的 appid = “XXXXXXXXXXXX”;更改为自己的cropId //redirct uri替换成 自己 的 scheme 和 domain 如 http , private.babel.cc 3. 开发者接口 1). 网页授权及JS SDK 配置 可信域名 如 private.babel.cc （需要使用微信JS SDK, 需完成域名归属验证 ，并将验证文件发给巴别鸟） 点击 网页授权及JS SDK 可信域名中输入自己的域名 再 申请域名校验，并获得验证文件 2). 企业微信授权登录 点击企业微信授权登录 配置web网页 ，扫码登录， 在 授权回调域 中输入自己的企业域名(同 可信域", "headings": [ { "level": 1, "title": "企业微信、钉钉及飞书接入指南", "id": "section" } ], "images": [], "text": "企业微信、钉钉及飞书接入指南 巴别鸟企业微信、钉钉、飞书接入指南 企业微信接入配置说明 1. 获得相关信息 （提供给巴别鸟） 1）企业 CropId 在此获得企业的cropId 2）应用 AngentId， Secret 通过创建内部 添加完自己的应用后，点开 san 获得agentId 与secret 2. 配置工作台主 点击工作台应用主页 https://open.weixin.qq.com/connect/oauth2/authorize?appid=XXXXXXXXXXX&redirect uri=http%3A%2F%2Fprivate.babel.cc%2Faccount%2FentWechatInnerSigninRedirect.do&response type=code&scope=snsapi base&state=STATE wechat redirect 替换其中的 appid = “XXXXXXXXXXXX”;更改为自己的cropId //redirct uri替换成 自己 的 scheme 和 domain 如 http , private.babel.cc 3. 开发者接口 1). 网页授权及JS SDK 配置 可信域名 如 private.babel.cc （需要使用微信JS SDK, 需完成域名归属验证 ，并将验证文件发给巴别鸟） 点击 网页授权及JS SDK 可信域名中输入自己的域名 再 申请域名校验，并获得验证文件 2). 企业微信授权登录 点击企业微信授权登录 配置web网页 ，扫码登录， 在 授权回调域 中输入自己的企业域名(同 可信域名) 如 private.babel.cc 配置 ios应用 ，输入的BundleID 需从巴别鸟获得, 并将生成的schema 发送给巴别鸟 配置 android应用， 输入的 应用签名 与 应用包名 需从巴别鸟获得，并将生成的schema 发送给巴别鸟 (android 的schema 同ios 的schema) 钉钉企业内部应用配置说明 第一部分 新建H5微应用 登录钉钉企业管理后台 钉钉企业管理后台登录网址https://oa.dingtalk.com/ /login，没有企业账号的，先注册，注册按照钉钉的注册流程即可。注意需要钉钉的管理员账号登录，因为后面新建内部应用需要有管理员权限。 新建企业内部H5微应用 1，登录钉钉开放平台 第一种方式，管理员登录成功后，点击顶部的【工作台】，找到【自建应用】，然后点击自建应用按钮。 第二种方式，管理员登录成功后，在同一个浏览器中输入https://open dev.dingtalk.com/ /index，打开网址，进入到开钉钉开放平台，如果你未登录，再登录一次。 2，新建H5微应用 进入到开钉钉开放平台后，点击顶部的【应用开发】，然后在侧边栏点击【企业内部开发】下的【H5微应用】，最后点击【创建应用按钮】 按照钉钉的要求填写应用的基本信息，开发方式选择【企业内部自主开发】 点击下一步，进入以下界面，配置开发信息界面。开发模式选【开发应用】，开发应用类型选【微应用】，其它的按钉钉要求填写。应用首页地址填写巴别鸟文档管理系统私有化后的服务器网站首页网址，服务器出口IP填写上述网址对应的IP地址，这个地址必须填写正确，否则钉钉很多功能将无法使用。点击【创建】按钮，创建应用成功。 给应用开启权限 创建应用成功后进入以下界面。点击【接口权限】 在【接口权限】界面，基础权限是默认开通的。 高级权限 企业通信录权限，需要我们手动开通，点击后面每行权限对应的按钮开通相应的权限，我们需要企业通信录的所有权限，以实现巴别鸟账号与钉钉账号打通。权限开通后如下： 至此，应用的创建与配置已经完毕。 接入巴别鸟文档管理系统 巴别鸟文档管理系统与钉钉对接，需要提供钉钉应用的信息，CorpId，AppKey，AppSecret。 获取CorpId。 登录钉钉开放平台后，点击顶部【首页】，在首页页面就可以查看CorpId。 获取AppKey，AppSecret。 登录钉钉开放平台后，点击顶部【应用开发】，左边侧栏选择【企业内部开发】 【H5微应用】，然后点击自己新建的应用，进入应用详细页面。 应用详情页面： 在这里便可以查到AppKey，AppSecret： 将获取到的CorpId，AppKey，AppSecret提供给巴别鸟的相关人员即可。 应用发布 相关配置及巴别鸟文档管理服务器准备就绪后，就可以发布H5应用了。进入应用详情页面，选择【应用发布】，然后点击【确认发布按钮】。 第二部分 钉钉扫码登录 钉钉授权登录配置 登录钉钉开放平台后，点击顶部【应用开发】，左边侧栏选择【移动应用接入】 【登录】，然后点击按钮【创建扫码登录应用授权】，创建扫码登录应用授权。 获取登录appId，appSecret 创建扫码登录应用授权成功后，在【登录】页面的列表里可以查询到应用的appId，appSecret。 将获取到的appId，appSecret提供给巴别鸟的相关人员即可。 飞书企业内部应用配置说明 第一部分 新建H5微应用 一、登陆飞书管理后台，点击应用管理 创建企业自建应用 输入相应的信息并确定创建 获取凭证与基础信息，并将获得的APP ID与APP Secret 发给巴别鸟 在应用功能项下点击网页输入网页配置，配置相应的地址 https://open.feishu.cn/open apis/authen/v1/index?app id=XXXXXXXXXX&redirect uri=http%3a%2F%2Fprivate.babel.cc%2Faccount%2FfeishuQRScanRedirect.do&state=STATE app id与地址需要替换成相应自己应用的 应用功能下打开机器人功能，以实现消息发送 需打开相应的权限，在下面权限设置中添加 应用功能下打开移动应用登录功能，以实现巴别鸟APP端，以飞书应用授权登录 用户登录协议 OAuth2.0 iOS应用配置 iOS Bundle ID 联系巴别鸟获取 android应用配置 请联系巴别鸟获取 安全设置，需要设置重定向URL 与IP 白名单 重定向URL http://private.babel.cc/account/feishuQRScanRedirect.do，用自己网盘地址及http/https 替换private.babel.cc IP 白名单，为部署是务器的公网IP地址 H5 可信域名设置为相应的网盘服务器地址 权限管理 ，暂时开通的权限有： 以应用身份读取通讯录 获取部门基础信息 获取部门组织架构信息 获取用户基本信息 获取用户组织架构信息 获取用户邮箱信息 获取用户 user ID 通过手机号或邮箱获取用户 ID 获取用户手机号 获取与发送单聊、群组消息 获取用户在群组中@机器人的消息 接收群聊中@机器人消息事件 获取用户发给机器人的单聊消息 以应用的身份发消息 给一个或多个部门的成员批量发消息 给多个用户批量发消息 发布应用 创建版本，提交版本 应用审核" }, { "lang": "zh", "slug": "reference-product-intro-cases", "title": "产品介绍与案例资料", "description": "巴别鸟企业网盘产品介绍、智巢 AI 和客户案例资料。", "category": "源资料参考", "top_category": "维护", "keywords": [ "产品介绍", "案例", "智巢AI" ], "url": "zh/reference-product-intro-cases.html", "source": "content/zh/reference-product-intro-cases.md", "summary": "产品介绍与案例资料 以下内容按原文页序整理，便于按关键词查找功能、案例和实施信息。 PDF 第 1 页 企业网盘及文件协同管理系统 PDF 第 2 页 巴别鸟 公司介绍 BabelBird PDF 第 3 页 巴别鸟 公司概述 BabelBird 优质客户： 部分资质： 巴别鸟是上海画擎信息科技有限公司的注册商标及 主要产品，上海画擎成立于2012年，总部位于上 海，2016年于北京设立分公司。画擎科技是一个 以技术为主导的团队，创始人均来自北大方正，拥 有极强的图形图像处理和云计算技术并专注于安全 存储及办公协作系统的研发。目前，巴别鸟已经完 成了B轮融资，用户数超过80万，文档数据量已突 破30PB。 图形图像和云计算领域的孜孜耕耘，高效工作方式 的不懈探索，以及对产品用户体验的极致追求，造 就了巴别鸟文档管理及协作平台。你可以用巴别鸟 解决 企业文件统一管理、协同协作、数据安全 三 大问题，大幅提高企业工作效率及数据安全性。 PDF 第 4 页 巴别鸟 产品介绍 BabelBird PDF 第 5 页 我们解决什么问题 文档混乱管理难 邮件工作效率低 来回讨论耗时长 文件异地编辑难 根据组织结构及成员权限统一管理 在所有设备版本一致。与伙伴同步 打开大多数格式文件，在文件内容 巴别鸟可以直接编辑在线文件 文件，全文搜索快速查找 共享文件，协同工作 上直接建立批注实时讨论 从office到CAD。高效完成协作 无权限不安全 OA审批太死板 档案管理成本高 系统培训费人工 角色、行为、部门、文件的权限 可按业务需求自定义各种审批流程 内置知识管理及档案管理模块 简单使用不改变", "headings": [ { "level": 1, "title": "产品介绍与案例资料", "id": "section" }, { "level": 2, "title": "PDF 第 1 页", "id": "pdf-1" }, { "level": 2, "title": "PDF 第 2 页", "id": "pdf-2" }, { "level": 2, "title": "PDF 第 3 页", "id": "pdf-3" }, { "level": 2, "title": "PDF 第 4 页", "id": "pdf-4" }, { "level": 2, "title": "PDF 第 5 页", "id": "pdf-5" }, { "level": 2, "title": "PDF 第 6 页", "id": "pdf-6" }, { "level": 2, "title": "PDF 第 7 页", "id": "pdf-7" }, { "level": 2, "title": "PDF 第 8 页", "id": "pdf-8" }, { "level": 2, "title": "PDF 第 9 页", "id": "pdf-9" }, { "level": 2, "title": "PDF 第 10 页", "id": "pdf-10" }, { "level": 2, "title": "PDF 第 11 页", "id": "pdf-11" }, { "level": 2, "title": "PDF 第 12 页", "id": "pdf-12" }, { "level": 2, "title": "PDF 第 13 页", "id": "pdf-13" }, { "level": 2, "title": "PDF 第 14 页", "id": "pdf-14" }, { "level": 2, "title": "PDF 第 15 页", "id": "pdf-15" }, { "level": 2, "title": "PDF 第 16 页", "id": "pdf-16" }, { "level": 2, "title": "PDF 第 17 页", "id": "pdf-17" }, { "level": 2, "title": "PDF 第 18 页", "id": "pdf-18" }, { "level": 2, "title": "PDF 第 19 页", "id": "pdf-19" }, { "level": 2, "title": "PDF 第 20 页", "id": "pdf-20" }, { "level": 2, "title": "PDF 第 21 页", "id": "pdf-21" }, { "level": 2, "title": "PDF 第 22 页", "id": "pdf-22" }, { "level": 2, "title": "PDF 第 23 页", "id": "pdf-23" }, { "level": 2, "title": "PDF 第 24 页", "id": "pdf-24" }, { "level": 2, "title": "PDF 第 25 页", "id": "pdf-25" }, { "level": 2, "title": "PDF 第 26 页", "id": "pdf-26" }, { "level": 2, "title": "PDF 第 27 页", "id": "pdf-27" }, { "level": 2, "title": "PDF 第 28 页", "id": "pdf-28" }, { "level": 2, "title": "PDF 第 29 页", "id": "pdf-29" }, { "level": 2, "title": "PDF 第 30 页", "id": "pdf-30" }, { "level": 2, "title": "PDF 第 31 页", "id": "pdf-31" }, { "level": 2, "title": "PDF 第 32 页", "id": "pdf-32" }, { "level": 2, "title": "PDF 第 33 页", "id": "pdf-33" }, { "level": 2, "title": "PDF 第 34 页", "id": "pdf-34" }, { "level": 2, "title": "PDF 第 35 页", "id": "pdf-35" }, { "level": 2, "title": "PDF 第 36 页", "id": "pdf-36" }, { "level": 2, "title": "PDF 第 37 页", "id": "pdf-37" }, { "level": 2, "title": "PDF 第 38 页", "id": "pdf-38" }, { "level": 2, "title": "PDF 第 39 页", "id": "pdf-39" }, { "level": 2, "title": "PDF 第 40 页", "id": "pdf-40" }, { "level": 2, "title": "PDF 第 41 页", "id": "pdf-41" }, { "level": 2, "title": "PDF 第 42 页", "id": "pdf-42" }, { "level": 2, "title": "PDF 第 43 页", "id": "pdf-43" }, { "level": 2, "title": "PDF 第 44 页", "id": "pdf-44" }, { "level": 2, "title": "PDF 第 45 页", "id": "pdf-45" }, { "level": 2, "title": "PDF 第 46 页", "id": "pdf-46" }, { "level": 2, "title": "PDF 第 47 页", "id": "pdf-47" }, { "level": 2, "title": "PDF 第 48 页", "id": "pdf-48" }, { "level": 2, "title": "PDF 第 49 页", "id": "pdf-49" }, { "level": 2, "title": "PDF 第 50 页", "id": "pdf-50" }, { "level": 2, "title": "PDF 第 51 页", "id": "pdf-51" }, { "level": 2, "title": "PDF 第 52 页", "id": "pdf-52" }, { "level": 2, "title": "PDF 第 53 页", "id": "pdf-53" }, { "level": 2, "title": "PDF 第 54 页", "id": "pdf-54" }, { "level": 2, "title": "PDF 第 55 页", "id": "pdf-55" }, { "level": 2, "title": "PDF 第 56 页", "id": "pdf-56" }, { "level": 2, "title": "PDF 第 57 页", "id": "pdf-57" }, { "level": 2, "title": "PDF 第 58 页", "id": "pdf-58" }, { "level": 2, "title": "PDF 第 59 页", "id": "pdf-59" }, { "level": 2, "title": "PDF 第 60 页", "id": "pdf-60" }, { "level": 2, "title": "PDF 第 61 页", "id": "pdf-61" } ], "images": [], "text": "产品介绍与案例资料 以下内容按原文页序整理，便于按关键词查找功能、案例和实施信息。 PDF 第 1 页 企业网盘及文件协同管理系统 PDF 第 2 页 巴别鸟 公司介绍 BabelBird PDF 第 3 页 巴别鸟 公司概述 BabelBird 优质客户： 部分资质： 巴别鸟是上海画擎信息科技有限公司的注册商标及 主要产品，上海画擎成立于2012年，总部位于上 海，2016年于北京设立分公司。画擎科技是一个 以技术为主导的团队，创始人均来自北大方正，拥 有极强的图形图像处理和云计算技术并专注于安全 存储及办公协作系统的研发。目前，巴别鸟已经完 成了B轮融资，用户数超过80万，文档数据量已突 破30PB。 图形图像和云计算领域的孜孜耕耘，高效工作方式 的不懈探索，以及对产品用户体验的极致追求，造 就了巴别鸟文档管理及协作平台。你可以用巴别鸟 解决 企业文件统一管理、协同协作、数据安全 三 大问题，大幅提高企业工作效率及数据安全性。 PDF 第 4 页 巴别鸟 产品介绍 BabelBird PDF 第 5 页 我们解决什么问题 文档混乱管理难 邮件工作效率低 来回讨论耗时长 文件异地编辑难 根据组织结构及成员权限统一管理 在所有设备版本一致。与伙伴同步 打开大多数格式文件，在文件内容 巴别鸟可以直接编辑在线文件 文件，全文搜索快速查找 共享文件，协同工作 上直接建立批注实时讨论 从office到CAD。高效完成协作 无权限不安全 OA审批太死板 档案管理成本高 系统培训费人工 角色、行为、部门、文件的权限 可按业务需求自定义各种审批流程 内置知识管理及档案管理模块 简单使用不改变使用习惯，可内嵌 都可自定义。更可分部门管理 并导出报表，支持手写签名 满足专业的档案存储及借阅管理 于windows资源管理器直接访问 PDF 第 6 页 为什选择我们？ 1.安全 公有云SAAS结构，支持私有化部署，分块加密技术 2.易用、高效、强大 海量文档统一管理能力、强大权限、一个平台集成所需功能 3.专业 10年+扎实技术后盾、一流企业级服务、快速迭代更新 PDF 第 7 页 我们的特点 l 企业海量文件统一存储 l 文件协作管理所需的所有模块 l 最新的技术栈——更高速度和性能 l 强大的安全及权限管理 l AI技术的应用及落地 l 数据安全及数据备份 巴别鸟iOS版（iPhone、iPad），巴别鸟安卓版，巴别鸟web版，巴别鸟微信版，巴别鸟mac同步端，巴别鸟windows同步端 l 全平台 l 支持信创 PDF 第 8 页 主要功能 • 企业文件统一管理，自动同步 • 企业专属AI助理、AI标签、AI知识库 • 在线预览大多数文件格式 • 可控的分享、协作、批注讨论 • 在线编辑office文件、批注讨论图片及PDF • 在线笔记、思维导图、流程图 • 按组织结构分级管理，强大权限管理体系 • 项目文件夹、动态、工作台等常用工具 • 全文搜索、高级搜索、标签、筛选 • 独立的档案库及备份机制 • 军用级安全 PDF 第 9 页 巴别鸟 智巢AI BabelBird PDF 第 10 页 巴别鸟 智巢AI BabelBird 让AI真正服务于你的企业 • 企业专属AI助理、AI客服 • AI搜索及基于对话的复合查询 • AI自动打标签文件分类 • 可自定义的AI知识库（智能体） • AI搜图（图搜图、文搜图） • AI OCR • AI文档阅读助理 • 支持excel文件的AI数据助理 PDF 第 11 页 巴别鸟 智巢AI 智搜AI搜索 BabelBird 学习企业的所有文档，按用户权限回答问题 • 精确的权限判断 • 可以以追问的形式深入回答问题 • 支持识别图片中的文字 • 回答都给出信息来源，便于找到对应文件 • 支持多模态 PDF 第 12 页 巴别鸟 智巢AI 智搜AI搜图 BabelBird 搜索你存储在网盘中的所有图片 • 通过文字描述搜索到相关图片 • 上传图片搜索相似的图片 • 按权限判断搜索范围 PDF 第 13 页 巴别鸟 智巢AI 智能数据助理 BabelBird 利用AI进行数据分析及数据查询 • 支持多个excel文件交叉分析 • 支持以URL的形式访问第三方数据源 • AI可自动编程进行数据查询及分析 • 可根据查询数据AI自编程生成图表 • 多语言 PDF 第 14 页 巴别鸟 智巢AI 智体 BabelBird 自定义智能体 打造专属AI客服及知识库 • 自定义智能体的人设及回复逻辑(prompt) • 可指定智能体学习的目标文件夹 • 支持以URL的形式访问第三方数据源 • 客服、知识库、分析师、作家…. 等多种行业预设模版 • 支持多Agent • 可生成嵌入代码，在第三方网站中使用 PDF 第 15 页 巴别鸟 智巢AI 助理 BabelBird • 以对话的形式集成多数智巢应用 • 使用对话完成交互 • 回答企业所有文档中涉及到的知识点 • 对话形式多维度查找网盘文件 • 多模态 PDF 第 16 页 巴别鸟 智巢AI 按需开发 BabelBird 专业团队打造符合企业使用场景及流 程的定制AI • 定制开发专属智能体 • 按企业需求开发AI应用 • 支持私有化部署 • 使用最前沿的技术栈 PDF 第 17 页 巴别鸟 功能介绍 BabelBird PDF 第 18 页 巴别鸟 服务也是功能的一部分 BabelBird • 根据客户实际情况制定最适合客户的方案 • 服务期内无限大版本免费升级 • 合理功能建议免费二开支持 • 专属客户经理 • 7 24小时远程技术支持 • 30分钟内应急响应 • 无限次远程培训 PDF 第 19 页 巴别鸟 文件管理 BabelBird • 个人文件、企业文件、归档文件分区管理 • 可基于组织结构分层管理（部门） • 细致的权限管理 • 项目文件夹 • 断点续传及增量上传技术 • 文件版本管理 • 多级回收站 • 收件箱 • 专用的素材库 • 提醒及关注文件 • 批处理文件 PDF 第 20 页 巴别鸟 高级搜索 BabelBird • 搜索文件内容（全文搜索） • 标签管理及标签搜索 • 高级搜索（多条件复合搜索） • 搜索结果可筛选 • 图片元数据搜索 • 文件说明搜索 • 文件列表筛选 • AI智能搜索（直接回答问题) PDF 第 21 页 巴别鸟 分享及协作 BabelBird Finished • 功能强大的链接分享 • 带身份验证的邀请分享 • 分享可选权限自定义 • 快照分享 • 分享文件审批级批注讨论 • 快速发送文件 • 项目分享 • 分享文件可统一管理 • 可按部门、加密等级开启/关闭分享 • 分享文件批注讨论、评论 • 分享日志及统计 PDF 第 22 页 巴别鸟 在线预览、编辑协同 BabelBird • 100+文件格式支持在线预览 • CAD、3D等专业文件格式在线预览 • 音视频文件在线播放 • 在线文件内容批注讨论（可实时） • 文件版本对比 • Office、WPS格式文件的在线编辑、协同编辑 • MD、思维导图、流程图 在线编辑 PDF 第 23 页 巴别鸟 同步及虚拟磁盘 BabelBird • 同步任意文件夹不改变本地路径 BabelBird • 同步方式切换（双向、仅上传、仅下载） • 同步文件夹中文件编辑时自动锁定防止冲突 • 设定自动同步时间 • 同步文件类型黑名单 • 和onedriver一样的虚拟映射盘 • Win和mac都支持 PDF 第 24 页 巴别鸟 AI知识库 BabelBird • 自定义智能体作为知识库及在线客服 • 不同类型的知识库可以用不同智能体（知识助理） • AI可学习指定范围的文档（无需人力整理撰写知识库文档） • 权限管理，可控制智能体使用范围 • 可内嵌于第三方网页中使用 PDF 第 25 页 巴别鸟 工作台及动态 BabelBird • 工作台卡片管理 • 工作台图表 • 可自定义的工作台栏目 • 动态栏目 • @用户功能 • 动态搜索 PDF 第 26 页 巴别鸟 工作流 BabelBird • 文件定稿审批 • 可自定义的审批流程 • 多阶段评审 • 审批支持文件流转 • 支持批注、手绘、评审完成插入签名 • 支持企业外成员参与审批 • 生成评审报告 • 文控模块 PDF 第 27 页 巴别鸟 管理 BabelBird • 强大的企业控制台 • 统计及分析 • 日志和报表 • Mac地址绑定及IP策略 • 部门管理及成员管理 • 自定义角色及自定义权限管理 • 大量可自定义选项 • 多语言 PDF 第 28 页 巴别鸟 安全 BabelBird • 文件密级 • 分块加密存储技术 • 部门安全策略 • 水印 • 哈希验证 • 在线杀毒 • 文件保险箱 • 服务器容灾(高可用） • 多级回收站 • 分布式数据库 • 详细日志及报表 • 分布式对象存储系统 PDF 第 29 页 巴别鸟 权限体系 BabelBird 由管理员及拥有部门文件管理权限的人设置 管理员后台管理 由拥有部门管理权限的人管理 部门角色 部门管理 自定义可选角色权限 部门成员对部门文件的基础权限 不同成员可以不同角色 自定义文件可选权限列表 由管理员/项目负责人/部门文件管理者 设置 文件访问控制 部门空间分配 项目或部门文件权限管理者精确控制 文件/文件夹的访问授权 部门权限及密级 由项目负责人/文件分享者 设置 组织结构及成员 分享/项目权限 加入项目和分享的成员权限 其他功能选项 权限优先级：文件访问控制 角色（基础权限） PDF 第 30 页 巴别鸟 扩展 BabelBird • 开放API • AD同步、SSO单点登录 • 对接OA、ERP、企业微信、钉钉、飞书…等系统 • 支持第三方应用接入 PDF 第 31 页 巴别鸟 案例集 BabelBird PDF 第 32 页 巴别鸟 成功案例 航空航天 BabelBird 中国空间技术研究院 中国空间技术研究院（中国航天科技集团公司五院）成立于 1968年2月20日，隶属中国航天科技集团公司，是中国主要的 空间技术及其产品研制基地，中国空间事业的骨干力量。 用户需求 • 安全合规的文件管理 • 多个地区的实验室资料统一管理 • 在线办公及高效协作 • 和钉钉打通，使用钉钉用户体系 • 纯私有化内网部署，通过VPN访问 ” 解决方案 钉钉+巴别鸟 是我们第一次尝试使用新的互 • 多个安全策略保证文件存储安全合规 联网产品来解决内部的沟通协作及文件统一 • 多层备份保证文件万无一失 管理问题。大幅提高了我们的协作效率及可 • 对接钉钉，使用钉钉用户体系及组织结构 • 自动同步保证各实验室数据统一 管理性。目前从我们实验室到整个中国空间 • 支持在线office文件实时协作 都开始使用巴别鸟产品。 中国空间 钱学森实验室 高主任 PDF 第 33 页 巴别鸟 行业案例 政府机构 BabelBird 国家体育总局体育彩票管理中心 体彩中心是隶属于国家体育总局的体育彩票管理机构。负责制定、 建立、管理、发行、销售等和体育彩票相关的主要事务。是全国 体育彩票运营的主管机构。 用户需求 • 数据安全要求合规 • 能在企业微信中分享源文件 • 可直接预览大多数文件 • 下载文件可输出为PDF文件并带水印 • 可通过API实现二开，对接其他系统 解决方案 ” • 强大的权限及文件密级设置 • 企业微信集成，可以在工作台中开启巴别鸟 能满足我们要求的网盘类产品并不 • 企业微信第三方APP集成，让第三方应用可读取巴 多，巴别鸟功能全面，在企业微信 别鸟中的数据 • 支持预览大多数所需文件 对接和安全性方面相当契合我们的 • 文件下载生成带水印的PDF，保证外发文件安全 需求 • 提供完善的API接口，并根据需要定制部分接口 体彩中心 韩经理 PDF 第 34 页 巴别鸟 行业案例 大型工程 BabelBird 中石油寰球胜科工程公司 寰球胜科工程公司（寰球胜科）是中国寰球工程公司与胜科海事工 程公司于2007年联合成立的合资公司，在新加坡商业注册局正式注 册，是中国寰球工程公司(HQCEC)的控股子公司。寰球胜科是一家 海上陆上一体化的石油化工工程设计及施工服务工程公司。 用户需求 • 对工程所需的文件精细化控制 • 分权限管理不同部门及不同成员 • 和项目发包方、外包方、业主间的所有文档发送接收做 到统一管理。 • 发送文件附带符合工程管理需求传送单及单号 • 统一管理所有发送接收记录，统一归档 ” 解决方案 我们和巴别鸟团队一起设计了适用于工程行 • 部署在华为云上，满足全球访问需求 业的文控管理系统，把复杂的文控管理流程 • 在标准版基础上和甲方一起设计产品原型 自动化，使以文控为核心的工程管理方法得 • 开发文控项目模块，引入文控所需的工作流 以落地，同时大幅简化了我们的工作。 • 不断迭代以满足用户需求 • 开发MDR管理系统自动生成MDR表单 HQSM文控部门 慕蓉总 PDF 第 35 页 巴别鸟 成功案例 医院 BabelBird 中日友好医院 中日友好医院（简称“中日医院”）是国家卫生健康委员会直 属大型综合性三级甲等医院，于1984年10月23日开院。时任中 共中央总书记胡耀邦同志、时任全国政协主席邓颖超同志分别 题写院名。 用户需求 • 安全合规的文件管理 • 医院非结构化数据统一管理 • 节约日益增长的存储空间 • 医生及教职工文件传输及存储 • 在线办公及高效协作 • 纯私有化内网部署 ” 解决方案 • 多个安全策略保证文件存储安全合规 经过多轮产品筛选后我们最终选择了巴别鸟 • 提供定制API接入医院其他系统作为数据存储核心 作为我们数据存储核心，细致的服务和功能 • 文件去重存储及数据迁移服务 全面的产品是我们做出选择的原因。 • 可管理容量的个人空间分配 • 利用闲置服务器构建分布式存储系统 中日友好医院 夏主任 PDF 第 36 页 巴别鸟 行业案例 建筑及制造 BabelBird 中冶京诚 由走过50多年光辉历程的中冶集团北京钢铁设计研究总院改制 用户需求 设立的股权多元化的大型国际化创新型工程技术公司。先后为 国内外500余家客户提供了近5000项工程技术服务。在历年国 家建设部、勘察设计协会等年度排名中，均位居前列，2007年、 • 公司拥有大量全球项目，项目管理混乱 2008年连续2年位列百强之首。 • 图文信息中心需要对整个公司的文件进行归档 • 各项目组组成复杂，大量上下游文件沟通需求，自有云存 储无法满足需求 解决方案 • 公有云部署，并且优化海外带宽，保证所需访问地 区的网络速度 • 引入不同于部门管理的项目管理机制，项目文件夹 ” 可组合、转交、指定外部参与者 • 强大的权限定制可以针对人、文件、组合、部门组 我选择巴别鸟的原因是他们家的权限管 合出各种访问策略，保证安全性的前提下提高效率 • 匿名上传、外部用户手机验证快速访问、邀请等机 理是最强大的，能满足下面项目团队各 制让外部团队也能可控的加入项目进行协作 种奇葩需求。 中冶京诚 何小姐 PDF 第 37 页 巴别鸟 成功案例 建筑行业 BabelBird MCC Singapore 中冶集团新加坡分公司 我们是中冶集团在新加坡的分公司，成立于2010年，一直积极参与新加 坡的房地产领域，并取得了良好的成绩。它已经开发了五个开发项目， 用户需求 共同开发了两个开发项目，并管理了五个开发项目。该公司连续三年被 评为新加坡十大房地产开发商，并获得了“亚洲最佳影响力品牌”奖。 • 内部协作办公 • 各分支机构统一管理文件，海量数据存储 • Revit中心文件云端共享协作 • 对文件权限的高粒度细节管理 • 文件的安全管控，防止外泄 • 英文版本要求 ” 解决方案 • 私有化，高冗余部署，使用独立存储 • 对Revit中心文件同步方式进行优化 我们试用了相。当多的企业网l盘类产品，巴别 • 不同部门使用不同的密级 鸟支持Revit后基本就是最好用的云平台了 • SSO单点登录，导入组织结构 • 在线office模块 MCC Singapore 苏先生 PDF 第 38 页 巴别鸟 行业案例 文创行业 BabelBird 泡泡玛特 北京泡泡玛特文化创意有限公司成立于2010年，是中国领先的潮流 文化娱乐公司 发展近十年来，围绕全球艺术家挖掘、IP孵化运营、 消费者触达、潮玩文化推广、关联产业投资整合五个领域POP MART 泡泡玛特旨在用“创造潮流，传递美好”的品牌文化构建了 用户需求 覆盖潮流玩具全产业链的综合运营平台 • 图稿批注讨论定稿 • 3D设计稿协同交流 • 合作设计师共享及管理 • 对外约稿管理 • 对接飞书 • 文档审批管理 • 大量数据灾备 解决方案 • 使用私有云巴别鸟+对象存储 保证大量数据存储 • 二次开发定制素材库，统一管理素材 • 使用同步功能，设计师图稿快速同步 • 使用3D预览批注讨论 • 对接飞书 • 使用巴别鸟进行定稿审批 PDF 第 39 页 巴别鸟 行业案例 文创行业案例分析 BabelBird 存储备份方案 泡泡玛特的重要数据都保存在巴别鸟上，所以系统的 灾备能力是一个重要的考量。要求在现有系统持续运 行过程中保证数据实时备份，并且当存储服务器损坏 后能快速切换到备用服务器。 解决方案 • 增加一台对象存储用于实时备份 • 新增的存储服务器和主存储互为主从，数据同时写入两台存储。 • 主存储服务器损坏可自动切换到从存储服务器 • 服务器恢复后可自动修复并同步数据 • 低成本实现了数据的备份+系统高可用 PDF 第 40 页 巴别鸟 行业案例 文创行业案例分析 BabelBird 素材库（资料库）开发方案 在使用了一段时间巴别鸟企业网盘后，泡泡玛特因业务需要提出了适合他们大量产品图片、素材安全有序管理的需 求。和巴别鸟团队合作推出了更适合他们生产管理流程中使用的素材库。 需求分析 解决方案 • 重要素材（如产品图片）防止内部泄漏 • 根据用户需求设计产品方案，和用户细致讨 • 可以按分类、素材库的维度来管理每一类产品 论，设计出产品原型。 • 支持公开、使用需要审批、内部绝密 三种不同 • 二次开发推出素材库模块，按分类 /子素材 类型素材库 库的模式来管理。 • 特定的素材库子库能设定加密有效期。过了有 • 素材库有独立的权限及管理选项。 效期会弹出审批请求，通过后自动公开 • 开发相应的接口，帮助用户完成数据迁移。 • 不同的成员可以按产品线组织对素材库的访问 权限。能对多个素材库进行有效管理 • 数据迁移需求 目前素材库已经在公有云版本上线，所有企业用户都可以使用。 PDF 第 41 页 巴别鸟 行业案例 文创行业 BabelBird 混知文化 混知是国内“知识娱乐化”的先锋创始者，致力于“娱乐化、 图像化、脉络化思维讲知识”代表作《混子曰》 《半小时漫画 》 用户需求 • 图稿统一管理共享空间 • 图稿批注讨论定稿 • 素材管理 • 办公文档管理 解决方案 • 使用公有云巴别鸟，能上网即能访问 • 使用同步功能，设计师图稿快速同步 • 直接可以开启PSD、AI、CAD等设计文件 • 批注讨论图稿内容，异地远程快速沟通 • 瀑布流快虚寻找素材 PDF 第 42 页 巴别鸟 行业案例 动漫游戏行业 BabelBird 叠纸游戏 叠纸游戏成立于2013年8月，是一家专注于互动娱乐领域的新型互联 网文化公司。公司以移动端女性向手游起步，当前拥有暖暖系列及恋 爱系列这两条主要产品线，并于2020年成立叠纸动画聚集顶尖动画电 用户需求 影艺术家团队的力量，打造原创3D动画电影。 • 和外包处理团队传输大批量文件 • 海量素材文件的管理 • 动画工程文件协作 • 3D模型在线预览 • 大文件及大批量小文件传输 • 私有化部署 解决方案 • 私有部署对象存储集群 • 优化大文件及海量小文件的传输及同步 • 优化大深度文件夹的文件同步 • 优化超高数量级的文件统一归档 • 素材管理，瀑布流预览 PDF 第 43 页 巴别鸟 行业案例 动漫游戏行业 BabelBird 吉比特 叠纸厦门吉比特网络技术股份有限公司是一家专业从事网络游戏创意 策划、研发制作及商业化运营的国家重点软件企业。公司已成功研发 或运营了《问道》《问道手游》《不思议迷宫》《地下城堡2：黑暗觉 醒（安卓版）》《异化之地》《奇葩战斗家》《贪婪洞窟2》《伊洛纳》 用户需求 《失落城堡》《魔渊之刃》 等多款游戏。 • 海量素材文件的管理 • 企业内大量文件统一管理 • 存储系统安全性要求 • 对接自研系统 • 大文件及大批量小文件传输 • 私有化部署 解决方案 • 私有部署对接吉比特自有对象存储 • 根据安全部门的要求优化安全设置 • 帮助完成数据迁移 • 按客户要求优化素材管理 PDF 第 44 页 巴别鸟 行业案例 动漫游戏行业 BabelBird 西山居 金山西山居创建于1995年初夏，是国内最早的游戏工作室。在美丽的海 滨小城珠海，一群西山居居士们十年如一日兢兢业业的奋斗。20年间， 西山居凭借其雄厚的研发实力，对游戏文化内涵、画面、音乐等方面的 用户需求 深刻理解，秉承一贯的精品风格 • 海量素材文件的管理 • 在家和团队协同工作 • 3D模型在线预览 • 各地工作室文件统一管理归档 • 项目文件统一管理及共享 • 大文件及大批量小文件传输 • 部署在金山云上 ” 解决方案 • 在金山云上进行私有化部署 • 优化大文件及海量小文件的传输及同步 巴别鸟功能方。面相当全面，l并且也支持部 • 优化超高数量级的文件统一归档 署在金山云上，能很好的满足我们需求 • 素材管理，瀑布流预览 • 在线office协同编辑模块 西山居 HANAKO PDF 第 45 页 巴别鸟 行业案例 直播平台 BabelBird 企鹅体育 腾讯旗下的体育直播平台 用户需求 • 市场部素材及品牌文件分发 • 大量视频文件存储及调用 • 产品及设计稿件沟通 • 和乙方共享资料及设计稿 • 前方记者的视频及稿件能够快速发回总部审核 解决方案 ” • 公有云部署，提高视频流量支持 使用巴别鸟工作已经成为我们团队的 • 支持开启MP4，AVI等视频文件，并提供视屏转码服务 • 可在线开启PSD、AI稿件，方便和设计沟通 日常，文件直接编辑，直接保存到云 • 稿件及视频材料快速审核系统支持 端，部门协作效率高很多 • 分享链接可以直接通过微信发送并打开，增强沟通效率 企鹅体育 市场经理 kitty PDF 第 46 页 巴别鸟 行业案例 教育行业 BabelBird SIA国际艺术学校 SIA国际艺术留学于2011年在纽约曼哈顿成立，2012年SIA正式进 军中国市场。SIA国际艺术留学在基于中西方艺术文化交流合作的 前提下，为国内广大学员提供接触、了解西方艺术教育的平台 用户需求 • 100多家分支机构的统一管理共享空间 • 新教案，教学资料的快速分发 • 最新的教学资料可以统一版本给各个教师 • 直接可以查看并评阅学生的设计稿件 解决方案 • 使用公有云巴别鸟，能上网即能访问 ” • 部门功能使每个分支机构都有自己可管理的独立空 作为一个有100多家分支机构的培训 间 • 版本管理使所有分支机构都使用统一更新的最新教 机构，巴别鸟帮助我们把散落在20多 学资料 个城市的分公司统一管理起来，保证 • 总公司可以了解各个分公司的文件管理情况并管理 课件能够版本统一，实时更新。 各个分公司的知识产权 • 直接可以开启PSD、AI、CAD等设计文件，便于教 师寻找文件并和学生沟通设计 SIA国际艺术学校 Aaron PDF 第 47 页 巴别鸟 行业案例 教育行业 BabelBird 上海市徐汇区爱菊小学 上海市徐汇区爱菊小学是全国“双有”先进集体、上海市中小学行 为规范示范校、上海市安全文明校园、上海市艺术教育工作先进单 用户需求 位、上海市少先队雏鹰大队、上海市华侨捐赠管理先进单位。 • 学校党政宣传资料统一管理 • 教师送印课件审批及管理 • 历年教学资料、音视频资料建档管理 • 教师所需的网络存储空间 • 商汤系统对接 解决方案 • 在商汤服务器上完成私有化部署 • 为学校开发了文件审批流转功能 • 每个老师分配私人文件空间 • 使用素材库、档案库管理学校大量多媒体材料 • 按年级/教研组为单位管理课件及教学报告 PDF 第 48 页 巴别鸟 行业案例 教育行业 BabelBird 河北农业大学 光绪二十八年（1902年）由直隶总督袁 世凯奏请慈禧太后恩准创立直隶农务学堂（河北农大前身）， 初建在保定霍家大院（现保定建华大街二道桥北），是中国成 立最早的高等农业院校之一，河北省建立最早的高等院校。 用户需求 • 分散在各处的教学资料，教案统一管理 • 低成本完成知识管理及查询系统 • 论文无纸化，在线答辩批改，论文管理 • 收发作业及师生材料共享及备份 • 对接教务系统，统一账号 解决方案 ” • 建立私有化的河北农大知识管理系统，对旧数据进 使用巴别鸟大幅提升了我们对教研材料 行数据迁移统一管理，新数据利用同步客户端无感 及学生论文的管理效率。低成本的完成 同步，不改变教师使用习惯 • 使用共享标签，全文搜索，档案管理模块创建知识 了我们非结构化数据上云管理的阶段目 库，并有序展现 标。 希望以后能和巴别鸟团队有更深入 • 在线开启论文并在线批注建立论文答辩系统 • 使用收件箱功能分发和收取学生作业并管理 的合作 • 打通教务系统，深度整合 河北农业大学 教学研究部 尹老师 PDF 第 49 页 巴别鸟 行业案例 医疗设备 BabelBird 佳能医疗系统（中国）有限公司 1997年3月，佳能（中国）有限公司成立，全面负责佳能在中 国市场销售的各项工作。经过多年努力，目前已经基本建成6大 区域总部。佳能（中国）将深深植根于中国市场，致力于成为 一家被中国人民信赖、尊敬的企业。 用户需求 • 全国各地分部能统一管理文件 • 分权限管理不同部门及不同成员 • 快速传送大文件，外发文件统一管理 • 部门内管理扁平化，跨部门协作可控制 • 销售及市场部门的项目信息强制同步 • 支持预览医学成像图片 ” 解决方案 • 公有云服务保证全国各地的访问速度 巴别鸟的权限管理功能非常强大，能很好的 • 权限管理的初始化建议及解决方案提供 满足我们多部门多地办公过程中的苛刻的权 • 组织机构同步及部门搭建 限管理要求。提高效率及文件共享安全性。 • 涉密部门MAC地址绑定 • 分享链接统一管理 • DICOM格式文件预览支持 佳能医疗科研部 朱亚新 PDF 第 50 页 巴别鸟 行业案例 金融行业 BabelBird 朗玛峰资本 国内领先的VC机构 用户需求 • 大量尽调材料的管理归档查询 • 大量合同文书的统一管理 • 投后材料的管理及定时汇总 • 投资经理资料收集及协同讨论 • 投资合同签订前的多方讨论 ” 巴别鸟让我们的文件管理变得高效 有序，版本管理功能大幅降低了管 解决方案 理法律文书的工作量。 • 公有云部署，高存储空间方案 • 档案库功能，归档管理历史文档 • 定时收件箱获取投后材料 朗玛峰 法务 尉迟 • 用项目文件夹管理被投企业 • 协同批注在统一版本上讨论合同细节 其他金融行业客户： PDF 第 51 页 巴别鸟 行业案例 制造业 BabelBird 西子洁能集团（原杭锅集团） 杭州锅炉集团股份有限公司（以下简称公司）是一家主要从事 锅炉、压力容器、环保设备等产品集研发、生产、销售、安装 及其它工程服务于一体的大型综合企业集团，上市公司。 用户需求 • 不可以从服务器硬盘上获取完整文件信息 • 对接OA及CRM，并可以独立管理文件 • 为其他系统提供文件预览服务 • 文件版本管理及回滚 • 某些部门只能在特定的电脑上使用巴别鸟 • 在线办公及高效协作 ” 解决方案 我们使用巴别鸟来作为整个集团的统一存储， • 单点登录支持 并对接OA和CRM系统，同时巴别鸟支持 • 私有化部署，文件分块加密存储 。l SSO且可独立管理。在相对低的成本上解决 • 通过完善的API对接OA及CRM系统 • Mac地址绑定限定使用电脑 了数据统一管理问题。 • 版本管理 • 支持DWG文件的在线批注，协同讨论 杭锅集团 CIO 张斌 PDF 第 52 页 巴别鸟 行业案例 建筑行业 BabelBird 卯丁科技 深圳卯丁科技时一家服务于建筑行业的SAAS 服务提供商，为建筑设计到施工提供一系列的软件服务。卯 丁通过和巴别鸟的白牌合作得以快速推出卯丁云为其行业客 户提供服务。 用户需求 • 通过接口获得巴别鸟的全部功能，服务于卯丁客户 • 界面支持iframe帮助开发快速调用 • 单点登录及支持域控对接，和卯丁用户体系打通 • 部署于卯丁控制的阿里云服务器上，并提供开发测试 环境和技术支持 ” 解决方案 “我们花了 1整年时间寻找能满足 • 在提供标准API的基础上为客户定制API接口，满足 和客户系统的无缝对接 我们要求的系统，最终巴别鸟私有 • 提供一系列组件供客户直接调用简化二次开发流程 化系统的API定制开发解决了我们 • 在阿里云上帮助用户部署可扩展的私有化系统 的问题。相见恨晚” • 提供白牌授权服务 卯丁科技—许经理 PDF 第 53 页 巴别鸟 行业案例 房地产 BabelBird 龙湖地产 龙湖集团1993年创建于重庆，发展于全国，业务涵盖地产开发、商业运 营、租赁住房、智慧服务、房屋租售、房屋装修六大主航道业务，并积 用户需求 极试水养老、产城等创新领域。 • 内部协作办公 • 各分支机构统一管理文件，海量数据存储 • 需要同步本地文件夹到云端 • 需要在映射盘中可以同步 • 结合现有的存储系统 ” 解决方案 巴别鸟的同步盘和映射盘特别契合我们的 • 私有化并根据用户需求二开客户端 。l • 对接现有存储系统的API 需求，同时他们提供了灵活的对接方式可以 • 实现在映射盘中建立同步文件夹功能 高效快速的嵌入我们现有系统。 • SSO单点登录 龙湖地产 程卓 PDF 第 54 页 巴别鸟 行业案例 新能源汽车 BabelBird 长城华冠 长城华冠是中国专业的汽车整车设计研发机构， 成立于2003年8月，新三板上市。2018年，长城华冠推出了自 有汽车品牌前途汽车 用户需求 • 能直接在Catia及CAD稿件上进行设计评审 • 无纸化办公，节约大量A0级图纸的打印工作 • 改版知识库弥补原有知识库的不足 • 对3D点图等三维总成图形进行讨论 解决方案 ” • 使用巴别鸟建立评审流程，用巴别鸟直接开启Catia 及CAD图纸并可以在打开的图纸上绘制讨论 我们单一供应商选择了巴别鸟。因 • 为高效评审增加的GB焊接符号插入系统，可快速按 为只有他们能够让我们的工程师快 国标标记图纸，增加评审效率 • 版本管理使所有图纸的各个版本都具有备份统一保 速审图，大幅提高效率的同时节约 存 大量印刷成本 • 知识库数据迁移到巴别鸟，利用巴别鸟的搜索引擎 及档案管理重建知识管理系统 • 直接开启转化为SLI文件的点图进行讨论 长城华冠 姚经理 PDF 第 55 页 巴别鸟 行业案例 大型连锁 BabelBird 无限极（中国）有限公司 无限极(中国)有限公司﹝简称“无限极(中国)”﹞是李锦记健康 产品集团旗下成员,成立于1992年,是一家从事健康产品研发、 生产、销售及服务的现代化大型企业。 用户需求 • 文件存储安全及系统长时间稳定使用 • 统一管理各个地区及部门的文件 • 为员工提供网盘及存储服务 • 协同办公及内部文件共享 • 对接单点登录及数据中台同步组织结构 • 对接企业微信 ” 解决方案 巴别鸟为无限极的员工提供了安全、好用、 • 私有化，高冗余部署 。l 高效的文件管理及协同平台。并且能和我们 • 员工占用存储空间分配 的ADFS及数据中台完美结合并无缝嵌入到 • 企业微信对接 • 杀毒软件对接 我们的企业微信中。 • 在线office模块 无限极 员工平台负责人 杨建业 PDF 第 56 页 巴别鸟 行业案例 生物制药 BabelBird 泛生子 泛生子（纳斯达克代码：GTH）是全球前沿的癌症精准医疗公司， 专注癌症基因组学的研究和应用，提供癌症早期筛查、用药指导、 预后监测、肿瘤新药研发服务等覆盖癌症全周期的产品与服务， 致力于将创新基因组学技术，应用于与癌症相关的诊断、治疗， 最终战胜癌症 用户需求 • 数据安全要求合规 • 对接已有对象存储和AD域控 • 保证研发部门的文件安全 • 下载文件可输出为PDF文件并带水印 • 可通过API实现二开，对接其他系统 ” 解决方案 • 强大的权限及文件密级设置 巴别鸟能很好的对接我们的对象存 • 通过S3接口对接对象存储 储系统，并且可以使用 API对接我 • 研发部门使用安全策略配置为绝密部门 们的业务系统。关键是他们提供了 • 文件下载生成带水印的PDF，保证外发文件安全 • 提供完善的API接口，并根据需要定制部分接口 相当棒的后期支持服务。 泛生子 杨经理 PDF 第 57 页 巴别鸟 案例分析 BabelBird 至纯科技 成立于2000年，是一家在上交所上市的高新 技术企业，证券代码603690.SH。公司坐落于上海紫竹这个 国家级科学园区内，注册资本2.08亿元，致力于为高端先进 制造业企业提供高纯工艺系统的解决方案。 ” 立项了一年多时间，我们最终选择了 巴别鸟，除了产品优秀外，他们的定 制化开发服务解决了我的后顾之忧。 至纯科技 iT经理 庄稼 PDF 第 58 页 巴别鸟 至纯科技文件共享及安全管理解决方案 BabelBird 异地办公共享文件 研发部门强安全管理 外发文件防泄漏 至纯科技总部在上海，生产工厂在江苏启东，在台湾和日本有研 研发部门作为核心部门，对安全要求最为强烈。但又要处理好 防止外发的可编辑文件被恶意泄露 发中心。客户需求多个办公地的文件需要像在同一个系统里一样 工作协作的效率问题 共享并协作，需要保证访问速度和安全性。系统使用人数为 1. 安装绿盾文件加密系统 3000人，采用私有云部署方式。 1. 研发部门的所有账号都使用mac地址绑定到相应成员的工 作电脑。使用其他设备无法登录。 2. 所有可编辑及下载权限的文件在下载时自动绿 多个方案比较后，至纯科技选择了超融合系统方案，在总部上 盾加密为绿盾外发文件 2. 研发部关闭文件分享功能，所有文件默认密级为高 海机房部署超融合系统，同时在江苏启东工厂部署一套镜像服 3. 外发文件按分享时设定的有效期设定绿盾外发 务器。公司内部用户通过VPN连接内网巴别鸟服务器。开启一 3. 研发部使用客户端编辑在线的设计文件，本地不留存文件， 文件有效期，到达有效期文件自动删除 个限制权限的外网服务器供外网访问。同步域控服务器导入组 关机即清空本地缓存。 织结构按部门单位进行文件共享。 4. 研发部所有跨部门文件分享都需要申请临时权限 4. 绿盾外发文件可以做到防copy，防另存，可编 辑 内部权限分级管理 上下游客户及供应商文件共享 至纯科技项目总述 每个部门对权限控制的要求不同，并且至纯拥有多家分公司和 销售需要自由分享文件，售后有很多临时项目组和上下游对接 事业部，管理员维护工作量大，需要能统一管理又能适当放权。 巴别鸟团队在和至纯的合作中，在各个细节处为至 巴别鸟团队和业务部门及职能多次会议沟通后，帮助至纯科技 1. 销售部门开启链接分享，但链接分享需要部门管理员授权 纯文件共享及安全管理中定制和调整了大量功能， IT部门初始化了巴别鸟系统。解决方案如下： 同意 并在产品使用及安全的角度给至纯科技提供了大量 1. 按涉密程度不同把部门分为三类。不涉密的部门部门管理 2. 使用“项目文件夹”进行项目管理，项目文件夹可以邀请 解决方案及现场培训，帮助至纯快速完成了私有化 员权限下放，部门经理不用登录后台在前台即可管理部门， 外界用户，并且有独立的权限管理，便于项目管理者自由 系统搭建及初始化工作。最终，至纯科技巴别鸟私 添加部门成员，管理部门角色，建立子部门。轻度涉密部 调整权限。项目文件夹可以根据项目阶段进行转交并最终 有化系统能较为完美的满足至纯科技各方面的需求， 门部门经理仅可管理部门文件权限。重度涉密部门由系统 存档 并且预留了如“档案管理”，“图纸审批”，“工 管理员进行所有管理。 作台”等扩展功能。至纯提出的“文件快速发送”， 3. 除项目文件夹外，所有对外分享权限限定为“仅批注”外 “部门管理员前台操作”等功能也应用在巴别鸟公 2. 设为不允许用户拥有个人空间，用户所有文件都自动同步 界用户仅可查看预览文件并批注。 有云平台上，为更多的客户提供便捷。巴别鸟团队 到部门空间。统一管理。 4. 所有对外分享文件都设定“查看者水印”水印为查看该文 也因杰出的产品及服务获得了至纯科技“优秀供应 3. 除部门经理，所有部门成员角色都设为“仅可查看其它人 件的用户的用户ID 商” 文件”当需要下载和编辑非自己创建的文件时需要临时申 请权限。 4. 跨部门文件分享统统限制为仅可使用邀请，并且需要部门 经理授权。分享必须设定有效期。 PDF 第 59 页 巴别鸟 至纯科技研发团队图纸管理及协作巴别鸟解决方案 BabelBird 实现方法 项目要求 至纯科技的设计稿件一般是CAD及SOLIDWORKS文件，这些文件只能使用本地应用程序进行编辑，很难有效管理副本不被copy丢失。至纯 科技上市后，对知识产权及设计稿安全管理的需求相当迫切，急需解决。首先想到的解决方案是使用桌面虚拟化来解决，工程师登录虚拟桌 面进行图纸编辑。但设计类软件对设备性能要求极高，要做到设计师满意的使用体验投入极大，并且，至纯科技除了总部外还有多个生产及 研发基地，如果使用桌面虚拟化在各个地区都需要安装强大的服务器并解决互联互通问题。最终，经过大量调研他们决定使用巴别鸟。可以 1. 设计文件的安全管理（不可带出公司） 充分利用现有硬件资源最大限度的解决文件安全问题。 2. 团队协同设计共享图纸 设计稿安全管理中主要使用的巴别鸟功能 3. 图纸下发至生产环节及合作伙伴 1. Mac地址绑定：通过mac地址绑定功能使工程师只能在特定的设备上访问巴别鸟。没有绑定mac的设备无法登录并获取文件。使用此功能 后可以保证工程师只有在研发部的设备上才能查看图纸。如果需要在其他远程设备上访问图纸需要管理员授权。 2. 客户端、映射盘（云桥）：工程师安装客户端后使用云桥可以在windows资源管理器中直接访问权限范围内可访问的文件，无需同步就可 以直接进行编辑修改。编辑后自动上传至云端保存。配合本地计算机U盘端口封禁及每次关机自动清除缓存的设置，可以确保设计文件保 存于云端而本地无副本。（映射盘可以不用下载访问文件，但是文件打开时会下载缓存文件，缓存文件严格意义上有被找出并copy的嫌疑， 所以需要配合禁用U盘端口及关机自动清除缓存设置来确保文件安全。） 3. 分享审批：研发部门关闭文件分享功能（安全保密员身份登录企业后台，在组织结构部门管理里把部门文件安全策略设为“一级保密”）， 所有需要分享的文件需要上级审批通过后才能分享。 4. 多级管理员：防止iT部门管理员权限过大访问研发部门文件内容造成文件泄露，iT部门仅使用“运维管理员”权限，无法查看研发部门文 件。研发部门文件管理由部门负责人（部门经理）管理。 5. 文件及文件夹权限可追加：对于一些密级要求更高的文件，巴别鸟除了控制人的权限（角色），部门的权限外，还可以进行每个文件或文 件夹的访问控制。在部门的文件（文件夹）上点击右键打开文件访问控制，就可以控制每个部门成员对这个文件（文件夹）的访问权限。 同一个部门的共享文件也可以做到部门中有的人能看有的人不可见。 6. 可以查看但不能下载图纸：没有编辑文件必要的用户都不给予编辑权限，但能在巴别鸟上打开图纸查看并讨论。如果需要也可开启水印。 7. 所有行为日志可查：对系统的所有访问及文件的操作都有日志可以查询，文件有文件日志，系统有系统日志，可导出报表 8. 文件碎片化存储：即使服务器系统被入侵后也不能获得文件信息。每个文件被打散成若干碎片进行存储 PDF 第 60 页 巴别鸟 至纯科技研发团队图纸管理及协作巴别鸟解决方案 BabelBird 实现方法 团队协同设计共享图纸中主要使用的巴别鸟功能 项目要求 1. 直接预览CAD并批注讨论：上海总部程师和启东设备生产工厂可使用巴别鸟在CAD图纸上批注直接沟通细节问题。在客户施工现场，施工 人员也可以用手机直接开启图纸讨论，并支持语音、绘制、图片等多种方式进行批注讨论。 1. 设计文件的安全管理（不可带出公司） 2. 客户端、映射盘（云桥）：可以直接使用客户端打开云端的文件进行编辑或直接使用资源管理器中的映射盘像正常访问本地磁盘一样打开 2. 团队协同设计共享图纸 编辑设计稿。 3. 图纸下发至生产环节及合作伙伴 3. 文件锁定及冲突管理：正在编辑的文件自动锁定，防止多方修改带来的冲突问题。偶尔因同步时间造成的冲突问题会弹出冲突界面。 4. 版本管理：无限保存的版本，随时可以回退版本。 5. 同步文件夹：针对一些文件需要多个关联文件才能启动的要求保留了同步文件夹功能，可以设定任意文件夹同步至云端也可以设定云端的 任意文件夹同步到本地。同步同时可以作为文件上传的快速手段。 6. 移动端同步及第三方应用打开：对于复杂度较高的SOLIDWORKS文件，施工现场也可以使用第三方应用打开的方式调用其他应用打开图 纸进行更多操作。安卓手机支持在手机上用第三方应用编辑后自动上传新版本。 7. 增量上传：只上传文件修改新增部分的数据，大幅节约上传时间及流量。 8. 更新提示：文件更新后（编辑，建立批注，讨论），文件相关人员的APP可以收到推送更新通知，网页版动态及邮箱也能看到通知。 9. 关联文件：相互有关系的文件可以建立关联关系，便于统一查找一系列文件（未解决多张图纸关联问题）。 10.快捷方式：不同文件夹需要引用同一个文件可以使用快捷方式，源更改了快捷方式的内容也跟随源进行更改。 11.快速发送文件：电脑本地的文件可以右键快速发送给相关同事。代替用邮件及微信来传送文件。 12.所有者模式：研发部门要求由所有者管理自己的稿件（owner），在所有者模式上，只有owner才有文件编辑权限，多人协同时通过移交 owner来进行文件的管控。巴别鸟在权限设置里支持两种模式的切换。 13.建立项目：能以项目文件夹的形式管理每个项目的稿件，项目支持独立管理，可转交，研发部门完成后可以直接整个项目转交工厂。 PDF 第 61 页 巴别鸟 私有化部署流程 BabelBird 确认需求 出部署方案 签署合同 甲方支付预付款 甲方按要求准备服务器 上门或远程部署（3 5工作日） 单点登录对接（1工作日） 测试及调优（1 2工作日） 企业管理员培训 初始化服务（配置权限部门及安全策略） 使用部门及员工培训 试运行 用户答疑及配置调整 系统验收 甲方支付尾款 上海画擎信息科技有限公司 www.babel.cc" }, { "lang": "zh", "slug": "reference-service-terms", "title": "服务条款", "description": "巴别鸟服务条款文档参考内容。", "category": "源资料参考", "top_category": "维护", "keywords": [ "服务条款", "法律", "参考资料" ], "url": "zh/reference-service-terms.html", "source": "content/zh/reference-service-terms.md", "summary": "服务条款 服务条款 服务说明 上海画擎信息科技有限公司通过以下几种方式向企业客户提供服务： 域名为bable.cc的网站; 为客户私有部署于客户机房或客户管理的云空间内的巴别鸟私有化系统; 上海画擎信息科技有限公司已经发布的名为“巴别鸟”的桌面客户端程序; 上海画擎信息科技有限公司已经发布的名为“巴别鸟”的智能移动应用程序（包括但不限于iOS，Android系统）。 巴别鸟服务条款（以下简称“服务条款”）适用于巴别鸟中提供的所有应用程序，但当甲方使用巴别鸟某一特定服务时，如该服务另有单独的服务条款、指引或规则，应成为本条款的附加条款，甲方应与本条款一并遵守。 巴别鸟以及功能的正常实现以甲方正确履行管理行为，正确完成系统设置等为前提条件。如甲方违反有关法律法规及本服务条款的规定，须自行承担完全的法律责任、并承担因此给上海画擎信息科技有限公司造成的损失的法律责任。 巴别鸟免费服务（基于SaaS） 在了解并同意本条款的基础上，甲方可以申请注册巴别鸟账户使用巴别鸟免费服务。巴别鸟免费服务内容包括免费版基本功能、限期体验功能等，详情内容以巴别鸟网站公示为准。 甲方了解并同意在注册巴别鸟时，提供真实有效的企业信息（如联系人、联系电话，电子邮箱地址等）。上海画擎信息科技有限公司有权停止提供虚假注册信息用户的巴别鸟免费服务使用权限。 甲方清楚并同意甲方及甲方用户在注册使用巴别鸟免费服务前必须同时无条件接受本服务条款所有条款项的约束，并对违反国家法律规定及本服务条款所产生的一切后果承担法律责任。 巴别鸟企业公有云版服务（基于SaaS） 开通企业公有云版服务。甲方购买巴别鸟企业公有云版时，可联系相", "headings": [ { "level": 1, "title": "服务条款", "id": "section" } ], "images": [], "text": "服务条款 服务条款 服务说明 上海画擎信息科技有限公司通过以下几种方式向企业客户提供服务： 域名为bable.cc的网站; 为客户私有部署于客户机房或客户管理的云空间内的巴别鸟私有化系统; 上海画擎信息科技有限公司已经发布的名为“巴别鸟”的桌面客户端程序; 上海画擎信息科技有限公司已经发布的名为“巴别鸟”的智能移动应用程序（包括但不限于iOS，Android系统）。 巴别鸟服务条款（以下简称“服务条款”）适用于巴别鸟中提供的所有应用程序，但当甲方使用巴别鸟某一特定服务时，如该服务另有单独的服务条款、指引或规则，应成为本条款的附加条款，甲方应与本条款一并遵守。 巴别鸟以及功能的正常实现以甲方正确履行管理行为，正确完成系统设置等为前提条件。如甲方违反有关法律法规及本服务条款的规定，须自行承担完全的法律责任、并承担因此给上海画擎信息科技有限公司造成的损失的法律责任。 巴别鸟免费服务（基于SaaS） 在了解并同意本条款的基础上，甲方可以申请注册巴别鸟账户使用巴别鸟免费服务。巴别鸟免费服务内容包括免费版基本功能、限期体验功能等，详情内容以巴别鸟网站公示为准。 甲方了解并同意在注册巴别鸟时，提供真实有效的企业信息（如联系人、联系电话，电子邮箱地址等）。上海画擎信息科技有限公司有权停止提供虚假注册信息用户的巴别鸟免费服务使用权限。 甲方清楚并同意甲方及甲方用户在注册使用巴别鸟免费服务前必须同时无条件接受本服务条款所有条款项的约束，并对违反国家法律规定及本服务条款所产生的一切后果承担法律责任。 巴别鸟企业公有云版服务（基于SaaS） 开通企业公有云版服务。甲方购买巴别鸟企业公有云版时，可联系相关客服并完成付款，支付成功后甲方所购买的巴别鸟企业公有云版即会及时开通。 企业公有云版服务时限。企业公有云本服务时限是甲方购买巴别鸟企业公有云版服务时选择的“购买时长”为准，单位为“年”。 企业公有云版服务升级。上海画擎信息科技有限公司升级巴别鸟企业公有云版服务时，甲方所使用的公有云版将会自动升级，无需支付其他费用。 企业公有云版服务续费。甲方以公有云的方式所购买的巴别鸟企业公有云版服务时限到期前1个月，上海画擎信息科技有限公司将通知甲方续缴费用，续费价格以上海画擎信息科技有限公司官方公布为准。如甲方在企业公有云版服务时限期满后仍未续费，上海画擎信息科技有限公司即停止对甲方提供已到期部分的企业公有云版服务。 企业公有云版服务终止。甲方在其购买的巴别鸟企业公有云版服务到期后仍未续费，则视为甲方自动放弃巴别鸟企业公有云版服务，甲方已到期企业公有云版服务即被限制或锁定。 巴别鸟订单合同。甲方在购买巴别鸟企业公有云版服务后，可与上海画擎信息有限公司签订[巴别鸟企业版（公有云）软件使用许可协议]。[巴别鸟企业版（公有云）软件使用许可协议]是上海画擎信息有限公司与甲方之间关于巴别鸟服务与费用的书面协定。 巴别鸟企业私有化服务 上海画擎信息科技有限公司仅提供巴别鸟部署及巴别鸟私有化授权服务。部署所需的硬件及环境由甲方准备及维护。 部署企业私有云版本。甲方购买巴别鸟企业私有云版本后，由上海画擎信息科技根据甲方签订合同时所选的项目（详见协议附件 服务订单）进行部署及相关调试。 企业私有云版服务时限。企业私有云版本的账号授权时限为终生授权，客服支持及升级服务按年为单位。购买后第一年免维护费用。 企业私有云版服务升级。上海画擎信息科技有限公司升级巴别鸟企业私有云版服务时，会第一时间通知甲方，由甲方决定是否升级，如甲方同意升级即进行远程升级服务，无需支付其他费用。 企业私有云版维护费。巴别鸟企业私有云版本为终生授权，但如果需要上海画擎信息科技有限公司提供相应的培训、答疑、及系统bug修正、系统升级服务则需支付维护费用。购买企业私有云版本后的第一年免维护费，第二年开始甲方需要按合同约定支付相应的维护费用。如逾期甲方没有支付维护费用，将视为甲方放弃本服务条款的所有服务。 巴别鸟订单合同。甲方在购买巴别鸟企业私有云版服务后，可与上海画擎信息有限公司签订[巴别鸟私有云软件使用许可协议]。[巴别鸟私有云软件使用许可协议]是上海画擎信息有限公司与甲方之间关于巴别鸟服务与费用的书面协定。 甲方权利和义务 甲方必须自行配备连通互联网和使用电信企业公有云版业务所需的设备，自行担负个人上网或第三方（包括但不限于电信或移动通信提供商）收取的通讯费、信息费、流量费等有关费用。如涉及电信企业公有云版服务的，我们建议您与您的电信企业公有云版服务提供商确认相关的费用问题。 甲方不得利用巴别鸟发送或传输任何妨碍社会治安或非法、虚假、骚扰性、侮辱性、恐吓性、伤害性、破坏性、挑衅性、淫秽色情等内容的信息。 甲方须自行负责对其系统内部成员用户进行管理，如：增加（删减）账号、设置用户密码等管理行为。甲方须指派专门的系统管理员对其巴别鸟账号进行维护管理，甲方管理员的行为由甲方负责，管理行为的后果以及责任由甲方承担。 甲方及其甲方用户应维持自身账号及密码的机密安全，甲方及其甲方用户不得将其账号或密码转让或出借第三方使用。上海画擎信息科技有限公司无法对第三方非法或未经甲方授权使用其账号及密码的行为做出甄别，因此上海画擎信息科技有限公司不承担任何责任。在此，甲方同意并承诺做到： 当甲方及甲方用户的账号及密码遭到未获授权的使用，或者发生其他任何安全问题时，甲方立即通知上海画擎信息科技有限公司。 甲方及甲方用户每次使用巴别鸟系统完毕后，点击退出巴别鸟。 甲方已清楚明白，巴别鸟仅可作为甲方内部使用，除非另有协议，甲方不得将其甲方账号进行转让、分销、或者买卖。 上海画擎信息科技有限公司权利和义务 上海画擎信息科技有限公司有义务为甲方提供巴别鸟的管理权限，便于甲方自行为甲方用户进行系统相关设置。 上海画擎信息科技有限公司不得公开、编辑或对外披露甲方及甲方用户存储在巴别鸟的任何数据。但下列情况除外 事先得到甲方书面明确授权； 根据中华人民共和国国家安全机构、公安部门的要求或根据相关的法律程序或维护社会公共利益的要求。 如甲方或甲方用户违反本服务条款的约定或法律规定，上海画擎信息科技有限公司有权中断或终止巴别鸟服务并且剩余服务费用不进行退还。 上海画擎信息科技有限公司有权根据实际情况调整或更新本服务条款内容，上海画擎信息科技有限公司有义务通知甲方并在巴别鸟官方网页或巴别鸟系统作出明显公示。修改后的条款一旦公布即有效代替原有条款，新条款适用于所有巴别鸟免费服务用户以及所有巴别鸟企业公有云版服务用户。 如甲方及甲方用户违反国家法律法规或本服务条款，上海画擎信息科技有限公司有权立即停止向甲方提供服务而不需承担任何责任。 知识产权、保密条款 巴别鸟的所有权和基于巴别鸟的所有知识产权（包括但不限于专利权、商标权、著作权、计算机软件著作权等）归上海画擎信息科技有限公司所有。上海画擎信息科技有限公司对巴别鸟的所有权不包括甲方及甲方用户存放在巴别鸟服务器中的数据。 上海画擎信息科技有限公司、上海画擎信息科技有限公司logo、巴别鸟的logo等，以及其他上海画擎信息科技有限公司标志及产品、服务名称、均为上海画擎信息科技有限公司之商标（以下简称“上海画擎信息科技有限公司标识”）。未经上海画擎信息科技有限公司事先书面同意，甲方不得将上海画擎信息科技有限公司标识以任何方式展示或使用或作其他处理，也不得向他人表明甲方有权展示、使用、或其他有权处理上海画擎信息科技有限公司标识的行为。 甲方有义务保护上海画擎信息科技有限公司的知识产权不受第三方侵犯。甲方及甲方用户不得使用、复制巴别鸟有关的软件、数据，不得允许第三方窃取巴别鸟的任何数据与软件。数据不包括甲方及甲方用户在巴别鸟服务器中存放的数据。 甲方和上海画擎信息科技有限公司任何一方对在合作过程中所获知的对方及上海画擎信息科技有限公司未向社会公开的技术及商业秘密均有保密的义务，未经对方书面许可，任何一方不得将其泄露给第三方，否则应承担违约责任并赔偿损失。 服务风险、免责声明 甲方已经清楚并明白，巴别鸟服务仅依其当前所呈现的状况提供，巴别鸟服务涉及到互联网及移动数据通讯等服务，可能会受到各个环节不稳定因素的影响。因此服务存在因上述不可抗力、洪水、地震、台风、火灾与其他天灾、战争、计算机病毒或黑客攻击、基于计算机系统和网络的各种犯罪行为、政府行为、系统出错或不稳定、用户所在位置、用户关机、GSM网络不稳定、3G网络不稳定、互联网络线路故障、骨干网通信线路故障原因等造成的服务中断或不能满足用户要求并因此给甲方带来损失的风险。甲方需承担上述风险，上海画擎信息科技有限公司不提供对巴别鸟适销性、适用性、可靠性、及时性、安全性、完整性、无病毒及无错误的任何明示或默认保证，不承担因此而对甲方造成的任何直接、间接、附带、衍生或惩罚性的赔偿。 如巴别鸟所发生的故障影响到甲方的正常使用，上海画擎信息科技有限公司承诺在第一时间内与相关单位配合，及时处理进行修复。上海画擎信息科技有限公司保留不经事前通知为维修保养、升级或其他目的暂停巴别鸟任何部分的权利。在此期间发生的服务暂停现象，或由于网络通路的偶然阻塞造成服务应用故障，属正常情况，不可视为上海画擎信息科技有限公司违约。 甲方同意，甲方与甲方用户经由巴别鸟以上传、张贴、发送即时消息、电子邮件或其他方式传送的资讯、资料、文字、软件、音乐、音频、照片、图片、视频、信息、资源链接、用户登记资料或其他资料（以下简称“内容”），均由甲方与甲方用户承担完全的法律责任，上海画擎信息科技有限公司无须承担任何直接、间接、或连带责任。由于上海画擎信息科技有限公司无法控制经由巴别鸟传送的内容，也无法对用户的使用行为进行全面监控，因此不保证甲方内容的合法性、正确性、完整性、真实性或品质。如甲方的内容存在侵犯第三人著作权的可能，上海画擎信息科技有限公司将遵循国家的法律法规进行处理。 甲方已经清楚地了解并知道，甲方用户如需使用巴别鸟必须接受本服务条款。在甲方部分或全部甲方用户不接受或不同意本服务条款而导致无法使用巴别鸟时，甲方仍同意向上海画擎信息科技有限公司支付服务费用。 甲方承诺因甲方、甲方系统管理员、甲方用户对巴别鸟的错误操作而对甲方所造成的任何损失负完全责任。这些错误操作包括但不限于甲方系统管理员误删了甲方用户所造成的数据丢失、甲方用户错误地删除了甲方企业网盘中的共享数据等。 甲方及甲方用户已经清楚地了解到，其通过巴别鸟与商家或个人进行任何形式的通讯或商业往来、或参与促销活动，包含相关商品或服务之付款及交付，以及达成的其他任何相关条款、条件、保证或证明，完全为甲方及甲方成员与商家及其他个人之间的行为。除有关法律有明文规定要求上海画擎信息科技有限公司承担责任以外，甲方因上述任何交易或上述商家或个人而遭受的任何性质的损失或损害，上海画擎信息科技有限公司均不予负责。 违约责任 甲方使用巴别鸟前须清楚了解并同意本服务条款，并对违反国家法律规定及本服务条款所产生的一切后果承担法律责任。 因上海画擎信息科技有限公司过失而造成甲方在使用巴别鸟过程中遭受损失的，甲方有权以书面形式通知上海画擎信息科技有限公司终止其巴别鸟账号。经上海画擎信息科技有限公司查证如甲方之情况属实，上海画擎信息科技有限公司会在10个工作日内按约收取服务起始日至服务终止日期间产生的费用后将甲方余款（如有）退还。 服务变更、中断或终止及服务条款修改 巴别鸟的所有权和运作权、一切解释权归上海画擎信息科技有限公司所有。上海画擎信息科技有限公司有权随时根据国家有关法律、法规的变化、行业的发展及公司经营状况和经营策略的调整等情况修改本条款。 上海画擎信息科技有限公司修改巴别鸟服务或本服务条款时，应根据本条款6.4项执行。甲方有义务对最新的服务条款进行仔细阅读并确认，当发生有关争议时，以最新的服务条款为准。 上海画擎信息科技有限公司保留对巴别鸟中所有应用程序的价格调整权及产品试用期的调整权。 如发生下列任何一种情况，上海画擎信息科技有限公司有权随时中断或终止向甲方提供服务或禁用某些甲方用户账号而无须通知甲方： 甲方违反本服务条款的规定； 按照国家主管部门的要求； 其他上海画擎信息科技有限公司认为是符合整体服务需求的特殊情形。 法律及争议解决 本服务条款要与国家相关法律、法规一致，如发生与相关法律、法规条款有相抵触的内容，抵触部分以法律、法规条款为准。 如双方发生任何争议但又不能友好协商的，任何一方均可向上海画擎信息科技有限公司住所地上海市有管辖权的人民法院提起诉讼。 巴别鸟提供的售后服务 巴别鸟采用一对一专人服务模式，有专门的客户经理负责为客户提供服务。 维护单位名称：上海画擎信息科技有限公司 软件维护期为一年，第二年后客户需缴纳维护费，进入下一轮软件维护期，如客户维护期满后不缴纳服务费，客户可以继续使用系统，但我司不再提供维护服务，直到补齐年服务费用后，服务继续。 维护期内上海画擎负责提供合同范围内软件版本的程序代码及系统配置信息的维护、支持，不包含因业务改变等因素所引起的新增功能开发。如中日友好医院需要新增功能及因业务流程变更带来的客户化开发服务，则由双方协商确定实施方案。 免费服务内容和范围 巴别鸟对所有付费客户提供产品使用周期中的终身免费质保服务，包括： 5 24小时的电话技术支持服务 7 24小时的紧急灾备处理服务 免费在线培训，系统使用指导 BUG第一时间反馈，快速处理 软件更新及升级服务 针对用户数量超过1000人的企业用户，巴别鸟提供了产品使用周期中的终身免费VIP服务，包括： 付费客户的所有免费服务 系统搭建及需求对应解决方案咨询服务 代客户初始化系统及完成配置 免费数据迁移服务（小于10TB的数据） 每年免费上门培训1次（用户数超过10000每年有三次免费上门培训机会） 专属大客户经理责任制服务 针对私有化用户，在用户正常缴纳年服务费的前提下，享受如下免费服务： 付费客户的所有免费服务 免费系统升级及更新服务，纯内网用户（内网无法连接到互联网）每年有1次免费上门升级及更新服务 代客户初始化系统及完成配置 服务器性能优化及排障 每年免费上门培训1次，无限次远程培训 针对基于巴别鸟系统的二次开发及功能定制用户，享受如下免费服务： 付费客户的所有免费服务 二次开发部分的功能质保，Bug修正 接口及功能联调服务 二次开发部分代码及接口的注释及指导服务，方便用户再开发 完工验收后，在我方成本可承受范围内的微调及功能修正（非Bug） 收费服务 在现有系统上的再开发工作，按需求评估开发工时及难度系数，按工时结算。 产品设计服务。根据客户新需求帮助客户进行产品架构、功能及交互的设计，并提供技术咨询。 有偿上门培训及调试服务。免费额度用完或不符合免费上门服务条件的用户可以付费申请。费用为 2000元1人1天 及报销到达用户处所的交通费用（高铁及当地出租车） 提供的服务项目包括如下： 序号 服务项目 服务内容 1 首访服务 由服务人员主动开展首次访问服务 2 回访服务 由服务人员主动开展回访的服务 3 软件常规运行维护服务 所购买软件的程序代码维护，如修补软件缺陷、安装调试软件补丁 4 系统升级技术咨询 当系统升级时提供的技术咨询服务 5 软件升级通知 当该版本软件升级时，及时通知客户 服务方式包括： 热线支持：通过400热线电话向客户提供技术问题解答； E MAIL支持：通过E MAIL解答客户问题； 远程维护：通过远程方式对客户环境下的巴别鸟软件进行调试。客户需提供远程维护所需的环境，否则，由客户承担因此而引起的售后响应时间滞后的责任。 现场服务：如属远程维护所不能解决的问题，我司会承担现场服务。属于应用软件自身问题带来的现场服务，属于免费维护范围。 故障处理流程 当客户使用中出现问题： 立即拨打专职客户经理电话（或微信联系），可以解决的立即解决； 不能立即解决的，立即联系技术人员对接，由技术人员远程协助客户解决； 仍然没有解决，反馈给客户经理，由客户经理安排技术人员上门服务。 其他 如本服务条款中的任何条款无论因何种原因完全或部分无效或不具有执行力，本服务条款的其余条款仍应有效且具有约束力，并且努力使该规定反映之意向具备效力。 本服务条款构成甲方与上海画擎信息科技有限公司之全部协议，规范您对本服务之使用，并取代您先前与上海画擎信息科技有限公司达成的全部协议。但在甲方使用相关服务、或使用第三方提供的内容或软件时，亦应遵从所适用之附加条款及权利。 上海画擎信息科技有限公司保留本服务条款之所有解释权。 甲方（盖章）： 乙方（盖章）： 甲方代表（签字）： 乙方代表（签字）： 日 期： 日 期：" }, { "lang": "zh", "slug": "reference-whitepaper-images", "title": "白皮书图片索引", "description": "从巴别鸟企业网盘白皮书抽取的全部嵌入图片，供配图、原文对照和 AI 视觉资料索引使用。", "category": "源资料参考", "top_category": "维护", "keywords": [ "白皮书", "图片", "截图", "配图" ], "url": "zh/reference-whitepaper-images.html", "source": "content/zh/reference-whitepaper-images.md", "summary": "白皮书图片索引 本页汇总《巴别鸟企业网盘白皮书》中的全部嵌入图片。 这些图片从源文档中按原始顺序抽取，保留为可直接访问的静态资源。页面主要用于原文对照、AI 视觉资料索引、后续人工挑选配图和搜索引擎发现。 项 数值 图片数量 129 来源文件 巴别鸟企业网盘白皮书.docx 白皮书图片索引图片 001 来源：巴别鸟企业网盘白皮书 / word/media/image1.png 静态路径： assets/images/whitepaper/whitepaper 001.png 白皮书图片索引图片 001 白皮书图片索引图片 001，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 002 来源：巴别鸟企业网盘白皮书 / word/media/image10.png 静态路径： assets/images/whitepaper/whitepaper 002.png 白皮书图片索引图片 002 白皮书图片索引图片 002，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 003 来源：巴别鸟企业网盘白皮书 / word/media/image100.png 静态路径： assets/images/whitepaper/whitepaper 003.png 白皮书图片索引图片 003 白皮书图片索引图片 003，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 004 来源：巴别鸟企业网盘白皮书 / word/media/image101.png 静态路径： assets/images/whitepaper/whitepaper 004.png", "headings": [ { "level": 1, "title": "白皮书图片索引", "id": "section" }, { "level": 2, "title": "白皮书图片索引图片 001", "id": "001" }, { "level": 2, "title": "白皮书图片索引图片 002", "id": "002" }, { "level": 2, "title": "白皮书图片索引图片 003", "id": "003" }, { "level": 2, "title": "白皮书图片索引图片 004", "id": "004" }, { "level": 2, "title": "白皮书图片索引图片 005", "id": "005" }, { "level": 2, "title": "白皮书图片索引图片 006", "id": "006" }, { "level": 2, "title": "白皮书图片索引图片 007", "id": "007" }, { "level": 2, "title": "白皮书图片索引图片 008", "id": "008" }, { "level": 2, "title": "白皮书图片索引图片 009", "id": "009" }, { "level": 2, "title": "白皮书图片索引图片 010", "id": "010" }, { "level": 2, "title": "白皮书图片索引图片 011", "id": "011" }, { "level": 2, "title": "白皮书图片索引图片 012", "id": "012" }, { "level": 2, "title": "白皮书图片索引图片 013", "id": "013" }, { "level": 2, "title": "白皮书图片索引图片 014", "id": "014" }, { "level": 2, "title": "白皮书图片索引图片 015", "id": "015" }, { "level": 2, "title": "白皮书图片索引图片 016", "id": "016" }, { "level": 2, "title": "白皮书图片索引图片 017", "id": "017" }, { "level": 2, "title": "白皮书图片索引图片 018", "id": "018" }, { "level": 2, "title": "白皮书图片索引图片 019", "id": "019" }, { "level": 2, "title": "白皮书图片索引图片 020", "id": "020" }, { "level": 2, "title": "白皮书图片索引图片 021", "id": "021" }, { "level": 2, "title": "白皮书图片索引图片 022", "id": "022" }, { "level": 2, "title": "白皮书图片索引图片 023", "id": "023" }, { "level": 2, "title": "白皮书图片索引图片 024", "id": "024" }, { "level": 2, "title": "白皮书图片索引图片 025", "id": "025" }, { "level": 2, "title": "白皮书图片索引图片 026", "id": "026" }, { "level": 2, "title": "白皮书图片索引图片 027", "id": "027" }, { "level": 2, "title": "白皮书图片索引图片 028", "id": "028" }, { "level": 2, "title": "白皮书图片索引图片 029", "id": "029" }, { "level": 2, "title": "白皮书图片索引图片 030", "id": "030" }, { "level": 2, "title": "白皮书图片索引图片 031", "id": "031" }, { "level": 2, "title": "白皮书图片索引图片 032", "id": "032" }, { "level": 2, "title": "白皮书图片索引图片 033", "id": "033" }, { "level": 2, "title": "白皮书图片索引图片 034", "id": "034" }, { "level": 2, "title": "白皮书图片索引图片 035", "id": "035" }, { "level": 2, "title": "白皮书图片索引图片 036", "id": "036" }, { "level": 2, "title": "白皮书图片索引图片 037", "id": "037" }, { "level": 2, "title": "白皮书图片索引图片 038", "id": "038" }, { "level": 2, "title": "白皮书图片索引图片 039", "id": "039" }, { "level": 2, "title": "白皮书图片索引图片 040", "id": "040" }, { "level": 2, "title": "白皮书图片索引图片 041", "id": "041" }, { "level": 2, "title": "白皮书图片索引图片 042", "id": "042" }, { "level": 2, "title": "白皮书图片索引图片 043", "id": "043" }, { "level": 2, "title": "白皮书图片索引图片 044", "id": "044" }, { "level": 2, "title": "白皮书图片索引图片 045", "id": "045" }, { "level": 2, "title": "白皮书图片索引图片 046", "id": "046" }, { "level": 2, "title": "白皮书图片索引图片 047", "id": "047" }, { "level": 2, "title": "白皮书图片索引图片 048", "id": "048" }, { "level": 2, "title": "白皮书图片索引图片 049", "id": "049" }, { "level": 2, "title": "白皮书图片索引图片 050", "id": "050" }, { "level": 2, "title": "白皮书图片索引图片 051", "id": "051" }, { "level": 2, "title": "白皮书图片索引图片 052", "id": "052" }, { "level": 2, "title": "白皮书图片索引图片 053", "id": "053" }, { "level": 2, "title": "白皮书图片索引图片 054", "id": "054" }, { "level": 2, "title": "白皮书图片索引图片 055", "id": "055" }, { "level": 2, "title": "白皮书图片索引图片 056", "id": "056" }, { "level": 2, "title": "白皮书图片索引图片 057", "id": "057" }, { "level": 2, "title": "白皮书图片索引图片 058", "id": "058" }, { "level": 2, "title": "白皮书图片索引图片 059", "id": "059" }, { "level": 2, "title": "白皮书图片索引图片 060", "id": "060" }, { "level": 2, "title": "白皮书图片索引图片 061", "id": "061" }, { "level": 2, "title": "白皮书图片索引图片 062", "id": "062" }, { "level": 2, "title": "白皮书图片索引图片 063", "id": "063" }, { "level": 2, "title": "白皮书图片索引图片 064", "id": "064" }, { "level": 2, "title": "白皮书图片索引图片 065", "id": "065" }, { "level": 2, "title": "白皮书图片索引图片 066", "id": "066" }, { "level": 2, "title": "白皮书图片索引图片 067", "id": "067" }, { "level": 2, "title": "白皮书图片索引图片 068", "id": "068" }, { "level": 2, "title": "白皮书图片索引图片 069", "id": "069" }, { "level": 2, "title": "白皮书图片索引图片 070", "id": "070" }, { "level": 2, "title": "白皮书图片索引图片 071", "id": "071" }, { "level": 2, "title": "白皮书图片索引图片 072", "id": "072" }, { "level": 2, "title": "白皮书图片索引图片 073", "id": "073" }, { "level": 2, "title": "白皮书图片索引图片 074", "id": "074" }, { "level": 2, "title": "白皮书图片索引图片 075", "id": "075" }, { "level": 2, "title": "白皮书图片索引图片 076", "id": "076" }, { "level": 2, "title": "白皮书图片索引图片 077", "id": "077" }, { "level": 2, "title": "白皮书图片索引图片 078", "id": "078" }, { "level": 2, "title": "白皮书图片索引图片 079", "id": "079" }, { "level": 2, "title": "白皮书图片索引图片 080", "id": "080" }, { "level": 2, "title": "白皮书图片索引图片 081", "id": "081" }, { "level": 2, "title": "白皮书图片索引图片 082", "id": "082" }, { "level": 2, "title": "白皮书图片索引图片 083", "id": "083" }, { "level": 2, "title": "白皮书图片索引图片 084", "id": "084" }, { "level": 2, "title": "白皮书图片索引图片 085", "id": "085" }, { "level": 2, "title": "白皮书图片索引图片 086", "id": "086" }, { "level": 2, "title": "白皮书图片索引图片 087", "id": "087" }, { "level": 2, "title": "白皮书图片索引图片 088", "id": "088" }, { "level": 2, "title": "白皮书图片索引图片 089", "id": "089" }, { "level": 2, "title": "白皮书图片索引图片 090", "id": "090" }, { "level": 2, "title": "白皮书图片索引图片 091", "id": "091" }, { "level": 2, "title": "白皮书图片索引图片 092", "id": "092" }, { "level": 2, "title": "白皮书图片索引图片 093", "id": "093" }, { "level": 2, "title": "白皮书图片索引图片 094", "id": "094" }, { "level": 2, "title": "白皮书图片索引图片 095", "id": "095" }, { "level": 2, "title": "白皮书图片索引图片 096", "id": "096" }, { "level": 2, "title": "白皮书图片索引图片 097", "id": "097" }, { "level": 2, "title": "白皮书图片索引图片 098", "id": "098" }, { "level": 2, "title": "白皮书图片索引图片 099", "id": "099" }, { "level": 2, "title": "白皮书图片索引图片 100", "id": "100" }, { "level": 2, "title": "白皮书图片索引图片 101", "id": "101" }, { "level": 2, "title": "白皮书图片索引图片 102", "id": "102" }, { "level": 2, "title": "白皮书图片索引图片 103", "id": "103" }, { "level": 2, "title": "白皮书图片索引图片 104", "id": "104" }, { "level": 2, "title": "白皮书图片索引图片 105", "id": "105" }, { "level": 2, "title": "白皮书图片索引图片 106", "id": "106" }, { "level": 2, "title": "白皮书图片索引图片 107", "id": "107" }, { "level": 2, "title": "白皮书图片索引图片 108", "id": "108" }, { "level": 2, "title": "白皮书图片索引图片 109", "id": "109" }, { "level": 2, "title": "白皮书图片索引图片 110", "id": "110" }, { "level": 2, "title": "白皮书图片索引图片 111", "id": "111" }, { "level": 2, "title": "白皮书图片索引图片 112", "id": "112" }, { "level": 2, "title": "白皮书图片索引图片 113", "id": "113" }, { "level": 2, "title": "白皮书图片索引图片 114", "id": "114" }, { "level": 2, "title": "白皮书图片索引图片 115", "id": "115" }, { "level": 2, "title": "白皮书图片索引图片 116", "id": "116" }, { "level": 2, "title": "白皮书图片索引图片 117", "id": "117" }, { "level": 2, "title": "白皮书图片索引图片 118", "id": "118" }, { "level": 2, "title": "白皮书图片索引图片 119", "id": "119" }, { "level": 2, "title": "白皮书图片索引图片 120", "id": "120" }, { "level": 2, "title": "白皮书图片索引图片 121", "id": "121" }, { "level": 2, "title": "白皮书图片索引图片 122", "id": "122" }, { "level": 2, "title": "白皮书图片索引图片 123", "id": "123" }, { "level": 2, "title": "白皮书图片索引图片 124", "id": "124" }, { "level": 2, "title": "白皮书图片索引图片 125", "id": "125" }, { "level": 2, "title": "白皮书图片索引图片 126", "id": "126" }, { "level": 2, "title": "白皮书图片索引图片 127", "id": "127" }, { "level": 2, "title": "白皮书图片索引图片 128", "id": "128" }, { "level": 2, "title": "白皮书图片索引图片 129", "id": "129" } ], "images": [ { "src": "../assets/images/whitepaper/whitepaper-001.png", "alt": "白皮书图片索引图片 001", "caption": "白皮书图片索引图片 001，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-002.png", "alt": "白皮书图片索引图片 002", "caption": "白皮书图片索引图片 002，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-003.png", "alt": "白皮书图片索引图片 003", "caption": "白皮书图片索引图片 003，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-004.png", "alt": "白皮书图片索引图片 004", "caption": "白皮书图片索引图片 004，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-005.png", "alt": "白皮书图片索引图片 005", "caption": "白皮书图片索引图片 005，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-006.png", "alt": "白皮书图片索引图片 006", "caption": "白皮书图片索引图片 006，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-007.png", "alt": "白皮书图片索引图片 007", "caption": "白皮书图片索引图片 007，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-008.png", "alt": "白皮书图片索引图片 008", "caption": "白皮书图片索引图片 008，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-009.png", "alt": "白皮书图片索引图片 009", "caption": "白皮书图片索引图片 009，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-010.png", "alt": "白皮书图片索引图片 010", "caption": "白皮书图片索引图片 010，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-011.png", "alt": "白皮书图片索引图片 011", "caption": "白皮书图片索引图片 011，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-012.png", "alt": "白皮书图片索引图片 012", "caption": "白皮书图片索引图片 012，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-013.png", "alt": "白皮书图片索引图片 013", "caption": "白皮书图片索引图片 013，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-014.png", "alt": "白皮书图片索引图片 014", "caption": "白皮书图片索引图片 014，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-015.png", "alt": "白皮书图片索引图片 015", "caption": "白皮书图片索引图片 015，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-016.png", "alt": "白皮书图片索引图片 016", "caption": "白皮书图片索引图片 016，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-017.png", "alt": "白皮书图片索引图片 017", "caption": "白皮书图片索引图片 017，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-018.svg", "alt": "白皮书图片索引图片 018", "caption": "白皮书图片索引图片 018，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-019.png", "alt": "白皮书图片索引图片 019", "caption": "白皮书图片索引图片 019，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-020.png", "alt": "白皮书图片索引图片 020", "caption": "白皮书图片索引图片 020，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-021.png", "alt": "白皮书图片索引图片 021", "caption": "白皮书图片索引图片 021，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-022.svg", "alt": "白皮书图片索引图片 022", "caption": "白皮书图片索引图片 022，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-023.png", "alt": "白皮书图片索引图片 023", "caption": "白皮书图片索引图片 023，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-024.png", "alt": "白皮书图片索引图片 024", "caption": "白皮书图片索引图片 024，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-025.png", "alt": "白皮书图片索引图片 025", "caption": "白皮书图片索引图片 025，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-026.png", "alt": "白皮书图片索引图片 026", "caption": "白皮书图片索引图片 026，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-027.png", "alt": "白皮书图片索引图片 027", "caption": "白皮书图片索引图片 027，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-028.png", "alt": "白皮书图片索引图片 028", "caption": "白皮书图片索引图片 028，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-029.png", "alt": "白皮书图片索引图片 029", "caption": "白皮书图片索引图片 029，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-030.png", "alt": "白皮书图片索引图片 030", "caption": "白皮书图片索引图片 030，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-031.png", "alt": "白皮书图片索引图片 031", "caption": "白皮书图片索引图片 031，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-032.png", "alt": "白皮书图片索引图片 032", "caption": "白皮书图片索引图片 032，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-033.png", "alt": "白皮书图片索引图片 033", "caption": "白皮书图片索引图片 033，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-034.png", "alt": "白皮书图片索引图片 034", "caption": "白皮书图片索引图片 034，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-035.png", "alt": "白皮书图片索引图片 035", "caption": "白皮书图片索引图片 035，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-036.png", "alt": "白皮书图片索引图片 036", "caption": "白皮书图片索引图片 036，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-037.png", "alt": "白皮书图片索引图片 037", "caption": "白皮书图片索引图片 037，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-038.png", "alt": "白皮书图片索引图片 038", "caption": "白皮书图片索引图片 038，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-039.png", "alt": "白皮书图片索引图片 039", "caption": "白皮书图片索引图片 039，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-040.png", "alt": "白皮书图片索引图片 040", "caption": "白皮书图片索引图片 040，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-041.png", "alt": "白皮书图片索引图片 041", "caption": "白皮书图片索引图片 041，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-042.png", "alt": "白皮书图片索引图片 042", "caption": "白皮书图片索引图片 042，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-043.png", "alt": "白皮书图片索引图片 043", "caption": "白皮书图片索引图片 043，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-044.png", "alt": "白皮书图片索引图片 044", "caption": "白皮书图片索引图片 044，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-045.png", "alt": "白皮书图片索引图片 045", "caption": "白皮书图片索引图片 045，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-046.png", "alt": "白皮书图片索引图片 046", "caption": "白皮书图片索引图片 046，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-047.png", "alt": "白皮书图片索引图片 047", "caption": "白皮书图片索引图片 047，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-048.png", "alt": "白皮书图片索引图片 048", "caption": "白皮书图片索引图片 048，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-049.jpeg", "alt": "白皮书图片索引图片 049", "caption": "白皮书图片索引图片 049，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-050.png", "alt": "白皮书图片索引图片 050", "caption": "白皮书图片索引图片 050，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-051.jpeg", "alt": "白皮书图片索引图片 051", "caption": "白皮书图片索引图片 051，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-052.png", "alt": "白皮书图片索引图片 052", "caption": "白皮书图片索引图片 052，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-053.png", "alt": "白皮书图片索引图片 053", "caption": "白皮书图片索引图片 053，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-054.png", "alt": "白皮书图片索引图片 054", "caption": "白皮书图片索引图片 054，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-055.png", "alt": "白皮书图片索引图片 055", "caption": "白皮书图片索引图片 055，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-056.png", "alt": "白皮书图片索引图片 056", "caption": "白皮书图片索引图片 056，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-057.png", "alt": "白皮书图片索引图片 057", "caption": "白皮书图片索引图片 057，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-058.jpeg", "alt": "白皮书图片索引图片 058", "caption": "白皮书图片索引图片 058，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-059.png", "alt": "白皮书图片索引图片 059", "caption": "白皮书图片索引图片 059，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-060.png", "alt": "白皮书图片索引图片 060", "caption": "白皮书图片索引图片 060，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-061.png", "alt": "白皮书图片索引图片 061", "caption": "白皮书图片索引图片 061，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-062.png", "alt": "白皮书图片索引图片 062", "caption": "白皮书图片索引图片 062，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-063.png", "alt": "白皮书图片索引图片 063", "caption": "白皮书图片索引图片 063，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-064.png", "alt": "白皮书图片索引图片 064", "caption": "白皮书图片索引图片 064，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-065.png", "alt": "白皮书图片索引图片 065", "caption": "白皮书图片索引图片 065，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-066.png", "alt": "白皮书图片索引图片 066", "caption": "白皮书图片索引图片 066，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-067.png", "alt": "白皮书图片索引图片 067", "caption": "白皮书图片索引图片 067，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-068.png", "alt": "白皮书图片索引图片 068", "caption": "白皮书图片索引图片 068，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-069.png", "alt": "白皮书图片索引图片 069", "caption": "白皮书图片索引图片 069，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-070.png", "alt": "白皮书图片索引图片 070", "caption": "白皮书图片索引图片 070，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-071.png", "alt": "白皮书图片索引图片 071", "caption": "白皮书图片索引图片 071，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-072.png", "alt": "白皮书图片索引图片 072", "caption": "白皮书图片索引图片 072，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-073.png", "alt": "白皮书图片索引图片 073", "caption": "白皮书图片索引图片 073，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-074.png", "alt": "白皮书图片索引图片 074", "caption": "白皮书图片索引图片 074，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-075.png", "alt": "白皮书图片索引图片 075", "caption": "白皮书图片索引图片 075，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-076.png", "alt": "白皮书图片索引图片 076", "caption": "白皮书图片索引图片 076，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-077.png", "alt": "白皮书图片索引图片 077", "caption": "白皮书图片索引图片 077，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-078.png", "alt": "白皮书图片索引图片 078", "caption": "白皮书图片索引图片 078，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-079.png", "alt": "白皮书图片索引图片 079", "caption": "白皮书图片索引图片 079，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-080.png", "alt": "白皮书图片索引图片 080", "caption": "白皮书图片索引图片 080，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-081.png", "alt": "白皮书图片索引图片 081", "caption": "白皮书图片索引图片 081，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-082.png", "alt": "白皮书图片索引图片 082", "caption": "白皮书图片索引图片 082，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-083.png", "alt": "白皮书图片索引图片 083", "caption": "白皮书图片索引图片 083，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-084.png", "alt": "白皮书图片索引图片 084", "caption": "白皮书图片索引图片 084，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-085.png", "alt": "白皮书图片索引图片 085", "caption": "白皮书图片索引图片 085，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-086.png", "alt": "白皮书图片索引图片 086", "caption": "白皮书图片索引图片 086，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-087.png", "alt": "白皮书图片索引图片 087", "caption": "白皮书图片索引图片 087，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-088.png", "alt": "白皮书图片索引图片 088", "caption": "白皮书图片索引图片 088，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-089.png", "alt": "白皮书图片索引图片 089", "caption": "白皮书图片索引图片 089，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-090.png", "alt": "白皮书图片索引图片 090", "caption": "白皮书图片索引图片 090，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-091.png", "alt": "白皮书图片索引图片 091", "caption": "白皮书图片索引图片 091，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-092.png", "alt": "白皮书图片索引图片 092", "caption": "白皮书图片索引图片 092，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-093.jpeg", "alt": "白皮书图片索引图片 093", "caption": "白皮书图片索引图片 093，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-094.png", "alt": "白皮书图片索引图片 094", "caption": "白皮书图片索引图片 094，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-095.png", "alt": "白皮书图片索引图片 095", "caption": "白皮书图片索引图片 095，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-096.png", "alt": "白皮书图片索引图片 096", "caption": "白皮书图片索引图片 096，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-097.png", "alt": "白皮书图片索引图片 097", "caption": "白皮书图片索引图片 097，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-098.png", "alt": "白皮书图片索引图片 098", "caption": "白皮书图片索引图片 098，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-099.png", "alt": "白皮书图片索引图片 099", "caption": "白皮书图片索引图片 099，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-100.png", "alt": "白皮书图片索引图片 100", "caption": "白皮书图片索引图片 100，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-101.png", "alt": "白皮书图片索引图片 101", "caption": "白皮书图片索引图片 101，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-102.png", "alt": "白皮书图片索引图片 102", "caption": "白皮书图片索引图片 102，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-103.png", "alt": "白皮书图片索引图片 103", "caption": "白皮书图片索引图片 103，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-104.jpeg", "alt": "白皮书图片索引图片 104", "caption": "白皮书图片索引图片 104，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-105.png", "alt": "白皮书图片索引图片 105", "caption": "白皮书图片索引图片 105，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-106.png", "alt": "白皮书图片索引图片 106", "caption": "白皮书图片索引图片 106，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-107.png", "alt": "白皮书图片索引图片 107", "caption": "白皮书图片索引图片 107，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-108.png", "alt": "白皮书图片索引图片 108", "caption": "白皮书图片索引图片 108，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-109.png", "alt": "白皮书图片索引图片 109", "caption": "白皮书图片索引图片 109，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-110.png", "alt": "白皮书图片索引图片 110", "caption": "白皮书图片索引图片 110，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-111.png", "alt": "白皮书图片索引图片 111", "caption": "白皮书图片索引图片 111，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-112.png", "alt": "白皮书图片索引图片 112", "caption": "白皮书图片索引图片 112，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-113.png", "alt": "白皮书图片索引图片 113", "caption": "白皮书图片索引图片 113，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-115.png", "alt": "白皮书图片索引图片 115", "caption": "白皮书图片索引图片 115，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-116.png", "alt": "白皮书图片索引图片 116", "caption": "白皮书图片索引图片 116，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-117.png", "alt": "白皮书图片索引图片 117", "caption": "白皮书图片索引图片 117，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-118.png", "alt": "白皮书图片索引图片 118", "caption": "白皮书图片索引图片 118，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-119.png", "alt": "白皮书图片索引图片 119", "caption": "白皮书图片索引图片 119，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-120.png", "alt": "白皮书图片索引图片 120", "caption": "白皮书图片索引图片 120，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-121.png", "alt": "白皮书图片索引图片 121", "caption": "白皮书图片索引图片 121，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-122.png", "alt": "白皮书图片索引图片 122", "caption": "白皮书图片索引图片 122，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-123.png", "alt": "白皮书图片索引图片 123", "caption": "白皮书图片索引图片 123，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-124.png", "alt": "白皮书图片索引图片 124", "caption": "白皮书图片索引图片 124，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-125.png", "alt": "白皮书图片索引图片 125", "caption": "白皮书图片索引图片 125，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-126.png", "alt": "白皮书图片索引图片 126", "caption": "白皮书图片索引图片 126，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-127.png", "alt": "白皮书图片索引图片 127", "caption": "白皮书图片索引图片 127，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-128.png", "alt": "白皮书图片索引图片 128", "caption": "白皮书图片索引图片 128，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "src": "../assets/images/whitepaper/whitepaper-129.png", "alt": "白皮书图片索引图片 129", "caption": "白皮书图片索引图片 129，从 巴别鸟企业网盘白皮书.docx 抽取。" } ], "text": "白皮书图片索引 本页汇总《巴别鸟企业网盘白皮书》中的全部嵌入图片。 这些图片从源文档中按原始顺序抽取，保留为可直接访问的静态资源。页面主要用于原文对照、AI 视觉资料索引、后续人工挑选配图和搜索引擎发现。 项 数值 图片数量 129 来源文件 巴别鸟企业网盘白皮书.docx 白皮书图片索引图片 001 来源：巴别鸟企业网盘白皮书 / word/media/image1.png 静态路径： assets/images/whitepaper/whitepaper 001.png 白皮书图片索引图片 001 白皮书图片索引图片 001，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 002 来源：巴别鸟企业网盘白皮书 / word/media/image10.png 静态路径： assets/images/whitepaper/whitepaper 002.png 白皮书图片索引图片 002 白皮书图片索引图片 002，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 003 来源：巴别鸟企业网盘白皮书 / word/media/image100.png 静态路径： assets/images/whitepaper/whitepaper 003.png 白皮书图片索引图片 003 白皮书图片索引图片 003，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 004 来源：巴别鸟企业网盘白皮书 / word/media/image101.png 静态路径： assets/images/whitepaper/whitepaper 004.png 白皮书图片索引图片 004 白皮书图片索引图片 004，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 005 来源：巴别鸟企业网盘白皮书 / word/media/image102.png 静态路径： assets/images/whitepaper/whitepaper 005.png 白皮书图片索引图片 005 白皮书图片索引图片 005，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 006 来源：巴别鸟企业网盘白皮书 / word/media/image103.png 静态路径： assets/images/whitepaper/whitepaper 006.png 白皮书图片索引图片 006 白皮书图片索引图片 006，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 007 来源：巴别鸟企业网盘白皮书 / word/media/image104.png 静态路径： assets/images/whitepaper/whitepaper 007.png 白皮书图片索引图片 007 白皮书图片索引图片 007，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 008 来源：巴别鸟企业网盘白皮书 / word/media/image105.png 静态路径： assets/images/whitepaper/whitepaper 008.png 白皮书图片索引图片 008 白皮书图片索引图片 008，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 009 来源：巴别鸟企业网盘白皮书 / word/media/image106.png 静态路径： assets/images/whitepaper/whitepaper 009.png 白皮书图片索引图片 009 白皮书图片索引图片 009，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 010 来源：巴别鸟企业网盘白皮书 / word/media/image107.png 静态路径： assets/images/whitepaper/whitepaper 010.png 白皮书图片索引图片 010 白皮书图片索引图片 010，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 011 来源：巴别鸟企业网盘白皮书 / word/media/image108.png 静态路径： assets/images/whitepaper/whitepaper 011.png 白皮书图片索引图片 011 白皮书图片索引图片 011，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 012 来源：巴别鸟企业网盘白皮书 / word/media/image109.png 静态路径： assets/images/whitepaper/whitepaper 012.png 白皮书图片索引图片 012 白皮书图片索引图片 012，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 013 来源：巴别鸟企业网盘白皮书 / word/media/image11.png 静态路径： assets/images/whitepaper/whitepaper 013.png 白皮书图片索引图片 013 白皮书图片索引图片 013，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 014 来源：巴别鸟企业网盘白皮书 / word/media/image110.png 静态路径： assets/images/whitepaper/whitepaper 014.png 白皮书图片索引图片 014 白皮书图片索引图片 014，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 015 来源：巴别鸟企业网盘白皮书 / word/media/image111.png 静态路径： assets/images/whitepaper/whitepaper 015.png 白皮书图片索引图片 015 白皮书图片索引图片 015，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 016 来源：巴别鸟企业网盘白皮书 / word/media/image112.png 静态路径： assets/images/whitepaper/whitepaper 016.png 白皮书图片索引图片 016 白皮书图片索引图片 016，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 017 来源：巴别鸟企业网盘白皮书 / word/media/image113.png 静态路径： assets/images/whitepaper/whitepaper 017.png 白皮书图片索引图片 017 白皮书图片索引图片 017，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 018 来源：巴别鸟企业网盘白皮书 / word/media/image114.svg 静态路径： assets/images/whitepaper/whitepaper 018.svg 白皮书图片索引图片 018 白皮书图片索引图片 018，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 019 来源：巴别鸟企业网盘白皮书 / word/media/image115.png 静态路径： assets/images/whitepaper/whitepaper 019.png 白皮书图片索引图片 019 白皮书图片索引图片 019，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 020 来源：巴别鸟企业网盘白皮书 / word/media/image116.png 静态路径： assets/images/whitepaper/whitepaper 020.png 白皮书图片索引图片 020 白皮书图片索引图片 020，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 021 来源：巴别鸟企业网盘白皮书 / word/media/image117.png 静态路径： assets/images/whitepaper/whitepaper 021.png 白皮书图片索引图片 021 白皮书图片索引图片 021，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 022 来源：巴别鸟企业网盘白皮书 / word/media/image118.svg 静态路径： assets/images/whitepaper/whitepaper 022.svg 白皮书图片索引图片 022 白皮书图片索引图片 022，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 023 来源：巴别鸟企业网盘白皮书 / word/media/image119.png 静态路径： assets/images/whitepaper/whitepaper 023.png 白皮书图片索引图片 023 白皮书图片索引图片 023，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 024 来源：巴别鸟企业网盘白皮书 / word/media/image12.png 静态路径： assets/images/whitepaper/whitepaper 024.png 白皮书图片索引图片 024 白皮书图片索引图片 024，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 025 来源：巴别鸟企业网盘白皮书 / word/media/image120.png 静态路径： assets/images/whitepaper/whitepaper 025.png 白皮书图片索引图片 025 白皮书图片索引图片 025，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 026 来源：巴别鸟企业网盘白皮书 / word/media/image121.png 静态路径： assets/images/whitepaper/whitepaper 026.png 白皮书图片索引图片 026 白皮书图片索引图片 026，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 027 来源：巴别鸟企业网盘白皮书 / word/media/image122.png 静态路径： assets/images/whitepaper/whitepaper 027.png 白皮书图片索引图片 027 白皮书图片索引图片 027，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 028 来源：巴别鸟企业网盘白皮书 / word/media/image123.png 静态路径： assets/images/whitepaper/whitepaper 028.png 白皮书图片索引图片 028 白皮书图片索引图片 028，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 029 来源：巴别鸟企业网盘白皮书 / word/media/image124.png 静态路径： assets/images/whitepaper/whitepaper 029.png 白皮书图片索引图片 029 白皮书图片索引图片 029，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 030 来源：巴别鸟企业网盘白皮书 / word/media/image125.png 静态路径： assets/images/whitepaper/whitepaper 030.png 白皮书图片索引图片 030 白皮书图片索引图片 030，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 031 来源：巴别鸟企业网盘白皮书 / word/media/image126.png 静态路径： assets/images/whitepaper/whitepaper 031.png 白皮书图片索引图片 031 白皮书图片索引图片 031，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 032 来源：巴别鸟企业网盘白皮书 / word/media/image127.png 静态路径： assets/images/whitepaper/whitepaper 032.png 白皮书图片索引图片 032 白皮书图片索引图片 032，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 033 来源：巴别鸟企业网盘白皮书 / word/media/image128.png 静态路径： assets/images/whitepaper/whitepaper 033.png 白皮书图片索引图片 033 白皮书图片索引图片 033，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 034 来源：巴别鸟企业网盘白皮书 / word/media/image129.png 静态路径： assets/images/whitepaper/whitepaper 034.png 白皮书图片索引图片 034 白皮书图片索引图片 034，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 035 来源：巴别鸟企业网盘白皮书 / word/media/image13.png 静态路径： assets/images/whitepaper/whitepaper 035.png 白皮书图片索引图片 035 白皮书图片索引图片 035，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 036 来源：巴别鸟企业网盘白皮书 / word/media/image14.png 静态路径： assets/images/whitepaper/whitepaper 036.png 白皮书图片索引图片 036 白皮书图片索引图片 036，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 037 来源：巴别鸟企业网盘白皮书 / word/media/image15.png 静态路径： assets/images/whitepaper/whitepaper 037.png 白皮书图片索引图片 037 白皮书图片索引图片 037，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 038 来源：巴别鸟企业网盘白皮书 / word/media/image16.png 静态路径： assets/images/whitepaper/whitepaper 038.png 白皮书图片索引图片 038 白皮书图片索引图片 038，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 039 来源：巴别鸟企业网盘白皮书 / word/media/image17.png 静态路径： assets/images/whitepaper/whitepaper 039.png 白皮书图片索引图片 039 白皮书图片索引图片 039，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 040 来源：巴别鸟企业网盘白皮书 / word/media/image18.png 静态路径： assets/images/whitepaper/whitepaper 040.png 白皮书图片索引图片 040 白皮书图片索引图片 040，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 041 来源：巴别鸟企业网盘白皮书 / word/media/image19.png 静态路径： assets/images/whitepaper/whitepaper 041.png 白皮书图片索引图片 041 白皮书图片索引图片 041，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 042 来源：巴别鸟企业网盘白皮书 / word/media/image2.png 静态路径： assets/images/whitepaper/whitepaper 042.png 白皮书图片索引图片 042 白皮书图片索引图片 042，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 043 来源：巴别鸟企业网盘白皮书 / word/media/image20.png 静态路径： assets/images/whitepaper/whitepaper 043.png 白皮书图片索引图片 043 白皮书图片索引图片 043，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 044 来源：巴别鸟企业网盘白皮书 / word/media/image21.png 静态路径： assets/images/whitepaper/whitepaper 044.png 白皮书图片索引图片 044 白皮书图片索引图片 044，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 045 来源：巴别鸟企业网盘白皮书 / word/media/image22.png 静态路径： assets/images/whitepaper/whitepaper 045.png 白皮书图片索引图片 045 白皮书图片索引图片 045，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 046 来源：巴别鸟企业网盘白皮书 / word/media/image23.png 静态路径： assets/images/whitepaper/whitepaper 046.png 白皮书图片索引图片 046 白皮书图片索引图片 046，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 047 来源：巴别鸟企业网盘白皮书 / word/media/image24.png 静态路径： assets/images/whitepaper/whitepaper 047.png 白皮书图片索引图片 047 白皮书图片索引图片 047，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 048 来源：巴别鸟企业网盘白皮书 / word/media/image25.png 静态路径： assets/images/whitepaper/whitepaper 048.png 白皮书图片索引图片 048 白皮书图片索引图片 048，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 049 来源：巴别鸟企业网盘白皮书 / word/media/image26.jpeg 静态路径： assets/images/whitepaper/whitepaper 049.jpeg 白皮书图片索引图片 049 白皮书图片索引图片 049，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 050 来源：巴别鸟企业网盘白皮书 / word/media/image27.png 静态路径： assets/images/whitepaper/whitepaper 050.png 白皮书图片索引图片 050 白皮书图片索引图片 050，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 051 来源：巴别鸟企业网盘白皮书 / word/media/image28.jpeg 静态路径： assets/images/whitepaper/whitepaper 051.jpeg 白皮书图片索引图片 051 白皮书图片索引图片 051，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 052 来源：巴别鸟企业网盘白皮书 / word/media/image29.png 静态路径： assets/images/whitepaper/whitepaper 052.png 白皮书图片索引图片 052 白皮书图片索引图片 052，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 053 来源：巴别鸟企业网盘白皮书 / word/media/image3.png 静态路径： assets/images/whitepaper/whitepaper 053.png 白皮书图片索引图片 053 白皮书图片索引图片 053，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 054 来源：巴别鸟企业网盘白皮书 / word/media/image30.png 静态路径： assets/images/whitepaper/whitepaper 054.png 白皮书图片索引图片 054 白皮书图片索引图片 054，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 055 来源：巴别鸟企业网盘白皮书 / word/media/image31.png 静态路径： assets/images/whitepaper/whitepaper 055.png 白皮书图片索引图片 055 白皮书图片索引图片 055，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 056 来源：巴别鸟企业网盘白皮书 / word/media/image32.png 静态路径： assets/images/whitepaper/whitepaper 056.png 白皮书图片索引图片 056 白皮书图片索引图片 056，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 057 来源：巴别鸟企业网盘白皮书 / word/media/image33.png 静态路径： assets/images/whitepaper/whitepaper 057.png 白皮书图片索引图片 057 白皮书图片索引图片 057，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 058 来源：巴别鸟企业网盘白皮书 / word/media/image34.jpeg 静态路径： assets/images/whitepaper/whitepaper 058.jpeg 白皮书图片索引图片 058 白皮书图片索引图片 058，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 059 来源：巴别鸟企业网盘白皮书 / word/media/image35.png 静态路径： assets/images/whitepaper/whitepaper 059.png 白皮书图片索引图片 059 白皮书图片索引图片 059，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 060 来源：巴别鸟企业网盘白皮书 / word/media/image36.png 静态路径： assets/images/whitepaper/whitepaper 060.png 白皮书图片索引图片 060 白皮书图片索引图片 060，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 061 来源：巴别鸟企业网盘白皮书 / word/media/image37.png 静态路径： assets/images/whitepaper/whitepaper 061.png 白皮书图片索引图片 061 白皮书图片索引图片 061，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 062 来源：巴别鸟企业网盘白皮书 / word/media/image38.png 静态路径： assets/images/whitepaper/whitepaper 062.png 白皮书图片索引图片 062 白皮书图片索引图片 062，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 063 来源：巴别鸟企业网盘白皮书 / word/media/image39.png 静态路径： assets/images/whitepaper/whitepaper 063.png 白皮书图片索引图片 063 白皮书图片索引图片 063，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 064 来源：巴别鸟企业网盘白皮书 / word/media/image4.png 静态路径： assets/images/whitepaper/whitepaper 064.png 白皮书图片索引图片 064 白皮书图片索引图片 064，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 065 来源：巴别鸟企业网盘白皮书 / word/media/image40.png 静态路径： assets/images/whitepaper/whitepaper 065.png 白皮书图片索引图片 065 白皮书图片索引图片 065，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 066 来源：巴别鸟企业网盘白皮书 / word/media/image41.png 静态路径： assets/images/whitepaper/whitepaper 066.png 白皮书图片索引图片 066 白皮书图片索引图片 066，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 067 来源：巴别鸟企业网盘白皮书 / word/media/image42.png 静态路径： assets/images/whitepaper/whitepaper 067.png 白皮书图片索引图片 067 白皮书图片索引图片 067，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 068 来源：巴别鸟企业网盘白皮书 / word/media/image43.png 静态路径： assets/images/whitepaper/whitepaper 068.png 白皮书图片索引图片 068 白皮书图片索引图片 068，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 069 来源：巴别鸟企业网盘白皮书 / word/media/image44.png 静态路径： assets/images/whitepaper/whitepaper 069.png 白皮书图片索引图片 069 白皮书图片索引图片 069，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 070 来源：巴别鸟企业网盘白皮书 / word/media/image45.png 静态路径： assets/images/whitepaper/whitepaper 070.png 白皮书图片索引图片 070 白皮书图片索引图片 070，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 071 来源：巴别鸟企业网盘白皮书 / word/media/image46.png 静态路径： assets/images/whitepaper/whitepaper 071.png 白皮书图片索引图片 071 白皮书图片索引图片 071，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 072 来源：巴别鸟企业网盘白皮书 / word/media/image47.png 静态路径： assets/images/whitepaper/whitepaper 072.png 白皮书图片索引图片 072 白皮书图片索引图片 072，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 073 来源：巴别鸟企业网盘白皮书 / word/media/image48.png 静态路径： assets/images/whitepaper/whitepaper 073.png 白皮书图片索引图片 073 白皮书图片索引图片 073，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 074 来源：巴别鸟企业网盘白皮书 / word/media/image49.png 静态路径： assets/images/whitepaper/whitepaper 074.png 白皮书图片索引图片 074 白皮书图片索引图片 074，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 075 来源：巴别鸟企业网盘白皮书 / word/media/image5.png 静态路径： assets/images/whitepaper/whitepaper 075.png 白皮书图片索引图片 075 白皮书图片索引图片 075，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 076 来源：巴别鸟企业网盘白皮书 / word/media/image50.png 静态路径： assets/images/whitepaper/whitepaper 076.png 白皮书图片索引图片 076 白皮书图片索引图片 076，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 077 来源：巴别鸟企业网盘白皮书 / word/media/image51.png 静态路径： assets/images/whitepaper/whitepaper 077.png 白皮书图片索引图片 077 白皮书图片索引图片 077，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 078 来源：巴别鸟企业网盘白皮书 / word/media/image52.png 静态路径： assets/images/whitepaper/whitepaper 078.png 白皮书图片索引图片 078 白皮书图片索引图片 078，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 079 来源：巴别鸟企业网盘白皮书 / word/media/image53.png 静态路径： assets/images/whitepaper/whitepaper 079.png 白皮书图片索引图片 079 白皮书图片索引图片 079，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 080 来源：巴别鸟企业网盘白皮书 / word/media/image54.png 静态路径： assets/images/whitepaper/whitepaper 080.png 白皮书图片索引图片 080 白皮书图片索引图片 080，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 081 来源：巴别鸟企业网盘白皮书 / word/media/image55.png 静态路径： assets/images/whitepaper/whitepaper 081.png 白皮书图片索引图片 081 白皮书图片索引图片 081，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 082 来源：巴别鸟企业网盘白皮书 / word/media/image56.png 静态路径： assets/images/whitepaper/whitepaper 082.png 白皮书图片索引图片 082 白皮书图片索引图片 082，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 083 来源：巴别鸟企业网盘白皮书 / word/media/image57.png 静态路径： assets/images/whitepaper/whitepaper 083.png 白皮书图片索引图片 083 白皮书图片索引图片 083，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 084 来源：巴别鸟企业网盘白皮书 / word/media/image58.png 静态路径： assets/images/whitepaper/whitepaper 084.png 白皮书图片索引图片 084 白皮书图片索引图片 084，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 085 来源：巴别鸟企业网盘白皮书 / word/media/image59.png 静态路径： assets/images/whitepaper/whitepaper 085.png 白皮书图片索引图片 085 白皮书图片索引图片 085，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 086 来源：巴别鸟企业网盘白皮书 / word/media/image6.png 静态路径： assets/images/whitepaper/whitepaper 086.png 白皮书图片索引图片 086 白皮书图片索引图片 086，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 087 来源：巴别鸟企业网盘白皮书 / word/media/image60.png 静态路径： assets/images/whitepaper/whitepaper 087.png 白皮书图片索引图片 087 白皮书图片索引图片 087，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 088 来源：巴别鸟企业网盘白皮书 / word/media/image61.png 静态路径： assets/images/whitepaper/whitepaper 088.png 白皮书图片索引图片 088 白皮书图片索引图片 088，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 089 来源：巴别鸟企业网盘白皮书 / word/media/image62.png 静态路径： assets/images/whitepaper/whitepaper 089.png 白皮书图片索引图片 089 白皮书图片索引图片 089，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 090 来源：巴别鸟企业网盘白皮书 / word/media/image63.png 静态路径： assets/images/whitepaper/whitepaper 090.png 白皮书图片索引图片 090 白皮书图片索引图片 090，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 091 来源：巴别鸟企业网盘白皮书 / word/media/image64.png 静态路径： assets/images/whitepaper/whitepaper 091.png 白皮书图片索引图片 091 白皮书图片索引图片 091，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 092 来源：巴别鸟企业网盘白皮书 / word/media/image65.png 静态路径： assets/images/whitepaper/whitepaper 092.png 白皮书图片索引图片 092 白皮书图片索引图片 092，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 093 来源：巴别鸟企业网盘白皮书 / word/media/image66.jpeg 静态路径： assets/images/whitepaper/whitepaper 093.jpeg 白皮书图片索引图片 093 白皮书图片索引图片 093，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 094 来源：巴别鸟企业网盘白皮书 / word/media/image67.png 静态路径： assets/images/whitepaper/whitepaper 094.png 白皮书图片索引图片 094 白皮书图片索引图片 094，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 095 来源：巴别鸟企业网盘白皮书 / word/media/image68.png 静态路径： assets/images/whitepaper/whitepaper 095.png 白皮书图片索引图片 095 白皮书图片索引图片 095，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 096 来源：巴别鸟企业网盘白皮书 / word/media/image69.png 静态路径： assets/images/whitepaper/whitepaper 096.png 白皮书图片索引图片 096 白皮书图片索引图片 096，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 097 来源：巴别鸟企业网盘白皮书 / word/media/image7.png 静态路径： assets/images/whitepaper/whitepaper 097.png 白皮书图片索引图片 097 白皮书图片索引图片 097，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 098 来源：巴别鸟企业网盘白皮书 / word/media/image70.png 静态路径： assets/images/whitepaper/whitepaper 098.png 白皮书图片索引图片 098 白皮书图片索引图片 098，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 099 来源：巴别鸟企业网盘白皮书 / word/media/image71.png 静态路径： assets/images/whitepaper/whitepaper 099.png 白皮书图片索引图片 099 白皮书图片索引图片 099，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 100 来源：巴别鸟企业网盘白皮书 / word/media/image72.png 静态路径： assets/images/whitepaper/whitepaper 100.png 白皮书图片索引图片 100 白皮书图片索引图片 100，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 101 来源：巴别鸟企业网盘白皮书 / word/media/image73.png 静态路径： assets/images/whitepaper/whitepaper 101.png 白皮书图片索引图片 101 白皮书图片索引图片 101，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 102 来源：巴别鸟企业网盘白皮书 / word/media/image74.png 静态路径： assets/images/whitepaper/whitepaper 102.png 白皮书图片索引图片 102 白皮书图片索引图片 102，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 103 来源：巴别鸟企业网盘白皮书 / word/media/image75.png 静态路径： assets/images/whitepaper/whitepaper 103.png 白皮书图片索引图片 103 白皮书图片索引图片 103，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 104 来源：巴别鸟企业网盘白皮书 / word/media/image76.jpeg 静态路径： assets/images/whitepaper/whitepaper 104.jpeg 白皮书图片索引图片 104 白皮书图片索引图片 104，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 105 来源：巴别鸟企业网盘白皮书 / word/media/image77.png 静态路径： assets/images/whitepaper/whitepaper 105.png 白皮书图片索引图片 105 白皮书图片索引图片 105，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 106 来源：巴别鸟企业网盘白皮书 / word/media/image78.png 静态路径： assets/images/whitepaper/whitepaper 106.png 白皮书图片索引图片 106 白皮书图片索引图片 106，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 107 来源：巴别鸟企业网盘白皮书 / word/media/image79.png 静态路径： assets/images/whitepaper/whitepaper 107.png 白皮书图片索引图片 107 白皮书图片索引图片 107，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 108 来源：巴别鸟企业网盘白皮书 / word/media/image8.png 静态路径： assets/images/whitepaper/whitepaper 108.png 白皮书图片索引图片 108 白皮书图片索引图片 108，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 109 来源：巴别鸟企业网盘白皮书 / word/media/image80.png 静态路径： assets/images/whitepaper/whitepaper 109.png 白皮书图片索引图片 109 白皮书图片索引图片 109，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 110 来源：巴别鸟企业网盘白皮书 / word/media/image81.png 静态路径： assets/images/whitepaper/whitepaper 110.png 白皮书图片索引图片 110 白皮书图片索引图片 110，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 111 来源：巴别鸟企业网盘白皮书 / word/media/image82.png 静态路径： assets/images/whitepaper/whitepaper 111.png 白皮书图片索引图片 111 白皮书图片索引图片 111，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 112 来源：巴别鸟企业网盘白皮书 / word/media/image83.png 静态路径： assets/images/whitepaper/whitepaper 112.png 白皮书图片索引图片 112 白皮书图片索引图片 112，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 113 来源：巴别鸟企业网盘白皮书 / word/media/image84.png 静态路径： assets/images/whitepaper/whitepaper 113.png 白皮书图片索引图片 113 白皮书图片索引图片 113，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 114 来源：巴别鸟企业网盘白皮书 / word/media/image85.tiff 静态路径： assets/images/whitepaper/whitepaper 114.tiff 该资源不是浏览器通用图片格式，保留文件供原文对照。 白皮书图片索引图片 115 来源：巴别鸟企业网盘白皮书 / word/media/image86.png 静态路径： assets/images/whitepaper/whitepaper 115.png 白皮书图片索引图片 115 白皮书图片索引图片 115，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 116 来源：巴别鸟企业网盘白皮书 / word/media/image87.png 静态路径： assets/images/whitepaper/whitepaper 116.png 白皮书图片索引图片 116 白皮书图片索引图片 116，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 117 来源：巴别鸟企业网盘白皮书 / word/media/image88.png 静态路径： assets/images/whitepaper/whitepaper 117.png 白皮书图片索引图片 117 白皮书图片索引图片 117，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 118 来源：巴别鸟企业网盘白皮书 / word/media/image89.png 静态路径： assets/images/whitepaper/whitepaper 118.png 白皮书图片索引图片 118 白皮书图片索引图片 118，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 119 来源：巴别鸟企业网盘白皮书 / word/media/image9.png 静态路径： assets/images/whitepaper/whitepaper 119.png 白皮书图片索引图片 119 白皮书图片索引图片 119，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 120 来源：巴别鸟企业网盘白皮书 / word/media/image90.png 静态路径： assets/images/whitepaper/whitepaper 120.png 白皮书图片索引图片 120 白皮书图片索引图片 120，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 121 来源：巴别鸟企业网盘白皮书 / word/media/image91.png 静态路径： assets/images/whitepaper/whitepaper 121.png 白皮书图片索引图片 121 白皮书图片索引图片 121，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 122 来源：巴别鸟企业网盘白皮书 / word/media/image92.png 静态路径： assets/images/whitepaper/whitepaper 122.png 白皮书图片索引图片 122 白皮书图片索引图片 122，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 123 来源：巴别鸟企业网盘白皮书 / word/media/image93.png 静态路径： assets/images/whitepaper/whitepaper 123.png 白皮书图片索引图片 123 白皮书图片索引图片 123，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 124 来源：巴别鸟企业网盘白皮书 / word/media/image94.png 静态路径： assets/images/whitepaper/whitepaper 124.png 白皮书图片索引图片 124 白皮书图片索引图片 124，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 125 来源：巴别鸟企业网盘白皮书 / word/media/image95.png 静态路径： assets/images/whitepaper/whitepaper 125.png 白皮书图片索引图片 125 白皮书图片索引图片 125，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 126 来源：巴别鸟企业网盘白皮书 / word/media/image96.png 静态路径： assets/images/whitepaper/whitepaper 126.png 白皮书图片索引图片 126 白皮书图片索引图片 126，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 127 来源：巴别鸟企业网盘白皮书 / word/media/image97.png 静态路径： assets/images/whitepaper/whitepaper 127.png 白皮书图片索引图片 127 白皮书图片索引图片 127，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 128 来源：巴别鸟企业网盘白皮书 / word/media/image98.png 静态路径： assets/images/whitepaper/whitepaper 128.png 白皮书图片索引图片 128 白皮书图片索引图片 128，从 巴别鸟企业网盘白皮书.docx 抽取。 白皮书图片索引图片 129 来源：巴别鸟企业网盘白皮书 / word/media/image99.png 静态路径： assets/images/whitepaper/whitepaper 129.png 白皮书图片索引图片 129 白皮书图片索引图片 129，从 巴别鸟企业网盘白皮书.docx 抽取。" }, { "lang": "zh", "slug": "reference-faq-images", "title": "FAQ 图片索引", "description": "从巴别鸟 FAQ 用户手册抽取的全部嵌入图片，供操作截图、原文对照和 AI 视觉资料索引使用。", "category": "源资料参考", "top_category": "维护", "keywords": [ "FAQ", "图片", "截图", "配图" ], "url": "zh/reference-faq-images.html", "source": "content/zh/reference-faq-images.md", "summary": "FAQ 图片索引 本页汇总《巴别鸟FAQ（用户手册）》中的全部嵌入图片。 这些图片从源文档中按原始顺序抽取，保留为可直接访问的静态资源。页面主要用于原文对照、AI 视觉资料索引、后续人工挑选配图和搜索引擎发现。 项 数值 图片数量 188 来源文件 巴别鸟FAQ（用户手册）.docx FAQ 图片索引图片 001 来源：巴别鸟FAQ（用户手册） / word/media/image1.png 静态路径： assets/images/faq/faq 001.png FAQ 图片索引图片 001 FAQ 图片索引图片 001，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 002 来源：巴别鸟FAQ（用户手册） / word/media/image10.png 静态路径： assets/images/faq/faq 002.png FAQ 图片索引图片 002 FAQ 图片索引图片 002，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 003 来源：巴别鸟FAQ（用户手册） / word/media/image100.png 静态路径： assets/images/faq/faq 003.png FAQ 图片索引图片 003 FAQ 图片索引图片 003，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 004 来源：巴别鸟FAQ（用户手册） / word/media/image11.png 静态路径： assets/images/faq/faq 004.png FAQ 图片索引图片 004 FAQ 图片索引图片 0", "headings": [ { "level": 1, "title": "FAQ 图片索引", "id": "faq" }, { "level": 2, "title": "FAQ 图片索引图片 001", "id": "faq-001" }, { "level": 2, "title": "FAQ 图片索引图片 002", "id": "faq-002" }, { "level": 2, "title": "FAQ 图片索引图片 003", "id": "faq-003" }, { "level": 2, "title": "FAQ 图片索引图片 004", "id": "faq-004" }, { "level": 2, "title": "FAQ 图片索引图片 005", "id": "faq-005" }, { "level": 2, "title": "FAQ 图片索引图片 006", "id": "faq-006" }, { "level": 2, "title": "FAQ 图片索引图片 007", "id": "faq-007" }, { "level": 2, "title": "FAQ 图片索引图片 008", "id": "faq-008" }, { "level": 2, "title": "FAQ 图片索引图片 009", "id": "faq-009" }, { "level": 2, "title": "FAQ 图片索引图片 010", "id": "faq-010" }, { "level": 2, "title": "FAQ 图片索引图片 011", "id": "faq-011" }, { "level": 2, "title": "FAQ 图片索引图片 012", "id": "faq-012" }, { "level": 2, "title": "FAQ 图片索引图片 013", "id": "faq-013" }, { "level": 2, "title": "FAQ 图片索引图片 014", "id": "faq-014" }, { "level": 2, "title": "FAQ 图片索引图片 015", "id": "faq-015" }, { "level": 2, "title": "FAQ 图片索引图片 016", "id": "faq-016" }, { "level": 2, "title": "FAQ 图片索引图片 017", "id": "faq-017" }, { "level": 2, "title": "FAQ 图片索引图片 018", "id": "faq-018" }, { "level": 2, "title": "FAQ 图片索引图片 019", "id": "faq-019" }, { "level": 2, "title": "FAQ 图片索引图片 020", "id": "faq-020" }, { "level": 2, "title": "FAQ 图片索引图片 021", "id": "faq-021" }, { "level": 2, "title": "FAQ 图片索引图片 022", "id": "faq-022" }, { "level": 2, "title": "FAQ 图片索引图片 023", "id": "faq-023" }, { "level": 2, "title": "FAQ 图片索引图片 024", "id": "faq-024" }, { "level": 2, "title": "FAQ 图片索引图片 025", "id": "faq-025" }, { "level": 2, "title": "FAQ 图片索引图片 026", "id": "faq-026" }, { "level": 2, "title": "FAQ 图片索引图片 027", "id": "faq-027" }, { "level": 2, "title": "FAQ 图片索引图片 028", "id": "faq-028" }, { "level": 2, "title": "FAQ 图片索引图片 029", "id": "faq-029" }, { "level": 2, "title": "FAQ 图片索引图片 030", "id": "faq-030" }, { "level": 2, "title": "FAQ 图片索引图片 031", "id": "faq-031" }, { "level": 2, "title": "FAQ 图片索引图片 032", "id": "faq-032" }, { "level": 2, "title": "FAQ 图片索引图片 033", "id": "faq-033" }, { "level": 2, "title": "FAQ 图片索引图片 034", "id": "faq-034" }, { "level": 2, "title": "FAQ 图片索引图片 035", "id": "faq-035" }, { "level": 2, "title": "FAQ 图片索引图片 036", "id": "faq-036" }, { "level": 2, "title": "FAQ 图片索引图片 037", "id": "faq-037" }, { "level": 2, "title": "FAQ 图片索引图片 038", "id": "faq-038" }, { "level": 2, "title": "FAQ 图片索引图片 039", "id": "faq-039" }, { "level": 2, "title": "FAQ 图片索引图片 040", "id": "faq-040" }, { "level": 2, "title": "FAQ 图片索引图片 041", "id": "faq-041" }, { "level": 2, "title": "FAQ 图片索引图片 042", "id": "faq-042" }, { "level": 2, "title": "FAQ 图片索引图片 043", "id": "faq-043" }, { "level": 2, "title": "FAQ 图片索引图片 044", "id": "faq-044" }, { "level": 2, "title": "FAQ 图片索引图片 045", "id": "faq-045" }, { "level": 2, "title": "FAQ 图片索引图片 046", "id": "faq-046" }, { "level": 2, "title": "FAQ 图片索引图片 047", "id": "faq-047" }, { "level": 2, "title": "FAQ 图片索引图片 048", "id": "faq-048" }, { "level": 2, "title": "FAQ 图片索引图片 049", "id": "faq-049" }, { "level": 2, "title": "FAQ 图片索引图片 050", "id": "faq-050" }, { "level": 2, "title": "FAQ 图片索引图片 051", "id": "faq-051" }, { "level": 2, "title": "FAQ 图片索引图片 052", "id": "faq-052" }, { "level": 2, "title": "FAQ 图片索引图片 053", "id": "faq-053" }, { "level": 2, "title": "FAQ 图片索引图片 054", "id": "faq-054" }, { "level": 2, "title": "FAQ 图片索引图片 055", "id": "faq-055" }, { "level": 2, "title": "FAQ 图片索引图片 056", "id": "faq-056" }, { "level": 2, "title": "FAQ 图片索引图片 057", "id": "faq-057" }, { "level": 2, "title": "FAQ 图片索引图片 058", "id": "faq-058" }, { "level": 2, "title": "FAQ 图片索引图片 059", "id": "faq-059" }, { "level": 2, "title": "FAQ 图片索引图片 060", "id": "faq-060" }, { "level": 2, "title": "FAQ 图片索引图片 061", "id": "faq-061" }, { "level": 2, "title": "FAQ 图片索引图片 062", "id": "faq-062" }, { "level": 2, "title": "FAQ 图片索引图片 063", "id": "faq-063" }, { "level": 2, "title": "FAQ 图片索引图片 064", "id": "faq-064" }, { "level": 2, "title": "FAQ 图片索引图片 065", "id": "faq-065" }, { "level": 2, "title": "FAQ 图片索引图片 066", "id": "faq-066" }, { "level": 2, "title": "FAQ 图片索引图片 067", "id": "faq-067" }, { "level": 2, "title": "FAQ 图片索引图片 068", "id": "faq-068" }, { "level": 2, "title": "FAQ 图片索引图片 069", "id": "faq-069" }, { "level": 2, "title": "FAQ 图片索引图片 070", "id": "faq-070" }, { "level": 2, "title": "FAQ 图片索引图片 071", "id": "faq-071" }, { "level": 2, "title": "FAQ 图片索引图片 072", "id": "faq-072" }, { "level": 2, "title": "FAQ 图片索引图片 073", "id": "faq-073" }, { "level": 2, "title": "FAQ 图片索引图片 074", "id": "faq-074" }, { "level": 2, "title": "FAQ 图片索引图片 075", "id": "faq-075" }, { "level": 2, "title": "FAQ 图片索引图片 076", "id": "faq-076" }, { "level": 2, "title": "FAQ 图片索引图片 077", "id": "faq-077" }, { "level": 2, "title": "FAQ 图片索引图片 078", "id": "faq-078" }, { "level": 2, "title": "FAQ 图片索引图片 079", "id": "faq-079" }, { "level": 2, "title": "FAQ 图片索引图片 080", "id": "faq-080" }, { "level": 2, "title": "FAQ 图片索引图片 081", "id": "faq-081" }, { "level": 2, "title": "FAQ 图片索引图片 082", "id": "faq-082" }, { "level": 2, "title": "FAQ 图片索引图片 083", "id": "faq-083" }, { "level": 2, "title": "FAQ 图片索引图片 084", "id": "faq-084" }, { "level": 2, "title": "FAQ 图片索引图片 085", "id": "faq-085" }, { "level": 2, "title": "FAQ 图片索引图片 086", "id": "faq-086" }, { "level": 2, "title": "FAQ 图片索引图片 087", "id": "faq-087" }, { "level": 2, "title": "FAQ 图片索引图片 088", "id": "faq-088" }, { "level": 2, "title": "FAQ 图片索引图片 089", "id": "faq-089" }, { "level": 2, "title": "FAQ 图片索引图片 090", "id": "faq-090" }, { "level": 2, "title": "FAQ 图片索引图片 091", "id": "faq-091" }, { "level": 2, "title": "FAQ 图片索引图片 092", "id": "faq-092" }, { "level": 2, "title": "FAQ 图片索引图片 093", "id": "faq-093" }, { "level": 2, "title": "FAQ 图片索引图片 094", "id": "faq-094" }, { "level": 2, "title": "FAQ 图片索引图片 095", "id": "faq-095" }, { "level": 2, "title": "FAQ 图片索引图片 096", "id": "faq-096" }, { "level": 2, "title": "FAQ 图片索引图片 097", "id": "faq-097" }, { "level": 2, "title": "FAQ 图片索引图片 098", "id": "faq-098" }, { "level": 2, "title": "FAQ 图片索引图片 099", "id": "faq-099" }, { "level": 2, "title": "FAQ 图片索引图片 100", "id": "faq-100" }, { "level": 2, "title": "FAQ 图片索引图片 101", "id": "faq-101" }, { "level": 2, "title": "FAQ 图片索引图片 102", "id": "faq-102" }, { "level": 2, "title": "FAQ 图片索引图片 103", "id": "faq-103" }, { "level": 2, "title": "FAQ 图片索引图片 104", "id": "faq-104" }, { "level": 2, "title": "FAQ 图片索引图片 105", "id": "faq-105" }, { "level": 2, "title": "FAQ 图片索引图片 106", "id": "faq-106" }, { "level": 2, "title": "FAQ 图片索引图片 107", "id": "faq-107" }, { "level": 2, "title": "FAQ 图片索引图片 108", "id": "faq-108" }, { "level": 2, "title": "FAQ 图片索引图片 109", "id": "faq-109" }, { "level": 2, "title": "FAQ 图片索引图片 110", "id": "faq-110" }, { "level": 2, "title": "FAQ 图片索引图片 111", "id": "faq-111" }, { "level": 2, "title": "FAQ 图片索引图片 112", "id": "faq-112" }, { "level": 2, "title": "FAQ 图片索引图片 113", "id": "faq-113" }, { "level": 2, "title": "FAQ 图片索引图片 114", "id": "faq-114" }, { "level": 2, "title": "FAQ 图片索引图片 115", "id": "faq-115" }, { "level": 2, "title": "FAQ 图片索引图片 116", "id": "faq-116" }, { "level": 2, "title": "FAQ 图片索引图片 117", "id": "faq-117" }, { "level": 2, "title": "FAQ 图片索引图片 118", "id": "faq-118" }, { "level": 2, "title": "FAQ 图片索引图片 119", "id": "faq-119" }, { "level": 2, "title": "FAQ 图片索引图片 120", "id": "faq-120" }, { "level": 2, "title": "FAQ 图片索引图片 121", "id": "faq-121" }, { "level": 2, "title": "FAQ 图片索引图片 122", "id": "faq-122" }, { "level": 2, "title": "FAQ 图片索引图片 123", "id": "faq-123" }, { "level": 2, "title": "FAQ 图片索引图片 124", "id": "faq-124" }, { "level": 2, "title": "FAQ 图片索引图片 125", "id": "faq-125" }, { "level": 2, "title": "FAQ 图片索引图片 126", "id": "faq-126" }, { "level": 2, "title": "FAQ 图片索引图片 127", "id": "faq-127" }, { "level": 2, "title": "FAQ 图片索引图片 128", "id": "faq-128" }, { "level": 2, "title": "FAQ 图片索引图片 129", "id": "faq-129" }, { "level": 2, "title": "FAQ 图片索引图片 130", "id": "faq-130" }, { "level": 2, "title": "FAQ 图片索引图片 131", "id": "faq-131" }, { "level": 2, "title": "FAQ 图片索引图片 132", "id": "faq-132" }, { "level": 2, "title": "FAQ 图片索引图片 133", "id": "faq-133" }, { "level": 2, "title": "FAQ 图片索引图片 134", "id": "faq-134" }, { "level": 2, "title": "FAQ 图片索引图片 135", "id": "faq-135" }, { "level": 2, "title": "FAQ 图片索引图片 136", "id": "faq-136" }, { "level": 2, "title": "FAQ 图片索引图片 137", "id": "faq-137" }, { "level": 2, "title": "FAQ 图片索引图片 138", "id": "faq-138" }, { "level": 2, "title": "FAQ 图片索引图片 139", "id": "faq-139" }, { "level": 2, "title": "FAQ 图片索引图片 140", "id": "faq-140" }, { "level": 2, "title": "FAQ 图片索引图片 141", "id": "faq-141" }, { "level": 2, "title": "FAQ 图片索引图片 142", "id": "faq-142" }, { "level": 2, "title": "FAQ 图片索引图片 143", "id": "faq-143" }, { "level": 2, "title": "FAQ 图片索引图片 144", "id": "faq-144" }, { "level": 2, "title": "FAQ 图片索引图片 145", "id": "faq-145" }, { "level": 2, "title": "FAQ 图片索引图片 146", "id": "faq-146" }, { "level": 2, "title": "FAQ 图片索引图片 147", "id": "faq-147" }, { "level": 2, "title": "FAQ 图片索引图片 148", "id": "faq-148" }, { "level": 2, "title": "FAQ 图片索引图片 149", "id": "faq-149" }, { "level": 2, "title": "FAQ 图片索引图片 150", "id": "faq-150" }, { "level": 2, "title": "FAQ 图片索引图片 151", "id": "faq-151" }, { "level": 2, "title": "FAQ 图片索引图片 152", "id": "faq-152" }, { "level": 2, "title": "FAQ 图片索引图片 153", "id": "faq-153" }, { "level": 2, "title": "FAQ 图片索引图片 154", "id": "faq-154" }, { "level": 2, "title": "FAQ 图片索引图片 155", "id": "faq-155" }, { "level": 2, "title": "FAQ 图片索引图片 156", "id": "faq-156" }, { "level": 2, "title": "FAQ 图片索引图片 157", "id": "faq-157" }, { "level": 2, "title": "FAQ 图片索引图片 158", "id": "faq-158" }, { "level": 2, "title": "FAQ 图片索引图片 159", "id": "faq-159" }, { "level": 2, "title": "FAQ 图片索引图片 160", "id": "faq-160" }, { "level": 2, "title": "FAQ 图片索引图片 161", "id": "faq-161" }, { "level": 2, "title": "FAQ 图片索引图片 162", "id": "faq-162" }, { "level": 2, "title": "FAQ 图片索引图片 163", "id": "faq-163" }, { "level": 2, "title": "FAQ 图片索引图片 164", "id": "faq-164" }, { "level": 2, "title": "FAQ 图片索引图片 165", "id": "faq-165" }, { "level": 2, "title": "FAQ 图片索引图片 166", "id": "faq-166" }, { "level": 2, "title": "FAQ 图片索引图片 167", "id": "faq-167" }, { "level": 2, "title": "FAQ 图片索引图片 168", "id": "faq-168" }, { "level": 2, "title": "FAQ 图片索引图片 169", "id": "faq-169" }, { "level": 2, "title": "FAQ 图片索引图片 170", "id": "faq-170" }, { "level": 2, "title": "FAQ 图片索引图片 171", "id": "faq-171" }, { "level": 2, "title": "FAQ 图片索引图片 172", "id": "faq-172" }, { "level": 2, "title": "FAQ 图片索引图片 173", "id": "faq-173" }, { "level": 2, "title": "FAQ 图片索引图片 174", "id": "faq-174" }, { "level": 2, "title": "FAQ 图片索引图片 175", "id": "faq-175" }, { "level": 2, "title": "FAQ 图片索引图片 176", "id": "faq-176" }, { "level": 2, "title": "FAQ 图片索引图片 177", "id": "faq-177" }, { "level": 2, "title": "FAQ 图片索引图片 178", "id": "faq-178" }, { "level": 2, "title": "FAQ 图片索引图片 179", "id": "faq-179" }, { "level": 2, "title": "FAQ 图片索引图片 180", "id": "faq-180" }, { "level": 2, "title": "FAQ 图片索引图片 181", "id": "faq-181" }, { "level": 2, "title": "FAQ 图片索引图片 182", "id": "faq-182" }, { "level": 2, "title": "FAQ 图片索引图片 183", "id": "faq-183" }, { "level": 2, "title": "FAQ 图片索引图片 184", "id": "faq-184" }, { "level": 2, "title": "FAQ 图片索引图片 185", "id": "faq-185" }, { "level": 2, "title": "FAQ 图片索引图片 186", "id": "faq-186" }, { "level": 2, "title": "FAQ 图片索引图片 187", "id": "faq-187" }, { "level": 2, "title": "FAQ 图片索引图片 188", "id": "faq-188" } ], "images": [ { "src": "../assets/images/faq/faq-001.png", "alt": "FAQ 图片索引图片 001", "caption": "FAQ 图片索引图片 001，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-002.png", "alt": "FAQ 图片索引图片 002", "caption": "FAQ 图片索引图片 002，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-003.png", "alt": "FAQ 图片索引图片 003", "caption": "FAQ 图片索引图片 003，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-004.png", "alt": "FAQ 图片索引图片 004", "caption": "FAQ 图片索引图片 004，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-005.png", "alt": "FAQ 图片索引图片 005", "caption": "FAQ 图片索引图片 005，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-006.png", "alt": "FAQ 图片索引图片 006", "caption": "FAQ 图片索引图片 006，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-007.png", "alt": "FAQ 图片索引图片 007", "caption": "FAQ 图片索引图片 007，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-008.png", "alt": "FAQ 图片索引图片 008", "caption": "FAQ 图片索引图片 008，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-009.png", "alt": "FAQ 图片索引图片 009", "caption": "FAQ 图片索引图片 009，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-010.png", "alt": "FAQ 图片索引图片 010", "caption": "FAQ 图片索引图片 010，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-011.png", "alt": "FAQ 图片索引图片 011", "caption": "FAQ 图片索引图片 011，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-012.png", "alt": "FAQ 图片索引图片 012", "caption": "FAQ 图片索引图片 012，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-013.png", "alt": "FAQ 图片索引图片 013", "caption": "FAQ 图片索引图片 013，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-014.png", "alt": "FAQ 图片索引图片 014", "caption": "FAQ 图片索引图片 014，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-015.png", "alt": "FAQ 图片索引图片 015", "caption": "FAQ 图片索引图片 015，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-016.png", "alt": "FAQ 图片索引图片 016", "caption": "FAQ 图片索引图片 016，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-017.png", "alt": "FAQ 图片索引图片 017", "caption": "FAQ 图片索引图片 017，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-018.png", "alt": "FAQ 图片索引图片 018", "caption": "FAQ 图片索引图片 018，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-019.png", "alt": "FAQ 图片索引图片 019", "caption": "FAQ 图片索引图片 019，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-020.png", "alt": "FAQ 图片索引图片 020", "caption": "FAQ 图片索引图片 020，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-021.png", "alt": "FAQ 图片索引图片 021", "caption": "FAQ 图片索引图片 021，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-022.png", "alt": "FAQ 图片索引图片 022", "caption": "FAQ 图片索引图片 022，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-023.png", "alt": "FAQ 图片索引图片 023", "caption": "FAQ 图片索引图片 023，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-024.png", "alt": "FAQ 图片索引图片 024", "caption": "FAQ 图片索引图片 024，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-025.png", "alt": "FAQ 图片索引图片 025", "caption": "FAQ 图片索引图片 025，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-026.png", "alt": "FAQ 图片索引图片 026", "caption": "FAQ 图片索引图片 026，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-027.png", "alt": "FAQ 图片索引图片 027", "caption": "FAQ 图片索引图片 027，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-028.png", "alt": "FAQ 图片索引图片 028", "caption": "FAQ 图片索引图片 028，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-029.png", "alt": "FAQ 图片索引图片 029", "caption": "FAQ 图片索引图片 029，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-030.png", "alt": "FAQ 图片索引图片 030", "caption": "FAQ 图片索引图片 030，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-031.png", "alt": "FAQ 图片索引图片 031", "caption": "FAQ 图片索引图片 031，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-032.png", "alt": "FAQ 图片索引图片 032", "caption": "FAQ 图片索引图片 032，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-033.png", "alt": "FAQ 图片索引图片 033", "caption": "FAQ 图片索引图片 033，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-034.png", "alt": "FAQ 图片索引图片 034", "caption": "FAQ 图片索引图片 034，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-035.png", "alt": "FAQ 图片索引图片 035", "caption": "FAQ 图片索引图片 035，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-036.png", "alt": "FAQ 图片索引图片 036", "caption": "FAQ 图片索引图片 036，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-037.png", "alt": "FAQ 图片索引图片 037", "caption": "FAQ 图片索引图片 037，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-038.png", "alt": "FAQ 图片索引图片 038", "caption": "FAQ 图片索引图片 038，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-039.png", "alt": "FAQ 图片索引图片 039", "caption": "FAQ 图片索引图片 039，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-040.png", "alt": "FAQ 图片索引图片 040", "caption": "FAQ 图片索引图片 040，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-041.png", "alt": "FAQ 图片索引图片 041", "caption": "FAQ 图片索引图片 041，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-042.png", "alt": "FAQ 图片索引图片 042", "caption": "FAQ 图片索引图片 042，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-043.png", "alt": "FAQ 图片索引图片 043", "caption": "FAQ 图片索引图片 043，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-044.png", "alt": "FAQ 图片索引图片 044", "caption": "FAQ 图片索引图片 044，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-045.png", "alt": "FAQ 图片索引图片 045", "caption": "FAQ 图片索引图片 045，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-046.png", "alt": "FAQ 图片索引图片 046", "caption": "FAQ 图片索引图片 046，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-047.png", "alt": "FAQ 图片索引图片 047", "caption": "FAQ 图片索引图片 047，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-048.png", "alt": "FAQ 图片索引图片 048", "caption": "FAQ 图片索引图片 048，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-049.png", "alt": "FAQ 图片索引图片 049", "caption": "FAQ 图片索引图片 049，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-050.png", "alt": "FAQ 图片索引图片 050", "caption": "FAQ 图片索引图片 050，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-051.png", "alt": "FAQ 图片索引图片 051", "caption": "FAQ 图片索引图片 051，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-052.png", "alt": "FAQ 图片索引图片 052", "caption": "FAQ 图片索引图片 052，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-053.png", "alt": "FAQ 图片索引图片 053", "caption": "FAQ 图片索引图片 053，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-054.png", "alt": "FAQ 图片索引图片 054", "caption": "FAQ 图片索引图片 054，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-055.png", "alt": "FAQ 图片索引图片 055", "caption": "FAQ 图片索引图片 055，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-056.png", "alt": "FAQ 图片索引图片 056", "caption": "FAQ 图片索引图片 056，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-057.png", "alt": "FAQ 图片索引图片 057", "caption": "FAQ 图片索引图片 057，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-058.png", "alt": "FAQ 图片索引图片 058", "caption": "FAQ 图片索引图片 058，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-059.png", "alt": "FAQ 图片索引图片 059", "caption": "FAQ 图片索引图片 059，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-060.png", "alt": "FAQ 图片索引图片 060", "caption": "FAQ 图片索引图片 060，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-061.png", "alt": "FAQ 图片索引图片 061", "caption": "FAQ 图片索引图片 061，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-062.png", "alt": "FAQ 图片索引图片 062", "caption": "FAQ 图片索引图片 062，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-063.png", "alt": "FAQ 图片索引图片 063", "caption": "FAQ 图片索引图片 063，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-064.png", "alt": "FAQ 图片索引图片 064", "caption": "FAQ 图片索引图片 064，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-065.png", "alt": "FAQ 图片索引图片 065", "caption": "FAQ 图片索引图片 065，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-066.png", "alt": "FAQ 图片索引图片 066", "caption": "FAQ 图片索引图片 066，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-067.png", "alt": "FAQ 图片索引图片 067", "caption": "FAQ 图片索引图片 067，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-068.png", "alt": "FAQ 图片索引图片 068", "caption": "FAQ 图片索引图片 068，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-069.png", "alt": "FAQ 图片索引图片 069", "caption": "FAQ 图片索引图片 069，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-070.png", "alt": "FAQ 图片索引图片 070", "caption": "FAQ 图片索引图片 070，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-071.png", "alt": "FAQ 图片索引图片 071", "caption": "FAQ 图片索引图片 071，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-072.png", "alt": "FAQ 图片索引图片 072", "caption": "FAQ 图片索引图片 072，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-073.png", "alt": "FAQ 图片索引图片 073", "caption": "FAQ 图片索引图片 073，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-074.png", "alt": "FAQ 图片索引图片 074", "caption": "FAQ 图片索引图片 074，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-075.png", "alt": "FAQ 图片索引图片 075", "caption": "FAQ 图片索引图片 075，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-076.png", "alt": "FAQ 图片索引图片 076", "caption": "FAQ 图片索引图片 076，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-077.png", "alt": "FAQ 图片索引图片 077", "caption": "FAQ 图片索引图片 077，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-078.png", "alt": "FAQ 图片索引图片 078", "caption": "FAQ 图片索引图片 078，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-079.png", "alt": "FAQ 图片索引图片 079", "caption": "FAQ 图片索引图片 079，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-080.png", "alt": "FAQ 图片索引图片 080", "caption": "FAQ 图片索引图片 080，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-081.png", "alt": "FAQ 图片索引图片 081", "caption": "FAQ 图片索引图片 081，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-082.png", "alt": "FAQ 图片索引图片 082", "caption": "FAQ 图片索引图片 082，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-083.png", "alt": "FAQ 图片索引图片 083", "caption": "FAQ 图片索引图片 083，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-084.png", "alt": "FAQ 图片索引图片 084", "caption": "FAQ 图片索引图片 084，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-085.png", "alt": "FAQ 图片索引图片 085", "caption": "FAQ 图片索引图片 085，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-086.png", "alt": "FAQ 图片索引图片 086", "caption": "FAQ 图片索引图片 086，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-087.png", "alt": "FAQ 图片索引图片 087", "caption": "FAQ 图片索引图片 087，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-088.png", "alt": "FAQ 图片索引图片 088", "caption": "FAQ 图片索引图片 088，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-089.png", "alt": "FAQ 图片索引图片 089", "caption": "FAQ 图片索引图片 089，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-090.png", "alt": "FAQ 图片索引图片 090", "caption": "FAQ 图片索引图片 090，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-091.png", "alt": "FAQ 图片索引图片 091", "caption": "FAQ 图片索引图片 091，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-092.png", "alt": "FAQ 图片索引图片 092", "caption": "FAQ 图片索引图片 092，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-093.png", "alt": "FAQ 图片索引图片 093", "caption": "FAQ 图片索引图片 093，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-094.png", "alt": "FAQ 图片索引图片 094", "caption": "FAQ 图片索引图片 094，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-095.png", "alt": "FAQ 图片索引图片 095", "caption": "FAQ 图片索引图片 095，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-096.png", "alt": "FAQ 图片索引图片 096", "caption": "FAQ 图片索引图片 096，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-097.png", "alt": "FAQ 图片索引图片 097", "caption": "FAQ 图片索引图片 097，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-098.png", "alt": "FAQ 图片索引图片 098", "caption": "FAQ 图片索引图片 098，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-099.png", "alt": "FAQ 图片索引图片 099", "caption": "FAQ 图片索引图片 099，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-100.png", "alt": "FAQ 图片索引图片 100", "caption": "FAQ 图片索引图片 100，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-101.png", "alt": "FAQ 图片索引图片 101", "caption": "FAQ 图片索引图片 101，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-102.jpg", "alt": "FAQ 图片索引图片 102", "caption": "FAQ 图片索引图片 102，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-103.png", "alt": "FAQ 图片索引图片 103", "caption": "FAQ 图片索引图片 103，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-104.jpg", "alt": "FAQ 图片索引图片 104", "caption": "FAQ 图片索引图片 104，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-105.png", "alt": "FAQ 图片索引图片 105", "caption": "FAQ 图片索引图片 105，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-106.png", "alt": "FAQ 图片索引图片 106", "caption": "FAQ 图片索引图片 106，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-107.png", "alt": "FAQ 图片索引图片 107", "caption": "FAQ 图片索引图片 107，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-108.png", "alt": "FAQ 图片索引图片 108", "caption": "FAQ 图片索引图片 108，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-109.png", "alt": "FAQ 图片索引图片 109", "caption": "FAQ 图片索引图片 109，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-110.png", "alt": "FAQ 图片索引图片 110", "caption": "FAQ 图片索引图片 110，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-111.png", "alt": "FAQ 图片索引图片 111", "caption": "FAQ 图片索引图片 111，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-112.png", "alt": "FAQ 图片索引图片 112", "caption": "FAQ 图片索引图片 112，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-113.png", "alt": "FAQ 图片索引图片 113", "caption": "FAQ 图片索引图片 113，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-114.png", "alt": "FAQ 图片索引图片 114", "caption": "FAQ 图片索引图片 114，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-115.png", "alt": "FAQ 图片索引图片 115", "caption": "FAQ 图片索引图片 115，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-116.png", "alt": "FAQ 图片索引图片 116", "caption": "FAQ 图片索引图片 116，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-117.png", "alt": "FAQ 图片索引图片 117", "caption": "FAQ 图片索引图片 117，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-118.png", "alt": "FAQ 图片索引图片 118", "caption": "FAQ 图片索引图片 118，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-119.png", "alt": "FAQ 图片索引图片 119", "caption": "FAQ 图片索引图片 119，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-120.png", "alt": "FAQ 图片索引图片 120", "caption": "FAQ 图片索引图片 120，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-121.png", "alt": "FAQ 图片索引图片 121", "caption": "FAQ 图片索引图片 121，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-122.png", "alt": "FAQ 图片索引图片 122", "caption": "FAQ 图片索引图片 122，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-123.png", "alt": "FAQ 图片索引图片 123", "caption": "FAQ 图片索引图片 123，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-124.png", "alt": "FAQ 图片索引图片 124", "caption": "FAQ 图片索引图片 124，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-125.png", "alt": "FAQ 图片索引图片 125", "caption": "FAQ 图片索引图片 125，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-126.png", "alt": "FAQ 图片索引图片 126", "caption": "FAQ 图片索引图片 126，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-127.png", "alt": "FAQ 图片索引图片 127", "caption": "FAQ 图片索引图片 127，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-128.png", "alt": "FAQ 图片索引图片 128", "caption": "FAQ 图片索引图片 128，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-129.png", "alt": "FAQ 图片索引图片 129", "caption": "FAQ 图片索引图片 129，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-130.png", "alt": "FAQ 图片索引图片 130", "caption": "FAQ 图片索引图片 130，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-131.png", "alt": "FAQ 图片索引图片 131", "caption": "FAQ 图片索引图片 131，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-132.png", "alt": "FAQ 图片索引图片 132", "caption": "FAQ 图片索引图片 132，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-133.png", "alt": "FAQ 图片索引图片 133", "caption": "FAQ 图片索引图片 133，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-134.png", "alt": "FAQ 图片索引图片 134", "caption": "FAQ 图片索引图片 134，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-135.png", "alt": "FAQ 图片索引图片 135", "caption": "FAQ 图片索引图片 135，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-136.png", "alt": "FAQ 图片索引图片 136", "caption": "FAQ 图片索引图片 136，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-137.png", "alt": "FAQ 图片索引图片 137", "caption": "FAQ 图片索引图片 137，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-138.png", "alt": "FAQ 图片索引图片 138", "caption": "FAQ 图片索引图片 138，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-139.png", "alt": "FAQ 图片索引图片 139", "caption": "FAQ 图片索引图片 139，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-140.png", "alt": "FAQ 图片索引图片 140", "caption": "FAQ 图片索引图片 140，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-141.png", "alt": "FAQ 图片索引图片 141", "caption": "FAQ 图片索引图片 141，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-142.png", "alt": "FAQ 图片索引图片 142", "caption": "FAQ 图片索引图片 142，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-143.png", "alt": "FAQ 图片索引图片 143", "caption": "FAQ 图片索引图片 143，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-144.png", "alt": "FAQ 图片索引图片 144", "caption": "FAQ 图片索引图片 144，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-145.png", "alt": "FAQ 图片索引图片 145", "caption": "FAQ 图片索引图片 145，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-146.png", "alt": "FAQ 图片索引图片 146", "caption": "FAQ 图片索引图片 146，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-147.png", "alt": "FAQ 图片索引图片 147", "caption": "FAQ 图片索引图片 147，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-148.png", "alt": "FAQ 图片索引图片 148", "caption": "FAQ 图片索引图片 148，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-149.png", "alt": "FAQ 图片索引图片 149", "caption": "FAQ 图片索引图片 149，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-150.png", "alt": "FAQ 图片索引图片 150", "caption": "FAQ 图片索引图片 150，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-151.png", "alt": "FAQ 图片索引图片 151", "caption": "FAQ 图片索引图片 151，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-152.png", "alt": "FAQ 图片索引图片 152", "caption": "FAQ 图片索引图片 152，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-153.png", "alt": "FAQ 图片索引图片 153", "caption": "FAQ 图片索引图片 153，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-154.png", "alt": "FAQ 图片索引图片 154", "caption": "FAQ 图片索引图片 154，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-155.png", "alt": "FAQ 图片索引图片 155", "caption": "FAQ 图片索引图片 155，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-156.png", "alt": "FAQ 图片索引图片 156", "caption": "FAQ 图片索引图片 156，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-157.png", "alt": "FAQ 图片索引图片 157", "caption": "FAQ 图片索引图片 157，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-158.png", "alt": "FAQ 图片索引图片 158", "caption": "FAQ 图片索引图片 158，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-159.png", "alt": "FAQ 图片索引图片 159", "caption": "FAQ 图片索引图片 159，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-160.png", "alt": "FAQ 图片索引图片 160", "caption": "FAQ 图片索引图片 160，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-161.png", "alt": "FAQ 图片索引图片 161", "caption": "FAQ 图片索引图片 161，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-162.png", "alt": "FAQ 图片索引图片 162", "caption": "FAQ 图片索引图片 162，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-163.png", "alt": "FAQ 图片索引图片 163", "caption": "FAQ 图片索引图片 163，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-164.png", "alt": "FAQ 图片索引图片 164", "caption": "FAQ 图片索引图片 164，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-165.png", "alt": "FAQ 图片索引图片 165", "caption": "FAQ 图片索引图片 165，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-166.png", "alt": "FAQ 图片索引图片 166", "caption": "FAQ 图片索引图片 166，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-167.png", "alt": "FAQ 图片索引图片 167", "caption": "FAQ 图片索引图片 167，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-168.png", "alt": "FAQ 图片索引图片 168", "caption": "FAQ 图片索引图片 168，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-169.png", "alt": "FAQ 图片索引图片 169", "caption": "FAQ 图片索引图片 169，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-170.png", "alt": "FAQ 图片索引图片 170", "caption": "FAQ 图片索引图片 170，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-171.png", "alt": "FAQ 图片索引图片 171", "caption": "FAQ 图片索引图片 171，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-172.png", "alt": "FAQ 图片索引图片 172", "caption": "FAQ 图片索引图片 172，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-173.png", "alt": "FAQ 图片索引图片 173", "caption": "FAQ 图片索引图片 173，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-174.png", "alt": "FAQ 图片索引图片 174", "caption": "FAQ 图片索引图片 174，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-175.png", "alt": "FAQ 图片索引图片 175", "caption": "FAQ 图片索引图片 175，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-176.png", "alt": "FAQ 图片索引图片 176", "caption": "FAQ 图片索引图片 176，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-177.png", "alt": "FAQ 图片索引图片 177", "caption": "FAQ 图片索引图片 177，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-178.png", "alt": "FAQ 图片索引图片 178", "caption": "FAQ 图片索引图片 178，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-179.png", "alt": "FAQ 图片索引图片 179", "caption": "FAQ 图片索引图片 179，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-180.png", "alt": "FAQ 图片索引图片 180", "caption": "FAQ 图片索引图片 180，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-181.png", "alt": "FAQ 图片索引图片 181", "caption": "FAQ 图片索引图片 181，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-182.png", "alt": "FAQ 图片索引图片 182", "caption": "FAQ 图片索引图片 182，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-183.png", "alt": "FAQ 图片索引图片 183", "caption": "FAQ 图片索引图片 183，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-184.png", "alt": "FAQ 图片索引图片 184", "caption": "FAQ 图片索引图片 184，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-185.png", "alt": "FAQ 图片索引图片 185", "caption": "FAQ 图片索引图片 185，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-186.png", "alt": "FAQ 图片索引图片 186", "caption": "FAQ 图片索引图片 186，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-187.png", "alt": "FAQ 图片索引图片 187", "caption": "FAQ 图片索引图片 187，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "src": "../assets/images/faq/faq-188.png", "alt": "FAQ 图片索引图片 188", "caption": "FAQ 图片索引图片 188，从 巴别鸟FAQ（用户手册）.docx 抽取。" } ], "text": "FAQ 图片索引 本页汇总《巴别鸟FAQ（用户手册）》中的全部嵌入图片。 这些图片从源文档中按原始顺序抽取，保留为可直接访问的静态资源。页面主要用于原文对照、AI 视觉资料索引、后续人工挑选配图和搜索引擎发现。 项 数值 图片数量 188 来源文件 巴别鸟FAQ（用户手册）.docx FAQ 图片索引图片 001 来源：巴别鸟FAQ（用户手册） / word/media/image1.png 静态路径： assets/images/faq/faq 001.png FAQ 图片索引图片 001 FAQ 图片索引图片 001，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 002 来源：巴别鸟FAQ（用户手册） / word/media/image10.png 静态路径： assets/images/faq/faq 002.png FAQ 图片索引图片 002 FAQ 图片索引图片 002，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 003 来源：巴别鸟FAQ（用户手册） / word/media/image100.png 静态路径： assets/images/faq/faq 003.png FAQ 图片索引图片 003 FAQ 图片索引图片 003，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 004 来源：巴别鸟FAQ（用户手册） / word/media/image11.png 静态路径： assets/images/faq/faq 004.png FAQ 图片索引图片 004 FAQ 图片索引图片 004，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 005 来源：巴别鸟FAQ（用户手册） / word/media/image110.png 静态路径： assets/images/faq/faq 005.png FAQ 图片索引图片 005 FAQ 图片索引图片 005，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 006 来源：巴别鸟FAQ（用户手册） / word/media/image111.png 静态路径： assets/images/faq/faq 006.png FAQ 图片索引图片 006 FAQ 图片索引图片 006，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 007 来源：巴别鸟FAQ（用户手册） / word/media/image12.png 静态路径： assets/images/faq/faq 007.png FAQ 图片索引图片 007 FAQ 图片索引图片 007，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 008 来源：巴别鸟FAQ（用户手册） / word/media/image120.png 静态路径： assets/images/faq/faq 008.png FAQ 图片索引图片 008 FAQ 图片索引图片 008，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 009 来源：巴别鸟FAQ（用户手册） / word/media/image13.png 静态路径： assets/images/faq/faq 009.png FAQ 图片索引图片 009 FAQ 图片索引图片 009，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 010 来源：巴别鸟FAQ（用户手册） / word/media/image130.png 静态路径： assets/images/faq/faq 010.png FAQ 图片索引图片 010 FAQ 图片索引图片 010，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 011 来源：巴别鸟FAQ（用户手册） / word/media/image14.png 静态路径： assets/images/faq/faq 011.png FAQ 图片索引图片 011 FAQ 图片索引图片 011，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 012 来源：巴别鸟FAQ（用户手册） / word/media/image140.png 静态路径： assets/images/faq/faq 012.png FAQ 图片索引图片 012 FAQ 图片索引图片 012，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 013 来源：巴别鸟FAQ（用户手册） / word/media/image15.png 静态路径： assets/images/faq/faq 013.png FAQ 图片索引图片 013 FAQ 图片索引图片 013，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 014 来源：巴别鸟FAQ（用户手册） / word/media/image150.png 静态路径： assets/images/faq/faq 014.png FAQ 图片索引图片 014 FAQ 图片索引图片 014，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 015 来源：巴别鸟FAQ（用户手册） / word/media/image16.png 静态路径： assets/images/faq/faq 015.png FAQ 图片索引图片 015 FAQ 图片索引图片 015，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 016 来源：巴别鸟FAQ（用户手册） / word/media/image160.png 静态路径： assets/images/faq/faq 016.png FAQ 图片索引图片 016 FAQ 图片索引图片 016，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 017 来源：巴别鸟FAQ（用户手册） / word/media/image17.png 静态路径： assets/images/faq/faq 017.png FAQ 图片索引图片 017 FAQ 图片索引图片 017，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 018 来源：巴别鸟FAQ（用户手册） / word/media/image170.png 静态路径： assets/images/faq/faq 018.png FAQ 图片索引图片 018 FAQ 图片索引图片 018，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 019 来源：巴别鸟FAQ（用户手册） / word/media/image18.png 静态路径： assets/images/faq/faq 019.png FAQ 图片索引图片 019 FAQ 图片索引图片 019，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 020 来源：巴别鸟FAQ（用户手册） / word/media/image180.png 静态路径： assets/images/faq/faq 020.png FAQ 图片索引图片 020 FAQ 图片索引图片 020，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 021 来源：巴别鸟FAQ（用户手册） / word/media/image19.png 静态路径： assets/images/faq/faq 021.png FAQ 图片索引图片 021 FAQ 图片索引图片 021，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 022 来源：巴别鸟FAQ（用户手册） / word/media/image190.png 静态路径： assets/images/faq/faq 022.png FAQ 图片索引图片 022 FAQ 图片索引图片 022，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 023 来源：巴别鸟FAQ（用户手册） / word/media/image2.png 静态路径： assets/images/faq/faq 023.png FAQ 图片索引图片 023 FAQ 图片索引图片 023，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 024 来源：巴别鸟FAQ（用户手册） / word/media/image20.png 静态路径： assets/images/faq/faq 024.png FAQ 图片索引图片 024 FAQ 图片索引图片 024，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 025 来源：巴别鸟FAQ（用户手册） / word/media/image200.png 静态路径： assets/images/faq/faq 025.png FAQ 图片索引图片 025 FAQ 图片索引图片 025，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 026 来源：巴别鸟FAQ（用户手册） / word/media/image21.png 静态路径： assets/images/faq/faq 026.png FAQ 图片索引图片 026 FAQ 图片索引图片 026，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 027 来源：巴别鸟FAQ（用户手册） / word/media/image210.png 静态路径： assets/images/faq/faq 027.png FAQ 图片索引图片 027 FAQ 图片索引图片 027，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 028 来源：巴别鸟FAQ（用户手册） / word/media/image211.png 静态路径： assets/images/faq/faq 028.png FAQ 图片索引图片 028 FAQ 图片索引图片 028，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 029 来源：巴别鸟FAQ（用户手册） / word/media/image22.png 静态路径： assets/images/faq/faq 029.png FAQ 图片索引图片 029 FAQ 图片索引图片 029，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 030 来源：巴别鸟FAQ（用户手册） / word/media/image220.png 静态路径： assets/images/faq/faq 030.png FAQ 图片索引图片 030 FAQ 图片索引图片 030，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 031 来源：巴别鸟FAQ（用户手册） / word/media/image23.png 静态路径： assets/images/faq/faq 031.png FAQ 图片索引图片 031 FAQ 图片索引图片 031，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 032 来源：巴别鸟FAQ（用户手册） / word/media/image230.png 静态路径： assets/images/faq/faq 032.png FAQ 图片索引图片 032 FAQ 图片索引图片 032，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 033 来源：巴别鸟FAQ（用户手册） / word/media/image24.png 静态路径： assets/images/faq/faq 033.png FAQ 图片索引图片 033 FAQ 图片索引图片 033，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 034 来源：巴别鸟FAQ（用户手册） / word/media/image240.png 静态路径： assets/images/faq/faq 034.png FAQ 图片索引图片 034 FAQ 图片索引图片 034，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 035 来源：巴别鸟FAQ（用户手册） / word/media/image25.png 静态路径： assets/images/faq/faq 035.png FAQ 图片索引图片 035 FAQ 图片索引图片 035，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 036 来源：巴别鸟FAQ（用户手册） / word/media/image250.png 静态路径： assets/images/faq/faq 036.png FAQ 图片索引图片 036 FAQ 图片索引图片 036，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 037 来源：巴别鸟FAQ（用户手册） / word/media/image26.png 静态路径： assets/images/faq/faq 037.png FAQ 图片索引图片 037 FAQ 图片索引图片 037，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 038 来源：巴别鸟FAQ（用户手册） / word/media/image260.png 静态路径： assets/images/faq/faq 038.png FAQ 图片索引图片 038 FAQ 图片索引图片 038，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 039 来源：巴别鸟FAQ（用户手册） / word/media/image27.png 静态路径： assets/images/faq/faq 039.png FAQ 图片索引图片 039 FAQ 图片索引图片 039，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 040 来源：巴别鸟FAQ（用户手册） / word/media/image270.png 静态路径： assets/images/faq/faq 040.png FAQ 图片索引图片 040 FAQ 图片索引图片 040，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 041 来源：巴别鸟FAQ（用户手册） / word/media/image28.png 静态路径： assets/images/faq/faq 041.png FAQ 图片索引图片 041 FAQ 图片索引图片 041，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 042 来源：巴别鸟FAQ（用户手册） / word/media/image280.png 静态路径： assets/images/faq/faq 042.png FAQ 图片索引图片 042 FAQ 图片索引图片 042，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 043 来源：巴别鸟FAQ（用户手册） / word/media/image29.png 静态路径： assets/images/faq/faq 043.png FAQ 图片索引图片 043 FAQ 图片索引图片 043，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 044 来源：巴别鸟FAQ（用户手册） / word/media/image290.png 静态路径： assets/images/faq/faq 044.png FAQ 图片索引图片 044 FAQ 图片索引图片 044，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 045 来源：巴别鸟FAQ（用户手册） / word/media/image3.png 静态路径： assets/images/faq/faq 045.png FAQ 图片索引图片 045 FAQ 图片索引图片 045，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 046 来源：巴别鸟FAQ（用户手册） / word/media/image30.png 静态路径： assets/images/faq/faq 046.png FAQ 图片索引图片 046 FAQ 图片索引图片 046，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 047 来源：巴别鸟FAQ（用户手册） / word/media/image300.png 静态路径： assets/images/faq/faq 047.png FAQ 图片索引图片 047 FAQ 图片索引图片 047，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 048 来源：巴别鸟FAQ（用户手册） / word/media/image31.png 静态路径： assets/images/faq/faq 048.png FAQ 图片索引图片 048 FAQ 图片索引图片 048，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 049 来源：巴别鸟FAQ（用户手册） / word/media/image310.png 静态路径： assets/images/faq/faq 049.png FAQ 图片索引图片 049 FAQ 图片索引图片 049，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 050 来源：巴别鸟FAQ（用户手册） / word/media/image311.png 静态路径： assets/images/faq/faq 050.png FAQ 图片索引图片 050 FAQ 图片索引图片 050，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 051 来源：巴别鸟FAQ（用户手册） / word/media/image32.png 静态路径： assets/images/faq/faq 051.png FAQ 图片索引图片 051 FAQ 图片索引图片 051，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 052 来源：巴别鸟FAQ（用户手册） / word/media/image320.png 静态路径： assets/images/faq/faq 052.png FAQ 图片索引图片 052 FAQ 图片索引图片 052，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 053 来源：巴别鸟FAQ（用户手册） / word/media/image33.png 静态路径： assets/images/faq/faq 053.png FAQ 图片索引图片 053 FAQ 图片索引图片 053，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 054 来源：巴别鸟FAQ（用户手册） / word/media/image330.png 静态路径： assets/images/faq/faq 054.png FAQ 图片索引图片 054 FAQ 图片索引图片 054，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 055 来源：巴别鸟FAQ（用户手册） / word/media/image34.png 静态路径： assets/images/faq/faq 055.png FAQ 图片索引图片 055 FAQ 图片索引图片 055，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 056 来源：巴别鸟FAQ（用户手册） / word/media/image340.png 静态路径： assets/images/faq/faq 056.png FAQ 图片索引图片 056 FAQ 图片索引图片 056，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 057 来源：巴别鸟FAQ（用户手册） / word/media/image35.png 静态路径： assets/images/faq/faq 057.png FAQ 图片索引图片 057 FAQ 图片索引图片 057，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 058 来源：巴别鸟FAQ（用户手册） / word/media/image350.png 静态路径： assets/images/faq/faq 058.png FAQ 图片索引图片 058 FAQ 图片索引图片 058，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 059 来源：巴别鸟FAQ（用户手册） / word/media/image36.png 静态路径： assets/images/faq/faq 059.png FAQ 图片索引图片 059 FAQ 图片索引图片 059，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 060 来源：巴别鸟FAQ（用户手册） / word/media/image360.png 静态路径： assets/images/faq/faq 060.png FAQ 图片索引图片 060 FAQ 图片索引图片 060，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 061 来源：巴别鸟FAQ（用户手册） / word/media/image37.png 静态路径： assets/images/faq/faq 061.png FAQ 图片索引图片 061 FAQ 图片索引图片 061，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 062 来源：巴别鸟FAQ（用户手册） / word/media/image370.png 静态路径： assets/images/faq/faq 062.png FAQ 图片索引图片 062 FAQ 图片索引图片 062，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 063 来源：巴别鸟FAQ（用户手册） / word/media/image38.png 静态路径： assets/images/faq/faq 063.png FAQ 图片索引图片 063 FAQ 图片索引图片 063，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 064 来源：巴别鸟FAQ（用户手册） / word/media/image380.png 静态路径： assets/images/faq/faq 064.png FAQ 图片索引图片 064 FAQ 图片索引图片 064，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 065 来源：巴别鸟FAQ（用户手册） / word/media/image39.png 静态路径： assets/images/faq/faq 065.png FAQ 图片索引图片 065 FAQ 图片索引图片 065，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 066 来源：巴别鸟FAQ（用户手册） / word/media/image390.png 静态路径： assets/images/faq/faq 066.png FAQ 图片索引图片 066 FAQ 图片索引图片 066，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 067 来源：巴别鸟FAQ（用户手册） / word/media/image4.png 静态路径： assets/images/faq/faq 067.png FAQ 图片索引图片 067 FAQ 图片索引图片 067，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 068 来源：巴别鸟FAQ（用户手册） / word/media/image40.png 静态路径： assets/images/faq/faq 068.png FAQ 图片索引图片 068 FAQ 图片索引图片 068，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 069 来源：巴别鸟FAQ（用户手册） / word/media/image400.png 静态路径： assets/images/faq/faq 069.png FAQ 图片索引图片 069 FAQ 图片索引图片 069，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 070 来源：巴别鸟FAQ（用户手册） / word/media/image41.png 静态路径： assets/images/faq/faq 070.png FAQ 图片索引图片 070 FAQ 图片索引图片 070，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 071 来源：巴别鸟FAQ（用户手册） / word/media/image410.png 静态路径： assets/images/faq/faq 071.png FAQ 图片索引图片 071 FAQ 图片索引图片 071，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 072 来源：巴别鸟FAQ（用户手册） / word/media/image411.png 静态路径： assets/images/faq/faq 072.png FAQ 图片索引图片 072 FAQ 图片索引图片 072，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 073 来源：巴别鸟FAQ（用户手册） / word/media/image42.png 静态路径： assets/images/faq/faq 073.png FAQ 图片索引图片 073 FAQ 图片索引图片 073，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 074 来源：巴别鸟FAQ（用户手册） / word/media/image420.png 静态路径： assets/images/faq/faq 074.png FAQ 图片索引图片 074 FAQ 图片索引图片 074，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 075 来源：巴别鸟FAQ（用户手册） / word/media/image43.png 静态路径： assets/images/faq/faq 075.png FAQ 图片索引图片 075 FAQ 图片索引图片 075，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 076 来源：巴别鸟FAQ（用户手册） / word/media/image430.png 静态路径： assets/images/faq/faq 076.png FAQ 图片索引图片 076 FAQ 图片索引图片 076，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 077 来源：巴别鸟FAQ（用户手册） / word/media/image44.png 静态路径： assets/images/faq/faq 077.png FAQ 图片索引图片 077 FAQ 图片索引图片 077，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 078 来源：巴别鸟FAQ（用户手册） / word/media/image440.png 静态路径： assets/images/faq/faq 078.png FAQ 图片索引图片 078 FAQ 图片索引图片 078，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 079 来源：巴别鸟FAQ（用户手册） / word/media/image45.png 静态路径： assets/images/faq/faq 079.png FAQ 图片索引图片 079 FAQ 图片索引图片 079，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 080 来源：巴别鸟FAQ（用户手册） / word/media/image450.png 静态路径： assets/images/faq/faq 080.png FAQ 图片索引图片 080 FAQ 图片索引图片 080，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 081 来源：巴别鸟FAQ（用户手册） / word/media/image46.png 静态路径： assets/images/faq/faq 081.png FAQ 图片索引图片 081 FAQ 图片索引图片 081，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 082 来源：巴别鸟FAQ（用户手册） / word/media/image460.png 静态路径： assets/images/faq/faq 082.png FAQ 图片索引图片 082 FAQ 图片索引图片 082，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 083 来源：巴别鸟FAQ（用户手册） / word/media/image47.png 静态路径： assets/images/faq/faq 083.png FAQ 图片索引图片 083 FAQ 图片索引图片 083，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 084 来源：巴别鸟FAQ（用户手册） / word/media/image470.png 静态路径： assets/images/faq/faq 084.png FAQ 图片索引图片 084 FAQ 图片索引图片 084，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 085 来源：巴别鸟FAQ（用户手册） / word/media/image48.png 静态路径： assets/images/faq/faq 085.png FAQ 图片索引图片 085 FAQ 图片索引图片 085，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 086 来源：巴别鸟FAQ（用户手册） / word/media/image480.png 静态路径： assets/images/faq/faq 086.png FAQ 图片索引图片 086 FAQ 图片索引图片 086，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 087 来源：巴别鸟FAQ（用户手册） / word/media/image49.png 静态路径： assets/images/faq/faq 087.png FAQ 图片索引图片 087 FAQ 图片索引图片 087，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 088 来源：巴别鸟FAQ（用户手册） / word/media/image490.png 静态路径： assets/images/faq/faq 088.png FAQ 图片索引图片 088 FAQ 图片索引图片 088，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 089 来源：巴别鸟FAQ（用户手册） / word/media/image5.png 静态路径： assets/images/faq/faq 089.png FAQ 图片索引图片 089 FAQ 图片索引图片 089，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 090 来源：巴别鸟FAQ（用户手册） / word/media/image50.png 静态路径： assets/images/faq/faq 090.png FAQ 图片索引图片 090 FAQ 图片索引图片 090，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 091 来源：巴别鸟FAQ（用户手册） / word/media/image500.png 静态路径： assets/images/faq/faq 091.png FAQ 图片索引图片 091 FAQ 图片索引图片 091，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 092 来源：巴别鸟FAQ（用户手册） / word/media/image51.png 静态路径： assets/images/faq/faq 092.png FAQ 图片索引图片 092 FAQ 图片索引图片 092，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 093 来源：巴别鸟FAQ（用户手册） / word/media/image510.png 静态路径： assets/images/faq/faq 093.png FAQ 图片索引图片 093 FAQ 图片索引图片 093，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 094 来源：巴别鸟FAQ（用户手册） / word/media/image52.png 静态路径： assets/images/faq/faq 094.png FAQ 图片索引图片 094 FAQ 图片索引图片 094，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 095 来源：巴别鸟FAQ（用户手册） / word/media/image520.png 静态路径： assets/images/faq/faq 095.png FAQ 图片索引图片 095 FAQ 图片索引图片 095，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 096 来源：巴别鸟FAQ（用户手册） / word/media/image53.png 静态路径： assets/images/faq/faq 096.png FAQ 图片索引图片 096 FAQ 图片索引图片 096，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 097 来源：巴别鸟FAQ（用户手册） / word/media/image530.png 静态路径： assets/images/faq/faq 097.png FAQ 图片索引图片 097 FAQ 图片索引图片 097，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 098 来源：巴别鸟FAQ（用户手册） / word/media/image54.png 静态路径： assets/images/faq/faq 098.png FAQ 图片索引图片 098 FAQ 图片索引图片 098，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 099 来源：巴别鸟FAQ（用户手册） / word/media/image540.png 静态路径： assets/images/faq/faq 099.png FAQ 图片索引图片 099 FAQ 图片索引图片 099，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 100 来源：巴别鸟FAQ（用户手册） / word/media/image55.png 静态路径： assets/images/faq/faq 100.png FAQ 图片索引图片 100 FAQ 图片索引图片 100，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 101 来源：巴别鸟FAQ（用户手册） / word/media/image550.png 静态路径： assets/images/faq/faq 101.png FAQ 图片索引图片 101 FAQ 图片索引图片 101，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 102 来源：巴别鸟FAQ（用户手册） / word/media/image56.jpg 静态路径： assets/images/faq/faq 102.jpg FAQ 图片索引图片 102 FAQ 图片索引图片 102，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 103 来源：巴别鸟FAQ（用户手册） / word/media/image56.png 静态路径： assets/images/faq/faq 103.png FAQ 图片索引图片 103 FAQ 图片索引图片 103，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 104 来源：巴别鸟FAQ（用户手册） / word/media/image560.jpg 静态路径： assets/images/faq/faq 104.jpg FAQ 图片索引图片 104 FAQ 图片索引图片 104，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 105 来源：巴别鸟FAQ（用户手册） / word/media/image57.png 静态路径： assets/images/faq/faq 105.png FAQ 图片索引图片 105 FAQ 图片索引图片 105，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 106 来源：巴别鸟FAQ（用户手册） / word/media/image570.png 静态路径： assets/images/faq/faq 106.png FAQ 图片索引图片 106 FAQ 图片索引图片 106，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 107 来源：巴别鸟FAQ（用户手册） / word/media/image58.png 静态路径： assets/images/faq/faq 107.png FAQ 图片索引图片 107 FAQ 图片索引图片 107，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 108 来源：巴别鸟FAQ（用户手册） / word/media/image580.png 静态路径： assets/images/faq/faq 108.png FAQ 图片索引图片 108 FAQ 图片索引图片 108，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 109 来源：巴别鸟FAQ（用户手册） / word/media/image59.png 静态路径： assets/images/faq/faq 109.png FAQ 图片索引图片 109 FAQ 图片索引图片 109，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 110 来源：巴别鸟FAQ（用户手册） / word/media/image590.png 静态路径： assets/images/faq/faq 110.png FAQ 图片索引图片 110 FAQ 图片索引图片 110，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 111 来源：巴别鸟FAQ（用户手册） / word/media/image6.png 静态路径： assets/images/faq/faq 111.png FAQ 图片索引图片 111 FAQ 图片索引图片 111，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 112 来源：巴别鸟FAQ（用户手册） / word/media/image60.png 静态路径： assets/images/faq/faq 112.png FAQ 图片索引图片 112 FAQ 图片索引图片 112，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 113 来源：巴别鸟FAQ（用户手册） / word/media/image600.png 静态路径： assets/images/faq/faq 113.png FAQ 图片索引图片 113 FAQ 图片索引图片 113，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 114 来源：巴别鸟FAQ（用户手册） / word/media/image61.png 静态路径： assets/images/faq/faq 114.png FAQ 图片索引图片 114 FAQ 图片索引图片 114，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 115 来源：巴别鸟FAQ（用户手册） / word/media/image610.png 静态路径： assets/images/faq/faq 115.png FAQ 图片索引图片 115 FAQ 图片索引图片 115，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 116 来源：巴别鸟FAQ（用户手册） / word/media/image611.png 静态路径： assets/images/faq/faq 116.png FAQ 图片索引图片 116 FAQ 图片索引图片 116，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 117 来源：巴别鸟FAQ（用户手册） / word/media/image62.png 静态路径： assets/images/faq/faq 117.png FAQ 图片索引图片 117 FAQ 图片索引图片 117，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 118 来源：巴别鸟FAQ（用户手册） / word/media/image620.png 静态路径： assets/images/faq/faq 118.png FAQ 图片索引图片 118 FAQ 图片索引图片 118，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 119 来源：巴别鸟FAQ（用户手册） / word/media/image63.png 静态路径： assets/images/faq/faq 119.png FAQ 图片索引图片 119 FAQ 图片索引图片 119，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 120 来源：巴别鸟FAQ（用户手册） / word/media/image630.png 静态路径： assets/images/faq/faq 120.png FAQ 图片索引图片 120 FAQ 图片索引图片 120，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 121 来源：巴别鸟FAQ（用户手册） / word/media/image64.png 静态路径： assets/images/faq/faq 121.png FAQ 图片索引图片 121 FAQ 图片索引图片 121，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 122 来源：巴别鸟FAQ（用户手册） / word/media/image640.png 静态路径： assets/images/faq/faq 122.png FAQ 图片索引图片 122 FAQ 图片索引图片 122，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 123 来源：巴别鸟FAQ（用户手册） / word/media/image65.png 静态路径： assets/images/faq/faq 123.png FAQ 图片索引图片 123 FAQ 图片索引图片 123，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 124 来源：巴别鸟FAQ（用户手册） / word/media/image650.png 静态路径： assets/images/faq/faq 124.png FAQ 图片索引图片 124 FAQ 图片索引图片 124，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 125 来源：巴别鸟FAQ（用户手册） / word/media/image66.png 静态路径： assets/images/faq/faq 125.png FAQ 图片索引图片 125 FAQ 图片索引图片 125，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 126 来源：巴别鸟FAQ（用户手册） / word/media/image660.png 静态路径： assets/images/faq/faq 126.png FAQ 图片索引图片 126 FAQ 图片索引图片 126，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 127 来源：巴别鸟FAQ（用户手册） / word/media/image67.png 静态路径： assets/images/faq/faq 127.png FAQ 图片索引图片 127 FAQ 图片索引图片 127，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 128 来源：巴别鸟FAQ（用户手册） / word/media/image670.png 静态路径： assets/images/faq/faq 128.png FAQ 图片索引图片 128 FAQ 图片索引图片 128，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 129 来源：巴别鸟FAQ（用户手册） / word/media/image68.png 静态路径： assets/images/faq/faq 129.png FAQ 图片索引图片 129 FAQ 图片索引图片 129，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 130 来源：巴别鸟FAQ（用户手册） / word/media/image680.png 静态路径： assets/images/faq/faq 130.png FAQ 图片索引图片 130 FAQ 图片索引图片 130，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 131 来源：巴别鸟FAQ（用户手册） / word/media/image69.png 静态路径： assets/images/faq/faq 131.png FAQ 图片索引图片 131 FAQ 图片索引图片 131，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 132 来源：巴别鸟FAQ（用户手册） / word/media/image690.png 静态路径： assets/images/faq/faq 132.png FAQ 图片索引图片 132 FAQ 图片索引图片 132，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 133 来源：巴别鸟FAQ（用户手册） / word/media/image7.png 静态路径： assets/images/faq/faq 133.png FAQ 图片索引图片 133 FAQ 图片索引图片 133，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 134 来源：巴别鸟FAQ（用户手册） / word/media/image70.png 静态路径： assets/images/faq/faq 134.png FAQ 图片索引图片 134 FAQ 图片索引图片 134，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 135 来源：巴别鸟FAQ（用户手册） / word/media/image700.png 静态路径： assets/images/faq/faq 135.png FAQ 图片索引图片 135 FAQ 图片索引图片 135，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 136 来源：巴别鸟FAQ（用户手册） / word/media/image71.png 静态路径： assets/images/faq/faq 136.png FAQ 图片索引图片 136 FAQ 图片索引图片 136，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 137 来源：巴别鸟FAQ（用户手册） / word/media/image710.png 静态路径： assets/images/faq/faq 137.png FAQ 图片索引图片 137 FAQ 图片索引图片 137，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 138 来源：巴别鸟FAQ（用户手册） / word/media/image711.png 静态路径： assets/images/faq/faq 138.png FAQ 图片索引图片 138 FAQ 图片索引图片 138，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 139 来源：巴别鸟FAQ（用户手册） / word/media/image72.png 静态路径： assets/images/faq/faq 139.png FAQ 图片索引图片 139 FAQ 图片索引图片 139，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 140 来源：巴别鸟FAQ（用户手册） / word/media/image720.png 静态路径： assets/images/faq/faq 140.png FAQ 图片索引图片 140 FAQ 图片索引图片 140，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 141 来源：巴别鸟FAQ（用户手册） / word/media/image73.png 静态路径： assets/images/faq/faq 141.png FAQ 图片索引图片 141 FAQ 图片索引图片 141，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 142 来源：巴别鸟FAQ（用户手册） / word/media/image730.png 静态路径： assets/images/faq/faq 142.png FAQ 图片索引图片 142 FAQ 图片索引图片 142，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 143 来源：巴别鸟FAQ（用户手册） / word/media/image74.png 静态路径： assets/images/faq/faq 143.png FAQ 图片索引图片 143 FAQ 图片索引图片 143，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 144 来源：巴别鸟FAQ（用户手册） / word/media/image740.png 静态路径： assets/images/faq/faq 144.png FAQ 图片索引图片 144 FAQ 图片索引图片 144，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 145 来源：巴别鸟FAQ（用户手册） / word/media/image75.png 静态路径： assets/images/faq/faq 145.png FAQ 图片索引图片 145 FAQ 图片索引图片 145，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 146 来源：巴别鸟FAQ（用户手册） / word/media/image750.png 静态路径： assets/images/faq/faq 146.png FAQ 图片索引图片 146 FAQ 图片索引图片 146，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 147 来源：巴别鸟FAQ（用户手册） / word/media/image76.png 静态路径： assets/images/faq/faq 147.png FAQ 图片索引图片 147 FAQ 图片索引图片 147，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 148 来源：巴别鸟FAQ（用户手册） / word/media/image760.png 静态路径： assets/images/faq/faq 148.png FAQ 图片索引图片 148 FAQ 图片索引图片 148，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 149 来源：巴别鸟FAQ（用户手册） / word/media/image77.png 静态路径： assets/images/faq/faq 149.png FAQ 图片索引图片 149 FAQ 图片索引图片 149，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 150 来源：巴别鸟FAQ（用户手册） / word/media/image770.png 静态路径： assets/images/faq/faq 150.png FAQ 图片索引图片 150 FAQ 图片索引图片 150，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 151 来源：巴别鸟FAQ（用户手册） / word/media/image78.png 静态路径： assets/images/faq/faq 151.png FAQ 图片索引图片 151 FAQ 图片索引图片 151，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 152 来源：巴别鸟FAQ（用户手册） / word/media/image780.png 静态路径： assets/images/faq/faq 152.png FAQ 图片索引图片 152 FAQ 图片索引图片 152，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 153 来源：巴别鸟FAQ（用户手册） / word/media/image79.png 静态路径： assets/images/faq/faq 153.png FAQ 图片索引图片 153 FAQ 图片索引图片 153，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 154 来源：巴别鸟FAQ（用户手册） / word/media/image790.png 静态路径： assets/images/faq/faq 154.png FAQ 图片索引图片 154 FAQ 图片索引图片 154，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 155 来源：巴别鸟FAQ（用户手册） / word/media/image8.png 静态路径： assets/images/faq/faq 155.png FAQ 图片索引图片 155 FAQ 图片索引图片 155，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 156 来源：巴别鸟FAQ（用户手册） / word/media/image80.png 静态路径： assets/images/faq/faq 156.png FAQ 图片索引图片 156 FAQ 图片索引图片 156，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 157 来源：巴别鸟FAQ（用户手册） / word/media/image800.png 静态路径： assets/images/faq/faq 157.png FAQ 图片索引图片 157 FAQ 图片索引图片 157，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 158 来源：巴别鸟FAQ（用户手册） / word/media/image81.png 静态路径： assets/images/faq/faq 158.png FAQ 图片索引图片 158 FAQ 图片索引图片 158，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 159 来源：巴别鸟FAQ（用户手册） / word/media/image810.png 静态路径： assets/images/faq/faq 159.png FAQ 图片索引图片 159 FAQ 图片索引图片 159，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 160 来源：巴别鸟FAQ（用户手册） / word/media/image811.png 静态路径： assets/images/faq/faq 160.png FAQ 图片索引图片 160 FAQ 图片索引图片 160，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 161 来源：巴别鸟FAQ（用户手册） / word/media/image82.png 静态路径： assets/images/faq/faq 161.png FAQ 图片索引图片 161 FAQ 图片索引图片 161，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 162 来源：巴别鸟FAQ（用户手册） / word/media/image820.png 静态路径： assets/images/faq/faq 162.png FAQ 图片索引图片 162 FAQ 图片索引图片 162，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 163 来源：巴别鸟FAQ（用户手册） / word/media/image83.png 静态路径： assets/images/faq/faq 163.png FAQ 图片索引图片 163 FAQ 图片索引图片 163，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 164 来源：巴别鸟FAQ（用户手册） / word/media/image830.png 静态路径： assets/images/faq/faq 164.png FAQ 图片索引图片 164 FAQ 图片索引图片 164，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 165 来源：巴别鸟FAQ（用户手册） / word/media/image84.png 静态路径： assets/images/faq/faq 165.png FAQ 图片索引图片 165 FAQ 图片索引图片 165，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 166 来源：巴别鸟FAQ（用户手册） / word/media/image840.png 静态路径： assets/images/faq/faq 166.png FAQ 图片索引图片 166 FAQ 图片索引图片 166，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 167 来源：巴别鸟FAQ（用户手册） / word/media/image85.png 静态路径： assets/images/faq/faq 167.png FAQ 图片索引图片 167 FAQ 图片索引图片 167，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 168 来源：巴别鸟FAQ（用户手册） / word/media/image850.png 静态路径： assets/images/faq/faq 168.png FAQ 图片索引图片 168 FAQ 图片索引图片 168，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 169 来源：巴别鸟FAQ（用户手册） / word/media/image86.png 静态路径： assets/images/faq/faq 169.png FAQ 图片索引图片 169 FAQ 图片索引图片 169，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 170 来源：巴别鸟FAQ（用户手册） / word/media/image860.png 静态路径： assets/images/faq/faq 170.png FAQ 图片索引图片 170 FAQ 图片索引图片 170，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 171 来源：巴别鸟FAQ（用户手册） / word/media/image87.png 静态路径： assets/images/faq/faq 171.png FAQ 图片索引图片 171 FAQ 图片索引图片 171，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 172 来源：巴别鸟FAQ（用户手册） / word/media/image870.png 静态路径： assets/images/faq/faq 172.png FAQ 图片索引图片 172 FAQ 图片索引图片 172，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 173 来源：巴别鸟FAQ（用户手册） / word/media/image88.png 静态路径： assets/images/faq/faq 173.png FAQ 图片索引图片 173 FAQ 图片索引图片 173，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 174 来源：巴别鸟FAQ（用户手册） / word/media/image880.png 静态路径： assets/images/faq/faq 174.png FAQ 图片索引图片 174 FAQ 图片索引图片 174，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 175 来源：巴别鸟FAQ（用户手册） / word/media/image89.png 静态路径： assets/images/faq/faq 175.png FAQ 图片索引图片 175 FAQ 图片索引图片 175，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 176 来源：巴别鸟FAQ（用户手册） / word/media/image890.png 静态路径： assets/images/faq/faq 176.png FAQ 图片索引图片 176 FAQ 图片索引图片 176，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 177 来源：巴别鸟FAQ（用户手册） / word/media/image9.png 静态路径： assets/images/faq/faq 177.png FAQ 图片索引图片 177 FAQ 图片索引图片 177，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 178 来源：巴别鸟FAQ（用户手册） / word/media/image90.png 静态路径： assets/images/faq/faq 178.png FAQ 图片索引图片 178 FAQ 图片索引图片 178，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 179 来源：巴别鸟FAQ（用户手册） / word/media/image900.png 静态路径： assets/images/faq/faq 179.png FAQ 图片索引图片 179 FAQ 图片索引图片 179，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 180 来源：巴别鸟FAQ（用户手册） / word/media/image91.png 静态路径： assets/images/faq/faq 180.png FAQ 图片索引图片 180 FAQ 图片索引图片 180，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 181 来源：巴别鸟FAQ（用户手册） / word/media/image910.png 静态路径： assets/images/faq/faq 181.png FAQ 图片索引图片 181 FAQ 图片索引图片 181，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 182 来源：巴别鸟FAQ（用户手册） / word/media/image92.png 静态路径： assets/images/faq/faq 182.png FAQ 图片索引图片 182 FAQ 图片索引图片 182，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 183 来源：巴别鸟FAQ（用户手册） / word/media/image920.png 静态路径： assets/images/faq/faq 183.png FAQ 图片索引图片 183 FAQ 图片索引图片 183，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 184 来源：巴别鸟FAQ（用户手册） / word/media/image93.png 静态路径： assets/images/faq/faq 184.png FAQ 图片索引图片 184 FAQ 图片索引图片 184，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 185 来源：巴别鸟FAQ（用户手册） / word/media/image930.png 静态路径： assets/images/faq/faq 185.png FAQ 图片索引图片 185 FAQ 图片索引图片 185，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 186 来源：巴别鸟FAQ（用户手册） / word/media/image94.png 静态路径： assets/images/faq/faq 186.png FAQ 图片索引图片 186 FAQ 图片索引图片 186，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 187 来源：巴别鸟FAQ（用户手册） / word/media/image940.png 静态路径： assets/images/faq/faq 187.png FAQ 图片索引图片 187 FAQ 图片索引图片 187，从 巴别鸟FAQ（用户手册）.docx 抽取。 FAQ 图片索引图片 188 来源：巴别鸟FAQ（用户手册） / word/media/image95.png 静态路径： assets/images/faq/faq 188.png FAQ 图片索引图片 188 FAQ 图片索引图片 188，从 巴别鸟FAQ（用户手册）.docx 抽取。" }, { "lang": "zh", "slug": "maintenance", "title": "维护与发布", "description": "说明如何本地维护、构建、调试和上传 babelwiki 静态目录。", "category": "维护", "top_category": "维护", "keywords": [ "维护", "本地调试", "发布" ], "url": "zh/maintenance.html", "source": "content/zh/maintenance.md", "summary": "维护与发布 本地维护 文档源文件位于 babelwiki/content/zh 和 babelwiki/content/en 。推荐流程是先更新 DOC 目录中的源文档或产品截图，再运行重建脚本生成 Markdown 和 HTML。 本地构建 本地预览 浏览器打开 http://127.0.0.1:8080/ 即可调试，根目录会直接显示中文“概况”文档页。 上传发布 将 babelwiki 整个目录上传到 www.babel.cc 对应目录，使其可通过 https://www.babel.cc/babelwiki/ 访问。上传后建议检查： index.html zh/overview.html llms.txt llms full.txt ai index.json developer api index.json image index.json sitemap.xml", "headings": [ { "level": 1, "title": "维护与发布", "id": "section" }, { "level": 2, "title": "本地维护", "id": "section-2" }, { "level": 2, "title": "本地构建", "id": "section-3" }, { "level": 2, "title": "本地预览", "id": "section-4" }, { "level": 2, "title": "上传发布", "id": "section-5" } ], "images": [], "text": "维护与发布 本地维护 文档源文件位于 babelwiki/content/zh 和 babelwiki/content/en 。推荐流程是先更新 DOC 目录中的源文档或产品截图，再运行重建脚本生成 Markdown 和 HTML。 本地构建 本地预览 浏览器打开 http://127.0.0.1:8080/ 即可调试，根目录会直接显示中文“概况”文档页。 上传发布 将 babelwiki 整个目录上传到 www.babel.cc 对应目录，使其可通过 https://www.babel.cc/babelwiki/ 访问。上传后建议检查： index.html zh/overview.html llms.txt llms full.txt ai index.json developer api index.json image index.json sitemap.xml" }, { "lang": "zh", "slug": "terms", "title": "条款协议", "description": "巴别鸟服务条款的分主题入口。", "category": "条款协议", "top_category": "条款协议", "keywords": [ "条款", "协议", "服务条款" ], "url": "zh/terms.html", "source": "content/zh/terms.md", "summary": "条款协议 条款协议汇总巴别鸟服务形态、双方权利义务、知识产权、保密、风险、违约、法律争议和售后服务相关内容。 条款协议概览：服务条款适用范围、服务形态和阅读入口。 免费服务条款：免费服务注册、信息真实性和用户责任。 企业公有云服务条款：公有云服务开通、时限、升级、续费、终止和订单合同。 企业私有化服务条款：私有云部署、授权时限、维护费、升级和订单合同。 甲方权利和义务：客户账号、管理员、使用行为和安全责任。 服务方权利和义务：服务方管理权限、数据披露边界、条款调整和服务终止权。 知识产权与保密：软件知识产权、商标、数据归属和双方保密义务。 服务风险与免责声明：不可抗力、网络风险、内容责任、用户操作风险和第三方交易风险。 违约责任与服务变更：违约责任、服务变更、中断、终止和条款修改。 法律争议与售后服务：法律适用、争议解决、售后服务、维护、免费服务和 VIP 服务。", "headings": [ { "level": 1, "title": "条款协议", "id": "section" } ], "images": [], "text": "条款协议 条款协议汇总巴别鸟服务形态、双方权利义务、知识产权、保密、风险、违约、法律争议和售后服务相关内容。 条款协议概览：服务条款适用范围、服务形态和阅读入口。 免费服务条款：免费服务注册、信息真实性和用户责任。 企业公有云服务条款：公有云服务开通、时限、升级、续费、终止和订单合同。 企业私有化服务条款：私有云部署、授权时限、维护费、升级和订单合同。 甲方权利和义务：客户账号、管理员、使用行为和安全责任。 服务方权利和义务：服务方管理权限、数据披露边界、条款调整和服务终止权。 知识产权与保密：软件知识产权、商标、数据归属和双方保密义务。 服务风险与免责声明：不可抗力、网络风险、内容责任、用户操作风险和第三方交易风险。 违约责任与服务变更：违约责任、服务变更、中断、终止和条款修改。 法律争议与售后服务：法律适用、争议解决、售后服务、维护、免费服务和 VIP 服务。" }, { "lang": "zh", "slug": "terms-overview", "title": "条款协议概览", "description": "服务条款适用范围、服务形态和阅读入口。", "category": "条款协议", "top_category": "条款协议", "keywords": [ "条款", "条款协议概览" ], "url": "zh/terms-overview.html", "source": "content/zh/terms-overview.md", "summary": "条款协议概览 服务说明 上海画擎信息科技有限公司通过以下几种方式向企业客户提供服务： 域名为bable.cc的网站; 为客户私有部署于客户机房或客户管理的云空间内的巴别鸟私有化系统; 上海画擎信息科技有限公司已经发布的名为“巴别鸟”的桌面客户端程序; 上海画擎信息科技有限公司已经发布的名为“巴别鸟”的智能移动应用程序（包括但不限于iOS，Android系统）。 巴别鸟服务条款（以下简称“服务条款”）适用于巴别鸟中提供的所有应用程序，但当甲方使用巴别鸟某一特定服务时，如该服务另有单独的服务条款、指引或规则，应成为本条款的附加条款，甲方应与本条款一并遵守。 巴别鸟以及功能的正常实现以甲方正确履行管理行为，正确完成系统设置等为前提条件。如甲方违反有关法律法规及本服务条款的规定，须自行承担完全的法律责任、并承担因此给上海画擎信息科技有限公司造成的损失的法律责任。", "headings": [ { "level": 1, "title": "条款协议概览", "id": "section" } ], "images": [], "text": "条款协议概览 服务说明 上海画擎信息科技有限公司通过以下几种方式向企业客户提供服务： 域名为bable.cc的网站; 为客户私有部署于客户机房或客户管理的云空间内的巴别鸟私有化系统; 上海画擎信息科技有限公司已经发布的名为“巴别鸟”的桌面客户端程序; 上海画擎信息科技有限公司已经发布的名为“巴别鸟”的智能移动应用程序（包括但不限于iOS，Android系统）。 巴别鸟服务条款（以下简称“服务条款”）适用于巴别鸟中提供的所有应用程序，但当甲方使用巴别鸟某一特定服务时，如该服务另有单独的服务条款、指引或规则，应成为本条款的附加条款，甲方应与本条款一并遵守。 巴别鸟以及功能的正常实现以甲方正确履行管理行为，正确完成系统设置等为前提条件。如甲方违反有关法律法规及本服务条款的规定，须自行承担完全的法律责任、并承担因此给上海画擎信息科技有限公司造成的损失的法律责任。" }, { "lang": "zh", "slug": "terms-free-saas", "title": "免费服务条款", "description": "免费服务注册、信息真实性和用户责任。", "category": "条款协议", "top_category": "条款协议", "keywords": [ "条款", "免费服务条款" ], "url": "zh/terms-free-saas.html", "source": "content/zh/terms-free-saas.md", "summary": "免费服务条款 巴别鸟免费服务（基于SaaS） 在了解并同意本条款的基础上，甲方可以申请注册巴别鸟账户使用巴别鸟免费服务。巴别鸟免费服务内容包括免费版基本功能、限期体验功能等，详情内容以巴别鸟网站公示为准。 甲方了解并同意在注册巴别鸟时，提供真实有效的企业信息（如联系人、联系电话，电子邮箱地址等）。上海画擎信息科技有限公司有权停止提供虚假注册信息用户的巴别鸟免费服务使用权限。 甲方清楚并同意甲方及甲方用户在注册使用巴别鸟免费服务前必须同时无条件接受本服务条款所有条款项的约束，并对违反国家法律规定及本服务条款所产生的一切后果承担法律责任。", "headings": [ { "level": 1, "title": "免费服务条款", "id": "section" } ], "images": [], "text": "免费服务条款 巴别鸟免费服务（基于SaaS） 在了解并同意本条款的基础上，甲方可以申请注册巴别鸟账户使用巴别鸟免费服务。巴别鸟免费服务内容包括免费版基本功能、限期体验功能等，详情内容以巴别鸟网站公示为准。 甲方了解并同意在注册巴别鸟时，提供真实有效的企业信息（如联系人、联系电话，电子邮箱地址等）。上海画擎信息科技有限公司有权停止提供虚假注册信息用户的巴别鸟免费服务使用权限。 甲方清楚并同意甲方及甲方用户在注册使用巴别鸟免费服务前必须同时无条件接受本服务条款所有条款项的约束，并对违反国家法律规定及本服务条款所产生的一切后果承担法律责任。" }, { "lang": "zh", "slug": "terms-public-cloud", "title": "企业公有云服务条款", "description": "公有云服务开通、时限、升级、续费、终止和订单合同。", "category": "条款协议", "top_category": "条款协议", "keywords": [ "条款", "企业公有云服务条款" ], "url": "zh/terms-public-cloud.html", "source": "content/zh/terms-public-cloud.md", "summary": "企业公有云服务条款 巴别鸟企业公有云版服务（基于SaaS） 开通企业公有云版服务。甲方购买巴别鸟企业公有云版时，可联系相关客服并完成付款，支付成功后甲方所购买的巴别鸟企业公有云版即会及时开通。 企业公有云版服务时限。企业公有云本服务时限是甲方购买巴别鸟企业公有云版服务时选择的“购买时长”为准，单位为“年”。 企业公有云版服务升级。上海画擎信息科技有限公司升级巴别鸟企业公有云版服务时，甲方所使用的公有云版将会自动升级，无需支付其他费用。 企业公有云版服务续费。甲方以公有云的方式所购买的巴别鸟企业公有云版服务时限到期前1个月，上海画擎信息科技有限公司将通知甲方续缴费用，续费价格以上海画擎信息科技有限公司官方公布为准。如甲方在企业公有云版服务时限期满后仍未续费，上海画擎信息科技有限公司即停止对甲方提供已到期部分的企业公有云版服务。 企业公有云版服务终止。甲方在其购买的巴别鸟企业公有云版服务到期后仍未续费，则视为甲方自动放弃巴别鸟企业公有云版服务，甲方已到期企业公有云版服务即被限制或锁定。 巴别鸟订单合同。甲方在购买巴别鸟企业公有云版服务后，可与上海画擎信息有限公司签订[巴别鸟企业版（公有云）软件使用许可协议]。[巴别鸟企业版（公有云）软件使用许可协议]是上海画擎信息有限公司与甲方之间关于巴别鸟服务与费用的书面协定。", "headings": [ { "level": 1, "title": "企业公有云服务条款", "id": "section" } ], "images": [], "text": "企业公有云服务条款 巴别鸟企业公有云版服务（基于SaaS） 开通企业公有云版服务。甲方购买巴别鸟企业公有云版时，可联系相关客服并完成付款，支付成功后甲方所购买的巴别鸟企业公有云版即会及时开通。 企业公有云版服务时限。企业公有云本服务时限是甲方购买巴别鸟企业公有云版服务时选择的“购买时长”为准，单位为“年”。 企业公有云版服务升级。上海画擎信息科技有限公司升级巴别鸟企业公有云版服务时，甲方所使用的公有云版将会自动升级，无需支付其他费用。 企业公有云版服务续费。甲方以公有云的方式所购买的巴别鸟企业公有云版服务时限到期前1个月，上海画擎信息科技有限公司将通知甲方续缴费用，续费价格以上海画擎信息科技有限公司官方公布为准。如甲方在企业公有云版服务时限期满后仍未续费，上海画擎信息科技有限公司即停止对甲方提供已到期部分的企业公有云版服务。 企业公有云版服务终止。甲方在其购买的巴别鸟企业公有云版服务到期后仍未续费，则视为甲方自动放弃巴别鸟企业公有云版服务，甲方已到期企业公有云版服务即被限制或锁定。 巴别鸟订单合同。甲方在购买巴别鸟企业公有云版服务后，可与上海画擎信息有限公司签订[巴别鸟企业版（公有云）软件使用许可协议]。[巴别鸟企业版（公有云）软件使用许可协议]是上海画擎信息有限公司与甲方之间关于巴别鸟服务与费用的书面协定。" }, { "lang": "zh", "slug": "terms-private-cloud", "title": "企业私有化服务条款", "description": "私有云部署、授权时限、维护费、升级和订单合同。", "category": "条款协议", "top_category": "条款协议", "keywords": [ "条款", "企业私有化服务条款" ], "url": "zh/terms-private-cloud.html", "source": "content/zh/terms-private-cloud.md", "summary": "企业私有化服务条款 巴别鸟企业私有化服务 上海画擎信息科技有限公司仅提供巴别鸟部署及巴别鸟私有化授权服务。部署所需的硬件及环境由甲方准备及维护。 部署企业私有云版本。甲方购买巴别鸟企业私有云版本后，由上海画擎信息科技根据甲方签订合同时所选的项目（详见协议附件 服务订单）进行部署及相关调试。 企业私有云版服务时限。企业私有云版本的账号授权时限为终生授权，客服支持及升级服务按年为单位。购买后第一年免维护费用。 企业私有云版服务升级。上海画擎信息科技有限公司升级巴别鸟企业私有云版服务时，会第一时间通知甲方，由甲方决定是否升级，如甲方同意升级即进行远程升级服务，无需支付其他费用。 企业私有云版维护费。巴别鸟企业私有云版本为终生授权，但如果需要上海画擎信息科技有限公司提供相应的培训、答疑、及系统bug修正、系统升级服务则需支付维护费用。购买企业私有云版本后的第一年免维护费，第二年开始甲方需要按合同约定支付相应的维护费用。如逾期甲方没有支付维护费用，将视为甲方放弃本服务条款的所有服务。 巴别鸟订单合同。甲方在购买巴别鸟企业私有云版服务后，可与上海画擎信息有限公司签订[巴别鸟私有云软件使用许可协议]。[巴别鸟私有云软件使用许可协议]是上海画擎信息有限公司与甲方之间关于巴别鸟服务与费用的书面协定。", "headings": [ { "level": 1, "title": "企业私有化服务条款", "id": "section" } ], "images": [], "text": "企业私有化服务条款 巴别鸟企业私有化服务 上海画擎信息科技有限公司仅提供巴别鸟部署及巴别鸟私有化授权服务。部署所需的硬件及环境由甲方准备及维护。 部署企业私有云版本。甲方购买巴别鸟企业私有云版本后，由上海画擎信息科技根据甲方签订合同时所选的项目（详见协议附件 服务订单）进行部署及相关调试。 企业私有云版服务时限。企业私有云版本的账号授权时限为终生授权，客服支持及升级服务按年为单位。购买后第一年免维护费用。 企业私有云版服务升级。上海画擎信息科技有限公司升级巴别鸟企业私有云版服务时，会第一时间通知甲方，由甲方决定是否升级，如甲方同意升级即进行远程升级服务，无需支付其他费用。 企业私有云版维护费。巴别鸟企业私有云版本为终生授权，但如果需要上海画擎信息科技有限公司提供相应的培训、答疑、及系统bug修正、系统升级服务则需支付维护费用。购买企业私有云版本后的第一年免维护费，第二年开始甲方需要按合同约定支付相应的维护费用。如逾期甲方没有支付维护费用，将视为甲方放弃本服务条款的所有服务。 巴别鸟订单合同。甲方在购买巴别鸟企业私有云版服务后，可与上海画擎信息有限公司签订[巴别鸟私有云软件使用许可协议]。[巴别鸟私有云软件使用许可协议]是上海画擎信息有限公司与甲方之间关于巴别鸟服务与费用的书面协定。" }, { "lang": "zh", "slug": "terms-customer-obligations", "title": "甲方权利和义务", "description": "客户账号、管理员、使用行为和安全责任。", "category": "条款协议", "top_category": "条款协议", "keywords": [ "条款", "甲方权利和义务" ], "url": "zh/terms-customer-obligations.html", "source": "content/zh/terms-customer-obligations.md", "summary": "甲方权利和义务 甲方权利和义务 甲方必须自行配备连通互联网和使用电信企业公有云版业务所需的设备，自行担负个人上网或第三方（包括但不限于电信或移动通信提供商）收取的通讯费、信息费、流量费等有关费用。如涉及电信企业公有云版服务的，我们建议您与您的电信企业公有云版服务提供商确认相关的费用问题。 甲方不得利用巴别鸟发送或传输任何妨碍社会治安或非法、虚假、骚扰性、侮辱性、恐吓性、伤害性、破坏性、挑衅性、淫秽色情等内容的信息。 甲方须自行负责对其系统内部成员用户进行管理，如：增加（删减）账号、设置用户密码等管理行为。甲方须指派专门的系统管理员对其巴别鸟账号进行维护管理，甲方管理员的行为由甲方负责，管理行为的后果以及责任由甲方承担。 甲方及其甲方用户应维持自身账号及密码的机密安全，甲方及其甲方用户不得将其账号或密码转让或出借第三方使用。上海画擎信息科技有限公司无法对第三方非法或未经甲方授权使用其账号及密码的行为做出甄别，因此上海画擎信息科技有限公司不承担任何责任。在此，甲方同意并承诺做到： 当甲方及甲方用户的账号及密码遭到未获授权的使用，或者发生其他任何安全问题时，甲方立即通知上海画擎信息科技有限公司。 甲方及甲方用户每次使用巴别鸟系统完毕后，点击退出巴别鸟。 甲方已清楚明白，巴别鸟仅可作为甲方内部使用，除非另有协议，甲方不得将其甲方账号进行转让、分销、或者买卖。", "headings": [ { "level": 1, "title": "甲方权利和义务", "id": "section" } ], "images": [], "text": "甲方权利和义务 甲方权利和义务 甲方必须自行配备连通互联网和使用电信企业公有云版业务所需的设备，自行担负个人上网或第三方（包括但不限于电信或移动通信提供商）收取的通讯费、信息费、流量费等有关费用。如涉及电信企业公有云版服务的，我们建议您与您的电信企业公有云版服务提供商确认相关的费用问题。 甲方不得利用巴别鸟发送或传输任何妨碍社会治安或非法、虚假、骚扰性、侮辱性、恐吓性、伤害性、破坏性、挑衅性、淫秽色情等内容的信息。 甲方须自行负责对其系统内部成员用户进行管理，如：增加（删减）账号、设置用户密码等管理行为。甲方须指派专门的系统管理员对其巴别鸟账号进行维护管理，甲方管理员的行为由甲方负责，管理行为的后果以及责任由甲方承担。 甲方及其甲方用户应维持自身账号及密码的机密安全，甲方及其甲方用户不得将其账号或密码转让或出借第三方使用。上海画擎信息科技有限公司无法对第三方非法或未经甲方授权使用其账号及密码的行为做出甄别，因此上海画擎信息科技有限公司不承担任何责任。在此，甲方同意并承诺做到： 当甲方及甲方用户的账号及密码遭到未获授权的使用，或者发生其他任何安全问题时，甲方立即通知上海画擎信息科技有限公司。 甲方及甲方用户每次使用巴别鸟系统完毕后，点击退出巴别鸟。 甲方已清楚明白，巴别鸟仅可作为甲方内部使用，除非另有协议，甲方不得将其甲方账号进行转让、分销、或者买卖。" }, { "lang": "zh", "slug": "terms-company-obligations", "title": "服务方权利和义务", "description": "服务方管理权限、数据披露边界、条款调整和服务终止权。", "category": "条款协议", "top_category": "条款协议", "keywords": [ "条款", "服务方权利和义务" ], "url": "zh/terms-company-obligations.html", "source": "content/zh/terms-company-obligations.md", "summary": "服务方权利和义务 上海画擎信息科技有限公司权利和义务 上海画擎信息科技有限公司有义务为甲方提供巴别鸟的管理权限，便于甲方自行为甲方用户进行系统相关设置。 上海画擎信息科技有限公司不得公开、编辑或对外披露甲方及甲方用户存储在巴别鸟的任何数据。但下列情况除外 事先得到甲方书面明确授权； 根据中华人民共和国国家安全机构、公安部门的要求或根据相关的法律程序或维护社会公共利益的要求。 如甲方或甲方用户违反本服务条款的约定或法律规定，上海画擎信息科技有限公司有权中断或终止巴别鸟服务并且剩余服务费用不进行退还。 上海画擎信息科技有限公司有权根据实际情况调整或更新本服务条款内容，上海画擎信息科技有限公司有义务通知甲方并在巴别鸟官方网页或巴别鸟系统作出明显公示。修改后的条款一旦公布即有效代替原有条款，新条款适用于所有巴别鸟免费服务用户以及所有巴别鸟企业公有云版服务用户。 如甲方及甲方用户违反国家法律法规或本服务条款，上海画擎信息科技有限公司有权立即停止向甲方提供服务而不需承担任何责任。", "headings": [ { "level": 1, "title": "服务方权利和义务", "id": "section" } ], "images": [], "text": "服务方权利和义务 上海画擎信息科技有限公司权利和义务 上海画擎信息科技有限公司有义务为甲方提供巴别鸟的管理权限，便于甲方自行为甲方用户进行系统相关设置。 上海画擎信息科技有限公司不得公开、编辑或对外披露甲方及甲方用户存储在巴别鸟的任何数据。但下列情况除外 事先得到甲方书面明确授权； 根据中华人民共和国国家安全机构、公安部门的要求或根据相关的法律程序或维护社会公共利益的要求。 如甲方或甲方用户违反本服务条款的约定或法律规定，上海画擎信息科技有限公司有权中断或终止巴别鸟服务并且剩余服务费用不进行退还。 上海画擎信息科技有限公司有权根据实际情况调整或更新本服务条款内容，上海画擎信息科技有限公司有义务通知甲方并在巴别鸟官方网页或巴别鸟系统作出明显公示。修改后的条款一旦公布即有效代替原有条款，新条款适用于所有巴别鸟免费服务用户以及所有巴别鸟企业公有云版服务用户。 如甲方及甲方用户违反国家法律法规或本服务条款，上海画擎信息科技有限公司有权立即停止向甲方提供服务而不需承担任何责任。" }, { "lang": "zh", "slug": "terms-ip-confidentiality", "title": "知识产权与保密", "description": "软件知识产权、商标、数据归属和双方保密义务。", "category": "条款协议", "top_category": "条款协议", "keywords": [ "条款", "知识产权与保密" ], "url": "zh/terms-ip-confidentiality.html", "source": "content/zh/terms-ip-confidentiality.md", "summary": "知识产权与保密 知识产权、保密条款 巴别鸟的所有权和基于巴别鸟的所有知识产权（包括但不限于专利权、商标权、著作权、计算机软件著作权等）归上海画擎信息科技有限公司所有。上海画擎信息科技有限公司对巴别鸟的所有权不包括甲方及甲方用户存放在巴别鸟服务器中的数据。 上海画擎信息科技有限公司、上海画擎信息科技有限公司logo、巴别鸟的logo等，以及其他上海画擎信息科技有限公司标志及产品、服务名称、均为上海画擎信息科技有限公司之商标（以下简称“上海画擎信息科技有限公司标识”）。未经上海画擎信息科技有限公司事先书面同意，甲方不得将上海画擎信息科技有限公司标识以任何方式展示或使用或作其他处理，也不得向他人表明甲方有权展示、使用、或其他有权处理上海画擎信息科技有限公司标识的行为。 甲方有义务保护上海画擎信息科技有限公司的知识产权不受第三方侵犯。甲方及甲方用户不得使用、复制巴别鸟有关的软件、数据，不得允许第三方窃取巴别鸟的任何数据与软件。数据不包括甲方及甲方用户在巴别鸟服务器中存放的数据。 甲方和上海画擎信息科技有限公司任何一方对在合作过程中所获知的对方及上海画擎信息科技有限公司未向社会公开的技术及商业秘密均有保密的义务，未经对方书面许可，任何一方不得将其泄露给第三方，否则应承担违约责任并赔偿损失。", "headings": [ { "level": 1, "title": "知识产权与保密", "id": "section" } ], "images": [], "text": "知识产权与保密 知识产权、保密条款 巴别鸟的所有权和基于巴别鸟的所有知识产权（包括但不限于专利权、商标权、著作权、计算机软件著作权等）归上海画擎信息科技有限公司所有。上海画擎信息科技有限公司对巴别鸟的所有权不包括甲方及甲方用户存放在巴别鸟服务器中的数据。 上海画擎信息科技有限公司、上海画擎信息科技有限公司logo、巴别鸟的logo等，以及其他上海画擎信息科技有限公司标志及产品、服务名称、均为上海画擎信息科技有限公司之商标（以下简称“上海画擎信息科技有限公司标识”）。未经上海画擎信息科技有限公司事先书面同意，甲方不得将上海画擎信息科技有限公司标识以任何方式展示或使用或作其他处理，也不得向他人表明甲方有权展示、使用、或其他有权处理上海画擎信息科技有限公司标识的行为。 甲方有义务保护上海画擎信息科技有限公司的知识产权不受第三方侵犯。甲方及甲方用户不得使用、复制巴别鸟有关的软件、数据，不得允许第三方窃取巴别鸟的任何数据与软件。数据不包括甲方及甲方用户在巴别鸟服务器中存放的数据。 甲方和上海画擎信息科技有限公司任何一方对在合作过程中所获知的对方及上海画擎信息科技有限公司未向社会公开的技术及商业秘密均有保密的义务，未经对方书面许可，任何一方不得将其泄露给第三方，否则应承担违约责任并赔偿损失。" }, { "lang": "zh", "slug": "terms-risk-disclaimer", "title": "服务风险与免责声明", "description": "不可抗力、网络风险、内容责任、用户操作风险和第三方交易风险。", "category": "条款协议", "top_category": "条款协议", "keywords": [ "条款", "服务风险与免责声明" ], "url": "zh/terms-risk-disclaimer.html", "source": "content/zh/terms-risk-disclaimer.md", "summary": "服务风险与免责声明 服务风险、免责声明 甲方已经清楚并明白，巴别鸟服务仅依其当前所呈现的状况提供，巴别鸟服务涉及到互联网及移动数据通讯等服务，可能会受到各个环节不稳定因素的影响。因此服务存在因上述不可抗力、洪水、地震、台风、火灾与其他天灾、战争、计算机病毒或黑客攻击、基于计算机系统和网络的各种犯罪行为、政府行为、系统出错或不稳定、用户所在位置、用户关机、GSM网络不稳定、3G网络不稳定、互联网络线路故障、骨干网通信线路故障原因等造成的服务中断或不能满足用户要求并因此给甲方带来损失的风险。甲方需承担上述风险，上海画擎信息科技有限公司不提供对巴别鸟适销性、适用性、可靠性、及时性、安全性、完整性、无病毒及无错误的任何明示或默认保证，不承担因此而对甲方造成的任何直接、间接、附带、衍生或惩罚性的赔偿。 如巴别鸟所发生的故障影响到甲方的正常使用，上海画擎信息科技有限公司承诺在第一时间内与相关单位配合，及时处理进行修复。上海画擎信息科技有限公司保留不经事前通知为维修保养、升级或其他目的暂停巴别鸟任何部分的权利。在此期间发生的服务暂停现象，或由于网络通路的偶然阻塞造成服务应用故障，属正常情况，不可视为上海画擎信息科技有限公司违约。 甲方同意，甲方与甲方用户经由巴别鸟以上传、张贴、发送即时消息、电子邮件或其他方式传送的资讯、资料、文字、软件、音乐、音频、照片、图片、视频、信息、资源链接、用户登记资料或其他资料（以下简称“内容”），均由甲方与甲方用户承担完全的法律责任，上海画擎信息科技有限公司无须承担任何直接、间接、或连带责任。由于上海画擎信息科技有限公司无法控制经由巴别鸟传送的内容，也无法对用户", "headings": [ { "level": 1, "title": "服务风险与免责声明", "id": "section" } ], "images": [], "text": "服务风险与免责声明 服务风险、免责声明 甲方已经清楚并明白，巴别鸟服务仅依其当前所呈现的状况提供，巴别鸟服务涉及到互联网及移动数据通讯等服务，可能会受到各个环节不稳定因素的影响。因此服务存在因上述不可抗力、洪水、地震、台风、火灾与其他天灾、战争、计算机病毒或黑客攻击、基于计算机系统和网络的各种犯罪行为、政府行为、系统出错或不稳定、用户所在位置、用户关机、GSM网络不稳定、3G网络不稳定、互联网络线路故障、骨干网通信线路故障原因等造成的服务中断或不能满足用户要求并因此给甲方带来损失的风险。甲方需承担上述风险，上海画擎信息科技有限公司不提供对巴别鸟适销性、适用性、可靠性、及时性、安全性、完整性、无病毒及无错误的任何明示或默认保证，不承担因此而对甲方造成的任何直接、间接、附带、衍生或惩罚性的赔偿。 如巴别鸟所发生的故障影响到甲方的正常使用，上海画擎信息科技有限公司承诺在第一时间内与相关单位配合，及时处理进行修复。上海画擎信息科技有限公司保留不经事前通知为维修保养、升级或其他目的暂停巴别鸟任何部分的权利。在此期间发生的服务暂停现象，或由于网络通路的偶然阻塞造成服务应用故障，属正常情况，不可视为上海画擎信息科技有限公司违约。 甲方同意，甲方与甲方用户经由巴别鸟以上传、张贴、发送即时消息、电子邮件或其他方式传送的资讯、资料、文字、软件、音乐、音频、照片、图片、视频、信息、资源链接、用户登记资料或其他资料（以下简称“内容”），均由甲方与甲方用户承担完全的法律责任，上海画擎信息科技有限公司无须承担任何直接、间接、或连带责任。由于上海画擎信息科技有限公司无法控制经由巴别鸟传送的内容，也无法对用户的使用行为进行全面监控，因此不保证甲方内容的合法性、正确性、完整性、真实性或品质。如甲方的内容存在侵犯第三人著作权的可能，上海画擎信息科技有限公司将遵循国家的法律法规进行处理。 甲方已经清楚地了解并知道，甲方用户如需使用巴别鸟必须接受本服务条款。在甲方部分或全部甲方用户不接受或不同意本服务条款而导致无法使用巴别鸟时，甲方仍同意向上海画擎信息科技有限公司支付服务费用。 甲方承诺因甲方、甲方系统管理员、甲方用户对巴别鸟的错误操作而对甲方所造成的任何损失负完全责任。这些错误操作包括但不限于甲方系统管理员误删了甲方用户所造成的数据丢失、甲方用户错误地删除了甲方企业网盘中的共享数据等。 甲方及甲方用户已经清楚地了解到，其通过巴别鸟与商家或个人进行任何形式的通讯或商业往来、或参与促销活动，包含相关商品或服务之付款及交付，以及达成的其他任何相关条款、条件、保证或证明，完全为甲方及甲方成员与商家及其他个人之间的行为。除有关法律有明文规定要求上海画擎信息科技有限公司承担责任以外，甲方因上述任何交易或上述商家或个人而遭受的任何性质的损失或损害，上海画擎信息科技有限公司均不予负责。" }, { "lang": "zh", "slug": "terms-liability-change", "title": "违约责任与服务变更", "description": "违约责任、服务变更、中断、终止和条款修改。", "category": "条款协议", "top_category": "条款协议", "keywords": [ "条款", "违约责任与服务变更" ], "url": "zh/terms-liability-change.html", "source": "content/zh/terms-liability-change.md", "summary": "违约责任与服务变更 违约责任 甲方使用巴别鸟前须清楚了解并同意本服务条款，并对违反国家法律规定及本服务条款所产生的一切后果承担法律责任。 因上海画擎信息科技有限公司过失而造成甲方在使用巴别鸟过程中遭受损失的，甲方有权以书面形式通知上海画擎信息科技有限公司终止其巴别鸟账号。经上海画擎信息科技有限公司查证如甲方之情况属实，上海画擎信息科技有限公司会在10个工作日内按约收取服务起始日至服务终止日期间产生的费用后将甲方余款（如有）退还。 服务变更、中断或终止及服务条款修改 巴别鸟的所有权和运作权、一切解释权归上海画擎信息科技有限公司所有。上海画擎信息科技有限公司有权随时根据国家有关法律、法规的变化、行业的发展及公司经营状况和经营策略的调整等情况修改本条款。 上海画擎信息科技有限公司修改巴别鸟服务或本服务条款时，应根据本条款6.4项执行。甲方有义务对最新的服务条款进行仔细阅读并确认，当发生有关争议时，以最新的服务条款为准。 上海画擎信息科技有限公司保留对巴别鸟中所有应用程序的价格调整权及产品试用期的调整权。 如发生下列任何一种情况，上海画擎信息科技有限公司有权随时中断或终止向甲方提供服务或禁用某些甲方用户账号而无须通知甲方： 甲方违反本服务条款的规定； 按照国家主管部门的要求； 其他上海画擎信息科技有限公司认为是符合整体服务需求的特殊情形。", "headings": [ { "level": 1, "title": "违约责任与服务变更", "id": "section" } ], "images": [], "text": "违约责任与服务变更 违约责任 甲方使用巴别鸟前须清楚了解并同意本服务条款，并对违反国家法律规定及本服务条款所产生的一切后果承担法律责任。 因上海画擎信息科技有限公司过失而造成甲方在使用巴别鸟过程中遭受损失的，甲方有权以书面形式通知上海画擎信息科技有限公司终止其巴别鸟账号。经上海画擎信息科技有限公司查证如甲方之情况属实，上海画擎信息科技有限公司会在10个工作日内按约收取服务起始日至服务终止日期间产生的费用后将甲方余款（如有）退还。 服务变更、中断或终止及服务条款修改 巴别鸟的所有权和运作权、一切解释权归上海画擎信息科技有限公司所有。上海画擎信息科技有限公司有权随时根据国家有关法律、法规的变化、行业的发展及公司经营状况和经营策略的调整等情况修改本条款。 上海画擎信息科技有限公司修改巴别鸟服务或本服务条款时，应根据本条款6.4项执行。甲方有义务对最新的服务条款进行仔细阅读并确认，当发生有关争议时，以最新的服务条款为准。 上海画擎信息科技有限公司保留对巴别鸟中所有应用程序的价格调整权及产品试用期的调整权。 如发生下列任何一种情况，上海画擎信息科技有限公司有权随时中断或终止向甲方提供服务或禁用某些甲方用户账号而无须通知甲方： 甲方违反本服务条款的规定； 按照国家主管部门的要求； 其他上海画擎信息科技有限公司认为是符合整体服务需求的特殊情形。" }, { "lang": "zh", "slug": "terms-law-support", "title": "法律争议与售后服务", "description": "法律适用、争议解决、售后服务、维护、免费服务和 VIP 服务。", "category": "条款协议", "top_category": "条款协议", "keywords": [ "条款", "法律争议与售后服务" ], "url": "zh/terms-law-support.html", "source": "content/zh/terms-law-support.md", "summary": "法律争议与售后服务 法律及争议解决 本服务条款要与国家相关法律、法规一致，如发生与相关法律、法规条款有相抵触的内容，抵触部分以法律、法规条款为准。 如双方发生任何争议但又不能友好协商的，任何一方均可向上海画擎信息科技有限公司住所地上海市有管辖权的人民法院提起诉讼。 巴别鸟提供的售后服务 巴别鸟采用一对一专人服务模式，有专门的客户经理负责为客户提供服务。 维护单位名称：上海画擎信息科技有限公司 软件维护期为一年，第二年后客户需缴纳维护费，进入下一轮软件维护期，如客户维护期满后不缴纳服务费，客户可以继续使用系统，但我司不再提供维护服务，直到补齐年服务费用后，服务继续。 维护期内上海画擎负责提供合同范围内软件版本的程序代码及系统配置信息的维护、支持，不包含因业务改变等因素所引起的新增功能开发。如中日友好医院需要新增功能及因业务流程变更带来的客户化开发服务，则由双方协商确定实施方案。 免费服务内容和范围 巴别鸟对所有付费客户提供产品使用周期中的终身免费质保服务，包括： 5 24小时的电话技术支持服务 7 24小时的紧急灾备处理服务 免费在线培训，系统使用指导 BUG第一时间反馈，快速处理 软件更新及升级服务 针对用户数量超过1000人的企业用户，巴别鸟提供了产品使用周期中的终身免费VIP服务，包括： 付费客户的所有免费服务 系统搭建及需求对应解决方案咨询服务 代客户初始化系统及完成配置 免费数据迁移服务（小于10TB的数据） 每年免费上门培训1次（用户数超过10000每年有三次免费上门培训机会） 专属大客户经理责任制服务 针对私有化用户，在用户正常缴纳年服务费的前提下，享受如下免费服务", "headings": [ { "level": 1, "title": "法律争议与售后服务", "id": "section" } ], "images": [], "text": "法律争议与售后服务 法律及争议解决 本服务条款要与国家相关法律、法规一致，如发生与相关法律、法规条款有相抵触的内容，抵触部分以法律、法规条款为准。 如双方发生任何争议但又不能友好协商的，任何一方均可向上海画擎信息科技有限公司住所地上海市有管辖权的人民法院提起诉讼。 巴别鸟提供的售后服务 巴别鸟采用一对一专人服务模式，有专门的客户经理负责为客户提供服务。 维护单位名称：上海画擎信息科技有限公司 软件维护期为一年，第二年后客户需缴纳维护费，进入下一轮软件维护期，如客户维护期满后不缴纳服务费，客户可以继续使用系统，但我司不再提供维护服务，直到补齐年服务费用后，服务继续。 维护期内上海画擎负责提供合同范围内软件版本的程序代码及系统配置信息的维护、支持，不包含因业务改变等因素所引起的新增功能开发。如中日友好医院需要新增功能及因业务流程变更带来的客户化开发服务，则由双方协商确定实施方案。 免费服务内容和范围 巴别鸟对所有付费客户提供产品使用周期中的终身免费质保服务，包括： 5 24小时的电话技术支持服务 7 24小时的紧急灾备处理服务 免费在线培训，系统使用指导 BUG第一时间反馈，快速处理 软件更新及升级服务 针对用户数量超过1000人的企业用户，巴别鸟提供了产品使用周期中的终身免费VIP服务，包括： 付费客户的所有免费服务 系统搭建及需求对应解决方案咨询服务 代客户初始化系统及完成配置 免费数据迁移服务（小于10TB的数据） 每年免费上门培训1次（用户数超过10000每年有三次免费上门培训机会） 专属大客户经理责任制服务 针对私有化用户，在用户正常缴纳年服务费的前提下，享受如下免费服务： 付费客户的所有免费服务 免费系统升级及更新服务，纯内网用户（内网无法连接到互联网）每年有1次免费上门升级及更新服务 代客户初始化系统及完成配置 服务器性能优化及排障 每年免费上门培训1次，无限次远程培训 针对基于巴别鸟系统的二次开发及功能定制用户，享受如下免费服务： 付费客户的所有免费服务 二次开发部分的功能质保，Bug修正 接口及功能联调服务 二次开发部分代码及接口的注释及指导服务，方便用户再开发 完工验收后，在我方成本可承受范围内的微调及功能修正（非Bug） 收费服务 在现有系统上的再开发工作，按需求评估开发工时及难度系数，按工时结算。 产品设计服务。根据客户新需求帮助客户进行产品架构、功能及交互的设计，并提供技术咨询。 有偿上门培训及调试服务。免费额度用完或不符合免费上门服务条件的用户可以付费申请。费用为 2000元1人1天 及报销到达用户处所的交通费用（高铁及当地出租车） 提供的服务项目包括如下： 序号 服务项目 服务内容 1 首访服务 由服务人员主动开展首次访问服务 2 回访服务 由服务人员主动开展回访的服务 3 软件常规运行维护服务 所购买软件的程序代码维护，如修补软件缺陷、安装调试软件补丁 4 系统升级技术咨询 当系统升级时提供的技术咨询服务 5 软件升级通知 当该版本软件升级时，及时通知客户 服务方式包括： 热线支持：通过400热线电话向客户提供技术问题解答； E MAIL支持：通过E MAIL解答客户问题； 远程维护：通过远程方式对客户环境下的巴别鸟软件进行调试。客户需提供远程维护所需的环境，否则，由客户承担因此而引起的售后响应时间滞后的责任。 现场服务：如属远程维护所不能解决的问题，我司会承担现场服务。属于应用软件自身问题带来的现场服务，属于免费维护范围。 故障处理流程 当客户使用中出现问题： 立即拨打专职客户经理电话（或微信联系），可以解决的立即解决； 不能立即解决的，立即联系技术人员对接，由技术人员远程协助客户解决； 仍然没有解决，反馈给客户经理，由客户经理安排技术人员上门服务。 其他 如本服务条款中的任何条款无论因何种原因完全或部分无效或不具有执行力，本服务条款的其余条款仍应有效且具有约束力，并且努力使该规定反映之意向具备效力。 本服务条款构成甲方与上海画擎信息科技有限公司之全部协议，规范您对本服务之使用，并取代您先前与上海画擎信息科技有限公司达成的全部协议。但在甲方使用相关服务、或使用第三方提供的内容或软件时，亦应遵从所适用之附加条款及权利。 上海画擎信息科技有限公司保留本服务条款之所有解释权。 甲方（盖章）： 乙方（盖章）： 甲方代表（签字）： 乙方代表（签字）： 日 期： 日 期：" } ] }