Rollout planner
Work out a phased Cephable rollout for your organization — pilot size, early adopters, timing, and the license and identity work each phase depends on.
Most Cephable rollouts that go badly go badly for the same reason: every seat is licensed on day one, before anyone has confirmed the camera and microphone policies actually allow the app to work. A phased rollout finds that in the pilot instead of in the helpdesk queue.
Enter your numbers below to get a starting plan. It follows the usual shape: prepare, a small pilot, a larger group of early adopters, then everyone else. The seat counts are a guide — in practice, choose each group by team, department, or site.
Pilot size
About 25 seats
Rollout stages
3
Everyone licensed by
Week 8
- 1
Prepare
weeks 1–2- Create the organization and confirm your license count in the Cephable Portal
- Configure SAML single sign-on and verify a test user can sign in
- Confirm camera and microphone policy allows Cephable on managed devices
- Confirm the enterprise installer and staging approach with your Cephable contact
- 2
Pilot
about 25 seats · weeks 3–4 · 5% licensed- Assign licenses to a small pilot group across at least two device models
- Include at least one assistive-technology user and one member of the helpdesk
- Collect setup friction: permission prompts, App Controls switching, mic selection
- Decide the default App Controls you will ship to everyone else
- 3
Early adopters
about 100 seats · weeks 5–6 · 25% licensed- Pick one or two teams or a site, assign their licenses, and push the install to their device group
- Publish the internal getting-started page and open a support channel
- Review usage and helpdesk tickets at the end of the stage before going wider
- 4
Everyone else
about 380 seats · weeks 7–8 · everyone licensed- Assign the remaining licenses and push the install to everyone else
- Apply anything learned from early adopters before pushing
- Go department by department or site by site rather than all at once
- 5
Steady state
from week 9- Turn on SCIM provisioning so joiners and leavers are handled automatically
- Set governance rules for where the assistant may automate
- Schedule a quarterly review of assigned versus active seats
Next steps
- Deploying at scale — the order of operations and device policy
- Single sign-on — configure before the pilot, not after
- Managing licenses — assigning and reclaiming seats per stage
Related
Deployment overview
What deploying Cephable across an organization involves, in the order you will need to do it.
Deploying at scale
What a Cephable rollout involves — getting the app onto devices, getting people into your organization, and the device policy to check first.
Managing licenses and members
Add members, assign seats, set what each role can do, and activate license keys.