Tenancy You Don't Have to Think About: Every Task Route Checks Workspace Membership
Every board, column, and task lookup in Tasks is gated on workspace membership — an ID alone is never enough to reach data outside your workspace.
If you're evaluating whether an employee could reach another team's board just by guessing or discovering an ID, here's the direct answer for Tasks: no, and it's enforced at the route level, not left to the client.
How it's enforced
Every by-ID route in Tasks — fetching a specific board, column, or task — checks the caller's workspace membership before returning anything. A board, column, or task is only reachable if the person asking belongs to the workspace it belongs to, whether that relationship is direct or transitive through the board it sits under. Knowing or guessing an ID isn't sufficient on its own; the membership check happens regardless.
Why we're stating this plainly
This is the kind of question an IT buyer or admin asks during procurement — can one employee see another team's data by URL-guessing — and it deserves a direct answer rather than a general assurance. Tasks enforces this pattern consistently across its routes, not as a one-off fix on a route someone happened to flag.
Part of a platform-wide pattern
This isn't unique to Tasks — the same "by-ID routes need a tenancy guard" discipline is enforced consistently across the platform, checked automatically as part of our standard guardrails rather than relying on each team to remember it independently.
If tenant isolation is on your evaluation checklist, this is the concrete mechanism behind the answer: membership is checked on every request that resolves an ID, every time.