Notebook users might sometimes experience issues with access to the application and one known occurrence is if a user who worked for an organization leaves after sometime and then returns to the same organization after a period of absence. One of the main reasons for this access issue could be a mismatch in the user's GUID between Notebook and the directory from where the user's credentials were imported.

Notebook 2025 Administration Guide says the following in Chapter 5, AD Integration:

"Users and Groups can be imported from an Active Directory (AD). The Windows service ElnDirectorySyncService handles reading configured base groups and all their sub-groups and member users from the AD, and creating and updating Notebook users and groups."

Although this sync is expected to work OK most of the time, the GUID mismatch between Notebook and Active Directory might still persist for some reasons not known from a user's Notebook setup. If other attempts at matching the GUID fails, the Notebook Administrator can check the GUID for the user in “user_details”  table in the Notebook database and confirm that it is different from the GUID on the Active Directory. Then update this table and set the GUID correctly so that it matches exactly with the GUID in Active Directory. After the update, do a commit and make sure the change is successful by rechecking the same database table for the user's GUID. Then ask the user to try access to Notebook again. This update is expected to resolve the access problem for the user.