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.

62 lines
3.4 KiB

  1. <h1>Projects and Teams</h1>
  2. <p>Use Projects to organize checks in your SITE_NAME account. Your account initially
  3. has a single default project. You can create additional projects and transfer
  4. your checks between them as your usage grows.</p>
  5. <p><img alt="An overview of projects" src="IMG_URL/projects.png" /></p>
  6. <p>Checks and integrations are project-scoped: each check and each configured
  7. integration always belongs to a particular project. Checks can be transferred
  8. from one project to another, preserving check's ping address:</p>
  9. <p><img alt="The transfer dialog" src="IMG_URL/transfer_check.png" /></p>
  10. <h2>Team Access</h2>
  11. <p>You can grant your colleagues access to a project by inviting them into
  12. the project's team. Each project has its separate team so you can grant access
  13. selectively. Inviting team members is <strong>more convenient and more
  14. secure</strong> than sharing a password to a single account.</p>
  15. <p><img alt="Team access section" src="IMG_URL/team_access.png" /></p>
  16. <p>The user who created the project is the <strong>owner</strong>. Any invited users
  17. are <strong>members</strong>. The members can:</p>
  18. <ul>
  19. <li>create, edit and remove checks</li>
  20. <li>create and remove integrations</li>
  21. <li>rename the project</li>
  22. <li>view and regenerate project's API keys</li>
  23. <li>give up their membership
  24. (from their <a href="../../accounts/profile">Account Settings</a> page)</li>
  25. </ul>
  26. <p>The members <strong>can not</strong>:</p>
  27. <ul>
  28. <li>invite new members into the project</li>
  29. <li>manage project's billing</li>
  30. <li>remove the project</li>
  31. </ul>
  32. <h2>Read-only Access</h2>
  33. <p>When inviting a team member, you can mark their membership as read-only:</p>
  34. <p><img alt="The Access Level parameter in the Invite form" src="IMG_URL/invite_member.png" /></p>
  35. <p>Read-only members can:</p>
  36. <ul>
  37. <li>view checks, including check details and ping logs</li>
  38. <li>view integrations</li>
  39. <li>give up their membership</li>
  40. </ul>
  41. <p>Read-only members can not modify checks, integrations, or project settings.
  42. They also cannot access the project's API keys as that would effectively give them
  43. read-write access through API.</p>
  44. <h2>Projects and Check Limits</h2>
  45. <p><strong>Check Limit</strong> is the total number of checks your account can have. The specific
  46. limit depends on the account's billing plan. When you reach the Check Limit
  47. you will not be able to create new checks.</p>
  48. <p>All projects owned by your account shares your account's Check Limit.
  49. For example, consider a Business account with two projects,
  50. "Project A" and "Project B". If A has 70 checks, then B cannot have more than
  51. 30 checks, in order to not exceed the Business account's total limit of 100.</p>
  52. <p>However, only checks from your own projects count towards your account's
  53. quota. If you get invited to somebody else's project, that does not change
  54. the number of checks you can create in your projects.</p>
  55. <h2>Projects and Team Size Limits</h2>
  56. <p><strong>Team Size</strong> is the number of <em>unique</em> users you can invite in your projects.
  57. Same as with Check Limit, all projects share your account's Team Size limit.
  58. However, if you invite the same user (using the same email address) into multiple
  59. projects, it only takes up a single seat.</p>
  60. <h2>Projects and Monthly Reports</h2>
  61. <p>SITE_NAME sends monthly email reports at the start of each month. The monthly reports
  62. list a summary of checks from <strong>all your projects</strong>. It contains status summaries for
  63. both the projects you own, and the projects you are a member of.</p>