Regulated pack

The Regulated pack adds the controls that regulators and auditors in healthcare, financial services, government and legal ask for, in one pack you install on the Advanced edition.

Who it is for

Rainbook's default is an easy CRM where everyone Jira lets in sees the whole customer. Some teams need more: their regulator, auditor or professional-conduct rules ask for controls beyond Jira's permissions. The Regulated pack is that one switch. It is optional and off by default: an admin turns it on in Settings › Packs, a site runs these controls exactly when the pack is installed, and it works like any other Rainbook site when it isn't.

When you install it, you choose one or more profiles. Where profiles overlap, the stricter setting applies.

Life sciences, government contractors and legal packs are early access.

The pack gives you the controls; how they fit your obligations stays your call and your auditor's. It works alongside any industry pack: a fintech software company can run the SaaS pack with the Financial services profile, and a law firm can run the Legal pack with or without the Regulated pack.

What you need

• The Advanced edition, on a paid Jira plan (Jira Standard or above). Confidential spaces and walls are built on Jira security levels, which Jira Free doesn't have. On Standard, Settings › Packs shows that the pack comes with Advanced.
• Early access. The Regulated pack ships with the base launch on Tue 15 Dec 2026 at early access, with its built parts. Parts that follow arrive in minor versions, and this page gains each one the day it ships.
• The listed Rainbook app. The pack isn't offered on Rainbook Beta. To evaluate it, start an Advanced trial of Rainbook.

If your site leaves Advanced, including a move to Jira Free, with the pack installed, every control stays on and email capture pauses. The pack needs Advanced on a paid Jira plan. Upgrade the Jira plan in your Atlassian billing, return to Advanced in Manage apps, or remove the Regulated pack. If email capture is paused for another Regulated pack issue, everything already stored stays protected. Contact Rainbook support, or remove the Regulated pack. Choosing Jira storage changes only where new content is written, never the installed pack protections.

Profiles, preview and removal

A member of rainbook-admins installs the pack from Settings › Packs. The preview explains, in plain sentences, what will change before anything is written:

• "Email bodies, files and AI outputs are kept in Rainbook's regulated store instead of on Jira work items, from today forward."
• "Every change is recorded in a tamper-evident history that starts today."
• "Removing the pack later moves nothing back onto Jira."

It then lists exactly what stays in Jira, explains how Rovo and AI clients behave with the pack, and shows the acknowledgement for each profile you chose. With Healthcare and life sciences: Rainbook holds no patient data and signs no business associate agreement, so patient information stays out of Rainbook. With Government and defence: you won't store Controlled Unclassified Information, export-controlled technical data or anyone's clearance or citizenship details in Rainbook or its Jira spaces, because Rainbook runs in Atlassian's commercial cloud.

With the pack, only people in rainbook-users use Rainbook, even on a site where everyone who can open the CRM space would otherwise use it; the preview lists the group and who is in it. Only members of rainbook-admins administer Rainbook; Jira admins are not Rainbook admins here unless they belong to that group.

Install is the confirmation; there is no tick box. Creating the pack's Jira groups needs a site admin, so the preview gives you copy buttons and Send to my site admin. Like every pack, the install resumes where it stopped if you close the tab.

After install, a guided setup page walks you through the recommended next steps, each with a link:

1. Decide whether to block Rovo for Jira, or remove Rovo from the groups that must not search CRM content.
2. Set Email audience to Only CRM users.
3. Review the Confidential space's groups.
4. Set retention schedules, once that part is on.
5. Set data residency for your Jira site; Rainbook follows it.
6. Optionally, apply an Atlassian data security policy to spaces Rainbook must not read.

Nothing on the page blocks you from using the pack.

The regulated store

With the pack's regulated store on (the default), the content of customer email lives in Rainbook's regulated store in your site's own Forge storage, not on Jira work items.

Email subjects are never written to Jira: a conversation is named "Email with Acme Corp · 2 Dec". Each stub reads "Message stored in Rainbook's regulated store. Open in Rainbook to read it." Everyone who can open the conversation in Rainbook reads the full message there.

