Connecting AI to an ERP creates an expectation that staff can read and change work through conversation. This project includes a request to use Codex from another computer with the appropriate ERP account. I see that as more than adding a chat window. The design must establish who can read company information, what they may change and how a prepared request differs from an executed operation. An owner handing the system to staff needs both convenience and a readable account of responsibility.
AI access and business-system identity are separate
Being able to use an AI tool does not establish authority to read the ERP's company records. The preserved remote design separates ERP account approval and the identity of the connected computer. It describes approval under the person's own ERP permissions rather than copying somebody else's login files. If several people share one account, their actions may share an identity too. Individual attribution therefore begins with account policy, not merely the text shown beside an AI response.
Administrators, staff and read-only users can have different permitted operations. Hiding an interface button is insufficient; the server must check the actual account and current authority. Account suspension and permission changes also need a defined effect on existing connections. Assuming a connection keeps its original permissions indefinitely would separate the AI channel from the business's ordinary user-management rules.
Reading, preparation and execution make different promises
Reading site status, preparing an address change and saving that change are different actions. The archived arrangement makes prepared changes and execution results separately inspectable. Joining the requested target with current and proposed values makes the intended operation understandable. Fluent text does not establish that an identifier or revision is correct, so the server still needs to validate the target and basis of the request.
If a document changed after it was read, an old prepared request should not blindly apply. Similar names must not substitute another partner or another issuing business. A system can define confirmation behavior for a clearly authorized operation, but should not expand that authority to unrelated changes. Convenient conversation should preserve an exact target and one intended operation, rather than accelerate execution by guessing through ambiguous business context.
Registration is not proof of a completed connection
Adding a server address is one step. Discovering authentication, obtaining the person's ERP approval and reading actual connection identity with issued permissions are further steps. The supplied remote acceptance record distinguishes server activation and isolated checks from another PC's outstanding real login. I retain that boundary instead of turning deployment evidence into a claim that every other computer has completed setup and use.
Preserving existing connections is part of the work too. Adding one ERP should not overwrite unrelated tools or their login settings. Inspect an existing connection with the same name before changing it. Explain whether web logout and revoking one computer are separate actions. Staff should be able to disconnect the intended connection without unexpectedly interrupting another person's work or believing that a broader revocation happened when it did not.
An embedded AI service is another capability boundary
Later archived discussion investigates using subscription-based AI inside the ERP website. Connecting business APIs to an AI client differs from obtaining provider authority to execute AI on the server. The records distinguish implemented foundations, provider registration or approval and actual response success. Login or an application prepared for submission does not establish that embedded server-side AI is active. This is a description of the dated project state, not a claim about current product entitlements.
This article uses preserved remote-connection notes and inspection records. I did not install another PC, log into the operating account or execute a business change. For another implementation, review synthetic read-only and editing accounts, permission revocation, reconnection and stale prepared changes. A system that lets the owner issue simple instructions needs especially clear identity, target and outcome records underneath. Conversational convenience should make work easier to request without making its authority or result harder to establish.