Connected relationship records
Clients, projects, tasks, files, approvals, documents, and finance remain connected.
A public record of what changed and what is current.
This page begins with a verified capability review rather than inventing launch history. Future material changes can be added with a date, product area, customer impact, and supporting documentation.
Provider-backed mail
Gmail and Outlook connection, synchronization, sending, attachments, and message actions have server-side paths.
Provider verification
Stripe Connect paths support client payment collection and verified reconciliation to invoices.
Current capability review.
The first entry documents what was verified in the product and public site on the record's starting date.
August 9, 2026: Acquisition and discovery expansion
Added focused solution, alternative, workflow, calculator, research, comparison-methodology, capability, and integration content to improve buyer evaluation and machine discovery.
August 9, 2026: Integration documentation review
Confirmed product paths for Dropbox and Google Drive file linking, Gmail, Google Calendar, Stripe Connect, Outlook, OneDrive, and QuickBooks surfaces.
August 9, 2026: Evidence publication standard
Established public rules against fabricated customer outcomes, invented benchmarks, unsupported comparisons, and ambiguous product claims.
How future entries will work
Each material update should include a date, affected area, customer impact, availability notes, and a link to the current documentation.
What belongs in this record.
The changelog should help a customer understand meaningful change, not amplify every internal edit.
IncludedNew customer-visible capabilities, material workflow changes, security or privacy changes, integration changes, and important availability updates.
LinkedCurrent feature, help, legal, security, or product documentation that explains the resulting behavior.
LabeledBeta, limited availability, provider dependency, plan requirement, and configuration requirements.
ExcludedInvented release dates, internal-only refactors without customer impact, and unverified roadmap promises.
Product updates, answered.
Does this page include Stelaah's full historical release record?
No. The public record begins on August 9, 2026 and does not invent dates for earlier work.
Will every internal change appear here?
No. Entries focus on meaningful customer-visible capability, security, privacy, integration, or availability changes.
Where should I confirm current availability?
Use the linked feature, pricing, help, and integration pages, then confirm the behavior in your workspace or during a product evaluation.
See what the connected system can do today.
Review the capability matrix or test Stelaah with one active client.