|
|
@ -1,7 +1,7 @@ |
|
|
<h1>Projects and Teams</h1> |
|
|
<h1>Projects and Teams</h1> |
|
|
<p>Use Projects to organize checks in your SITE_NAME account. Your account initially |
|
|
<p>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.</p> |
|
|
|
|
|
|
|
|
has a single default project. You can create additional projects and transfer |
|
|
|
|
|
your checks between them as your usage grows.</p> |
|
|
<p><img alt="An overview of projects" src="IMG_URL/projects.png" /></p> |
|
|
<p><img alt="An overview of projects" src="IMG_URL/projects.png" /></p> |
|
|
<p>Checks and integrations are project-scoped: each check and each configured |
|
|
<p>Checks and integrations are project-scoped: each check and each configured |
|
|
integration always belongs to a particular project. Checks can be transferred |
|
|
integration always belongs to a particular project. Checks can be transferred |
|
|
@ -9,12 +9,12 @@ from one project to another, preserving check's ping address:</p> |
|
|
<p><img alt="The transfer dialog" src="IMG_URL/transfer_check.png" /></p> |
|
|
<p><img alt="The transfer dialog" src="IMG_URL/transfer_check.png" /></p> |
|
|
<h2>Team Access</h2> |
|
|
<h2>Team Access</h2> |
|
|
<p>You can grant your colleagues access to a project by inviting them into |
|
|
<p>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 |
|
|
|
|
|
|
|
|
the project's team. Each project has its separate team so you can grant access |
|
|
selectively. Inviting team members is <strong>more convenient and more |
|
|
selectively. Inviting team members is <strong>more convenient and more |
|
|
secure</strong> than sharing a password to a single account.</p> |
|
|
secure</strong> than sharing a password to a single account.</p> |
|
|
<p><img alt="Team access section" src="IMG_URL/team_access.png" /></p> |
|
|
<p><img alt="Team access section" src="IMG_URL/team_access.png" /></p> |
|
|
<p>The user who originally created the project is listed as <strong>owner</strong>. Any invited users |
|
|
|
|
|
are listed as <strong>members</strong>. The members can:</p> |
|
|
|
|
|
|
|
|
<p>The user who created the project is the <strong>owner</strong>. Any invited users |
|
|
|
|
|
are <strong>members</strong>. The members can:</p> |
|
|
<ul> |
|
|
<ul> |
|
|
<li>create, edit and remove checks</li> |
|
|
<li>create, edit and remove checks</li> |
|
|
<li>create and remove integrations</li> |
|
|
<li>create and remove integrations</li> |
|
|
@ -30,7 +30,7 @@ are listed as <strong>members</strong>. The members can:</p> |
|
|
<li>remove the project</li> |
|
|
<li>remove the project</li> |
|
|
</ul> |
|
|
</ul> |
|
|
<h2>Read-only Access</h2> |
|
|
<h2>Read-only Access</h2> |
|
|
<p>When inviting a team member, their membership can be marked as read-only:</p> |
|
|
|
|
|
|
|
|
<p>When inviting a team member, you can mark their membership as read-only:</p> |
|
|
<p><img alt="The Access Level parameter in the Invite form" src="IMG_URL/invite_member.png" /></p> |
|
|
<p><img alt="The Access Level parameter in the Invite form" src="IMG_URL/invite_member.png" /></p> |
|
|
<p>Read-only members can:</p> |
|
|
<p>Read-only members can:</p> |
|
|
<ul> |
|
|
<ul> |
|
|
@ -38,25 +38,26 @@ are listed as <strong>members</strong>. The members can:</p> |
|
|
<li>view integrations</li> |
|
|
<li>view integrations</li> |
|
|
<li>give up their membership</li> |
|
|
<li>give up their membership</li> |
|
|
</ul> |
|
|
</ul> |
|
|
<p>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 |
|
|
|
|
|
|
|
|
<p>Read-only members can not modify checks, integrations, or project settings. |
|
|
|
|
|
They also cannot access the project's API keys as that would effectively give them |
|
|
read-write access through API.</p> |
|
|
read-write access through API.</p> |
|
|
<h2>Projects and Check Limits</h2> |
|
|
<h2>Projects and Check Limits</h2> |
|
|
<p><strong>Check limit</strong> is the total number of checks your account can have. The specific |
|
|
|
|
|
limit depends on the account's billing plan.</p> |
|
|
|
|
|
<p>Account's check limit is shared by all projects owned by your account. |
|
|
|
|
|
|
|
|
<p><strong>Check Limit</strong> is the total number of checks your account can have. The specific |
|
|
|
|
|
limit depends on the account's billing plan. When you reach the Check Limit |
|
|
|
|
|
you will not be able to create new checks.</p> |
|
|
|
|
|
<p>All projects owned by your account shares your account's Check Limit. |
|
|
For example, consider a Business account with two projects, |
|
|
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 |
|
|
"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.</p> |
|
|
30 checks, in order to not exceed the Business account's total limit of 100.</p> |
|
|
<p>However, only checks from your own projects count towards your account's |
|
|
<p>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 |
|
|
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.</p> |
|
|
|
|
|
|
|
|
the number of checks you can create in your projects.</p> |
|
|
<h2>Projects and Team Size Limits</h2> |
|
|
<h2>Projects and Team Size Limits</h2> |
|
|
<p><strong>Team size</strong> 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".</p> |
|
|
|
|
|
|
|
|
<p><strong>Team Size</strong> is the number of <em>unique</em> users you can invite in your projects. |
|
|
|
|
|
Same as with Check Limit, all projects share your account's Team Size limit. |
|
|
|
|
|
However, if you invite the same user (using the same email address) into multiple |
|
|
|
|
|
projects, it only takes up a single seat.</p> |
|
|
<h2>Projects and Monthly Reports</h2> |
|
|
<h2>Projects and Monthly Reports</h2> |
|
|
<p>SITE_NAME sends monthly email reports at the |
|
|
|
|
|
start of each month. The monthly reports list a summary of checks from |
|
|
|
|
|
<strong>all projects you have access to</strong> (either as the owner or as a member).</p> |
|
|
|
|
|
|
|
|
<p>SITE_NAME sends monthly email reports at the start of each month. The monthly reports |
|
|
|
|
|
list a summary of checks from <strong>all your projects</strong>. It contains status summaries for |
|
|
|
|
|
both the projects you own, and the projects you are a member of.</p> |
Pēteris Caune
4 years ago