Managing team members

Use the Team tab in the Project properties screen to manage the people assigned to the project and their administration rights. Team members are automatically added to the project when you assign jobs to them.

Team members assigned the User role must be assigned to a job to be able to work on it. They can also create their own jobs. Team members who have administrator permissions can assign any job to themselves and work on it.

Team members are assigned the User role or the Administrator role.

User role

A team member with the user role can:

  • create jobs, update jobs that are assigned to them, and delete jobs that they have created
  • invite other users to the project or reassign their own jobs to a different user
  • add or remove report stylesheets to the project
  • leave the project

Users cannot edit or modify the properties of projects or jobs that are not assigned to them.

Administrator role

A team member with the administrator role can perform the same tasks as users, and can also:

  • edit the project properties
  • delete any job or project
  • manage the administration rights of other users
  • invite users to the project
  • remove other users from the projects

To change roles

To change a team member's role, select their name in the team list and tap Update. Select the Role and then tap Update.

  1. Select the project and tap Project properties.

  2. Select the Team tab.

  3. Click Invite New User.

  4. Enter the email address of the person you are inviting. This must be the email address the person uses or will use for their Trimble Identity.

  5. Select the User or Administrator role. Generally, field users will have the User role.

  6. Click Invite.

    If the invited user already has a Trimble ID, they will receive an email with the project link and will automatically be added to the project. If the invited user does not have a Trimble ID, they will receive an email instructing them to create a new account. After creating their Trimble ID, they can access the project and the folders and the files to which they have permissions.

To invite multiple users at once, create a .csv file that specifies the email address, group, and role for each user. Trimble Access does not use the Group field, so this field can be left blank. The .csv file format will be: email, , role. To import the .csv file, click Invite Multiple Users, select the file, and click Invite.

When you create a job, you can assign it to someone in the project team, or to a new user who is then added to the project.

In the Create a job screen:

  • Enter part of their name in the Assignees field and then select the team member from the list of names that match.

  • If you have not yet added the person to the project team, click . Enter their email address and select their role. Click Invite.

In Trimble Access version 2021.20 or later, jobs can also be assigned or reassigned to team members from the field.

To remove someone from the project, select their name in the Team tab and tap Update. Tap Remove.

An administrator cannot leave a project or change their user role to User if they are the only administrator assigned to the project.

The Restrict job visibility check box is only shown (and can only be changed) if the signed in user is assigned the Administrator role.

For projects created using Trimble Sync Manager version 1.4.64 or later, the Restrict job visibility setting is disabled by default. This means that anyone assigned to the project can download and view the jobs in the project but they can only work on those jobs if they are assigned to them.

If Restrict job visibility is enabled, users with the User role will never see jobs that are not assigned to them.

Because Trimble Access prevents users from working on jobs that are not assigned to them, always make sure users are assigned to the jobs they need to work on. If a Trimble Access user is unable to see a job or is unable to make changes to a read-only job, assign them to the job. Do not attempt to create an editable copy of the job on the controller, for example by copying the job from a USB drive or by downloading it from an email. Creating a copy of the job can cause unintended problems when you attempt to upload the data to the cloud, such as duplicate jobs or lost data.

Jobs always remain visible to project administrators, the person who created the job, and users who are assigned to the job, irrespective of whether the Restrict job visibility setting is enabled or disabled.