Gitbook Guidelines
Creating and Updating
a) Format: Language - English Current software version - 3.1.1 Media - Electronic b) Review: Change - The person that edits the gitbook can request for review. This happens when you edit the page and click the dropdown submit for review. In the change requests tab, you can find the reviews. And the EA manager should approve after a review.
Control of documentation
a)Use: Employee training and technical information - Developer chapter Compliance with ISO 27001 and EA processes information - Compliance chapter b) Information protection: Confidentiality - Personal information c) Access: Access control - Visitors will be invited with a link. Editors can be everyone from Advantech that are invited from the admin.
d) Storage and Preservation: Library: Enterprise Applications Backup: When you are editing the gitbook, you can archive the change. Again, you can go to the change requests in the previous point. And there you can find the archived version of the gitbook. e) Control of changes: Change history: Gitbook has a history of tracking changes. The EA manager will give access to the person that is going to edit the information. A good practice is to describe briefly the change because it is saved by default without explanation. f) Retention and disposition: Retention: The editor can roll back to the old version of the gitbook by clicking the three dots on the actual change. This can happen in the change history.
Disposition: The editor can delete the gitbook space by clicking the triple dot menu on the top right corner and he can retrieve the version in 7 days. They will be permanently deleted after this time.
Last updated
