How It Works
You define rules that tell Gately which URLs to protect and who can access them. When someone tries to visit a protected URL, Gately checks if they meet the requirements — and redirects them if they don’t.Creating a Gated Content Rule
Set the URL pattern
Enter the URL or path you want to protect. Choose a matching rule — contains, exact, starts with, ends with, or regex.
Choose an access type
Select who can access this content — by plan, by authentication, both, or admin only.
Set the redirect URL
Enter the URL to send users to if they don’t have access — usually your login or upgrade page.
Access Types
| Type | Who can access |
|---|---|
| Plan Required | Members on one or more specific plans |
| Authentication Required | Any logged-in member |
| Both | Logged-in members on a specific plan |
| Admin Only | Specific email addresses you define |
URL Matching
| Rule | Example | Matches |
|---|---|---|
| Contains | /members | Any URL with /members in it |
| Exact | /dashboard | Only /dashboard exactly |
| Starts With | /premium/ | Any URL starting with /premium/ |
| Ends With | /pro | Any URL ending with /pro |
| Regex | /course/[0-9]+ | Pattern-based matching |
Admin Only Access
The Admin Only access type lets you restrict content to a specific list of email addresses — useful for internal pages, beta features, or team-only content.Tips
Protect a whole section
Protect a whole section
Use Starts With to protect an entire section of your site at once — for example,
/members/ covers all pages under that path.Combine with Redirect Rules
Combine with Redirect Rules
Set up a Redirect Rule for Access Denied to send users to a helpful upgrade or login page instead of a blank error.
Test your rules
Test your rules
After saving a rule, open the URL in an incognito window to verify the redirect works as expected.