Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify the display of an admin user permissions #5658

Merged
merged 3 commits into from
Feb 25, 2021
Merged

Clarify the display of an admin user permissions #5658

merged 3 commits into from
Feb 25, 2021

Conversation

brianteeman
Copy link
Contributor

What's this PR do?

The display of an admin user settings is confusing as it says you have no permissions. This PR changes that by changing the conditional check to include displaying Yes for each permission if the user is an admin. Users who are not admin are not impacted. This is purely a visual change so is completely backwards compatible

Screenshots (if appropriate)

image

image

What Issues does it Close?

Closes #5657

What are the relevant tickets?

Any background context you want to provide?

After user testing the users wondered why it said they had no permission to do anything and then went looking to see how to add the permission.

Where should the reviewer start?

How should this be manually tested?

How should the automated tests treat this?

Questions:

  • Is there a related website / article to substantiate / explain this change?

    • Yes - Link:
    • No
  • Does the development wiki need an update?

    • Yes - Link:
    • No
  • Does the user documentation wiki need an update?

    • Yes - Link:
    • No
  • Does this add new dependencies?

    • Yes
    • No
  • Does this need to add new data to the demo database

    • Yes
    • No

@MrClever MrClever changed the title Correct the display of an admin user permissions Clarify the display of an admin user permissions Feb 25, 2021
Copy link
Collaborator

@MrClever MrClever left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clarity is a good thing, and I'm happy to merge this.

I tweaked the wording of the PR though ;) I don't think the original behaviour was "incorrect" as an "Admin" has all permissions by default, so all permissions are implied to be "yes", which meant all other explicit permissions are ignored for admin users (hence why they display "no" because they don't get set). However, for people unfamiliar with the security model in use (which is different from the more common "role-based" model) the original behaviour could be a source of confusion.

@DawoudIO DawoudIO merged commit 8ff5ca3 into ChurchCRM:master Feb 25, 2021
@brianteeman
Copy link
Contributor Author

Thank you

@brianteeman brianteeman deleted the patch-3 branch February 25, 2021 08:44
@DawoudIO DawoudIO added this to the 4.3.2 milestone Mar 1, 2021
@DawoudIO DawoudIO added the UI label Mar 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

admin user permissions
3 participants