← Docket · Guide, by task · FAQ · Security · Terms

Five minutes a source, on your own credentials

Connect the one place your work actually arrives, paste a credential you made yourself, and in five minutes you have a real list of what is waiting on you. There is no Docket account in the middle: every credential is yours, stored on your Mac, and revocable at the vendor without telling us. Nothing below is mandatory, and every source is off until you turn it on. Each section says what the connection needs, what that credential can reach, and what Docket will and will not do with it. First run opens the Connect wizard and asks the same questions; this page is here if you would rather read first.

Jira (the core source)

One token per account, and every client's board arrives in one ranked list. Docket works with Cloud and Data Center, several accounts at once, and routes every write back to the account that owns the ticket, so you never have to remember which Jira you are answering in.

Jira Cloud

1. Create an API token: Atlassian account → Security → API tokens.
2. In Docket: Sources → Jira, then add your site URL, your login email and the token.

Jira Data Center / Server

1. Create a Personal Access Token: your profile → Personal Access Tokens.
2. Add the base URL and the PAT. No email needed, since DC authenticates the token alone.

What the token can do: whatever your Jira user can. Docket reads your assigned issues and writes only what you tell it to, whether that is a comment, a transition or an estimate, and every write lands in the in-app audit log.

Linear

Your Linear issues join the same list as your Jiras, and your answers go back as comments, states and estimates. It takes a personal API key: Linear → Settings → Security & access → Personal API keys, the personal page rather than the workspace one. In Docket: Sources → Linear, and paste it. Your workspace and your teams are read from the key, so there is nothing else to fill in.

What the key can do: whatever your Linear user can. Docket reads the issues assigned to you and writes back only what you send or approve: a comment, an assignee, a state change, a new issue, an estimate, a priority. An estimate follows your team's own scale in Linear, points or T-shirt sizes, and a team with estimates turned off shows no estimate control. No work log, because Linear has no native time tracking and a verb we cannot honour is worse than one we never offered. It is one GraphQL endpoint, api.linear.app, so an outbound firewall shows a single host doing all of it rather than a spread; the security page names it and says what each call sends.

Figma (comments and @mentions)

The comments waiting on you arrive with your tickets, including the ones addressed to your teammates, and you answer them without opening the file. To connect, open Sources, choose Figma and press Sign in with Figma. A browser tab opens on Figma with a consent screen that names what Docket asks for: who you are, the comments on a file and the right to reply to them, and the file's name and its contents. Approve it, then add the files you want watched.

What that sign-in can reach: the files you add and any Figma file linked from your issues. It cannot list the files in your team. Docket reads the comment threads on those files, draws a picture of the spot each comment is pinned to, and posts the replies you write here. The only thing it ever writes is a comment. It cannot change a design, move a file or touch your team's settings. The grant is kept in your Keychain on this Mac, and you can revoke it in Figma → Settings → Connected apps. FigJam files ride the same connection.

If you want Docket to find the files in your team for you, which a sign-in cannot do, there is one escape: paste a Figma personal access token under Scan your whole team with a pasted token. That token reaches everything your Figma account can, all files and teams, so start with the sign-in.

Calendar

The recommended route needs no setup at all: Docket reads your Mac's own calendars through Apple's EventKit, so it sees whatever Calendar.app has (Google, Exchange, iCloud, all at once). macOS asks for permission once, and focus blocks you accept are written back the same way. No OAuth client, no tokens, nothing to expire.

Confluence

The pages that mention you stop being something you go looking for. Base URL plus a token (the same token flow as Jira on the same instance), and they arrive beside your tickets.

Obsidian

Your own open tasks join the same list. Point Docket at your vault folder and it reads the unticked boxes (- [ ]) out of your notes. Nothing is uploaded anywhere, because it is a folder on the machine you are sitting at.

Dovetail

Your research highlights land in the Research view, on an API token from Dovetail's settings.

Miro

A token from a Miro app (your profile → Your apps → create → install; scope boards:read). Plan-dependent: Miro's API access differs per subscription tier, so if your plan doesn't expose the REST API, the source card will say the connection is refused rather than pretending it's quiet.

