> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ones1ght.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Concepts & Glossary

> Domain terms in the OneS1ght console — areas, positioning, Skills, policies, roles, and more.

This page defines the core terms used throughout the OneS1ght console. Each term is explained once for administrators seeing it for the first time. For screen-by-screen usage, see the documentation for each area.

## Space & positioning

<AccordionGroup>
  <Accordion title="Store / Area" icon="location-dot">
    The top-level unit that positioning targets. An area contains zones and points.
  </Accordion>

  <Accordion title="Zone" icon="draw-polygon">
    A polygon region drawn on the store floor plan. Zones are a pass-through of floor-plan data provided by GeoSpace.
  </Accordion>

  <Accordion title="Point" icon="location-pin">
    A OneS1ght-specific spot. Types include standing sign, sampling table, end cap, and other.
  </Accordion>

  <Accordion title="Positioning / UWB" icon="satellite-dish">
    The technology that identifies visitor location. Based on UWB (ultra-wideband), it captures in-store position and movement.
  </Accordion>

  <Accordion title="GeoSpace (GCH)" icon="building">
    The partner that provides building, floor-plan, and zone data. OneS1ght integrates this data as a pass-through.
  </Accordion>

  <Accordion title="North Star metric" icon="star">
    The core metric OneS1ght tracks is the **location → purchase conversion rate**.
  </Accordion>
</AccordionGroup>

## AI & data

<AccordionGroup>
  <Accordion title="Skill" icon="puzzle-piece">
    An installable AI analysis feature. Whether it can be installed is determined not by domain but by **whether the connected data requirements are met**.
  </Accordion>

  <Accordion title="Data Source" icon="database">
    An external data connection that a Skill reads. It connects and configures data rather than copying it.
  </Accordion>

  <Accordion title="BYOK (Bring Your Own Key)" icon="key">
    A model where the customer registers their own LLM provider API key. One default model is designated per provider.
  </Accordion>
</AccordionGroup>

## Policies & agents

<AccordionGroup>
  <Accordion title="Action agent" icon="robot">
    The entity that executes policies through features and automation rules. You turn features on and configure rules per store.
  </Accordion>

  <Accordion title="Policy / Action" icon="bullhorn">
    The behavior to execute. It splits into two tracks:

    * **B2B store-manager policy**: measures for improving store operations
    * **B2C customer-app (SDK) policy**: personalized measures through the customer app
  </Accordion>
</AccordionGroup>

## Roles (permissions)

The console has three system roles. Menus and features are shown according to role.

| System role | Display name | Description                                                            |
| ----------- | ------------ | ---------------------------------------------------------------------- |
| owner       | Owner        | Organization owner. Can manage billing, subscription, and org deletion |
| manager     | Manager      | Operational management of org, positioning, agents, and more           |
| viewer      | Member       | Read-focused access to dashboards, reports, and more                   |

<Info>
  Menu visibility is split into **all** (everyone, including Members), **manage** (Owner + Manager), and **owner** (Owner only). Each screen's documentation shows its access level at the top.
</Info>