Files and sharing

A project's Files tab holds its scan data, photos, drawings and anything else, in folders you name. Files go straight from the browser to storage and come back through short-lived links, never through the application itself. From here you share a folder or a file with the client, make a share link, link files to reports and welds, look at scan data, and keep plain tables. Owners, admins and technicians upload and arrange files; every staff member reads what the folder gives them.

Folders

• New folder makes a folder anywhere, at any depth. Add the standard folders adds the five fixed ones (procedures, standards, technique sheets, validation and other), named in each reader's language; new projects start with them.
• An asset has a folder of its own, opened from the asset's page as The asset's own folder: a folder named after its tag, with a folder per method inside (PAUT, TOFD, UT and so on, those your company offers, and any other method the asset's reports and requests use). Scans of a vessel go there.
• The dossiers a project builds land in a folder named Dossiers. See the handover dossier.

Uploading

Upload files or Choose files, or drop files on the page. Any kind of file goes, up to the size the page names.

• A large file goes up in parts, each signed by the application, so a lost connection costs one part, not the file. The page shows "Uploading …" with the percentage.
• Each file gets a SHA-256 Fingerprint once it is stored; a large one shows "Fingerprint being computed" for a while.
• Smaller files are scanned for viruses as the upload finishes, where scanning is on. An infected file is not kept; a file that could not be checked is refused for the moment, to be tried again in a few minutes.
• A file whose content is not what its name says is not kept.
• A file is refused once your storage is full. See the Storage section below.

An archived project keeps its files for download, and takes no new ones.

Renaming, moving and removing

On a file's or a folder's row:

• Rename: a file keeps its ending, which says what kind of file it is.
• Move to…: into another folder of the project, or The top of the project. Sharing follows folders, so moving into or out of a shared folder changes what the client sees.
• Remove deletes a file's bytes; the record of it stays in the activity log. A file linked to a draft report is unlinked first; the files of an issued report stay, because they are part of its record.
• Download, and Download all for everything in a folder, each file through its own short-lived link.

Who reads a project folder

Every project folder has a list of who reads it and who may also download, under Who of the company reads this folder:

• By default it follows the folder above. A folder with no list above it is read and downloaded by everyone on staff.
• Owners and document controllers press Change and choose A list of its own: everyone on staff, a role, named people, an office, those certified in a method at a level or above, with May download ticked where a copy may be taken. The same lists work in the document library.
• Someone who may read but not download sees the folder marked Read only and reads a file in the page, their name across every page, with no download button.

Owners and document controllers see everything. A client reaches a project's folder only through sharing, whatever the list says. See the document library for the same rules there.

Sharing with the client

Each folder and file is Visible to the client or Not visible to the client; a file inside a shared folder is Visible to the client through its folder.

• Share with the client on a folder makes it and everything in it visible in the portal; on a file, that file alone. Stop sharing takes it back.
• In the portal the client sees the shared folders and files of the project under Shared files, and downloads them through short-lived links; every download is recorded.
• Settings, Reports has Share a report's files with the client when it is issued: the scans and files linked to a report reach the portal with it. Off, you share by hand.

What is shared is seen by every client user of the project, including the end client's where a project has one. See the client portal.

Share links

A folder or a file can also go to someone without an account: Share link on its row makes a link on your portal address, with a password and an expiry if you choose, revoked at will, every opening recorded. See verification and share links.

Files on reports and welds

• On a report: the Linked files card of the editor links a file as scan data, scan plan, photo, sketch or other. Linked files are listed on the PDF and frozen at issue. See writing a report.
• On a weld or TML: the joint's page has Scans and files. A file whose name names the weld is linked by itself when it is uploaded to the asset's folders: V101_W12_PAUT.nde, or V101-W12-PAUT.nde, is W-12's scan, while W-12-A is never taken for W-12. The row says "Found by its name". Anything else is linked by hand with Link a file of the project, and Unlink takes a link off; the file stays. See the tracker.
• A file's row says how many reports it is linked to.

Scan data previews

Where previews are switched on, a .nde file (the open format of Evident's instruments) gets a Previews link once it is stored. A worker reads the file and leaves images: per scan group a C-scan, an S-scan drawn to scale or a linear scan, B-scan or TFM image, an A-scan through the highest amplitude, and a thumbnail. The page says what each image shows, with the axes in millimetres and microseconds; the images carry no text of their own, so they read in every language.

Look through the scan colours the data in the browser: a position along the scan, a beam or index position, the cross-section there, the A-scan, and a gain slider. The file itself stays the record; previews help to look at the data and are not the analysis. Make the previews again asks the worker once more, for instance after a failure the page explains.

Scan plans

A scan plan exported from NDT Insonify, a .json file among the project's files, fills the scan setup section of a report. On the report's Scan plan card choose the Plan and press Check the plan: a page shows each field as the report has it and as the plan has it, and what the plan says that this template cannot take. Nothing changes until you Apply the changes; the plan is then linked to the report and listed on it, and every value can still be changed in the editor.

Photos from your phone

From the project's files, or from a draft report, Photo from your phone shows a QR code. Point your phone's camera at it, or open the app on your phone and choose Camera: the request is waiting there. Take the picture and tap Send, as many as you need; each lands in the project's files, in the folder you were in, linked to the report where you asked from one. The phone must be signed in as you, in the same company, and only your phone answers your request, which runs out after a while. See offline and phone.

Sheets

The project's Sheets tab holds free-form tables for anything the tracker does not cover: a line list, a punch list, a schedule. Start a sheet, name it, and type into the grid; a block copied from a spreadsheet pastes into any cell and the sheet grows to take it. Changes are saved as you go, and a sheet saved elsewhere in the meantime refuses yours until you reload. Pick a cell to see what it held before, who changed it and when.

Sorting and filtering change only what you see; the sheet keeps its order for everyone. Export to Excel writes the sheet out. Show this sheet to the client in the portal makes it read-only there, with every change as it is saved. Archive puts a sheet away, read-only, until it is restored.

Storage

Everything stored counts against your company's storage: project files, the issued PDFs, and documents read by AI. The dashboard's Storage card shows what is used and your plan's limit. Uploads are refused once it is full: remove files, or ask for more storage. See billing and plans.