Control

Configure the access, systems, credentials and runtime settings that determine what a Lleverage Project is allowed to do.

Use Control when the operational process is clear but Lleverage still needs the right authority and environment around it: access to an ERP or mailbox, people in the right Project, an Agent routed into Teams, a schedule, credentials, or a runtime setting.

Control explains how Lleverage is configured to operate. Broader questions about who owns the process, where people remain accountable and how changes reach production live under Governance, Rollout and operations and Security and assurance.

Project Operators do not see Control. Visibility can also vary by role and project configuration.

Connect the systems the work needs

Use Connections to authorise external accounts and integration actions used by Agents and Workflows.

If people should talk to the Agent through Slack or Microsoft Teams, use Channels instead. Connections provide system capability; Channels route conversations.

Decide who can access the Project

Use Members and Roles and Permissions to manage Project membership and current roles.

For organisation-level authentication, see Enterprise SSO Setup.

Configure when and how Agent work starts

Use Schedules for recurring Agent runs.

Use Settings for Project identity, Agent behaviour and navigation configuration.

Workflow schedules are configured through the Workflow publishing path; see Scheduling workflows.

Provide runtime credentials and configuration

Use:

• API Tokens for Project-scoped API access;

• AI Models for model-provider credentials;

• Databases for database-provider connections;

• Secrets for sensitive values;

• Variables for reusable non-secret configuration.

Do not copy credentials into ordinary Files, Skills, prompts or documentation. Variables are not secret storage. See Secrets and variables reference.

Measure execution

Use Metrics to define measurements that Workflows can emit and Monitoring can chart or inspect.

Scope matters

Control is presented inside a Project, but not every configuration object is purely Project-scoped. Read the scope notes on each page before assuming a change affects only the Project you are currently viewing.

Where to go next

• External systems → Connections

• Slack / Teams Agent routing → Channels

• Membership and roles → Members

• Project / Agent configuration → Settings

• Operational ownership and human boundaries → Governance