Frequently Asked Questions (FAQ) AI Apps Builder

AI Apps Builder is a free Jira app available on the Atlassian Marketplace. After installation, each user receives 100 credits to explore the product and create custom apps. Credits are used when sending messages in the AI chat. For details on the credit system, see Understanding Free Tier Usage Limits in AI Apps Builder.

You need to use your API token to deploy the app created with AI Apps Builder. The token is used only to authorize the installation of the generated Forge app to your specific Jira Cloud site.

The API token:

• Is used only for deployment

• Is not stored by AI Apps Builder

• Is not used to access Jira data

• Is not used at the app’s runtime

• Is not used for analytics or data collection

• Does not affect the app after deployment

Once deployment is complete, the app runs independently as a standard Forge app within your Jira environment. It does not rely on the API token in any way.

If the API token expires or is revoked, the deployed app will continue to function normally.

The token is simply a secure authentication mechanism required by Atlassian to authorize app deployment.

No. The API token is required only during deployment. Once your app is successfully deployed, it will continue working even if your API token expires or is removed. The API token's lifetime does not affect your app's lifetime.

To deploy the Forge app generated with AI Apps Builder, you must have administrator permissions on the Jira site where the app will run.

Yes, you still have options. If you are not an administrator on the Jira site where you want to deploy the app, you can:

• Use your personal Jira site or Jira Sandbox to generate and test the app.

• Once the app is ready, you can move it to the correct production site using a shared link.

• After that, a Jira administrator can complete the installation on the target site.

For detailed steps, see our documentation: How to Move Forge Apps Built with AI Apps Builder to Another Jira Site.

Yes. You can give access to additional users by adding them as Contributors in the Atlassian Developer Console. This allows others to help manage or work with your app. To learn how to do this, see our documentation: Managing Forge Apps - Atlassian Developer Console.

Yes, you can continue improving your app after deployment. You can refine the UI, update the logic, or add new features to your existing app. Please note that any changes you make will only appear in Jira after you redeploy the app.

Yes, you can. AI Apps Builder allows you to create multiple modules or pages within a single app. This can include dashboards, configuration pages, reporting views, or any other UI your workflow requires. If you want to see what a multi-module app can look like, explore our detailed use case of an Automated Jira Issue Assignment System.

You can find all the apps you created with AI Apps Builder directly in your Jira site. To learn more, please read our documentation page: How to Access the Apps, Widgets, and Dashboards You’ve Built with AI Apps Builder.

Yes. If you choose the manual deployment option, you can download a ZIP file with the full source code of your generated app. This is useful when you want to review the code, learn from the structure, or share it with a developer.

Learn how to write clearer, more effective prompts with proven techniques and practical examples in our guide: How to Write Effective AI Prompts: Best Practices and Practical Examples.

Yes. If you create and use your own Forge app, you are responsible for any costs related to Atlassian Forge usage. Here’s an overview of Forge pricing starting January 2026.