What’s Changing?
Today, “Tags” in Snapfix (for example: Location, Equipment, Category) are managed in each Group. This has worked well for flexibility, but it can create duplication and extra work when the same Tags are needed across multiple Groups.
We’re introducing Account-level Tags, which means:
• Tags can be created once and shared across all Groups.
• Group Admins can still restrict which Tags are visible in their Group.
• Managing Tags is easier, cleaner, and consistent across your account.
To help everyone move to this new system, Snapfix will run an automatic migration.
👉 Most customers will benefit from letting us migrate Tags automatically.
👉 A small number with more complex setups may prefer to opt out and do it themselves.
Why Does This Matter for Hotels and Facilities Teams?
Tags in Snapfix are one of the simplest yet most powerful ways to keep your operations organized. Whether you’re managing a hotel, resort, care facility, or multi-site property portfolio, Tags help your team quickly categorize issues, track assets, and keep everything consistent.
Up until now, Tags (such as Location, Equipment, or Category) were managed at the Group level. This worked for flexibility, but it also meant duplication and extra admin when the same Tags were needed across multiple Groups. For example, hotel reception areas, room numbers, or boiler equipment might need to be entered multiple times leading to wasted effort and potential confusion.
That’s why Snapfix is introducing Account-level Tags. This is a major step forward in making your workflows easier, cleaner, and more scalable across your entire organization.
How Does this Update Benefit You?
By centralizing Tags at the Account level, you get:
• Consistency across your hotel or facility portfolio: No more duplicate entries like “Reception” or “Lobby” across different Groups.
• Time savings for your admin and management teams: Create a Tag once and apply it everywhere.
• Improved reporting and compliance: With one source of truth for Tags, your dashboards and audits become cleaner and more reliable.
• Scalability for growth: Whether you’re adding new hotels, buildings, or facilities, Tags can be extended without rework.
This update isn’t just a technical change, it’s a step toward helping hospitality and facilities teams reduce complexity and stay focused on what matters most: delivering great guest and resident experiences.
Example 1: Simple Setup (Auto Migration Recommended ✅)
Scenario:
• Tags with the same name are used across multiple Groups.
• But, they mean the same thing everywhere (e.g., “Reception” always refers to the hotel reception).
How it looks today (Group level):
• Group A → Tag Folder “Location” includes “Reception, Room 101, Room 102”
• Group B → Tag Folder “Location” includes “Reception, Room 201, Room 202”
How it will look after auto migration (Account level):
Account → Tag Folder “Location” (shared across Groups)
Tags: “Reception, Room 101, Room 102, Room 201, Room 202”
Result:
• “Reception” exists only once at Account level and is available everywhere.
• No duplication.
• No data loss.
Direction for Customer: ✔ You should let Snapfix auto-migrate.
Example 2: Complex Setup (Consider Opting Out ⚠️)
Scenario:
• Tags with the same name are used across multiple Groups.
• But the meaning depends on the Group.
Example:
• Group A (Building A) → Tag Folder “Location” includes “Reception” (Reception in Building A)
• Group B (Building B) → Tag Folder “Location” also includes “Reception” (Reception in Building B)
Problem:
• If auto-migrated, both “Reception” Tags would merge into a single “Reception” at Account level.
• This loses the distinction between Building A Reception and Building B Reception.
How opt-out helps:
• Group A → “Reception (Building A)”
• Group B → “Reception (Building B)”
• Each Tag remains separate, with a description added for clarity.
Direction for Customer: ⚠️ If you rely on the Group context to distinguish Tags, you should opt out and manage the migration yourself.
What Happens If You Do Nothing?
If we don’t hear from you, your account will be automatically migrated using the auto migration rules.
• Simple setups: All good, no action needed.
• Complex setups: Tags with duplicate names will be merged. You may need to tidy them up afterward if you didn’t opt out.
Summary: Should You Opt Out?
• Most customers: Stay opted in – the migration will save you time and keep your Tags consistent.
• Customers with Group-specific duplicate Tags: Consider opting out if the same Tag name means different things in different Groups.
Next Steps:
1. Review your Tags in Snapfix.
2. Decide if your setup is simple or complex (see examples above).
3. Let us know only if you want to opt out here. Otherwise, you’re all set!
Final Thoughts
Snapfix is designed to be the most intuitive maintenance and operations platform for hospitality and facilities teams. Account-level Tags reduce duplication, streamline reporting, and give managers more confidence in their data.
This update is one more way we’re helping teams save time, improve compliance, and deliver exceptional guest and resident experiences with less admin and fewer headaches.