Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE] New cmdlet Set-PnPTeamsChannelUser #1841

Closed
milanholemans opened this issue May 5, 2022 · 2 comments · Fixed by #1865
Closed

[FEATURE] New cmdlet Set-PnPTeamsChannelUser #1841

milanholemans opened this issue May 5, 2022 · 2 comments · Fixed by #1865
Labels
enhancement New feature or request

Comments

@milanholemans
Copy link
Contributor

milanholemans commented May 5, 2022

After the creation of Add-PnPTeamsChannelUser, Get-PnPTeamsChannelUser and Remove-PnPTeamsChannelUser, we miss the last CRUD cmdlet: Set-PnPTeamsChannelUser.

This cmdlet can update the role of a user in a private channel. Valid roles: Owner, Member.

Describe the solution you'd like
Set-PnPTeamsChannelUser -Team "My Team" -Channel "My Channel" -Identity [email protected] -Role Owner

Describe alternatives you've considered
Remove the user first by using Remove-PnPTeamsChannelMember and then readd the user using Add-PnPTeamsChannelMember.

Additional context
Cmdlet parameters:

Parameter Required Description
Team Yes Specify the group id, mailNickname or display name of the team to use.
Channel Yes Specify id or name of the channel to use.
Identity Yes Specify membership id, UPN or user ID of the channel member.
Role Yes Specify the role of the user. Valid roles: Owner, Member.
@milanholemans milanholemans added the enhancement New feature or request label May 5, 2022
@milanholemans
Copy link
Contributor Author

I'm willing to work on this one.

@gautamdsheth
Copy link
Collaborator

Go for it !! All yours 😊🙏🔥

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants