Claude Team Ask Your Org: Find Answers in Shared Work
Ask Your Org helps Claude search connected company sources. Set it up around authorized access, check the cited evidence, and keep the team’s approved decisions easy to find.
Updated 5 min read
Claude Team Ask Your Org is a dedicated search project for finding cited answers across connected company sources. It needs organization setup and authorized connections. Pair that search with a shared record such as fenbs when the answer also depends on decisions, rules, and current work that the team needs across AI apps.
How do you set up the organization’s search project?
- Have an Owner open Ask Your Org and select Set up for your org.
- Choose the enabled source connections requested by the setup, including Documents and Chat; Email is optional.
- Choose the organization name and description, then finish setup.
- As a member, open the resulting Ask project and complete the connection prompts for the sources you need.
- Try a narrow question whose correct answer you can verify in the original source.
Anthropic’s enterprise search guide (opens in a new tab) documents this project on Team and Enterprise, including setup and source citations. The sidebar name can use your organization’s name. For the wider workspace setup, see the Claude Team plan guide; choosing an organization plan instead of an individual subscription belongs in the separate Team versus Max comparison.
Before adding sources, pick an everyday question with a clear owner. For example, ask which approved project brief applies to a particular launch. Starting with a question you can check reveals missing information sooner than connecting every available service and asking for a summary of the business.
What can each person actually search?
Search depends on the connections and credentials in use. Anthropic says results respect source permissions, with an important exception: a custom connector using a shared credential reaches what that credential can access. Review that boundary before adding a custom service, especially one intended for a narrower group.
A connector is a connection that lets Claude use an outside service. Anthropic’s connector guide (opens in a new tab) explains organization enablement, authentication, and action controls. Some connectors can change data as well as read it; Owners can restrict actions. Set access for the job you intend rather than treating a search request as a reason to enable every action.
For Microsoft 365, Anthropic’s security guide (opens in a new tab) describes delegated access and administrator consent. Members cannot use that connector to bypass source sharing settings. Ask the source owner to review permissions when access is wrong; copying a restricted document into a more widely available place changes who can see it.
Test with the intended participants. Choose an ordinary shared document and a document the test account should not reach. Check behavior without putting sensitive material into a test prompt. A connection working for its Owner does not establish that every teammate has appropriate access.
How should you ask a question that can be checked?
Name the project, the subject, and the kind of evidence you want. Include a date range when time matters. Ask Claude to identify missing evidence and distinguish an approved instruction from a suggestion. These are review habits: the wording helps define the task, but it cannot guarantee that every relevant source will be found.
- For a project: “Find the approved launch brief for the website refresh. Identify its owner, approval date, and any later source that changes its scope.”
- For a process: “Find the current instructions for requesting design review. Cite the steps and identify who owns the process.”
- For a disagreement: “Find sources supporting each proposed launch date. Separate proposals from approvals and tell me what remains unresolved.”
Open the cited source before relying on the answer. Check that it says what the summary suggests, applies to your team, and remains current. A discussion about a possible change can be highly relevant to search while still being the wrong authority for what you should do next.
For a workspace built around selected shared material, read Claude Projects for teams. Here, the immediate task is checking an answer found across connected sources.
What if the documents disagree or the answer is incomplete?
Treat disagreement as a useful finding. Put the conflicting claims side by side with the source dates, owners, and approval status. Ask the responsible person which instruction applies. A newer document is not automatically authoritative; it may be a draft or cover a different project.
| What you see | What to check | What to do next |
|---|---|---|
| A source is absent | Whether the connection and account can reach it. | Resolve access or ask its owner for an authorized source. |
| Two instructions conflict | Scope, approval, and the person responsible. | Keep the question open until a person settles it. |
| A summary lacks support | Whether each important claim has matching evidence. | Narrow the question and verify the underlying passage. |
| A result describes old work | Whether later decisions changed the next action. | Find the current decision and remaining task. |
When a person resolves the conflict, record their choice, its scope, and its reason in Decisions and rules. How fenbs works explains how those rules reach the assistant’s starting context instead of relying on someone to rediscover the right discussion.
Keep the answer your team agreed to follow
Use fenbs for the approved decision behind the documents and the tasks that follow from it. Record what a person chose, add any continuing rule, and save where the work stands. Connected assistants can read that shared project context before acting on a search result.
Create a free accountFree for one person · No credit card · Works with Claude, ChatGPT, Cursor and more
How do you keep a verified answer useful tomorrow?
Save the smallest durable result. A useful record might say which brief is approved, why a competing draft was rejected, and who must check the remaining issue. Include a link to the source, with enough explanation that another teammate understands its relevance without rereading the whole discussion.
Keep reference documents in the systems their owners maintain. Put a follow-up in a task when it requires work; record an ongoing instruction as a rule when a person has agreed it. Search and current work then support each other without creating another unmanaged copy of every document.
Do not assume a cited answer applies to every audience. Before forwarding a summary, check whether its recipients should see the underlying information. Finding something through your own access is a reason to review the result, not permission to distribute it more widely.
How to do this with fenbs
- Create a free account, free for one person with no credit card. For shared work, use a team kanban board and give colleagues appropriate member roles.
- Add the project that prompted the search. Save a concise context note with the relevant source links and any unresolved question.
- Record the person’s approved choice in Decisions and rules. Identify its scope and reason, keeping proposals open until a person decides.
- Connect Claude using the guide in Integrations, through MCP, a standard way for an AI app to use an outside tool, and browser sign-in.
- Ask Claude to read the project context before continuing. Save progress afterward, including the next task and anything waiting on a person.
fenbs does not replace organization-wide document search or import your Claude chats. Use Ask Your Org when finding source material is the job. Use fenbs when the team also needs the decision, rule, and next step to stay available across assistants; explore that workflow in the team brain hub.