Managed Services Deployment Guide for Nudge Security
How to configure multi-tenancy for managed service providers of Nudge Security
Pre-Deployment
Register your NFR/Demo instance of Nudge Security
Register any customer instances of Nudge
Deploy Nudge Security in your environment
Confirm the connection to your customer’s instance
Removing a connected account
Pre-deployment: Register your NFR instance with Nudge Security.
Before you get started, make sure to register with Nudge Security to get access to an NFR (not for resale) instance of Nudge Security.
Note: You’ll also need to register any customer opportunities with Nudge Security.
To get started, please contact sales@nudgesecurity.com.
Step One: Deploy Nudge Security in your environment.
If you don’t have a Nudge Security account for your managed services organization, you’ll need to create one first. It takes just a few minutes to set up.
You can quickly deploy Nudge Security from the following marketplaces:
For additional setup instructions, please refer to our getting started documentation:
Step Two: Set up your customer’s Nudge Security account.
💡 As a reminder, register any customer opportunities with Nudge Security before setting up customer accounts. This will ensure that communications properly route to your MSP organization.
In order to facilitate deployment of Nudge in your customer’s environment, you will use a special link, encoded with your organization’s details. This allows you to seamlessly deploy to your customers and configure their instance for remote management all in one easy step.
In your Nudge instance, visit Settings > Organization Settings and navigate to “Add a managed organization”
Click “Generate link” and a custom (unique to you) link will be generated. Copy this link to deploy your customer’s instance. Note that this link is good for 14 days and will expire afterwards. At any time, you can regenerate a new link, rendering any prior links unusable. Any customer instances created with the links prior to their revocation will not be affected.
💡 Note: A 12 month license is automatically created when this link is used to deploy to your customer’s account. If you or your customer would like to evaluate Nudge beforehand, they will (or you on their behalf) need to deploy a trial using the standard link (nudgesecurity.io/login). Once the evaluation is complete, you can use your “secure deployment” link to associate their instance with yours and establish remote management. This will also create a 12 month license for them at that time.
Step Three: Confirm the connection to your customer’s instance
After using your “secure deployment link” to begin the deployment of a Nudge Security instance in your customer’s environment, you will need to confirm the external management request.
Once you do, this instance of Nudge will available for external management from your Nudge instance. You will see a carrot next to your Instance name that you can click to expose a drop down menu. All Nudge instances managed by your organization will now appear in the menu.
How to remove a connected account
At any time, an administrator within your MSP management account or your customer’s managed account can revoke the connection between the two accounts.
To revoke a connection, start in either account. Navigate to Settings > Organization Settings.
From the MSP management account, navigate to “Add a managed organization.” Find the managed customer account you want to disconnect and click “revoke.”
From the customer managed account, navigate to “Invite an external manager.” Find the MSP management organization account you want to disconnect and click “revoke.”
Note: Removing the connection between a managed service provider and a client will disable the license. The client instance will default to a trial instance valid for 14 days so that, if needed, you can re-establish the connection to the service provider without any data loss.
Need help?
For questions or support, please contact:
sales@nudgesecurity.com for any sales related inquiries
help@nudgesecurity.com for any technical issues