Child pages
  • Confluence page permissions and ConfiForms

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • each form has an administrator(s) - a user(s) who can do all the operations with stored data 
  • form administrator is the one who has EDIT permissions on the page where form is configured or ConfiForms Form macro has explicitly set this person (or a group) as form administrator
  • each stored entry has an owner (or owners), a user who has created this entry (by default, but could be overwritten). Each record in ConfiForms has an ownedBy user multi-select field (part of metadata fields Documentation). Which can be used to give/share an ownership to the record between individuals (form administrators will have this ability in any way, no matter who is the owner of the record)
  • an owner could change entry data (unless edit functionality is disabled, but only in the fields which are not restricted to this user)
  • anonymous users can create records but cannot modify any record (this is because the record has to be owned by the user and records created by anonymous users owned by "no-one"). Such records could be edited/deleted by form administrators
  • an administrator could change any entry (including "delete"), he has also permissions to export stored data in XML, CSV, JSON and EXCEL formats
  • entry owner is a mutable field and could be changed by a form administrator (or record owner). This means that the original creator of the entry will loose his edit rights to the entry if the owner is altered (ownedBy field)
  • stored data is visible to a user if he has access to the page where form is configured (page VIEW permission)

...