About this article
This article explains the necessary permissions Templafy requests when the Teams App Connector is configured and accessed.
About the Requested Permissions
To use the Teams App Connector, Templafy requires several scopes, or delegated permissions from the Microsoft Graph API. This means that any permission given is on behalf of the signed in user, so Templafy will never be able to access anything that the current signed in user can't access.
- ChatMessage.Send - This allows Templafy to send a message to the Teams chat on behalf of the signed in user when the app connector is added as a tab. It also allows Templafy to post message in the chat when a document is created / added
- Chat.ReadBasic - This allows Templafy to see members of the Teams chat in order to share documents
- ChannelMessage.Send-This allows Templafy to send a message to the Teams channel on behalf of the signed in user when the app connector is added as a tab. It also allows Templafy to post message in the channel when a document is created / added
- Files.ReadWrite.All - This allows Templafy to create and add documents to the SharePoint site associated with the Teams channel it has been added to.
- User.ReadBasic.All - This allows Templafy to get the email address of the user in order for Templafy to identify the signed-in user
- User.Read - This allows Templafy to access basic user profile information.
The Templafy Teams App connector also requests four OpenID Connect Scopes
How to Grant Consent for Permissions
In order to Grant Consent, an Office 365 admin should search for Templafy under the Apps section of teams. In the Templafy app overview, click on