Configuration is additive, not a permission shortcut. A global plugin, personal preference, memory entry, or workspace file never grants access that the current user or Agent service account does not already have.
Configuration model
The current instruction and verified tool results remain authoritative for the task. Imported preferences and memory provide context; they do not override safety, approval, identity, or exact runtime evidence.
Administrator: configure AI for the instance
Open Settings → AI Agents → Configuration as an Instance Administrator. These settings establish the tenant-wide baseline used by the Assistant and autonomous Agents.Global instructions
Global instructions express stable organization-wide expectations, for example:- use the tenant’s approved Components and plugins before ad-hoc alternatives;
- preserve backward compatibility for published Endpoints;
- redact customer identifiers from user-visible reports;
- validate changes in Sandbox before activation;
- return an operation identifier for production mutations.
Default plugins
Select active registry plugins that should be available by default for AI work in the instance. Instance defaults and explicitly selected plugins remain subject to plugin status, capability policy, operation safety, permissions, and approval requirements. A disabled, deleted, unavailable, or policy-blocked plugin cannot become executable merely because it is configured as a default. Use Plugin instructions—up to 4,000 characters—for tenant guidance such as which system is authoritative, when a plugin is preferred, or which operations require extra care. Keep capability-specific schemas and authentication in the plugin definition rather than duplicating them in prose.Runtime output limits
The administrator can set the maximum output-token ceiling for AI execution from 10,240 to 128,000. This is an upper bound, not a target: individual models, tasks, and runtime policies can use less. Increasing the ceiling can help large code reviews or long structured deliverables, but it also increases latency and cost exposure. Prefer better task scope, references, and artifact workflows before raising it globally.Memory policy
The tenant memory policy controls whether memory is enabled, the default recall count, and the retention horizon exposed by the instance configuration.
Memory is selective. RevoEngine does not convert every answer, tool output, or conversation into durable memory. See Memory and workspaces.
Storage retention
Instance AI settings also define default retention for private database exports and Agent-created artifacts. Both accept 1–3,650 days. Expiration archives the file first; permanent removal remains governed by the instance garbage-collection policy. Use shorter retention for reproducible temporary exports and longer retention only when the artifact is required as durable operational evidence. An Agent can still select a more appropriate explicit lifecycle when policy and the Storage contract allow it.AI security rules
Administrators can provide up to 8,000 characters of security guidance, selection terms, and blocked runtime tool names. Use this layer for tenant-wide restrictions such as credentials, customer data, regulated records, or forbidden external mutations. Security guidance complements—not replaces—roles, ACLs, service-account permissions, plugin safety metadata, and approval classification. Test both an allowed and a denied example after changing this configuration.User: configure personal Assistant defaults
Open Settings → Assistant. These preferences belong to the signed-in human account and shape new interactive Assistant messages; they do not redefine an autonomous Agent.
Personal custom instructions are useful for stable preferences:
Per-turn overrides
The composer can override model, reasoning, planner behavior, or plugin selection for the current work. A per-turn choice changes that execution context without rewriting the saved account default. Work mode, persona, and custom instructions remain account-level response preferences until changed in Settings → Assistant. For example, keep Medium + Standard + Balanced as a daily default, then select High + Review required + Coding for a risky cross-Component migration.Agent: define durable behavior
An autonomous Agent adds another stable layer that personal Assistant preferences do not provide:- a named identity, mission, responsibilities, operating principles, and success criteria;
- a least-privilege service account used for runtime authorization;
- Agent instructions, model, reasoning, planning, and execution mode;
- Agent-owned and policy-managed plugin attachments;
- default and per-tool permission policy;
- concurrency, child-run, retry, inbox, and trigger behavior;
- scoped Agent memory and a governed workspace root.
Memory: durable knowledge, not conversation history
Use memory only for concise information that should remain useful after the current thread or run:
Memory use remains bounded by scope, access, and instance policy. Deleted memory is excluded from use and can be restored through its governed lifecycle.
Do not store secrets, full documents, transient progress, raw tool output, or reasoning in memory. Store exact content in Storage and keep only a concise convention or reference in memory.
Workspace: the Agent’s durable filesystem
Every successfully created Agent receives a managed workspace or can be linked to an authorized existing Storage folder. The linked root is an enforced boundary:- listing, recursive name search, bounded reads, folder creation, upload, and artifact writes stay inside the root;
- the workspace root itself cannot be mutated by the Agent;
- another Agent’s managed root cannot be attached as an ordinary shared folder;
- ordinary Explorer writes outside the root retain their normal permission and approval policy;
- downloads and administrative workspace operations still require authenticated Agent access.
Organize concurrent work
Use a predictable structure when an Agent delegates or resumes work:Example enterprise setup
1
Set the tenant baseline
Add global engineering and data-handling instructions, attach the approved CRM and billing plugins, configure memory and artifact retention, and block prohibited external tools.
2
Let users personalize presentation
Each engineer selects a work mode, persona, default reasoning level, planner behavior, and concise custom instructions without changing tenant governance.
3
Create a reconciliation Agent
Assign a finance service account, define the reconciliation mission, attach only finance capabilities, and start with review-required mutations.
4
Use scoped state
Keep stable ledger conventions in Agent or Workspace memory, source files and reports in the Agent workspace, and active progress in the durable run checkpoint.
5
Validate the boundaries
Run one allowed read, one approval-gated write, one blocked operation, one memory recall, and one workspace artifact flow. Inspect the same run in Activity and Trace.
Governance checklist
- Keep global instructions stable, short, and tenant-specific.
- Attach only active, reviewed default plugins.
- Treat plugin defaults as capability availability, not authorization.
- Keep personal preferences out of organization-wide policy.
- Use a dedicated service account for every production Agent responsibility.
- Store knowledge in memory and exact files in the workspace.
- Define retention for memory, exports, and Agent-created artifacts.
- Test allowed, approval-required, and denied operations after policy changes.
- Review Agent workspace ACLs before linking an existing folder.
- Correlate changes and runs through Activity, Trace, and durable execution history.
Assistant
Work in supervised, persistent threads.
Agent configuration
Configure one autonomous Agent and its policy.
Memory and workspaces
Choose the correct durable state boundary.
Instance settings
Review all instance-wide controls.