Skip to content
Seco

Open questions

Nothing here has an answer yet. Each item stays pending until it is confirmed with its owner.

  • P8-Q1 — Scope & audience

    Who logs in (customer procurement, engineering, per-site or global) and what is the single most valuable first view?

    Owner: Jimmy Connor / portal owner (to confirm)

    Pending confirmation

  • P8-Q2 — Data boundary

    Which internal features become customer-facing (obsolescence notices, sales/spend, market share, order/expediting status, consignment) and which stay internal-only?

    Owner: Jimmy Connor / Steven Bell

    Prototype direction: Prototype strawman: obsolescence and order delivery are exposed for the seed account; sales/spend, market share, consignment and drawings are hidden. Not a confirmed decision.

    Pending confirmation

  • P8-Q3 — Data isolation & security

    A customer sees only their own account's data. What is the auth and row-level isolation approach on Power Pages?

    Owner: CSP (technical)

    Pending confirmation

  • P8-Q4 — Authentication

    How do customer users sign in — external identity / invitation flow on Power Pages?

    Owner: CSP (technical)

    Pending confirmation

  • P8-Q5 — Owners

    Who owns portal requirements and client-side sign-off?

    Owner: To confirm

    Pending confirmation

  • P8-Q6 — Notice delivery

    For the obsolescence 12-month notice: CRM email, portal notification, or both? Ties to SAM Q7.

    Owner: Steven Bell

    Direction (not confirmed): 3 Sep 2026 Q&A (Steven Bell): the 12-month notice should be an automated email originating from CRM; the portal's role is to show the customer which of their products are affected and the notice status, not to send the notice. Not confirmed — depends on Seco fixing the CRM process first.

    Prototype direction: Prototype strawman: the lifecycle view shows affected parts and notice status only; no 'send notice' action is offered.

    Pending confirmation

  • P8-Q7 — Exposure scope

    Is what a customer sees configured per account, or is there a global default with per-account overrides?

    Owner: Jimmy Connor / Steven Bell

    Raised by: CSP, 4 Sep 2026 — exposure-control discussion

    Pending confirmation

  • P8-Q8 — Hidden means what?

    When a widget or section is hidden for the portal, is only the tile hidden or is the underlying data also not exposed to the customer at all? (Recommendation to discuss: hidden = not exposed.)

    Owner: CSP (technical) with Steven Bell

    Raised by: CSP, 4 Sep 2026 — exposure-control discussion

    Prototype direction: Prototype strawman: hidden = not exposed. A widget that is not exposed produces no tile and no data request (fail closed).

    Pending confirmation

  • P8-Q9 — Inheritance across the hierarchy

    Does a site (e.g. RR Bristol) inherit its portal exposure from the global account (RR), or is it set per site? Ties to P8-Q1.

    Owner: Jimmy Connor

    Raised by: CSP, 4 Sep 2026 — exposure-control discussion

    Pending confirmation

  • P8-Q10 — Who may expose

    Of the three management roles in the internal SAM app, which may change portal exposure directly and which may only propose? Is an approval step needed?

    Owner: Steven Bell

    Raised by: CSP, 4 Sep 2026 — exposure-control discussion

    Pending confirmation

  • P8-Q11 — Audit

    Does the customer, or Seco, need a visible history of when their portal view changed and by whom?

    Owner: Steven Bell

    Raised by: CSP, 4 Sep 2026 — exposure-control discussion

    Pending confirmation

  • P8-Q12 — Embedded reports

    For Power BI embed widgets, does portal exposure require a separate customer-facing report / row-level security rather than the internal report?

    Owner: CSP (technical) with Orla

    Raised by: CSP, 4 Sep 2026 — exposure-control discussion

    Pending confirmation