This article lists the frequently asked questions related to login, environment, and licensing information.
Logging In / Environments / Licensing FAQs
How do I log in to Salesforce 2.0 App after inviting a Salesforce 2.0 administrator from inSync?
You will receive an email notification to create a Salesforce 2.0 administrator account. For more information, see Deploying the Salesforce App.
My temporary administrator account credentials have expired after 48 hours duration. How do I proceed?
Contact Support to send a new email invitation. You can activate the administrator account using the new activation email. For more information, see Create Administrator Account for the Salesforce App.
What happens if I authenticate sandbox Org instead of a production Org?
You can associate a license to a production organization only after completing 14 days of association with the current sandbox organization.
How are the active users mapped with the number of organizations that are added from the License page in the Settings tab for a data backup license?
The user can continue to add or authenticate organizations till the threshold of the licensed users is reached.
What happens if I have added an org in the Environment Hub but not in the License page for backup?
It is important that you authenticate the org from the License page after configuring the environment from Environment Hub for backups to work successfully.
How many sandboxes does a sandbox seeding license cover?
The Sandbox Seeding license will cover all of the sandboxes related to a Production org. Users in sandboxes do not count against the users for a license. For example, if you authenticate a production org with 100 users to a license, then the production user count is considered to estimate the license user count. In this case, the license user count will be 100 users.
Why does re-authentication fail or trigger a license limit error after a Salesforce sandbox refresh?
When you perform a sandbox refresh in Salesforce, it generates a completely new Organization ID (Org ID). Because Druva tracks environments by their unique Org ID, the refreshed environment is recognized as an entirely new organization rather than an update to the existing one.
Since standard data seeding/backup licenses typically permit only one Full Sandbox per Production Org for free, attempting to add or re-authenticate the refreshed sandbox triggers a license limit error because the previous sandbox session is still consuming the slot.
How to resolve:
Option 1 (Free): Remove the older sandbox environment association from the Druva Salesforce App, and then create and authenticate a new environment.
⚠️ Warning: Removing the old organization will permanently delete its associated backup sets, archival sets, and data templates.
Option 2: If you need to retain historical backup data for the older sandbox, contact your account manager to procure additional sandbox licensing slots before authenticating the refreshed org.