feat: further restrict permissions to view and access reports #112
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds the ability to restrict reports to those with specific access permissions. To access/list any reports, a user must have at minimum the
[reports] managepermission. But to view a report, the user must have the report specific permission. For example, the member status report requires access to the[reports] userspermission. The member activity report requires access to the[reports] gatekeeperpermission.Please note that these permissions will not be set by default. This will require a user with a BoD role or above to set permissions appropriate to the defined roles. Please expect to set the bookkeeper role with at least
[reports] manageand [reports] users`.Superuser role:

Bookkeeper role:

Unpermissioned role:

