Permission Errors
If you see a message such as You don't have access to Members, your staff role does not include that permission.
Ask your organization admin to review your staff role and menu permissions.
What The Admin Should Check
- Open Settings > Staff Accounts and confirm the staff account is active.
- Check the staff account's assigned role.
- Open Settings > Staff Roles.
- Confirm the role is active.
- Confirm both menu/view permission and action permission are enabled for the workflow.
- Confirm the staff account has library access where the feature depends on library assignment.
For example, a user may see Members but still not see Import Members if the role has member view permission but not member import permission.
Common Permission Cases
| What The Staff Sees | Likely Cause | Fix |
|---|---|---|
| Menu is missing | Menu/view permission is disabled. | Add the menu permission to the role. |
| Page says no access | Direct route was opened without view permission. | Add view permission or keep the route blocked. |
| Button is hidden | Action permission is disabled. | Add only the action permission the job needs. |
| Save is disabled | No dirty change or validation is missing. | Edit a real value and complete required fields. |
| Library data is missing | Staff has no assigned library access. | Assign libraries from Staff Accounts. |
Do And Don'ts
- Ask the organization admin to review role permissions when menus are missing.
- Check both menu/view permissions and action permissions.
- Use inactive roles to pause staff access when appropriate.
- Don't contact CodeAchi support for normal staff permission changes.
- Don't give broad admin permissions just to fix one missing button.
- Don't forget direct URL access can still be blocked even if a menu is hidden.
FAQ
Who should read this page?
Admins and staff should read this page when they need to understand or complete the Permission Errors workflow in Libcodesk.
Does this work in both Libcodesk WebApp and Standalone app?
When a workflow differs between Libcodesk WebApp and the Standalone app, the guide points out the setup-specific step so staff can follow the right path.
Does local setup use the same steps?
Local setup follows the same user workflow where the feature exists, but the work stays on the Standalone app device instead of Cloud setup.
What permission do I need?
If you cannot see the menu or action, your staff role probably does not include the required permission. Ask your organization admin to review your role.
Why is the Save button disabled?
Save and update buttons stay disabled until Libcodesk detects a real change. This prevents accidental writes, unnecessary logs, and duplicate requests.
How do I fix validation errors?
Read the message beside the active button or inside the modal. Required fields, duplicate values, invalid dates, and permission issues must be corrected before saving.
Can I use imports instead of manual entry?
Where import is available, it is recommended for larger datasets. Always validate the file first and review row-level errors before importing.
Where should staff or members ask for help?
Staff should contact their organization admin. Members should contact their library. Organization admins may contact CodeAchi for license, billing, or cloud access issues.