--- title: Requesting content description: Content Governance provides multiple ways for employees to request content to be created for employee communications and for your company's content team to clarify the request and assign the request to team members.Employees that have access to the Employee Center Pro can request content to be developed for distribution to other employees.Employees who have access to Service Catalog can request content from the Service Catalog.The content team uses the Content Request form to create a content request when the original request was made verbally or through some other method outside of Content Governance. The Content Request form enables the content team to create a content request and then assign, track, review, approve, and publish content.Use the Content Request Item form to provide details on what type of content should be created from a content request. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/employee-service-management/employee-experience-foundation/ec-content-gov-request.html release: australia product: Employee Experience Foundation classification: employee-experience-foundation topic_type: concept last_updated: "2026-03-12" reading_time_minutes: 20 breadcrumb: [Managing content requests, Authoring and managing employee communications, Employee Center Pro, Unified Employee Experience, Employee Service Management] --- # Requesting content Content Governance provides multiple ways for employees to request content to be created for employee communications and for your company's content team to clarify the request and assign the request to team members. Once a content request has been created, Content Governance provides the ability to track the request, review the content created from the request, approve it, and publish it. There are several ways for your employees to request content to be created: - **[Employee Center Pro](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/employee-service-management/employee-experience-foundation/ec-content-gov-request.md)** Employees can use the Content Request catalog item from the Employee Center Pro. Your company decides where on the Employee Center Pro it appears. Any employee that has access to Employee Center Pro can request content. - **[Service Catalog](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/employee-service-management/employee-experience-foundation/ec-content-gov-request.md)** Employees can request content from the Service Catalog similar to requesting content from the Employee Center Pro. - **[Content Request form](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/employee-service-management/employee-experience-foundation/ec-content-gov-request.md)** Primarily used by the content team to create a content request when the original request was made verbally or through some other method. The **Content Request** form allows the content team to create the request, then track, review, approve, and publish the content that is created from the request. ## Request content from the Employee Center Pro Employees that have access to the Employee Center Pro can request content to be developed for distribution to other employees. ### Before you begin Role required: none You can use unified taxonomy to link the request content to a topic so the request can be accessed from the Topic page. For more information, see [Unified Taxonomy for Employee Center](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/employee-service-management/employee-experience-foundation/config-taxonomy.md). ### Procedure 1. Navigate to **All** > **Self-Service** > **Employee Center**. 2. Select **Content Request**. Your company decides where on the Employee Center this appears. **Note:** You can also enter **Content Request** from the Search bar. 3. Fill in the fields on the **Content Request** form.
| Field | Description |
|---|---|
| **\*Please select the type of communication you'd like to schedule** | How you want your content to be communicated. Your choices are:- Portal - Mobile - To-do - Other |
| **\*What type of content do you need for your communication?** | The type of content you want communicated. The type of content depends on what type of communication you select in the field above. Your choices for Portal are: - Banner - Video - Topic Content Section - What is your desired Topic page? This field appears when you select Topic Content Section. - Enter the topic page you want your requested content to appear in. - Other Your choices for Mobile are: - Banner - Video Your choices for To-do are: - Click a button - View a video - Click a link - Sign a document Your choices for Other are: - Email - SMS Text - Other **Note:** The Content Manager should define what it means to select Other/Other. For example, it could be used for another type of personal communication like company chat. |
| **What is your desired Topic page?** | Enter the topic page you want your content to appear in. This field only appears when you select **Topic Content Selection** from the **What type of content do you need for your communication** drop-down. For more information, see [Dynamic topic pages](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/employee-service-management/employee-experience-foundation/dynamic-topic-page.md). |
| **Which employees should see your communication?** | Who you want your content to be directed to.You can direct your content at all employees or as specific as you want. For example, you may want your content only available to employees that work and reside in the US and have different content for employees outside the US. You can also have your content and communication target specific employees, groups, divisions, specific roles, or job titles. |
| **Start date** | The date you want you content made available. |
| **End date** | The date you want your communication to stop. |
| **What languages will you need the content translated into?** | The language\(s\) you want your content to be created in and made available to your audience.**Note:** The available languages are dependent on what your company has installed. |
| **Please add any additional reviewers required for your communication \(optional\)** | Click into the field and select people you want to review and approve the content that is created from your request.When approvals are required and the content request item is moved to the **In Review** state, the content request appears under **My tasks** for the reviewers and approvers. The content can be previewed, approved, or don't approve. |
| **Please add any additional information about your communication \(optional\)** | Details that can clarify what you want included in the content you are requesting. |
| **Please add a URL for your call to action button \(optional\)** | A URL link you want your audience to select if you are requesting to-do, survey, or any type of action content. |
| **Add attachments** | Any files that you want to be included in the content you are requesting. |
| Field | Description |
|---|---|
| **\*Please select the type of communication you'd like to schedule** | How you want your content to be communicated. Your choices are:- Portal - Mobile - To-do - Other |
| **\*What type of content do you need for your communication?** | The type of content you want communicated. The type of content depends on what type of communication you select in the field above. Your choices for Portal are: - Banner - Video - Topic Content Section - What is your desired Topic page? This field appears when you select **Topic Content Section**. - Enter the topic page you want your requested topic to appear in. - Other Your choices for Mobile are: - Banner - Video Your choices for To-do are: - Click a button - View a video - Click a link - Sign a document Your choices for Other are: - Email - SMS Text **Note:** Requires integration with Notify. For more information, see [Notify](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/notify-landing-page.md). - Other **Note:** The Content Manager should define what it means to select Other/Other. For example, it could be used for another type of personal communication like company chat. |
| **What is your desired Topic page?** | Enter the topic page you want your content to appear in. This field only appears when you select **Topic Content Selection** from the **What type of content do you need for your communication** drop-down.For more information, see . |
| **Which employees should see your communication?** | Who you want your content to be directed to. |
| **Start date** | The date you want you content made available. |
| **End date** | The date you want your communication to stop. |
| **What languages will you need the content translated into?** | The language\(s\) you want your content to be created in and made available to your audience.**Note:** The available languages are dependent on what your company has subscribed to. |
| **Please add any additional reviewers required for your communication \(optional\)** | Select the **Lock** \[Omitted image "icon-hr-unlock-add-parties.png"\] Alt text: Lock icon icon. Next, select the Lookup using list \[Omitted image "magnify-glass-outline-icon.png"\] Alt text: Lookup using list icon icon. Select people you want to review the content that is created from your request. When approvals are required and the content request item is moved to the **In Review** state, the content request appears under **My tasks** for the reviewers and approvers. The content can be previewed, approved, or rejected. |
| **Please add any additional information about your communication \(optional\)** | Details that can clarify what you want included in the content you are requesting. |
| **Please add a URL for your call to action button \(optional\)** | A URL link you want your audience to select if you are requesting to-do, survey, or any type of action content. |
| **\[Omitted image "attach-icon.png"\] Alt text: Manage Attachments icon Manage Attachments** | Any files that you want to be included in the content you are requesting. |
| Field | Description |
|---|---|
| **Number** | A unique number that identifies the content request. This field pre-fills the content request number and cannot be edited and has a CONREQ prefix followed by a sequential number. |
| **Assigned to** | The person assigned to create the content from the content request.**Note:** After the record is saved, a notification email is sent to the assigned to person. If you select an assignment group, the Assigned to person must be a member or the selected group. When you enter an Assigned to person, this person automatically appears as the Assigned to person in a Content Request Item. If you leave this field blank, the Assigned to person on a Content Request Item is also blank. |
| **Assignment group** | The group assigned to create the content from the content request. If you select an assignment group, the Assigned to person must be a member or the selected group. **Note:** For more information, see [Manage ownership groups](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/create-edit-ownership-group.md). When you enter an assignment group in this field, it automatically appears in the **Assignment group** field for a Content Request Item. You can only enter members of that group to the **Assigned to** field for a Content Request Item. |
| **Opened by** | The person who is requesting the creation of content. |
| **Priority** | The urgency associated with the content request. Your choices are:- 1- Critical - 2 - High - 3 - Moderate - 4 - Low - 5 - Planning |
| **State** | The status of the content request.- New - Assigned - Work in Progress - In Review - Ready to Publish - Published - Cancelled |
| **Due date** | The date the request for content should be completed. |
| **Short description** | A short description of the content request. The text entered here appears by default in the short description for the content item. |
| **Description** | A longer description of the content request with more details. |
| **Work notes** | Additional information about the content request.Work notes are useful if additional information is required from the requester. |
| **Additional comments \(Customer visible\)** | You can choose to make this information visible to the requester by checking the Additional comments \(Customer visible\) box. |
| Fields | Description |
|---|---|
| **Number** | A unique number that identifies the content item associated with a content request. |
| **Content Request** | A unique number that identifies the content request. This field pre-fills the content request number and cannot be edited and has a CONREQ prefix followed by a sequential number. |
| **Content** | The name of the content to fulfill the content request. Select the **Lookup using list** icon \(\[Omitted image "magnify-glass-outline-icon.png"\] Alt text: Lookup using list icon and select the content that was created to fulfill the content request. For more information on creating content, see [Portal content](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/employee-service-management/employee-experience-foundation/ec-streamline-content.md).Once content is selected and you fill in the required fields, you can save the content request item and schedule the content to be published. The **Schedule Content** related list appears after saving the record. For more information, see [Publishing content](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/employee-service-management/employee-experience-foundation/ec-content-publishing-schedule.md). |
| **Assigned to** | The person assigned to create the content from the content request.This field is required to change the state to **Work in Progress**. If you select an assignment group, the **Assigned to** person must be a member or the selected group. **Note:** When a person is entered in the **Assigned to** field for a Content Request, that person is automatically entered into this field when: - The **Assigned to** field is empty. - The **Assigned to** field is not automatically entered when: - The **Assignment group** field is different on the content request and content request item. - When the **Assigned to** field is manually entered on the content request item. Entering an assigned to person on the content request item does not override the assigned to person on a content request. |
| **Assignment group** | The group assigned to create the content from the content request. If you select an assignment group, the Assigned to person must be a member or the selected group. **Note:** For more information, see [Manage ownership groups](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/create-edit-ownership-group.md). When an assignment group is entered in the **Assignment group** field for a Content Request, it automatically appears in this field. |
| **Opened by** | The person who is requesting the creation of content.**Note:** When the state of the content request item is changed to **In review**, the **Opened by** person receives a notification. |
| **Due date** | The date the request for content should be completed. |
| **Priority** | The urgency associated with the content request. Your choices are:- 1- Critical - 2 - High - 3 - Moderate - 4 - Low - 5 - Planning |
| **State** | The status of the content request.- Open - Work in Progress: An assigned to person must also be entered to change the state to **Work in Progress**. - In Review - After the content request item is scheduled for publication, the content request item should be changed to **In Review**. Adding a Schedule Content record to the content request item is required to change the state to **In Review**. - When the State is changed to **In Review**, a notification is sent to the content requester and creates a to-do task for the requester. - A notification and a to-do task is also created for any approvers associated with the content request item. - The notification contains the details of the request and a link to a To-do that appears in the Employee Center for the Opened by person or the content requester. In the To-do, there are buttons to preview and review the content. - When the content requester reviews and approves the content, the **Ready to Publish** button appears on their **To-dos** page. - Ready to Publish - Selecting the **Ready to Publish** button indicates the content requester has approved of the content. - Adding a Schedule Content record to the content request item is required to change the state to **Ready to Publish**. - Published - After the content request has been set to **Ready to Publish**, the content manager can change the state to **Published**. - After the state is changed to **Published** all content items are scheduled for publication and become available to your employees when the availability start date from the **Schedule Content** is reached. - Adding a Schedule Content record to the content request item is required to change the state to **Published**. - Cancelled - Cancels the content request item. - All records associated to the content request item are retained and can still be reviewed after cancellation. |
| **Short description** | A short description of the content request. The text entered here appears by default in the short description for the content item. |
| **Description** | A longer description of the content request with more details. |
| **Additional comments \(Customer visible\)** | You can choose to make this information visible to the requester by checking the Additional comments \(Customer visible\) box. |