Changes between Version 13 and Version 14 of Internal/Rbac/OrbitRbacDesign/ResourcesRoles


Ignore:
Timestamp:
Oct 5, 2006, 8:58:28 PM (19 years ago)
Author:
anonymous
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • Internal/Rbac/OrbitRbacDesign/ResourcesRoles

    v13 v14  
    2929
    3030ORBIT Roles
    31  * ORBIT Administrator:  browse, add, modify and delete ORBIT users; browse, add, modify and delete ORBIT projects;  browse, add, modify and delete Project Leaders and Project Administrators; set logging options and audit ORBIT logs; can delegate to Designated ORBIT Administrator; cardinality = 1.
    32  * Designated ORBIT Administrator:  same privileges as ORBIT Administrator except cannot delegate role; cardinality = 1.
    33  * Experimenter:  all privileges to run an ORBIT experiment and analyze results, but not modify or delete results.
    34  * Analyst:  can only analyze results of an ORBIT experiment, not run one.
    35  * Project Administrator:  browse selected fields of and add ORBIT users;  add and delete users to and from roles in his or her project;  can delegate role to Designated Project Administrator; cardinality = 1 per project.
    36  * Designated Project Administrator:  same privileges as Project Administrator except cannot delegate; cardinality = 1 per project.
    37  * Project Leader:  can modify or delete results of any of the project's experiments; complete access to any project-specific resources;  can delegate to Designated Project Leader; cardinality = 1 per project.
    38  * Designated Project Leader:  same privileges as Project Leader except cannot delegate;  cardinality = 1 per project.
    39  * Developer:  not sure what the scope of a developer's privileges should be.  Does a developer become and Experimenter to run a test?
     31 1. ORBIT Administrator:  browse, add, modify and delete ORBIT users; browse, add, modify and delete ORBIT projects;  browse, add, modify and delete Project Leaders and Project Administrators; set logging options and audit ORBIT logs; can delegate to Designated ORBIT Administrator; cardinality = 1.
     32 1. Designated ORBIT Administrator:  same privileges as ORBIT Administrator except cannot delegate role; cardinality = 1.
     33 1. Experimenter:  all privileges to run an ORBIT experiment and analyze results, but not modify or delete results.
     34 1. Analyst:  can only analyze results of an ORBIT experiment, not run one.
     35 1. Project Administrator:  browse selected fields of and add ORBIT users;  add and delete users to and from roles in his or her project;  can delegate role to Designated Project Administrator; cardinality = 1 per project.
     36 1. Designated Project Administrator:  same privileges as Project Administrator except cannot delegate; cardinality = 1 per project.
     37 1. Project Leader:  can modify or delete results of any of the project's experiments; complete access to any project-specific resources;  can delegate to Designated Project Leader; cardinality = 1 per project.
     38 1. Designated Project Leader:  same privileges as Project Leader except cannot delegate;  cardinality = 1 per project.
     39 1. Developer:  not sure what the scope of a developer's privileges should be.  Does a developer become and Experimenter to run a test?
    4040
    41 If there are different types of ORBIT experiments, may want more than one Experimenter role.
     41If there are different types of ORBIT experiments, we may want more than one Experimenter role.
    4242
    4343Might consider a separate ORBIT database administrator role too to backup and restore stuff and clean out and maybe archive stuff.