Customers in Advvy — Master Clients, Clients, Contacts, Products & Product Classifications

Modified on Fri, 19 Jun at 4:30 PM

Overview

Five records work together to represent your customers in Advvy.

Advvy organises customer data across five linked record types. Each plays a distinct role — from the top-level grouping of clients all the way down to individual product lines and the people who approve work through the Client Portal. Understanding how they connect helps you set up campaigns correctly and ensures reporting, billing, and approvals all work as expected.

Master Client

Top-level grouping

Client

Billable entity

Contact

People & portal users

Product

Brand / product line

Product Classification

Grouping / taxonomy

How the Records Connect

Entity relationship map showing how all five records link to each other and to Campaigns.

Master Client
a1a_masterclient

↓ One Master Client → Many Clients

Client
account

↙ Contacts ↓ Products Products ↘

Contact
contact

Product Classification
a1a_productclassification

→

Product
a1a_product

↓ Portal access Product groups Products ↓ Used on Campaigns

Master Client can also be self-referential (Parent Master Client) · Client can be self-referential (Parent Client) · Product can be self-referential (Parent Product)

Entity Details

1 — Master Client

The top-level grouping record for related clients across an agency.

a1a_masterclient · Custom Entity

Master Client

A Master Client is the top-level grouping record in Advvy's customer hierarchy. It allows an agency to group multiple Client records that belong to the same holding company, parent brand, or client group. Master Clients support their own parent/child hierarchy — a Master Client can have a Parent Master Client, enabling multi-tier corporate group structures. They are primarily used for consolidated reporting and data governance.

Schema Name

a1a_masterclient

Custom Entity

Yes

Audited

Yes

Ownership

User Owned

Self-Referential

Yes — Parent Master Client

Used On Campaign

Via Client → Master Client

Field	Type	Required	Notes
Name	Text	Required	The Master Client display name (max 100 chars)
Code	Text	Optional	Internal code used for identification and reporting
Agency / Branch	Lookup	Required	Links to the Business Unit (branch) that owns this record
Business Unit	Lookup	Recommended	Supports scoped reporting by BU
Parent Master Client	Lookup	Optional	Self-referential — enables multi-tier holding group structures (→ a1a_masterclient)
Is Parent	Yes/No	Optional	Flags this record as a parent in a holding group
External Account Code	Text	Optional	Code from an external/source system
External Account Name	Text	Optional	Name from external system (for reconciliation)
Reporting Code	Text	Optional	Code used in consolidated reports
Reporting Name	Text	Optional	Display name in reporting outputs
Source System Status	Yes/No	Auto	Active by default — used for data sync governance
Exclude from Automated Mgmt	Yes/No	Optional	Removes record from automated data management processes

ℹ️

Master Clients are optional but recommended for large client bases. Not every agency uses them — but for clients with sub-brands or holding company structures, they enable consolidated reporting across all related Client records.

2 — Client

The core billable entity in Advvy — the company that campaigns are built for and invoiced to.

account · Standard Dynamics 365 Entity (customised)

Client

The Client record is the primary customer record in Advvy. It represents the business entity that owns the campaign — the company being planned for and billed. Clients link to a Master Client (optional), have their own parent/child hierarchy (Parent Client), and anchor Contacts, Products, Campaigns, and Brands. Every Campaign in Advvy must have a Client, and the Client field on a Campaign is locked after first save.

Schema Name

account

Custom Entity

No (customised)

Audited

Yes

Ownership

User Owned

Self-Referential

Yes — Parent Client

Required on Campaign

Yes — locked after save

