Docs › Administration › Roles & admin actions
Roles & admin actions
Last updated July 2026 · ~4 min read
MeetCrew has three roles within a tenant, all scoped to your organization. Every administrative action is attributed to the administrator who performed it, so your audit trail names a person, not a service.
The three roles
A Tenant Administrator has full control: managing teammates, roles, retention, memory-sharing, metering, and decommissioning. A Deployment Administrator configures only the teammates assigned to them. A User is a standard member who can take part in meetings but configures nothing. User membership is inherited automatically from your Microsoft Entra tenant; the two administrative roles are assigned explicitly.
Attribution of admin actions
Administrative actions attribute to the acting administrator rather than to a shared system identity. When an administrator makes a change, the audit record carries that administrator’s Entra identity as the actor. Role assignments, teammate creation and deletion, and decommissioning are all recorded this way.
Cross-tenant boundaries
Role assignments are local to a single tenant. A Tenant Administrator in one customer’s tenant holds no role in any other. Authorization is enforced deny-by-default, so an unassigned caller is refused.
MeetCrew operators hold no role inside your tenant. Support access to tenant data runs through a separate, two-person-approved, audited flow, with notification to your administrators.
Was this helpful? Yes · No | Still stuck? Contact support.