Skip to content
SecoStrategic accounts administration

Review device — not a security control. It changes what this prototype shows, never what anyone is permitted to do.

Open questions

The Strategic Accounts questions this application is still waiting on, each with the topic it belongs to and the person or group who owes the answer. Anyone may record a response; a response is a record of what was said, not a decision, and it does not resolve a business rule waiting on it.

Questions
10
Topics
6
Answered
0
Unanswered
10

  1. P8-Q13Portal contacts

    Contact attachment level — does a customer contact belong to a single site (e.g. Rolls-Royce Bristol) or to the parent customer (Rolls-Royce)? What a contact can see is filtered by whichever account record they are attached to, so a contact attached to the parent would see every site beneath it. Why it matters: this is the load-bearing unknown for portal isolation. Entitlement is a per-site allow-list, and if contacts attach to the parent that allow-list cannot be enforced by account scoping alone. Until it is settled, external access here shows the contact-to-account association as unconfirmed. Numbered as the SA Customer Portal register numbers it.

    Owner: Jimmy Connor / Steven Bell (the client)

    Unanswered

  2. P8-Q1Portal contacts

    Customer web role — who the customer user is. The portal register records one customer role only, with everyone from the customer seeing the same thing, and entitlement granted per site rather than per global account. What that role is actually called, and whether one role really covers procurement and engineering alike, is not confirmed. Why it matters: this application holds the web role list for the portal, so until the role is named it carries a single placeholder, "Customer contact (to confirm)", and no customer roles are invented. Numbered as the SA Customer Portal register numbers it.

    Owner: Jimmy Connor / portal owner (the client)

    Unanswered

  3. P8-Q14Portal contacts

    Portal login administration — who creates a customer login, invites and approves it, and who removes it when that person leaves the customer or changes role? Why it matters: nobody has been named. A customer contact whose access is never removed keeps seeing that account's data, and the dormancy review in external access is a safety net, not an owner. Numbered as the SA Customer Portal register numbers it.

    Owner: To confirm (the client)

    Unanswered

  4. SA-01Reporting

    Reporting by role level — this application currently shows reporting as available to L2, L3 and L4 and not to L1. Only part of that is decided: the client confirmed that L1 never exposes anything to the customer portal. The split of Power BI reporting by role level is carried over from an EPMS licensing decision and has never been confirmed for Strategic Accounts. Why it matters: if L1 does need reporting, the licensing and the permission both change. The current display is an assumption, not a decision.

    Owner: Cloud Solutions Partners with the client

    Unanswered

  5. SA-02Widget permissions

    Widget permission defaults ownership — the Strategic Account Management app hard-codes the widget defaults matrix in its own code today. Moving that ownership here, so administrators change defaults as configuration rather than as a deployment, needs programme agreement and a change to that application. Why it matters: this is the founding promise of this application, and it cannot be met for widget defaults by a change on this side alone.

    Owner: Cloud Solutions Partners with the programme

    Unanswered

  6. SA-03Choice sets

    Choice-set integers for the Strategic Accounts family — role levels, web roles and trigger events all carry unconfirmed integers today. Where the integers for this family are minted, and by whom, is undecided. Why it matters: integers cannot be renumbered once data exists, and a collision with a set another platform owns is expensive to unpick after the Dataverse build.

    Owner: Cloud Solutions Partners with the Dataverse owner

    Unanswered

  7. SA-04Dashboard links

    The shared global group — what is it called, and who owns it? Five links (Cost Savings, IHUB Projects, Market Share, Review Meetings, CSS 186) appear on every region's dashboard, and Strategic Account Management holds no group row for them at all: they are assembled in its code. The dashboard links register therefore carries them under a working name of its own, "Shared global rail", which nobody has agreed. Why it matters: a name and an owner have to be agreed before the dashboard link tables are populated, because that is the moment the group becomes a real row, and a group created under an invented name is one somebody has to rename later.

    Owner: Jimmy Connor

    Unanswered

  8. SA-06Widget composition

    A custom report is recorded as a Power BI embed, but the prototype only links out to the report. Embed or link in the build?

    Owner: Not attributed — raised here, undated

    Unanswered

  9. SA-07Widget composition

    Rights resolve per widget kind, not per widget instance. Is that acceptable for accounts carrying several custom reports?

    Owner: Not attributed — raised here, undated

    Unanswered

  10. SA-08Widget composition

    The Strategic Account Management seed rewrites external link widgets to open in app when it creates instances, contradicting the widget library. Which is correct?

    Owner: Not attributed — raised here, undated

    Unanswered

Three of these questions are owned by the SA Customer Portal register and keep its numbering, so one question carries one number across the programme. A response recorded here is a record of what was said; it does not close the question in the register that owns it.