Documentación de EvoX
  • Producto
  • Precios
  • Documentación
  • Mercado
Volver a EvoMap
Iniciar sesiónRegistrarse
Overview
Practice cases
Features
Configuration
Configuration basics
Permissions and approvalsNetwork and background operationFeature switches
Developers
Security
Administration
Overview
Practice cases
Features
Configuration
Configuration basics
Permissions and approvalsNetwork and background operationFeature switches
Developers
Security
Administration
Documentación de EvoX/Product/Permissions and approvals

Permissions and approvals

Before starting, define what a task may access, what it may do, and which actions need another confirmation. Preferences, project rules, and plugin installation are not substitutes for authorization.

Define task boundaries

Open Settings > Permissions. Choose whether to maintain global rules, rules for one workspace, or inspect organization rules.

ObjectScopeAvailable action
Global rulesUser-level tool and path rulesAdd or revoke a rule
WorkspaceTrust and project rules for a directoryEnter an absolute path and manage its trust and rules
Organization rulesAdministrator-managed rulesInspect them; personal rules cannot override them
Policy simulatorA hypothetical tool, target path, and workspace requestInspect the decision, source scope, and reason without running a tool

Put project-specific rules in that workspace instead of broadening them into global allowances. Folder trust, simulated policy decisions, and actual runtime approvals are separate states.

Actual approvals and rule previews

The Permissions panel manages tool, path, and workspace rules and provides a policy simulator.

Rule management is a preview and does not govern actual tool-call approvals. An allow rule, trusted workspace, or successful simulation is not authorization for automatic execution.

During a task, check the conversation's approval mode, actual confirmation requests, and execution results.

In the global-rule form or a workspace’s rule form, enter a tool, path pattern, and effect, then add the rule:

FieldWhat to enter
ToolAn actual tool name such as Bash; * means any tool
Path globA target pattern such as /work/docs/**, replaced with your real path
EffectAllow, ask, or deny

Provide at least a tool or a path. A tool limits the capability; a path limits the target. Avoid unnecessary wildcards. After adding, inspect the stored tool, path, and effect. To change an existing rule, revoke it and add the corrected rule; confirm the target before revoking and run the simulator again.

Enter an absolute directory path for a workspace. After adding and trusting it, manage its project rules within that entry. Turning trust off differs from forgetting a workspace: forgetting removes its trust setting and project rules, not disk files.

Review a confirmation request

  1. Read the proposed action and target, including file paths, account, and remote resources.
  2. Check that it belongs to the task. For sending, publishing, deleting, or spending, inspect content and effects separately.
  3. Approve or decline according to the task; an Allow entry in a rule list does not replace this confirmation.
  4. After declining, narrow the scope to a draft or read-only check and continue within the authorized boundary.

Organization policies

Organization policies control capabilities in managed environments. Personal preferences do not override organization restrictions, and resetting personal rules does not remove managed policies.

Reset deletes custom personal rules and directory-trust settings while leaving organization rules and project files intact. Revoke one entry when only one rule needs removal. Inspect diagnostic exports for sensitive paths, content, or identifiers before sharing.

Start with a verifiable task

Check rules with the simulator before running a real command:

  1. Enter a tool such as Bash, an absolute target-file path, and its workspace.
  2. Test the rules and inspect Allow, Ask, or Deny together with the source scope and reason.
  3. Compare one target inside the workspace with one outside it to check the intended boundary.
  4. Repeat the same inputs after revoking or changing a rule.

Simulation runs no commands, changes no files, and does not alter actual approvals. For an unexpected result, inspect path matching, workspace trust, and organization rules instead of broadening wildcards.

See Permissions for task authorization examples and Network and background operation for connection diagnostics.

AnteriorMessaging channelsSiguienteNetwork and background operation