> ## Documentation Index > Fetch the complete documentation index at: https://docs.royaltyport.com/llms.txt > Use this file to discover all available pages before exploring further. # Portals > Connect the distributor, publisher, and collecting-society portals your organization uses so statements sync into Royaltyport automatically ## What is Portals? **Portals** is the organization-level home for the external systems your royalties come from — distributors, publishers, collecting societies, and label back-ends. Connect a portal once, and Royaltyport signs in on your behalf and pulls new statements as they're published, so you no longer download files by hand and upload them project by project. You'll find **Portals** in the organization header menu, alongside Integrations. Each connection stores your login securely, remembers which accounts you have on that portal, and keeps a full history of every sync it runs. ## What you can connect Portals covers the systems music-rights teams collect from, including major distributors and labels (Universal, Warner, Sony Music Publishing, BMG, Concord, Kobalt, peermusic, FUGA), collecting societies (Buma/Stemra), and royalty back-ends such as Curve. Connections fall into three kinds: | Connection type | How it works | | ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Login portals** | You provide the username and password you'd use on the portal's own website. Royaltyport signs in and downloads your statements on a schedule. | | **Email intake** | Some sources deliver statements by email rather than a login. You forward those emails to a Royaltyport intake address, and they're checked automatically every day. | | **File sync** | Sources that expose their files through Microsoft SharePoint / Graph are connected by authorizing access and choosing which folders to sync. | Connecting starts from a searchable **directory** of the sources Royaltyport knows about. Sources with a built-in integration connect through the guided flow below. A source that's listed but **not yet integrated** can still be set up now: add your login and Royaltyport builds support for it and connects it for you — no need to send credentials again later. If a source isn't in the directory at all, **request** it and the Royaltyport team adds it. ## Connecting a portal Adding a connection is a short guided flow: Search the directory and pick your source. Enter the login you use on that portal. Your credentials are encrypted and used only to sign in and sync — they're never shown back to you. If the portal requires two-factor authentication, tell Royaltyport how it's delivered (see below) so scheduled syncs can complete unattended. Connecting authorizes Royaltyport to sign in on your behalf and sync your statements. Some portals then ask you to re-authenticate once from the connection page to finish. ### Two-factor authentication Many portals protect logins with a second factor. Royaltyport supports three arrangements so it can sign in during a scheduled sync when nobody is watching: * **None** — the portal has no second factor. * **Authenticator app (TOTP)** — provide the portal's setup key. You can paste the key, upload the QR-code image the portal shows, or scan it with your camera. Royaltyport generates the rotating code itself at sync time; the codes are never stored. * **Email code** — the portal emails a one-time code at each sign-in. Forward those code emails to the Royaltyport intake address shown for your organization, and the code is read and entered for you. The address is also shown on the connection page, so you can set forwarding up later if codes stop arriving. ## What a connected portal does Once connected, a portal keeps your statements flowing into the right projects: * **Automatic syncs** run on a schedule you set — weekly, monthly, or quarterly, at a time of day you choose. Email-intake sources are checked **every day** and need no schedule of their own. * **Sync now** downloads on demand, optionally narrowed to a specific statement period. * **Per-account project assignment** — a single login often covers several accounts or catalogs. Choose which accounts to sync (accounts start off, so you pull only the ones you care about), then assign each to one or more projects, and statements from that account upload straight into those projects. You can leave auto-upload on so new statements land in your projects with no extra step. Adding, changing, or removing a connection — and triggering a sync — requires organization admin access. Any organization member can view the portals list and a connection's activity. ## The connection page Opening a connection shows everything about that source in one place: * **Sync status** — when it last synced successfully, how long the last run took, when the next run is due, and how many new files arrived. * **Health** — whether the connection is working, needs you to re-authenticate, or is having trouble. When a portal needs a fresh sign-in, a **Re-authenticate** action appears here. * **Connection details** — the login account, the two-factor method in use, and when it was connected. **Update login** lets you change the stored username, password, or two-factor method — including correcting the two-factor method in place, without disconnecting and re-adding the connection. * **Accounts and projects** — the accounts found under your login and which projects each one feeds. * **Recent runs** — a history of every sync, with the files and volume downloaded and, for any failures, the reason they failed. Expand a run's failures to **retry** them — a single failing group or all of a connection's unresolved failures at once — and Royaltyport re-fetches only what didn't come through, skipping files already downloaded. Once a later sync recovers a failure, the run marks it recovered rather than leaving it flagged. (See [Working with lists](/working-with-lists) for how to search and page through history.) * **Download** — export the synced files as a ZIP, choosing everything, only what's new since the last sync, or a date range. Downloading is a local export and doesn't change what syncs from the portal. If a source stops working across the organization, failed syncs are collected as **incidents** on the Portals home so you can spot a broken connection quickly. ## Disconnecting Removing a connection stops all future syncs. You can choose whether to also delete the files and history Royaltyport has already stored for it. ## Related Documentation Where synced statements land, and how they're extracted and reviewed. Add statements manually when a source isn't connected as a portal. Connect a Curve royalty back-end at the project level. How search, sort, filter, and paging work across Royaltyport.