PERMISSIONS

What this covers: querying the PERMISSIONS entity (31 rows; label field FILE_ID).

Why you need it: list, fetch, count, and aggregate permissions; answer "which/how many/how much" questions.

Syntax:

• LIST PERMISSIONS [WHERE ...] [ORDER BY <FIELD> [DESC]] [LIMIT n] [OFFSET n]
• GET PERMISSIONS "<file_id>"
• COUNT PERMISSIONS [BY <FIELD>] [WHERE ...]
• RESOLVE PERMISSIONS "<name>"
• Operators: IS, IS_NOT, CONTAINS, GT, GTE, LT, LTE; combine with AND / OR.

Returns: JSON rows plus _meta (provenance, epoch, related follow-up queries, hints).

Workflows:

1. COUNT PERMISSIONS - size the data before listing.

2. COUNT PERMISSIONS BY PRINCIPAL then LIST PERMISSIONS WHERE PRINCIPAL IS "acme.com" LIMIT 10 - segment, then drill in.

3. RESOLVE PERMISSIONS "<fuzzy name>" then GET PERMISSIONS "<canonical>" - resolve before fetching when a name lookup misses.

Constraints:

• Filter only on fields listed in HELP SCHEMA; unknown fields are hard errors.
• Enum values are exact strings (e.g. PRINCIPAL: acme.com, alice@acme.com, anyone, bob@acme.com, carol@acme.com, dana@vendor.io, eng@acme.com).
• Default LIMIT is 100; count in a LIST response is not the true total.