NocoBase provides plugins for users, authentication, permissions, files, notifications, Agents and other common application features. This section covers what each plugin does, how to configure it, and how to use its pages, components, APIs, services or Skills in your application.
Use the topics below to find the plugins you need. For shared installation, registration, update and removal procedures, see Manage plugins.
Find plugins by function
This section covers 21 plugins. Related features are grouped by topic, while other plugins have individual entries. Each guide covers capabilities, scenarios, implementation, and AI development constraints in four chapters.
| Feature | Usage guides | Main uses |
|---|---|---|
| Users and authentication | User management, Authentication, API keys | Manage users, sign in and authenticate API requests |
| Permissions and data access | Permission management, Default data access, Sharing rules, Restriction rules | Control permitted operations and access to records |
| Database explorer | Database explorer | Inspect database connections, tables and fields |
| Files | Files | Upload, store and access files |
| Notifications | Notifications, Notification providers, In-app notifications, Web push | Configure notification channels, deliver notifications and integrate inboxes and browser push |
| Send email, synchronize mailboxes and extend mail services | ||
| Agents | Agents | Configure a model API or connect an Agent on a machine for conversations and task execution |
| Knowledge base | Knowledge base | Manage document spaces, versions, search and change reviews |
| Approvals | Approvals | Configure approval policies and handle outcomes |
| Scheduled tasks | Scheduled tasks | Declare schedules, inspect execution records and enable or disable tasks |
| Template printing | Template printing | Use Skills to implement DOCX and PDF template printing |
| Localization | Localization | Integrate localization and application language switching |
| Application foundation | Application foundation | Inspect the Core capabilities used by an application and their runtime information |
Before integration
Check the application's actual registrations and installed versions. Installation does not enable a plugin. Some plugins also require configuration factories or application-owned data, pages and permissions.
Paths such as /client and /server in each guide refer to that package's public exports. Page and HTTP paths are relative to the application mount: an application at /main serves /api/users at /main/api/users. Consult the running application's /api/swagger/docs or /api/swagger for complete request, response and access contracts.
Read a plugin's usage guide
Each plugin guide follows four chapters:
- Capabilities: the problem, supplied pages, components, APIs, services or Skills, and application responsibilities.
- Scenarios and examples: a business need, development prompts for a Coding Agent, usage steps and completion criteria.
- Key principles and implementation: integration areas, code and configuration changes, interface changes and important mechanisms.
- AI development constraints and verification: plugin-specific boundaries, common mistakes and acceptance requirements.
Development prompts target a Coding Agent working in the current application directory. Have it read AGENTS.md, application rules and relevant Skills shipped with installed versions first. Where no development Skill exists, use public interfaces, types and documentation. Chapter four addresses reliable AI-assisted integration; it does not require the plugin itself to have AI features. See Continue developing your app and Testing for shared workflows.
Plugins provide different kinds of capabilities. Template printing supplies implementation guidance. User management supplies administration APIs and an invitation page, while the application owns its administration UI. Knowledge base and Application foundation provide registrable pages. Each guide explains ownership of pages, data and business logic.
These guides were checked against source on 2026-10-28, using main-repository revision 015404ecd and the commercial approval plugin's public contracts. Agents has a separately verified application baseline, screenshots and source download. Installed versions may differ. Verification steps describe checks for the consuming application; they do not claim that every plugin integration was executed while writing these guides.
Related documentation
- Manage plugins: install, register, update and remove plugins.
- Plugin index: look up full package names, repositories and inclusion in the default template.
- Develop plugins: learn when and how to create your own plugin.