People

Administrators use People to maintain the roster, account access, roles, and memberships. A person can be added before their first Google sign-in, then use the same record for learning and reporting.

Preregister a person

Open Account menu → Manage organization → People, then select Pre-register user.

  1. Enter the person's Name and Google email. Use the address of the Google account they will sign in with.
  2. Set Hire date if their new-user learning window should start from a known date. Leave it blank for an existing user with no onboarding clock.
  3. Under Access, choose Learner, Manager, Contributor, or Administrator. See Roles and permissions before granting publishing or administrative access.
  4. Choose a Reporting team, or Organization (no direct team).
  5. Select any direct learning-group memberships, then select Pre-register user to save.

No invitation email is sent. Give the person the installation address and have them sign in with the matching verified Google account. Their first sign-in attaches that identity to the roster entry without resetting its memberships or learning history.

Preregistration works when new account registration is closed. With registration open, people can also create Learner accounts through Google sign-in; see Access and registration. For a batch of people and teams, use Import people and teams.

Edit a person's responsibilities

Find the person by searching or filtering the roster. Select their name or Edit in their row's actions to open Account.

Change their name, Access role, hire date, reporting team, or direct groups, then select Save profile. Login email is read-only, including on preregistered records; changing the name does not change the sign-in identity.

Each person has one direct reporting team. That place in the team hierarchy affects whose reports include them and which team-based learning audiences apply. A learning group can overlap several teams, and a person may belong through more than one source. The Groups column includes effective memberships, so removing a direct group selection may leave membership supplied by a linked team. See Learning groups.

The Manager role does not select the team someone manages. Assign them explicitly in the team's Manager field. Contributors can also hold reporting responsibility. Reporting teams explains the resulting scope.

Set the learning stage

The User type area shows New user or Existing user from the person's onboarding clock. A recorded hire date starts that clock; signing in does not start it.

When you change a hire date, the editor shows the current and proposed onboarding end. Saving applies the clock change while preserving course completion history.

The organization's default window and saved course deadlines are separate choices. Review Due dates before using a hire-date change to correct a learning timeline.

Stop or restore access

Clear Active profile and select Save profile to deactivate someone. Their account and learning history remain; no deletion timer starts. To restore access, review their role and memberships, select Active profile, and save again.

The roster's actions also offer Activate selected and Deactivate selected for batches. Fieldbook protects your own administrator access and requires an active administrator to remain. A deleted person must first be restored and reviewed through Delete and restore records.

Deactivation stops account access. On a public installation, it does not prevent the person from browsing the same public content available to other signed-out guests.

Make a batch change or inspect progress

Select roster rows to Add to groups, Remove from groups, Set reporting team, or Set hire date. Review the selection before applying the change. Removing group membership here removes the direct membership; another membership source can still include the person.

To inspect one person's learning, open their row's actions and select Progress. Progress and reporting explains the measures, assignment sources, and administrator correction actions.