Add Members

Definition

The Add Members action in the Microsoft Teams category allows you to add users to a Team, Channel, or Chat within Microsoft Teams. Depending on the selected type, you can specify whether members should join as standard participants or as owners with elevated permissions. This action supports dynamic inputs, meaning you can either choose from available Teams, Channels, or Chats in your connection or provide IDs and user details dynamically from previous steps in your flow. Key capabilities include bulk-adding members via email addresses or user IDs, assigning ownership roles, and handling different membership rules depending on whether you’re targeting a Team, Channel, or Chat.

Example Use Case

1. Employee Onboarding

Automatically add new hires to their department’s Team and relevant project Channels, ensuring they have instant access to resources and discussions.

2. Project Kickoff

When a new project is created, add all project members to a dedicated Team or Chat, streamlining collaboration from day one.

3. Cross-Department Collaboration

Quickly add members from multiple departments into a shared Team or Channel for joint initiatives without manual effort.

4. Escalation Handling

Automatically add managers or key stakeholders to a Chat when an escalation or urgent issue is raised in a workflow.

5. Event or Training Setup

Enroll participants into a Team or Channel dedicated to an event, training, or workshop for centralized communication.

Inputs

Below are the input fields for the Add Members action in the Microsoft Teams category. The available fields change depending on the Type (Team, Channel, or Chat). Wherever you see the token picker (chain icon), you can supply values dynamically from previous steps in your flow (e.g., IDs or email addresses captured earlier). After you connect, dropdowns are auto-populated with the items your connection can access.

1. Connection

Select the authenticated Microsoft Teams connection the action should use.

What it does: Authorizes the action to read Teams/Channels/Chats and add users.
Why it matters: The connection’s account must have sufficient permissions (e.g., Team owner or an account allowed to manage membership). If the account can’t see or manage a resource, it won’t appear in dropdowns and membership changes may fail.

2. Type

Choose where you want to add people: Team, Channel, or Chat.

Effect: This selection determines which additional fields appear.
At a glance:
- Team → Team Id, Members, Owners
- Channel → Team Id, Channel Id, Members, Owners
- Chat → Chat Id, Owners (adds participants to the chat)

When Type = Team

Add users at the team level (they’ll gain access to all standard channels in that team).

2.1.1. Team Id

Select the team to add members to.

How to provide: Dropdown, Token Picker, or comma‑separated user IDs or Emails.

2.1.2. Members

Add users as standard members of the team.

How to provide: Dropdown, dynamically via the Token Picker, or comma‑separated user IDs or Emails.

Behavior:

Invalid or unknown users will be reported in Failed members output.

2.1.3. Owners

Add users as owners (elevated permissions) of the team.

How to provide: Same options as Members (Dropdown, Dynamically via the Token Picker, or comma‑separated user IDs or Emails.).

Behavior:

If tenant policies prevent owner assignment, those users will appear under Failed members with details in the run history.

Tip: Use this to grant team management privileges (e.g., adding/removing members, updating settings).

When Type = Channel

Add users at the channel level.

Important: For standard channels, membership is inherited from the parent team—you cannot add individual members to a standard channel. Every team member is automatically a member of every standard channel. Use Type = Team to manage membership for standard channels. Adding individuals at the channel level applies to private (and certain shared) channels.

2.2.1. Team Id

Select the parent team of the channel.

How to provide: Dropdown, or supply Team Id dynamically via the token picker.

Why needed: Channels belong to a specific team; you must identify the team to list/select the channel.

2.2.2. Channel Id

Select the specific channel to add members to.

How to provide: Dropdown, or provide Channel Id dynamically using token Picker.

Notes:

For standard channels, individual membership cannot be managed here (inherited from the team).
For private channels, only members of the parent team can be added to the channel.

2.2.3. Members

Add users as channel members (for private/shared channels that support direct membership).

How to provide: Dropdown, dynamically via the Token Picker, or comma‑separated user IDs or Emails.

Notes:
- Users typically must already be members of the parent team to join a private channel.
- Standard channels ignore individual membership—manage at the team level instead.

2.2.4. Owners

Add users as channel owners (for channel types that support ownership, e.g., private channels).

How to provide: Dropdown, Dynamically via the Token Picker, or comma‑separated user IDs or Emails.
Notes: Tenant policies may limit who can be a channel owner; failures will surface in the outputs/run history.

When Type = Chat

Add users to a 1:1 or group chat.

2.3.1. Chat Id

Select the chat to add participants to.

How to provide: Dropdown, or provide Chat Id dynamically via the token picker.
Notes: Visibility is limited to chats the connection’s account can access. Some chat types (e.g., meeting chats) may have restrictions on adding new participants.

2.3.2. Owners

Select users to add to the chat (participants).

How to provide: Dropdown, Token Picker, or comma‑separated user IDs or Emails.
Notes: While the field label is Owners for consistency, in chats this effectively adds participants. Platform constraints may apply (e.g., only certain participants can add others depending on chat settings/policy).

General Input Tips

Dynamic values: Anywhere you see the token picker (chain icon), you can insert IDs or lists from earlier steps (e.g., a CSV list of emails from a form submission).
Multiple users: Separate entries with commas when typing manually; the picker supports multi‑select.
Validation & errors: Nonexistent users, policy blocks, or permission issues will appear under Failed members in the outputs; check the run history for details.
Idempotency: Re-adding an existing member typically results in a no‑op (reported as success or skipped, depending on the connector’s behavior).

Example: Adding New Project Members to a Microsoft Team

Scenario: Your company has just started a new project, and several employees from different departments need to collaborate within a Microsoft Team dedicated to the project. Instead of manually adding each member and assigning owners, you automate the process with the Add Members action.

Steps:

Connection – First, you connect your Microsoft Teams account. This ensures Zenphi can access your Teams, Channels, and Chats.
Type – Select Team, since you want to add members directly to a project team.
Team Id – From the dropdown, choose the project’s Microsoft Team (e.g., Marketing Campaign 2025).
Members – Add the email addresses of team members (e.g., [email protected], [email protected]). You can also pick them from the dropdown list.
Owners – Add the project manager’s email address as the owner (e.g., [email protected]). Owners will have higher privileges than members.

Result: When the flow runs, all specified members will be added to the project team, and the manager will be assigned as the owner. If some users cannot be added (e.g., incorrect email or no license), they will appear in the Failed Members output so you can take corrective action.

Updated about 7 hours ago