How are others handling internal documentation?

As I build out my client-side documentation, I’m starting to think my initial approach for internal docs might have been a mistake.

I originally used the global KB for internal docs, but now I realize that having an internal company might offer better organization for storing additional things like passwords, vendor information, employee contacts, other internal resources; in addition to my internal KB docs.

A few questions for those who’ve tackled this:

  • Does it make sense to create a separate internal company for this?

  • Do you use multiple internal companies (e.g., one per division), or do you manage this through permissions?

  • How are others structuring their internal documentation?

  • If you do separate internal documentation, what do you still keep in the global KB?

Would love to hear how others are approaching this!

3
1 reply