Summary
Version 2.1.2 focuses on collaboration, workflow integration, and security.
Key additions include:
Private and shared visibility settings for Tracking Reports
Word export for Impact and Strategy Reports
Add Context button in chats for dynamic reasoning
Two-Factor Authentication (2FA) support
Standardized policy cards across modules
UI and infrastructure refinements for consistency and reliability
1. Tracking Reports Enhancements
Private and Shared Visibility
Purpose: Give users more control over who can view and manage tracking reports.
New Capabilities:
Each tracking report can now be marked as:
Private – visible only to the creator.
Shared – accessible to all members of the user’s group within the organization.
Users can toggle between Private and Shared views to see at a glance which reports are visible to others.
2. Report Output Enhancements
Export to Word
Purpose: Allow teams to edit and reuse Abstract-generated reports in their own templates and workflows.
Update:
Impact Reports and Strategy Reports can now be downloaded as Word (.docx) files.
Preserves report structure and key formatting.
Why it matters: Makes it easier for users (e.g., law firms, GR teams) to tailor Abstract’s outputs for internal memos, client briefings, or legislative filings.
3. Chat Enhancements
Add Context Button
Purpose: Give users fine-grained control over what Abstract references in each conversation.
New Capabilities:
New “Add Context” button in every chat.
Users can add:
Public Policy Documents from any purchased jurisdiction (bills, regulations, agendas, executive orders).
Private Uploads they’ve previously added to their workspace.
Abstract now clearly displays which documents are being referenced in each chat message, showing when no uploads are used or which files are informing its reasoning.
Example:
If a user uploads an employment contract and asks a question about labor policy, Abstract will show that the response references that specific document, providing transparent context.
4. Platform Security
Two-Factor Authentication (2FA)
Purpose: Strengthen account protection for enterprise users.
Update:
Introduced SMS-based 2FA for accounts that require multi-factor authentication.
5. Report and UI Updates
Removed Fiscal Note Section: The fiscal note segment in Strategy Reports was deprecated to streamline output and remove low-value sections.
Policy Card Standardization:
All policy cards (e.g., Bill SB-9) now share a consistent design and metadata layout.
Applies across chats, reports, and tracking modules.
Displays key information such as title, jurisdiction, and status in a unified format.
Bug Fixes:
General cleanup and reliability improvements across report rendering.