AI Employee OS Guide

Understand the platform, its concepts and deployment options.

Welcome

I can explain AI Employees, Agents, Knowledge, Collections, Workspaces, Workflows, permissions and flexible deployment—from Managed Cloud to On-Premises and customer-provided infrastructure.

Explore a topic

AIOSAI Employee OS

Build governed AI Employees on approved company knowledge, modular capabilities and deployment models that fit your organization.

Build an AI Employee

Platform

  • Platform overview
  • Platform Atlas
  • Knowledge
  • AI Employees
  • Agents
  • Connectors

Build & operate

  • AI Employee Builder
  • Workflow Builder
  • Permissions
  • Analytics
  • Administration
  • Enterprise

Explore

  • Solutions
  • Healthcare
  • Construction
  • Manufacturing
  • Demo
  • Pricing

Resources

  • Learn Center
  • FAQ
  • Glossary
  • AI Documentation
  • Privacy
  • Imprint

© 2026 eban GmbH. All rights reserved.

TermsDPASLAContact
Skip to article
AIOS
AI Employee OS
Start free trial
HomeLearnTeams And Permissions

Platform

Platform overviewPlatform AtlasKnowledgeAI Employees

Build

AI Employee BuilderAgent StoreWorkflow BuilderConnectors

Operate

PermissionsAnalyticsAdministrationEnterprise

Explore

SolutionsDemoLearnPricing
Start 7-day free trial
Learn
Learn AI Employee OS

Getting started

What is AI Employee OS?What is an AI Employee?What is an Agent?AI Employees vs Agents

Platform

What is Ask AI?What are Conversations?What is Knowledge?What are Collections?What are Documents?What are Connectors?What is a Workspace?

Organization

What are Teams and Permissions?

Automation

What are Workflows?

Deployment

What is the Modular Architecture?What is Managed Cloud?What is Dedicated Cloud?What is On-Premises Deployment?What is Bring Your Own Infrastructure?

Reference

Frequently asked questionsProduct glossary
Organization•5 min read•Beginner

What are Teams and Permissions?

Control who can access AI Employees, Knowledge and capabilities across the organization.

Company Knowledge

Employee handbook

Policies and guidance

Technical manuals

Approved product documentation

Quality procedures

Controlled operational knowledge

Approved knowledge

Trusted company context

Available only to the AI Employees and people your organization authorizes.

Definition

Teams group people around shared responsibilities, while permissions define what each person or group may access and use.

Why it matters

Company Knowledge and business capabilities should not be available to everyone by default. Teams and permissions help the platform reflect real organizational responsibilities and information boundaries.

Real-world example

Separating HR and engineering access

The HR team can use employee-policy Collections and the HR Employee, while the engineering team can access technical documentation and the Engineering Employee. Shared company information remains available to both.

Key benefits

Reflect real departments and responsibilities

Limit access to sensitive Knowledge

Assign AI Employees to the right audiences

Scale governance as the organization grows

Common questions

Is every user an administrator?

No. Organizations can assign responsibilities and access according to the roles they define.

Can one user belong to several teams?

Where supported by the organization's setup, a user can participate in multiple teams and receive the appropriate combined access.

Related topics

What is a Workspace?

5 min read

What is Knowledge?

4 min read

What are Collections?

4 min read

PreviousWhat are Conversations?Continue learningWhat is the Modular Architecture?