---
sourceDocument: Yokohama Employee Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/employee-service-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Employee Service Management

ft:clusterId :

    - emplsm

bundleId :

    - emplsm

workflow :

    - Employee


---

# Properties installed with Content Experiences

# Properties installed with Content Experiences {#ariaid-title1}

Release version: Yokohama  
Updated January 30, 2025  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 8 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Properties installed with Content Experiences

The Content Experiences \[snca\] plugin in ServiceNow adds configurable properties that control how campaigns run, focusing on scheduled jobs and system performance.
These properties allow you to manage campaign execution timings, audience targeting, and content scheduling to optimize resource use and minimize impact on your instance.
Show full answer Show less  
You can access these properties via **Content Experiences \> Configurations \> Properties**. Properties marked with an asterisk () have default values recommended for campaigns targeting 100,000 users or fewer, with options to increase values for larger audiences if scheduled jobs run longer than expected.

## Key Properties and Their Practical Uses

* **Approvals**: Control whether all approvers must approve scheduled content before publishing or if a single approval suffices.
* **Content Management Ownership**: Enable ownership controls for audiences, content items, topics, and portal pages, allowing restrictions on who can schedule or edit content.
* **Scheduled Job Controls**: Define max run times, event staggering, and limits for adding users to campaigns, sending notifications, managing to-dos, deactivating users, and purging campaign data. These settings help manage job duration and workload to ensure smooth operation.
* **Content Limitations**: Set maximum numbers for campaign targets, records processed, notifications sent (email, SMS, push), and users handled per job run to prevent performance degradation, especially for large databases.
* **State Management**: Configure delays and record update limits related to campaign publication state transitions and immediate triggering of campaigns post-publish, with recommendations based on audience size.
* **User Deactivation and Purging**: Control how many users to deactivate or purge per job run, scheduling of purge operations after campaigns end or users exit campaigns, including configurable delay periods.
* **Campaign Re-evaluation**: Set frequency in days for automatic re-evaluation of campaign audiences, adjustable on the campaign form for flexibility.
* **Portal Preview**: Define the URL suffix for service portal or Employee Center previews, enabling testing of content across different portals.

## Why These Properties Matter

These properties enable you to tailor campaign execution and content management to your organization's scale and performance needs. By adjusting run times, event staggering, and record limits, you ensure campaigns run efficiently without overloading the system. Ownership and approval settings enhance content governance, while purging and deactivation controls maintain data hygiene and system health.

## What You Can Expect

