Getting started
Follow this path after you register and verify your email. Each step matches routes in the authenticated application.
Prerequisites
- A verified user account (email/password or Google OAuth if enabled).
- At least one workspace—you typically land in your first workspace automatically after registration.
- Organizations on Google Workspace or Microsoft 365 can follow the same onboarding path; we prioritize support and documentation for both productivity suites.
Step-by-step
-
Sign in
Use email and password or Google OAuth if your environment enables it. Multi-factor authentication may be required by your administrator.
-
Open your workspace
You land on the analytics dashboard. URLs are scoped with your workspace slug, for example
/w/your-workspace/dashboard. Bookmark this for your team. -
Create a link
Go to Create link, set a title and HTTPS destination, optional UTM defaults and campaign tag, then save. Every link ships with a matching QR code you can export. Owners and admins manage content; analysts consume analytics.
-
Distribute the short link
Share the
/t/{short_code}URL in ads, email, and social—or place the QR asset on packaging and signage. Clicks and scans enqueue asynchronously—see Architecture. -
Invite teammates
Owners and admins invite members from Team settings. Invitations are email-based and bind the user to a workspace role.
Custom domains (white-label)
Owners and Admins can serve short links from client-branded domains (e.g. go.clientbrand.com) via Workspace settings → Domains. Add the hostname, create the ownership TXT record at _iutils-links-challenge.{your-domain} with the token shown, and point a CNAME (or A/ALIAS at the apex) at links.iutils.net. Verification runs automatically and is re-checked daily; if the TXT record disappears the domain stops serving and Owners/Admins are emailed.
Once verified, assign the domain to links when creating or editing them — the copy button, share panel, public stats page, and QR codes all use the branded URL. Unknown short codes on a custom domain land on its configurable not-found URL. Note: short codes remain globally unique across all domains, and TLS is expected to terminate at your edge/proxy (Cloudflare, Caddy, Forge).
For administrators
Before go-live, confirm Stripe keys, mail transport, queue workers on the ingestion queue, and cron for the scheduler. See Operations.