Repsly has migrated legacy Visibility Settings for forms into the Rule Builder.
This update preserves all existing visibility behavior while moving it into a single, modern rule-based framework - giving admins more flexibility, clearer visibility logic, and less manual maintenance.
There is no action required. All existing visibility settings are automatically converted into equivalent rules.
What’s Changing?
Previously, form visibility was configured in separate sections:
By representatives
By custom representative attributes
By teams
By places (place tags)
These controls now live inside the Rule Builder as structured rules:
| Legacy Setting | New Rule |
|---|---|
| By representatives | Visible by Representatives |
| By custom rep attributes | Included in Visible by Representatives |
| By teams | Visible by Teams |
| By places (place tags) | Visible on Places |
All visibility logic is now managed in one consistent location.
Why This Matters
For Admins managing multi-team, multi-form programs, this migration provides:
✅ One place to manage visibility
All form visibility logic now lives in the Rule Builder.
✅ Safer, more precise control
Clear AND/OR logic ensures forms only appear where intended.
✅ Scalable configuration
Target by representatives, teams, place tags, place names, and territories - all in a structured framework.
✅ Easier auditing
The Form Templates list now shows:
Whether visibility rules are applied
The total rule count
A clear rule summary in the sidebar
How the New Rules Work
1️⃣ Visible by Representatives Rule
Replaces: By representatives and By custom representative attributes
Admins can:
Select individual representatives
Add representative attribute filters (e.g., role, employment type)
Logic inside the rule:
Selected reps AND attribute filters must match.
Example:
Visible by Representatives:
10 named reps
Employment Type = Full-Time
This means the form is visible only to reps who are both selected and match the attribute filter.
2️⃣ Visible by Teams Rule
Replaces: By teams
Admins can:
Select one or more teams using the searchable multi-select picker
Logic inside the rule:
Selected teams use OR logic
(If a rep is in any selected team, they can see the form.)
When stacked with other rules:
Rules combine using AND logic
Example:
Visible by Teams: Team A OR Team B
AND Date Rule: Jan 1–Jan 31
If all teams were previously selected, no rule is created — behavior remains unchanged.
3️⃣ Visible on Places Rule
Replaces and expands: By places (place tags)
Admins can now target forms using:
Place tags
Place names
Territories (if enabled)
All within a single rule.
Logic inside the rule:
Place tags, names, and territories combine using OR logic.
Example:
Visible if place matches ANY of:
3 place tags
5 place names
2 territories
Migration Behavior
Existing place tags are preserved in the new rule.
If “All place tags” were selected previously, no rule is created (since that means visible everywhere).
Place names and territories start empty unless configured.
Rule Stacking Logic (Important)
Across rule types, rules combine using AND logic.
Example:
Visible by Representatives
AND Visible by Teams
AND Visible on Places
AND Date Rule
All conditions must be met for the form to appear.
No Rule = No Restriction
If no rule is applied (e.g., no place rule):
👉 The form is visible in all places.
Unlike legacy settings, where “All” was explicitly selected, now the absence of a rule means no restriction.
Only adding a rule introduces limitations.
What Happens During Migration?
When migration is enabled:
Existing visibility settings are automatically converted into equivalent rules.
Behavior remains unchanged.
No action is required from admins.
Forms without restrictions remain unrestricted.
Admins can immediately edit migrated rules in the Rule Builder.
Where to Find It
Web (Admin):
-
Go to Forms. Open a Form Template.
-
Navigate to the Rule Builder.
3. The left sidebar displays a readable summary of each visibility rule applied.
4. The Visibility Status column makes it easy to see whether a form is currently Visible, Hidden, or Upcoming based on its date rules and how many rules are set for a form.
Benefits for Large Retail Programs
Admins gain:
Reduced manual work
Fewer visibility errors
Clearer auditing
A scalable foundation for future automation
Rollout & Availability
Available on Web (Admin)
Migrated automatically for existing forms
Get familiar with other Rules