Difference between revisions of "Security/Data restrictions"

From TempusServa wiki
Jump to navigation Jump to search
old>Admin
old>Admin
Line 2: Line 2:


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).
Access to configuration:
Designer > [solution] > Security - Filters


=== Ownership by data exclusive group ===
=== Ownership by data exclusive group ===
Designer alias: Use Exclusive groups for access control
[[Fieldtype/Exclusive_group]]
[[Fieldtype/Exclusive_group]]


Line 9: Line 14:
* Cardinality: One
* Cardinality: One


Designer > [solution] > Security - Filters - Use Exclusive groups for access control


=== Ownership by data member lists  ===
=== Ownership by data member lists  ===
Designer alias:  Use Lists of members for each item
The solution contains a [Fieldtype/Member list|memberlist] field where users can have their access added or removed. Behind the scenes a table with a relation between the record and the user is maintained.
The solution contains a [Fieldtype/Member list|memberlist] field where users can have their access added or removed. Behind the scenes a table with a relation between the record and the user is maintained.


Line 18: Line 24:


=== Ownership by being the creator  ===
=== Ownership by being the creator  ===
Designer alias: Use Creator only restriction (ignore group recommended)
You must have created this record in order to see access it.
You must have created this record in order to see access it.



Revision as of 10:14, 9 March 2013

Data/record filters

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

Access to configuration: Designer > [solution] > Security - Filters

Ownership by data exclusive group

Designer alias: Use Exclusive groups for access control

Fieldtype/Exclusive_group

  • Scope: Group
  • Cardinality: One


Ownership by data member lists

Designer alias: Use Lists of members for each item

The solution contains a [Fieldtype/Member list|memberlist] field where users can have their access added or removed. Behind the scenes a table with a relation between the record and the user is maintained.

  • Scope: User
  • Cardinality: Many

Ownership by being the creator

Designer alias: Use Creator only restriction (ignore group recommended)

You must have created this record in order to see access it.

  • Scope: User
  • Cardinality: One

Differentiated FIELD level access

Differentiated STATE level access