Field	Type	Required	Notes
Name	Text	Required	The client's display name — used throughout Advvy and on MBAs
Unique Client Name	Text	Optional	System-unique name to distinguish clients with identical names
Code	Text	Optional	Internal client code for identification and reference
Branch	Lookup	Required	Agency/Branch that owns this client (→ businessunit)
Master Client	Lookup	Optional	Links to a parent Master Client record for group reporting (→ a1a_masterclient)
Parent Client	Lookup	Optional	Self-referential — supports parent/subsidiary client structures (→ account)
Type	Choice	Optional	Client type classification (→ a1a_clienttype)
Rating	Choice	Required	Platinum / Gold / Silver / Bronze — client tier for prioritisation
Client Team	Lookup	Optional	Team responsible for this client (→ team)
Week Start Day	Choice	Optional	Controls the week start day for media planning (Mon–Sun). Defaults to system setting.
Finance System Account Code	Text	Optional	Account code in the external finance system for invoice matching
Finance System Account Name	Text	Optional	Name in the external finance system
Finance System Default Tax Type	Lookup	Optional	Default tax type applied to invoices (→ a1a_financetaxtype)
Finance System Invoice Theme	Lookup	Optional	Invoice template/theme for this client (→ a1a_financeinvoicetheme)
Media Plan Template	Lookup	Optional	Default Excel template for this client's media plans (→ a1a_advvyfiletemplate)
TCC Calculation Method	Choice	Optional	Controls how Total Campaign Cost is calculated for this client
Legal Documentation	Multiline Text	Optional	Stores client-specific legal text referenced in MBAs or documents
Client Clause 1 / 2	Text	Optional	Custom clauses printed on client-facing documents
Reporting Code / Name	Text	Optional	Overrides the display in reporting outputs
Source System Status	Yes/No	Auto	Active by default — controls sync eligibility from external systems

⚠️

The Client field on a Campaign cannot be changed after the Campaign is saved. Always confirm the correct Client record exists before creating or converting a Campaign.

3 — Contact

People linked to a Client — including Client Portal users who review and approve MBAs.

contact · Standard Dynamics 365 Entity (customised)

Contact

A Contact is a person associated with a Client. In Advvy, Contacts serve two roles: they are general contact records for a client (such as account managers or brand contacts), and they can be configured as Client Portal users who receive MBA notifications and approve work through the Client Portal. Portal Contacts are distinguished by the Portal User flag and have login credentials, portal visibility settings, and product-level access controls.

Schema Name

contact

Custom Entity

No (customised)

Audited

Yes

Ownership

User Owned

Portal Access

Yes — via Portal User flag

Product Scoped

Yes — Contact → Product

Field	Type	Notes
First Name / Last Name	Text	Standard contact name fields (inherited from Dynamics 365 Contact)
Email (standard)	Email	Primary email address used for general communication
Contact Type	Lookup	Classifies the contact's role (→ a1a_contacttype, e.g. Agency Contact, Client Approver)
Client (Parent Account)	Lookup	The Client this Contact belongs to (→ account) — set via standard Dynamics Account field
Product	Lookup	Scopes this Contact's portal access to a specific Product (→ a1a_product)
Portal User	Yes/No	Portal — Enables Client Portal access for this Contact. Must be Yes to receive MBA notifications.
Login Email	Email	Portal — The email used for Client Portal login (may differ from primary email)
Portal Visibility	Choice	Portal — Controls what the contact sees: Media (campaign/MBA data) or Workflow content
Portal Currency	Lookup	Portal — The currency used when displaying financial data to this contact in the portal
Portal Invitation URL	URL	Portal — The unique portal invitation link generated for this contact
Token / Token Expiry Date	Text / Date	Portal — Authentication token for portal session management
Theme	Lookup	Portal — Visual theme applied to this contact's portal experience
Country	Lookup	Contact's country (→ a1a_country)
Generated Unique ID	Text	System-generated unique identifier for external references
Source System Status	Yes/No	Active by default — controls sync eligibility

Portal User contacts receive MBA approval notifications automatically. A Contact must have Portal User = Yes and a valid Login Email to access the Client Portal and approve MBAs. The Portal Visibility field controls which sections of the portal they can see.

4 — Product

The product or brand line that a Campaign is planned and reported against.

a1a_product · Custom Entity

Product

A Product in Advvy represents a brand, product line, or business unit within a Client. Products are required on every Campaign — they anchor reporting, media classification, and MBA generation to a specific line of business. Products can be grouped under a Product Classification for taxonomy, and support parent/child structures (Parent Product) for sub-brand management. Contacts can be linked to Products to scope their Client Portal access to specific product lines.