Email (IMAP, read-only)

Any IMAP mailbox: server, address, password, though Gmail and iCloud require an app-specific password (the add-form links the steps). Unread subjects and senders appear on Today; rows open in Apple Mail when the message is there. Read-only by protocol: the app opens the mailbox with EXAMINE and fetches with PEEK, so it cannot mark anything read, move a message, or send. Headers only, with one exception: the app fetches a calendar invitation's text/calendar part so it can show the invite (title, time, "awaiting your reply"); prose bodies are never fetched or stored. Shown only, never counted.

Dictation (system-wide)

Hold the dictation key (right ⌥ by default), speak, release: the words are typed at your cursor in whatever app is focused. Transcription runs on this Mac with Apple's on-device speech models; the audio never leaves the machine, and Dutch and English work in the same sentence. Docket feeds the recognizer your own ticket, project and teammate names, so "KES-214" comes out as KES-214. The mic is live only while the key is held.

Switching language without letting go: tap ⇧ while you are still holding the dictation key to cycle NL → EN → AUTO. The pill shows the choice as you make it, the choice is armed when you release, and it writes the same setting the Seat tab does, so the pill and Settings can never disagree about which language is next.

Two macOS permissions: Microphone (asked on first use) and Accessibility, which lets Docket press ⌘V for you in the target app. If Accessibility isn't granted, the text still lands on your clipboard and Docket tells you to paste it yourself. The Dictation page keeps a history you can copy from, newest first.

Connectors from the library

For the tools your work lives in besides the ones above, Docket ships a library of connectors: GitHub, GitLab (gitlab.com or your company's own), Asana, Notion, Trello, Todoist, ClickUp, monday.com, Sentry and Linear. In Docket: Sources, under Not connected, pick your tool and paste a token you made there. Some also ask for one more thing, such as a workspace, a board or a database, and the drawer says which. There is no URL or field map to write: the library already knows the address and which field is the title, the status and the date.

What a connector from the library brings in counts: the work assigned to you lands in Needs you and My work beside your Jira issues. Each card in the library says counts or shown only before you connect anything, and a row assigned to someone else is tallied on the source's card and left off your list. These connectors read and write nothing back, so you answer in the tool itself. The Linear connector above is the one that also writes back; its library template only reads. The token goes in the macOS Keychain with the rest, and the security page names each host.

Your own feeds

Any other JSON endpoint can become a card on Today: a URL, an optional auth header, and a small field map (which array, which field is the title, the date, the link). Feeds are shown only, never counted, so they can't distort what "needs you" means. A row that doesn't match your map is dropped and counted on the card, so a wrong map is visible instead of silently blank.

Meetings: what the review screen tells you

A recording ends on Review & route, which shows what was extracted and changes nothing until you say so: edit anything, nothing is created until you save. A long transcript does not fit an on-device model's context in one pass, so Docket splits it and the same line says how many pieces it took, summarised in 3 parts, rather than summarising the first slice and presenting it as the whole meeting. If a part comes back with nothing, that is said too.

When a source looks empty

You never have to wonder whether a quiet source is quiet or broken, which is the failure that makes an aggregator untrustworthy. Docket tells you which it is:

1. "This filter has returned work before — an empty list means an empty list." Genuinely quiet. Enjoy it.
2. "This filter has never returned anything since it was set." Usually the filter, not the work, and the message links straight to the setting to check.
3. A source that is down says on its own card what failed, in one line: the HTTP status where there is one ("Figma credential refused (401)"), or the class of failure where there is not, which is one of timed out, host not found, connection refused and path not found. The views it feeds say the list is incomplete rather than showing a clean zero, and the repair itself sits in the Configure drawer, where there is room for a sentence.

For anything deeper: Activity → Copy diagnostics produces a paste-safe report (names and hosts are pseudonymised) that shows exactly what each connection last returned. Support conversations start from that paste, so they start from facts.

Billing

What you are charged, when it renews and what happens when you cancel is written out in the billing policy, in the terms rather than in small print under a price. It is linked from the pricing section too, so the answer sits next to the decision instead of three pages away.