User is Not Authorized for Usage Message

If a user receives a message that he/she is not authorized for usage after logging in, verify the following for the user receiving the message:

  • The v30 Access check box is checked on the Edit User screen.
  • The user has a theme selected on the Edit User screen.
  • The user is assigned to a role that has access.
  • The user is assigned to a user type (for SaaS licensed customers).
  • The personnel account for the user is linked to the user's User ID.
  • The personnel account for the user is assigned an email address.

Related articles

Comments

5 comments

Date Votes
  • Thomas Hohm (m:con-mannheim:congress GmbH)

    "The user is assigned to a role that has v20 access."  => which criteria does the role have to fulfill?

    0 upvotes

  • Kaitlyn Batliner

    Hi Thomas,

    v19 uses 'Menus' to control what a user has access to. v20 uses Roles to control what a user has access to. When you make the move from v19 to v20, these 'Menus' are moved into the Roles window in v20. They are moved over in a sense that they create the shell/header for the roles you are about to build out in v20. No features are assigned to these roles, so when the article above states that "the user needs to be assigned to a role that has v20 access", it means you need to go into the Roles window and complete building out the role.

    The role will need to have the appropriate users assigned, appropriate features assigned, potentially access exceptions as well. Article below advises you on how to assign features to roles. If you need assistance in building roles or access management in general, please feel free to reach out to one of our coordinators or consultants to put time on the calendar with you. Many times, moving to v20 decreases the amount of roles an organization has.

    https://supportcenter.ungerboeck.com/hc/en-us/articles/204553198-Assigning-Features-to-Roles

    Best,

    Kaitlyn Batliner

    Ungerboeck Consultant

     

    0 upvotes

  • Thomas Hohm (m:con-mannheim:congress GmbH)
    • Edited

    Hi Kaitlyn,

    thanks a lot. That's all well known on our side.

    We had a role where already a lot of users are assigned to and they all can log in. I created a new user, assigned it only to this existing role, set all the described user settings and still got the "User is Not Authorized for v20" message. 

    I could not see a reason why and searched in the support center. I found this description and could answer all bullet points with "yes". 

    In order to get deeper into the described requirements I was looking for an answer if there is a specific setting the role must have in order to set the authorization.

    Thanks,

    Thomas

     

    0 upvotes

  • Kaitlyn Batliner

    Hi Thomas,

    Thank you for the additional information. That helps narrow down the issue. Please check and see if the user is checked for remote access.

    Kaitlyn Batliner

    Ungerboeck Consultant

    0 upvotes

  • Thomas Hohm (m:con-mannheim:congress GmbH)
    • Edited

    Hi Kaitlyn,

    Thank you.

    The user is not disabled, has an email address, has a portal, has a layout theme, ...

    ... has remote access allowed, has access level internal, has exactly 1 role assigned and one personnel account assigned.

    During all this checking forwards and backwards, there is one thing that made this user login work: change access level to administrator, try to login (login works!) and change the level back to internal (login still works). 

    I have no idea what happened behind the scenes and I do not have another case with this problem.

    1 upvotes

Please sign in to leave a comment.