Abstract: An internally-constructed permissions graph database enabling a user to construct and alter the graph database permissions within the graph database. Edge permissions define whether a one node can View, Edit, or Manage another node. A node can view another node if there is at least one edge path connecting the nodes having a “View” permission. Similarly, a node can “Edit” or “Manage” another node if there is at least one edge path connecting the nodes having allowing “Edit” and/or “Manage” permissions, respectively. If a contiguous path of permission edges does not exist from the “caller node” to the “requested node” to be acted upon, then permission to perform the desired action or operation on that node is not granted. Edges have permissions, and Nodes have properties. A “Caller Node” makes Requests upon and “Requested Node,” which are limited by edge permissions.

Abstract: An internally-constructed permissions graph database enabling a user to construct and alter the graph database permissions within the graph database. Edge permissions define whether a one node can View, Edit, or Manage another node. A node can view another node if there is at least one edge path connecting the nodes having a “View” permission. Similarly, a node can “Edit” or “Manage” another node if there is at least one edge path connecting the nodes having allowing “Edit” and/or “Manage” permissions, respectively. If a contiguous path of permission edges does not exist from the “caller node” to the “requested node” to be acted upon, then permission to perform the desired action or operation on that node is not granted. Edges have permissions, and Nodes have properties. A “Caller Node” makes Requests upon and “Requested Node,” which are limited by edge permissions.