Workspace membership
Keep the team’s accounts and invitations organised. Workspace membership is separate from the guest flow used to join an individual call.
Guest joining explained ↗ORGANISE THE WORK. RESPECT THE CONVERSATION.
Bring accounts and members together in a workspace. Manage invitations, roles and shared credit without treating private conversations as a team-wide content archive.
Workspace and member management are free. Paid communication still consumes credit.
Accounts · Invitations · Shared credit

START WITH PEOPLE AND RESPONSIBILITIES
Before sending invitations, consider who belongs in the workspace and who needs to handle organisation or billing. Owner, admin, billing and member roles represent different responsibilities; assigning a role is not an automatic grant of private conversation access.
Next, decide how paid usage will be funded. Shared credit and daily, weekly, monthly or per-call controls support allowance decisions. The appropriate choice depends on how the team plans to communicate, not simply on the number of members.
For a meeting, agree on Direct or Translated mode and check the relevant language pairs. For usage review, use metadata analytics and credit information rather than assuming that an administrator can read or listen to private conversations.
Keep any local recording or transcript choice separate from team membership. A workspace helps organise people and credit; it does not create an automatic archive of everything they say.
BRING PEOPLE TOGETHER INTENTIONALLY
Teams organises accounts through invitations and member management. Invite the people who belong in the workspace, and consider what responsibilities they need rather than giving everyone the same role.

Keep the team’s accounts and invitations organised. Workspace membership is separate from the guest flow used to join an individual call.
Guest joining explained ↗Owner, admin, billing and member roles distinguish different workspace responsibilities. Do not assume a role grants every possible permission.
People can use direct or translated communication as appropriate to the mode and language pair. Choose each person’s language using the options available for that conversation.
Explore supported languages ↗A workspace admin is not automatically allowed to access private conversation content. Managing members, funding usage and reading what people say are different things.
Keep workspace decisions separate from recording or transcript choices. Those optional local-saving tools have their own controls, charges and consent requirements.
Read the privacy boundaries ↗MAKE SHARED CREDIT A DELIBERATE CHOICE
Teams supports shared credit and allowances, with daily, weekly, monthly and per-call controls. Choose limits that fit the way your team communicates, without assuming the workspace includes unlimited paid calls.

Organise allowances around a day’s communication.
Use a weekly allowance perspective for recurring work.
Set a monthly allowance context for a team budget.
Consider a limit for an individual paid conversation.
These are allowance periods and controls, not published example budgets or a promise of unlimited usage. Paid communication consumes credit at the relevant mode’s rate.
Understand prepaid pricing ↗USAGE INFORMATION, NOT PRIVATE CONTENT
Metadata analytics covers usage and credit with no additional feature charge. It helps distinguish communication activity from the content of a conversation.
Account Settings covers profile, default language, call history and prepaid billing. History is a usage record, not an automatic recording or saved transcript.
Workspace and member management remain free. Communication charges and optional recording or transcript charges are separate.
Understand optional saving ↗For a small team, membership, invitations and clear credit decisions are useful starting points. Pick the communication mode for the conversation rather than assuming every meeting needs translation.
Explore team meetings ↗Business, Enterprise and API arrangements require separately approved specifications. Teams does not imply a published SSO offer, a standard enterprise package or promised integrations.