Team accounts — without the shared password.

Invite people by email and give each one their own login, their own two-factor and the role their job calls for — full admin down to read-only, with a free Billing seat for your accountant. Uptimia never bills per user — seats are part of the plan, not a line on the invoice.

Start free trial → View pricing
No per-user pricing Free billing seats No credit card
Monitor types, one team
12
Team seats up to
100
Checkpoints
171+
Countries covered
70+

From invite to audit trail

Dana was invited on Monday as an Editor limited to two client groups. By Tuesday she was editing monitors — and the other two groups were still absent from her account, not greyed out in it.

Mon Priya invites dana@caldmont.comPicks the role and the monitor groups before the invite goes out role: editor
Mon Dana sets a password and her own 2FAHer own login — not a shared one; two-factor is hers to manage role: editor
Tue She edits monitors — in her 2 groups onlyEverything outside her scope simply isn't there for her role: editor
later Priya changes the role — one clickChange or revoke anytime; a demoted API key loses access on its next request logged
one loginper person
Every change is on the record.audit log
Invites, role changes, scope changes, removals — the last 20 access changes read back as "who did what", so a change in access is never a mystery.
invited · Dana · editorscope · 2 groupsrole changed · editor → adminvisible to the owner and admins
The alternative is one shared login. Everyone has every permission, nobody has their own two-factor, and the log can't tell you who paused the monitor or deleted the contact. who did that?

What each role can touch

One column per person you'll invite — the developer who runs everything, the client who only looks, the accountant who only needs the invoices. Pick the closest fit; change it later with one click.

Capability Owner Admin Editor Read-only Billing
View monitors, incidents & logsthe dashboard, read-only—
Create & edit monitorsadd, pause, configure——
Contacts & alertingwho gets paged, and how——
Status pagespublic and private——
Invite people & set rolesteam & audit log———
Integrations, API keys & securityaccount-level settings———
Plan & usagehow much of the plan is used◑◑◑
Billing & invoicesprices, cards, receipts———
Delete the accountowner only————
Full access ◑ Usage counters only — no prices, cards or invoices — No access Every role manages its own password and two-factor auth.
Safe to hand out

Read-only really means read-only

That's what makes it safe to bring in a client, a contractor or a junior. Hiding a button is a courtesy, not a control — Uptimia checks the permission on the server for every read and write, so a request a role isn't allowed to make is refused, however it's made.

  • Safe for outsiders — a client on a Read-only seat can watch their monitors, and that's all they can do
  • The same rules everywhere — the app, the menu and the API all answer to one permission map
  • Removed means removed — take a seat away and its session and keys stop working on their next request
How roles are enforced →
Sam Read-only clicks Delete
DELETE /api/v2/monitors/42
server checks the role
Request refused
403 Forbidden
code: forbidden
required: monitoring.manage
role: viewer
The delete never runs. Read-only members can look at everything and acknowledge an incident — but they can't change it.
The check runs on the server, not in the browser — so it can't be sidestepped by anyone clever with the address bar. 403

Scope, billing seats and API keys

Monitor-group scoping

Editors scoped to their own groups

An agency handling ten clients doesn't want every editor seeing every account. Scope an Editor or Read-only member to specific monitor groups, and the rest of the fleet is invisible to them — in lists, on the dashboard, in search and in exports.

  • Pick the groups a member can see — everything else is treated as if it doesn't exist
  • New monitors they create land in their own scope automatically, so they never lose sight of their own work
  • Enforced on the server — an out-of-scope monitor id answers as though it does not exist, on reads and writes alike
How monitor groups work →
Dana's monitorsEditor · 2 groups
Client · Marlbeck7 monitors
Client · Tinbarrow5 monitors
Client · Harrowfenout of scope
Internal & stagingout of scope
Harrowfen and staging aren't hidden — they're absent. Dana can't open, edit or even find a monitor outside her two groups. 2 of 4
The billing seat

A free seat for your accountant

