Docs
Getting Trident into a tenant, and getting hold of me when it breaks
Two things live on this page: the install-and-setup sequence, and how support works during a pilot. The page-by-page reference is next door.
Install and set up
Trident is not on AppSource, so it goes in as a per-tenant extension upload. You need an account that can install extensions, in practice a Business Central administrator.
- Upload the app file. Open Extension Management, choose Upload Extension, pick the
.appfile I sent you, and let the deployment finish before touching anything else. It appears in the list as Trident, publisher Marvera, once installed. - Run the guided setup. Search for Assisted Setup and run Set Up Trident Finance. It walks the number series, the billing product for charter fees and for APA, and the posting defaults, and will not let you finish while a required field is empty.
- Check the readiness list. Open Trident Setup Readiness Center. Eleven checks, each with a status, a detail line and a recommended action. Blocked means the thing it names will fail; Warning means it will work but something is missing that you probably wanted.
- Assign one permission set per user. Nobody needs SUPER for day-to-day Trident work, and the pilot proof exists precisely to show that.
| Set | Object | Intended holder |
|---|---|---|
| Trident Read MV | 70241018 | Look, do not touch. Charters, schedules, APA entries, statements, workspaces. Write actions are refused, and so is the Diagnostics page. |
| Trident Ops MV | 70241017 | The daily job: build schedules, create invoices from stages, record and review APA expenses, run reconciliation, prepare statements. |
| Trident Admin MV | 70241000 | Everything Ops does, plus Charter Setup, payment templates, pricing setup, APA categories and Diagnostics. |
| Trident API MV | 70241019 | A service-to-service account hitting the API pages. Not for a human. |
After that, users reach Trident through the Trident Charter Finance role centre. What each page is for is written up in the page reference.
Reporting something
There is no ticketing system and no support rota. There is me, at [email protected]. Send what you have; these three things save a round trip each:
- Your Business Central version and the Trident version, both readable in Extension Management.
- What you did, what you expected, what happened instead.
- The error text or a screenshot, with anything sensitive taken out before it leaves your side.
What you get back
An acknowledgement inside two business days. Usually much faster, and never later than that without a reason I will give you.
For anything security-related, put SECURITY in the subject line. Those are read first, kept confidential, and not discussed anywhere public until there is a fix to discuss.
What I will not do is publish a resolution time I cannot keep. Trident is pre-release and there is one maintainer. Pilot reports are the main thing steering what gets built next, which is the honest version of a priority commitment.
The rest of it
- Page reference — every main Trident page, what it holds, and what the actions on it do.
- Privacy — where the data sits, how the fields are classified, what the telemetry carries.
- Licence terms — the pilot template.
- Product page — what Trident does, with screenshots.