Hi everyone,
I’m a Jira administrator at a multinational company and I’ve created a Rovo AI Agent using Forge. So far:
- I’ve built and tested the agent in development mode on our company’s Jira instance.
- Everything is working as expected, and now I’d like to make the agent available to all users in our instance.
I have a few questions regarding the next steps:
- Do I need to move the agent from development to production?
If so, what is the process to do that in the Forge environment?
- Do I need to publish the agent on the Atlassian Marketplace in order to install it on our production instance?
Or is there an alternative?
- I see in the Developer Console that I can distribute the app via an installation link or by listing it in the Marketplace.
What is the recommended approach for making the agent available only within my company (not publicly)?
I’d appreciate any guidance or best practices on how to properly deploy and distribute a Forge-built Rovo AI Agent across an enterprise instance.
Thanks in advance!
Hi @JordiRomeraAguila ,
If you are agent is wrapped in a Forge app, then it’s actually pretty easy to move it into production: You deploy it to the production environment like this:
forge deploy -e production
And then install it on your site:
forge install -e production
You do not need to publish the app/agent on the marketplace. You also do not need to share it via the Developer Console. That option would allow others to install your app on their instance, even if you do not have access to that instance.
In your case though, you should be good with just deploying and installing the app with the production flag.
Hope that helps,
Oliver
Hi @osienbenmarck,
I’ve created a Rovo agent and deployed it to production, as shown in this screenshot:
However, when another user tries to interact with the agent, they receive an error saying authorization is required, as you can see in this screenshot:
In the third screenshot, it says the app is still in development, even though I’ve already run the following commands:
bash
CopiarEditar
forge create
forge deploy -e production
forge install -e production
Despite this, only I can use the Rovo agent — other users in my organization can’t access it.
Am I missing something? Is there an additional step required to make the Rovo agent accessible to other users?
Any guidance would be greatly appreciated. Thank you in advance!
Best regards,
Jordi
I ran into this issue a while back and switching the distribution status under Distribution in Developer Console did the trick.