231 | | Access to and configuration of resources is affected by the project(s) a user is acting as a member of. When a user requests resources, thay specify the projects under which they are requesting them. A user requesting resources as a member of a project representing a university class may have access to different resources than one acting as a member of the testbed administration. How membership affects the resources a group can claim is set by testbed [wiki:NewAdmin policy]. |
232 | | |
233 | | In addition, the membership in projects controls how resources will be configured. A resource in use by a particular project will generally be configured to be accessible to all members of that project. A student who allocates resources as a member of a small design group while implementing a class project may later allocate resources as a member of the whole class when presenting the work to the class's TA and professor. |
| 231 | Access to and configuration of resources is affected by the circle(s) a user is acting as a member of. When a user requests resources, thay specify the circle under which they are requesting them. A user requesting resources as a member of a circle representing a university class may have access to different resources than one acting as a member of the testbed administration. How membership affects the resources a group can claim is set by testbed policy. |
| 232 | |
| 233 | In addition, the membership in circles controls how resources will be configured. A resource in use by a particular circle will generally be configured to be accessible to all members of that circle. A student who allocates resources as a member of a small design group while implementing a class project may later allocate resources as a member of the whole class when presenting the work to the class's TA and professor. |