Enterprise Terminology

  • Blueprint (template):  A master or baseline environment template that may contain machines, storage, networking, pre-installed software, company branding and use case collateral from which all environments are created.
  • Environment Policy:  Defines the amount of time the end-users will have the use of the environment, and how to handle inactivity. The environment’s life time is set according to the environment policy associated with it.  During the Runtime lease, the environment will be up with all machines running. During the Storage Lease , the environment will be archived and can be made accessible by extending it from the environment details page. After the environment disk time expires, the environment is securely deleted. You can also define how to handle inactivity during the Runtime lease (suspend, delete or do nothing)
  • End User (Customer):  Current or potential user of your products who has access to the Environment Explorer only. A customer will not be able to access the CloudShare Dashboard.
  • Invite End User (Customer Invitation):  An End User invitation is a specially crafted email containing a link that grants the invitee the right to the Environment Explorer (Customer portal) only.  The link is a single use token, granting access to one environment as specified by the sender.  Once the email is sent, the invitation token remains valid as configured in the invitation creation form (30 days by default).  The lifetime of the environment is also specified in the invitation creation form by the usage package selected.  Once the environment expires, the customer is automatically removed from the related campaign.  An Invitation can be emailed using CloudShare Dashboard in a fixed format or with your own mail client in any format.
  • Dashboard:  When you first log in to the system, you’ll be presented with a centralized management console called the “CloudShare Dashboard”. This management console is the heart of the CloudShare solution. The dashboard allows provisioning, monitoring and overall control of the environments. (also allows user management, evaluations, usage reports and associated analytics)
  • Environment:  Environments consist of machines, storage, networking, and preinstalled software, of which you and your invited users will each get an independent copy.  They exist as an individual instance (a clone copy) of the Blueprint
  • Environment Explorer:  The User Interface (End User portal) of the running Environment that provides access to the machines and collateral.
  • External Address:  This is your external address as assigned to a specific machine. Upon each environment resume from suspend, typically you will be assigned a new External address.
  • Teams:  Organizations are Project Member user groups that can invite others to, and run environments in their specific organizations. Project Managers can add different organizations (whether partners/re-sellers or different business units), each one headed by one or more Team Managers. Team Managers of a specific organization are limited to the scope of their own team, only Project Managers can oversee all activities across all organizations in their project(s)
  • Preparing (State):  "Preparing" appears when an environment is first created and/or resumed from suspend by clicking the View Environment link. Preparing also appears when you change the resources of a particular machine within your environment. The time it takes for the environment to be ready depends on the number of machines and resources used. In most case, the environment will be ready in less than 5 minutes but may take up to 10 minutes. However, you will be able to access each machine as they become available.
  • Project: A company initiative with which the environment would be associated. A project houses one or a collection of blueprints (prototypes). A project can hold Project Member users from multiple organizations and Environment Policies
  • Project Member:  A user in CloudShare that has access to the Dashboard. The user might have one of the three Project Roles.
  • Project Member Invitation:  A project member user invitation is a specially crafted email containing a link that grants the invitee access to the CloudShare Dashboard. The link allows a one-time creation or modification of a single user. When new users click the link, they fill the required details and become a user of the set role in the project.  If existing users receive the link, the relevant role is added to heir current access level (i.e. if team members receive a project manager invitation, they will become a project manager). To demote users, remove them from the project entirely and then send another invitation at the correct role level
  • Project Roles: CloudShare features a simple user hierarchy comprised of three distinct roles:
    • Project Manager: Project managers are administrators for an entire project, able to see and monitor all users and all organizations in the project, as well as add new project users. Project managers are also able to manage and publish snapshots
    • Team Manager: Team managers are able to add new team members, and view others Environments, but are limited to the scope of their own Organization/team; only Project Managers can see activity in multiple teams
    • Team Member:  Team members can interact with their customers (end users) only - the actions of fellow Team Members or other customers not assigned to them cannot be viewed 
  • Reports:  Allows you the ability to track usage of all your issued environments and resource consumption 
  • Revert:  The "undo all" action provides the ability to restore your environment or individual machine state to a previously saved snapshot 
  • Run Environment:  CloudShare environments are launched in one of three ways: 
    1. End Users (Customer) or Trainees clicks the link in an invitation email
    2. Project Member (Vendor) user clicks the "create environment" button inside the CloudShare Dashboard. Once an environment is created, the user can interact with it via the Environment Explorer. The environment is also accessible under the appropriate environments sub-tab in the CloudShare Dashboard
    3. Sponsored API (Single-Sign-On) provides a robust and secure way to deliver links to environments. Sponsored API was designed specifically to be integrated with external tools such as LMS and CRM solutions. 
  • Running (State): The state of the Machine and or the Environment which is available for access
  • Suspended (State): A dormant state of your environment from which the end users and project members can resume their environments
  • Take Snapshot:  Project Managers can take a snapshot to save the state of the environment - complete with the state of applications that are currently running. You will need to Take Snapshot of the environment you are building in order to save it as a blueprint (prototype), otherwise when the duration of the environment expires, you will loose all your work. You can keep up to 5 snapshots for  each of your blueprints (historical save points). For version control and change management, Enterprise offers two distinct flags available from the "Take Snapshot" page:  
    1. A "Default" snapshot is the snapshot visible to all users. This is the snapshot that will be used when creating a new environment by Team Members or when end users accept new and pending invitations
    2. A "Latest" snapshot is the most recent save point that is not yet made available for general user community since the work is incomplete 
  • View button: Enable you to access the Environment Explorer portal (End User Portal)



Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request


Powered by Zendesk