give NGO users the full opportunity view - #950
Open
ivannissimrch wants to merge 4 commits into
Open
Conversation
Contributor
|
@ivannissimrch to make it simple now - anyone from the same NGO/agent can see the oppotunities there of that NGO/agent |
4 tasks
Collaborator
Author
|
Thanks, scoping by agent then. I created a PR on be, 916 it limits the list to the caller's own agent. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
NGO users get the same opportunity view as coordinators: the list tab, full table columns, clickable rows and cards, and the schedule filter. Previously, they got a read-only version with fewer columns and nothing clickable.
Needs the backend scoping first, so the list only contains their own opportunities. I'll open the backend issue shortly.
Quick clarification before I open the be issue.
The one thing I want to confirm: does "their own domain" mean every shelter under that domain, or just the shelter the user belongs to? The issue says "their own operator their email domain" but then "for their own shelter", and those give different lists if a domain has more than one shelter.
Changes
useAuthreturnsisAgent;isOwnProfileisAuthorized || isAgentinstead ofisAuthorizedisAuthorizeditself is unchanged, so the other places that use it keep their current meaningRelated Issues
Closes #934
Screenshots / Demos
Checklist