Database Reference

Staff adds sales representatives and their customer assignments without replacing Magento customer or order records. Optional add-ons extend that relationship with history, visits and representative-created quotes.

Staff and customer ownership

Relationship Why it matters
customer_salesstaff belongs to one customer_salesstaff_group Groups representatives for permissions, reporting or organizational structure.
customer_salesstaff_customer links one customer_salesstaff with one customer_entity Defines which customers a representative may manage.

Customer History and Customer Visit add-ons

Relationship Why it matters
customer_salesstaff_customer_history belongs to one customer_entity and one customer_salesstaff Keeps representative notes and activity with the customer account they concern.
customer_salesstaff_customer_history_file belongs to one customer_salesstaff_customer_history Stores attachments with the correct history entry.
customer_salesstaff_visit belongs to one customer_salesstaff and one customer_entity Records the customer covered by a planned or completed visit.
customer_salesstaff_visit can refer to one customer_address_entity Connects an on-site visit with the selected customer location.

Staff Quote add-on

Relationship Why it matters
customer_salesstaff_quote belongs to one customer_salesstaff Records the representative responsible for the quote.
customer_salesstaff_quote can belong to one customer_entity Associates the quote with the selected customer.
customer_salesstaff_quote belongs to one store Preserves the Store View and commercial context used for the quote.
customer_salesstaff_quote can create one sales_order Links an accepted representative quote to its Magento order.
customer_salesstaff_quote_item belongs to one customer_salesstaff_quote and one catalog_product_entity Stores the products and negotiated line details.
Quote history and attachments belong to one customer_salesstaff_quote Preserve changes, communication and supporting files with the quote.

Authentication tokens and internal processing fields are not included. Use the Staff account, Admin screens or module APIs for changes so customer access and attribution rules remain intact.