Documentation Audit Trail

@Ilan B - FYI 

Thanks for sharing your idea @banthonisz! Great to hear that you’re building your product docs on inSided. I have some questions regarding your idea:

As such, we need to conduct regular audits on the content, in case a screen changes. It would be great if there was a user facing audit log/version control that showed:

• Date created
• Last date updated
• Next update date

Just to make sure, do you mean having the information above in the destination, maybe on a topic page?

And why is ‘Next update date’ important information for end users? 

This could then create a queue in the Control environment saying “Hey there are 30 articles in need of audit, 2 are overdue”. We currently have to do this using external tools like Airtable and would love to bring it into Insided.

Are you building this product documentation in the knowledge base now?

I’d love to hear more about your current workflow in creating this queue, for example:

1. How do you set due for content?
2. Does all content share the same ‘valid period’? 
3. Who is in charge of updating the content?

Some screenshots of your current walkaround would be helpful for us to understand your needs. :)

Hello @banthonisz. Thank you for posting this idea. We have made the decision to park it for now because it didn’t get a lot of votes and replies.