We have an IAM user who already has the admin role. Anyhow they can’t view all the nodes whichever created under the same user account?
Please ensure that you selected the appropriate region to view the available nodes.
When I add users to one project via IAM, they appear in other projects as well. How can I restrict users to specific projects with different permissions?
Create a Project Policy:
In the target project, create a policy that defines the permissions you want to assign to the user. Ensure the policy includes only the resources and actions that the user should have access to.
Add the User to the Project:
Once the policy is created, add the IAM user to the specific project. Assign the role of "Member", and associate the user with the project policies you created in the previous step.
Why is the newly added admin user unable to activate their account, while another added user was activated immediately?
The user might already exist in the system but may not have successfully completed the sign-up process. This can prevent proper activation.
Resolution:
The user should either:
Complete the pending signup process so that this email ID can be added as an admin IAM user,
Notify us from their registered (primary) email address to deactivate the incomplete account so a new invite can be sent.
Another possible reason is that the user may have a primary account with the same email address.
The invitee must switch the CRN to their invited organization in order to activate their IAM user account.