MCM-41 — Invite a Teammate to the Organization

← Back to MCM Nexus overview

As an Org Owner,
I want to invite a specific teammate by email,
so that I don't have to wait for them to independently sign up and request to join — see MCM-29 — Organization Join Requests for that reactive path.

Acceptance Criteria

• Owner can invite a teammate from within the Nexus portal by entering their name and email.
• The invited email must match the organization's own domain — an Owner cannot invite someone outside their organization's domain, consistent with how organizations are identified by domain (see MCM-02).
• Inviting a teammate creates their account immediately — no approval step, since the Owner is directly authorizing it. This reuses the same account-creation mechanism MCM-29 uses when the Owner approves a join request, just triggered directly instead of via a pending request, and with its own invitation-worded welcome email (see Email Template below) rather than MCM-29's approval email.
• The invited teammate becomes a Member with the same full access to the organization's subscription details as any other Member — identical outcome to an approved join request.
• Inviting an email that already belongs to an existing account, an already-pending join request, or a different organization entirely is rejected with a clear, specific error rather than silently creating a duplicate.
• Owner sees a list of the organization's current Members, separate from the pending-join-requests list.
• The temporary password expires 24 hours after issuance; if the invited teammate hasn't logged in by then, it no longer works.

Technical Design

Inviting a teammate reuses the same account-creation mechanism MCM-29 uses on approval — Keycloak identity and temporary credential — just triggered directly by the Owner instead of by approving a pending request, and with no join-request record created at all, since there's nothing to review. It sends its own invitation-worded welcome email (see Email Template below) rather than MCM-29's approval email, since the teammate never submitted a request in the first place. The invited email's domain is checked against the organization's own domain before proceeding, the same check MCM-02 applies at signup time.

Email Template

Distinct from MCM-29's approval email since the teammate never submitted a request:

Subject: You've Been Invited to Join <Company Name> on MCM Nexus

Dear <Teammate Name>,

Greetings from the MCM Team!

<Owner Name> has invited you to join <Company Name> on MCM Nexus. Use the temporary password below to log in and set your own password.

## Your Login Details

Portal: https://nexus.mcm.revdau.ai/login
Email: <Teammate Email>
Temporary Password: <generated password>

This temporary password expires in 24 hours — please log in and set your new password before then.

You'll be asked to set a new password the first time you log in. Once in, you'll have full access to your organization's subscription details.

If you have any questions, our support team is available to help.

Support Email: mcm@revdau.ai
Documentation Portal: https://mcm.revdau.ai/docs/

Thank you for choosing MCM.

Best Regards,
MCM Team

UI / Frontend Changes

• New "Team" area for the Owner: list of current Members, with an "Invite Teammate" action (name and email form).
• Inline validation for a domain mismatch or an email that already has an account/pending request.
• Confirmation before sending an invite, since it creates the teammate's account immediately.

Out of Scope

• Inviting someone as a co-Owner — invited teammates always become Members (see MCM-29's existing Out of Scope on Owner transfer/co-owners).
• Revoking a Member's access once invited — not yet covered by this or MCM-29.