Use the Rovo app for Slack

The Rovo app for Slack brings Rovo into the conversations where your team already works. Chat one-to-one with Rovo, bring Rovo into a channel, keep it beside you in the sidebar, or set up Rovo and your own custom agents to reply automatically in your team's channels.

Rovo helps you find answers across your connected tools, summarize long threads, and create and update work in Jira and Confluence, all without leaving Slack.

Rovo for Slack is available to anyone with access to a Rovo-enabled Atlassian site. Install the app and you can start chatting right away, without creating a bot account or waiting for an admin.

はじめる前に

以下が必要です。

• Slack account: An account in a Slack workspace where your organization allows the Rovo app to be installed.

• Atlassian account: An active Jira or Confluence Cloud account.

• Rovo access: Access to at least one Atlassian site (for example, your-site.atlassian.net), where Rovo is enabled. If you're unsure whether Rovo is enabled for your organization, contact your Atlassian admin.

• Admin setup, for public replies only: If your team wants Rovo to reply publicly in a channel, this has to be set up first, either by the agent's owner in Rovo Studio or by an Atlassian organization admin. See Configure the shared account for Rovo in Slack. Rovo works in channels without this, replying privately to whoever asked.

If your Slack email address is different from your Atlassian email address, Rovo asks you to sign in to your Atlassian account once.

Set up or reinstall Rovo in Slack

Any user can install the Rovo app for their Slack workspace and complete onboarding.

1. Install the Rovo app from the Slack Marketplace. Select Add to Slack and follow the prompts.

2. If Rovo has already been installed in your workspace, Slack shows Open in Slack instead of Add to Slack. To reinstall Rovo, start Rovo for Slack setup from the onboarding page.

Rovo connects you to an Atlassian site you have access to. If you have access to more than one, you can change it at any time.

Start a chat with Rovo

To start a chat:

1. 左側のナビゲーションで、[Apps (アプリ)] までスクロールします。

2. Select Manage, then Browse apps.

3. Search for Rovo and select it.

4. Select New chat, or select the History tab to pick up an earlier conversation.

Add Rovo to the top bar or sidebar

To add Rovo to the top bar:

1. Open a direct message with Rovo.

2. Select More actions (•••) next to New chat.

3. [Add Rovo to top bar (Rovo をトップバーに追加)] を選択します。

You can then select the Rovo icon in the top bar from any channel to open a private chat that uses that channel as context.

To add Rovo to the sidebar:

1. Select your profile avatar, then go to Preferences.

2. Select Navigation.

3. Scroll to App agents & assistants.

4. Select Rovo from the list.

Use Rovo in a channel

To use Rovo in a channel:

1. Invite Rovo to the channel, or mention @Rovo and add it when prompted.

2. Ask your question.

3. The first time Rovo is used in that channel, you'll see a private setup card that nobody else can see. Select Confirm to connect the suggested Atlassian site and use private replies, or Change settings to choose a different site or change how Rovo replies in the channel.

Rovo saves the settings for that channel and answers your question.

Each channel is set up on its own, so different channels can connect to different Atlassian sites and reply in different ways.

Use Rovo

Rovo is the agent built into the app. @Rovo works as soon as the app is installed, with no extra setup.

In a direct message

The simplest way to work with Rovo is a direct message. Rovo acts as a single AI assistant across your work, pulling answers from Jira, Confluence, and the third-party tools you've connected to Rovo. Replies are private to you and use your own permissions.

While Rovo works, it shows you its progress rather than leaving you waiting on a blank reply.

In a channel

Mention @Rovo in a channel to ask a question where the work is happening. By default, Rovo replies privately to you.

How Rovo replies in a channel

Each channel decides this for itself, so different channels can work differently. Type /rovo manage in the channel to choose:

• Requesting user, the default: Rovo replies only to the person who asked, using that person's own access, and they choose whether to post it to the thread. Everyone who asks gets their own reply, scoped to their own access. Choose this for everyday team work, or whenever people should only see what they already have access to.

• Shared account: Rovo replies in the channel for everyone to see, using a single account your organization has set up rather than the access of the person asking, so the whole channel gets the same answer from the same content. Select this for a help or support channel.

An Atlassian organization admin has to set the shared account up once per Slack workspace before it can be chosen. See Configure the shared account for Rovo in Slack.

If it can only reach some of your content, its access needs widening, which the admin grants. Searching your connected third-party tools works when Rovo replies to you privately, using the tools you've connected yourself. With a shared account, only the tools your admin has authorized for it are available.

Use your organization's custom agents

What is a custom agent?

A custom agent is an agent that your organization has built in Rovo Studio for a specific job, for example an onboarding agent, a support deflection agent, or a fact checker. You use custom agents in Slack the same two ways you use Rovo: in a direct message, or in a channel.

A custom agent has to be published on the Atlassian site connected to the channel before it can be used there.

Chat with a custom agent in a direct message

Search for the agent from the Home tab in the Rovo app and open a conversation with it directly. As in any direct message, replies are private to you and use your own permissions.

Add a custom agent to a channel

To add a custom agent to a channel:

1. Mention @Rovo and invite it to the channel.

2. /rovo manage と入力します。

3. Select Custom agent, then search for and select the agent by name.

4. Give it at least one trigger. @Rovo summons Rovo, not your agent, so without a trigger, nobody can invoke it. A keyword is the usual choice.

How a custom agent replies

Unlike Rovo, a custom agent's access isn't a channel setting. Its owner sets it in Rovo Studio, and Slack shows it to you without letting you change it:

