> ## Documentation Index > Fetch the complete documentation index at: https://mirage.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # Team & field reporters > Invite stewards by email and deploy field reporters with shareable invite codes Your organization's **People** page manages everyone who works in Mirage with you. There are two ways to bring people in, built for two different situations: | Method | Best for | How it works | | - | - | - | | **Email invitation** | Teammates you know by email, especially new stewards | A personal, single-use link sent to their inbox | | **Invite code** | Field reporters, recruited in batches or on the ground | A shareable 6-character code anyone can redeem | ![People page with team members, email invites, and recruitment kit](https://mintcdn.com/mirage/eVR3n30GbOeZdkdj/images/steward-people-page.png?fit=max\&auto=format\&n=eVR3n30GbOeZdkdj\&q=85\&s=1873a962cc2c688109ebe7822f3f4d4e) The People page: your team, email invites, and the reporter recruitment kit. ## Invite teammates by email **1. Send the invitation** On the **People** page, enter one email address or paste a whole list of up to 50 (separated by commas, spaces, or new lines) and choose a role: **steward** (full dashboard access) or **reporter**. **2. They accept** Each invitee receives an email with a personal join link. If they don't have a Mirage account yet, they sign up first and then land in your organization automatically. **3. Track it** Pending invitations are listed on the People page with a colored status: **Invited** (delivered), **Email failed**, or **Copy link** (shown when email isn't configured: send the link yourself). You can copy the link, resend, or remove an invitation any time before it's accepted. Invitations expire after 14 days. > [!WARNING] > > Stewards can do everything in your organization: manage projects, review reports, generate donor reports, and handle billing. Only invite people you trust with the steward role; give field staff the reporter role instead. > [!TIP] > > If someone signs up with an email whose domain matches your organization's website, Mirage suggests your organization to them and lets them request an invite. You'll get a notification instead of them joining automatically. ## Deploy field reporters with invite codes Invite codes are the fastest way to get reporters into the field. One code can onboard a whole cohort, no email addresses needed. **1. Generate a code** On the **People** page, generate an invite code. You get a 6-character code (like `PQXN8K`) that's easy to read aloud, text, or print. **2. Configure it (optional)** Give the code a **label** so you remember what it's for ("Q3 field cohort"), attach a **project context**, and set an **expiration date** or a **maximum number of uses**. You can deactivate a code at any moment: existing members keep their access; the code just stops working for new joins. **3. Share it** Reporters redeem the code at [report.mirage.partners](https://report.mirage.partners), either by entering it on the **Join** screen or by opening your code's link directly. For in-person recruitment, print the QR card Mirage generates for each code and let reporters scan it. **4. Watch them arrive** The People page tracks how many times each code has been used. As soon as a reporter joins, your organization's open reporting tasks appear on their dashboard. ### Recruitment landing pages Each invite code can optionally publish a **recruitment landing page**: a public page at a shareable URL that shows your organization, the tied project's story, and the latest verified field evidence behind it. It's easy to read it as a reporter-recruitment tool, but it deliberately serves **two audiences at once**: * **Field reporters** see a legitimate, branded invitation instead of a bare code, with the project they'd be reporting on and proof that the work is real. * **Interested donors** who land on the same page can leave their name, email, and giving priorities. Those arrive in your organization as **donor leads**. See [Managing donors](https://mirage.mintlify.site/donor-reports/managing-donors.md#donor-leads). > [!WARNING] > > A published landing page is **public**: anyone with the URL sees your organization, the tied project's context, and recent verified field evidence. Publish one only when you're comfortable with that project's story being seen by strangers, and unpublish it when a campaign ends. Codes without a published landing page expose nothing: the code only works as a join key. ### Tying a code to a project Attaching a **project context** to an invite code is optional: * **Tie it to a project** when you're recruiting for a specific site or campaign ("Kisesa well monitors, Q3") or whenever you publish a landing page, since the page draws its story and evidence from that project. * **Leave it untied** for general-purpose codes: onboarding your standing field team, or reporters who will float across projects. They'll see all of your organization's open tasks either way. > [!TIP] > > Point your reporters at the [Field reporter quickstart](https://mirage.mintlify.site/reporters/reporter-quickstart.md). It's written for them, covering joining, installing the app on their phone, and submitting their first report. ## Roles on the People page The **Team** card lists everyone in your organization, stewards and reporters alike, with their role: * **Steward**: full administrative access to the dashboard. * **Reporter**: sees and submits against your reporting tasks in the reporter app; no dashboard access. A person's role is per-organization, so someone can be a steward for one organization and a reporter for another. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.