Versions
Versions is the audit history of changes made in Owner (PaperTrail-style version records).
Go to Configuration β Company β Versions in Owner.
The list shows:
| Column | Description |
|---|---|
| Date | When the change happened |
| Author | Who made the change |
| Model | Which entity was changed (item_subtype if present, otherwise item_type) |
| Action | Event type stored in the event field |
| ID | Item ID |
You can filter by Model, ID, Action, From, and Until; open Details for a row; or export to CSV.
The Model and Action filters are free-text fields. Type the exact value (case-sensitive as stored), for example Customer or login.
There is no create, edit, or delete action on this tab β it is read-only.
Action valuesβ
These are the event values that can appear in the Action column / filter. Not every company will see all of them β only actions that have happened for that company.
Standard CRUD and sessionβ
| Action | Meaning |
|---|---|
create | Record created |
update | Record updated |
destroy | Record destroyed (PaperTrail default delete event) |
delete | Custom delete event (used on some resources, e.g. Customer, ContactPolicy, Synchro) |
login | User or customer signed in |
logout | User signed out |
reset_password | Password reset performed |
send_reset_password | Reset-password email sent to a customer |
Campaigns and deliveryβ
| Action | Meaning |
|---|---|
send / send_test / deliver | Campaign or plan send / test / delivery |
schedule / cancel_schedule / remove_schedule | Scheduling changes |
cancel / pause / resume | Campaign lifecycle |
clone / cloned | Clone requested / clone completed |
reuse / undo_reuse | Reuse / undo reuse |
export / export_customers / export_sales | Exports |
update_history / *_history | History-related updates (e.g. send_history, pause_history) |
calculate_forecast / calculate_roi | Forecast / ROI calculations |
generate / generate_and_execute / execute / execute_step / process | Generation / execution jobs |
approve | Plan campaign approved |
tag / retro_tag / reset_tags / score_error_tag | Tagging operations |
rollback / restore / repeat | Recovery / repeat operations |
Coupons, vouchers, scores, customersβ
| Action | Meaning |
|---|---|
generate | Coupon generation |
archive / unarchive | Coupon archive state |
give_coupon | Coupon given to a customer |
redeem_segment / print_undo | Redemption-related actions |
give_score / subtract_score / transfer_score / delete_score | Score operations (incl. massive actions) |
reject / run | Massive action reject / run |
validate | Credit validation |
add_card / update_card | Customer card added / updated |
recover_customer_email | Customer email recovery |
Otherβ
| Action | Meaning |
|---|---|
sync | Synchro sync |
set_products | Feature products assignment |
delete_segments / delete_last_apply | Segment category / last-apply cleanup |
create_detail / update_detail / destroy_detail | Report or campaign-block report detail changes |
massive_update / massive_update_error | Bulk field update job / failure |
clone | Loyalty rule or tier definition clone |
Model valuesβ
These are the entity names that can appear in the Model column / filter. The UI shows item_subtype when present, otherwise item_type. Filtering by Model matches either field.
Configuration and accessβ
| Model | What it is |
|---|---|
Company | Company settings |
Configuration | Company configuration flags |
APIKey | API keys |
CartAdditionalCost | Additional costs catalog |
CartChannel | Cart channels |
CustomAttributesDefinition | Custom attribute definitions |
ContactPolicy | Contact policy |
CurrencyConversion | Currency conversion |
CashbackConfiguration / FeatureCashbackConfiguration / ProductCashbackConfiguration / PaymentMethodCashbackConfiguration | Cashback configs |
User / Account / Customer | Owner users / accounts / customers (STI may appear as Account with subtype) |
UserRole / UserRoleGroup / RoleGroup / RoleGroupRole / RolesPermission / GlobalRole | Roles and permissions |
TermCondition | Terms and conditions |
Customers, data, audiencesβ
| Model | What it is |
|---|---|
Profile | Customer profile |
CustomerAttributeDefinition | Calculated / customer attribute definitions |
Segment / SegmentCategory | Audiences and categories |
Location / LocationTaxonomy / LocationTaxonomyTerm | Stores and location taxonomies |
Product / Feature / FeatureTaxonomy / FeatureInternal | Products and features |
PaymentMethod | Payment methods |
Filter | Filters |
Period | Periods |
Synchro | Sync jobs |
BigqueryJob / BigqueryJobStep | BigQuery jobs |
Loyalty and promotional engineβ
| Model | What it is |
|---|---|
LoyaltyRule / LoyaltyRuleCategory / LoyaltyRuleConfiguration / LoyaltyRuleHistory / LoyaltyRuleLineAttribute / LoyaltyRuleMoment | Points campaigns (new engine) and related |
CustomEntityLoyaltyRule / CustomerAttributeLoyaltyRule | Loyalty rule links |
Promotion / PromotionalDiscount | Promotions / discounts |
Coupon / Voucher / Redemption / Credit | Coupons, vouchers, redemptions, credits |
Reward / RewardCategory / RewardCodeBatch / RewardTaxonomy / RewardTaxonomyTerm | Rewards |
TierDefinition | Tiers |
ChallengeDefinition | Challenges |
MassiveAction | Massive loyalty actions |
MotivatorLineAttribute / CustomEntityMotivator / CustomerAttributeMotivator | Legacy motivator-related |
Campaign personalization and messagingβ
| Model | What it is |
|---|---|
Campaign / CampaignCategory / CampaignTemplate / CampaignHistory / MembershipCampaignHistory | Targeted delivery campaigns |
CampaignHistoryCoupon / CampaignHistoryMessage / CampaignHistoryChallenge | Campaign history subtypes |
CampaignBlock / CampaignBlock::History / CampaignBlock::CustomHistory / CampaignBlock::Report / CampaignBlock::CostByCategory / CampaignBlock::LocationROI | Campaign blocks and related |
Plans::Plan / Plans::CampaignPlan / Plan | Intelligent Delivery plans |
Message / MessageCategory | Messages |
NewsTaxonomy / NewsTaxonomyTerm | News taxonomies |
Recipe | Recipes |
Alert | Alerts |
Report / ReportDetail | Reports |
ConnectorAction | Connector actions |
Start with a Model filter (e.g. Coupon, LoyaltyRule, Customer) and optionally narrow by Action (update, login, send). Use ID when you already know the record id.