chore(release): 2026-02-10 "February A" #1584
Conversation
<!--- Please provide a general summary of your changes in the title above --> # Pull Request type <!-- Please try to limit your pull request to one type; submit multiple pull requests if needed. --> Please check the type of change your PR introduces: - [ ] Bugfix - [ ] Feature - [ ] Code style update (formatting, renaming) - [ ] Refactoring (no functional changes, no API changes) - [ ] Build-related changes - [ ] Documentation content changes - [ ] Other (please describe): ## What is the current behavior? <!-- Please describe the current behavior that you are modifying, or link to a relevant issue. --> Issue Number: N/A ## What is the new behavior? <!-- Please describe the behavior or changes that are being added by this PR. --> - - - ## Does this introduce a breaking change? - [ ] Yes - [ ] No <!-- If this does introduce a breaking change, please describe the impact and migration path for existing applications below. --> ## Other information <!-- Any other information that is important to this PR, such as screenshots of how the component looks before and after the change. -->
Signed-off-by: trigal <10123216+trigal2012@users.noreply.github.com>
Signed-off-by: trigal <10123216+trigal2012@users.noreply.github.com>
Automated changes by [create-pull-request](https://github.com/peter-evans/create-pull-request) GitHub action
…1580) <!--- Please provide a general summary of your changes in the title above --> # Pull Request type <!-- Please try to limit your pull request to one type; submit multiple pull requests if needed. --> Please check the type of change your PR introduces: - [x] Bugfix - [x] Feature - [ ] Code style update (formatting, renaming) - [ ] Refactoring (no functional changes, no API changes) - [ ] Build-related changes - [ ] Documentation content changes - [ ] Other (please describe): ## What is the current behavior? <!-- Please describe the current behavior that you are modifying, or link to a relevant issue. --> Issue Number: N/A ## What is the new behavior? <!-- Please describe the behavior or changes that are being added by this PR. --> Implemented Cascading Hierarchy for Data Portal Access Added markdown to document current and future intentions of the Roles root dataPortalAdmin dataPortalManager dataPortalBasic ## 3. Permission Matrix | Capability | Basic | Manager | Admin | Root | | :------------------------- | :---: | :-----: | :---: | :--: | | Edit All Org/Location Data | ✅ | ✅ | ✅ | ✅ | | View User List | ❌ | ✅ | ✅ | ✅ | | Assign Basic/Manager Roles | ❌ | ✅ | ✅ | ✅ | | Assign Admin Roles | ❌ | ❌ | ✅ | ✅ | | Assign Root Roles | ❌ | ❌ | ❌ | ✅ | --- - - ## Does this introduce a breaking change? - [ ] Yes - [x] No no breaking changes but volunteer permissions should be updated manually once this is deployed <!-- If this does introduce a breaking change, please describe the impact and migration path for existing applications below. --> ## Other information these accounts can be used for testing on the preview url | User ID | Username | Email | Permission ID | Role | Password | | :--- | :--- | :--- | :--- | :--- | :--- | | `user_01KGKJ4W7S3RCY4A01092FSBQX` | rootTest | `diana+preview-root@inreach.org` | `perm_01GW2HKXRTRWKY87HNTTFZCBH1` | **root** | | | `user_01KGKJYTXV9FY4CKES7N76YZT0` | adminTest | `diana+preview-admin@inreach.org` | `perm_01H0QX1XC0335R04JMGMQ3KXVN` | **dataPortalAdmin** | | | `user_01KGKK0M53H7AB5027D3X62G4V` | managerTest | `diana+preview-manager@inreach.org` | `perm_01H0QX1XC04Z9G8H44G464YHQQ` | **dataPortalManager** | | | `user_01KGKK20EG14BMYN186NK2FV4V` | basicTest | `diana+preview-basic@inreach.org` | `perm_01H0QX1XC037A47900JPAX6JBP` | **dataPortalBasic** | |
<!--- Please provide a general summary of your changes in the title above --> # Pull Request type <!-- Please try to limit your pull request to one type; submit multiple pull requests if needed. --> Please check the type of change your PR introduces: - [ ] Bugfix - [ ] Feature - [ ] Code style update (formatting, renaming) - [ ] Refactoring (no functional changes, no API changes) - [ ] Build-related changes - [ ] Documentation content changes - [ ] Other (please describe): ## What is the current behavior? <!-- Please describe the current behavior that you are modifying, or link to a relevant issue. --> Issue Number: N/A ## What is the new behavior? <!-- Please describe the behavior or changes that are being added by this PR. --> - - - ## Does this introduce a breaking change? - [ ] Yes - [ ] No <!-- If this does introduce a breaking change, please describe the impact and migration path for existing applications below. --> ## Other information <!-- Any other information that is important to this PR, such as screenshots of how the component looks before and after the change. -->
…remote (#1582) <!--- Please provide a general summary of your changes in the title above --> # Pull Request type <!-- Please try to limit your pull request to one type; submit multiple pull requests if needed. --> Please check the type of change your PR introduces: - [ ] Bugfix - [ ] Feature - [ ] Code style update (formatting, renaming) - [ ] Refactoring (no functional changes, no API changes) - [ ] Build-related changes - [ ] Documentation content changes - [ ] Other (please describe): ## What is the current behavior? <!-- Please describe the current behavior that you are modifying, or link to a relevant issue. --> Issue Number: N/A ## What is the new behavior? <!-- Please describe the behavior or changes that are being added by this PR. --> - - - ## Does this introduce a breaking change? - [ ] Yes - [ ] No <!-- If this does introduce a breaking change, please describe the impact and migration path for existing applications below. --> ## Other information <!-- Any other information that is important to this PR, such as screenshots of how the component looks before and after the change. -->
<!--- Please provide a general summary of your changes in the title above --> # Pull Request type <!-- Please try to limit your pull request to one type; submit multiple pull requests if needed. --> Please check the type of change your PR introduces: - [ ] Bugfix - [ ] Feature - [ ] Code style update (formatting, renaming) - [ ] Refactoring (no functional changes, no API changes) - [ ] Build-related changes - [ ] Documentation content changes - [ ] Other (please describe): ## What is the current behavior? <!-- Please describe the current behavior that you are modifying, or link to a relevant issue. --> Issue Number: N/A ## What is the new behavior? <!-- Please describe the behavior or changes that are being added by this PR. --> - - - ## Does this introduce a breaking change? - [ ] Yes - [ ] No <!-- If this does introduce a breaking change, please describe the impact and migration path for existing applications below. --> ## Other information <!-- Any other information that is important to this PR, such as screenshots of how the component looks before and after the change. -->
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (20)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing touches🧪 Generate unit tests (beta)
Tip Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|



Pull Request type
Please check the type of change your PR introduces:
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Does this introduce a breaking change?
Other information