The Knowledgebase and Updates can each be switched off.

A site that does not publish one of them turns it off under Setup › Management Levels. Its pages then answer "page not found", and its menu links, page sections, sitemap entries and (for the Knowledgebase) ticket suggestions disappear. The records are kept.

Departments

Departments define ownership, visibility, routing address, access rules, autoresponder behavior, feedback requests, and closure policy. Keep the name and description customer-friendly because both appear in the ticket form.

Ticket workflow

  1. Classify.Select the right department, priority, customer, and related service.
  2. Understand.Read the history, attachments, account activity, and recent billing events.
  3. Respond.Use clear formatting, explain ownership, and give a concrete next step.
  4. Resolve.Record the outcome, update reusable knowledge, and close only when policy allows.

Knowledgebase and download addresses

Since 1.10.0 knowledgebase and download addresses read like the site's structure instead of carrying row numbers and .html:

PageOld addressAddress now
Knowledgebase category/knowledgebase/12/Account-and-Security/knowledgebase/account-and-security/
Knowledgebase article/knowledgebase/reset-a-password.html/knowledgebase/account-and-security/reset-a-password
Download category/files/category/1/Annual-Reports.html/files/annual-reports/
Download/download.php?type=d&id=30/download.php?Xk3J9qPa2mZ4bT7w
Main category
An article's address uses its main category, chosen under Organization in the article editor from the categories it is ticked in. It starts on the first one; an article that existed before 1.10.0 keeps the lowest-numbered category it was already shown under.
Public link
The public link in the article editor is a field: type a new slug and save. Knowledgebase and download categories have the same field. Saving an article or an update never moves it to a new address on its own — since 1.9.7 a corrected title keeps the address it already has, and a new one is made only for a record that has none, or whose address another record has since taken.
Category links
Made from the name — "Account & Security" becomes account-and-security — and cannot be all digits or use the words the routes need: tag and search in the knowledgebase, category and search in downloads.
Download tokens
A download's token is random and permanent, so a file's address no longer gives away its number or leads to the others.

The readable addresses are switched on, the new columns added and filled in, and links to the old addresses in the site's own content rewritten — knowledgebase articles and their translations, updates, events, Content Manager pages, menus, blocks and custom sitemap links — the first time an administrator opens Help Center › Knowledgebase or Downloads. Until then the public pages keep the old addresses. Afterwards, changing an article's link or main category, or a category's link, updates the links to it in that same content. Links to other websites, and links to articles that no longer exist, are left as they are.

The old addresses

Since 1.11.0 the old knowledgebase addresses answer with a permanent (301) redirect to the readable one, so links from search engines, other sites and older posts keep working:

  • /knowledgebase/{article}.html, and an article asked for under a category other than its main one, go to the article's address;
  • /knowledgebase/{id}/{name} goes to the category's address;
  • /files/category/{id}/{name}.html goes to the download category's address.

download.php?type=d&id= stays retired and answers "page not found": a file is reached only by its token. In 1.10.0 itself every old address answered "page not found", so links that broke between 1.10.0 and 1.11.0 work again once the site is on 1.11.0.

One address per page.

On a site with friendly URLs, a page asked for in the basic form — index.php?rp=/updates/x.html, where old links and redirects land — answers with a permanent redirect to its clean address, /updates/x.html. Only GET and HEAD requests are redirected; the admin area and posted forms are unchanged.

Who sees an article

Private
Only a signed-in client can open it. A visitor who is not signed in is asked to sign in, and the article is left out of every listing they see: the category page, tag pages, search results and their summaries, the most-read strip, related articles and sitemap.xml.
In a hidden category
An article whose main category is hidden, or that has no category at all, is not shown: its address sends the reader to the knowledgebase home, and it is left out of every listing. A hidden category's own address answers 404 to visitors, as does a hidden download category; a signed-in administrator still sees both.

Knowledgebase Settings › Writing can make every new article start private, so a half-written one stays off the public site until somebody makes it public.

