Why can't I see this?
Most "it's not there" questions in Structured AI are not about your role or about sharing. They're about what your organization has switched on. This page is the troubleshooter.
Four reasons, in the order to check them
1. It's switched off for your organization. Most tools are gated per account - Chat, Compare Versions, Overlay, Compare Against Control, Comment Closure, Shop Drawing Review, Spec Audit, Workflows, Organize, and the Bluebeam and ACC connectors. That's why two people at two firms see different rails. Ask us to switch it on.
2. You don't have the grant. Some capabilities are handed out per person by your org owner. Ask them before assuming it's an account-level thing.
3. It's not a rail tool any more. Custom checks appear inside the Project QAQC panel with a Custom or Shared pill, not as their own tool. Building codes are browsed from your account menu. Neither is missing; both moved.
4. You're in the Revit pane. The drawing-set tools aren't offered there at all. Open the project in the browser. See Connect Revit.
Seeing it but not being able to use it
Every gated area has two switches, and they're deliberately separate:
- Can you see it - does the tool appear at all.
- Can you run it - can you actually start work with it.
That separation is doing real work: it's how a read-only account gets the results of a comparison to look at without being able to start new ones.
So a tool you can see but can't start is not a bug and not a missing page - it's the second switch. If you need to be able to run it, ask your org owner.
Checks specifically
Check gating goes finer than tool gating. Your organization's check library can be turned on by discipline group, or check by check, so what you have is the checks you actually review for.
If a check you need isn't in your library, you have two routes: build it yourself, or tell us what you review for and we'll build it into your library.
Also worth ruling out before concluding a check is missing: review intent narrows what's recommended. A coordination-focused brief legitimately won't surface completeness checks - they're still there in the full library below the recommendations.
Grants an owner can hand out
Owners grant individual capabilities to individual members from the members table on the Dashboard. The set changes as the product grows, but it's things like code-library stewardship, project-wide check runs, and connector access for a viewer who needs to publish markups.
A grant has three states: on, off, and inherit - inherit meaning "whatever the organization's default is". Leaving someone on inherit is usually right; it means they follow the organization when the organization changes.
Per-person grant columns on the members table
When it really is about access
If the thing you can't see is a document, checklist, workflow or code book rather than a tool, it's the access model, not a feature gate - someone hasn't shared it with you yet. See How access works.
If it's a project a colleague mentioned: projects are shared with named people or organization-wide, and being in the same organization isn't by itself enough. Ask them to share it.
Talk to us - we can see what's switched on for your account and tell you in a minute. Other kinds of problem are in Troubleshooting.