Your accountant needs the receipts, not the monitors. The Billing seat sees plans, invoices and payment — and nothing else. It doesn't count against your plan's seats, and it never receives an alert.

  • Free — a Billing seat isn't counted toward your plan's member limit
  • Billing only — no monitors, no incidents, no alerts, no contacts
  • Switch a member to Billing and their alerting is torn down cleanly; switch them back and the seat count re-checks
See plans & seats →
AF
Alex Freemanalex@caldmont.com
Billing
Sees plans, invoices and payment method
No monitors, incidents or alerts
Can't be added to a team or a contact
Free seat · not counted toward your plan
The accountant gets the invoices, never a 3 a.m. page. A Billing seat lands on the plans page and never sees monitoring. free
Automation, same rules

A script can't outrank its owner

Teams automate — deploy hooks, scripts, the mobile app. Every API key issued to a member runs as that member: same role, same monitor groups. Demote or remove the person and their keys follow, so there's no back door through a script somebody wrote last year.

  • A key acts as its owner — it can do exactly what the member can do, and nothing more
  • Changes take hold at once — demote a member and their key is demoted from its next call
  • Leavers lose their keys — remove a seat and every key it held stops working
API keys & roles →
App sign-in keyissued to Dana
Editor
****************************c19a
Runs as Editor · scoped to 2 groups
Can't touch team, billing or API keys
Role re-checked on every request
Owner-minted keys keep full authority. Only a key carrying a member's seat inherits that member's limits — automation never quietly outgrows the person behind it. live

Bring your team in.Keep hold of the keys.

Team seats come with the plan — Uptimia never bills per user. Billing seats are free on top, and the 30-day trial starts with fifty seats.

Start your free 30-day trial →
30 days free no credit card cancel anytime

How adding a teammate works

Three steps on the Team members page — the access is decided before the invite goes out.

Step 130 s

Invite by email, pick a role

Enter an email, choose one of the four roles you hand out — the fifth, Owner, is you — and, for an Editor or Read-only member, the monitor groups they can touch. A panel spells out what they'll be able to do.

Email
dana@caldmont.com
AdminEditorRead-onlyBilling
They'll be able to edit monitors in 2 groups
Step 2their turn

They set their own login

The invite lands in their inbox. They choose a password and their own two-factor — their credentials, not a copy of yours. Pending invites can be resent, copied or revoked from the list.

Set a password
••••••••••••
Two-factor
Their own 2FA — managed by them
LaterActivate →
Step 3from then on

They see only their role

Their sidebar, their routes and their API keys all follow the role. Change it later with one click from the role badge — every change is written to the audit trail.

#caldmont · access log
Priya Tue
● role changed — Dana → Editor
scope · 2 groupsby owner
Also logged invitedremoved

Also included

An audit trail of access changes

The last 20 invites, role changes, scope changes and removals — each one reading back as "who did what". Visible to the owner and admins, so a change in who-can-do-what is never a guess.

Priya changed Dana → EditorROLE Marco invited jordan@…INVITE Priya removed a memberREMOVED

Two-factor, per person

Every seat manages its own 2FA. Locked out? An owner or admin can reset a member's two-factor.

member 2FA · self-service + reset

Undo on removals

Delete a member or revoke an invite and a 6-second undo holds the action before it's committed.

removed Sam · Undo (6s)

Resend or copy an invite

Pending invite gone stale? Resend the email or copy the activation link from the row.

invite pending · resend · copy link

Alert schedules & teams

Each member sets quiet hours and days off; group them into teams for on-call routing.

quiet 22:00–07:00 · on-call team

One account, every monitor type

Roles, groups and contacts apply the same way across all 12 monitor types — from uptime and SSL to transaction and heartbeat — one place to manage who can touch what.

checkout · caldmont.comTRANSACTION www.caldmont.comUPTIME api.caldmont.comSSL

What is a team account?

A team account lets several people share one monitoring workspace, each with their own login and a role that decides what they can see and change. Instead of passing round a single password, you invite people by email and assign a role — from full administration down to read-only — with permissions enforced by the server on every request, not merely hidden in the interface.

Giving access

How do roles work?

