Open CRM → People in the school you operate. The directory holds Person records for that school; it is not a separate lead database. An owner/admin can inspect everyone in the school. A closer reads only people in their assigned closing scope and can capture one contact; a coach reads only students from assigned enrollments. A setter cannot open the CRM list. Bulk import and duplicate linking belong to the owner/admin.
Choose New person on People. For Maya Chen, an Instagram conversation may give you only Channel: Instagram and a Reference on that channel such as @maya.builds. That pair is enough for a Person record; you can also use an email address or phone number. Leave Email empty if you do not know it. Enter a school Source only when an appropriate active source is configured. Save, then use Open their record to inspect the result. Recording Maya creates neither a user account nor an enrollment.
If you enter an email already found on the current People page, the capture sheet names the existing record and links to it. The capture service may also refuse an address collision outside the visible page. Open the existing record and check the identity instead of repeatedly submitting. This capture rule does not mean email is a unique database key: Person email is optional and nonunique, and duplicates can exist, especially across channels or concurrent writes.
For a list collected at an event, choose Import people. The screen has four stages: Upload, Map, Preview, and Report. Upload a .csv file of up to 1 MB and 500 rows. Map each selected column to at most one Person field. The current Map columns screen requires exactly one column mapped to Email; it also offers First name, Last name, and Phone. A single no-email contact belongs in New person, not this CSV flow. Source, campaign, consent, channel and external reference are not CSV destinations in the current screen.
Use Preview before writing. It reports rows To create, Already known, File duplicate, or Rejected and writes nothing. Inspect a matched address and any rejected row before choosing Import people. The final Import report shows what was created or skipped; if processing was interrupted, completed rows remain and the report offers Resume. Review the resulting People records in the same school. Import does not grant accounts or assign a lead status simply because a row came from a prospect list.
| Task | Owner/admin | Closer | Setter |
|---|
| Read People | All school people | Assigned closing people only | No CRM list |
| Capture one Person | Yes | Yes | No CRM list/capture |
| Import CSV | Yes | No | No |
| Link or unlink duplicate records | Yes | No | No |
Suppose the owner recorded Maya's Instagram handle first and a later event import left a second Maya record with maya@example.com. Search and open both records. Names and addresses are clues, not proof; confirm with Maya or another trustworthy context that they describe the same human. On the secondary record, use Linked records → Link this record to another, search for the primary record, and select it. The secondary disappears from normal lists while its content is read on the primary. Nothing is overwritten or deleted. If the match was mistaken, choose Unlink from the primary record's Linked records section; both records return to their prior state. Linking across schools or chaining aliases is refused.
For integrations, the People API currently covers batch import and alias link/unlink with an API key bound to a school. It does not expose general Person list/read/edit or qualification form operations. The operator's school session and business role still decide what the screens allow.
