In order to understand how Vulcan works, let's first agree some common language and terminology for the core concepts.
As in most applications, the
User identity runs through every aspect of Vulcan.
Users have, by default, an
Users can be owners or members of
Organisations - and are able to switch freely between their
Organisations associated with the
User account. They have various
roles and various
Organisations have many
Organisations are business or company accounts, usually associated to a
Projects have many
Projects have specified types, according to the Vulcan Modules. These can be Knowledge and Research Projects, Chatbot Projects, Automation Projects - and there's more to come.
Charts are individual canvas workspaces that information
Objects are collected, laid out, organised and interacted with.
Objects are the nodes that represent information in a given
Objects have types, grouped according to the Vulcan Module, and depending on the type, will have particular features and characteristics.
Properties, which can be inspected and interacted with via the
Property Editor is relevant to the
Object and we will discuss more of the specific
Property Editor features in these docs.
Property Editor has access to a library or
Components are small, targeted dynamic "widgets" that contain extended functionalities, that can be added in-line to the
Property Editor's text-editor via "slash-commands" or via tabbed pages.