Why this matters
The more complete your learner profiles, the less manual work for admins — and the more relevant the experience for each learner.
Less admin time — automation (group assignment, training rules, reporting) only works if employee profiles are complete. Empty fields = manual work for you.
Right training, right people — learners get content that fits their role, sector, and team instead of generic suggestions.
Compliance accuracy — jurisdiction-based rules (e.g. California, NSW) only fire if learners have a location on file.
Reporting that actually rolls up — slice completion by department, manager, location.
This guide covers the six fields that drive the biggest lift, what each one unlocks, and how to populate them.
The six fields that matter most
These six fields drive almost every admin and AI feature in Go1 today. Capture them on every learner.
Field | What it powers |
Job title | Knowledge Checks, Morgan answers, content recommendations, dynamic groups |
Industry | Industry-relevant content recommendations, sector-specific Knowledge Checks, compliance context |
Department | Easy bulk assignment (e.g. assign to all of Sales), dynamic groups, team-level reporting |
Location (country, state, city) | Easy bulk assignment by jurisdiction (e.g. assign to all learners in California), compliance training, location-based recommendations |
Language (e.g. | Content delivered in the learner's language, Intelligent Translations of the experience and content |
Manager / reporting line | Managers assigning learning to their team, team-level reporting |
Pro tip: Job title, industry, department, location, and language are the highest-impact fields for personalisation. Manager unlocks team and reporting features. Aim to capture all six for every active learner.
Pre-launch checklist for AI features
Before you turn on Morgan, Knowledge Checks, or content recommendations across your organisation:
Job title is set for the majority of active learners (the higher the coverage, the better the personalisation)
Industry is set for your organisation and per learner if you span multiple sectors
Department is set if you want dynamic groups or department-level reporting
Location is set for any learner subject to compliance training
Language is set for any learners with different language preference from the portal
Manager is set if you plan to use team-level reporting or manager workflows
A recurring sync is in place (SSO/SCIM or scheduled CSV) — not a one-off load
How to populate learner profiles
You have several options, in order of how much coverage they deliver. Pick the one that matches how you manage your users today.
Option 1: SSO and SCIM (best coverage)
If you use an identity provider (Okta, Microsoft Entra, Google Workspace, etc.), connect it to Go1. The data flows through automatically and stays in sync as people change roles, locations, or managers.
SSO — sends learner attributes (job title, location, etc.) on every login as SAML claims or OIDC scopes. Read the SSO setup guide.
SCIM — automatically provisions, updates, and de-provisions users from your identity provider, including profile fields. Read the SCIM provisioning guide.
Ask your IT team to include the six fields when configuring SSO claims or SCIM attributes.
Option 2: CSV import
If you don't have an SSO/SCIM connection yet, you can upload learner data via CSV. Read the full Create and manage users guide.
Go to Admin → People
Select Import users
Use the template, including columns for job title, industry, department, location, language, and manager
Schedule a recurring refresh — daily or weekly is best; monthly is the minimum to keep AI experiences accurate
Note: A one-off CSV is stale within months. Schedule a recurring refresh to keep AI experiences accurate.
Option 3: Ask learners to complete their profile
Learners can update their own profile from the avatar menu. This works as a top-up, not a substitute for the options above.
Heads up: If you use job title, department, or location in dynamic group rules, those fields are locked from learner edits — so learners can't accidentally move themselves into or out of a group by updating their profile. Learners will see those fields as read-only.
Frequently asked questions
What if I don't have all six fields?
Start with job title — it has the broadest impact across AI features. Add the others as you can.
What about other fields like employee ID, job level, or skills?
Those also help. Job title, industry, department, location, language, and manager are the six with the biggest impact today. Capture additional fields if your import already includes them.
How often should the data refresh?
On change, ideally. Daily or weekly for CSV; every login for SSO. Monthly is the minimum — roles, locations, and managers change frequently and stale data leads to stale AI experiences.
Where can I find the technical field labels and API details?
For developers and integrators, see the Go1 developer documentation — it covers the technical labels, API field names, and integration patterns for each of these fields.
How is profile information used?
Profile information is used to deliver your team's experience inside your Go1 portal — powering personalisation, content recommendations, and AI features like Morgan and Knowledge Checks. It is not shared with other customers, and Go1 does not use your data to train AI models. For full details, see How Go1 uses AI, the Go1 privacy policy, or visit the Go1 Trust Centre.