# Tables Spiich builds for you

> An admin turns a shared table into one whose rows Spiich picks for each person on a schedule, from a plain-English brief. Spiich only chooses from records already in your CRM.

- Source: https://spiich.ai/help/your-data/tables-spiich-builds-for-you
- Section: Your data in Spiich
- Who can do this: Workspace admins
- Time: 5-10 minutes
- Last updated: 2026-08-24

## Before you start

- You are a workspace admin.
- At least one active teammate to generate the table for.
- Credits available on your workspace, for manual rebuilds and any agents you attach.

Most tables use a filter you write once and it stays that way. This one uses a brief instead, plain English that tells Spiich what belongs, and Spiich re-picks the rows itself on a schedule you set.

## What it is

A normal [table](/help/your-data/tables-and-views) is defined by a saved filter and sort that never move on their own. This one replaces the filter with a brief, for example `The deals I should push on today. Prefer ones with real momentum I have not touched this week.` On the schedule you choose, Spiich rereads the brief and picks the rows again, one set per person in the audience.

Spiich only chooses from records already in your CRM. It never creates a record and never searches the web: the row-picking agent works entirely from what your workspace already syncs.

These tables live in their own **This morning** section on the Tables page. Each row there carries the table's name, a **Spiich** badge and a **Configure** link straight into its setup.

## Turn a table into one Spiich builds

1. **Start from a shared table**
   Go to [`Tables`](https://app.spiich.ai/tables), click **New table**, or open an existing table and click **Edit**. Name it, choose the primary entity and add columns, same as any other table.

2. **Switch on Let Spiich pick the rows**
   Scroll to **Let Spiich pick the rows** and turn it on. The table is forced to Shared scope: it always has an audience, never a single owner.

3. **Write the brief**
   Under **What should Spiich pick?**, describe which records belong in the table in plain English, up to 2000 characters. Say what to prefer, not only what to include.

4. **Set Rows to keep**
   Pick a number from 1 to 25. It is a ceiling per person, not a target: Spiich fills up to that many rows, never more, and can return fewer.

5. **Set the rebuild schedule**
   Under **Rebuild**, pick **Every day**, **Every other day** or **Every week**, and the hour of day. Tick **In each person's own local time** if each person should regenerate at their own local hour rather than one fixed hour for the whole workspace.

6. **Choose the audience**
   Under **Who it is generated for**, tick each teammate who should get their own version. Only active members show up here.

7. **Optionally add agents and a restrict filter**
   Under **Agents it may run on the rows**, pick up to 3 background agents to run on whatever Spiich picks; each run bills the person the table was generated for. Under **Restrict what Spiich can pick from**, leave it empty to let Spiich search everything that person can see, or add a filter for anything that must never appear, whatever the brief says. A restrict filter is a hard boundary the brief cannot override.

8. **Turn on the schedule and save**
   Switch on **Generate on this schedule** (it reads **Paused** while off), read the cost summary, and click **Save**. The table appears under **This morning** on the Tables page.

## What a built table looks like

Every row carries a **Why it's here** column: a short explanation of why Spiich picked that record. A row that was not there at the previous rebuild carries a **New** badge, so you can see what changed without comparing lists by eye.

These tables cannot be filtered or sorted from the header. The agent's own ranking is the order. The search box still works over whatever rows are currently loaded.

> **Note:** Editing the brief updates it for the next rebuild only. The rows already on the table are not regenerated on the spot; they stay exactly as they are until the schedule runs again, or until someone triggers a manual rebuild.

## Rebuild it now

You do not have to wait for the schedule. Click **Rebuild** in the table header, or **Generate now** / **Run again** in the banner above the rows, to run the agent immediately for yourself.

A manual rebuild is billed in credits, shown before you commit, and only offered to people already in the table's audience. Anyone else sees a message explaining that they are not in the audience yet, and that an admin can add them.

The banner above the rows always states which of four situations you are looking at:

| Banner state | What it means |
| --- | --- |
| Fresh rows | The last rebuild for you finished normally |
| Rebuilding | A run is in progress right now |
| Deliberately empty | Spiich read through your records and found nothing worth surfacing today |
| Left over from a failed run | The last rebuild did not complete, so you are seeing an earlier run's rows |

## Limits

- Rows to keep: 1 to 25 per person. Rebuild interval: every 1 to 7 days. Brief: up to 2000 characters. Audience: up to 200 members. Agents it may run: up to 3.
- A table Spiich builds is always Shared. It cannot be a personal table, and it has no individual owner.
- It cannot be filtered or sorted in the header. The order is the agent's ranking, not yours.
- Editing the brief never regenerates existing rows on the spot; they stay until the next scheduled rebuild.
- Only workspace admins can create one, or change its brief, schedule, audience, agents or restrict filter.
- A manual rebuild is only offered to people in the table's audience, and it is billed in credits, shown before you commit. The chat assistant can manage an ordinary table, but it cannot change a built table's row-picking setup.

## If something goes wrong

**"You are not in the audience yet."** An admin has not added you under **Who it is generated for**. Ask them to open the table, click **Edit**, and tick your name.

**"The last rebuild failed, so these rows are from an earlier run."** The most recent run did not finish, and the previous rows were kept rather than cleared. Click **Run again** in the banner, or **Rebuild** in the header, to try again.

**"Spiich read through your records and found nothing worth surfacing today."** Nothing matched the brief, often because the restrict filter is too narrow or the brief is too specific. An admin can loosen the filter or reword it; anyone in the audience can click **Run again** to retry as is.

**Rebuild will not start, and the banner reads "Already rebuilding".** A second rebuild cannot start while one is already running for you. Wait for it to finish, then try again.

## Frequently asked questions

### Who can set up a table Spiich builds?

Only workspace admins can create one, write its brief, or change its schedule, audience, agents or restrict filter. Once it exists, anyone in its audience can trigger a manual rebuild of their own version.

### Does Spiich ever create records to fill one of these tables?

No. It only chooses from records already synced into your CRM, and it never searches the web. If nothing in your CRM matches the brief, the table comes back deliberately empty rather than inventing something to fill it.

### Can I filter or sort a table Spiich builds?

No. Its own ranking is the order, explained per row in the **Why it's here** column. You can still search over the rows currently loaded, the same as any table.

### What happens to the rows on screen if I change the brief?

Saving updates the brief for the next scheduled rebuild only. The rows already on the table are not regenerated on the spot; they stay until that rebuild runs, or until someone in the audience triggers a manual one.

## Related

- [Tables and views](https://spiich.ai/help/your-data/tables-and-views)
- [How Spiich and your CRM stay in sync](https://spiich.ai/help/your-data/crm-sync-rules)
- [What background agents are](https://spiich.ai/help/background-agents/background-agents-overview)
- [Background Agents](https://spiich.ai/product/background-agents)
- [Background agents setup guide](https://spiich.ai/articles/background-agents-setup-guide)