Once published, they appear in Navigator as a Quick Panel, Quick Action, or Quick Section, giving end users a ready-made AI tool without needing to open Researcher directly. An App is a packaged version of a template. An org admin configures the experience once (what the AI does, what it looks like, who can use it), publishes it, and it becomes available to users across Navigator.
Where to access Apps
Apps are managed from the org admin area of Evo Researcher: Evo Researcher → Org Admin → Apps Only users with the correct role will see this section in the sidebar.
Who can access Apps
Access to the Apps section is role-based. There are two distinct roles.
Role | What they can do |
App Author | Create, edit, and delete apps |
App Publisher | Publish, unpublish, and manage who can see an app |
Both roles can see the Apps section. The buttons and actions available depend on which role the user holds. A user can hold both roles. These roles are assigned by an org admin in the Users section.
What Apps do
An App defines the full experience a user gets when they launch it from Navigator. During setup, the author configures:
Name and description: how the app appears in Navigator
Template: the underlying Researcher template that powers the AI behaviour
Surface type: whether it appears as a Quick Panel, Quick Action, or Quick Section
Panel size: small, medium, or large (for Actions and Sections)
Mobile: whether the app is also deployed to the Evo mobile app
Feature toggles: which capabilities are available to the user inside the app, e.g. file uploads, connectors, conversations, artifacts
Manage access: whether the app is visible to the whole organisation, specific users, or specific groups
An app can be in one of two states:
Draft: created but not yet live; only visible in the Apps management section
Published: live in Navigator and accessible to the configured audience
By default, a published app is available to the entire organisation unless access is specifically edited. An app can also be configured to lead with an action instead of opening into chat. This is set during setup. To open an app with an action, an action must be configured in the underlying template.
Can Apps be edited?
Yes, with the following rules.
Action | Who | Notes |
Create | App Author | Creates a draft, not visible in Navigator until published |
Edit | App Author | Changes take effect immediately on published apps |
Delete | App Author | Permanent; requires confirmation |
Publish | App Publisher | Makes the app live in Navigator |
Unpublish | App Publisher | Removes the app from Navigator; reverts to draft |
Manage access | App Publisher | Change who can see the app (org, users, or groups) |
Note: Editing a published app takes effect immediately, there is no staging step after publish. If changes need to be reviewed before going live, unpublish the app first, make the edits, then republish. Note: Manage access is currently accessed from the three dot menu on an app card.