Team roles, activity, and analytics

Roles

• Owner: ultimate workspace and billing authority; manages seat capacity and high-impact settings.
• Admin: manages members, roles, access configuration, team settings, audit, and permitted exports.
• Manager: typically sees team or defined-scope activity/analytics and may invite/manage within policy.
• Member: sees their own activity by default.

The exact permission matrix is configurable. Always trust the current Roles & access screen rather than assuming a title grants every possible action.

Activity feed

The team feed shows tracked team messages with open/click context permitted to your role. Views/read state are user-specific conveniences; they do not delete the underlying event.

Analytics

Team analytics can include trends, heatmaps, member comparison/leaderboards, message engagement, devices, countries, and network evidence. Interpret the same signal-quality rules used in personal reports: privacy proxies and scanners are not human opens, and group deliveries are not named-recipient proof.

Member comparisons should account for role, territory, audience, volume, and type of work. A higher open rate is not automatically better performance, and privacy/client mix can make direct comparisons misleading.

Privacy by role

Managers and admins may see message metadata, recipients, activity, or analytics beyond their own account when policy allows. Configure the narrowest access consistent with the team's purpose, disclose team visibility to members, and avoid exposing subject/recipient data to roles that only need aggregates.

Audit log

Role, invite, removal, settings, and other administrative actions are recorded for accountability. Audit availability does not replace provider logs or legal retention requirements, but it helps answer who changed workspace state and when.