Discover how Timeneye seamlessly integrates with Microsoft services to enhance productivity and streamline task management. This article provides a comprehensive overview of the permissions and data access requested for each integration.
Timeneye offers seamless integration with Microsoft services to enhance productivity and streamline task management. When integrating Timeneye with Microsoft, certain permissions and data access are requested to ensure smooth functionality. Below, we outline the permissions and data requested for each integration.
In the context of software development and API (Application Programming Interface) integrations, a "scope" refers to a permission or access level granted to an application or service to interact with another system or resource on behalf of the user.
When an application integrates with a third-party service or platform (such as Microsoft services in the case of Timeneye), it needs to specify the level of access it requires to perform certain actions or retrieve specific data. These permissions are defined and requested through scopes.
1. Invite users from Microsoft Azure Tenant
Requested Scopes:
-
User.ReadBasic.All: This scope allows Timeneye to read basic profile information of all users in the Azure tenant. It includes details such as name, email address, and profile picture.
-
offline_access: This scope grants Timeneye access to refresh tokens for long-term access to Microsoft services without requiring the user to re-authenticate frequently.
Purpose:
-
Timeneye utilizes these permissions to facilitate the process of inviting users from the Microsoft Azure tenant. By accessing basic user profiles, Timeneye can seamlessly onboard users into the system.
2. Outlook Calendar Integration
Requested Scopes:
-
Calendars.Read: This scope enables Timeneye to read events from all calendars in the user's Outlook account.
-
offline_access: Similar to before, this scope allows Timeneye to maintain long-term access to the user's Outlook calendar without constant re-authentication.
Purpose:
-
With these permissions, Timeneye can synchronize events from the user's Outlook calendar, providing visibility into scheduled activities and enabling efficient time tracking through suggested time entries.
3. Microsoft Planner Integration
Requested Scopes:
-
Tasks.Read: This scope grants Timeneye read-only access to tasks within Microsoft Planner.
-
User.Read: Allows Timeneye to read the profile of the signed-in user.
-
User.ReadBasic.All: As in the previous integration, this scope enables Timeneye to access basic profile information of all users in the Azure tenant.
-
offline_access: Maintains persistent access to Planner and user profiles without frequent re-authentication.
Purpose:
-
Timeneye utilizes these permissions to integrate with Microsoft Planner, facilitating task management. By accessing tasks and user profiles, Timeneye can provide comprehensive insights and time tracking capabilities.
4. Microsoft To-Do Integration
Requested Scopes:
-
Tasks.ReadWrite: This scope allows Timeneye to read and write tasks in the user's Microsoft To-Do list.
-
offline_access: Provides continuous access to Microsoft To-Do without the need for frequent re-authentication.
Purpose:
-
With these permissions, Timeneye seamlessly integrates with Microsoft To-Do, enabling users to manage tasks efficiently. Users can track time spent on tasks directly from their To-Do lists.
4. Microsoft Teams Calls Integration
Requested Scopes:
-
CallRecords.Read.All: This scope grants Timeneye privileged access to callRecords for every call and online meeting within your organization, including calls to and from external phone numbers. This includes potentially sensitive details about who participated in the call, as well as technical information pertaining to these calls and meetings that can be used for network troubleshooting, such as IP addresses, device details, and other network information.
This scope requires Admin consent.
Purpose:
-
With these permissions, Timeneye integrates with Microsoft Teams to enhance user experience by providing suggestions related to Video/Audio calls made through Teams. If the user enabled the Outlook calendar integration, the call is associated with an Outlook Calendar event and its actual duration differs from the scheduled time, the event duration is automatically updated to reflect the true length of the call.
Privacy and Security:
-
Data Protection: Timeneye respects user privacy and complies with data protection regulations. All data accessed from Microsoft services is handled securely and used solely for integration purposes.
-
Authentication: Timeneye employs secure authentication mechanisms to ensure that only authorized users can access Microsoft integrations.
-
Data Encryption: Any data transmitted between Timeneye and Microsoft services is encrypted to prevent unauthorized access.
By granting these permissions, users can enjoy the full benefits of Timeneye's integration with Microsoft services, enhancing productivity and task management efficiency while ensuring data security and privacy. If you have any concerns or require further assistance, please don't hesitate to contact our support team.