...
2. Modules.
3. Administrators.
4. To add Admin to a module, select blue widget.
5. Contacts pop up will appear.
1) 6. Search by either Role, User Group or Company using blue drop down menu
2) 7. Select User / Group
3) 8. Click ok
9. When updates have been completed, click on submit.
Removing a Module Admin
1) . Highlight the User / or Group
2) . Delete (using keyboard)
3) . Click Submit to update
Contract Admin Module
...
3. Correspondence.
4. Contract Admin.
1) 5. Highlight and delete Admin, as required.
2) 6. Click on Blue Widget
3) 7. Search & Select User / Group / company to be added
4)8. Click Ok
Once Admin has been updated, scroll to bottom of page and click on update.
...
In RIB CX, you can give Module Admin rights to any User / User Group / Company without giving them full Project Administrator rights. As shown previously
1) . Add or Remove from Module
2) . Submit once updated
History Log for Module Administrator Changes
Changes to Module Administrators are now logged and can be viewed via the history button.
A pop-up screen will open and History of previous Admins and Admin updates will be displayed.
Assigned Module Administrators
...
Administrator | What Privileges Does The Module Administrator Get | When Can the Project Administrator Modify the Module Administrator | |
---|---|---|---|
Setup Phase | Live Phase | ||
Budget | Can release retention amount after total claimed amount is 100%. Assess claims and variations. Add additional line items to a budget. See all budgets in a project. | YES | NO |
CA Project Admin | Can release retention amount after total claimed amount is 100%. Assess claims and variations. Add additional line items to a budget. | YES | YES |
Config | Can edit and create distribution lists , and rules, correspondence workflows and set applicability of saved searches. This user needs to be a Project Administrator in order to access all configuration for distribution lists, rules, correspondence workflows and saved searches. This is useful if you want only one or a select few Project Admin users to be able to edit this config. Note: remove the group PROJECTADMINS from Config Admin so that only these users have access to edit these. | YES | NO |
Contacts | Can create / edit companies and users. Can create / edit groups. Can be set at a company level, but they can only create / edit users for that company. | YES | YES |
Correspondence | Can access all correspondence, except if issued in Private mode. | YES | NO |
Dashboard | Can configure dashboards for folders. | YES | YES |
Document Type | Can change the Configuration of a document after set up phase (See also Edit Basic Form Details). By default this is applied to all new documents. This user needs to be a Project Administrator in order to see the document type menu item. This is useful if you want only one or a select few Project Admin users to be able to edit document types. Note: remove the group PROJECTADMINS from Document Type Admin so that only these users have access to edit document types. Refer here for how to set up administrators on a form by form basis. | YES | NO |
Postmaster | Is notified of delivery failures for email / fax notifications. | YES | YES |
Register | Can add / edit / remove folders in the register. Can access / edit all transmittals. Has access to all documents on the register. | YES | YES |
Tender | Has access to manage the tender database for their company. Can setup tender project. Can set the default form types for a tender project. | YES | YES |
Utilities | This group is used to give a user who is not a Project Administrator access to bulk utilities that affect the whole project. Can access Utilities In Project tools menu.
| YES | YES |
Workflow | User(s) who can access workflow configuration in the Publication Space. | YES | YES |
...