Getting Started — Your First 15 Minutes
This guide gets you from "never used Nembl" to "I just submitted and resolved a real request" in about 15 minutes. We'll set up an IT Support service end to end — the same shape works for HR requests, vendor approvals, customer onboarding, anything.
Goal: at the end you'll have a working Service, an Offering, an Inbox that catches submissions, and one completed Request. Nothing is throwaway — you can keep it as the starting point for your real IT Support process.
What you'll need
- A working email address (we'll send you a sign-in link)
- About 15 minutes of focused time
- Optional: a teammate willing to be invited (you can skip this and do everything yourself)
Step 1 — Sign up (1 min)
Open Nembl
Go to nembl.devopspolis.com (opens in a new tab) and click Sign Up.
Create your login
Enter your name, email, and a password. Verify your email by clicking the link Nembl sends you.
Land on your Dashboard
You're now signed in with a free Individual account. The Dashboard greets you and shows empty stats — that's expected for a brand-new account.
Individual vs Company: a fresh signup gives you an Individual account (one person, free). To bring teammates in, you'll create a Company in the next step. You can always switch back to your Individual account from the header account-switcher.
📸 Screenshot opportunity: Dashboard for a brand-new account — empty state with the Getting Started checklist visible.
Step 2 — Create a Company (2 min)
A Company is the tenant that holds your services, workflows, users, and inboxes. Even if you're a solo founder, create one — it's where you'll grow.
Open the account switcher
Click your initial in the top-right header.
Create a Company
Pick Create Company. Enter a name (e.g. "Acme Corp") and click Create.
You're now in the Company context
The header changes to show the Company name. The sidebar gains the Admin group with Services, Workflows, IAM, etc.
Company accounts require a paid plan after a 14-day trial. The Free Individual account stays free forever and works fine for solo testing.
Step 3 — Create your first Service (3 min)
A Service is the category of work your team handles. "IT Support" is one service; "Marketing Briefs" would be another.
Go to Admin → Services
Click Services under the Admin group in the sidebar.
Click New Service
A modal opens.
Fill in the basics
- Name:
IT Support - Slug: leave the auto-generated
it-support - Description:
Hardware, software, and access requests for the team - Pick an icon and color if you like
Save
You land on the new service's detail page. Status is DRAFT — that's fine; we'll publish it after we add an offering.
📸 Screenshot opportunity: New service detail page showing DRAFT badge + empty Offerings tab.
Step 4 — Add an Offering (2 min)
An Offering is a specific thing under a Service. "IT Support" can have offerings like "New Laptop", "Software Install", "Reset Password". Each Offering can have its own form, intake rules, and workflow.
Open the Offerings tab
On your IT Support service's detail page, click Offerings.
Click New Offering
Fill in:
- Name:
New Laptop - Slug:
new-laptop - Short description:
Request a new company laptop
Save
The Offering is created in DRAFT. Optional: click Form to add fields like "Employee Name", "Department", "Laptop type" — but you can skip this and Nembl will use a default form.
Publish the Offering
Click the Publish button at the top right. Confirm. Status flips to PUBLISHED.
Publish the parent Service
Go back to the Service detail (breadcrumb). Click Publish. The Service is now live.
Both the Service and the Offering must be PUBLISHED for users to see them in the Service Catalog. DRAFT entities are admin-only.
Step 5 — Submit your first Request (1 min)
Now the fun part — act as a regular user submitting a request.
Open the Service Catalog
Click Service Catalog in the sidebar.
Click IT Support
You'll see the offerings. Click New Laptop.
Click Submit Request
Fill in the form (anything will do for testing). Set Priority to Medium. Click Submit.
See it appear in My Requests
The page redirects to your new Request's detail view. You can also see it under My Work → My Requests.
📸 Screenshot opportunity: Submitted request detail page with status PENDING and a fresh activity log entry.
Step 6 — Process the Request (3 min)
By default, every Service has an Inbox where new submissions land for triage.
Open the Inbox
Go to Admin → Inboxes. You'll see the auto-created IT Support — New Laptop inbox with 1 pending badge.
Open the Inbox detail
Your test request is sitting there.
Accept the request
Click it open and hit Accept. The status moves from PENDING to ACCEPTED.
Mark it complete
For this demo, click Complete to close the request. In real life, you'd advance through your workflow phases instead.
Verify
Go back to My Requests — the request now shows COMPLETED.
📸 Screenshot opportunity: Inbox view with pending count, Accept/Reject buttons visible.
What you just built
In ~15 minutes you set up:
- ✅ A Service ("IT Support") that other users can see in the catalog
- ✅ An Offering ("New Laptop") with a default submission form
- ✅ An Inbox (auto-created) that catches new submissions
- ✅ The full lifecycle from submit → triage → accept → complete
This is the smallest viable shape of every Nembl process. From here, you scale by adding Workflows (multi-step phases with approvals and automation), Forms (custom fields per Offering), Responsibilities (who handles what), and Agents (AI that triages or processes phases).
Where to go next
Pick what matches your goal:
| Goal | Read this |
|---|---|
| Add multi-step approval to your Service | Workflow Builder Overview |
| Customize the submission form | Forms |
| Bring teammates in and assign permissions | Users → Roles & Permissions |
| See worked examples for common processes | Examples |
| Wire AI agents to triage automatically | AI Agents |
| Sell services to other Companies | B2B Registry |
Or just keep clicking around — nothing you do in your trial Company can break anything outside it.