Schema Name

a1a_product

Custom Entity

Yes

Audited

Yes

Ownership

User Owned

Self-Referential

Yes — Parent Product

Required on Campaign

Yes (optional at creation)

Field	Type	Required	Notes
Name	Text	Required	The product/brand name (max 100 chars)
Client	Lookup	Required	The Client this Product belongs to (→ account). Every Product must be linked to a Client.
Code	Text	Optional	Internal product code used in reference data and reporting
Product Classification	Lookup	Optional	Groups this Product under a classification for taxonomy and reporting (→ a1a_productclassification)
Parent Product	Lookup	Optional	Self-referential — links to a parent product for sub-brand structures (→ a1a_product)
Primary Contact	Lookup	Optional	The main Contact for this Product — used to scope portal access (→ contact)
Contact	Lookup	Optional	Secondary contact link on the Product record (→ contact)
Product Description	Multiline Text	Optional	Free-text description of the product or brand
Reference Name	Text	Optional	Alternative name used in certain reference data outputs
External Code / ID	Text	Optional	Identifiers from an external or source system for sync reconciliation
Colour	Text	Optional	Hex colour for visual identification in reporting and plan views
Reporting Code / Name	Text	Optional	Overrides the Product name and code in reporting outputs
Source System Status	Yes/No	Auto	Active by default — controls sync eligibility

ℹ️

A Campaign supports multiple Products. Save the Campaign first — a Products table then appears on the record, allowing multiple products to be added. The Product field on the Campaign form is a quick-add, not a single-select restriction.

5 — Product Classification

A taxonomy layer for grouping Products under a Client.

a1a_productclassification · Custom Entity

Product Classification

Product Classifications are grouping records that categorise Products under a Client. They sit between the Client and the Product in the data hierarchy — a Client has many Product Classifications, and each Product Classification contains many Products. They are used to group related products for reporting, filtering, and taxonomy purposes. Like Products, they are Client-specific — a Product Classification always belongs to one Client.

Schema Name

a1a_productclassification

Custom Entity

Yes

Audited

Yes

Ownership

User Owned

Self-Referential

Used On Product

Yes — as a grouping lookup

Field	Type	Required	Notes
Name	Text	Required	The classification name (max 100 chars)
Client	Lookup	Required	The Client this classification belongs to (→ account). Must match the Client of any Product assigned to it.
Code	Text	Optional	Internal classification code
Unique Product Classification Name	Text	Optional	System-unique name to prevent duplicate classification names within a client
Colour	Text	Optional	Hex colour for visual grouping in plan views
External Code / ID	Text	Optional	Source system identifiers for sync reconciliation
Reporting Code / Name	Text	Optional	Overrides the classification name in reporting outputs
Source System Status	Yes/No	Auto	Active by default — controls sync eligibility

Product Classifications are optional but useful for clients with large product portfolios. If a Client only has a handful of products, classifications may not be necessary. They become valuable when you need to group and filter Products in reporting by category (e.g. "Insurance Products", "Home Loan Products").

Key Takeaways

The hierarchy flows downward: Master Client → Client → Product Classification → Product. Contacts sit alongside Clients and can be scoped to a Product for portal access.

Master Clients and Product Classifications are optional grouping layers. Small client rosters may not need them — but they become important for multi-brand clients and consolidated reporting.

The Client field on a Campaign cannot be changed after saving. Always confirm the correct Client record exists before creating or converting a Campaign Brief.

Contacts with Portal User = Yes can log in to the Client Portal, receive MBA notifications, and approve work. Their portal visibility and product scope are controlled by the Portal Visibility and Product fields on the Contact record.

Products are required on Campaigns, but multiple Products can be added. Save the Campaign first — the Products table then appears to allow multi-product selection.

Master Clients, Clients, and Products all support parent/child hierarchies. Each can have a "Parent" of the same type, enabling multi-tier corporate and brand structures within each record type.