Filing to your Google Drive
Connect a Google account and Vylan copies approved documents into a folder structure you design. It is the one place your documents leave Vylan.
Most firms already keep client files somewhere — a Drive everyone knows their way around. Filing puts approved documents there automatically, named and foldered the way you would have done it by hand.
Connecting
Open your filing settings and Connect under Google Drive. Once it is on, the card shows Connected as {email} and Open the Vylan folder in Drive takes you straight there.
Vylan creates and works inside one folder: Vylan files into a “Vylan” folder it creates in your chosen storage. You can move or rename that folder; Vylan keeps filing into it. It does not look at or reorganise anything else in your Drive.
Vylan stores your data in Canada. Documents you file to a connected storage provider leave Vylan and live wherever that provider hosts them. Worth knowing before you switch it on, and worth being able to answer when a client asks.
Deciding the shape
Under Folders & naming you build a Folder structure and a File name from tokens — the client, the year, the document type. Separate folder levels with /. Click a token below to insert it.
The Preview shows the path a real document would take, including the fallback when something is missing: If no year can be determined: {path}. Read it before saving — a template that looked obvious while you typed it can put ten thousand files somewhere odd.
Changing the structure or the naming affects documents filed afterwards. It does not go back and reorganise what is already in Drive, so redesigning it a month in leaves you with two shapes.
What gets filed, and when
Approved documents. Filing runs on its own after approval rather than the instant you click, so give it a few minutes before concluding something is wrong.
There is no filing log or report. To check something arrived, open the Vylan folder in Drive and look — that is the honest answer rather than a screen that would only tell you what Drive already knows.
Renaming or moving a document inside Vylan afterwards does not follow through to the copy already in Drive. The two stop matching from that point, which is usually fine and occasionally surprising.