Overview
In Salesforce Environment Hub, administrative action sequencing determines whether invited users can see orgs added to the Environment Hub. Because Environment Hub org visibility does not apply retroactively to users who are invited after orgs have already been linked or added, following the proper setup sequence is critical to ensuring seamless org visibility for all team members.
Recommended Best Practice Sequence (Working Path)
To ensure all team members automatically receive visibility into linked Salesforce orgs, execute administrative tasks in the following sequence:
Invite Users: Send user invitations and onboard team members, ensuring they have the required permissions to access Salesforce Environment Hub.
Refer: Inviting users to a project in SFDC | Druva | Documentation
Configure Sharing: Set up and verify the necessary Environment Hub sharing settings and object permissions across user profiles.
Add / Link Orgs in Environment Hub: Add or link target Salesforce orgs within the Environment Hub.
Expected Result: All invited users immediately see and can access all newly added/linked orgs within their Environment Hub view.
Verification
Follow these steps to verify that the best practice sequence succeeded:
Log in as a newly invited user and open the Environment Hub app.
Confirm that all target orgs are visible in the Environment Hub member list.
Non-Working Sequence (Problematic Path)
The sequence below causes visibility issues for newly invited users and should be avoided:
Add / Link Orgs First: Orgs are added or linked to Environment Hub before inviting users.
Invite Users Later: Team members are invited to Salesforce after the org links have already been created in Environment Hub.
Impact / Result: Newly invited users will not see the previously added orgs in their Environment Hub view because visibility settings do not update retroactively.
Workaround (If the Non-Working Sequence Was Followed):
Affected users must manually add or connect the required org to their own Environment Hub view.