Owner
invites by email
assigns a role
Editor
2 groups

The role, and any monitor-group scope, is chosen at invite time and enforced from the member's first request.

Removing access

Change or revoke, anytime

Seat removed
+ its API key
fails closed
Audit log
records it

removed · their session and their keys stop working on the next request → written to the audit trail

The difference

Shared login vs. roles

A shared password gives everyone every permission and tells you nothing about who did what. Named seats with roles give each person their own login, their own two-factor, and only the access their job needs.

See the five roles →
What you wantOne shared loginRoles
Give the accountant just billing✗ All or nothing✓ Billing seat
Let a client read, not edit✗ Full access✓ Read-only
Limit an editor to their monitors✗ Sees everything✓ Scoped
Everyone has their own 2FA✗ One shared secret✓ Per person
Know who changed what✗ No way to tell✓ Audit trail

Teams & roles FAQ

01What are teams and roles in Uptimia?+
A team account lets several people share one workspace, each with their own login. Every member carries a role — Owner, Admin, Editor, Read-only or Billing — that decides what they can see and change. Roles are enforced on the server, so what a role can't do, it can't do by any route.
02What are the five roles?+
Owner has full control including billing and deleting the account. Admin manages everything except billing and owner-only actions. Editor manages monitors, alerting and status pages. Read-only can view everything and acknowledge an incident, but change nothing. Billing is a free seat that sees only plans and invoices.
03Is the Billing seat really free?+
Yes. A Billing seat isn't counted toward your plan's member limit. It sees plans, invoices and the payment method — no monitors, no incidents, no alerts — so your accountant gets the receipts without taking a paid seat.
04What does "enforced server-side" mean?+
The interface hides controls a role can't use, but the real check happens on the server for every read and write. A Read-only member who reaches a delete link — or crafts the request by hand — is refused with a 403. One shared permission map drives the menu, the API and the check, so they can't drift apart.
05Can I limit someone to certain monitors?+
Yes. Scope an Editor or Read-only member to specific monitor groups, and everything outside those groups is invisible to them — in lists, on the dashboard, in search and in exports. Monitors they create land in their own scope automatically.
06Does everyone get their own login and two-factor?+
Yes. Each member sets their own password and their own two-factor auth — never a shared secret. If a member is locked out, an owner or admin can reset that member's two-factor.
07What's the default role for a new invite?+
Read-only — the least-privileged seat. You raise a member's role deliberately, rather than granting broad access by accident. You can change any role later with one click from the role badge.
08Do API keys respect roles?+
Yes. A key that carries a member's seat — one an admin creates in the control panel, or the key returned when that member signs in from the app or the token endpoint — runs with their role and monitor-group scope, re-resolved on every request. A demoted seat's key loses access at once, and a removed seat's key is rejected outright. Owner-minted keys keep full owner authority.
09What's in the audit trail?+
The last 20 access changes — invites, role changes, scope changes, removals and invite revokes — each reading back as "who did what". It's visible to the owner and admins.
10How many team members can I add?+
Your plan sets how many paid seats you have, and the seat meter at the top of the Team members page shows how many are left. Billing seats are free on top of that number, and never counted. Removing a member frees their seat immediately, with a 6-second undo in case it was a mistake.
11What's the difference between a team and a role?+
A role is what one person is allowed to do. A team groups members together for alert routing — so an incident can page an on-call group, with the team's own schedule if you set one. A member can hold a role and belong to several teams.
12Which plans include team accounts?+
All of them — team accounts, all five roles, monitor-group scoping, the audit trail and per-member two-factor come with every plan, the free one and the 30-day trial included. What varies by plan is the number of paid seats beside the owner: one on Free and Basic, ten on Professional, a hundred on Enterprise — and fifty during the trial. Billing seats are free everywhere, and no plan bills per seat.

Bring your team in today.

Invite the people who keep your sites up — and give each of them exactly the access they should have.

Invite your team →
30-day free trial No per-user pricing Free billing seats No credit card
Billing seats are free and never count toward your plan’s seats.