NEWSROOM FLOOR In pilot Sign in

Help desk

Start here

Write your first article

The path most writers here settle into: gather your sources first, then let the Copilot write the draft. Four steps from a blank desk to a piece ready to publish.

  1. New pieceOn the desk, press + New piece. Give it a headline, choose News or Blog, and press Create. It opens as a draft.
  2. Pick your writerClick the byline and choose who the piece is by.
  3. Gather your sourcesOpen the Corpus tab on the right, search the record, and press Cite on every fact you want to build on.
  4. Draft itOpen the Copilot tab, press Write from my sources, then Apply to the page. Edit, and publish when it is ready.
Start your paper →

Kick off your first automated article

Let the newsroom write on a schedule. Open The automation, pick the sections and how many stories each, and set who approves. Press Write news now for a batch straight away; drafts land on the desk for you to read.

Build a paper →

Craft articles from sources

Strong pieces stand on facts you placed. Cite from the Corpus before you write; the Copilot uses only what you cite. Writing your own opinion instead? Flip the piece from News to Blog and it runs under the Opinion label without a source floor.

Start your paper →

Or search everything below. Type what you want to do; the list filters as you type. Press Ask and the desk answers from these notes and points at the exact control. Sign in and every link opens your own paper.

Need a person? Your tickets · ask for a feed, report a problem, request a feature. A person reads every one.

