Auto, Apps, Integrations & Files

This guide covers the company-level connection and knowledge surfaces that users most often confuse:


The Core Split

The company dashboard intentionally separates connection surfaces.

Apps

Use Apps for company-scoped app connections and app recommendations.

This is the right place for app-style providers and company app groups.

Integrations

Use Integrations for company-scoped Google Workspace services and similar built-in company integrations.

This is the right place for:

SOPs

Use SOPs for operating guidance and reference material that teaches the company how you want it to work.

Files

Use Files for the documents and artifacts the company already has or creates over time.


Apps: What You Manage There

The current Apps tab is the company’s main app-management surface.

Company Apps page showing the connected app catalog

Use it to:

This is where app connections belong when the company needs a provider like a business tool, sales tool, support tool, or workspace tool that is not part of the built-in Google integration lane.


Integrations: What You Manage There

The Integrations tab is the company’s Google Workspace surface.

Use it to:

If a company plan depends on Google tools, this is the place to make sure they are attached to the company correctly.

Company Integrations page showing connected Google services


SOPs: What Belongs There

The SOPs tab is for the reference material that defines how the company should operate.

Typical examples:

This is the best place to upload the knowledge you want the company to follow consistently.

Training mode can reuse that company guidance, but the files created during task training are reviewed inside Train, not managed as general SOP uploads.


Files: What Belongs There

The Files tab is for the broader company file library.

The current tab supports:

Company Files page showing folders and delivered work

This is where users usually go when they want to review:

This is different from the training bundle review. Training creates task-specific guidance files for one task run, while Files is the broader company file library.


Managed Website Support In Files

If a company is using a generated or managed website, the Files tab becomes even more important.

That surface can include website-related state such as:

So for companies that need a website, Files is not just a document browser. It becomes part of the website operations surface too.


These tabs complete the same operating system even though they are not the primary connection surfaces:

Employees

Use Employees for real people tied to the company and for the routing details that help the company know who to involve.

Channels

Use Channels for the delivery endpoints the company can use, including messaging routes and company call-routing surfaces.

Profile

Use Profile for company identity, website details, logo, company stage, and other core profile fields.

Skills

Use Skills for the company’s skill-management surface.

Memory

Use Memory for long-lived company context, including boot memory, categories, semantic memory indicators, and generated memory files.

This is where the user refines persistent company context rather than only reviewing one live chat or one task.

Usage

Use Usage for company-level cost and activity measurement over time.


Quick Decision Rule

Use this rule when you are not sure where to go: