GitLab Storage

GitLab URL

Use https://gitlab.com unless you run your own GitLab server.

Click once, approve on GitLab, and PMS keeps the connection alive by itself — nothing to renew or paste later.

Application ID

Secret — blank keeps the saved one

Redirect URI — copy this into the GitLab application

Personal access token — leave blank to keep the saved one

Needs the api scope. Checked with GitLab before saving. Stored encrypted at rest. Never shown after save.

Max file size (MB)

Per image / video. 1024 MB = 1 GB. Max 2048.

Start a new part at (GB)

When a task backup reaches this size, a “Part 2” GitLab project is created. GitLab free limit is 10 GB per project.

—

Sign in to GitLab with the company account that owns the backups.
Open Avatar → Preferences → Applications (direct link) and click Add new application.
Name it PMS Media Backup, paste the Redirect URI shown on the left, keep Confidential ticked, tick the api scope only, and save.
Copy the Application ID and Secret into the fields on the left and click Save settings.
Click Connect GitLab, then Authorize on the GitLab page.

If the connection ever stops, super-admins get an alert — click Reconnect GitLab and Authorize again.

Sign in to GitLab with the company account (not a personal one), e.g. [email protected].
Open Avatar → Edit profile → Access tokens (direct link).
Click Add new token, name it PMS Media Backup.
Set an expiry date (max 1 year). PMS will remind you before it expires.
Tick the api scope only.
Click Create token, copy it (starts with glpat-) and paste it here.

Anyone with this token can read and delete every backup. Keep it private and replace it if it leaks.

Files are stored in private GitLab projects named backup-of-task-{id}, one per task that has backup enabled.