Describe the bug in current situation
When an account user (not coordinator, or admin - specific to user role 'user') is on the entity dashboard for a company if there is a pending request from another account to manage that business they will see the request and ability to action it in the 'To Do' list. However, a user cannot actually approve these requests. Currently if the user tries to take action they get a generic error.
Link bug to the User Story
Impact of this bug
Users cannot complete their desired task and are unsure why.
Chance of Occurring (high/medium/low/very low)
High
Pre Conditions: which Env, any pre-requesites or assumptions to execute steps?
Steps to Reproduce
Steps to reproduce the behavior:
- Client 1 goes to the business registry dashboard in test
- Client 1 locates a business through the lookup and chooses the button to 'Manage Business'
- Client 2 (with existing affiliation to the company) logs on to the entity dashboard for that company
- Client 2 account 'user' tries to accept the request to manage in the to-do list
- See error
Actual/ observed behavior/ results
Early adopters are confused on why the users cannot manage this work
Expected behavior
To be determined. Need to determine if there is any risk in allowing for users. If so, this would be an easy way to ensure affiliations can be managed. If this must be tackled by coordinator or admin only then we need to hide the option in the to-do list for users.
Screenshots/ Visual Reference/ Source

Root Cause Analysis (RCA) results
If applicable, document the root cause analysis results for the scenarios. This section is mandatory before the issue can be closed
Describe the bug in current situation
When an account user (not coordinator, or admin - specific to user role 'user') is on the entity dashboard for a company if there is a pending request from another account to manage that business they will see the request and ability to action it in the 'To Do' list. However, a user cannot actually approve these requests. Currently if the user tries to take action they get a generic error.
Link bug to the User Story
Impact of this bug
Users cannot complete their desired task and are unsure why.
Chance of Occurring (high/medium/low/very low)
High
Pre Conditions: which Env, any pre-requesites or assumptions to execute steps?
Steps to Reproduce
Steps to reproduce the behavior:
Actual/ observed behavior/ results
Early adopters are confused on why the users cannot manage this work
Expected behavior
To be determined. Need to determine if there is any risk in allowing for users. If so, this would be an easy way to ensure affiliations can be managed. If this must be tackled by coordinator or admin only then we need to hide the option in the to-do list for users.
Screenshots/ Visual Reference/ Source

Root Cause Analysis (RCA) results
If applicable, document the root cause analysis results for the scenarios. This section is mandatory before the issue can be closed