- Who this is for
- Overview
- Before you start
- How to add employer context
- Editing or deleting employer context
- How Enhance features use this information
- Best practice guidance
- Limitations
- Related articles
Who this is for
Administrators holding both the supervisor permission and the manage tenant settings permission.
Overview
Aptem Enhance features can already draw on organisation-wide context and programme-level context. Administrators can now add employer context too: a text description that applies to one or more employers a provider delivers apprenticeships to. This lets the Aptem virtual assistant (AVA) reflect an employer's own workplace policies, terminology, and expectations, alongside the organisation and programme context already in place.
How to add employer context
- Navigate to Settings
- Select Brand & Customisation → Context for Enhance Features
- Under Employer context, choose Add new
- Select one or more employers to apply the context to. An employer that already has context appears in the list but cannot be selected again until its existing entry is edited or deleted
- Enter the context describing that employer
- Select Save
The context applies to every employer selected.
Editing or deleting employer context
To update an entry, select it from the list. You can change the context text, or add and remove linked employers; your changes apply to every employer linked to that entry once saved.
To remove an entry, select Delete. This unlinks all employers currently attached to it, and they no longer carry employer-level context. Organisation and programme context, where set, are unaffected.
How Enhance features use this information
AVA reads the employer context for a learner's employer, in addition to organisation and programme context, when shaping its responses. As with organisation and programme context, employer context cannot change AVA's safeguarding routing or refusals, and cannot expose its underlying instructions.
If a learner is linked to an employer with no employer context set, AVA's behaviour is unchanged: organisation and programme context still apply where configured.
Best practice guidance
- Keep content short, factual, and focused on workplace terminology, policies, and expectations
- Exclude contact details; use Aptem's dedicated safeguarding contact setting instead
- Avoid sensitive or personal data
- Don't attempt to override AVA's safety behaviour
- Follow your own safeguarding policies when deciding what to include
Limitations
- Employer-level only; this article doesn't cover organisation or programme context (see related articles)
- Plain text exclusively
- No visible change history in the current release (who changed an entry and when is recorded, but not yet shown in the UI)
- No preview function before saving