Permission Model

From . .. poMMo .. .

Jump to: navigation, search

Permissions in poMMo are organized similar to phpmyadmin permissions.

Contents

[edit]

Database Tables

The relevant database tables are:

  • PERMISSION
  • PG_PERM (weak entity)
  • PERMISSIONGROUP
  • USER

For the entire database schema see Plugins_Database_Structure

The permission table defines the existing permissions and a short description for its use. Permission Groups are sets of persons that have the same permissions, e.g. Editors, Senders, Admins,... Users are all persons who want to log in poMMo and use its functionalities. (1:n user - permissiongroup) PG_PERM is a weak entity to model the n:m relation: permissiongroup - permission Here each permission id is associated with a permissiongroup id and a FLAG IS_GRANTED that denotes if the respective permission is granted or not.

perm_cat denotes the category used for easier meta-ordering in the webinterface (planned).

[edit]

Permissions listing (16)

[edit]

Category poMMo core functionality [category in DB: CORE]

  • SEND
  • COMPOSE
  • HISTORY
  • SUBSCRIBER
later: SUBSCRIBER_VIEW, SUBSCRIBER_ALL (ADD, DEL, EXPORT)
  • IMPORT
  • GROUP
later: GROUP_VIEW, GROUP_FULL (ADD, DEL)
[edit]

poMMo ADMIN functionality [category in DB: ADMIN]

  • CONFIGURE
(maybe here some extra permissions for messages configurations? The rest is only altered by Administrators)
  • FIELD
later: FIELDS_VIEW, FIELDS_ALL (ADD, DEL, EDIT)
  • SUBSCRIPTFORM


[edit]

poMMo PLUGIN functionality [category in DB: PLUGIN]

  • PLUGINCONF
later: CONF_VIEW, CONF_ALL (EDIT, ENABLE) ?BOUNCECONF
  • USER
later: USER_VIEW, USER_ALL (ADD, EDIT, DEL)
  • LIST
later: LIST_VIEW, LIST_ALL (ADD, EDIT, DEL)
  • RESPPERS
later: RESP_VIEW, RESP_ALL (ADD, EDIT, DEL)
  • BOUNCE
  • additional: (not implemented)
    • MAILINGQUEUE
    • CLICKSTAT
Retrieved from "http://pommo.org/Permission_Model"
Personal tools