The most common reasons for Claude integrations in the workspace are "admin has been enabled, but you still can't use it": you haven't done third-party authentication yet, you're not currently using a private project, or you're using a chat with synchronized content to do something that isn't supported, such as continuing to share.
Many teams use Claude integrations for the first time and think that if the administrator clicks Enable in the background, members should be automatically available. Actually not. Anthropic's current mechanism is that the organization administrator first opens the integration capability to members, and then each member has to connect to the corresponding third-party account before Claude can read the content according to your permissions. In other words, the organization switch only solves "allowed use", not "you are connected".
If you encounter "I can see it in the menu, but I really can't use it", press this line:
1. Go to the plus menu in the bottom left corner of Settings or chat to confirm that you have completed the verification in person.
2. Make sure you have access to the original third-party content so that Claude doesn't overstep your authority by reading files that you can't see in the first place.
3. If you are using it in Projects, make sure it is a private project. Many integrations are currently only available in private projects.
4. If you already have synced content in this chat, don't be surprised if you fail to share it, Claude has restrictions on this type of chat.
Why is the platform so troublesome? Because integration is essentially pulling third-party data into Claude for use. Organization-level permission, user-level authentication, and original system permission verification must all be aligned to be both available and not overstepping.
Many users will keep staring at "Is Claude broken by itself" after getting stuck, but in fact, more often than not, the process is not complete. In particular, private projects are the most easily overlooked. If you are looking for a half-day function in an ordinary shared project, it may not be that it is not open, but that this scenario is not supported in the first place.
If you just want to quickly verify that the integration is working properly, the easiest way is not to just throw away complex tasks, but to add a document or repository that you have determined to have permissions in a private project, and then do the most basic read test. This is the easiest way to distinguish whether it's an authentication issue, a permission issue, or a wrong project type.
Therefore, the administrator is "open" does not mean that you are "usable". Claude integrations are often not yet valid for your own certification and the right use cases.
