I was just testing remote deployment of configurations and rules, and I stumbled onto a bug, I think.
I have a new configuration, and a new rule that applied to a single company. In the client on my test desktop, I had already logged in as another user in another company. I switched users in the client, but the rule was never triggered (I've waited a whole day to make sure).
I know that a user changing company is a rare occurence, but I think this should work nonetheless.
I created a new configuration, but for Windows instead of MacOS/Linux. When I changed it to MacOS/Linux and opened the client again, the new configuration was pushed.
The old backup plan was still present and active. It's probably a good idea to keep it there, but something to keep in mind when managing the service.