The lead user in each account can use the Admin menu in the application tool bar to access the settings for your account.Here you can manage the users in your account. Users can be disabled, passwords rest etc.
You can also manage the status levels available for decisions in your account. Status levels let you track the completeness of your work on the core objects in your database, the Decisions. You can define as many or as few status levels as you like and assign each a color. There is no requirement for each level to have a unique color, though that's typical. These colors will be used in the Decision Requirements Diagram so you can quickly see the status of your Decisions. The default database contains three status levels – In Process, Completed and Implemented. The list is sequential – each Status Level from top to bottom is considered “more complete” than the last. You can add new levels, re-order them and remove to get the status levels that make sense for your projects.
The final setting is the assignment of Completeness Checks to Status Levels. DecisionsFirst Modeler has a number of built in completeness and correctness checks. Some of these are Errors and some are Warnings. When triggered, these checks will highlight elements of the Decision as being incomplete or inconsistent. To maximize your flexibility the checks are not applied automatically – you can select the Status Level at which you want to enforce each check. This lets you decide what kind of completeness checks you want to apply at each stage, mapping them to your own status levels. Any Decision that is in the Status you pick or a more complete one (one displayed further down the list) will execute the check and display any Warnings or Errors that apply.