Review privacy before connecting communication services

Identify the data involved

Communication connectors can expose message metadata, participants, subjects, content, event details, phone numbers, or transcripts. Determine which fields the workflow needs and which people, clients, or channels must be excluded.

Apply least privilege

Connect the narrowest appropriate account and grant only the permissions shown as necessary. Use user-level access when workspace-level administration is not required. Review external provider grants after role changes and remove obsolete connections.

Limit automation

Begin integration rules with Save, not automatic submission. Review descriptions and project routing for confidentiality and accuracy. A broad rule can send sensitive or unrelated activity into the wrong client workspace.

Respect consent and professional duties

For calls, meetings, or transcripts, comply with applicable consent and recording laws. For legal, financial, health, or other regulated work, follow contractual and professional obligations governing client data. TimeSentry configuration does not replace those duties.

Set a review cadence

Periodically audit connected accounts, active rules, failed synchronizations, retention settings, and who can manage integrations. Remove data according to company policy without assuming that disconnecting a provider deletes previously imported records.