Articles and channels: creating, publishing and access
An article is an editable document with authors and versions. A channel defines where it is published and who the audience is, categories help readers find content, and H2 headings organize the text within an article. This guide walks through creating a draft, publishing, editing again, the table of contents and access restrictions.
Creating an article and working with a draft
Open the "Articles and channels: creating, publishing and access" section and start a new content item. The first line is the title. Write the text in the main document and add the formatting you need. The title should explain the topic of the whole article rather than repeat the first short question from a chat. For detailed instructions, keep related actions together in one article.
Changes are saved automatically. Before closing, wait for the "Saved" confirmation; if you have connection problems, check the save status. If the document was changed in another window and a version conflict occurs, save your edits separately and reread the current version before editing again.
Headings, files and document structure
Use H2 for standalone sections, for example "Getting started", "Setting up access" and "What to do if something goes wrong". A subheading should clearly name what the following paragraphs cover. Text structured this way is easier to read, and the assistant can pick the right section without loading the whole article.
The editor toolbar lets you format text and add lists, tables and formulas. You can insert images and videos by adding a file. Wait until attachments finish processing before you publish: media that isn't ready can prevent the published version from being prepared.
Authors and editors
A content item can have several contributors with different roles. The main author and additional co-authors define authorship, and an editor gets the text-editing capabilities provided by their role. Authorship is not the same as channel membership and doesn't make the content public.
The publishing channel and the article's author are different properties. In the feed, the content belongs to the selected channel, while its authors are preserved. The author display setting controls how authors are shown but doesn't replace access permissions for the document.
How an article becomes available to readers
Saving creates or updates a draft. Publishing always goes to a channel: when you publish for the first time, choose a channel, and Sensever prepares a document version and posts the content as the root message of a thread in that channel in a single operation. You can't publish content without a channel or to a group. The content address is sensever.com/<channel>/<content>; there is no numbered page like sensever.com/content/<type>/<id>. The channel message is exactly the point where access to the published content is checked.
The article keeps its own document, authors and version. No separate publication or post entity is needed between the article and the message. Plain text with attachments can be sent directly as a channel message; a full article is for a document with a title, sections and the editor.
Updating and unpublishing
After publishing, you can keep editing the draft. Readers see the published snapshot until you update the publication; you don't need to choose the channel again when updating — the content stays in its channel. This lets you prepare changes without showing unfinished text. Check not only that the draft is saved but also that the right version is published.
Unpublishing closes reading and keeps the draft. Deleting the content is a separate action. A link or a previously sent card doesn't override the denial of access to an unpublished or deleted article.
Table of contents from H2
In the publishing settings, turn on "Show table of contents" if you want a list of sections before the text. It is generated automatically from non-empty H2 headings. Without this setting no table of contents is created; headings in the text alone aren't enough.
A change to this setting becomes visible after you publish a version. In the API it is set with the boolean metadata.show_toc. H2 headings matter for structuring the content even if the author chooses to hide the table of contents.
Channel categories and navigation
A channel's content is split by type, for example articles and videos. Within a selected type, the owner organizes categories nested up to four levels deep. A category helps readers find content but doesn't widen its audience.
You can open the channel structure with a separate button on the channel or article page. The tree shows where the current content item sits. The H2 table of contents covers the text of a single article, while the category tree covers multiple content items in the channel.
Article address and discussion
A public link looks like /channel-slug/article-slug. The content slug is reserved when the content is posted to the channel; changing the title doesn't create a new address or a new discussion. If titles match, the address gets a suffix. In integrations, use the current source.url from the library response.
Comments are tied to the article's permanent ID, not to its title or URL. Changing the text doesn't delete the conversation. Access to the discussion is checked against access to the source content.
Public, private and link-only channels
A public channel is meant for open content. A private channel requires read permission; a direct link doesn't grant access to outsiders. The unlisted mode hides the channel from regular search but keeps link access, and it isn't suitable for storing secrets.
Content permissions are checked against the root message and the channel's restrictions. Moving content to another category doesn't change these permissions. Don't treat the appearance of a link or card as proof that the content is public.
Paid access and API limits
Automatic payment collection and subscription sales aren't connected yet. You can use privacy independently of monetization. The fact that the architecture has a mechanism for paid audiences doesn't mean a payment interface is ready.
The API for changing the audience of a root message supports public, members and circle for channels with Access Policy enabled. In all other cases it returns access_policy_not_enabled. This is a limitation of the technical contract, not a suggestion for regular users to turn on internal flags.
Reacties