These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Knowledge Base Builder
- Data model
The tables behind Knowledge Base Builder
Knowledge Base Builder ships with 12 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 12
- Features
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Guidance
Knowledge articles stores the article body, category, owner, status and publication date. Article feedback references the article and stores reader response.
Service context
Services and Assets identify the operating service and affected equipment.
Case work
Incidents and incident updates keep an issue and its dated history. Problems capture root cause; service requests capture requested service work.
Change and events
Changes stores the planned service window and outcome. Integration receipts records provider event receipts and results.
Identity
People identifies record owners, requesters, assignees and update authors. Users carries account details.
Every table, by feature
- Article workspace3
- Publication review4
- Reader feedback3
- Service context5
- Incident guidance5
- Problem and request work5
- Shared and settings2
- Knowledge articles
Knowledge Articles for Knowledge Base Builder
Linked to People - Article feedback
Article Feedback for Knowledge Base Builder
Linked to Knowledge articles - People
People for Knowledge Base Builder
Linked to Users
- Knowledge articles
Knowledge Articles for Knowledge Base Builder
Linked to People - People
People for Knowledge Base Builder
Linked to Users - Incidents
Incidents for Knowledge Base Builder
Linked to Services, Assets, People - Incident updates
Incident Updates for Knowledge Base Builder
Linked to Incidents, People
- Article feedback
Article Feedback for Knowledge Base Builder
Linked to Knowledge articles - Knowledge articles
Knowledge Articles for Knowledge Base Builder
Linked to People - Incident updates
Incident Updates for Knowledge Base Builder
Linked to Incidents, People
- Services
Services for Knowledge Base Builder
Linked to People - Assets
Assets for Knowledge Base Builder
Linked to Services - Incidents
Incidents for Knowledge Base Builder
Linked to Services, Assets, People - Changes
Changes for Knowledge Base Builder
Linked to Services - People
People for Knowledge Base Builder
Linked to Users
- Incidents
Incidents for Knowledge Base Builder
Linked to Services, Assets, People - Incident updates
Incident Updates for Knowledge Base Builder
Linked to Incidents, People - Services
Services for Knowledge Base Builder
Linked to People - Assets
Assets for Knowledge Base Builder
Linked to Services - Knowledge articles
Knowledge Articles for Knowledge Base Builder
Linked to People
- Problems
Problems for Knowledge Base Builder
Linked to Services, People - Service requests
Service Requests for Knowledge Base Builder
Linked to People, Services - Services
Services for Knowledge Base Builder
Linked to People - Knowledge articles
Knowledge Articles for Knowledge Base Builder
Linked to People - People
People for Knowledge Base Builder
Linked to Users
Keys and references
Article feedback.Article points to knowledge articles; knowledge articles.Owner points to People. Incidents links to Services, Assets and People, while incident updates points to Incidents and its author. Problems, service requests and Changes point to Services. People.User points to Users. Keep these references intact when moving data so a comment, update or finding stays with its intended record.
Migration order
- Bring in Users and People, then verify active people and owner assignments.
- Bring in Services and their owners, followed by Assets linked to the appropriate service.
- Bring in Incidents, Problems, service requests and Changes with their service and person references.
- Bring in incident updates against the intended incidents and authors.
- Bring in knowledge articles with owners, then article feedback against the intended article.
- Bring in integration receipts if provider event history is part of the starting scope.
Set up Knowledge Base Builder your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.