Skip to main content

Internal IT Department Management on AtlasOS

AtlasOS adapts to the way internal IT departments operate — providing a lean, focused platform for fleet management, asset lifecycle tracking, security posture monitoring, and service desk operations without client-facing modules or billing overhead.

Who is this for? In-house IT departments, corporate technology teams, and internal service desks that manage devices, infrastructure, and security for their own organisation.

Terminology

AtlasOS maps its universal concepts to internal IT language:

AtlasOS ConceptInternal IT Term
EntityDepartment
EntitiesDepartments
EngagementChange Request
ComplianceSecurity Policies
ServiceService

You will see these labels throughout the sidebar, dashboards, and reports.

Enabled Modules

The Internal IT vertical ships with a deliberately lean set of modules. This is an internal operations vertical, not a client-facing practice — so many modules found in other verticals are intentionally disabled.

ModulePurpose
Smart InboxRoute internal support emails and vendor correspondence
TasksTrack change requests, maintenance work, and support items
ChatInternal team communication
AI AgentsAutonomous workflow assistance and intelligent triage
RMM+Level.io integration for endpoint fleet management
Asset LifecycleHardware inventory, warranty tracking, and refresh planning
Security PostureEndpoint protection status and patch compliance monitoring

What is NOT enabled

The following modules are disabled in this vertical:

  • Billing — internal departments do not invoice other departments via AtlasOS.
  • Time Tracking — no billable hour logging.
  • Client Portal — no external-facing portal.
  • Compliance Calendar — no statutory compliance tracking. Security Policies replace this.
  • Contracts — no contract management.
  • Onboarding Forms — no client intake forms.
  • Broadcasts — no bulk external communications.
  • Documents — document management is not enabled by default.
  • SLA Tracking — not applicable for internal operations.
  • Project Milestones — not enabled by default.

There are no compliance bodies or obligation types configured for this vertical.

Entity Types

Entity TypeUse Case
CompanyInternal departments and business units

Only the company entity type is available. This vertical does not use sole_prop or other entity types.

Default Landing View

When you log in, AtlasOS opens to the Tasks view — your active support and change request queue.

Getting Started

  1. Create your practice and select In-House IT as your firm type during the setup wizard.
  2. Connect Level.io for fleet management — link your Level.io account under Administration > Integrations > RMM+ to enable endpoint monitoring, alert ingestion, and device inventory.
  3. Import departments and locations — add your organisational departments and physical sites so that assets and tickets can be grouped logically.
  4. Configure asset tracking — set up your hardware register with warranty dates, assigned users, and refresh cycle targets.
  5. Invite your team and assign roles (IT administrators, technicians, service desk agents).
  6. Start operating — incoming support emails auto-route via Smart Inbox, fleet alerts populate your queue, and asset lifecycle tracking begins.

Next steps: Read the Internal IT Overview for the full configuration reference, or jump to Fleet & Devices to set up endpoint monitoring.


For shared platform features (Smart Inbox, AI Advisory, Practice Admin, Dashboard), see the Shared Features page which links to the main Accounting documentation.