Approvals & data
Decide what an agent may see, what it may do and who reviews the result. Treat those as separate decisions.
On this page
Access is not permission to act.#
Access defines the information or tools an agent can use. Approval defines which proposed actions need a person’s decision.
For example, reading meeting notes to prepare a follow-up and sending that follow-up to a customer are separate permissions. The planned workflow is to prepare the action, wait for approval where required and then return the result.
Make the approval meaningful.#
For each workflow, decide what the reviewer needs to inspect:
- The proposed action and the exact destination or recipient.
- The information behind it, including linked sources and missing details.
- The change it will make, and what happens if approval is withheld.
Keep human review around customer-facing work, consequential changes and decisions where an error is costly. AI can miss context or produce an incorrect answer.
Use only the context the task needs.#
Start with a limited set of documents and tool access. Decide who owns that information, whether it can be shared with the selected services and when access should be reviewed.
Before involving sensitive company data, establish your requirements for retention, deletion, access management and provider agreements. Send specific requirements to contact@crevox.io; do not assume that every requirement is already met.
Know which services process the work.#
ChatGPT and Grok are planned model choices. The selected model provider may process the context needed for a task. Connected tools may also receive the data required for an action.
Mac execution is a planned option alongside cloud execution. Running an agent on a Mac does not mean its AI model is offline or that context never leaves the device.
Model training settings, processing and retention are different matters. The rules depend on the actual account and connection. See the provider controls and primary sources.
Separate product evaluation from this website.#
The live website runs a waitlist. It collects your signup and, if you choose, survey answers. Its privacy policy describes that data separately from the planned product.
For a team evaluation, read the security and control overview and share the requirements that would prevent your team from adopting Crevox. We will distinguish confirmed behavior from work still planned.