Known Limitations in ORIA Reasoner

Administrative Setup

• Requires admin setup: ORIA Reasoner is disabled until an admin configures a Model Group for it. This is set once at the work-area level, not per user — see Before You Start.

Session and Tool Behavior

• Tools are opt-in per session: no tool is enabled by default, and tool selections do not carry over between sessions.

• Institutional Memory scope is opt-out, not opt-in: sessions default to every domain your profile can access. Narrow it deliberately when scope matters.

• Personal-domain memory writes are silent by default: enable Ask me before saving anything if you want to review everything Oria commits to your personal memory.

Permissions and Governance

• Three tool categories are permission-gated: Ontology Actions, MCP Collections, and Connected Applications. The visibility of these tabs is dynamically filtered based on your user profile and subscription level.
• Expected behavior: If you don't have the necessary access configured, these sections will not be displayed or will intentionally appear empty. This is not a system error, but a security restriction.
• Double validation (Plan vs. Permissions): Functionalities are restricted by both your profile permissions and your plan level. If you are missing a tool, please verify your subscription level before opening a support ticket.

⚠️

Missing a category? Contact your ARPIA administrator directly (not Technical Support), as each category requires specific permission assignments for your user.

Configuration and Setup

• Databases requires a second step: the database must be created and attached from the tool's ⚙ icon after the tool is added. The tool is present but has nothing behind it until you do this.

• Standing instructions cannot widen scope. They shape how Oria works, not what it can reach — scope is set only in the Expert's or session's panel.

Artifact and Session State

• Expert reference files affect existing sessions. Adding a shared file changes the context available to sessions already created in that Expert.

• Scheduled Tasks: the scheduling engine is not yet active. Scheduled definitions are saved but will only begin running once the engine is turned on.

When in Doubt

Before filing a ticket, check:

1. Is the tool enabled in Session Tools?
2. Is the relevant ontology node added in Ontology Nodes?
3. Is your seat plan sufficient for this capability? (See Plan Requirements)
4. Do you need admin to configure something? (See Before You Start)