Deployment · AlefOS Documentation
Put one real workflow into production without rebuilding every tool.
We configure the company workspace, managers, permissions, groups and first workflows with your team, then support adoption for 90 days.
Guided Team setup · Manager permissions configured · 90-day adoption support
Week one outcome
Guided setupWorkspace
The company tenant and Owner are ready.
Managers
Scopes, visibility and permissions are configured.
First workflows
Initial Groups, sources and review routines are connected.
First result
The team reviews its first signals, missions and manager briefing.
A guided deployment
What happens during week one.
The first week establishes the company structure and first usable workflows. The following 90 days help the team refine permissions, integrations and habits.
Confirm the operating model
Identify the Owner, managers, teams, Groups and first connected sources.
Create the company workspace
Set up the tenant, Owner access and the first company structure.
Configure manager visibility
Define scopes, permissions, Groups and the signals each manager can use.
Launch the first workflows
Connect initial sources and review the first signals, missions and manager briefing.
Days 8–90 focus on onboarding, adoption, integration refinement and the habits that make company memory useful.
Configure Team for real work
Shared company memory needs the right structure, permissions and responsibilities before it becomes useful.
More than account activation
Deployment turns a Team subscription into working company memory.
Managers need configured access
Adding a manager requires permissions, defined responsibilities, groups, onboarding and training.
Start with the right structure
The goal is to begin with the right people, access rules and workflows instead of a random account setup.
What gets configured
The Owner, managers, team members, permissions, groups, integrations and initial workflows are configured around the company.
Team members and managers
Adding a team member is usually straightforward. Adding a manager changes visibility, responsibility and access.
Team member
Contributes to company memory through daily work.
Manager
Needs configured access, visibility rules, groups and onboarding.
Result
The company starts with structured memory and controlled access.
Detailed Deployment reference
Read the detailed Deployment reference below for roles, permissions, configuration and deployment.
Why deployment exists
Team is not only a company account to activate.
It is a company memory to configure.
Before AlefOS becomes useful across a company, the workspace needs the right Owner, managers, team members, groups, permissions, integrations and onboarding.
Deployment ensures that AlefOS starts with the right company structure, access rules and working model.
What deployment includes
Deployment can include:
- Company workspace creation.
- Owner setup.
- Manager setup.
- Permissions.
- Teams.
- Groups.
- Integrations.
- Initial configuration.
- Manager training.
- 90 days onboarding for the initial deployment.
The goal is not only to create accounts.
The goal is to make sure the company can use AlefOS as shared operational memory from the beginning.
Owner and managers
The Owner controls the company workspace and its main configuration.
Managers require more setup than standard team members because they need authorized visibility and defined responsibilities.
A manager’s authorized access can depend on:
- Which users they supervise.
- Which groups they can read.
- Which contacts or missions they can access.
- Which work activity they should see.
- Which actions they can validate.
- Which integrations are available within their responsibility.
This is why manager setup requires more preparation than standard team-member activation.
Adding team members vs adding managers
Adding a team member is usually straightforward.
A team member contributes to company memory through calls, messages, contacts, missions, appointments and notes.
Adding a manager is different.
A manager requires configured permissions, visibility rules, groups, training and onboarding.
The manager does not only use AlefOS.
The manager uses authorized company memory to guide the work within their responsibility.
Deployment packages
Deployment pricing depends on the company structure and the number of managers requiring configuration.
Current deployment packages:
- Team S: 1 manager including Owner - $1,500.
- Team M: 2 managers including Owner - $3,000.
- Team L: 4 managers including Owner - $5,000.
- Team XL: 8 managers including Owner - $9,000.
- Additional manager deployment: $750.
These packages cover the initial configuration required to make the Team workspace usable, controlled and ready for real work.
90 days onboarding
The initial Team deployment includes 90 days of onboarding support.
This period helps the company:
- Configure the company workspace correctly.
- Train the Owner and managers.
- Structure useful Groups.
- Confirm permissions.
- Review first Missions.
- Connect the right integrations.
- Correct early usage issues.
- Build habits around shared memory and controlled actions.
The first months matter because this is when company memory begins growing and becoming useful in daily work.
What deployment is not
Deployment is not a generic onboarding call.
It is not only account creation.
It is not a simple checklist.
Deployment is the configuration phase that turns AlefOS into working company memory with the right roles, permissions and working habits.
Key takeaway
Deployment is what turns a Team subscription into working company memory.
The simple idea:
Team members can be added quickly.
Manager access must be configured properly.
Company memory only works when access, visibility and habits are clear from the start.
Choose your next step
Build shared memory around the way your company already works.
Talk with AlefOS about users, permissions, providers and the first deployment workflow to connect.