> For the complete documentation index, see [llms.txt](https://docs.scribeware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scribeware.com/customizations/tables.md).

# Tables

Whole-report tables built from smart tags — every finding, where it was and what it costs, gathered up from work you were doing anyway.

A group tagged consistently across a report can be gathered into a table: every finding, where it was, and how bad it is. A table is built from your tagging, so it fills itself in as you work.

{% hint style="info" %}
Tables are built on the desktop app. Anything marked **(beta)** needs the 7.2 compatibility update. See [Updating Company Compatibility](https://docs.scribeware.com/customizations/updating-company-compatibility.md).
{% endhint %}

## How a Table Comes Together

1. **Tag your observations** from a [smart tag group](https://docs.scribeware.com/customizations/smart-tags.md) attached to the report.
2. **Build the table** in the report's **Overview** chapter, where you pick the group it's fed by and its columns.
3. **Place it in the report** by adding a [Table Reference](https://docs.scribeware.com/customizations/tables/placing-a-table-in-the-report.md) to a section. A table doesn't print until you do this or add it to a [Smart Summary](https://docs.scribeware.com/customizations/smart-summaries/titles-intro-text-and-tables.md#tables).

## Which One Do You Need?

| You want                                                                         | Use                                                                                                             |
| -------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- |
| Values lined up in rows and columns, gathered from the whole report, with totals | A table                                                                                                         |
| The observations themselves, grouped by what they're tagged with                 | A [Smart Summary](https://docs.scribeware.com/customizations/smart-summaries.md)                                |
| One observation's tags printed as a small table inside that observation          | A group that [prints as a table](https://docs.scribeware.com/customizations/smart-tags/how-smart-tags-print.md) |

A smart summary can also carry a table.

## In This Section

{% content-ref url="/pages/BKemF4Umb9VLop3myLL2" %}
[Creating a Table](https://docs.scribeware.com/customizations/tables/creating-a-table.md)
{% endcontent-ref %}

{% content-ref url="/pages/mQR2BnQpIyp2EQo3tJza" %}
[Table Columns](https://docs.scribeware.com/customizations/tables/table-columns.md)
{% endcontent-ref %}

{% content-ref url="/pages/QK5tzzLorEZmwTvtTpSj" %}
[Rows and Filters (beta)](https://docs.scribeware.com/customizations/tables/rows-and-filters.md)
{% endcontent-ref %}

{% content-ref url="/pages/R2oLGNwr2YsbM6nUaCyo" %}
[Formulas and Totals](https://docs.scribeware.com/customizations/tables/formulas-and-totals.md)
{% endcontent-ref %}

{% content-ref url="/pages/dKxeOAyiMMW3MJCFkeLt" %}
[Placing a Table in the Report](https://docs.scribeware.com/customizations/tables/placing-a-table-in-the-report.md)
{% endcontent-ref %}

{% hint style="success" %}
The Scribeware AI assistant can create tables and add columns too. Formula columns have to be built in the app.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.scribeware.com/customizations/tables.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
