A new team starts using AI

Short answer. Invite the people from Team, add a department for their cost center, and connect the source they will use. Teams access is a separate switch and stays off until an owner turns it on or invites them.

The people

On Team, section Invite colleagues, send the invitation. The success sentence is "Invitation sent to {email}". A pending row reads "{email} · {role} · waiting to accept". The email says the invitation expires in 7 days. While one is pending, a second send says "An invitation is already pending for this email."

Give them the role they need. An owner, an admin, or a person with finance rights can ask spend questions. A member who is none of those can be in the account and still see "Ask your Meridian admin for access to spend questions" in Teams.

The department

Add a department before their spend should land on a cost center. A department budget can alert at 80% unless you set another percent. The alert is a warning. It does not move spend, and deleting the department does not reassign history.

Seat charges use the department column on the CSV. An agent uses the department on the agent. Set both when both exist.

The source and Teams

Connect the provider, gateway, or billing export on Integrations. Until the first sync saves records, Dashboard can stay on "No sources connected yet" or the source can read "Active, awaiting usage".

Meridian in Teams or Copilot needs Settings → Microsoft Teams & Copilot. That connection is optional. Meridian sign-in does not use it. Allow everyone in our tenant is off until an owner turns it on. The help text says "When on, people in this Microsoft tenant can use the Teams agent as members." Otherwise the person needs an invite. The Teams agent signs in through Microsoft Entra, so the customer's own MFA and Conditional Access policies apply there.

The setup list is Meridian setup checklist.