The likely cause to this issue is the fact that the User Record in FinOps is not enabled.
In order for a user to be enabled in FinOps, you must have met the following criteria:
Must have accepted their Invite to Access Evo
Must have been given USER permissions in Access Evo Member Roles to the FinOps database.
Must be in a Security Profile within FinOps Administrator.
You should check with the user that they can access FinOps from the Access Evo nine-dot menu, and when launching FinOps that they are successfully logged in with no errors.
If your user:
Has accepted their invite to Access Evo and are not a deactivated Access Evo user.
Has been given USER permissions in Access Evo Member Roles.
Then you need to check whether they are in a Security Profile in FinOps Administrator.
To do this:
Check you know your CLOUD\Hosting.Admin credentials for authenticating on the FinOps RD Gateway.
In a web browser go to the FinOps RD Gateway and log in using your CLOUD\Hosting.Admin credentials.
Open the FinOps Administrator application and log in to the correct Database.
Click System Control, then Security Profiles.
Select the Security Profile you believe the user should be a Member of and click Members.
User is in User list without a value in Current Profile
If you see the user in the User list without a value in the Current Profile column, this means that the user exists without a profile.
Select the user, then click Add.
Ensure they have a valid Resource Code.
User is in the members list
If your user is in the Members list, or if they are in the Users list with a value in the Current Profile, then they are an enabled user.
The only exception to this is if the user has a pending Access Evo invite and they haven't accepted it yet.
If they have accepted their invitation, please raise a new case online and reference the title of this article. Please include the UserID in the case.