This article provides some initial orientation for those working with OrgVue and some key terminology in context
Pre-requisite for working in OrgVue
- You must have an account provided to be able to access OrgVue: this will give you access to at least one named tenant: your tenant administrator will be able to provide this access
- Once you are notified of your OrgVue access by email, you need to follow a one-off validation step to activate your account
Dataset access using your activated account
- When logging into OrgVue, you log into a single tenant, which is the container for all your activity
- Each tenant has multiple tabs for logical organisation of datasets e.g. People, Roles; each tab typically contains one or more datasets but may contain none
- Work in OrgVue is done within a given dataset within a given tab within a given tenant
- Each dataset will have a set of permissions, shown next to the tag underneath the dataset title. You may not have access to all datasets in your tenant
- If there are no set permissions, such as for dataset 1505 JH in the screenshot above, only the creator of the dataset and tenant administrators can access it.
- If you are "missing" datasets, it is likely that insufficient access permissions have been set i.e. there are datasets present but hidden.
- Permissions can also determine if the data you see is, say, read only or read-write.
- The person who sets overall permissions available in a tenant is typically the Tenant Administrator.
- You can share a dataset with others using appropriately set permissions, otherwise datasets you create are accessible by you only: this article explains how to set permissions
- If you are a non-Admin you can only use known, existing roles to set permissions: only an Admin can create roles.
A logically and physically-separated partition on the OrgVue server keeping your data private and secure: when you log in to OrgVue, you are logging into a specific tenant to you which you have been given access
A container for a set of data that can be opened and analysed via the various tools and capabilities that OrgVue offers: a tenant contains multiple datasets
Data within datasets is comprised of nodes which have properties to describe them. The tab in which a dataset is stored typically describes the node types stored there e.g. in the People tab are datasets which contain data about people i.e. within the People tab, a node typically represents a person.
The type of account assigned to an individual that accesses OrgVue. The base roles are Admin and User, but others can be created.
An Admin role has unlimited access to the content of a tenant and can add users and define roles; other roles, including User, are assigned to define what data non-Admins can and cannot see.