Vault Schema Configuration
Dynamic type definitions for nodes and relationships
📦 Node Types (4)
User
Key Holder
User node representing system users
3 field(s), 1 required
→
User node representing system users
3 field(s), 1 required
Project
Key Holder
Project node representing a project or initiative
5 field(s), 1 required
→
Project node representing a project or initiative
5 field(s), 1 required
Task
Task node representing a work item
5 field(s), 1 required
→
Task node representing a work item
5 field(s), 1 required
Document
Document node representing files or documentation
5 field(s), 1 required
→
Document node representing files or documentation
5 field(s), 1 required
🔗 Relationship Types (6)
HAS_ACCESS
outgoing
User has access to a key holder node
From: User → To: User, Project, Task, Document
→
User has access to a key holder node
From: User → To: User, Project, Task, Document
OWNS
outgoing
User owns a node
From: User → To: Project, Task, Document
→
User owns a node
From: User → To: Project, Task, Document
PART_OF
outgoing
Entity is part of another entity
From: Task, Document → To: Project
→
Entity is part of another entity
From: Task, Document → To: Project
DEPENDS_ON
outgoing
Task depends on another task
From: Task → To: Task
→
Task depends on another task
From: Task → To: Task
ASSIGNED_TO
outgoing
Task is assigned to a user
From: Task → To: User
→
Task is assigned to a user
From: Task → To: User
RELATED_TO
bidirectional
Generic relationship between entities
From: Project, Task, Document → To: Project, Task, Document
→
Generic relationship between entities
From: Project, Task, Document → To: Project, Task, Document