Welcome to JumpCloud! Thank you for entrusting us to manage your users and devices. This document gives you a proven, structured approach to implementing our directory services in your organization.
Whether you\u2019re migrating to JumpCloud from another directory service, or beginning to organize and secure your environment, this guide will help you successfully design, test, and implement JumpCloud.
Looking for a more tailored project plan for your specific migration needs? Check out the Implementation Project Plans below based on your selected package.<\/p>\n\n\n\n
Get to know our product terminology<\/strong>:<\/p>\n\n\n\n JumpCloud University is a reflection of how much we value education as part of our solution. This learning platform is designed to give you the flexibility to take applicable courses and skip courses that you don\u2019t need. We believe in freeform learning so you can take any course, watch any video, and practice any task without being locked into a certain series. Learn by doing! Explore JumpCloud\u2019s features from multiple perspectives without impacting your live environment or jumping through hoops for test accounts. JumpCloud\u2019s Guided Simulations page<\/a> contains examples for both admins and users alike. These simulations cover some of our most popular modules such as agent installation, password reset, Conditional Access Policies, and configuring MDM. Before you can really start to build out your JumpCloud directory, we recommend creating and modifying various global settings like password aging, complexity, lockouts, and more. These configurations are enacted on all resources within the JumpCloud platform.<\/p>\n\n\n\n End User Impact<\/strong>: None<\/strong>\/Low<\/strong><\/p>\n\n\n\n This step involves building the user directory. You’ll connect users with devices in the Going Live<\/a> steps.<\/p>\n\n\n\n End User Impact<\/strong>: None<\/strong>\/Low<\/strong><\/p>\n\n\n\n User Import Types and Privileges required<\/strong>:<\/p>\n\n\n\n Considerations<\/strong>:<\/p>\n\n\n\n \u200bStep-by-step Implementation links<\/strong>:<\/p>\n\n\n\n CSV Import<\/strong><\/p>\n\n\n\n Google Workspace Directory Import<\/strong><\/p>\n\n\n\n Don’t connect users to the Google Workspace Directory until you’re ready to Go Live.<\/p>\n\n\n\n Microsoft 365 Directory Import<\/strong><\/p>\n\n\n\n Don’t connect users to the Microsoft 365 Directory until you’re ready to Go Live.<\/p>\n\n\n\n Okta Real Time User Import<\/strong><\/p>\n\n\n\n Active Directory Integration<\/strong><\/p>\n\n\n\n You should deploy the JumpCloud agent on any devices that you want JumpCloud to manage. You can install the JumpCloud agent on devices that are connected to a domain, however the agent is limited to just Commands and System Insights.<\/p>\n\n\n\n End User Impact<\/strong>: Low<\/strong><\/p>\n\n\n\n Required Privileges<\/strong>:<\/p>\n\n\n\n JumpCloud Agent Requirements<\/strong>:<\/p>\n\n\n\n Considerations<\/strong>: <\/p>\n\n\n\n Installation Methods<\/strong>:<\/p>\n\n\n\n Windows<\/strong><\/p>\n\n\n\n Linux<\/strong><\/p>\n\n\n\n macOS<\/strong><\/p>\n\n\n\n Before deploying agents to your macOS devices, JumpCloud recommends configuring JumpCloud MDM with your ABM account. Check out how you can get started with <\/a>JumpCloud<\/a> MDM<\/a>. <\/p>\n\n\n\n If you\u2019re using a third-party MDM (like JAMF, Kandji, Mosyle, etc), you may disregard the latter statement and continue installing the JumpCloud Agent. <\/p>\n\n\n\n Note<\/strong>: Users must approve Full Disk Access to the JumpCloud Agent during install for macOS 12.0+ Monterey. See how to grant full disk access to the JumpCloud Agent<\/a>. <\/p>\n\n\n\n At JumpCloud\u2019s core, it’s all about managing Users, their access, passwords, and identities across your environment. We recommend creating User Groups and Device Groups first as this will help you organize your user and device objects when you begin to import and add resources. As JumpCloud is GBAC-based (group-based access control), before Users can be given access to resources such as SSO Apps, they must be bound to a User Group that\u2019s been granted App access.<\/p>\n\n\n\n Groups are the best way to control users’ access to resources. If the groups will be used to control access to a resource, connect the group to the resource.<\/p>\n\n\n\n End User Impact<\/strong>: Low<\/strong><\/p>\n\n\n\n Considerations<\/strong>:<\/p>\n\n\n\n Implementation Steps<\/strong>:<\/p>\n\n\n\n Device groups can be used to control user or user group access to devices.<\/p>\n\n\n\n End User Impact<\/strong>: Low<\/strong><\/p>\n\n\n\n Considerations<\/strong>: <\/p>\n\n\n\n See Getting Started: Device Groups<\/a> to learn how to create Device Groups.<\/p>\n\n\n\n Educate Your Employees<\/strong><\/p>\n\n\n\n When installing any new software or environment-wide application, it\u2019s always best practice to educate and notify your end users before implementing. Send the following links to your organization employees so they can be aware of any changes, steps, and items during the implementation project. <\/p>\n\n\n\n Note<\/strong>: See Email Templates and Recommendations for Educating Users<\/a> for example user communications before implementing certain features throughout your project plan.<\/p>\n\n\n\n End User Impact<\/strong>: High<\/strong><\/p>\n\n\n\n Ensure end users understand JumpCloud will be managing their identity \u2014 their access to devices, applications, and other resources is managed by JumpCloud.<\/p>\n\n\n\n Considerations<\/strong>:<\/p>\n\n\n\n Implementation Steps<\/strong>:<\/p>\n\n\n\n To use JumpCloud’s Google Workspace Directory integration, one of the following Google licenses are required:<\/p>\n\n\n\n End User Impact<\/strong>: Medium<\/strong> – User workflow impacted<\/p>\n\n\n\n Prerequisites<\/strong>:<\/p>\n\n\n\n Considerations<\/strong>:<\/p>\n\n\n\n Implementation Steps<\/strong>:<\/p>\n\n\n\n\n
Best Practices Before You Start<\/h2>\n\n\n\n
JumpCloud University Admin Training and Certification<\/h3>\n\n\n\n
We believe learning is most effective when the learner gets to choose what they need, when they need it, and how they need it \u2014 and then move on with their day. Structure is there if you want it, but you can easily have freedom to get in, get the information you need, and get out.
Before starting your initial implementation of JumpCloud, we recommend taking the initial courses within our catalogue. JumpCloud is a large platform and is capable of managing a myriad of technical resources. JumpCloud University\u2019s courses train IT admins on best practices for utilizing JumpCloud to the fullest extent.
It\u2019s best practice for newer customers to have an IT team member become JumpCloud Core Certified before rolling out the platform within the technical environment. By obtaining the JumpCloud Core Certificate, this verifies the holder\u2019s core knowledge, best practices, and implementation steps using JumpCloud\u2019s platform.
To get started with your training and certification today, check out JumpCloud University<\/a>.<\/p>\n\n\n\nGuided Simulations<\/h3>\n\n\n\n
These simulations are a great way to help train end users within the organization on how to leverage JumpCloud to do important tasks like managing their passwords, activating their account, and installing the agent.<\/p>\n\n\n\nSupport and Troubleshooting<\/h3>\n\n\n\n
\n
\n
Tips for Set Up and Management<\/h3>\n\n\n\n
\n
Set up your Admin Portal<\/h2>\n\n\n\n
Settings<\/h3>\n\n\n\n
\n
Building Users in JumpCloud<\/h3>\n\n\n\n
\n
\n
\n
\n
\n
\n
\n
\n
Deploying Agents to Devices<\/h3>\n\n\n\n
\n
\n
\n
\n
\n
\n
\n
Configuring JumpCloud Groups<\/h3>\n\n\n\n
Creating User Groups<\/h4>\n\n\n\n
\n
\n
Creating Device Groups<\/h4>\n\n\n\n
\n
Going Live <\/h3>\n\n\n\n
\n
\n
\n
\n
Google Workspace Directory Sync<\/h3>\n\n\n\n
\n
\n
\n