NOTE: Only Platform Premier and Platform Enterprise 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 or secondary accounts:
However, the use of secondary accounts grants the primary account additional benefits.
- share data point storage for Intuiface Analytics
- deploy secondary account experiences onto any Player associated with that secondary account
- share cloud storage account(s) for experience publishing and sharing
- share views quota for experiences running on the web via Player Next Gen
- automatically log into the secondary account's Share and Deploy console to share and delete experiences published by the secondary account
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.
Secondary accounts can also be used to test experiences in development, preventing unfinished experiences from appearing within a Primary Account's Experiences panel. Once the Secondary Account's creative team is finished with the experience, they can share it with the appropriate Primary Account for publishing and deployment.
- 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 secondary account request, you have a primary Intuiface account.
A secondary account (SA) is similar in capability to a primary account (PA). A secondary account can
- use Composer and Player licenses to edit and run experiences
- publish and share experiences
- create, edit, and share charts and dashboards as part of Intuiface Analytics
- As data points are associated with their corresponding SA, Primary accounts can also create Secondary account-specific charts and dashboards
- edit Headless CMS bases
- create unique credential keys (independent of the PA credential key) for the automatic retrieval of a paid license
- use the remote deployment feature if the PA is an Enterprise-level account
However, there are some secondary account limitations. Secondary accounts
- cannot purchase licenses
- cannot create (and thus own) a Headless CMS base
- cannot prevent their Primary account from accessing, viewing, or downloading published experiences or Analytics data
- can only use cloud storage provided by their primary account
- cannot view its own or its Primary account's audit trail log
- cannot receive perpetual licenses (a legacy license type) from their primary account (i.e. secondary accounts are limited to receiving subscription licenses)
Secondary accounts are created in response to a primary account request.
- Targeted primary account contains an active Platform subscription or other active licenses. Only accounts without an active Platform subscription - and, for legacy customers, accounts without active Composer/Player subscriptions or perpetual Composer licenses - can receive a secondary account request.
- 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.
- Invited account already has a pending invitation from a different primary account. The already invited account must first decline the pending invitation and then ask for a new invitation from the second primary account.
- Invited account possesses data points. These data points must first be deleted in order for the account to receive a secondary account request.
- Invited account possesses one or more Headless CMS bases. These bases must first be deleted in order for the account to receive a secondary account request.
Steps for creating a secondary account:
- The primary account holder logs into the Manage My Secondary Accounts section of the Management Console.
- 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.
- 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.
- 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 new 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 an Intuiface registration form. Completion of the registration form and a response to the resulting account validation email will create a Secondary Account for them.
- At any time, the primary account holder can cancel this request. The email address targeted receives an email stating the request has been canceled.
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.
Secondary Accounts inherit the data point limit and capabilities determined by their Primary account's Platform plan. Secondary Accounts cannot use Players or store data points that are not visible to the Primary account.
Primary Accounts have access to all data collected by all of their Secondary Accounts.
In order for a Secondary Account to be upgraded to Primary Account status, all of its collected data points must first be deleted.
Within the license dashboard, primary accounts have four options for each secondary account.
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.
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 https://support.intuiface.com, requesting the closure of a specified secondary account.
NOTE: Secondary accounts cannot be closed if they contain
- experiences published to the Primary account's cloud storage
- data points
- active subscription licenses (or legacy perpetual licenses)
- licenses loaned by any Primary account
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.
- 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-stored instance of these experiences must be deleted via the Share and Deploy console. Locally saved versions of experiences can remain.
- Secondary Accounts can only be upgraded if they do not contain data points. These data points must first be deleted.
- Any licenses loaned by the Primary Account for the Secondary Account must first be returned. released.
- Any licenses loaned by Primary Accounts other than the one in possession of the Secondary Account will stay with the Secondary Account after it is upgraded.
- After a return to Primary Account status, the Secondary Account regains the cloud storage configuration it had prior to becoming a Secondary Account.
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 console using 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 console using 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.