Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Role

Examples

Create accounts

Delete accounts

Run partner tools (TeraGrid)

Run local tools

Access Community Data

Add/Delete Community Data

Add/Delete Groups

Use Collaboration Tools (chat)

Add/Delete User data

Allocate Resources

Request Resources

Create CO Organization spaces

Constrained user

psuedo-anonymous, temporary, guest, possibly student, conference/tutorial specific accounts

(error)

(error)

(error)

(tick)

(tick)

(error)

(error)

(error)

(tick)

(error)

(error)

(error)

iPlant user

identifiable user

(error)

(error)

(tick)

(tick)

(tick)

(error)

(tick)

(tick)

(tick)

(error)

(tick)

(error)

Steward

community data steward, local tool owner

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(error)

(tick)

(error)

Administrator

Faculty, TA, Admin Asst.

(tick)

(tick)

(tick)

(tick)

(tick)

(error)

(tick)

(tick)

(tick)

(warning)

(tick)

(error)

Developer

tool developers/tool users (in Atmosphere), image creators

(error)

(error)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(error)

(tick)

(error)

Organization

creating a CO, allocating resources to the CO

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)

(tick)


Legend

 

(error)

not allowed

(tick)

allowed

!)

allowed but with limited scope


  • Constrained User - psuedo-anonymous, temporary, guest, possibly student, conference/tutorial specific accounts (there may be user registration specifically for that tutorial; this may be a special set up depending on the situation; these may be pre-created not individual registration; these may be very restricted in capability/access; if there are a large number of temporary accounts like this, will that trigger audit issues with granting agencies?); some sort of persistent, recurring access while not tracking personal information
    • they can run many (but not all, not TeraGrid, for example) of iPlant managed resources, they can view and subscribe all the community data in the system, they can add data temporarily, they can sign themselves up for mailing lists; they cannot create groups, they cannot invite other users, nothing that falls under collaboration (collaboration and communication requires more identification)
    • not an iPlant user, as they can be restricted by the faculty more than what a general iPlant user will be; if the individual behind the student account wants more access, they may request a full iPlant user account that will be a wholly separate account than their student account

...