Knowledgebase Settings

Setup › Knowledgebase Settings, also under Help Center › Knowledgebase › Settings, is where an organization says how its resource centre reads. Each tab saves only its own settings, a figure outside its limits is refused rather than quietly changed, and every default is what WBAMS did before the page existed.

Resource centre
How many articles the most-read strip holds, or none; whether a summary is shown under each title and how long it runs; whether category tiles show how many articles they hold; whether the tag list is offered, and how many of the most-used tags it lists.
Article page
How many related articles sit under an article, and whether the most-read articles fill the strip when the category and tags cannot; whether the view count, the article's tags and the "was this helpful?" vote are shown. Views are still counted when the count is hidden.
Reading
An estimated reading time at a words-a-minute figure you set, and the contents list beside a long article: whether it is offered and how many headings an article needs first.
Writing
The presentation template a new article starts on, whether a new article starts private, and the default preview image.

While the Knowledgebase is switched off under Website Sections, the page says so and offers nothing to set. Since 1.11.0 the Draisap knowledgebase home counts each article once, however many categories it is filed in.

Two systems, two sets of templates

Updates and the Knowledgebase are different systems for different readers. Updates is the newsroom - news, announcements, releases, launches, service status. The Knowledgebase is the resource centre - references, how-tos, tutorials, FAQs, troubleshooting, policies. From 1.6.0 each has its own presentation templates, its own content blocks in the editor and its own styles in the client themes; nothing is shared between them but the mechanics. Each update or article carries one template, chosen in its editor. Translations inherit the canonical record's template so one record does not change look between languages.

Newsroom templates (Updates)

News Update
A short, dated announcement - a change, a reminder, a heads-up.
Feature Story
A fuller story with a lead image, a pull quote and a takeaway.
Progress Brief
Dated operational progress: where things stand, what moved, what is next.
Community Story
People-first coverage: customers, partners and the team.
Urgent Notice
Time-sensitive: who is affected and what to do now.
Release Notes
A version and what it adds, changes and fixes.
Product Launch
A headline feature, its highlights and a call to action.
Service Status
An incident: current status, impact, timeline and resolution.
Scheduled Maintenance
A maintenance window: when, what is affected, what to expect.
Event
A webinar, meetup or launch day: when, where, agenda, how to join.
Roadmap
What is coming next, in order, and how sure you are.

The newsroom blocks the Updates editor inserts: lead, dateline, heads-up, action required, pull quote, highlights, change list, version, image, timeline, status line, call to action, related links and roadmap list. They carry news-* classes and are styled only inside an update.

Resource templates (Knowledgebase)

Reference
A durable answer with clear sections, terms and review details.
Explainer
Background and context - the why, not just the how.
How-to
Prerequisites, numbered steps and a check at the end.
Tutorial
A guided walkthrough with screenshots and a result.
FAQ
Short questions with direct answers.
Troubleshooting
Symptoms, likely causes, the fix and how to confirm it.
Changelog
Added, changed and fixed, version by version.
Feature Spotlight
One feature: what it does, where it is, tips for using it well.
Security Guidance
Risks, boundaries and the safer way to do it.
Policy
How we handle something, what we ask of you, and the definitions.
Glossary
Terms and what they mean here, in alphabetical order.
Checklist
Everything to confirm before, during and after.
Comparison
Options side by side, with a recommendation. A cell reading yes or no prints as a mark.

The resource blocks the Knowledgebase editor inserts: summary, key facts, note, warning, important, result, before you start, steps, checklist, definitions, question, comparison table, change list, version, screenshot, related articles and revision note. They carry doc-* classes and are styled only inside an article. Since 1.9.7 both client themes also style doc-timeline (a dated list, drawn as a rail with markers), doc-glossary (a term list, boxed like doc-terms), and doc-term-alt and doc-credit (an alternative spelling under a term, and a photo credit in a caption). In Draisap, a key-facts value may hold italics or a link and still read as one line; it no longer needs wrapping in a <span>.

