White Papers
Abstract
This document defines the onboarding request process for Bob Enterprise subscriptions, clarifying the differences between TechZone managed access and dedicated instances. It guides requesters to the simplest viable option, sets expectations for lead time and justification, and standardizes required information to speed approvals and provisioning while reducing unnecessary dedicated account requests.
Content
Purpose
This document explains the user onboarding request process for Bob Enterprise subscriptions. Its goals are to:
Clearly distinguish request types to reduce confusion and routing delays
Require explicit justification when a trial or TechZone managed account cannot be used
Educate requesters on the differences between Dedicated Instance and TechZone Managed access
Collect complete and consistent information upfront to accelerate approvals and provisioning
Splitting request types has proven effective in guiding users toward the simplest viable option and reducing unnecessary dedicated account requests.
Overview of Access Models
1. TechZone Managed Account (Enterprise – User Access)
Lead‑time expectations: Faster provisioning
Centrally managed by TechZone
Provides user‑level access only
Supports workshops, enablement sessions, demos, and most hands‑on experiences
Additional users must be added by TechZone
Lower cost and operational overhead
Choose this option if you need Enterprise access for workshops, demos, or learning activities and do not require admin‑level control.
2. Dedicated Instance (Enterprise – Admin Access)
Lead‑time expectations: Additional setup time (typically 1+ extra weeks)
Fully dedicated Bob Enterprise subscription
Provides admin‑level access
Higher cost and operational overhead
Choose this option only if your requirements cannot be met using a TechZone managed account or a trial.
Important Guidance for Requesters
General - Read Before Submitting
- Trials and TechZone managed accounts should be the default
- Dedicated instances require clear, explicit justification
- If your primary need is “adding user X so I can run a workshop,” a TechZone managed account is usually sufficient
- This request process is intentionally designed to guide requesters to the most appropriate access model
Policies - Read Before Submitting
To ensure limited resources are available for client engagements and to account for required manual setup steps, the following policies apply:
A valid Opportunity ID is required for all requests. Education-only, test, or exploratory requests are not supported at this time. This policy helps conserve resources for active client and partner engagements
Requests must be submitted at least 7 days in advance
Request reviews typically take up to 5 business days
Account provisioning may take an additional business day, as setup steps within the Bob product are currently manual
Important note on provisioning timelines:
The IBM Bob product team is aware that onboarding and provisioning currently require manual steps. The TechZone team has formally requested product enhancements, including APIs and automation, to improve setup speed and scalability.
Until automation is available, provisioning timelines may vary based on request volume and complexity. The TechZone team will continue to process requests as quickly as possible within these constraints.
If you would like to help accelerate improvements, please communicate the importance of APIs and automation to the IBM Bob product team. Increased visibility and advocacy help prioritize these enhancements.
Request Type A: Bob Enterprise Subscription – Dedicated Instance
Use this request only when admin access, account isolation, or advanced configuration is required.
Submission Instructions
Submit a custom support request including all of the following:
Detailed justification explaining why a trial or TechZone managed account cannot be used
Start Date
End Date
Your Organization (e.g., Global Sales, Client Engineering, Partner Ecosystem)
Admin IBMID / Email
Number of Seats
Number of Bobcoins
Must be requested in packs of 1,000
Recommended: 50–100 coins per user
Maximum: 200 coins per user per month
Opportunity ID
Client Name
Brief description of the event or use case
Note: Dedicated instances require additional lead time and should be requested well in advance of the start date.
Request Type B: Bob Enterprise Subscription – TechZone Managed Account
This is the recommended option for workshops, enablement sessions, and most client‑facing events.
Submission Instructions
Submit a custom support request including all of the following:
Justification for requiring Enterprise access instead of a trial
Start Date
End Date
Your Organization (e.g., Global Sales, Client Engineering, Partner Ecosystem)
Admin IBMID / Email (TechZone contact responsible for user additions)
Number of Seats
Number of Bobcoins
Must be requested in packs of 1,000
Recommended: 50–100 coins per user
Maximum: 200 coins per user per month
Opportunity ID
Client Name
Brief description of the event or use case
Partner Access Process
Partners cannot submit onboarding requests directly. All partner access must be sponsored by an IBM internal owner, typically from the Partner Ecosystem team.
Partner Access via Dedicated Instance
When a Dedicated Instance is approved:
A Partner Ecosystem team member (or designated IBM sponsor) submits the onboarding request
After provisioning, the admin owner may:
Invite partner users directly, or
Manage partner access based on the engagement scope
Appropriate when partners require:
Isolated environments
Admin‑level workflows
Longer‑running or reusable subscriptions
Partner Access via TechZone Managed Account
When using a TechZone managed account:
A Partner Ecosystem team member (IBMer) submits the onboarding request
The request must include a complete list of partner email addresses
The Partner Ecosystem team provides the list to TechZone Support
TechZone Support invites partners to the shared subscription
Preferred for:
Partner‑led or partner‑inclusive workshops
Enablement sessions
Short‑term, event‑based access
Note: Partner email lists should be finalized before the event to avoid delays.
How to Make a Bob Enterprise Onboarding Request
- Partners cannot submit onboarding requests directly
- Partners must work with their IBM internal sponsor (typically from Global Sales or Partner Ecosystem)
- The IBMer submits the request on the partner’s behalf
- Partner email lists must be complete and accurate to avoid onboarding delays
If you are a partner requesting Bob access, please coordinate with your IBM counterpart before the event and provide all emails for the request and any information as found in the requirements in the above section to provide justification and information for the request.
Step 1: Review Access Models and Policies
Before submitting a request, ensure you understand:
- The difference between TechZone Managed Accounts and Dedicated Instances
- That trials and TechZone managed access are the default
- That Dedicated Instances require explicit justification
- That a valid Opportunity ID is required
- That requests must be submitted at least 7 days in advance
Requests that do not meet these criteria may be delayed or denied.
Step 2: Identify the Correct Request Type
Choose one of the following request types based on your needs:
- Request Type A — Dedicated Instance (Enterprise – Admin Access)
Use only when admin‑level access, isolation, or advanced configuration is required and cannot be met through a trial or TechZone managed account. - Request Type B — TechZone Managed Account (Enterprise – User Access)
The recommended option for workshops, enablement sessions, demos, and most client or partner engagements.
Selecting the correct request type helps reduce delays and avoids unnecessary provisioning overhead.
Step 3: Submit a TechZone Support Request
Submit a custom support request and include all required fields for your selected request type (as listed in Sections Request Type A or Request Type B above).
Incomplete requests may be returned for clarification and will extend processing time.
Tip: Be explicit and detailed in your justification, especially when requesting a Dedicated Instance.
Step 4: Reference Official Guidance (IBMers Only)
IBMers can access the full onboarding guide, examples, and submission guidance here:
TechZone Collection – Bob Enterprise Onboarding: https://techzone.ibm.com/collection/69bac0f2c5a26dc2f7881d2d
This collection walks through:
- Bob overview
- Bob positioning
- Bobathon for seller information
- Request submission flow
- Required justification examples
Summary Decision Guide
Requirement | Recommended Option |
Workshops / demos / training | TechZone Managed Account |
User-level access only | TechZone Managed Account |
Admin-level control required | Dedicated Instance |
Faster provisioning needed | TechZone Managed Account |
Account isolation is mandatory | Dedicated Instance |
Final Notes
Partner access must always be sponsored by an IBM internal owner
Clear justification and complete user lists reduce onboarding delays
When in doubt, start with a TechZone managed request and escalate only if requirements cannot be met
RequirementRecommended OptionWorkshops / demos / trainingTechZone Managed AccountUser‑level access onlyTechZone Managed AccountFaster provisioning requiredTechZone Managed AccountAdmin‑level control requiredDedicated InstanceAccount isolation mandatoryDedicated Instance
Final Notes
Partner access must always be sponsored by an IBM internal owner
Clear justification and complete user lists significantly reduce onboarding delays
When in doubt, start with a TechZone managed request and escalate only if requirements cannot be met
Was this topic helpful?
Document Information
Modified date:
07 May 2026
UID
ibm17270891