EMMAWiki/TermsAndConcepts/ForUsers/Access Control - Revision history

Alu: /* Access control by permissions */

2011-10-26T12:17:54Z

Access control by permissions

← Older revision		Revision as of 14:17, 26 October 2011
Line 92:		Line 92:

	'''Warnings:'''		'''Warnings:'''

	{{Warning}} Use of ''No'' can have bad effects. You can lock yourself out from an object, even your own. Be carefull to set group permissions to ''No''. Maybe you are a member of that group?		{{Warning}} Use of ''No'' can have bad effects. You can lock yourself out from an object, even your own. Be carefull to set group permissions to ''No''. Maybe you are a member of that group?

Alu: /* Access control by permissions */

2011-10-26T12:17:38Z

Access control by permissions

← Older revision		Revision as of 14:17, 26 October 2011
Line 92:		Line 92:

	'''Warnings:'''		'''Warnings:'''
			{{Warning}} Use of ''No'' can have bad effects. You can lock yourself out from an object, even your own. Be carefull to set group permissions to ''No''. Maybe you are a member of that group?

	~~/!\ Use of ''No'' can have bad effects. You can lock yourself out from an object, even your own. Be carefull to set group permissions to ''No''. Maybe you are a member of that group?~~		{{Warning}} Be careful with ''Change permisions''. If you set it to ''No'' for yourself, you will not be able to set it back. If you set it to ''Yes'' for another user, this person may alter the permissions at will. Normally this should be left '''Undefined''' except for the owner.

	~~/!\~~ Be careful with ''Change permisions''. If you set it to ''No'' for yourself, you will not be able to set it back. If you set it to ''Yes'' for another user, this person may alter the permissions at will. Normally this should be left '''Undefined''' except for the owner.

	==== Remarks on permissions ====		==== Remarks on permissions ====

Admin: 10 revisions

2011-10-26T06:13:15Z

10 revisions

← Older revision	Revision as of 08:13, 26 October 2011
(No difference)

imported>MichaelDondrup at 16:37, 1 September 2005

2005-09-01T16:37:47Z

← Older revision		Revision as of 18:37, 1 September 2005
Line 50:		Line 50:

	The role of a member may vary between different projects. You could be Chief in your own project, but guest in projects of other groups.		The role of a member may vary between different projects. You could be Chief in your own project, but guest in projects of other groups.
	<a name="permissions" />
			<a name="permissions">
	== Access control by permissions ==		== Access control by permissions ==
			</a>

	GPMS roles define global rights on a project, e.g. if you are allowed to add users or delete something at all. But what if you want to give access to the experiment		GPMS roles define global rights on a project, e.g. if you are allowed to add users or delete something at all. But what if you want to give access to the experiment

imported>MichaelDondrup at 16:34, 1 September 2005

2005-09-01T16:34:55Z

← Older revision		Revision as of 18:34, 1 September 2005
Line 50:		Line 50:

	The role of a member may vary between different projects. You could be Chief in your own project, but guest in projects of other groups.		The role of a member may vary between different projects. You could be Chief in your own project, but guest in projects of other groups.
			<a name="permissions" />
	== Access control by permissions ==		== Access control by permissions ==
	~~[[#permissions\|'']]~~

	GPMS roles define global rights on a project, e.g. if you are allowed to add users or delete something at all. But what if you want to give access to the experiment		GPMS roles define global rights on a project, e.g. if you are allowed to add users or delete something at all. But what if you want to give access to the experiment

imported>MichaelDondrup at 16:29, 1 September 2005

2005-09-01T16:29:14Z

← Older revision		Revision as of 18:29, 1 September 2005
Line 52:		Line 52:

	== Access control by permissions ==		== Access control by permissions ==
			[[#permissions\|'']]

	GPMS roles define global rights on a project, e.g. if you are allowed to add users or delete something at all. But what if you want to give access to the experiment		GPMS roles define global rights on a project, e.g. if you are allowed to add users or delete something at all. But what if you want to give access to the experiment

imported>MichaelDondrup at 16:08, 1 September 2005

2005-09-01T16:08:45Z

← Older revision		Revision as of 18:08, 1 September 2005
Line 103:		Line 103:
	* If youwant to set an object to immutable, to prevent accidential deletion, set the ''delete'' permission for ''ALL'' to ''No''. If you later change your mind, you can set the permission back.		* If youwant to set an object to immutable, to prevent accidential deletion, set the ''delete'' permission for ''ALL'' to ''No''. If you later change your mind, you can set the permission back.
	* Permissions do not automatically account for Arrays and Data in Experiments. They have to be set explicitly.		* Permissions do not automatically account for Arrays and Data in Experiments. They have to be set explicitly.
			* When a member is removed from a project, the permissions are not automatically removed. Also the ownership of the Experiments the user has created remains. This serves to track, who created what. The former member will not have the possibility to see his objects as he cannot log in. If necessaray the ownership of the old objects can be changed by the Chief. If later the member is added again, the permissions will apply again.

imported>MichaelDondrup at 16:00, 1 September 2005

2005-09-01T16:00:24Z

@@ Line 5: / Line 5: @@
 The access control model in EMMA is two-fold. It consists of the two basic components:
 * '''Role-based access control''' -- Defines global privileges for a specific project.
 * '''Access control by privileges''' -- Defines per-object (experiment, data) access
@@ Line 39: / Line 39: @@
 Here are the different types of roles you can have in a project and their corresponding privileges.
 * '''Chief''' -- The main responsible, may add, edit and delete almost everything, including array layouts and pipelines. May add and remove members of a project.
 * '''Maintainer''' -- Same as Chief, but may not manage memberships.
@@ Line 48: / Line 51: @@
 The role of a member may vary between different projects. You could be Chief in your own project, but guest in projects of other groups.
-== Access control by privileges ==
+== Access control by permissions ==

imported>MichaelDondrup at 17:35, 31 August 2005

2005-08-31T17:35:49Z

← Older revision		Revision as of 19:35, 31 August 2005
Line 3:		Line 3:

	Access control in EMMA 2.0 is provided for each individual object. You may check and change other member's rights on experiments and data you have created.		Access control in EMMA 2.0 is provided for each individual object. You may check and change other member's rights on experiments and data you have created.
			The access control model in EMMA is two-fold. It consists of the two basic components:

	To understand, how access control works in emma, we have to look at the following concepts:		* '''Role-based access control''' -- Defines global privileges for a specific project.
			* '''Access control by privileges''' -- Defines per-object (experiment, data) access

			== Role-based access control ==

			To understand, how role-based access control works in emma, we have to look at the following concepts:

	* User		* User
Line 41:		Line 47:

	The role of a member may vary between different projects. You could be Chief in your own project, but guest in projects of other groups.		The role of a member may vary between different projects. You could be Chief in your own project, but guest in projects of other groups.

			== Access control by privileges ==

imported>MichaelDondrup at 17:29, 31 August 2005

2005-08-31T17:29:42Z

@@ Line 2: / Line 2: @@
 = 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 careful to not lockout yourself from this object by setting permissions to 'No'.
+Access control in EMMA 2.0 is provided for each individual object. You may check and change other member's rights on experiments and data you have created.
-* 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
+To understand, how access control works in emma, we have to look at the following concepts:
-** Maintainer
-** User
+* User
-** Guest
+* Member