Skip to main content
Version: 26.0.32

Admin

Admins prepare the organization foundation for Libcodesk. This section covers the settings that should normally be controlled by organization owners or trusted administrators: appearance, organization identity, libraries, staff roles, staff accounts, and license/activation status.

Shared library operations such as Members, Member Types, and Membership Plans are documented under Member Management because staff can use those modules when their role allows it.

  1. Review License And Activation so the organization is valid and ready.
  2. Choose a header Theme for a comfortable training and support environment.
  3. Complete Organization Settings, especially country, date format, time format, currency, and organization type.
  4. Review Library Manager and confirm the Main Library plus any branches.
  5. Create Staff Roles with only the permissions each job needs.
  6. Create Staff Accounts, assign roles, and assign library access.
  7. Move to Member Management for plans, member types, and members.
Screenshot To Add

Add an admin dashboard or Settings menu screenshot showing Organization, Library Manager, Staff Roles, Staff Accounts, plus the About menu containing Software Information, Software Update, and License.

Do And Don'ts​

Do
  • Configure organization settings, libraries, roles, and staff before large member work.
  • Give staff only the permissions they need for their job.
  • Review audit history when important records change.
  • Keep admin-only setup separate from day-to-day member work.
Don't
  • Don't share the admin account with staff.
  • Don't delete configuration records without checking related workflows.
  • Don't skip testing imports with a small file before importing large data.
  • Don't place member workflows under Admin when staff may also perform them by permission.

FAQ​

What belongs in Admin?

Admin covers organization-level setup: appearance, organization settings, libraries, staff roles, staff accounts, and license/activation review.

Why are Members, Member Types, and Membership Plans not under Admin?

Those modules are shared operational workflows. Admins can configure them, but librarians may also use them when their role includes the required permissions.

Should every staff member receive admin access?

No. Create Staff Roles for job responsibilities and assign only the menus and actions needed for that staff member.

What should I configure before adding members?

Set organization date/currency, confirm libraries, create membership plans, create member types, and then add or import members.

Where should staff go if they cannot access a menu?

Staff should contact the organization admin. The admin should review the staff role and permissions before escalating any cloud or license issue.

Does Local setup use the same admin workflow?

Yes where the feature exists. The Standalone app follows the same workflow shape, but Local setup keeps daily work on the selected Standalone app device instead of Cloud setup.

Why do admin changes keep audit history?

Admin changes affect access, identity, branches, and licensing. Audit history helps the organization inspect who changed what and when.

Can I use one shared admin login for everyone?

No. Each person should have their own account so permissions, audit history, and support logs remain clear.

Operational lists use the available window width in Libcodesk WebApp and the Standalone app, in both Cloud setup and Local setup where supported. Collections, members, staff and library lists keep their normal page margins while wider windows provide more room for table columns and actions. Reports, circulation, accounts and other working lists follow the same layout principle. On narrow screens, scroll a wide table horizontally to reach its columns and row menu. Forms, settings dialogs and document editors keep a focused width for readability; widening a window does not change the number of records loaded.