* Optimized scheduled job performance with limits on run times and workloads to reduce impact on your ServiceNow instance.
* Granular control over campaign content approval and ownership, helping maintain governance and content quality.
* Configurable notification and user management parameters to scale campaigns appropriately for large audiences.
* Automated campaign audience re-evaluation and content preview capabilities to improve campaign accuracy and delivery.
* Data purging mechanisms to manage storage and maintain system efficiency post-campaign.  
The Content Experiences \[sn_ca\] plugin adds properties that determine how a campaign runs related to scheduled jobs and performance.
To access Content Experiences properties, navigate to Content ExperiencesConfigurationsProperties.  
Content Experiences properties determine how the scheduled jobs run and help to ensure that there is limited impact on the performance of your instance.  
Note:  
Properties with an asterisk (\*) in front of the name indicates that the default values are recommendations when the number of users targeted is 100,000 or less. If your audience is over 100,000 and the scheduled jobs run longer than expected, you can try increasing the values. {#properties-installed-with-content-auto__table_ltb_wmq_zgb__entry__2}

| Property | Usage |
|-|-|
| All approvers must approve any schedule content record to publish it (sn_ca.all_must_approve) | Indicates that all approvers must approve any scheduled content prior to publishing it. If you check No, only one approver is required to publish a campaign. |
[Table 1. Approvals]

{#properties-installed-with-content-auto__table_ltb_wmq_zgb} {#properties-installed-with-content-auto__table_btz_j1r_gnb__entry__2}

| Property | Usage |
|-|-|
| Allow Ownership for Audiences (sn_cd.activate_audience_delegation_controls) | Indicates you want to be able to enable audience ownership within Content Experiences. For more information, see [Content Ownership](https://servicenow-prod.fluidtopics.net/yLqH5cBLxIP0L2QKunYKeA "Define who has permission to create content, where they can publish it, and which employees can view it."). |
| Allow Ownership for Content Items (sn_cd.activate_content_authoring_controls) | Indicates you want to be able to enable content item ownership within Content Experiences. For more information, see [Content Ownership](https://servicenow-prod.fluidtopics.net/yLqH5cBLxIP0L2QKunYKeA "Define who has permission to create content, where they can publish it, and which employees can view it."). |
| Allow Ownership for Topics (sn_cd.activate_topic_ownership) | Indicates you want to enable topic ownership within Content Experiences. Ownership of a topic includes: * Ability to restrict what groups or users can schedule content to a topic for a campaign. * Ability to edit content assigned to the topic. * Ability to preview content for the topic. {#properties-installed-with-content-auto__ul_nh1_g1p_hsb} Note: Other users that have access to the content can view the content scheduled to the restricted topic, but cannot remove the topic from the schedule. For more information on this and what roles are required, see [Content Ownership](https://servicenow-prod.fluidtopics.net/yLqH5cBLxIP0L2QKunYKeA "Define who has permission to create content, where they can publish it, and which employees can view it."). |
| Allow Ownership for Portal pages (sn_cd.activate_page_ownership) | Indicates you want to exclude groups or non-applicable content managers (specific users) from assigning content to a specific portal page. |
[Table 2. Enable Content Management Ownership]

{#properties-installed-with-content-auto__table_btz_j1r_gnb} {#properties-installed-with-content-auto__table_j5x_mgg_hsb__entry__2}

| Property | Usage |
|-|-|
| \*Max run time in seconds of scheduled job (Job will finish processing current item after time has elapsed) (sn_ca.add_users.max_run_time) | The maximum amount of time (in seconds) the Content Experiences: Update Campaign Audience scheduled job runs. Limits the length of the scheduled job, but completes any work in progress and does not pick up any new work. Default value: 1,800 seconds |
| The number of seconds to stagger events to process campaigns by (sn_ca.add_users.event_stagger.campaign) | The amount of time between campaign events when a scheduled job runs. Staggering provides time for the events to be processed during the staggered time. Default value: 300 seconds |
| The number in seconds to stager events to add user by (sn_ca.add_users.event_stagger.users) | The amount of time between campaign events to add users when the Content Experiences: Update Campaign Audience scheduled job runs. Staggering provides time for the events to be processed during the staggered time. Default value: 3 seconds |
| Max number of events to add users per campaign (sn_ca.add_users.max_events) | The maximum number of events that users can be added for a campaign when the Content Experiences: Update Campaign Audience scheduled job runs. Default value: 1,000 |
| Max number of users to add per event (sn_ca.add_users.max_users_per_event) | The maximum number of users you can add in a single event. Default value: 1000 |
[Table 3. Add users]

{#properties-installed-with-content-auto__table_j5x_mgg_hsb} {#properties-installed-with-content-auto__table_u3z_ssh_jdb__entry__2}

| Property | Usage |
|-|-|
| \*Max run time in seconds of scheduled job (Job will finish processing current item after time has elapsed) (sn_ca.campaign.max_run_time) | The maximum amount of time (in seconds) the Content Experiences: Add Non-Portal Campaign Content scheduled job runs. Limits the length of the Content Experiences: Send Email Notifications scheduled job, but completes any work in progress and does not pick up any new work. Default value: 2,700 seconds |
| \*Max number of campaign targets to process per job run (sn_ca.campaign.max_records_process) | The maximum number of people a campaign can target per scheduled job run. Default value: 100,000 |
| \*Max number of records to create per job run (sn_ca.campaign.max_records_create) | The maximum number of records to create per job run. Default value: 100,000 |
| The number of seconds to stagger events to process pending content by (sn_ca.campaign.pending.event_stagger) | The number of seconds between each time the Content Experiences: Add Non-Portal Campaign Content scheduled job runs to try to send non-portal content. Default value: 3 seconds |
[Table 4. Non-Portal Content]

{#properties-installed-with-content-auto__table_u3z_ssh_jdb} {#properties-installed-with-content-auto__table_thc_34y_fgc__entry__1}

| Note ||
|-|-|
| These properties determine limits on non-portal content (emails and SMS). The Content Experiences: Send Email Notifications scheduled job runs every hour by default and attempts to send non-portal content not sent in the first pass. Customers with a large database should consider increasing this property after testing the impact it could have on performance. ||
[Table 5. Non-Portal content limitations]

{#properties-installed-with-content-auto__table_thc_34y_fgc} {#properties-installed-with-content-auto__table_pfm_zhv_gfb__entry__2}

| Property | Usage |
|-|-|
| Max run time in seconds of scheduled job (Job will finish processing current item after time as has elapsed) (sn_ca.task.max_run_time) | The maximum amount of time (in seconds) the Content Experiences: Create To-dos scheduled job runs. Limits the length of the scheduled job, but completes any work in progress and does not pick up any new work. Default value: 300 seconds |
| Max number of records to create per job run (sn_ca.task.max_records_create) | The maximum number of records to create per scheduled job run. Default value: 25,000 |
[Table 6. To-do Content]

{#properties-installed-with-content-auto__table_pfm_zhv_gfb} {#properties-installed-with-content-auto__table_rty_qph_jdb__entry__2}

| Property | Usage |
|-|-|
| The maximum number of users to add per event for SMS (sn_ca.sms_notification.max_users_per_event) | The maximum number of users to add per event for an SMS notification. Default value: 1,000 |
| \*Max run time in seconds of scheduled job (Job will finish processing current item after time has elapsed) (sn_ca.notification.max_run_time) | The maximum amount of time (in seconds) the Content Experiences: Send Email Notifications, Content Experiences: Send Push Notifications, Content Experiences: Send SMS Notifications scheduled jobs run. Default value: 1,800 seconds |
| \*The maximum number of events to queue per job run for SMS (sn_ca.sms_notification.max_events) | The maximum number of events to queue for SMS messages when the Content Experiences: Send Email Notifications, Content Experiences: Send Push Notifications, Content Experiences: Send SMS Notifications scheduled jobs run. Default value: 100 Note: The Notify (com.snc.notify ) plugin must be activated for this sys property and Content Experiences: Send SMS Notifications scheduled job to appear. |
| The number of seconds to stagger events by (sn_ca.notification.event_stagger) | The amount of time between events when the Content Experiences: Send Email Notifications, Content Experiences: Send Push Notifications, Content Experiences: Send SMS Notifications scheduled jobs run. Staggering provides time for the events to be processed during the staggered time. Default value: 3 seconds |
| \*The maximum number of events to queue per job run for Email (sn_ca.notification.max_events) | The maximum number of events to queue for the Content Experiences: Send Email Notifications, Content Experiences: Send Push Notifications, Content Experiences: Send SMS Notifications scheduled jobs run. Default value: 100 |
| The maximum number of events to queue per job run for Email (sn_ca.notification.max_events) | The maximum number of events to queue per job run for email notifications. Default value: 100 |
| The maximum number of users to add per event for Email (sn_ca.notification.max_users_per_event) | The maximum number of users to add per event for email notifications. Default value: 1,000 |
[Table 7. Notifications]

{#properties-installed-with-content-auto__table_rty_qph_jdb} {#properties-installed-with-content-auto__table_fb5_5ph_jdb__entry__2}

| Property | Usage |
|-|-|
| The number of seconds to stagger the sn_ca.campaign.published event after kicking off the Create To-Dos and Send Notifications Flow Designer Actions. Default is 2700 seconds or 45 minutes. (sn_ca.campaign.published.event_stagger) | Determines the time to delay the publication of a campaign after the Create To-Dos and Send Notifications Flow Designer Actions are started. This sys property determines when the state of a campaign is set back to Published after going through the other states. The Published state is required for the scheduled jobs to pick up for future processing. Default value: 2700 seconds or 45 minutes. |
| Max run time in seconds of scheduled job (Job will finish processing current item after time has elapsed) (sn_ca.state_management.max_run_time) | The maximum amount of time (in seconds) the Content Experiences: Manage Content States scheduled job runs. Default value: 300 seconds |
| Used to manage whether we want to trigger the campaign publishing process immediately after publishing the campaign. (sn_ca.publish.campaign.immediately) | Check Yes to indicate you want a campaign to trigger immediately after selecting the Publish button. Checking Yes is recommended for campaigns targeting less than 100,000 users. Note: Selecting Yes bypasses the scheduled jobs and is dependent on the start date and time. |
| Max number of records to update per job run (sn_ca.state_management.max_records_update) | The maximum number of records to update per job run. Default value: 25,000 |
[Table 8. State Management]

{#properties-installed-with-content-auto__table_fb5_5ph_jdb} {#properties-installed-with-content-auto__table_uq4_bqh_jdb__entry__2}

| Property | Usage |
|-|-|
| Max run time in seconds of scheduled job (Job will finish processing current item after time has elapsed) (sn_ca.user_deactivation.max_run_time) | The maximum amount of time (in seconds) the Content Experiences: Deactivate Campaign Users scheduled job runs. The scheduled job deactivates flagged users. Default value: 300 seconds |
| Max number of users to deactivate per job run (sn_ca.user_deactivation.max_users_per_job) | The maximum number of users to deactivate per job run. The Content Experiences: Deactivate Campaign Users scheduled job runs every six hours by default. Default value: 25,000 users |
[Table 9. User Deactivation]

{#properties-installed-with-content-auto__table_uq4_bqh_jdb} {#properties-installed-with-content-auto__table_jyq_t4y_fgc__entry__1}

| Note |
|-|
| These properties determine limits on the Content Experiences: Deactivate Campaign Users scheduled job for optimal performance. Customers with a large database should consider increasing this property after testing the impact it could have on performance. |
[Table 10. Content Experiences limitations]

{#properties-installed-with-content-auto__table_jyq_t4y_fgc} {#properties-installed-with-content-auto__table_e2s_tqh_jdb__entry__2}

| Property | Usage |
|-|-|
| Max run time in seconds of scheduled job (Job will finish processing current item after time has elapsed) (sn_ca.purging.max_run_time) | The maximum amount of time (in seconds) the Content Experiences: Purge Campaign Data scheduled job runs. Default value: 300 seconds |
| Max number of users to purge per job run (sn_ca.purging.max_users_per_job) | The maximum number of users to purge per job run. Default value: 25,000 |
| Purge campaign data after the campaign ends (sn_ca.purging.purge_after_campaign_end) | Purge all campaigns when the end date is reached. Default value: Yes |
| Number of days after the campaign ends to start purging campaign data (sn_ca.purging.days_after_campaign_end) | The number of days after the campaign end date when campaigns are purged. Default value: 180 days |
| Purge campaign data for a user after user exits campaign (sn_ca.purging.purge_on_user_removed) | Indicates if campaign information for a user should be purged after the user is removed from the campaign. Default value: Yes |
| Number of days after user exits campaign to start purging campaign data (sn_ca.purging.days_after_user_removed) | The number of days after a user is removed from a campaign to remove the campaign information. Default value: 180 days |
[Table 11. Purging]

{#properties-installed-with-content-auto__table_e2s_tqh_jdb}

## Campaign Re-evaluation {#properties-installed-with-content-auto__section_shs_vtq_zjb}

{#properties-installed-with-content-auto__table_ppw_ztq_zjb__entry__2}

| Property | Usage |
|-|-|
| The number of days after which the campaign audience to be re-evaluated (sn_ca.campaign.reevaluation_frequency) | The default number of days to re-evaluate a campaign audience. You can override this default from the Re-evaluate campaign and Re-evaluate frequency fields on the Campaign form. For more information, see [View campaign targets](https://servicenow-prod.fluidtopics.net/XqitHhFJvErrYJE7Qk~nNw "Use campaign targets to view a list of employees that your campaign has targeted, their status, and the date they were added."). Default value: 7 days |
[Table 12. Campaign Re-evaluation]

{#properties-installed-with-content-auto__table_ppw_ztq_zjb}

## Portal Preview {#properties-installed-with-content-auto__section_vgq_rtw_n4b}

{#properties-installed-with-content-auto__table_wgq_rtw_n4b__entry__2}

| Property | Usage |
|-|-|
| Service Portal URL suffix you want to use for portal previews (sn_cd.preview.portal_url_suffix) | The URL suffix of the service portal or Employee Center (EC) your company uses for portal previews. You can change this system property when you want to preview your content over different portals. Default value: esc |
[Table 13. Portal Preview]

{#properties-installed-with-content-auto__table_wgq_rtw_n4b}
**Related concepts**   

* [Campaign overview and Campaign analytics dashboards](https://servicenow-prod.fluidtopics.net/Wo55oyhCdM7AgNNWXq0vIg "Content Analytics collects data on user interactions and generates visualizations to help campaign managers determine the effectiveness of campaigns.")
* [Content Analytics dashboards](https://servicenow-prod.fluidtopics.net/g95TRLtN36yXAPn3i4pUnQ "Content Analytics display data visualizations for portal data collected in the default tracking profile.")
* [Content engagement dashboard](https://servicenow-prod.fluidtopics.net/HHQcnW2ZDYCN3QozEXe5Lg "Content analytics displays data visualizations of engagement metrics for content published to the portal or Now mobile app in the Content Engagement dashboard.")
* [Content Library Overview dashboard](https://servicenow-prod.fluidtopics.net/9jtUtHD1vnVVDUdo8sztBQ "Content analytics displays data visualizations of performance metrics for content published to the portal or Now mobile app in the Content Library Overview dashboard.")
* [Feedback Analytics dashboard](https://servicenow-prod.fluidtopics.net/pNyCDgwaKa74Ou3cvQMp3Q "Track all your feedback responses with the Feedback Analytics for portals, email, Virtual Agent, kiosks, and Now Mobile.")  
**Related reference**   

* [Approvals experience reference](https://servicenow-prod.fluidtopics.net/xGOvpWvaWlHizZ9NZttO~g "Use the following reference information for better approval experience.")
* [Block content form](https://servicenow-prod.fluidtopics.net/vpb5Ie9iFabDXm8zry0Jqg "Block content form")
* [Components installed with Employee Center Pro](https://servicenow-prod.fluidtopics.net/bFe86DJvYklEwuBTGk9GbA "Several types of components install with the activation of the Employee Center Pro plugin, including user roles and tables.")
* [Components installed with Content engagement](https://servicenow-prod.fluidtopics.net/SoNeXpVIfJKWUF~3YsYPRA "Several types of components are installed with activation of the Content engagement plugin, including tables, user roles, and scheduled jobs.")
* [Components installed with Content Experiences](https://servicenow-prod.fluidtopics.net/KR0Q83iQQ_aJEb766WFQTw "Several types of components install with the activation of the Content Experiences [sn_cd] plugin, including tables, user roles, and scheduled jobs.")
* [Components installed with Content Publishing](https://servicenow-prod.fluidtopics.net/6yVP7pRXh6l_p_JllmMRLA "Several types of components install with the activation of the Content Delivery [com.sn_content_delivery] plugin, including tables, user roles, and scheduled jobs.")
* [Components installed with Content Governance](https://servicenow-prod.fluidtopics.net/IaHXrPW5CnLqltmoAPlAJw "Several types of components install with the activation of the Content Governance [sn_cg] plugin, including tables, user roles, and scheduled jobs.")
* [Components installed with Content Analytics](https://servicenow-prod.fluidtopics.net/v8XPQtdVkxIdNOVfqR8Hwg "Several types of components install with the activation of the Content Analytics [sn_cda] plugin, including tables, user roles, and scheduled jobs.")
* [Employee Center Pro widgets](https://servicenow-prod.fluidtopics.net/dmRp4exLTvxivp2TanlIgg "You can use base system widgets as-is in the portal or clone them to suit your own business needs.")
* [Feedback configuration form](https://servicenow-prod.fluidtopics.net/wkXrMA~DiWVC2dZEnbIVYA "Description of the feedback configuration form fields to target a portal for feedback responses.")
* [Feedback definition form](https://servicenow-prod.fluidtopics.net/OlcFc__wR3MlIXaipJtXLA "Description of the feedback definition form fields to curate the experience and service feedback widgets in the portal pages.")
* [Link content form](https://servicenow-prod.fluidtopics.net/NvYtLJUndIqgqS1QX4So5Q "Link content form.")
* [Location Consent form](https://servicenow-prod.fluidtopics.net/JHmx617HcPI3Ta4h5_IRpA "The location consent form helps you configure the communication channels for appointment bookings.")
* [Notification content form](https://servicenow-prod.fluidtopics.net/_RCsTU9zwa0upgnIfGejqw "Notification content form")
* [Properties installed with Content Governance](https://servicenow-prod.fluidtopics.net/FEdgeioM9nYGw_5Oht9dWQ "The Content Governance [sn_cg] plugin adds properties that determine how many records to show in the Content Operations dashboard.")
* [Properties installed with Content Publishing](https://servicenow-prod.fluidtopics.net/TDsWC69DwTLCClmk2YA_PQ "The Content Publishing [com.sn_content_delivery] plugin adds the following properties that are designed to control how scheduled jobs work in relation to notifications, to-dos, and communities.")
* [Schedule appointment form](https://servicenow-prod.fluidtopics.net/RfB6oKkWXjufcFnzPqPelg "Use the Schedule appointment form to select a reason and provide contact information for your appointment.")

*[\>]: and then