The Staging and UAT tenants should be used as follows:
Production: Live tenant currently in production use
Staging: This is where development works should occur, packages of change are built here for example new forms fields etc.
UAT: the package built in Staging is tested here by both the developing administrator an also end users potential.
Once the package of changes is tested and proved to be working it can be processed in to production.
There are 2 documents which may help
These explain how the opsconsole works and how to manage packages between tenants (if you are on cloud/SaaS) it will be slightly different as the Ivanti SaaS team do the actual application of packages, you can request this via the ISM support portal support.heatsoftware.com its under the service requests tab.
The online help also have some good information
Where we use additional tenant for production examples would be an HR department wants their own tenant with a seperate database for security, it would be hosted on the same infrastructure as the ITSM system but otherwise not connected in anyway.
I hope this makes sense.
Many thanks Alasdair
If a deployment was configured with only a production installation could the Development and UAT tenants be added retrospectively a few months later or is it required that they exists from day one?
See you soon
You can add additional tenants at anytime it doesn't have to be on day one.
Thanks very much Alasdair