GOVERNANCE

Automation should not mean giving up control.

Define who can access what, which actions run automatically, which require approval, and what gets recorded.

Access and automation are configured around your systems, permissions, governance, and operating requirements.

LotLight ACC governance — role-based access, human approval gates, governed execution, and append-only audit trail across connected dealership systems

Illustrative view of role-based access, approval controls, and append-only action history.

WHO CAN DO WHAT

Every action starts with knowing who is asking.

ACC should not treat every employee the same. A request passes through identity, role, permissions, and workflow rules before anything runs.

  1. REQUEST
  2. IDENTITY
  3. ROLE
  4. PERMISSION
  5. WORKFLOW RULE
  6. ACC

POLICY CHECKS BEFORE EXECUTION

  1. 1
    ACCESS POLICYIs this user allowed to request the action?
  2. 2
    SYSTEM POLICYDoes the connected platform permit this operation?
  3. 3
    WORKFLOW POLICYIs this action allowed to execute automatically?
  4. 4
    APPROVAL POLICYDoes an authorized person need to approve it first?

A single store may use simple department-level permissions. A group can apply broader policy by rooftop, region, role, and workflow. Dealer Group Governance.

The user sees Chat. ACC checks the controls underneath.

ACCESS AND APPROVAL

Access and automation are configured around your rules.

ACC can read, prepare, and act within the access and controls approved for the deployment. Deployment scope is defined by your organization.

READ

Retrieve approved information.

PREPARE

Assemble reports, exceptions, recommendations, or proposed changes.

ACT

Perform approved actions where access and permissions allow.

ACCChat Workspace
ILLUSTRATIVE DEMONSTRATION
Update this customer record and notify the service manager.

Approval required before I make this change.

This demonstration simulates approval and execution; it does not access dealership systems.

Approval rules may vary by:

  • role
  • workflow
  • rooftop
  • action type
ACCOUNTABILITY

See what happened after the automation runs.

Action HistoryAppend-only
  1. 8:14 AM
    Lead follow-up workflow started
  2. 8:14 AM
    User identity verified
  3. 8:14 AM
    CRM read completed
  4. 8:15 AM
    Follow-up action approved
  5. 8:15 AM
    Customer record updated
  6. 8:15 AM
    Workflow result returned through Chat

This append-only audit history can show:

  • who initiated
  • what ran
  • which systems were involved
  • whether approval occurred
  • what result was returned
YOUR OPERATING BOUNDARY

Your data should work inside the environment your organization approves.

LotLight ACC is built on L2H.ai's Agentic Command Center platform, which provides the underlying workflow, governance, integration, and control architecture.

Architecture and controls are designed and documented to support enterprise security requirements. Framework mappings and current assurance documentation can be reviewed during the security process.

Your data. Your workflows. Your rules.

REQUEST A DEMO

See how ACC can automate without giving up control.

Bring us one workflow and the rules around it. We will map where ACC reads, where it acts, where approval belongs, and what gets recorded.