Email captured before you install the Regulated pack stays in Jira, including message comments and attachments. A move job that takes it off Jira arrives in January.

Installing the pack also clears AI summaries and next steps that Rainbook wrote to Jira fields, and deletes earlier nightly archive attachments from Jira; the preview says so.

Download full regulated export on Settings › Regulated pack builds a ZIP in your browser of every regulated body and file and all of the sealed history, with its manifests and public key. It also holds the AI outputs Rainbook keeps in its storage (account and deal briefs, record and email summaries, health reasons, and your own drafts and meeting prep) for every record you can open, and an archive.json that names your nightly archive: the latest full set and every daily set after it (a restore needs all of them), with each part's attachment ID or stored key and its checksum. Other people's drafts and meeting prep are personal and stay out; each person keeps theirs by copying it before you uninstall. If some AI outputs are on records you can't open, or a data security policy blocks apps from them, the export says how many; an admin who can open them gets them.

Each email's stub comment in Jira ends with "Admins can download it with Download full regulated export", so anyone who finds the stub knows where the message is kept.

The Confidential space

The pack creates a restricted Confidential space in your Jira, with its own group and security level, opened only by the people you add. Rainbook's AI never reads anything in it, in Ask, summaries, drafts, agents or the Rainbook agent's own actions.

Rovo, AI clients and the pack

Everything in the restricted Confidential space stays out of Rainbook's AI. People who can open that space can also see its contents in Rovo search and chat. To keep it out of Rovo completely, block Rovo for Jira in Atlassian Administration.

Rovo search and chat index Rainbook's work items like any other Jira work, so Rovo can still show the records, native deal and account fields and stub comments to people Jira lets see them. Rovo's reads happen inside Atlassian, so Rainbook's activity history doesn't record them. To limit Rovo:

• Block Rovo for Jira in Atlassian Administration → Rovo → Rovo access, or remove Rovo from the groups that must not search CRM content.
• For AI clients such as Claude or ChatGPT connected to Atlassian's MCP server, the setup page shows how to apply a data security policy that blocks the Activity and Confidential spaces. Those clients read every Rainbook work item a person can see and, with write access, can edit those items and their properties as ordinary Jira edits. Rainbook's own tools for AI clients are coming soon.

With the pack, the Rainbook agent and Rainbook's tools in Rovo start off; an admin can turn them on in the pack's settings. Their answers never include anything from the Confidential space. Email summaries for AI clients are always off. Anything a person sends to ChatGPT falls under your own OpenAI terms.

Rainbook's AI with the pack

Rainbook's AI keeps working, with tighter limits:

• AI outputs are stored only in Rainbook, never on Jira fields, comments or the sidebar card.
• Admins keep a Never send to AI list of fields and can turn AI off per work type. Before every request, Rainbook removes SSNs, card numbers, IBANs and passport-like and medical-record-like numbers.
• Email bodies are sent to the model for summaries unless you turn those AI features off.
• Drafts use only the last three messages and the record's native fields.
• Require a second approver starts on: every proposal becomes an Approval request, and the person who asked can't approve their own.
• Ask keeps your saved charts, but deletes question text and narration after 7 days. Show sources keeps a record of each AI result without its text.
• After a reinstall, Rainbook's AI stays paused until an admin confirms the AI settings.
• The Healthcare and life sciences profile's prompts leave out patient detail. The Legal profile's prompts leave out health, criminal and immigration facts, and AI stays off for a matter until its Client AI consent is Given.
• Rainbook adds no accounts or deals to the graph feed behind Rovo Search.

Sensitive-data detectors

Card and SSN masking runs on every Rainbook site. The pack adds the full detector library, at capture and at import: a detector set to Block holds a message back and sends a notice, and one set to Notice stores it masked and tells the admin. Held messages wait in the Inbox for release, and the sensitive-data report shows what was caught. With the Government and defence profile, CUI and ITAR markings are blocked and locked. Every detector runs on patterns, checksums and word lists inside Rainbook; none sends content to an AI model.

Ethical walls

