Your CRM runs in the Jira you already have
Gambit is a CRM that runs inside Jira Cloud. Your deals use JQL, dashboards, Automation and the Jira mobile app. Your team moves in from Salesforce, HubSpot or Pipedrive export files, with a dry run before anything is written. On Jira plans that include Rovo, the Gambit agent answers in Rovo Chat. What uses your Atlassian allowances
Free on Jira sites of up to 10 users.
Sales teams work deals, accounts and contacts in Jira
Deals, leads, accounts and contacts are Jira work items, under the permissions your site already has. Product and engineering teams see each customer's revenue on the bugs and epics they already work on. Gambit installs in Jira Cloud sites only.
On Jira Free, everyone on the site sees every record; private deals need Jira Standard or above.
Account owners track their customers' support requests
Gambit links Jira Service Management requests to accounts by the requester's email or organization, and each link says why. Bugs linked to those requests pick up the customer too. To link by organization, map your organizations to accounts in the setup wizard.
Sales teams ask Rovo about their pipeline
Reps and managers ask the Gambit agent in Rovo Chat to find accounts, summarise a deal or run a report. Each person sees exactly what Jira lets them see. Agents you build in Rovo Studio can call Gambit's tools, and the same permission rules apply. The agent works on Jira plans that include Rovo.
The Gambit agent in Rovo · AI and Rovo · What uses your Atlassian allowances
Admins link work items to accounts from Jira Automation
Add the Link to customer account action to a Jira Automation rule. Leave the account blank to match it from the requester. Gambit's packs add rule templates, such as raising a bug's priority when the revenue at stake on it passes $100,000, and each says how many Automation steps it uses. The rule runs the action as the person who connected it, so it links only work items that person can see and edit.
Gambit's own AI, capture and background jobs are included in your subscription and use neither Rovo credits nor Automation steps. The Gambit agent in Rovo, Rovo Studio agents that use Gambit's tools, and Automation rules built from Gambit's templates or actions use your Atlassian allowances: Rovo credits from 3 Dec 2026, and Automation steps from your first renewal on or after 3 Dec, shown per rule in your admin Usage tab.
Reps get customer email on the account and deal, no BCC
Gambit Mail Sync files customer email from Microsoft 365 and Google Workspace on the right account and deal. Its mailbox permissions are read-only, so it can't send, change or delete mail.
Capture needs a paid Gambit plan.
Microsoft 365 users connect their own mailbox wherever their IT allows it, or IT connects everyone; Google Workspace capture is connected by the IT admin; capture is labelled beta; personal Gmail opens after Google's review, with a waitlist.
Mail Sync is a separate Marketplace app with its own price.
Admins import Salesforce, HubSpot or Pipedrive exports
A dry run checks each row and flags duplicates before anything is written into your Jira site. Spreadsheets work too, and you can undo an import for 14 days.
Only Gambit admins run imports, from export files. Direct imports that sign in to your old CRM arrive in January 2027.
Teams export their records to CSV or an Excel workbook
Open Settings › Export and backups to save your records as CSV files or one Excel workbook. An export holds only the records you can see.
For your Jira admin
Mail Sync requires an active Gambit subscription.
Questions and answers
Does Gambit connect to the CRM I use today?
No live sync. You move in by importing Salesforce, HubSpot or Pipedrive export files, or a spreadsheet. A dry run checks every row before anything is written, and Undo lasts 14 days. Direct imports that sign in to those CRMs arrive in January 2027, on paid plans.
Get on the Gambit mailing list
Gambit is on its way to the Atlassian Marketplace.