Security/Data restrictions - Revision history

Tvi: 38 revisions imported

2021-12-10T10:55:26Z

38 revisions imported

← Older revision

Revision as of 12:55, 10 December 2021

2013-03-09T10:07:57Z

Permissions [mandatory]

← Older revision		Revision as of 12:07, 9 March 2013
Line 24:		Line 24:
	* 0-1 Status (records have status)		* 0-1 Status (records have status)
	* 0-1 Blocks (fields belong to blocks)		* 0-1 Blocks (fields belong to blocks)
	* ~~Read permission~~		* Allow read
	* ~~Write permission~~		* Allow write

			Permissions stack in an aggregate like manner, allowing to build complex structures from different fragments. This is also the reason that the Allow read and Allow write properties can be set to empty values (typically for generic permissions).

	=== Differentiated FIELD level access ===		=== Differentiated FIELD level access ===

2013-03-09T10:01:43Z

Differentiated FIELD level access

← Older revision		Revision as of 12:01, 9 March 2013
Line 28:		Line 28:

	=== Differentiated FIELD level access ===		=== Differentiated FIELD level access ===
	Fields belong to blocks.		Fields belong to blocks. Permissions may be bound to such a block.

	A permission with a block specified will ONLY apply to the fields belonging to this block.		A permission with a block specified will ONLY apply to the fields belonging to this block.

2013-03-09T09:58:49Z

Understanding permissions

← Older revision		Revision as of 11:58, 9 March 2013
Line 8:		Line 8:

	* '''Optional''' filters binding certain data to certain users		* '''Optional''' filters binding certain data to certain users
	** Owner user		** Owner user (the user that created the record)
	** List of users		** List of users (dynamic list of users for each record)
	** Per group		** Per group (group property)

	If a user has no active permissions, they will not have any kind of access to the solution. Filters on the otherhand is just considered to be additional restrictions, limiting the access granted by permissions.		If a user has no active permissions, they will not have any kind of access to the solution. Filters on the otherhand is just considered to be additional restrictions, limiting the access granted by permissions.

2013-03-09T09:57:23Z

Differentiated STATE level access

← Older revision		Revision as of 11:57, 9 March 2013
Line 34:		Line 34:
	=== Differentiated STATE level access ===		=== Differentiated STATE level access ===
	Permissions may be bound to a certain status.		Permissions may be bound to a certain status.

			A permission with a status specified will ONLY apply to records in this status.

	== Filters [optional] ==		== Filters [optional] ==

2013-03-09T09:56:49Z

Differentiated FIELD level access

← Older revision		Revision as of 11:56, 9 March 2013
Line 29:		Line 29:
	=== Differentiated FIELD level access ===		=== Differentiated FIELD level access ===
	Fields belong to blocks.		Fields belong to blocks.

			A permission with a block specified will ONLY apply to the fields belonging to this block.

	=== Differentiated STATE level access ===		=== Differentiated STATE level access ===

2013-03-09T09:55:15Z

Understanding permissions

← Older revision		Revision as of 11:55, 9 March 2013
Line 11:		Line 11:
	** List of users		** List of users
	** Per group		** Per group

			If a user has no active permissions, they will not have any kind of access to the solution. Filters on the otherhand is just considered to be additional restrictions, limiting the access granted by permissions.

			In both cases the security restrictions allways apply, even during system access, API interaction, intergration etc.

	== Permissions [mandatory] ==		== Permissions [mandatory] ==

2013-03-09T09:51:09Z

Filters [optional]

← Older revision		Revision as of 11:51, 9 March 2013
Line 34:		Line 34:

	Access to configuration:		Access to configuration:

	Designer > [solution] > Security - Filters		Designer > [solution] > Security - Filters

2013-03-09T09:50:55Z

Data/record filters [optional]

← Older revision		Revision as of 11:50, 9 March 2013
Line 29:		Line 29:
	Permissions may be bound to a certain status.		Permissions may be bound to a certain status.

	== ~~Data/record filters~~ [optional] ==		== Filters [optional] ==

	All ownership options can be overrided by belonging to a certain group, that ignores all types of filters (3 below).		All ownership options can be overrided by belonging to a certain group, that ignores all types of filters (3 below).

2013-03-09T09:39:43Z

Differentiated access [mandatory]

← Older revision		Revision as of 11:39, 9 March 2013
Line 12:		Line 12:
	** Per group		** Per group

	== ~~Differentiated access~~ [mandatory] ==		== Permissions [mandatory] ==

	Permissions to solutions are granted as a sum of multiple permissions.		Permissions to solutions are granted as a sum of multiple permissions.
Line 28:		Line 28:
	=== Differentiated STATE level access ===		=== Differentiated STATE level access ===
	Permissions may be bound to a certain status.		Permissions may be bound to a certain status.


	== Data/record filters [optional] ==		== Data/record filters [optional] ==