RPLConnection
Why connect Google Drive to an RPL portfolio
Updated 9 November 2026 · Australia
The work is already in Drive. It is sorted by year, by client, or by whoever emailed it to you. A portfolio cannot read that folder until the connection is on. When it is, you stop downloading a photo just to upload it again.
What is already sitting in Drive
A photo of an install before the wall was closed. A PDF test sheet. A letter from a builder. People keep these because the job required them, not because they were building a qualification file. Years of that material is a recognition of prior learning folder that has never been asked which unit it covers.
The drag is the transfer. Opening Drive, finding the job, saving it, then typing the site and the date into another product is where people stop. The second job feels like admin. The fiftieth job does not get done.
What the connection is for
Connect once. Finished files that are photos or letters can come across with the name of the file and, where you have put it in the note, the site and the date. Each new file you add in Drive after that can follow the same path. You still confirm the work is yours. The portfolio still only suggests the unit.
That is the retention. The portfolio stays useful because it does not ask you to rebuild a library you already kept. The advantage is the years you do not retype, not a new place to store the same photo.
What it will not do
A Drive folder is not a unit, and it is not a qualification. Sign-in to Google Drive is not switched on yet. Until it is, the row in Add connection says Soon. You can still file one job by hand from Bring a job, including a link to the file.
Do not connect a drive that holds someone else’s identity documents, medical papers, or a whole company’s private quotes. Bring the job, not the entire account.
Soon means the sign-in is not on. You can still file one finished job, and you still confirm the links.
Bring a job