Back to playlist · Clients Guide to Gigdesk
Part 5 of 5 ·Oversight ·6 min read
✦ Clients guide · Chapter 5

Track work with notifications

Follow every workspace conversation as a tagged thread, filter the logstream, and hand 3rd parties a scoped token that can read and post without an account.

Copies the whole guide — steps, prompts & all — for your AI agent

Once a project is live, the last thing you want is to keep pinging people for status. Gigdesk gives you two quiet windows into the work: the Notifications pseudochat, where every event is a tagged message you can filter, and each project's Tasks Queue, where the live gigs show their state at a glance. This last client chapter shows you how to follow the whole thing without interrupting anyone.

Notifications is a pseudochat

Open Notifications from the project sub-nav and you get a running feed for the workspace. It's a pseudochat: every message carries tags, and each card shows who sent it (for example from System), a timestamp, and a Mark read control. There's a Tags filter at the top — the trick is to pick a unique tag as a tracer and filter on it, so one conversation reads as a single clean thread instead of getting lost in the stream.

Notifications pseudochat with tag filter and a System event Filter by tracer tag A tagged message
Notifications is a pseudochat — every message carries tags; a unique tag acts as a tracer so each conversation reads as a filterable thread.
Note Anything holding a notification token can read and send here — it's not limited to logged-in people. Each workspace auto-mints a System token and a Default token, so events start flowing the moment the workspace exists.

Tokens let your tools post

Notification tokens are how a third party — or one of your own scripts — reads and posts to the feed with no Gigdesk account at all. Hand a tool a token and it can drop a tagged message in whenever something happens: a build finished, a proof was submitted, a queue drained. Because those tokens exist per workspace out of the box, you rarely have to set anything up; you just decide which tracer tag each source should stamp on its messages.

The Tasks Queue shows the live gigs

Notifications tells you what happened; the Tasks Queue tells you what's running. Open a project's Tasks page and you see the Dollar Platoon task-queue gigs at a glance — each queue card with its price, a LIVE badge, and links to Timeline ↗ and Manage ↗. Between the two views you can follow a project end to end without asking anyone for an update.

Step by step

  1. 1

    Open Notifications

    From the project sub-nav, click Notifications. The feed shows every tagged message — sender, timestamp, and a Mark read control on each card.

  2. 2

    Pick a tracer tag

    Decide on a unique tag for the thread you care about — say tracer=acme. Have your chatbots and tools stamp it on their messages.

  3. 3

    Filter on the tracer

    Use the Tags filter to narrow the feed to that tracer. Now one conversation reads as a single thread you can scan top to bottom.

  4. 4

    Cross-check the Tasks Queue

    Open the project's Tasks page to see the live gigs — price, LIVE badge, and each queue's Timeline ↗ — so you know what's still in flight.

Client Tasks Queue showing live gigs and their timelines Live queues at a glance
Between Notifications and each gig's timeline, you can follow the whole project without pinging anyone.
Give each thread its own tracer Don't reuse one tag for everything. A tracer per client or per batch of work keeps the filter meaningful — you can always pull up exactly that thread later, and your tools can post to it without an account.

Key takeaways

  • Notifications is a pseudochat — every message is tagged; filter on a unique tracer tag to read one conversation as a thread.
  • Notification tokens let third parties and your own tools read and post with no account; each workspace auto-mints a System and a Default token.
  • The Tasks Queue shows the live gigs at a glance, so between it and Notifications you can track a whole project without pinging anyone.

That's the client playbook.

You can build a project, invite gigworkers, fund the queues, and follow the work — all without a status meeting. If you're ready to run one, request an invite; if you're curious how the other side lives, read the freelancers guide.

Request an invite Read the freelancers guide