Layi Docs

Services & Apps

Install reusable Layi apps such as Receptionist, HR/payroll, and AI Data, then run them from your workspace.

Last updated: June 2026

Install services, not raw tools

A Layi service is an installed app your team can open, configure, and operate from the dashboard. Examples include Receptionist, HR/payroll, and AI Data. Tools and providers sit underneath the service: for example, a Receptionist app may connect calendar, email, voice, or CRM tools, while an HR app may connect HRIS or payroll providers.

This keeps the user experience centered on the business workflow. Users install the app, then connect only the provider tools that app needs.

App-first UX
Install a complete workflow such as Receptionist, HR/payroll, or AI Data instead of starting from individual provider connectors.
Provider setup underneath
Connect Gmail, Outlook, calendars, HRIS, payroll, voice, CRM, or custom APIs only when the installed app needs them.
Shared runtime model
Installed apps share action history, approvals, compliance checks, and external API/MCP/SDK/A2A access when enabled.

Install flow

Use this path when you want to add a packaged business workflow to a workspace.

1

Browse app templates

Open the template marketplace and filter for the app family you need.

Open marketplace
2

Preview and install

Open a template detail page, review its actions, surfaces, connector needs, and compliance notes, then install it into your workspace.

Preview templates
3

Manage from My Apps

After installation, open the app workspace from My Apps to review status, cases, metrics, configuration, and runtime work.

Open My Apps

Example app families

The same install pattern works across app families. Capabilities depend on the installed template, configured providers, tenant permissions, and enabled actions.

Receptionist

Front office

Install a front-desk app for appointment intake, message triage, callback workflows, and customer handoff tracking.

  • Review appointment and message actions
  • Connect calendar, email, phone, or CRM tools when needed
  • Open the app from My Apps to monitor cases and handoffs

HR / Payroll

People ops

Install HR apps for staff records, onboarding, leave, payroll-adjacent workflows, and approval-gated people operations.

  • Review staff, leave, payroll, or benefits actions
  • Connect HRIS/payroll providers underneath the app
  • Require approvals for sensitive write/admin actions

AI Data

Expert ops

Install AI Data apps for verified expert routing, quality audit, rubric updates, identity workflows, and fraud-resistant review operations.

  • Install the AI Data templates needed for the demo or pilot
  • Open each app to review available actions and runtime state
  • Use QA and compliance outputs as evidence, not certification claims

Use an installed app

After installation, the app appears in My Apps. Open it to operate the workflow and review its state.

  • Review status and metrics

    Use the app workspace to inspect health, active work, case lists, metrics, and recent events.

  • Run allowed actions

    Read actions can usually run directly. Write, admin, export, or high-risk actions may require permissions or explicit approval.

  • Configure connectors

    Provider tools are connected underneath the service. A service can still install before every connector is configured.

  • Use external surfaces when needed

    For partner or developer access, enabled apps can expose safe operations through API, MCP, SDK, or the Layi A2A task bridge.

Permissions, approvals, and compliance

Installed apps are tenant-scoped and inherit the organization context. Compliance starts from your organization business profile, including configured industry, region or market, compliance regimes, and regulated data classes. Templates then add service-specific requirements, and every action execution can attach a compliance result to the outcome.

The current model is advisory and auditable: it can flag issues, attach compliance results, and create review events, but it should not be described as certification.

Org profile baseline
Business profile settings define candidate regimes and data classes based on the organization’s industry, region, and operating context.
Template additions
Installed apps such as Receptionist, HR/payroll, and AI Data can add their own compliance requirements on top of the org baseline.
Execution evidence
Each action can return a compliance payload with flags, violations, audit requirements, and review metadata when available.

Governance checklist

  • Tenant scope: apps and actions run inside the authenticated workspace/org.
  • Business profile: org industry, region, regimes, and data classes seed the compliance baseline.
  • Access class: actions are classified as read, write, admin, or export.
  • Dynamic requirements: templates and action payloads can add context-specific compliance scope.
  • Approval gates: sensitive operations can require explicit approval before execution.
  • Compliance checks: results can include passed, flagged, violations, audit requirements, and review metadata.
  • Audit trail: app actions and external calls are recorded for review and investigation.

Layi SDK

Use API, MCP, SDK, and A2A surfaces when you need developer or partner access to installed app operations.