Conditions page: mention that conditions don't reduce what Check reads

Open Beginner friendly
#1,415 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

@NopeCharon is already working on this.

Since Nov 9, 2026.

  • #1421 by @NopeCharon — open

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
78/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Domain
documentation

Research direction

The change belongs in the Limitations section of the Conditions page at openfga.dev/docs/modeling/conditions, so find that page's source file in the docs repository. Add the suggested paragraph from the issue, keeping its link to the Multi-tenant SaaS use case, and check that the link resolves in the local docs build. Done when the paragraph appears in the Limitations section and the site builds without broken links.

Written by the indexing model from the issue text.

Description

Hi! The Conditions page explains the use cases and limits well. One thing we learned the hard way: a condition is evaluated after OpenFGA reads the tuples, so it doesn't reduce how many tuples a Check reads.

That's fine for time windows or IP rules. But if a condition is used to pick one tuple out of many, for example an org id on a relation shared by every org, each Check reads all of them first. In our case p95 went from 26 ms to about 1.5 s as that relation grew from ~1,300 to ~67,000 tuples (details in openfga/openfga#3380).

Suggested note for the Limitations section:

Conditions are checked after tuples are read, so they don't reduce how many tuples a Check reads. If a condition is used to pick one tuple out of many (for example, one per tenant on a shared relation), consider giving each tenant its own objects instead. See Multi-tenant SaaS.

Happy to open a PR if that's easier.

Dominant language
MDX
Stars
52
Forks
110
Avg merge
2d 12h
Merged PRs (30d)
21

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openfga/openfga.dev

All issues in openfga/openfga.dev

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.