
Roles & Access
Part of Team communication integrations
Reviewing what an installed Teams chat app can access
Inspect an installed chat app’s scopes, consent and space access, then decide whether each permission still fits its purpose.
undefined
For an installed Teams chat app, review the permissions it requests, the description that goes with each one, and how that access is approved. Record whether the access is app-only, without a signed-in user, or delegated, on behalf of a user. Then decide whether the access the app holds still fits its purpose.
In Teams admin centre, Manage apps flags permissions that need consent. View details shows the permissions and access to organisational information that the app requests.
Record the installation you can verify
Record the app and publisher, who installed or approved it, its business purpose and its known installation location. Compare its permissions with the work it still needs to do, rather than judging access by the messages it visibly posts.
Look for the permission name Chat.ReadBasic.WhereInstalled and its description. It allows the app to read names and members of one-to-one and group chats where the associated Teams app is installed, without a signed-in user.
The permission applies to all one-to-one and group chats where the associated Teams app is installed. Record an installation location only when you can verify it.
Key permissions for Teams chat apps
- Permission name
- Chat.ReadBasic.WhereInstalled
- Access type
- App-only (no signed-in user)
- Scope
- One-to-one and group chats where the app is installed
Check the permission and consent route
For custom and third-party apps, open Teams admin centre > Teams apps > Manage apps. The Permissions column flags apps with permissions that need consent; View details shows the permissions and access requested.
Only Global Administrators can grant consent to requested Graph permissions on behalf of all users. Teams Administrators can view the required permissions, and the option to view details and grant consent applies to custom and third-party apps, not Microsoft-provided apps.
Read each permission description before consent, because granting consent allows an app to access organisational information. A user or administrator must grant a permission, and the org-wide route names the role that may approve it on behalf of all users.
Check whether access is delegated, on behalf of a user, or app-only, without a user. The description for Chat.ReadBasic.WhereInstalled says that permission can be used without a signed-in user, so the access it grants is not tied to one person.
Compare permissions requested after an update with the app’s approved purpose. Review the app again when its requested permissions change.
App-only vs delegated access in Teams apps
- App-only accessNo signed-in user required. Access granted directly to the app, e.g., `Chat.ReadBasic.WhereInstalled`.
- Delegated accessOn behalf of a user. Requires user consent and is tied to an individual account.
Record the decision
For each significant permission, note the work it enables and who accepted the access, if known. Investigate grants that are unexplained, no longer needed or wider than the app’s purpose.
Decide whether the access still fits the app’s recorded purpose and whether the work it supports is still needed. If it does not, decide whether to keep using the app with that access.
Use one register entry per app: app and publisher; known installation location or unverified; permission and access description; access mode or account, if known; purpose; decision; business owner; review date; and next action. Review again when the purpose, publisher, integration account or requested permissions change.



