cds-snc / cds-snc/platform-forms-client
Explore how we might implement team structures and privileges
Open
Epic
- Dominant language
- TypeScript
- Stars
- 46
- Forks
- 16
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 91
Description
# Team management
## Context
Service owners, program administrators, form builders, and developers can create a team structure and privileges that make sense for the following flows:
- [ ] Sharing a form for testing and feedback
- [ ] Generating and using an API key
- [ ] Publishing forms
- [ ] Adding and managing team members
Contributor guide
Research direction
No files, tests, or entry points are identified in the issue. Start by mapping the four listed flows—form sharing, API keys, publishing, and team-member management—and define the team structure, privileges, and completion criteria for each before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- next.js, typescript
- Domain
- authorization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100