Blueprints created in the Tier 3 Cloud Platform can have one of three possible privacy settings: public, private, and private shared. Public blueprints are visible to any customer using the Tier 3 Control Portal and are most widely used for general purpose environments (e.g. “Single Exchange Server”, “Primary Domain Controller”) that use default server templates. Private blueprints are only available for viewing or deployment by users within a given account. It makes sense to use this setting when building blueprints that have unique server templates or configurations that are specific to an organization or business unit. Private shared blueprints are those which are visible to users within a given account as well as any users in sub-accounts. Use this setting when creating blueprints that should be private to a specific organization (i.e. parent account) but are relevant to the sub-account holders who may represent business units or customers.
1. Ensure That Primary Account Has Sub-Accounts
View account details for the parent account and select the “Sub Accounts” option.
In the image above, clicking the name of the topmost account (which is the sub account) displays the sub account details, including a reference to the parent account.
2. Create Private Blueprint from Parent Account
Find the “Create Blueprint” link on the Control Portal navigation menu.
Create a new blueprint with the Privacy Setting set to Private.
Finish building the blueprint (see KB article How to build a Blueprint for full details on completing a blueprint) and submit it for publishing.
While staying within the parent account, navigate to the “All Blueprints” page by clicking the "Blueprints” item in the navigation menu.
Search for and locate the just-created blueprint. In the screenshot below, note that the blueprint was successfully found by searching for a partial name.
3. Attempt to Locate this Blueprint From a Sub Account
Log into the Control Portal using the credentials of a user in a sub account of the parent that created the blueprint.
Search for the blueprint created by the parent account. In the screenshot below, note that the blueprint was not found by searching for a partial name or searching the master list.
The blueprint was not found because the Privacy Setting of “Private” prevented the blueprint from being visible to any other account, including sub accounts.
4. Switch Blueprint’s Privacy Setting to Private Shared
Log into the Control Portal as a user in the parent account.
Locate the recently created blueprint and select it for editing.
On the first page of the Blueprint Designer, switch the Privacy Setting to Private Shared.
Save the blueprint by completing the Blueprint Designer wizard and republishing it. After publication, locate the blueprint and confirm that it has shared visibility.
5. Access Private Shared Blueprint from Sub Account
Log into Control Portal using a user that is part of the sub account.
Search for the blueprint created by the parent account. In the screenshot below, note that the blueprint was successfully found by searching for a partial name.
This user in the sub account is now able to deploy this blueprint as they wish.