What are the permissions requested by Teamflect
The Microsoft Graph API is a comprehensive service provided by Microsoft that allows developers to access a wide range of data and functionalities across various Microsoft 365 services, such as Outlook, SharePoint, and Teams. It serves as a unified endpoint to interact with these services programmatically. Third-party applications require Graph API permissions to securely access and retrieve data stored within Microsoft 365, ensuring that only authorized applications can read, modify, or manage data on behalf of users. These permissions establish a secure and controlled framework for accessing and utilizing Microsoft 365 data within external applications.
Teamflect, as an application designed for Microsoft 365, requires specific permissions from the Graph API to effectively integrate and function within the Microsoft 365 ecosystem. These permissions enable Teamflect to access and interact with relevant data residing in Microsoft 365 services. By requesting and obtaining these permissions, Teamflect ensures a secure and authorized connection to the necessary data sources, allowing users of the application to seamlessly collaborate, communicate, and manage their Microsoft 365 resources within the Teamflect environment.
Here's an explanation of each permission:
User.Read: This permission allows Teamflect to read the basic profile information of the signed-in user, such as their display name and email address. It helps in identifying and associating the user within the application.
User.ReadBasic.All: This permission grants Teamflect the ability to read basic profile information of all users in the organization. This permission is used when a user opens the profile page of another user.
People.Read: This permission enables Teamflect to access the user's contacts and organizational hierarchy, allowing the application to retrieve and display information about the user's colleagues and their reporting structure. This permission is used to recommend potential feedback providers, org-chart in user profiles.
Calendars.Read: With this permission, Teamflect can access the user's calendar events. It allows the application to retrieve information about the user's appointments, meetings, and other calendar-related data. With this permissions, Teamflect is able to identify the 1-on-1 and team meetings.
Presence.Read.All: This permission grants Teamflect the ability to read and display the presence status of all users in the organization. Presence status indicates whether a user is available, busy, away, or offline, and it helps in displaying real-time availability information within the application.
Tasks.ReadWrite: This optional permission enables Teamflect to read and write tasks on behalf of the user. It allows the application to retrieve tasks from the user's task lists and create, update, or delete tasks as needed. This permission is used when the To Do integration of Teamflect is enabled.
Directory.Read.All: This permission provides Teamflect with read access to the organization's directory, including user and group information. It allows the application to retrieve details about users, such as their roles, department, and manager, as well as retrieve information about groups within the organization. Teamflect uses this permission to allow end-users to related their OKRs to their Microsoft Teams teams.
These permissions collectively enable Teamflect to securely access and utilize relevant data and functionalities within Microsoft 365, ensuring a seamless and integrated experience for the application users.
The privacy and security of customer data are essential considerations for any reputable application provider. In the case of Teamflect or any other third-party application, it is crucial to emphasize that employees or third parties do not have standing access to customer data. The permissions granted are solely intended to enable the core functionalities of the application, ensuring a seamless user experience.
The implementation of robust data protection measures is further reinforced by regulatory frameworks, such as the General Data Protection Regulation (GDPR) in the European Union. Such regulations impose strict guidelines on data handling and require companies to prioritize the security and privacy of customer data. Failure to comply with these regulations can result in severe penalties, incentivizing application providers to maintain high standards of data privacy.