User Rights - Revision history

NWE at 18:50, 8 February 2017

2017-02-08T18:50:04Z

MHM at 12:19, 11 January 2017

2017-01-11T12:19:02Z

LGE at 12:58, 2 September 2016

2016-09-02T12:58:49Z

LGE at 12:53, 2 September 2016

2016-09-02T12:53:19Z

LGE: Created page with "For security and administration purpose, {{UBIK}} allows configuring different access rights for users on the server. The client allows/disallows certain actions based on thes..."

2016-09-02T12:52:58Z

Created page with "For security and administration purpose, {{UBIK}} allows configuring different access rights for users on the server. The client allows/disallows certain actions based on thes..."

New page

For security and administration purpose, {{UBIK}} allows configuring different access rights for users on the server. The client allows/disallows certain actions based on these configurations.

== Scopes ==
Scopes affect how different rights can be assigned. The following scopes are supported.
* Per User: For the same content, different users might be assigned with different rights.
* Per Object: User rights can be assigned to single object instances.

== Definitions ==
[[File:UI_WinX_User_Rights_ReadOnly_Object.png|thumb|An read-only object]]
[[File:UI_WinX_User_Rights_ReadOnly_Properties.png|thumb|Properties of an read-only object]]
The following user rights are defined in {{UBIK}}.
* Read & Write: Users can do anything to the content (only from a user right perspective, however, it is still subject to other rules such as the editability of properties).
* Read-Only: Users can only view the content. Modifications such as editing, deleting and creating children are not allowed.
* No Right: This is only implicit on the client in the sense that content defined as such will not even be delivered from the server to the client.

All these user rights applied on the content usually do not extend by relations. For example, a read-only object does not prevent its children from being modified unless the children carry the read-only right themselves.

{{Attention|One exception to this is the [[MRO_Objects_(UBIK_WinX)#Task_Owner|MRO task owner]] object. If a task owner is configured as read-only, all its MRO related children will be read-only as well.}}

← Older revision		Revision as of 18:50, 8 February 2017
Line 21:		Line 21:

	[[Category:WinX\|User Rights]]		[[Category:WinX\|User Rights]]
		+	[[Category:Android\|User Rights]]

← Older revision		Revision as of 12:58, 2 September 2016
Line 19:		Line 19:
	{{Attention\|One exception to this is the [[MRO_Objects_(UBIK_WinX)#Task_Owner\|MRO task owner]] object. If a task owner is configured as read-only, all its MRO related children will be read-only as well.}}		{{Attention\|One exception to this is the [[MRO_Objects_(UBIK_WinX)#Task_Owner\|MRO task owner]] object. If a task owner is configured as read-only, all its MRO related children will be read-only as well.}}

−	~~[[Category:Pages with broken file links\|User Rights]]~~
	[[Category:WinX\|User Rights]]		[[Category:WinX\|User Rights]]

← Older revision		Revision as of 12:53, 2 September 2016
Line 18:		Line 18:

	{{Attention\|One exception to this is the [[MRO_Objects_(UBIK_WinX)#Task_Owner\|MRO task owner]] object. If a task owner is configured as read-only, all its MRO related children will be read-only as well.}}		{{Attention\|One exception to this is the [[MRO_Objects_(UBIK_WinX)#Task_Owner\|MRO task owner]] object. If a task owner is configured as read-only, all its MRO related children will be read-only as well.}}
		+
		+	[[Category:Pages with broken file links\|User Rights]]
		+	[[Category:WinX\|User Rights]]

@@ Line 5: / Line 5: @@
 * Per User: For the same content, different users might be assigned with different rights.
 * Per Object: User rights can be assigned to single object instances.
 == Definitions ==