Workspace

Run the operation, not the inbox.

Gent Workspace is where a team runs recurring email work. Each lane gives one operation its intake, owners, workflows, and record, so the work has a clear place to move.

The unit of work

One lane, one recurring operation.

A lane is not another mailbox label. It is the operating home for something your team repeats: qualifying leads, collecting invoices, triaging customer requests, or gathering approvals.

The lane is the operation. Workflows are the rules and automations inside it: classify an arrival, create a task, hold an approval, or hand work to another system.

Intake

The inbox and threads where the work begins.

Owners

People accountable for decisions and progress.

Workflows

Rules, tasks, review, and system handoffs.

Record

The files, activity, and history behind the work.

Start with the job

Useful before it is automated.

Lead response

Incoming sales email has one owner, qualification steps, a draft/review path, and a record of the next action.

Invoice intake

Vendor mail and attachments stay tied to the finance work, its review point, file record, and downstream handoff.

Customer triage

Requests are classified, assigned, and escalated with thread context intact instead of disappearing into a shared queue.

See what runs now and what remains in review.

For builders

From workflow to operation.

Test a workflow in Devspace first. When it becomes recurring business work, put it in a lane and activate that lane once its inbox, owner, and automation are ready.

Test

An unassigned workflow or resource is still being explored. It is not yet a lane.

Prepare

A draft lane gives the operation its name, inbox, owners, workflows, and controls before it runs.

Run

An active lane is a recurring operation with its work record, review path, and automation in one place.

Pause a lane to stop its automation while its inbox keeps receiving mail, or archive it when the operation is complete.