Modules, permissions and integration boundaries EN

Understand how configured capabilities shape the workspace without confusing module visibility, permission and external-system authority.

Kaduno can expose different combinations of business capabilities without treating each combination as a separate application. Module metadata helps shape the workspace and supported operations. That is distinct from a person's permission to perform an action, and distinct again from an external provider's authority.

This is a source-reviewed conceptual explanation dated 13 November 2026, not proof of activation, enforcement or performance in your production environment. No module-count, bundle-size or latency benchmark is presented.

From configuration to an available operation

Licence + store configuration + dependencies
                     |
                     v
             Active capabilities
                /          \
               v            v
       Workspace surfaces   Operation checks
                                  |
                   Identity + store + permissions
                                  |
                           Allowed operation
                                  |
                     Configured external flow
                                  |
                 Provider's account and own rules

The branches matter: removing a menu and refusing a request are different jobs. This diagram is not a deployment topology. Different interfaces have their own contracts; it does not assert that every check runs in this precise sequence.

Module activation is not a user role

The active feature set is derived from licensing, runtime/store configuration and module dependencies. Metadata is used by navigation, settings, dashboards and capability selection. Dependencies can affect what must be enabled together. The administrator should review the resulting configuration, not just a checkbox.

The API includes module checks, but the reviewed implementation also distinguishes foundation functions, separately licensed capabilities and controlled platform operations. Some enforcement has rollout settings. A visible menu, a hidden menu or an advertised module is therefore insufficient evidence that an operation is allowed or denied in the installed release.

Before promising a particular module combination, verify licensing, dependencies, activation, role, required provider agreements and the operation's actual response. Turning a module off is not a substitute for revoking an account or credential.

Interfaces are not interchangeable credentials

InterfaceAccess to establishCheck before writes
Signed-in administrationUser identity, organisation/store membership and roleRequired role, selected store, operation and active capability
REST integrationStore-scoped key with the endpoint's permissionsCorrect store, explicit scopes, module/setup requirements and error contract
MCP assistantConnected identity/key, store, available tools and applicable agent policyTool contract, action risk, client confirmation behaviour and actual result

Do not copy a server-side REST key into browser code or assume it is a login session. Do not grant a wildcard scope merely because a feature is missing from a menu. The API exercise begins with reads and checks the store before doing more.

What changes when an assistant asks?

Kai's policy can restrict tool groups, action prefixes and risk levels. Tool selection and policy checks are implemented in code; a prompt alone is not an access-control boundary. A client cannot be assumed to implement every confirmation mechanism merely because it understands MCP.

A read, a proposed write and an approved execution are different states. Confirm which actions require approval in the selected client and configuration, and verify the result before repeating a consequential action. This article does not claim every write always produces a confirmation card or that all risk settings are enabled by default.

Use a permitted read, a write whose approval is withheld, and a deliberately denied operation as separate controlled acceptance scenarios. These are proposed tests, not fabricated transcripts of completed checks. Do not submit real payments, orders or invitations to demonstrate the boundary without specific authorisation.

External systems remain external

Provider connections, the accounting hub, PullPush, REST APIs and webhooks can serve different handovers. Not every integration passes through PullPush, and an available API does not imply a ready-made connector. PullPush is in beta.

For a customer's own provider account, store-scoped credentials identify the intended connection. Missing customer credentials must not be treated as permission to use another customer's account. Where supported, a channel-specific credential can take precedence over a credential for the same store.

Selected centrally supplied services use separately governed platform keys. They are not replacement credentials for customer-owned payment, freight or accounting accounts. Confirm each service's account, activation, billing and processing terms.

Data sent to a model provider or external system crosses another processing boundary. The application's store isolation does not establish that provider's retention, location, training policy or contractual terms. Request the applicable provider information before transmitting personal data.

Document the handover, not just the connector name

For each flow, record the data owner, source/destination, field mapping, identity, credentials, permitted actions, correlation/idempotency mechanism where available, error handling and operational owner. A delivery status does not by itself prove correct business processing or exactly-once execution.

Test denied access and uncertain outcomes as well as successful delivery. A timeout can happen after a provider has acted; inspect the destination before retrying. Visma order-export verification shows how to distinguish a sales order from payment, shipment and invoice acceptance.

What still needs evidence

Before acceptance, obtain the deployed release/configuration and observed results for the required module combination and interfaces. Performance comparisons need controlled fixtures, repeatable scripts and reported limitations. This article does not supply those measurements or certify production controls.

Continue with store and permission boundaries, the integration directory and the conceptual architecture map.