• An agent using its own access replies in the channel for everyone to see, drawing only on content its owner has given it.

• An agent using the requesting person's access replies privately to whoever asked, who then chooses whether to post it to the thread.

Only the owner can change this, in Rovo Studio. If they do, the channel behaves the new way from the next question onward, and replies already posted stay exactly as they are. If the agent can't find something your team expects it to find, its owner needs to widen its access.

Some channels work differently. In channels set up before agent accounts existed, and on some Atlassian sites, a custom agent uses the same /rovo manage choice as Rovo does: Requesting user or Shared account. Those channels show a banner explaining that custom agents are moving to the Rovo Studio model. See Configure the shared account for Rovo in Slack for the shared account.

Set up automatic replies in a channel

By default, an agent answers when it is invoked. You can also give it triggers so it replies on its own. This is how teams deflect repeat questions in a help channel, keep a triage channel moving, or add a specialist agent to review what's being discussed.

Triggers mean something slightly different for each agent. For Rovo they're optional, because @Rovo already works; a trigger just lets Rovo answer without being mentioned. For a custom agent, at least one trigger is necessary, because @Rovo summons Rovo rather than your agent.

トリガーのタイプ

Triggers determine when an agent replies. @Rovo is a built-in mention trigger; the other triggers let an agent reply without being mentioned.

You can give one agent more than one trigger. For example, Rovo can reply to every new message and to the keyword Assist.

Manage agents, triggers, and thread replies

Type /rovo manage in the channel to see the active agents and triggers, edit or rename them, remove an agent, or change the connected Atlassian site.

From /rovo manage, you can also turn on continuous replies for an agent in that channel. The agent then replies to every message in a thread it has been triggered in, so you don't have to trigger it again to keep the conversation going. The agent that answered first handles the rest of that thread, so other triggers and keywords won't work there. You can only use this setting in a channel with one agent.

Example: a help channel that answers repeat questions

To set up a help channel that answers repeat questions automatically:

1. Add Rovo, or your organization's support agent, to the help channel with /rovo manage.

2. Give it the New messages trigger so every question posted gets an answer.

3. Turn on continuous replies for that agent from /rovo manage so follow-up questions in the thread are answered too.

4. If you want answers everyone in the channel can see, set it up for whichever agent you added.

   1. For Rovo, select Shared account in /rovo manage, which your admin sets up first: see Configure the shared account for Rovo in Slack.

   2. For a custom agent, ask its owner to set it to use its own access in Rovo Studio.

   3. Either way, give that account or agent access only to the knowledge you're comfortable with anyone in the channel reading.

Example: mixing triggers and 2 agents

You might add Rovo and have it reply to every new message as well as to the keyword Assist, then add an agent called Fact Checker with the keyword CheckAI. With that setup:

• Rovo responds automatically to channel messages.

• You keep a thread going by mentioning Assist in your replies.

• You fact-check the thread at the end by mentioning CheckAI.

安全性と権限

Rovo respects your organization's existing access controls at all times.

• Your access applies to you: In direct messages and in private channel replies, Rovo only returns content you have permission to see.

• Public replies use Rovo's own access, never yours: A public reply can't reach anyone's private content.

• Nothing is shared without your say: A private reply stays visible only to you until you post it to the thread, where it's marked as shared via Rovo.

• Automated replies follow the same rules: An agent replying to a trigger uses exactly the same access as one replying to a mention.

• Confirmation before acting: Rovo previews and asks you to confirm before it creates or updates a Jira work item, publishes a Confluence page, or acts in a connected third-party tool. Actions always run with your own permissions and are confirmed privately to you, even in a channel where Rovo replies publicly.

• Nothing changes retroactively: If an agent's access changes, replies already posted stay exactly as they are.

トラブルシューティング

Can't find the Rovo app in Slack

Your Slack workspace admin may need to approve the Rovo app for your workspace.

Rovo can't find something, or the answer looks wrong

• Check the site: Make sure the channel is connected to the Atlassian site where the content lives. Type /rovo manage to change it.

• Check whose access is being used: If Rovo is replying privately, you need permission to view the item. If it's replying publicly, Rovo or the agent needs permission, which its owner grants.

• Be specific: Try pasting the direct URL, or use more specific keywords.

Other people can't see Rovo's answer

Rovo is replying privately, so the answer is visible only to you. Select Post to thread to share it with the channel.

A custom agent stopped replying in a channel

• Its owner may have changed its access in Rovo Studio to use the asking person's access, so answers now go privately to whoever asked rather than to the channel.

• If the agent has just been moved onto its own access, its owner also has to grant it access to content before it can be used. Until then, it won't answer.

• Check the trigger is still configured with /rovo manage. A renamed or removed keyword stops the agent responding.

Can't turn on public replies in a channel

For Rovo, Shared account is always shown as an option in /rovo manage, but selecting it shows a warning if your organization hasn't set it up yet. Ask your Atlassian organization admin to follow Configure the shared account for Rovo in Slack.

For a custom agent, you can't change this from Slack at all: ask the agent's owner to set it to use its own access in Rovo Studio. Private replies keep working in the meantime.

Two agents are both replying, or the wrong one is

Type /rovo manage to review the triggers. Keywords must be unique within the channel, and only one agent can use the New messages trigger. If continuous replies are on, the agent that answered first will handle the rest of that thread.

Do I have to mention @Rovo every time?

In a thread, yes, unless continuous replies are turned on for the agent handling that thread in the channel. Type /rovo manage to turn them on.