Authorizing meetings

Tenant administrators decide which AI teammates exist, which meetings they may join, and who may configure them. Authorization is an administrative choice, made once by people you designate, not a per-meeting negotiation.

Who holds authority

A Tenant Administrator has full control of the tenant: create, configure, suspend, or delete teammates, manage retention and memory-sharing settings, and assign administrative roles. A Deployment Administrator has narrower authority scoped to specific teammates — editing their standing instructions, voice, character, name, and backend binding — without the ability to create or delete teammates or assign roles.

Which meetings a teammate may join

A teammate joins a meeting when it is invited through your calendar or dispatched by an administrator. Before it joins, MeetCrew checks the meeting organizer’s tenant region. If the organizer’s tenant sits outside your supported region, the teammate refuses to join and the operating tenant’s admin is notified.

Who may configure teammates

Configuration authority follows role assignment, and every write path is deny-by-default: absent an explicit role granting the requested capability, the request is refused. Teams that run different teammates can each manage their own without gaining control of the whole tenant.