{
  "title": "Deployment",
  "internal_name": null,
  "slug": "deployment",
  "url": "https://alefos.ai/documentation/deployment",
  "json_url": "https://alefos.ai/documentation/deployment.json",
  "summary": "See what happens during the first week of a guided AlefOS Team deployment.",
  "description": "We configure the company workspace, managers, permissions, groups and first workflows with your team, then support adoption for 90 days.",
  "category": "Business",
  "last_updated": "2026-07-03",
  "keywords": [
    "deployment",
    "Team setup",
    "onboarding",
    "managers",
    "permissions"
  ],
  "sections": [
    {
      "heading": "Why deployment exists",
      "content": "Team is not only an account to activate.\n\nIt is a company memory to configure.\n\nBefore AlefOS can become useful for a team, the workspace needs the right structure: owner, managers, users, groups, permissions, integrations, visibility rules and onboarding.\n\nDeployment exists to make sure AlefOS starts cleanly, with the right operating model instead of a random account setup."
    },
    {
      "heading": "What deployment includes",
      "content": "Deployment can include:\n\n- Tenant creation.\n- Owner setup.\n- Manager setup.\n- Permissions.\n- Teams.\n- Groups.\n- Integrations.\n- Initial configuration.\n- Manager training.\n- 90 days onboarding for the initial deployment.\n\nThe goal is not only to create access.\n\nThe goal is to make sure the company knows how to use AlefOS as operational memory from the beginning."
    },
    {
      "heading": "Owner and managers",
      "content": "The Owner controls the company tenant and the first management layer.\n\nManagers require more setup than regular users because they need authorized visibility.\n\nA manager cockpit can depend on:\n\n- Which users they supervise.\n- Which groups they can read.\n- Which contacts or missions they can access.\n- Which signals they should see.\n- Which actions they can validate.\n- Which integrations are connected to their scope.\n\nThis is why manager deployment is treated differently from simple user activation."
    },
    {
      "heading": "Adding users vs adding managers",
      "content": "Adding a field user is usually simple.\n\nA field user mainly feeds the memory through daily work: calls, messages, contacts, missions, appointments and notes.\n\nAdding a manager is different.\n\nA manager requires configuration, permissions, visibility rules, groups, cockpit setup, training and onboarding.\n\nThe manager does not only use AlefOS.\n\nThe manager drives part of the company from AlefOS memory."
    },
    {
      "heading": "Deployment packages",
      "content": "Deployment pricing depends on the Team structure and the number of managers to configure.\n\nCurrent deployment packages:\n\n- Team S: 1 manager including Owner - $1,500.\n- Team M: 2 managers including Owner - $3,000.\n- Team L: 4 managers including Owner - $5,000.\n- Team XL: 8 managers including Owner - $9,000.\n- Additional manager deployment: $750.\n\nThese packages cover the initial configuration work needed to make the Team workspace usable, controlled and ready for real work."
    },
    {
      "heading": "90 days onboarding",
      "content": "The initial deployment includes 90 days of onboarding support.\n\nThis period helps the company:\n\n- Configure the tenant correctly.\n- Train the Owner and managers.\n- Structure useful Groups.\n- Confirm permissions.\n- Review first Missions.\n- Connect the right integrations.\n- Correct early usage patterns.\n- Build habits around memory and validation.\n\nThe first months matter because this is when the company memory starts growing."
    },
    {
      "heading": "What deployment is not",
      "content": "Deployment is not a generic onboarding call.\n\nIt is not only account creation.\n\nIt is not a simple checklist.\n\nDeployment is the configuration phase that turns AlefOS into a working company memory with the right roles, scopes and habits."
    },
    {
      "heading": "Key takeaway",
      "content": "Deployment is what turns a Team subscription into a real operating system for the company.\n\nThe simple idea:\n\nUsers can be added quickly.\n\nManagers must be configured properly.\n\nCompany memory only works when access, visibility and habits are clear from the start."
    }
  ],
  "typical_questions": [
    "What happens before kickoff?",
    "What becomes usable during week one?",
    "What does AlefOS configure for managers?",
    "What does the company need to prepare?",
    "What happens during the 90-day onboarding?"
  ],
  "related_pages": [
    "team",
    "contact",
    "groups",
    "whatsapp",
    "call-provider",
    "meeting-providers"
  ],
  "important_notes": [],
  "markdown": "# Deployment\n\nLast updated: 2026-07-03\n\nWe configure the company workspace, managers, permissions, groups and first workflows with your team, then support adoption for 90 days.\n\n## Why deployment exists\n\nTeam is not only an account to activate.\n\nIt is a company memory to configure.\n\nBefore AlefOS can become useful for a team, the workspace needs the right structure: owner, managers, users, groups, permissions, integrations, visibility rules and onboarding.\n\nDeployment exists to make sure AlefOS starts cleanly, with the right operating model instead of a random account setup.\n\n## What deployment includes\n\nDeployment can include:\n\n- Tenant creation.\n- Owner setup.\n- Manager setup.\n- Permissions.\n- Teams.\n- Groups.\n- Integrations.\n- Initial configuration.\n- Manager training.\n- 90 days onboarding for the initial deployment.\n\nThe goal is not only to create access.\n\nThe goal is to make sure the company knows how to use AlefOS as operational memory from the beginning.\n\n## Owner and managers\n\nThe Owner controls the company tenant and the first management layer.\n\nManagers require more setup than regular users because they need authorized visibility.\n\nA manager cockpit can depend on:\n\n- Which users they supervise.\n- Which groups they can read.\n- Which contacts or missions they can access.\n- Which signals they should see.\n- Which actions they can validate.\n- Which integrations are connected to their scope.\n\nThis is why manager deployment is treated differently from simple user activation.\n\n## Adding users vs adding managers\n\nAdding a field user is usually simple.\n\nA field user mainly feeds the memory through daily work: calls, messages, contacts, missions, appointments and notes.\n\nAdding a manager is different.\n\nA manager requires configuration, permissions, visibility rules, groups, cockpit setup, training and onboarding.\n\nThe manager does not only use AlefOS.\n\nThe manager drives part of the company from AlefOS memory.\n\n## Deployment packages\n\nDeployment pricing depends on the Team structure and the number of managers to configure.\n\nCurrent deployment packages:\n\n- Team S: 1 manager including Owner - $1,500.\n- Team M: 2 managers including Owner - $3,000.\n- Team L: 4 managers including Owner - $5,000.\n- Team XL: 8 managers including Owner - $9,000.\n- Additional manager deployment: $750.\n\nThese packages cover the initial configuration work needed to make the Team workspace usable, controlled and ready for real work.\n\n## 90 days onboarding\n\nThe initial deployment includes 90 days of onboarding support.\n\nThis period helps the company:\n\n- Configure the tenant correctly.\n- Train the Owner and managers.\n- Structure useful Groups.\n- Confirm permissions.\n- Review first Missions.\n- Connect the right integrations.\n- Correct early usage patterns.\n- Build habits around memory and validation.\n\nThe first months matter because this is when the company memory starts growing.\n\n## What deployment is not\n\nDeployment is not a generic onboarding call.\n\nIt is not only account creation.\n\nIt is not a simple checklist.\n\nDeployment is the configuration phase that turns AlefOS into a working company memory with the right roles, scopes and habits.\n\n## Key takeaway\n\nDeployment is what turns a Team subscription into a real operating system for the company.\n\nThe simple idea:\n\nUsers can be added quickly.\n\nManagers must be configured properly.\n\nCompany memory only works when access, visibility and habits are clear from the start.\n\n## Typical questions\n\n- What happens before kickoff?\n- What becomes usable during week one?\n- What does AlefOS configure for managers?\n- What does the company need to prepare?\n- What happens during the 90-day onboarding?"
}