Tools

Tools turn AI into a coworker

A chat can answer. A digital employee can work because it has controlled access to the right tools.

Access follows the role

A support employee needs email and knowledge. A sales employee needs CRM and follow-up tasks. A back-office employee needs documents and structured data.

Start with the smallest useful toolchain

The first productive role should not receive every possible integration. It usually starts with the systems needed for one repeatable workflow: where the request arrives, where context is stored, where the result is documented and where a person approves critical steps.

Each connection needs an operating rule

Before a system is connected, CODIKI defines what may be read, what may be written, which actions stay draft-only and which events need a handover. This keeps the employee useful without turning tool access into uncontrolled automation.

Read access is different from write access

Reading a CRM record, creating a draft email and changing an ERP status are very different risk levels. CODIKI separates those permissions explicitly. Many first roles start read-only or draft-only and receive write access only where the process, logging and approval path are clear.

Errors must have a path

Every tool can fail: an API is unavailable, a field is missing, a customer record is ambiguous or a document is outdated. A digital employee needs a defined fallback: ask for clarification, hand over to a person, retry later or stop and log the case.

Secrets never belong in prompts

API keys, mail credentials and database passwords must be managed outside the conversation context. The employee receives scoped tool access through the operating environment, not raw secrets in instructions.

Security is designed in

The employee gets only the access required for the role. Sensitive actions can require human approval or stay read-only.