Teams

A team is one account used by several people. Everyone sees and manages the same domains, and every alert reaches everyone — so a warning never depends on one inbox, or on one person who is on holiday or has left.

Teams are part of Pro. The person who sets up the team is the owner: everyone works in their account, with their domains and their subscription. Everyone else joins with a role: admin, member or viewer.

Inviting someone

1. Go to Settings → Team.
2. Enter your colleague's e-mail address, choose a Role and click Send invitation.
3. They get an e-mail with a link. It works once and is valid for seven days.

A team has up to ten people, open invitations included. Under Members you see everyone and every open invitation.

• Withdraw cancels an invitation.
• Remove takes someone off the team at once.
• Invitation expired? Invite the same address again — the new link replaces the old one.

Accepting an invitation

Sign in with the invited address, open the link and click Accept invitation. The link does nothing for anyone signed in with another address, so a forwarded invitation is useless.

No account yet? Register with the invited address — with a password or with Google, GitHub or Microsoft — confirm it, and open the link again. The new account is on Free by itself; in the team it uses the owner's Pro plan.

The invitation cannot be accepted when:

Situation	What to do
Your account monitors domains of its own	Export them as CSV if you want to keep the list, delete them, then accept. The owner can import the file into the team.
You are already on a team, or have a team with members	An account can be on one team only. Leave the other team, or remove your members, first.
The link has expired, was withdrawn or was already used, or the owner is no longer on Pro	Ask for a new invitation.

Roles

	Viewer	Member	Admin	Owner
See domains, details, history and Activity; get the alerts	✅	✅	✅	✅
Add, edit, check, snooze and delete domains; import CSV	–	✅	✅	✅
Create and revoke client reports	–	✅	✅	✅
Invite and remove members and viewers, change their role	–	–	✅	✅
Make someone admin, remove an admin	–	–	–	✅
Webhooks, plan and billing	–	–	–	✅

• Viewer suits a manager or a customer's IT team: they see everything and get every alert, but cannot change anything — not in the browser and not with the API.
• Member is the default. New domains count towards the team's limit.
• Admin takes invitations off the owner's plate. Only the owner can make or remove admins, so an admin can never lock the owner, or another admin, out.

To change a role, pick it next to the person under Members and click Save.

Everyone uses the API with their own token, which works on the team's domains with the rights of their role.

What is shared and what is personal

	Owner	Everyone else
Domains, tags, labels, client reports	owns them; the team works on them	works on the owner's, as their role allows
Plan and billing	✅	–
Login, password, two-factor authentication, connected sign-ins	own	own
E-mail alerts on or off, which alerts to receive	own	own
Webhooks for the team's alerts	✅	–
Language and theme	own	own

Alerts in a team

• Every alert goes to everyone, at their own address, in their own language, with their own settings under Settings → Notifications. A colleague can switch off "certificate renewed or changed" while the owner still gets it.
• Webhooks are the owner's. Team alerts go to the webhooks the owner sets up — a shared Slack channel, say. Members get them by e-mail; their own webhooks receive nothing from the team, so nothing keeps arriving in a personal channel after someone leaves.
• No extra repeats. The one-alert-a-day rule applies per domain, for the whole team: everyone gets the alert at the same time, then nobody gets it again within the waiting period.
• A snooze is for everyone. It belongs to the domain, not to a person. To stop hearing about something yourself, switch it off in your own settings instead.
• The summary e-mail covers the team's domains. Each member chooses daily, weekly or none under Settings → Notifications.

Activity log

Settings → Activity shows who changed what, newest first: domains added, edited, deleted or snoozed, CSV imports, invitations and role changes, client reports and webhooks. Changes made through the API are marked API. Each domain's page shows its own entries at the bottom.

Everyone on the team sees the log, viewers included. Entries are kept for a year. If someone deletes their CertWatchr account, their entries stay but no longer show their name.

Leaving or being removed

A member can click Leave team under Settings → Team at any time; the owner can remove them there too. Either way:

• The domains stay with the team. The person is back in their own account, without domains and on their own plan — usually Free.
• Their login, password, two-factor authentication and settings stay as they are.
• From that moment they get no team alerts, and their API token no longer works on the team's domains.

While a team is paused, members cannot add domains: those would land in their own account and disappear from view once the team resumes. To use your own account instead, leave the team.

When something changes for the owner

Change	Effect on the team
The owner changes plan	The new plan applies to the whole team at once, with its limits and features.
The owner leaves Pro	The team is paused. Members are back on their own accounts, cannot see the team's domains and get no team alerts. Invitations stop working. The owner still sees the members and can remove them. Membership is kept: when the account is on Pro again, the team carries on as before.
The owner deletes their account	Every member is released automatically and keeps their own login, as if they had left. The owner's domains are deleted with the account.