nielsperetzke
/
healthchecks
1
0
Fork 0
Code Issues 0 Pull Requests 0 Projects 0 Releases 32 Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1486 Commits
2 Branches
15 MiB
 
 
 
 
 
Tree: bd98174d4c
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from 'bd98174d4c'
${ noResults }
healthchecks/templates/docs/projects_teams.md

2.9 KiB
Raw Blame History

Projects and Teams

Use Projects to organize checks in your SITE_NAME account. Your account initially has a single default project. You can create additional projects and organize your checks in them as your usage grows.

An overview of projects

Checks and integrations are project-scoped: each check and each configured integration always belongs to a particular project. Checks can be transferred from one project to another, preserving check's ping address:

The transfer dialog

Team Access

You can grant your colleagues access to a project by inviting them into the project's team. Each project has its own separate team so you can grant access selectively. Inviting team members is more convenient and more secure than sharing a password to a single account.

Team access section

The user who originally created the project is listed as owner. Any invited users are listed as members. The members can:

  • create, edit and remove checks
  • create and remove integrations
  • rename the project
  • view and regenerate project's API keys
  • give up their membership (from their Account Settings page)

The members can not:

  • invite new members into the project
  • manage project's billing
  • remove the project

Read-only Access

When inviting a team member, their membership can be marked as read-only:

The Access Level parameter in the Invite form

Read-only members can:

  • view checks, including check details and ping logs
  • view integrations
  • give up their membership

Read-only members can not modify checks, integrations or project settings. They also cannot access project's API keys as that would effectively give them read-write access through API.

Projects and Check Limits

Check limit is the total number of checks your account can have. The specific limit depends on the account's billing plan.

Account's check limit is shared by all projects owned by your account. For example, consider a Business account with two projects, "Project A" and "Project B". If A has 70 checks, then B cannot have more than 30 checks, in order to not exceed the Business account's total limit of 100.

However, only checks from your own projects count towards your account's quota. If you get invited to somebody else's project, that does not change the number of checks you can create in your own projects.

Projects and Team Size Limits

Team size is the number of unique users you can invite in your projects. The team size limit is also shared by all projects owned by your account. However, if you invite the same user (using the same email address) into several projects, it only takes up a single "seat".

Projects and Monthly Reports

SITE_NAME sends monthly email reports at the start of each month. The monthly reports list a summary of checks from all projects you have access to (either as the owner or as a member).