> For the complete documentation index, see [llms.txt](https://docs.userlane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.userlane.com/getting-started/glossary.md).

# Glossary

Alphabetical list of Userlane product terms with one-line definitions.

This glossary covers the terms used across the Userlane Help Center. Each definition is deliberately short; the linked article has the full explanation.

**Adoption**: A HEART dimension that measures how widely a tool is taken up, including whether people return after first use. See Adoption.

**AI Assistant**: The conversational feature inside the Assistant that answers questions from published and connected content, recognizes where the user is and who they are, and hands off to guides or support. See Configure the AI Assistant.

**Announcements**: In-app messages targeted to an audience and scheduled for a specific time, with reach, interaction, and dismissal analytics. See Announcements.

**App Discovery**: A scan of the applications people use in the browser, covering the application inventory, usage patterns, license utilization signals, and shadow IT detection. See [App Discovery](/visibility/app-discovery.md).

**Application**: A browser-based tool that Userlane tracks. Each application configured in the Userlane portal has its own content, analytics, settings, and URL configuration. See Set up the application URL.

**Assistance**: The part of Userlane that helps people inside each application: the Assistant, In-app guidance, Validators, Contextual Actions, and announcements. See Assistance overview.

**Assistant**: The floating in-app panel that end users interact with. It provides access to guides, announcements, surveys, search, and connected knowledge sources. See [The Assistant](/assistance/the-assistant.md).

**Attribute**: A piece of information about a person beyond their in-app behavior, such as department, role, or location, passed to Userlane through single sign-on (SSO), a connector, a manual upload, or the application programming interface (API). Attributes power audience rules and analytics filtering. See [Attributes](/administration/attributes.md).

**Attribute source**: The system that sends attribute values to Userlane. Sources include SSO claims, attribute source connectors (such as SAP SuccessFactors, Microsoft Entra ID, or Salesforce), manual comma-separated values (CSV) upload, and the Attribute Import API. See Attribute sources.

**Audience**: A reusable group of users defined by rules about their attributes, behavior, or tag interactions, used by both content targeting and analytics. See [Audiences](/administration/audiences.md).

**Browser extension**: The recommended way to deploy Userlane. The extension is pushed through device management or activated silently through SSO, and it runs across every browser-based application the user opens. See How Userlane is deployed.

**Contextual Actions**: A trigger model where a condition (an element appearing, a page loading, an attribute matching, or a prior interaction) fires a response such as a guide, an announcement, a tooltip, a tag, or a task. See Creating Contextual Actions.

**CSAT**: Customer satisfaction. A standardized survey type that runs on a quarterly cycle and feeds the Happiness dimension of HEART. See Surveys.

**Display rules**: Conditions that control where and when a piece of content appears, set by audience, URL pattern, and application state. Display rules are part of the Contextual Actions model. See Targeting.

**Editor**: The workspace where Userlane content is built. The Editor opens from the Userlane portal and is separate from the portal, where content is targeted and analytics are viewed. See A tour of the Editor.

**Efficiency**: A HEART dimension that measures how consistently users complete tasks, measured against each task's own typical completion time. See Efficiency.

**Goals**: Time-bound targets tracked against Userlane data. Goals sit alongside HEART without affecting it and cover four outcome areas. See Goals.

**Guides**: Step-by-step walkthroughs recorded in the Editor that lead a user through a process inside an application. See Creating guides.

**Happiness**: A HEART dimension that measures user satisfaction, fed by CSAT survey results on a rolling quarterly sample. See Happiness.

**HEART**: Userlane's five-dimension model for scoring how well an application works for the people using it, on a scale of 0 to 100. The dimensions are Happiness, Efficiency, Adoption, Risk, and Task Success. See [HEART](/intelligence/heart.md).

**Intelligence**: The part of Userlane that shows how well each application works for the people using it and proves what changed: the HEART Score, Goals, Tasks and Tags, and Surveys. See Intelligence overview.

**Knowledge connectors**: Integrations that connect the AI Assistant to existing documentation sources (SharePoint, Confluence, GitBook, KnowledgeOwl, or Zendesk) so it can answer questions from the organization's own content. See Knowledge connectors.

**NPS**: Net Promoter Score. A standardized survey type that measures how likely users are to recommend the application. See Surveys.

**Portfolio Overview**: A single screen that rolls up adoption, cost, and risk across every application, showing which decisions the data supports. See Portfolio Overview.

**Risk**: A HEART dimension that measures whether processes are followed and data stays compliant, fed by validator results. See Risk.

**Selectors**: The rule Userlane uses to find an element on the page. When a guide step, tooltip, or Contextual Action targets a button or field, a selector identifies that element. See [Creating selectors](/assistance/in-app-guidance/creating-selectors.md).

**Snippet**: A JavaScript tag that loads Userlane on a single application. The browser extension is the recommended deployment path; the snippet is an alternative for environments where the extension cannot be used. See How Userlane is deployed.

**Survey**: A question set shown to users inside the application. Userlane supports three types: standard surveys (custom questions), NPS, and CSAT. Surveys are part of Intelligence. See Surveys.

**Tags**: A single tracked action, such as a click on a specific element. Use a tag when you need to count whether something happens without tracking a multi-step process. Tags do not feed HEART. See [Tags](/intelligence/tags.md).

**Targeting**: Controlling where and when content appears by combining audience rules, URL patterns, and application state. See Targeting.

**Task Success**: A HEART dimension that measures whether people complete what they set out to do. It depends on task definitions existing in the application. See Task Success.

**Tasks**: A defined multi-step process tracked automatically. Tasks differ from guides in that they measure a process without prescribing how to complete it, and they report completion rate, efficiency, and time to complete. Tasks supply the data HEART reports on. See [Tasks](/intelligence/tasks.md).

**Tooltips**: An inline explanation attached to an element on the page. A tooltip can include a beacon marker that draws attention before the tooltip opens. See Creating tooltips.

**Validators**: A capability that checks what a user enters or selects against a rule, with three modes for different enforcement levels. Validator results feed the Risk dimension of HEART. See [Creating validators](/assistance/in-app-guidance/validators.md).

**Visibility**: The part of Userlane that shows which browser-based applications and AI tools are in use across the organization, from the browser extension alone: App Discovery and Portfolio Overview. See Visibility.

{% hint style="info" %}
**Looking for something else?**

Try [Orientation](/getting-started/orientation.md), A tour of the Userlane portal, or Contact and escalation.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.userlane.com/getting-started/glossary.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.