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

[Spike] Assess DRY Permissions library for committee access #1252

Open
exalate-issue-sync bot opened this issue Dec 11, 2024 · 0 comments
Open

[Spike] Assess DRY Permissions library for committee access #1252

exalate-issue-sync bot opened this issue Dec 11, 2024 · 0 comments

Comments

@exalate-issue-sync
Copy link

From row 10 https://docs.google.com/spreadsheets/d/1BMpVJ9z8-nSyUHvH6SXJlJfRehZyd8PQM_8a0WrpA9I/edit?gid=0#gid=0

Determine if DRY Permissions implements it’s permission controls during retrieval from the database. If not, we will still need to implement access controls another way.

If it does determine a design to:

utilize the schemas to control access

  • set up the library with existing models (reports, transactions, contacts, etc…)
  • migrate existing data
  • create a followup ticket to implement

If it does not, no followup

QA Notes

null

DEV Notes

null

Design

null

See full ticket and images here: FECFILE-1889

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

0 participants