Ask the Community
Groups
Overview of client onboarding steps - Connect IT Community | Kaseya
<main> <article class="userContent"> <p>This article provides an overview of how to onboard a new client company.</p> <ol><li>Create a <strong>new client organization</strong> that is linked to your PSA and RMM.</li> </ol><ul><li>Create the organization in your PSA and then change it to a Type ("Customer") and Status ("Active") that's enabled for sync.</li> <li>If using RMM only, create the organization via manual entry in IT Glue.</li> <li>It's recommended that the client sub-organizations are created too, in your PSA and, if possible, in your RMM. First, decide whether the organization is even <a href="/home/leaving?allowTrusted=1&target=https%3A%2F%2Fkaseya.vanillacommunities.com%2Fkb%2Farticles%2Faliases%2Fitglue%2Fhc%2Fen-us%2Farticles%2F360004934517-When-to-use-sub-organizations-" rel="noopener nofollow">suitable for this kind of structure</a>.<br><br> To create the <strong>comparable parent/child structure</strong> in IT Glue:</li> </ul><ul><li>Create the sub-organization in your PSA and then change it to a type ("Customer") and status ("Active") that's enabled for sync.</li> <li>If using RMM only, create a new organization in IT Glue and make sure it's assigned to a parent organization.</li> <li>Capture all<strong> locations and contacts</strong>.</li> </ul><ul><li>Capture this information in your PSA and and let it push to IT Glue.</li> <li>If using RMM only, create this information via import or manual entry in IT Glue.</li> <li>Create each of the<strong> client's vendors</strong> as organizations that are linked to your PSA.</li> </ul><ul><li>Create the organization in your PSA and then change it to a type ("Vendor") and status ("Active") that's enabled for sync.</li> <li>If using RMM only or if not syncing with PSA vendors, create the vendors via manual entry in IT Glue.</li> <li>Next, deploy your <strong>RMM agents</strong>.</li> </ul><ul><li>Let the configuration data sync to your PSA and then from your PSA to IT Glue.</li> <li>If using RMM only, determine whether to use any additional data collection methods, such as network scanning. Import this information into IT Glue.</li> <li>After the next RMM sync, <strong>match data from your RMM </strong>to data inside IT Glue, such as configurations items that propagated from your PSA or that your team entered directly into IT Glue.</li> <li>Set up <strong>user roles and accesses</strong> to the organization.</li> </ul><ul><li>Every item within IT Glue can be secured down to the user and group level, offering different access levels and visibility of sensitive data. For more information, see <a href="/home/leaving?allowTrusted=1&target=https%3A%2F%2Fkaseya.vanillacommunities.com%2Fkb%2Farticles%2Faliases%2Fitglue%2Fhc%2Fen-us%2Farticles%2F360004935397-Inviting-clients-to-your-IT-Glue-account" rel="noopener nofollow">Inviting clients to your account</a>.</li> <li>Continue to document all the <a href="/home/leaving?allowTrusted=1&target=https%3A%2F%2Fkaseya.vanillacommunities.com%2Fkb%2Farticles%2Faliases%2Fitglue%2Fhc%2Fen-us%2Farticles%2F360004938398-Getting-started-Building-blocks" rel="noopener nofollow">building block assets</a>.</li> <li>When you're done with the building blocks, document any remaining <strong>flexible assets </strong>and continue to document<strong> passwords</strong> as you go.</li> <li>Finally, create any client-specific <strong>written procedures</strong>.</li> </ul><p>Related articles</p> <ul><li><a href="/home/leaving?allowTrusted=1&target=https%3A%2F%2Fkaseya.vanillacommunities.com%2Fkb%2Farticles%2Faliases%2Fitglue%2Fhc%2Fen-us%2Farticles%2F360004938038--Syncing-between-IT-Glue-and-PSAs-overview" rel="noopener nofollow">Syncing between IT Glue and PSAs overview</a></li> <li><a rel="nofollow" href="/home/leaving?allowTrusted=1&target=https%3A%2F%2Fkaseya.vanillacommunities.com%2Fkb%2Farticles%2Faliases%2Fitglue%2Fhc%2Fen-us%2Farticles%2F360004933697">About RMM configuration integrations</a></li> </ul> </article> </main>