How to Invite Team Members

Team collaboration lets you bring analysts, partners, and stakeholders into your Mogul Deal Evaluator account — either across the team or per deal, with role-based permissions and scenario-level scope. Team features are part of the top-tier plan; the Team page shows an upgrade prompt if your plan doesn't include them.

The three roles

• Admin — manages team members and assigned access (and, on a deal, can manage that deal's access).
• Analyst — works on assigned deals and edits the scenarios shared with them.
• Viewer — read-only access.

Invite to your team

1. Open Team from the sidebar and click Invite member.
2. Add one or more email addresses (press Enter after each) and choose the team role — Viewer is the default; you can change a member's role any time from the Members tab.
3. Send. Invitees get an email link to accept; invitations also appear in a "Your Invitations" panel on their own Team page with Accept / Decline buttons.

The invite dialog shows your seat usage — seats are set by your plan, and a pending invitation occupies a seat until it is accepted or revoked. Pending invites live in their own tab, where you can Resend or Revoke them; invitations expire, so resend if someone waited too long.

Share specific deals

From a deal you can invite someone to that deal only: enter their email, pick a role for the deal, and choose the scenarios they can work in — all scenarios or a specific subset. (A deal admin always has all-scenario access.) The Team page's Shared deals tab lists every deal-level grant, where Edit changes a member's role or scenario scope for that one deal and Remove revokes access to that deal only — not their team membership.

Keep track

The Activity tab logs the trail — invitations sent, resent, revoked, accepted; role changes; members removed; deals shared and access updated — so an account owner can audit who has what.

Common mistakes to avoid

• Inviting everyone as Admin. Admins manage members and access; most collaborators need Analyst (work on assigned deals) or Viewer (read-only).
• Team-inviting someone who needs one deal. Deal-level sharing with scenario scope is tighter and doesn't hand them your whole pipeline.
• Forgetting scenario scope. An analyst granted "all scenarios" can edit your base case — share only the scenarios they should touch.
• Confusing removal types. Removing a shared-deal row revokes one deal; removing a member from the Members tab removes them from the team.