I don’t think groups has time based automation rules yet, but it’s something we’ve asked for.

Maybe try and go about it a different way, such as when they complete something it places them into the new group. 

@Neil Patterson as far as I know the only way to change user attributes in bulk is by using the CSV import option (you can use it to change a single field if you want) or if you build a connection to your source, like an HR system, CRM, etc.

Thanks @lrnlab - this is how we do it at the moment.  Just wondered if there was an automatic way of doing it.

Will look into them perhaps completing a checklist that then triggers a move of group as @JZenker suggests :)

Hello! We implemented something like this in our system. I’ll do my best to explain it.

We have a “New Hire Clothing” Group and they’re assigned there by rules from an additional field of Department = clothing and Hire Date = After 7/20/21. This group has a menu that lands them on an Onboarding Hub page we’ve created that has the onboarding courses we want them to take. The Onboarding group is low on the menu order, right above our default menu.

Then we have a normal Clothing group that has rules of Hire Date = After 7/20/21, Department = Clothing, and enrollment status on those onboarding courses = complete. Once these conditions are satisfied, then they’re automatically moved to this group and put into a new menu that this group is assigned to. Since this menu is higher on the list, they’ll never see or have access to the onboarding hub. 

Did that make sense? I can post images of our menu and group rules if that would help! It’s like a graduated access kind of thing. We want them to take the onboarding courses before they get into product training and all that. 

One of the things that may make your groups feel sticky is that it is much easier to get people into groups and not necessarily out of them.

I have a secondary anchor (like many of you are talking through) that helps to say if the person is within X days of being with the organization and we flag them as a new employee. It starts as a flag of Yes for thirty days and becomes a No afterwards.

The rest is then covered by what is described above by various others:

1. using an anchor of a start date for when the logic began in your platform.
2. using a completion criteria of a course to trigger the next group

The good news the use of the flag and one other (an “active user” flag)? Does seem to remove them nicely from that initial grouping.

Does anyone know if these suggestions work with Extended Enterprise? We’re always up against the innovation barrier that is Ext. Ent.

I would want to apply some awesome conditional menus like those in this thread to one of my two domains, but not the other.

There’s a lot of great advice in this thread but I wanted to mention that there’s a guide for setting of some of these suggestions that might be helpful: