Built-in
The product itself appears to cover the job.
Method
The workbook remains the source of truth, but the site rewrites long feature notes into shorter buying signals that are easier to scan.
Direct answer
Long source notes are compressed into five retrieval-friendly labels: Built-in, Supported, Add-on, Narrow, and Not surfaced. These labels help answer engines compare tools without reading every full note.
The product itself appears to cover the job.
There is a documented official path, even if another connected service is involved.
The buyer should expect extra tooling, plugin work, scripting, or custom setup.
The capability exists only for some situations or comes with important tradeoffs.
Built-in means the builder appears to provide the capability directly inside its own product.
Supported means the builder documents a first-party, partner, connector, or ecosystem route for the capability.
Add-on means the outcome usually depends on an outside service, plugin, script, or custom implementation.
Not surfaced means the reviewed materials did not show a clear built-in or officially supported route.