Roles & admin actions

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, which teammates each Deployment Administrator looks after, memory-sharing, metering, and decommissioning. A Deployment Administrator configures the teammates assigned to them and can read their memory, but cannot create or delete teammates, share memory, change compliance settings, or assign roles; on every other teammate it is a User. 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, the teammates assigned to each Deployment Administrator, 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.