App Roles Help

Use this page to view and manage application role permission overrides for a selected business and application. Changes are immediate and affect what members of each role can do the next time they sign in.

What this page does

• Lets an authorized administrator select a business (DropDownListBusinesses) and an application (UserApps).
• Loads role panels (Admin, Standard, Basic, Custom) showing permission sections and individual permissions.
• Toggle permission checkboxes to grant or revoke that specific permission for the selected role.
• Sends changes to the server immediately via an AJAX call to UpdatePermissionOverride.
• Shows brief feedback with the toast notification (showUpdateToast) and surfaces errors in the top ErrorPanel.

Quick start — common tasks

1. Select your business from the Select Business dropdown (DropDownListBusinesses).
2. Select the app from the App dropdown (UserApps).

• If no app is selected, the permission panels stay hidden.

1. Role panels appear in the permission area (divPermissnos) — look for the boxes rendered into:

• litAdmin
• litStandard
• litBasic
• litCustom1
• litCustom2

1. To change a permission: check or uncheck the permission checkbox.

• The page sends the change immediately (no Save button).
• A toast appears with a success message; on failure the toast or ErrorPanel shows an error.

What each control means

• DropDownListBusinesses — selects which business/organisation you are managing.
• UserApps — selects which application’s role permissions you are editing.
• litAdmin, litStandard, litBasic, litCustom1, litCustom2 — HTML containers where each role’s permission tree is displayed.
• Permission checkboxes have class perm-checkbox and attributes like data-permissionid you can toggle to change that permission.
• ErrorPanel with LabelErrorMessage — shows validation or server error messages; dismiss with the × button.

How changes are applied

• Toggling a checkbox triggers a JavaScript fetch POST to AppRoles.aspx/UpdatePermissionOverride with:
• permissionId
• isGranted (true/false)
• pageToken (client token to help detect stale requests)
• The server responds with a short message. The page shows that message in a toast for ~1.5s.
• Changes are persisted immediately in the database and will take effect for users when they next sign in (or when permission caching is refreshed).

User roles and permission overrides (conceptual)

• Admin / Standard / Basic: typical role tiers with different default permissions.
• Custom panels allow per-business custom roles or additional overrides.
• Checking a permission in a role overrides the app’s default permission for users in that role.

Messages you may see

• Success toast (green): confirmation like “Updated” or a custom message from the server.
• ErrorPanel (red): shown when there’s a problem (session expired, load failure, server error). Click the × to dismiss.
• If the page can’t find session/business/app data the ErrorPanel will explain next steps (e.g., re-sign in or select a business).

Troubleshooting

Panels not visible after selecting app

• Ensure you actually selected an app in UserApps (AutoPostBack triggers server to load content).
• Check for JavaScript errors in the browser console.

Checkbox change does not persist

• Check network tab — the POST to UpdatePermissionOverride should return JSON; if it returns an error, inspect the response.
• Session expiry can block updates — try signing in again.

Toast never appears but checkbox updated on backend

• Possible client JS error. Try a browser refresh; check console.

Concurrent edits

• The page uses a per-page pageToken to reduce race conditions, but rapid multi-user edits can still create conflicts; coordinate large role changes.

Security & access

• Only users with appropriate administrator privileges should access this page.

If you see permission editing but shouldn’t have it, notify your system administrator.

• Changes made here affect many users. Review impact before toggling widely used permissions.
• There is no explicit “undo” button in the UI — keep a record of changes or coordinate with the team.

If needed, request support to revert DB changes.

Best practices

• Make changes during low-usage hours where possible.
• Test permission changes with a test account to confirm behavior before applying to production roles.
• Use the Custom role panels (litCustom1, litCustom2) for special-case overrides rather than changing Admin/Standard broadly.
• Keep a change log (who changed what, when) outside the UI if your organization requires auditing.

Accessibility & keyboard use

• Permission checkboxes are standard inputs — use Tab to navigate and Space/Enter to toggle.
• Toasts and ErrorPanel messages use polite notifications; screen-reader users should be able to hear brief feedback.

If something still fails

Collect these items before contacting support:

• Business and App names selected
• Permission id (if shown) or name of the permission you toggled
• Time you made the change
• Screenshot of the ErrorPanel or browser console errors and the network request/response from browser devtools

Provide details to your admin/dev team so they can inspect the server logs and database.