Powell Teams bot notifications allow admins and IT to delegate a part of the Microsoft Teams governance to end users and team owners enhancing security and keeping your tenant in a good health.
Table of content
- Introduction & help center
- Notification configuration
- Approbation notifications
- Expired teams notifications
- Inactive teams notifications
Introduction & help center
The Powell Teams bot is now available into the product. You can access to the product, display an product introduction video or ask for help. The help center articles and content are available to read directly into the chat interface.
First of all, the feature needs to be activated in the additional configuration page in the administration section of the menu.
For each scenario of the bot, you are able to activate or desactive the notifications. It allow you to choose the use case you find usefull for your needs.
Powell Teams application will then send cards in the Microsoft Teams chat to different type of users. One card is sent for each team concerned by a scenario. One an action has been taken, then the card is replaced by a confirmation card.
Cards are sent by default in the connected user langage Microsoft Teams setting if that langage is supported by Powell Teams (French, English, German, Japaneese, Corean or Russian).
The default langage configuration possibility on this page allow you to define a default langage for users that are not using one of those idiom on their Microsoft Teams environment.
All cards that have been sent before the switch off of any bot use case are still available for your end-users.
Sign in experience
The first interaction of your end-users with any Microsoft bot needs them to be registered. So when your users interact with their first Powell Teams card they have to sign in first.
After clicking on any action of a card, they will receive the following Microsoft sign in card:
When users click on "sign in" then, no confirmation message is sent to him/her. And they will then have to click again on the action wanted on the Powell Teams card.
Notice that once signed in, there is no need to do it again.
Approbation bot notifications
Thanks to this use case, the approvers of team creation request with approvals are able to be notified without even opening Powell Teams.
All the approvers receive a card asking them to approve or refuse the request. They are also able to open the detail of the request if they want to have more information about the request. Once the team approved by any way (bot, interface or API),
Once the approbation has been done (with the bot, in the Powell Teams interface or even API), then the requester will receive the information about the status of his request. Here for exemple, a refused team creation request:
Expired teams bot notifications
After the report generation made each Saturday, Powell Teams will send to team owners concerned by the "expired teams" report a card letting them know about their team situation.
Owners are able to take actions on their teams. They can archive the team, delete it or extend the expiration date from the same number of days initially configured in the team's template.
Once the action, taken, the owner received a confirmation, for exemple here, the expiration date has been changed:
Inactive teams bot notifications
After the report generation made each Saturday, Powell Teams will send to team owners concerned by the "Inactive teams" report a card letting them know about their team situation.
Owners are able to take actions on their teams. They can archive the team or delete it.
Once the action, taken, the owner received a confirmation, for exemple here, the team has been archived: