Skip to main content
Contacts (contacts.tuturuuu.com, apps/contacts) owns the workspace-user CRM surface. A CRM workspace user and a signed-in platform account are different entities; links between them are explicit. Central login, the Contacts app session, workspace membership, and feature/role checks govern access.

Find the right area

Some areas depend on workspace modules. An unavailable module must distinguish access denial, disabled configuration, and loading/failure states; it should not pretend that all of these mean a missing record. See Contacts module availability.

Mobile attendance history

Choose a day before opening a group’s attendance sheet. Members and marks are loaded for that group and day. Editing attendance, including session attendance, saves changed marks. Clearing a saved mark sends the cleared status. The mobile attendance tests cover saved and cleared marks.

Mobile CSV and archiving

Review imported contacts page by page before confirming a CSV import. The preview identifies skipped invalid and duplicate email rows. The completion message uses the server’s inserted count, and offline imports show their queue status. Export lets you choose the contact status and CSV columns. Private columns are available only with the corresponding contact permission. The export checks every page and stops if it cannot confirm a complete result. Selecting an archive end date enables archiving. Turning off archiving clears the end date. The mobile CSV tests cover quoted fields, skipped rows, pagination, and private column visibility.

Mobile duplicate batches

Use Merge reviewed pairs after checking the surviving contact in each pair. A batch accepts independent pairs of two contacts and requires confirmation. It stops on an unconfirmed merge and displays the confirmed count. Review the current duplicate results before starting another batch. The mobile bulk merge widget tests cover cancellation and stopping after an unconfirmed pair.

Mobile group membership

Open a group’s Group members action to see its members and their roles. Members load in pages. People who can update user groups can remove a member. People with that permission and contact-directory access can search for a contact and add them as a student or teacher. Removing a group membership keeps the contact in the workspace directory. The mobile group membership widget tests exercise adding and removing a member in light and dark appearance.

Mobile private profile fields

Contacts shows gender, ethnicity, and national ID to people who can view private contact information. People with the relevant contact create or update permission can enter or clear these fields on the form. The Contacts workspace widget tests cover private field visibility in light and dark appearance.

Mobile contact billing

Open Invoices from a contact’s detail to view their invoice history and outstanding subscription fees. This section requires Contacts private-info access and the Finance invoice-view permission. It follows the device’s finance amount visibility setting. Invoice history loads in pages and the outstanding amount comes from the grouped subscription calculation. The mobile contact billing widget tests exercise opening the section and paging through invoice history in light and dark appearance. From an unlinked contact in the mobile app, choose Invite account holder to link. Select one workspace account, create the invitation, then share it with that account holder. This action requires permission to update contacts and view both public and private contact information. The recipient signs into Tuturuuu to review the inviter, contact display name, workspace, and expiration. They can confirm or decline. An authorized operator can revoke an active invitation. Issuing a new invitation replaces any active invitation for the contact. Invitations expire after one day and can be used once by the selected account. The database rechecks the workspace, contact, membership, and eligibility at confirmation. The link and its actor-attributed audit event commit together. When provisioning records an account’s starter profile, the invitation can identify that profile for replacement. The account holder reviews the merge before confirming. The sender must also have permission to delete users, since the merge transfers the starter profile’s records and removes that profile. Earlier mappings without provisioning provenance cannot be replaced this way. A profile retained in a merge loses starter status. The private consent audit records the merge result, including duplicate records removed on collisions. An authorized duplicate contact merge may transfer the source’s existing account link to the retained contact when the retained contact is unlinked. The confirmation page and API omit contact email and platform account IDs. Linked account holders and workspace operators with permission to update contacts can unlink an account from the contact details. Unlinking preserves the contact and writes an attributed audit event. Workspace membership remains active. On the member’s next visit, workspace provisioning can create a fresh member profile. The original contact stays unlinked. Direct signed-in writes to the link table are denied. Manual group linking can move a teaching assignment to an already linked profile. Creating a mapping through manual linking or member profile editing requires an invitation. Matching email addresses cannot attach an existing contact to an account. Membership provisioning and owner consolidation create a fresh member profile when needed. Group assignments leave contact mappings alone. Email-based guest self-join requires confirmation before it can attach a contact. The contact-link route and confirmation tests cover explicit consent and permission failures. The Supabase contact-account-link-confirmation test covers direct write denial, edited email matches, recipient binding, audit attribution, and replay.

