Global Knowledge Editors can publish existing articles, regardless of ownership, to the Technology Help website.
Table of Contents
- Best Practices for Publishing
- Publishing an Existing Article to the Technology Help Website
- Additional Resources
Best Practices for Publishing
- Global Knowledge Editors should ALWAYS communicate with the appropriate stakeholders (e.g., group owners) before publishing knowledge articles.
- Global Knowledge Editors should always follow the Checklist for Internal and Public-Facing Knowledge.
- It is best to only publish articles that your group owns, though you may be called on to review and publish articles on behalf of another group.
- Only articles with an Approved status can be published.
- It is good practice for Global Knowledge Editors to have someone else approve their articles.
- If you need to have an article published to the Technology Help website and are not a Global Knowledge Editor, submit an OIT-Service Lifecycle Request. A Global Knowledge Editor will review the article and communicate with you.
Publishing an Existing Article to the Technology Help Website
- Open the article's page in the TDX Knowledge Base.
- Review it for clarity and technical accuracy.
- Select Edit Article.
- Select the Settings tab.
- Make sure Category is set to the technology, service, or business process that the article addresses.
- Example: an article about the TDX Knowledge process would belong to the Knowledge Management category.
- Make sure the Status is set to Approved.
- Check the Published to KB checkbox.
- Set the Next Review Date to one year from the current day.
- Example: if you are approving the article on October 5th, 2025, set the Next Review Date to October 5th, 2026.
- Make sure the Owner is set to the appropriate group. Remove yourself as Owner if necessary.
- Add any Knowledge Internal Notes if necessary.
- For Restrict Access: Require login with a UMN Internet ID to view this content?, refer to Restrict Access to Content and Understanding the Restrict Access and Publishing Settings to determine if the article needs to be restricted.
- Example: if an article only contains basic information that can be found about the technology on the web, restricted access is probably not needed.
- Example: if an article contains content on how to use, locate, access, or secure a technology specifically within our University environment, restricted access is needed.
- Make sure Category is set to the technology, service, or business process that the article addresses.
- Click Save.
- Select the article title from the breadcrumb links to return to view mode.

- The article's History (under the article itself) should update to show that you have Changed Published from "No" to "Yes".

- The article's Details section should indicate its new Status as Published.
