Sponsor campaign and ad entity Represents sponsorship campaigns and advertisements.Documentation Index
Fetch the complete documentation index at: https://memberpulseptyltd.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Fields
Field Registry (from workspace/sources/entity-registry.csv)
| Field | Input Type | Required | Notes |
|---|---|---|---|
| Sponsor ID | Number | Required | - |
| Sponsor Name | Text | Required | - |
| Sponsor Description | WYSIWYG (Textarea) | Required | - |
| Sponsor URL | URL | Required | - |
| Sponsor Services | Multi-select | Required | - |
| Sponsor Industry | Multi-select | Required | - |
| Sponsor Logo | File | Required | Image only (JPG, PNG - limit to 3mb) |
| Sponsor Contact Number | Number | Not Required | - |
| Sponsor Contact Email | Required | - | |
| Sponsor Lead Email | Not Required | - | |
| Use Lead Form | True / False | Required | Toggle to display enquiry form on the company directory/profile page |
| Sponsorship Tier | Select | Required | Based on sponsorship tiers created by the admin |
| Sponsorship Status | Selector | Required | For Expression of Interest Approval, options are: Approval, Denied, Pending (the approval table should include the tier they want to join up to) |
| Sponsorship Start Date | Date | Required | - |
| Sponsorship End Date | Date | Required | Calculated based on the tier packages created by the admin |
| Sponsor Primary Member | Number | Required | Admin selects a member/user as the primary entity to edit the sponsorship details |
| Sponsorship Company | Number | Not Required | Links to Company ID for directory usage |
| Sponsor Billing Name | Text | Required | Attach CC to buy credits |
| Sponsor Billing CC | Text | Required | - |
| Sponsorship Credit Balance | Number | Required | Credits are used to pay for sponsor ads - option to buy credits which gives them top up costs |
| Offer ID | Number | Required | Repeater fields to allow sponsors to offer deals to members, this is only available on sponsorship tiers based on what’s created by the admin |
| Offer Name | Text | Required | - |
| Offer Description | Text | Required | - |
| Offer Link | URL | Required | - |
| Offer Image | File | Required | - |
| Sponsored Event ID | Number | Required | Pulls from events |
| Support Ticket ID | Number | Required | Automatically generated by the system and locked |
| Support Ticket Subject | Text | Required | - |
| Support Ticket Description | WYSIWYG (Textarea) | Required | - |
| Support Ticket Files | File | Not Required | - |
| Support Ticket Status | Select | Required | Open, Awaiting Response, Closed |
| Support Ticket Member ID | Number | Required | Automatically pulls through based on the member who created the ticket |
| CRM ID | Number | Required | Automatically pulls into a CRM note or ticket ID based on if a CRM is connected |
| Support Ticket Type | Select | Required | Pulls through a list of different support ticket types defined in the settings |
| Support Ticket Staff ID | Number | Required | Automatically pulls through based on who gets assigned |
| Sponsor Ad ID | Number | Required | Repeating fields, but not required |
| Sponsor Ad Name | Text | Required | - |
| Sponsor Ad Description | WYSIWYG (Textarea) | Required | - |
| Sponsor Ad Image | File | Required | - |
| Sponsor Ad URL | URL | Required | - |
| Sponsor Ad Credit Cost | Number | Required | Cost is automatically calculated and displayed here based on start date and end date entered |
| Sponsor Ad Start Date | Date | Required | - |
| Sponsor Ad End Date | Date | Required | - |
Relationships
| Relation | Type | Target Entity |
|---|---|---|
| company | ManyToOne | Company |
| events | ManyToMany | Event |
| courses | ManyToMany | Course |
Features
Sponsorship
Acceptance Criteria
Frontend
- Admin/client UI can view and manage
Sponsorshiprecords where applicable.
Backend / API
- CRUD operations exist for
Sponsorship(create, read, update, delete/archive).
Permissions
- Access is restricted to appropriate roles (tenant-scoped).
Business Rules
- Fields and relationships documented on this page are enforced for
Sponsorship.
Error Handling
- Invalid payloads return field-level validation errors.