Built in response to customer feedback surrounding the native SharePoint sharing mechanism, Atvero CheckPoint is an information exchange portal that records a complete transmittal transaction history whilst keeping the data in your hands.

The native SharePoint sharing mechanism

and its challenges for architects and engineers

Limitated with audit trails

Finding a comprehensive and complete audit history of transmittals can be a challenge for architects and engineers who use SharePoint to work on projects and share information. The audit trail available within the SharePoint sharing link is limited to only showing which users have opened and viewed documents but now who has downloaded them.

Difficult external collaboration

SharePoint security is generally aimed at collaboration, and therefore has limitations when setting distinct permissions on different items within a project. Some SharePoint users are not averse to inviting external people to a project and are concerned that too much information could be visible to those external people who were not close collaborators.

Atvero CheckPoint

A highly secure and auditable information exchange portal

Securely share with external parties

Atvero CheckPoint was built to deliver a safe and secure method of sending information when working with external parties and can provide a complete transmittal transaction history whilst keeping the data in your hands in your Azure tenancy. Internal users can manage and monitor the access of CheckPoint, controlling the expiry of the shared CheckPoint links and checking detailed user activity such as when links where accessed and which files were downloaded.

External users can gain access to the information shared with them through CheckPoint using a branded web portal, in which they will need to input an authentication code as well as proving their identity as verified recipients using email addresses.

Send files with flexibility

Atvero customers who have CheckPoint functionality can also share information that does not need to be recorded within official transmittals. Sharing via CheckPoint maintains a record of the details of senders, recipients and what was sent, without polluting the official issued register. This functionality can be turned on and off through out the life cycle of a project to ensure that users are following the correct quality control pathways.

Our vision for the future

At present, CheckPoint is primarily focussed on the tracking of outbound information from Atvero. Our roadmap in the future, will look to expand CheckPoint to support receiving of inbound transmittal information. In this way, external parties could be invited to upload via a similar web link, taking them to the branded portal, where they can drag and drop files and folders into the portal for upload into CheckPoint. Internal members of the linked Atvero project will then be able to approve or reject the pending files.