How to Set Up Team-Based Uptime Monitoring

Solo uptime monitoring works great when it is just you. You set up a handful of monitors, configure your alert channels, and keep an eye on things from your own dashboard. But the moment your team grows -- a second engineer joins on-call, a product manager wants visibility into status pages, an ops lead needs to manage alert channels -- the single-user model starts to break down. Who owns what? Who gets notified? Who can change the configuration without breaking someone else's setup?

CronAlert solves this with team-based monitoring. Multiple people share the same monitors, alert channels, status pages, and API keys under one team, with role-based access and audit logging to keep things organized. Here is how it works and how to set it up.

How teams work in CronAlert

Every CronAlert account starts with a personal team. This is created automatically when you sign up, and it is where your monitors live by default. You do not need to do anything special to use it -- if you are a solo user, your personal team is all you need.

When you are ready to collaborate, you create a shared team. A shared team is a separate workspace with its own set of resources. Monitors, alert channels, status pages, and API keys all belong to the team, not to any individual user. Everyone on the team sees the same data and can manage the same resources.

This is a deliberate design choice. In CronAlert, resources are scoped to teams, never to individual users. There is no concept of "my monitors" versus "your monitors" within a team. If a monitor is on the team, everyone on the team can see it. This eliminates the common problem of critical monitors being invisible to half the team because they were set up under someone else's personal account.

Roles and permissions

Each team member is assigned one of three roles. The role determines what they can do within the team:

• Owner. Full control over the team. Can invite and remove members, change roles, manage all resources, and delete the team entirely. Every team has exactly one owner -- the person who created it.
• Admin. Can manage team resources (monitors, alert channels, status pages) and invite new members. Admins cannot delete the team or change the owner.
• Member. Can view and manage team resources -- create monitors, configure alerts, update status pages. Members cannot invite other users or change team settings.

In practice, most teams have one owner (the team lead or account holder), one or two admins (senior engineers who need to manage the roster), and everyone else as members. The permissions are intentionally simple. There is no complex matrix of granular permissions to configure -- just three roles that cover the common cases.

Setting up a team

Creating a team and inviting your first members takes under a minute.

Go to your team settings and click Create Team. Give it a name -- your company name, project name, or whatever makes sense for how your group is organized. You are automatically assigned as the owner.

From the team settings page, enter the email addresses of the people you want to invite. Each person receives an email with an invitation link. They do not need an existing CronAlert account -- if they do not have one, they will be prompted to create one when they accept the invite.

Each invitee clicks the link in their email, signs in (or registers), and is added to the team. They can immediately see all the team's monitors, alert channels, and status pages.

By default, new members join with the member role. The owner can promote anyone to admin from the team settings page. Adjust roles based on who needs to manage the team roster versus who just needs access to the monitoring resources.

Team-scoped resources

Once your team is set up, every resource you create belongs to that team. This includes:

• Monitors. All URL checks, their configuration, and their check history are scoped to the team. Any team member can create, edit, pause, or delete monitors.
• Alert channels. Email, Slack, Discord, webhook, and other notification channels are shared across the team. Set up a Slack channel once and every monitor on the team can use it.
• Status pages. Public status pages belong to the team. Multiple team members can manage incidents and post updates without needing to share login credentials.
• API keys. Programmatic access tokens are team-scoped. This means your CI/CD pipeline can use a team API key that does not break when the person who created it leaves the company.

To switch between teams, use the team dropdown in the app navigation. When you switch teams, the dashboard, monitors list, and all other views update to show that team's resources. Your personal team is always available as a fallback -- it is where your resources live if you are not working within a shared team.

Plan limits

Team collaboration is available on higher-tier plans. Here is how the member limits break down:

Free and Pro plans are designed for individual use. You still have a personal team, and all your resources are scoped to it, but you cannot invite additional members. If you need collaboration, the Team plan is the starting point.

Audit logging on Business

On the Business plan, CronAlert tracks every significant action taken within a team. This includes monitor creation and deletion, alert channel changes, team membership changes, status page updates, and more. Each audit log entry records who performed the action, what they did, and when it happened.

Audit logs are scoped to the active team, so switching teams shows you a different set of events. This is particularly useful for organizations that need compliance visibility or simply want to answer the question "who changed the alert threshold on the production API monitor at 3am?"

For most teams, audit logging is a nice-to-have. For teams operating in regulated industries or managing infrastructure for clients, it is a requirement. CronAlert's audit logs give you a complete trail without requiring a third-party logging integration.

Frequently asked questions

Can I be on multiple teams?

Yes. Every account can belong to multiple teams at the same time. You might have your personal team for side projects, a shared team for your day job, and another shared team for a client project. Switch between them using the team dropdown in the app -- each team has its own independent set of monitors, alert channels, and status pages.

What happens if the team owner leaves or is unavailable?

Only the team owner can delete a team or transfer ownership. If the owner needs to step away, they should transfer ownership to another team member first. If a team is deleted by the owner, all resources are moved to the owner's personal team -- monitors continue running and no data is lost. Plan ahead by ensuring at least one admin knows the team structure.

Are resources shared across the whole team?

Yes, completely. All monitors, alert channels, status pages, and API keys belong to the team, not to the person who created them. There are no per-user silos. If you create a monitor while on a shared team, every member of that team can see and manage it. This is by design -- it prevents the common problem of institutional knowledge being locked in one person's account.

Getting started

If you are on a Team or Business plan, you can create a shared team right now from your team settings. Invite your colleagues, assign roles, and start consolidating your monitoring under one shared workspace.

If you are on the Free or Pro plan and want team collaboration, upgrade to the Team plan to unlock up to 10 members, 500 monitors, and all the collaboration features described here.

Uptime monitoring is only as good as the people who act on the alerts. Giving your whole team visibility into the same monitors, the same incidents, and the same status pages means faster response times, fewer miscommunications, and no more "I did not know that monitor existed" moments during an outage.