Onboard an Enterprise

Onboard an Enterprise

Create an enterprise, give it a baseline policy, and issue an enrollment token.

1. Exchange the signup token for a bound enterprise resource. This can only be done once per signup token; the returned enterprise name is the parent for every device, policy, and token that follows.
2. Read the enterprise back to confirm the binding persisted and that the notification configuration was accepted as sent.
3. Write the baseline policy every device inherits at enrollment. A policy is created by patching its full resource name, so this same operation both creates and updates.
4. Mint an enrollment token bound to the baseline policy. The returned qrCode is what a factory-reset device scans to enroll.

What you'll need to have ready

• projectId: The Google Cloud project id that will own the enterprise.
• signupUrlName: The signup URL name returned when the signup URL was created (e.g. signupUrls/C1234).
• enterpriseToken: The enterprise token returned to the callback URL after the admin completed signup.
• enterpriseDisplayName: The display name shown to device users for this enterprise.
• policyId: The short policy id to create as the baseline (e.g. "default").
• pubsubTopic: Optional Pub/Sub topic that receives enterprise notifications.

For your developer

Arazzo workflow google-android:onboard-enterprise, 4 operations: createEnterprise → getEnterprise → patchPolicy → createEnrollmentToken. Specs on APIs.io.