Choose when the rule runs
The After rules do not decide whether someone gets access.
Set up a rule
- Tell Zite which table or connected system to check, which field contains the email address, and what should happen when no match is found.
- Open Settings → Login → Sign-in. Review Custom access rules, which appears when your app has rules.
- Use Chat about this to change them.
- Publish, then test the live sign-in flow with both an allowed and a disallowed person.
Only let people whose email is in the Members table sign up. Refuse anyone else. If someone is removed from Members, block future sign-ins and sign them out at the next session check.Use Preview as user to check the app experience, but test the actual login rules on the published app too.
Pair rules with sign-up settings
For a roster-based portal, use Invite only plus a rule that admits people on your roster. Add Before sign in and Session check rules if removing someone from the roster should also end their access. A database row alone does not verify someone’s identity. They still sign in using the app’s configured method, such as a magic link or Google.If the roster is unavailable
If a rule errors or takes too long, Zite falls back to its normal access behavior. A failed rule is not an automatic refusal.- New sign-ups: pairing the roster with Invite only keeps uninvited newcomers out when the roster cannot be checked.
- Existing users: a failed check may let them continue under the normal app permissions.
- Session checks: results are cached for a few minutes, so roster changes are not instant.