User Permissions
The User Permissions page is used by Super Admin users to control what each user can do inside JPCRM.
This page is still marked as in development, so it may currently use mock data. However, it shows the structure for how permissions will be managed.
What this page is for
Section titled “What this page is for”User permissions help admins decide which parts of the system a user can access.
Permissions are managed by:
- Selecting a user
- Viewing the modules available in JPCRM
- Choosing what actions the user can perform in each module
- Saving or resetting the permission setup
This helps keep access controlled and prevents users from changing or viewing areas they should not use.
User selector
Section titled “User selector”At the top of the page, there is a User dropdown.
Use this dropdown to choose the person whose permissions you want to review or update.
Once a user is selected, JMS shows the selected user on the right side of the permissions panel.
For example:
Selected: John Doe
This confirms whose permissions you are currently working on.
Permission table
Section titled “Permission table”The main section contains a permissions table.
Each row represents a module in JPCRM, such as:
- Dashboard
- Contacts
- Businesses
- Notice Board
- Documents
- Channels
Each module has permission options across the row.
Permission actions
Section titled “Permission actions”The table uses four main permission types:
Create
Section titled “Create”Allows the user to create new records in that module.
For example, if Create is enabled for Contacts, the user may be able to add new contacts.
Allows the user to view records in that module.
For example, if Read is enabled for Dashboard, the user can open and view dashboard information.
Update
Section titled “Update”Allows the user to edit or change existing records.
For example, if Update is enabled for Businesses, the user may be able to change business details.
Delete
Section titled “Delete”Allows the user to delete records.
This permission should be used carefully because it gives the user the ability to remove information from the system.
All and None buttons
Section titled “All and None buttons”Each permission column has quick action buttons:
- All: Selects that permission for all visible modules.
- None: Clears that permission from all visible modules.
These buttons are useful when setting up permissions quickly.
For example, an admin may click All under Read if a user should be able to view all modules, then only enable Create or Update where needed.
Row permission button
Section titled “Row permission button”Each module row also has an All button on the far right.
This allows the admin to quickly enable permissions for that specific module row instead of changing each checkbox one by one.
Checkboxes
Section titled “Checkboxes”The checkboxes show whether a permission is enabled or disabled.
- A selected checkbox means the user has that permission.
- An empty checkbox means the user does not have that permission.
Admins can toggle these checkboxes based on what the user needs to do in their role.
Reset button
Section titled “Reset button”The Reset button clears or reverts changes before they are saved.
Use this if you made changes but want to return to the previous permission setup.
Save button
Section titled “Save button”The Save button stores the permission changes.
In the current screen, the button is labelled Save (Mock) because the page is still in development.
Once fully implemented, this button will save the selected permissions for the chosen user.
When to use this page
Section titled “When to use this page”Use the User Permissions page when you need to:
- Review what a user can access
- Give a user permission to view or manage a module
- Remove access from a user
- Control who can create, edit, or delete records
- Set up permissions for a new user
- Check access before giving someone a new role
Important note
Section titled “Important note”Only give users the permissions they need to do their work.
For most users, Read access may be enough. Permissions like Create, Update, and especially Delete should only be given when the user is trusted to manage that information correctly.