Accounts and access

A manufacturing request often reaches sales under a trading name while the proposal belongs to a particular legal company. The customer record keeps the company name and code alongside its main contact, address and eligibility note. The owning organization identifies the business entity responsible for that relationship. Before a Relationship Owner creates an opportunity, App Administrator should confirm that the selected company is the intended customer and that its eligibility information still applies.

Keep the main customer contact current and agree who verifies a change in procurement personnel. Confirm the intended address when correspondence and delivery refer to different locations. Preserve the company code when details change, so the next import joins the existing customer history. The owner should be able to explain who supplied the changed information and which customer request it affects.

• Customer identity. App Administrator maintains customer companies, including their active setting and eligibility note. Relationship Owner reads the company context before preparing a deal; making a customer inactive should be reviewed for its effect on existing open work.
• Organization membership. Team membership connects each internal person to a business entity and user identity. Active membership, the recorded role label and time zone help resolve the actor and operating context used by guarded workflow actions.
• Access decisions. Keep the configured role separate from the free-text membership role label. An identity supplied by a page must be checked against live membership and the caller’s authority before a business action is accepted.

Decide who maintains company codes, who can change organization membership and how account eligibility is evidenced. Map existing company identifiers before importing opportunities. Confirm which organization time zone governs dated review work and how the team’s own time zone is used when displaying it.

Agree who administers user access and who performs independent review. Configure a controlled decision action for the eligible reviewer. Neither a membership label nor a visible review queue should grant permission to modify the decision record. Rehearse these distinctions with ordinary accounts rather than an administrator session, including a staff member whose access was withdrawn.

A Relationship Owner receives a request for machined housings from a customer whose company name has recently changed. App Administrator matches its company code to the existing customer record, confirms the owning organization and updates the contact information with a documented reason. The owner then links the new opportunity to that existing company, avoiding a second customer history under the new spelling.

Later, the owner transfers to another organization. Rehearse the page action using their earlier identity and confirm that the live membership check prevents access outside the permitted scope. Auditor should still be able to trace the earlier opportunity and its decision evidence within authorized access. A personnel change should not remove the customer record or rewrite the actor retained on an earlier decision.

• Active customer accounts — Review the company code, contact information, eligibility context and owning organization before preparing a deal.
• My organization membership — Check the signed-in person’s organization, active membership and identity mapping during access rehearsal.

Opportunity qualification uses this customer context. Proposal to customer outcome keeps the same customer company through review and close. Check permissions before inviting the pilot team.