---
title: Society connections
description: "Save your login for a society's file server, test it, and check for the society's responses from the Workspace."
keywords: [society connections, connection, file server, SFTP, ICE, The MLC, login, saved login, test connection, check for responses, acknowledgements]
---

A society connection is your login for a society's file server, where CWR files are delivered and the society's responses come back. A connection is optional. Without one, you download each file and upload it to the society yourself.

Society connections are switched on for some workspaces only. If there is no **Society connections** card at the bottom of **Settings**, they are not switched on for yours, and nothing on this page applies.

## What you can connect to

- **PRS for Music / MCPS via ICE** is ICE's file server. One connection serves both PRS for Music and MCPS.
- **The MLC** is The MLC's file server.

## Before you start

- You need the login the society gave your organisation for its file server. Adding a connection does not apply to the society for one.
- Add your publisher details in **Settings** first, because a new connection is filled in from them. See [Publisher details](/docs/workspace/settings/publisher-details).
- Only an owner or editor can add, change or test a connection. Anyone else sees the page with a note saying so.

## Open the page

1. Open **Settings**.
2. The last card, **Society connections**, lists the connections saved. Press **Open society connections**.

The page opens with the **Settings** tab still selected. **Back to Settings** takes you back.

## Add a connection

1. Press **Add a connection** and choose the server.
2. Check the publisher fields: **Publisher name (as registered)**, **Publisher IPI number** and **Short code for your filenames**. They are filled in from your publisher details, and the form says so. Change them only if this login sends files for a different publisher.
3. For The MLC, choose the **Receiver file code** and the **Issued connection protocol** exactly as The MLC gave them to you.
4. If you already have a login to the same server, give this one a **Name for this login**, for example the publisher it is for. With one login to a server, the form does not ask.
5. Press **Save connection details**. Saving them sends nothing.
6. The connection's tile then asks for the login. Type the login the society gave you, and tick the box saying it is your organisation's own login.
7. Press **Test and save login**. TrackForge signs in with it, and the tile says **Login tested and saved.**

Where saving a login is not available, the tile says **Saving a login is not available at the moment, so the login is asked for each time.** The buttons then ask for the login every time, and a login typed there is used once and is not kept.

## What a connection's tile shows

Each connection is a tile named after its society. When you have two logins to the same server, each tile also shows the name you gave it.

Beside the name, a plug icon shows whether it is connected: the two plugs are joined when the connection works, and apart when it does not. The badge at the top right gives its one status in words:

- **Connected**: the saved login last signed in and read your folders.
- **Can’t connect**: the last test failed. The line on the tile gives the society server's reason.
- **Login needed**: no login is saved yet.
- **Not tested**: a login cannot be saved here, and none has been tried yet.

Under the name, a line says which publisher the connection sends as, with its short code, for example "Sends as Example Music Publishing Ltd (EXM)". **Edit details** opens the connection's details again and shows the server it uses.

With a login saved, the tile says **Login saved** and when. **Replace** asks for a new login. **Remove** deletes the saved one, after you confirm with **Remove login**. Responses already kept stay.

## Test connection and Check for responses

- **Test connection** signs in and counts the files in your folders on the society's server. The answer is one line on the tile.
- **Check for responses** keeps a copy of the society's acknowledgements for files sent under your sender code. Those for a file sent from the Workspace update its works. It is offered where the society's server allows it.

Neither changes, moves or deletes anything on the society's server, and neither sends a registration. To read what a society said, see [Understand a response](/docs/workspace/files/understand-a-response).

Once a login is saved, the tile may offer **Check for responses automatically, about twice a day**. With that on, **Email updates for new responses or required action** sends you an email when there is something new.

## Sending files

Where the page shows **Sending is not switched on**, TrackForge does not send files for your workspace yet. You download each file, upload it yourself and record that you sent it. See [Download, send and record](/docs/workspace/files/send).

On **Settings**, each society you register with has a line saying how its files travel: you upload them yourself, you upload them and check for responses through your connection, or they go through your connection. Joined plugs mark a line that goes through a connection, and plugs apart mark one that does not.

## How your login is kept

The panel **How we protect your login** on the page says the same:

- Your login is kept in Google Cloud Secret Manager, in Google's London region, not in TrackForge's database.
- Google encrypts it where it is stored, and it travels only over encrypted connections.
- TrackForge's server reads it only to do what the buttons do. Google logs every read. It is never shown again, and never shared.
- Removing it deletes it from Google, rather than only taking it out of use.

## If something goes wrong

- **There is no **Society connections** card in Settings.** Society connections are not switched on for this workspace.
- ****Save connection details** stays switched off.** A field is missing or not valid. The IPI number is 9 to 11 digits, and the short code is 2 or 3 letters or digits. A second login to the same server also needs a name.
- **The tile says **Can’t connect**.** Read the reason on the tile. Check the details with **Edit details**, then **Replace** the login if it has changed.
- **The tile says **The connection details changed, so enter the login again.**** The details were edited after the login was saved. Enter the login again.
- **The tile says **The saved login has not been removed yet.**** Press **Retry removing the login**.
- **There are no buttons.** Only an owner or editor can add, change or test a connection.

## Related

- [Publisher details](/docs/workspace/settings/publisher-details)
- [Societies](/docs/workspace/settings/societies)
- [Download, send and record](/docs/workspace/files/send)
- [Understand a response](/docs/workspace/files/understand-a-response)
