There are a number of orgvue environments and your orgvue tenant is only hosted in one environment. (There is a different URL for each environment.) It is important that you access your orgvue tenant at the correct URL.
The URL of your tenant's environment is included in the email you will have received letting you know that you have access to orgvue. See below: the URL is shown underneath the 'Access Your Account' link. (Clicking the 'Access Your Account' link takes you to this environment.)
The tenant name is in bold after 'You now have an account with ...'
We recommend that you retain this email for reference. The first question orgvue Support will likely ask you is what is the name and environment of your tenant.
In addition, once you have signed in to orgvue the tenant name is displayed at the top right of the Workspace :
In this screen shot, the tenant name is 'OrgVue Traini...'.
Should you have access to multiple tenants under your username, you should notice the availability of a drop-down with the tenant name. This provides users ease of navigation to their other tenants.
orgvue Environment URLs are provided within the following linked article: https://support.orgvue.com/hc/en-us/articles/360000166025-orgvue-Hosting-Information
Data Server Resilience
orgvue is hosted in three different AWS regions. (An AWS Region is a physical location in the world where the hosting servers are geographically located.) In each of those regions there are at least three 'Availability Zones' (physical locations) which provide continued orgvue access should one of those Availability Zones fall over. Such an event would be invisible to an orgvue user.
Each Availability Zone has one or more discrete data centres, and each of these has redundant power, networking and connectivity, and is housed in separate facilities.
An orgvue tenant is held in only one of the AWS Regions.
- The AWS backups are stored by AWS itself with KMS encryption in the relevant region
- Backups cannot be moved away from AWS without AWS/KMS permissions
- Production databases are backed up daily by AWS service
- Backups are taken daily, overnight GMT, and retained for 30 days
- Client data is also encrypted when backed up
- Postgres Backup orgvue service uses S3/KMS (also encrypted)
- S3/KMS enforce policies are in place so data cannot be pushed to S3 without KMS permissions
NOTE: When you access orgvue the system will add the current version of the currently accessed orgvue app to your URL like this : -
- You go to https://orgvue.eu-west-1.concentra.io/app/login-gateway
- Once the environment has been accessed you will note that the URL now shows as https://orgvue.eu-west-1.concentra.io/app/login-gateway/1.0.2021020301/ (or similar, note the "1.0.2021020301" on the end of the URL which indicates the version of the login-gateway app)
- Once you have signed in and accessed your orgvue tenant you will see the version number in the URL, like this : -
- Here the orgvue version is 3.12 (and the tenant ID is "ORGVUE_SUPPORT")
- Do not save the versioned URL for orgvue as a bookmark
- Saving the 'clean' URL for orgvue means that you will always be directed to the current version of orgvue
- Version structure : -
- 3.12.202102050156 The leading digit group is the Major Release
- 3.12.202102050156 The second digit group is the Release
- 3.12.202102050156 The third digit group is the Update
Recovery Time Objective / Recovery Point Objective
RTO = 4 hours
RPO = 1 hour
Details on orgvue's security regime are available here : -