Project Administrators can only make these changes for Projects when they have Administrator rights.

Administrator to a Project, however, will not be able to edit Project details or delete the Project.

The illustration below provides an example of the start menu. 

Open

Projects

When a Project Administrator clicks on "Projects" they see all the projects they are an admin on.

Open

List of Projects

Selecting one of those projects opens the project admin view of the project with a menu of features across the top.

New user in project

The project admin can add new users to their project by selecting New user in project and filling out the details. They can also add a new user based on the project profile of another existing user on the project by selecting the equal sign at the end of the row of a current user on the project, this will match the user settings from the existing user. Jump to https://drofus.atlassian.net/wiki/spaces/DV/pages/1318356394/Project+Administrator#Add-new-user to learn more.

Import/Update Users

Where there is a long list of users or a need to update several users, the project admin can select Import/Update Users and leverage a CSV/Excel file. We provide a template they can download that includes the existing users on the project. Jump to https://drofus.atlassian.net/wiki/spaces/DV/pages/1318356394/Project+Administrator#Import%2FUpdate-Users to learn more.

New user group

User groups are a great way to define permissions. The project admin can select New user group to configure a new one to be used on user profiles to better manage several users with the same permissions. To learn more about this feature go to https://drofus.atlassian.net/wiki/spaces/DV/pages/1332417661.

Database

As a project admin, there are times when a backup of a project is needed for archival purposes. The project admin can select Database to access these backups. They can also run task on the database including compressing the database to reclaim space if several rooms, items, or occurrences have been deleted. They can also purge all documents on a project from the database.

User log

The project admin can access User log data to know who and when users on the project have accessed the project.

Run Task

There are several tasks a project admin can run from the project admin site, including:

1. Update roles

2. Set all user rights to read access

3. Remove All Users

4. Purge deleted items

5. Enable all project users

6. Disable all project users

7. Clear all logs

To learn more about these tasks go to https://drofus.atlassian.net/wiki/spaces/DV/pages/1353155818.

Copy Data

The project admin can copy data between projects if they are also an admin on another project. Select Copy Data to start the process of either copy project-specific data to another project or database-specific data to another database. To learn more about this feature, go to https://drofus.atlassian.net/wiki/spaces/DV/pages/1342637220.

Copy to same db

The project admin can copy a project in the same database to build a multi-project single database. Select Copy to same db to start this process. To learn more about this feature, go to https://drofus.atlassian.net/wiki/spaces/DV/pages/1342637207/Creating+New+Projects#Multi-Project-Single-Database.

Copy to new db

The project admin can copy a project to create a new database. This is often used when an admin wants to start from a multi-project single database and extract one of the projects from it to create a new project with its own independent database.

Audit log

Any changes to the project done by project administrators are logged in the Audit log.

User audit log

Any changes to user permissions show in the User audit log.

Users

You can read about User Management here: User Management.

Inactive Users

The section will display a list of users not logged in dRofus recently. It is possible to set the time frame (6 months, 1 year, 2 years or never logged in) using the select control at the top of the list.

Kick Out Users

The list of currently logged-in users, available from the Server Status section, has an additional button on the rightmost column shaped like a red cross. By clicking that button, the administrator can kick the associated user out of dRofus. This is useful if the administrator has to execute a special operation (moving or copying a database, for example) that requires that no users are logged in on any of the interested databases.

Add new user

There are several ways of opening the "Add new user" window. The Project Administrator can get there from the list of Projects by clicking on the short-cut on the right of the area field, or they can click to open a Project and choose "Add new user to Project.” They can also open the window via the user list by clicking on a user and adding them to the Project.

When creating new users, please follow these simple guidelines:
1. Username and email must be all lower case. Users accounts cannot be used by more that one person and should be unique per email.

2. Select from the automatically displayed user list if the user already exists. The system will suggest an existing user if you start to fill in matching user profile data. You will only see users that share Projects with you. 

3. Administrator user rights should only be given to a limited number of people after special training. Remember that Administrators can add/remove other users and delete Project data from the admin site.

4. Enter the user information under User details. First name, last name and email address are obligatory. Emails can be used as usernames.

Note that the system automatically searches for users which match the name as it is typed in the form. If the new user being added already has a log-in for another Project, the program will display the user as an alternative under "Existing similar users". The system will also automatically generate a user name based on the information typed in for First name and Last name. This can be edited manually if required. If a user name already exists, an error message will appear at the top requiring a new user name. 

User Permission Levels

The User rights function allows control of the individual rights of a user within the different dRofus modules. Hold the mouse cursor over the blue question mark to view help text explaining the different rights.

Level 4 - None means the user will not have any permissions and in most cases the module will not appear at all. 

Level 3 - Read means the user will have read only access and non editing permission.

Level 2 - Limited means the user will have some editing permissions that can be refined based on other modules permissions (see sections below to define tab(s) within Item Specification, tab(s) within Room Data, Tender and Existing Items permissions)

Level 1 - Full means the user has full editing permissions.

Modelserver

In order to upload or replace IFC files on dRofus web, users need to have full level 1 permissions.

Administration Levels

Bim Administrators have access to edit Attribute configurations in Revit and updating dRofus settings related to Revit/ArchiCAD.

Administrators have access to change settings and preferences in dRofus; they also have access to this system for managing users.  

No access to Admin Site appears when Administrator is checked offering the option to limit access from the Project admin site allowing these types of admins access to the client admin settings, but not to user or Project administration. 

If a database contains several Projects, there is an option to add the user to all the Projects sharing that same database. For information on creating a Project/database, go to Owner administrator.

