📤 Permissions: record sharing

This discussion spins out of the email-specific thread at Following Felix's feedback here: The open problem should be reframed from an email-only feature into a broader permissions / roles workstream. Why broaden it The "request access" capability is not unique to emails. The same underlying logic will apply to sharing or requesting access to other resources such as notes, tasks, and future object types. Rather than solving this in an email-specific way, we should define the generic model first. Questions to solve • Which resources can be shared or requested access to? • What is the underlying data model for grants, requests, approvals, denials, revocations, and auditability? • How do explicit shares interact with workspace roles and other permission layers? • What should the access-request lifecycle look like, including deduplication and notification behavior? • Which parts are generic platform behavior vs. resource-specific UI? E…