New: temperature, fans, power supplies and SSD health per server. View hardware health

Try it free
Projects in the PeakNode portal: three projects (IT operations, inference, AI training) to which eight uptime monitors, seven servers, four heartbeats and six domains and DNS monitors are assigned.

As soon as several people look at the monitoring, three questions come up: how do I keep customers or departments apart, who is allowed to change things, and who switched off the alert yesterday? PeakNode answers them with projects, with teams and graded permissions, and with a change log.

Screenshot from the portal with sample data (German interface).

What is Teams and projects?

In PeakNode, teams and projects organize your inventory and access. Projects group monitors, heartbeats, server monitors and status pages, for example by department, location or customer. With a team you invite people to your account by email and decide per area whether they may only view, or also create, update and delete. The change log records who created, changed or deleted what, and when.

Organize, control access, trace changes

Three building blocks that belong together. Where each one ends is shown in the table below.

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.

Permissions in a team

How permissions can be distributed

MemberViewCreate and updateDelete
Operations engineerEverythingUptime monitoring, heartbeats, server monitors, maintenance windows, incidentsIncidents
Colleague from the network teamEverythingDNS monitoring, domains and SSL, notification channelsno permissions
Contact person at the customerEverythingno permissionsno permissions

Example. “View” always applies to everything in the team’s account. You grant create, update and delete separately per area.

What each building block does and where it ends

The limits are listed here so that you can choose the model that fits the separation you need.

Building blockPurposeLimit
ProjectGroup monitors, heartbeats, server monitors and status pages by customer, department or location, filter listsNo access boundary: a team member sees all projects of the account
TeamInvite people to your own account, grant permissions per areaView always applies to everything. Account settings, payments and logs stay with the owner
Change logTrace who created, changed or deleted what and when, including via the APIVisible to the owner only. Check results and alerts are not recorded there but under incidents. Comments, acknowledgements and deletions of incidents are not logged
Two-factor loginSecure the portal login with a second factor, mandatory per teamApplies to the portal login, not to API keys
Separate account per customerStrict separation: data and plan belong to the customer, the IT service provider switches in as a team memberEach account has its own plan

The number of projects and team members is set by the plan. Changes made via the API are logged with the owner of the API key.

Set up in three steps

Projects can be introduced at any time later on; you assign existing monitors when editing them.

  1. Create projects

    Under “Projects”, create one project per customer, department or location with a name and color, and assign the monitors.

  2. Create a team and invite

    Under “My teams”, create a team, switch on “Require two-factor authentication for all members” if needed and invite members by email. Tick the create, update and delete permissions for each member.

  3. Trace changes

    In the account under “Change log”, filter by period, type, action or person. Export as CSV for analysis outside the portal.

How do I give colleagues access to my monitoring?

Create a team in PeakNode and invite your colleagues by email. Whoever accepts the invitation switches into your team with their own account and works there with the permissions you granted. No shared password is needed.

Can a team member have read-only access?

Yes. Every member has the “View” permission; you grant all other permissions individually. A member without create, update and delete sees monitors, readings and incidents but cannot change anything.

Can I restrict access to individual projects or customers?

No. Permissions apply per area, not per project, and a team member may view everything in the account. If customers should get portal access without seeing each other, run a separate account for each customer and have yourself invited there as a team member. For a plain view of the current state, a password-protected status page is often enough.

How do I see who changed or deleted a monitor?

In the account’s change log. Every creation, change and deletion of a monitor is listed there with time, person and the source it came from. The account owner can see the log.

Can I enforce two-factor authentication for my team?

Yes, with the team setting “Require two-factor authentication for all members”. Members without a second factor can only enter the team once they have set it up in their own account. The requirement applies to the portal login; API keys keep working unchanged.

How many teams and members are possible?

That is set by the plan. The free Proof of Concept plan includes no team, Premium 1 team, Enterprise unlimited teams. The on-premises edition has no limit on users. The current figures are on the pricing page.

How does an IT service provider handle several customers?

In one of two ways. Either you create all customers in your own account, one project per customer, and each customer gets a status page. Or each customer runs their own account, invites you as a team member and remains the owner of their data. The page For IT service providers compares both models.

Share your monitoring with your team

Create an account and organize your inventory into projects by customer or department. Teams are included in the Premium and Enterprise plans.