Build a Permissioned Internal App with NocoBase
Configure NocoBase collections, role-scoped actions, and a tested workflow in a staging app.
Identify the NocoBase version, enabled plugins, data source, and approved staging app. Pick a concrete record such as an equipment request, and write its collection schema before configuring screens. Define fields, required values, allowed states, requester and approver relationships, and any tenant or department boundary. Use synthetic data and one independent fixture per user role. Decide what should happen when an association is deleted or no approver exists. ## Key Points - [NocoBase collection modeling](https://nocode.docs.nocobase.com/data-sources/data-modeling/collection) - [NocoBase ACL configuration](https://nocode.docs.nocobase.com/ai-builder/acl) - [NocoBase collection events](https://nocode.docs.nocobase.com/workflow/triggers/collection)
skilldb get automation-workflow-services-skills/nocobaseFull skill: 31 linesBuild a Permissioned Internal App with NocoBase
Model one internal request
Identify the NocoBase version, enabled plugins, data source, and approved staging app. Pick a concrete record such as an equipment request, and write its collection schema before configuring screens. Define fields, required values, allowed states, requester and approver relationships, and any tenant or department boundary. Use synthetic data and one independent fixture per user role. Decide what should happen when an association is deleted or no approver exists.
Build the smallest list and detail pages that demonstrate the task. The requester should be able to submit and view their own requests. An approver may need a department queue and the right to review a subset. Define a role matrix for create, read, update and approval actions. Hiding a button helps the UI communicate policy, but server-side collection and action permissions must enforce the actual boundary.
Configure and inspect the workflow
Choose the documented trigger for a record transition. Keep the workflow scoped to the intended collection and fields. Specify the approved effect, such as writing a separate decision record or setting an assignment. Use an explicit status check or unique linkage so an update performed by the workflow cannot keep starting it. If actions use a service identity, record which record scope that identity can access.
Test the workflow in the staging app before enabling external messaging or irreversible steps. Inspect the workflow run record for input, branch choice, outcome and resulting row. Avoid putting private form values into general logs. Determine how the configured version handles retry and concurrent runs. When no native step guarantees uniqueness, use a supported database constraint, action idempotency, or an operator reconciliation path before automating writes.
Verify from both sides of the permission boundary
Test as a requester and approver rather than relying on the administrator UI. Confirm the intended record appears for each user. Try a different department's record and a direct call through the supported interface with insufficient role. Inspect the database or app view after a denied action. Repeat the trigger and verify a single durable decision.
Keep the schema, permission settings, app version, workflow definition and results together. Document how a maintainer can disable or update the workflow without leaving existing requests ambiguous. Move production settings only through the organization's reviewed deployment path.
References
Install this skill directly: skilldb add automation-workflow-services-skills
Related Skills
Pipedream
Build serverless event-driven workflows with Pipedream using triggers, Node.js/Python steps, and data stores. Configure HTTP endpoints, cron schedules, and app integrations with built-in authentication and state management.
Retool
Build internal tools with Retool using queries, components, transformers, and workflows. Configure resource connections, JavaScript transformers, and event-driven UI logic for admin panels and dashboards.
Build a Guarded Slack Workflow
Configure a Slack Workflow Builder form and test role boundaries, step results, and repeated delivery in an approved test channel.
Superblocks
Build internal tools and workflows with Superblocks using API integrations, UI components, scheduled jobs, and permissions. Configure backend logic, frontend applications, and role-based access control for enterprise-grade admin panels.
Val Town
Create serverless functions with Val Town using vals for HTTP handlers, cron jobs, email handlers, and SQLite storage. Configure public and private vals with TypeScript, leveraging the built-in runtime for rapid API prototyping.
Windmill
Build scripts, flows, and apps with Windmill using TypeScript and Python runtimes. Configure approval steps, schedules, error handlers, and resource types for developer-centric workflow automation.