Producers, crew, partners, and anyone connecting a camera
File Transfer
SFTP and FTPS for large files and camera uploads — a separate login from the rest of the platform.
File Transfer is a managed file-transfer server at sftp.artgrp.au, for two things email isn't built for: sending or receiving files too big or too many for an inbox, and letting an on-site camera upload its footage automatically.
A different login to everything else
Unlike every other tool on this platform, File Transfer doesn't use Google or the email-and-password sign-in described in Getting started — there's no login.artgrp.au involved at all. Instead, you connect with a dedicated username and password (or an SSH key), in a file-transfer client rather than a web browser, using one of the two protocols below.
Sending or receiving files (SFTP)
If you're a partner, supplier, or crew member moving files with us, connect with an SFTP client — FileZilla is a common free one, or the sftp command on a Mac or Linux machine — to:
- Host:
sftp.artgrp.au· Port:22· Protocol: SFTP (not plain FTP)
You'll land in your own folder, separate from everyone else's.
Camera uploads (FTPS)
If you're setting up an IP camera (Reolink is what we use) to upload footage automatically, its FTP settings need:
- FTP server:
sftp.artgrp.au(host only — noftp://, no port on the end) - Port:
21· Mode: Passive - "FTPs Only": turned on — this is explicit TLS, and it's what actually secures the upload. A camera without it turned on will look like it's connecting but the file won't land.
- Username and password: the camera's own account, not a personal one
Getting access
Ask your Artefact contact for an SFTP or FTPS account. It's issued to you directly rather than through the admin dashboard's app-access grants — having access to other tools on the platform doesn't give you one of these, and vice versa.
Where to go when stuck
This one isn't self-service the way the rest of the platform is — if a connection won't authenticate or a camera stops uploading, contact Artefact directly rather than trying to fix it from your end.
Related
- Getting started — how the rest of the platform's sign-in works, for context on why this one is different