Team workspaces

Certificate coverage breaks when only one person knows the renewal path.

Shared workspaces keep hostnames, warnings, checks, and access visible when teammates are away, clients move, or responsibilities change.

View pricingGetting started docs

Workspace control

Ownership stays visible

4 members

Teams keep monitors, roles, labels, and renewal context together when responsibility shifts.

OwnerCertificate Desk
Pending2 invites
AuditRoute changed 2h ago
Owner, admin, member, pending invite
Shared ownership

Roles and invites keep certificate work out of one inbox.

Team access shows who can operate, who can review, and which invites are still pending before responsibility changes.

01

Role-based workspace access

Owner, admin, and member roles separate sensitive account actions from daily certificate review.

  • Owners control billing-sensitive and workspace-level decisions.
  • Admins maintain monitors, channels, and alert settings.
  • Members can review certificate health without owning every setting.
Role boundaries for certificate work
RoleCan doUse when
OwnerManage billing-sensitive settings, workspace ownership, invites, and role changes.A founder, agency lead, or platform owner controls the account.
AdminCreate and edit monitors, imports, alert channels, and alert settings.Operators own day-to-day certificate coverage.
MemberReview monitors, certificate snapshots, events, and delivery history.Teammates need visibility without changing routes or access.
02

When renewal ownership changes

Workspace owners can invite teammates, manage pending invites, and update roles before coverage depends on one person. When a renewal owner leaves, a client moves teams, or a Slack webhook rotates, the monitor, route, and history stay visible to the workspace.

  • Review who owns app, API, checkout, identity, and client monitors.
  • Update alert channels when personal inboxes or old webhooks are removed.
  • Use audit logs to see which access or route changed before a missed warning.
03

Shared accountability for renewals

Team workspaces make expiry warnings, certificate changes, alert destinations, delivery attempts, and audit history visible to the people responsible for follow-up.

  • Keep status visible when the original monitor creator is away.
  • Make renewal handoffs easier when domains move between teams or clients.
  • Review warning history without searching personal inboxes.
FAQ1 answer

  1. Why use a team workspace for certificate monitoring?

    A team workspace keeps monitors, alert channels, delivery attempts, and roles visible to more than one person, which reduces renewal risk when responsibility changes.

Related3 pagesAlert routingSend warnings to shared channels instead of personal inboxes.Explore Alert routing
FeatureAudit logsInspect who changed monitors, channels, or access.Use caseDevOps and SRESee how operational teams use failure classes and webhooks.
Share the coverage

Choose the plan that matches your team size and monitored hostname count.

Starter supports small teams; Team gives more monitored hostnames and members for shared responsibility.

View pricingRead getting started