When adding users, a Project Administrator can select an email format from the drop-down menu, based on the modules to which the user is to have access. The Project Administrator can also view a preview of an email, by clicking on the email icon.

When adding users, there are two final options. The Project Administrator can either choose to add the user and return to the user list in the Project, or they can choose to add and save a new user. Once they have made their choice, the system automatically sends an email to the user with log-in details. A copy of the email will be sent to all database administrators.

Modify Item rights for a user

Project Administrators define the access rights in the web administration page for each user. Click on the "Responsibility groups" or click "Go to Item rights detail" below the Item rights settings to set specific rights:

If a user is limited to responsibility groups this is also shown on the user:

Examples

If the intent is to prevent a user from modifying the item for responsibility group IT, but needs full access to edit all other items, they can give the user (default) Item rights = 1 (full), but limit the user to e.g. IT = 2. This means the user will have full access to work with all items, but are not allowed to modify type values on the item (e.g. specification, price, name etc.).

If the intent is to make sure a user is only working with items with responsibility group IT set the user settings as (default) Item rights = 3, but give full access = 1 for the IT responsibility group. This means the user is only allowed to create, modify and delete items with the IT responsibility group and also only add/remove these too rooms. This also means that the user e.g. cannot do operations on Item lists for rooms if this Item list contains other items than IT Item. E.g. cannot assign or remove a room template if this also contains ARC Item. This "hard" limitation therefore is probably most common to use in combination with separate Item lists that only contain IT Item (see Multiple Item List Types).

If the intent is to make sure a user can only see item with responsibility group IT set the user settings as (default) Item rights = 4 (no access), but give 1,2 or 3 to the IT responsibility group (depending if the user would like to work with, place or read only IT Item. This means that the user will not see any of the other items either in the item overview or in the room lists. Including those items without a responsibility group set (default is 4).

If the intent is to make sure to hide IT Item from a user there are two options – the first option is to set the user settings to let the user only see a selection of responsibility groups (like example above) or the second option is to set a (default) Item to either 1,2 or 3 and set IT access rights to 4.

Potential user rights issues

In some of the examples above the settings can not only limit the write access to some items, but also hide them from the user. This can lead to situations that are confusing for the user. For example if a user has access to all items but cannot see IT Item they are not allowed to for example delete an Item list for a room, even though it seems like they can edit all the Item in the room. So if a user profile is limited to some Items for some users it is recommended to put these items into different Item lists.

If a user has read only access to some item, but write access to others it can also be confusing if a user adds a sub-item with different responsibility groups. If for example a user does not have access to IT Item, but full access to ARC items, and the item the user is about to add/remove to a room has IT Item as subs and they are not allowed to remove it. Even though they have write access to the "parent" item, because this will also modify the count of an item they do not have write access to in the room.

If a user profile is limited to a responsibility group, this only means that they were not allowed to add any item with another responsibility group to an Item list in dRofus. But this was not a "strict" permission. So if the intent is to had full Item rights (=1) the user setting could be modified to limit the item to have the responsibility group they have access to and then add it to the room. Also there were no limitation to other operations on the Item list itself so the user could for example assign a room to a template or delete an Item list from a room, even though this list or template had items not in the same responsibility group.

Prevent user access to Price-related fields

Within the Item Properties panel, there are three price-related fields - i.e., "Budget price", "Price date" and "Price Comment":

A user profile can be set to prevent a user's read or write access to these three fields by checking the box ""Hide price":

In other words:

If the User has "1 - Full" as Item rights, and the "Hide price" box is not checked, the User will be able to read + edit the price fields.

If the User has "2 - Limited" or "3 - Read" as Item rights, and the "Hide price" box is not checked, the User will only be able to read the price fields.

If the User had "1 - Full", "2 - Limited" or "3 - Read" as Item rights, and the "Hide price" box is checked, the User will not be able to read any of the price fields - i.e., they will be blank.

Limit user access to a tab in the item specification

A user profile can can be limited to write access to one or several tabs in the item specification. From the user access menu click "Item specification" and select which tabs the user should be able to edit. Note that if the user has 1=Full on Item, and is limited to one tab in specification, the user will no longer be able to change property data of the item (Names, ID's, Prices etc.). 

Limit user access to a flag in Room Data

A user profile can be limited to one or several tabs in Room Data. First the user profile needs to be set to give the user 1=Full or 2=Limited access to rooms. Then from the user access menu click "RDS" and select which flag the user should be able to edit. The user will have read access to non-selected flags.

Limit user access on Tender groups

A user profile can be limited to one or several tender groups in the procurement module. First set the user setting to 1=Full access to the procurement module. Then within the "Tender groups" flag, click on the tender groups that the user needs access to.

User access to Existing Items

A user can create a register of existing items within the Existing Items module and associate (attach) these to pre-defined Items only if that User has Permission Level 1 to Responsibility Group for that Item. Once the Existing Item ↔ Item have been attached, Users will be able to allocate occurrences to Rooms for only those Items for which the User has Responsibility Group Permission Level 1 or 2.

Export to CSV (Users)

When viewing the list of Users within a Project, Project Administrators can carry out the "Export to CSV" command as follows. This will export user data to a CSV (comma separated values) text file which can be opened in Excel as a spreadsheet:

This enables the Project Administrator to view this list in Excel as well as any other tool that support CSV file types.

Import/Update Users

Using the import/update users feature can be helpful when trying to add several users to a single project. The template provided will included users who are already in the project to allow updating of permissions. Keep in mind our CSV format is using semicolons, so if you export from our template and make changes, make sure when you save the file again for upload it uses semicolons and not commas.