Welcome to our Knowledge Base

Understanding Permissions and Consents in VisPlan: A User Guide

As a user of VisPlan, it’s essential to understand the permissions requested by our application within Microsoft Teams. Permissions enable VisPlan to access specific features and functionalities, enhancing your collaborative experience. When prompted to grant permissions, this article describes which permissions VisPlan requires.

In some organizations users are not allowed to consent and grant permissions to apps in Teams, please contact your local Microsoft 365 administrator to help you install and consent to use VisPlan

What are Permissions?

Permissions are access rights that VisPlan and other apps requests to perform specific tasks within Microsoft Teams. They allow the app to interact with different features and Microsoft services effectively.

How Will You Be Prompted?

When you first use VisPlan within Microsoft Teams, you’ll encounter permission prompts detailing the access VisPlan requires. You’ll have the opportunity to review these permissions before granting access. This ensures transparency and empowers you to make informed decisions about your data.

Why Are Permissions Needed?

Permissions are necessary for VisPlan to function optimally and provide you with a seamless experience within Microsoft Teams. By granting the required permissions, you enable VisPlan to access the resources it needs to enhance collaboration and productivity.

Please note that certain permissions related to DevOps, Planner, and Project may only occur if specific features are enabled in your VisPlan plan. Additionally, advanced features like DevOps and Project may only be available in higher license tiers.

Below, we detail the purposes behind each permission requested by VisPlan:


  • Microsoft Graph (Team.ReadBasic.All, Channel.ReadBasic.All):
    • Purpose: These permissions enable VisPlan to determine your team and channel memberships.
    • Functionality: By understanding your memberships, VisPlan can display relevant plans accessible to you and allow smooth navigation between them.
  • Microsoft Graph (User.Read, User.ReadBasic.All):
    • Purpose: These permissions are fundamental for user interaction and profile display within VisPlan.
    • Functionality: User.Read allows basic user profile information retrieval, while User.ReadBasic.All facilitates displaying user photos and active status within the VisPlan interface.
  • SharePoint (AllSites.Manage):
    • Purpose: This permission allows VisPlan to create, write, and read tables within your organization’s SharePoint site associated with the team.
    • Functionality: It enables storage of plan-specific information securely within your SharePoint environment, ensuring data integrity and accessibility.


  • Azure DevOps (user_impersonation):
    • Purpose: This permission is requested when connecting VisPlan to Azure DevOps work items.
    • Functionality: It enables seamless integration with Azure DevOps services, facilitating efficient management of work items within VisPlan when DevOps features are enabled in your plan.
  • Microsoft Graph (Tasks.ReadWrite):
    • Purpose: This permission is crucial when VisPlan interacts with Microsoft Planner.
    • Functionality: It enables synchronization of actions and tasks between VisPlan and Microsoft Planner, ensuring seamless coordination and task management when Planner features are enabled in your plan.
  • SharePoint (Project.Read):
    • Purpose: Specifically used for VisPlans connected to Microsoft Project Online.
    • Functionality: It enables VisPlan to read statuses from objects in Microsoft Project, facilitating comprehensive project tracking and management within the VisPlan interface when Project features are enabled in your plan.

More Information

For more information on Microsoft Teams permissions and how they impact your experience, please refer to the official Microsoft documentation:

Comments are closed.