entity icon indicating copy to clipboard operation
entity copied to clipboard

UI Design: Significant Individual table on Company Dashboard and Company Information page (Add a SI)

Open steveburtch opened this issue 2 years ago • 13 comments

User Story

As a legal professional or business owner I want to be able to initiate the process of adding a significant individual (SI) from the Company Information page, so that I can understand the basic functionality of the skeleton version.

As a legal professional or business owner I was to be able to open "View and Change Business Information" to view the Significant Individuals listed on a company.

Notes

  • The business dashboard page is the starting point for the 'skeleton' version of the Add Significant Individuals functionality
  • Currently the "View and Change Business Information" page does not allow you to initiate change of directors. We are modeling SI's the same way directors are modeled so will mock up to not allow change of SI's from the company information page. Question to flag for entities: Why are some elements able to be changed from View and Change and others are not allowed. Does it make more sense to also allow change of directors and SI's from the company information page?
  • Initial state is empty. A user is not required to input Significant Individuals at the time of incorporation so there may be cases where the table is empty
  • Within the table and company information page we can only show public information for SI's

Instructions

  1. Add a table to the company dashboard with a link to edit SI information
  2. Add a read only table to the company information page with a link to view SI information
  3. Create a view with full details for competent authorities

Figma

https://www.figma.com/design/4oi1IWHe0DmbY8EZk3Srs3/Add%2Fedit-SI?node-id=112-1979&t=VgwE7XRK2IXF2NPY-1

Archive Wireframes

https://www.figma.com/file/C2ThYIhZSO44dYBVGp8xAj/Register-Beneficial-Owners?type=design&node-id=3272%3A2&mode=design&t=FxM1Ayno2V8k1Kle-1 https://www.figma.com/file/4oi1IWHe0DmbY8EZk3Srs3/Add%2Fedit-SI?type=design&node-id=112%3A2063&mode=design&t=LBS0TwmXvV8UM4IQ-1

steveburtch avatar Nov 17 '23 16:11 steveburtch

Updated to change from showing Significant Individuals on the Company Information Page to simply providing an option for filing. @J-Baese can you please review the wireframe above and make any changes needed based upon not showing significant individuals names here?

mstanton1 avatar Feb 16 '24 19:02 mstanton1

@J-Baese as per today's design review I have updated this ticket to cover both the company dashboard and company information page. Thank you:)

mstanton1 avatar Mar 04 '24 19:03 mstanton1

Ok so a couple of different states here - Empty & filled. The empty state will look like this: image.png

Whereas the filled state will be like this: image.png

@mstanton1 I just realized that these names drop down to show the addresses in the director ones, should we do the same here? Or is the control more valuable? Thoughts?

J-Baese avatar Mar 05 '24 03:03 J-Baese

For the company information view we'll be looking at adding a table at the bottom that looks like this: image.png

@mstanton1 I figure having control listed here would be useful but not sure if that falls under the public info? We can adjust as needed.

J-Baese avatar Mar 05 '24 04:03 J-Baese

@J-Baese the access control matric stating which fields are public is available here: https://docs.google.com/spreadsheets/d/1zr3ud_RF89GAL7dFGVG69jmAN315ICZp/edit#gid=629614066

Avinash has noted that Full Legal Name, Preferred Name, Birth Year (not full date) and Citizenship or Permanent Residency are available to the public. Details about the company that a SI is linked to are also listed in the matrix but information about the company will already be included on that page.

mstanton1 avatar Mar 05 '24 16:03 mstanton1

^^ this, but looking good!

steveburtch avatar Mar 05 '24 17:03 steveburtch

@mstanton1 So here's where it gets tricky - is this view public or is this view the user who entered all the info in? If it's a casual public user who has only view access then I understand only showing the bare minimum. However it's the user who's expected to maintain these records and we are giving them edit access, they should be allowed to be able to see the control and the effective dates in order to makes sure they are editing the correct pieces of info. I don't see how hiding the info here for the person in charge of inputting the info is helpful from a user perspective.

Bottom line there should be no public users who have edit control over someone else's business, therefore there should be a different view for those in charge of editing their businesses information.

J-Baese avatar Mar 05 '24 18:03 J-Baese

@J-Baese this logic of only showing the public information aligns with the recent changes where we also only show public information on edit. If we should full data on the dashboard and company information page, it negates the value in protecting that data in the edit flow.

While a user must be logged on to the account to reach this page, our accounts are set up to allow widespread access and delegation. In most cases a Law Firm will create one account and all members of the law firm will have access. There are further delegation abilities so a law firm may then delegate access to another account to manage the business and all users on that account could then access the information. We are looking into reducing the amount of data collected, thus potentially reducing harm of sharing this data. However as the data elements are currently legislated we should proceed with the current plan that we won't show these, and we can continue with user research to identify any strong concerns.

mstanton1 avatar Mar 05 '24 18:03 mstanton1

@mstanton1 are Kaine, Sal, and Linda in the loop on this ^. Because the business is responsible for ensuring the information being submitted is accurate, I'm concerned this will mean that law firms (or other representative of the business) will re-enter all information about all SI's in every annual report filing - because they will feel that that will be the only way they can ensure the information is accurate in the filing. They would probably do it even if there were no known changes since they wouldn't know the information on file was accurate. This seems like it would be a lot of unnecessary work/expense.

forgeuxGH5 avatar Mar 05 '24 20:03 forgeuxGH5

@forgeuxGH5 we documented the approach and shared with Linda, Sal and Kaine. The expectation is we continue with user research and if that flags key concerns we will dig deeper into those.

Post MVP introduction of the profile may enable us to show more information. That will be the first piece we visit once the end to end MVP flow is in place. Similarly, I'm still engaging in discussions about use of SIN. If a lesser amount of data was collected, with less risk the approach may shift.

Note - I've been working to start building relationships with other Jurisdictions and LOTR so we can collaborate. In LOTR a different thought was had on not pre-populating all information. In their case the thought was this requires them to actually go through and make updates as needed moreso than prepopulation of the entire record which may result in the client scanning and submitting the filing.

mstanton1 avatar Mar 05 '24 22:03 mstanton1

@J-Baese @forgeuxGH5 I believe this can be moved into Ready for Dev? It's in the Visual Design in Progress but with the current dashboard approach of leveraging Nuxt with lesser customization I'd imagine we'd want to do the same with this component (it's similar to directors) so could avoid the extra design effort now on this. Can you confirm you're okay with this being moved?

mstanton1 avatar May 24 '24 20:05 mstanton1

@J-Baese can you make sure the designs for these components are up to date - we might want to split this into two design tickets - one for the Business Dashboard and one for the Company Info page. That way we can prioritize. I'm not sure where those designs are at so I can't really comment on moving to ready-for-dev.

forgeuxGH5 avatar May 27 '24 18:05 forgeuxGH5

Pulling ticket back into wireframes in progress for review. This page should not include private information, or should have that redacted.

mstanton1 avatar Nov 01 '24 17:11 mstanton1

Reviewed current Figma for Entity Dashboard view with policy and there were some questions about the mental model behind the data shown. Can we work on creating two mocks for review and decision.

https://www.figma.com/design/4oi1IWHe0DmbY8EZk3Srs3/Add%2Fedit-SI?node-id=2332-24893&p=f&t=yvHQCMrXVNWCHL0u-0

Mock 1 could include only public details in this page: SI name, citizenship and year of birth. Mock 2 could aim to include a few details that are more likely to change (address?).

mstanton1 avatar Jan 08 '25 17:01 mstanton1