Date: Fri, 29 Mar 2024 15:22:52 +1000 (AEST) Message-ID: <1312954036.67.1711689772567@BCIWEB27.BCI.local> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_66_331519109.1711689772566" ------=_Part_66_331519109.1711689772566 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The BrigHub documents overall process to follow is as listed below.
Documents to be published into BrigHUB are worked on via an appropriate = Team as the draft storage. While a document is not ready to be released it = should stay in an appropriate Team and edited by members of the Team. Only = a single copy of an active draft document should be worked on at the one ti= me. Teams stores version history which can be accessed at any time, previou= s versions can be accessed using the follow instructions: Checking a Fil= e's Version History in Teams. Once a draft is complete ap= proval from the document owner needs to be given before uploading into Brig= HUB. Document owner would generally be the owner of the Team however this w= ill not always be the case.
BrigHUB's Document Repository consists of eight top level folders, they = are as follows:
Use two decision flow charts below to help distinguish which top level f=
older the document should be uploaded to.
Follow the instructions linked below to correctly use the BrigHub Docume= nt Repository