Mobile audit activity

Open Audit log from the Contacts dock if your role can manage workspace audit logs. Each event shows the contact, action, actor, and local time. Field changes show the old and new values and omit unchanged fields. Filter events by date range, action, source, contact, or actor. The final selected date is included. Some historical events have limited change details. The mobile Contacts rebuild widget tests exercise the timeline in light and dark appearance.

Cross-app people integration

The shared people-search integration is under development. Its first slice adds GET /api/v1/workspaces/{wsId}/people and the @tuturuuu/internal-api/people client; this does not establish that every app already uses the endpoint. Mail recipient selection, Calendar attendees, Tasks contacts search, and Meet invitations adopt it in separate slices. In the shared Tasks assignee popover and task-card assignee menu, a search of 2–100 characters can show a separate Contacts group. Each contact opens its workspace record in Contacts. Contacts never enter the assignee list or its numeric shortcuts, including when a contact ID, explicit linked account or email matches a member. Board-viewable members and direct guests remain the assignment source, and existing assigned users can still be removed. Contact-read denial does not disable board assignment. Existing task mention notifications keep their authenticated-member semantics; opening a contact sends no notification. This applies to active apps using the shared Tasks UI; standalone contact views and member assignment permission checks retain their own rules. Regression coverage lives in task-contact-results.test.tsx, assignee-select.test.tsx and task-assignees-contacts.test.tsx in packages/tasks-ui. Search is workspace scoped and requires membership and contact-read permission. Results contain only a contact or member identity and permitted name, email and avatar fields. CRM notes, addresses, guardians, birthdays, balances and identity documents are excluded. Hidden member names and emails cannot be used to find records through this endpoint, including linked Contacts records. Contact email requires private-information permission; public names and avatars require public-information permission. Query text is bounded to 2–100 characters and results to at most 20. Wildcard queries are unsupported. A contact ID remains distinct from an authenticated member ID. Searching does not create membership, send an invitation, change a profile, or make a contact eligible for task assignment. Assignment and notification keep their existing member and board access checks. Explicitly adding a mail sender uses the existing contact-create permission and requires a separate user action. The shared account/profile panel proposal builds on the existing satellite and Web panels and current-user profile API. Global account names remain separate from workspace CRM profiles; shared name fallback and private-detail policy stay with their existing owners. Email changes retain verification and sensitive action checks. No database migration is part of the initial search slice. Focused coverage lives in the Web workspace-people tests, the people route tests, and packages/internal-api/src/people.test.ts. Execution and deployment evidence are required separately before this proposal can be described as shipped. User management describes user and account boundaries. Reports and Tutoring explain the education/CRM flows. Group access does not grant a linked parent unrestricted editing rights. Outreach and topic announcements require their own delivery configuration and recipient rules.

Ownership and privacy

Explicit Mail sender creation

Mail’s sender card offers Add to Contacts only after the API confirms the current member has create_users. The action creates a workspace contact through the existing audited RPC; it never creates an authenticated member, guest group, identity link, invitation or notification. The message’s displayed sender name is bounded to the contact name limit. The server accepts only an operation UUID, email and display name, and derives the contact ID from the verified actor, workspace and operation. It does not accept actor or contact IDs from the client. The handler opens its contact-operation write client only after the membership and create-permission checks. Shared authentication and permission helpers may already open read-only admin clients under the verified user. The browser retains the operation UUID in tab storage scoped by actor, workspace and a hashed sender identity before the explicit submit. Reopening the action or checking an UNKNOWN result performs a read-only status request, never another create. An unobserved result remains UNKNOWN; it does not mean no contact exists. A later confirmed commit opens the contact without replaying the write. Storage failure prevents submission. Server reconciliation returns only state and a contact ID, with no CRM fields. Repeated or concurrent calls with the same operation converge through the existing contact primary key and audit RPC. This rule applies to Mail’s workspace sender card. Existing Contacts forms keep their own creation behavior. No database policy or migration is changed. Regression coverage includes contact-create-operation.test.ts, the active Web people/contacts/route.test.ts, and Mail’s sender-operation and create-control tests. Signed-in runtime acceptance remains a separate release check. Contacts owns the users routes removed from Web. Shared domain/UI code lives in packages/users-core and packages/users-ui. Non-owned workspace destinations redirect to their canonical app rather than being implemented as catch-all API proxies. Workspace CRM records, reports, attendance, and outreach are private and receive noindex directives. The public product description belongs on the main site’s CRM page. Source routes list all Contacts pages and handlers. Permissions and Satellite apps explain the shared access contract.

