EMMAWiki/TermsAndConcepts/ForUsers/Access Control: Difference between revisions
Jump to navigation
Jump to search
imported>VirginieMittard No edit summary |
imported>VirginieMittard No edit summary |
||
| Line 4: | Line 4: | ||
* Access control in EMMA 2.0 is provided for each individual object. Here you can check other member's rights on this object. If you have the appropriate permissions you can also change these permissions. Be carefull to not lockout yourself from this object by setting permissions to 'No'. | * Access control in EMMA 2.0 is provided for each individual object. Here you can check other member's rights on this object. If you have the appropriate permissions you can also change these permissions. Be carefull to not lockout yourself from this object by setting permissions to 'No'. | ||
* For each project, there is a "chief" who has all the privileges and can give access or not to other users for this project. He also decides what kind of tasks you can perform or not on this project, e.g. to change an existing pipeline or to create a new one, to import data from ArrayLIMS, etc...Here are the different types of members you can have on a project and their corresponding privileges. | * For each project, there is a "chief" who has all the privileges and can give access or not to other users for this project. He also decides what kind of tasks you can perform or not on this project, e.g. to change an existing pipeline or to create a new one, to import data from ArrayLIMS, etc...Here are the different types of members you can have on a project and their corresponding privileges. | ||
* Chief | ** Chief | ||
* Maintainer | ** Maintainer | ||
* User | ** User | ||
* Guest | ** Guest | ||
Revision as of 10:44, 24 August 2005
Access Control
- Access control in EMMA 2.0 is provided for each individual object. Here you can check other member's rights on this object. If you have the appropriate permissions you can also change these permissions. Be carefull to not lockout yourself from this object by setting permissions to 'No'.
- For each project, there is a "chief" who has all the privileges and can give access or not to other users for this project. He also decides what kind of tasks you can perform or not on this project, e.g. to change an existing pipeline or to create a new one, to import data from ArrayLIMS, etc...Here are the different types of members you can have on a project and their corresponding privileges.
- Chief
- Maintainer
- User
- Guest