Config entities are used to store per-user information

When the user form is saved, the module creates/updates an individual config entity to store the "Your current logout threshold" information. This will cause data loss for any site that is using the configuration management system in the intended way.

Example

On your live production server, a new user is added. This causes config entity autologout.user.5 to be created.

Meanwhile, on your development box, you update the definition of a view and commit that configuration change.

Now it's time to move your change to the production server, so you pull the commit to the production server and run a configuration sync to make things current. *Poof*, the config entity autologout.user.5 is now gone because it never existed in the codeline. (Nor should it. That would create an impossible workflow of trying to keep the codeline consistent with active content in production.)

Proposed resolution

"Your current logout threshold" should instead be added as a field to the User entity.