Default-off Start candidate

The additive Contacts Worker is restricted to the separately admitted staging origin. All customer pages, including tutoring, and local/API-proxied handlers retain Next ownership; only an inert candidate probe is native. EN/VI paths, Contacts satellite sessions and central Web API ownership are preserved. See Contacts Start candidate for owner inputs, regression controls, staging acceptance and instant rollback boundaries. This exception adds no live customer rule or production route.

Calendar invitation creates

The shared Calendar create dialog supports explicit contact guest selection for writable Google and Outlook sources when legacy color generation is disabled. A dedicated authenticated, read-only capability query binds availability to the selected workspace, provider, connection and calendar. Missing, stale or refreshing capability disables guest selection and submission. Retry refreshes availability inside the open dialog without changing draft fields, guests or request identity; failed or denied refresh keeps submission blocked. Discovery never sends invites or refreshes provider colors. The server retains final authority over generation and retained-request refusals. Creation preserves the draft request identity for explicit recovery of an uncertain response. Guest addresses use the existing normalized people-picker projection, 100-guest limit and time zone. Saved-event attendee editing, native sources and provider-color invitations remain unavailable. Google color discovery remains separate for recoverable color creates. Regression coverage: Calendar invitation-capabilities route tests, shared UI calendar-event-create-payload, use-calendar-invitation-capabilities and use-calendar-draft-save tests, plus existing provider meeting and generation tests.

Existing Calendar guest snapshots

Saved-event guest details are read only in the shared Calendar modal in Calendar, Web, Tasks and Contacts. View guests performs an explicit organizer-authorized provider read; Refresh guests repeats only that read. The server derives actor, workspace, calendar and provider event identity from the authorized local event and writable connection. The UI keeps snapshots out of generic event Save payloads. It does not offer add/remove or RSVP changes. Snapshots are scoped to the open component instance, are not persisted, and are removed after a failed refresh. This slice admits only nonrecurring Google/Outlook organizer events with complete attendee lists and a provider revision. Native, read-only, foreign-source, provider-color, pending create, retained generation and legacy-mode events are refused. Missing recurrence state fails closed. The response projects guest names/addresses and RSVP/resource/optional flags; it does not return account credentials or raw provider payloads. Reads do not notify guests or change RSVP. Attendee writes require a durable event-level operation ledger before admission. The create reservation binds an event insertion and its stable provider create ID; it is not an attendee journal. Meeting coordination fingerprints expire after two hours. An attendee ledger must bind actor/workspace/source/calendar/event, operation identity, base revision and full intended attendee metadata; atomically fence dispatch and every new operation while outcome is unknown; survive reload and coordinate with all other event writers. Unknown outcomes permit bounded read reconciliation only, never another notification-producing write. Ordinary mutable event metadata or an expiring lease alone does not provide that fence. Google documents conditional modification with ETag/If-Match and a 412 conflict. The Graph event update contract limits notifications when the body contains only attendees, but does not establish If-Match semantics for event PATCH. Outlook mutation stays blocked until its conditional-write contract is verified. No read-only snapshot implies write capability. Existing create invitations retain their separate durable identities. Regression coverage: attendee-snapshot.test.ts, the event attendees route tests, shared calendar-attendee-snapshot.test.tsx, and native registry/mount parity. Successful add/remove, stale-write conflict and UNKNOWN mutation recovery are not implemented by this read-only slice; no corresponding safety claim is made.