file upload option disappearing in teams bot
We have Teams bot (we're the developer). When users first start teams, they have the file upload option available under the + button next to the type a message box. However, shortly afterwards, this option disappears. Not all users, just some. Seems to occur for both Mac and Windows users. Our manifest looks like this: { "$schema": "https://developer.microsoft.com/en-us/json-schemas/teams/v1.19/MicrosoftTeams.schema.json", "manifestVersion": "1.19", "version": "1.0.7", "id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", "developer": { "name": "example", "websiteUrl": "https://www.example.com", "privacyUrl": "https://www.example.com/privacy", "termsOfUseUrl": "https://www.example.com/privacy" }, "icons": { "outline": "example_mono.png", "color": "example_portrait.png" }, "name": { "short": "example", "full": "example, your digital assistant" }, "description": { "short": "example is a digital AI assistant designed to streamline your workflow.", "full": "example is an advanced AI-powered professional assistant developed by example, crafted to enhance productivity and efficiency in the workplace. With a focus on accuracy and a professional demeanor, example assists with information retrieval, scheduling, communication, and various tasks, ensuring that you have more time to focus on what matters most in your business." }, "accentColor": "#fb9745", "bots": [ { "botId": "yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy", "scopes": [ "personal" ], "isNotificationOnly": false, "supportsFiles": true, "commandLists": [ { "scopes": [ "personal", "team" ], "commands": [ { "title": "New", "description": "Starts a new conversation" } ] } ] } ], "permissions": [ "identity", "messageTeamMembers" ], "webApplicationInfo": { "id": "yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy", "resource": "https://RscBasedStoreApp" }, "validDomains": [ "*.ngrok-free.app", "*.ngrok.app", "exampledev.ngrok.app" ] } ``` As far as I can see from the current manifest schema, the bot needs no other scopes. Is this a known bug or are we screwing something up with the config? Any help appreciated!
Distribution list vs file storage
We're having a bit of a disagreement within our company, wanted to get some feedback. On one hand, a higher-up became frustrated when he went looking for a file related to a client, and found 3-4 different Sharepoint sites with the client's name. This was usually the result of different departments creating their own Teams/Sharepoints for the same client. His feeling is every client should only have a single Sharepoint. Also, it should be attached to Teams so that Teams users can easily stay in Teams to access the files. On the other hand, the IT department wants to create Teams (which will inevitably have a Sharepoint) for distribution lists, as it will allow for more modern technology to be used when compared to using traditional distribution lists. But then that causes problems with the above, as it will result in more confusion about where a file might be located. The single email that comes with the Team/Sharepoint isn't really usable because both Creative and Customer Service are storing files there, but Creative doesn't want to get emails intended just for Customer Service and vice-versa. So it would have to be additional Teams/Sharepoints for the client. Nobody thinks we can just procedurally keep people from storing files in the Teams/Sharepoints that were really just intended to be a distribution group, regardless of special naming conventions or whatnot. How do other people handle the distribution list vs file storage issue?
Can I restrict certain Team Members to be 'Read Only' for files, whilst being able to access Posts?
Hi, Any advice would be much appreciated on this as I've been going round in circles and I don't know how best to resolve it, or if there's another way around it. Essentially what I am wanting is to be able to add someone within my organisation as a member of a Team (members have edit access by default, as most people require this) but, rather than them being a full member, I just want them to have read only access to the files area. So we would almost like to have - Team Owners (can do everything) Team Members (edit access) Guests (can see posts but read only access to files) When adding someone via Teams we only have the Owner / Member choice, with no way to restrict in in finer detail on a per-person basis. I have tried using Sharepoint permissions to drill into the 'Members' group but - as they were added via Teams - it groups them together as a 365 managed group and doesn't let me amend individual user permissions. Is there a clever way to do this? Or a different way of adding people so that they can both have read-only access to files and also see the posts area? Many thanks in advance!
File attachment issue with custom apps
Hi there, my org is currently on public preview and the latest version is 25017.203.3370.1174. We are running few chatbot apps withing the org and since the updates, we see that the file attachment option in our chatbot app is either disabled for everyone or inconstant for few users. Checked the manifest and mad suer the file operations attribute is set to "true". No idea what's causing this issue!
Some channels are not showing up in the MOVE TO list of channels under the same Team
I am copying files from several standalone teams to channels under a single team. I have access to all the channels under the single team but for some reason, they do not all show up in the choices for COPY TO. Anyone know how to fix this or why? I am referring to the Quick Access list that pops up when using MOVE TO from one Team Files to another Team Channel.
