For large fulcrum accounts, automating user management based on inactivity over a certain period is helpful for controlling costs.

While it is helpful to have access to the last sync data through changesets, it's difficult to paint a complete picture of a users activity without having programmatic access to the login data. We find that a user may get accidently flagged for removal if they are a back office or read only user who's primary interface is the website. Because they use the mobile app infrequently they have a tendency to get flagged as inactive even though they are logging in. If they are a read only account, they never generate a change log so we can't account for their activity through that avenue either.

Having access to the last sign in date in the memberships would be very helpful for solving this issue.