Verify who’s asking
A business request needs context: which company is being served and which connection is authorized for that company. Gateway policies check company status and connector assignments. This establishes the boundary for the request before a configured tool is used.
Give each connection a defined purpose
Allowed tools and destinations are configured explicitly. Reading information and making changes are treated as separate permissions. During setup, we discuss what information a workflow needs, which actions are in scope, and where approval or review belongs.
Keep company boundaries visible
Company-specific access is central to the gateway design. Connector assignments are checked against the company they belong to, including rejecting assignments across company boundaries. The protections and permissions needed for each connected system are reviewed as part of its configuration.
Keep a record of requests
Gateway request and usage records help administrators review activity, understand denials, and assess how configured connections are used. This visibility supports operational oversight. Record availability and review procedures depend on the connection and the agreed setup.
Treat human review as part of the workflow
An AI-generated answer or draft may need checking before it is used. We define review points with the customer, particularly around changes to business systems and actions with external effects. The appropriate controls depend on the work being performed and the permissions actually enabled.
Ask specific security questions before connecting
Which data is needed? Which tools can the workflow call? Can it modify records? Who can approve an action? What activity can an administrator review? We welcome these questions during scoping so that the proposed workflow and its boundaries are clear. This page describes our approach; it is not a claim of third-party certification or a guarantee that every integration has identical controls.