This explains what changes when we move your World Manager Account Groups into FranConnect Roles — what you'll notice, what stays the same, and what to expect on the day it happens.
Why we're doing this
Today, managing what a user can see and do is split across two places: WM Account Groups (which control access to Training & Development) and FC Roles (which control everything else on the FranConnect platform). Because these two systems don't talk to each other, an admin has to make the same change twice to keep a user's access matching in both places — and it's easy for one update to be missed, so a user's WM access and FC access quietly fall out of step over time.
After this change, FC Roles become the one place you manage a user's full access — both their FranConnect permissions and their World Manager training permissions — in a single screen.
What happens to your Account Groups
Every WM Account Group you currently use that has at least one active user in it will be turned into a matching FC Role, carrying across the same default permissions that group already grants today.
- You won't lose any group — every active group becomes a role.
- Naming depends on the group's level. World-level groups keep their exact name, with a number added only if it clashes with an existing Role (e.g. "World Manager1"). Divisional/National-level groups always get their division added to the name (e.g. "Australia - General Manager"), so you can tell them apart at a glance — and if that combination also clashes, a number is added the same way. You're free to rename any migrated role afterward.
- Groups with no active users, or duplicate/unused groups, won't be carried across as roles — there's nothing to migrate.
What happens to your users
If your user has the standard, default permissions for their group today, this is automatic — they're simply placed on the matching new FC Role. There's nothing for you to do, and their day-to-day access doesn't change.
If your user has custom permissions (i.e. someone has gone in and individually ticked or unticked specific permissions for them, outside the group default), their access is preserved exactly as it is — nothing changes for them on day one. These custom permissions will keep working behind the scenes until the first time an admin opens that person's new FC Role and makes an edit. At that point, the role's permissions take over going forward.
If your user belongs to more than one Account Group today, they'll be placed on each matching FC Role — one role per group, the same way it works today, just managed from a single screen instead of two. If that same user also has custom permissions, those permissions keep overriding their combined access across all of their roles, exactly as described above, until the first time any one of those specific roles is edited.
In short: nobody loses access, and nobody needs to act immediately. Custom permissions are a safety net that stays in place until you (or your team) are ready to manage that person through their new Role.
What stays the same
- Your existing Account Groups page and Account Custom Permissions page remain visible in World Manager — they just become read-only, since they're no longer the system that manages access. Nothing is deleted.
- Fusebox (the feature that controls which modules are visible for each hierarchy level) is not changing or being switched off — it keeps working exactly as it does today. The only visible difference is on the Role screen itself: if Fusebox has a permission switched off for your hierarchy level, that permission simply won't appear as an option there — it's not something you can grant from Roles until it's enabled in Fusebox.
- Any targeting you've set up (e.g. a training course targeted to "All Store Managers") keeps working, because it now targets the matching Role instead of the old Group.
- Terminology changes: Anywhere in FranConnect or World Manager that referred to "Account Group" or "Group" will now say "Role" instead — for example, in target-selector menus. The one exception is the legacy Account Groups page itself, which keeps its name since it still shows your pre-migration groups for reference.
What this means for new users going forward
Once the migration is complete, creating a new user is simpler: you assign them a single FC Role, and that Role determines everything they can do — both in FranConnect and in World Manager Training & Development. There's no separate step to also assign a WM Account Group.
You'll also notice the separate "Training & Development" access checkbox is removed from the user screen — it's no longer needed, because your Role selection alone now determines a user's access, including to Training & Development.
This is also now the standard setup for any brand-new WMI customer: new implementations are configured directly with FC Roles from day one — there are no WM Account Groups to create or migrate. If you have specific questions about a new implementation, reach out to your Implementation team.
Timeline — what to expect
- Before cutover: No action needed from you. We'll confirm the exact date with you in advance.
- On cutover: This happens during a scheduled migration window (planned for low-traffic hours). Your Account Groups convert into Roles, and your users are automatically placed on the matching Role based on today's group membership.
- After cutover: You manage all user access from the Roles screen in FranConnect. The old Account Groups and Account Custom Permissions pages remain visible for reference only.
- Ongoing: If a user had custom permissions preserved from before the migration, the first time you edit their Role, that Role's permissions become the new source of truth for them.
Recommended: Migration adds the full set of World Manager permission fields to every FC Role — not just the roles that came from a WM Account Group — so a role that never touched Training & Development before will now show those permission options too. They're added unchecked, so nothing changes about what anyone can access. Even so, we'd recommend reviewing your full role list with your Customer Success Manager after migration, so you can consolidate or clean up any roles that no longer need to exist side by side.
Frequently asked questions
Will my users lose access to anything during the migration? No. Every active group becomes a role with the same permissions, and anyone with custom permissions keeps them exactly as they are until you choose to edit their role.
Do I need to do anything before the migration happens? No action is required. We'll let you know the scheduled date ahead of time.
What if I have users with custom, one-off permissions set up? They're untouched by the migration. Their existing custom permissions keep working as a safety net until the first time someone edits their new Role — so there's no rush and no risk of surprise changes.
Can I still see my old Account Groups after this happens? Yes — the page stays visible for reference, but you'll manage access going forward from Roles, not from Account Groups.
What if my group name is already taken by a Role? You won't lose the group. World-level groups get a number added to the end of the name (e.g. "World Manager1"); Divisional/National-level groups are always named with their division first (e.g. "Australia - General Manager") so they're distinct by default. Either can be renamed afterward if you'd like.
Is anything being switched off? No features are being disabled. Fusebox continues to work as it always has; the Account Groups and Account Custom Permissions pages simply become read-only. The one thing to be aware of: a permission that's switched off in Fusebox for your hierarchy level won't show up as an option on the Role screen — so if you're expecting to see a particular permission there and don't, check Fusebox first.
Questions about your specific account? Reach out to your Customer Success contact or FranConnect Support.