8000 Create sandbox documentation (#762) · box/developer.box.com@6d13eef · GitHub
[go: up one dir, main page]

Skip to content

Commit 6d13eef

Browse files
authored
Create sandbox documentation (#762)
* Add information about sandboxes * formatting issue * Create sandbox documentation * remove repetition * Apply review comments * lint issues * add link
1 parent 9d93562 commit 6d13eef

File tree

2 files changed

+42
-0
lines changed

2 files changed

+42
-0
lines changed

.spelling

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -358,3 +358,4 @@ SVGs
358358
px
359359
natively
360360
Kus
361+
add-ons
Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
---
2+
rank: 4
3+
related_guides:
4+
- authentication
5+
- authorization
6+
- api-calls
7+
---
8+
9+
# Sandboxes in Box Platform
10+
11+
Developer sandboxes in Box provide a secure, controlled environment where developers can build, test, and collaborate on applications without affecting the actual data of your enterprise. They offer a safe space to experiment with Box APIs, test settings, try new integrations, and work alongside external partners.
12+
13+
## What is a developer sandbox?
14+
15+
A developer sandbox is an environment isolated from your production (live) enterprise setup that keeps development activities separate from real business data.
16+
17+
## Why use a sandbox?
18+
19+
Using a sandbox allows you to:
20+
21+
* Safely build apps within an enterprise-linked environment instead of a free standalone account.
22+
* Collaborate securely with both internal teams and external collaborators. Contractors, partners, and other external users can join the sandbox without accessing live systems and compromising security.
23+
* Test apps under realistic testing conditions, as sandboxes inherit your enterprise's plan and add-ons at creation time. If there are any changes to the plan or add-ons, they can be [manually synced][4] by an enterprise admin.
24+
25+
## Accessing your sandbox
26+
27+
Sandboxes in Box are created by enterprise admins. See [this document][1] to learn how to create a sandbox.
28+
When you are assigned as a primary admin of a sandbox, you receive a log-in email from Box with your sandbox user ID.
29+
30+
To access the [Dev Console][2] inside the sandbox environment and set up a password, click the link in the email. You can also access your sandbox by logging in with your sandbox credentials on [developer.box.com][3].
31+
32+
The sandbox's primary admin can create individual sandbox accounts, giving developers access to a new Box environment that matches the plan of their parent Box enterprise.
33+
34+
### Accessing multiple sandboxes
35+
36+
As a primary admin, you can log into multiple sandboxes. If you want to use this functionality for existing sandboxes, you can remove the unique email address and get a system generated email.
37+
38+
[1]: https://support.box.com/hc/en-us/articles/360043697274-Managing-developer-sandboxes-for-Box-admins
39+
[2]: https://cloud.app.box.com/developers/console
40+
[3]: https://developer.box.com
41+
[4]: https://support.box.com/hc/en-us/articles/360043697274-Managing-developer-sandboxes-for-Box-admins#:~:text=in%20a%20sandbox.-,Synchronizing,-sandbox%20with%20production

0 commit comments

Comments
 (0)
0