You can create multiple users who can configure policies in the web interface. However, if there are multiple users, there is the possibility that two or more users might try to edit the same object, policy, or other setting at the same time.
The web interface will not prevent multiple users from editing the same item. This ensures that if someone is away on vacation, or leaves the company, with uncommitted changes, other users can make needed edits without being prevented from doing so.
But this does mean that you can find yourself in a situation where your edits, or intended edits, conflict with what another user wants to do.
It is critical for you to understand that only a single user can commit changes to a given item at one time. If you make edits to an object that another user edited, and the other user commits changes before you do, you will have to discard all of your changes, not just to that object, but to all other objects you changed, even those without conflicts. If you find that you need to change an item, and another user has already edited it, work directly with the other user to ensure changes are committed in a timely manner so that you can complete your changes.
In the web interface, icons indicate whether an item has been edited by another user, and the type of conflict that exists for that object:
- Warning—This item is being edited by another user. Mouse over the icon to see the user name. Except in extraordinary circumstances, you should not edit the item until the user commits changes.
- Pending—You and other users have made edits to this item. Whoever commits their changes first will create a Commit conflict for the other users.
- Commit—Another user has committed changes to this item that you have also edited. You must now discard all of your pending changes, not just the change to this item. At this point, you would waste your time making additional edits before discarding changes. You can examine your pending changes to understand the edits you will have to redo.