About Product Builds, Sandboxes, and Run-time Access
This topic provides an overview of how run-time access to product builds in your development sandboxes is configured and controlled.
You should read Introducing User Accounts and Development Accounts, Introduction to Access Groups, and About Product Groups, Products, Product Instances, and Content Packages, before reading this topic.
Sections in this topic:
Introducing Xbox One sandboxes and development accounts
A development sandbox is a special Xbox One Content Isolation container to which product instances and all of the product builds or content packages that they contain can be assigned. Using sandboxes, Content Isolation safeguards your products, along with their configuration information and other related materials, from unauthorized access.
In order to run product builds in any development sandbox, you must log on by using the credentials of a development account that is “owned” by your Xbox One user account. In addition, at least one of the following conditions must apply:
- Your user account is included in an access group that has been both assigned the Runtime Access permission and granted access to the development sandbox that the content package is assigned to.
- You are logging on from a development kit that is included in an access group that has been both assigned the Runtime Access permission and granted access to the development sandbox that the content package is assigned to.
For more information about Runtime Access permission and creating sandboxes, see Grant Run-time Access.
Running your product builds
The following diagrams illustrate the various ways that users can access and run product builds in a development sandbox.
- In this first diagram, the development sandbox and the product builds located in it are shown at the left.
- In the center is an access group that includes two user accounts and one trusted device. Each of the user accounts “owns” one or more development accounts. (Note that a single user account can own many more development accounts than are shown here.)
- To the right are three users, two of whom (Sam and Pat) have user accounts (each with its own development account or accounts) that are included in the access group, and one of whom (Chris) has a user account that is not included in the access group.
Because Pat’s user account is a member of the access group, Pat can log on from any development kit by using the logon credentials of the one development account owned by her user account.
Sam’s user account is also a member of the access group. Sam’s user account owns not one but two development accounts, so Sam can use the logon credentials of either of those development accounts to access and run the product builds in the sandbox.
Sam can also run two logons simultaneously, effectively acting as two separate users, by using the logon credentials of one of his development accounts for one logon and the credentials of his other development account for the other logon.
Chris’s user account does not belong to the access group; but Chris can still run product builds in the sandbox by logging on from the trusted development kit that is included in the group.
Important
Even when logging on from a device that is included in the access group, Chris must use the credentials of a development account that is owned by her Xbox One user account, and not the credentials of the user account itself.