There are a number of tools available for tenant management outside the OrgVue user interface, which can be used for audit and debugging purposes, and also for data export.
To use these tools, log into OrgVue in the normal way but once your login has been accepted, type/paste the required URL directly into your browser's address bar Note that your standard OrgVue permissions still apply and access to these tools is not available unless you have the Admin role (with two exceptions - the 'tenants' endpoint which is covered in Specimen 1 below and the 'files' endpoint which is covered in Specimen 7 below, for both of which you only need the 'user' role).
In each of the documented uses below, replace [orgvue] with the appropriate address i.e. ‘orgvue2’ , depending on the physical environment you are trying to access.
Because in each instance the OrgVue server is being accessed direct, you will need to state the tenant ID of your tenant within the URL, i.e. replace [tenantID] with your Tenant ID.
The tenant ID may be a non-published anonymous set of alphanumeric symbols, but the first specimen (below) provides a lookup of all tenant IDs and names to which you have access.
Specimen One: List Accessible Tenants
orgvue hosting URL/tenants/tenants
(Note: the current OrgVue hosting URLs are available here - https://support.orgvue.com/hc/en-us/articles/360000166025-OrgVue-Environment-URLs-. You need to replace orgvue hosting URL in the address above with the OrgVue URL on which your OrgVue tenant is located.)
Lists tenant names and IDs for which you have access.
Specimen Two: List Tenant Sessions
orgvue hosting URL/[tenantID]/sessions
Lists the last 50 sessions for all users who access the tenant. The sessions are marked as A (active) or E (expired).
To go further back use this and specify any number you want : -
orgvue hosting URL/[tenantID]/sessions?size=100
Further detail on the sessions concerned can be reviewed based on clicking the corresponding down arrow, and further detail still (drilldown) can be identified by appending the relevant Path indicated to the base URL e.g.
orgvue hosting URL/[tenantID]/dataset/9BFAD887-DCDB-9016-BF51-9841A112A4DD
Specimen Three: Transactions
orgvue hosting URL/[tenantID]/transactions
orgvue hosting URL/[tenantID]/transactions/50
orgvue hosting URL/[tenantID]/email@example.com
List the most relevant transations on the tenant, can be restricted by number or by named user account if required
** Note this page contains advanced functionality of which you should be aware before accessing it, please contact OrgVue Support before accessing this page **
Specimen Four: Users in a Tenant
orgvue hosting URL/[tenantID]/users
For Tenant Admins - lists all individuals with access to the tenant, also showing their role
For non-Tenant Admins - lists all individual's role (s) if they have tenant access
Specimen Five: Datasets in a Tenant
orgvue hosting URL/[tenantID]/datasets
List of datasets and owners with ability to:
- access audit log - see Events by Key link
- download csv - see CSV link on left
- download tsv - see TSV link on left
- upload/merge data - see Upload link
- link direct to Transactions - see above
When using the standard OrgVue export function (i.e. Copy) in rare circumstances with very large data structures, Excel may fail to export correctly. By using the download/export methods here (click on the relevant link), this will be guaranteed to be a true representation of the data, without any TSV parsing issues that might exists between the copy buffer and Excel.
Note that the property names shown in the headers of the export will be the keys for the data, which are normally hidden in the standard OrgVue user interface.
Specimen Six: Tasks
orgvue hosting URL/[tenantID]/tasks
Shows dataset-associated tasks
Specimen Seven: Files in a Tenant
orgvue hosting URL/[tenantID]/files
This is a secure encrypted location where the client is able to place files without exposing them to the perils of sending files through by email. This is a useful transfer location when trying to diagnose problems.
This endpoint can be accessed by a profile with either the 'user' or 'admin' role.
Note also that files can be tagged with view/edit role associations as well.