Business waits three months for IT scheduling and builds a registration form by dragging fields. Low-code wins. Three months later: forty tables, copied permissions, customer phones in personal spreadsheets, finance numbers that do not reconcile. The problem is not low-code—it is missing boundaries: which flows business may configure, which IT must control.
Clear boundaries make low-code an accelerator. No boundaries make it a shadow-system incubator.
What Business Can Configure
Good self-service flows affect only one department, can be rolled back, and do not touch legal-entity data or external channels: department inspections, meeting notes, temp sign-ups, internal knowledge logs. Fields may change, but accounts must use company directory and data must land in managed space—not personal drives.
- No sensitive fields: customer ID, bank cards, cost price, formulas.
- No direct write access to inventory, ledger, or payroll.
- No interfaces to public email, customs, banks, or e-commerce platforms.
- Before launch: one business owner and one IT guardian—guardian reviews only permissions and backup.
What IT Must Control
Master data codes, role-permission models, audit logs, external interfaces, and cross-department money and inventory documents must go through change control. Low-code may let business draw forms, but the publish button stays with IT. The XYN digital intelligence system separates configurable flows from controlled master data: business edits its nodes, not company-wide codes and permissions. Internal tools can grow without one mis-click rewriting the ledger.
Draw boundaries before issuing low-code accounts. Issue accounts first and add boundaries later—shadow tables are already running.
