Projects organize the inventory
A project has a name and a color. Uptime monitors, heartbeats, server monitors, DNS monitors, domains and status pages can be assigned to a project, and the lists can be filtered by it. A project is a way of organizing: permissions belong to the team, not to the project.
Invite colleagues by email
You create a team and invite people by their email address. Whoever accepts switches into your account via “Login” and sees there as whom and in which team they are currently working. They return with “Exit”.
Permissions per area
A member may view everything in the team’s account. You grant create, update and delete separately per area: uptime monitoring, heartbeats, server monitors, DNS monitoring, domains and SSL, status pages, notification channels, incidents, maintenance windows, projects. Members without update permission only see a monitor’s credentials, such as an Authorization header, as asterisks in the export.
Trace who changed what
Every creation, change and deletion of monitors, heartbeats, status pages, channels, projects, maintenance windows, teams and members is recorded in the change log, with time, person, object and source: portal, API, CSV import, link from an email, administrator or system. For changes, the old and new values are shown, plus account events such as a regenerated API key. Passwords, tokens and other secret values appear only with the field name.
Filter and export the log
The log can be filtered by period, object type, action and person, and exported as CSV. How long entries are kept depends on the plan’s data retention. The account owner can view it, team members cannot.
Login with a second factor
Every account can secure its login with an authenticator app and a six-digit code. On a team, this can be made mandatory for all members.