-
Notifications
You must be signed in to change notification settings - Fork 1
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
Public solver role access #23
Comments
How does a public solver have the role assigned? Shouldn't any user of the system have access to be a public solver? |
@stepchud Currently, if you do not have .gov or .mil email account, your role is set to public solver by default. But if you do have a .gov or .mil email account, your role is set to challenge manager, and you would have to request your role to be changed to public solver if you want to solve challenges (to avoid conflict of interest). |
I found a small cross browser issue for PC/Edge and PC/Chrome in the login process and will update the correct card. |
@r-bartlett-gsa all checks complete prior to move to "production" column. |
User Story
As a user with a public solver role, in order to submit my solution to a challenge, I would like to be able to access appropriate sections of the site upon login.
Acceptance criteria:
If any other user who does not have a public solver's role assigned to them tries to access public solver role specific features, they are redirected to their /dashboard (based on their assigned role) and an error message is displayed: "You do not have access to this section of Challenge.gov."Development tasks:
Definition of Done
Doing (dev team)
PR that changes or adds UIinclude a screenshot of the WAVE report for the altered pagesConfirm changes were validated for mobile responsivenessStaging
Accessibility tested (Marni)Keyboard navigationFocus confirmedColor contrast complianceScreen reader testingDeploy to production (production-like environment for eval capability) (dev team)Production
The text was updated successfully, but these errors were encountered: