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. 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

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.