An article's preview image

Since 1.10.0 a knowledgebase article has a Preview image with alt text in its editor, as an update does. It is shown beside the article in an automatic knowledgebase menu and on share cards. Without one, the first picture in the article is used, and without either, the default image set under Knowledgebase Settings › Writing › Preview image. WBAMS ships a default; any picture can replace it, and a switch there makes every article without a preview image use it. The line under each title in a menu is the opening sentence of the article's summary. The preview image has to be a picture from the media library or an https:// address.

Writing in the editor

The Presentation card is the first thing in both editors. Choosing a template fills the editor with that template's structure - a release-notes update starts with a version line, a lead and a change list; a troubleshooting article with symptoms, likely causes, a fix and a result - and restyles the editor canvas to match, so the author writes inside the template and sees what clients will see, in light or dark mode. Choosing another template with text already written asks whether to replace the text with the new structure or keep it and only restyle; Reload this template's structure starts over. The block bar under the title offers that system's blocks; a block keeps its name in every template of its system, so switching templates later restyles what was written rather than breaking it. Live preview shows the article in the client theme.

The Video block has its own editor: paste a YouTube or Vimeo link or pick an MP4 / WebM from the media library, set a poster (YouTube supplies its own thumbnail; for a library file, pause the preview on a good moment and press Use this frame to save that frame as the poster), a caption, the aspect ratio, a start time for YouTube, and loop / muted / autoplay for library files. Readers see the poster and a play button and nothing loads from the video host until they press it. In the editor the video shows as its poster; click it for a toolbar with edit, change poster, aspect ratio and remove, or double-click to open the editor.

List views take their excerpt from the lead (news-deck) or summary (doc-summary) paragraph, or from the first paragraph when there is none. Bodies pass through the article sanitizer, which allows headings, paragraphs, lists, links, quotations, tables, figures with captions, definition lists and the other structural HTML5 elements the blocks use; scripts, forms and event attributes are removed.

Upgrading from 1.5

Content written before 1.6.0 used five shared templates and mtd-* blocks. The 1.6.0 upgrade maps each stored template to the nearest template of its own system - Standard becomes News Update or Reference, Editorial Feature Story or Explainer, Field Brief Progress Brief or How-to, Cultural Feature Community Story or Policy, Safety Notice Urgent Notice or Security Guidance - and rewrites the block classes. Nothing needs re-editing.

Write for the reading layout

  • Open with a concise summary that answers why the article matters.
  • Use descriptive headings, short paragraphs, lists, callouts, and source links to create a clear reading rhythm.
  • Use art or photography only when it adds context; provide accurate alternative text and never publish sensitive personal information.
  • Keep dates, corrections, source ownership, and review status visible when the subject can change.
  • Test the list card, category view, detail page, search result, print view, mobile layout, keyboard path, and both color modes.

Updates

Updates replace legacy Announcement terminology. Use them for customer-visible service news, release information, operational notices, and important changes. Keep the title specific, publish date accurate, content actionable, and slug permanent. In the admin menu, Help Center › Updates opens to All updates and Settings, and Help Center › Knowledgebase to Articles and Settings.

An update can be marked Featured in the editor: the newest featured update leads the first page of the newsroom full width, and the others keep their place by date with a badge. The updates page lists each update once, in the visitor's language: a translation is a row of its own pointing at its original, and since 1.11.0 the list takes the originals and shows each in the visitor's language rather than listing every translation as a separate story. The by-month archive lists a month only once an update in it is published.

An update, an event, a gallery album and a knowledgebase article each describe themselves when shared: their own title and summary, their address, their preview image with its size and alt text (for an article without one, the first picture in the article), and, for articles, the date published. A page with no picture of its own uses the Default share image from Content Manager › SEO Tools.

Updates Settings

Setup › Updates Settings, also under Help Center › Updates › Settings, is where an organization says how its newsroom reads. Each tab saves only its own settings, and every default is what WBAMS did before the page existed.

