| Auszug |
|---|
|
Nuclos record grant: $username, INTID, CANWRITE, CANDELETE, CANSTATECHANGE, user groups, PostgreSQL intid. |
Language: Deutsch · English
Record grant
Permissions at record level – via a data source that returns the visible records per user.
| Status |
|---|
| colour | Blue |
|---|
| title | Application developer |
|---|
|
| Status |
|---|
| colour | Green |
|---|
| title | Updated: Jul 2026 |
|---|
|
| Status |
|---|
| colour | Grey |
|---|
| title | applies to Nuclos 4.2026.x |
|---|
|
What is a record grant?
The record grant is a generic concept for permission restrictions at record level. The record grant data source type (Configuration → Data sources → Record grant) is assigned to a business object and receives $username as its only parameter.
| Info |
|---|
|
Principle: username in → data source processes → list of visible records (INTID) out. The only mandatory column is INTID. |
Optional columns
| Column | Effect |
|---|
| CANWRITE | true/false (1/0): controls write access to the record (default: true). |
| CANDELETE | true/false (1/0): controls delete access to the record (default: true). |
| CANSTATECHANGE | since Nuclos 4.8: allows/denies status change independently of CANWRITE (default = value of CANWRITE). General status-change rights must still exist. |
Nesting & assignment
Data sources can be nested; not every one must be assigned to a BO. This lets you model hierarchical or multi-dimensional permissions (e.g. site mapping). Existing permission mechanisms remain and are processed with higher priority.
| Warnung |
|---|
|
Record grants must be assigned under Administration → user group to the user groups they should apply to. On PostgreSQL the intid column must be lowercase. |
Related pages
Status model
Status rights.
Open →
