Skip to main content
Administrator Guide
Last Updated: 2026-11-06
About the ServiceNow Connector for Self-Service Agent

About the ServiceNow Connector for Self-Service Agent

This topic describes capabilities, limitations, and best practices related to the ServiceNow integration with Self-Service Agent.

Article Ingestion

Workday ingests ServiceNow Knowledge Article records (kb_knowledge) in the Published workflow state only. Articles in any other workflow state, such as Draft, Review, Retired, or Outdated, are excluded.
Workday ingests the article body from the article text field.
Workday does not ingest article attachments (sys_attachment) or process attachment content to answer worker queries. If an attachment contains critical information required for responses, move the attachment content directly into the HTML body text of a Knowledge Article.

Security and Architecture

Self-Service Agent follows the read access your workers have in ServiceNow, based on the user criteria and roles on your knowledge bases and articles. Workday applies article-level user criteria only when the glide.knowman.apply_article_read_criteria system property is set to true.
Workday identifies ServiceNow users by the email address on their user record, or by their user name if it’s formatted as an email. Users without either aren’t included in the permissions Workday syncs.
Permission changes are checked every 3 hours.
Workday does not support block-level security for Knowledge Blocks (kb_knowledge_block). While embedded Knowledge Blocks are ingested as part of the parent article's rendered text, Self-Service Agent will not enforce block-level User Criteria (Can Read / Cannot Read conditions). Consequently, a worker who lacks access to view a specific Knowledge Block within ServiceNow may still receive answers derived from its content. To secure restricted content, extract the Knowledge Block into a standalone Knowledge Article and apply article-level user criteria.
Workday doesn’t evaluate advanced scripted user criteria or custom fields added to user criteria. Criteria that would grant access grant it to no one, and criteria that would deny access block everyone. To make those articles available, replace them with static user criteria based on groups, roles, departments, locations, or companies.

Help SKU and the ServiceNow Connector

The ServiceNow connector for Policy Intelligence doesn't require the Workday Help SKU. However, if you want to use Workday Help in addition to ServiceNow, then the Workday Help SKU is required.
When you don’t have the Workday Help SKU, you must configure ServiceNow before enabling the Policy Intelligence skill; otherwise, we display an error and the skill won’t be enabled.
If you have the:
  • Workday Help SKU and don't configure the ServiceNow connector, the Self-Service Agent provides answers from your Help articles only.
  • ServiceNow connector configured and don't have the Help SKU, the Self-Service Agent provides answers from your SharePoint documents only.
  • ServiceNow connector configured and the Help SKU, the Self-Service Agent provides answers from both. We recommend that you have a single policy in 1 system or the other so that the agent doesn’t provide inaccurate answers.
There are no additional costs for configuring the ServiceNow connector or for storing policy files in Workday. The Policy Intelligence skill consumes the same amount of Flex Credits irrespective of where the answer came from.

Best Practices

URLs: Spell out the URLs in the policy files so that the agent includes them in a response.
Content: Because Workday can’t follow links in articles, add important linked content to the article itself or connect the knowledge base that contains the linked article.