QA

Refine results
Status
Category
Technology
Confidence Level
  • In scope
    High

    Users authenticate separately on GI and IR Impact

    Section: Users, authentication and data separation

    Assumption: GI and IR user data must remain fully separate to avoid unintended coupling or side effects.

    Agreed item: Confirm that users authenticate separately on GI and IR Impact.

    • There are users who login to both IR and GI
    • There are GI and IR preferences in Workbooks as it stands
    • If they are on both sites they are
      • flagged as ‘both’ in the brand in the CRM
    • Not an issue to show GI content within their IR profile
    • No known data protection issues to share between IR and GI, but Andy thinks this is an issue – you shouldn't be shown to be sharing their data across the sites
    • Consensus is that data is kept completely independent across each website

    Source: GI website scoping workshop notes (12 Jan, 10–12pm)

    No comments to show.
    Category:
    Tech:
  • In scope
    High

    Usernames, passwords and login sessions are entirely independent between the two sites

    Section: Users, authentication and data separation

    Assumption: GI and IR user data must remain fully separate to avoid unintended coupling or side effects.

    Agreed item: Confirm that usernames, passwords and login sessions are entirely independent between the two sites.

    • Correct

    Source: GI website scoping workshop notes (12 Jan, 10–12pm)

    No comments to show.
    Category:
    Tech:
  • In scope
    High

    Accounts using the same email address on both sites are not linked in any way

    Section: Users, authentication and data separation

    Assumption: GI and IR user data must remain fully separate to avoid unintended coupling or side effects.

    Agreed item: Confirm that accounts using the same email address on both sites are not linked in any way.

    • Correct

    Source: GI website scoping workshop notes (12 Jan, 10–12pm)

    No comments to show.
    Category:
    Tech:
  • In scope
    High

    Updates to user profiles or preferences on GI do not propagate to IR, and vice versa

    Section: Users, authentication and data separation

    Assumption: GI and IR user data must remain fully separate to avoid unintended coupling or side effects.

    Agreed item: Confirm that updates to user profiles or preferences on GI do not propagate to IR, and vice versa.

    • Correct. Aim organisationally that GI and IR are completely separate entities
    • Have two separate databases – a GI and IR ones.
    • Deduping will be needed in some cases

    Source: GI website scoping workshop notes (12 Jan, 10–12pm)

    No comments to show.
    Category:
    Tech:
  • Deferred / Phase 2
    Medium

    Password resets and credential changes apply only to the site on which they are performed

    Section: Users, authentication and data separation

    Assumption: GI and IR user data must remain fully separate to avoid unintended coupling or side effects.

    Agreed item: Confirm that password resets and credential changes apply only to the site on which they are performed.

    • Agreed
    • Service providers are the main people across both brands A note RE CRM, as HubSpot likely to be procured later in the year. Workbooks to be retired.

    Source: GI website scoping workshop notes (12 Jan, 10–12pm)

    No comments to show.
    Category:
    Tech: ,
Andy White, Freelance WordPress Developer London