[People · Phase 2] Soci and association fees on Entra ID #144

Status: design agreed (9 November 2026), not started

Roadmap: #146 (decisions 10–15). Design: docs/people/soci.md (#154). Read it before picking up a sub-issue.

Goal

Make the dashboard the association's Libro Soci: who is or was a socio, the data the association must keep, the yearly fee and how the status ends.

In short

• Microsoft 365 is the source of truth for who is a socio now (the Soci group, which Auth reads as the Socio role). The backend register holds everything else, keyed on the account and the member number:
  • legal name, alias;
  • codice fiscale, place and date of birth, residence;
  • admission and end;
  • fees, history.
• Nothing is shared with People records, but Soci stay under People, in their own panel group.
• Admitting a socio moves to People › Soci, keeping the account workflow (licences, Soci group, welcome email) and collecting the bookkeeping data in the same dialog.
• Fees: the Regolamento's rules are hard-coded. Upload, then Direttivo confirms, then paid; or Mark as paid by hand. No association receipts.
• Lapse: automatic after 31 December, out of the Soci group, then Deletion pending, where accounts are deleted by hand. Switched off until the register is complete.
• Emails (reminders, lapse, birthdays) go to the PoliNetwork mailbox.
• Permissions: soci:read, soci:write and soci:delete go to the Direttivo; people:self goes to the Socio role.

Order

1. Auth: [People · Phase 2] Configure the Soci permissions in the production IdP auth#85 (production permissions), [People · Phase 2] Expose the Microsoft 365 object ID in the access snapshot auth#84 (Microsoft 365 object ID in the access snapshot).
2. Register: [People · Phase 2] Soci register and admission backend#122, then [People · Phase 2] Soci › Register and Admit socio #155.
3. Fees: [People · Phase 2] Soci fees: uploads, review and fee emails backend#123, then [People · Phase 2] Soci › Fees and the Socio card in My area #156.
4. Ending and deletion: [People · Phase 2] End a socio's status, automatic lapse and account deletion backend#124, then [People · Phase 2] End status, Restore and Deletion pending #157. Birthdays: [People · Phase 2] Birthday emails for Soci backend#125.
5. Production rollout:
   • register the existing soci;
   • mark the 2026/27 fees already paid;
   • switch on SOCI_AUTO_LAPSE;
   • delete azure:members:create / azure:members:write ([People · Phase 2] Configure the Soci permissions in the production IdP auth#85).

Later, not planned

• Export the register per year as a spreadsheet.
• Receipts signed with the CIE.
• Resigning from My area.