Skip to content

Access and credentials

This page explains how our forward-deployed engineers and the agents they build get access to your systems, why every account is named and scoped, and how access is removed.

  1. We ask in writing. Our engineers send your IT manager or ERP administrator one request per system. It names the system, read or write, the engineer or agent that needs it, the reason and the end date.
  2. You create the account. Your IT team creates it in your own systems, under your password, sign-in and device rules.
  3. We check the scope. The engineer signs in and confirms that the account reaches what the request listed. If it reaches more, we tell you so that you can narrow it.
  4. The account goes on the access inventory. This is the list of every account our engineers and agents hold, with its scope, its purpose and its end date. Your IT manager can ask for it at any time.

These steps cover accounts in your own systems. Two accounts can sit outside them: the AI model provider account and the hosting account. Who holds each during the engagement is agreed in your contract, and if either is ours, it moves to you at handover. Stages and terms lists what your contract records.

Stage Access our engineers ask for
Discovery Sprint Read access to the ERP data, and a view of the spreadsheets and shared inboxes the work runs through. No write access to the ERP.
Embedded Build The same, plus write access for each workflow when it is ready to write back, through an interface the ERP supports. A service account for each agent.
Operate & Automate What the engineers on call need to run, monitor and support the software. Accounts of engineers who have left your engagement are removed.

Each engineer has one account per system, in their own name. We do not use a shared login, a generic vendor account or an employee’s login.

  • Your logs show which person did what.
  • Removing one engineer does not lock out another.
  • No password gets passed around, because none is shared.

Our engineers do not ask your people for their passwords. If someone offers to log an engineer in under their own name to save time, the engineer says no and sends a request.

Each agent has its own service account, separate from any person’s, with only the access its workflow needs.

Three rules apply to every service account:

  • One agent, one account. The audit trail and your ERP’s own log both show which agent did what.
  • The account’s secrets are kept out of code, documents and email.
  • Your IT team can disable the account at any time. That cuts the agent off from the system, whatever else is happening.

Guardrails and limits covers an agent’s limits and its stop switch.

Access is removed when the need for it ends. Four events trigger it.

Event What is removed
An engineer leaves your engagement That engineer’s accounts, on their last day
An agent is retired That agent’s service account
A stage ends and the next one does not start Every account our engineers hold
A handover to another team is complete Every account our engineers hold in your systems. Service accounts for agents you keep running stay, under your control. An AI model provider account or hosting account that was ours moves to you.

The steps are the same each time:

  1. We send your IT manager the accounts to remove, taken from the access inventory.
  2. Your IT team disables them. You do not need our cooperation to do it.
  3. Any secret the departing person could have known is changed.
  4. Badges and keys go back to your site contact.