> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://support.robaws.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Problems logging in

Is logging in not working? The cause is almost always in the login details themselves or in a setting on the user profile. Go through the four points below. You can read how logging in normally works in [Logging in to Robaws](https://support.robaws.com/en/article/logging-in-to-robaws-rhr6wg/).

## The username or password is not correct

You log in with your username (your e-mail address or ID) and your password. Both have to be exactly right, otherwise you get the message **'Invalid login or password'**.

||| The username is case sensitive. Also watch out for a space that you copy along by accident — that is the most common cause.

Have you lost your password? Then click on 'forgot password' on the login page or [change your password](https://support.robaws.com/en/article/changing-your-password-1ripat0/).

|| If you were invited via your Google or Microsoft account, no password has been created. In that case, log in via the Google or Microsoft button on the login page.

## The user has no user role

Every user has to be linked to a user role. That role determines which permissions the user has and which modules he or she gets access to. Without a role the user cannot log in.

You link the role on the user profile in the field **userrole**. You can read how to build up roles in [Setting up the permissions of your users](https://support.robaws.com/en/article/setting-up-the-permissions-of-your-users-7wabst/).

## The user only has API access

If the setting **'API-only'** is switched on in the profile, that user is free of charge, but he or she can only address the API. Logging in to the Robaws platform is then refused.

If that person also has to work in Robaws itself, switch 'API-only' off and give the user access to Robaws. You can find more about API users in [Giving a user access to the API](https://support.robaws.com/en/article/giving-a-user-access-to-the-api-1uwkuga/).

## The user has no access to Robaws or Wappy

Access to Robaws and access to Wappy are set separately on the user profile, and each access is a separate licence. If the access for that environment is missing, the user gets the message **'You don't have access because your user doesn't have a license. Contact the administrator of your Robaws organization.'** when logging in.

In that case, switch on the correct access in the profile: Robaws for the platform, [Wappy](https://support.robaws.com/en/article/wappy-bmkzk0/) for the app. When you activate Wappy, you also choose the [Wappy plan](https://support.robaws.com/en/article/wappy-licences-c9uch7/) straight away. How to set up a profile completely is described in [Adding a new user](https://support.robaws.com/en/article/adding-a-new-user-frez0i/). If your question is specifically about the app, have a look at [Wappy | Logging in](https://support.robaws.com/en/article/wappy-logging-in-kyyncc/) as well.

## Still no access?

Do the points above not solve your problem? Then send us a message at support@robaws.com. Mention the username and the exact error message you see — then we can look straight away at what is going wrong.