Wherever a rule is needed (a table’s five actions, a bucket’s five rules, a channel’s subscribe and publish, a route, a subscription), Studio shows the same rule picker.

​
The choices

​
Lists mean “all”

Choose List and add rules: Signed-in users, Users with role editor, Signed in with 2FA. The request passes only for a signed-in editor who completed a second step. For “any of” (an owner or an admin), use a Custom condition with Any of, containing Owns the record and Has role.

​
Mixing named rules and conditions

A list can mix: This environment → team_member and Users with role editor together means “a team member who is an editor”.

​
Unknown names

A rule that names something that doesn’t exist is refused when you save. Studio warns first: “x” is not a policy in this environment, so this action will be refused when you save. Named rules belong to an environment: a rule created in development must exist in production too (promote it).

​
Choosing well

  • Use built-ins for most cases.
  • Use named rules for anything used more than once, or that a teammate should be able to read and change in one place.
  • Use custom conditions for one-offs.
  • Use List to add a requirement (“and also 2FA”).

Named rules

Create saved rules.

Shortcuts

What each shortcut means.