Nothing here matches that yet. Press Ask, or ask a person.
Getting started
How do I write my first article by hand?
Four steps. On the desk, press + New piece, give it a headline, choose News or Blog, and press Create; it opens as a draft. Click the byline to pick the writer. Open the Corpus tab on the right, search the fact record, and press Cite on each fact you want the piece to stand on. Then open the Copilot tab, press Write from my sources, and Apply to the page. Edit, and publish when it is ready.
The desk →
How do I kick off my first automated article?
Open The automation. Pick the sections and how many stories each, and choose who approves: publish as written, or hold each piece for you. Press Write news now for a batch straight away, or set automatic writing to Daily to run every day. Drafts land on the desk; the ones that clear the fact check publish, or wait for your approval.
The automation →
How do I build a paper from my website?
Paste your site's address in the one field on the landing page, or, signed in, open New paper (the card on Home, or + New desk in the desk menu) and choose From your website. The floor reads your site, shows the masthead it proposes with dropdowns for theme, type, language, mark and colour, and after you sign in it builds the desk, the writers and the first stories. A site that refuses automated readers still gets a paper drawn from its name and mark.
Build from my site →
What happens after I build a paper?
The floor writes your first stories from the fact record, facts at least two newsrooms carry, files them as drafts you read first, and paints portraits if you ticked that. Nothing reaches readers until you go public. On your first day, read the drafts on The desk, open Settings to see what the paper covers, then switch it public under How it publishes.
The desk →
What should I do on my first day?
Three things. Read the first drafts on The desk and approve or edit them. Open Settings and check What it covers: the sections and subjects drafted from your site. Then go public under How it publishes, Reach. Everything else has a sensible default; charging readers, your own domain and a logo can all wait.
Settings →
Where is everything? The settings are grouped.
Settings opens on six cards. What it covers, Where the facts come from, How it publishes, How it looks, Who can work on it, and Developers. Each opens into its own cards. The strict rules, how many newsrooms must carry a story and how long a lone story waits, have their own Strictness card under What it covers. The defaults are right for almost every paper.
Settings →
Where do my paper's stories come from?
From the fact record, claims read from thousands of sources and kept only when at least two independent newsrooms carry them. Your paper draws the facts its subjects and sections claim. To add a source of your own, paste an RSS link or your own links under Where the facts come from.
The sources →
Can my paper be in Spanish?
Yes. Under How it publishes, Language and units, switch Spanish on, pick the register (Colombian, Mexican and more) and set what the paper opens in. Every piece is rendered into Spanish beside the English record, and the subtitle is translated for the other view when you save. To use the console itself in Spanish, pick Spanish in the footer; the choice follows your account.
Language and units →
Where is everything? How is the app laid out?
In rings, and you step inward. Home lists every paper you work on, with the numbers for all of them together. Open a paper and you are on its floor: that one paper's numbers and its rooms. The rooms are the desk (write, edit, publish, take off air), the masthead (your writers), Live, Readers, Members and files, Settings, and Credits and costs. Everything that configures the paper is inside Settings. The line under the header always says where you are, for example Home / your paper / Settings / Brand and images: click any part to go back up, or the small arrow beside a part to jump to its neighbours.
Home →
Where did The floor, The desk and Settings go from the top of the page?
They moved inside the paper they belong to. The old tabs opened the desk or the settings of whichever paper you had used last, which was easy to get wrong with more than one paper. Now you pick the paper first on Home, and its desk and its settings are rooms on that paper's floor. What used to be called the floor, the page with all your papers, is Home. Old links and bookmarks still work and land on the new address. Help is in the menu under your name.
Home →
Money
How do I charge readers for my paper?
Open Desk settings and pick the Paywall tab. Set a price, monthly or yearly, and how many articles a reader gets free. Tick Turn the paywall on and save. Readers past the free count see a wall and subscribe through the same checkout your own plan uses.
Paywall settings →
Where does the money go when a reader subscribes?
Your share of each payment lands in your DRM3 wallet as credits, every billing cycle. Your account page shows the balance.
Your account →
Can readers see anything before they pay?
Yes. The free-article count on the Paywall tab decides how many articles a reader opens before the wall. Set it to 0 to wall every article, or 3 to let them read three.
Paywall settings →
How much does it cost me to run this paper?
Writing spends your daily credits; the credit chip in the header shows the balance and links to every cost. A paid plan raises the daily allowance. You can also bring your own inference key on any plan.
The costs →
Who owns this paper, and whose credits pay to run it?
Every paper has one owner: the account that carries its plan and credits. Writing and the automation spend the owner's credits, whoever on the masthead starts the run. Readers pay for their own questions on the Signal Desk from their own credits, never yours. Admins you add can run the paper but do not pay for it. To move the plan and credits to another person, transfer the paper.
Admin →
If I add an admin, do they pay to run the paper, or do I?
You do. An admin runs the paper on your behalf, so every piece they write and every run the automation makes spends the owner's credits, never the admin's. The one thing an admin pays for is their own reading: a question they ask on a Signal Desk comes from their own credits. Adding a seat never moves the bill; only a transfer does.
Admin →
Where do readers see my price and subscribe?
On your paper's channel page, at /subscribe on its address. When the paywall is on, the page leads with the price, the free articles a reader gets first, your one line, and the Subscribe button. Set the price on the Paywall tab in Desk settings.
Channel page →
How does a reader cancel their paid subscription?
On their own, online, with no login. Their receipt email carries a link to their subscription page: the price, the next charge and a Cancel button. The paywall, their RSS feed page and the Members page each carry a Manage or cancel link to the same page. A reader who lost the email enters the address they paid with at drm3.network/account/subscribe/newsroom-floor/manage and gets a new link by mail. Cancelling keeps their access through the period they paid for, stops every later charge, and can be taken back until that date. You do nothing, and your share of the payments already made is unchanged.
The reader's manage page →
Publishing
How do I approve pieces before they go out?
Open The automation. Under Who approves, pick Hold each piece for my approval. The newsroom keeps writing on its schedule, and every piece waits on your desk as a draft. Approve, edit or reject it from the desk home or the docket.
The automation →
What if I forget to approve a piece?
Under Who approves, choose what happens when you do not get to a piece: wait for you, park it after N hours, or publish it after N hours. Publish-after only sends a piece that already cleared the fact check.
The automation →
Can I write everything myself?
Yes. Set automatic writing to Off. Press + New piece on the desk, write, place your sources in the Record tab, and press Publish. Or press Write news now and the newsroom drafts pieces for you to finish.
The desk →
Why will my own article not publish? It says it stands on 0 sources.
A news piece must stand on sources you placed. If it is your own writing, an opinion or a company post, click the small chip next to the headline that says news and flip it to blog. A blog piece publishes without a source floor and carries the Opinion label.
The desk →
How do I add sources to a piece?
Open the piece. In the right pane pick Record to see the facts behind it, or Corpus to search the whole fact record. Search with the magnifier, press + Cite on a fact to place it, or tick the results you want and press Summarize in Copilot to get a short grounded briefing you can cite from. The Copilot can then write the piece from what you placed.
The desk →
Can I publish at a set time?
Yes. Open the piece and press the clock next to Publish to schedule it. It goes live at that time with a signed receipt.
The desk →
How do I take a story down?
Open it and press Off air. Readers see nothing; the story and every version are kept, and you can put it back on air any time. To record that a story was wrong, use Redact instead: it stays on the record with your reason.
The desk →
How do I change who a piece is by?
Open the piece and click the byline card to reassign it to any writer on the masthead. Add writers under The masthead.
The masthead →
Automation
How do I make the newsroom write every day?
Open The automation. Set automatic writing to Daily and choose how many pieces a day. Then choose who approves: publish as written, or hold each piece for you.
The automation →
How many pieces will it write?
Up to the number you set on The automation, within your daily credits. A story only prints when two independent outlets carry it, unless you allow labelled single-source pieces under Advanced.
The automation →
It writes about things my paper does not cover. How do I narrow it?
Open The automation, then Coverage. Subjects and themes are exact words. A fact that carries one is yours. Keep them to the one or two words the news prints. A sentence never matches. Tick a topic and the desk reads only facts tagged with it. The brief is matched by meaning, so say in it what the desk does not cover. Click any word on that page to test it against today's record.
Coverage →
How do I change how it writes?
The Voice tab on The automation holds the standing instruction for every piece and the structure of a piece. It sets tone and angle; it can never add facts. Each section can carry its own angle too.
The automation →
Which model writes my paper, and can I change it?
The Voice tab shows the model bench. Pick the one that writes here; your plan decides which are open to you. The fact check always runs on a strong model.
The automation →
Why did it publish nothing today?
The status chip in the title band says why in a sentence. Usually the beat found stories from one outlet only, and the newsroom waits for a second independent outlet. Widen the beat, or allow labelled single-source pieces under Advanced.
Today's material →
My paper keeps printing news from somewhere else. How do I keep it to my own place?
Open The automation, then Coverage. Under Subjects, list your towns, agencies, teams and people. The desk takes them wherever they appear, even in a story that never names your region. Do not list your region or country as a subject. A place name claims every story that mentions it. Put the place in the brief. If one of your names is also somewhere else (San Juan is a county in Utah; Carolina and Florida are US states), add it under Places with a marker that only means your desk, such as Puerto Rico or boricua. The name then counts only beside a marker. Turn on Let the desk read what it is unsure about and an unclaimed fact gets a short yes or no against your brief. Write the brief as you would brief a reporter. Say what the desk does not cover.
Automation →
People
I run many papers with different people. Can I group them?
Yes. Open Paper groups from the desk menu, make a group, title it yourself (a partner's name, a client, a beat) and tick the papers under it. The desk menu then lists your papers under those headings. A group is a container and nothing more: it grants no seat and changes no admin. Seats stay per paper, under Desk settings. The same page lists who admins each paper, so a shared desk shows both names.
Paper groups →
How do I let a colleague work on my paper?
Desk settings, the Admin tab, Seats. Invite by email as an editor, an approver or an admin. The seat activates on their first DRM3 sign-in.
Seats →
Can I hand my paper to someone else?
Yes. Desk settings, Admin, Transfer ownership. They accept by email and take over the plan and billing. The name and address never change.
Admin →
The paper
How do readers see my paper?
Open Desk settings, the General tab, and the Reach group. Sign the publisher agreements once, then switch the paper public. It serves at your-id.newsroomfloor.com. Until then only your seats can see it.
Reach →
How do I put my paper on my own domain?
On the Publisher plan and above. Open Your own domain and type the address under Your own address. You add one record at your registrar and the certificate is ours: a subdomain (news.example.org) is one CNAME to cname.newsroomfloor.com, which any registrar allows; an apex (example.org) is a nameserver change to the two names the page shows, which every registrar allows. The page reads serving on its own, usually within minutes for a CNAME and within the hour of the nameserver change reaching the registry. Nobody attaches anything by hand. Your newsroomfloor.com address keeps working.
Your own domain →
How do I know my domain is pointed at Newsroom Floor?
Open Your own domain. Each domain you added carries its live state in Cloudflare's own words (waiting on your CNAME, record seen and the certificate on its way, waiting on your nameservers, serving, or stopped with the reason) and a Check now button; the floor re-reads every pending domain every five minutes on its own, so you never have to come back. Above that, every address shows what DNS says a moment ago and how many readers arrived on it today.
Your own domain →
How do I change how the paper looks?
Open your paper and press the gear at the bottom right. Pick a theme, type size and face, and press Make these the live defaults. Layout and accent colour are under Desk settings, Appearance.
Your paper →
How do I send readers to my own website?
Under Reach, add a link, a label and one line. They ride the foot of every page of your paper.
Reach →
Can my paper also run in Spanish?
Yes. Under Language and units, switch Also publish in Spanish on and pick which Spanish. Then choose what the paper opens in: a Spanish paper opens in Spanish, and a reader's own pick or the language in the address wins over that. The subtitle you wrote under Identity is translated into the other language when you save, and you can reword either line; the nameplate stays one brand on both views unless you set one per language. Neither view ever shows the other language's line.
Desk settings →
Can readers get my paper by email?
Yes. The subscribe box on your front page collects addresses. On days you publish, subscribers get a digest in your paper's colours. Nothing to switch on.
Your paper →
Can my paper have a full footer, and a Just the facts section?
Both, on Desk settings, Reach. The foot: one tagline, up to five titled columns of links (one per line as Column | Label | https://your-site.com/page, or a path on this paper such as /archive), and a postal address if you print one. It appears on every page. Leave it empty and the paper keeps its plain two-row foot. Just the facts: one switch. On, the front carries a band of the day's most checkable statements from your own stories, each opening the story that cites it, before the stories themselves.
Desk settings →
What is the look, and how do I change how my paper is laid out?
The look is how your paper is drawn: the layout, the theme, the bands on the front in order, and the front's numbers (title rows under the lead, the rail's depth, pieces with deks per section). Desk settings has a tab for it. Wear a named look from the gallery, or leave it on your own settings, and put anything you want changed in the overrides as JSON. The nameplate, sections, sources, prompts and writers are not the look; they stay where they are.
The look →
Can I reorder the bands on my front, or turn one off?
Yes. On the look tab, the overrides take a bands list: the front's bands top to bottom, by name. A band you leave out does not render; a band you move renders where you put it. The names are on the tab (ticker, masthead, nav, cover, facts, news, utterances, wire, newsletter, footer and the rest). The same list goes through the API (PUT /api/v1/papers/{paper}/template) and the MCP tool set_template.
The look →
How do I turn the day cover off, or change how many stories it combines?
The day cover is the wide painted picture at the top of the front, above the first article. On the look tab it has its own card: it is on by default, and one button turns it off, so the front starts at the first article and nothing is painted for the day. While it is on, you can pin how many of the day's biggest stories the picture combines: the director's own choice of two or three, or exactly two, or exactly three. The same two settings, cover and cover_stories, are on the config API and the MCP set_config tool.
The look →
What is the From the wire section on my paper?
It is work from another Newsroom Floor paper that yours carries. When a paper puts its reporting on the wire and you take the offer, your paper picks up its closest pieces each day and shows them in their own section, below everything your own newsroom wrote. Each piece keeps the writer's name and the paper it came from, and opens on that paper, which holds the record. Nothing is copied: you are showing their live article, so a correction they make is a correction on your page too. It never counts towards how many sources one of your own stories stands on.
Desk settings →
How does my paper choose which carried pieces to show?
By how close a piece is to what your paper says it is about. Your Coverage subjects and themes are the test: a piece that the other paper filed under one of your subjects counts for most, then its headline, then its dek and its cited facts, then its body. The closest news piece and the closest opinion piece are carried each day, ranked separately so a busy news day never crowds out the column. A piece with no connection to your subjects is not carried at all, so a wire you take never fills your paper with things your readers did not come for.
Coverage →
How do I report live from an event?
Open Live in the desk menu. Start an event: name it, say where you are, pick who files it. From that moment the paper has a live page at /live. The first line you put on it raises a red LIVE band at the top of the front, with the newest line, the reporter's face and a Follow button; readers who open the page see every update as it lands, without reloading. You can file three ways. Talk: link a Telegram group or chat (the next answer) and everything sent there, words, voice notes, video and photographs, goes on the page as it is said. Say it: hold the talk button on the Live page and speak; your voice is typed out under the recording. Type it: a note, with a photograph if you like. Notes filed from the Live page stay private until you press Put it on the page. Fix the words on any line; take any line off the page and the note is kept. Press Stop to end the event; tick write the wrap-up and every line on the page is gathered into one draft on your desk, in the order it was filed.
Live →
How do I set up Telegram so what I say goes on the paper?
Four steps. One: on the Live page press Link Telegram. A window shows a code like /link K7QM2X; it works once and for thirty minutes. Two: open Telegram. For a group, open the group, tap its name, tap Add Members, search newsroomfloor_bot and add it. For a channel, add the bot as an administrator. For just you, open t.me/newsroomfloor_bot and press Start. Three: send the code in that chat. The bot answers Linked to your paper and gives the page's address. Every chat links on its own: a group and your private chat with the bot are two different chats. Four: start an event on the Live page, or send /live and a name in the chat. Then talk. In Stream mode, the default, every message, voice note, video and photograph goes on the page as it is said, and the bot answers each with two buttons, Pull it off and Clean it up. Send /ask and the bot asks before each line goes on. Send /quiet and lines stay private notes with a Put it on the page button. Start a line with ! to put it on in any mode. /page and /pull move the last line on or off. /end closes the event. /help lists all of it. Everyone in a linked group can file to this paper, so only add people you would give a desk seat.
Live →
Where are All news, past editions and the archive on my paper?
On one row under the search box: Every story (every story the paper is running, newest first, at /all), the last three back issues as date pills, the archive, Staff, the API door and the subscribe landing, with sign-in on the right. The feed and the archive icons sit up on the date line beside the language toggle. The reader panel for the language and theme lives there too.
Desk settings →
Can a reader boost or mute sections?
Yes. 'Customize your mix' under the section nav opens a row of section chips. One tap marks a section MORE (it moves to the head of the columns), a second tap MUTES it (its block and every item filed under it hide), a third clears it. The choice is kept in that reader's browser for this paper; Reset clears it.
Desk settings →
What is 'The data' under a section head?
Live instrument readings for that section: the same readings the ticker carries, bucketed by the section's topic categories (set on the Coverage card in Desk settings, per section), up to four with their instrument and age. Each opens the paper's search on that instrument. A section with no reading shows nothing, and the whole block is off until you switch it on under The data ticker in Desk settings.
Desk settings →
My paper is printing readings that have nothing to do with my beat. How do I choose them?
Desk settings, The data ticker. Two switches say where readings print: the scrolling bar across the top of the front, and 'The data' blocks under each section head. Under them, nine kinds say which readings ride: economy, markets, odds, weather, quakes, the web, crypto, AI and world. Pick the ones that belong on your paper and nothing else appears. A new paper prints no readings at all until you pick some, so a local daily never carries AI model traffic by accident.
Desk settings →
Can the paper sign pieces as a house desk instead of a persona?
Yes. Desk settings › Pictures, portraits and the contact form › The desk byline names it (for example 'Your Paper Desk'); pieces no persona wrote then sign with it, 'from the fact record', the paper's mark standing in for a portrait. Tick 'Sign every piece' to make it the one blanket writer for the whole paper.
Desk settings →
How do I put 'by My Company' next to the nameplate, or fix the exact brand colour?
Desk settings › Pictures, portraits and the contact form: Masthead credit is the short line beside the nameplate; Exact accent colour is a six-digit hex for the wordmark and links when the hue alone does not land your brand. A CamelCase nameplate word (TruthFoundry) carries the accent on its second half.
Desk settings →
My paper is thin. Can it carry the fact record's own stories?
Yes. Desk settings › Pictures, portraits, credits and the contact form › The lake wire files every story the fact record composes (one per thread per day, two or more publishers) on your paper, signed by the desk byline, in the section that claims its category, with a footnote per publisher. Your own line's pieces stand beside them; a same-subject repeat folds to the better-sourced one on the front.
Desk settings →
What does the No. on the dateline count?
The number of days this paper has published, counted from its archive. It is not the day of the year and not a counter anyone can set; a paper that has printed 31 editions reads No. 31.
The desk →
How do I make the paper entirely my own, end to end?
Five steps, all in Settings. The address: open the Your own domain card, add your host, and follow the two-lane page (your nameservers, or one CNAME); make it the primary address once it serves. The look: your mark and its dark twin, the banner, the accent, a theme, the footer columns and your own pages under the masthead. The name on it: a publisher name, a masthead credit, and a desk byline if you want the house to sign pieces. Your readers: they sign in with a DRM3 account on your own domain, the paywall and the briefing work there, and downloads are yours to post. Search engines: verify the property and submit the sitemaps from the Search engines card. What stays is one quiet powered-by line at the foot and the AI disclosure on every byline, which the law requires.
Your own domain →
Is there a page I can read or send that explains putting my paper on my own domain?
Yes, the full walkthrough is one public page. It covers what you get, the two ways to point an address (a subdomain is one CNAME; a whole domain is a nameserver change), the one record you add at your registrar, and what we handle for you. Send the link to whoever manages your DNS.
How to wire your domain →
The desk feels cramped on my laptop. Can I show one or two panes instead of three?
Yes. The bar at the foot of the desk has three toggles: Docket, Page and Panels. Each one is on or off, so you can show one, two or all three; one always stays on. Double-click a toggle to show that pane alone. Option 1, 2 and 3 toggle them from the keyboard and Option 0 brings all three back. Drag the divider between two panes to size them. The desk remembers your shape on this browser.
Open the desk →
Can I approve or reject several pieces at once instead of one at a time?
Yes. When more than one piece is waiting, every row in the approval queue carries a tick box and a Select all appears above them. Tick the ones you want and press Approve selected or Reject selected. Each piece still goes through the same publishing path on its own, with its own receipt, so a piece that cannot publish refuses by itself and the rest still land; the queue then tells you exactly what happened. Twenty-five at a time. One thing is never bulk-approved: a piece the fact check held back. Its box will not approve, the bar says how many it is leaving behind, and you open those and read the circled sentences first.
Open the queue →
While a piece waits for my approval, does the newsroom keep working on it?
Yes. Every few hours it asks the record what has come in about that story since it was written, and the queue row says so: "3 new sources since it was written". Nothing is changed behind you; the draft you were sent is the draft you open. When you open it, Fold these in adds those sources to the piece and rewrites the body so it actually uses them, then hands it back for you to read before you approve. To stop the looking on one paper, set Keep looking for new sources to off in its settings.
Open the queue →
Data
Can I get my paper as data, or let an agent run it?
Yes. Mint a key under Desk settings, API keys. Every story, its sources and the masthead come back as JSON. An admin key runs the whole desk over the API or over MCP.
API keys →
What is the receipt on every story?
A signature over the story's bytes. It proves who filed the piece and that it has not changed since. It is added trust; it does not claim the story is correct. Readers can check it in their own browser from the story page.
Provenance →
Where does my paper get its news from?
From a shared record of the news that DRM3 keeps. Around two thousand sources are polled for it around the clock, in dozens of languages, and everything they publish is turned into facts your writers can stand a story on. Your paper reads whichever of those facts match its beat. The Sources page in the desk menu shows the whole of it: which publishers your paper has actually printed from, how often, and the master list of every source the record is read from, searchable, with each feed link ready to copy.
The sources →
How do I add my own source to my paper?
Open Sources in the desk menu and paste the RSS or Atom link into the box. It is filed to your paper alone: it is polled every few hours, its articles become facts, and no other paper reads it. Most sites publish a feed at /feed, /rss or /feed.xml, and a browser extension or the site's own footer will name it. If you believe the whole record should carry a source you added, use Offer to DRM3 on its row; if we take it, we run it and you no longer have to.
The sources →
A publisher I want is in the list, so why is my paper not printing it?
Because the list says what the record can reach, and your beat says what your paper prints. A story runs when its subject matches your coverage and enough independent outlets carry it. So the fix is almost never the source list: widen or sharpen the subjects and sections in Desk settings, or add the subject to the beats board, which measures whether the record can feed it at all. The Material page shows today's supply fact by fact, with the publisher beside each one, and says which stories are being held and why.
The material →
Help
I need a person.
Open Support from the desk menu or your account menu. Say what happened, attach a screenshot or a file, and a person reads it. The app adds which paper you were on. Replies land on the ticket, in your DRM3 account, and in your email.
Ask for help →
The channel
Where is my paper's landing page?
Every public paper has one at /subscribe on its own address (yourpaper.newsroomfloor.com/subscribe, or your own domain). It says what the paper is and hands a reader every way to get it: the paper, the email briefing, the video edition, the podcast feed, RSS, the API, and the agent edition. /channel and /about lead there too.
The catalog →
How do alerts work, and can they reach my own system?
An alert is a watch you set on a paper: every story as it runs (instant), a daily or weekly briefing, only the sections you name, and the video edition when it posts. It reaches you by email, and, if you give an https address, every alert is also POSTed there as JSON (paper, cadence, sections, the stories with their links, the video) with an HMAC-SHA256 of the body under X-NRF-Signature, keyed by a signing key that is yours: the subscribe API answers with it as webhook_secret, and your alert settings page shows it. Set it on the paper's channel page under Alerts, on your own alert settings page, or by API: POST /api/v1/subscribers with {email, cadence, sections, cast, webhook}; a desk key can add up to 20 readers at once at /api/v1/subscribers. Nobody is alerted until they confirm.
Help →
Where is my paper's video edition?
On your paper's own address at /cast (yourpaper.newsroomfloor.com/cast, or your own domain): the day's newscast, every past edition, the transcript and the signed record. The front page carries the newest edition under the doors row, /podcast.xml is the same editions as a podcast feed, and the desk home's grid links it under Video edition. The paper has to be public for readers to reach it.
The catalog →
Can a subscriber pick which sections they get, or how often?
Yes, from any of three doors, all writing the same choices: as it publishes, a daily briefing, or a weekly one; which sections; and whether the video edition rides along. Every alert email carries a Change what you get link. The landing page's signup form asks the same questions up front, and confirming a signup lands on that settings page. And a reader SIGNED IN to your paper with their DRM3 account sets it on their own membership page at /member, with no email needed: the card there shows what they get, and joining from it puts them on the list at that click, because the account already proved the address.
The catalog →
A reader is signed in to my paper. Can they set what they get by email?
Yes. On the paper's own address, /member is the reader's membership page, and The email briefing card sits on it: what they get today, when they get it, which sections, whether the video edition rides along, and a button to stop the emails. A reader who is not on the list yet gets one button to join, and joining there needs no confirmation email, because signing in already proved the address. The settings page the alert emails link to also opens for a signed-in reader with no link at all.
A reader's membership page →
How many stories go in the email briefing, and who writes the summary over them?
The subscriber email is a curated briefing: a short written summary over the day's stories that go together, then those stories, the most-connected one first. Set how many under Settings, then Reach, then The email briefing (one to ten, five by default); the same value is briefing_size on the desk config over the API and MCP. The stories are chosen for how much they are about one another, and the summary is written by your paper's own model, billed to your account, so it reads like an editor's standfirst. If the model is out of reach the email still goes with a plain lead line, so a briefing never fails to send.
Help →
Does my paper have its own API?
Yes, on its own address, with a front door built for it. /api is the gateway: what the API is, the base address, your first call in cURL, JavaScript and Python, every door grouped with a live try-it panel, four things to build, the three lanes, and the house rules. /api/v1 is the index that names every door as a link: stories with their cited facts, sections, the archive by day, search, the front as JSON, the video editions, subscribe, and an OpenAPI document at /api/v1/openapi.json. No key needed for a public paper. A desk key from Desk settings opens the private lane on the same address. If the paper publishes in Spanish, the whole gateway is in Spanish.
The API gateway →
Can I put one of my stories on another website?
Yes. Open /api on your paper's own address and scroll to the embed section: pick a story, and it writes the code. Paste it into a blog post, a docs page or a client's site. The card shows the headline, the picture, the byline and your paper's name, and every part links back to you. It sets no cookies. If the other site strips scripts, use the first version, which is a single tag. And in WordPress, Ghost or Notion you can skip the code altogether: paste the story link and it becomes the card by itself.
The API gateway →
Who can read my paper's API, and what does a key change?
Three levels on one address. With no key, a public paper shows what its readers already see, so a public paper is public data, and a private paper answers as if it were not there. A read key for the paper, or any seat on it, opens the paper's own level: the newsroom, the filing proofs, the settings as read and the subscriber count. An admin key, or your admin seat, writes the paper. A key names one paper and works only under that paper's address. A reader who signs in on your paper gets a reader key of their own, which reads what their subscription pays for and nothing else.
The API gateway →
Can my own website sign readers up to my paper's alerts?
POST JSON to /api/v1/subscribers on your paper's address: email, plus cadence (instant, daily or weekly), sections, and cast. The reader gets a confirm email and joins when they click it. Your desk key also reads the list at /api/v1/subscribers: the count with any key, the addresses and each reader's choices with an admin key. Give a webhook and the answer carries each reader's signing key.
The API gateway →
Can I post my paper's stories to social media?
Your paper's address serves /api/v1/posts: every piece on air as a ready-to-post short form, sized for X, with the story link and picture. Point a scheduler or an automation at it, or copy from it. Nothing there is written by a model; it is the headline, the dek when it fits, and the link.
The API gateway →
How do I post the day's news or the video to X automatically?
Open Desk settings and pick the Post to X tab. Link your X account to your login (one click; you come straight back), then tick Post the day's news, Post the video of the day, or both, and save. The paper posts once a day as you, when the edition and the video are up. Post today's news now and Test without posting are on the same tab, and every post is listed with its link.
Post to X →
Can my email briefing carry my own ad?
Yes. The first promo in your Space (Desk settings, The Space) with a link rides every briefing as one card after the news: your title, your copy, your picture, your button, labelled as an advertisement with your publisher name. No promo set = your link-back (Reach) stands in as a plain card. No link at all = no card.
The Space →
Is there a podcast feed?
When the paper has a published video edition, /podcast.xml on its address is a feed a podcast app can subscribe to: one episode per day's edition, the video as the enclosure. /cast is the same edition on the page.
The catalog →
Can my paper carry another paper's stories, or offer mine to another paper?
Yes, through the wire. A paper files an offer (all of its stories, one section, or only the pieces it marks) and names who may carry them; a carrying paper holds a link and carries pieces as references to the source's signed, filed bytes, never copies, with the source's mark and the writer's byline on every one. Twice a day the wire picks, for each active link, the news piece and the opinion piece closest to the carrying paper's own topics; a piece already carried is never picked again. Today the doors are the keyed admin API: GET /api/v1/syndication for your standing, POST /api/v1/syndication/offers to file an offer, /market to see offers open to you, /subscribe to take one, /pick to carry one piece by hand, and /pick-now to run the day's pick for your paper at once. The carried strand sits below your own pieces on the front and says where each one came from.
The API →
How do I add a video edition (a short movie of the front page), and what does it cost?
Desk settings, the Video edition group: switch it on, pick the lane (the drawn desk, or people on camera), the Mountain hour it bakes, the length target and the style. It bakes on Publisher and up; a lower plan keeps the setting and waits. Each edition is charged to the paper's owner at the ledger's price, 50 credits for the drawn desk and 1,200 for people on camera, when it is queued. The edition lands on the paper at /cast, in the podcast feed and on the front page. To make one right now, press Bake today's edition now in the same group: it saves the dials, charges one edition and queues it; the cast page carries it when the bake finishes.
Desk settings →
How are the API addresses laid out?
As one tree, and the path names the paper. Everything about a paper sits under /api/v1/papers/ followed by the paper's name: its stories, sections, days, search, config, staff, the line, its own domains and the Signal Desk. The method is the verb: GET reads, POST adds, PATCH edits the config, PUT sets the look or the public switch, DELETE removes. On the paper's own domain the same tree sits at /api/v1, because the domain already names the paper. Read /api/v1 with your key to see which paper it names, then read that paper's address to see every route your key reaches. Every error comes back as an error code and one sentence you can act on.
The API gateway →
Home
Can I open every paper at once?
On Home, next to Your papers: Open N live opens every paper that is on air, each on its own address; Open N previews opens every paper you hold a seat on as its console preview, live or not. A browser lets one click open one tab, so past the first it may block the rest, and the note beside the button says how many it opened. Click the blocked pop-up icon in the address bar to allow them for this site, then try again, or unfold One at a time under the buttons and open them one by one.
Home →
Reach
A two-sentence piece is not an article. Can short items run differently?
Yes. Turn on Utterances in Desk settings, Reach. A live piece under seventy words leaves the columns and runs as one line under the news: its section, its headline, and how many sources it stands on. The story page and its receipt stay as they are.
Utterances →
Provenance
A live dispatch has one source. How does that publish?
A dispatch is your own reporter, at the scene, under their own byline. That is one witness, not a rehash of somebody else's article, so the two-source floor does not apply to a live wrap-up and the piece publishes labelled as standing on one source. The reader's live page says the same thing in plain words above the dispatches.
Live →
Folders
What is a folder, and how do I use one?
A folder holds the facts you keep: a hand-curated, sourced corpus a paper's writers may cite. Open Research and the folder pane sits beside the record. Search, press Keep on a fact worth having, and it lands in the folder the pane is showing. Assign the folder to a paper and its writers cite those facts in stories they overlap, up to six a story; a series column draws fourteen an episode.
Research →
How do I read what is in a folder, and search inside it?
The folder pane on Research shows the open folder: its count, the papers it feeds, where its facts come from, and the facts fifty at a time, newest first. Search inside this folder looks in that folder only. Press a source in the strip to see only its facts. Full page at the foot gives the same folder at its own address, which is the one to send a colleague. On a phone the pane is the bar at the bottom of the screen; pull it up.
Research →
Can I put my own note or a link in a folder?
Yes. In the folder pane press Add a fact of your own, type the fact or note, say where it came from, and press Add. It lands at the top and says typed beside its source. For many links at once, Add from links and documents opens the corpus builder with this folder chosen; the refinery reads each link and keeps the checkable facts here.
Research →
I deleted a folder by accident. Where did it go?
Nothing is destroyed. A deleted folder moves to the archive with everything it held, and you restore it from /find/folders under Archive. Removing one fact asks first and can be undone from the message that appears for a few seconds after.
The archive →
I run papers for several clients. How do I keep their research apart?
Tag each folder with the client's name when you make it, then filter by that tag at the top of /find/folders. Assign each folder only to that client's paper, so one client's research can never be cited by another's writers.
Your folders →
Can an agent use my folders over the API?
Yes, with an admin-scoped key. The tools are search_record, list_folders, read_folder, create_folder, update_folder, add_to_folder, move_folder_item, remove_folder_item and assign_folder, and the same routes answer under /api/v1/papers/{paper}/folders. A key reaches the folders its desk's owner holds, and reads come back a page at a time.
Desk settings →
Analytics
Where do I see how my paper is doing?
Analytics on your desk. It opens with reads day by day over thirty days, then who reads the paper, then four sections about your audience: Users (the seats who work on it and the accounts held on it), Subscribers (the list, who confirmed, what each asked for, and how the briefing landed), Revenue (your price and who pays it), and Usage per subscriber (your own people by name, when they last opened the paper and when you last sent to them). Every country seen sits at the foot.
Analytics →
What does the revenue number on Analytics actually mean?
It is your paying subscriber count times today's list price, so it is what readers are billed at list, before payment fees and before the platform share, and it moves the moment you change your price. It is not cash collected. Money taken, refunds, and the credits paid into your wallet each cycle are held by DRM3 billing, not by the paper, so the paper does not show them.
Analytics →
Can I see which articles a particular subscriber read?
No, and that is deliberate. Story reads are counted without identity, so no reader is followed from page to page. What you do see about your own people, because the relationship is yours, is when they last opened the paper signed in, when you last sent to them, what they asked for, whether they pay, and how many of your emails landed or were refused.
Analytics →
Signal Desk
What is a Signal Desk, and how is it different from a paper?
A Signal Desk is the other thing a property can be. Instead of a newspaper on the shared record of facts, it is a private wall of regulatory signals over one client's own record, like a county's meeting transcripts or a regulator's filings. Each headline is the action a body took, each signal has its own page with the source record behind it and a link into the moment it happened, search matches by meaning and shows you how close each hit reads, and readers keep watchlists that email them when something new matches. The whole address sits behind a sign-in wall, and the material never reaches any other paper.
Signal Desk settings →
How do I turn my property into a Signal Desk?
Open Desk settings and pick Signal Desk. Set it to run as a Signal Desk, name the dataset and table your data lands in, say who supplies it and how it arrives so readers can see where it came from, choose whether only invited people read it or anyone signed in on your paper, pick how close a search hit must read, and save. Invite your readers on the same page first: switching it on walls the whole address at once. You never publish a Signal Desk - its address serves as soon as you switch it on, and the publish switch is refused on it.
Signal Desk settings →
Who can read my Signal Desk, and how do I invite someone?
Add their address to the reader roster at the foot of the Signal Desk page. That sends them an invite by email: the desk's name, what it is, and where to sign in with that address. They reach the desk by signing in with the DRM3 account at that address; every other account is turned away and told who to ask. Everyone who holds a seat on the paper always reads it, whatever the roster says. Set it to anyone signed in instead if you would rather not keep a list.
Signal Desk settings →
Where do the groups on my Signal Desk wall come from?
They are your paper's own sections, in the order you put them in. A section's first record category is the group a signal files under, and the section's name is the label your readers see, so you edit them on Coverage like any other section. A signal whose category matches no section still shows, at the foot, under its own name.
Coverage →
Can an agent set up a Signal Desk over the API?
Yes, end to end. The whole setup rides the config door as one signal_desk object: whether it is on, the feeds it stands on (sources: each a dataset, a table and what readers are told about it), who may read it, how close a search hit must read, and the cadence a new watchlist opens on. The reader roster has its own door at /api/v1/papers/{paper}/signal/readers, with GET to read it and POST to invite or revoke; one feed is dropped with DELETE /api/v1/papers/{paper}/signal/connection. Over MCP the tools are get_signal_desk, set_signal_desk, disconnect_source, signal_access, invite_reader, remove_reader, send_digest, digest_subscribers, build_signals and signal_build_status. The full walkthrough is in the agent skill.
For agents →
What does an invited reader receive, and how do I know it went?
An email in your desk's own look: your mark, name and motto on the masthead, a line with the desk's live numbers (feeds, records, signals, coverage), who invited them to the Signal Desk, one button, Create my DRM3 account, and a quiet block on what the desk is, each feed it stands on, and that this is reader access and not an admin seat. The seat is the address you invited; the account is theirs to create, and the desk opens the moment they sign in with it. Someone who already has a DRM3 account at that address signs in and is through. You get a copy of every invite unless you switch that off on the Signal Desk page. Each roster row says whether the invite went, with the date, or why it did not; press Resend invite to send it again. The same happens when a reader is invited over the API or by an agent. To see the mail yourself, press Test invite under Send me a test.
Signal Desk settings →
How do readers get the desk by email?
On the desk itself, under the search and the watchlists, a signed-in reader picks Daily, Weekly or Off next to Email me the digest. No watchlist is needed. The digest carries every signal filed since their last one, across every section and every feed, newest first, each with its headline, section, place, date and a link to its page; a reader with nothing new gets no mail. Every digest carries a link that turns it off in one click. A watchlist still emails on its own, for the signals that match it.
Signal Desk settings →
Can I send the digest to everyone right now?
Yes. Press Send the digest now on the Signal Desk page and every reader who signed up gets theirs at once; the page then says how many were sent, how many had nothing new, and how many failed and why. The desk digest setting on the same page is the schedule: daily or weekly sends on its own, on the cadence each reader chose, and off leaves only the button. An agent does the same with send_digest, and reads the signups with digest_subscribers.
Signal Desk settings →
Can I see who is using my Signal Desk?
Yes. Analytics on your desk draws the desk's own shape: signed-in reads by day, the signals readers open most and how often they take a quick look, what they open (the front, Data, About, API, signal pages), the watch sections they pick, searches by day with the mean number of hits, the digests sent and to how many readers, what their DRM3 bells said, invites sent, the roster and seats, and readers active in the last 7 and 30 days, with each feed's records and signals. The sign-in wall is never counted, a reader is counted by a hash of their account id and never by name or address, and a search is counted by its length and its hits, never its words. An agent reads the same numbers with desk_analytics.
Analytics →
Do readers see the digest in their DRM3 account too?
Yes, while the bell is on. Every digest the desk sends a reader, and every watchlist match it mails, also lands on that reader's DRM3 account: a line in their activity and a bell alert that opens the desk. A reader who has not created their account yet gets the email alone, and the console says so after a send (rang 3 bells, 1 no account yet). The switch is When a digest goes out on the Signal Desk page, on by default; Email only turns it off. An agent sets it with portal_alerts on set_signal_desk. A test you send yourself never rings a bell.
Signal Desk settings →
Can readers ask the desk questions, get a brief, or summarize a signal?
Yes, three ways. Ask this desk is a box in the deck: the question is matched by meaning against the desk's own signals, the top passages go to the model and nothing else does, and every sentence of the answer cites the signal it came from. If nothing on the desk speaks to the question, the desk says so and no model is called. Brief me, on a watchlist (Manage, or the feed head) or on the desk, writes 120 to 200 words on what is new since the reader's last digest, cited. Summarize on a signal's page turns its transcript into one paragraph cited to the video moments; the first reader pays and everyone after reads it for nothing. Each answer prints what it cost and names the passages read. The three switches are on the Signal Desk page, on by default; an agent sets them with ai on set_signal_desk and calls them with ask_desk, brief_watchlist and summarize_signal.
Signal Desk settings →
Who pays for the AI answers on my Signal Desk?
The reader who asks, from their own DRM3 credits, never you. Every call goes through the DRM3 inference queue on the reader's account, the ledger is the meter, and the line under each answer says what it charged and the balance left. A reader with no credits sees Add credits to ask with a link to their account, and nothing is called. A reader can also switch on an AI brief at the top of their digest email; that brief is paid from their credits on each send, and when their balance is short the digest goes out without it and says so. Analytics on your desk counts the asks, briefs and summaries and the credits charged. The desk's private record never leaves it except as the passages sent to the queue for that one answer; nothing is written anywhere else and nothing is kept beyond the cached summary.
Analytics →
What are the Data, About and API pages on my Signal Desk?
The desk's reader pages, linked in the rail under the header on every page. The front carries one line of facts (feeds, records, signals, coverage, Private) and the signals. Data is the provenance: one card per feed with the supplier, how it arrives, the dataset, its records and signals, the last delivery read, and the tag readers see on a card. About is what the desk is: jurisdictions, the bodies that met, the date range, the owner, the private clause, and how access works. API is what a reader can read by machine on the desk's own address, listing only the doors that answer. All three sit behind the same sign-in wall as the front, and the preview shows the same pages.
Signal Desk settings →
Can I see the invite and the digest before a reader does?
Yes. Under Send me a test on the Signal Desk page, press Test invite or Test digest. Each goes to your own signed-in address and to nobody else, in this desk's own look and with its real numbers: the invite reads as if you had invited yourself, and the digest carries the last 10 signals. Nothing on the roster or the signups changes, and no reader's digest moves. The page then says it was sent, with the provider's id, or why it was not. An agent does the same with send_test_mail, which mails the desk's admin.
Signal Desk settings →
Where do I see the data my Signal Desk stands on?
On the Data page, under Desk settings and on the Signal Desk page itself. It lists every feed the desk stands on, one card each, and for the feed you open it shows who supplied it and under what terms, every delivery that has landed with the file, the count and who sent it, and a search over the rows themselves. Each row opens its own origin: whether it is private, the credential it came in under, who asked for it, and the delivery it arrived on. Each feed is read with its own key, so the page shows exactly what your keys reach and nothing else.
Data →
How do I connect my dataset to the desk?
Two ways, and the better one needs no key at all. Share the dataset to this desk from your DRM3 account and the key arrives on its own: the feed appears on the Data page, says it is connected by a share and names the person who shared it, and the account can take the share back whenever it likes. Or add the feed by hand on the Signal Desk page and paste its key under that feed on the Data page, minted on your Data console and scoped to that dataset. Either way it is stored encrypted against this desk and that feed: never shown again, never returned by the API, never written into your settings. The page shows a fingerprint and the last four characters so you can tell which key is on file.
Data →
How does my data become signals?
Press Build signals now on the Data page. It reads your rows and files one signal each: the headline is the action the body took, taken from the words in the record, and the page behind it carries the source and a link into the moment it happened. Run it as often as you like. A row whose source has not changed is left exactly as it is, so a second run writes nothing, and a row that replaces an earlier one retires that signal: off the wall, still in the archive. Every run is listed under the button with what it read and what it changed. Turn on automatic builds on the Signal Desk page and a new delivery builds itself.
Data →
Why did a signal file under the wrong group?
Because of the words on your section. A signal files under the section whose words best match the record, so the terms you put on a section on Coverage are what decide it. Those same words are also the examples your readers see in the search box, so they are worth getting right twice over. Add the words your field actually uses, then press Re-derive every row on the Data page and the whole wall refiles against your new wording.
Coverage →
My desk says the share was revoked. What happened?
The account that shared the dataset with this desk took the share back, so the key it was reading with is gone. The Data page names who did it and when, and the build refuses to run rather than half finishing. Nothing the desk already built is affected: every signal on the wall stays exactly where it is. Share the dataset to the desk again from your DRM3 account, or paste a key, and the desk carries on from where it stopped.
Data →
Can my Signal Desk stand on more than one dataset?
Yes, up to eight. Each feed is one of your account's datasets with its own supplier, its own delivery path and its own key: a data partner's nightly export beside the clerk's weekly file, say. Share a second dataset to the property from your DRM3 account and it lands beside the first, or add it by hand on the Signal Desk page. The provenance band then names every feed with what it landed, each signal carries a small tag with the dataset it came from, the Filters panel gains a Feed facet, and every build reads every feed and reports each one's rows and signals. Search, watchlists and digests work across all of them.
Signal Desk settings →
How do I disconnect one feed without touching the others?
On the Signal Desk page or the Data page, type the dataset's name into its row and press Disconnect. The desk forgets that feed's key and drops it from the list; the other feeds keep their keys and nothing about them changes. The signals the feed already built stay on the wall, still tagged with the dataset they came from, because a disconnect stops the desk reading, it never unpublishes. Taking the share back from your DRM3 account does exactly the same, and an agent does it with disconnect_source.
Data →
How do I change what readers are told about where a feed came from?
Open the feed on the Data page and use the form headed What readers are told about that feed: who supplies it, how it reaches the desk, and an optional privacy sentence. That is what the data-and-provenance band prints under the header, so a desk standing on two feeds shows two supply chains, each in its own words. A feed you shared from your account arrives with a standard supply line until you set your own. Only the feed you are editing changes, and the band updates the moment you save.
Data →
What happens if I switch my Signal Desk back to a newspaper?
Every signal goes off air. A newspaper serves its stories to the world, and the material on a Signal Desk is your client's private record, so switching the property back takes the whole corpus out of search, out of the site map and off every address a reader or a search engine can reach. Nothing is deleted: each signal keeps its revisions and comes back exactly as it was the moment you switch the desk on again. Because it is a withdrawal and not a preference, the page asks you to tick the confirmation before it will save, and it tells you afterwards how many signals came down.
Signal Desk settings →
Do I have to publish my Signal Desk for people to reach it?
No, and you should not try. A Signal Desk serves on its own address the moment you switch it on, behind its sign-in wall. Publishing is the newspaper switch - it is what puts a paper on the open web - so it is refused on a Signal Desk and there is nothing for it to do there. Your readers reach the desk by signing in at its own address with the DRM3 account you invited; nobody else gets past the wall, and search engines are told to stay out.
Signal Desk settings →
How does someone I invited actually get in?
They open the desk's own address and sign in there. The Sign in link on the wall sends them to DRM3 to sign in with the account at the address you invited, and brings them back onto the desk; the session stays on that address and reaches nothing else of yours. Everyone holding a seat on the property reads it without being invited. If you want to see the desk as one of your readers sees it before you send the address out, the Data page's own preview shows you the wall exactly as it is served.
Signal Desk settings →
What happens when a corrected record replaces one I already published?
The new record files a new signal, and the one it replaces comes off the wall and stays in the archive with its history intact. That holds even when both records arrive in the same upload: the earlier one is still filed first and then retired, so the record of what was said before the correction is never lost. The build's own log counts them, so you can see how many signals a delivery superseded.
Data →
My data partner delivers one zip per meeting. Does the desk read that shape?
Yes. Each feed on a Signal Desk says what its rows arrive in: meeting records (one row per meeting with its transcript and segments, the standard columns) or the data partner's meeting zip (one zip per meeting holding its metadata and a word-level transcription, or the pages of a document). Set it on the Data page under What readers are told about that feed, or over the API with shape on the feed. A zip is read as delivered: the meeting date, the place and the body come from the partner's own metadata, the words are grouped into moments so Watch at still lands on the right minute even when no speaker is named, and each signal's page links View on the source site and shows the duration. A corrected record with the same id replaces the earlier one; the earlier version stays in the archive.
Data →
I moved a feed's records into another feed. How do I take the old signals down?
Two ways, both on the Data page. Disconnect the old feed with Also take its signals off the wall ticked: the desk forgets its key, drops it from the list and retires every signal it built; they stay in the archive and nothing is deleted. Or, for a feed that stays but was delivered afresh, press Re-derive every row: when the desk reads the whole feed it retires the signals whose rows are no longer in it and files the rest again. Over the API the disconnect takes withdraw_signals true, and an agent passes the same to disconnect_source.
Data →
Coverage
My paper is about one law or one trade and it keeps printing the whole industry. How do I keep it on the beat?
A subject only ever pulls facts in, so a trade's own words (shipbuilding, tanker, port, dredging) claim every yard, ship and harbour on earth. Open Desk settings, Coverage, the Markers segment. List the words that can only mean your desk (for a paper on the Jones Act: Jones Act, cabotage, coastwise, Puerto Rico, Hawaii, Alaska, Matson, MARAD, the American yards and ports) and turn on Every fact must carry a marker. From then on a fact that names none of them never reaches the desk, whatever else it says, while shipbuilding and tankers still count when they are yours. Before you save, press Measure against today's record on the Subjects segment: every word shows how many facts it claims today and how many of those carry a marker, and the wide ones turn the warning colour with one button to remove them.
Markers →
How do I see which of my subjects are pulling in off-topic stories?
On the Coverage tab, the Subjects and Themes segments carry Measure against today's record. It reads the same facts the line will read and paints two numbers on every word: how many facts it claims, and how many of those carry one of your markers. A word that claims many and anchors few is wide, turns the warning colour, and is where off-beat pieces come from. Remove the wide words with the one button, or keep them and turn on the marker rule so they only count beside a marker. The numbers change with the day's news; measure again after a change.
Coverage →
Search engines
Why does my paper not show up on Google?
A search engine only lists a page it has been told about: through a property you verified with it, a sitemap you submitted, or a link from a site it already knows. Your paper serves everything a crawler needs on its own (robots, two sitemaps, a canonical address, article data on every piece), but none of that reaches Google until you verify the property and submit the sitemap, which takes ten minutes on the Search engines card and no DNS change. Then give it a link: list the paper in the catalog, put it on your own site, post it. Expect days to a few weeks before pages appear; it is the engine's clock, not the paper's.
Search engines →
How do I verify my paper with Google Search Console or Bing, without touching DNS?
Open Google Search Console, add a property of the URL-prefix kind with your paper's address (https://your-address/), pick the HTML tag method and copy the code it shows. Paste it into the Google field on the Search engines card and save; the paper now serves the tag on every page, so go back and press Verify. Bing Webmaster Tools works the same way with its own tag in the Bing field, or import the property from Search Console in one click. Nothing at your registrar changes.
Search engines →
Which sitemaps do I submit?
Submit both addresses the card shows: /sitemap.xml lists every page (the front, back issues, sections, staff and every piece on air, each with its real date) and /news-sitemap.xml lists the last two days of pieces in the Google News format, which is what Top Stories reads. Submitting them is the step that reaches Google. Bing, Yandex, Seznam and Naver need no submission: the paper tells them about each new page the moment it goes live, on its own.
Search engines →
Which search engines is my paper in, and how fast does a new piece show up?
Your paper is in Bing, Yandex, Seznam and Naver, and it stays current on its own: the moment a piece goes live, its address is sent to those engines, so it can appear in hours instead of waiting days to be crawled. You do nothing, it is on by default, and the card shows the last time it ran and how many pages have gone out. Google works differently: it does not take the instant notice, so you reach it through the property you verify in Search Console and the sitemap you submit, which is the step above this one on the card.
Search engines →
Can I set what the front page is called in search results?
Yes. The front page's title is your nameplate with your motto unless you set one on the Search engines card, and the description is the day's own line unless you set one. Put the words a reader would type there: the place, the subject, the language. Each piece already carries its headline, its summary, its author and its date in the form search engines read; the piece settings drawer in the editor can override a piece's own title and description.
Search engines →