Features

Six views

Switch any table between a grid, a status board, a month calendar, a timeline, a card gallery and a dashboard of totals. Every view reads the same records with the same filters, so nothing has to be copied to be seen differently.

More about six views

Grid: Sort, search and filter by status; edit in a record drawer that shows the full history. Compact and comfortable density.
Board: One column per status, so the state of every piece of work is visible at a glance.
Calendar: A month view placed on the table's due date — or its first date, date-time or timeline field. Step back and forward a month at a time.
Timeline: Bars from start to finish for records with a timeline (date range) field.
Gallery: Cards with the fields that matter, for tables that read better as a set of things.
Dashboard: Totals for number and currency fields and a count of work by status, across every matching record — not just the current page.
Saved views: Save the filters a team works from as a named view. It appears as a chip above the table for everyone with access.

Guest access

Invite someone outside your workspace to a single table. You choose which fields they can read, which of those they can edit, and whether they see specific records or every record. Their access expires on its own.

More about guest access

Field by field: Pick the readable fields, then the editable ones. A guest can never edit a field they cannot read.
Record by record: Share chosen records, or all current and future records subject to the table's access rules.
Bound to one verified email: The invitation only works for someone signed in with the invited, verified email address. It never joins or moves their own account.
Expires by default: Invitations expire after 7 days. Accepted access lasts 90 days unless you revoke it sooner — revocation takes effect immediately.

Bulk editing

Select records in the grid, choose a field, set the new value and update them together. The change is all-or-nothing, it respects each record's revision, and the last bulk edit can be undone in one click.

More about bulk editing

All or nothing: Every record in the batch is updated, or none is. If someone changed a record since you loaded the page, the batch stops instead of overwriting their work.
Undo that is safe: Undo restores the previous values — and refuses to clobber edits made after the bulk change.
Same rules as one-at-a-time: Only fields you can edit are offered; validation and permissions are the same as editing a single record.
From the API too: The REST API accepts batches of up to 100 changes with a request ID, so a retried script never applies a change twice.

Independent review

Ask for a review of a saved record and an approver decides it. The person who requested or created the work cannot approve it, and the approval is tied to the exact version that was reviewed.

More about independent review

No self-approval: Requesters and creators cannot approve their own work, whatever their role.
Bound to what was seen: An approval records the version of the record, its linked records, the table's schema and any evidence. Change any of them and a fresh approval is needed.
Waiting work in one place: My work lists the reviews and records assigned to you across every table you can open.
AI can help, never approve: Optional AI triage summarises or sorts work using only the fields you allow. It never grants an approval.

Forms & import

Publish a response form that anyone with the link can fill in, or bring an existing list across from a spreadsheet with a preview of every row before anything is saved.

More about forms & import

Public response forms: Choose the fields to ask for and share the link. Each response becomes a record.
CSV with a preview: Upload or paste a CSV, map columns to fields and see per-row validation before committing. A repeated import of the same file is safe.
Export without surprises: Export the current page as CSV. Cells that a spreadsheet would treat as a formula are neutralised.

API & integrations

Create a key bound to one table, give it only the operations it needs, and use it from scripts and YakPipes workflows. Records can also generate documents in YakDocs and keep files in YakFiles.

More about api & integrations