A Fanvue manager account is a separate login, registered through Fanvue's manager sign-up with an email address that has never been used on Fanvue, which a creator invites from Settings > Management so an agency or manager can switch between the creator profiles it handles. Fanvue's help article on manager accounts says a manager cannot access payouts, change the creator's email or password, or delete the account, and the team members a manager invites can work in the feed, messages and a restricted vault but cannot publish.
That makes the manager account the sanctioned alternative to handing over a password, which Fanvue's General Terms prohibit. This guide covers the set-up, what each role can reach, the gaps in Fanvue's own documentation and the steps for removing someone. The wider principles of giving any agency access, such as who keeps recovery and how handovers are recorded, are covered in our agency account access checklist, and they apply on Fanvue just as they do on OnlyFans.
How the invitation chain works
On Fanvue the creator grants access; the help article gives a manager no way to add a creator on their own. It describes this sequence:
- The agency or manager registers through Fanvue's manager sign-up page, using an email address not previously registered on Fanvue. This becomes the agency's primary account, and its dashboard stays empty until a creator connects.
- The creator opens Settings > Management, enters the email the manager registered with and clicks Send Invite.
- The manager receives a confirmation email and must be logged in as the manager account when clicking the link; otherwise, the article warns, an error appears.
- The creator invitation and confirmation repeat for every creator the manager handles.
- Team members, usually chatters, register through the ordinary Fanvue sign-up rather than the manager one.
- Signed in as the manager, the agency invites each team member from its team members settings using the email that person registered with, and the team member accepts while logged in to their own account.
Every step leaves an email in someone's inbox. Keep those messages, because they are the simplest record of who was invited, by whom and on what date, and that record is what you will want if access is ever disputed.
Access matrix: who can do what
Fanvue spreads access across several roles and documents them in different places. The matrix below combines the manager article, the payout options article, the account settings article and the API Access & Usage Policy. Where Fanvue does not document a step, the matrix says so instead of guessing.
| Role | What it can reach | What it cannot do | How access ends |
|---|---|---|---|
| Creator (owner) | Everything, including payout methods, two-factor authentication and account deletion | Hand the login to anyone else under the General Terms | The owner keeps control throughout |
| Manager account | Switching between every creator profile that invited it, and inviting team members | Payouts, the creator's email or password, deleting the account, or enabling two-factor authentication on its own login | Removal is not described in the manager article; start in Settings > Management and get written confirmation from support |
| Team member (chatter) | Main feed, messages and vault for every creator under that manager account | Publishing content, or deleting and posting from the vault | Also undocumented; the manager removes them from the team and support confirms |
| Connected app | Only the scopes the creator approved, such as reading chats or creating posts | Anything outside the approved scopes | Settings > Account > Third Party Apps Consent > Revoke |
| Agency through the API | Chats, mass messages, media uploads, posts, tracking links and analytics for managed creators | Operations the API policy does not list, such as payout changes | Revoke the agency's app consent and remove the manager connection |
| Your linked account | A separate creator profile on your verified identity, with its own login, earnings and payouts | Isolate warnings, which count across all your linked accounts | Not covered by the linked accounts article; ask support |
Two rows deserve a second look. The manager article says team members cannot publish, yet the API policy lists agency operations that include creating posts and sending mass messages for managed creators, so an agency working through the API may be able to do more than its chatters can in the web app. And the manager login cannot use two-factor authentication at all, which matters because one password opens every creator profile connected to it.
Gaps and contradictions in Fanvue's own documents
Fanvue's help pages and its terms do not line up perfectly. Where they conflict, follow the binding terms and get anything else confirmed in writing.
- Shared manager logins. The manager article's FAQ says only one manager account can be assigned to each creator and suggests sharing the manager account's login details as a temporary workaround for agencies that need several administrators. The account section of the General Terms forbids sharing your password or giving others access to your account. Until the multiple-administrator feature Fanvue says it is building arrives, ask support in writing before anyone shares a manager login.
- No two-factor protection for managers. The account settings article notes that management and agency accounts cannot enable two-factor authentication. The Australian Cyber Security Centre's multi-factor authentication guidance calls MFA one of the most effective protections against unauthorised access, so a login that cannot use it needs a long, unique password kept in a password manager and known to as few people as possible.
- No agency rulebook yet. Fanvue's policy hub for agency users still reads “Coming Soon”, so no agency-specific terms have been published, while the General Terms make the account holder solely responsible for all activity under their account.
- Removal is undocumented. The manager article explains how to connect a manager and add chatters but not how to disconnect either one, so check the Management settings yourself and ask support to confirm the change.
- Access is all-or-nothing inside a manager account. Team members see every creator under the manager account they join. The only documented way to restrict a chatter to certain creators is a separate manager account for those creators, and each creator can be assigned to only one manager account.
Linked accounts are a different feature
Linked accounts let one verified creator run more than one profile; they do not give anyone else access. Fanvue's linked accounts article says you can create one from Settings > Account once your KYC is approved, you have completed at least one successful withdrawal and none of your accounts has an active warning or compliance issue.
The same linked accounts article limits each verified identity to 2 accounts for a human creator and 15 for an AI creator, counting any that support linked earlier. Each account has its own login, earnings and payout set-up and stays private from fans, but warnings and strikes are tracked across all of them, so trouble on one profile can pause linking and follow you to the others. Linking a second account you already own is handled by support. Because you cannot refer yourself, the referral step is skipped when you create one, a rule our guide to the Fanvue referral program explains alongside the commission terms. AI creators planning several personas should read the Fanvue AI creator rules first.
Keep money and identity controls with the creator
Fanvue draws its firmest line around money. The payout options article, dated 21 August 2026, says only the creator, not agencies or managers on the account, can add, change, set as default or delete payout methods. Payouts cannot go to an account in someone else's name, including a manager, partner, family member or agency, even with permission, and the bank account name has to match the creator's verified KYC name.
New payout methods also pass through a security check that the payout options article says can take up to 24 hours, during which they show as In review. Treat that status as an alarm: if a method you did not add appears, assume the account is compromised, change the password and contact support.
The rest of the identity layer belongs with the creator too: the login email, the password and two-factor authentication on the creator account. The account settings article notes that accounts created with a Google or X login need a password set before two-factor can be switched on, and that losing the device holding your codes means proving your identity to support to get back in.
A safer starting set-up
It is easier to set access up narrowly than to claw it back later. Before the first invitation goes out, agree these points between creator and manager:
- Group creators under a manager account only if the same chatters may safely see all of them; otherwise use a separate manager account for each group.
- Each chatter registers and works under their own Fanvue login, never a shared team account.
- A written list records which creators each team member can see and who approved it.
- Any app or API connection gets its own approval, with the narrowest scopes that do the job; our Fanvue API guide explains what each scope exposes.
- The creator keeps the login email, the password, two-factor authentication and every payout method.
- Both sides know the offboarding steps below before anyone starts work.
Offboarding checklist when a manager or chatter leaves
Run this on the day someone's role ends, whether they leave on good terms or not. Several steps rely on controls described in the account settings article and Fanvue's January 2026 API policy update.
- Write down what you are removing, with the date: the manager email, each team member and every connected app.
- Look in Settings > Management for the option to remove the manager, then ask Fanvue support to confirm in writing that the connection has gone, since the help article does not describe this step.
- For a departing team member, have the manager remove them from the team, remembering they could see every creator under that manager account.
- Change the creator password, then use the option in Settings > Account to log out of all devices and sessions.
- Check that two-factor authentication is still switched on for the creator login.
- Open Settings > Account > Third Party Apps Consent and revoke every app you no longer use or do not recognise.
- If you ever created an app because someone asked you to, delete it under Creator Tools > Build, as Fanvue's January 2026 policy update advises.
- Review the payout methods list for anything you did not add, and confirm the default method is still your own.
- Review automated messages, AI messaging settings, scheduled posts and lists the person set up, because automated features can keep working after the person who configured them has gone.
- Delete tracking links and free trial links they created that you no longer need.
- Keep the chat history: messages the team sent went out in your name and remain your responsibility.
If the departing manager was an agency, our agency account control map shows how to separate day-to-day operation from recovery so the next handover is cleaner.
Limits of this guide
The steps above reflect Fanvue's help articles, terms and API policy on 1 October 2026. Fanvue says it is working on multiple administrators, its agency policy hub is still unwritten and help articles change without notice, so check the linked pages before relying on any detail, especially the removal steps the manager article leaves out. Where this guide suggests confirming something with support, that is because Fanvue has not documented it, not because the step is known to work a particular way.
This is general information, not legal advice. Any arrangement with a manager or agency should be written down, covering access, payment and what happens to content and data when it ends, and reviewed by a lawyer if significant money or content rights are involved.