> For the complete documentation index, see [llms.txt](https://rpa-connect.gitbook.io/rpa-connect/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rpa-connect.gitbook.io/rpa-connect/en-us/interaction-channels/instance-management-in-teams-and-the-portal/activity-in-microsoft-teams.md).

# Activity in Microsoft Teams

The main difference between Teams and the RPA Connect Portal lies in the *Activity* tab, as its functionality focuses on the notifications we previously discussed when addressing the [integration with Microsoft Entra ID](https://github.com/entaconsulting/rpa-connect-docs/blob/gitbook-transfer-data/english/administracion/integracion-con-microsoft-entra-id/README.md). When a new form instance is assigned to you, the application will send you a pop-up notification and create a new chat message in the ***Activity*** tab.

<figure><img src="/files/MqTAjJdfi3SM7YonqyYt" alt=""><figcaption><p>Notification in Microsoft Teams</p></figcaption></figure>

On this card, you will see:

* The title of the form, which is set based on the instance data.
* The stage, if it is part of a workflow, indicating the current ***stage*** of the process.
* A personalized message for each user or form with details of the expected action for that request. To configure it, you can use the ***notificationMessage*** parameter when creating actions with BluePrism, as we previously saw for the [***Create Stage*** function](https://github.com/entaconsulting/rpa-connect-docs/blob/gitbook-transfer-data/english/blueprism/conexion-con-blueprism/otras-acciones/acciones-vinculadas-a-stages.md#create-stage).
* A link to the ***Inbox***, where you can review the form instance.