36 | | We describe each of these in more detail below. They are interrelated and the descriptions link to one another in this document. We intend for readers to jump between sections to help intuition. |
| 36 | |
| 37 | Projects and circles are related in that they control access to testbed resources. |
| 38 | |
| 39 | Membership in an approved project means a user can access testbed |
| 40 | resources in general. They've been trusted directly or by transitivity |
| 41 | by the testbed administration to have "an account" to which usage can be |
| 42 | charged and responsibility delegated. Projects must be approved by |
| 43 | administrators to confer rights. |
| 44 | |
| 45 | Membership in a circle allows users to specify fine grained access |
| 46 | between one another. None of the circle memberships are effective |
| 47 | unless the user is also in an approved project. Circles do not need to |
| 48 | be vetted by admins because their powers are gated by projects. |
| 49 | |
| 50 | Being in a project means a user can use DETERLab. Being in the circle of |
| 51 | users that can read an experiment means a user can use that particular |
| 52 | experiment in that particular way (assuming that the user is in an approved |
| 53 | project). |
| 54 | |
| 55 | We describe each of these abstractions in more detail below. They are interrelated and the descriptions link to one another in this document. We intend for readers to jump between sections to help intuition. |