To understand how they work, it's helpful to think of access management at two levels:
Account access level: credentials used to log in to WuBook.
System operation level: users who define which people can use each module and with what permissions.
Understanding this difference is key to managing access correctly and also to identifying the cause of most login problems.
1. Account access level
This level defines which credentials allow access to the WuBook account. There are two types:
Account Code
The Account Code is the primary identifier for the account in WuBook. It consists of two letters and three or four numbers (for example: AB1234) and cannot be modified. It is the code that is automatically assigned when the account is created and is associated with the account holder or owner. It is used to log in to the system; in practice, it represents the primary access to the account.
Sub-accounts
Sub-accounts allow you to create additional access for other people, maintaining separate security credentials. They are created from Wubook Account (New) > Account Management and follow this format:
AccountCode-CustomName
Example: AA1234-RESERVATIONS
↳ Direct link: Login Wubook
2. System Operation Level (Optional, but Recommended)
This function is located in WuBook Account and allows you to create users to access and interact with all sections of WuBook: WuBook Account, WooDoo, and ZaK.
This is the specific tool for managing ZaK users. In practice, it's the same set of users created in Users and Groups, but it only displays those who have permission to use the PMS.
Common login problems
1. You are using the wrong user type
The message displayed on the screen will be “Authentication Error.”
Before attempting to recover your password, it is important to verify that you are using the correct user type:
Account Code or Sub-Account to log in to WuBook.
Personal User (Users and Groups / ZaK Team) when the account is already open and you are requesting access to a specific section.
Attempting to log in with a second-level user (for example, “Ana”) from the main login screen will cause this error (and vice versa).
2. The username and level are correct, but the password is incorrect
In this case, the system will display the same message: “Authentication Error.”
The solution will depend on the type of access:
If it's an account login (Account Code or Sub-account), you can recover the password by following the identity verification process.
If it's an internal user (Users and Groups / ZaK Team), you'll need to contact the account administrator to set a new password.
3. The credentials are correct, but the user doesn't have permission to access the section
In this case, an error message won't necessarily appear. The system will simply request the credentials again and won't allow access to the requested section. When this happens, the account administrator should review the user's assigned permissions and enable access, if necessary.