Which channels can we use?

You choose. Teams can work with Hermes through Slack, Discord, Microsoft Teams, Telegram, WhatsApp, or Buzz, for example, and one person can also use Hermes Desktop on a workstation. Each channel has its own setup needs: Microsoft Teams, for example, needs an address that is reachable from the internet. Choose the channels your team already uses rather than treating one channel as a requirement.

Can multiple employees work in the same project?

Yes. Everything recorded in the project, such as agreements, procedures, and notes, is available to everyone who works in it. Conversations work differently: in a shared channel, each person has their own conversation with Hermes by default. If your team wants one shared conversation for a channel, that is a setting you can choose together.

Is Hermes difficult to learn?

No. It works like a chat in a channel your team already knows, but with the context of the project. A short introduction covers how to start a task, how to check the result, and when Hermes asks for approval. Voltti's support answers the questions that come up later while you work.

Can I start with one person and expand later?

Yes. You can start with one person, using Hermes Desktop on a workstation or a channel that already fits the work. When more people join, they can work together on a shared node through a channel the team chooses. Your existing configuration, skills, and knowledge can move with the installation; you do not need to start over or adopt a prescribed channel.

Can we control who uses Hermes and what it can access?

Yes. In each channel, the gateway only responds to people on an allowlist. You set which tools the agent can use per platform with toolsets. Higher-risk actions can wait for a person's approval. You decide the rules, and Voltti sets them up with you during installation. Read more on our page about security and privacy.

Can departments see each other's data?

Not if you separate them. Each department can get its own Hermes profile, with its own memory, sessions, skills, and credentials. According to the official documentation, Hermes does not share credentials between profiles. The right separation depends on your organization: sometimes separate projects are enough, sometimes separate profiles work better. Voltti discusses this with you and sets it up during installation.

Hermes for teams: work in the right project

What is Hermes for teams?

Hermes for teams means one shared Hermes installation that your colleagues work with through channels such as Slack, Discord, Microsoft Teams, Telegram, or Buzz. It is more than a chat window: it is a workspace connected to your projects, knowledge base, and tools. Read more about Hermes on our page about the Hermes Agent. For what the agent itself does, with six use cases, see Hermes Agent explained.

What is a project in Hermes?

In Hermes Desktop, a project is a named workspace with one or more folders. At Voltti, we also organize a team's work in the team channels around projects. Such a project is a defined workspace with:

the files and folders that belong to the task
agreements and procedures Hermes needs to follow
access to the tools the task needs
session history, so earlier work stays available

A marketing team can have a project for campaign reports, while the support team has one for customer questions. Each employee opens the project that fits the task. The agent then has the context, skips unnecessary questions, and gets to work.

How does a team work with Hermes?

Here is what that looks like for one recurring task:

A colleague asks Hermes in the team channel for a short overview of last week's marketing results.
Hermes works in the marketing project, so it knows which sources count and how the team wants the overview written.
It retrieves the figures from the sources it has access to and drafts the overview. Our article on retrieving marketing data with an AI agent shows how that works in detail.
A team member checks the draft and decides what happens next.
If the team agrees on a new way of working, someone records it in the project, so Hermes follows it next time.

Our own Hermes installation at Voltti works the same way. Each client's work runs in its own environment with its own access, and every content task starts as a ticket and ends with a verification report in that ticket. People and the agent work from the same queue.

Who can use it, and what can it access?

A shared agent needs clear rules. The official Hermes documentation on the messaging gateway states the default plainly: "By default, the gateway denies all users who are not in an allowlist or paired via DM." In other words, the gateway ignores anyone who is not on an allowlist or paired through a direct message. You decide which colleagues can talk to Hermes in each channel.

You set which tools the agent can use per platform with toolsets. The agent can have different tools in Slack than in the terminal, for example. You agree on which folders belong to a project during setup: the marketing project does not need the finance folder. Do departments need to stay fully separate? Then each department gets its own Hermes profile. According to the documentation on running multiple profiles, each profile has its own bot tokens, sessions, memory, and skills. It does not share credentials with other profiles. At Voltti, we keep each client's work apart the same way.

Higher-risk actions, such as sending an email to a customer or changing data in a system, can wait for a person's approval. Voltti sets up access, profiles, and approval steps with you as part of the installation. Read more on our page about security and privacy.

What stays shared and what stays personal?

Project knowledge is shared. When someone records a decision in the project, such as an agreement, a procedure, or a note, the agent uses it for everyone who works there. Conversations are different. According to the Slack documentation for Hermes, each person in a shared channel gets their own conversation by default, and that setting applies to the other platforms too. One person's questions do not clutter someone else's context. If your team prefers one shared conversation for a channel, you can choose that instead. Everyone then shares the same context and its usage costs, and a reset clears it for everyone.

Desktop and team channels

One person can also use Hermes Desktop on a workstation with the full toolset. Teams work together on a node running Hermes through a channel such as Slack, Discord, Microsoft Teams, or Buzz. Hermes Desktop can also connect to a Hermes installation on another machine, such as that shared node. Telegram and WhatsApp are further options. Each channel has its own setup needs: Microsoft Teams, for example, needs an address that is reachable from the internet, while Slack can work without one. Your team chooses the channels it already uses; growing the team does not require moving to a particular channel.

In short, Hermes for teams comes down to one shared installation, separate projects, and clear rules on who can do what. Want to try Hermes yourself first? Our guide to installing Hermes on desktop or terminal walks you through both routes. Want to know how a pilot runs? Read about Voltti's approach. Or see how Hermes differs from ChatGPT in our comparison of Hermes vs ChatGPT and Copilot.