Getting Started
Everything you need to go from sign-up to your first resolved ticket — in under 30 minutes.
New to Stack-Ops?
When you first sign in, you'll land on the main dashboard. It will be mostly empty — that's expected. Follow the four steps in this guide in order: learn what's here, configure your organization, add your team, then create your first ticket. After that you're operational.
What is Stack-Ops?
Understand the platform before you configure it
Stack-Ops is a connected IT operations platform built for internal IT teams. It replaces the traditional helpdesk with a workspace that links your ticket queue directly to the assets, employees, vendors, contracts, licenses, and inventory that sit behind every support request.
Instead of switching between spreadsheets, email threads, and separate tools, your team works from one place — opening a ticket and seeing the employee's assigned devices, active licenses, relevant vendor contracts, and full asset history all in context.
The platform is built around these core modules:
Tickets & Task Cases
Support intake with full context — asset, license, and SLA in one structured record.
Asset & Inventory
Track hardware, components, consumables, and licenses against your workforce.
Employee Lifecycle
Onboarding, offboarding, and asset assignments — documented and auditable.
Vendors & Contracts
Provider relationships, AMC contracts, and renewal windows in one place.
Additional modules — Knowledge Base, Subscriptions, Reports & Analytics, and Billing — are covered in the .
Set up your organization
Configure Stack-Ops for your team before adding users
Go to Settings → Organization. This is where your workspace identity and operating preferences live. The page has four tabs — configure them before inviting teammates so everyone works with the correct settings from day one.
Enter your company name, display name, industry, contact details (support email, billing email, phone, website), and billing address. Upload your organization logo from this tab.
Only relevant if your organization manages multiple sub-companies or clients. You can skip this tab on initial setup for single-company teams. Each company gets its own code, and users and assets can be scoped to specific companies.
Set the timezone, date format, time format (12h / 24h), currency, language, fiscal year start, and week start day. These affect timestamps, SLA deadlines, and renewal dates across the platform — set this before creating any records.
Enable or disable optional modules. Currently includes the Budget module toggle. Leave defaults unless your team specifically needs to turn a module off.
Organization settings can only be updated by users with the Admin role. Make sure your account has Admin access before configuring the workspace.
Invite your team
Add administrators, technicians, and end users to your workspace
Go to Settings → Users to manage your team. Stack-Ops uses role-based access — assign each person the role that matches what they need to do in the platform. Roles cannot be stacked; each user has one primary role.
Full access to all modules, settings, billing, and user management. Typically your IT manager or team lead. Keep the number of Admin accounts small.
IT staff who work tickets, manage assets, employees, and operations. Cannot access billing or organization settings. This is the role for most of your IT team.
Employees who submit support requests. They access a simplified portal to create tickets, check status, and browse the knowledge base. They do not have access to the operations area.
- 1Navigate to Settings → Users and click "New User".
- 2Enter the first name, last name, email address, and username.
- 3Select the appropriate role: Admin, Technician, or End User.
- 4Optionally link the user to an existing employee record and assign them to a department or position.
- 5Leave "Send Welcome Email" checked — the user receives a sign-up link to set their own password.
- 6Once they sign in, they appear as active in your user roster and can begin working immediately.
For large teams, use the Bulk Import option on the Users page to upload multiple users at once via spreadsheet. Contact support for the import template.
Importing your data
Migrate existing records into Stack-Ops before go-live
Most IT teams have existing data in spreadsheets — an asset register, employee list, vendor contacts, or license inventory. Stack-Ops supports bulk import for all core modules via spreadsheet. Contact support for the template for any module.
Recommended import order
Companies
Only if you use the multi-company feature. Companies must exist before employees and assets can be scoped to them.
Employees
Import your employee roster first. Employees are referenced when assigning assets and granting licenses — they must exist before those imports run.
Assets
Hardware assets — laptops, monitors, phones, printers. Include serial numbers, manufacturers, purchase dates, and warranty expiry dates. Assign to employees in this import or separately afterward.
Licenses
Software licenses with seat count, type, purchase date, expiry, and linked provider.
Components
Sub-items installed into assets — RAM, drives, GPUs. Components reference the asset they are installed in.
Consumables
Depletable items — toner, cables, batteries — with current quantity and minimum threshold.
Bulk import is available for Users, Employees, Assets, Licenses, Components, and Consumables. Contact support@stack-ops.io for the spreadsheet template for any module. Import employees before assets if you want assignment data included in the initial import.
Your first ticket
Walk through creating and resolving a support ticket end-to-end
Tickets in Stack-Ops are structured intake records, not message threads. Each ticket is assigned a unique number (e.g. TKT-001) and carries a category, priority level, SLA deadline, assignee, attachments, comments, internal notes, and a full activity timeline.
Priority levels — set the urgency for the team. SLA deadlines are calculated from the ticket category's configured hours, not priority.
- 1Click "New Ticket" from the Tickets dashboard.
- 2Enter a title and description. Set the category and priority — the SLA deadline calculates automatically.
- 3Optionally link the ticket to a specific asset, component, or license. This gives the assigned technician full context without leaving the ticket.
- 4Assign to a technician, or leave it unassigned for the team to pick up from the work queue.
- 5Use comments for requester-facing replies and internal notes for team-only context. Attach files up to 10 MB (images, PDF, Word, Excel, CSV, plain text).
- 6Progress the ticket through statuses: Open → In Progress → Resolved → Closed. Closed tickets can be reopened.
- 7On resolution, optionally link or create a Knowledge Base article so the fix is reusable next time.
The ticket detail page has a Timeline tab that logs every status change, assignment, asset link, component installation, consumable issue, and comment — a full audit trail for every support record.
The end-user portal
What employees see when they need IT support
Users with the End User role access a simplified portal — distinct from the IT operations area. The portal is designed for employees submitting support requests, not for IT management.
Submit a ticket
Create support requests using guided templates or a blank form. Templates pre-fill category and priority for common request types.
Track status
View all open and historical tickets — with current status, assigned technician, and any replies from the IT team.
Browse the knowledge base
Access published articles marked as end-user visible — for self-service troubleshooting and how-to guides.
Ticket templates available to end users
End users use the same Stack-Ops URL as the rest of the team. The portal view is determined by the role assigned at sign-in — no separate URL or app is needed.
You're set up. What's next?
With your organization configured, team invited, and first ticket created, you're operational. Explore the rest of the platform through the Product Guide.