I'm investigating options for how to present a 'self-update' system that requires approval by an authority. An analogy might be, updating your profile on this site, but someone needs to approve your edit.
The complexity in this situation is:
- The approval might take a few days to enact.
- The edits might be done by more than one person. E.g. the profile is for an organisation, any of the users of that organisation can make an edit.
- Desire to allow multiple edits (across the whole profile) without specifically locking anything since there is a pending edit.
When thinking of the UX, the options to present this to the user seem to be:
- Any edit locks all future edits of the profile until acceptance/rejection.
Users are shown the original content.
- Any edit locks all future edits of the profile until acceptance/rejection. Users are shown the new content (perhaps indicating it is a pending edit).
- Similar to 1, but at a field level.
- Similar to 2, but at a field level.
- No locks, but each field is shown in it's original state, but a hover (or other indication) allows the 'queue' of unapproved changes to be shown.
- Similar to 5, but showing the last (but as yet unapproved) edit.
There is a desire to allow multiple edits, but I'm struggling to find other systems to cite as examples. Perhaps the only one I can think of is Wikipedia that allows revoking edits. In the case of Wikipedia, do they have a model of unpublished pending edits or do they always show the last change?
Ideas and referenced examples welcome.