Introduction

NOTE: Only Premier and Enterprise-level Intuiface accounts can request the creation of and manage secondary accounts.

Design agencies and other Intuiface users often work on multiple projects for multiple clients simultaneously. To simplify license and experience sharing with these clients - and to limit client visibility to experiences specific to their project(s) - Intuiface includes the notion of secondary accounts. Primary accounts - i.e. any traditional Intuiface account - can have any number of linked secondary accounts.

A primary account at the Premier and Enterprise levels can already, for any other primary and secondary accounts:

• share experiences
• loan subscription and perpetual licenses

However, use of secondary accounts grants additional benefits.

• share data point plans for Intuiface data tracking. See here for details.
• deploy experiences - either shared with or owned by the secondary account - onto any Player associated with that secondary account. See here for details.
• share cloud storage account(s) for experience publishing and sharing. See here for details.
• automatically log into the secondary account's Share and Deploy console to share and delete experiences published by the secondary account. See here for details.
• share perpetual Composer licenses, no need to formally loan them. See here for details. (NOTE: Perpetual Composer Enterprise licenses are no longer sold. Only legacy Intuiface accounts may have such licenses.)

The result is an ability to access and deploy both experiences and licenses at the project level. Each project could have its own Intuiface account - a secondary account - and that account would only have visibility to the experiences and licenses the primary account holder wanted to share.

NOTE:

• The only way to create a secondary account is in response to a request from a primary account - see the next section. If you have not explicitly responded to a request, you have a primary Intuiface account.
• Secondary accounts have the same capabilities as primary accounts, including the ability to use the remote deployment feature of Intuiface.

Capabilities of a Secondary Account

A secondary account (SA) is similar in capability to a primary account (PA). For example, a secondary account can 1) use Composer and Player licenses to edit and run experiences, 2) publish and share experiences, 3) use its own unique credential key (not the PA credential key) for the automatic retrieval of a paid license, and 4) if an Enterprise-level account, use the remote deployment feature.

However, there are some secondary account limitations. Secondary accounts

• cannot purchase licenses
• can only use subscription licenses loaned by a primary account (any primary account; doesn't have to be their own) or perpetual Composer licenses belonging to their PA - i.e. it cannot directly purchase any licenses
• can only use cloud storage provided by their primary account

Creating a Secondary Account

Secondary accounts are created in response to a primary account request.

Secondary account requests are disallowed under the following circumstances:

• Targeted primary account contains purchased or loaned licenses. Only after all loaned and owned licenses are removed can a primary account become a secondary account. Loaned licenses must be retrieved by their owner. Owned licenses must be manually transferred by Intuiface Technical Support into the account of the PA making the request. To work with Technical Support, submit a ticket through the Intuiface Support website.
• Preexisting secondary account is targeted. Secondary accounts cannot be transferred from one primary account to another. The secondary account must first be upgraded to a primary account in order to receive a new secondary account request.

Steps for creating a secondary account:

1. The primary account holder logs into the Manage My Secondary Accounts section of Management Console.
2. In the upper left-hand corner, enter the email address of either an existing Intuiface account or of the person/company you would like to work with.
   
   
3. An email is automatically sent to the address you specified. The table on the Manage My Secondary Accounts page will be updated with a new row for this email address. The Status will be set to Pending.
   
   
4. The email recipient decides whether or not to accept the secondary account request
   
   • Those with a preexisting Intuiface account just have to accept the request. Conversion to a secondary account is automatic. The now secondary account holder can still access all experiences it had access to as a primary account.
   • Those with no preexisting Intuiface account are directed to a custom Intuiface registration. Completion of the registration form creates a secondary account for them.
5. At any time, the primary account holder can cancel this request. The email address targeted receives an email stating the request has been cancelled.
   
   

Cloud Storage Rules for Secondary Accounts

Secondary accounts inherit access to the cloud storage accounts of their parent primary account (A secondary account does not have access to the "Storage Settings" option in the Share and Deploy console). At the same time, secondary accounts retain access to all experiences it published and to all experiences shared with it prior to secondary account conversion.

Here are the rules for cloud storage use by secondary accounts:

• All experiences created as a secondary account
  • Published to the primary account's cloud storage account(s).
• All experience published prior to secondary account conversion
  • Remain in the original cloud storage account.
  • Changes made by the secondary account or those granted Write privileges for these experiences are also published to the original cloud storage account.

In summary, Intuiface remembers which cloud storage accounts were used prior to secondary account conversion and continues to use them with experiences published to those cloud accounts.

Data Tracking Rules for Secondary Accounts

Secondary Accounts can define their own data tracking connectors and have exclusive access to their data points. Primary Accounts cannot see data points collected by Secondary Accounts without first logging into the Secondary Account.

However, the Secondary Account's monthly data point limit is defined at the Primary Account level. Secondary Accounts cannot purchase their own Data Tracking plans.

If a Secondary Account is promoted to a Primary Account, all data points and connectors will be placed into the new Primary Account.

Managing Secondary Accounts

Within the license dashboard, primary accounts have four options for each secondary account.

Permit access to Primary Account's Composer Licenses

By default, the option Permit access to Primary Account’s Composer licenses is set to No, which means the secondary account cannot use Composer licenses possessed by the primary account. Set it to Yes if you want the secondary account to have access to the Primary account's Composer licenses.

Close: Close the Secondary Account

By selecting the Close option, the primary account holder is expressing their desire to close the secondary account. To prevent unintended closure, the primary account holder must submit a ticket to Support at http://support.intuiface.com, requesting the closure of a specified secondary account.

NOTE: Secondary accounts cannot be closed if they contain

1. experiences published to any of the primary account's cloud storage providers
2. subscription licenses transferred by the primary account

Published experiences must be deleted and transferred licenses returned before the secondary account can be closed.

Upgrade: Convert to Primary Account Status

By selecting the Upgrade option, the primary account holder releases the secondary account, returning it to primary account status. The secondary account holder will receive an email notifying them of the upgrade.

NOTE:

• Secondary accounts can only be upgraded if they do not contain experiences published by the secondary account to any of the primary account's cloud storage providers. The cloud-based version of these experiences must be deleted via the Share and Deploy console. Locally-saved versions can remain.
• Any licenses transferred into the secondary account will stay with the secondary account after it is upgraded. If the primary account wishes to keep licenses transferred into the secondary keep, those licenses must be retrieved. See this article for details.
• After a return to primary account status, the secondary account regains the cloud storage configuration it had prior to becoming a secondary account.

Access: Remote Login for Deployment and Experience Management

By selecting the Access option, the primary account holder is logged into the secondary account's Share and Deploy console. The primary account holder can now

• view data points collected via the Data Tracking interface asset
• share and delete experiences published by the secondary account
  • It is not necessary to use the Access action in order to share or delete published experiences. This can be achieved simply by logging into the Share and Deploy consoleusing the primary account credentials and then selecting a secondary account from the dropdown list at the top of the console.
• deploy experiences - either shared with or owned by the secondary account - to Players associated with the secondary account
  • It is not necessary to use the Access action in order to deploy experiences. This can be achieved simply by logging into the Share and Deploy consoleusing the primary account credentials and then selecting a secondary account from the dropdown list at the top of the console.

In addition, the license dashboard can be accessed, permitting the primary account holder to release licenses consumed by the secondary account.

NOTE: To return to the primary account's Management Console, log out of the active Management Console session then log back in using primary account credentials.