Requirements
- Desktop app required — Adding accounts only works in the AgencyKey desktop application, not the web version
- Creator account — The OnlyFans account must be a creator account, not a fan account
- Permission — Your role needs permission to add creator accounts
Step-by-step process
1. Open the add dialog
Go to the Accounts page and click the Add Creator button.2. Choose the login proxy
The connection flow uses a proxy:- Use the AgencyKey-managed option for a temporary login proxy; it returns to the managed pool after connection.
- If your role allows it, choose one of the agency’s custom proxies.
- Enable Auto-link proxy when you want the chosen custom proxy to remain assigned to the creator after connection.
3. Log in to OnlyFans
Click Connect to OnlyFans. A login window opens. Complete the sign-in and any OnlyFans verification in that window. Enter credentials only in the OnlyFans login window, and do not ask employees to share the creator’s password or verification codes in chat.4. Done
After successful login:- The account appears in your accounts list
- Status shows as Connected
- You’re automatically assigned as a team member
Trial
A newly connected creator receives up to 30 active trial days, with a maximum of 90 calendar days from connection. See Billing for what counts as an active day.Security notes
- OnlyFans passwords are never stored
- After login, only the session credentials required to operate the CRM are stored on protected AgencyKey servers, encrypted at rest
- The standard team workflow does not require sharing session credentials with employees
- Each connected account uses an isolated session
- Temporary data from the login window is cleared after the process completes
Common issues
”Desktop app required”
You’re using the web version. Download the desktop app to add accounts.”This account is not a creator”
You logged in with a fan account. Only creator accounts can be added.”Proxy connection failed”
The selected proxy isn’t working. Try:- Choose a different proxy
- Check whether the custom proxy is configured correctly
- Try the AgencyKey-managed login proxy if it is available