Creating New Staff Accounts

• Article Type: General
• Product: Aleph
• Product Version: 16.02

Description:
When I try to add permissions for the ALEPH library (when creating a new staff account from the circ module) I get the message: "The library code you have entered is incorrect or not allowed for you."
As I was able to do this in v14, I am anticipating that I should be able to create an account and assign privileges for a user in the ALEPH library.
I see the ALEPH library listed with all of the other libraries (usm01, usm50, etc.) so why is it even listed if I cannot assign permissions to it?
The default users accounts that came with the v14 (e.g. yohanan/yohanan) also have permissions assigned in the ALEPH library. In v.16 the default accounts Master and ALEPH accounts have ALEPH listed as permitted libraries with privileges.
What else needs to be done to allow a user account to be added with privs to ALEPH?"
We were told that there are no privileges that should be added to the ALEPH entity, that appears at the top of the Permitted libraries, and that if we wanted to test, we can add the ALEPH to library_relation, the PAS section.
However, we would like to know WHY ALEPH appears when opening a User Permissions, and if we should add any permissions there.

Resolution:
The ALEPH in the password authorizations are needed if you want to be able to update the alephe tables via alephadm. In order to be able to do this, the operator must be an ADMIN OR ALEPH needs to be defined in the PAS line.