Grant Promptless Access to Files in Private and Shared Teams Channels
Promptless can now read files attached in private and shared Microsoft Teams channels. Standard channels were already accessible. Private and shared channels were not, because Microsoft gives each of them its own separate SharePoint site.
The problem
Section titled “The problem”Private and shared channels each get their own isolated SharePoint site, separate from the team root. Microsoft exposes a channel’s site only to its members, so Promptless had no way to discover those sites at connect time. Only the team-level site appeared in the site picker.
That meant any file attached in those channels was outside Promptless’s reach. A design spec posted in a private channel was invisible to Promptless. So were a partner’s API references dropped into a shared channel. The files Promptless most needed for context were often in the channels it could not access.
What changed
Section titled “What changed”The site picker in the Microsoft Teams connection flow now lists each private and shared channel as its own selectable site. Each channel appears alongside the team-level site. You can grant Promptless read access to individual channels the same way you grant it to team-level sites.
Microsoft exposes a private or shared channel’s site only to that channel’s members. Promptless resolves available sites using the account you authenticate with at connect time. Only channels the connecting account belongs to appear in the site picker. If a channel does not appear, reconnect as a member of that channel. It then appears in the site picker.
This change only affects which attached files Promptless can read. The Promptless bot’s presence and behavior in your channels are unchanged.
Who benefits most
Section titled “Who benefits most”Teams that keep working docs in private or shared channels benefit most. If design specs, architecture decisions, or API references live there, those files can now inform Promptless’s suggestions.
Shared channels matter most for teams that collaborate externally. Your product team might run a shared channel with a partner’s engineers. Technical decisions documented there can now feed into Promptless’s context.
How to set it up
Section titled “How to set it up”Reconnecting requires the Promptless Admin role. Open the Integrations page and reconnect as an account that belongs to the private or shared channels you want to include. After reconnecting, select those channels from the site picker and follow the connection flow to complete the access grant. Selecting a site surfaces it for granting but does not grant access on its own.
If you join new private or shared channels later, reconnect again so they appear in the site picker. Then select and complete the grant for each new channel.