I've never had to do this, since my department's policy is to have users download a new copy of the front end every time they open the app, but I can think of one case where this would be acceptable:
Let's say you have a main form/subform setup (or even just one form), where the bulk of the data is displayed in datasheet mode. There could be situations where different users only care about seeing specific columns.
In datasheet mode, you are able to show and hide columns, add your own filters, re-sort based on the columns of your choice, etc. These all count as design changes. As long as they are running from local copies, then if you are NOT forcing a fresh download every time they launch the app, you might consider allowing users to save their changes so that the form's output, which they have already spent time customizing for their needs, remains constant for each user from session to session.
This can be a better solution than creating a different near-identical form for each user or type of user, especially if they will still occasionally need to see the data they normally hide.