Which boards support which route
The four routes, the boards behind each one, why a board can be filled but not sent, and what the refused list is actually refusing.
Every listing gets a route and a reason, printed before you press anything. There are four.
| Route | What happens | Where |
|---|---|---|
| Sent for you | Submitted directly on the board | Boards that accept a direct submission |
| Filled for you | Opened in a real tab, filled, left for you to send | Boards with a form adapter |
| By hand, with help | A copy-out screen in the board's own field order | Everywhere else |
| Refused | Nothing runs | The refused list below |
Boards with a form adapter
Greenhouse, Lever, Ashby, Workable, SmartRecruiters and Recruitee. These can be filled, by the extension on a page you are on and by a queued run.
Boards that can be submitted without you
Greenhouse.
That is a shorter list than the filling one on purpose. A board whose form fills reliably is not the same as a board whose submit step has been measured against a live posting, and offering the second on the strength of the first is how a queue promises a send and quietly performs a fill. Where the fill works and sending is unverified, the honest answer is the filling route.
The refused list
| Board | Why |
|---|---|
| Automating it risks your own account, so it is blocked and nothing runs there | |
| Indeed | Forbids automated applying |
| Workday | Needs employer-issued credentials no third party can hold |
| SuccessFactors | Needs an account of its own |
| iCIMS | Needs an account of its own |
| Taleo | Needs an account of its own |
These are decisions rather than gaps in the roadmap. The same list is checked in three places: when the route is printed, before a tab is opened, and by the extension when it arrives on the page. It used to be three lists that disagreed, which meant a candidate was told a form would be filled, watched it not happen, and got the reason only by opening the run log.
What the routes mean for a real search
Measured against the live index, most listings are not submittable by anyone: a majority need a person in a browser, a large minority can be filled by machine, and a smaller share accept a direct submission. So "apply to everything automatically" is not a product anyone can build. What can be built is: submit what is submittable, fill the rest, and lay out the remainder for pasting.
The document does not care
Tailoring works on any posting you can read, including every board on the refused list. The route decides how the application is delivered, not whether you get a document for it.
For those, use apply by hand on a manual board.
Questions about this
Why can Lever be filled but not submitted?
Because sending has only been verified on boards where it was measured against a live posting. A board whose form fills reliably is not automatically a board whose submit step has been proved.
What does refused mean?
A decision that stays. Either the application sits behind an account the employer issues, or the board forbids automation.
Is the list of supported boards growing?
New form adapters get written. The refused list is a different thing and is not a backlog.
What happens on a board with no adapter at all?
You get the tailored document and the copy-out screen, laid out in that board's own order, and you paste it in.
Check the route before you queue
Every listing prints its route before you press anything. That line is the promise, and it is checked against the same list the extension enforces.
Open Involve Resume