Who Can See an Article
The three gates that decide whether a customer can read an article: its own visibility, the audience of every category above it, and the companies it is shared with.
On this page
The rule, in one sentence#
A customer can read an article only when it is published, its own visibility is Portal, every category above it is Portal, and their company is on its audience.
Fail any one of those and the article is invisible to that customer — not locked, not greyed out, genuinely absent from browse, absent from search, and its direct URL returns "not found".
Your own team is not affected by any of this. Members see every published article shared with them in the Library, internal and customer-facing alike — and out of the box everything is shared with the whole organization. These controls exist to govern the customer side only; which members can read an article is its sharing. For your team, the visibility and category settings below only help decide which tab lists the article.
Gate 1 — The article's own visibility#
Set in the editor's Audience panel, under Visibility. The panel is shown to everyone who can open the editor; if you do not hold Publish knowledge-base articles its controls are disabled and a hint says who can change them, so a missing permission never looks like a missing feature.
- Portal (customers) — customers may read it.
- Internal (members only) — your team only, permanently.
A new article starts as Portal (customers), unless you create it on the Internal Articles tab, where it starts as Internal (members only).
When you choose Internal, a hint appears: "Internal articles never appear on your customer portal." In the Library, internal articles carry an Internal badge so your team can tell at a glance whether a customer is also reading it.
Changing this takes effect on the customer's very next page load. There is no republish step.
Gate 2 — The category audience (the clamp)#
This is the newest control and the one worth understanding properly, because it is the one that acts at a distance.
A category has its own audience, set in the category dialog under Audience:
- Portal (customers)
- Internal
Setting a category to Internal hides everything nested underneath it from the customer portal — every subcategory, every article, however deep, including articles added later. The hint in the dialog states it directly:
Internal hides this category — and everything nested under it — from the customer portal, whatever the individual articles say. Articles keep their own audience setting.
That last sentence is the important one, and it leads to the two properties below.
It is a clamp, not a cascade#
Marking a category Internal does not rewrite the articles inside it. Their own visibility setting is left exactly as it was. The hiding is worked out fresh every time someone reads, by walking up the category tree.
The practical consequence is that the change is completely reversible:
- You have a section with a mix of Portal and Internal articles.
- You mark the section Internal while you rework it. Everything vanishes from the customer portal.
- You mark it Portal again. Every article returns to exactly the state it was in — the Portal ones become visible again, and the ones you had individually marked Internal stay internal.
Step 3 is what a cascade would get wrong. If marking the section Internal had stamped "internal" onto every article, turning it back on would have published articles you had deliberately kept private. Because nothing was written down, there is nothing to get wrong.
Use this to stage a section before launch
Because it is lossless, an Internal category is a good staging area. Build a whole section with the articles set the way you eventually want them, keep the parent category Internal while you work, and flip the parent to Portal when you are ready. Everything goes live in one move, already configured.
Inherited Internal#
When a category sits under an Internal ancestor, its own Audience control stays editable and keeps showing that category's own setting. The inherited restriction is explained beside it rather than applied to it, because the two are genuinely separate facts: what this category is set to, and what an ancestor is currently doing to it.
The hint names the ancestor, then tells you what it means for this category. If this category's own setting is already Portal, there is an action to take:
Runbooks is Internal, so this category and everything under it is hidden from customers right now. Re-open Runbooks to make this one visible — your setting here is already Portal.
If the category is Internal in its own right as well, re-opening the ancestor would not be enough, and the hint says so instead of promising otherwise:
Runbooks is Internal, so this category and everything under it is hidden from customers right now. This category is also Internal in its own right, so it stays hidden even if Runbooks is re-opened.
This updates live as you edit. Changing the Parent category in the dialog to something Internal makes the notice appear before you save, so you can see what filing it there is about to mean.
Why the control is not disabled
Keeping it editable matters most in the ordinary case of an internal category nested inside another one — an internal HR under an internal Company policies. Disabling the control there would leave that category's own setting unreachable, with no way to change it short of temporarily re-opening the parent.
Spotting it in the tree#
In the Manage category tree, an Internal badge appears on every category that is effectively internal — including ones that are internal only by inheritance. Hovering tells you which kind:
- Internal — hidden from the customer portal, along with everything nested under it.
- Internal — inherited from Runbooks. Hidden from the customer portal.
The badge deliberately appears on inherited ones too. A badge that showed only on the parent would leave every child looking public when it is not.
The Manage table shows the articles own setting
The Visibility column on the Manage article table shows what each article is set to, not what a customer would experience. An article can read
portalthere and still be hidden by a category above it — that column is an editing surface, so it deliberately shows the stored value.The surfaces that tell you the effective answer are the Internal badge on the category tree, the badges in the article library and reader, and the editor, which names the category responsible:
Hidden from customers: the category Runbooks is Internal. This article's own audience is unchanged and applies again when that category is available to customers.
The editor's own Audience controls keep showing and saving the article's own setting, for the same reason the category dialog does — the clamp is never written into the article.
Gate 3 — Companies#
Portal-visible articles can be narrowed to specific customer companies. This lives in the same Audience rail panel, under Companies, with an Edit button (enabled for Publish knowledge-base articles holders). The companies you can pick are your Service Desk companies — if the picker says No companies found, add companies in Service Desk first.
In the Article audience dialog:
- All companies — every company with portal access can read it. This is the default.
- Specific companies — pick companies with Choose companies; each appears as a removable chip.
The summary in the rail reads All companies, 1 company, or {n} companies.
No companies is a real setting, not an empty one
Choosing Specific companies and then removing every company means no company can read this article. That is a valid state and DevStride keeps it, but it looks identical to "not configured yet" at a glance. The dialog refuses to save an empty pick — "Choose at least one company, or share with all companies" — and if an article ends up in that state, the rail shows a warning: "No companies selected — this article is not visible to any portal company."
You can set the company audience while the article is still Internal. That is deliberate: it lets you narrow the audience before exposing the article, rather than publishing to everyone and restricting afterwards. The rail explains this with the hint "Audience applies only to portal-visible articles — set it now and it takes effect when visibility switches to portal."
Putting the three together#
The gates are evaluated in order, and all must pass:
| # | Gate | Where you set it | Fails when |
|---|---|---|---|
| 0 | State | Publish button | Article is a draft or archived |
| 1 | Visibility | Editor → Audience → Visibility | Set to Internal |
| 2 | Category audience | Category dialog → Audience | Any ancestor category is Internal |
| 3 | Companies | Editor → Audience → Companies | The reader's company is not on the list |
An uncategorized article skips gate 2 entirely — it has no ancestors, so nothing clamps it and its own visibility decides.
Troubleshooting: my article is not showing up for customers#
Work down this list in order.
- Is it published? The state chip in the editor must read
published. A draft or archived article is invisible to customers regardless of everything else. - Is its visibility Portal? Editor rail → Audience → Visibility.
- Is a category hiding it? Check the category tree for an Internal badge on its category or any category above it. Hover the badge to see whether it is set there or inherited, and from where.
- Is the company on the list? Editor rail → Audience → Companies. If it reads No companies, nobody can see it.
- The definitive check: look under the slug in the editor's URL panel. If Live on your customer portal is shown, gates 0–2 all pass. If it is missing, one of them is closed.
Why an excluded article 404s instead of saying access denied
When a customer opens the URL of an article they are not entitled to read, the portal returns the same "not found" response it gives for an article that never existed. This is intentional. A "you do not have access to this" message would confirm the article exists and leak its title through the URL — so an excluded article is indistinguishable from a nonexistent one.
Two behaviours worth knowing#
Deleting an Internal category preserves its restriction. The clamp is normally never written down, but a deleted category takes its rule with it — so DevStride writes Internal onto whatever would otherwise be exposed: the articles that become Uncategorized and the child categories that move up a level. Nothing hidden becomes visible, and anything written down shows in the UI and can be widened again. Details in Organizing with categories.
Moving things does change who can read them. Dragging a category out from under an Internal parent, or an article from an Internal category into a customer-facing one, makes it readable by customers at once. It is reversible by moving it back, but there is no warning at the moment of the drop — be deliberate when reorganizing a tree that mixes internal and customer-facing sections.