Developer sandbox
A safe space, with SYNTHETIC DATA, for a developer to test an extension against its permission contract before trusting it. Pick a published extension and see, resource by resource and action by action (READ / WRITE), what the contract ALLOWS and what it DENIES — including the effect of the authori…
What you find on this screen
A portrait of the screen, read from the screen itself — it changes when the screen changes.
Available actions
Provision kit
The list shows
WhenVerticalDemoHead officeMigrationTrackEligible
Form fields
Ramo
Ramo Rotulo
Demo Pronto
Matriz Pronta
Matriz Qtd Nao
Migracao Pronta
Trilha Atribuida
Trilha Matriculas
Relatorio
Dhcadastro
Start here
The partner gets certified without taking a week of the team’s time
Enabling a partner in a vertical used to take a week of senior people putting together a demo, a learning path and materials. The kit automates it: enter the partner code, choose the vertical and provision — the rest is assembled by reusing the services that already exist.
What this screen is
The partner becomes qualified in a vertical without consuming a week of the team's time. Choose the vertical and trigger the kit: reusing the services that already exist, it assembles the enablement package — seeded demo per vertical, "zero no" matrix for the vertical, self-service Migration Kit and certification track (Academy) — and shows the checklist of what is ready. Indicate a sandbox so the seeding and the track enrollment actually take effect.
How to
What the kit puts together
Four deliverables at once: the seeded demo of the vertical (realistic sample data), the "zero no" matrix for that vertical (real readiness, not promised), the self-service Migration Kit and enrollment in the Academy certification track.
The checklist and the FIT seal
QUALIFIED only when all four fronts are complete; until then, the badge says PENDING ITEMS and each line shows in red what is missing — including how many "no" answers the vertical's matrix still has. A qualified partner in a vertical full of holes is the worst of all worlds: the pending item shows up here before it shows up at the customer.
This partner’s kits
The history lists each provisioning with the result at the time. Running it again for the same partner is safe and is the right way to re-check after closing a pending item.
Rules
Sem sandbox, parte do kit não atua de verdade
Seeding the demo and enrolling in the track need a company to act on: use the current company as a sandbox (switch) or enter another one's code. Without that, the kit checks what it can, but does not seed — and the checklist shows the pending item.
Frequently asked questions
Which question this screen answers
Does a new partner become qualified in a vertical without consuming a week of the team's time? Choose the vertical, indicate a sandbox and trigger the kit: it assembles the vertical's seeded demo, the "zero no" matrix, the self-service Migration Kit and enrollment in the Academy certification track — and returns the checklist of what is ready. The QUALIFIED badge appears when all four checklist items are complete for that partner in that line of business.
Was this article helpful?
In the same module: Channel4
Model governanceThe auditable model cards for the actuarial core's models: documented method, baseline always in view, Brier …Partner OEM profileThe brand of an OEM partner: name, logo, color, domain, sender e-mail, L1 support and own billing, which is w…Actuarial coreThe math behind risk, VISIBLE (no black box). Per indicator: the credibility-weighted estimate — how much com…Digital twin (what if…?)The company's what-if simulator: pull a lever and see the effect propagate through cash (13 weeks), margin, a…
Tenka Academy
Explore the AcademyStep-by-step learning paths for your industry, inside the platform.