Permission types¶
Each permission has the object type the permission relates to. For now three object types are supported:
ZAAK
(case)INFORMATIEOBJECT
(document)
Each object type has its required shape for a blueprint permission. It is explained in the details in Blueprint permissions.
Each permission provides the right to perform one of the following types of operations:
- zaak permissions:
activiteiten:inzien
- to read activities of theZAAK
.activiteiten:schrijven
- to add activities to theZAAK
.checklist:inzien
- to view aCHECKLIST
of theZAAK
.checklist:schrijven
- to edit aCHECKLIST
of the ZAAK.checklisttypes:inzien
- to view theCHECKLISTTYPE
of theZAAK
.checklisttypes:schrijven
- to edit theCHECKLISTTYPE
of theZAAK
.zaken:aanmaken
- to create theZAAK
.zaken:add-documents
- to addINFORMATIEOBJECTs
to theZAAK
.zaken:afsluiten
- to end theZAAK
.zaken:create-status
- to set aSTATUS
on theZAAK
.zaken:geforceerd-bijwerken
- to force edit theZAAK
(after setting aRESULTAAT
).zaken:inzien
- to see theZAAK
details.zaken:lijst-documenten
- to view the list ofINFORMATIEOBJECTs
related to theZAAK
.zaken:nieuwe-relaties-toevoegen
- to add new relations to theZAAK
.zaken:set-result
- to set aRESULTAAT
on aZAAK
.zaken:toegang-aanvragen
- to request access to theZAAK
.zaken:toegang-verlenen
- to manage access to theZAAK
.zaken:wijzigen
- to modify theZAAK
for example to change the confidentiality level.zaakproces:starten
- to start a process related to theZAAK
in camunda.zaakproces:usertasks-uitvoeren
- to perform Camunda tasks.zaakproces:send-bpmn-message
- to send messages in the Camunda process.
- document permissions:
zaken:download-documents
- to see the metadata and content of the document.zaken:update-documents
- to update the content of the document.
The permissions used only in the old version of the ZAC:
- zaak permissions:
zaken:afsluiten
- to close theZAAK
.zaken:set-result
- to set result to theZAAK
.zaken:create-status
- to add status to theZAAK
.
They can be grouped into roles for blueprint permissions. It is explained in the details in the “Blueprint permission” subsection.