Welcome to DTC's Knowledge Base
This is the go-to place for all things DTC tech — from everyday IT basics 🖥️ to advanced specialtiesspecialties. like Dell SANs 💾. You’You'll find professional, reliable documentation and insights that power our teams and keep us on point.
⚠️ Can’Can't see some documents or getting “"page not found”found" errors?
That usually means you’you're not logged in.
👉in. Look up to the top right corner, click Login, then select Login with Azure 🔐. YouSee canSigning seeUp this& pageLogging hereIn for a more detailed guide including signing up. Signing Up and Logging Into BookStackguide.
🚀 Ready to get started? Click Here to exploreExplore the shelves!shelves
Want to contribute? Awesome! 🙌 Just sendSend a quick request to helpdesk@dtctoday.com to unlock your Editor privileges ✍️.privileges. Every DTC team member is encouraged to add and improve our shared knowledge.
Before youcreating divenew in, pleasecontent, check out the rest of this book for important Rules and Best Practices 📏✅ on creating Books & Pages. Let’sAnd keep this space sharp, useful, and professional for everyone.
Welcome aboard! 🚀 Let’s build something great together.
Knowledge Base Structure
This is how our KB is organized. Each shelf answers a different question. Ifif you're not sure where something goes,belongs, usesee thisthe asKnowledge yourBase guide.
PoliciesStructure & SOPs
Taxonomy "What'sGuide ourfor policy? What'show the officialKB process?"
Standard Operating Procedures— Step-by-step procedures for recurring workDTC Company Information Security Policy— Company-wide infosec policyDTC MSA Security Baseline— Minimum security standards for managed clientsAdmin Policies— Internal administrative policies (insurance, compliance, HR)Employee On-boarding & Off-boarding— People processesClient Onboarding & Offboarding— Client lifecycle processes
Infrastructure & Tooling
"How do I configure, operate, or troubleshoot this system?"
DTC's Pillars of Technology— Architectural standards and philosophy (what we believe and why)Network Operations— DNS, firewall rules, ACLs, troubleshooting, and network procedures (vendor-agnostic)Ubiquiti— UniFi/UDM-specific configuration, device adoption, firmware managementVoIP— VoIP operations, troubleshooting, and provider-specific docs (RingCentral, Freedom Voice, Weave, etc.)Backup & Disaster Recovery Operations— Veeam standards, deployment, daily ops, troubleshooting, DR runbooksServers— Server build standards, Hyper-V, migration proceduresNerdio Azure Virtual Desktop (AVD)— Cloud desktop infrastructureWorkstation Lifecycle: The Image Playbook— Imaging, deployment, and refresh proceduresOEM Drivers & Tools— Driver packages and vendor utilitiesOS Download Links— Operating system ISOs and media
Technical Knowledge
"How does this technology work?" (reference and learning material)
Dental Apps— Dentrix, Eaglesoft, Open Dental, PBS Endo, TDO, DTX Studio, and other dental softwareDental Hardware— Sensors, cameras, scanners, and dental-specific peripheralsProduction Apps— Non-dental applications in the DTC stackActive Directory— AD architecture, GPO, and domain managementKnown OEM Problems— Documented vendor bugs and workaroundsNetworking(reference) — Protocol fundamentals, standards references
Guides & Self-Help
"How do I do this specific task?"
How Tos— Step-by-step guides for Halo, Microsoft, 1Password, RingCentral, and other internal toolsBench Operations— Hardware prep, imaging, and bench workflowReceiving— Product receiving and inventory intake
Sales & Account Management
"Client-facing materials, pricing, and AM resources"
Sales & Account Management— Product catalog, competitive positioning, solution comparisons, AM technical guides
Vendors
"Vendor-specific contacts, agreements, and resources"
Vendor documentationis organizedby partner
Application Resources
"Application-specific deep dives and resources"
Application reference material (being reorganized — dental app docs moving to Technical Knowledge)
Public Documents
"Client-facing and publicly shareable documentation"
Emerging Technologies & Research
"What's coming next?"
Archives
"Retired or historical documentation"
Executive
"Restricted-access leadership documents"
Taxonomy Principles
When deciding where to put a new page, follow these rules:things.
ApplicationWelcome
data lives with the application.Port requirements, AV exclusions, firewall rules, and troubleshooting all go in the app's own book or chapter... not in a master reference doc.Vendor-specific books stay vendor-named.Techs search "Ubiquiti" not "Network Operations." Keep vendor books for vendor-specific UI procedures.Operations docs go in Infrastructure & Tooling.If it tells you how to configure, operate, or fix something, it belongs here.Standards and philosophy go in Pillars of Technology.If it explainswhatwe do andwhy(nothow), it goes in Pillars.SOPs go in Policies & SOPs.Official procedures with defined steps, owners, and compliance requirements.Link, don't duplicate.If information exists in one place, link to it from everywhere that needs it. Never copy the same content into multiple pages.
Last updated: 2026-03-06aboard.