Newsroom
Updates per page; how many months the by-month archive reaches back, or none; whether the first page is led by one full-width story; whether the category filter and the card summaries are shown, and how long a summary runs.
Article page
How many further updates sit under an update, and whether those in the same category come first; an estimated reading time at a words-a-minute figure you set; whether share links are offered.
Feed
Whether a feed is offered at all, how many updates it carries, and whether each item is the whole update or a summary and a link.
Writing
The presentation template and category a new update starts on, and how many rows the admin list shows.

While Updates is switched off under Website Sections, the page says so and offers nothing to set.

Categories

An update can carry one category, typed in the Category field of the Publishing card (the field suggests the categories already in use; a new name starts a new category). The updates page shows a row of category tabs once any published update has one, each update's card shows its category, and a visitor who picks one sees only its updates at /updates?category=Name. Translations share the category of the update they translate. In the admin list, the Category column and filter narrow the list the same way, and the Updates page section can show a single category.

An update that is published with a future date is scheduled: it stays off the updates page, the page sections and the RSS feed until that date.

Preview image and alt text

Open Help Center › Updates › All updates and add or edit an Update to reach the Preview image fields and live preview. An Update can optionally reference one preview image. The canonical record owns the image location so every translation uses the same asset. The canonical alt text is the fallback, and each translated Update can supply localized alternative text. These fields are native Update data; do not hardcode article images or descriptions into a theme template.

The Preview image field stores a reference to an asset that is already available to public browsers; it does not upload a file. Use one of these formats:

  • Site-relative: a portable asset path such as assets/images/updates/service-window.jpg. A leading-slash path such as /assets/images/updates/service-window.jpg is also accepted when the asset intentionally lives at the web origin root. Do not hardcode an installation folder such as /portal/ into reusable content.
  • External: a complete https:// URL with a host, such as https://cdn.example.org/updates/service-window.jpg.

A site-relative path may also begin ./ or be a filename in the current asset base. A non-empty path can carry a query string or fragment, such as assets/brief.webp?v=2#lead; a query-only or fragment-only value is not an image path.

Locations can contain at most 2,048 characters. WBAMS rejects http:// and other scheme-like values, protocol-relative values beginning //, embedded usernames or passwords, literal control or whitespace characters, quotes, markup delimiters, backslashes, malformed URLs, and any .. path segment. URL-encoded paths are decoded repeatedly—up to eight passes—before checking decoded control characters, markup delimiters, quotes, backslashes, and traversal, so encoded traversal is not an alternative. Validation protects the stored location but does not upload, proxy, download, or continuously monitor the asset; verify that the final public page can load it over HTTPS without authentication or hotlink restrictions. A syntactically valid URL that later returns an error remains stored until an editor clears or replaces it.

Recommended media

Prepare a well-composed 16:9 crop, normally 1600 × 900 pixels, at an appropriate web file size. Keep important detail away from the crop edges, confirm publishing rights, and never expose private customer or case information in the file, filename, URL, metadata, or visible image. An external host receives each visitor's image request, so use only an approved provider whose availability, privacy, and retention terms fit the site.

Alternative-text decision

  • If the image communicates information that the title and body do not, write concise alt text that conveys the same purpose. Do not begin with “image of,” repeat the headline, or include a credit line.
  • If the image is only decorative, leave the canonical alt text blank. Serepok emits an empty alternative and hides the image from assistive technology; the Update title and Read More control remain clear links to the article.
  • Translate meaning rather than words. A localized alt value overrides the canonical text for that translation; an empty localized value falls back to the canonical alt text.

Clearing the Preview image also clears its alt text. If no valid location is stored, the Updates index keeps its 16:9 media rhythm with a neutral decorative placeholder. The Update detail page emits no lead-image markup and retains the selected presentation template's existing treatment.

Email routing

Protect mailbox credentials, validate senders, prevent loops, restrict attachment types, and monitor failed imports. The scheduler must run reliably for queued or polled workflows.