CloudShare Creates the First Project
When a CloudShare subscription is activated, CloudShare typically provides the following:
- A CloudShare account for the company, with an initial administrator user.
- An Account Manager user/profile associated with the account.
- Access credentials for signing in and starting to work.
- An initial project that is already linked to the account.
When the account is created, CloudShare also creates an initial project that can be used to configure how the company will use CloudShare.
A project is the main working area in CloudShare. It is more than a simple folder. Each project includes:
- The environments and blueprints that are created and used within the project.
- The policies that control environment runtime and storage.
- The users who are allowed to work with those resources, according to their project role.
- The experiences that package those environments into structured classes, labs, demos, and proof-of-concept sessions.
Additional projects can be created later for different use cases, such as training, proof-of-concept activities, or prospect demos.
When initial sign-in is performed using the access credentials provided by CloudShare, the platform opens in the Training area. As a new Account, the Training list is empty, as shown below:
Best Practices – Planning an Implementation
Determine What Business Success Means
Based on the company’s essential metrics, build a picture of how CloudShare can benefit the business to show ROI. Work with the CloudShare Customer and Technical Account Manager to drive more sales, engage more learners, or reduce internal costs.
Define Metrics
Metrics should not simply revolve around the throughput of users and their hours of usage (although these are important KPIs), but also how any interaction in CloudShare delivers value to the business (such as cost savings from a better understanding of staff, increased sales due to better-prepared partners, reduced support tickets through better-educated users, and so on).
Use Well-Defined Naming Conventions
When creating projects, blueprints, policies, and training or sales enablement experiences, use a naming convention that makes sense and allows growth. For example, projects could be named after regions or business units; blueprints should have version numbers and/or build dates; policies should use names to outline what the policy does, and so on.