-
Notifications
You must be signed in to change notification settings - Fork 18
Organizations
Organizations are how Caseflow groups members of various BVA (and beyond!) teams. Since members of the same team have similar responsibilities and levels of access, we are able to use organization membership as a form of access control. And since an appeal must visit multiple teams at the Board before being dispatched, we are able to use organizations to address members of those Board teams without the application code having to know explicitly who those individual members are.
- Visit
/organizations/{TEAM URL}/users
(or click the "{TEAM NAME} team management" link the dropdown that appears after you click your CSS ID in the top-right of each page).- You must be an admin of the selected organization or have the "System Admin" Caseflow function granted in order to visit this page.
- Search for the person you would like to add to the team in the "Select user to add" dropdown bar and click their name.
- The you would like to add to the team must have already logged in to Caseflow in order to be selectable in this list.
- Their name should appear as an item in the list of names below the "{TEAM NAME} team" heading.
- Visit
/team_management
(or click the "Caseflow team management" link the dropdown that appears after you click your CSS ID in the top-right of each page).- You must be a member of the
Bva
organization in Caseflow in order to visit this page.
- You must be a member of the
- Click the "+ Add Judge Team" button beside the "Judge teams" heading. A modal will appear.
- Search for the name of the judge you would like to create the judge team for, click on their name, and click "Submit".
- Their name should appear as a row at the bottom of the list of "Judge teams".
In order to create an organization that maps directly to a specific Board team and can be addressed in the application code by calling MyNewTeam.singleton
, you will need to create a new class for that team in the models/organizations/ directory following the pattern laid out by other organizations there.
- AodTeam
- BusinessLine
- Bva
- BvaDispatch
- BvaIntake
- Colocated
- FieldVso
- HearingAdmin
- HearingsManagement
- JudgeTeam
- LitigationSupport
- MailTeam
- PrivacyTeam
- PrivateBar
- PulacCerullo
- QualityReview
- SpecialCaseMovementTeam
- TranscriptionTeam
- Translation
- Vso
(list created by running Organization.all.pluck(:type).uniq.sort
)
- Home
- Acronyms and Glossary
- Caseflow products
- Caseflow Intake
- Caseflow Queue
- Appeals Consumer
- Caseflow Reader
- Caseflow eFolder
- Caseflow Hearings
- Caseflow Certification
- Caseflow APIs
- Appeal Status API
- Caseflow Dispatch
-
CSUM Roles
- System Admin
- VHA Team Management
- Active Record Queries Resource
- External Integrations
- Caseflow Demo
- Caseflow ProdTest
- Background
- Stuck Jobs
- VA Notify
- Caseflow-Team
- Frontend Best Practices
- Accessibility
- How-To
- Debugging Tips
- Adding a Feature Flag with FeatureToggle
- Editing AMA issues
- Editing a decision review
- Fixing task trees
- Investigating and diagnosing issues
- Data and Metric Request Workflow
- Exporting and Importing Appeals
- Explain page for Appeals
- Record associations and Foreign Keys
- Upgrading Ruby
- Stuck Appeals
- Testing Action Mailer Messages Locally
- Re-running Seed Files
- Rake Generator for Legacy Appeals
- Manually running Scheduled Jobs
- System Admin UI
- Caseflow Makefile
- Upgrading Postgresql from v11.7 to v14.8 Locally
- VACOLS VM Trigger Fix M1
- Using SlackService to Send a Job Alert
- Technical Talks