Environment: Cloud & Vortex Organization 

Summary:

Org Admins from Org B are able to "suggest changes" for UserA, who is managed by Org A, after UserA logs in and becomes active. This violates the managed user process as Admin from Org B should not have authority over UserA's profile details.

Additionally, the managed UserA will not be able to take any action on the suggestions. Therefore it creates the confusion for admin of Org B as he think he can suggest the change it will work.

Steps to Reproduce:

1. Manage a UserA into Org A.
2. Invite UserA to Org B.
3. Note that initially, the suggestion button for UserA is not functional until the status is invite in Org B. It requires to be "Active" in status.
4. Once UserA logs into the site/product (Org B) the status will change from invited to active.
5. Org B admin will see an option to "suggest changes".

Expected Results: Admin from Org B should not be able to make any profile change suggestions for UserA, as UserA is a managed account under Org A.

Actual Results: After UserA logs in and becomes active, Admin from Org B are able to make profile change suggestions for UserA, despite UserA being managed by Org A. The managed UserA will not be able to take any action on the suggestions.

This creates a conflict with the managed user process.