Mentor access and team seats: what a mentor sees, and what they never can

You invite; nobody asks

The data in your journal is yours, so access only ever flows one way: from Journal > Mentors, you type an email and flip one switch, "let them comment on trades and days". There is no "a mentor requests access" button anywhere in the product. The invitation link works once, expires after 7 days, and only the invited email address can accept it; whoever accepts sees your data starting from that moment, with the seat pool re-checked on every single request so a plan that no longer has room, or an ended invitation, applies immediately, not on the next sign-in.

What opens up to a mentor

A mentor, or a team viewer, reads the same trades, tags, annotations, playbooks and notes you see, your daily written reviews, your voice memos, the journal's own insights (playbook comparisons, your discipline rating, the weekly edge finder), your import history, the execution audit's cost numbers, your prop-tracker's guard readings, and any Strategy Lab run you have sent to the journal. Every one of these was opened deliberately, route by route; a new page FxMind builds is closed to a mentor by default until it is explicitly opened, so the safe direction is always "a mentor sees nothing new" rather than the other way round.

What a mentor never sees or does, on any plan

• Your broker credentials or account-linking details. A mentor never touches how your account connects.
• Trading. No order can ever be sent from a mentor's session, on any account, under any role.
• Billing, settings, or your analyst questions. A mentor's own questions to the analyst are never billed against your allowance, because they cannot ask them on your account at all.
• Your data export or your trade list's CSV. Exporting your own data stays yours alone to do.
• Whether a trade has a public share link, or the link itself. Publishing your own results is your decision, not something a mentor can see the state of.

Team seats: the same pool, a second role

A team seat reads exactly like a mentor's: same view, same read-only rule, same labelled banner. The difference is the admin role, which can also invite and remove other seats on your behalf, and switch whether a seat may comment; only you, the account holder, can make or unmake an admin, and an admin can never touch their own seat's role, including making themselves the holder. Nobody on a team, admin included, reaches billing, settings, account linking, or a trading seat: there is no such thing yet as a seat that can place an order on your account.

Switching journals, and ending access

A mentor or teammate stays signed in as themselves the whole time; opening your journal is a switch they make from their own account, always shown with a clear "Viewing \<name\>'s journal (read-only)" banner and a one-tap way back to their own. You can end anyone's access at any time from your side, and they can leave on their own from theirs; either one takes effect on the very next request, nothing cached. Every invite, accept, comment and revoke writes to your audit log, visible to you under Security in Settings, and account deletion removes every grant in both directions along with the comments tied to it.

Seats, by plan

A seat is one named person besides you, and you always occupy one of the seats your plan includes: what is left over is what you can hand to a mentor or a teammate, in any mix.

How a trader uses it: for one trade or one day, Ask for a review (every plan) lets a mentor or a community look and answer as comments, seeing only what you switch on. To keep a mentor on the whole journal, give them a seat: 1 mentor on Elite, 4 on Desk. See /features and /pricing.

A pending invitation holds a seat until it is accepted or expires, and the seats that count are always the earliest accepted ones: if a plan shrinks, the newest grants pause rather than being deleted, and they come back the moment the plan grows again.