User management and teams
User and access management
- Every prime contractor has an own Groundhawk organisation
- Users are created under this prime contractor organisation
- Site = Worksite
- Team = Access group where all users assigned to Team get access to all Sites assigned to Team.
- There are five user roles that give different access:
- 1. Viewer = View only to Specific sites or to Team sites
- 2. Field user = Can only see sites self created or assigned to
- 3. Project manager = Wide visibility to sites in the organisation
- 4. Documenter = Wide visibility and editing rights to projects in the organisation
- 5. Manager = User administrator, full visibility to users and sites
User management
- Prime contractor is responsible for user management, creating new users, maintaining the correct information and suspending access when users should not have them anymore.
- New users: Organisation manager creates the user and email is sent to the user with username and password.
- Remove access: User access is removed by turning user into inactive.
Setting up teams in your organisation
- Organisation = Prime contractor
Every prime contractor is an own organisation in Groundhawk. - Teams for subcontractors.
All Subcontractor personnel get immediate access to sites created under that subcontractor team and there is no need to share user names or assign user names for each site individually. Just add the Subcontractor-team to the site and all get access. - Teams for network owners / customers.
All network owner personnel that is in this Team can follow all their sites.
Teams and example
The purpose of Teams in Groundhawk is to make access management of especially subcontractor personnel easier.
Example:
PrimeContractor Ltd uses 2 subcontractors (X,Y) and that builds fiber and electricity networks for 2 customers (A,B). There are 5 ongoing sites.
PrimeContractor can now create team SubY assign sites 3, 4 and 5 to SubY, as well as all Subcontractor Y personell working for sites 3, 4, 5 into this team.
Now if a new team member joins that person is added to team SubY and automatically gets to see sites 3,4,5 and can make mappings to those projects.
If the Subcontractor Y starts a new Site (6) for the Primecontractor that site is just added to team SubY and now all personnel of subcontractor Y has automatically access to the new site.
Personnel at Subcontractor X doesn’t see any of the projects in the team SubY and vice versa.
Teams configuration expanded
In this expanded configuration there are 4 teams defined. 2 for subcontractors and 2 for network owners.
Site 1 belongs both to teams SubX and FibA automatically giving rights to FibA personnel to view and SubX personnel to make mappings for Site 1.
NEW SITE EXAMPLE: When a new site 6 for FiberNetA is created, there are two Teams assigned to it: FibA team, and SubY team. Now automatically Project manager 1,2 and Fieldusers 6,7,8 get access to this new site (6).
