Company blocklist
Block an employer so automated sourcing cannot re-add them after you take them off your board, and choose whether their profile stays.
A
JUse the company blocklist when a company must leave your board and you need automated sourcing to stop putting them back.
Two ways to block
When you Block company, you choose one of two outcomes. Remove from the board is selected by default.
Remove from the board
- The company's jobs are deleted from your board.
- The company profile, its directory entry, and its sitemap entry are gone. The public URL returns a not-found page.
- Backfill, CSV and XML import, API writes, employer sign-ups, and public job submissions that match this company are all rejected.
- The company disappears from your Companies list, from Company sources, and from the company picker on the job form. It is not on your board any more.
- To find it again, filter Companies by Block status → Blocked. It is listed there marked Removed, which is where you unblock it.
Pick this when you want the company gone and to stay gone. This is what most operators want.
Keep the profile, stop sourcing
- Every published job for that company is archived. Drafts are left alone.
- Company-vertical backfill registration is stopped when it was active.
- Automated writers reject new jobs for that employer: backfill sync, CSV and XML import, and Operator API, MCP, and CLI bulk or upsert paths.
- The company profile stays on your board. You can still post a job for them yourself, and employers and public submitters can still post if those are enabled.
Pick this when you want to stop pulling in a company's jobs but keep their page, for example an employer who posts with you directly and whose jobs you do not want duplicated from a feed.
You can upgrade a kept-profile block later with Remove from board on the row menu.
Deleting a blocked company
Deleting a company that is on the blocklist does not take it off the blocklist. It removes the profile and jobs from the board and keeps the block, exactly like the remove outcome above. That is deliberate: a plain delete leaves nothing behind, so backfill would re-add the company within a day.
To delete a blocked company completely, unblock it first, then delete it.
Unblocking
Unblocking is explicit. It does not republish archived jobs. A removed company comes back as an empty profile, and backfill may add its jobs again.
How identity is matched
Writes are blocked when they match any of these stable keys:
- The board company id
- Linked Forager company id
- Normalized website domain
- For a removed company, the exact company slug as well
Name substring matching is not used for the blocklist.
Operator UI
You can block from Companies or from Grow → Backfill. Both write to the same list.
From Companies:
- Open the company row menu.
- Choose Block company.
- Pick Remove from the board or Keep the profile, stop sourcing, optionally add a reason, then confirm.
From Backfill:
- Open Grow → Backfill.
- Find the company on Backfilling, Backfill available, Review, or Unsupported.
- Open the row menu → Block company.
- Pick an outcome, optionally add a reason, then confirm.
Company sources has a Blocked tab. Unblock from that tab, or from the Companies row menu (Unblock company).
API and CLI
# Block and remove from the board (default in the dashboard)cavuno companies block <companyId> --remove --reason "legal request" --yes# Block and keep the profile (archives live jobs, stops automated re-import)cavuno companies block <companyId> --reason "posts directly" --yes# Unblock (does not republish archived jobs)cavuno companies unblock <companyId> --yes
HTTP:
POST /v1/companies/:id/blockwith optional body{ "reason": "...", "remove": true }. The response reportsremovedandremoval_scheduled.POST /v1/companies/:id/unblock. The response reportswas_removed.DELETE /v1/companies/:idon a blocked company keeps it blocked and removes it from the board. Unblock first to delete it completely.
MCP agents use the same Operator API paths.