Skip to main content
You need company custodian management permission and your custodian’s advisor codes. Connections belong to your company. You can set up the connection first, then choose which books receive each code. This permission lets you assign codes to company books without granting you access to those books’ client records.

​
Connect a custodian

1

Open custodian settings

Go to Settings → Custodian.
2

Choose a custodian

Choose your custodian’s tile to open its setup dialog. It walks you through one step at a time and saves your progress, so you can close it and come back.
3

Add your codes

Enter your codes when the dialog asks for them. Fidelity asks for rep or branch codes and provides a company header for its Integration Xchange release process. Altruist shows your rep codes after you enable the Slant integration in Altruist, so the dialog walks you through that first. Adding a code does not assign it to any book.
4

Choose which books receive the data

After codes are added, the dialog lists your books for each code. Use Books & codes under Manage connection to change the assignment for any code later. Books receive access only through these assignments.
5

Complete the release requirements

Follow the instructions on each step. Exact values you need to enter at the custodian have a copy button, and portal links open in a new tab. When you finish a submission or signature, enter the date and Slant records it. You can report an earlier date or correct a previously reported date from the same step.
6

Return when you need an update

Once the remaining work belongs to the custodian or to Slant, the dialog tells you what happens next and you can close it. Slant watches for matching deliveries and processing results in the background and emails you when a step comes back to you and when the connection is live.
Each company has one connection per custodian. Choosing a custodian tile again reopens it. A reported submission records what you told Slant. It does not establish custodian approval or data receipt. Some requirements need your firm administrator, the custodian, or Slant staff. The dialog shows who the connection is waiting on. When usable data starts flowing for a code, Slant automatically completes its earlier submission, signature, and feed setup steps. You do not need to go back and check them off. Reporting a completed signature also completes the preceding submission step. Ownership and feed matching checks still apply; these automatic updates record setup progress without inventing signature records.

​
Understand your connection status

Each code has separate ownership, delivery, processing, and data freshness results. Received means Slant observed matching delivery; verified ownership alone does not prove a feed is arriving. Accounts, balances, positions, transactions, contract details, and carrier values can arrive separately. Content dates determine freshness. A historical file processed today does not make current data fresh. Delivery windows account for the provider’s calendar and Eastern time. If a carrier’s schedule has not been confirmed, its freshness remains unknown. Today’s delivery window may still be open. Company managers see observed accounts and contracts for the whole connection. Other users see only data shared with books they can access. Counts do not promise that every expected account has arrived. Slant checks the data categories required for your custodian automatically. Every requested code must meet those requirements before setup completes; assigning books is separate. After assigning a code, open the book’s custodian accounts to review them and link remaining accounts to clients. Linking gaps are shown separately from delivery and processing.

​
Save FAN Mail logins

DST FAN Mail has no codes to enter. The dialog walks you through getting a FAN Mail login, then asks for each FAN Mail ID, its password, and the book that should receive its accounts; select Save login, and Add another login for firms with one login per advisor. Passwords are encrypted and stored outside the rest of your setup. Reopen the connection and choose FAN Mail logins under Manage connection when a password changes or the connection reports that DST rejected a login. Slant registers each fund company or carrier as it starts delivering. Contract details can arrive before carrier values; some carriers supply values only at month end. See the DST FAN Mail release guide.

​
Maintain a connection

Open a connection from Settings → Custodian to reach Manage connection: add codes, change which books receive each code, remove a code, check data status, or start setup over. Completing setup does not prevent later health degradation. Remove from connection removes a code from that connection’s requirements. Book access remains controlled through Books & codes. Removing a book assignment revokes the access that depended on it; removing the claim revokes its remaining assignments while retaining intake history. Accounts available through another claim remain available. Slant monitors your connection automatically.
Start over rechecks the setup from the beginning while preserving codes, book assignments, and past history.