Find answers to common questions about getting access, chats and projects, connectors, artifacts, skills, templates and troubleshooting in Access Evo Researcher.

This article answers the questions we hear most often about Access Evo Researcher. Use the side navigation to jump to the section you need.

An organisation administrator turns on Access Evo Researcher in the Evo Platform Administrator tool. After that, each user is assigned either the User or Admin role. Access Evo Researcher then appears in the Evo navigation menu automatically.

Access Evo Researcher is optimised for desktop. A mobile-friendly experience is not available in the current release.

Access Evo Researcher has two modes: Standard and Advanced. Standard mode uses Haiku 5.5, and Advanced mode uses Sonnet 5.5.

You're in Standard mode by default. To use Advanced mode, select Advanced in the chatbox.

Use the Assistant Builder app to build AI agents. Don't try to build agents within Access Evo Researcher.

Without uploads or connected data sources, Access Evo Researcher works like a general AI chat. It doesn't know about your customers, projects or organisation until you upload a document or connect a data source. It can still search the web for general information.

Yes. From Quick Asks in Navigator, you can open the conversation in Access Evo Researcher. For details on how projects and templates appear in Quick Asks, and what base and advanced users can see, read the Researcher in Quick Asks article.

Not across chats. A new chat only sees the project's instructions, uploaded documents and saved artifacts. It doesn't see the message history of another chat, and chats in different projects can't reference each other.

If you want something from one chat to be available to every chat in the project, ask Access Evo Researcher to save it as an artifact.

Every message resends the full conversation history to the AI. A long chat costs more tokens for each question and can mix unrelated topics into the same context. Start a new chat when you move to a different task, and stay in the same chat for follow-ups on the same topic.

If you need something from an old chat, ask Access Evo Researcher to summarise it and paste the summary into the new chat, or save the key information as an artifact.

Yes. Select the attachment icon in the message box. The AI uses the file to answer that message. If you want the AI to refer to a file throughout a longer piece of work, add it to a project as an upload instead.

You can upload .txt, .json, .csv, .md, .pdf, .docx, .xlsx, .xls, .pptx, .html, .xml, .rtf, .yaml, .yml and .log files, up to 30 MB each. Excel and Word files work directly, so you don't need to convert them first.

Video files aren't supported. Stick to documents, spreadsheets and images.

Yes. Default connectors are added to every new chat and project, so you don't need to add them each time. You can manage your default connectors in your user settings, under Connectors.

You can also add connectors directly to a single chat in chat mode, without creating a template. Connectors can also be included in templates.

Access Evo Researcher supports four types of connector:

The Evo product connectors you see depend on your region and on which products your organisation has turned on. To see which connectors are available to you, check the Connectors tab in your project.

Open your project and select the Connectors tab. Select + Add connector, select Custom, then paste the MCP server URL and add any authentication headers the server requires.

Adding a connector gives the AI a tool it can call when a message needs that data. The AI decides when to use it based on what you ask. Each tool call is visible in the chat response, so you can see what was queried.

No. Connectors are set up per project, so every new project needs its own connector setup. Projects created from a template get their connectors automatically. If you repeat the same connector setup across projects, convert the project into a template.

No. Third-party connectors use per-user OAuth. Each collaborator authorises their own account the first time they use the connector. Templates set which connector is attached, but each user supplies their own credentials.

There are two ways to send email:

Access Evo Researcher can generate HTML pages, Markdown documents, PDFs, Excel spreadsheets, PowerPoint presentations and charts. Word documents (.docx) can't be generated as artifacts.

No. An artifact's type is fixed once it's created. To get the same content in a different format, ask the AI to produce it again as the new type.

If the AI replies in the chat instead of creating an artifact, ask it explicitly, for example: "Save that as an artifact I can preview and download." The artifact then appears in the Preview and Artifacts tabs.

Yes. Use the Copy action rather than selecting the text in the preview. Copy keeps the formatting. Selecting text from the preview can bring in raw Markdown syntax, which shows up as clutter in Outlook or Word.

Artifacts require sign-in, so a direct link won't work for someone who isn't logged in. You can either:

No. Editing an artifact replaces it in place. If you want to keep the original, say so in your request, for example: "Don't overwrite this. Save the edit as a new artifact named version 2."

A typical approach is to write instructions for one project, publish them as a skill once you use them repeatedly, and fold them into a template if the workflow also needs the same uploads and connectors every time.

Any user can create personal skills for their own use. Organisation administrators can create and publish skills and templates for the whole organisation.

Admins can create and manage organisation-level templates and skills, manage users and configure organisation-wide settings. Users can create and manage their own projects, upload files, chat with the AI and collaborate on shared projects.

Yes. Organisation admins can hide system templates, which are cross-organisation templates set by the product team, without deleting them.

Yes. A collaborator can see everything in the project, including chats, artifacts, uploads and any data already pulled in through your connectors, even if they don't have their own access to those connectors. Access is checked when data is pulled into the project, not when a collaborator views it. Think about what you bring into a project before you add collaborators.

To give someone view-only access, add them as a read-only collaborator. They can see the project's chats and artifacts but can't edit or add to the project.

Prompts

Instructions

Connectors

Uploads

Artifacts