Exam objective 3.4 focuses on how to configure a knowledge base, write useful articles, and set up a self-service portal. This matters because the whole point of a service desk is to solve problems fast, and giving users a way to help themselves through a well-organised knowledge base is the single biggest efficiency gain you can deliver. For the SNOW-CSA exam, you need to know exactly how to create, publish, and retire articles, and how to make them visible on the portal so end users can find answers without ever raising a ticket.
Jump to a section
A simple way to picture Knowledge Management and Self-Service
A well-organised office library is the heart of a company's shared knowledge. The library itself has locked shelves for confidential documents, open shelves for general reference books, and a catalogue system that helps anyone find the exact manual, policy, or how-to guide they need in seconds.
Before the library existed, employees hoarded their own copies of important documents in their desk drawers, asked colleagues for help repeatedly, or simply guessed how to do their jobs. The library replaced this chaos with a single source of truth. Whenever someone learns a better way to reset a printer or file an expense report, they update the relevant manual on the library shelf, and everyone else sees the new version immediately. The librarian (the Knowledge Manager) decides which documents are accurate enough to publish and which old ones should be removed.
Now imagine an employee who needs to fix a jammed photocopier. Instead of interrupting three coworkers and wasting an hour, they walk to the library, find the quick-guide card in the 'Repairs' section, and fix it in five minutes. That is exactly how a ServiceNow knowledge base works, and the self-service portal is the library's front door, open 24/7 from any device.
Knowledge Management in ServiceNow is the process of capturing, organising, and sharing information so that users, customers, and IT staff can find answers without relying on memory or guesswork. The system replaces the old habit of sending emails around the office asking 'Does anyone know how to…?' with a central library that everyone can search.
A knowledge base is a container for articles. Think of it as a filing cabinet. Each knowledge base can have its own permissions, so some bases might be public (visible to all employees) and others restricted to certain teams (for example, a 'Security Policies' base only visible to the IT security group).
Articles are the individual documents inside a knowledge base. Each article has a title, a short description, a body, and optional attachments like PDFs or screenshots. Articles can be formatted with simple text, images, tables, and links. Every article goes through a lifecycle:
Draft: The author is still working on it. Only the author and people with 'write' access can see it.
Review: The article is submitted for approval. A knowledge manager or subject-matter expert checks it for accuracy.
Published: The article is live and visible to users on the portal.
Retired: The article is taken down, usually because the information is outdated or replaced by a newer article.
Archived: The article is hidden from everyone but can still be restored if needed.
A knowledge category is a tag that groups related articles. For example, categories like 'Password Reset', 'Email Setup', or 'VPN Access' help users filter search results. Categories can be nested, meaning you can have a top-level category called 'Account Access' and a subcategory called 'Password Reset' inside it.
The self-service portal is the website where end users log in to find articles, submit requests, check the status of their existing tickets, and chat with agents. In ServiceNow, the standard portal is called the Service Portal. You can customise its look, add widgets (like a search bar or a 'Top Articles' list), and decide which knowledge bases are searchable from the portal.
Why does all this exist? Before knowledge management, every time a user had a common problem like 'I forgot my password', they would call the service desk, wait on hold, and an agent would spend five minutes resetting it. Multiply that by thousands of employees and hundreds of common issues, and the cost in time and money is enormous. A knowledge base lets users fix their own password in two minutes by reading the 'Password Reset' article. The service desk team can focus on complex problems that truly need a human.
Key technical concepts you must understand:
KB Article states: As mentioned, Draft, Review, Published, Retired, Archived. Each state has different visibility rules. For the exam, remember that only Published articles appear on the portal.
Can read without account: This is a check-box on the knowledge base record. If ticked, anyone on the internet can read articles from that base without logging in. Useful for public-facing knowledge.
Article number: Every article gets a unique reference like 'KB0012345'. You can use this number to link to the article directly.
Flag: Articles can be flagged for review, meaning a knowledge manager knows that this article might need an update.
Attachments: You can attach files to articles, but remember that attachments use storage space and can affect performance if very large.
ServiceNow also provides a 'Related Knowledge' feature that automatically suggests articles based on the content of a ticket. When an agent is working on an incident, the system shows a panel with articles that might help solve the issue. This speeds up resolution and encourages agents to reuse existing knowledge rather than reinventing the wheel.
Create a Knowledge Base
Navigate to Knowledge Management > Knowledge Bases, click 'New', give it a name (e.g., 'HR Policies'), set the 'Can read without account' flag to 'No' for internal use, and assign a knowledge manager. This defines the container where all your articles will live.
Define Knowledge Categories
Go to Knowledge Management > Knowledge Categories, click 'New', and create categories like 'Password Reset' or 'Email Setup'. These tags organise articles so users can filter search results. You can create subcategories to nest topics.
Create an Article
Within the knowledge base, click 'New Article'. Fill in the title, short description, and body text. Attach any supporting files (PDFs, images). Set the initial state to 'Draft'. This is the content creation stage.
Submit for Review
Once the article is complete, change its state from 'Draft' to 'Review' and assign a reviewer (usually the knowledge manager). The reviewer checks for accuracy, clarity, and compliance before allowing the article to go live.
Publish the Article
The reviewer changes the state to 'Published'. The article is now live on the self-service portal. End users can search for it, view it, and rate it. You can also set a retirement date for automatic removal later.
Configure the Self-Service Portal
Go to Service Portal > Designer, find the 'Knowledge Base' widget on your portal homepage, and configure it to search from the knowledge base you created. Add a 'Top Articles' widget to show popular content. Save and preview.
An IT professional at a mid-sized company (1,200 employees) is tasked with setting up a knowledge base for the HR department. The HR team needs to publish articles about holiday policies, expense reimbursement procedures, and benefits enrolment deadlines. The IT professional must ensure these articles are only visible to employees (not the public), that they appear on the company's employee self-service portal, and that older articles are automatically retired after they expire.
Step by step, here is what the IT professional does:
Creates a new knowledge base called 'HR Policies' in ServiceNow. They set the 'Can read without account' check-box to 'No' so that only authenticated users can see it. They also assign the knowledge manager role to the HR director so that HR can approve articles themselves.
In the knowledge base record, they configure the default article state to 'Draft' so that new articles are not accidentally published. They also set a 'Retirement date' field in the article template. Any article with a retirement date in the past will automatically move to the 'Retired' state when a scheduled job runs.
They create knowledge categories: 'Leave and Holiday', 'Expenses', 'Benefits', and 'General Policies'. Inside 'Leave and Holiday', they add subcategories like 'Annual Leave', 'Sick Leave', and 'Parental Leave'.
They create a sample article about the holiday request process. The article includes a step-by-step guide, a link to the holiday request form on the portal, and a PDF attachment of the official policy document. They set the article to 'Draft', then submit it for review. The HR director logs in, reviews the article, and changes its state to 'Published'.
They go to the Service Portal and add a 'Knowledge Base' widget to the home page. They configure the widget to search only the 'HR Policies' knowledge base. They also add a 'Top Articles' widget that shows the three most-viewed HR articles this month.
After six months, the retirement date on the holiday policy article passes. A scheduled job automatically changes its state to 'Retired'. The article disappears from the portal search results, but it still exists in the knowledge base for audit purposes.
The IT professional monitors usage reports. They see that the 'Password Reset' article (which they also own) has been viewed 450 times this month, saving an estimated 75 hours of service desk time. They use this data to justify expanding the knowledge base to other departments.
The SNOW-CSA exam tests Knowledge Management and Self-Service heavily. Expect around 8-12 questions on this topic, most of them scenario-based. You will be given a description of a company's needs and asked to choose the correct configuration steps or identify the best article state.
Here are the specific concepts the exam loves:
Article states and transitions: You must memorise the exact states (Draft, Review, Published, Retired, Archived) and know which user roles can move an article between them. A common question: 'An author has finished writing an article. What state should they set it to next?' Answer: Review.
Knowledge base permissions: The exam will test whether you know that 'Can read without account' makes articles public. They might give you a scenario where an article needs to be visible only to logged-in users, and the correct answer is to uncheck that box.
Portal visibility: They will ask which knowledge bases appear on the portal. The correct answer is: only knowledge bases that are explicitly configured in the portal's 'Knowledge Base' widget or search source.
Flag and retirement: You need to know that flagging an article notifies the knowledge manager that it might need updating, and that retirement can be manual or automated via a scheduled job.
Category structure: Expect a question like 'Where do you create knowledge categories?' Answer: In the Knowledge Category module under Knowledge Management.
Searching knowledge: They test that portal search uses the 'kb_knowledge' table and that the 'IR' (Index and Relevance) engine prioritises Published articles.
Attachments in articles: You must know that attachments are stored in the 'db_attachment' table, and that they are included when you export a knowledge base.
ServiceNow's 'Related Knowledge' feature: The exam might ask how articles are suggested to agents. The correct answer: based on the incident's Short Description or Work Notes.
Trap to watch out for: The exam sometimes describes a scenario where an article is in 'Draft' state and a user says they cannot see it on the portal. The trap answer might be 'the article needs to be flagged'. But the real reason is that only 'Published' articles appear on the portal. Always check the state first.
Another trap: They might ask about the 'Retired' state versus 'Archived'. Remember: Retired articles are still searchable by administrators and can be viewed (but not by end users). Archived articles are not searchable at all unless you specifically look in the archive table. The exam expects you to know that Archived is the deeper, more permanent removal.
Key definitions to memorise:
Knowledge base: container.
Article: individual piece of content.
Category: grouping tag.
Portal: front-end website.
State: lifecycle status.
Flag: review indicator.
Can read without account: public visibility toggle.
A knowledge base is a container for articles, and you control who can see it using the 'Can read without account' flag at the knowledge base level.
Only articles in the 'Published' state appear on the self-service portal for end users.
An article moves through five states: Draft, Review, Published, Retired, and Archived.
You must assign a knowledge manager to a knowledge base before articles can be reviewed and approved.
Knowledge categories are hierarchical tags that help users filter search results on the portal.
The self-service portal uses widgets like 'Knowledge Base' and 'Top Articles' to surface relevant content to users.
Flagging an article notifies the knowledge manager that the content might need updating.
Retired articles are not deleted; they are hidden from end users but can be restored by administrators.
These come up on the exam all the time. Here's how to tell them apart.
Knowledge Base
A container that holds multiple articles.
Has its own permissions (e.g., can read without account).
Created under Knowledge Management > Knowledge Bases.
Knowledge Category
A tag or label used to group articles within a base.
Does not have its own access control; inherits from the base.
Created under Knowledge Management > Knowledge Categories.
Draft State
Article is still being written by the author.
Visible only to the author and users with 'write' permission.
Can be edited freely without notification.
Review State
Article is submitted for approval by a knowledge manager.
Visible to the reviewer and the author (not end users).
Cannot be edited without undoing the review submission.
Retired State
Article is hidden from end users but still in the main table.
Administrators can view and restore the article.
Occurs automatically on a scheduled retirement date.
Archived State
Article is moved to a separate archive table.
Not searchable in the normal articles list even by admins.
Requires manual archival action; no automatic process.
Service Portal
The overall website where end users interact with ServiceNow.
Includes many widgets, navigation, and branding.
Configured in Service Portal > Designers.
Knowledge Base Widget
A specific component on the portal that displays knowledge articles.
Controls which knowledge bases are searchable from the portal.
Configured within the portal page editor.
Mistake
Articles that are in 'Review' state are visible to end users on the portal.
Correct
Only 'Published' articles appear on the portal. 'Review' articles are only visible to the reviewer and the author.
Beginners often think 'Review' means 'approved' because in everyday language 'under review' sounds close to 'approved'. But in ServiceNow, 'Review' is a pre-publish stage where the content is not yet live.
Mistake
You can create a knowledge base without setting up a knowledge manager role.
Correct
ServiceNow requires that you assign a knowledge manager to a knowledge base before articles can be reviewed. Without one, articles will remain stuck in 'Draft' or 'Review' forever.
Many new administrators skip the role assignment because they expect the system to work with default permissions. But the workflow depends on a human being assigned to the 'Knowledge Manager' role to approve or reject submissions.
Mistake
If an article is retired, it is permanently deleted and cannot be recovered.
Correct
Retired articles are not deleted. They simply change to 'Retired' state and become invisible to end users. Administrators can still see them and can set them back to 'Published' if needed. 'Deleting' an article requires a separate action and permanently removes it.
The word 'retired' sounds final, like 'archived' in email, but in ServiceNow it is a soft removal. People assume deletion when they see the article disappear from search.
Mistake
The 'Can read without account' check-box applies to individual articles.
Correct
That check-box is configured at the knowledge base level, not per article. All articles in that knowledge base either require login or do not, depending on the base setting.
New administrators often look for a per-article permission and get confused when they cannot find it. The exam tests that you know this is a base-level setting.
Mistake
Attachments in knowledge articles are stored as part of the article record in the 'kb_knowledge' table.
Correct
Attachments are stored in the 'db_attachment' table, not in the article table itself. The article record simply links to the attachment.
It is natural to assume an uploaded file is stored inside the same database row as the article content, but ServiceNow separates them for performance reasons.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
Go to the knowledge base record that contains the article, and tick the 'Can read without account' check-box. This makes all articles in that base visible to anyone on the internet, not just logged-in users.
The article's state changes to 'Retired'. It no longer appears in portal search results for end users, but administrators can still find and restore it. It is not deleted.
Yes. While editing an article, use the 'Attachments' section to upload PDFs, images, or other files. They are stored separately in the 'db_attachment' table and appear as downloadable links in the published article.
Check the article state. It must be 'Published'. Also confirm that the knowledge base containing the article is configured as a search source in the portal's 'Knowledge Base' widget.
Edit the knowledge base record, find the 'Knowledge Manager' field, and select a user who has the 'knowledge_manager' role. That person will be responsible for reviewing and approving articles.
Retired articles are hidden from end users but still visible to administrators in the standard article list. Archived articles are moved to a separate archive table and require extra steps to view or restore. Archive is a deeper removal.
You've finished Knowledge Management and Self-Service. Continue through the SNOW-CSA study guide to build a complete picture of the exam.
Done with this chapter?