The short answer
The Financial tab in the Contact 360 view is dark-launched — the code is shipped but the tab is hidden behind a feature key called Crm.FinancialPosition.View. The grant is off by default for every tenant. To turn it on, your kernel administrator (or your ZiplineOS account manager) needs to enable it in the feature-grants matrix.
What is "dark-launched"?
ZiplineOS ships some features in a "dark" state — fully built, fully tested, fully merged into the product, but invisible until someone explicitly turns them on. We do this when a feature is ready to roll out gradually rather than all-at-once, or when it depends on a tenant-by-tenant policy decision (which Financial does — not every customer wants their staff seeing financial-position data on contacts).
Where to enable it
- Customer admins: ask your account manager to enable
Crm.FinancialPosition.Viewfor your organisation. - ZiplineOS staff: kernel feature-grants matrix → find the contact's organisation → toggle
Crm.FinancialPosition.Viewfor the relevant role(s).
Will it show up immediately?
Yes — once the grant is flipped, the tab appears on the next page load. There's no build, no deploy, no waiting.
How is this enforced?
The grant is checked on the server as well as in the UI, so even if a power user crafted a custom request, they couldn't read financial-position data without the grant. The UI tab is just the visible end of the same check.
Related
- What's changed in the Contact 360 view in CRM?
- For the full Contact 360 redesign reference, visit the Rolodex (CRM Portal) at https://crm.ziplineos.com.au.
