Revoke Venturelytic Admin Access

Created by Sharif Oraby, Modified on Wed, 03 Apr 2024 at 11:17 AM by Sharif Oraby

How to Inactivate the Venturelytic Admin in Your Salesforce Org


Following the completion of the implementation phase, we are set to transfer our administrative privileges over to your team. This transition signifies that your Salesforce org will be entirely under your control, ensuring that our access is fully revoked. By following the steps outlined below, you will assume complete management of your Salesforce environment.


Step 1: Change the Primary Contact in Company Information

1. Log in to Salesforce with an account that has System Administrator permissions.

2. Navigate to Setup by clicking the gear icon in the top right corner.

3. Use the Quick Find box to search for "Company Information" and select it.

4. On the Company Information page, find the Primary Contact field.

5. Click Edit and select a new Primary Contact from your organization from the dropdown list.

6. Click Save to apply the changes.


Step 2: Make the Venturelytic Admin User Inactive

1. Return to Setup and use the Quick Find box again to search for "Users".

2. Select Users under the Administration section.

3. Locate the user ‘Admin Venturelytic’ with the email address support@venturelytic.com and profile ‘System Administrator’.

4. Click Edit next to their name.

5. Uncheck the Active checkbox to make the user account inactive.

6. Click Save.


Step 3: Remove the Venturelytic Admin from the "Venturelytic" Installed Package

1. Still in Setup, use the Quick Find box to search for "Installed Packages".

2. Click on Installed Packages.

3. Locate the "Venturelytic" package and click on Manage Licenses next to it.

4. Find the user Admin Venturelytic in the list of licensed users.

5. Click Remove to revoke their access to the Venturelytic package.




Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article