Knowledge base Rise Up

Custom fields: four ways to automate learning

  • Updated
Custom fields · Use cases

Custom fields: four ways to automate learning

Custom fields store the information your organisation needs on each user, group or course. Four use cases show how to turn that information into automatic, targeted training — pick the one that matches how your data reaches the platform.

 

Custom fields

What custom fields do

Custom fields let you store the information your organisation needs on the platform — beyond the standard profile. Once filled, they decide who joins which smart group and, through those groups, who receives which course or learning path.

Describe

Add your own information to a record. Each field is linked to one or more entities: User, Course, Group, Course registrations or Session.

Structure

Choose a type for each field: Short text, Drop-down list, List of values or Date. Created in Settings > General > Custom fields.

Use

Field values feed smart groups, e-mails, certificates and documents, list filters, exports, imports, SSO, SCIM and webhooks.

 

Use cases

Choose your use case

Each use case is a complete, step-by-step guide built around a fictional example: the fields to create, the smart groups to build, the operators to use and the pitfalls to avoid.

1HR mirror

Assign training automatically from your HR data

For you if

Your HR system feeds the platform through a connector, SSO or SCIM.

What you set up

Country, legal entity, job family and status drive smart groups: every hire, transfer and promotion updates training automatically.

Example Alvora Group · 9,000 employees

Read the use case →
2Sign-up questionnaire

Route learners from their sign-up answers

For you if

Learners create their own account and there is no HR feed.

What you set up

A few questions at registration — site, level, objective — send each learner to the right course or learning path.

Example Campus Horizon · 12 campuses

Read the use case →
3Network of sites

Train a network of sites

For you if

Your teams are spread across stores, branches, depots or agencies.

What you set up

Person data stays on the user, site data moves to one group per site: target training by job and site format.

Example Novastore · 240 stores

Read the use case →
4Data already stored

Put the data you already store to work

For you if

Your fields are filled for exports and BI, but no smart group uses them.

What you set up

Review your existing fields and build a first smart group on data you already have — with no new import.

Example Veltra Energy · 15,000 users

Read the use case →

 

Quick guide

Which use case fits you?

Your situation Where field values come from Start with
An HR system knows your org chart HR connector, SSO, SCIM or a regular import Use case 1 · HR mirror →
No HR system, learners register themselves Learners, at sign-up Use case 2 · Sign-up questionnaire →
Staff spread across many sites Import, HR feed or manual entry — plus one group per site Use case 3 · Network of sites →
Fields already filled, enrolment still manual Existing imports or HR feed Use case 4 · Data already stored →
Use cases combine
Many platforms mix several use cases: an HR mirror for employees and a sign-up questionnaire for external learners, or site groups on top of HR data. Start with the one that solves your most urgent need, then add the next.

 

Before you start

Five questions before creating a field

  1. What will it drive? A smart group, an e-mail, a document or an export. If nothing, do not create it.
  2. What does it describe? Person → User · site or team → Group · training → Course · one enrolment → Course registrations · one session → Session.
  3. Which type? Drop-down list for stable values · Date for anything time-based · Short text for free information or values your HR system may rename.
  4. Who fills it? HR system, SSO or SCIM, import, an administrator or the learner at sign-up. Name one owner for the list of values.
  5. Is it sensitive? Decide who can see the field before filling it, and never store national identifiers.
Fields set membership, not rights
A custom field decides who joins a smart group. It never grants permissions: rights come from roles in Settings > Permissions.

 

Start from an outcome, not a setting.

Not sure which use case fits your platform? Our team can review your custom fields with you.

Contact Support

 

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request