With the Financial services or Legal profile, a private deal can become an Ethical wall. Only the people it is shared with can open it and its email; Rainbook admins can't unless they are named, and Rainbook's AI never uses its content on any other record. Jira site admins can still reconfigure Jira's schemes.

Sidebars with the pack

The Gmail and Outlook sidebars keep working. With the regulated store on, a sidebar shows the contact, account, owner and open deals (stage, amount and close date) with Open in Rainbook, and no AI summary card. Draft reply stays on, built only from the open message and those native fields, and an admin can turn it off. Log thread sends the message to the regulated store, like capture. Calendar events marked private or confidential are skipped. See Sidebars for installing and pairing.

Sealed history

From the moment you install, every change in Rainbook's activity history is chained: each entry carries a hash of the one before it, starting from a genesis entry for your site.

• Daily seals. Each day is sealed into a segment signed with your site's own key. The public key is on the activity history page.
• Verify chain. Check any date range in the app; Rainbook reports the first broken link if anything was changed.
• Export sealed days. Export any range as a ZIP of segments, manifests, the public key and the verification steps, so your auditors can check it offline and keep it in your own write-once storage.
• Known limit. If Rainbook restarts while recording an audit entry, that entry can appear twice in the log. Both copies are sealed and pass Verify chain; the repeat has the same action, object and time.

The full verification algorithm is published on the Regulated pack page.

Coming next

Each of these joins the pack in a minor version, and this page gains its section the day it does.

• Protected fields on the record page: choose sensitive fields from your industry packs (privileged notes, pricing terms, capture strategy and others), and the pack moves their values into the Confidential space, shown on the deal or account page only to people who can open them, with every view recorded in the activity history. Protect your sets before your team enters data: Rainbook hides a protected field's value from everyone without access, and from search, Ask, AI and exports, but Jira keeps its own change history for every work item, so a value entered before the field was protected stays in that work item's History tab, visible to anyone who can open the work item, and Rainbook cannot edit Jira's history. Choosing protected sets before data entry avoids this entirely.
• Retention schedules and legal hold: set how long captured email, meetings, sealed history, AI drafts and nightly archives are kept, with a preview and your confirmation before anything is deleted, and hold an account, deal, matter, person or the whole site so nothing in scope is deleted until the hold is released.
• Adverse-event intake: with the Healthcare and life sciences profile, possible adverse events and product complaints held back from capture and routed to your safety team.
• Regulated email backfill: move email captured before you installed the pack into the regulated store, from January.

The DORA addendum and the pack page

EU financial entities can sign the DORA addendum, which ships with the pack: service description, data locations, data protection, access, recovery and return of data, service levels, incident assistance, cooperation with authorities, termination and exit support, and audit and inspection rights.

The Regulated pack page holds the full detail for your security and compliance reviewers: the regulated store, the Confidential space, sealed history and its verification algorithm, how to block Rovo for Jira, the pack's sensitive-data policy and the register-of-information data for your DORA register.

Removing the pack

Removing the Regulated pack changes new content only. New email and files are stored as on any Rainbook site; nothing already in the regulated store moves back onto Jira, and it stays downloadable through Download full regulated export. The Confidential space and everything in it stay in Jira for their groups. The sealed history closes with a final sealed segment and stays verifiable. Detection returns to card and SSN masking, and your acknowledgements and history are kept.

Uninstalling Rainbook with the pack

With the Regulated pack, email bodies and files live in Rainbook's regulated store, outside your Jira work items, and imported history older than 90 days lives in Rainbook's storage. Uninstalling removes both from your site; Atlassian can restore them to a reinstall you request within 21 days. Run Download full regulated export first; it includes your imported history. Confidential records stay in your restricted Confidential space.

If you uninstall Rainbook, email content and audit history held by Rainbook are deleted after Atlassian's recovery period. Download a full export first.

Before you uninstall:

1. Download the latest nightly copy from Settings › Export and backups, under Nightly copies. With the pack it is never attached to Jira.
2. Run Download full regulated export on Settings › Regulated pack.

Your records, their native fields and each email's stub comment stay in Jira, and every stub names the export. For what every Rainbook site keeps on uninstall, see the Admin guide.